How to unwrap images using transform query in JAVA SDK as CDAAsset is not serializable ?

How to handle unwrapping using transformquery in java sdk for image attribute as CDAAsset cannot be unwrapped? for example
@TransformQuery.ContentfulEntryModel("article")
public class Article implements Serializable {
@TransformQuery.ContentfulField("image")
private CDAAsset image;
@TransformQuery.ContentfulField("title")
private String title;
@TransformQuery.ContentfulField("description")
private String description;
@TransformQuery.ContentfulField("link")
private String link;
}
it fails with content type CDAAsset not able to serailize

Hey @ritz0106
if you take a look at sample test here: https://github.com/contentful/contentful.java/blob/master/src/test/java/com/contentful/java/cda/integration/Integration.java#L708 unwrapping is possible for CDAAsset fields. CDAAsset is also serializable, so maybe removing implementing Serializable interface for Article will help.

Please reopen if the issue still happens


[rayci] add artifact dir for windows

Add artifact dir for windows. Create a new windows jobenv that mounts artifact dir, this is for safe roll out of this feature (the new jobenv requires the existent of the artifact dir that needs to set up in pre-commit).
Test:

CI

added the mount_windows_artifact field


Center view using Stevia?

How do you center a view using Stevia?

You would use view.centerInContainer()


Default chunk_size and cores to ppj

Back in issue #49 we discussed having chunk size defaulting to the ppj, but we lost track of that issue so I'm filing this.
I'm thinking it the logic should be: unless overridden in the environment or command-line, -c and -j both default to --ppj. That way, you default to running as many commands in parallel in a job as you have processors allocated, and the user only needs to change one option, --ppj, if they want to scale that up or down.

Er, to be clear, setting --ppj on the command line should adjust -j and -c unless they are also set. This isn't the case right now.

Yes, definitely agree.
Sidenote: do we handle infinite chunk size yet? I think we said if chunks are "0" we allow arbitrarily large chunks?

Gabe, can you have a look at this fix and let me know what you think.

This fix up looks okay to me, other than to generalize the default class a bit further if possible.

We could generalize but then there might be too much metaprogramming black magic. I'll have a think about it this evening.

On Apr 21, 2016, at 10:35 AM, Gabriel A. Devenyi<EMAIL_ADDRESS>wrote:
This fix up looks okay to me, other than to generalize the default class a bit further if possible.
—
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub

Lets handle this via #85


improvements to  FillImputer and UnivariateFillImputer unsupervised models

This PR

Makes FillImputer and UnivariateFillImputer models slightly more efficient
Add an error msg when applying UnivariateFillImputer to a  column v of scitype AbstractVector{Union{Missing, <:Finite}} if  the column doesn't contain the same levels as that of the categorical value imputer to be imputed. (i.e all( in( levels(filler) ), levels(v) ) == true).
The user can now specify the categorical value filler which is to be imputed in a column v of scitype AbstractVector{Union{Missing, <:Finite}} provided the categorical value filler to be imputed is taken from any categorical vector with the same levels as that found in v.
The following example shows the third point.

julia> using CategoricalArrays: pool

