Awake not working

Microsoft PowerToys version
0.41.4
Running as admin

[X] Yes

Area(s) with issue?
Awake
Steps to reproduce
Awake doesn't work out of the box for me. I selected stay awake for two hours, and after the usual "sleep" time the computer went off.
Secondarily, I can't change the setting from the tray area icon, it just reflects what is set in the app itself.
✔ Expected Behavior
should keep the computer alive
❌ Actual Behavior
computer goes to sleep mode regardless of the setting.
Other Software
No response

For the tray, this is tracked in #12145.
Can you clarify what the "usual sleep time" is? How did you select the 2 hour limit for Awake?

Sorry if it wasn't clear. I've selected keep computer awake for the next 2hrs from the power toys main window app, under awake section. By usual sleep time (in my case after 20 idle minutes the computer goes to suspend mode) I meant the sleep time is specified in the windows settings in power management.

I can't reproduce this on my machine - can you share your logs, please? What is the version of PowerToys that you are using?

As stated in the first message, version is 0.41.4.
Where can I find the logs? I've tried looking in the PowerToys folder but haven't found anything

Hi @eirinn1975 ,
The logs would be included in a bug report. Could you please send one?
Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop report into a GitHub comment.
Thank you!

PowerToysReport_2021-07-15-14-30-10.zip
There you are :)

Looking at the logs, I don't see the timed keep-awake ever kicking in. Specifically, the last line in the app log is:
[2021-07-15 14:29:59.4582 INFO Awake.Core.APIHelper] Initiated indefinite keep awake in background thread: 25464. Screen on: False

This echoes what's in the Awake settings (see AwakeMode for reference on number mapping):
{"properties":{"awake_keep_display_on":false,"awake_mode":1,"awake_hours":2,"awake_minutes":0},"name":"Awake","version":"1.0"}

Which tells me that somehow the setting did not take effect. @eirinn1975 - can you try switching modes (from indefinite back to timed), and see if the issue persists?

I'll make some tests today. Is the awake feature based on some service?

After a few tests: I set up suspension and screen off to 1 minute. turned on the awake function for both screen and indefinite time on awake. screen worked, and suspension avoided. I then turned off the keep screen awake function, it worked (screen went black). Then I disabled awake, and the computer stayed on. Seems now I'm in the opposite situation...
Here is the log after these tests.
PowerToysReport_2021-07-19-08-54-53.zip

I am having the same issue on my machine running Win11

Having the same issue win 10

@weoinvm can you please provide some context as to what you are trying to do, what behavior you are seeing, and what system configuration do you have?

