UnicodeEncodeError ascii' codec can't encode characters

Am trying to run a training job using fastai in a Docker container (not Jupyter notebook) and getting a UnicodeEncodeError in the fastprogress library. Am running fastprogress version 0.1.15, fastai version 1.0.28 with Python v3.6.
Full stack trace includes the following:
algo-1-3QNM9_1_51756cf5708d | Called _train method with model arch: resnet34, batch size: 64, image size: 224, epochs: 4
algo-1-3QNM9_1_51756cf5708d | Getting training data from dir: /opt/ml/input/data/training
algo-1-3QNM9_1_51756cf5708d | Model architecture is resnet34
algo-1-3QNM9_1_51756cf5708d | Creating pretrained conv net
algo-1-3QNM9_1_51756cf5708d | Downloading: "https://download.pytorch.org/models/resnet34-333f7ec4.pth" to /root/.torch/models/resnet34-333f7ec4.pth
100% 87306240/87306240 [00:01<00:00, 70374700.25it/s]
algo-1-3QNM9_1_51756cf5708d | Fit four cycles
algo-1-3QNM9_1_51756cf5708d | epoch  train_loss  valid_loss  accuracy
/usr/local/lib/python3.6/dist-packages/PIL/Image.py:953: UserWarning: Palette images with Transparency   expressed in bytes should be converted to RGBA images
algo-1-3QNM9_1_51756cf5708d |   'to RGBA images')
Traceback (most recent call last):
algo-1-3QNM9_1_51756cf5708d |   File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
algo-1-3QNM9_1_51756cf5708d |     "__main__", mod_spec)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
algo-1-3QNM9_1_51756cf5708d |     exec(code, run_globals)
algo-1-3QNM9_1_51756cf5708d |   File "/opt/ml/code/shirts.py", line 152, in <module>
algo-1-3QNM9_1_51756cf5708d |     _train(parser.parse_args())
algo-1-3QNM9_1_51756cf5708d |   File "/opt/ml/code/shirts.py", line 66, in _train
algo-1-3QNM9_1_51756cf5708d |     learn.fit_one_cycle(4)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastai/train.py", line 20, in fit_one_cycle
algo-1-3QNM9_1_51756cf5708d |     learn.fit(cyc_len, max_lr, wd=wd, callbacks=callbacks)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastai/basic_train.py", line 162, in fit
algo-1-3QNM9_1_51756cf5708d |     callbacks=self.callbacks+callbacks)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastai/basic_train.py", line 94, in fit
algo-1-3QNM9_1_51756cf5708d |     raise e
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastai/basic_train.py", line 82, in fit
algo-1-3QNM9_1_51756cf5708d |     for xb,yb in progress_bar(data.train_dl, parent=pbar):
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastprogress/fastprogress.py", line 67, in __iter__
algo-1-3QNM9_1_51756cf5708d |     if self.auto_update: self.update(i+1)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastprogress/fastprogress.py", line 85, in update
algo-1-3QNM9_1_51756cf5708d |     self.update_bar(val)
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastprogress/fastprogress.py", line 97, in update_bar
algo-1-3QNM9_1_51756cf5708d |     else: self.on_update(val, f'{100 * val/self.total:.2f}% [{val}/{self.total} {elapsed_t}<{remaining_t}{end}]')
algo-1-3QNM9_1_51756cf5708d |   File "/usr/local/lib/python3.6/dist-packages/fastprogress/fastprogress.py", line 262, in on_update
algo-1-3QNM9_1_51756cf5708d |     if printing(): WRITER_FN(to_write, end = '\r')
algo-1-3QNM9_1_51756cf5708d | UnicodeEncodeError: 'ascii' codec can't encode characters in position 14-15: ordinal not in range(128)
algo-1-3QNM9_1_51756cf5708d | 2018-11-20 08:10:39,646 sagemaker-containers ERROR    ExecuteUserScriptError:
algo-1-3QNM9_1_51756cf5708d | Command "/usr/local/bin/python -m shirts --batch-size 64 --epochs 4"

Bit tricky as this is running in a docker container and hard to modify the fastprogress.py file. Perhaps encoding it in UTF-8 would work
e.g. replace this line with the following:
bar = self.fill.encode('utf-8') * filled_len + '-' * (self.length - filled_len)

Seems to only happen with Python 3.6. Works fine with Python 3.7

This has been fixed as I set the locale inside the Docker container to the following:
ENV LANG C.UTF-8
ENV LC_ALL C.UTF-8

Now working fine

This has been fixed as I set the locale inside the Docker container to the following:
ENV LANG C.UTF-8
ENV LC_ALL C.UTF-8

Now working fine

I had the same issue with Python3.6 and putting those ENVs to my container fixed the problem. Thanks!

Was having the same issue in a different docker container I created. Thanks for this fix @mattmcclean !


How performant are these polyfills (esp. in IE11)?

