Add support for additional Azure regions

Context
seeking contributor
Overview
Adding support for Azure regions is not extremely straightforward. In different places, the naming of these regions is not exactly the same or predictable, so initially our team has only been able to add support for regions we are currently using. We would appreciate the addition of any regions not yet supported that you are using.
Out of Scope:
Related issues/Dependencies:
Acceptance Criteria

[ ] When I have usage in a previously unsupported Azure region, I now see the data for that region added to the total data for my Azure usage
[ ] When I have usage in a previously unsupported Azure region, I now see my usage for that region within the bar chart, with the appropriate label, percentage of usage, color for grid intensity
[ ] When I have usage in a previously unsupported Azure region, I now see that region in the region bar chart with a hover that has the region name and cloud provider, and total co2e for this region
[ ] When I reference a new Azure region, I should follow the existing naming conventions
[ ] When I have usage for a previously unsupported region that I can see this region in the region map and it's grid intensity is listed in the methodology on the microsite (Please reach out to the Green Cloud team if these two need to be completed - we will handle it.)

Tech Tasks

[ ] Changes to be made in packages/azure/src/lib/AzureRegions.ts
[ ] Add appropriate test coverage, including edge cases.
[ ] Run Changesets, bump any packages that have been updated/changed
[ ] Did you make changes to the client, api or cli package? If so, considering updating the create-app templates.
[ ] If any create-app templates have been updated, make sure to run the test-create-app script to ensure it still works properly.

Tech Notes
Review Tasks

[ ] eg. specific QA details, update methodology, or update microsite

I'd like to help since I'm interested in trying this on Azure subscriptions with resources in France regions. If someone can point to the right direction/materials, I'll take it from there

Hi @ab-smith , sorry for the delayed response and thanks for volunteering to help with this issue! It would be awesome to have support for France regions! A good starting place for adding support for the regions are to begin with the AzureRegions.ts file. The ConsumptionManagement API from Azure often returns inconsistent strings for the region, so you will have to add the official name along with possible aliases from the API that you know of -- you can follow the other listed regions for the appropriate pattern. A good way to discover the aliases is to see what you're able to receive from the API after connecting your Azure credentials with subscriptions that include those regions to the CCF app. Our app should return the list of the regions you have that are unsupported.
Afterwards, we may need to map an emissions factor for that region if we don't have one already in the AzureFootprintEstimationConstants.ts file for the AZURE_EMISSIONS_FACTORS_METRIC_TON_PER_KWH constant. We have a list of these emissions factors and their sources in the Azure section of our methodology which we usually get from the EPA or carboonfootprint.com. You're welcome to explore these sources to map the appropriate Emissions Factors for the region, otherwise feel free to make the PR with the added regions in the AzureRegions.ts file and we can verify and add the emissions factors before merging.
Thank again! Also, don't hesitate to reach out if you have any questions or need additional support!

Hi @ab-smith
This seems to be an issue for my team too (See #401)
Did you have the chance to get into this point ?

Hi, unfortunately no, I had to postpone this for now.

@4upz-tw @ericksod I'd like to contribute to this issue, but I'm not used to webapp development and API usage. Is there any command that you could share to detect which values to put in AzureRegions or AzureFootprintEstimationConstants.ts ?
I'm able to make any manual API calls to Azure API (through python and bash mostly)


brick:regulates in v1.3

It appears that the regulates relationship is no longer part of the BrickSchema standard in v1.3. Was this intentional? I couldn't find mention of it in release notes.

Hi @emesar I don't believe it was ever an official part of Brick -- I believe the regulates relationship was added as an experiment but it was only ever added to a few classes. We removed the few uses of it to avoid future confusion and to make room for an eventual design to replace it. In particular, the emerging ASHRAE 223P standard should give us some concepts that will make modeling this a little easier. It would be great to discuss this with you; feel free to attend any of the upcoming Brick working group meetings (https://brickschema.org/blog/working-groups/)


Make profile pic object serializable

The User object is serializable, but ProfilePic isn't. Android throws an exception when adding the object to a Bundle.

Thanks for contributing!

Thanks for contributing!


raftstore: fix compact_to for entry cache

Signed-off-by: gengliqi<EMAIL_ADDRESS>What problem does this PR solve?
Problem Summary:
In the original code, the idx of compact_to function means all entries whose indexes are less than idx should be compacted.
However, the code below incorrectly uses idx.
https://github.com/tikv/tikv/blob/834ec1108d85623b2b19b00df2fa8e1359c726b6/components/raftstore/src/store/peer_storage.rs#L245
For example, if there are some cached_entries whose indexes are [0, 10), [10, 20). After this peer has applied the first cached_entries and call compact_to with applied_index + 1, which is 10. The second one will be removed because of the above code, leading to the unnecessary read io of raft db.
What is changed and how it works?
What's Changed:
Fix it and add comments for this function.
TODO: Add unit test for cached_entries.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test

Side effects

No

Release note
None

There is a test test_storage_cache_update already. Can you update the case to cover this?

There is a test test_storage_cache_update already. Can you update the case to cover this?

I updated test_storage_cache_size_change test which is more suitable for the bug here. PTAL.

/merge


List and show agents in the CLI

Includes man-pages. List includes formatting human and csv types, along
with the ability to list roles on their own lines. The Show command
gives additional information, and requires a public key as the
identifier. (Agent ID is synonymous with public key.)

about for agent subcommand should be updated to reference list and how
https://github.com/hyperledger/grid/blob/5541e3518a583d269b90eeba520bc984babc1610/cli/src/main.rs#L156

about for agent subcommand should be updated to reference list and show
https://github.com/hyperledger/grid/blob/5541e3518a583d269b90eeba520bc984babc1610/cli/src/main.rs#L156

good catch! however, this also is the case for many other commands as well. I may make a separate PR and fix them all, but for now I will update the current one to reflect the correct fix.


cloudflare-dynamic-dns: 4.3.2 -> 4.3.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zebradil/cloudflare-dynamic-dns/releases.
meta.description for cloudflare-dynamic-dns is: Dynamic DNS client for Cloudflare
meta.homepage for cloudflare-dynamic-dns is: https://github.com/Zebradil/cloudflare-dynamic-dns
meta.changelog for cloudflare-dynamic-dns is: https://github.com/Zebradil/cloudflare-dynamic-dns/blob/4.3.3/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.3.3 with grep in /nix/store/2zvaqw9is21widxlyh7k12cnrxn5zh9h-cloudflare-dynamic-dns-4.3.3
found 4.3.3 in filename of file in /nix/store/2zvaqw9is21widxlyh7k12cnrxn5zh9h-cloudflare-dynamic-dns-4.3.3

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

cloudflare-dynamic-dns

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2zvaqw9is21widxlyh7k12cnrxn5zh9h-cloudflare-dynamic-dns-4.3.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/9be3c09dca2838e332aa28179821fcdaf38fe7ad#cloudflare-dynamic-dns

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2zvaqw9is21widxlyh7k12cnrxn5zh9h-cloudflare-dynamic-dns-4.3.3
ls -la /nix/store/2zvaqw9is21widxlyh7k12cnrxn5zh9h-cloudflare-dynamic-dns-4.3.3/bin

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

1 package built:

cloudflare-dynamic-dns

Maintainer pings
cc @zebradil for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


How to enable preview mode

Great starter kit, loving it already.
However, I faced one issue. In your blog video, it shows how we can click a button on a page to preview it with NextJs. I don't see that button on my strapi admin ui.
Is there something I need to do to enable that?
Many thanks 🙏🏼

Hello! Happy to hear you enjoy this starter.
I've addressed this issue over there: https://github.com/strapi/strapi-template-corporate/issues/1


nothink work

I have same issue, nothink work with alt and z or alt+z same time, I have warmenu named /resources/warmenu and k9 named /resources/k9 but nothink work, not blip on the map I try all in false in config and still same issue!?

That really makes no sense.. Everyone else has it working.

did you start the war menu before k9 and did you start the k9..

yes I have see on fivem the resently problem and this same for me... I have warmenu before k9 and of course I start the k9... I dont understand this great script but no work for me..

but not just after the warmenu, some line after... You think is problem?

Say again? I didnt understand your last comment?

Sorry im french... The warmenu in server.cfg is before k9 but not just after, some line after. I have other start between tow

That should be fine. Do you see any errors on the server or client console.

not any error... And the K9 blip not spawn also!?

K9 has to be spawned for the blip to spawn.

I have the good message in consol when I start my server

Yeah, that's just my version checker.

oh ok for blip

yes I know... So you have found the problem for 'bladehype911' in fivem?
I think is same like me?

He was saying to make sure to load the warmenu before the K9 he didnt have anything wrong.

Maybe send some screenshots of how you have it installed.

ok I make it

I don't believe there is anything wrong with Tyne script as I have just reinstalled it on my test server and it works fine. Take the rest of your issue to the k9 topic in the fivem forums.

I use esx gamemode so this problem....


The value of absIndexMin in getVisibleNavIndex is not correctly calculated.

Issue description:
The value of absIndexMin in getVisibleNavIndex is not correctly calculated.
Demo link/slider setting:
http://crazycoolsite.com/mga/reviews.html
tns({
  container: '.reviews-slider__slides',
  items: 2,
  gutter: 50,
  controls: false,
  navContainer: '.reviews-slider .slider-nav'
});

Tiny-slider version:   last version
Browser name && version:  all browsers
OS name && version:   Mac OS

May I know the details?

Yes. On the page in the working slider there should be three items of navigation, and the slider makes two items of navigation. Try the buttons left and right and pay attention to the navigation items. The first and second are good, but the third navigation disabled. Then the cycle begins from the first.

Hi, that's right.
As I checked, you have 3 items originally. The dots work as "slide by page". So "3 slides" = "2 pages". That's why only 2 dots will show.

Okay, Thanks for the answer. Pay attention to the navigation elements. It's wrong behavior. The second element has two slides. Can I fix this?

You can try loop: false

You can use "navAsThumbnails: true" and no need to set "loop: false"

Many thanks!


Add 'make deploy' target to simplify testing with local cluster.

make deploy: build and push an image, then deploy with helm.
Make variables REGISTRY_ORG and TAG control the image used.

/retest

/lgtm


Anchor bottom height for pedestrians & cyclists

I noticed here:
https://github.com/open-mmlab/OpenPCDet/blob/b7553c879d0ba36477931efe07a55adbc39823b9/tools/cfgs/kitti_models/pv_rcnn.yaml#L78
that the anchor_bottom_height for pedestrians and cyclists is actually set to -0.6. From other works, I saw that this value is actually the center of the pedestrian & cyclist object, not the bottom. Should it instead be shifted down by h/2 of these two objects? Though perhaps regression will learn the bias regardless
Also, I was wondering if you could shed some light on how exactly the bottom height for car was calculated. I know that papers generally use -1.0 for the center, and lowering that by half the height of the car yields -1.78. However, when I just took the average of the z bottom height for cars, I ended up with -1.51. Why would there be a difference?
Thank you for your great work!

Hi, actually I have tried several anchor_bottom_heights with small variance, and the results are similar.
I guess -1.51 and -1.78 could achieve similar results.
For the KITTI dataset, I remembered that -1.78 is copied from original second codebase.
For a new dataset, you could statistics the box height from training set.

I see - I guess the regressor will learn whatever bias there is
I do think the bottom heights for ped & cyc should be lower, but I'll see if it makes a difference


bug: Linux misspelled as "Lunux" in mysql/postgres start database shell scripts

Provide environment information
System:
OS: macOS 14.0
CPU: (8) arm64 Apple M1 Pro
Memory: 104.80 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 21.5.0 - /opt/homebrew/bin/node
npm: 10.2.4 - /opt/homebrew/bin/npm
Describe the bug
Linux is misspelled as "Lunux" in the instruction comments of start-database.sh scripts for both my-sql and postgres.
Reproduction repo
https://github.com/t3-oss/create-t3-app
To reproduce
Just a typo in the comments
Additional information
No response

PR: https://github.com/t3-oss/create-t3-app/pull/1740


Improve the text at the top of the home page

Received the latest home page text from the product team.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: pankaj00ap sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

New Feature


mkl-dnn sha256sum not match since two available link has different sha256sum

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Utuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version: 2.1.0
Python version: 3.6.8
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 0.24.1
GCC/Compiler version (if compiling from source): 5.5.0
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
Bazel build fails since mkl-dnn sha256sum doesn't match.
In tensorflow/workspace.bzl, there are two links:
urls = [
"https://storage.googleapis.com/mirror.tensorflow.org/github.com/intel/mkl-dnn/archive/v0.21.3.tar.gz",
"https://github.com/intel/mkl-dnn/archive/v0.21.3.tar.gz",
],
However the sha256sum of the two links is not the same. The sha256sum of the first url is given in workspace. Due to some connect issue in China, we don't have access to the first url and can only use the second. Then sha256sum not match is met.
Provide the exact sequence of commands / steps that you executed before running into the problem
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@tz301
Request you to provide the exact sequence of commands / steps that you executed before running into the problem.Thanks!

@ravikyram
Our project using tensorflow as dependency. When we use "bazel build //project_name:module", it fails on mkl-dnn sha256sum check. We have solved this problem by adding mkl-dnn lines the same as that in tensorflow/workspace.bzl but manually change the strip-prefix and sha256sum in our workspace.
But I think it should be a bug, since the two urls for mkl-dnn have different sha256sum, it should be the same, right? Thanks.

It seems that mkl-dnn redid their release and have different hash now than the one we mirrored. Unfortunately, the mirror is read-only by design, so all you can do is locally change the hash

This is unintended result of repository migration from intel/mkl-dn to oneapi-src/oneDNN. The source code blob includes metadata that include repo name.

Understood. I have done it locally.
But I just find that the master branch also has this issue, hope it can be fixed in master branch.

We cannot fix until there is a new release for mkl-dnn. The things stored at mirror.tensorflow are read-only, we cannot rewrite them. So we have to use that hash always.
When mkl-dnn makes a new release we can mirror from the new repo and then both links will have the same hash.

oneDNN v1.4 is released.

We need a PR to update to the new version and then we're can close this. Thank you

We need a PR to update to the new version and then we're can close this. Thank you

https://github.com/tensorflow/tensorflow/pull/38671   This will fix it for the build for mkl build (config=mkl).  Compiling TF without config=mkl will still use old 0.2x release (at least for now).
@tz301 how are you building TF?

@agramesh1  Our project is also a bazel project, and include tensorflow's github url in workspace. Due to this issue, I have to include mkl-dnn url locally (the same version as that in tensorflow's workspace) and copy tensorflow's mkl-dnn.BUILD file.
It's worked now in our project, though not very elegant. If there are more elegant ways to fix this in old branch, please advise, thank you.