I have the same problem.
Awake does not keep the computer awake. Does not appear to make any difference what I set it to. Computer goes to sleep after the usual amount of time.
(I realise this isn't a particularly helpful report - let me know if you want logs or anything - I'm just adding it here to indicate that I'm another person finding that this tool doesn't do what it's designed to do)

Same behavior with my Surface Book 2...

Just to put in my two penny's worth. I am having the same issue with Windows 11 (all updates as of 12 Dec 2021) and Awake 0.51.1. After some work I think the issue only happens after the PC awakes from a sleep state. It works fine after a cold start. I hope this helps find the issue.

I have same issue here on one computer.
Maybe it's related to Modern Standby (S0 power state), because it works without issue on other computers that don't support modern standby...

@dend Do you know if both sleep and hybernation should be prevented? Since they are different settings and the latter one is buried deep in advanced System Configuration settings...

Happy and Healthy New Year!
I just ran into this issue - but under different/very specific circumstances - so perhaps my observations could help to solve this:
What I'm trying to do is to use Awake to prevent sleep mode while doing a backup from a remote server via rsync:
(1) wake up sleeping computer via magic packet/wakeonlan
(2) connect via ssh (Cygwin), start Awake to keep it in this state
(3) run backup (ssh/rsync)
(4) connect via ssh (Cygwin), kill Awake
(5) computer resumes sleeping
I've been using this setup (with DontSleep instead of Awake) for years on various other/older laptops.
However, with my newest laptop this starts to behave "strange":
The above flow still works like a charm when the computer is not yet sleeping in the first place.
BUT: It reproducibly fails when it has just woken up by (1):

Awake is started properly by (2) (ssh to the server running "tasklist" shows it)
Awake in the logs even reports "Initiated indefinite keep awake in background thread..." and no errors
Running "powercfg -requests" (again via ssh) shows Awake is requesting SYSTEM as expected
BUT: The computer still falls back to sleep within a few seconds!

Observations:

When you manually wake up the computer again later (e. g. by keyboard) after the above "failure", Awake is still running and even prevents the computer from falling asleep again!
Having --display-on or not does not make a difference; after the wakeonlan the screen remains black/off.
Using --pid 0 (idle) or 4 (kernel) does not make a difference.
This is the case on both, Windows 11 Pro as well as Windows 10 Pro (both freshly installed, all updated with no other software installed, except Cygwin + PowerToys).
(DontSleep has exactly the same issue; it even requests AWAYMODE...)

What eventually "fixed" it for me was a BIOS setting:
There is a "Sleep State" option in the BIOS, with two settings:

"Windows and Linux" - [for systems] "that at are compatible with Suspend-To-Idle",
("powercfg /availablesleepstates" reports S0 enabled, S1+S2+S3 disabled)
"Linux S3" - [for systems] "that are not compatible with Suspend-To-Idle"
("powercfg /availablesleepstates" report S0 not available, S1+S2 disabled, S3 enabled)

Using the default "Windows and Linux" I see the above behavior, however switching this to "Linux S3" things are working again as expected!
My conclusion: @CRi83 could be pointing in the right direction:
When Windows is (already) in S0 "sleep" mode, it seems to ignores (changes to) SetThreadExecutionState!?
To prevent this, Awake could try to "wake the computer up completely" (whatever that means) before setting SetThreadExecutionState?

Interesting - thank you for the observation and detailed report @abenneke. I am currently investigating if there is a way to do this.

An interesting tidbit in the official docs:

Windows prevents desktop applications from running during any part of modern standby after the DAM phase completes.

Wonder if this has anything to do with observed behavior. It also seems like I need to expand logging to see when the behavior occurs before this can be addressed, and for that I need to get the SYSTEM_POWER_STATE. Just need to figure out which API returns that.

Does not work for me as well.
If I set "Keep screen on" to true, then the display still goes dark after predefined time.
The logs constantly state:
[2022-03-11 20:16:18.3749 INFO Awake.Program] Detected a settings file change. Updating configuration...
[2022-03-11 20:16:18.3749 INFO Awake.Program] Resetting keep-awake to normal state due to settings change.
[2022-03-11 20:16:18.3749 INFO Awake.Program] Operating in passive mode (computer's standard power plan). No custom keep awake settings enabled.

So it seems that it acutally never enables the keep-awake state?
Anything I can do to help debug the issue?

@Morgy93 are you setting a specific mode of operation other than passive after setting the display on? Are you doing this through the tray or the PowerToys settings?

@Morgy93 are you setting a specific mode of operation other than passive after setting the display on? Are you doing this through the tray or the PowerToys settings?
Also - what OS version do you have?

OS: Windows 11 Home 21H2 22000.556
I used the tray icon and only enabled "Keep screen on".
I'll see if it makes a difference if set via PowerToys directly.
PowerToys is not run with administrator privileges.

@Morgy - "Keep Screen On" should only work when you have the active mode selected (either timed or indefinite) and not passive. I'll think through this a bit more from the UX perspective - maybe the option should not be available to keep the display on unless you've selected a compatible mode.

@morgy - "Keep Screen On" should only work when you have the active mode selected (either timed or indefinite) and not passive. I'll think through this a bit more from the UX perspective - maybe the option should not be available to keep the display on unless you've selected a compatible mode.

Yes, that would be great! Shall I open another issue for it?
That makes it clear so that the option is bound to an enabled Awake state.

@Morgy93 yes please - a new issue would be great here.

Glad I found this. So looks like this PowerToy isn't working at all. I tried to keep my Surface Book 3 awake to test something while I was away, but my test failed and apparently because Awake didn't keep the machine awake. The Event log shows that my Surface Book entered connected standby mode regardless. I think this tool doesn't work with modern standby.

So apparently setting "Put the computer to sleep" to "Never" in the regular power options doesn't work, either. It still goes to connected standby. Now I'm wondering if it has something to do with Dynamic lock, which I've configured. According to the System log, it goes to connected standby as soon as I walk away with my phone.

It's possible that I may have just figured out what's going on. I enabled the group policy to allow apps to prevent automatic sleep. By default the policy doesn't allow it. It seems to have worked. YMMV, but at least for the tests I just did my machine stayed awake.

I enabled the group policy to allow apps to prevent automatic sleep. By default the policy doesn't allow it. It seems to have worked.

It seems to have worked for me, too. Thank you!

This seems to have been addressed. That said, @marcelgood @schnodo - I am tagging this item for myself to address in documentation as well, since it's a good way to get tripped up if you don't actually have the GPO set up. Thank you for the feedback!

The ticket's closed but...what about those of us with Home editions of Windows. Any tips?

@padevel if the app is not working for you, please open a new issue with repro steps along with system details 👍

@dend I don't see anything at https://learn.microsoft.com/en-us/windows/powertoys/awake about the group policy setting - is it still expected that we need to do this in order for Awake to work properly?

For anyone else having this issue with Windows 11 Home Edition.
I think I found the issue.
If I go to the Control Panel -> Changed Advanced Power Settings, I can see that I have Sleep set to Never.
However, Hibernate was still set to 15 minutes and sure enough the computer was powering down after fifteen minutes even with Powertoys Awake set to "indefinite".

For anyone else having this issue with Windows 11 Home Edition. I think I found the issue.
If I go to the Control Panel -> Changed Advanced Power Settings, I can see that I have Sleep set to Never. However, Hibernate was still set to 15 minutes and sure enough the computer was powering down after fifteen minutes even with Powertoys Awake set to "indefinite".

Yep; same for me! Changed hibernate settings and finally stayed awake. Thanks for posting @looeee !

Hibernate setting disabled for AC (battery was set to 400000min or so), standby setting disabled for AC, gpedit allow apps to keep awake system in AC enabled, rebooted...
Powertoys Awake set to "indefinite" and enabled.
System still enters Modern Standby when turning off the screen.
Completely preventing standby via firmware option works but is undesired.
Do you want me to create a new issue ticket?

On Windows 11 awake does not work in any way. The question is, why are you releasing a version that doesn't fulfill a basic function? How long have people been writing to you saying it doesn't work? Might want to ask some of the apple developers for help on how to do things. Maybe you should be honest with yourself, not do things you don't understand, and then when you don't know what to do with yourself, please... recruit yourself to Ukraine and hopefully you'll serve better there. You're nobodies in this business. Useless.


Remove voyager.js request (https://s3.amazonaws.com/laravelvoyager/voyager.js)

Laravel Version: 5.5.28
Voyager Version: 1.0.12
PHP Version: 7.1.3
Database Driver & Version: SQLite3 & 3.15.1

Description:

the following message gets outputted to the browser console from a file named voyager.js loaded from https://s3.amazonaws.com/laravelvoyager/voyager.js: Welcome to Voyager 1.0.
Is there any way to remove that request? My Voyager installation runs on a machine without access to the internet and that request results in a net::ERR_NAME_NOT_RESOLVED error.

Steps To Reproduce:

login to your Voyager dashboard and check the console output

Duplicate of https://github.com/the-control-group/voyager/issues/2562

My apologies. Closing now.


add Ch.Types.Decimal, precision: ..., scale: ...

I've added field :dec, Ch, type: "Decimal(18, 6)" instead.
Ref https://github.com/plausible/chto/pull/43


camera doesnt fill entire screen

As many of you have seen before, the camera preview doesn't fill the full screen on my Lumia 950. I'm not sure if it's the same for other phones but it could be due to the qhd? It does it for back and front facing cameras

Thanks for putting in an issue.
We know of this. Ill try to get to this next.

Same here on 950XL

It works fine on 830 with latest version.

I'm using last build uploaded to AppVeyor and camera really doesn't fill full screen

Sounds like it's the soft keys that are the problem

And plz someone plz fix the 90 degree and story problem

Still doesn't fill screen as of build from 5 min.ago

Hm ... WTF? This appears on the latest version of the app, I'm on the latest build on Windows 10 Mobile, L535

@starcorroder It is still 90 degrees offset? What device are you on? I thought I fixed this in issue #15


Wrap error messages in an ErrorMessage type

Implements #446

Nice. I assume this slightly changes the API, and therefore needs to be a 0.1.0 increase in version number?

Indeed, this is a breaking change. Code like let msg: String = sdl2::init().unwrap_err() will break.

Sure. I'll roll a release tomorrow lunch, when I get an opportunity (no access to internet at home at the moment)


ideal_labeler when matching multiple input vectors

make ideal_labeler return a randomly chosen label instead of first label when matching multiple input vectors

Codecov Report

Merging #172 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #172      +/-   ##
==========================================
+ Coverage   89.46%   89.47%   +<.01%
==========================================
  Files          37       37
  Lines        1566     1567       +1
==========================================
+ Hits         1401     1402       +1
  Misses        165      165

Impacted Files
Coverage Δ

libact/labelers/ideal_labeler.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


api: Use serialized signature for execute_transaction endpoint

What
Make sui_executeTransaction API the same as sui_executeTransactionSerializedSig.
This sui_executeTransaction now requires the client is responsible to serialize flag || signature || pubkey in one field and submit as signature. Instead of sending three separate fields previously (scheme, pubkey, signature).
Why
This simplifies future use cases for multisig and multi agent execute transaction.
How to use
In Rust:
let serialized_sig = crypto::Signature::from_bytes(&[&*flag, &*sig_bytes, &*pub_key].concat()).unwrap();

In CLI: See usage of sui keytool sign.
target/debug/sui keytool sign --address 0xb59ce11ef3ad15b6c247dda9890dce1b781f99df --data $DATA_TO_SIGN

Intent message to sign: AAAAAAP986VtisOQSZxhH9M4A24xOaDppQDue7TlY/36sS2HyepBJa2PjB3RkxSAjb+7Pv1voJYk/RjX9AlYZ5+hAgAAAAAAAAAgghpx3ucYetjUIHnaFCho6iaUXnt4hczdAeLlgIw0GqsBAAAAAAAAAOgDAAAAAAAA
Signer address: 0xb59ce11ef3ad15b6c247dda9890dce1b781f99df
Serialized signature (`flag || sig || pk` in Base64): $SERIALIZED_SIG

In Typescript:
      // Serialize signature field as: `flag || sig || pk`
        const serialized_sig = new Uint8Array(
          1 + signature.getLength() + pubkey.toBytes().length
        );
        serialized_sig.set([SIGNATURE_SCHEME_TO_FLAG[signatureScheme]]);
        serialized_sig.set(signature.getData(), 1);
        serialized_sig.set(pubkey.toBytes(), 1 + signature.getLength());

Also fixed some ergonomics and bugs of keytool and offline signing docs.

should we rename sui_executeTransactionSerializedSig to sui_executeTransaction instead?

should we rename sui_executeTransactionSerializedSig to sui_executeTransaction instead?

we should try avoiding renaming APIs since we have to ensure a deployment of wallet does not happen before sui deploy, because the client is calling into the sui_executeTransactionSerializedSig.

should we rename sui_executeTransactionSerializedSig to sui_executeTransaction instead?

renaming API is dangerous here since we have to ensure a deployment of wallet does not happen before sui deploy, because otherwise the current version of wallet calls into the sui_executeTransactionSerializedSig and the endpoint is gone

So I was thinking we change  sui_executeTransaction to do the exactly same thing as sui_executeTransactionSerializedSig and deprecate sui_executeTransactionSerializedSig gradually, because its name is too long.

should we rename sui_executeTransactionSerializedSig to sui_executeTransaction instead?

renaming API is dangerous here since we have to ensure a deployment of wallet does not happen before sui deploy, because otherwise the current version of wallet calls into the sui_executeTransactionSerializedSig and the endpoint is gone

So I was thinking we change sui_executeTransaction to do the exactly same thing as sui_executeTransactionSerializedSig and deprecate sui_executeTransactionSerializedSig gradually, because its name is too long.

i see what you mean,  this works! revised. i will have wallet still points to sui_executeTransactionSerializedSig here and once this change is deployed with sui, we can make wallet to call sui_executeTransaction


create pod network error with kube-flannel-aliyun.yml

Expected Behavior
# kubectl get pods -n kube-system | grep kube-flannel
kube-flannel-ds-amd64-g667t        1/1     Running   1          19h
kube-flannel-ds-amd64-z7zpb        1/1     Running   2          26h

Current Behavior
[root@master k8s]# kubectl apply -f kube-flannel-aliyun.yml
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
error: unable to recognize "flannel.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

Possible Solution
some config may out of date?
Steps to Reproduce (for bugs)
[root@master k8s]# kubectl apply -f kube-flannel-aliyun.yml
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
error: unable to recognize "flannel.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

Your Environment

Flannel version:
Backend used (e.g. vxlan or udp):
Etcd version:
Kubernetes version (if used):

[root@master k8s]# kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

Operating System and version: CentOS 7

[root@master k8s]# uname -a
Linux master 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Link to your project (optional):

Can you use Documentation/kube-flannel.yaml instead? kube-flannel-aliyun is stale and outdated. We will remove it at some point.
A new release of Flannel was recently made. Please use the latest version and report if there are any issues.


Adding task split run option in data file #78

Hello @Slowblitz! Thanks for opening this PR.

In the file ando/rulesStructured.py:

Line 44:101: E501 line too long (130 > 100 characters)
Line 45:5: E123 closing bracket does not match indentation of opening bracket's line

Do see the Hitchhiker's guide to code style

Pull Request Test Coverage Report for Build 722319131

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 40.123%

Totals

Change from base Build 722119932:
0.0%

Covered Lines:
195

Relevant Lines:
486

💛  - Coveralls

I'll try to fix #79 in this PR too


Update Flutter and fix platform projects

This PR aims to fix various build issues that I encountered during development.
What has been done:

added various files to respect what .gitignore says, in order to not have 20+ uncommitted files, whenever a build is triggered
updated flutter to latest stable version

LGTM @mikev-cw i think that could be merged.

Agreed, let's merge!


Airflow Gunicorn service not running || web UI inaccessible

Airflow version: 1.8.0
Gunicorn version: 19.3.0
Python version: 2.7
When: We restarted the server where airflow service was running
What happened: Everything is working fine but airflow Gunicorn service is not running due to the web server UI is not accessible.
Web server log: Whenever we start the webserver its getting stuck :
airflow webserver
[2021-12-22 18:26:15,403] {init.py:57} INFO - Using executor LocalExecutor
[2021-12-22 18:26:15,477] {driver.py:120} INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
[2021-12-22 18:26:15,509] {driver.py:120} INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt

____    |( )_______  /  /________      __
____  /| |_  /__  /  / __  /  __ _ | /| / /
___  ___ |  / _  /   _  / _  / / // / |/ |/ /
//  |//  //    //    //  _/____/|__/
/usr/local/lib/python2.7/dist-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.cache is deprecated, use flask_cache instead.
.format(x=modname), ExtDeprecationWarning
[2021-12-22 18:26:15,906] [9263] {models.py:167} INFO - Filling up the DagBag from /usr/local/lib/airflow/dags
/usr/local/lib/python2.7/dist-packages/airflow/utils/helpers.py:406: DeprecationWarning: Importing SSHHook directly from <module 'airflow.contrib.hooks' from '/usr/local/lib/python2.7/dist-packages/airflow/contrib/hooks/init.pyc'> has been deprecated. Please import from '<module 'airflow.contrib.hooks' from '/usr/local/lib/python2.7/dist-packages/airflow/contrib/hooks/init.pyc'>.[operator_module]' instead. Support for direct imports will be dropped entirely in Airflow 2.0.
DeprecationWarning)
[2021-12-22 18:26:17,439] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): sync_dag>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name trust_ride_ano_in_1 --executor-memory 4g --queue trust --num-executors 5 --master yarn --driver-memory 10G --py-files /home/suvratjain/RideAnomalyDetection.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/suvratjain/RideAnomalyDetection/raw_data.py --country IN --s3_path s3a://s3-emr-test-stg/fraud/ride_level_anomaly/raw_feature/IN/{{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
/usr/local/lib/python2.7/dist-packages/airflow/models.py:1927: PendingDeprecationWarning: Invalid arguments were passed to BashOperator. Support for passing such arguments will be dropped in Airflow 2.0. Invalid arguments were:
*args: ()
**kwargs: {'provide_context': True}
category=PendingDeprecationWarning
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name trust_ride_ano_gb_1 --executor-memory 4g --queue trust --num-executors 5 --master yarn --driver-memory 10G --py-files /home/suvratjain/RideAnomalyDetection.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/suvratjain/RideAnomalyDetection/raw_data.py --country GB --s3_path s3a://s3-emr-test-stg/fraud/ride_level_anomaly/raw_feature/GB/{{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name partner_ano_in_1 --executor-memory 10g --queue trust --num-executors 20 --master yarn --driver-memory 20G --py-files /home/suvratjain/PartnerAnomalyDetection.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/suvratjain/PartnerAnomalyDetection/main.py --country IN --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name customer_ride_ano_in_1 --executor-memory 5G --queue trust --num-executors 20 --master yarn --driver-memory 5G --py-files s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/CustomerAnomalyDetection/CustomerAnomalyDetection.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/CustomerAnomalyDetection/CustomerRideFeatureCollection.py --country IN --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name customer_ride_ano_gb_1 --executor-memory 5G --queue trust --num-executors 20 --master yarn --driver-memory 5G --py-files s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/CustomerAnomalyDetection/CustomerAnomalyDetection.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/CustomerAnomalyDetection/CustomerRideFeatureCollection.py --country GB --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name outstation_partner_ds_in_1 --executor-memory 20g --queue trust --num-executors 10 --master yarn --driver-memory 20G --py-files /home/souritmanna/Trust/gitlab_repo/anomaly-detection/outstation_anomaly_detection/partner_anomaly/OutstationPartnerAnomaly.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/souritmanna/Trust/gitlab_repo/anomaly-detection/outstation_anomaly_detection/partner_anomaly/data_fetching.py --country IN --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --output_s3_path s3a://s3-emr-test-stg/fraud/outstation_partner_level_anomaly/
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name auto_ride_ds_in --executor-memory 10g --queue trust --num-executors 10 --master yarn --driver-memory 20G --py-files /home/suvratjain/AutoRideAnomaly.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/suvratjain/AutoRideAnomaly/raw_data.py --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --country IN --s3_path s3a://s3-emr-test-stg/fraud/auto_ride_level_anomaly/raw_feature/IN/{{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}/
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name customer_non_ride_ano_au_1 --executor-memory 5G --queue trust --num-executors 20 --master yarn --driver-memory 5G --py-files /home/suvratjain/CustomerNonRideAnomaly.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true /home/suvratjain/CustomerNonRideAnomaly/CustomerNonRideDataFetch.py --country AU --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --s3_path s3a://s3-emr-test-stg/fraud/customer_non_ride_anomaly/raw_feature/AU/{{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
echoq spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name trust_ride_ano_gb_1 --executor-memory 4g --queue trust --num-executors 5 --master yarn --driver-memory 10G --py-files s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/RideAnomalyDetection/RideFeatureCode.zip --conf spark.ui.showConsoleProgress=true --conf spark.driver.maxResultSize=6g --conf spark.files.overwrite=true s3a://s3-emr-test-stg/fraud/datascience/anomaly-detection/RideAnomalyDetection/raw_data.py --country GB --s3_path s3a://s3-emr-test-stg/fraud/ride_level_anomaly/raw_feature/GB/{{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }} --day_t {{ task_instance.xcom_pull(key="for_date", task_ids='set_for_date') }}
spark-submit --files /etc/spark2/conf/hive-site.xml --deploy-mode cluster --name partner_ano_au_1 --executor-memory 10g --
[2021-12-22 18:26:32,333] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): Bind_To_Favourites>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,334] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): Generate_RocksDB>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,344] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(SparkRemoteOperator):
[2021-12-22 18:26:32,426] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(MarathonOperator): data_processor_bangalore>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,427] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(S3KeySensor): data_processor_city_BANGALORE_output_sensor>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,429] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(MarathonOperator): data_processor_bangalore_kill>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,430] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(MarathonOperator): data_processor_delhi>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,431] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(S3KeySensor): data_processor_city_DELHI_output_sensor>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,433] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(MarathonOperator): data_processor_delhi_kill>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,434] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(MarathonOperator): data_processor_mumbai>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:32,435] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(S3KeySensor): data_processor_city_MUMBAI_output_sensor>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:34,949] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): ahemadabad_UnscheduledStopFinalModel>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:34,950] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(DummyOperator): lucknow_dag_start>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:34,951] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): lucknow_AbandonedZoneScoreFinalModel>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:34,952] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): lucknow_RouteDeivationFinalModel>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
[2021-12-22 18:26:34,953] [9263] {models.py:1958} WARNING - schedule_interval is used for <Task(BashOperator): lucknow_UnscheduledStopFinalModel>, though it has been deprecated as a task parameter, you need to specify it as a DAG parameter instead
/usr/local/lib/python2.7/dist-packages/airflow/models.py:1927: PendingDeprecationWarning: Invalid arguments were passed to SparkSubmitOperator. Support for passing such arguments will be dropped in Airflow 2.0. Invalid arguments were:
*args: ()
**kwargs: {'driver_memory': '2g', 'application_args': ['staging', '2021-12-22'], 'java_class': 'com.ola.fs.preauth.exps.Exps1'}
category=PendingDeprecationWarning
No response after this line.
Now when tried to start gunicorn getting App not found error:
root@airflow1:/usr/local/lib/python2.7/dist-packages/airflow# gunicorn -b <IP_ADDRESS>:8080 airflow
[2021-12-22 21:11:03 +0000] [21851] [INFO] Starting gunicorn 19.3.0
[2021-12-22 21:11:03 +0000] [21851] [INFO] Listening at: http://<IP_ADDRESS>:8080 (21851)
[2021-12-22 21:11:03 +0000] [21851] [INFO] Using worker: sync
[2021-12-22 21:11:03 +0000] [21856] [INFO] Booting worker with pid: 21856
[2021-12-22 21:11:03,753] {init.py:57} INFO - Using executor LocalExecutor
[2021-12-22 21:11:03,840] {driver.py:120} INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
[2021-12-22 21:11:03,860] {driver.py:120} INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
Failed to find application: 'airflow'
[2021-12-22 21:11:03 +0000] [21856] [INFO] Worker exiting (pid: 21856)
[2021-12-22 21:11:03 +0000] [21851] [INFO] Shutting down: Master
[2021-12-22 21:11:03 +0000] [21851] [INFO] Reason: App failed to load.
root@airflow1:/usr/local/lib/python2.7/dist-packages/airflow#
Please help me to fix this issue ASAP.

