Doesn't Work in 2023

This app didn't work for me in 2023. Why?
The app only shows the logo of "Poprism Web Browser" and later Roku OS says that the app isn't available anymore.

The app has been taken down for unknown reasons. Sadly, I don't know how to compile Roku apps.

The app has been taken down for unknown reasons. Sadly, I don't know how to compile Roku apps.

It's as easy as zipping the files and putting it into the dev mode app installer.

The app has been taken down for unknown reasons. Sadly, I don't know how to compile Roku apps.

It's as easy as zipping the files and putting it into the dev mode app installer.

Oh, really? That's cool!

Yeah, uh, ProSureString, you're wrong.

I just installed it that way and it just shows the splash screen


Missing attributes to lids and windows

Describe the issue
Following the fix related to https://github.com/bimmerconnected/bimmer_connected/issues/298, I can now get data, however I have lost a lot of details.
I used to have details of each window and door in the attributes of binary_sensor.220d_lids and binary_sensor.220d_windows.
These have now disappeared.
Expected behavior
detailed lids and window attributes to be present with their statuses
Which Home Assistant version are you using?
core-2021.8.5
What was the last working version of Home Assistant Core?
core-2021.7
What is your region?
Rest of world
ConnectedDrive website

[X] I can still successfully login to the BMW ConnectedDrive website and the car status is available there.
[X] I have ConnectedDrive enabled for my vehicle.

Number of cars

[ ] I have 2 or more cars linked to the ConnectedDrive account.
[ ] I have a Mini vehicle linked to my account.

Output of bimmer_connected fingerprint
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

Will have a look at this.
I see it for my car as well.
Also cbs, check control messages and the lock state are missing the attributes other than car and vin.

I have a test instance of HA version 2021.8.3 with BMW as a custom integration (with the latest bimmerconnected library) which still has all the attributes. So seems something has changed in HA 2021.8.4 or 2021.8.5.

I have found the issue. It's caused by the PR mentioned above. Will make a HA PR with a fix the coming days.

PR is merged in HA and on the list of the 2021.8.7 milestone -> https://github.com/home-assistant/core/milestone/427?closed=1.

I can confirm this is resolved indeed. Thanks for the quick fix, as always 👍


[v2] Router with Async ajax call why it is not working?

I am using v.2 Links does not work when using router async function
< a href="/page-content/">go</ a>
in the script, it seems that nothing inside the async function is executed... not even the alert...
any solution or what i am doing wrong? if I use url below path without the async function then the link working again... but with the function the click stop working... :(
routes: [
{
path: '/page-content/',
async: function (resolve, reject) {
alert('');
app.request({ ...
  });

}
}

solved!        page should have always   < div class="view view-main view-init" data-url="/" > and links works


update to 0.12 breaks the time picker

Describe the bug
After an update from 0.11.6 the component time picker is broken, the error is:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'mask')
    at Proxy.maskInput (eval at d.el (alpine.js:144), <anonymous>:22:30)
    at Proxy.onInput (eval at d.el (alpine.js:144), <anonymous>:92:27)
    at eval (eval at d.el (alpine.js:174), <anonymous>:3:21)
    at d.el (alpine.js:174)
    at d (alpine.js:131)
    at alpine.js:151
    at be.evaluateCommandExpression (alpine.js:1760)
    at z (alpine.js:933)
    at HTMLInputElement.l (alpine.js:909)
    at s (alpine.js:106)

Tested with alpine 2 and 3

Why do you not use the latest version?
https://github.com/PH7-Jack/wireui/releases/tag/v0.14.1

i've the same issue with 0.14.1, i narrow down till 0.12 to find what was the breaking change.
Christophe

Can you run php artisan optimize:clear? Compile the assets again and force refresh the browser
You must to use apinejs v3.

OK problem fixed with compilation, force the assets,...


zed c3 support

adding basic syntax highlighting support for zed

Closing due to incomplete state

Will reopen when plugin is further along


Switched to using differences in deviances to compare models

To deal with issue #38 I've attempted to change to using deviances for out-of-sample fits rather than RMSE in the zooplankton example.  I'm still a bit uncertain if I'm using the right form of deviance to compare model fits though. Simon talks about both scaled and unscaled deviances in the book; I've focused on unscaled deviance, but is that appropriate here? @dill,  I think we need your input on this. I'm getting a bit out of my depth on the statistical theory of glms.

It seems like from Wood (2017) that the scaling is only really used for getting to the Chi-sq test statistic, so I think we are fine to not scale.
Looks to be from the out-of-sample deviance that the difference between models 4 and 5 (which I guess are renamed now) are marginal in most cases, and one the "intercept" model does better (what is happening with K. cochlearis??), but I guess our point is that in the cases where it does matter we have that extra flexibility.

I also went through the code that generates this and it looks good to me, btw.


Change number of genes for filter_genes as a pipeline input parameter.

https://github.com/break-through-cancer/btc-spatial-pipelines/blob/0f39feb1656e9f94545a2ff6ffb60deae414581e/workflows/spatial.nf#L107

This will need some refactoring of the pipeline:

[ ] create "filter genes" parameter in the "deconvolution settings" , when empty do not filter any genes
[ ] move "bleeding correction" boolean to the "deconvolution settings"
[ ] convert from h5ad and plug BAYESTME_BLEEDING_CORRECTION into CoGAPS
[ ] in addition, fix #43

*setting "filter genes" to some very large number such as 99999 should work too, as the number of genes to keep is determined as min(requested genes to keep, number of genes in the dataset), with the only moderate disadvantage that standard deviations will need to be computed. @jeffquinn-msk OK with that?


Add support for overriding default folder location of CreateDatabase

Add support for overriding default folder location of CreateDatabase script group. This is regarding issue #464.

Simple and easy, thanks a lot! This is the way to do it. Find an issue/error, then send a PR where you fix it :)


Adds command pa app owner set, Closes #4646

Closes #4646

Thank you, I'll review it ASAP!

Merged manually. Thank you for this super useful command!👏


Remove and ignore words.go from git

I understand the idea of not checking in generated files, but this change will break anyone using golang and the documented install  process.

In that case, I suggest updating the words.go copy in the repository. It contains a bunch of words that should no longer be there (upto etc).

yes that will happen...


Implemented fol_fc_ask()

It is the inefficient implementation so I have commented out the test cases which takes 1 minute to run.
Also added constant_symbols() and its test.

This looks good.
Can we have a simpler test that runs faster?
Also, I note that we define knowledge bases with
map(expr, ['A', 'B', 'C', ...])
could we just do
expr('A, B, C, ...')
and since expr calls eval, wouldn't this just return a tuple of sub-exprs?