@agramesh1,
If this would help we can do a patch release from the branch Tensorflow uses. Just let me know which release you need.

@vpirogov @agramesh1
We are using tf-1.15.0, "https://github.com/tensorflow/tensorflow/archive/v1.15.0.tar.gz" is included in our workspace now. Thanks!

There will be a 1.15.3 patch release soon. We can cherry-pick this on the branch and release with that included too.

I posted v0.21.5. Updating branches or configurations still relying on v0.x to this version will address the problem for these as well.

The issue should have been fixed in PR #39725 now.

Closing as fixed. Please reopen if that's not the case.

@mihaimaruseac Seems fixed in master branch. Is this branch also fix as you mentioned before?  "There will be a 1.15.3 patch release soon. We can cherry-pick this on the branch and release with that included too."

Oh, there was no PR to cherry-pick for 1.15.3 so it didn't get included.
We should cherry-pick the #39725 PR on the r1.15 branch in the events of there being a 1.15.4 patch release though that would not be before TF 2.3 release at least.

I think this is fixed now, right?


Monitoring - uninstall the monitoring v2 app causes cattle-cluster-agent restarts

What kind of request is this (question/bug/enhancement/feature request):
bug
master-head e9a98a3
Steps to reproduce (least amount of steps as possible):

as admin, install monitoring v2 in a downstream cluster
as admin, uninstall the monitoring app

Result:

the dashboard is reloaded and not accessible

the cluster goes to the unavailable state

the pod of the workload cattle-cluster-agent crashes and restarts

logs of the crashed pod
time="2020-09-25T22:03:51Z" level=error msg="Error during subscribe websocket: close sent"
E0925 22:03:51.396776       1 leaderelection.go:357] Failed to update lock: Put "https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/configmaps/cattle-agent-controllers?timeout=15m0s": context deadline exceeded
I0925 22:03:51.560057       1 leaderelection.go:278] failed to renew lease kube-system/cattle-agent-controllers: timed out waiting for the condition
E0925 22:03:51.680182       1 leaderelection.go:297] Failed to release lock: resource name may not be empty
time="2020-09-25T22:03:51Z" level=fatal msg="leaderelection lost for cattle-agent-controllers"

update:
the cluster keeps failing into the error state and is not usable now.
here are the logs of the kube-controller-manager and kube-scheduler from the control plan node
kube-controller-manager-logs.txt
kube-scheduler-logs.txt

@jiaqiluo I'm unable to reproduce this error on a Rancher cluster based on the latest master; was there a specific setup that you used for this that we could use to consistently reproduce this? I've also never encountered this with monitoring before.
From what I can tell from the logs, it's seems like you were using a 3 node cluster with 1 server and 2 agents in Digital Ocean; was there a particular VM size that you were using on these nodes?
As far as I can tell, this issue seems flakey and could be related to memory or networking issues specific to that cluster, but it's hard to pinpoint exactly what caused this error to occur.

@aiyengar2 I will let you know if I hit it again.

I hit this in rancher:master-head ec04f78, docker install
The steps and results are the same as the issue describes.

@jiaqiluo Is this only docker installs or is this HA installs as well?

@deniseschannon  I see it only in the docker install mode.

@jiaqiluo Do you know if this occurs with other apps? DO other apps cause the cattle-cluster-agent to restart?

@deniseschannon  I have not noticed this happen when uninstalling other apps. From a conversation with @aiyengar2, the reason might be that some logic for monitoring v1 (even v1 is not enabled) tries to manipulate the same CRDs that monitoring v2 installed/uninstalled, which causes some sort of overloading or data corruption and eventually pulls the pods down.

I was unable to reproduce this after installing, uninstalling, reinstalling monitoring v2 multiple (5) times.
Rancher version: v2.5.4-rc7
steps used:
-- install HA rancher cluster (3 node)

add a 3 node cluster ( in my case using Linode)
install the monitoring v2 in dashboard
uninstall the monitoring
re-install the monitoring
-- install docker rancher (single node)
add a 3 node cluster ( in my case using Linode)
install the monitoring v2 in dashboard
uninstall the monitoring
re-install the monitoring

4 uninstall/reinstall attempts were made per rancher install, none of which resulted in reproducing the issue.  The cluster was in a persistent usable state throughout the tests.

@slickwarren Since this is not reproducible with the latest RC, can we close this? If you get into this setup again, please share with us and we we can investigate.
cc: @jiaqiluo

@slickwarren Since this is not reproducible with the latest RC, can we close this? If you get into this setup again, please share with us and we we can investigate.
cc: @jiaqiluo

yes, thanks

yes, thanks


Fix CodeMirror crash while syntax highlighting

Fix the bug in #110.
value and mode of CodeMirror should not be initialized, and set in componentDidUpdate() later.
I don't know why, but it can actually solve the issue. It may be a bug of React-CodeMirror.

@hackjutsu
By tracing the log, I found that when clicking #edit/#new links, the componentDidMount() of GistEdit will be called with no filename or value props. They are all undefined.
Then the componentDidUpdate() of GistEdit will be called with actual props.
But something is strange. If mode and value are set in Render() directly, they can not be changed in componentDidUpdate(). And if value is set with https://gist.github.com/hackjutsu/2367861489c591b110a0bdd33270e99a and mode is unset, the CodeMirror will crash! So I have to implement it as this commit... I think there may be something of React-CodeMirror is intractable.