Hi, @Vivekdjango!
I suggest looking in https://docs.gunicorn.org/en/stable/ or https://airflow.apache.org/docs/apache-airflow/stable/, and checking with those communities.
This repo is the former home of helm charts which are now found at Artifact Hub. Project support is not available in this repo. Thanks!

Oh, and one more thing - if this question is indeed related to a Helm chart, then you may find the info you're looking for in https://github.com/airflow-helm/charts/. Best!


Request review for 3 patches.

poll event handling issue and fix.
re-alloc patch @k_mem_pool_alloc().
Workqueue issue and fix.

outdated, closing. Reopen with updates/rebase if needed.


Problems with Stronghold backup compatibility

Bug description
I am unable to restore from an older Stronghold backup (exported from Firefly V1 with older wallet.rs bindings) using the latest Stardust changes for Firefly, which uses the latest NodeJS bindings from wallet.rs. The crux is that 1) I can successfully import a Stronghold backup that was created with the new bindings and 2) I can successfully import the old Stronghold backup in Firefly V1, so I concluded that there may be a lower-level problem.
Rust version
Which version of Rust are you running?
N/a
Version
Which version of the library are you using?
develop
Hardware specification
What hardware are you using?

Operating system: Ubuntu 22.04
RAM: 32GB
Cores: 8
Device: Framework Laptop

Steps To reproduce the bug
Explain how the maintainer can reproduce the bug.

Use old and new Strongholds with NodeJS bindings

Expected behaviour
Successfully import both old and new Stronghold backup files.
Actual behaviour
I cannot import old Stronghold backups. With the same logic and process for both, I guess this error when importing the old one:
{type: "ClientError", error: "`no password has been supplied, or the key has been cleared from the memory`"}