julia> using DataFramesjulia> using MLJ
[ Info: Precompiling MLJ [add582a8-e3ab-11e8-2d5e-e98b27df1bc7]
[ Info: Model metadata loaded from registry.

julia> data = (b=["hello", missing, "world"],) |> DataFrame
co3×1 DataFrame
│ Row │ b       │
│     │ String? │
├─────┼─────────┤
│ 1   │ hello   │
│ 2   │ missing │
│ 3   │ world   │

julia> coerce!(data, autotype(data, :string_to_multiclass))
3×1 DataFrame
│ Row │ b       │
│     │ Cat…?   │
├─────┼─────────┤
│ 1   │ hello   │
│ 2   │ missing │
│ 3   │ world   │

julia> mode(data.b)
CategoricalValue{String,UInt32} "hello"

# specify a categorical value `lev` to be imputed. `lev` is taken from a categorical vector `x` with
# the same levels as that found in `data.b` or `transform` will error.
julia> get_level(x, lev) = pool(x)[get(pool(x),  lev)]    # this line edited by @ablaom
get_level (generic function with 2 methods)

# replaces `missing` with `"world"` instead of the mode (`"hello"`)
julia> mach = fit!(machine(FillImputer(features = [:b], finite_fill = e -> get_level(data.b, "world")), data))
[ Info: Training Machine{FillImputer} @384.
Machine{FillImputer} @384 trained 1 time.
  args:
    1:	Source @123 ⏎ `Table{AbstractArray{Union{Missing, Multiclass{2}},1}}`

julia> MLJ.transform(mach, data)
3×1 DataFrame
│ Row │ b     │
│     │ Cat…  │
├─────┼───────┤
│ 1   │ hello │
│ 2   │ world │
│ 3   │ world │

@OkonSamuel Thanks for that. 1 and 2 sound like a good idea.
As far as 3 goes, this already works, no?
import DataFrames
using MLJ

data = (b=["hello", missing, "world"],) |> DataFrames.DataFrame

coerce!(data, autotype(data, :string_to_multiclass))
world = transform(data.b, "world")
mach = machine(FillImputer(features = [:b],
                           finite_fill = e -> world), data) |> fit!

julia> transform(mach, data)
3×1 DataFrame
│ Row │ b     │
│     │ Cat…  │
├─────┼───────┤
│ 1   │ hello │
│ 2   │ world │
│ 3   │ world │

Note that instead of your get_level, I'm using transform, which has been overloaded in MLJBase to do the same thing (see doc-string below).
So can you explain why the code labelled as "hack" in your PR is necessary. What am I missing here?

transform(e::Union{CategoricalElement,CategoricalArray,CategoricalPool},  X)

Transform the specified object X into a categorical version, using
the pool contained in e. Here X is a raw value (an element of
levels(e)) or an AbstractArray of such values.
v = categorical([:x, :y, :y, :x, :x])
julia> transform(v, :x)
CategoricalValue{Symbol,UInt32} :x

julia> transform(v[1], [:x :x; missing :y])
2×2 CategoricalArray{Union{Missing, Symbol},2,UInt32}:
 :x       :x
 missing  :y

---

Note that instead of your get_level, I'm using transform, which has been overloaded in MLJBase to do the same thing (see doc-string below).

Great. This makes this even simpler.

So can you explain why the code labelled as "hack" in your PR is necessary. What am I missing here?

Sorry. i should have made the last commit more explanatory. Initially i thought this wasn't possible due to an issue someone was experiencing on slack but after much investigation i found out that the hack wasn't needed so i removed it in the clean-up commit.(
https://github.com/alan-turing-institute/MLJModels.jl/pull/292/commits/16727fe1fa2a99e1d53f7545a89e8ddabdd6aa4b)


Lookup session by capability

Fixes #562 where view and command-based LSP code only looks at scope to find the most suitable session.
In a case where two servers run for the same scope (eg. typescript and eslint server on source.js), LSP would pick the first session, instead of checking which server provides the relevant capability.

Coverage increased (+0.1%) to 37.064% when pulling e7660f8c32e06d91b35e4e2b0c8e2792ead7d906 on lookup-by-capability into 7bb8de0bb5924b7ea41e1b943ce384a3f0d43766 on master.


Add GetDetailedStatus to support polling LRO intermediate progress

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.MySql


NEW: Add test for PHP 7.3 support

Just pushing this PR as an experiment, to see where the travis-CI support is at, and also to see whether 3.x-dev already supports it. With 3.x support likely in some form until late 2019 / early 2020, being able to run it on PHP 7.3 would be handy if feasible.

We could put this in allowed failures and merge it. 7.3 support tracker: https://github.com/travis-ci/travis-ci/issues/9717

IMO allowed_failures have very little value and simply burn through our build quota. I'll close the PR and reopen it once that travis ticket is closed.

As with #8432 I think this is good to merge since PHP 7.3 is in RC now we shouldn't expect any breaking changes for new features to be introduced


Full support for pruned nodes

Bitfeed can run on a pruned node (#49), but the user experience is degraded and some features don't work.
Handling pruned data more gracefully would enable full support for pruned nodes.

[ ] Friendly error message when a searched block or transaction is unavailable due to pruning.
[ ] Fetch prevouts using gettxout instead of getrawtransaction for transactions in the mempool.

even if an ancestor transaction is pruned, the input we need is still stored in the UTXO cache.

(only works for mempool transactions)

[ ] Special handling for pruned/unavailable inputs in the transaction details diagram

Label input address as 'pruned' or 'missing'
Label amount as 'unknown'
Set input line weight as the average unknown fee (i.e. share unused value equally across missing inputs)

Draw in a different color?

When the transaction without information that is in the mempool
the input is "unknown" and the fee paid does not appear due to not knowing
Note: when I wrote in #49, the screen also did not appear

on the other hand transactions he doesn't know and are already in the block he doesn't show anything
https://user-images.githubusercontent.com/9739913/169853274-e83ec089-6b9a-41ef-926e-29a7780ac770.mp4


Update typescript definitions

The typing definitions of React can no longer be installed as a global module. It throws the cannot find name space React, so I think it'd be better to add import * as React from react at the top.
I also added the definition of <Item/>  and updated <ListItem/>,<Icon/>

The module name was incorrect in the first file. I'll resubmit later


drivers device instances

We should keep lists (probably per bus) of all the Device (I2C/SPI/CAN) instances in the system.

this would make deconfliction easier and explicit
allow us to drop unnecessary CDev usage (/dev/mpu6000_accel, /dev/mpu6000_accel1, /dev/mpu6000_accel_ext, /dev/mpu6000_accel_ext1, etc https://github.com/PX4/Firmware/blob/master/src/drivers/mpu6000/mpu6000.h#L52)
improve the debug tooling/reporting

print a simple summary of all drivers by bus, address, configuration, driver type

it might make sense for serial drivers (eg most lidar, px4io) to become Devices as well

@davids5

GitMate.io thinks possibly related issues are #7675 (Some questions about  “mc_att_control” hope to get help), #6193 (GPS altitude spike feeding into altitude control loop despite GPS fusion disabled), #8315 (drivers unification), and #8525 ( adis16448 driver question??).

Still relevant

Done!


coverage: When enable coverage, some testcases need more time

Describe the bug
I am testting coverage on qemu_arc_em and nsim_em with sanitycheck. I found that when enable coverage, some testcases will timeout.

nsim_em:

tests/lib/heap_align/lib.heap_align FAILED: Timeout
tests/kernel/timer/timer_monotonic/kernel.timer.monotonic FAILED: Timeout
tests/crypto/mbedtls/crypto.mbedtls FAILED: Timeout
tests/kernel/lifo/lifo_usage/kernel.lifo.usage FAILED: Failed

The above 3 timeout failures will pass when use west,. But accoding to the console output, these testcases need more time to finish
For tests/kernel/lifo/lifo_usage/kernel.lifo.usage, if increase timeout (K_MSEC(timeout + 10)) , it will pass. For examples, K_MSEC(100).
https://github.com/zephyrproject-rtos/zephyr/blob/3dba8cc8509b1c52d5bebf6eafcf95c0eb8b2cbe/tests/kernel/lifo/lifo_usage/src/main.c#L328

qemu_arc_em:

ERROR   - qemu_arc_em               samples/portability/cmsis_rtos_v2/timer_synchronization/sample.portability.cmsis_rtos_v2.timer_synchronization FAILED: Exited with 1
ERROR   - qemu_arc_em               samples/scheduler/metairq_dispatch/sample.kernel.metairq_dispatch FAILED: Exited with 1
ERROR   - qemu_arc_em               samples/portability/cmsis_rtos_v1/timer_synchronization/sample.portability.cmsis_rtos_v1.timer_synchronization FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/portability/cmsis_rtos_v2/portability.cmsis_rtos_v2 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/subsys/logging/log_immediate/logging.log_immediate FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/subsys/logging/log_immediate/logging.log_immediate.clean_output FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/posix/common/portability.posix.common        FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/posix/common/portability.posix.common.newlib FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/portability/cmsis_rtos_v1/portability.cmsis_rtos_v1 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/workq/critical/kernel.workqueue       FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/workq/work_queue/kernel.workqueue     FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/workq/work_queue_api/kernel.workqueue.api FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.multiq FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/sleep/kernel.common.timing            FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler   FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.multiq_no_timeslicing FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.no_timeslicing FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/preempt/kernel.scheduler.preempt FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/queue/kernel.queue.poll               FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/queue/kernel.queue                    FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/pipe/pipe/kernel.pipe                 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/pipe/pipe_api/kernel.pipe.api         FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/mem_pool/mem_pool_threadsafe/kernel.memory_pool.threadsafe FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/mem_pool/mem_pool_concept/kernel.memory_pool.concept.legacy FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/common/kernel.common                  FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/common/kernel.common.misra            FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/context/kernel.common                 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout.poll FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_api/kernel.fifo             FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_api/kernel.fifo.poll        FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/mbox/mbox_usage/kernel.mailbox.usage  FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/crypto/mbedtls/crypto.mbedtls                FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/benchmarks/timing_info/benchmark.kernel.timing.default FAILED: Exited with 1

I tested samples/portability/cmsis_rtos_v2/timer_synchronization with west , if I increase the TIMER_TICKS to 250, it will pass:
https://github.com/zephyrproject-rtos/zephyr/blob/3dba8cc8509b1c52d5bebf6eafcf95c0eb8b2cbe/samples/portability/cmsis_rtos_v2/timer_synchronization/src/main.c#L15

not sure how the timeout in the code relates to the timeout of running the test and failing due to timeouts in sanitycheck.

are any of these tests CPU bound? coverage accounting will add nontrivial overhead.

I think this one was already fixed with recent move to multiprocessing.


share token spread around

Tasks

[ ] add a const variable that holds the shared token (currently 2arzyJZYj2oNnHX)
[ ] use it in frontend/src/features/landing_page/components/GeoMap.tsx
[ ] use it in ontend/src/features/landing_page/components/Teammember.tsx
[ ] use it in frontend/src/features/map_planning/layers/plant/components/PlantingElement.tsx
[ ] use it in frontend/src/features/map_planning/layers/plant/components/PlantListItem.tsx
[ ] use it in  frontend/src/features/map_planning/layers/plant/components/PlantingElement.tsx
[ ] use it in frontend/src/features/landing_page/components/BlogOverview.tsx

Use case
nextcloud integration
Related Pull request
#729

Probably it is not the best idea to make a dependency across all these features. And it is relatively easy to search&place all occurrences. So I'll close the issue for now.


Port packaging scripts from Cirq

Fixes #483

Can you explain what this PR does?

It adds scripts related to packaging and uploading to PyPI. For instance, you can cut a new release with a one-line command. You can also cut a dev release, or upload a release to the Test PyPI and verify that the release works as expected, which is good to do before doing a real release.

@Strilanc I made the changes but staled your review

... but I need this right now. Anyway, it's pretty clear that I just did what you said.


Handle NULL states in send/recv functions

Just saw this:
treasury_pipelinedb | Segmentation fault (PID 146)
treasury_pipelinedb | version: PipelineDB 0.9.6 at revision 0fbff9211a2f5275f40e8a69630a37b9833a5338 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
treasury_pipelinedb | backtrace:
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (debug_segfault+0x15)[0x60db15]
treasury_pipelinedb | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fc9ca0478d0]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (numaggstatesend+0x16)[0x73ce16]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   [0x5b9ea2]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (ExecProject+0x175)[0x5bf705]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   [0x5c4b06]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (ExecAgg+0xb8)[0x5c4c48]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (ExecProcNode+0x95)[0x5b8a15]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (ExecutePlan+0x45)[0x5b6f25]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (ContinuousQueryWorkerMain+0x1e4)[0x6575d4]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   [0x656c1f]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (StartBackgroundWorker+0x181)[0x660151]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   [0x66bdd2]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   [0x474cde]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (PostmasterMain+0xe8a)[0x66da5a]
treasury_pipelinedb | pipelinedb: bgworker: worker0 [pipeline]   (main+0x3fd)[0x475c9d]
treasury_pipelinedb | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fc9c9080b45]

I'm using FILTER in aggregates so my guess is that if everything is filtered by the aggregate, the state is NULL, and we need to handle it here: https://github.com/pipelinedb/pipelinedb/blob/6bd75dd0bfe003deac472ae22d1573098770fae2/src/backend/utils/adt/numeric.c#L7778

@usmanm I just noticed that you're running 0.9.6 here. This issue was actually by https://github.com/pipelinedb/pipelinedb/commit/6bd75dd0bfe003deac472ae22d1573098770fae2, in which a few transout/combinein functions were made strict: NULL input -> NULL result, so the transout function body is never even reached)
Do you want a backport for 0.9.6? We'd just add a one-off patch to that version that doesn't touch catalogs, but obviously the ideal thing to do here is upgrade to 0.9.7. Binary upgrades work pretty well so it should be fairly easy. Anyways, just let me know what you need, happy to help!

Oh, I think I just pulled pipelinedb/pipelinedb from Docker Hub and didn't realize I was on a previous version. No need to back port! I will test with the latest version.

Cool, we were only pushing explicit versions to DockerHub, so latest was out of date. I just updated the builder to push both pipelinedb:<version> and pipelinedb:latest though.


add pages for sigstore-blog

Summary

add pages for sigstore-blog

dont need it is already applied :)


Contribution

Hello,
Can you please provide the accuracy results?
Thank you.

We provide some results in https://arxiv.org/pdf/1710.06081.pdf. Hope to be useful.


can't run/build project for web platform when import uni_link_desktop to any file of project

Please update to 0.1.6, it builds on the web, but it doesn't do anything on the web


misc/cgo/testplugin: TestIssue25756pie broken on darwin/arm64 on release-branch.go1.17

--- FAIL: TestIssue25756pie (1.25s)
    plugin_test.go:274: ./issue25756pie.exe: exit status 2
        panic: plugin.Open("life"): plugin was built with a different version of package sync/atomic

greplogs -l -e 'plugin was built with a different version of package sync/atomic' --since=2022-01-01
2022-05-18T16:46:28-0e7138a/darwin-arm64-11
2022-05-18T16:46:28-0e7138a/darwin-arm64-12
―
Curiously, this failed on the darwin-arm64-11 and darwin-arm64-12 builders but not darwin-arm64-11_0-toothrot. 🤔
I wonder if the new arm64 builders are misconfigured in some way?
(This is a release-blocker because darwin/arm64 is a first class port; attn @golang/release.)

It looks like the test is using the go command from $PATH rather than the one from GOROOT/bin:
https://cs.opensource.google/go/go/+/master:misc/cgo/testplugin/plugin_test.go;l=116;drc=afd181cf0b69c3591d7e47ceca4fabf14434d77e
That could have something to do with it.
(That will be fixed automatically by CL 404134, but that isn't even merged at head, let alone at 1.17.)

I can't reproduce this on a gomote instance. (I tried both go test ./cgo/testplugin and go tool dist test testplugin using a gomote push of the current release-branch.go1.17.)
I suspect that this may be a bad interaction with some bug in the buildlet binary on this builder, and possibly also a remaining bug in the test (https://golang.org/cl/407315 didn't fix it).
From the output of go version -m I determined that it is from some time at or after CL 356589 but before CL 381735 (Jan. 28). Notably, it does not include CL 354754.
As a next step I suggest that we bump the buildletVersion constant in cmd/buildlet and deploy a fresh build of it to these builders.

See also #46239. It is not reproducible locally or on gomote. The skip is specific to the toothrot builders https://cs.opensource.google/go/go/+/release-branch.go1.17:misc/cgo/testplugin/plugin_test.go;l=268

Just a hunch: https://go.dev/cl/353449 was included in Go 1.18, but not backported to 1.17. That might interact with dist test and the buildlet in some non-trivial way to produce what appears to be version skew due to a mismatched GOROOT.
I'll send a backport of that through the SlowBot to see if it fixes things. (https://go.dev/cl/407881)

Looks like that's the jackpot!
https://storage.googleapis.com/go-build-log/cefcdb71/darwin-arm64-12_6a7eca57.log


[BUGFIX] argilla: allow change default distribution values

Description

When creating a rg.Settings instance with default distribution, updates on the min_submitted attribute do not take effect.

settings = rg.Settings(fields=...)

settings.distribution.min_submitted= 3 # this not takes effect

Maybe related to https://github.com/argilla-io/argilla/issues/5718
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested

Checklist

I added relevant documentation
I followed the style guidelines of this project
I did a self-review of my code
I made corresponding changes to the documentation
I confirm My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@frascuchon not related to #5718 because that was an update through the UI that did not seem to take place.


Make sncast declare work with scarb 2.7.0

Which component is your feature related to?
Cast
Feature Request
When running sncast declare on Scarb 2.7.0, we get the following error:
error: An error occurred in the called contract = ContractErrorData { revert_error: "Sierra compilation error: Unable to compile Sierra to Casm. No matching ContractClass or CasmContractClass found for version 1.6.0" }

Because of this, the CI currently runs on the previous versions. After making sncast declare work with Scarb 2.7.0, please also change the CI to run on 2.7.0. Additionally, unignore this test: test_script_init_happy_case().

Solving this issue is blocked until devnet's next release and starknet-rs fix of this issue

We just need to bump starknet-rs to 660a732

It turns out that the issue still remains despite the starknet-rs fix - starknet-devnet-rs uses outdated starknet-rs dependencies without that fix.
Marking as blocked until devnet bumps SDK.

➜ sncast --profile dev-profile declare --contract-name ERC20 --fee-token strk
   Compiling snforge_scarb_plugin v0.31.0 (git+https://github.com/foundry-rs/starknet-foundry?tag=v0.31.0#72ea785ca354e9e506de3e5d687da9fb2c1b3c67)
    Finished `release` profile [optimized] target(s) in 0.16s
   Compiling starknet_erc20 v0.1.0 (/Users/qiaopengjun/Code/starknet-code/hello_starknet/starknet_erc20/Scarb.toml)
    Finished release target(s) in 4 seconds
[WARNING] Profile dev-profile does not exist in scarb, using 'release' profile.
command: declare
error: An error occurred in the called contract = ContractErrorData { revert_error: "Sierra compilation error: Unable to compile Sierra to Casm. No matching ContractClass or CasmContractClass found for version 1.6.0" }

Does anyone have a solution to this problem? What is the reason?


Add RPM signing check script

Adding a script that will verify that all RPM packages passed to it are signed.
It also automatically installs Microsoft public key.

This PR adds the script, but additional action (updating our release pipeline to use it) must be taken.


Clarify what is being faster

The README mentions several phrases, e.g. "for faster execution", "speed boost", "wrapped in performance.now() measurements". I think it is helpful for the reader (without the need to look at the benchmark code) to be very specific as to what timing metric is being measured and compared.

Good point. What could I do to make this clearer?
Essentially I run:
var start = performance.now();
// code goes directly here
var end = performance.now();
report(end - start) // this is a global function defined in index.html

Scripts are loaded 251 times (using random query string parameters to ensure the browser re-parses), then the median is taken. Arguably this should be more than 251 to reduce variance, but 251 seemed like a good balance between high variance and waiting a long time.
How would you recommend I amend the README? I'm happy to accept a pull request. :)

By "code goes directly here", what does code refer to? Please give an example with a hypothetical micro-library.

var start = performance.now();
window.MyModule = {hello: 'world'};
var end = performance.now();
report(end - start);

So is it that it only boosts initial execution? Execution during runtime (e.g. async tasks and event invoked code) is not touched by the optimization?

This optimizes parsing, not execution. Parsing is basically done when script is added to a page. So in general, yes, this boosts only startup, but isn't that a good thing already?

Yes, parsing is the major thing that's optimized here. My readme is a bit loosey-goosey about definitions; I could be clearer.

Optimize a JavaScript file for faster parsing execution.
Also benchmark on mobile where the parsing execution is very important will be great.

Indeed it would be good to clarify real world benefit, as by eye it just looks as micro optimization that doesn't bring any noticeable gain.
I take it boost purely parse time, and doesn't bring any improvements to execution time. Is that right? if so, can documentation provide some real world examples (using popular libraries), on why it's useful?
e.g. let's assume that parse time is 10ms, and execution time is 100ms, then if I read the doc correctly, using this module may (in best scenario) speed up my script from 110ms to 105ms.
I'd say that's nothing valuable, and seeing gain numbers as 57.09% in doc is very misleading to  unwary developers.

@medikoo If your parse times is 10ms on mobile, then obviously your don't need this optimization. It's opt-in after all. But thing is, benchmarks shown in readme are done on a good Macbook machine and there parse time numbers already often 50ms. I can clearly see that being 500ms on mobile (requires real benchmarks of course).
Anyway, every ms matters and as it's said in readme -- you shouldn't blindly apply with opt to your project. Test and measure first. If it gives boost, then it makes sense to use this opt.
P.S. But I agree anyway with requirement of clear docs and benchmarks on mobile (otherwise, indeed, you'll have hard time convincing people).

Same here! Would suggest something like "Optimize JavaScript to be parsed faster". Beside that I also wonder if it does affect runtime performance at all (i.e. does it change JIT at all)? I would not apply such a pattern until I'm certain that there are no hidden costs once you actually use the functions. It feels like it just postpones some engine steps that would otherwise be applied while parsing (for better JIT'ing?). Overall I agree that doing as much as possible lazy is a good idea, as long as there are no heavy costs involved later. So this seems use case specific and I guess one might see better performance if i.e. only one jQuery function is used. But testing this would certainly need detailed benchmarks; and interpreting the numbers could be quite difficult.

@mgrete Kyle wrongly used "JIT" word in this situation. JIT isn't related to lazy parsing, JIT is Just-In-Time compilation to machine code. E.g. for C++ you do that on build step, but for JS browsers do that when they load source code, i.e. Just-In-Time.

@NekR I actually wonder if this pattern influences how V8 can do JIT optimizations?

I'm fine to change the phrasing to emphasize "parsing." Execution does occur when the script is loaded, but using that phrase makes it sound like every API call is faster, which is not true.

@tchock @NekR I wrote a blog post some time ago describing this lazy parsing concept in more details: Lazy Parsing in JavaScript Engines.
Note: pre-parse is V8's specific term. In JavaScriptCore, it's simply called syntax checker.

@nolanlawson It'll be good to report the standard deviation of those measurements. Probably easier if you just use Benchmark.js. See also this excellent article from @mathias and @jdalton Bulletproof JavaScript benchmarks

Thanks for the links; I'll take a look. The benchmarking here could definitely be more rigorous. I didn't use benchmark.js because I didn't see an easy way to hook it in and do the full re-evaluation (e.g. note how I had to append random query params to ensure code wasn't pre-cached/-JITed).


NEW API: GetObjectAttributes

This PR is related to https://github.com/minio/minio/pull/18732
P.s. the CI/CD tests will fail until we update the main repo with the new endpoint.

IMO you should make this easier to use and abstract away the overly complicated parts (pun not intended, but nice).

The api has been simplified based on our discussion today, I will double check AWS behavior tomorrow when it comes to large part numbers.

@zveinn
Running lint check
Error: api-get-object-attributes.go:65:1: exported: comment on exported type ObjectAttributePart should be of the form "ObjectAttributePart ..." (with optional leading article) (revive)
// ObjectAttributesResponse ...
^
Error: constants.go:63:2: exported: exported const GetObjectAttributesTags should have comment (or a comment on this block) or be unexported (revive)
	GetObjectAttributesTags = "ETag,Checksum,StorageClass,ObjectSize,ObjectParts"
	^
Error: make: *** [Makefile:15: lint] Error 1

@zveinn
Kinda interesting this gets thrown...
{"args":{"bucketName":"minio-go-test-rizxvdf5fd4dqwbk","objectName":"file2","opts":"minio.ObjectAttributesOptions{}"},"duration":6607,"error":"XML syntax error on line 1: invalid UTF-8","function":"GetObjectAttributes(ctx, bucketName, objectName, opts)","message":"GetObjectAttributes failed","name":"minio-go: testGetObjectAttributes","status":"FAIL"}

Something is broken in the tests as well now because in this PR master branch runs fine with MinIO latest release.
{"args":{"bucketName":"minio-go-test-riqvc9tscw0inoj5","contentType":"","filePath":"","metadata":"custom/contenttype","objectName":"ugqepx3npjrsgnzcb1940qnoiikd5y","sse":{}},"duration":62,"function":"FPutEncryptedObject(bucketName, objectName, filePath, contentType, sse)","name":"minio-go: testSSES3EncryptionFPut","status":"PASS"}
{"args":{"bucketName":"minio-go-test-t1jmaabgxw9mey3i","objectName":"v33nnuhfn0gdkz1wbqjhmsx3gjn6gx"},"duration":4491,"function":"GetObject(bucketName, objectName)","name":"minio-go: testSSES3EncryptedGetObjectReadAtFunctional","status":"PASS"}
{"args":{"bucketName":"minio-go-test-3v21332559zpfsz4","objectName":"ob2ojnkoranpdpgvf5tsnnqch0vjgc"},"duration":7785,"function":"GetObject(bucketName, objectName)","name":"minio-go: testSSES3EncryptedGetObjectReadSeekFunctional","status":"PASS"}
{"args":{"destination":{"Bucket":"minio-go-test-rplpr2u4nzbis0ct","Object":"srcObject","Encryption":null,"UserMetadata":null,"ReplaceMetadata":false,"UserTags":null,"ReplaceTags":false,"LegalHold":"","Mode":"","RetainUntilDate":"0001-01-01T00:00:00Z","Size":0,"Progress":null},"source":{"Bucket":"minio-go-test-rplpr2u4nzbis0ct","Object":"srcObject","VersionID":"","MatchETag":"","NoMatchETag":"","MatchModifiedSince":"0001-01-01T00:00:00Z","MatchUnmodifiedSince":"0001-01-01T00:00:00Z","MatchRange":false,"Start":0,"End":0,"Encryption":{}}},"duration":262,"function":"CopyObject(destination, source)","name":"minio-go: testEncryptedSSES3ToSSES3CopyObject","status":"PASS"}
{"args":{"destination":{"Bucket":"minio-go-test-9q30ubdszad5fhmk","Object":"srcObject","Encryption":null,"UserMetadata":null,"ReplaceMetadata":false,"UserTags":null,"ReplaceTags":false,"LegalHold":"","Mode":"","RetainUntilDate":"0001-01-01T00:00:00Z","Size":0,"Progress":null},"source":{"Bucket":"minio-go-test-9q30ubdszad5fhmk","Object":"srcObject","VersionID":"","MatchETag":"","NoMatchETag":"","MatchModifiedSince":"0001-01-01T00:00:00Z","MatchUnmodifiedSince":"0001-01-01T00:00:00Z","MatchRange":false,"Start":0,"End":0,"Encryption":{}}},"duration":261,"function":"CopyObject(destination, source)","name":"minio-go: testEncryptedSSES3ToUnencryptedCopyObject","status":"PASS"}
{"args":{"destination":{"Bucket":"minio-go-test-1kleakxixnvtqvnj","Object":"dstObject","Encryption":{},"UserMetadata":null,"ReplaceMetadata":false,"UserTags":null,"ReplaceTags":false,"LegalHold":"","Mode":"","RetainUntilDate":"0001-01-01T00:00:00Z","Size":0,"Progress":null},"source":{"Bucket":"minio-go-test-1kleakxixnvtqvnj","Object":"srcObject","VersionID":"","MatchETag":"","NoMatchETag":"","MatchModifiedSince":"0001-01-01T00:00:00Z","MatchUnmodifiedSince":"0001-01-01T00:00:00Z","MatchRange":false,"Start":0,"End":0,"Encryption":null}},"duration":233,"function":"CopyObject(destination, source)","name":"minio-go: testUnencryptedToSSES3CopyObject","status":"PASS"}
{"args":{},"duration":151,"function":"CopyObjectPart(destination, source)","name":"minio-go: testUnencryptedToSSES3CopyObjectPart","status":"PASS"}
{"args":{},"duration":135,"function":"CopyObjectPart(destination, source)","name":"minio-go: testSSES3EncryptedToUnencryptedCopyPart","status":"PASS"}
{"args":{},"duration":169,"function":"CopyObjectPart(destination, source)","name":"minio-go: testSSES3EncryptedToSSES3CopyObjectPart","status":"PASS"}

However this PR is passing GetObjectAttributes but failing in other places.


Bluetooth: Mesh: Test provisioning multiple devices

Adds a BabbleSim test for provisioning multiple devices in a row. This
scenario had a regression in #33782, which is fixed in #35405.
Signed-off-by: Trond Einar Snekvik<EMAIL_ADDRESS>Expected to fail until #35405 is merged.

@trond-snekvik CI is still failing even though #35405 was already merged. Could you look into it?

@trond-snekvik CI is still failing even though #35405 was already merged. Could you look into it?

Just needed a rebase :slightly_smiling_face:


Make games discrete

play to 5 or 7 or something and then declare a winner, reset scores, reshuffle deck etc

Just fixed in 7c4e313692b35ea6a264a81fe5b5433faa1964b0


Add support for unpatched_vulnerabilities

Ref: EC-216

Codecov Report

Merging #797 (f0ef51a) into main (0ed9fe3) will not change coverage.
Report is 11 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #797   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           86        84    -2
  Lines         3342      3435   +93
=========================================
+ Hits          3342      3435   +93

Files
Coverage Δ

policy/lib/rule_data.rego
100.00% <ø> (ø)

policy/lib/tekton/pipeline.rego
100.00% <100.00%> (ø)

policy/lib/tekton/task.rego
100.00% <100.00%> (ø)

policy/lib/tekton/task_test.rego
100.00% <100.00%> (ø)

policy/pipeline/required_tasks.rego
100.00% <100.00%> (ø)

policy/pipeline/required_tasks_test.rego
100.00% <100.00%> (ø)

policy/release/attestation_type.rego
100.00% <100.00%> (ø)

policy/release/attestation_type_test.rego
100.00% <100.00%> (ø)

policy/release/cve.rego
100.00% <100.00%> (ø)

policy/release/cve_test.rego
100.00% <100.00%> (ø)

... and 15 more


Remove copying the go client binaries when gradlew startup

Motivation:
Every time the server starts using gradlew startup, it copies the go client binaries under dist folder.
Most of the tasks in gogradle does not support the input and output yet, it does not skip the tasks although there's no modified sources. Therefore, It takes a lot to startup.
Modifications:

Remove copying the go client binaries when gradlew startup

Result:

Starting ther server is faster

Codecov Report

Merging #70 into master will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
- Coverage   49.06%   48.96%   -0.11%
==========================================
  Files         211      211
  Lines        9779     9779
  Branches     1319     1319
==========================================
- Hits         4798     4788      -10
- Misses       4242     4255      +13
+ Partials      739      736       -3

Impacted Files
Coverage Δ

.../linecorp/centraldogma/client/AbstractWatcher.java
42.85% <0%> (-6.73%)
:arrow_down:

...internal/storage/repository/git/GitRepository.java
74.84% <0%> (-0.31%)
:arrow_down:

Continue to review full report at Codecov.

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

A lot of tasks in gogradle does not support inputs and ouputs yet. https://github.com/gogradle/gogradle/issues/131

Replaced by #73


add support for merge operation

add support for merge operation

This has a dependency on   https://github.com/finos/legend-pure/pull/452


Nx and Vite handling conflict of .env files

the ideal priority
/apps/[app]/.env.[mode].local
/apps/[app]/.env.[mode]
/apps/[app]/.env.local
/apps/[app]/.env
/.env.[mode].local
/.env.[mode]
/.env.local
/.env
but if there is an environment variable in both above file, the one in [mode] will not take effect
the reason is that Nx will first process /apps/[app]/.env.local /apps/[app]/.env /.env.local /.env，and Nx does not support mode mode，[mode] files will not be processed
when the Vite executor is executed, Vite will process all .env files, but at this time the environment variable Vite pre-processed by Nx will not overwrite

https://github.com/chf007/vite-plugin-nx-dotenv
I wrote a plugin for Vite to temporarily solve this problem.

Cool fix @chf007! If you want, you can open a PR and add a snippet in the @nx-plus/vite README about this package

There are still some problems with the plugin: because the priority of the plugin cannot be higher than the Vite built-in define plugin, the ideal priority cannot be achieved in the build mode.
At present, it may only be solved by giving pr to Vite.

There are still some problems with the plugin: because the priority of the plugin cannot be higher than the Vite built-in define plugin, the ideal priority cannot be achieved in the build mode.
At present, it may only be solved by giving pr to Vite.

This problem has been solved in vite-plugin-nx-dotenv version 1.0.1, regardless of serve mode or build mode, we can correctly get the desired environment variable value.


Multi-threading api problem

I made a global ServiceProvider from where each thread gets it's api, but one thread is using the websockets, I don't know if that is a problem? But the application now works fine for 1-3 days until it closes without any error. You have any ideea what is happening? Because with the older version of API  worked fine.

Hi, after I updated all the reference dll files and visual studio, now seems to work, except the api rate limiter for the order processor (which runs on another thread), it is too aggressive and cannot process the orders when there is more than 2-3 open orders, after manual stop and restart of the candlestick reader thread it continues to execute orders until it blocks again and some orders remain unfilled forever because of this. It's strange that when restarting the other thread it continues with the order processor thread and there are 1sec delays for each one.
Please note that binance let's a higher number of requests if larger amounts of orders get filled and without many unfilled moving orders.

@sonvister ok I will try to find the issue, the app is definitely not requesting more than 2-3/sec in total from all the threads combined and it hits the rate limiter very often when using the orders (cancel, get bid price, post new order and get order status), stopping and restarting the other thread it continues to work normally for a period of time.

Try refactoring your code completely using async - await. I guess you're mostly using sync code.


action update wipes previous state of action

Describe the bug
Create an action, then update it only to attach a new parameter or annotation. This will wipe the code attached to the action so that subsequent invokes fail. Opening this is a bug because this is very different from wsk's implementation which permits updating an action piecemeal.
To Reproduce
> ./bin/run runtime:action:create foo ~/projects/openwhisk/tests/dat/actions/hello.js

> ./bin/run runtime:action:invoke foo -p payload world -r
{
  "payload": "hello, world!"
}

> ./bin/run runtime:action:update foo -p payload world

> ./bin/run runtime:action:invoke foo -r
 ›   Error: failed to invoke the action: 502 Bad Gateway
 ›     specify --verbose flag for more information

> ./bin/run runtime:action:get foo --save && cat foo.js

Expected behavior
Expecting a parameter update to just attach the parameters, not affect the entire action.

Some preliminary inspection of the code suggests the issue is related to an restriction in npm openwhisk itself which doesn't permit an update without specifying the code, and aio sets the code to '' to address that. 🤦♂


Remove ban reasons because they are not a thing in IRC anymore

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

No change log entry needed, just code clean-up

Will merge it in after #2667


Start sorting only after n typed chars

Filtering seems speedy; sorting seems kind of slow (at least on my crappy laptop). Waiting 1.5 (edit: 2.5) seconds for M-x is not an ideal user experience :/
It's probably a dumb suggestion, but what about waiting for a few keystrokes to limit the list before sorting (apart from recent items, obviously), or would that have to be implemented on the Ivy side? (edit: or company or what have you)

Well, the problem is the "apart from recent items" part. We do all the sorting at once, and it's pretty well optimized. I'm not sure it would be much faster to sort only based on recency. In fact, the recency-based sorting is probably the slowest part, because after that all we're going by is length.
You might think that we shouldn't have to sort the whole list just to present recent candidates. The main issue is that candidates which were previously selected might no longer be present in the collection. For example, a file might have been deleted. It would be very confusing if such candidates appeared, especially if they then disappeared when the full sort was done.
I agree with you wholeheartedly that waiting even 500ms for M-x is quite unacceptable, but unfortunately I haven't been able to think of any good ways to optimize further that will not have massive disadvantages.
One solution, of course, is to see how much performance is improved by gccemacs: https://akrl.sdf.org/gccemacs.html#orgb905200
Fundamentally, prescient.el is not implementing a complex algorithm, nor is it processing a lot of data, so a large part of the blame for slowness I think can be placed on the Emacs Lisp language implementation itself.
Let me know if you have any ideas or thoughts on this.


Add option to set bootnext on bootset

Add the Possibility to set the bootnext boot with the bootset tool

Dear @santos-lucas
Thanks a lot for this dev !
Yes you are right, this is a missing feature in bootset. Thanks for fixing it. 😊


Fix notebook cell selection

In #430, we made it so that cursorless will focus the correct cell when you issue a selection commands (eg "take"). However, this code doesn't always work. Not sure exactly when it fails, but we believe it's when the currently focused cell is off screen

I wonder if the new commands for notebook input focus will be helpful; we could try running interactive.input.focus at the start to see if it helps


Button hover colors should be in _variables.scss file

The mixin for button-variant is defined like this:
@mixin button-variant($background, $border, $active-background: darken($background, 7.5%), $active-border: darken($border, 10%))

Because of this, if you want to have the active background 10% darker or 7.5% lighter (for example) you either have to change the mixin file or write more custom css. This could be easily fixed:
/mixins/_buttons.scss
@mixin button-variant($background, $border, $active-background, $active-border)

_variables.scss
$active-background: darken($background, 7.5%);
$active-border: darken($border, 10%);

It looks as though this was probably the original intent, but somebody forgot to move those variables out of the mixin file.

Hi, I believe this has already been brought up, for example here: #23750

Hi @mwentz I think this is a good move, would you like to send a PR?

Remember that variables should follow the $component-state-property-size formula. So it might something like:
$btn-active-bg: darken($background, 7.5%);
$btn-active-border: darken($border, 10%);

Can I do this?

I though a lot about this, at first it seems like a great idea, but the variable would make much sense outside the mixing, at least not to me. I mean the darken function of background and border without context will just be really confusing for users.
I love the idea to abstract the active hover state in a way users can change it. Is there any way to do it with another approach?

Thanks @andresgalante for your thoughts. I created a PR with these changes before I saw your last comment. You are totally right, so I closed the PR.

So basically the context of $background and $border are local variables so it does not make sense to extract them out into the _variables.scss file.

Well... it makes sense for you an me that we know the mixin and the context where btns are defined, but I don't think it does for users (and maybe I am completely wrong).
I honestly have been thinking a lot about how to abstract that into a variable to help you out, and I can't find a good way yet. Let's keep digging on this one, it'd be a huge win IMO if we can give the users the opportunity to change the hover and active state on the variables.
Thanks a lot for your patience with me.

Closing as a won't fix—leaving these as-is.

@andresgalante I find myself struggling with the button mixins often enough with the need to modify some states (especially the hard-coded percantages and 'lighten' vs 'darken'). As far as I can see the approach of the opening comment wouldn’t work, not so much because of the confusion, but because the $background variable is undefined until it gets set in the @each loop in /scss/_buttons.scss
How about a solution along these lines – this approach would users let easily adjust the percentages as well as the color funcion:
/scss/mixins/_buttons.scss
@mixin button-variant(
  $background,
  $border,
  $change,
  $btn-hover-change-bg,
  $btn-hover-change-border,
  $btn-active-change-bg,
  $btn-active-change-border) {
    @if $change == "darken" {
      $hover-bg:     darken($background, $btn-hover-change-bg);
      $hover-border: darken($border, $btn-hover-change-border);
      $active-bg:    darken($background, $btn-active-change-bg);
      $active-bg:    darken($border, $btn-active-change-border);
    } else {
      $hover-bg:     lighten($background, $btn-hover-change-bg);
      $hover-border: lighten($border, $btn-hover-change-border);
      $active-bg:    lighten($background, $btn-active-change-bg);
      $active-bg:    lighten($border, $btn-active-change-border);
    }

    ...

  }
}

/scss/_variables.scss
$btn-change: "darken";
$btn-hover-change-bg: 7.5%;
$btn-hover-change-border: 10%;
$btn-active-change-bg: 10%;
$btn-active-change-border: 12.5%;

Hi @johanneskrtek thanks for sending your idea. This issue had come up and was closed at least 2 times. I'll be happy to review a PR with your idea, but at mdo will have the final word on this subject.

Hi, I‘d be happy to provide a PR with a good solution for the button mixin. The buttons are a rather interconnected topic, so I’d like to improve my idea first so we won’t end up with a hasty result. E.g. from my own experience users might want to be able to switch between 'lighten' and 'darken' for the hover and active state independently. I’m also aware of the elegance of the current solution, it’s just a bit inflexible due to the hard-coded parts. I’ll try to strike a balance.

@andresgalante here you go: #24682.


There is no directive with "exportAs" set to "mdMenu" ("

I'm implementing the mdMenu/matMenu component and get:
There is no directive with "exportAs" set to "mdMenu" ("
when I ng serve.

I'm running material "@angular/material": "^2.0.0-beta.11",
I've imported MatMenuModule into a custom material module that is imported by my apps shared module so it is available. I've tried importing directly to component, no difference. Actually I even removed MatMenuModule completely from the app and I still get the same issue. I do not understand what the error is implying. Any help understanding and debugging this?

Show your full code, please.

See https://github.com/angular/material2/issues/7306

Closing as duplicate of: #7306


Add biome?

See:
https://twitter.com/BenBondLamberty/status/1144294126269022208
https://en.wikipedia.org/wiki/Holdridge_life_zones

This is on the google form.

Nah. Ameriflux uses the Köppen climate classification, which is much more precise, and there's an R package to assign these automatically. Removing CSR_BIOME from the current master and renaming this issue.


add ci configuration

We've decided to leave Rubocop failed until next task

Rubocop's already fixed, but tests are crashed. Will fix it myself


Set new-task window height to a fixed amount and blurred the background on opening

Turns out dynamically resizing an element based on text size is a chore so I settled on a fixed window with nice scrolling. I also added animations to blur the tasks for a cleaner look.

I also hosted this updated version at salocor.github.io/todo-list-app

Sure

Alright there we go I think I got it. Let me know if there's anything else you need me to do. 😄

Great work @salocor! Thank you so much for contributing!
Let's get it merged🚀


Dragging immediately

Hi there. Is there a way to drag immediately on press without waiting long press?

did you try onPressIn?
onPress fires when the finger lifts up, so that won't work for dragging.


DecoderInitializationException occurs while implementing Drm media source

We face issues with the DRM encrypted MPD URLs on Android TV devices(however, its working fine on Android mobile devices and Android TV emulators) while the non-encrypted URLs are working fine.
We are getting the "MediaCodecRenderer$DecoderInitializationException: Decoder init failed: OMX.amlogic.avc.decoder.awesome.secure.Format"
We are initiating two instances of the player at the same time, one is for live streaming and the other for video-on-demand content. We are facing the issue only for video-on-demand content. But if we use only one player at a time it's working fine on real Android TV devices.
Here is the video-on-demand link we have used/tested:
https://e3ed58e1e3c374eda698a424a11aebee.egress.mediapackage-vod.us-east-1.amazonaws.com/out/v1/494048d66a244aa9892379629448d166/138b3fc7a3684793a728b23f431acfca/819e73eabaee4ce69400f6775496acad/index.mpd)

This isn't an issue with the codelab. If you have issues with ExoPlayer please file them at: https://github.com/google/ExoPlayer/issues


Deep subfolders are not included automatically in the index for public/modules///**/*.js

Hi how i can do for make the routine can detect more deep for javascript files in public?.
I got something like this  and its not recognizing:
public/modules/users/directives/Authorization/auth.js

but recongnize :
public/modules/users/directives/auth.js

It looks like you're using an older version of MEANJS; pre 0.4.0.
Try changing this line
https://github.com/meanjs/mean/blob/v0.3.3/config/env/all.js#L64 to 'public/modules/**/*.js',

Thanks!


Bilinear mode in topi::nn::upsampling not working

To repro, use following changes in test_topi_upsampling.py:
--- a/topi/tests/python/test_topi_upsampling.py
+++ b/topi/tests/python/test_topi_upsampling.py
@@ -22,7 +22,7 @@ def verify_upsampling(batch, in_channel, in_height, in_width, scale, layout='NCH
         raise NotImplementedError(
             'Layout not supported {} '.format(layout))

-    B = topi.nn.upsampling(A, scale, layout=layout)
+    B = topi.nn.upsampling(A, scale, layout=layout, method='BILINEAR')

     b_np = topi.testing.upsampling_python(a_np, scale, layout)

cc @srkreddy1238

@KeDengMS
NCH layout ???
Can you conform the error log ?

Yes NCHW layout, but I believe it exists in NHWC as well. The error is from a crash in dereferencing nullptr in here. The problem is that shape is a Mul node with two ImmInt as input, and as_const_int returns nullptr for non-const node.
It seems const folding should be applied, and moreover the bilinear interpolation code path needs to be tested.

@KeDengMS  a bit confused.
Is the issue about "Layout Not Supported" or "Crash " ?
Can you share complete log or the sample code?

I think it's nothing about Layout, but more for BILINEAR mode. The repro is to change the python test to use BILINEAR mode: B = topi.nn.upsampling(A, scale, layout=layout, method='BILINEAR'), then you'll find the crash.

But the log says NotImplementedError('Layout not supported {} '.format(layout)). What is the "layout" parameter you passed in? It should be "NCHW" or "NHWC".

The repro I show above is from git diff, not the log. The testcase tests both NCHW and NHWC

@KeDengMS I can repro your crash. The fix is to add util.simplify to https://github.com/dmlc/tvm/blob/master/topi/python/topi/nn/upsampling.py#L34

@srkreddy1238 I made a branch to fix this issue here. But some bilinear upsampling tests are failing. Can you have a look?

Thanks @KeDengMS  for bringing up the issue and thanks @masahi for finding the root cause and fix.
I have added the final piece (atol=1e-5 allowance) at #1708 for your review comment.

Thanks for the fix!


RuntimeError: Error(s) in loading state_dict for RWKV:

我使用 minipile 测试时：
python train.py --load_model /data/models/rwkv/RWKV-5-World-7B-v2-20240128-ctx4096.pth
--proj_dir /data/models/rwkv/lora --data_file /data/datasets/BlinkDL/minipile-tokenized/rwkv_vocab_v20230424/minipile
--data_type binidx --vocab_size 65536
--ctx_len 10 --epoch_steps 10 --epoch_count 100 --epoch_begin 0 --epoch_save 5 --micro_bsz 1
--n_layer 24 --n_embd 2048
--pre_ffn 0 --head_qk 0 --lr_init 1e-5 --lr_final 1e-5 --warmup_steps 0 --beta1 0.9 --beta2 0.99 --adam_eps 1e-8
--accelerator gpu --devices 1 --precision bf16 --strategy deepspeed_stage_2 --grad_cp 1
--lora_load rwkv-0 --lora --lora_r 64 --lora_alpha 128 --lora_dropout 0.01 --lora_parts=att,ffn,time,ln
报错如下：
INFO:pytorch_lightning.utilities.rank_zero:########## Loading /data/models/rwkv/RWKV-5-World-7B-v2-20240128-ctx4096.pth... ##########
Traceback (most recent call last):
RuntimeError: Error(s) in loading state_dict for RWKV:
size mismatch for emb.weight: copying a param with shape torch.Size([65536, 4096]) from checkpoint, the shape in current model is torch.Size([65536, 2048]).
size mismatch for blocks.0.ln1.weight: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.ln1.bias: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.ln2.weight: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.ln2.bias: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.ln0.weight: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.ln0.bias: copying a param with shape torch.Size([4096]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for blocks.0.att.time_mix_k: copying a param with shape torch.Size([1, 1, 4096]) from checkpoint, the shape in current model is torch.Size([1, 1, 2048]).
size mismatch for blocks.0.att.time_mix_v: copying a param with shape torch.Size([1, 1, 4096]) from checkpoint, the shape in current model is torch.Size([1, 1, 2048]).
size mismatch for blocks.0.att.time_mix_r: copying a param with shape torch.Size([1, 1, 4096]) from checkpoint, the shape in current model is torch.Size([1, 1, 2048]).
size mismatch for blocks.0.att.time_mix_g: copying a param with shape torch.Size([1, 1, 4096]) from checkpoint, the shape in current model is torch.Size([1, 1, 2048]).
size mismatch for blocks.0.att.time_decay: copying a param with shape torch.Size([64, 64]) from checkpoint, the shape in current model is torch.Size([32, 64]).
size mismatch for blocks.0.att.time_faaaa: copying a param with shape torch.Size([64, 64]) from checkpoint, the shape in current model is torch.Size([32, 64]).
size mismatch for blocks.0.att.receptance.weight: copying a param with shape torch.Size([4096, 4096]) from checkpoint, the shape in current model is torch.Size([2048, 2048]).
size mismatch for blocks.0.att.key.weight: copying a param with shape torch.Size([4096, 4096]) from checkpoint, the shape in current model is torch.Size([2048, 2048]).
size mismatch for blocks.0.att.value.weight: copying a param with shape torch.Size([4096, 4096]) from checkpoint, the shape in current model is torch.Size([2048, 2048]).
…………

看错参数了


.toolTip size = .bottom falls behind other widgets in view

Describe the bug
When .toolTip(side: .bottom) is set the tool tip doesn't seem to respect Z stack.  It puts the tooltip behind other widgets in the view.
To Reproduce
Steps to reproduce the behavior:

Set a tooltip to side: .bottom
Observe tool tip in view is below other widgets.

Expected behavior
It should respect Z stack; like .toolTip(side: .top) does.
Screenshots

.bottom
.top

Smartphone (please complete the following information):

Device: iphone SE (2023)
OS: iOS  17.3.1

i face the sam issue


Organize dependency versions

Description:
Currently dependency versions have been specified in modules and this led including different versions.
eg:- guava 2 versions are there in the lang repo
23.0 -> https://github.com/ballerina-platform/module-ballerinax-twitter/blob/main/gradle.properties#L10
30.0-jre -> https://github.com/ballerina-platform/ballerina-lang/blob/bc56b9d64ffb9601380a047c039e0e23b6120b9b/language-server/modules/langserver-core/build.gradle#L72
These should be avoided and versions have to be moved to gradle properties files and prevent them to happen

[ ] Move all the dependency versions to gradle.properties file
[ ] Remove duplicated dependencies with multiple versions
[ ] Identify remove unnecessary dependencies from pack
[ ] Configure dependencies with appropriately (eg:- Some required only to compile or tests)

Fixed in https://github.com/ballerina-platform/ballerina-lang/pull/33892


travis: Upload build artifacts for release branch.

Only upload's artifacts for release branch.

@cPhost looks like we can't build the 32-bit installers, right?

Finally after some more tries, got something working properly... Opening a new PR.


Procedurally Generate Solar System

For once, this should actually be easier than it sounds.

Just a bit late, but I've added a very basic procedural generation system (it could definitely be spiced up, but it's working!)


Unable to load GoogleCharts with Zone.js 0.8.8

After upgrading to Zone.js 0.8.8 I'm unable to load GoogleCharts library. It is working fine in 0.8.7 so I assume something went wrong in 0.8.8.
Here a simple example of the loader:
index.html:
<script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script>

app.ts:
google.charts.load('current', {'packages': ['corechart', 'gauge']});
google.charts.setOnLoadCallback(() => { ... });

What is the exception?

That's the funny part: there is no exception at all. It creates a script element to load https://www.gstatic.com/charts/45.1/loader.js and appends onload callback:
google.a.c.zb = function(a, c, d) {
        google.a.c.log("loadScript: " + a);
        var e = c.createElement("script");
        e.type = Ya;
        e.language = "javascript";
        e.async = !1;
        e.defer = !1;
        c = c.body || c.head || c.getElementsByTagName("HEAD").item(0) || c.documentElement;
        c.insertBefore(e, c.lastChild);
        d && google.a.c.md(e, d); <-- HERE
        e.src = a;
        google.a.c.log("end loadScript: " + a)
    }

google.a.c.md = function(a, c) {
        if (c)
            if ("undefined" === typeof a.onload) {
                var d = !1;
                a.onreadystatechange = function() {
                    d || (a.readyState && a.readyState !== K ? google.a.c.window.setTimeout(a.onreadystatechange, 100) : (d = !0,
                    a.onreadystatechange = Y(),
                    google.a.c.window.setTimeout(c, 0)))
                }
            } else
                a.onload = c <-- HERE (a is the script element, c is the callback)
    }

But the c above is never called....

OK, found it:
var value = originalDescGet.apply(this); <-- Value is null here
value = desc.set.apply(this, [value]); <-- Setter does not return any value (as far as I know) so value is changed to undefined
if (typeof target['removeAttribute'] === 'function') {
    target.removeAttribute(prop);
}
return value; <-- Here it is undefined, but should be null

And in GoogleCharts:
google.a.c.md = function(a, c) {
        if (c)
            if ("undefined" === typeof a.onload) { <-- Here the check obviously fails....and things do not work anymore
                var d = !1;
                a.onreadystatechange = function() {
                    d || (a.readyState && a.readyState !== K ? google.a.c.window.setTimeout(a.onreadystatechange, 100) : (d = !0,
                    a.onreadystatechange = Y(),
                    google.a.c.window.setTimeout(c, 0)))
                }
            } else
                a.onload = c
    }

ok, thanks, it has been fixed in #747.

Thanks! Just for info: when is the release planed? Thanks.

@Eddman, I am not sure the release date, it should be soon!

Has been fixed in 0.8.9, thanks.


Dynamically add items to Ionic 2 side menu

I am using latest version of ionic 2.
Ionic version: 2.1.8
I want to add item dynamically in a sidebar.
app.component.ts;
export class MyApp {

  pages: Array<{title: string, component: any, icon: any }>;

  this.pages = [
  { title: 'Dashboard', component: DashboardComponent, icon: 'ios-home-outline' },
  { title: 'Complaints', component: ComplaintPage, icon: 'ios-sad-outline' },
  { title: 'Suggestions', component: SuggestionPage, icon: 'md-bulb' },
  { title: 'Appreciations', component: AppreciationPage, icon: 'ios-thumbs-up-outline' },
  { title: 'Poll', component: PollPage, icon: 'ios-stats-outline' },
  { title: 'Survey', component: SurveyPage, icon: 'ios-analytics-outline' },
  { title: 'ReportIssue', component: ReportIssuePage, icon: 'ios-bug-outline' },
  ];

}

app.html
<ion-content>
  <ion-list>
    <button menuClose ion-item *ngFor="let p of pages" (click)="openPage(p)">
      <ion-icon item-left [name]="p.icon"></ion-icon>
      {{p.title}}
    </button>
  </ion-list>
</ion-content>

I want to show complaint item if complaint status is 'NEW'.
So, Is it possible to showing complaint item for some specific condition? I tried with ngIf but its do not work.
what is the best way to implement this kind of features?

Why don't you try asking in the support forum?

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!

Hi Tusharbalar, how did you get this solved. Kind Regards

I have implemented the same thing, and it's working correctly in my app
.ts file
export class MyApp {

  public status: boolean = false;
  @ViewChild(Nav) nav: Nav;
  constructor(public platform: Platform) {}

  initializeApp() {
    this.platform.ready().then(() => {
      this.networkService.checkNetworkStatus();
      StatusBar.styleDefault();
      Splashscreen.hide();
      this.getStatus();
      if (this.platform.is('ios')) {
        Keyboard.disableScroll(true);
      }
    });
  }

  getStatus(condition here) {
    if (your logic here) {
      this.status = true;
    } else {
      this.status = false;
    }
  }

}

HTML file
<ion-content>
  <ion-list>
    <button *ngFor="let p of pages"  *ngIf="status" menuClose ion-item (click)="openPage(p)">
      <ion-icon item-left [name]="p.icon"></ion-icon>
      {{p.title}}
    </button>
  </ion-list>
</ion-content>

Working as well. Thanks

how do i append pages from another page.
means :+1:
app.component.ts;
page content navmenu variables like pages,
but from another page i would like to append value in this.pages
from login.ts append below objects in existing variable which is available in  app.component.ts
how do i bind and sync
this.pages = [
{ title: 'Log out', component: logOut, icon: 'logout' },
{ title: 'abc', component: xyz, icon: 'ios-ls' },
];


[Feature Request] Wait at fort if lure is on

Short Description
When the bot reaches a fort that has a lure on, I'd like to be able to set the bot to wait at fort for a pre-determined amount of time, and/or until the lure has ended where the bot will continue walking on its 'route'.
While waiting at the fort, the bot will catch the lured pokemon (which is already in the code to do so), and would provide output as to how long it will remain at the lure for.
Possible solution

How it would help others
This gives the bot a more 'human' feel to it, and would potentially allow for rarer Pokemon to be caught via a lure which has been set.
An enhancement may be to allow the bot to check for any lures in its inventory (troy disk) and set a lure on specific fort (using GPS location) that it known to produce rare Pokemon.

Hanging around a lured fort is definitely very human-like behaviour, and likely to result in better captures. I support this concept.

+1, I think it's a very good idea !

+1

Working great for me. Thanks.

could our bot do FollowPath, but stays at fort with lure on?

Do we agree that is done ?

Yep, looks good


Add docs for mutation.

will finish review tonight, sorry for delay

@digitalbuddha Should this PR be closed?

Needs one more approver


Remove black Text-Background of titlebar-text?

Is there a way to get rid of the black Background of the titlebar text?

It's a bug in DWM. I'm not sure if I can do anything about it.

I'll just flag this as won't fix, but still keep this open for now.

Thanks a lot, maybe there will be a way to fix it somehow in the future.
I've been wondering, is it at least possible to change that background colour so I could match it to my background/mica-effect-colour on my local machine? Or is it determined by the OS and can't be changed?

is it determined by the OS and can't be changed?
Yes, it's that black background (that's white in light mode) is rendered by dwm for a bug in dwm itself.

February 16, 2022 - This is now fixed in the Windows 11 Insider Preview Build 22557 🎉😄

I think I will close this as it's basically resolved in 22557.


Custom property-panel does not work in 4.3 any more

Describe the Bug

Plugins, which add custom tabs or groups to the properties panel is no longer possible.
The getTabs method of plugins is no longer called in version 4.3.
I created an example repo for a plugin, the getTabs method of which is called in version 4.1.1, but not in 4.3.
I have not tested if it works in 4.2.
Steps to Reproduce

Get this example repo: https://github.com/hrzwkstim01/camunda-modeler-4.3-property-panel-test (extended from 'camunda-modeler-plugin-example')
Use generated plugin in modeler v4.1.1. There you can see a console.log
Use generated plugin in modeler v4.3. There you can not see a console.log

Expected Behavior

The console.log should also be visible in the latest version of the modeler.
Environment

OS: [Windows 10]
Camunda Modeler Version: [4.3]

Depends on https://github.com/camunda/camunda-modeler/issues/2133

We changed the interface of the CamundaPropertiesProvider, cf. https://github.com/bpmn-io/bpmn-js-properties-panel/blob/master/CHANGELOG.md#breaking-changes-1
Make sure you adjust it when you extend it: https://github.com/hrzwkstim01/camunda-modeler-4.3-property-panel-test/blob/main/client/bpmn-js-extension/ExampleExtensionService.js#L3
We did similar here in the Modeler itself: https://github.com/camunda/camunda-modeler/commit/538682ab07faa3d50d691b3dd74b64d973bae551

That should do the trick. Feel free to re-open if that's not the case.

@pinussilvestrus
Thanks for you answer.
I already recognized that the interface changed, so I used the same constructor which is used by the modeler.
Take a look at https://github.com/hrzwkstim01/camunda-modeler-4.3-property-panel-test/blob/main/client/bpmn-js-extension/ExampleExtensionService.js
Still it does not seem to work

Seems to be also an issue with other existing plugins, e.g. https://github.com/camunda/camunda-modeler-process-io-specification-plugin

Thanks for reporting anyway!

This seems to be a problem with multiple properties provider: https://github.com/camunda/camunda-modeler/blob/develop/client/src/plugins/element-templates-modal/modeler/index.js#L20
We will have a look.

@pinussilvestrus @nikku
Some updates on this topic?

We will restore the ability to customize properties panels in the future. We cannot give you a concrete estimate yet.
Could you elaborate how you use the extension? Do you experiment with the API? Do you have an extension deployed, i.e. in production right now?

Currently, we are developing a custom property panel to the tabs for our needs.
We plan to get productive this month and to extend more tabs/groups in future.
As this extension is not supported any more, we are currently working with version 4.1.1, which prevents us to stay up-to-date with you guys and getting required features, for instance auto complete for expressions.
Additionally, working with an old version of the modeler, will lead to an extensive effort of integration once this feature gets live again.

We faced the same issue, using v4.1.1 at the moment but it may reqire more work in future, is there a progress on the issue? Kind regards.

@iskn90 Could you elaborate on your setup and usage of the API, too? It helps us to better understand the impact of this issue for you.

Hi @hrzwkstim01,
we pushed a fix recently (https://github.com/camunda/camunda-modeler/pull/2145) to make it possible to create multiple properties providers. That should make all those plugins working again with the next nightly + release.
However, from now on we suggest using the new propertiesPanel.registerProvider API instead of simply overriding the propertiesProvider module. You can see this example for some guidance.
Feel free to reach-out if you have further questions 👍


Assert errors when opening robomaker logs

I'm using python 3.9.13. When I tried to open robomaker logs, I got the following errors:
Exception in Tkinter callback
Traceback (most recent call last):
File "C:\Python39\lib\tkinter_init_.py", line 1892, in call
return self.func(*args)
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\ui\dialog.py", line 96, in ok
self.apply()
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\ui\new_files_dialog.py", line 37, in apply
import_new_logs(self.new_log_files, self.please_wait, self.parent.get_log_directory())
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\log\log_utils.py", line 28, in import_new_logs
log.parse(f, please_wait, i / total_count * 100, (i + 1) / total_count * 100)
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\log\log.py", line 91, in parse
self._parse_episode_events(
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\log\log.py", line 208, in _parse_episode_events
parse.parse_intro_event(line_of_text, self._log_meta)
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\log\parse.py", line 81, in parse_intro_event
_parse_actions(line_of_text, log_meta, MISC_ACTION_SPACE_B)
File "C:\Projects\AWS\Deepracer\deepracer-log-guru\src\log\parse.py", line 301, in _parse_actions
assert a["index"] == index
AssertionError
I don't know if my logs are too big or not. They are around 5MB-8MB in size.

Issue was due to incorrect numbering of manually modified action space. Won't fix in Guru at this time unless it becomes a more common issue.


How to Pass Data from Panel to Grid

I have this input form with 4 fields....and the search button when clicked calls a function in the EndPoint which returns a List Response. My question is how do i get the List Response result set to display in the grid below?
See attached screenshots..
Panel

Grid

Marco Bisio

grid.view.setItems(list, true)


Add Dark Mode

Add dark mode and a toggle button, so users can use the page in day and night very conveniently.

I would like to work on it


requiredAsterisk, Shadow & Slideup

closes: #2084
converted SCSS files from these components to styled-components.

Ok @thesanjeevsharma you can check it out now. You have no idea how much i learned doing this task 😁


Bump iana-time-zone-haiku from 0.1.1 to 0.1.2

This PR bumps iana-time-zone-haiku from 0.1.1 to 0.1.2 which allows us to get rid of eight dependencies.

That cleans up Cargo.lock quite a bit. Nice!


Wrong minimum OS Version on binary target

Hello,
I can not upload my app to AppStore due invalid minimum OS Version in binary target. I tried change this value to 13.0 however it doesn't work. Could you please help check on this issue?
My project iOS target: 15.0

hi @tuannguyenanh177 I'm going to investigate and get back to you shortly

hi @tuannguyenanh177 Please try with v0.2.2 of the player

Good afternoon. I have the same situation as the previous comments. Is there a solution to this problem?

Good afternoon, @samuelOsborne . I have the same situation as the previous comments. Is there a solution to fix this problem?

@samuelOsborne Minimum OS version in project - 14.0

hi @PollyVern I think ive located the problem. Inside our plist files the min version is 13.0 but the binaries have it set to 17.0
Currently investigating why this is happening

hi @PollyVern thanks for your patience, atm the early minimum os version I can get to is 15.5 via our github ci/cd build pipeline
Im gonna to try and build the core player locally with lower ios sdks if I manage to get them out of xcode

@samuelOsborne Thank you so much for quickly trying to rectify the situation. Sure wish you could find a solution, because we won't be able to get the project version up to 15.5.
I look forward to any changes

hi @PollyVern @tuannguyenanh177. After updating our workflow, the lowest SDK version i've managed to use for iOS is 15.4, you can find the release here ➡ https://github.com/LottieFiles/dotlottie-ios/releases/tag/v0.4.1
I know you both wanted lower versions, but for the moment this is the lowest our github runners will allow without breaking :(

@samuelOsborne  Thank you for trying to solve the problem. On the current project, alas, I will just use the "Lottie" library

I'm having the same issue here. And my project's iOS minimum version is iOS 16.

I'm having the same issue. And my project's iOS minimum version is set to iOS 16.

hi @badepaz sorry about that, will continue looking in to it and let you know

hi @badepaz Please try out the latest release of dotlottie-ios for the fix!
cheers


[WFLY-18289] Correct GAV handling

Fix incorrect use of maven properties for GAVs
Consolidate on a single scheme for controlling testsuite feature pack GAVs Use the wildfly-standard-expansion-bom in testsuite/layers-expansion
https://issues.redhat.com/browse/WFLY-18289

@yersan Perhaps get rid of project.groupId? It is inherently ambiguous, and if it's gone but we see it re-added in code review we can require its replacement by the author.  If we allow it then reviewers have to analyze every new use for correctness.
Both project.groupId are heavily used, so in both cases a bulk change would be required. Of course, project.groupId is more heavily used, but sed or whatever would do the bulk change won't care.

Note that getting rid of ee.maven.groupId won't work downstream.

Thanks @bstansberry , as discussed, my comment requests more changes outside of the main scope of this PR and we do not want to delay it due to those comments, so this should be good.
Bootable JAR failure is unrelated. And cloud tests should not be affected either since this PR is not changing any GA. For upstream all ee.maven.groupId and full.maven.groupId and project.groupId are all the same.

Thanks @yersan. We should definitely continue thinking about your suggestion.

Why is project.groupId inherently ambiguous? By definition, it resolves to the groupId of the pom in which it is used.

Because this system of groupId expressions isn't intended for the intra-project dependency use case. It exists to facilitate forking the WildFly code base into two separate downstream projects that use different groupIds. So when you look at project.groupId in terms of how it will impact a WildFly build, it's unambiguous. But if you look at how it will impact a downstream build, it's "ambiguous".
Most of the changes in this PR are a forward port of things I needed to correct to get the EAP XP 5 branch to build.

Thanks @yersan


Find schema of the table and the column

Is there any way to use the iterative method to find the schema of the table and the column?
Because I want to use table schema and column schema as dynamic variables, what are the examples or methods?

Hi @pili2026
From Cassandra itself point of view, I don't know the way how to get such metadata by some query.
From CDRS end there is also no way to do that.


...would offer a task to minify #html code.

Max Klenk published this wish on stomt.

The HTML files which are wrapped in Javascript in the partials tasks are minified before they get merged. And now also the index.html and inlined css and js code is minified which may save another 20-60% of its file size.


Revert "Set up channel receivers early"

Reverts celsworth/lxp-bridge#145
Sorry @celsworth, I've just noticed a regression caused by this PR.
In src/lxp/inverter.rs, the flow is start { while connect() { sender() } }
Since we call sender in a loop, and since that's where the take is, any time the inverter reconnects, lxp-bridge dies with the error "should only be called once" :grimacing:
Best to revert the whole thing and maybe revisit once your integration test suite is in place :sweat_smile:
As it happens, I think I've got an approach to broadcasting the holding registers that doesn't need this PR anyway. I was working on that when I triggered this bug! Hopefully I'll have something to show tonight.

Oops :)
Yeah the integration suite is a bit dodgy at the moment, its a good start but its quite easy to make it hang through race conditions. Could do with setting it up to run in CI first off then I might take a look at improving it and adding more tests.


Preview image still only visible on /[lang] url

I noticed when posting a link to my friends to test the demo that the preview url is still only visible on the /[lang] url but looking at the app folder i could not see immediately why this was the case.
@vinayaksh42 any ideas? I know you helped in removing the /[lang] url on the homepage and hoped you might have some insight
nothing in /app/head.tsx mentions the /[lang] url

The logic for removing the /en ending was to simply stop the redirect that was occurring due to middleware.ts when a URL without a locale was requested. More info at https://github.com/saving-satoshi/saving-satoshi/pull/247/files#diff-3c67eb27b539c61276d7c7cbcdbe15d4b37a6cbf58bf8bc12c1c4d7619c96d1c
Not sure why this issue might be occurring as in the root folder of app we have the actual homepage (https://github.com/saving-satoshi/saving-satoshi/tree/master/app)

This preview image is still only available with /[lang] url. Ben/Kevin will investigate this further.


Associate .cson with CoffeeScript

Fixes #2568

Hi @Tyriar, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Looks like AppVeyor flaked

Thanks @Tyriar !


Fix: Illegal ICD10 Codes

Description
During my ICD10CM analysis, I found these.
Nico said:

These showed up. We need to fix them manually.
https://docs.google.com/spreadsheets/d/1KMTF7aUAeamVr_vZQSKxoJF28itRT4ZXUIiHcr8pFzk/edit

Related issues
#628

Concretely:
Go through all the codes in prefixOriginal:code column and figure out what on the https://www.icd10data.com/ site they were supposed to refer to. You can use search in protege to find any related Mondo terms.

@joeflack4 and @matentzn can you clarify what needs to be done? Should I fix these in Mondo?

Note these odd "+"s and "*"s come from ORDO.
https://www.ebi.ac.uk/ols/ontologies/ordo/terms?iri=http%3A%2F%2Fwww.orpha.net%2FORDO%2FOrphanet_100067
Clearly they should not be part of the actual ID itself and ORDO is using
some kind of ad-hoc expression language. I think it's worth (a small amount
of) investigating what they are trying to do and seeing if there is a way
to represent this another way.
On Tue, Feb 22, 2022 at 9:35 AM Nicole Vasilevsky @.***>
wrote:

This code does not exist in ICD10: E35.1*
It is not marked as MONDO:equivalentTo in Mondo and it comes from
Orphanet. Should we delete these in Mondo? I don't think it would be
appropriate to mark this MONDO:equivalentObsolete because it was never
equivalent in Mondo (although it is an equivalent mapping in Orphanet
https://www.ebi.ac.uk/ols/ontologies/ordo/terms?iri=http%3A%2F%2Fwww.orpha.net%2FORDO%2FOrphanet_100067
).
—
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/mondo/issues/4524#issuecomment-1048043969,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOKEEZ3SRWI3KWOWRFTU4PCMZANCNFSM5O7DEHXQ
.
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 are subscribed to this thread.Message
ID: @.***>

I think this is what needs to be done:
Given this example: MONDO:123 --> ICD10:E35.1*

Based on the bad code you try to figure out what the correct mapping is, e.g MONDO:123 --> ICD10:E35.1 or whatever code you think.
The correct code should be changed to ICD10CM:E35.1
The expression language pattern (where a correct code is postfixed by a symbol like *, + etc) one should be changed to ICD10EXP: for now, e.g MONDO:123 --> ICD10EXP:E35.1*, and no MONDO:equivalent*** should be on it (or if it has to, then "related"). This part is independent of the two above.

Does this make sense? I see this can be quite daunting, but I am happy to discuss tomorrow!

to do:

all fo the + and * should be changed to ICD10EXP, but I need to review these and make sure there is at least one correct code if possible.

Just curious, is ICD10EXP: a new prefix that should resolve to some URI base? Is it a problem if it doesn't?

No, we should filter these out before release.. We just don't want to loose the province atm!

These are removed by ../sparql/update/delete-axiom-annotations-by-prefix.ru
This ticket is dealt with by @nicolevasilevsky @sabrinatoro @joeflack4
good job all.


About Reddit pretraining | NameError: name 'graph' is not defined

Thanks for this great work!
I've just little observation, while trying to run GPT-GNN using Reddit.
https://github.com/acbull/GPT-GNN/blob/8ac50bf0720e5260b175f55e338c09e3a3adf729/example_reddit/pretrain_reddit.py#L103
should all graph re-named  to graph_reddit ?

Same question here. I think it will fix the bug. @acbull  could you plz fix it?

Thanks for this great work! I've just little observation, while trying to run GPT-GNN using Reddit.
https://github.com/acbull/GPT-GNN/blob/8ac50bf0720e5260b175f55e338c09e3a3adf729/example_reddit/pretrain_reddit.py#L103
should all graph re-named to graph_reddit ?


Remove guard

Removes guard as the configuration is outdated and I'm certain nobody
uses it.

:+1:


Project > Field Budget > Preview not supported file preview screen is shown While the user deleting the new version of the file on the "universal template" and deleted file name is displayed

Roles: All
Describe the bug
Project > Field Budget > Preview not supported file preview screen is shown While the user deleting the new version of the file on the universal template  and deleted file name is displayed
Steps to Reproduce

Login as a Project Manager
Create a new Project and go to the project details page
Click on the Budget Details button
Click on the Add Universal Template button and upload any file.
Click on the kebab menu and add a new version of the file
Delete the new version of the file and refresh the page
Click on the universal template file

Expected Result
Previewing is not supported for this file type message should be displayed and deleted file name should not be displayed on the preview screen
Actual Result
Preview not supported file preview screen is shown While the user deleting the new version of the file on the universal template  and deleted file name is displayed
See video -
https://user-images.githubusercontent.com/5212585/118441612-0d41c400-b707-11eb-9f16-5a8f067a3dd6.mp4
FYI: @ParkeBrown @michaelmarshall
cord-field# 1d6e8100

Reproduced successfully. Project Manager is able to successfully upload files as universal templates. The preview option is not available and the message is shown. After deleting file and refreshing page, the deleted file name is displayed on preview screen.