Please refer to my fix:https://github.com/hackjutsu/Lepton/commit/c2f541a372eb18c13f8327f6898343f282a1040b

@hackjutsu
You find the exact source of the crash. It's a better solution.


[BUG][0.3.9] Authentication method concern due to deprecation of token in API’s query string for Memsource TMS APIs

Describe the bug
Find out the impact of the deprecation and how to change the authentication method to one of the supported ones.
Affected version
To Reproduce
Steps to reproduce the behavior
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots or Traceback
If applicable, add screenshots or Traceback to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @cyril-ui-developer
It needs to be changed https://github.com/unofficial-memsource/memsource-cli-client/blob/master/memsource_cli/api_client.py#L103
Add something like:
if query_params['token']:
    header_params.append('Authorization', "Bearer " + query_params['token'])
    query_params.remove('token')

Would you like to take this or if not I can.

Hi @cyril-ui-developer
It needs to be changed https://github.com/unofficial-memsource/memsource-cli-client/blob/master/memsource_cli/api_client.py#L103
Add something like:
if query_params['token']:
    header_params.append('Authorization', "Bearer " + query_params['token'])
    query_params.remove('token')

Would you like to take this? or maybe @ludekjanda can change it.

@zerodayz Feel free to take it or assign it to @ludekjanda. I am not familiar with the codebase. Thanks.


[Apple Reminders] Could not find extension's manifest file. You might need to reinstall the extension.

Extension
https://www.raycast.com/raycast/apple-reminders
Description
Error:
Could not find extension's manifest file. You might need to reinstall the extension.

Steps To Reproduce
On Sunday, all of my extensions stopped working. All extensions now result in the same error:
Could not find extension's manifest file. You might need to reinstall the extension.

I am reporting this under "Apple Reminders", but it also happened for brew, vscode, etc. I think the underlying issue is likely the same.
The following steps were attempted but did not resolve the issue:

Reload extension
Clear extension cache

The issues is resolved by uninstalling and then reinstalling the extension.
Current Behaviour
No response
Expected Behaviour
No response

Are you still facing the issue?

I resolve the issue by doing the following:

The issue is resolved by uninstalling and then reinstalling the extension.

Since then, it has not happened again.

This may have been a temporary issue. I'm closing this issue to maintain a clean backlog then. Feel free to comment or reopen it it if you still have the problem.


Add custom_model to AIPTW

Similar to TMLE, AIPW will allow for valid inference with machine learning (given Donsker class estimators). As a result, AIPTW will gain the custom_model optional argument. It will also have the Donsker check update as mentioned in #109 #124

Added as part of #143


Graphic Pack 97 FPS++ BOTW no 60 fps anymore

With the pack 87 fps++ works just fine and i get stable 60 fps @ 4k.
Now after i updated directly to 97 fps++ dont work anymore.
(Static 60fps dont work also)

for me too, massive drop in framerate from 60fps to 15-20

Thx till now i just used the FPS++ folder from pack 87. Only thing now is that the order in graphic packs menu isnt correct. Now it is at  "old packs" again.

Don't use the pre-release versions! It's not very clear, true


Bump to Elixir v1.16.0 and OTP 26

Also formatted the code, resolved String.slice/2 warning appearing with Elixir v1.16-otp-26 and updated github workflows ci config file

thanks for the contribution, just added one question

@michelson for elixir libraries anyone running older than 3 versions should be left behind. For exqlite I only support latest 3 versions of OTP and Elixir.
https://github.com/elixir-sqlite/exqlite/blob/8cac98612426d41672730d18511204eb23ce77a3/.github/workflows/ci.yml#L52-L53
I would say supporting back to 1.14 should be minimum and anyone on 1.12 needs to update as that does not compile with latest OTP at all and has severe security vulnerabilities.

@michelson any news if we can get this bump to happen? The string slice warning is now appearing all over my tests.

@michelson any updates?


Remove/disable free credit enrollment [SATURN-1752]

Entering the enrollment flow relies on setting global state freeCreditsActive in state.js. This removes just about every case where that happens, and also removes/changes handling of when the profile's trialState is Enabled.

Looked over code and think it all looks reasonable - I agree with the approach to leave the currently enabled users logic in and just not allowing anybody new. Haven't tested yet - will work on now


rST description not rendered on PyPI

I noticed that the PyPI package page has the rst readme in plain text. Using the readme package to check it, I found that the changelog markup in CHANGES.rst is causing the problems.
We could:

Take the change log out of the package's long description. I prefer this, because the change log makes the PyPI page very long as more releases happen.
Manually change the changelog and change directives back to plain rst. The Sphinx docs would presumably lose something from this.
Have some code that tries to convert the rich rst into plain rst when setup.py runs. This would be fragile, and could easily get out of date.

Hmm, indeed. I have to agree with your assessment. Option 1 is imho the best, I've never been one for keeping changelogs anyhow. Looking at the github issues (or more detailed, commit log) seems more useful to me than changelogs as I'll always try to maintain backwards compatibility anyhow.
I've disabled this part of the code in the setup.py and manually updated the pypi page for now.

And I see there's a new release out already - thanks!

Yes, luckily I still have some time before my flight leaves :)

Have a good trip!


chore: v1 initial structure

Sorry about the WIP commits 😅

Codecov Report

Merging #332 into next will decrease coverage by 56.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             next     #332       +/-   ##
===========================================
- Coverage   87.31%   31.26%   -56.05%
===========================================
  Files          82       43       -39
  Lines         607      387      -220
  Branches      137      103       -34
===========================================
- Hits          530      121      -409
- Misses         77      263      +186
- Partials        0        3        +3

Impacted Files
Coverage Δ

packages/reakit/src/Tabs/Tabs.tsx

packages/reakit/src/_utils/hoist.tsx

packages/reakit/src/Table/TableWrapper.tsx

packages/reakit/src/Tabs/TabsContainer.tsx

packages/reakit/src/Toolbar/ToolbarContent.ts

packages/reakit/src/Table/Table.tsx

packages/reakit/src/Toolbar/ToolbarFocusable.tsx

packages/reakit/src/Step/StepShow.tsx

packages/reakit/src/Tabs/TabsPrevious.tsx

packages/reakit/src/_utils/callAll.ts

... and 65 more

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 c14f170...da2b069. Read the comment docs.


Install: Makes Waypoint Resources Configurable

Please provide a description of this PR:
Previously, waypoint CPU and memory resources were hardcoded. This PR updates the waypoint deployment to allow these resources to be configured by .Values.global.proxy.resources.
Fixes #51496

@danehans: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests-arm64

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

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests-arm64

gencheck_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test gencheck

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

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests-arm64

gencheck_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test gencheck

unit-tests_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests

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

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests-arm64

gencheck_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test gencheck

unit-tests_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests

integ-ambient_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test integ-ambient

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

I agree with Costin in principle but that new api is parameters ref. Depending on how soon we can get that to standard, this PR may make sense

This exact same API already exists for Gateway API for istio class. IMO it is entirely unexpected that the behavior is different between istio-waypoint and istio

A lot of APIs exist in Istio. That doesn't mean all of them make sense for
waypoint and ambient, or that they are good APIs.
Are you saying it is a good thing that we use the same default for gateways
and sidecars, and it is the right thing for waypoints
too ? Or that it may not be - but since we made a mistake it's ok to repeat
it ?
If the same default is used for Gateway API - it is probably something we
need to deprecate and fix for sidecar users because
there is no correct value for both ingress gateways and sidecars.
Keith - I assume you mean the upstream Gateway API. There is no exclusivity
or requirement that if something may
be added in the future - we are not allowed to have an Istio API doing the
same. In fact, this PR is doing exactly that,
defines an API for setting the default for the waypoint class. If you want
some consistency with the future API ( which
IMO is a pretty bad idea - the Gateway API is becoming Istio MeshConfig and
will eventually make Istio API look good
in comparison) - we can define a per-class setting in MeshConfig.
In practical terms - most users set those things at install time, i.e. are
part of the 'helm install API' - even if GatewayClass
defined something, users will still interact with it via helm install and
we would populate whatever fields they set.
On Wed, Jun 12, 2024 at 6:55 AM John Howard @.***>
wrote:

This exact same API already exists for Gateway API for istio class. IMO
it is entirely unexpected that the behavior is different between
istio-waypoint and istio
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/51505#issuecomment-2163075203, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2XOKUIHN3H2M7JZYFTZHBHNFAVCNFSM6AAAAABJDQUDQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGA3TKMRQGM
.
You are receiving this because your review was requested.Message ID:
@.***>

+1 to John - incremental progress is ok here. Per GatewayClass (or even per gateway) configuration is the ideal but having some knob is better than no knob at all

On Wed, Jun 12, 2024 at 7:16 AM John Howard @.***>
wrote:

I do think its okay to repeat a "mistake". The mistake is that we
introduced an API that adds some value, but is not perfect.
That cost is already amortized by having it in (ingress) Gateway API.
There is no additional tech debt we incur by adding it in waypoint --
actually, probably less tech debt by having consistency. In the meantime it
adds value to users.
Is it perfect, of course not.

So what's the harm in adding a setting that allows setting resources for
waypoints - which does provide the same or
better value to users ?
It's not far more complicated - and it will provide even better value since
they will be able to set a different
value for waypoints than sidecars.
I do agree it adds value - but any change also has a cost, and the cost for
some experimental code
or implementation detail is very different from the cost of an API.
Message ID: @.***>

Ok, so let's make even more incremental progress - and add a separate
default for waypoints.
And I strongly disagree that 'incremental progress' with no API-like review
is the right way for
things that are exposed to the users and expected to be very hard to
change.
On Wed, Jun 12, 2024 at 7:21 AM Keith Mattix II @.***>
wrote:

+1 to John - incremental progress is ok here. Per GatewayClass (or even
per gateway) configuration is the ideal but having some knob is better than
no knob at all
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/51505#issuecomment-2163143971, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2RTCB2LUJ526GAYEH3ZHBKQBAVCNFSM6AAAAABJDQUDQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGE2DGOJXGE
.
You are receiving this because your review was requested.Message ID:
@.***>

Separate default makes sense to me

Commit https://github.com/istio/istio/commit/8f010e8a22611dac8b5f7e6340709e663942c7a4 introduces .Values.global.waypoint.resources to configure waypoint resources.

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test unit-tests

integ-ambient_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test integ-ambient

unit-tests-arm64_istio
8f010e8a22611dac8b5f7e6340709e663942c7a4
link
true
/test unit-tests-arm64

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

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
60daa5aac8d7b5141b6eb922782bc9747a44b565
link
true
/test integ-ambient

unit-tests-arm64_istio
8f010e8a22611dac8b5f7e6340709e663942c7a4
link
true
/test unit-tests-arm64

unit-tests_istio
8f010e8a22611dac8b5f7e6340709e663942c7a4
link
true
/test unit-tests

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

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
8f010e8a22611dac8b5f7e6340709e663942c7a4
link
true
/test unit-tests

unit-tests-arm64_istio
4d33a4a28db09097a15539f8e988e9bcb69c8703
link
true
/test unit-tests-arm64

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

@danehans: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
4d33a4a28db09097a15539f8e988e9bcb69c8703
link
true
/test unit-tests-arm64

unit-tests_istio
4d33a4a28db09097a15539f8e988e9bcb69c8703
link
true
/test unit-tests

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

@costinm the PR has been updated based on your feedback and is passing CI, PTAL.

I believe this PR directly addressed @costinm's concern and Costin is OOO so I think it makes sense to move this forward. If I am mistaken, @costinm, and you still have concerns LMK and we can revert/tweak/etc


Don't allow inlines to wrap other inlines

I had the same thought and came to the same conclusion. We'll probably want a visually disabled state at some point, but it's not immediately obvious what that should look like so we can punt it for now.


Add load_time and coldstart

Signed-off-by: Eric Windisch<EMAIL_ADDRESS>

@ewindisch if this is rebased, we could add coldstart to python


Currently we have a releases folder with prod, dev and stage - Can we change it to different clusters

Let's say I have multiple clusters deployed, and I need to have different release folders for the different clusters.
Currently, I have created different repositories for different clusters. Now with 2 clusters, it's okay. But with multiple clusters, it would be a mess.
Can you (@stefanprodan ) help me here? Maybe I'm missing something.

you could use a --git-path option in your fluxcd installation

Thank you @c4m4


PCB for this hardware

Hi,
thanks for building this, just wanted to let you know that i built a PCB for this code.
its not been tested yet but i will report back when its been tested:
https://easyeda.com/raptordemon/ESP8266_IR_blaster-f8f224faba554bf3bb6ce0e32759fc23
cheers!
Raptor

This looks really cool
I don't have much experience with this, is the 1.3 revision using the latest pin assignments now?
I'd definitely like to order a couple of these if you've tried
I thought I had replied to this comment earlier and may be going crazy but don't see that reply now
Let me know how it goes! Is this using the V2 nodeMCU?

Never mind it was on the pull request that I commented, sanity restored
But yeah definitely keep me posted and send some pics when you get the PCB ordered, I'd like to check it out

yea sorry about that, feel free to delete one.
do these look correct?
int pinr1 = gpio14; // Receiving pin
int pins1 = gpio4; // Transmitting preset 1
int pins2 = gpio5; // Transmitting preset 2
int pins3 = gpio12; // Transmitting preset 3
int pins4 = gpio13; // Transmitting preset 4
its for the 25mm / 1in width node mcu like this one:
https://www.amazon.com/Generic-ESP8266-NodeMcu-Internet-Development/dp/B01N0B48NI/ref=sr_1_6?ie=UTF8&qid=1500467677&sr=8-6&keywords=nodemcu
im not sure if that counts as the v2

Yeah that's the V2, there's an unofficial V3 version that's larger that was made by some other company, that's why I asked
And those pinouts look correct yes

great, i m going to reorder the boards this week and hopefully get it right this time.

One other question, it looks like the transmitters are using 3.5mm jacks? Maybe the receivers as well. What’s up with that?

On Jul 20, 2017, at 1:43 PM, raptordemon<EMAIL_ADDRESS>wrote:
great, i m going to reorder the boards this week and hopefully get it right this time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/mdhiggins/ESP8266-HTTP-IR-Blaster/issues/50#issuecomment-316778480, or mute the thread https://github.com/notifications/unsubscribe-auth/ADcO6iHfCCOqOffewKt8GLedx5DPUfoLks5sP5HRgaJpZM4OZ8mE.

Just as an information.
I use the firmware with this hardware: https://www.openhardware.io/view/385/MySWeMosIRShield-IR-blaster-shield-for-WeMos-D1

That's pretty cool looking, but looks like no spot for a receiver?

Nevermind, just saw the receiver

There is a receive on one side between two LEDs. Someone already printed a housing.
https://forum.fhem.de/index.php/topic,72950.msg659524.html#msg659524

Looks like the GPIO15 reset option was causing people a lot of problems, I had to change to GPIO10
Any chance I could get you to at least update the small blueprint? I'm not familiar with this and afraid I'm gonna screw something up

sure no problem