Errors
{type: "ClientError", error: "`no password has been supplied, or the key has been cleared from the memory`"}

Can't reproduce this error
firefly-v1-backup.zip
const { AccountManager, CoinType } = require('@iota/wallet');

async function run() {
    try {
        const accountManagerOptions = {
            storagePath: './alice-database',
            clientOptions: {
                nodes: ['https://api.testnet.shimmer.network'],
                localPow: true,
            },
            coinType: CoinType.Shimmer,
            secretManager: {
                Stronghold: {
                    snapshotPath: `./firefly-v1-backup.stronghold`,
                    password: "some_hopefully_secure_password",
                },
            },
        };

        const manager = new AccountManager(accountManagerOptions);

        const account = await manager.createAccount({
            alias: 'Alice',
        });
        console.log('Account created:', account);

        const secondAccount = await manager.createAccount({
            alias: 'Bob',
        });
        console.log('Account created:', secondAccount);
    } catch (error) {
        console.log('Error: ', error);
    }
}

run();

works fine


Setting $gutter has no effect.

My code is organised as follows (in case this might be a bug in how I'm setting it, or the ordering of files or something):
main.scss

imports 'settings.scss'
imports 'grid.scss'

In settings, I set $gutter like this: $gutter: 1em !global;
In grid I have a basic two column grid set up:
.container {
  @include outer-container();
}
.column {
  @include span-columns(6);
  @include omega(2n);
}

If my understanding of how $gutter works is correct, when altering the value the space between these two columns should change too. But in my setup as above, it has no effect. Disclaimer: I can't find anyone else reporting this issue, so it's very possible it's not a bug in Neat.

My bad, it has to be set before importing neat. Whoops!


tutorial Simon Foster used to create tree assets

Simon Foster apparently spends the time to look at his youtube comments and post meaningful replies. I was reading a reply chain and found this link that he posted, which he said was the method used to create the trees RCT1 and RCT2:
http://www.animationartist.com/2000/Tutorials/LWTrees/lwtrees.html

So … What's your bug report / feature request then?

The original website seems to have been taken down, so I saved I copy of the site archived by the Wayback Machine. Available upon request.


Separate withTheme from Button component

Separated withTheme from Button component.
Deleted ThemeProvider and unnecessary options from stories.
Updated test.
No more changes

@darkwindcz Should <Button /> render  like in <ButtonLink /> ?

@tomashapl yes,  both <Button /> and <ButtonLink /> should be able to render a or button.
In my opinion, when developer use prop href, it should render button. I am not sure if it's needed to be able to tell component what type it should render manually.

@darkwindcz Thanks.
@wEprous Can you handle this ? It should be the same like in ButtonLink component i think.

@tomashapl Yeah, sure :)

@wEprous
You forgot delete old code from Button/index.js right ? please check your code before pushing it to review. 🙏


Refactor all utests to use Theory and MemberData

This should make it easier to maintain the tests as new .NET Core versions are released and support is dropped for older versions.

LGTM. Feel free to merge. I'll rebase with these changes in my PR for ARM tests.

FYI...the CI failure is unrelated to these changes.


tour: Page "range" is not clear

Context: /moretypes/12
There was insufficient information on the page for "range" to explain the associated code. Having not read the documentation for range I was not aware that i and v are both values returned by the range function - representing the index and value of each element of pow - and it took me a while to come to that realisation. I did not immediately realise that i and v were separated by a  comma as opposed to the semicolon I expected to see. This could be made clearer with a more verbose description.

What about the next slide?