(Not sure this is the right venue for this; let me know if there's a better place to have this conversation)
For context: I'm interested in converting a set of AngularJS 1.x components to WCs, with Skate. We'd target IE11 + evergreens.
While doing some benchmarking I've found substantial performance hits when rendering web components, particularly in IE11. Slower than AngularJS 1.x, even I'm not sure if I'm doing something wrong in my benchmark, or if the polyfills themselves are slow, but I'd like another set of eyes on them.
Here's a few Webpackbins wherein I'm testing the load time to create 1k elements with various frameworks:

Framework
URL
IE11
FF
Chrome
Safari TP

Vanilla CE
https://www.webpackbin.com/bins/-KkurrXiOAGwv6DDVDt_
2905
534
190
170

Skate 5
https://www.webpackbin.com/bins/-Kkm6e7UGhPHnNUvRxXU
3579
683
183
277

Skate (no connectedCallback )

3409
776
192
288

Skate (no slot)
https://www.webpackbin.com/bins/-KkuibIirN3VlNrHvM40
2296
539
184
290

Vue
https://www.webpackbin.com/bins/-KkqHt9FOCoXV_qc7q_w
620
502
204
269

AngularJS
https://www.webpackbin.com/bins/-KkqLUTVDarHnAbziblD
608
445
263
271

(Note: Webpackbin doesn't work in IE11, so I had to download the bins and npm start them locally)
So yeah, I don't think this is an issue with Skate (as vanilla custom elements experience the same issue), but perhaps with ShadyDOM in particular. But we likely won't be able to go forward with a WC rewrite of our library if it's going to result in a 5x slowdown in the browser used by the majority of our customers.
Any idea what might be going on? Maybe my tests aren't good benchmarks of real-world behavior?

(Not sure this is the right venue for this; let me know if there's a better place to have this conversation)

The perforance issues are most-definitely related to ShadyDOM as they patch the DOM interfaces. The Custom Element polyfill might add a little bit, but I would expect it to be acceptable. I'd say that it'd be a good idea to narrow it down to one or the other and then have the conversation in the respective repositories: github.com/webcomponents/custom-elements and github.com/webcomponents/shadydom.

Any idea what might be going on? Maybe my tests aren't good benchmarks of real-world behavior?

If you want to test raw element creation, I think your tests are fine. The problem (at least to me) has been clear from the beginning: polyfills - at least in this respect - are going to be slow. Some can deal with it and some can't, and you'll have to make the best choice that fits your use case.
So most of your customers are still using IE11?
As a side note, it's nice to see Skate beat everything else under native (and even get really close in polyfilled FF.

In looking at the benchmarks, the Skate one is unnecessarily calling super.connectedCallback(). It might be good to get rid of this. Classes and super calls are notoriously expensive in transpiled code.

I'd say that it'd be a good idea to narrow it down to one or the other and then have the conversation in the respective repositories

Makes sense. Should I focus on ShadyDOM or are you still maintaining CloudyDOM?

So most of your customers are still using IE11?

Yeah, corporate Win7 environment for the most part. Edge is our next step but it'll be a while.

it's nice to see Skate mostly beat everything else under native (and even get really close in polyfilled FF)

You guys are rocking the party that rocks the pinata. 🎉

Makes sense. Should I focus on ShadyDOM or are you still maintaining CloudyDOM?

cc @matthewp

Made the change, but didn't seem to affect things much.

Just in case :p

Yeah, corporate Win7 environment for the most part. Edge is our next step but it'll be a while.

I'm wondering what type of performance you'd get out of something like https://github.com/skatejs/ssr/blob/master/sd.js. It's still the early days, but that only patches the custom element, not every DOM interface. It doesn't use slots yet, though, but I'm not sure if it ever will.

Made a separate ticket at https://github.com/webcomponents/shadydom/issues/155. I think we can close this one out.

I'm wondering what type of performance you'd get out of something like https://github.com/skatejs/ssr/blob/master/sd.js

I'm not entirely sure how this would be used. We haven't looked at SSR much; partially because we're developing lots of AngularJS 1.x apps, which aren't easy to SSR. But I'll be interested to see this develop; maybe an example of how it's used would help make this less opaque.
Anyhow, thanks again for your help!

I'm still maintaining cloudydom, but it's mostly just pulling down from shadydom, so best to start there.

Maybe something you could do would be to - instead of having 1000s of custom elements - to have a single custom element that accepts an array prop? Not sure of your use case, though.

@mattdsteele In the web components issue, you said "Vue (dev mode)". Out of curiosity what is prod mode like?

Wish I could say; I wasn't able to make it work in IE11 in prod mode 😐
On Wednesday, May 24, 2017, Trey Shugart<EMAIL_ADDRESS>wrote:

@mattdsteele https://github.com/mattdsteele In the web components
issue, you said "Vue (dev mode)". Out of curiosity what is prod mode like?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/web-components/issues/47#issuecomment-303896276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXv1d6CdgTq63KCXJIYzqsf-SpqovgRks5r9Nd6gaJpZM4NlY3K
.

IE9 and above

o_0


State boundaries disappear at >z8

Fixed with https://github.com/datadesk/web-map-maker/commit/a1358a0a5328734036854c905812b79e2e2870eb


[Feature]:Add Ratings

Describe the feature
Adding product ratings
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

You have been assigned.


[$250] Allow native app releases to take staging env variables into consideration

Problem
In this issue https://github.com/Expensify/App/issues/10163, we have implemented a setting toggle which will aim all the API commands to staging or production API (if in Staging App). However, this works only in desktop or web, but not in native mobile apps as the live logs shown.
The reason it does not work is that we always build the App only once for deploy. We just relabel staging release for the production one and so when building the staging App we use the production env variables causing this issue
Actual behaviour

On native mobile App (iOS and Android), the staging API toggle is turned on
The API requests are still made to production API endpoints

Expected behaviour

On native mobile App (iOS and Android), the staging API toggle is turned on
The API requests will be made to the staging endpoints same as on web app version

Why is it important
This will allow us to test staging changes with staging API at the same time.
Solution
Find a way how we can use the environment variables in native app so we can distinguish between staging and production to send the API requests to desired API endpoints.

I realized we have this Staging badge or dev badge even in the native apps so we must have some way to figure that out and the withEnvironment HOC
I am not sure if we can use those in the API toggle but would be worth discovering.

Upwork Job

No proposals yet

We just relabel staging release for the production one and so when building the staging App we use the production env variables causing this issue

It looks difficult to me to imagine something while we continue to release the andorid/ios app by relabeling the staging release.
What I want to propose instead is to use https://github.com/luggit/react-native-config npm and issue the build commands like
$ ENVFILE=.env.staging react-native run-ios                  //for staging and
$ ENVFILE=.env.production react-native run-ios           //for production
I can try the same. Request you comment @mountiny

@smrutiparida We already do that. Please check the code and let us know if you feel something is off.

@mountiny I think the issue details are not very clear. I don't understand the expected behavior. Can you please improve these?

My second solution above can help the android code read a version no from a firebase remote config. Based on the version stored in remote, the API_URL can be configured dynamically within in the code. By doing so, the android build can be tested against staging URL for all versions higher than the remote version. It can also be released to PROD by only changing the label. @mountiny is that the expected thing ?

@parasharrajat @smrutiparida I have added some lines to the issue body. The problem is that the native apps disregard the API endpoint settings, they always send requests to the production API even if the staging API toggle in settings in turned on.
I am unfortunately not that familiar with firebase remote config so I am not sure. Is there any way we could use this approach: https://github.com/Expensify/App/issues/11561#issuecomment-1266689289 to achieve this natively?

Thanks for adding that details. It is a lot more clear to me now.

@mountiny What I have understood so far is, we rename the label of a staging build to release to PROD. This is the reason API_URL present in the ENV values are as PROD_URL as there are no way presently for an iOS/Android android build to read the env values dynamically based on dev/taging/prod post the creation of a build.
@parasharrajat Which setting you mean ?

What I have understood so far is, we rename the label of a staging build to release to PROD. This is the reason API_URL present in the ENV values are as PROD_URL as there are no way presently for an iOS/Android android build to read the env values dynamically based on dev/taging/prod post the creation of a build.

Yes we take the code in main and build it with prod settings and release as Staging version. What used to be staging version is then relabelled to production so no changes to the code.

There are three env files with the name .env.<environemnt>. so IMO, .env.staging is used while building the staging app.

@parasharrajat @mountiny shall we work on it or hold on to this issue ?

There are three env files with the name .env.. so IMO, .env.staging is used while building the staging app.

I suspect they might be used for web and desktop but what I understood about the native deploy pipeline the app does not get the staging env variables the same way as on web, hence this issue.
@smrutiparida no, this issue is still persistent and would be great to fix it

Another way can be reading variable from firebase remote config

// remote config with production version if same found in the build then
// app points to PROD_URL for everything else STAGING_URL is set for testing.
// We can improvise this logic.

const checkAppVersion = remoteConfig().getValue('app_production_version');

if (checkAppVersion.asString() === getBuildVersion()) {
  setEnvironmentAsProduction();
}
else
{
  setEnvironmentAsStaging();
}

https://github.com/invertase/react-native-firebase/tree/main/packages/remote-config

Hi
I was thinking to try this with Firebase config. Are we looking for a proposal beyond above.

Any proposal is accepted that fixes the issue.

Correct, but ideally we prefer to solve this without adding new packages.

**** Proposal

First, I moved the of the URLs based on security and environment value lib/Environment files

Second, basic implementation of returning the URLs based on environment value

BetaChecker.isBetaBuild() shall set the environment for ios and android based on existing code and return the proper environment value
We just moved the shouldUseStagingServer check to index.js and index.native.js as part of keeping the code in one place.

Do the same for desktop and web in index.js

Please review @mountiny @parasharrajat

All config should be in Config.js file. The environment will only give us env info.

What we are solving here is,
In the fastlane config i.e ./Fastfile we have the below config.
desc "Generate a new local APK"
  lane :build do
    ENV["ENVFILE"]=".env.production"

    gradle(
      project_dir: './android',
      task: 'assemble',
      build_type: 'Release',
    )
  end

Because of which a build always calls the production API URL configured in the .env.production. And since we use the same build for testing and just relabels it as mentioned in description of this bug, quoted below.

The reason it does not work is that we always build the App only once for deploy. We just relabel staging release for the production one and so when building the staging App we use the production env variables causing this issue

With this change, even  a Fastfile production configured build by comparing between the package version and the version uploaded to play store presently, shall be able to figure out if the build is the PROD one or STAGING one. Knowing which it shall use the staging API URL for staging build and PROD API URL for prod build

@mountiny could you please suggest what to do next ?

@smrutiparida I am not sure on this one, I am not that familiar with the deploy flow so dont want to agree with changes which might not be intended. I will ask someone who might be more familiar

I agree the root cause is because we always use .env.production in fastlane builds. I also agree that using our existing BetaChecker.isBetaBuild() is best here. We should be able to come up with a clean solution that uses BetaChecker.isBetaBuild() and .env.staging, right?
I think @smrutiparida is close to the ideal solution, but maybe there is some additional code cleanup @parasharrajat or @mountiny can suggest..

Feedback on the proposal https://github.com/Expensify/App/issues/11561#issuecomment-1285351812:

Config variables should be in Config.js file. you can move the logic to dynamically calculate it in that file but all of those will only be exported from this file.

Waiting for proposals...

We should be able to come up with a clean solution that uses BetaChecker.isBetaBuild() and .env.staging, right?

The present issue is to use the Staging API_URL in Staging build. Which is achieved by BetaChecker.isBetaBuild() check. Using .env.staging for staging build shall need change in Fastlane process which is a larger discussion. Hence I think that change can be kept out of scope of this issue and we can create another task for that.

Feedback on the proposal #11561 (comment):

Config variables should be in Config.js file. you can move the logic to dynamically calculate it in that file but all of those will only be exported from this file.

Please name the config variables we should move.
The ENVIRONMENT_URLS constant is already present Environment.js and we have introduced 2 new Constants for API_URL named SECURE_ENVIRONMENT_URLS and UNSECURE_ENVIRONMENT_URLS. Since those 2 constants are local to Environment.js. moving that to Config.js may not be needed.

@AndrewGable @parasharrajat thoughts?

I am still confused about the root cause. I will give it another try in some time.

@smrutiparida I agree that using the entire staging config is not what we exactly ask for in this issue, but it would be great to get some sense if that is ultimately what we want to achieve (I think it would make sense as at the moment it is confusing and easy to just assume Staging versions use the env.staging variables).
I think it should be fine to do the necessary changes in this issue to allow the Staging API toggle in Android and iOS native apps too.
@smrutiparida To follow the contributor process can you please post a proposal here how that would be achieved. As @AndrewGable mentioned, you are close to he solution, can you please clean it up based on the feedback and we can review it again? Thank you very much!

it is confusing and easy to just assume Staging versions use the env.staging variables

@mountiny The solution won't be that straight forward. The present Fastlane process does not even read the .env.staging values. how shall we read those values. We would need a totally different approach for that.

I think it should be fine to do the necessary changes in this issue to allow the Staging API toggle in Android and iOS native apps too.

In the PR #10690 we introduced STAGING_EXPENSIFY_URL and STAGING_SECURE_EXPENSIFY_URL. This change shall help you read these 2 values in an android/ios staging build by using isBetaCheckBuild() function. Proposal below.

We should be able to come up with a clean solution that uses BetaChecker.isBetaBuild() and .env.staging, right?

@AndrewGable .env.staging file is no where read by the Fastlane build. A clean solution here should be to totally get away with the .env files and use firebase config to read the environment values. I have mentioned about that solution
here https://github.com/Expensify/App/issues/11561#issuecomment-1291493698

Proposal
Use additional check of Environment.getEnvironment() along with IS_IN_STAGING configuration to known the environment values for setting API URL.
BetaChecker.isBetaBuild() shall set the environment for ios and android based on existing code and returns the proper environment value

Created a new Upwork Job (and invited @parasharrajat for eventual C+ payment) as the last one expired.

Looks promising to me @parasharrajat what are your thoughts?

@smrutiparida just wanted to confirm, we cannot use the isBetaChecker for web/desktop too? Just wondering it would be nice to only have one method to distinguish that env variables on all platforms

@mountiny You're right. We can remove CONFIG.IS_IN_STAGING  and just use the Environment.getEnvironment to know both. The BetaChecker code support it for web/desktop and android/ios.
However some additional testing shall be needed as the web/desktop change of this functionality introduced the variable in the config in #10690. Can you see that previous PR and confirm if I shall remove it or not.

Once you confirm, the change shall look like this

Yeah I think that looks fine to me, I would just wait for Rajat to confirm.
The change itself makes sense to me however, I cannot predict without testing this will work compared to just using the CONFIG

My mind is blocked atm. I will check back in sometime.

No problem, make sure to rest. I think we can go ahead with @smrutiparida proposal, I hope you have tested this locally. We can try to polish this in the PR.
Please, feel free to raise the PR

Seems fair to me, can we update the price to 500 or handle this by the extra bonus? @MitchExpensify

Updated the price as I'm less likely to forget that way :D

This is in review, not overdue.

We are having some tough time deciding next steps as the PR review and testing showed some drawbacks of this solution we are not sure are worth it.
I have suggested bringing the discussion Slack to see what others might think about the side-effects.

Working on a new PR, hopefully that will work just fine for us. @smrutiparida you will be compensated for your work here even if we dont go with your solution.

This is not done yet, original PR has been reverted and the fix is being worked on.

The PR has been updated and is ready for a review.

I will take a look.

@mountiny we're just waiting on a deploy here, right?

Yeah this is in staging and I have QAed and it worked at least from what I saw 🎉

Noice! ❤

Reassigning the Bug label as I'm heading ooo and this will need a new CM!

@kadiealexander Coming from this comment we should have a payment off:

500 to @smrutiparida for their efforts to fix this

Thanks @mountiny!!!! Is payment due now?

I would say yes, this has been PR which was kind of untraditional in terms of the process. The internal PR should already be in production.

Thanks @mountiny! New job post is here, I've already sent hire contracts to @parasharrajat and @smrutiparida, please let me know once you've accepted and I'll issue payment.

ETA: @mountiny correct me if I'm wrong, but the problem behind this issue doesn't look like it can be added to TestFlight for regression testing? Just confirming before I take action on the checklist above.

Yeah I dont think think Applause could test the native apps which is the main issue here


Disk usage with genetic backtesting

Hi,
The genetic backtesting seems to work pretty well. However, I noticed it creates a lot of files in the simulations folder and takes a lot of disk space.
I suggest adding a flag to the sim command to skip the html file generation and to use it with the genetic backtesting.
Thanks

Actually, passing the --filename none flag would already work.

Can we also write the JSON and csv files to Simulations as well? If you leave it running for awhile it clutters up the app's root directory.

I think putting them in a new directory would be better.


Array Concatenation

Is there currently a way to concatenate arrays?

You can use join(array, " ")  replacing " " with whatever you want to concatenate with


Fixes Volumes size to be int

Fixed the Volume size to be int instead of string

Nice, thank you! can you also commit the api_data.json you used? looks like there are some new fields in instance CloudSpecificAttributes...

Code Coverage is 82.1%, details at https://s3.amazonaws.com/rs-code-coverage/rsc/2015-08-06_375_Coverage-82.1.txt (sometimes the URL can take a few minutes to be available)

@raphael : I didn't make any changes to the api_data.json. Is it possible the previous merge didn't have the generated code committed?

interesting, I guess so... looks good then.


added support for UIPageControl

Still need to add a test. But before I do please let me know if it's otherwise OK.

@tcurdt  Tests and it's good to go!

👍

@tcurdt please don't forget to add this new files in each target, iOS and tvOS.

The tests are passing now.
I might not have enough insights into the rex_value discussion. Feel free to adjust as it fits.


p.hex()

Implement p.hex() as a replacement to p.bytes(). p.hex() encodes hex strings as the "blob" type in SQLite and "bytea" type in Postgres. p.hex() is case insensitive and returns lowercase values.
Internally, refactored the indexing store encoding and decoding logic, such that encoding validates columns against the respective column type.

Still need to determine the proper "filtering" behavior in the server.


Barely any speedup when running Llama for inference (with Kernel Injection) [BUG]

As with other models when using DS inference with a Batch size 1. You would expect to see more inference speedup using kernel injection.
However tokens per second is very similar to vanilla Pytorch.
To Reproduce
Using Deepspeed - v0.9.2
required = HF Transformers, pytorch
This was ran on an A6000, using the latest HF transformers pytorch docker image
Script to test
import torch
import deepspeed
import time

# Load the tokenizer
from transformers import AutoTokenizer
tokenizer = AutoTokenizer.from_pretrained("TheBloke/stable-vicuna-13B-HF")

print("Loading original model...")
model = LlamaForCausalLM.from_pretrained("TheBloke/stable-vicuna-13B-HF", torch_dtype=torch.float16).cuda()

# Prepare the input
prompt = "this is a test prompt"
input_ids = tokenizer(prompt, return_tensors="pt").input_ids.cuda()

# Start timing for the original model
print("Generating tokens using original model...")
start_time = time.time()

tokens = model.generate(input_ids, max_new_tokens=500)

end_time = time.time()
original_model_time = end_time - start_time

# Compute and print tokens per second for original model
original_model_tps = 500 / original_model_time
print(f'Original model completed. Tokens per second: {original_model_tps}')

# Free up GPU memory
print("Clearing GPU memory...")
del model
torch.cuda.empty_cache()

# Reload the model for deepspeed
print("Reloading model for deepspeed...")
model = LlamaForCausalLM.from_pretrained("TheBloke/stable-vicuna-13B-HF", torch_dtype=torch.float16).cuda()

# Initialize deepspeed model
print("Initializing deepspeed model...")
ds_model = deepspeed.init_inference(model=model, mp_size=1, dtype=torch.float16, replace_with_kernel_inject=True).eval()

# Start timing for the deepspeed model
print("Generating tokens using deepspeed model...")
start_time = time.time()

tokens = ds_model.generate(input_ids, max_new_tokens=500)

end_time = time.time()
deepspeed_model_time = end_time - start_time

# Compute and print tokens per second for deepspeed model
deepspeed_model_tps = 500 / deepspeed_model_time
print(f'Deepspeed model completed. Tokens per second: {deepspeed_model_tps}')

Results:
Original (pytorch) model completed. Tokens per second: 49.076392832520355
Deepspeed (ds inf) model completed. Tokens per second: 50.66601410413505
Expected behavior
You should expect to see better performance from the DS inference model than we are currently getting.
ds_report output
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variablesto where it can be found.
async_io ............... [NO] ....... [NO]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.0
 [WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
Traceback (most recent call last):
  File "/opt/conda/bin/ds_report", line 6, in <module>
    cli_main()
  File "/opt/conda/lib/python3.10/site-packages/deepspeed/env_report.py", line 121, in cli_main
    main(hide_operator_status=args.hide_operator_status, hide_errors_and_warnings=args.hide_errors_and_warnings)
  File "/opt/conda/lib/python3.10/site-packages/deepspeed/env_report.py", line 115, in main
    op_report(verbose=not hide_errors_and_warnings)
  File "/opt/conda/lib/python3.10/site-packages/deepspeed/env_report.py", line 52, in op_report
    is_compatible = OKAY if builder.is_compatible(verbose) else no
  File "/opt/conda/lib/python3.10/site-packages/deepspeed/ops/op_builder/spatial_inference.py", line 29, in is_compatible
    sys_cuda_major, _ = installed_cuda_version()
  File "/opt/conda/lib/python3.10/site-packages/deepspeed/ops/op_builder/builder.py", line 43, in installed_cuda_version
    output = subprocess.check_output([cuda_home + "/bin/nvcc", "-V"], universal_newlines=True)
  File "/opt/conda/lib/python3.10/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/opt/conda/lib/python3.10/subprocess.py", line 503, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/opt/conda/lib/python3.10/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/opt/conda/lib/python3.10/subprocess.py", line 1847, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
NotADirectoryError: [Errno 20] Not a directory: '/opt/conda/bin/nvcc/bin/nvcc'```

**System info (please complete the following information):**
 - OS: Ubuntu 18.04
 - 1 X A6000

I have the same issue

@anujnayyar1 @drxmy is this issue solved? any update?

I have the same issue.

Nope still no luck. If anyone from the DS team could input here, would be really grateful.


Close btn to close Tab

Why close this issue?

You create a blank issue with no explanation. Please check the contribution guide before posting.


Add Syllabus to Learning Object

@saragon02 Could you add/review the syllabus mapping in the resource_type mapping file: https://github.com/galterlibrary/InvenioRDM-at-NU/blob/master/cd2h_repo_project/modules/records/data/resource_type_mapping.csv ?

Completed.


ERROR LOADING PLUGIN homebridge-eightsleep-pod:

==================== [19/12/2021, 21:23:26] ERROR LOADING PLUGIN homebridge-eightsleep-pod: [19/12/2021, 21:23:26] ReferenceError: window is not defined     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/fast-abort-controller/src/index.ts:20:5)     at Module._compile (node:internal/modules/cjs/loader:1101:14)     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)     at Module.load (node:internal/modules/cjs/loader:981:32)     at Function.Module._load (node:internal/modules/cjs/loader:822:12)     at Module.require (node:internal/modules/cjs/loader:1005:19)     at require (node:internal/modules/cjs/helpers:102:18)     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/promise-backoff/src/index.ts:2:1)     at Module._compile (node:internal/modules/cjs/loader:1101:14)     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) [19/12/2021, 21:23:26] ====================
I have been trying to add the EightSleep Plugin but I keep getting this error after adding the plugin. My config looks like this:
{     "platform": "EightSleepPod",     "email"<EMAIL_ADDRESS>    "password": "************",     "oauthClient": {         "id": "0************************8",         "secret": "f*********************************************6"     } }

thanks will fix!

try v2.4.2 and lmk

It now loads but there is a different error when I try and interact with the EightSleep Pod
Get Active Error -> InvalidSideStatusError: invalid currentTargetLevel
    at validateSideStatus (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/validateDeviceStatus.ts:76:11)
    at Object.validateDeviceStatus [as default] (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/validateDeviceStatus.ts:52:12)
    at EightSleepAppApi.<anonymous> (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/EightSleepAppApi.ts:79:32)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/dist/cjs/EightSleepAppApi.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
{
  "sideStatus": {
    "currentLevel": -79,
    "currentTargetLevel": 15,
    "currentActivity": "schedule",
    "version": 2,
    "smartTemperature": {
      "bedTimeLevel": 15,
      "initialSleepLevel": -10,
      "finalSleepLevel": 0,
      "currentPhase": "bedtime"
    }
  }
}
 {
  sideStatus: {
    currentLevel: -79,
    currentTargetLevel: 15,
    currentActivity: 'schedule',
    version: 2,
    smartTemperature: {
      bedTimeLevel: 15,
      initialSleepLevel: -10,
      finalSleepLevel: 0,
      currentPhase: 'bedtime'
    }
  }
}

And
 Get RotationSpeed Error -> InvalidSideStatusError: invalid currentTargetLevel
    at validateSideStatus (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/validateDeviceStatus.ts:76:11)
    at Object.validateDeviceStatus [as default] (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/validateDeviceStatus.ts:52:12)
    at EightSleepAppApi.<anonymous> (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/src/EightSleepAppApi.ts:79:32)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/dist/cjs/EightSleepAppApi.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
{
  "sideStatus": {
    "currentLevel": -79,
    "currentTargetLevel": 15,
    "currentActivity": "schedule",
    "version": 2,
    "smartTemperature": {
      "bedTimeLevel": 15,
      "initialSleepLevel": -10,
      "finalSleepLevel": 0,
      "currentPhase": "bedtime"
    }
  }
}
 {
  sideStatus: {
    currentLevel: -79,
    currentTargetLevel: 15,
    currentActivity: 'schedule',
    version: 2,
    smartTemperature: {
      bedTimeLevel: 15,
      initialSleepLevel: -10,
      finalSleepLevel: 0,
      currentPhase: 'bedtime'
    }
  }
}

got it I see.

I hadn’t tested a non left/right split bed and I was too lazy to reset mine to test it. thanks for sharing the error I see how to handle that now!

are you using the beta temperature settings feature or something**?** it’s interesting to see the target level a number not divisible by 10. I will make my response validation looser, to fix this.

thanks!

try v2.4.2 and lmk

Yep its working now! Thanks for supporting this! I really appreciate it!

woohoo! enjoy :-)

Hi!
I wanted to post on this thread, because I'm one v 2.4.3 and am now getting the second set of errors posted above. I normally have the beta temperature setting disabled, but I get these errors now whether it's enabled or disabled.
Pasting a subset of my errors below:
Get CurrentHeaterCoolerState Error -> InvalidSid
eStatusError: invalid currentTargetLevel
at validateSideStatus (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightslee
p/src/validateDeviceStatus.ts:76:11)
at Object.validateDeviceStatus [as default] (/usr/local/lib/node_modules/homebridge-eightsleep-pod/
node_modules/eightsleep/src/validateDeviceStatus.ts:51:11)
at EightSleepAppApi. (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules
/eightsleep/src/EightSleepAppApi.ts:79:32)
at Generator.next ()
at fulfilled (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/dist/cj
s/EightSleepAppApi.js:5:58)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
{
"sideStatus": {
"currentLevel": 7,
"currentTargetLevel": 6,
"currentActivity": "schedule",
"version": 2,
"smartTemperature": {
"bedTimeLevel": 6,
"initialSleepLevel": 10,
"finalSleepLevel": 9,
"currentPhase": "bedtime"
}
}
}
{
sideStatus: {
currentLevel: 7,
currentTargetLevel: 6,
currentActivity: 'schedule',
version: 2,
smartTemperature: {
bedTimeLevel: 6,
initialSleepLevel: 10,
finalSleepLevel: 9,
currentPhase: 'bedtime'
}
}
}
[07/02/2022, 22:39:20] [EightSleepPod] Get TargetHeaterCoolerState Error -> InvalidSide
StatusError: invalid currentTargetLevel
at validateSideStatus (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightslee
p/src/validateDeviceStatus.ts:76:11)
at Object.validateDeviceStatus [as default] (/usr/local/lib/node_modules/homebridge-eightsleep-pod/
node_modules/eightsleep/src/validateDeviceStatus.ts:51:11)
at EightSleepAppApi. (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules
/eightsleep/src/EightSleepAppApi.ts:79:32)
at Generator.next ()
at fulfilled (/usr/local/lib/node_modules/homebridge-eightsleep-pod/node_modules/eightsleep/dist/cj
s/EightSleepAppApi.js:5:58)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
{
"sideStatus": {
"currentLevel": 7,
"currentTargetLevel": 6,
"currentActivity": "schedule",
"version": 2,
"smartTemperature": {
"bedTimeLevel": 6,
"initialSleepLevel": 10,
"finalSleepLevel": 9,
"currentPhase": "bedtime"
}
}
}
{
sideStatus: {
currentLevel: 7,
currentTargetLevel: 6,
currentActivity: 'schedule',
version: 2,
smartTemperature: {
bedTimeLevel: 6,
initialSleepLevel: 10,
finalSleepLevel: 9,
currentPhase: 'bedtime'
}
}
}
[07/02/2022, 22:39:20] [EightSleepPod] Get Active Error -> InvalidSideStatusError: inva
The logs look ok before this, but there is a warning that precedes this. Including this just in case it helps. Let me know if I can include more info!
This plugin slows down Homebridg
e. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly
call the callback! See https://git.io/JtMGR for more info.
[07/02/2022, 21:39:31] [homebridge-eightsleep-pod] This plugin slows down Homebridg
e. The read handler for the characteristic 'Current Heater-Cooler State' didn't respond at all!. Please che
ck that you properly call the callback! See https://git.io/JtMGR for more info.
[07/02/2022, 21:39:31] [homebridge-eightsleep-pod] This plugin slows down Homebridg
e. The read handler for the characteristic 'Target Heater-Cooler State' didn't respond at all!. Please chec
k that you properly call the callback! See https://git.io/JtMGR for more info.
[07/02/2022, 21:39:31] [homebridge-eightsleep-pod] This plugin slows down Homebridg
e. The read handler for the characteristic 'Rotation Speed' didn't respond at all!. Please check that you p
roperly call the callback! See https://git.io/JtMGR for more info.

Hey feel free to file a new bug. I'll try to take a look two weekends from now. The validation bug is an easy fix, just need to lax the rules in the eightsleep module. The homebridge warnings is something I've been meaning to get to.. might also be easy too. PRs welcome

<EMAIL_ADDRESS>


Push/Pull Targeted Help Wanteds based on Contributor interests/competencies

Moved to https://github.com/finos/open-developer-platform/issues/179
Building on some concept of a contributor/developer profile (see https://github.com/finos/open-developer-platform/issues/178) build the capability to allow FINOS contributors to subscribe to requests for help that match with their personal areas of interest, especially their (programming) language competencies.
Two example use cases:

A FINOS project maintainer can generate a list of contributors within the FINOS community who have experience and interest in Java (and who have opted in to allow FINOS maintainer to find/see them)
A developer with Haskell experience can subscribe to notifications of Haskell related help wanted within the FINOS portfolio (and, perhaps optionally, beyond)

An impetus for this discussion was the Kdb meeting on 2020-10-5

Moved to https://github.com/finos/open-developer-platform/issues/179


Add support for GraphQL?

Currently the template sets up a REST api.  However, GraphQL is a great way to build modern web applications.
What this would involve:

Backend: django graphene install and setup
Fronted: React Apollo install and setup

Yes, it would. I have had a look at Apollo recently as I was in a Javascript only environment. I have not used Django Graphene yet on a project. I should do so soon though.


fix(django): Add sync_capable to SentryWrappingMiddleware

Apparently, not having the sync_capable on the SentryWrappingMiddleware sometimes breaks things when we have an async-only middleware, such as ServeStatic.
Fixes #3506

@sentrivana or @antonpirker, do you think we need a test for this? I am not sure how exactly we would test this change

Nice!

do you think we need a test for this? I am not sure how exactly we would test this change

Do we already have any middleware tests? It'd be great to have a test case that sets up a middleware, then inits the SDK, and then checks whether the wrapped middleware has all the expected attributes, including sync_capable.
If there's already a similar test case, we can just add this to it/repurpose that. If we don't have this, that's a blind spot we should fix. But if it's too much effort, you can just create a ticket and eventually we'll get to it during maintenance.

@sentrivana @antonpirker, I added a test. Would appreciate if one of you could check that it looks reasonable


NOSTORY: EKS upgrade.

Description
This PR aims to refactor the eks module as well as add features that were not available. To view a full list of features/changes click on the link below.
Features/Fixes/Patches/Changes list:
Please check the CHANGELOG.md
Checklists:
PR Owners Checklist:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you checked there aren't open Pull Requests of upstream or parallel code that will cause conflicts?
[x] Have you updated the CHANGELOG.md?
[x] Have you updated the README.md(s)?
[x] OWNER: Does your submission pass?

[x] Pre-commit (attach logs/print screen to this PR)
[x] Checkov/terrascan (attach logs/print screen to this PR)
[x] Terraform resources examples build/destroy successfully with Terraform 0.14.11 minimum?

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[] Have you written new tests for your core changes, as applicable?
[x] Have you successfully run tests with your changes locally?

PR Reviewers Checklists?

[] Are all your comments/changes resolved?
[] Are you happy with the OWNER checklists and additional information provided?
[] Does your review tests pass?

[] Terraform resources examples build/destroy successfully with Terraform 0.14.11 minimum?

For checkov logs, some failed checks are from the VPC module. These can be addressed in the current VPC upgrade

Hey @patrickmukumbu can you please confirm that this PR is not only adding the aws_auth config map, right? this PR is adding something else, as I can see. Can you please elaborate a bit more about this? Thanks!
In the other hand, I tried to create the stack with the example provided (without modifying anything) and I got the following error:
│ Error: Missing required argument
│
│   on main.tf line 41, in module "test_eks_cluster":
│   41: module "test_eks_cluster" {
│
│ The argument "role_arn" is required, but no definition was found.

Hey @patrickmukumbu can you please confirm that this PR is not only adding the aws_auth config map, right? this PR is adding something else, as I can see. Can you please elaborate a bit more about this? Thanks!
In the other hand, I tried to create the stack with the example provided (without modifying anything) and I got the following error:
│ Error: Missing required argument
│
│   on main.tf line 41, in module "test_eks_cluster":
│   41: module "test_eks_cluster" {
│
│ The argument "role_arn" is required, but no definition was found.

And also, I though would be good to add the .terraform and .terraform.lock.hcl to the **.gitignore** file. So I went ahead and added it to this PR! let me know if that made sense

Hey @mariomerco . Please edit the source to "../../" in your local machine. The tf registry pointer is meant to be used upon merging. Sorry I forgot to mention this earlier. This applies to the other modules as well
The eks module is still under development so this example only creates the cluster network and eks cluster

checkov.txt
Hey @hugoalmeida264 , here are the checkov logs for eks module.

Found a couple of things in here. Let me know if you agree or not ;)

Hey @mariomerco in addition to the development that Patrick had done, I updated this module and made some changes (a list of the changes can be found in this CHANGELOG.md). Kindly review for me if the changes you had requested were captured.
Thank you.


Temperature and Humidity Sensor

I have several Temperature and Humidity Sensor from Tuya
Manufacturer - Tuya Inc.
Model - bguser20
It is identified as an accessory but the value displayed is the battery level for Temperature and Humidity.

Pkease provide your device's standard instruct and standard status, which can be obtained from tuya platform - device debug, or from homevridge debug logs.

Humidity shows well, temperature 100 degrees for all sensors

Hi @Lopatalo , If something is wrong please give me your device's detail info, thanks

Ahoj@Lopatalo, Pokud je něco špatně, dejte mi prosím podrobné informace o vašem zařízení, děkuji

Product : WIFI温湿度传感器
Device ID : bf9e78fa5d1dd28a7dvfcd
Tuya Inc.
Model : q29ebws5adwye1l8
Firmware : 1.6

I need standard instruct and standard status @Lopatalo

Potřebuji standardní instrukce a standardní status@Lopatalo

Your device seems normal. Can you confirm if it is caused by accessory cache?
To clean the cache, please see:
https://github.com/0x5e/homebridge-tuya-platform/issues/24#issuecomment-1296162250

In Homebridge Web GUI setting page, there's a option to clean accessory cache.

still not working despite removing cache and installing again the Tuya PlugIn.

Lopatalo's device instructions are normal. @Bob1979CAN please provide yours, if clean cache is not useful.

Vaše zařízení vypadá normálně. Můžete potvrdit, zda je to způsobeno mezipamětí příslušenství? Chcete-li vyčistit mezipaměť, viz: #24 (komentář)
Pokud bude čistá mezipaměť fungovat, vyčistím mezipaměť pokaždé po upgradu pluginu.

Clearing the cache didn't help. Still the same problem.

Well, I have no idea now... I will add some logs next version and can you open the debug mode and upload the logs? Thanks.

I think this is just an api mapping issue.

I think this is just an api mapping issue.

Yes, I need some log, every type have different products and my virtual sensor works well, I need logs for the non-working device.

Same problem T&H sensor shows temperature 100. Humidity correct. Clean up cache not help.

@0x5e

I think this is just an api mapping issue.

Yes, I need some log, every type have different products and my virtual sensor works well, I need logs for the non-working device.

I have the same issue. Here is the relevant log from the api response
TuyaOpenAPI response: path = /v1.0/homes/69714089/devices, data = {"result":[{"active_time":1667236305,"biz_type":0,"category":"wsdcg","create_time":1667234720,"icon":"smart/icon/ay1525749833414yotNt/d9d4ceec63cb81ff6e8c8d6c2fb4edb3.png","id":"*********","ip":"*********","lat":"","local_key":"*******","lon":"","model":"TH01 CB3S","name":"My sensor","online":true,"owner_id":"******","product_id":"lf36y5nwb8jkxwgg","product_name":"T & H Sensor","status":[{"code":"va_temperature","value":255},{"code":"va_humidity","value":51},{"code":"battery_state","value":"high"},{"code":"temp_unit_convert","value":"c"}]
I removed some private data, but you can still see the values.
For me the humidity shows as expected, but the temperature stays at 100

I looked at the code, it looks like at TemperatureHumiditySensorAccessory.ts you are using Math.Min in order to make sure it stays within limit. but the API reports the current temperature without a decimal point (Instead of 25.5C it reports 255C).
So when you're doing Math.Min to the temperature value and 100, it will always be 100.
I think this is the bug's origin. Hope I could help a little :)

I looked at the code, it looks like at TemperatureHumiditySensorAccessory.ts you are using Math.Min in order to make sure it stays within limit. but the API reports the current temperature without a decimal point (Instead of 25.5C it reports 255C).
So when you're doing Math.Min to the temperature value and 100, it will always be 100.
I think this is the bug's origin. Hope I could help a little :)

In my case, real value is 21.7... I think 100 is the battery level...

In my case, real value is 21.7... I think 100 is the battery level...
Even so. If the real value is 21.7, the api will report it as 217, and when Math.Min will get 100 (Const value) and 217 (Real temperature value) it will return 100. Mine is still reporting 100 even though my battery level is not 100%

You right!
Please prompt me, where I can open source code and add divide to ten...

I have a similar issue. Temperature and Humidity Sensor shows up in homekit as Temperature sensor only with 100 degrees.
Please see below device details.
"category": "wsdcg",
"functions": [
{
"code": "temp_unit_convert",
"lang_config": {
"c": "℃",
"f": "℉"
},
"name": "Temp unit convert",
"type": "Enum",
"values": "{"range":["c","f"]}"
}
],
"status": [
{
"code": "va_temperature",
"lang_config": {
"unit": "℃"
},
"name": "Temperature",
"type": "Integer",
"values": "{"unit":"℃","min":-200,"max":600,"scale":1,"step":1}"
},
{
"code": "humidity_value",
"lang_config": {
"unit": "%"
},
"name": "Current Humidity",
"type": "Integer",
"values": "{"unit":"%","min":0,"max":100,"scale":0,"step":1}"
},
{
"code": "temp_unit_convert",
"lang_config": {
"c": "℃",
"f": "℉"
},
"name": "Temp unit convert",
"type": "Enum",
"values": "{"range":["c","f"]}"
}
]
},

Thanks for providing the informations. So this issue is similar to Smart Heater
https://github.com/0x5e/homebridge-tuya-platform/discussions/2#discussioncomment-3990021
We always miss the scale option, scale=1 means we should divide the value by 10^1, scale=0 means divide by 10^0.

Last update beta 1.9 not solve the problem with T&H sensor. Temperature still 100.

@MarshallGary do you know how to clone and run plugin locally?
The code is here:
https://github.com/0x5e/homebridge-tuya-platform/blob/develop/src/accessory/TemperatureHumiditySensorAccessory.ts#L17-L23
First we get the va_temperature's function property, it should be like this:
{
  unit: "℃",
  min: -200,
  max: 600,
  scale: 1,
  step:1
}

The min & max can be ignored because HomeKit has it's on min & max of -270 and 100.
https://developers.homebridge.io/#/service/TemperatureSensor
The temperature value is from this.device.getDeviceStatus('va_temperature').value and we should / Math.pow(10, property.scale) before use.
Finally if it still out of [-270, 100] then we strip it.
Please help review and running locally if anyone can, thanks :)

@MarshallGary do you know how to clone and run plugin locally?
The code is here: https://github.com/0x5e/homebridge-tuya-platform/blob/develop/src/accessory/TemperatureHumiditySensorAccessory.ts#L17-L23
First we get the va_temperature's function property, it should be like this:
{
  unit: "℃",
  min: -200,
  max: 600,
  scale: 1,
  step:1
}

The min & max can be ignored because HomeKit has it's on min & max of -270 and 100. https://developers.homebridge.io/#/service/TemperatureSensor
The temperature value is from this.device.getDeviceStatus('va_temperature').value and we should / Math.pow(10, property.scale) before use.
Finally if it still out of [-270, 100] then we strip it.
Please help review and running locally if anyone can, thanks :)

  I don't know how to clone and run. Please help me, I will send you all needed feedback.

That's a bit difficult to say all the steps in English for me, mostly you can refer this readme to start a plugin develop environment:
https://github.com/homebridge/homebridge-plugin-template
Then you may add some logs before or after the code around va_temperature, or I will submit a debug branch for you later.

That's a bit difficult to say all the steps in English for me, mostly you can refer this readme to start a plugin develop environment: https://github.com/homebridge/homebridge-plugin-template
Then you may add some logs before or after the code around va_temperature, or I will submit a debug branch for you later.

English is non-native for me too.
Open repository created from template: https://github.com/MarshallGary/TuyaPlatform-T-and-H-sensor

read https://github.com/homebridge/homebridge-plugin-template/blob/master/README.md
but clone https://github.com/0x5e/homebridge-tuya-platform develop branch instead :)

What about this, you create a new account and pair sensor into the account, and provide the username and password to me, let me debug remotely.

I managed to create a accuracy 0.1 device and have known where the problem is. I can't get va_temperature's scale from /v1.0/devices/functions. I need some core modification.

I managed to create a accuracy 0.1 device and have known where the problem is. I can't get va_temperature's scale from /v1.0/devices/functions. I need some core modification.

How I can help you?

It's complicate to say, I can handle this, thanks @MarshallGary .
In the history there's no 'functions' and 'specification' things, they are almost the same thing, just different in write and read. Now the API seperate them then makes me difficult to process.

Please try beta.20, should fixed now.

Please try beta.20, should fixed now.

It works for me

Please try beta.20, should fixed now.

Yeah!!! Temperature is correct!!! Thank you so much!!!

Please try beta.20, should fixed now.

Yeah!!! Temperature is correct!!! Thank you so much!!!

Temperature and humidity are not updated in homebridge. Still the same data.

Updated to Beta.20 temperature shows correctly in homekit. Many thanks
Any possibility of exposing the Humidity Sensor to homekit.

Updated to Beta.20 temperature shows correctly in homekit. Many thanks
Any possibility of exposing the Humidity Sensor to homekit.

If still not working, please provide homebridge debug log

Even after 24 hours, the status of the sensors in hombridge has not been updated.

@Lopatalo1976 We need useful information to solve this problem, "My device is not working" can't help.

log.txt

@0x5e temperature sensor is working fine, humidity sensor is not appearing. Please see below logs, let me know if this is enough
[2022-11-03, 9:48:56 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667483337}
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=undefined, t=1667483337, 1970-01-20T07:11:23.337Z
currentMessage: dataId=28d26f2d-0d09-4c47-afa7-f401a416e320, t=2, 1970-01-01T00:00:00.002Z
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=12d577b6-9744-49dc-bd93-579513dfa759, t=1667483337, 1970-01-20T07:11:23.337Z
currentMessage: dataId=47b85aa5-2ace-48fb-8a22-25fee8245cd1, t=1667483336, 1970-01-20T07:11:23.336Z
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=71585394-ba2a-41dc-84aa-61f59d86d3fe, t=1667483337, 1970-01-20T07:11:23.337Z
currentMessage: dataId=baf645b7-37bb-41eb-b4c8-dc5063708701, t=1667483336, 1970-01-20T07:11:23.336Z
[2022-11-03, 9:48:57 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 9:56:21 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=offline, bizData={"time":1667483781}
[2022-11-03, 9:56:37 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667483797}
[2022-11-03, 9:57:36 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=offline, bizData={"time":1667483857}
[2022-11-03, 9:57:46 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667483866}
[2022-11-03, 9:59:38 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=e4dedffd-fb85-496f-984d-46e32997ba79, t=1667483978, 1970-01-20T07:11:23.978Z
currentMessage: dataId=555c71dc-2ae0-41be-9d82-125c3b818392, t=1667483977, 1970-01-20T07:11:23.977Z
[2022-11-03, 9:59:38 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 9:59:38 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=e4dedffd-fb85-496f-984d-46e32997ba79, t=1667483978, 1970-01-20T07:11:23.978Z
currentMessage: dataId=5aff1602-36bd-46e9-a1ee-5f646475b020, t=1667483977, 1970-01-20T07:11:23.977Z
[2022-11-03, 9:59:38 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:00:53 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=b710bf59-b66b-4327-aef2-946c285bc7cb, t=1667484053, 1970-01-20T07:11:24.053Z
currentMessage: dataId=fcb46cc8-0627-4aaf-a7f7-b3cee7145367, t=1667484052, 1970-01-20T07:11:24.052Z
[2022-11-03, 10:00:53 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:00:53 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=b710bf59-b66b-4327-aef2-946c285bc7cb, t=1667484053, 1970-01-20T07:11:24.053Z
currentMessage: dataId=43ac7cc7-a245-43a9-a929-72d9f5bf2bac, t=1667484052, 1970-01-20T07:11:24.052Z
[2022-11-03, 10:00:53 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:01:36 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667484097}
[2022-11-03, 10:01:37 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=undefined, t=1667484097, 1970-01-20T07:11:24.097Z
currentMessage: dataId=e45db8b4-d315-4854-8c9f-e6c6ce307978, t=2, 1970-01-01T00:00:00.002Z
[2022-11-03, 10:01:37 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:02:01 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667484121}
[2022-11-03, 10:02:01 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=undefined, t=1667484121, 1970-01-20T07:11:24.121Z
currentMessage: dataId=245b6e36-66d4-49fe-9a98-c13a50b3277d, t=2, 1970-01-01T00:00:00.002Z
[2022-11-03, 10:02:01 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:04:27 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667484267}
[2022-11-03, 10:04:28 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=undefined, t=1667484267, 1970-01-20T07:11:24.267Z
currentMessage: dataId=0df43097-bfee-4e4b-a30b-dab390325fb7, t=2, 1970-01-01T00:00:00.002Z
[2022-11-03, 10:04:28 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[2022-11-03, 10:04:45 a.m.] [@0x5e/homebridge-tuya-platform] Unhandled mqtt message: bizCode=online, bizData={"time":1667484285}
[2022-11-03, 10:04:46 a.m.] [@0x5e/homebridge-tuya-platform] TuyaOpenMQ warning: message received with wrong order.
lastMessage: dataId=undefined, t=1667484285, 1970-01-20T07:11:24.285Z
currentMessage: dataId=30d37502-a300-476d-8207-1fc66cc61951, t=2, 1970-01-01T00:00:00.002Z
[2022-11-03, 10:04:46 a.m.] [@0x5e/homebridge-tuya-platform] Fallback to use API fetching the latest device status.
[11/3/

@Lopatalo @Lopatalo1976  are you the same one?
From the logs:
[03/11/2022, 20:08:44] [TuyaPlatform] TuyaOpenAPI response: path = /v1.0/iot-03/open-hub/access-config, data = {"code":28841101,"msg":"No permissions. This API is not subscribed.","success":false,"t":1667502524334,"tid":"efbe6f5b5baa11ed8a25fe1b67a66e75"}

You need to subscribe the following APIs at "Tuya IoT Platform -> Cloud -> Development -> Project -> Service API":

Authorization Token Management
Device Status Notification
IoT Core

Unless it can't receive device status message.
And I will add some logs and instructions when receiving 28841101 error.

@hotbird1970 Please enable the debug mode before getting logs. I need to see your device detail and logs.
I've updated the Troubleshooting recently:
https://github.com/0x5e/homebridge-tuya-platform#troubleshooting

@0x5e  Please let me know if this is enough.
"status": [
{
"1": 209,
"code": "va_temperature",
"t": "",
"value": 209
}
]
}
[2022-11-04, 6:32:09 p.m.] [@0x5e/homebridge-tuya-platform] CurrentTemperature: property = { unit: '℃', min: -200, max: 600, scale: 1, step: 1 } multiple = 10 status = { code: 'va_temperature', value: 209 }
[2022-11-04, 6:32:09 p.m.] [@0x5e/homebridge-tuya-platform] Update value 20.900000000000034 => 20.9, subtype=undefined, characteristic=00000011-0000-1000-8000-0026BB765291
[2022-11-04, 6:32:09 p.m.] [@0x5e/homebridge-tuya-platform] [TuyaOpenMQ] onMessage:
protocol = 4
message = {
"status": [
{
"2": 55,
"code": "humidity_value",
"t": "",
"value": 55
}
]
}

Enough, your humidity code is different than others. Will be added in next beta.

Please try the latest version and if problem still exists, please tell me. @hotbird1970

everything is working great. Thanks @0x5e !!

Yes, both Temperature and Humidity Sensors now show on homekit
working great thank you

Is there a way to configure the timing to pull the update from tuya platform. It seems to me that the temperature is not updated very often in home app (maybe every hours)

There's no need to set pull interval, because mqtt is an long connection and it can receive state change immediately. If you can't receive state update, please open an new issue and paste your logs.


nixos/syncthing: match stale ids by subtracting in jq

Description of changes
https://github.com/NixOS/nixpkgs/issues/259256

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

another problem which is not fixed here: it's not possible to delete folders with a / in the ID

hmm, it seems like this approach is flawed. In the frontend the PUT endpoint is used, since that one is capable of escaping the IDs correctly. I guess we should do the same?

I removed the 2nd commit from this PR. And marked this PR to fix #259256. Will open a new issue for the curl -X DELETE topic downstream and upstream today.

@ofborg test syncthing
@ofborg test syncthing-init
@ofborg test syncthing-no-settings


improve code style

Even though pylint's score is > 9, it reports several issues: reusing identifiers in different scopes and check_tree has too many statements, benches and local variables. This will require breaking up the check into different functions.

Is the PEP 8 style guide the ideal we should be aiming for in this project? Should this be the document I turn to when considering all things style related? I noticed that a couple of doc-strings etc have been modified and I would like to get them right the first time, does this document guide your choices for that kind of thing?

PEP 8 is for code and PEP 257 is about docstrings. The best is to use a tool like pylint or flake8 to check the style. Can't remember if either of them automatically uses pydocstyle.

Thanks for this. Internal functions have many global variables that can trip one up when reading the code. External functions will have more arguments. Maybe a class is the way to go with one public method check and several private methods _check_op etc.  The location and add_error methods can probably be merged into a single private one.
I think your else loop handling needs fixing, because the OPTIONS have "for else" and "while else".
The main loop could become
if isinstance(node, NO_LINE):
    pass
elif handler := node_handlers.get(type(node)):
    handler(node)
elif not ...

However, I wonder if this will be too many changes for just removing two pylint messages, i.e. low ROI. Maybe better to do all the refactoring after the tool can be installed with pip and it doesn't matter whether the tool is made of 1 or 10 files.

Good spot with handle_loop_else probably could be fixed with something simple like
def handle_loop_else(node, loop_type: str) -> None:
        if node.orelse and loop_type + " else" not in options:
            message = f"else in {loop_type}-loop"
            add_error(node.orelse[0], message)

Yes, waiting until #11 is completed is probably the best course of action now you mention it. I am assuming that we can also remove a lot of the import conditionals once pip is up and running.  In a way it is low ROI, but the returns I am getting in education are quite high :smile:


Use proper locks when modifying alert status

Read locks are used, which will cause panics @fabxc @stuartnelson3
fatal error: concurrent map read and map write

goroutine 58 [running]:
runtime.throw(0x9fdd14, 0x21)
	/home/lukasz/usr/go/src/runtime/panic.go:596 +0x95 fp=0xc42058e730 sp=0xc42058e710
runtime.mapaccess2_fast64(0x946e20, 0xc4201472f0, 0x24e4121619386f95, 0xffffffffffffffff, 0xc42058e798)
	/home/lukasz/usr/go/src/runtime/hashmap_fast.go:168 +0x1b2 fp=0xc42058e758 sp=0xc42058e730
github.com/prometheus/alertmanager/types.(*memMarker).SetSilenced(0xc42014cb80, 0x24e4121619386f95, 0x0, 0x0, 0x0)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/types/types.go:115 +0x92 fp=0xc42058e7a8 sp=0xc42058e758
github.com/prometheus/alertmanager/notify.(*SilenceStage).Exec(0xc4201d8620, 0xc7a360, 0xc4200f3bf0, 0xc4200caf40, 0x3, 0x4, 0xc7a360, 0xc4200f3bf0, 0xc4200caf40, 0x3, ...)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/notify/notify.go:360 +0x2dd fp=0xc42058e8a8 sp=0xc42058e7a8
github.com/prometheus/alertmanager/notify.MultiStage.Exec(0xc42023d410, 0x3, 0x3, 0xc7a360, 0xc4200f3bf0, 0xc4200cad40, 0x3, 0x3, 0xc4200f3b01, 0x91cfa0, ...)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/notify/notify.go:259 +0xa5 fp=0xc42058e930 sp=0xc42058e8a8
github.com/prometheus/alertmanager/notify.(*MultiStage).Exec(0xc4201d86c0, 0xc7a360, 0xc4200f3bf0, 0xc4200cad40, 0x3, 0x3, 0xffffffffffffffff, 0xc42058ea40, 0x7252d5, 0xc420232640, ...)
	<autogenerated>:6 +0xad fp=0xc42058e9b8 sp=0xc42058e930
github.com/prometheus/alertmanager/notify.RoutingStage.Exec(0xc42023d380, 0xc7a360, 0xc4200f3bf0, 0xc4200cad40, 0x3, 0x3, 0x6, 0x91e020, 0xc4200135e0, 0xc420014b40, ...)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/notify/notify.go:245 +0xde fp=0xc42058ea30 sp=0xc42058e9b8
github.com/prometheus/alertmanager/dispatch.(*Dispatcher).processAlert.func1(0xc7a360, 0xc4200f3bf0, 0xc4200cad40, 0x3, 0x3, 0x2)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/dispatch/dispatch.go:264 +0x86 fp=0xc42058eae8 sp=0xc42058ea30
github.com/prometheus/alertmanager/dispatch.(*aggrGroup).run.func1(0xc4200cad40, 0x3, 0x3, 0x2)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/dispatch/dispatch.go:372 +0x58 fp=0xc42058eb28 sp=0xc42058eae8
github.com/prometheus/alertmanager/dispatch.(*aggrGroup).flush(0xc420192360, 0xc42058ef20)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/dispatch/dispatch.go:432 +0x47f fp=0xc42058ed80 sp=0xc42058eb28
github.com/prometheus/alertmanager/dispatch.(*aggrGroup).run(0xc420192360, 0xc4201de480)
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/dispatch/dispatch.go:373 +0x88c fp=0xc42058efd0 sp=0xc42058ed80
runtime.goexit()
	/home/lukasz/usr/go/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc42058efd8 sp=0xc42058efd0
created by github.com/prometheus/alertmanager/dispatch.(*Dispatcher).processAlert
	/home/lukasz/work/go/src/github.com/prometheus/alertmanager/dispatch/dispatch.go:269 +0x32c

Hmm, CI is taking long, might be that there's a lock that's not getting released and blocking

Oh, that's likely because SetSilenced can call SetActive, which also does the locking

Updated and now passing tests

Should this get merged and 0.6.2 be released?

I would hope so, I'm sure @fabxc will review this when he gets a chance, until that happens it's best to stay on 0.6.0 which shouldn't have any issues

Sorry about not being responsive. LGTM

Does this issue justify a new 0.6.x release?


Create .NET Core/Visual Studio Code cross-platform setup instructions

Inspired by #38, esp. comments by @NobbZ and @ErikSchierboom -
I'm running .NET Core and Visual Studio Code on Ubuntu and it's a dream. Way nicer for doing exercism exercises than the ceremony and overkill of Visual Studio, and it's easily installed on Windows, OS X, and Linux... https://www.microsoft.com/net/core#linuxubuntu has dead simple instructions and ends with a link to download VS Code...
I think it might be well worth doing a cross-platform howto with a unified workflow, then have Visual Studio / Xamarin as an advanced/alternative option; VS and MonoDevelop are fine for people who are already using them, but with the amount of HALP! requests getting started w/ C# and/or F# on Gitter, streamlining the process with uniform, open-source tools (and without the heavyweight IDEs) seems like a good way to lower the barrier to entry for new users.

I totally agree! And it is something we are planning on doing, it's just that the .NET Core stuff is still quite a bit in flux. At the moment, Microsoft is working hard to complete the work of reverting he project system to MSBuild (instead of project.json). When that is finished, we will be porting all the exercises over to work on .NET Core with all the added benefits.
For some more information, see #138.

I'll keep an eye out for when the xcsharp maintainers feel it's mature enough, I'd be happy to help with the porting process. Thanks!

@canweriotnow Great! We'll post any updates here. By the way, if you're interested in tracking the work Microsoft is doing, you can check the CLI and MSBuild repositories.

As a reminder, we will be updating the docs as part of #200. We should be adding docs for the following scenarios:

Running from the command-line using the .NET CLI
Running from Visual Studio
Running from Visual Code
Running from Visual Studio for Mac
Running from Project Rider

It might seem a bit much, but I think this will be worthwhile.

I've updated the .NET Core PR with some initial docs on how to install or run the tests. If anyone would read and check them, that would be great! Here are the direct links to the files:

INSTALLATION.md
TESTS.md

I've opted to not have detailed instructions on how to run the tests in the various IDE's, as most other language tracks also don't do it. It's also much easier for us maintainers if we have a single, supported way to run the tests. In our case, I opted for the .NET CLI option for three reasons:

It's very simple
It's similar to how other languages run their tests
It's cross-platform (meaning we don't have to duplicate documentation)

CC: @canweriotnow @GalaDe @robkeim @balazsbotond @bressain @jmbradnan

@ErikSchierboom I just had a quick look through the documentation and it looks good! Thanks for all of your work on this.

@robkeim Thanks! Tomorrow is the Visual Studio 2017 and .NET CLI 1.0 launch. If everything runs fine on those release versions, I'll (finally) merge the .NET Core PR. Would be great to finally have it working. We can then work on further polishing the track. I've actually did some thinking a found lots of ways we can improve things even more. For all of these ideas, I've created a new issue.

@canweriotnow With #199 merged, I think this issue can now be closed. To be clear, we've updated the track to be based on the .NET CLI, which is cross-platform and thus has the same interface on all platforms. You should thus now have things nicely working on .NET Core!


Update SearchTextField.swift

Add an id attribute to the SearchTextFieldItem

I think we are probably trying to do the same thing. I just submitted a related issue:
https://github.com/apasccon/SearchTextField/issues/68
As soon as you add an ID you might realize you want to add more things.  Do you think making the SearchTextFieldItem into a class so it can be extended would address your use case too?

hey people!, now in 1.1.7 version the SearchTextFieldItem is an extendable class. Thanks for the suggestions!.

@btanner yes this worked perfectly for me, good suggestion!


Update integration test CI

Description of changes
Updates to CI to enable running the integration tests from the cedar-integration-tests repository.
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[X] A change "invisible" to users (e.g., documentation, changes to "internal" crates like cedar-policy-core, cedar-validator, etc.)

I confirm that this PR (choose one, and delete the other options):

[X] Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

[X] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

Marking as ready for review because it seems to be working with cedar-integration-tests#3. The corpus tests are currently failing, but that's a separate issue not related to this change.


[FIX] Ability to split emails with large recipient counts

I suspect James could struggle in distributed version to distribute very large count of recipients To this end, splitting email would help.
This is a default Postfix behaviour.

The code snippet is extracted from MailToAllUsers mailet.

Still missing doc changes for MailToAllUsers.adoc, as it does not send mails in batches anymore


I can't find Labyrinth Enchantment

I can't find Labyrinth Enchantment, in unique helms

Can you copy-paste the item in a new reply (please use a code-snipped to preserve formatting)

I've searched for the stat on the PoE trade website and it should be fixed in the next release:

This issue has been fixed in v0.7.3


Fix missing codename arguments

Closes #149 and #150

bumping this @krobertson have you considered merging this PR?

I am hitting this as well.

Patch applied to my local installation allowing successful verification on my buckets.

Tested on my local machine, can confirm this patch is working with my local ruby env v2.7.0.


Add more functions to File::Spec implementation

Add more functions to File::Spec implementation.  Specifically splitpath, splitdir, curdir, and updir are used by File::Path and need to be implemented before that module is translated.

Fixed in v0.971


Map/4 (Rough) location tracking

As a user I need to know where I am. If I know my rough location, I can navigate easily if I know where I want to go.

The positioning should be as exact as possible, there will be limitations by GPS/Galileo.

The location should be shown in the map, the option to toggle it is necessary, especially not to interfere with the offline map. just for perspective, navigation will be a project in the future, it is also integrated in leaflet (as far as I know).


Py module macro

Codecov Report

Merging #513 into master will decrease coverage by 0.07%.
The diff coverage is 76%.

@@            Coverage Diff             @@
##           master     #513      +/-   ##
==========================================
- Coverage   54.07%   53.99%   -0.08%
==========================================
  Files          67       67
  Lines       12948    12964      +16
  Branches     3146     3148       +2
==========================================
- Hits         7001     7000       -1
- Misses       4138     4155      +17
  Partials     1809     1809

Impacted Files
Coverage Δ

vm/src/macros.rs
14.28% <ø> (ø)
:arrow_up:

vm/src/stdlib/random.rs
0% <0%> (ø)
:arrow_up:

vm/src/stdlib/math.rs
30.87% <84.44%> (-2.47%)
:arrow_down:

Continue to review full report at Codecov.

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

I did something similar in #247, this looks a bit less "magic" (which is a good thing).

I quite liked the very magic version. :)
I hope the simpler version is a reasonable compromise.

These coverage reports are interested. I've decreased coverage despite not adding any new code.

Yeah, I think it counts macro bodies and comments against you. :disappointed:

As the main person against too much macros, I approve of this macro!


add go jenkins file - build should not trigger

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Test comment

please run test

run test

run test


Unique id in balance.update

There is rather specific problem with lack of unique id's in balance.update - it leads React application to rerender the whole array of entries because keys are not unique.
I'm convinced that besides React it might lead to problems in other cases, for example caching or logging.
Also it's a bit inconsistent with deals and orders :)

I was plan to add an balance history uniq id.

So is there any update on this?


chore(): ungulpify

adds types, prettier, lint-staged, CI, usual suspects
typechecking is disabled; fixes for types should be in another PR (likewise formatting)

Current dependencies on/for this PR:

master

PR #6   👈

PR #7

This comment was auto-generated by Graphite.

just reopening #4 so I can stack PRs on it

fwiw I'm not eager to merge this until I can run some E2E tests, which I hope to get setup today


Support Elasticsearch 7.10

Issue #, if available:
Description of changes:
Support Elasticsearch 7.10
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks good


dev test: Center and Spread 1.0.0-dev.11

Dev Test
Simulation links

github repository for issues
phet top level directory
sim: all_phet.html
phet-io wrapper index

Test Matricies
Please include (non-screen reader) a11y testing in these records if applicable.

[x] Latest macOS, Safari (Time =  3hrs)
[x] Windows 10, Chrome (Time = 3.5)
[x] Windows 10, Firefox (Time = 3hrs)
[x] Latest iOS, Safari (Time = 1.5)
[x] Windows 11, Chrome (Time = 3)

Light testing, or optionally skip if time crunch:

[x] Latest macOS, Chrome (Time = 2hrs)
[x] Latest Chrome OS, Chrome (Time = 1.5hrs)

If PhET-iO is being tested:

[x] Latest macOS, Safari (Time = 2.5hrs)
[x] Windows 10, Chrome (Time = 5.5)
[x] Windows 10, Firefox (Time = 3.5hrs)
[x] Latest iOS, Safari (Time = .5)
[x] Windows 11, Chrome (Time = 2)

Features included

[x] PhET-iO
[x] Alternative Input
UI Sound
Sonification
Description
Voicing

Focus and Special Instructions
This sim is going to be used as a dev version for a classroom starting in April. Please thoroughly test phet brand.
phet-io is included but we have not tested it thoroughly and haven't spent time designing the tree. Please report any issues related to phet-io, but if there's a large blocking problem, don't worry about testing around it until it's fixed.
Also, please assign issues to me and @samreid.

For QA...

General features

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Run through the string tests on at least one platform, especially if it is about to go to rc.
Check the Game Up harness on one platform.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have
all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the
a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and
descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
this Google Document. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

QA is done


Fix spelling

Those uses of 'iff' may be deliberate: https://en.wikipedia.org/wiki/If_and_only_if

@seanm Ah, sorry. Didn't know that.


game crashing

crash-2016-10-24_14.10.45-server.txt
latest forge, minecraft 10.2, latest mod version

Under what circumstance does this happen as this report is useless without context as it references vanilla code only.

No reply so closing.


Reproducer for HHH-18285 on branch 6.5 - Non-polymorphic embeddable inheritance fails starting with Hibernate ORM 6.6

https://hibernate.atlassian.net/browse/HHH-18285
Not a fix, just a reproducer.  Same reproducer as #8586 , but on branch 6.5.
This shows the use case was working in Hibernate ORM 6.5.

Closing since this was fixed via https://github.com/hibernate/hibernate-orm/pull/8608


Migrate html text to own markdown files

Migrate html text to own markdown files, in a single location. Make it easier for Marketing peeps to edit website text.
cc @jsfowles
original: https://jira.numenta.com/browse/WEB-172

Rough plan how this would work:
https://github.com/numenta/numenta-web/pull/135


逸出字元"\S"問題詢問

@yuyueh commented on Wed Jul 04 2018
您好。本頁介紹中提到的逸出字元"\S"，最後"int _ctr"符合的結果應為" _"而非" "。

文件詳細資料
⚠ 請勿編輯此區段。 這是 docs.microsoft.com ➟ GitHub 問題連結的必要項。

ID: 16d4698e-4220-c422-a554-8a481803d240
Version Independent ID: f0e3b82a-8d81-ad9e-97fc-efb92f7d0d38
Content: 規則運算式語言 - 快速參考
Content Source: docs/standard/base-types/regular-expression-language-quick-reference.md
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

Translation: Hello. The escape character "\S" mentioned in the introduction to this page, and finally "int ctr" should match the result "" instead of " ".

This is not a source. It has been fixed in zh-TW repository, but only not been released yet.

This was a localization issue that's been fixed. Closing.


Use micromamba  on the CI instead of setup-python

Done for part of it that makes sense https://github.com/jupyterlite/xeus-python-kernel/blob/main/.github/workflows/build.yml#L21


Credit Transactions | Adjustments to the PVR feature |2|

Task:
This card is to make several adjustments to the PVR feature. Currently, the PVR feature allows the government analyst to initiate three transaction types: Part 3 Award, Validation and Reduction. Validations and reductions are tied to compliance reporting and that feature will be handling those items directly through the compliance reporting government-side workflow. Therefore, we need to make a few adjustments to the existing PVR feature to account for these upcoming changes.
New Credit Transaction button:

IDIR user
Current location: Credit Transactions page
New location: SFS page
Update the label to read "New Part 3 Award"
screenshot attached

New Credit Transaction heading:

IDIR user, New Credit Transaction page
Update the heading to read "New Part 3 Award"

Transaction Type:

IDIR user, New Credit Transaction page
Part 3 Award should be the only available transaction type
Validation and Reduction options should be removed

Recommend for Approval button:

IDIR user, New Credit Transactions page
Confirmation alert text should be updated to read: "Are you sure you want to recommend approval of this Part 3 Award?"

Recall as Draft button:

IDIR user, PVR transaction view page, Gov't analyst role, Reviewed/Recommended status, Recall as draft button
Change button label to "Retract Recommendation"
Confirmation alert when clicking on the Retract Recommendation button should be updated to read: "Are you sure you want to retract your recommendation of this Part 3 Award? This will return the transaction to a draft state where it will no longer be visible to the Director."

Return to Analyst button:

IDIR user, PVR transaction view page, Director role, Reviewed/Recommended status, Return to Analyst button
Confirmation alert when clicking on the Return to Analyst button should be updated to read: "Are you sure you want to return this Part 3 Award transaction to the Government Analyst?"

Approve button:

IDIR user, PVR transaction view page, Director role, Reviewed/Recommended status, Approve button
Confirmation alert when clicking on the Approve button should be updated to read: "Are you sure you want to approve this Part 3 Award?"

Decline to Approve button:

IDIR user, PVR transaction view page, Director role, Reviewed/Recommended status, Decline to Approve button
Update warning message to reflect Part 3 Agreement language (see attached screenshot). Note: unlike the text within the screenshot, please ensure adequate spacing between the two paragraphs.
Confirmation alert when clicking on the Approve button should be updated to read: "Are you sure you want to decline to approve this Part 3 Award?"

https://trello.com/c/LZ3L77xQ/1642-credit-transactions-adjustments-to-the-pvr-feature-2

 Credit Transactions | Adjustments to the PVR feature |2|


Rename the project from Repoman to Repoaudit

Repoaudit is slightly more descriptive of what the
project actually does (it audits repositories).

Do you think the lower-case version should be changed to repo-audit as well, or can it stay as repoaudit?


SSL-Inspection: no internet connection for Android Devices

If setting up ssl-inspection in squid, i get no internet connection on Android devices. Windows and Linux (WLAN and LAN) work flawlessy.
Perhaps an issue about connectivitycheck.gstatic.com/gen_204 (and others)?
Thx,
Roger

This is most likely an certificate issue.
For clarification: What do you mean by "i get no internet connection"?
Is Android saying you don't have connectivity?
Is DNS not working (can you go to http://<IP_ADDRESS>)?
How did you configure the forward proxy exactly?

Try this:
Check "Enable SSL inspection"
Check "Log SNI information only"
That should enable "SSL Peek and Splice".
This allows Squid to extract the domains from the traffic (and enforcing ACLs) without actually breaking the encryption.
"Bumping" ("Enable SSL inspection" without "Log SNI only", also known as MiTM) is something you don't want to do, except you really know what you're doing and know why you're doing it (regulatory compliance f.ex.). You're heavily degrading the security and privacy by doing so.
It also breaks sites that use certificate pinning, I'd expect that you'll find most "common" services unusable.

Hi all,

i will look for a tcpdump
No certificate of the CA is installed
I putted connectivitycheck.[android][google].com and play.googleapis.com in ssl bump host list, also .1e100.net...nothing helped.

meanwhile i leave it on sni.

Maybe it is HTTPS so the connection fails if the certificate is not trusted.

Can be resolved, if entered the following in the no ssl bump sites of the forwarding tab:
.google.[your own country]
.google.com
.googleapis.com
.gstatic.com
.1e100.net
Do not forget to install CA as "VPN and Apps"

Thank you for the follow up and solution. 😊

@fichtner maybe that should be added to the docs.

@ruggerio I made a short Note for the docs in that special case. Can you review opnsense/docs#21 please?

It's ok! Thats how i got it working (tested, i deleted everything und putted it in step by step in several mixtures).

@fabianfrz it's probably worth noting that since Android Nougat this no longer works; Android by default tends to ignore User loaded CA certs and only honour the ones in System - making interception virtually impossible on Android.


Remove old reference to MVC namespace for Authorize

@Rick-Anderson @rachelappel @blowdart

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

:shipit:


propel build - whitespace on windows

When I do build on Windows using PHP 5.6.21 all generated files keep trailing whitespaces whereas on Linux I get all trailing whitespaces removed. I suspect that regex from here
https://github.com/propelorm/Propel2/blob/master/src/Propel/Generator/Builder/Om/AbstractOMBuilder.php#L1029
is not working OK on windows as far as my tests displayed.

I believe most of us in the team don't have windows. Care to fix it and create a pull-request?

git? autocrlf enabled? ;)

@modmanx were you able to solve it? I experience the same issue. What is more interesting is that I'm having my project in the docker container; building propel objects from inside the Linux container. @schursin it is not related to EOF character. Simple SOME extra "spaces" are added.

Is someone able to make a PR here with suggested changes?

g propel objects from inside the Linux container. @schursin it is not related to EOF character.  Simple SOME extra "spaces" are added.

add this program dos2unix to your dockerfile and run this script it before performing the migrations
// run inside propel directory
find . -type f -print0 | xargs -0 dos2unix

this should help you


oppetarkiv

oppetarkiv change url and redirects from oppetarkiv.se to https://www.svtplay.se/kategori/oppet-arkiv so the scraper no longer works

Thanks for letting me know, I've made some changes and pushed a new commit. Let me know if all is fixed. : )


fix(console): ui issues

adds info for user if no secret is provided on app create

Closes #1640
Closes #1642
Closes #1638
Closes #1671

:tada: This PR is included in version 1.2.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚡Use min solidity version 0.8.19

Description
Solidity version 0.8.19 has the fix "Assembler: Avoid duplicating subassembly bytecode where possible", which is good for deployment size/gas
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

It is intentional that the minimum solc is 0.8.4. Devs can configure their desired compilation version in their foundry.toml file.


Can add, edit and delete tasks, reorder tasks, and track tasks

I decided to work on this again and I think it is closer to what we imagined. I have the live site made with this branch if you want to have a look at what I've updated :D

Niceeeee!! Happy to jump on and help!
On Tue, 18 Jun 2024 at 16:32, Sean Meade @.***> wrote:

@sean-meade https://github.com/sean-meade requested your review on: #84
https://github.com/sean-meade/rise-and-reflect/pull/84 Can add, edit
and delete tasks, reorder tasks, and track tasks.
—
Reply to this email directly, view it on GitHub
https://github.com/sean-meade/rise-and-reflect/pull/84#event-13203075866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6RW4ZYCVMV4LAWBPSDUYJTZIBHKDAVCNFSM6AAAAABJQJIOSSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGIYDGMBXGU4DMNQ
.
You are receiving this because your review was requested.Message ID:
@.***>

@pjrclarke https://rise-and-reflect.onrender.com/ if you want to take a look. It's nowhere near perfect but it is so much closer!