I was unable to get the second format to work in multiple lines. eval throws SyntaxError due to the new line characters. I tried to use ''' inside """ but that didn't work either. I think it is better to leave it as it is. Using techniques to ignore the newline character would only make it harder to read.


do not apply root transforms on linked modules

resolver now accepts a 4th argument which should be the original
(non-real) file path.
Required for fixing https://github.com/substack/node-browserify/issues/1386 / https://github.com/substack/node-browserify/pull/1365
Definitely could use a better variable name, so this is open for suggestion and comments.
This change is missing tests right now. I'll add them if I get some feedback that we might want to merge this.

Thanks! I've published this as 4.0.0 to be extra cautious since in previous releases symlink issues have been very sensitive. I think we can put this into the browserify v12 release.

Sounds good to me. I realized I didn't add tests, but I can look into adding them later. Wasn't sure if this solution was of interest.


add --verbose flag to helm test

When set to true, this flag will stream the test pod logs in the output
cc/ As per our discussion @foxish @erictune @vdice

Would this be different in kind to supporting the already global --debug flag?

@michelleN if this should go in 2.3.0, feel free to add it. For now, I'll drop it into triage.

This would be a nice addition.  Currently if you run helm test --cleanup and the job fails it will output.  FAILED: test, run `kubectl logs test --namespace test` for more info
Which is not that useful as helm has already deleted the pod :)

What is the status on this item?

+1

Is this being worked on? I'm working on ci/cd scripts using helm, and I'm wondering if I should wait for this to be finished or try to parse helm test outputs and manually attach to the running tests. I would write the PR myself, but I'm not super comfortable with go and don't have time to pick it up right now.

Nobody's currently working on this feature AFAIK. Sorry!

Here's my Bash workaround in the absence of this feature:
#!/bin/bash

helm_release=$1

test_pods=$(helm status $helm_release -o json | jq -r .info.status.last_test_suite_run.results[].name)
namespace=$(helm status $helm_release -o json | jq -r .namespace)

for test_pod in $test_pods; do
  echo "Test Pod: $test_pod"
  echo "============"
  echo ""
  kubectl -n $namespace logs $test_pod
  kubectl -n $namespace delete pod $test_pod
  echo ""
  echo "============"
done

/remove-lifecycle rotten

I've used @tomstockton to write a bash file that will follow the logs as it's testing:
test.sh
# Define the Namespace
NAMESPACE=mynamespace

HELM_RELEASE=$NAMESPACE-123
POD_NAME=$HELM_RELEASE-test

echo "=====================
echo "Testing $HELM_RELEASE"
echo "=====================

# Delete previous test pod if any
kubectl delete pod $POD_NAME --ignore-not-found -n $NAMESPACE && sleep 5

# Keep checking the pod status every 5 seconds
# Stops when its phase is "Running"
# This allows us to start following logs only when "Running"
# "Unknown" happens if pod is not found
function is_pod_running() {
    UNKNOWN_COUNT=0
    while [[ ! $POD_STATE = "Running" ]]
    do
        sleep 5
        POD_STATE=$(kubectl get pod $POD_NAME --ignore-not-found -n $NAMESPACE -o=jsonpath='{.status.phase}')
        POD_STATE=${POD_STATE:-"Unknown"}

        if [[ $POD_STATE = "Unknown" ]]; then
            UNKNOWN_COUNT=$((UNKNOWN_COUNT + 1))
            if [[ $UNKNOWN_COUNT = 5 ]]; then
                echo "Pod in Unknown state for more than $UNKNOWN_COUNT times, cancelling"
                exit 1
            fi
        fi

        echo "$POD_NAME is $POD_STATE"
    done
}

# Follow logs
# Automatically stops once pod finishes executing (success or failure)
function follow_logs() {
    echo "Logs for $POD_NAME"
    echo "===================================="
    kubectl -n $NAMESPACE logs $POD_NAME --follow
}

# Run the tests
helm test $HELM_RELEASE & (is_pod_running && follow_logs)

I really like how the verbose switch works in kubectl.  It probably makes development on kubernetes itself go a little bit faster because it's easier to see what's going on by adding -v9 and be able to view all the REST requests being made against the cluster.
Does anyone know off-hand what REST calls are made for helm version?  I'd like to be able to detect if tiller is installed in a namespace or not, and am having trouble sorting that out.

Helm and Tiller communicate via gRPC, so it's not an HTTP request being made to Tiller, but the RPC call is listed here.

implemented in #6612


Add Sdotbelow, dotbelowcomb to PriAfrican glyph set, update data.json mapping for PriAfrican glyph set

Fixes #141

Thank you very much for these changes Denis!


Alluxio Embedded HA can't work when two follower crash

Alluxio Version:
2.6.1
Describe the bug
A clear and concise description of what the bug is.
Our cluster has three master nodes, namely master-0, master-1, and master-2, of which master-2 is the leader. Master-0 and master-1 went down at the same time. After the two nodes restarted, master-1 became the new leader. At this time, we found that no new raft logs were generated in master-2. After we killed master-2 and restarted master-2, we found that the raft log still could not be generated.
To Reproduce

Kill 2 followers at the same time in a 3-node cluster
After the cluster restarts and the new leader is selected, kill the original leader
Observe the changes in the raft log

Expected behavior
When the two nodes are down and restarted normally, the cluster can still return to normal working status
Urgency
Normal

Since this is not supported currently by Ratis, I will close this as a bug
@maobaolong do you have further input? Feel free to re-open it if you have further update.


Fixed trix removal of underline style

Changed the trix-editor underline parser to allow underline strings in input

Thanks!


Implementation For InitialOnly feature based on One-Shot Query

Description
Related to DISCO-368
It's an initial version of implementing InitialOnly feature based on the one-shot query
Primary reviewers
@m-samiec

This looks like a good start! Nice work.
We need to rework a few factors, main one being moving using the actor completeness filter along with the initial only data. Adding initial only tag component also to indicate presence so we don't need to do it unnecessarilly.
I also don't see any changes to the replicator to ensure that initial_only values are always replicated to the runtime, and don't use the standard unreal replication rules where they're only replicated initially.

I've continued work on this feature here - https://github.com/spatialos/UnrealGDK/tree/feature/initial-only-support

https://github.com/spatialos/UnrealGDK/pull/2926


promql: handle NaN in changes() correctly

Fixes #2042
@brian-brazil

:+1:
Can you add a test for 0 NaN 0 returning 2?

Added

LGTM


Added John Anderson (sontek) to contributors

I'll push this up to pypi after we've added the hashing client and the testing changes.


[solver/ddp] if gaps are zero, solution is feasible

This comes from a problem that is documented here: https://gitlab.laas.fr/aparag/warmStart/-/blob/master/unicycle/Feasible warmstart.ipynb
If the solver is being started with isFeasible=False. This boolean is only updated to true when you make a full step. And if for some reason, this doesn't happen (which normally should not occur), this boolean remains False. We don't set this boolean on the basis of the gaps. we set it on the basis of the user input.

actually I agree. If we are setting it from the gaps, we don't need isFeasible anymore.

actually I agree. If we are setting it from the gaps, we don't need isFeasible anymore.

Then, it could be good to handle it in this PR. Do not forget to deprecate the current signature

This would require changes in all solvers. I'll keep this patch as self-contained, and handle it in a different pr

This would require changes in all solvers. I'll keep this patch as self-contained, and handle it in a different pr

Ok, it sounds good as well.

I'll merge this since Travis is passing, and gitlab-ci is either being allowed to fail, or failing because of time-out.


AYS Service for installing a new image

Currently admin/root access is required to ovc_master and at least to one storage node in order to add an OS image, as documented here: https://gig.gitbooks.io/ovcdoc_public/content/Sysadmin/Images/deploy_new_image.html
We should create a Actor template for this so that adding an OS image can be automated through a Cockpit

I'm not sure to agree on this.
The G8 operator and the cockpit pilote are two different person. The cockpit pilote don't have have right and access to G8 infrastructure and I don't think we should allow that.

The Cockpit can be used for many use cases:

we use the Cockpit to automate parts of our development processes
the Cockpit is used for bridging resellers to operators
operators can use a Cockpit to automate administrative tasks

Today we have really to many admin tasks which are rather simple, but still require admin access to the controllers and compute/storage nodes, this is asking for problems
I'm wondering how else we plan to minimise admin access, preventing human errors, ...

Okay, but not for 8.1.0


partial support for fw 1.5.4_0052

on fw 1.5.4_0084, model zndmwg02lm  with this patch  bluetooth sensors works too

I confirm that my Flower Care (ble HHCCJCY01), HT (LYWSDCGQ/01ZM), HT (LYWSD03MMC) work with this codes. Thanks.

I can confirm ble HHCCJCY01, ble XMWSDJ04MMC and mesh WX10ZM working with the PR from @XTR1984 and firmware 1.5.4_0090

Can confirm it works for BLE RTCGQ02LM / BLE LYWSD02MMC / ble (735) / mesh (4896) with gateway 1.5.4_0090. Thanks for the great work.

HT LYWSD03MMC work with this codes. Thanks.


Counting valleys on hackerrank

Problem Link
https://www.hackerrank.com/challenges/counting-valleys/problem
Coding platform
Hackerrank
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

I will provide solution in C++

I would like to solve this issue in python

Hi @Nivedita967
I would like to solve it in Java. Please assign it to me.

I would like to do this in C.

@Nivedita967 Please check my pull request


Update Buildable instances for BlockHeader and Hash

Issue Number
#711
Overview

[x] I added an idea for new BlockHeader buildable instance where the prevBlockHash comes first, and the blockHeader points towards it.
[x] I made Hash tag build to 424c4f43 instead of 424c4f43...c0dd1877.
[x] I implemented To/FromText and Buildable instances on Hash tag in general, instead of having one instance per tag.

Comments

fmtLn $ build h
-- Old: Block (5.36#1036) -> 424c4f43...434b3033
-- New: 424c4f43 ⬸ [5.36#1036]

fmtLn $ build (prevBlockHash h)
-- Old: 424c4f43...434b3033
-- New: 424c4f43

For the Block buildable instance having the prevBlockHash last might make sense though 🤔
            "Block (14.19#42) -> dffc3506...6969a73b\n\
            \    - ~> 1st c29d3ea0...13862214\n\
            \      <~<PHONE_NUMBER>610 @ 82d81858...aebb3709\n\
            \      <~<PHONE_NUMBER>0 @ 82d81858...37ce9c60\n"

Also, the unicode arrow isn't good when printed in error messages in its escaped form.

bors r+

bors r+

🤔
Failures:

  test/integration/Test/Integration/Jormungandr/Scenario/CLI/Launcher.hs:155:13:
  1) No backend required, Launcher CLI tests, LAUNCH - cardano-wallet launch [SERIAL], LAUNCH - Invalid block0 file (not a serialized block)
       "\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Using state directory: /var/lib/buildkite-agent/.local/share/cardano-wallet/jormungandr/testnet\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Running as v2019.9.13\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Wallet backend server starting...\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Node is J\246rmungandr on testnet\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Database layer started.\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 08:39:34.79 UTC] Generated J\246rmungandr's configuration to: /var/lib/buildkite-agent/.local/share/cardano-wallet/jormungandr/testnet/jormungandr-config.yaml\n" does not contain "As far as I can tell, this isn't a valid block file: test/data/jormungandr/secret.yaml"

  To rerun use: --match "/No backend required/Launcher CLI tests/LAUNCH - cardano-wallet launch [SERIAL]/LAUNCH - Invalid block0 file (not a serialized block)/"

Failures:

  src/Test/Integration/Scenario/CLI/Mnemonics.hs:30:5:
  1) Mnemonics CLI tests CLI_MNEMONICS_01 - Can generate mnemonics with default size
       uncaught exception: IOException of type InvalidArgument
       fd:18: hGetContents: invalid argument (invalid byte sequence)

  To rerun use: --match "/Mnemonics CLI tests/CLI_MNEMONICS_01 - Can generate mnemonics with default size/"

  src/Test/Integration/Framework/DSL.hs:1286:22:
  2) Server CLI tests, LOGGING - cardano-wallet serve logging, LOGGING - Launch can log --verbose
       "" does not contain "Running as v2019.9.13"

  To rerun use: --match "/Server CLI tests/LOGGING - cardano-wallet serve logging/LOGGING - Launch can log --verbose/"

Randomized with seed 475995922

stack test cardano-wallet-jormungandr:integration --ta '--match "/No backend required/Launcher CLI tests/LAUNCH - cardano-wallet launch [SERIAL]/LAUNCH - Invalid block0 file (not a serialized block)/"'
fails with same error message on master, for me locally.

Runs fine for me. I am on jormungandr 0.5.0 at the moment. Which one are you?

jormungandr 0.5.0 too

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

Back to the flaky jormungandr-tests… We had the same failure in #771, so this PR shouldn't be the problem… trying again
bors r+

bors r+


proxy fails to take into account DOCKER_BRIDGE

Reported by a user:

I used strace on 'weave launch-proxy --with-dns' and found this
execve("./weave", ["./weave", "--local", "docker-bridge-ip"], ["PROCFS=/hostproc", "PATH=/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"]) = 0 <0.000217>
..
..
execve("/sbin/ip", ["ip", "-4", "addr", "show", "dev", "docker0"], ["SHLVL=1", "PATH=/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PROCFS=/hostproc", "PWD=/home/weave"]) =
The environment calling the weave script does not have DOCKER_BRIDGE set so the weave script defaults it to docker0.

I reckon the proxy should be told about DOCKER_BRIDGE when it is launched.


[BUG]: Grafana not open web interface

What happened?
I start Grafana. Grafana started. But not open web interface. Answer from ngix - 502 Bad Gateway.
Version 3.2.2 RC11.
Also I have Wireless card mtk7925:
[   12.774532] mt7925e 0000:01:00.0: HW/SW Version...
Relevant log output
I don't know what logs you need to attach here.

How often does this bug happen?
Every time
What version are you using?
3.2.2 RC11.
Self Service

[ ] I would be willing to fix this bug myself.

Guidelines and Policies

[X] I have read the contributing guidelines and agree to follow the code of conduct and contribution policies.

Hi @gcastle2007, did you wait a few moments after starting grafana before trying to access? When the grafana service starts, its web server is not up right away. I just loaded the latest release on a WLAN Pi, and it is working as expected.
This is the error you will get when the grafana UI is not ready after starting:

Otherwise, check output of systemctl status grafana-server for any errors.

You are right, the memory card is very slow. That's why it took a very long time to start, more than 1 minute.
With the EMMC memory, everything starts up pretty quickly.

Just curious, what class SD card are you using?

oldest... ;) I bought new card Kingston Canvas Go! Plus 64Gb. It is better. I will set this card tomorrow. I use these card on 4 my 3d printers with raspberry and orange PI.
I start "Scan for Wi-Fi networks", but wait 10 minuts in this "status":

yes... it is sd card problem... :)

yes... it is sd card problem... :)


sales-and-support/pricing-discounts.md

pricing-discounts.md
@jacobsmith928 please complete this document as mentioned in the Products Outline doc earlier.

done.

neat! maybe put an email at the end where we say "Please contact us to schedule a conversation."?

fixed.


Add no-wait and force-kill-waittime options to Delayed::Comand

I've added support to these options that are used for Daemons gems.
In our case we have some long running jobs that we don't want to be locked when the process is killed on a new deployment, with these we avoid that problem and  the process is going to still running after the current job is completed. Later our monitor system will start a new process.
What do you think? is this too specific to the daemons gem? I don't find another way to pass options to the daemons gem

Will you accept this pull request if I rewrite it to work with current master? I think that it's really useful especially when you suffer from "process with pid X won't stop, we forcefully kill it" as described in #593 /cc @albus522

Is it possible to resolve conflicts in this I think that this feature should be integrated please.

Does this require a specific min version of the daemons gem?

👍

have a more flexible solution that works with any version of the daemons gem here https://github.com/collectiveidea/delayed_job/pull/916

Any plans to update this PR now that #916 was merged? It looks like we would still need the force_kill_waittime option in Delayed::Comand, since it is not an accepted command line option in the daemons gem, so couldn't be passed through daemon-options.

After some research in one of my projects, I agree with @mike-stewart : #916 doesn't solve the problem of passing the force_kill_waittime option, we need another change to support this.

The new --force_kill_waittime switch for Daemons is included in the recent 1.3 release.

Can this Issue be closed since --force_kill_waittime switch has been added to the Daemons gem and no longer needs to be explicitly supported internally in delayed_job?

Can this Issue be closed since --force_kill_waittime switch has been added to the Daemons gem and no longer needs to be explicitly supported internally in delayed_job?


Missing typescript definitions the findByIds query building method.

Typescript definition for findByIds seem to be missing.

Thanks, I'll add that ASAP.

Thank you for the fast resolution! Happy holidays :)


Docker Error KeyError

I have run docker for first time and I get keyerror, it seems code is trying to get postgress user and database, So is it needed to be created on base system ?
There were no instructions to setup DB on https://github.com/isaacmg/fb_scraper/wiki/Docker-Image
variables.list:
FB_ID=myappid
FB_KEY=mysecreate
IDS=cnn,paddlesoft,msnbc
# Include only if you want to scrape comments
COMMENTS=1
# Include below ONLY if you want to use Kafka.
USE_KAFKA=1
KAFKA_PORT=localhost:9092

Error:
docker run --env-file variables.list paddlesoft/fb_scraper Traceback (most recent call last):   File "threaded_proc.py", line 6, in <module>     from fb_scrapper import scrape_groups_pages   File "/fb_scraper/fb_scrapper.py", line 2, in <module>     from fb_posts import FB_SCRAPE   File "/fb_scraper/fb_posts.py", line 11, in <module>     from save_pg import save_post_pg   File "/fb_scraper/save_pg.py", line 3, in <module>     db = Database(os.environ['db'], user=os.environ['pg_user'], password=os.environ['pg_password'], host=os.environ['pg_host'], database=os.environ['pg_db'])   File "/opt/conda/lib/python3.6/os.py", line 669, in __getitem__     raise KeyError(key) from None KeyError: 'db'

Yeah I think the newer version by default uses PostgreSQL to save scrapping times as shelving is unstable.  So I think you need to set the following
db = Database(os.environ['db'], user=os.environ['pg_user'], password=os.environ['pg_password'], host=os.environ['pg_host'], database=os.environ['pg_db'])
I might create a parameter in the future where you can choose whether to use PostgreSQL too.

But is there already a postgress added in to the Docker or we need to setup that database on the host ?

At the moment Postgres is not part of the Dockerfile as it would take up too much memory. The way I was using is as part of a docker-compose with a separate container for PostgreSQL and another for FB scraper. Another easy option is to just set up a Heroku app as those come with a free PostgreSQL database.

I will add more documentation and  a branch that doesn't require PostgreSQL over the next couple weeks.


Add multiple send topics with &&

Added, sending multiple topics with && relation
$message->addRecipient(new Topic(['your-topic1', 'your-topic2']));

Coverage increased (+0.1%) to 97.163% when pulling 8df6cab832c4c716ce8beafde055690bbbd0cb93 on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 8df6cab832c4c716ce8beafde055690bbbd0cb93 on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 8df6cab832c4c716ce8beafde055690bbbd0cb93 on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 76e9dd812a5ab09fbc2e1f72def2e33983af4aab on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 76e9dd812a5ab09fbc2e1f72def2e33983af4aab on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 3c41f8048fa48c6e62d6ff790abbc902a761e09a on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 3c41f8048fa48c6e62d6ff790abbc902a761e09a on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.

Coverage increased (+0.1%) to 97.163% when pulling 3c41f8048fa48c6e62d6ff790abbc902a761e09a on IIISpikerIII:master into 897979470a596a30ce6782ee229db53f673e54b6 on Paragraph1:master.


Camera settings are not saved!

Hello, when I edit some settings at the camera_settings page in the web interface, the changes are not applied after saving. Reloading the page shows the old settings.
I tried turning off the status and IR LEDs, but no success.
Model y21ga, Firmware 0.3.3
I don't use the app or the cloud

Update:
The only way for me to change the settings is to export the config file, change it and import it again. Then the settings are displayed correctly in the web interface.

Try to clean the cache of your browser.


Notification not processed, Column original_ngsi_entity unknown

In our QL logs there is often the following entry:
2020-10-16 03:27:40.405 ERROR:reporter.reporter:Notification not processed or not updated for payload: [{'id': 'urn:ngsi-ld:Device:odp-user-data-watt:d280aa74-611c-4c10-a1d2-a0f0030b6353:watt', 'type': 'Device', 'category': {'type': 'Text', 'value': 'actuator', 'metadata': {}}, 'controlledProperty': {'type': 'Array', 'value': ['power', 'energy'], 'metadata': {}}, 'location': {'type': 'geo:json', 'value': {'coordinates': [[[15.708413583, 47.10982405], [15.708098437, 47.109178286], [15.708792658, 47.108699439], [15.709802027, 47.108866351], [15.710117187, 47.109512114], [15.709422964, 47.109990965], [15.708413583, 47.10982405]]], 'type': 'Polygon'}}, 'location_index': {'type': 'Text', 'value': '8a1e10a552d7fff', 'metadata': {'level': {'type': 'String', 'value': '10'}}}, 'refDeviceModel': {'type': 'Text', 'value': 'urn:ngsi-ld:DeviceModel:odp-user-data-watt:d280aa74-611c-4c10-a1d2-a0f0030b6353', 'metadata': {}}, 'source': {'type': 'Text', 'value': 'odp/user-data-watt', 'metadata': {}}, 'value': {'type': 'Number', 'value': '0.0', 'metadata': {'timestamp': {'type': 'DateTime', 'value': '2020-07-29T15:40:00.000Z'}}}, 'time_index': '2020-07-29T15:40:00+00:00', 'location_centroid': {'type': 'geo:point', 'value': '47.10941360785714, 15.709008634142856'}}]. SQLActionException[ColumnUnknownException: Column __original_ngsi_entity__ unknown] Thread ID: [140427210357536]  Process ID: [15]
2020-10-16 03:27:40.911 INFO:reporter.reporter:Env variable LOGLEVEL not set, using default value of: INFO Thread ID: [140427210357536]  Process ID: [7]
2020-10-16 03:27:40.913 INFO:reporter.reporter:Env variable LOGLEVEL not set, using default value of: INFO Thread ID: [140427210357536]  Process ID: [8]
2020-10-16 03:27:40.918 ERROR:translators.crate:Failed to insert entities because of below error; translator will still try saving original JSON in "etdevice".__original_ngsi_entity__ Thread ID: [140427210357536]  Process ID: [12]
Traceback (most recent call last):
  File "/src/ngsi-timeseries-api/src/translators/sql_translator.py", line 331, in _insert_entity_rows
    self.cursor.executemany(stmt, rows)
  File "/usr/local/lib/python3.8/site-packages/crate/client/cursor.py", line 67, in executemany
    self.execute(sql, bulk_parameters=seq_of_parameters)
  File "/usr/local/lib/python3.8/site-packages/crate/client/cursor.py", line 53, in execute
    self._result = self.connection.client.sql(sql, parameters,
  File "/usr/local/lib/python3.8/site-packages/crate/client/http.py", line 331, in sql
    content = self._json_request('POST', self.path, data=data)
  File "/usr/local/lib/python3.8/site-packages/crate/client/http.py", line 458, in _json_request
    _raise_for_status(response)
  File "/usr/local/lib/python3.8/site-packages/crate/client/http.py", line 187, in _raise_for_status
    raise ProgrammingError(error.get('message', ''),
crate.client.exceptions.ProgrammingError: SQLActionException[ColumnUnknownException: Column __original_ngsi_entity__ unknown]

Neither do we send any attribute called __original_ngsi_entity__ in our payload nor did we define the etdevice table in crate ourselves. Mostly did I trust that QL will create a working schema on its own. We just defined primary keys afterwards to prohibit duplicates. The name of the missing column indicates that the sql translator tries to persist an private python attribute, but thats just my uneducated guess.
I added __original_ngsi_entity__ as a text column to our crate table, but since then I wasn't able to reproduce the error. Nevertheless its just a matter of time until we will get those Errors again.

@pinkerltm
it seems you are using latest which is not the stable release (which is still 0.7.6), anyhow ql should automatically add columns to crate (at least this is test up to crate 4.1.8) leveraging the column policy 'dynamic'.
by chance did you create/edit manually your table?
can you do "SHOW CREATE TABLE" on the related table?

@pinkerltm any feedback?

@pinkerltm thanks for reporting this :-)

Neither do we send any attribute called original_ngsi_entity in our payload...

QL adds that automatically since #335---have a look at that PR for details of what that column is and what is for.

The name of the missing column indicates that the sql translator tries to persist an private python attribute, but thats just my uneducated guess.

...and you guessed it right, Sir :-)

We just defined primary keys afterwards to prohibit duplicates.
...
I added original_ngsi_entity as a text column to our crate table

In general, I'd advise you against changing QL generated tables in any way since it could result in all sorts of wonderful and mysterious errors if e.g. the table definition gets out of sync w/r/t entity metadata stored in the metadata table :-)
Surely QL's one-size-fits-all approach to storing data isn't a good match for every data processing scenario, but that's what we've got...
Now the above two changes combined have the side-effect that every time an entity with a duplicate key is notified, the insert will fail and QL will try saving the entity data as is in  __original_ngsi_entity__, but this will fail too since the expected column type is object not text---well, at least this is what I think it should happen, but the driver or Crate might convert the in-memory Python dict representing the JSON payload into a string if it notices the column type is text, I haven't tested that scenario, so don't take my word for it :-)

Nevertheless its just a matter of time until we will get those Errors again.

Yes, I'd say that may well be the case. The one thing I still don't understand is why this exception got raised:

crate.client.exceptions.ProgrammingError: SQLActionException[ColumnUnknownException: Column original_ngsi_entity unknown]

The one reason could be the table's column policy isn't set to dynamic. Like @chicco785 said, if you could please post here the output of
SHOW CREATE TABLE mt<your tenant>.etdevice

@chicco785 it looks like another issue @pinkerltm is going to have (sorry @pinkerltm!) is that the JSON payload contains nested arrays:
{
  'id': 'urn:ngsi-ld:Device:odp-user-data-watt:d280aa74-611c-4c10-a1d2-a0f0030b6353:watt',
  ...
  'location': {
    'type': 'geo:json',
    'value': {'coordinates': [[[15.708413583, 47.10982405], [15.708098437, 47.109178286], ...

so even if he had never manually modified the table, every time an insert had failed (for whichever reason), QL would have crashed on trying to save the original data anyway, see #344 about it.

@chicco785 @c0c0n3 my apologies for the long delay ...had another project which claimed all my attention recently, I guess you are aware of such situations.
As stated above, we rely on QL to create the table, and I just altered it to have a primary key to keep it clean of duplicates. We are really struggling to not lose any measurements/state changes, therefore we collect them in Kafka (as an queue) before handing them over to Orion-QL-Crate... and as we also want to prevent postprocessing of the QL generated table (i.e. after several kafka-consumer-replays) we need to prohibit the creation of duplicates.
Anyway, heres the output of SHOW CREATE TABLE ...
CREATE TABLE IF NOT EXISTS "doc"."etdevice" (    "entity_id" TEXT,    "entity_type" TEXT,    "time_index" TIMESTAMP WITH TIME ZONE,    "category" TEXT,    "controlledproperty" ARRAY(TEXT),    "location" GEO_SHAPE INDEX USING GEOHASH,    "location_index" TEXT,    "refdevicemodel" TEXT,    "source" TEXT,    "value" TEXT,    "location_centroid" GEO_POINT,    "fiware_servicepath" TEXT,    "__original_ngsi_entity__" TEXT,    PRIMARY KEY ("entity_id", "time_index", "source", "value") ) CLUSTERED INTO 6 SHARDS WITH (    "allocation.max_retries" = 5,    "blocks.metadata" = false,    "blocks.read" = false,    "blocks.read_only" = false,    "blocks.read_only_allow_delete" = false,    "blocks.write" = false,    codec = 'default',    column_policy = 'strict',    "mapping.total_fields.limit" = 1000,    max_ngram_diff = 1,    max_shingle_diff = 3,    number_of_replicas = '2-all',    refresh_interval = 1000,    "routing.allocation.enable" = 'all',    "routing.allocation.total_shards_per_node" = -1,    "store.type" = 'fs',    "translog.durability" = 'REQUEST',    "translog.flush_threshold_size" = 536870912,    "translog.sync_interval" = 5000,    "unassigned.node_left.delayed_timeout" = 60000,    "warmer.enabled" = true,    "write.wait_for_active_shards" = '1' )

@c0c0n3 ok, if I understand all that right, I think the best approach for our scenario is to alter the type my __original_ngsi_entity__ column to object. That way I would be able to recognize if any (!) failures happen during insert and will have a greater chance to not loose any data due to schema changes for example.
P.S. sorry, giving up the primary key/duplicate prevention is not really an option for us ;)

@pinkerltm, thank you for getting back to us, no need to apologise! :-)
So I think I've got to the bottom of this. I've posted below detailed explanations but here's the take-home:

You can have a PK constraint on any table created by QL since it doesn't interfere with QL's normal operation.
QL creates tables with a column policy of dynamic. You can't make it strict like you have it at the moment.
The __original_ngsi_entity__ has to have a type of object.
Even if you fix (2) and (3) you might still experience issues when an insert fails and the notified entity payload contains a GeoJSON location with nested arrays.

(4) will take a while to fix, we have two issues to juggle: #344 and #375. One thing you can do until we fix this is ignore errors in the logs related to (4).
What caused the reported error
Your table has a column policy of strict instead of dynamic. When QL creates a new Crate table, it does so by explicitly setting column_policy = 'dynamic'. So this is what I think must've happened. You initially had QL 0.7.5 and the table got created without the __original_ngsi_entity__ column---this feature was introduced by #335 and released in version 0.7.6. Then the table definition got changed slightly by hand: adding a PK and setting the column policy to strict or perhaps you recreated the table yourself? Whatever the case, you ended up with a table, which for the sake of argument, is similar to the test table below
CREATE TABLE test (
    eid TEXT,
    tix TIMESTAMP WITH TIME ZONE,
    PRIMARY KEY (eid, tix)
) WITH (column_policy = 'strict');

Notice if you don't specify a column policy, Crate defaults it to strict. Next you upgraded to QL 0.7.6 and on inserting data QL encountered an error---this could've been a duplicated PK or something else, it doesn't matter. What QL does if it can't insert the entity on the first shot, it tries to at least save the original JSON that was posted to the notify endpoint in the __original_ngsi_entity__ column---see #335 for the details. The SQL statements QL issued would've been be similar to the ones below:
CREATE TABLE IF NOT EXISTS test (
    eid TEXT,
    tix TIMESTAMP WITH TIME ZONE,
    __orig__ OBJECT
) WITH (column_policy = 'dynamic');

INSERT INTO test (eid, tix, __orig__) VALUES ('d:1', '2020-11-04T17:59:02.531Z', '{ "eid": "d:1" }');

Unfortunately the first statement has no effect so the table definition is left unchanged---exactly the same problem as in #375. In particular the column policy is still strict and there's no __orig__ column, so the INSERT is doomed to fail and if you try that yourself in the Crate admin console, you'll get
SQLActionException[ColumnUnknownException: Column __orig__ unknown]

So it looks like, strictly speaking, this isn't a bug in QL, the column policy shouldn't have been manually changed from dynamic to strict. Case closed? Not quite. Read on...
An accident waiting to happen
Now I think you can keep the PK constraint since it won't interfere with QL's normal operation. But you should definitely change

the column type to dynamic
the __original_ngsi_entity__ to object

Cool. The meanies are lying in wait though :-) In fact, next time both the conditions below are met

the first insert fails---if I got you right, this can happen quite frequently because you have tons of duplicates to deal with and so getting rid of the PK constraint isn't really an option.
the payload contains a GeoJSON location with coordinates requiring nested arrays---e.g. a polygon just like you have in the example payload seen in the log snippet you posted here.

Then the second insert QL attempts to recover from the first failing will fail too because the __original_ngsi_entity__ will now contain a GeoJSON object with nested arrays and Crate doesn't support that---see #343. Here's the scenario exemplified using our fictitious test table from earlier.
CREATE TABLE test (
    eid TEXT,
    tix TIMESTAMP WITH TIME ZONE,
    loc GEO_SHAPE,
    __orig__ OBJECT,
    PRIMARY KEY (eid, tix)
);

Now say QL gets notified of an entity update, tries to insert it
INSERT INTO test (eid, tix, loc)
VALUES ('d:1', '2020-11-04T17:59:02.531Z',
    { type = 'Polygon', coordinates = [[ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ]] }
);

and it goes well but soon afterwards, it gets notified of the same update again, so the PK constraint will make the insert fail---notice the insert could fail for any other reason, the crux of the matter here is that there's a location in the payload containing nested arrays. Next thing QL tries to do is stash away the original JSON POSTed to the notify endpoint with another insert similar to
INSERT INTO test (eid, tix, __orig__)
VALUES ('d:1', '2020-11-04T17:59:02.531Z',
    '{
      "eid": "d:1",
      "loc": { "type": "Polygon", "coordinates": [[ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ]] }
    }'
 );

but this will fail too because the JSON in the __orig__ column value contains nested arrays. Oh dear. It looks like we're stuck between a rock and a hard place. Unfortunately I can't offer you any workaround at the moment except for ignoring this kind of failure for the time being. We'll have to rethink how to recover from insert failures, so hopefully this won't be an issue going forward, keep an eye on #344.

@pinkerltm i suppose we can close the issue given that ColumnUnknownException: Column __original_ngsi_entity__ unknown is caused by  hacking of tables and not a QL bug.

@chicco785 wasn't able to verify it yet, but with the great explanation I should be able to fix it. Thanks a lot

@pinkerltm fyi in PR#373 we are changing columns default from dynamic to strict and manage the add of columns in ql, which would avoid any issue, when it's released. it may be experimental for a while though, due to the fact of quite some changes we introduced, and that may need additional testing. these are all updates coming:

implement basic redis cache for metadata (reducing query to database)
provide a reusable connection to database (nor crate driver or pg8000 seems to support pool natively)
improve logs and use orion like format
add support for fiware-correlator (facilitate tracking data chains between agents, orion and quantumleap)
change crate table column_policy from dynamic to strict
support injection of NGSI-LD payloads in NGSI-V2 backward compatible way
when type is not an NGSI type, it's type is derived from value (support #383)


Sometimes when you scroll in MultipleChoiceViewController more than one button gets highlighted

Not sure if this is happening anymore


Clear cookes not on the Whitelist when exiting Firefox.

There always seem to be a few non whitelisted cookies that never get deleted for some reason.  An option to clear all non whitelisted cookies when exiting Fx would probably handle this.

It's probably cause you had a site or a subdomain still open relating to that cookie. You can try going into the popup -> Cookie cleanup (Ignore open tabs) and see if that helps.

Also, currently there's no way to set an extension to do something on exit with current WebExtension APIs, so it would have to be on browser start up.

Failling to clear github cookies with the addon.

open github page and log in
click "clean all cookies: ignore open tabs"
reload
Still logged.
try closing all tabs github related
Still logged
:(

@labors89 Have you used any other Cookie Extension before by any chance?
Try these troubleshooting steps:

Clear all your cookies (start with a clean slate)
Reset settings other cookie extensions might have made in about:config -> restore default of all network.cookie.* preferences

Try these troubleshooting steps:

Clear all your cookies (start with a clean slate)
Reset settings other cookie extensions might have made in about:config -> restore default of all network.cookie.* preferences

Did the above but github cookies still present, same problem happens in chrome, even with a new profile with only ublock origin and cookie-autodelete enable..

@labors89 That's weird cause I don't have this issue. Can you go into your developer tools and click Browser Console (Contol + Shift + J) on Firefox and see what appears when you click Cookie Cleanup in the options.

Hmm, for some weird reason it didn't worked with firefox , chrome or chrome + new profile. Just tried to create a new profile with firefox and now everything is gold.
I really have no clue about how to analyse the console output, sorry I cannot pinpoint the cause. But thank you anyway :)

@labors89 Yeah I figured a new profile would help since legacy extensions like to leave a lot of crud that doesn't get cleared until you make a new profile.


fix(remix-dev/vite): change build output paths

This is a fix for https://github.com/remix-run/remix/pull/8039#issuecomment-1817641697 and a better fix for https://github.com/remix-run/remix/issues/8023 and https://github.com/remix-run/remix/issues/8038.
See the changeset and updated docs for more details, but tl;dr:

The server is now compiled into build/server by default (rather than build)
The client is now compiled into build/client by default (rather than public/build)

This fixes an issue where the way Vite manages the public directory clashes with the way the existing Remix compiler works. So far we've been trying to get Vite to behave like the Remix compiler but it's causing issues since it's such a different model, so instead we're now leaning into the way Vite works.
As a bonus, I personally think the build output feels a lot cleaner too ✨

Would this necessitate updating image sec references in the apps as well?
For example, given you had an image stored at public/images/my-image.jpg and a reference to it in a page <img src="/images/my-image.jpg"/>, what would need to change here (if anything?)
Would the recommended approach change to storing image assets in a app/assets directory and let vite bundle them and handle the asset paths?
import imageSrc from "~/assets/images/my-image.jpg"

...

<image src={imageSrc}/>

@justinwaite Without this PR, you'd have to move your images from public to app. The PR is addressing this exact situation so you can keep your images in public and reference them directly by the path without having to import. You can get more context here: https://github.com/remix-run/remix/pull/8039#issuecomment-1817641697.

This is available in the latest nightly, currently 0.0.0-nightly-8c42697-20231122
@justinwaite @gustavopch @nicksrandall If you could all try it out and report back, that would be super helpful 🙏

@markdalgleish I have migrated and it is working. I like this approach.

@markdalgleish I was able to fork my original stackblitz and migrate: https://stackblitz.com/edit/remix-run-remix-5qicaa?file=vite.config.ts
The setup in the stackblitz is to emulate how we would setup an app to run on a base path with how Remix works today. In this case, the basepath is /mybase. It requires that:

Assets (images, etc) be placed in public/mybase
Routes are explicitly prefixed with mybase (e.g. mybase._index.tsx or mybase.settings.tsx)
The publicPath is set to /mybase in the remix config in the vite plugin (no longer need to mess with assetsBuildDirectory).

Testing it out, the build directory does indeed get populated with client and server directories. The assets in the public directory are copied into the client build. Remix serve seems to gracefully handle everything. When I check the network logs, js bundles and images are being properly served from /mybase.
Just a couple of thoughts:

I really like the new build output structure. Makes sense, it's cleaner, and one less directory for me to make sure my editor is ignoring properly (and one less entry into gitignore 😄 )
I wish Vite dev emulated production more closely. When running Vite in dev mode, assets are under /mybase, but rather are scattered around /node_modules, /app, @id, @vite, etc. This really only becomes annoying when trying to proxy apps in local development, where I have to manage proxy entries for all of those unique root-level entrypoints. Perhaps this would be a better experience if the vite base option were supported natively within remix?

Thanks for the quick support on this one!

@markdalgleish Working here as well!


use Integer instead of Float for TPS

cc @jbunce who flagged this.
We should change our TPS to use int instead of floats: https://github.com/omisego/elixir-omg/blob/master/docs/perf_test_result_dumps.md

done


Bug in indicator when hides a tab

Example
http://codepen.io/anon/pen/mJjdRj
I fixed this issue changing one line in tabs.js to $links = $this.find('li.tab:visible a');

Why are you hiding a tab? Why can't you just remove it? I don't think this is a problem that needs to be addressed at our level. If you have found a fix then you should be fine.

Your framework is a charm. I think the framework can handle this kind of situation. Other mature frameworks that i have been used handle this. Please reconsider this functionally to next release :)
Thanks!


i18n(zh-cn): Translate reference/api-reference.mdx

What kind of changes does this PR include?

New or updated content
Translated content

Description
-Translate reference/api-reference.mdx content to Chinese.


CONFIG to define a FILENAME and use that instead of FILE to reduce flash usage

Is your enhancement proposal related to a problem? Please describe.
In order to reduce flash usage, we're trying to minimize the strings that are compiled in, mainly from using asserts defined in __assert.h.
Many strings show up as WEST_TOPDIR/zephyr/drivers/clock_control/nrf_clock_calibration.c but ideally this can be reduce to just nrf_clock_calibration.c.
There's a config to help reduce the strings by removing the condition being tested CONFIG_ASSERT_NO_COND_INFO but it would be great if there could be one to use the filename instead of the file+path.
Describe the solution you'd like
Usually we can pass in -D__FILENAME__="$(notdir $<)" to the CFLAGS and that would strip the full path and just use the filename only.
Describe alternatives you've considered
I tried adding that via a zephyr_compile_options but that's leading to build errors.
arm-none-eabi-gcc: error: $(notdir $<): No such file or directory

Did someone get this to work?

Hey @henrikbrixandersen, I see this is assigned to you now. Do you have an idea if this is easily doable with existing build infrastructure?

I am sorry, but this is not assigned to me and I'm afraid I don't have a solution to this.


How to share fastlane config files between users

So, I have fastlane configured in my local machine and I want to commit the config files to the repo but they have my username for applestore saved there.
Is this the normal behavior?

Hi @lucasfeliciano Great to hear from you! If you'd like to avoid this you can use ENV files and put them in your .gitignore. Otherwise you can always not include them in your project and just get prompted at runtime.
Hope that you have a great day!

So in the Appfile you can do the following:
apple_id ENV["APPLE_ID"]

and then run fastlane using
<EMAIL_ADDRESS>fastlane beta

In general you can also pass your Apple ID username using
<EMAIL_ADDRESS>fastlane lane

and don't specify it in the Appfile 👍


videogame sales notebook updated for SageMaker SDK improvements

Description of changes:
Hello, I am the original author of this notebook.  Since it was originally published around the GA launch of Amazon SageMaker, there have been many improvements related to the SageMaker SDK.  This pull request incorporates simplified, much more readable code leveraging the SageMaker SDK.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I have pushed a second round of changes responding to the comments above.

I have pushed a third round of changes addressing the comments related to region and simplifying the session usage.

lgtm. would like a review from the Algorithms team.

Looks good to me!


extra parameters when using python api: issues

Dear adugnag, thanks for creating this fantastic package!
I have no problem running the javascript api and incorporating it into my workflow on the GEE code editor.
I am having issues running the same workflow over the same study area using the python api: I am running into issues around the extra parameters of orbit_num and platform number specifically. I noticed these are not required for the JS code but are required for the python. Can I just comment these out? I noticed there are no default values for these two?
Thanks!

Hello
I'd like to know if you knew how to execute it. How did you do it? Thank you very much.@bhyleee
Thanks @adugnag

PLATFORM_NUMBER=='A' or PLATFORM_NUMBER=='B'

Yes I was hoping it would be a similar situation where the script would query for both A or B, but I eventually just select one or the other. Thanks
"ORBIT": 'BOTH',
"ORBIT_NUM": None,
"PLATFORM_NUMBER": "A",

Sorry for the very late response. I just updated the Python code so there shouldn't be anymore bugs.


Update README.md

Fixes https://github.com/tensorflow/tensorflow/issues/44734

Thank you for doing this.


Crash on install.

[Enter steps to reproduce below:]

Install it
Objserve the bug

Atom Version: 1.0.3
System: Mac OS X 10.10.4
Thrown From: break package, v0.3.1
Stack Trace
Failed to load the break package
At Cannot read property 'prototype' of undefined

TypeError: Cannot read property 'prototype' of undefined
  at __extends (/Users/rokyed/.atom/packages/break/lib/break-view.coffee:1:1)
  at /Users/rokyed/.atom/packages/break/lib/break-view.coffee:5:3
  at Object.<anonymous> (/Users/rokyed/.atom/packages/break/lib/break-view.coffee:121:5)
  at Object.<anonymous> (/Users/rokyed/.atom/packages/break/lib/break-view.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (/Users/rokyed/.atom/packages/break/lib/break.coffee:1:13)
  at Object.<anonymous> (/Users/rokyed/.atom/packages/break/lib/break.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:715:34)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:190:28
  at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:167:15)
  at Package.module.exports.Package.load (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:181:12)
  at PackageManager.module.exports.PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:373:14)
  at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:452:30)
  at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:370:29
  at exit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:59:16)
  at triggerExitCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:213:47)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:227:18
  at Socket.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:98:18)
  at emitOne (events.js:82:20)
  at Socket.emit (events.js:166:7)
  at Pipe.close (net.js:464:12)

Commands
 18x -3:41.8.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -3:36.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -3:28.7.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -3:28.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -3:15.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -2:59.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  7x -2:47.7.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -1:07.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ],
    "projectHome": "/www/mainline"
  }
}

Installed Packages
# User
atom-material-syntax, v0.2.1
atom-material-ui, v0.5.13
break, v0.3.1
git-diff-details, v0.19.0
git-log, v0.4.1
minimap, v4.12.2
pdf-view, v0.23.0
pigments, v0.9.3
tabs-to-spaces, v0.11.0
terminal-panel, v1.14.1

# Dev
No dev packages

Hi @rokyed
This is likely related to #18. Unfortunately I no longer use Atom and have since stopped maintaining this package. It should have been unpublished as per https://github.com/atom/atom/issues/6867#issuecomment-112425395 Maybe if you could drop a note there to let the people who have the power to remove it from the official Atom packages. If you are interested in maintaining / fixing I would be happy to transfer ownership

Hi,
@rokyed This should now be resolved.


LIS

Submission Title
LIS
Submission Type
Algorithmal
Submission Description
Longest increasing subsequence problem is to find a subsequence of a given sequence in which the subsequence's elements are in sorted order, lowest to highest, and in which the subsequence is as long as possible.
Contributors

[x]  C++ -
[ ]  C -
[ ]  Python -
[x] Java -
[ ] JavaScript -
[ ] TypeScript -
[ ] Golang -
[ ] Ruby -
[ ] Scala -

Can i work on this issue in c++?

Hello, I would like to work on this issues in Java

Can you assign this to me in python?

@ahampriyanshu Pull request added 👍

Can you assign this issue to me? I would like to work in CPP.

@ahampriyanshu .can you assign this issue to me..i ll work on this in C.

thanks everyone :v:


Plex Recently Added: How to use?

Hello, I'm not sure what i'm doing wrong to get this new app working on my tidbyt. What i've set in the tidbyt app for this app:
My Plex server is set to Preferred, not Required.
Server IP: the local IP of my plex server: <IP_ADDRESS>
Server port: the local port of my plex server: 32400
Plex Token: my plex token per https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
API Key: blank -- since i'm not using the nodejs route, this isn't used, right?
I save it but it never connects, just the cloud with the line through it in place of the preview.
I'm willing to try the nodeJS route if there were instructions. Any help would be greatly appreciated.
*EDIT: Apparently LAN connection isn't possible. Changed to public IP/port and it now works!

If you're running this from the tidbyt app, then the script is running on their servers, so your local IP of <IP_ADDRESS> won't work. You'll need to set Secure Connections: Preferred in your plex settings and use the local IP.
I write in the readme this is ill-advised since it is a bit of a security issue. The alternative is to run the nodejs server on the network and proxy the request through that with the API key.

Also, the instructions for setting up the proxy server are here https://github.com/tidbyt/community/tree/main/apps/plexrecentlyadded


sushy-emulator - use listening addr in _sushy_url

If listining address is set to something other than :: or <IP_ADDRESS>, then use the listening address as _ip_address in the _sushy_url fact.
Also use ansible.utils.ipwrap to ensure address is wrapped in brackets when needed.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

recheck

/approve

/lgtm


messaging layer should include receiver metadata such as origination

Messages delivered through the framework currently consist solely of a deserialized frame representing on-wire structures (e.g. RecvMsg(msg *pb.OpenchainMessage)).  Anything within the frame should generally be treated as suspect without further validation (such as checking a digital signature).  However, there are use-cases where locally source metadata would be useful: For example, a TLS encrypted channel or a chain-code to chain-code invoke have attributes that are already ascertained by the peer without falling back to a more heavy-handed in-band mechanism such as signature verification.  The proposal is that the messaging layer should include a metadata frame that the peer can use to convey additional information along with a message between elements within itself.  This could minimally include message origination (e.g. peer "X", or chaincode instance "Y") and perhaps a flag to indicate the confidence in the origination assertion (e.g. "verified=true" if the message arrived over TLS or emanated from a chaincode invoke operation).  e.g. RecvMsg(meta *Meta, msg *pb.OpenchainMessage)

@ghaskins @binhn where does this stand?

@christo4ferris I still care about this

@ghaskins can you please open a JIRA issue and then close this? Thanks


[Accessibility] Drawing Bluetooth pattern WIP

https://microbit-global.monday.com/boards/1356069004/pulses/1368253368
WIP!!

For some reason the bottom right LED cannot be hovered / highlighted directly or indirectly:

The inputs don't stop a user typing 100 or 0 and then tabbing along to the next input.
Should we use cursor: pointer;?
Should the highlight work on increasing and decreasing the number of lit LEDs. It only has changes for increasing at the moment. Not sure if this is really for this PR or a follow up.

Overall it works well and makes it accessible.

For some reason the bottom right LED cannot be hovered / highlighted directly or indirectly
The inputs don't stop a user typing 100 or 0 and then tabbing along to the next input.

Great catches!

Should we use cursor: pointer;?

Good point, yes, I think we should to make the inputs completely undetectable when unfocused

Should the highlight work on increasing and decreasing the number of lit LEDs. It only has changes for increasing at the moment. Not sure if this is really for this PR or a follow up.

Will see whether this PR touches that logic, if so, can do in this PR :)

Will work towards merging for now, and do potential copy changes later


Missing documentation about Gamepad API

This is not a bug report, but a documentation issue, I can't find any information about the Gamepad API, where can I find information to know how to simulate a gamepad and trigger key presses with it?

Not stale

I don't think we support that and currently it's not a priority for us, unfortunately.

Thanks for the timely response 🙇♂


Progress color always matching Normal color

This is my button
    <com.dd.processbutton.iml.ActionProcessButton
        pb:pb_colorPressed="@android:color/transparent"
        pb:pb_colorComplete="@color/blue"
        pb:pb_textComplete="@string/complete"
        pb:pb_colorError="@color/red"
        pb:pb_textError="@string/error"
        pb:pb_colorProgress="@color/blue"
        pb:pb_textProgress="@string/progress"
        pb:pb_colorNormal="@color/green"
        android:text="@string/confirm_idle" />

the progress state shows as green for some reason. I'm not setting the colors again in code or anything.

Try to run sample app and check if issues remains.

The issue is in the sample app too: http://imgur.com/a/tlAtW

@pakoito sorry, I can't reproduce this issue. For me color always changes according to pb_colorProgress. Can you provide Android Version and Device manufacturer?

Samsung Galaxy S4, Android 4.4.2

I just tried on Android 4.4.4 device, all seems to work. Can you install sample app from play store? Also can you check on emulator or another device?

Xiaomi MI2-S with MIUI 6 (4.1.X) with the app from the store has the same issue.

I have tested on several devices, Nexus 5, Nexus 7, Xperia S and Genymotion. So when you install sample app, and choose Action Button Progress sample, progress is green?

Link to video :)

Your video is showing the problem too! Check the imgur link above, progress state -which if I understood correctly is Loading.. - is set to white background, yet the button still shows the same as idle. My original post has Loading green.
In the default sample idle is blue and loading is violet or purple, IIRC. If my color blindness is not kicking in, your video shows both as the same color.

Ok, I misunderstood you. So pb_colorProgress is used for button progress line, in btnSignIn.setMode(ActionProcessButton.Mode.PROGRESS); mode. So you can't change color of button in progress mode.

Okay, can you please put this as a feature request then, please?

@pakoito yes, but I will not be able to update library for a while...

Created issue #35

Great, thank you.


Create a Google Drive and the project description document

How To Do This

Create the shared Google Drive
Create the Description Document in Google Drive
Invite everyone to the Google Drive
Mark this Issue as closed

The Drive has been created.

The document as well.


push data asynchronously at leader

now we always start appending log to log store at leader until all the futures of pushing data to followers are completed , which will involve unnecessary latency
this PR aims to make pushing data asynchronously,  so that logs can be set to follower ASAP. it does not matter whether push_data is successful, since follower will try to fetch data from the leader if push_data fails

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 67.17%. Comparing base (1a0cef8) to head (dd3156d).
Report is 91 commits behind head on master.

Files with missing lines
Patch %
Lines

src/lib/replication/repl_dev/raft_repl_dev.cpp
66.66%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #590       +/-   ##
===========================================
+ Coverage   56.51%   67.17%   +10.65%
===========================================
  Files         108      109        +1
  Lines       10300    10729      +429
  Branches     1402     1466       +64
===========================================
+ Hits         5821     7207     +1386
+ Misses       3894     2824     -1070
- Partials      585      698      +113

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

it seems right but I would like to hold this till we solve and bake a stable version for PG move.

sure, will also loop other members in

we dont wait for the future at all

we use folly::collectAllUnsafe to wait for the completion of all the future, no?

collectAllUnsafe

https://github.com/facebook/folly/blob/main/folly/futures/Future.h#L2360-L2385
it returns a future which satisfied when all to_be_collected features satisfied.

collectAllUnsafe

I see , you are right. I misunderstood the meaning of collectAllUnsafe. now I think , as you said , there is no difference compared to run_on_forget. let me close this pr


feat: Exclude configs from actions while committing to git repo

Description
Exclude the app slug from git repo as the imported app from git repo will have different name.
For actions created from datasources of type SAAS, API we need to exclude the config values from committing to git repo
Fixes #11997
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Locally

Checklist:

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

I'll let @nidhi-nair to review this PR as I don't have the complete context here 🙂

@AnaghHegde, for the remote plugin migration, we'll also have Twilio and a bunch of Hubspot plugins on prod. Could you please limit that to Airtable. Also let's talk to @hiteshjoshi and get a clear set of guidelines about when we're supposed to mark this value as true or false from a product perspective? We can use Twilio and Hubspot as examples to figure this out. This will help our SaaS (remote) team set this up independently.
Also, looks like our default behaviour for this is that we do copy over the config. Is that intended? If one of the plugins skips on this config because of an oversight, what behaviour do we want to default to?

@nidhi-nair For the default behaviour yes we do copy over the config as it does not have any sensitive data and does not affect the import flow.For Twilio and Hubspot we can have a call to discuss this in detail.

@AnaghHegde Since the linked issue has been closed because we don't wish to follow the proposed implemenetation plan, is this PR still relevant? Can we close this PR?

Closing this PR as we have decided to not to implement this feature.


Update F# on Azure Docs

The following F# docs need to be updated to the new SDKs https://aka.ms/azsdk/releases

[ ] Blob Storage https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/blob-storage

[ ] Queue Storage https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/queue-storage

[ ] File Storage https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/file-storage

[ ] Table Storage https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/table-storage

Table Client Lib is coming soon. Skip for now

[ ] Package Management https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/package-management

Include both Azure. and WindowsAzure. until we have Table client lib.

@jongio I'm just reading through this. To be honest, I think a better way to approach this today would be to find whatever Azure Storage docs you have for the new SDK and add an "F#" tab to each of them. Potentially a few new pages e.g. working with "Azure Storage from F# Scripts" or something but putting all the docs together might be the way forward.
I know the reasoning why these separate articles were created - at the time it made more sense - but I think putting the F# docs in the same place that the C# versions for them would be better. @dsyme I think that you were involved in the original creation of these pages - what do you think?

For example, I'd be inclined to update these docs to support C# and F# as separate articles (and simultaneously let's rename the ".NET SDK" examples to "C# SDK").

cc @cartermp

Completely agree with @isaacabraham's suggestion.

I'm not totally sure.   On the one hand it would be great if the Azure SDK team took the view that the SDK was a multi-language SDK and designed and documented each experience with that in mind, making best use of the full range of facilities each language provides.
However, in reality, the SDK is designed and documented as a C# SDK.  The SDK is still very good to use from F#, but it neither captures what's special about F# in this context nor lands F# programmers in the sweetest spot, because it misses community-developed resources like The Azure Storage Type Provider
I reckon the most valuable point of investment is to systematically document how to make F# programmers most productive on Azure.  The Azure SDK will be part of that.  In many ways that's what the https://docs.microsoft.com/en-us/dotnet/fsharp/using-fsharp-on-azure/ were angling to achieve.

Maybe there's room for both? I would like to get F# docs "into the box" on the standard Azure docs as it's probably going to get better SEO for people searching for help on the Azure Storage SDK, but already there are some evident differences in how the docs might be structured - for example, in the linked docs above, it talks about using a console application and setting up environment variables etc. - this is totally not how an F# developer would explore an API, they'd just open up a script, reference the nuget package and go from there (in .NET 5 this becomes even more compelling). So maybe there's a case for having both reference docs on the "standard" page, and a more opinionated piece that refers to things that are more F# specific?
The Type Provider is in a sorry state at the moment - @cartermp has done a lot of more to help out but it's been months since I touched it - it actually does seem to currently work on .NET Core in the current version but I was thinking, if we moved to this new SDK it'd probably make sense just to start from scratch and create a much more lightweight TP that was quicker to author and maintain - it probably wouldn't have support for all the fancy stuff that the current TP (particularly around Tables) has, but instead just a simple way to rapidly get to the blob references given either a live or offline schema / blob list.

Yes, part of what I'd like about a community collaboration on this specific topic is it gives us a chance to revise the community technologies as well (including simplifying and deprecating them)

Hi @jongio, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.


Code Settings page

figma link:   https://www.figma.com/file/dOQv8d0yWU9BU7Adea2LIU/TEAM35_MY_DEBTORS?node-id=904%3A773
Reply done when this task is completed

Still working on it


Updates to AlertDto to make comments a nullable value.

Updates to AlertDto to make comments a nullable value.

Updates to AlertDto to make comment nullable as it can be null. Link to Slack conversation with Syscon team -
https://mojdt.slack.com/archives/C02T3S6QEVC/p1677258431981179


fixed 404 link errors and minor edits

end-to-end.md:
-- fix 404 link errors and minor edits
broombridge.md
-- fix 404 link errors
-- fix generic anchor text instances ("here")
-- Edited the data generation paragraph. The original run-on sentence was hard to interpret - please review to ensure that didn't alter the intent.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/libraries/chemistry/samples/end-to-end.md
75
55
9
link
:white_check_mark:

articles/libraries/chemistry/schema/broombridge.md
68
26
13
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

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

File
Status
Preview URL
Details

articles/libraries/chemistry/samples/end-to-end.md
:white_check_mark:Succeeded
View

articles/libraries/chemistry/schema/broombridge.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/libraries/chemistry/samples/end-to-end.md
75
55
9
link
:white_check_mark:

articles/libraries/chemistry/schema/broombridge.md
68
26
13
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

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

File
Status
Preview URL
Details

articles/libraries/chemistry/samples/end-to-end.md
:white_check_mark:Succeeded
View

articles/libraries/chemistry/schema/broombridge.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 2cdd39a:
:clock10: Pending: waiting for processors (11 builds ahead of you)
:warning: Docs Build is busy, currently there are 11 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 2cdd39a:
:clock10: Pending: waiting for processors (11 builds ahead of you)
:warning: Docs Build is busy, currently there are 11 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/libraries/chemistry/samples/end-to-end.md
75
55
9
link
:white_check_mark:

articles/libraries/chemistry/schema/broombridge.md
68
26
13
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/libraries/chemistry/samples/end-to-end.md
75
55
9
link
:white_check_mark:

articles/libraries/chemistry/schema/broombridge.md
68
26
13
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 2cdd39a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/libraries/chemistry/samples/end-to-end.md
:white_check_mark:Succeeded
View

articles/libraries/chemistry/schema/broombridge.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 2cdd39a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/libraries/chemistry/samples/end-to-end.md
:white_check_mark:Succeeded
View

articles/libraries/chemistry/schema/broombridge.md
:white_check_mark:Succeeded
View

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


remove Header flag from BottomNavigationBar items

Description
The flag is breaking iOS Switch Control for unknown reasons. And is is also very strange to have these buttons marked as Header (e.g. the Voice Over announcement is just confusing).
Related Issues
Fixes https://github.com/flutter/flutter/issues/37867
Tests
I added the following tests:

Updated tests to reflect that header flag is gone.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

Are we sure this didn't fix something else on another platform?
Shoudl we restrict this to only iOS?

(Discussed offline - this was added for iOS but is wrong)
LGTM!


SageMaker on Flyte: TrainingJob for training with built-in algorithms and basic HPOJob support  [Alpha]

TL;DR
This PR adds the necessary definitions for basic support of SageMaker TrainingJob and HPOJob (Hyperparameter Optimization)
Type

[ ] Bug Fix
[ ] Feature
[x] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
This PR adds the basic support for users to invoke SageMaker TrainingJob (built-in algorithm mode) and SageMaker HPOJob from within Flyte. The follow paragraphs demonstrates the supported use cases.
Defining a Simple Training Job
Users can leverage SageMaker's powerful built-in algorithms easily without needing to write any function or logic. They can simply define a SdkSimpleTrainingJobTask in Flytekit and supplies the settings and the spec of the built-in algorithm as follows:
alg_spec = training_job_models.AlgorithmSpecification(
    input_mode=_sdk_sagemaker_types.InputMode.FILE,
    algorithm_name=_sdk_sagemaker_types.AlgorithmName.XGBOOST,
    algorithm_version="0.72",
    metric_definitions=[training_job_models.MetricDefinition(name="Minimize", regex="validation:error")]
)

# Definition of a SageMaker training job using SageMaker's built-in algorithm mode of XGBoost
xgboost_simple_train_task = training_job_task.SdkSimpleTrainingJobTask(
    training_job_config=training_job_models.TrainingJobConfig(
        instance_type="ml.m4.xlarge",
        instance_count=1,
        volume_size_in_gb=25,
    ),
    algorithm_specification=alg_spec,
    cache_version='v1',
    cacheable=True,
)

Defining a simple Hyperparameter Tuning Job
SageMaker-on-Flyte also supports easy chaining between a TrainingJob task and a hpo job. After users define a TrainingJob task, he/she may want to apply hyperparameter tuning to the the training, while also maintaining the flexibility to run the TrainingJob task standalone. This should be easily doable by using the SdkSimpleHPOJobTask in our SDK. SdkSimpleHPOJobTask accepts the definition of a TrainingJob task as a part of the spec.
# Definition of a SageMaker hyperparameter-tuning job.
# Note that is chained behind the simple TrainingJob task defined above
xgboost_simple_hpo_task = hpo_job_task.SdkSimpleHPOJobTask(
    training_job=xgboost_simple_train_task,
    max_number_of_training_jobs=10,
    max_parallel_training_jobs=5,
    cache_version='2',
    retries=2,
    cacheable=True,
)

Invoking Training Jobs Task and Hyperparameter Tuning Jobs Task
Invoking Training Job Tasks and HPO Job Tasks from inside a Flyte workflow is pretty much the same as invoking other types of tasks. You should be able to achieve this by simply supplying the required inputs to the task definition. For Training Job Tasks and HPO Job Tasks , required inputs are pre-defined inputs that we think is needed for every training job. That's why you don't see the declaration of these inputs in the task definition -- we added them for you in our SDK.
@workflow_class
class SageMakerSimpleWorkflow(object):
    static_hyperparameters = Input(Types.Generic, required=True, help="Sample hyperparameter input")

    my_simple_trianing_task_exec = xgboost_simple_train_task(
        train="s3://path/to/train/data",
        validation="s3://path/to/validation/data",
        static_hyperparameters=static_hyperparameters,
        stopping_condition=StoppingCondition(
            max_runtime_in_seconds=43200,
        ).to_flyte_idl(),
    )
    ...

Flyte's Single Task Execution capability also makes it easy to invoke a SimpleTrainingJobTask and SimpleHPOJobTask. That is, users do not need a workflow to launch the SageMaker tasks; instead, they can simply define the tasks, and then register and launch the tasks standalone, which enables fast iterations.
xgboost_simple_train_task = training_job_task.SdkSimpleTrainingJobTask( ... )

xgboost_simple_hpo_task = hpo_job_task.SdkSimpleHPOJobTask(
    training_job=xgboost_simple_train_task,
    ...
)

Tracking Issue
https://github.com/lyft/flyte/issues/255
Follow-up issue
https://github.com/lyft/flyte/issues/431

🔨

This looks awesome, two major comments

Support for other formats (currently you can keep it at CSV)
Docs to be added

Looks good to me, but we should get plugin merged before this


SourceTable of the DrillDownPageID / LookupPageID must match the Table ID

Title
We sometimes make a full copy of table from Business Central to new tables, copy from an existing table to a buffer / temporary / staging / import table, ... When copying these source tables, sometimes the DrillDownPageID and LookupPageID are forgotten to be updated on the new target table and still reference to the 'old' source table, which is wrong. DrillDown and Lookup will not work properly on the newly created table, since the SourceTable of the pages referenced by DrillDownPageID / LookupPageID does not match the ID of the parent table.
Description
Reason for the rule
The rule will help the developer to detect table definitions containing invalid DrillDownPageID / LookupPageID properties that are not in line with the SourceTable used on these referenced pages.
Bad code sample

Good code sample

Remarks
Other bad code sample

Yes, please consider this. Otherwise we only discover later that the drilldown/lookup can't work, at runtime, when we could've fixed it at compile time right from the start.

https://github.com/StefanMaron/BusinessCentral.LinterCop/discussions/39

Thanks for reporting this issue. Sorry we haven’t completed it yet, but we’ve had to prioritize elsewhere. We’re planning to give the CodeCop engine and its rules an overhaul in a future major release. Thanks for your patience.


Angular cannot compile the 'docx-preview-sync'

Describe the bug
Error: export 'praseAsync' (imported as 'docx') was not found in 'docx-preview-sync' (module has no exports)
or
Error: export 'renderAsync' (imported as 'docx') was not found in 'docx-preview-sync' (module has no exports)
Document
I have installed the package "npm i docx-preview-sync", but
When trying to compile the Angular project I have got the error.
Source code
import * as docx from 'docx-preview-sync';
docx.renderAsync(download.content, document.getElementById("wordContainer"))
.then(x => console.log("docx: finished"));

Describe the bug Error: export 'praseAsync' (imported as 'docx') was not found in 'docx-preview-sync' (module has no exports) or Error: export 'renderAsync' (imported as 'docx') was not found in 'docx-preview-sync' (module has no exports)
Document I have installed the package "npm i docx-preview-sync", but When trying to compile the Angular project I have got the error.
Source code
import * as docx from 'docx-preview-sync';
docx.renderAsync(download.content, document.getElementById("wordContainer")) .then(x => console.log("docx: finished"));

Sorry,The Readme.md is old version from docx-preview.
Try to use parseSync function instead of parseAsync function.
I rewrite  Readme.md for this library,it's useful for user.
This library is still in the development stage, so it is not recommended to use it in production.


Fusion: fixing frame range targeting

Changelog Description
Frame range targeting at Rendering instances is now following configured options.
Testing notes:

open fusion workfile and create render instance.
test all three options on render target switch. Make sure comp timeline is set to different frame range then asset db and set render range to some different range then comp range so you can test the calculation of handles.
ideally test it on multiple rendering targets

Closes https://github.com/ynput/OpenPype/issues/5012

...and have a validation for when they are outside of the comp's global in/out because Fusion seems to fail rendering for those cases anyway...

I have created a validator that might be of interest to modify and integrate in this PR: https://github.com/ynput/OpenPype/pull/4921

...and have a validation for when they are outside of the comp's global in/out because Fusion seems to fail rendering for those cases anyway...

I have created a frame-range validator that might be of interest to modify and integrate in this PR: #4921

Thanks. Took a quick look but unfortunately it's not a perfect fit, but it does show some ideas for improvements to the validator in this PR.

We are having bug in the Render Local. It is not restoring original render range after it is rendered.

@jakubjezek001 could you try again?

@jakubjezek001 could you try again?

works perfect now and ready to be Approved ;) Thanks @BigRoy

I did a lot of the commits so take my approval with a grain of salt please. @EmberLightVFX anything that still stands out to you?

Eh, sorry to be so quick. This was painful at one of our clients and there was a pressure to deploy it quickly. @EmberLightVFX you might want to give some feedback on this please.


threadpoolctl.threadpool_limits(n) is surprisingly expensive

Results from a profiling session of https://github.com/joblib/threadpoolctl/blob/ee7fad84615fbdf846a69a915530542b3f7efee9/threadpoolctl.py#L334:
   334                                               def __init__(self, user_api=None, prefixes=None,  modules=None):
   335       250        122.0      0.5      0.0          if modules is None:
   336       250        162.0      0.6      0.0              self.prefixes = [] if prefixes is None else prefixes
   337       250         92.0      0.4      0.0              self.user_api = [] if user_api is None else user_api
   338
   339       250         94.0      0.4      0.0              self.modules = []
   340       250     936453.0   3745.8     98.7              self._load_modules()
   341       250      11421.0     45.7      1.2              self._warn_if_incompatible_openmp()
   342                                                   else:
   343                                                       self.modules = modules

We should look into caching the modules. However, we also have to consider that the modules are possibly only loaded after an UDF task is executed, meaning we have to be careful when to cache.

[x] Track the state of modules that threadpoolctl autoloads throughout script execution
[ ] Implement caching to re-use the module list

A few points from tests:

Issue is reproduced on Windows. Different module inspection method, same bottleneck
With the current release 2.2.0, instantiating the high-level API sets the limits immediately, i.e. re-using the module information would require accessing the internals of threadpoolctl and re-implementing some things.
With the upcoming release 2.3.0 there is a separate ThreadpoolController exposed that allows to separate module discovery from setting the limits
It is possible to re-use the discovered modules that way. However, if new libraries are loaded in the meantime, they will not have limits set.

For the new version this sample code checks a few times if the loaded modules change. If they remain constant a few times, it stops discovery:
class ThreadpoolWrapper:
    def __init__(self):
        self._info = threadpoolctl.threadpool_info()
        self._controller = threadpoolctl.ThreadpoolController()
        self._stable = 0
        self._limit = None

    def check_update(self):
        new_info = threadpoolctl.threadpool_info()
        if new_info != self._info:
            self._stable = 0
            self._controller = threadpoolctl.ThreadpoolController()
        else:
            self._stable += 1

    def __call__(self, limits):
        if self._stable < 3:
            self.check_update()
        return self._controller.limit(limits=limits)

w = ThreadpoolWrapper()

with w(2):
    print(threadpoolctl.threadpool_info())

That means our own set_num_threads() context manager will have to be changed to keep some state between calls. Alternatively we could keep the state in Environment and maybe pass it on to set_num_threads() as an optional parameter?
Until the release of threadpoolctl>=2.3.0 I can see the following options:

Wait on the issue
Depend on the GitHub version
Copy the current threadpoolctl into LiberTEM -- it is quite small and BSD licensed.

Actually, the Environment is instantiated for each task, meaning we should keep the state globally in the interpreter.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1159 ms

Resolved: Bofrost.de performance has improved in cae4527.


add prompt with defer and remove whitespaces

Sorry I'm new to contributing. This one looks better it looks like Atom was doing some whitespace things. I wasn't able to see how to overwrite the old one so please just delete the other.

This is super!
I was actually looking more into what this really is about, and I like the solution here.
What I ended up discussing with myself here, is this:

I don't think the displaydialog should explain to let the user leave the window open, but rather show the countdown on the “Not Now” button.
If the timer-file is higher than 0, and the app is installed with another BLOCKING_PROCESS_ACTION, shouldn't we put the timer to 0 then?
Maybe plist-files would be better, and then use defaults write and defaults read for these values. Then all timers can be in one file.
The BLOCKING_PROCESS_ACTION change is to tell_user_then_kill but the displaylog command only mentions kill