Well I generally don't move on to a subsequent slide until I've understood the current slide. That said, the next slide doesn't add much to my understanding. Both of these slides assume too much of the reader; given that it's a "Tour" it should assume nothing. The content from the Wiki (https://github.com/golang/go/wiki/Range) should be included here.

I'll take this one.


a.bg and Config.ini not found exception

Hello, I have some problems,  run CrazyStorm Player Project, throw Filenotfound exception , The code is FileStream stream = new FileStream("a.bg", FileMode.Open), and run CrazyStorm 2.0 throw the same Excetion, Config.ini is not exist， Can you tell me how to solve, 3Q

CrazyStorm Player is unfinished yet so you can't run it right now.
"Config.ini" has been added to the project, you can check it out.


source: Error while reading file '-'

regardless of the test, even if it's empty, the pond seems to be leaky and the tape doesnt stick:
$ fish -v
fish, version 2.3b2-159-g432c005

$ fishtape -v
fishtape v1.0.0

$ fishtape test/*.fish
'end' outside of a block
- (line 9): end
            ^
from sourcing file -
    called on standard input

source: Error while reading file '-'

Can I see the full source code?

how to reproduce: have a non existing or empty test. run fishtape on it.

Yeah, observed. See my edit above.

Closing in favor or #21.


Safe mode must disallow attributes like "onload", "onclick"

Possibly by disabling attributes altogether (like enable_attributes=False), or by applying a filter. There is a fairly comprehensive list at http://ha.ckers.org/xss.html#XSS_Event_handlers
This is the mode that people are expected to use when rendering user input. This has to be the default, especially since most people don't know about or use this attribute syntax in the first place. The output must be actually guaranteed safe, not just partly safe. This vulnerability is just as dangerous as javascript: links.
{@onclick=alert('hi')}some paragraph

In fact, all Django sites that user markdown current have this vulnerability, because the markdown template filter does not pass enable_attributes=False when called with 'safe'.

As we have documented:

Note that "safe_mode" does not alter the enable_attributes option, which
could allow someone to inject javascript (i.e., {@onclick=alert(1)}). You
may also want to set enable_attributes=False when using "safe_mode".

Unfortunately, this is an issue of poor naming. Perhaps it should have been called "raw_html" rather than "safe_mode". However, we have left it for historical (backward compatible) reasons. Too many other libraries and projects expect the current name so we leave it.
The fact is, with our extension API, we have no way of ensuring that any third party extensions are "safe" either. If you really want something that is "safe", then I suggestion a third party post-processor which completely sanitizes markdown's output. Perhaps something like bleach.
I should also note that this request is for a blacklist that blocks "attributes like 'onload', onclick'." Whereas solutions like bleach implement a whitelist. Whitelists block everything that is not known to be safe, which is a much safer approach. If markdown was to continue on this blacklist approach, we would constantly be chasing new "unsafe" input. For that reason, we will not be implementing the suggested solution. As existing solutions already exist, I'm closing this wontfix.

You are right that a blacklist is never the right answer. I meant a filter of non-whitelisted attributes, and only providedthe blacklist for reference.
It's not an issue of poor naming. The "safe" mode does more than just not interpret "raw_html", like filtering javascript: links. It should do as it says and make the output safe.
I understand that backwards compatibility is an issue, but security is even more important. Security should always be the default, not an extra option like enable_attributes. I suspect that many, many sites using markdown have this vulnerability. Not fixing it would be simply irresponsible.


cmd/compile: ExampleInfo output not being checked

What version of Go are you using (go version)?

$ go version go1.17 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/adowns/Library/Caches/go-build"
GOENV="/Users/adowns/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/adowns/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/adowns/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/adowns/workspace/text/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4c/1b3s36l94blb6xg1_4p_13800000gn/T/go-build2465748359=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Ran a parser looking for instances of this issue where there are any comment blocks after "output" comment blocks. This makes the test pass regardless of what is in the output comment block.
What did you expect to see?
No examples of this issue.
What did you see instead?
Found that ExampleInfo has a "TODO" comment after the "output" comment.

Thanks for working on this, I only added the label to get it off the automated triage pile.


IE 7 issue with custom dropdowns

I've noticed this issue only in ie 7 but apparently the js that creates the dropdowns ignores any css rules applied to it but heres a photo of the issue.
http://screensnapr.com/v/dIgblu.png
and the big issue
http://screensnapr.com/v/1Ljcze.png
i understand the background is a rbga which ie7 doesnt support but when i attempt to overwrite that rule in the sheet for ie it completely ignores it.

Can you provide a link, or maybe just the CSS you're trying to modify? Hard to tell from the pic what exactly the issue might be. Thanks.


About the definition of snake-case and upper-snake-case

This might be more of a question than an issue.
It was encountered that when using the namestyle upper-snake-case, a variable name like CONSTANT_VALUE_1 does cause a namestyle violation, but CONSTANT_VALUE1 doesn't.
There are arguments for both variants to be the "correct" snake-case, so I mainly want to ask:
Is your understanding of snake_case and upper_snake_case that numerical components have to be prefixed with letters, or could it be adapted in the implementations of snake_case and upper_snake_case themselves?
Of course, there's always the options to implement any custom namestyle variant with a regular expression, but if there are predefined styles, the configuration ends up simpler.

Actually, I always use camelCase or PascalCase styles for my code. Naming style checks are just something I did on the side because there were no plugins involved in Lua. In my earliest version, it only allowed numbers to appear at the end of identifiers. After looking at a lot of code, I realized this wasn't adequate, so I changed the way the checks were done. The issue with snake_case was simply because at that time, I didn't deal with the underscore followed by a number. Actually, I haven't read any specific naming conventions, I just rely on my intuition.


compile_ios_tensorflow.sh failing

Hi there
I'm following the instructions on your website to build a version of tensor flow for iOS:
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/makefile
Unfortunately when I get to final step:
tensorflow/contrib/makefile/compile_ios_tensorflow.sh
It errors with:
/Projects/ML/tensorflow/tensorflow/contrib/makefile/gen/lib/libtensorflow-core-armv7.a -arch armv7 -miphoneos-version-min=9.2 -Xlinker -S -Xlinker -x -Xlinker -dead_strip -all_load -L/Projects/ML/tensorflow/tensorflow/contrib/makefile/gen/protobuf_ios/lib -lz -lstdc++ -lprotobuf -lm
Undefined symbols for architecture armv7:
"tensorflow::shape_inference::InferenceContext::Merge(tensorflow::shape_inference::Shape const*, tensorflow::shape_inference::Shape const*, tensorflow::shape_inference::Shape const**)", referenced from:
tensorflow::$_0::operator()(tensorflow::shape_inference::InferenceContext*) const in libtensorflow-core-armv7.a(math_ops.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Projects/ML/tensorflow/tensorflow/contrib/makefile/gen/bin/benchmark] Error 1

'[' 2 -ne 0 ']'
echo 'armv7 compilation failed.'
armv7 compilation failed.
exit 1

That problem is caused by the out-of-date tf_cc_files.txt file that is in the repo. That version doesn't include newer files such as shape_inference.cc, the source of the missing symbols in your error.
If you run ./gen_file_lists.sh from tensorflow/contrib/makefile it will generate a new tf_cc_files.txt for you. Then run the compile script again and see if it works.
Note that you have to remove "make/" from lines 26, 32, 38, 46, 52, and 58 in gen_file_list.sh in order to make the script put the files into the same directory as the Makefile. I forgot to raise this an issue when I found it.

Piggybacking on this issue (let me know if it's better suited as a separate one). I changed gen_file_list.sh, ran it and then attempted building again, now I'm instead getting the following:
Undefined symbols for architecture x86_64:
  "_deflate", referenced from:
      tensorflow::io::ZlibOutputBuffer::Deflate(int) in zlib_outputbuffer.o
  "_deflateEnd", referenced from:
      tensorflow::io::ZlibOutputBuffer::Close() in zlib_outputbuffer.o
  "_deflateInit2_", referenced from:
      tensorflow::io::ZlibOutputBuffer::ZlibOutputBuffer(tensorflow::WritableFile*, int, int, tensorflow::io::ZlibCompressionOptions const&) in zlib_outputbuffer.o
  "_inflate", referenced from:
      tensorflow::io::ZlibInputBuffer::Inflate() in zlib_inputbuffer.o
  "_inflateEnd", referenced from:
      tensorflow::io::ZlibInputBuffer::~ZlibInputBuffer() in zlib_inputbuffer.o
  "_inflateInit2_", referenced from:
      tensorflow::io::ZlibInputBuffer::ZlibInputBuffer(tensorflow::RandomAccessFile*, unsigned long, unsigned long, tensorflow::io::ZlibCompressionOptions const&) in zlib_inputbuffer.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Users/albhaf/src/github.com/tensorflow/tensorflow/tensorflow/contrib/makefile/gen/host_bin/proto_text] Error 1
+ '[' 2 -ne 0 ']'
+ echo 'armv7 compilation failed.'
armv7 compilation failed.
+ exit 1

@albhaf That looks like a different problem.
I had a quick look and I think that it's being caused by support being added in the main tensorflow build for reading compressed files. The download dependencies script in the makefile directory is now out of date, along with the Makefile.
A quick work-around should be to remove the two zlib references from your generated tf_cc_files.txt. I haven't checked that yet, but the iOS Camera Demo doesn't use zlib so it might be ok.

Apologies about the breakage! I'm working to make the update a bit less of a manual process.
I'll investigate how we can avoid the new zlib dependency (since we don't want additional libraries to link in), and hopefully have an answer soon.

Thanks everyone! I've tested this again and it should be fixed in #2936, so I'll close this. Comment or reopen if you're still hitting problems.

Thanks! Managed to successfully build with 582e6c8.
Recent changes in master (I suspect 7764e8f6 from a brief look), appears to have caused it to regress again if it's of any interest:
Undefined symbols for architecture x86_64:
  "tensorflow::PosixFileSystem::NewWritableFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, tensorflow::WritableFile**)", referenced from:
      vtable for tensorflow::LocalPosixFileSystem in env.o
  "tensorflow::PosixFileSystem::NewAppendableFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, tensorflow::WritableFile**)", referenced from:
      vtable for tensorflow::LocalPosixFileSystem in env.o
  "tensorflow::PosixFileSystem::NewRandomAccessFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, tensorflow::RandomAccessFile**)", referenced from:
      vtable for tensorflow::LocalPosixFileSystem in env.o
  "tensorflow::PosixFileSystem::NewReadOnlyMemoryRegionFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, tensorflow::ReadOnlyMemoryRegion**)", referenced from:
      vtable for tensorflow::LocalPosixFileSystem in env.o

Shoot, probably my fault, I'll send a fix.

I'm actually looking at it now too. It builds fine using the makefile on Linux, so it's not just a new file added. I'm running build_all_ios.sh to repro the problem, and I'll update with more details when I have them.

Actually, I can't find any reference to those symbols -- my change removed the old APIs and converted to the new ones, so I'm not sure why we're seeing that.

Checking if I can reproduce it and making sure it's on a clean state, in case it was in an inconsistent one from jumping between refs.

It seemed like it was, I must have missed to clean in between checkouts.
I can build it from master now, sorry for the noise.

Great to hear, and no worries! Thanks for the update and the report.

Am I doing it right? I want to run ios examples and trying to compile lib in this way:


How to ignore a file from rendering as a page

How do I ignore or hide a file from turning into page? I'd like import partial mdx files but not have them turn into a page.
I have a page structure that looks like
.
└── pages/
    └── installation/
        ├── javascript.mdx
        ├── _nodejs.mdx
        ├── _browser.mdx
        ├── java.mdx
        ├── _android.mdx
        └── _spring.mdx

Anything that begins with _****.mdx should not be rendered as a page. However, I'd still like to import them.
For example, in javascript.mdx, I'd like to import ./_nodejs.mdx and _./browser.mdx as a component as an include:
import Browser from "_browser.mdx"
import NodeJS from "_nodejs.mdx"

# Installation

Here's how to install our package in the Browser

<Browser />

Here's how to install our package in NodejS

<NodeJS />

However, it seems these _ mdx files still become pages and I am not sure how to disable them:

Is it possible to configure Nextra to ignore any files that begin with _ or some other pattern from rendering into a page?
Thank you community, for an awesome easy-to-use package.
Here are my package dependencies if it helps:
"dependencies": {
    "next": "^13.4.9",
    "nextra": "latest",
    "nextra-theme-docs": "latest",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    "@types/node": "18.11.10",
    "typescript": "^4.9.3"
  }

I've achieved the same result by moving the .mdx file to transclude outside of the pages directory. e.g. in components

You can do it only by moving outside of pages directory as said @keaganaut

I am currently experiencing this issue with buffer files created by emacs (format .#page in the same dir as the file being edited). I can't seem to figure out how to tell next/nextra to ignore these files, which end up breaking the server and its hot loading capabilities any time I edit a page. Unfortunately for these I can't move them out of the directory (afaik).
><EMAIL_ADDRESS>dev /Users/x/docs
> next dev

   automatically enabled Fast Refresh for 3 custom loaders
  ▲ Next.js 13.5.3
  - Local:        http://localhost:3000

 ✓ Ready in 2.2s
 ⨯ [Error: ENOENT: no such file or directory, stat '/Users/x/docs/pages/.#page.mdx'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/Users/x/docs/pages/.#page.mdx'
}


Cannot reload udev rules

I configured the udev rules to the /etc/udev/rules.d folder to allow non-root users to access the device. When I run sudo udevadm control --reload to update the rules, I get an error that "Failed to send reload request: No such file or directory".
# reload rules
> sudo udevadm control --reload
Failed to send reload request: No such file or directory

What should I do to reload the rules?

https://github.com/microsoft/WSL/issues/8502#issuecomment-1153301518
if you get Failed to send reload request: No such file or directory that means your udev service is not running. Check with sudo service udev status before reloading, and if not running start it with sudo service udev start.

Seems to work now.

microsoft/WSL#8502 (comment)
if you get Failed to send reload request: No such file or directory that means your udev service is not running. Check with sudo service udev status before reloading, and if not running start it with sudo service udev start.

This does not apply to Arch Linux.


[Bug] Model runs into an error when no record exists in fivetran_formula_model

Is there an existing issue for this?

[x] I have searched the existing issues

Describe the issue
When an object has no formula then no record exists under fivetran_formula_model and that causes the model to fail.
For instance, in my environment, there is no formulas for case_opportunity. If I include the below statement in my SQL model

{% set sf_object_name = 'case_milestone' %}
{{ config({ 'alias': sf_object_name}) }}
{{ salesforce_formula_utils.sfdc_formula_view(source_table=sf_object_name, materialization='table',  full_statement_version=true) }}

Then I'm getting the below error

16:25:15  1 of 1 START sql table model julien_dbt_fivetranlog.case_milestone ............. [RUN]
16:25:18  BigQuery adapter: https://console.cloud.google.com/bigquery?project=fivetran-wild-west&j=bq:US:afdb7919-2106-4f9d-831a-5dab7d7b66e2&page=queryresults
16:25:18  1 of 1 ERROR creating sql table model julien_dbt_fivetranlog.case_milestone .... [ERROR in 3.22s]
16:25:18
16:25:18  Finished running 1 table model in 0 hours 0 minutes and 6.26 seconds (6.26s).
16:25:18
16:25:18  Completed with 1 error and 0 warnings:
16:25:18
16:25:18  Database Error in model salesforce_test (models/salesforce_test.sql)
16:25:18    Syntax error: Expected "(" or keyword SELECT or keyword WITH but got ")" at [28:5]
16:25:18    compiled Code at target/run/dbt_wildwest_fivetranlog/models/salesforce_test.sql

When I check the compiled model, I can see that the statement is indeed empty

create or replace table fivetran-wild-west.julien_dbt_fivetranlog.case_milestone
OPTIONS()
as (
-- Best practice for this model is to be materialized as view. That is why we have set that here.
/*
The below sets the old_formula_fields variable to the results of the get_column_values results which queries the field column from the fivetran_formula table.
The logic here is that the variable will be a list of all current salesforce formula field names. This list is then used within the dbt_utils.star operation to exclude them.
This allows users with the Fivetran legacy Salesforce fields to ignore them and be replaced by the new fields.
*/
);