GPIO10 is working well for me on the NodeMCU board, can't speak to the other variants but I changed all my boards over to that without problems
Also, I have a new update hopefully coming soon and am looking for a better tester that uses the IR Blaster with Alexa (and I guess is in the US cause of Amazon's limitations). Any interest?

Just ordered all the parts, this looks amazing. I'll be using it with IFTTT & Google Assistant, is that any help?
PS: The PCBs looks great as well, will get those as well ^^

HI pcb's updated, v1.5 is the latest it has gpio10 as the wifi reset. i have not tested this board as i am using the v1.3 and still have boards.
please let me know if it works
Raptor

Awesome thanks, I'll order some for testing
Also @raptordemon if you use your devices with Alexa, any interest in beta testing something?

yw.
yea i can do that.

Reply to this email directly, view it on GitHubhttps://github.com/mdhiggins/ESP8266-HTTP-IR-Blaster/issues/50#issuecomment-334563295, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASaxhD07irI5vg4Gc65DwGTY3ijSW_clks5spSmkgaJpZM4OZ8mE.

Invite sent, and sent you an email explaining the new features

@ipjcrane @raptordemon
Any luck with the beta testing?
If you need more help with setup here is a complete setup tutorial video that I finished making that will be live when Amazon enables the V3 API for all users
https://www.youtube.com/watch?v=JysKXOdrOlM

@raptordemon,
Are the circuit boards available yet?  Just starting this project and ordering parts now.  I have no breadboards and just heard about the samples you sent to mdhiggins.  Sounds like they'd be a much cleaner solution.

They are available. Use the v1.5 schematic when ordering. For first time builds though I would recommend using a breadboard for testing/debugging

Just wanted to say nice job!   I have built a prototype board using the ESP8266-12E module and am having fun playing with it.   I may decide to develop a board as well and share it out for those who want to reduce the size a bit as the NodeMCU is a bit bulky compared to the ESP module and a few surface mount components.
Do you have any plans to update the interface for the back end server?   One thing that would make it a bit more 'general user' friendly is if you had options not to have to enter the url for each command.  I feel if the interface simply asked for your ip, port, model of device, password, etc... and then for each command only required the hex codes for your remote it would make setting up various devices much simpler.
In any case, great job!

Probably not
While it would make the interface a little cleaner it locks in less flexibility and it would also potentially break compatibility with all the people who have already defined their devices
In the current iteration you can actually combine controlling different controllers within the same virtual device
That being said it would be nice to reduce some of the redundant data. I'll have to see if I can come up with a clever solution that's backward compatible

@raptordemon

Nice job on the V1.5 PCBs!  Many thanks for sharing.

I just ordered a batch of 10 large and 10 regular V1.5 boards from EasyEDA (China).  Got them and built them up today.  They were cheap - $26 got me 10 of each, including DHL shipping from China. Delivery was 3 days after ordering.

@raptordemon & @mdhiggins
2.  Only one problem:  configpin=GPIO10 crashed my NODEMCU board, even without being plugged in to the IR Blaster board.  Solution for me was to use configpin=16 (aka D0).  It is NOT a good idea to use GPIO10 on a NODEMCU board because it's a reserved pin on some versions, including the NODEMCU Version 0.9 board which uses it for flash chip write control.  0.9 NODEMCU crashes with pinmode(10,INPUT_PULLUP).
@raptordemon
3.  Some suggestions for improvement:

make the pin spacing for the resistors wider to accommodate 1/4W resistors
put down pads for a micro config switch in addition to a config jumper.  Putting a reset jumper in place on the smaller boards is inconvenient.
put down pads for config mode on GPIO16 to support V0.9 NODEMCU (in addition to those on GPIO10 for V1.0)

I think at some point GPIO16 was the reset pin but was causing boot issues though I can’t remember exactly. It’s been quite frustrating finding a reliable reset pin but 10 hasn’t given me any trouble on the V2 nodeMCU which is the latest official
Sent from my iPhone

On Dec 21, 2017, at 12:53 AM, zobotek<EMAIL_ADDRESS>wrote:
@raptordemon
Nice job on the V1.5 PCBs! Many thanks for sharing.
I just ordered a batch of 10 large and 10 regular V1.5 boards from EasyEDA (China). Got them and built them up today. They were cheap - $26 got me 10 of each, including DHL shipping from China. Delivery was 3 days after ordering.
@raptordemon & @mdhiggins
2. Only one problem: configpin=GPIO10 crashed my NODEMCU board, even without being plugged in to the IR Blaster board. Solution for me was to use configpin=16 (aka D0). It is NOT a good idea to use GPIO10 on a NODEMCU board because it's a reserved pin on some versions, including the NODEMCU Version 0.9 board which uses it for flash chip write control. 0.9 NODEMCU crashes with pinmode(10,INPUT_PULLUP).
@raptordemon
3. Some suggestions for improvement:
make the pin spacing for the resistors wider to accommodate 1/4W resistors
put down pads for a micro config switch in addition to a config jumper. Putting a reset jumper in place on the smaller boards is inconvenient.
put down pads for config mode on GPIO16 to support V0.9 NODEMCU (in addition to those on GPIO10 for V1.0)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@raptordemon - This may sound really basic but I can't figure out how to order PCB's.  When I go to PCB Order on https://easyeda.com/order, it isn't clear on how to place an order.   Any suggestions?

@KDean7 I was having a hard time too.  But I figured it out.  Here's what you need to do:
-go to: https://easyeda.com/raptordemon/ESP8266_IR_blaster-f8f224faba554bf3bb6ce0e32759fc23
-scroll down to the last board
-under the last board, there is a blue box that says "Open in Editor"
-click that button and it will take you to a new page
-once it loads, there are tabs at the top for all the different board configurations
-choose the tab with the board you want
-next to the website logo , there is a drop down that lets you save the file
-choose save as (if you do not have an account, you will be prompted to create one)
-now choose Generate Gerber File
-at the bottom of the popup screen (you can order from here if you want) there is another button that says "Generate Gerber"
-now you have the gerber file that you can upload to the website that you want to order from.
Does any have any amazon or aliexpress links (or part#'s) for the wifi_reset button and/or the 3.5mm audio jack?

Does any have any amazon or aliexpress links (or part#'s) for the wifi_reset button and/or the 3.5mm audio jack?
I ended up ordering these jacks: https://www.aliexpress.com/item/20PCS-3-5mm-1-8-Female-Audio-Connector-5-Pin-DIP-Stereo-Headphone-Jack-PJ3024M/32689293903.html  they do fit but I have not been able to confirm that they work yet.  they do fit in the holes.  I will update once I can confirm they do indeed work.
for the reset button, I'm just using headers with a jumper.

I ordered and received the following boards:
IRBlaster v1.5 small
IRBlaster v1.5
I have soldered components on to the small board, but it's not transmitting IR.  The IR Receiver works fine.
I am wondering if I have 2n2222 and/or IR transmitter backwards.  Has anyone successfully used either of these boards?
If so, which way do these components fit in the board?  ie does the flat side of the component follow the outline on the board?
Can you post a picture of the completed board?

Hey , I got 1.5 board soldered everything up and The reciever works great but only the LED 1 to work and the others don’t. Btw i don’t have the 3 jacks soldered in, Without them does that mean it won’t finish the circuit and doesn’t power the other 3 LED’s?
Thanks

hi guys great work really, I order the boar 1.5 I solder everything in place except for the jacks that part I just confess I didn't understood and I still don't know how to do it im about to upload the code but not sure if everything is really in the place im kind of new in all this trying to learn. if someone have a pic showing how is the final result or similar would be really good. thanks ill be updating my progress.

sorry for the delay, you should not need to populate the jacks for the extra leds to work. ill see if i can test mine

I ordered and received the following boards:
IRBlaster v1.5 small
IRBlaster v1.5
I have soldered components on to the small board, but it's not transmitting IR. The IR Receiver works fine.
I am wondering if I have 2n2222 and/or IR transmitter backwards. Has anyone successfully used either of these boards?
If so, which way do these components fit in the board? ie does the flat side of the component follow the outline on the board?
Can you post a picture of the completed board?

Did you ever got it to work? I have the same issue?

Hey there.  Got mine to work correctly.  I have a schematic that shows how to correctly determine proper part orientation.  Will post here later today.
Do you have pic of your esp board to place here?  Not sure what you mean by a 1.5 board big and small..

Hey there, The PCB you posted a pic of is interesting.  It looks like all of the parts are positioned correctly.  Like the flat side of the LED and Transistor are placed correctly, which means the polarity is correct.  I traced the lines from the parts the best I could and everything appears to be good.
Please also send a pic of the ESP8266 board you plug into the headers on the PCB.  Maybe your ESP8266 has a different pinout than what is needed by the PCB.
Attached is a schematic I developed and used for this project based on the project notes:

Here is the PCB i built using this schematic:

If you use plug connectors, for like the LED, you would be able to swap out the parts more easily to see if you had a part that was malfunctioning.  I am currently transitioning to these connectors for my builds.

I then put my PCB into a project box.

please send a pic of your ESP8266 board

Here you go.
The only difference I see is that I use a 180 ohm resistor and you 10 ohm

That's the exact same ESP8266 board I use : )
Believe you nailed it with your keen observation there lol.  Going from a 10 ohm to an 180 ohm resistor would have a great impact in my opinion.  This resistor size directly controls the brightness of the Infrared LED.
In the project video of IR Blaster Tutorial, at 1:32 minutes:seconds, mdhiggins references the resistance at 10 ohm as that would provide 500 mAmp current to the IR LED.
The IR Blaster Tutorial video is located here -- https://youtu.be/JysKXOdrOlM
With a little experiment lol, maybe you can tell if you just have a rather dim IR LED bulb... find out exactly where the actual TV IR Receiver is located around the display screen.  What I normally do lol is put the remote like directly against the TV and move it around while pressing the on/off button.  When you identify that sweet spot that turns off the TV you can then hold your IRBlaster, with the IR LED pointed towards the TV of course, and send your commands away.
With any luck you will see that your device works but it's might be just a bit dim... then replacing the resistor will fix this.
I did see many diagrams on Google images showing a higher value resistor like you used.  When building mine I tried to just base it off of the video.  But every hurdle in this project seems to be monumental lol.
Out of the 4 boards I've built, I couldn't get 1 to work..  never figured out why, but I think it had a lot to do with my despicable soldering..

I can't get it to work. I gave up and look for other methods to operate my fire place

Just buy one of these.  Works really nicely with Michael's code.
https://www.aliexpress.com/item/32958748327.html
See #236 for more information.

Built a few of the boards and its working great! Thanks for the update

thats great news! thanks for the feedback!!

From: Michael Higgins @.>
Sent: Monday, September 13, 2021 10:33 AM
To: mdhiggins/ESP8266-HTTP-IR-Blaster @.>
Cc: raptordemon @.>; Mention @.>
Subject: Re: [mdhiggins/ESP8266-HTTP-IR-Blaster] PCB for this hardware (#50)
Built a few of the boards and its working great! Thanks for the update
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mdhiggins/ESP8266-HTTP-IR-Blaster/issues/50#issuecomment-918255418, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPY2IPOJNTCFAV2IFXMEV3UBYDSHANCNFSM4DTHZGCA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


dns: add records for wiki.nixos.org

In prevision for the deployment of the wiki.

Terraform will perform the following actions:

  # netlify_dns_record.nixos["wiki.nixos.org-A"] will be created
  + resource "netlify_dns_record" "nixos" {
      + hostname = "wiki.nixos.org"
      + id       = (known after apply)
      + type     = "A"
      + value    = "<IP_ADDRESS>"
      + zone_id  = "5e6ce1b8b6f808aa16acd1ff"
    }

  # netlify_dns_record.nixos["wiki.nixos.org-AAAA"] will be created
  + resource "netlify_dns_record" "nixos" {
      + hostname = "wiki.nixos.org"
      + id       = (known after apply)
      + type     = "AAAA"
      + value    = "2a01:4f9:c012:8178::"
      + zone_id  = "5e6ce1b8b6f808aa16acd1ff"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Deployed.

Thank you :)


Cannot connect to Debian 12 using VS Code Remote SSH extention

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Install Visual Studio Code

Version: 1.92.1 (user setup)
Commit: eaa41d57266683296de7d118f574d0c2652e1fc4
Date: 2024-08-07T20:16:39.455Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

Add Remote SSH extension
Connect to Debian 12

Connection does not complete. Error is reported in console:
leonbrag@hpdebian's password:
e93277eb2fbf: running
Installing to /home/leonbrag/.vscode-server...
e93277eb2fbf%%1%%
Downloading with wget
Download complete
e93277eb2fbf%%2%%
tar --version:
tar (GNU tar) 1.34
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
code 1.92.1 (commit eaa41d57266683296de7d118f574d0c2652e1fc4)
Starting VS Code CLI... "/home/leonbrag/.vscode-server/code-eaa41d57266683296de7d118f574d0c2652e1fc4" command-shell --cli-data-dir "/home/leonbrag/.vscode-server/cli" --on-port --on-host=<IP_ADDRESS> --parent-process-id 1917 &> "/home/leonbrag/.vscode-server/.cli.eaa41d57266683296de7d118f574d0c2652e1fc4.log" < /dev/null
printenv:
    SHELL=/bin/bash
    PWD=/home/leonbrag
    LOGNAME=leonbrag
    XDG_SESSION_TYPE=tty
    MOTD_SHOWN=pam
    HOME=/home/leonbrag
    LANG=en_US.UTF-8
    VSCODE_AGENT_FOLDER=/home/leonbrag/.vscode-server
    SSH_CONNECTION=<IP_ADDRESS> 61347 <IP_ADDRESS> 22
    XDG_SESSION_CLASS=user
    USER=leonbrag
    SHLVL=1
    XDG_SESSION_ID=8
    XDG_RUNTIME_DIR=/run/user/1000
    SSH_CLIENT=<IP_ADDRESS> 61347 22
    PATH=/usr/local/bin:/usr/bin:/bin:/usr/games
    DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
    _=/usr/bin/printenv
    OLDPWD=/home/leonbrag/.vscode-server
Spawned remote CLI: 1964
Waiting for server log...
e93277eb2fbf: start
SSH_AUTH_SOCK====
DISPLAY====
listeningOn==<IP_ADDRESS>:38907==
osReleaseId==debian==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult==success==
didLocalDownload==0==
downloadTime==538==
installTime==169==
serverStartTime==50==
execServerToken==347f9ecc-0d37-4d52-a8c6-95626c1fb472==
e93277eb2fbf: end

Posted in wrong place. Will report in Remote SSH tools


Add a full_url property to image rendition objects

Is your proposal related to a problem?
To include a Twitter 'share' image on a template, you'd typically do something like:
{% image page.social_image fill-1200x1200 as social_img %}
<meta name="twitter:image" content="{{ social_img.url }}">

However, this may return either a local URL (/media/images/foo.jpg) or an absolute URL (https://media.example.com/images/foo.jpg) depending on how media files are configured at the Django level. There's no good way to consistently return a full absolute URL, as required for the 'share' image to work.
Describe the solution you'd like
Add a full_url property to the image Rendition model, which prepends settings.BASE_URL to the rendition's url property if it begins with a /, and returns the url unchanged if not. This will then allow us to write
<meta name="twitter:image" content="{{ social_img.full_url }}">

(Using settings.BASE_URL isn't perfect - it's only an informal convention for Wagtail sites to define it, and it doesn't account for multi-site installations - but it's probably good enough for most purposes.)

@kevinhowbrook has applied a fix for this on RCA:
https://github.com/torchbox/rca-wagtail-2019/pull/551/files

It looks like this fix still needs to be implemented. Can you guys assign this issue to me?

I'm really sorry, I've not finished this yet. I was having trouble setting it up on my windows machine but now I've got it setup. The issue seems pretty straightforward but just to confirm, do I need to do anything else other than adding a full_url method in wagtail/images/models.py right? No need to add any documentation of any sort?
I'm a beginner to open source contributions so help would be really appreciated.

Hi @sankalpmukim,
Yes, this will need to be added to the documentation - I'd suggest updating the section at https://github.com/wagtail/wagtail/blob/main/docs/topics/images.rst#more-control-over-the-img-tag to mention the new method.
Additionally, you'll need to write some unit tests to show that the new method is working as intended (which helps us to spot if this feature gets broken by any future code changes) - see https://docs.wagtail.io/en/stable/contributing/developing.html#testing.

Alright thanks, this will be part of a single PR and this issue right? Also, do I mention the issue number in each commit(if tests, method and documentation are 3 different commits) or do in 1 commit? Again, thank you for cooperating with noob me!

@sankalpmukim Yes, one PR with individual commits for implementation, tests and documentation is usually a good way to arrange it. No need to mention the issue number in every commit - having a commit message that's immediately understandable is more important. I'd probably use something like:

Implement full_url property on image renditions. Fixes #6803
Add tests for Rendition.full_url property
Add documentation for Rendition.full_url


Decreased vocalization

I'd like to request a 'decreased or reduced vocalization" term. Def. producing sound from the vocal organs less frequently or less loudly than expected (based on the definition for excessive vocalization). Parent term is MP:0001529, abnormal vocalization. In J:228203, mice emit fewer ultrasonic calls than wild-type mice.
Thanks,
Monika

MP:0020351


updated  ipdrone.py

Sets new features. Now this program can speak out in a welcome screen

rather useless ngl


Enet integration works beautifully only 1 error message

Hello Magnus,
I am very grateful to you for the effort you have put into the Enet integration for Home assistant. I am very happy with this.
I have Home Assistant running together with the Homey Pro 2023 and so I can control the whole house.
Everything works 100% I only have this error message in Home Assistant.
Is there something I haven't done right yet?

The error message (in red) says; "setting failed"
Thank you in advance for your response.
Best Regards,
Robert

Hi Robert,
Thank you for the kind feedback!
Has this error message always been there? Do you find any additional information in the log file?

Hi Magnus,
Thanks for your response, this notification has always been there (from the installation).
In the log I can't find any notifications.
I have a piece of "Config Entry" here;
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.12.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.11.6",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "6.1.63-haos",
"supervisor": "2023.12.0",
"host_os": "Home Assistant OS 11.2",
"docker_version": "24.0.7",
"chassis": "embedded",
"run_as_root": true
},
"enet": {
"version": "0.1",
"requirements": []
},
"hacs": {
"version": "1.33.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"google_home": {
"version": "1.11.0",
"requirements": [
"glocaltokens==0.7.0"
]
},
"dwains_dashboard": {
"version": "3.6.0",
"requirements": []
},
"homey": {
"version": "1.1.0",
"requirements": []
}
},
"integration_manifest": {
"domain": "enet",
"name": "Enet Smart Home",
"config_flow": true,
"documentation": "https://github.com/mnordseth/enet-homeassistant",
"issue_tracker": "https://github.com/mnordseth/enet-homeassistant/issues",
"requirements": [],
"ssdp": [],
"zeroconf": [],
"homekit": {},
"dependencies": [],
"version": "0.1",
"codeowners": [
"@mnordseth"
],
"iot_class": "local_polling",
"is_built_in": false
},
"data": {
"config_entry": {
"entry_id": "41f2314bf5f20ac1360b47af3d68bb6e",
"version": 1,
"domain": "enet",
"title": "Enet Smart Home",
"data": {
"url": "http://192.168.xxx.xxx/",
"username": "xxxxx",
"password": "xxxxxxxxxxxx"
},
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": null,
"disabled_by": null
},
"enet_data": [
{
"uid": "5e2c69ad-f6dd-431a-b355-f5c2000003ce",
"typeID": "DVT_SA1M",
"metaData": {
"serialNumber": "000a01391715"
},
"installationLocationUID": "5e2c69ad-f6dd-431a-b355-f5c20000011d",
"installationArea": "Veranda",
"batteryState": null,
"isModified": false,
"isSoftwareUpdateAvailable": false,
"usedLinkResources": 12,
"securityMode": "SECURE",
"deviceChannelConfigurationGroups": [
{
"no": 0,
"deviceParameters": [],
"deviceChannels": [
{
"no": 255,
"channelTypeID": "CT_DEVICE",
"writeProtected": false,
"active": true,
"effectLocationUID": null,
"effectArea": null,
"inputDeviceFunctions": [],
"outputDeviceFunctions": [],
"deviceParameters": [],
"deviceChannelDependency": null


pre/post compile hooks

From @pixeleet on August 15, 2016 10:26
As a Developer using the Deis platfrom I'd like to have pre/post compile hooks available for dockerfile based builds too, so I can execute checks that my services required for tests are alive and execute tests after an image has been made. Thus making my flow more CI/CD enabled.
Copied from original issue: deis/dockerbuilder#89

From @mboersma on September 13, 2016 21:17
This general idea works well for buildpack-based apps (now that deis/slugbuilder#104 landed).
It would be useful to have a similar pre-/post-compile hook mechanism for Dockerfile apps, as well as for deis pull deploys. We should put some thought into how to implement that in a consistent way--suggestions welcome!

From @robholland on October 14, 2016 13:6
This probably belongs on deis/controller then?

From @pixeleet on October 14, 2016 13:55
So controller would setup the service you depend on for testing? Would it work with shell scripts? Would it be a DSL like some ci systems use? How do you imagine it working @robholland?

From @robholland on October 14, 2016 20:56
Simplest functionality would be to specify commands that are run inside the container after build/pull. This would be useful for asset compilation for example, which needs to be run with the correct environment.

From @robholland on October 18, 2016 16:23
How about:
$ deis hooks:post:list
=== app Post Hooks
$ deis hooks:post:add 'bundle exec rake assets:precompile'
=== app Post Hooks
bundle exec rake assets:precompile
$ deis hooks:post:remove 'bundle exec rake assets:precompile'
=== app Post Hooks

The registered commands are run inside the docker container after build and before deployment to k8s.

From @bacongobbler on October 14, 2016 15:20
I still think it's fair to keep it here for the time being until someone writes out a design document/PR for the proposed feature.

From @bacongobbler on October 18, 2016 16:44
I'm concerned about the added time to run the one-off command in the same API call as when we build the app. We're already seeing a large number of issues come in that's usually ELB-related with the builder timing out.
If you're willing to take a crack at a PR as well as some end-to-end tests, I don't see an issue with the proposal as long as it works.

From @bacongobbler on March 22, 2017 21:5
Does anyone have the time to work on this or shall we remove from the milestone since the cut-off for v2.13 is April 3rd?

From @mboersma on March 22, 2017 21:15
It seems unlikely we can tackle this in time for v2.13. I'll kick it into the future.


Add https://clearbit.com/resources/tools/connect to mail addresses section

hey @edoardottt i have a request to add https://clearbit.com/resources/tools/connect to mail addresses section
Clearbit Connect: A Gmail extension that helps you find email addresses and other information about your contacts.
@edoardottt  pls add hacktober fest label to it

@ExitoLab pls assign this issue to me

I already know this product, but it's an extension not an online service


8.3.0 Examples link is 404

The currently published docs on redux-form.com has its Examples page returning a "404" page:
https://redux-form.com/8.3.0/examples/

And, if you click on the example links in the nav sidebar, such as the Simple Example at https://redux-form.com/8.3.0/examples/simple/ then all of the sidebar links become /8.2.2/ instead of /8.3.0/

Also please check codesandbox examples. There are outdated versions of react, redux-form and redux libraries in it.
Thanks!


Move the bigchaindb/nginx_3scale repo under this repo & make edits

Krish and I discussed this in a private channel. The idea is to move the contents of the bigchaindb/nginx_3scale repo under the k8s/nginx-3scale/ directory in this repo, so it's more like the k8s/nginx/ directory (and other subdirectories of k8s/).

[ ] Merge all outstanding pull requests in the bigchaindb/nginx_3scale repo.
[ ] Move all the files over, so that the new directory structure is similar to k8s/nginx/.
[ ] Update the top-level LICENSES.md file in this repo to mention another exception: the licensing of things in the k8s/nginx-3scale/ directory is described by a separate LICENSE.md file in that directory.
[ ] Update the README.md file.
[ ] Move any outstanding issues on the bigchaindb/nginx_3scale repo to this repo.
[ ] Delete the old bigchaindb/nginx_3scale repo.

Maybe also rename nginx_entrypoint.bash?

Pull request takes care of the following aspects:

Move all the files over, so that the new directory structure is similar to k8s/nginx/.
Update the top-level LICENSES.md file in this repo to mention another exception: the licensing of things in the k8s/nginx-3scale/ directory is described by a separate LICENSE.md file in that directory.
Update the README.md file.(There was no change in the README.md)
Renaming nginx_entrypoint.bash -> nginx_3scale_entrypoint.bash

Outstanding issues are migrated to bigchaindb/bigchaindb repo. #1725, #1726, #1727
No pending PRs left on bigchaindb/nginx_3scale.
We can delete the bigchaindbd/nginx_3scale repo we merge the PR.

We should ideally not delete this repo till we are sure that we will never need it.
If and when we roll back the split nginx changes for websocket support, we will need this old code and the associated history.


Improve handling cloudflare errrors

If a domain is in a deletion process, we cannot get analytics.
On this error, we continue on others domains, now

You should split the bump from the error handling in a separate PR


Button checked state is hard to be seen in some themes

Describe the bug
special in some "dark light" themes. here are examples
Charlotte themes:

Emilia:

official:

To Reproduce
pass
Expected Behavior
make it clear
Environment
Windoes
GoLand 2023.1.1
Build #GO-231.8770.71, built on May 3, 2023

Probably very similar or the same as #649?

Probably very similar or the same as #649?

yes，and just like #659 . it should be a feature. bug report is a mistake.
anyway, it is a feature for usability

Yeah I see the issue, thanks for submitting.


Text coloring on hex values are two different colors

VSCode Version: 1.18.1
OS Version: Windows 10

Steps to Reproduce:

Open python file, as an example
Write "someVariable = 0x2564"
See that "0x" is not the same color as "2564"

Reproduces without extensions: Yes

This issue was moved to MagicStack/MagicPython#112


problem with loader

this is my problem when I use this problem:
./node_modules/react-to-pdf/dist/module.js 43:32
Module parse failed: Unexpected token (43:32)
File was processed with these loaders:

./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|       format: this.options.page.format,
|       orientation: this.options.page.orientation,

  ...this.options.overrides?.pdf,

|       unit: "mm"
|     });

@doudouinfo check out this it's the same error as of yours
https://github.com/wojtekmaj/react-pdf/issues/1043


feat: change callbacks for useBeforePhysicsStep and useAfterPhysicsStep to be mutable

feat: change callbacks for useBeforePhysicsStep and useAfterPhysicsStep to be mutable

borrowed approach from @react-three/fiber useFrame - https://github.com/pmndrs/react-three-fiber/blob/master/packages/fiber/src/core/hooks.tsx#L64
without this, updated callbacks with state changes won't be called

An alternative approach could be providing a dependencies array

Would it make sense to add a DependencyList to the useXXXPhysicsStep instead?
useBeforePhysicsStep(() => {
 // do something with someThing
}, [someThing])

Is there a benefit from using a ref?

@wiledal I'd be happy with either. The ref approach is what useFrame uses, so I was going for consistency.
The biggest pro for the ref approach I think is simplicity - you can't accidentally forget to include a dependency. And you can still wrap the callback in useCallback if you really want that behaviour.

Rebased on main. Let me know if you're ok with the approach 🙂


FBNeo does not load Neo Geo games with last update

I updated via WiFi to the latest version and now I can't load the Neo Geo roms using Retroarch, I only get a black screen and it doesn't seem to do anything else. They were working fine before the update.
I tried other roms (CPS1, CPS2...) using the same core (FinalBurn Neo v<IP_ADDRESS> e8106ea65) and they are working as expected, no issues there, only with Neo Geo roms.

I was able to load 2020 Super Baseball, Art of Fighting, Art of Fighting 2, and Metal Slug without issue on my end after the same updates.  I even tried on a new image and completed the same updates, and same result.  I can't replicate this issue on my end.

Works for me, tried different games?

It seems like a weird issue, I couldn't load any of the games in the neogeo directory, but I deleted the games and loaded them again and now they work. I still don't know what happened, but it doesn't seem to be related to the new version. Not sure if it's worth studying the issue or just close it

Closing due to not being able to replicate and issue was resolved by reloading the games into the neogeo directory.


Unity Bugs out when using Fancy Zones Transparency

Microsoft PowerToys version
0.67.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce

Turn On Fancy Zones
Tick "Make Dragged Window Transparent"
Move Unity Main Window with Fancy Zones

✔ Expected Behavior
The Unity Main Window Becomes Transparent and Moves to different zones as expected
❌ Actual Behavior
The Unity Main Window Becomes Black / Unresponsive
Other Software
No response

Seeing this too.
This has been a problem since 2020, see https://github.com/microsoft/PowerToys/issues/4451

Are you still experiencing this issue? /needinfo

Are you still experiencing this issue? /needinfo

Yes I checked on PowerToys Version v0.85.1 and unity 2022.3.46f1. And the issue still persists.
I would like to add that the issue occurs whey you resize the window as well as when you minimise and maximize a window. with the transparency feature off there are no issues whatsoever


LC_MONETARY is not respected

Pretty much the same issue as #11.
Everything is shown as GPB, but I'm expecting to see EUR. My LANG is en_GB.UTF-8, but LC_MONETARY is set to de_AT.UTF-8.

When I start the application, I get the warning Locale not supported by C library. Using the fallback 'C' locale.
I'm using version 2023.1.0-beta1 from flathub beta.

See: https://stackoverflow.com/a/30892121
What happens if you set both language and format to de_AT.UTF-8?

What happens if you set both language and format to de_AT.UTF-8?

A crash 😄
$ flatpak run org.nickvision.money

(process:2): Gtk-WARNING **: 23:20:05.767: Locale not supported by C library.
	Using the fallback 'C' locale.
Registering new type NickvisionMoneyGNOMEViewsMainWindow with parent AdwApplicationWindow
Unhandled exception. System.FormatException: String '31/01/2023' was not recognized as a valid DateOnly.
   at System.DateOnly.ThrowOnError(ParseFailureKind result, ReadOnlySpan`1 s)
   at System.DateOnly.Parse(String s, IFormatProvider provider)
   at NickvisionMoney.Shared.Models.Account..ctor(String path) in /run/build/org.nickvision.money/NickvisionMoney.Shared/Models/Account.cs:line 92
   at NickvisionMoney.Shared.Controllers.AccountViewController..ctor(String path, Localizer localizer, EventHandler`1 notificationSent) in /run/build/org.nickvision.money/NickvisionMoney.Shared/Controllers/AccountViewController.cs:line 92
   at NickvisionMoney.Shared.Controllers.MainWindowController.AddAccount(String path, Boolean showOpenedNotification) in /run/build/org.nickvision.money/NickvisionMoney.Shared/Controllers/MainWindowController.cs:line 131
   at NickvisionMoney.GNOME.Views.MainWindow.<>c__DisplayClass58_0.<CreateRecentAccountRow>b__0(Button sender, EventArgs e) in /run/build/org.nickvision.money/NickvisionMoney.GNOME/Views/MainWindow.cs:line 550
   at GObject.Signal`1.<>c__DisplayClass2_1.<Connect>b__1(Value[]& _)
   at GObject.Object.ClosureHelper.MarshalCallback(Closure closure, Value returnValue, UInt32 nParamValues, Value[] paramValues, Nullable`1 invocationHint, Nullable`1 marshalData)
   at GObject.ClosureMarshalCallHandler.<.ctor>b__2_0(IntPtr closure, IntPtr returnValue, UInt32 nParamValues, ValueData[] paramValues, IntPtr invocationHint, IntPtr marshalData)

Creating a new account works and correctly uses Euros. But I'd like to leave my language set to English and still use Euros.

A crash 😄

This is a separate issue. @fsobolev It has to do with
Date = DateOnly.Parse(readQueryTransactions.GetString(1), new CultureInfo("en-US", false))

on line 103 of the current Account.cs. Maybe we shouldn't set the culture info to US here since previous versions of Money could have non US formated dates.

Creating a new account works and correctly uses Euros, but I'd like to leave my language set to English and still use Euros.

See #128. We are adding settings to an account where you could change the currency used by the account from Money itself.

See #128. We are adding settings to an account where you could change the currency used by the account from Money itself.

That's good to hear, but I think defaulting to the correct currency would improve the user experience. locale -k currency_symbol returns "€" as expected, so I don't think my settings are broken.

so I don't think my settings are broken.

The currency_symbol is displayed as € since that was you have your formats set to de_AT.UTF-8. But since your language is en_GB.UTF-8 when an application tries to load the locale, it combines the two and tries to find en_AT.UTF-8 which is not a valid C locale in any program, hence why it doesn't display correctly.

A crash 😄

This is a separate issue. @fsobolev It has to do with
Date = DateOnly.Parse(readQueryTransactions.GetString(1), new CultureInfo("en-US", false))

on line 103 of the current Account.cs. Maybe we shouldn't set the culture info to US here since previous versions of Money could have non US formated dates.

I added a try catch block to loading the date.
It will first try to load using the en_US which newer Money files will be formated in and if that fails it will try to parse the date with the current locale.
try
{
    transaction.Date = DateOnly.Parse(readQueryTransactions.GetString(1), new CultureInfo("en-US", false));
}
catch
{
    transaction.Date = DateOnly.Parse(readQueryTransactions.GetString(1));
}

I've also made it so AddTransaction and UpdateTransaction save dates in en_US format in the database from now on as well.
https://github.com/nlogozzo/NickvisionMoney/commit/d11c534ecb4ae6995d2799a8a4edab5656eb407a

Maybe we shouldn't set the culture info to US here since previous versions of Money could have non US formated dates.

That's exactly the reason I added CultureInfo. Without this I got crashes when I tried to open files with mixed dates.

Maybe we shouldn't set the culture info to US here since previous versions of Money could have non US formated dates.

That's exactly the reason I added CultureInfo. Without this I got crashes when I tried to open files with mixed dates.

Yeah i realized that too. Hence I added the try catch so it can parse both forms of a date if needed.
But what do we do with something like
1/2/22
That could be Jan 2 or Feb 1 depending on the way you look at it.
Should we parse with the current culture first and then if it throws an error try en_US format?

Should we parse with the current culture first and then if it throws an error try en_US format?

Idk how it should be implemented in code, but I think that the app should look at the date and if it's not in en_US format rewrite it immediately. I guess this is the best way to fix all possible problems with dates formats.

Ok @SoMuchForSubtlety
Unhandled exception. System.FormatException: String '31/01/2023' was not recognized as a valid DateOnly. is being caused by a bug in the code where updating a transaction does not store the date in en_US format, which is what the Account expects.
I've fixed this issue for the next beta, however, it means that your .nmoney file is bugged.
As always, .nmoney files containing real data should never be used in beta versions for reasons as this.
However, if you need to recover data from that .nmoney file, please use DB Browser and open the .nmoney file in there and correct the date formats to en_US format. After that, the file should be able to open in Money.

We found a way to support LC_MONETARY individually. Will be added with #233

@SoMuchForSubtlety could you please tell what is the correct date format for de_AT locale? I mean in real world, not the format that GNOME Settings shows. Because it shows %Y-%m-%d, which seems to be incorrect, probably a bug in GNU libc.

It's dd.mm.yy or dd.mm.yyyy, but think officially we use ISO 8601.

Ah ok, we only ask because GNOME control center shows the format as DD-MM-YYYY but C# reports the format as DD.MM.YYYY
So as long as DD.MM.YYYY is valid that is what will be used by Denaro.

https://github.com/nlogozzo/NickvisionMoney/releases/tag/2023.2.0-beta1


Variable Expansion Divergence

Howdy. I recently opened up https://github.com/moonrepo/moon/issues/760 which is a project using dotenvy.
I wanted to raise a situation that we ran across with variable expansion and the need for curly brackets in order for dotenvy to parse successfully. In the past, we've used an .env file that looks like this:
export NODE_ENV=dev
export DEPLOY_ENV=$NODE_ENV

This works really well with both source .env (via shell) as well as parsers like the Node-standard https://github.com/motdotla/dotenv. Kudos for dotenvy also supporting export by the way. Recently we used a similar file with moon, which uses this project for its .env file needs, and were getting some unexpected results. The value for $DEPLOY_ENV was;

using source: dev
using Node dotenv: dev
using dotenvy: _ENV

The moon devs pointed out that we might have to use curly brackets, changing the file to:
export NODE_ENV=dev
export DEPLOY_ENV=${NODE_ENV}

And that worked fine, with dotenvy returning dev as expected. Here's where I think dotenvy diverges from the spec:
echo $SHELL is a parameter expansion, and parameters can contain underscores (https://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html), so substituting and empty string for the $DEPLOY portion of $DEPLOY_ENV is likely a bug. Curly brackets are only necessary for positional expansion or when the character that follows isn't a part of the variable/parameter name (https://tldp.org/LDP/Bash-Beginners-Guide/html/sect_03_04.html) so it looks like there's a possible bug in the implementation around that in dotenvy as well.

Issues also arise when using the same syntax for a $DATABASE_URL.
$DATABASE_URL="postgres://$POSTGRES_DB_USER:$POSTGRES_DB_PASSWORD@localhost:$POSTGRES_DB_PORT/$POSTGRES_DB_NAME"

Both sqlx and diesel fail to read the env var in this format.

An alternative crate dotenvs does not reproduce any of the failure cases noted by the two comments above. It may be a viable replacement to consider in the meantime.


load tracing policy provided by command line via sensor manager.

See: https://github.com/cilium/tetragon/blob/2ec5097ce3a7607b454b61b3e8ceead106841eb2/cmd/tetragon/main.go#L318-L336

I'm interested in it. Can you give me more information？


.analysis_options shouldn't be a hidden file

The analysis options file is similar to pubspec.yaml in that developers should be able to see it and edit it. It's not like .packages which is normally machine-generated. Therefore I argue that it shouldn't be a hidden file - we should make it visible for all to see.
(It should probably also have the .yaml extension so the editors will do the right thing.)

See also #23927

analysis_options.yaml is an option now. Is that enough to resolve this issue or do we want to wait until .analysis_options is fully removed?

Closing in favor of https://github.com/dart-lang/sdk/issues/28385 which has longer discussion.


[WebSub] Add log to identify error reported in #13605

Purpose

Add logs to identify possible error reported in https://github.com/ballerina-platform/ballerina-lang/issues/13605 as it was not observed after that and could not reproduce.

Codecov Report

Merging #14033 into master will increase coverage by <.01%.
The diff coverage is 88.23%.

@@             Coverage Diff              @@
##             master   #14033      +/-   ##
============================================
+ Coverage     64.59%    64.6%   +<.01%
  Complexity      426      426
============================================
  Files          2156     2156
  Lines         95624    95628       +4
  Branches      12749    12749
============================================
+ Hits          61773    61776       +3
  Misses        28838    28838
- Partials       5013     5014       +1

Impacted Files
Coverage Δ
Complexity Δ

...rinalang/net/websub/nativeimpl/GetSubscribers.java
90% <88.23%> (-10%)
0 <0> (ø)

...allerinalang/net/jms/LoggingExceptionListener.java
50% <0%> (-50%)
0% <0%> (ø)

...ain/java/org/ballerinalang/net/websub/hub/Hub.java
69.53% <0%> (-1.57%)
0% <0%> (ø)

...et/http/actions/httpclient/AbstractHTTPAction.java
79.14% <0%> (+0.85%)
0% <0%> (ø)
:arrow_down:

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
84.56% <0%> (+1.85%)
0% <0%> (ø)
: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 862fb79...dc9062d. Read the comment docs.


Fix NDArray ToDLPack Bug

Description
Fix Issue #13658
The variable shape in DLTensor is pointed to the TShape instance in tblob_ in NDArray.
However, the NDArray instance in NDArrayDLManager is different from the original NDArray instance.
Test Case written by @jermainewang
import mxnet as mx
import numpy as np
import tvm

def foo():
  x = mx.nd.array([0, 5], dtype='int64')
  dl = x.to_dlpack_for_read()
  return tvm.nd.from_dlpack(dl)

for i in range(10):
  y = foo()
  y.asnumpy()

Command:
for i in {0..100}; do echo $i && python3 t.py || break ; done

The test is passed more than 300 times on Ubuntu 16.04.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Tiny Changes. The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Fix NDArray::ToDLPack

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

LGTM. Thanks @wkcn .


offline image processing.

I have app, which has requirement of scan business card and convert it in contact, this sdk full fill my requirement but that not enough, we need scan business card offline as without having a internet, so will it possible with this sdk, if yes, then please let me know how?
Thanks.

Hello! We suppose it could more convenient for you to use FineReader Engine SDK or Mobile Capture SDK. Please check the suitable solution with our sales team<EMAIL_ADDRESS>

Reopen it if you have other questions.


Issue with hyphens in build args used in FROM

Hi thanks for a great tool.
I'm taking the Dockerfile and devcontainer.json from here.
The ARG for setting the ${VARIANT} contains a dash which seems to create a problem with the passing of command-line args in this script.
Here is the error I get:
docker: invalid reference format: repository name must be lowercase.
See 'docker run --help'.

and the debug output is:
Using workspace -v
[DEBUG] CONFIG_DIR: ./.devcontainer
[DEBUG] CONFIG_FILE: devcontainer.json
[DEBUG] CONFIG:
{
        "name": "Node.js",
        "build": {
                "dockerfile": "Dockerfile",
                "args": { "VARIANT": "16-bullseye" }
        },

        "customizations": {
                "vscode": {
                        "extensions": [
                                "dbaeumer.vscode-eslint"
                        ]
                }
        },

        "remoteUser": "node"
}
[DEBUG] DOCKER_FILE: /home/amo_chumber/scratch/devcontainer-test/.devcontainer/Dockerfile
[DEBUG] REMOTE_USER: node
[DEBUG] ARGS: --build-arg VARIANT="16-bullseye"
[DEBUG] SHELL: null
[DEBUG] PORTS:
[DEBUG] ENVS:
[DEBUG] WORK_DIR: /workspace
[DEBUG] MOUNT:  --mount type=bind,source=-v,target=/workspace
Building and starting container
invalid reference format
[DEBUG] DOCKER_IMAGE_HASH: Sending build context to Docker daemon  4.096kB
Step 1/2 : ARG VARIANT=16-bullseye
Step 2/2 : FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:${VARIANT}
docker: invalid reference format: repository name must be lowercase.
See 'docker run --help'.

I suspect this is a bash-ism with some quoting...

yeah definitely a bash-ism:
amo_chumber@cloudshell:~/scratch/devcontainer-test$ docker build -f .devcontainer/$(cat .devcontainer/devcontainer.json | grep -v // | jq -r '.build.dockerfile') $(cat .devcontainer/devcontainer.json | grep -v // | jq -r '.build.args | to_entries? | map("--build-arg \(.key)=\"\(.value)\"")? | join(" ")') .
Sending build context to Docker daemon  4.608kB
Step 1/2 : ARG VARIANT=16-bullseye
Step 2/2 : FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:${VARIANT}
invalid reference format

vs
amo_chumber@cloudshell:~/scratch/devcontainer-test$ docker build -f .devcontainer/Dockerfile --build-arg VARIANT="16-bullseye" .
Sending build context to Docker daemon  4.608kB
Step 1/2 : ARG VARIANT=16-bullseye
Step 2/2 : FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:${VARIANT}
 ---> f9bdb7d738da
Successfully built f9bdb7d738da

So changing line 57 to:
ARGS=$(echo $CONFIG | jq -r '.build.args | to_entries? | map("--build-arg \(.key)=\(.value)")? | join(" ")')
seems to resolve this but I'm not sure of the wider implications of removing the \" from around \(.value)...

Changing line 57 didn't fix it for me. I had to manually go in and change it so that it wasn't using an argument. That does seem to be the issue though. Good job!