A solution could be to remove that model but the customer would like to make sure any new formula is picked up by this DBT transformation so this is not an acceptable solution
Relevant error log or model output
See above

Expected behavior
Create an empty table or other approach. At least, remove the error
dbt Project configurations
name: 'dbt_wildwest_fivetranlog'
version: '1.0.0'
config-version: 2

profile: 'dbt_wildwest_fivetranlog'

model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"
clean-targets:
  - "target"
  - "dbt_packages"

vars:
    fivetran_log_database: fivetran-wild-west
    fivetran_log_schema: julien_fivetran_log_live

    salesforce_schema: julien_salesforce_sandbox

Package versions
packages:
  - package: fivetran/salesforce_formula_utils
    version: 0.7.2

What database are you using dbt with?
snowflake, bigquery
dbt Version
1.3.0
Additional Context
This issue has been raised by LeasePlan. They have raised a few issues while moving from V1 to V2 and although many seem to be related to Salesforce Data Quality issue, it would really help them get passed this issue.
I haven't done so yet, but in the meantime, we will look into adding a IF statement around the salesforce_formula_utils.sfdc_formula_view function to check the existence of a model first
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

HI @fivetran-juliengoulley thanks for opening this issue. I actually just chatted with our product team and discovered that this is something which will be addressed within the connector. As such, this is likely something we won't reflect within the dbt package.
Therefore, I will mark this as won't do and will close out this issue once the update is rolled out to the connector.

I have experienced the same issue, can you please advise when this issue will be fixed by the connector update?
I have to update to below to make sure the code works
{{ salesforce_formula_utils.sfdc_formula_view(     source_name = 'salesforce',     source_table='account_history',     full_statement_version=false     ) }}

HI @fivetran-juliengoulley thanks for opening this issue. I actually just chatted with our product team and discovered that this is something which will be addressed within the connector. As such, this is likely something we won't reflect within the dbt package.
Therefore, I will mark this as won't do and will close out this issue once the update is rolled out to the connector.

Experiencing the same with the latest versions of dbt and this package.
In which way will be addressed? Wouldn't the macro still try to fetch the formula from fivetran_formula_model, are you going to have a "dummy" formula there?

It would probably be better to just raise an error if there's no formula model, wouldn't it?


Avoid transpiling class-properties as they are natively supported

This PR is incomplete -- current status: babel problem
goal:  make babel do less:
tested at: https://github.com/NullVoxPopuli/babel-transpilation-tests
current problem: (all in babel, not ember-cli-babel) decorator plugin assumes class-properties plugin is needed (it's not)
This is not intended to be merged, but serves as something for folks to point their package.jsons at when they want to see if they can disable class-property transpilation across their whole app and addons.
hopefully: class property transformation is not required for decorators .
(it used to be required tho).
There is an assertion / error that's added by the decorators plugin tho.
Upon manual removal in the above demo everything still works fine.
Here is the the test:
input
function f(target, key, desc) {
  let oldGet = desc.get
  let oldInit = desc.initializer

  desc.get =() => {
    console.log('called f on ', key);
    return oldInit?.() || oldGet();
  }
}
class A {
  #a = 'hi';

  get #b() {
    return 'hello' + this.#a;
  }

  get c() { return this.#b; }

  @f g;

  @f h = 2;

  i = 3;
}

let a = new A();

console.log({ g: f.g, c: a.c, h: a.h, i: a.i });

output
remove lines which define g and h
"use strict";

var _class, _descriptor, _descriptor2;

function _applyDecoratedDescriptor(target, property, decorators, descriptor, context) { var desc = {}; Object.keys(descriptor).forEach(function (key) { desc[key] = descriptor[key]; }); desc.enumerable = !!desc.enumerable; desc.configurable = !!desc.configurable; if ('value' in desc || desc.initializer) { desc.writable = true; } desc = decorators.slice().reverse().reduce(function (desc, decorator) { return decorator(target, property, desc) || desc; }, desc); if (context && desc.initializer !== void 0) { desc.value = desc.initializer ? desc.initializer.call(context) : void 0; desc.initializer = undefined; } if (desc.initializer === void 0) { Object.defineProperty(target, property, desc); desc = null; } return desc; }

function _initializerWarningHelper(descriptor, context) { throw new Error('Decorating class property failed. Please ensure that ' + 'proposal-class-properties is enabled and runs after the decorators transform.'); }

function f(target, key, desc) {
  let oldGet = desc.get;
  let oldInit = desc.initializer;

  desc.get = () => {
    console.log('called f on ', key);
    return oldInit?.() || oldGet();
  };
}

let A = (_class = class A {
  #a = 'hi';

  get #b() {
    return 'hello' + this.#a;
  }

  get c() {
    return this.#b;
  }

  g = _initializerWarningHelper(_descriptor, this);
  h = _initializerWarningHelper(_descriptor2, this);
  i = 3;
}, (_descriptor = _applyDecoratedDescriptor(_class.prototype, "g", [f], {
  configurable: true,
  enumerable: true,
  writable: true,
  initializer: null
}), _descriptor2 = _applyDecoratedDescriptor(_class.prototype, "h", [f], {
  configurable: true,
  enumerable: true,
  writable: true,
  initializer: function () {
    return 2;
  }
})), _class);
let a = new A();
console.log({
  g: f.g,
  c: a.c,
  h: a.h,
  i: a.i
});

the goal of this effort is the following:

to reduce the amount of work babel is doing
to use one babel / ember-cli-babel instance for the whole app tree (the complexity brought by addons compliing themselves with their own ember-cli-babel has been problematic for app-land control).

To do this, a consuming app must have only one ember-cli-babel instance in the whole node_modules graph.
Related issues:

https://github.com/babel/ember-cli-babel/issues/447
https://github.com/babel/ember-cli-babel/issues/446
https://github.com/babel/ember-cli-babel/issues/417
https://github.com/babel/ember-cli-babel/issues/447

This won't be possible. best place we can spend effort is moving to platform-decorators


[Feature Request] Hi-Power / Eco modes

Hi. I like to use eco mode at night and occasionally Hi power modes during the day.

there is no known way yet to send these codes to the unit through the SPI bus. see https://github.com/absalom-muc/MHI-AC-Ctrl/issues/126 for more information. Within your home automation it might be possible to achieve the same result. if it is discovered to be possible through the SPI, you are welcome to reopen the request


Updated sensitivity analysis parameters in the usage doc.

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   65.57%   65.57%
=======================================
  Files          12       12
  Lines        1191     1191
  Branches      298      298
=======================================
  Hits          781      781
  Misses        303      303
  Partials      107      107

Continue to review full report at Codecov.

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

👍


fix(measure): measure line should be absolutely positioned

Measure lines should be drawn on the mean ellipsoid surface since that is where the calculation is occurring. If we want the line clamped to terrain then we will need to pull the highest quality meshes that intersect the line, clamp the line, and calculate distance from that.

This accurately depicts what is being measured, but the user interaction in 3D with terrain is not ideal. The mouse cursor is almost always disjoint from the line being drawn. Should 3D/terrain measurements switch to straight line distance and use the exact coordinate at each mouse event?

That's possible but we'll need to update the measurement as the terrain is loaded and each vertex is moved due to clampToGround.


Log Where The TSServer is Logging to When it Exits Or Starts

Request
When the TSServer has logging enabled, we should print the log file location into the vscode output console at start and when the server exits. This will help users collect logs when something goes wrong

This will be in the next insiders build


Which tab is active -- not clear

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.476]
Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.5.2762.0

Steps to reproduce
open multiple tabs in terminal. The switch tab between them
Expected behavior
I can see which tab is active clearly.
Actual behavior  -- Could we use a very different color to identify the active tab ?
Please see bellow picture. it's hard to figure out which tab is active when my monitor is not so good. I have to chick on each tab to find the active one.

This looks like a dup of #771. It should be improved in v0.6.2951.0.
See also #1337 and #2994.

Thanks for the report! @j4james is correct, this looks like #771, the fix for which should already be available.
I'd also throw out #3327 as another potentially related issue.
/dup #771


IFrame.contentWindow.postMessage(base64EncodedPdfString) no longer works in pdf.js v2.5.207

The following way to set up the content of the pdf viewer no longer works in pdf.js v2.5.207:
Markup:
<iframe id="pdfFrame" aura:id="pdfFrame" src="{! $Resource.pdfjs + '/pdfjs/web/viewer.html'}" onload="{!c.loadPdf}"/>
JS:
loadPdf: function(base64EncodedPdfString) {
    document.getElementById('pdfFrame').contentWindow.postMessage(base64EncodedPdfString, location.origin);
}

The following snippets don't work either:
document.getElementById('pdfFrame').contentWindow.postMessage(base64EncodedPdfString, '*');
document.getElementsByTagName('pdfFrame')[0].contentWindow.postMessage(base64EncodedPdfString, '*');
component.find('pdfFrame').getElement().contentWindow.postMessage(base64EncodedPdfString,  '*');

Am I missing something important?
Configuration:

Web browser and its version: chrome 7.0.4280.141, safari 14.0.1 (156<IP_ADDRESS>.10, 15610)
Operating system and its version: masOS Catalina 10.15.7
PDF.js version: 2.5.207
Is a browser extension: no

The following example integrates the pdf.js library with the Salesforce Aura Component.

The following way to set up the content of the pdf viewer no longer works in pdf.js v2.5.207

There's no changes in the PDF.js library, and/or its default viewer, which would explain the issues your seeing; hence the assumption that whatever the problem is started with that a particular PDF.js version might be a red herring.
However, if you're convinced that it's a PDF.js regression, you should be able to use git bisect to find the offending change; see https://github.com/mozilla/pdf.js/wiki/Bisecting-a-Regression

The following example integrates the pdf.js library with the Salesforce Aura Component.

We know nothing about "Salesforce Aura Component", and thus we (obviously) cannot provide support for that here.
Finally, please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

The following way to set up the content of the pdf viewer no longer works in pdf.js v2.5.207

There's no changes in the PDF.js library, and/or its default viewer, which would explain the issues your seeing; hence the assumption that whatever the problem is started with that a particular PDF.js version might be a red herring.
However, if you're convinced that it's a PDF.js regression, you should be able to use git bisect to find the offending change; see https://github.com/mozilla/pdf.js/wiki/Bisecting-a-Regression

The following example integrates the pdf.js library with the Salesforce Aura Component.

We know nothing about "Salesforce Aura Component", and thus we (obviously) cannot provide support for that here.
Finally, please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

I'm following this solution and it does work with the pdf.js library included in the solution's git repo, but not with the latest one.

I'm following this solution and it does work with the pdf.js library included in the solution's git repo, but not with the latest one.

I'm following this solution and it does work with the pdf.js library included in the solution's git repo, but not with the latest one.

Then please direct further support question there, rather than here, since we cannot provide assistance for third-party implementation of the PDF.js library.

I'm following this solution and it does work with the pdf.js library included in the solution's git repo, but not with the latest one.

Then please direct further support question there, rather than here, since we cannot provide assistance for third-party implementation of the PDF.js library.

Hi @SlavaDonnikov,
Just wondering if you were able to resolve this issue?
I am actually having similar issue while post data to view.html in LWC with the newest pdf.js version.
Thanks.


Add an Arcball Sample

Nice to work with glmnet : http://en.wikibooks.org/wiki/OpenGL_Programming/Modern_OpenGL_Tutorial_Arcball

@dwmkerr  any updates for this one? :) cause it's simpler to support rotation


Experience with blue/green using this module?

I have issues
I'm submitting a...

[ ] bug report
[x] feature request
[x] support request
[x] kudos, thank you, warm fuzzy

What is the current behavior?
Currently, in order to achieve blue/green deployment with worker groups (i.e. updating to a new AMI), I have to add a new worker group with the updated AMI, let them spin up, drain the old nodes so pods transition, then scale down the old worker group (set min/max/desired to 0).
This is not a terrible way of doing it but the problem is that the old ASG (and related resources) sticks around forever and there doesn't seem to be a way to clean up the old stuff without major surgery. If I change the AMI 3 times, I now have 3 worker groups - 2 inactive and scaled to 0 and one active.
Is there a better way of doing this with this module? There's a distinct possibility I'm missing some fundamental terraform concepts but this seems like a complex issue to me. My code ends up looking like this after a new worker group is fully deployed and the old is scaled down (you can see how even semi-frequent deployments would make this list long and leave a lot of trailing garbage):
                  map(
                      "name", "k8s-worker-179fc16f",
                      "ami_id", "ami-179fc16f",
                      "asg_desired_capacity", "0",
                      "asg_max_size", "0",
                      "asg_min_size", "0",
                      ),
                  map(
                      "name", "k8s-worker-67a0841f",
                      "ami_id", "ami-67a0841f",
                      "asg_desired_capacity", "5",
                      "asg_max_size", "8",
                      "asg_min_size", "5",
                      "instance_type","${lookup(var.worker_sizes, "${terraform.workspace}")}",
                      "key_name", "${aws_key_pair.infra-deployer.key_name}",
                      "root_volume_size", "48"
                      )

Environment details

Affected module version: latest with customizations
OS: OSX and AL2
Terraform version: 0.11.7

Any other relevant info
I have seen other code around the internet that does blue/green ASGs but those are for much simpler use-cases IMO - a create_before_destroy and letting it rip would bring a K8s cluster down. I have no qualms with multiple apply steps - its the cleanup part that I'm after.

Hey @hobbsh - totally valid points here. Let's see if we can't find a way.
Thinking about this a bit, the situation wouldn't be so bad if we had a load balancer enforcing health in tandem with create_before_destroy and a minimum healthy instance count. Alas, not in this brave new world...
I haven't quite put together how removing a dead asg entry from the list ends up being disruptive especially if you've explicitly named your groups as you show above. Does terraform tear down everything and recreate the ones that remain?

@brandoconnor Yes terraform sees the index change and recreates everything. Terraform will see the list indexes have changed and reassign the resource names based on the new indexes. It's a bit confusing to me why a one element worker_group list does not have [0] appended to it in the resource name, it shows up as just module.eks.aws_autoscaling_group.workers. Only after adding a second worker_group does the index appear, but that may be irrelevant and something I haven't noticed in Terraform until now.
I have been thinking about possibly adding a flag like delete = true so all that's left of an old ASG map is map("delete", "true") but that would require reworking the count parameter on all the ASG resources. I have also done targeted destroys but then that gets messy with resources wanting to recreate since the ASG still exists in the worker_groups list, again requiring some sort of flag to tell Terraform not to recreate. Maybe more things will be possible when Terraform v0.12 is released.
I dug back in the terraform history and found an example of what deleting the original ASG looks like:
~ module.eks.aws_autoscaling_group.workers
      launch_configuration:                      "staging-k8s-worker2018072300313993610000000b" => "${element(aws_launch_configuration.workers.*.id, count.index)}"

  - module.eks.aws_autoscaling_group.workers[1]

-/+ module.eks.aws_launch_configuration.workers (new resource required)
      id:                                        "staging-k8s-worker2018072300313993610000000b" => <computed> (forces new resource)
      associate_public_ip_address:               "false" => "false"
      ebs_block_device.#:                        "0" => <computed>
      ebs_optimized:                             "true" => "true"
      enable_monitoring:                         "true" => "true"
      iam_instance_profile:                      "staging20180723003138205600000007" => "staging20180723003138205600000007"
      image_id:                                  "ami-179fc16f" => "ami-c82004b0" (forces new resource)
      instance_type:                             "m4.large" => "m4.large"
      key_name:                                  "infra-deployer" => "infra-deployer"
      name:                                      "staging-k8s-worker2018072300313993610000000b" => <computed>
      name_prefix:                               "staging-k8s-worker" => "staging-k8s-worker"
      root_block_device.#:                       "1" => "1"
      root_block_device.0.delete_on_termination: "true" => "true"
      root_block_device.0.iops:                  "0" => "0"
      root_block_device.0.volume_size:           "20" => "48" (forces new resource)
      root_block_device.0.volume_type:           "gp2" => "gp2"
      security_groups.#:                         "2" => "2"
      security_groups.1093865381:                "sg-cf611ebf" => "sg-cf611ebf"
      security_groups.3825257995:                "sg-45093e3b" => "sg-45093e3b"
      user_data_base64: "REDACTED "

  - module.eks.aws_launch_configuration.workers[1]

Less practical of a solution but perhaps a slight improvement on what you've got - consider reusing the orphaned map left by a blanked out worker group entry such that a pair of entries are dedicated to a service in a blue-green fashion. A deployment becomes somewhat heavy in that it requires 3 distinct changes but it's at least somewhat better than leaving a long trail of deployment corpses.
State 1: Blue is live; green offline
map(
                      "name", "k8s-worker-blue",
                      "ami_id", "ami-179fc16f",
                      "asg_desired_capacity", "0",
                      "asg_max_size", "0",
                      "asg_min_size", "0",
                      ),
                  map(
                      "name", "k8s-worker-green",
                      "ami_id", "ami-67a0841f",
                      "asg_desired_capacity", "5",
                      "asg_max_size", "8",
                      "asg_min_size", "5",
                      "instance_type","${lookup(var.worker_sizes, "${terraform.workspace}")}",
                      "key_name", "${aws_key_pair.infra-deployer.key_name}",
                      "root_volume_size", "48"
                      )

State 2: transitional, Both blue and green live. When containers are balanced, monitor, verify, and drain green.
map(
                      "name", "k8s-worker-blue",
                      "ami_id", "ami-179fc16f",
                      "asg_desired_capacity", "5",
                      "asg_max_size", "8",
                      "asg_min_size", "5",
                      "instance_type","${lookup(var.worker_sizes, "${terraform.workspace}")}",
                      "key_name", "${aws_key_pair.infra-deployer.key_name}",
                      "root_volume_size", "48"
                      ),
                  map(
                      "name", "k8s-worker-green",
                      "ami_id", "ami-67a0841f",
                      "asg_desired_capacity", "5",
                      "asg_max_size", "8",
                      "asg_min_size", "5",
                      "instance_type","${lookup(var.worker_sizes, "${terraform.workspace}")}",
                      "key_name", "${aws_key_pair.infra-deployer.key_name}",
                      "root_volume_size", "48"
                      )

State 3: spin down green; blue takes all traffic
map(
                      "name", "k8s-worker-blue",
                      "ami_id", "ami-179fc16f",
                      "asg_desired_capacity", "5",
                      "asg_max_size", "8",
                      "asg_min_size", "5",
                      "instance_type","${lookup(var.worker_sizes, "${terraform.workspace}")}",
                      "key_name", "${aws_key_pair.infra-deployer.key_name}",
                      "root_volume_size", "48"
                      ),
                  map(
                      "name", "k8s-worker-green",
                      "ami_id", "ami-67a0841f",
                      "asg_desired_capacity", "0",
                      "asg_max_size", "0",
                      "asg_min_size", "0",
                      )

The good news is the unit of deployment in a k8s-centric system shouldn't be the worker nodes themselves so having to roll out a refreshed worker group often doesn't seem likely, though it's an eventuality given that AMIs all need updates and retirement.

@brandoconnor thanks for the thoughts! I was pretty caught up in having one worker group and no extra resources that I kinda glossed over the concept of alternating the worker groups (instead of creating a new one and trying to delete all old ones completely). I'll give this a shot next time I need to roll out a new AMI (probably in a few weeks).
Compared to something like kubespray, this module combined with a managed controlplane allows much greater flexibility (I can create a mirror cluster in a different region in 20 minutes!) so I really appreciate the work put in here! This is probably good to close and hopefully helps other people in a similar situation.

 This is the first I'd heard the project contrasted with kubespray. Perhaps a dedicated doc on certain operational aspects like this is warranted. I'll keep that in mind moving forward.


IpVersions/KeyValueStoreXdsDelegateIntegrationTest.BasicSuccess is flakey

I have seen this a few times, but infrequently, and only recently

[       OK ] IpVersions/KeyValueStoreXdsDelegateIntegrationTest.BasicSuccess/3 (268 ms)
[ RUN      ] IpVersions/KeyValueStoreXdsDelegateIntegrationTest.BasicSuccess/4
./test/integration/server.h:445: Failure
Value of: TestUtility::waitForCounterGe(statStore(), name, value, time_system_, timeout)
  0x1b977d4: testing::Test::Run()
  0x1b98924: testing::TestInfo::Run()
... Google Test internal frames ...

contrib/config/test/kv_store_xds_delegate_integration_test.cc:360: Failure
Expected equality of these values:
  2
  test_server_->counter("xds.kv_store.load_success")->value()
    Which is: 1
Stack trace:
  0x1b97934: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x1b977d4: testing::Test::Run()
  0x1b98924: testing::TestInfo::Run()
... Google Test internal frames ...

contrib/config/test/kv_store_xds_delegate_integration_test.cc:367: Failure
Expected equality of these values:
  "saz"
  getRuntimeKey("baz")
    Which is: ""
Stack trace:
  0x1b97934: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x1b977d4: testing::Test::Run()
  0x1b98924: testing::TestInfo::Run()
... Google Test internal frames ...

unknown file: Failure
C++ exception with description "cannot bind '[::1]:45237': Address already in use" thrown in the test body.
[external/com_google_absl/absl/flags/internal/flag.cc : 115]

https://dev.azure.com/cncf/envoy/_build/results?buildId=135269&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=67a76341-37f4-5b49-db38-acbb8a59af82&l=213
for some reason im not seeing any trace of this in azp analytics, not sure why
The issue would appear to be running out of (or trying to reuse currently active) ports

@alyssawilk this is an arm flake afaict - and is the symptom i was wondering about re the lds_integration test (altho i didnt find evidence so far in that case)

Thanks @phlax! If I find more related failures I'll post them here, so we can track this.
Do you know if it repeats over the same test?
cc @abeyad who may think of a reason that causes this flake.

Do you know if it repeats over the same test?

not sure iiuc but we dont test flakily in ci anymore but it is passing other times so we can be fairly sure its a flake - i didnt test locally

Based on the error message, it seems like when we try to shutdown the fake upstream and restart it, the restarted fake upstream tries to bind to a port already in use.  I'm guessing the problem may stem from some weird interaction in https://github.com/envoyproxy/envoy/blob/4b352da9c8496e536432a82d29b8ba0347c01941/contrib/config/test/kv_store_xds_delegate_integration_test.cc#L251-L252.
I'll assign this to myself and take a look.

I'm able to reproduce this locally (fails a handful of times in 100 runs).  Will hopefully find the issue and get out a fix soon.


When is the code and trained model going to be released?

Can you please inform us approximately when is the code and the trained model going to be released?
And please also update the license of the repo. Thanks!

+1

I think the code is already uploaded to the repo.
Do you mean the dreambooth trained model?
Btw, we just update the github to MIT license. So feel free to use it.

I think the code is already uploaded to the repo. Do you mean the dreambooth trained model? Btw, we just update the github to MIT license. So feel free to use it.

conda build environment error  , and pip requirements faild.


feat: add container resource detector.

This PR adds a resource detector for Containers.
It will add the container ID if possible.
For containers running on a Docker runtime, it will also try to add
* container.image.name
* container.image.tag
* container.name
* container.runtime
but that depends on the availability of a readable Docker Socket.
I've decided to remove setting additional container resource attributes and only support setting the container.id.
Reasoning behind that:

Setting other container resource attributes requires a readable docker.sock/containerd.sock, which requires correct - probably most of the time equals to elevated - permissions. Most easy way to do that is of course running the container as root. I do not want to promote that.
I could try and add support for configuring access to the docker.sock using TLS certs; but that would make auto-instrumentation a lot less auto
Other languages also only seem to be setting container.id

Fixes: #179

@robertlaurin could we get an additional set of eyes on this when you get a chance?

@mwear @robertlaurin from the SIG I understood that the plan was to split the resource detectors gem into separate gems. That totally makes sense to me; and I'll rework this PR a bit to reflect that. Once that's done and approved, I'm happy to also split of the other two into separate gems.
One point on which I would like advice or some directions is the addition of other container resource attributes (see PR description, and - currently outdated - image). It'll be helpful to add the other container resource attributes as well; but I do not want to promote running the container as root. Do you perhaps have another idea on how I could add them?

The container.id cannot be determined reliably when the container has additional copy-on-write layers written to it's filesystem. I'll have to sort that out first -> returning to draft mode.

Regarding adding the other container resource attributes: I've learned that I can use the otelcols k8sattributesprocessor to fix that.

@arielvalentin lgtm

@ericmustin would you mind merging and releasing?

@mwear @ericmustin @arielvalentin anything I can do to get this merged?

CI is broken; but there's already a PR which fixes that: https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/581


[Maintenance] Fix broken skinning test

Background
The skinning test is currently broken! This has most likely been the case for some time.
Actual:
[
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0,
  0.0
]
Expected:
[
  0.99999994,
  -3.0733645e-8,
  1.1920929e-7,
  0.0,
  1.3969839e-8,
  0.9999999,
  -5.401671e-8,
  0.0,
  -2.9802322e-8,
  -6.146729e-8,
  1.0,
  0.0,
  0.0,
  0.0,
  0.0,
  1.0
]

However, skinning does actually work, so something is just wrong with the tests.

Hi, Can I contribute on this project ? I am new to the opensource.

Hi there, thanks so much for reaching out!
While I'd love to say "yes, dive right in!!" Hotham is a very complex project with a lot of moving parts. I think if you're someone who's looking to get involved in Open Source for the first time, we're probably not a good fit for you. ☹
I highly recommend finding a library that you use regularly, and then finding bugs, or improving their tests! Even these small changes are an amazing way to get started - at least that's what worked for me.
Best of luck!

Thankyou ! for the feedback Kane. This would help me a lot.  👍🏼


use windows Trusted Root Certification Authorities similar to win-ca

Our company uses internal ca and proxy all the ssl traffic.
Currently, the CA still has problem within vscode
see copilot (https://github.com/orgs/community/discussions/8866), vscode (https://github.com/microsoft/vscode/issues/177139)
In the end, the win-ca extension works for me. https://github.com/ukoloff/win-ca
The plugin is working perfectly, but it is hard to get the IT apartment to approve that plugin.
Could we add a similar function to vscode core? either of the following will work for me (and other users behind a cooperate firewall).

support the system CA similar to win-ca (I think the essential part is the delayed load of the CA)
give us an option to provide the root-ca file by path. (most of the company like us already has the file ready to be used for curl/node/linux)

We are using a modified version of win-ca (https://github.com/Microsoft/vscode-windows-ca-certs) to load the OS certificates. You have System Certificates enabled in your user settings? (It should be enabled by default.)

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Automatically configure Capybara when not using Cucumber

Would really love to see this merged in, lots of people are foregoing Cucumber now. Not that it's not easy to configure yourself, but having it work by default sure is nice.


[fr] Replace old link with new link in deploying the dashboard ui doc.

Description:
Update Deploying the Dashboard UI with the new link in french web-ui-dashboard doc.
Proposed Solution:
Updated link from
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/aio/deploy/recommended.yaml
to
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.6.1/aio/deploy/recommended.yaml
Page to Update:
https://kubernetes.io/fr/docs/tasks/access-application-cluster/web-ui-dashboard/#déploiement-du-tableau-de-bord

fixes #38149

Hi, @rekcah78 found this issue please take a look.

/close


polymake: 4.5 -> 4.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/polymake/versions.
meta.description for polymake is: "Software for research in polyhedral geometry"
meta.homepage for polymake is: "https://www.polymake.org/doku.php"
meta.changelog for polymake is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6/bin/.polymake-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6/bin/polymake had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6/bin/.polymake-config-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6/bin/polymake-config had a zero exit code or showed the expected version
0 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 4.6 with grep in /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6
found 4.6 in filename of file in /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
polymake

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A polymake https://github.com/r-ryantm/nixpkgs/archive/0948b62a1f8f2656be85e122ad8b33208544ab39.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6
ls -la /nix/store/cm5k8h2xws3q9h2ba2ayalprmzgacvdf-polymake-4.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

polymake

Maintainer pings
cc @timokau @omasanori @7c6f434c @collares for testing.

@collares does now Sage use bindled polymake?

I think Sage uses no polymake at all at the moment. I think Sage should use polymake, but unfortunately I will only be able to investigate that is to change in a couple of weeks (I assume it will be easy, though).