INSTALLATION SUCCEEDED but Application is not installed on iPhone 6 plus

Hi , I have tried to install application using "react-native run-ios --device --udid *********************640b". i got log that says Installation INSTALLATION SUCCEEDED but application is not installed on iPhone. anyone have a idea?
Technical details
WebStorm: 2018.2
React:16.6.3
React-Native:0.58.3
Log:
** BUILD SUCCEEDED **
The following commands produced analyzer issues:
Analyze /Users/w***/WebstormProjects/app/node_modules/react-native/React/Base/RCTModuleMethod.mm normal arm64
Analyze /Users/w****/WebstormProjects/app/node_modules/react-native/Libraries/Image/RCTImageCache.m normal arm64
Analyze /Users/w*****/WebstormProjects/app/node_modules/react-native/Libraries/Network/RCTNetInfo.m normal arm64
(3 commands with analyzer issues)
installing and launching your app on iPhone ...
** INSTALLATION SUCCEEDED **

The same problem in iPhone 6s
iOS 12.1.4
{
  "name": "maya",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "immutability-helper": "^3.0.0",
    "lodash": "^4.17.11",
    "react": "16.6.3",
    "react-native": "0.58.5",
    "react-native-blur": "^3.2.2",
    "react-native-document-scanner": "^1.4.2",
    "react-native-elements": "^1.1.0",
    "react-native-fbsdk": "^0.8.0",
    "react-native-firebase": "^5.2.3",
    "react-native-gesture-handler": "^1.1.0",
    "react-native-google-signin": "^1.2.1",
    "react-native-image-picker": "^0.28.0",
    "react-native-linear-gradient": "^2.5.3",
    "react-native-vector-icons": "^6.3.0",
    "react-native-walkthrough-tooltip": "^0.5.0",
    "react-navigation": "^3.3.2",
    "react-redux": "^6.0.1",
    "redux": "^4.0.1",
    "save": "^2.3.3"
  },
  "devDependencies": {
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "24.1.0",
    "jest": "24.1.0",
    "metro-react-native-babel-preset": "0.52.0",
    "react-test-renderer": "16.6.3"
  },
  "jest": {
    "preset": "react-native"
  },
  "rnpm": {
    "assets": [
      "./assets/fonts/"
    ]
  }
}

** BUILD SUCCEEDED **

The following commands produced analyzer issues:
        Analyze /Users/macbook/Documents/freelance/react-native/maya/node_modules/react-native/React/Base/RCTModuleMethod.mm normal arm64
        Analyze /Users/macbook/Documents/freelance/react-native/maya/node_modules/react-native/Libraries/Image/RCTImageCache.m normal arm64
        Analyze /Users/macbook/Documents/freelance/react-native/maya/node_modules/react-native/Libraries/Network/RCTNetInfo.m normal arm64
(3 commands with analyzer issues)

installing and launching your app on iPhone Макс...
** INSTALLATION SUCCEEDED **

┌──────────────────────────────────────────────────────────────────────────────┐
│                                                                              │
│  Running Metro Bundler on port 8081.                                         │
│                                                                              │
│  Keep Metro running while developing on any JS projects. Feel free to        │
│  close this tab and run your own Metro instance if you prefer.               │
│                                                                              │
│  https://github.com/facebook/react-native                                    │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /Users/macbook/Documents/freelance/react-native/maya

Loading dependency graph, done.

The application opened for a few seconds and then closed.
Launched via Xcode.  The app is started but does not connect to hot reload.

I had the same problem this morning, when i tried to send to my iPod.
After some digging, I realized my signing process was all messed out. I had my provisioning distribution selected instead of development.
If you're signing your ipa file using an AppStore certificate, you can't install it directly on your iPhone without passing through Apple's review or AppStore first.
You can sign your release app with an Ad-Hoc certificate and test into a limited number of devices without passing through AppStore.
Anyway, for develop just make sure you have a iOS Development Provisioning selected.

Same here for us, we've tried multiple computers and mutliple iOS devices on multiple iOS OS versions and none install. We always get a 'info Installing and launching your app on devphone' at the end and indicates its been installed, but no app on the device, ever.


Security problem on Android 9

When I run the example program on Android 9, when I use Rust to register the Binder service and obtain the Binder interface, an error Parcel object will be returned, prompting EX_SECURITY. I'm running as root. I don't know if there is any way to solve this problem?

I don't recall encountering this, and I unfortunately don't have an Android 9 device to check on at the moment.


Remove unnecessary space at beginning of titles

Please remove the unnecessary space at beginning of titles, as it makes sorting in various applications with additional channels complicated.
E.g.:
#EXTINF:-1 group-title="Tokyo" tvg-id="nhkg_tokyo" tvg-logo="https://upload.wikimedia.org/wikipedia/commons/6/6f/NHK%E7%B7%8F%E5%90%88%E3%83%AD%E3%82%B42020-.png", NHK G
should be:
#EXTINF:-1 group-title="Tokyo" tvg-id="nhkg_tokyo" tvg-logo="https://upload.wikimedia.org/wikipedia/commons/6/6f/NHK%E7%B7%8F%E5%90%88%E3%83%AD%E3%82%B42020-.png",NHK G
Notice the removed space between the , and N.
Thank you very much!

Can you explain: "it makes sorting in various applications with additional channels complicated"?

Probably they mean sorting from A-Z is complicated due to the space before the channel title being present.
I don't know which client are they using and which other clients may have the same problem.


Fixing back Redirectable

Little hacky, but looks like it works.
Story: https://www.pivotaltracker.com/story/show/183760908

It should be sent with forms params, that the trick to save it between
validation errored requests. As for redirect shortcut I took it from
inherited resources documentation so it should be good.
On Thu, Dec 22, 2022, 20:58 Tiago Santos @.***> wrote:

@.**** commented on this pull request.
In app/controllers/concerns/back_redirectable.rb
https://github.com/wri/fti_api/pull/381#discussion_r1055805918:

def form(options = {}, &block)
if block.present?

 extended = Proc.new do |f|

   return_to = request.params[:return_to] || request.referer

   f.hidden_field :return_to, name: :return_to, value: return_to if return_to.present?

shouldn't it be also disabled so that it's not sent in the form params?
—
Reply to this email directly, view it on GitHub
https://github.com/wri/fti_api/pull/381#pullrequestreview-1228195830,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ2CLCQ3W5EUGPP73H6RHLWOSXGNANCNFSM6AAAAAAS4JV5DE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yeah, first time I use that to be honest.
On Thu, Dec 22, 2022, 21:02 Tiago Santos @.***> wrote:

@.**** commented on this pull request.
In app/controllers/concerns/back_redirectable.rb
https://github.com/wri/fti_api/pull/381#discussion_r1055808293:

@@ -1,36 +1,28 @@

frozen_string_literal: true
module BackRedirectable

def back_redirect
controller do

 def edit

   session[:return_to] ||= request.referer

   super

 end

 def new

   session[:return_to] ||= request.referer

   super

 end

def self.extended(base)

this gets evaluated just by extending the module?
—
Reply to this email directly, view it on GitHub
https://github.com/wri/fti_api/pull/381#pullrequestreview-1228199525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ2CLDXM7PYT3BJH2L3OOTWOSXUNANCNFSM6AAAAAAS4JV5DE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry looks like responding via email is not great as it responds to main thread.


Inconsistent behaviour in Cosmos Query Item because of use of kwargs

I found an issue while working with the cosmos SDK in python, when calling query_items (and it seems other calls as well) with partition_key=None or without the partition_key at all leads to different behaviours because of the build_options function that is referenced here:
https://github.com/Azure/azure-sdk-for-python/blob/663c846e4d24166f0e76092a80989cfd08521bf2/sdk/cosmos/azure-cosmos/azure/cosmos/aio/_container.py#L349
This function pops a whole lot of known arguments (partition_key among others) even when the value is None, which then leads the rest of the code that is handling kwargs to have nothing left to work with, so either that logic is redundant or a check if the value is None should be added to the build_options function.
Let me know if you need more info.
Code snippets:
This code works (as in when supplying an existing ID it returns the item) when address is not None, but does not work when address is None, because of the issue above.
[
    item
    async for item in self.container.query_items(
        query="SELECT * FROM c WHERE c.id = @id OR c.address = @address",
        parameters=[
            {"name": "@id", "value": item_id},
            {"name": "@address", "value": address},
        ],
        partition_key=address,
        populate_query_metrics=True,
    )
]

This doesn't works:
[
    item
    async for item in self.container.query_items(
        query="SELECT * FROM c WHERE c.id = @id OR c.address = @address",
        parameters=[
            {"name": "@id", "value": item_id},
            {"name": "@address", "value": address},
        ],
        partition_key=None,
        populate_query_metrics=True,
    )
]

This does work:
[
    item
    async for item in self.container.query_items(
        query="SELECT * FROM c WHERE c.id = @id OR c.address = @address",
        parameters=[
            {"name": "@id", "value": item_id},
            {"name": "@address", "value": address},
        ],
        populate_query_metrics=True,
    )
]

This is a great catch - thanks for the report @eavanvalkenburg!
@simorenoh, @JericHunter - would you be able to take a look?

Just noticed it is even worse, when passing a partition_key because the _build_options pops that out of kwargs it then runs logic to look for a partition_key and when it doesn't find one sets the feed_options['enableCrossPartitionQuery'] to True, so it does a cross partition query with a partition_key, potentially incurring higher RU's!

it will probably make most sense if the signature for query_items for both async and sync are the same and that would also solve this issue (with minor tweaks in the async code)

@eavanvalkenburg this is great, thanks for all the findings and the time spent looking into it! I'll take a look when I get a moment to do so, just wanted to let you know we're aware of the issue and pushed PR 👍

@simorenoh  Any update on this ?
It also prevents the use of the continuation token, as enableCrossPartitionQuery is always set to true:
query = container.query_items(
    query="SELECT * FROM c",
    partition_key=my_partition_key,
    enable_cross_partition_query=False,
    max_item_count=20,
)

pager = query.by_page(continuation_token=continuation_token)
page = await anext(pager)

items = []
async for item in page:
    items.append(item)

The above raises ValueError: continuation tokens are not supported for cross-partition queries.

Hi @Plouc314, sorry for the delay. From the time I last updated this issue a lot has changed, and I am no longer working in the Python SDK - I have assigned Jeric who is the new main developer to take over when he gets the bandwidth. Thank you for your patience!


Clone elements-imaging into this repository

Pushed from element-calcium-imaging as remote so that the version history is maintained.


[3.1.6] Test | Updating tests to acquire token from user-assigned managed identity (#2360) (#2473)

Backporting https://github.com/dotnet/SqlClient/pull/2473 to 3.1
Subsequently we are also backporting: https://github.com/dotnet/SqlClient/pull/2360

/azp run


[WIP] get rid of float in favor of sympy

Float is a source of imprecision, as #111 shows. I'm working on a pull request to get rid of float (and math) in favor of sympy, as suggested to @awcross1.
Please, comment on this issue if you have any thought.

Why not just check if the value is one to floating point precision, and then just set to one if so?  Adding an entire dependency for a single corner-case is probably not the way to go.

Hi @nonhermitian ,
There are several situations where dealing with floats is hard. There are several zero checks and simplifications that we can delegate to this library.

@lbello what's the status of this issue? I know there have been several commits regarding float to sympy migration.

For sure, the tools are still using floats. I will take a look to the rest. If it's just the tools, I would probably consider this done for now.

The coming approach is to handle sympy and numpy options. Give option to the user to have a symbolic representation or an efficient numpy as numbers. Soon, a PR about this.


Update /docs Dependencies

This PR updates the Gemfile.lock dependencies lockfile within the /docs subdirectory, to resolve Snyk warnings.

Thanks for helping out @evansims 👍🏻


add latest ubuntu image families to gce

add latest ubuntu image families to gce
Description
similar to https://github.com/apache/libcloud/pull/1358 we update the image families with the latest data from https://cloud.google.com/compute/docs/images
still unsure whether ubuntu versions that are now EOL and/or that are no longer listed on that page should be removed - so we just kept them around.

Looks like that Python 3.5 tests are failing because of some race, I will try to replicate it locally.

Pushed a fix for test failure in abbce640d974049f6c2a2c701e80c2cf8c680f59.

thank you for your work!


Troubleshooting 403 Errors

If you receive a 403 (Authorization Error) response from the Postman calls, check that you have configured RBAC for the user.
For Azure RBAC, refer to the following:
https://docs.microsoft.com/en-gb/azure/healthcare-apis/azure-api-for-fhir/configure-azure-rbac
[Enter feedback here]

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 74d0dae2-ed92-bad6-1a97-4fdcda016c07
Version Independent ID: ec5ca2c6-319a-1af5-eda3-95e84c7fac8d
Content: Web App Tutorial - Test connecting to Azure API for FHIR
Content Source: articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md
Service: healthcare-apis
Sub-service: fhir
GitHub Login: @CaitlinV39
Microsoft Alias: cavoeg

Hi @mike-westaway Thanks for your findings,We will investigate and update as appropriate

@mike-westaway Could you please clarify what the ask is?


[SPIKE] Addition of PostGIS

Is your spike related to a problem or idea? Please describe.
It was identified that there is a need for PostGIS.
Describe the outcome you'd like
Research was is needed to integrate PostGIS with our current Postgres solution. This should result in a number of issues to resolve this issue.
What is the reason or source for the spike
Internal request: EP-419
Additional context
https://postgis.net/

DoD checklist

[ ] Reader is able to understand the results of spike
[ ] The results of the spike are presented in a table (to show simply what are compared or researched parameters) / not applicable
[ ] Each value / cell in the results table is described more deeply below
[ ] Demo of the spike (automated as much as possible)
[ ] Design doc updated

As discussed with product team for now we are removing that from the scope.


Get domains list automatically from load-balancer service

As services grow in number, it become more tedious to add new service domains to DOMAINS var in letsencrypt stack. In my use case, most of the time, domains added to letsencrypt get added to (cattle) load balancer too. So why not making it automatically fetch domains from load balancer?

I'm not yet familiar with rancher-letsencrypt codebase, but here's roughly my implementation idea:
additional env vars with sample value:

DOMAINS_FROM_LB: stackname/lbservice
DOMAINS_FILTER: *.example.com

I have found that we can query certain lb's upstream hosts by making requests to Cattle's internal metadata service:
curl http://rancher-metadata.rancher.internal/latest/stacks/<stackname>/services/<lbservice>/lb_config/port_rules/<number>/hostname

What do you think? Any edge cases we should be cautious about?

Any update ?


Notifications indicator does not go away until you view another observation

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

As another user on the website, add a comment to one of your observations
Open the app
The notifications indicator in on the bell icon in the bottom tabs should appear
Tap on the bell icon to get to Notifications
Tap on the observation with an unread notification
Even though though you're looking at the content that triggered the notification, the indicator in the bottom tabs still appears
Tap the back button to return to Notifications
Notifications updates to show that the observation was viewed, but the indicator in the bottom tabs still appears
Go back to MyObs and view a different observation
Now the indicator goes away

Expected behavior
The indicator should reset when you view an observation, and if you're viewing the only observation that triggered a notification, the indicator should go away.
Context (please complete the following information):

Device: iPhone SE (3rd gen)
OS: iOS 17.3.1
App version: 0.24.0 (73)

Additional context
This is related to my work at https://github.com/inaturalist/iNaturalistReactNative/pull/1101/commits/9209a0ca79a19bf34a573aed7ec22ccfd0e6937d. Clearly that needs improving.

We'll work on this together next bugfix iteration.


python312Packages.aioairzone-cloud: 0.4.7 -> 0.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.aioairzone-cloud is: Library to control Airzone via Cloud API
meta.homepage for python312Packages.aioairzone-cloud is: https://github.com/Noltari/aioairzone-cloud
meta.changelog for python312Packages.aioairzone-cloud is: https://github.com/Noltari/aioairzone-cloud/releases/tag/0.5.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.1 with grep in /nix/store/9lqqh1fkh4drbqi4pykhlwfsfslrsfhb-python3.12-aioairzone-cloud-0.5.1
found 0.5.1 in filename of file in /nix/store/9lqqh1fkh4drbqi4pykhlwfsfslrsfhb-python3.12-aioairzone-cloud-0.5.1

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.airzone_cloud
python311Packages.aioairzone-cloud
python312Packages.aioairzone-cloud

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9lqqh1fkh4drbqi4pykhlwfsfslrsfhb-python3.12-aioairzone-cloud-0.5.1 \
  --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 python312Packages.aioairzone-cloud https://github.com/r-ryantm/nixpkgs/archive/31807cd7130658b16aab7da3f75d0507e6bee77d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/31807cd7130658b16aab7da3f75d0507e6bee77d#python312Packages.aioairzone-cloud

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9lqqh1fkh4drbqi4pykhlwfsfslrsfhb-python3.12-aioairzone-cloud-0.5.1
ls -la /nix/store/9lqqh1fkh4drbqi4pykhlwfsfslrsfhb-python3.12-aioairzone-cloud-0.5.1/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.airzone_cloud

4 packages built:

python311Packages.aioairzone-cloud
python311Packages.aioairzone-cloud.dist
python312Packages.aioairzone-cloud
python312Packages.aioairzone-cloud.dist

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 302765 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.airzone_cloud

4 packages built:

python311Packages.aioairzone-cloud
python311Packages.aioairzone-cloud.dist
python312Packages.aioairzone-cloud
python312Packages.aioairzone-cloud.dist


Nullish

I found a cool way to optimize my functions using the Nullish coalescing operator (??) but jshint does not like it. It is something wrong that I have done or is this just not a feature that is currently supported?

Having the same issue. hope this will be fixed soon.


Mat/Pat - Missing word in Before you Begin

AC

[ ] Change "HR Centre" to "HR Service Centre" as shown above in the Before you begin tab.

This is the bullet under 'Privacy'

Moving to PO


Custom DNS support.

Administrators can publish custom DNS resolution rules based on groups, and clients will accept DNS resolution according to the group rules and write them into the hosts file.

It could be me, but isn't this somewhat already a feature?

I'm sorry I didn't make it clear, but at the moment you can only have one domain name by setting the client name, but only one

I would like to have multiple domain names.

And I think that's possible to?

How should I proceed, please?

I understand, are you referring to using a custom DNS server to achieve support for more domain name mappings? I am hesitant to open another DNS server.

As far as I know, you can create a server/endpoint in your env and assign it an internal ip only. THen make that your dns server for the domains you wanna use. So yeah.

It's what I do for my infra.

@Cikaros  can you clarify what are you trying to achieve? What is the issue?

This can easily be done with coredns and again like @Codixer it is something I do in my own environment and outside the scope of this project


Compilation error

Hello,
I tried building the latest source, as of 2024.3.5, with MSVC 2022, but I get the following build errors:
1>W:\Github\godotdec\godotdec\Program.cs(31,50,31,58): error CS1501: No overload for method 'FileOpen' takes 3 arguments
1>W:\Github\godotdec\godotdec\Program.cs(227,36,227,59): error CS1061: 'BinaryReader' does not contain a definition for 'Read32BitPrefixedString' and no accessible extension method 'Read32BitPrefixedString' accepting a first argument of type 'BinaryReader' could be found (are you missing a using directive or an assembly reference?)

Seems like I forgot to push the last commit. Oops. Should work now, the errors are caused by an outdated dependency.


Heatlayer radius over 80 creates strange object outside default heat

If I create heatlayer with radius over 80 it creates valid heatmap but outside that circle, something strange appears.
Code:
    var heat = L.heatLayer([], {         radius: 80,         minOpacity: .6,         opacity: 0.8,         blur: 100,         gradient: {             1.0: color,         },     });     heat.addTo(mymap);

It seems that bigger radius than some value is creating second object(?) outside default heat circle.

This doesn't only happen when the radius is over 80. I have the same issue with a higher blur value. As far as I can tell it happens whenever the blur value is greater than the radius with the size of the object increases with the blur value.
Code to reproduce issue:
 heatLayer = L.heatLayer(heatdata, {radius: 75,  gradient: gradient, blur: 80, maxZoom:18});
 heatLayer.addTo(map);

As a workaround: Import simpleheat 0.3.0 or later after importing Leaflet.heat.
Leaflet.heat includes a simpleheat version from 2014: https://github.com/Leaflet/Leaflet.heat/blob/fbca30069de2b8416be8c63110e5d258579e3169/dist/leaflet-heat.js#L1-L5
The issue has been resolved in simpleheat in 2015: https://github.com/mourner/simpleheat/issues/14, Version 0.3.0 has been released afterwards.
Using TypeScript and Webpack, we achieved this workaround: https://github.com/LSS-Manager/LSSM-V.4/commit/7d07baa219a70b60fb2d41433500994c7e5f5819 importing Leaflet.heat first, then simpleheat and afterwards we've assigned the imported simpleheat to the global scope.

Hi @jxn-30 is a release possible with this fix included? Thanks

Hi @jxn-30 is a release possible with this fix included? Thanks

I am not a maintainer of this project, so I am not in the power to do so. However, there already exists an Issue that also requests a new release: #132

Oh, ok, thank you anyway. I guess @IvanSanchez can do the new release?

Hi @jxn-30 is a release possible with this fix included? Thanks

I am not a maintainer of this project, so I am not in the power to do so. However, there already exists an Issue that also requests a new release: #132


Memory leak fixes in tests

Description
Fixes for leaks detected by ASAN (not complete).
Testing instructions
Unit tests; with ASAN.
Types of changes

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

Checklist

[x] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] I have read the guidelines for adding a new blockchain
[x] If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

Leak issues reduced from 671 to 517.
2020-11-20T16:21:56.8880178Z SUMMARY: AddressSanitizer: 21552 byte(s) leaked in 517 allocation(s).


1.24-13 doc

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


The provided authorization grant is invalid, expired, or  revoked While Sending email from Runbook

I followed This documentation to setup up email notification.
I am getting following error during the Runbook execution.  what could be the issue?
revoked","field":null,"help":null}]}
At line:72 char:13
+ $response = Invoke-RestMethod -Uri https://api.sendgrid.com/v3/mail/s ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod],
WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Here is the Runbook Logic
Param(
  [Parameter(Mandatory=$True)]
  [String] $destEmailAddress,
  [Parameter(Mandatory=$True)]
  [String] $fromEmailAddress,
  [Parameter(Mandatory=$True)]
  [String] $subject,
  [Parameter(Mandatory=$True)]
  [String] $content
)

$connectionName = "AzureRunAsConnection"
try
{
    # Get the connection "AzureRunAsConnection "
    $servicePrincipalConnection=Get-AutomationConnection -Name $connectionName

    "Logging in to Azure......."
    Add-AzAccount `
        -ServicePrincipal `
        -TenantId $servicePrincipalConnection.TenantId `
        -SubscriptionId $servicePrincipalConnection.SubscriptionId `
        -ApplicationId $servicePrincipalConnection.ApplicationId `
        -CertificateThumbprint $servicePrincipalConnection.CertificateThumbprint
    Write-Output "`n**********************************************"
    Write-Output "Currently working on subscription.. [$((Get-AzContext).Subscription.Name)]"
    Write-Output "**********************************************`n"
}
catch {
    if (!$servicePrincipalConnection)
    {
        $ErrorMessage = "Connection $connectionName not found."
        throw $ErrorMessage
    } else{
        Write-Error -Message $_.Exception
        throw $_.Exception
    }
}
# $Conn = Get-AutomationConnection -Name AzureRunAsConnectionNew
# Connect-AzAccount -ServicePrincipal -Tenant $Conn.TenantID -ApplicationId $Conn.ApplicationID -CertificateThumbprint $Conn.CertificateThumbprint | Out-Null
$VaultName = "poc-notifications1"
$SENDGRID_API_KEY = (Get-AzKeyVaultSecret -VaultName $VaultName -Name "SendGridAPIKey").SecretValueText
Write-Output "$SENDGRID_API_KEY"
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Authorization", "Bearer " + $SENDGRID_API_KEY)
$headers.Add("Content-Type", "application/json")

$body = @{
personalizations = @(
    @{
        to = @(
                @{
                    email = $destEmailAddress
                }
        )
    }
)
from = @{
    email = $fromEmailAddress
}
subject = $subject
content = @(
    @{
        type = "text/plain"
        value = $content
    }
)
}

$bodyJson = $body | ConvertTo-Json -Depth 4

$response = Invoke-RestMethod -Uri https://api.sendgrid.com/v3/mail/send -Method Post -Headers $headers -Body $bodyJson

@raghureddy45 Please provide us with the link to the documentation you are referring to so we can better assist.

@raghureddy45 I will close this. If you still have feedback please open a new issue directly on the doc you are referring to so we can better assist.


Support OAuth user login for ArcGIS Online org entered at runtime

Tweak the provided WinPhone and Desktop  OAuthAuthorize components to support this workflow.
We may also consider providing a WinStore OAutAuthorize component based on the WebView that supports this workflow (seems there is no way to support this workflow with the WebAuthenticationBroker)

Verified.  Unfortunately, on phone it requires use a web view instead of web authentication broker.


fix(MetadataWidget): fix view for large hierarchies

Large hierarchies should no longer be truncated or run over the edge. Moved problematic inline styles to the correct positions. Added some stories for testing.

:tada: This PR is included in version 1.20.12 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.22.18 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


0.5.0 try3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This is on top of #48

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Wow. Just Wow.
Linux:
which f2py3: $PREFIX/bin/f2py3
head f2py3:
#!/bin/sh
'''exec' $PREFIX/bin/python "$0" "$@"
' '''
# -*- coding: utf-8 -*-
import re
import sys
from numpy.f2py.f2py2e import main

OS-X X86:
which f2py3: $PREFIX/bin/f2py3
head f2py3:
#!/usr/bin/env python
# -*- coding: utf-8 -*-
import re
import sys
from numpy.f2py.f2py2e import main

OS-X Arm:
which f2py3: $BUILD_PREFIX/bin/f2py3
head f2py3:
#!$BUILD_PREFIX/bin/python
# -*- coding: utf-8 -*-
import re
import sys
from numpy.f2py.f2py2e import main

Any comments @conda-forge/help-osx-arm64  ?

This is I think the long existing bug in scikit-build re: cross compiling with numpy.  See https://github.com/conda-forge/zfpy-feedstock/blob/main/recipe/meta.yaml#L19-L20 for a patch example.

@erykoff I don't see the connection. The python interpreter is found fine. The f2py3 executable is being executed by the wrong interpreter (shell instead of python).

@erykoff  f2py3- h fails even before scikit-build or cmake is executed.

I've seen something related ... and I think this is a bug in the numpy feedstock.  The f2py, f2py3, and f2py3.X entry points should be defined here for non-windows: https://github.com/conda-forge/numpy-feedstock/blob/main/recipe/meta.yaml#L24-L25
Note that these are all the same; you can just call f2py instead of f2py3 but that won't fix it here, because the conda installer is putting the wrong header in when the entry point isn't defined in the feedstock.  And this can bite in weird and surprising places depending on how python is invoked.

The incorrect shebang is only occuring in the cross-compilation setup though. The entry-points are correctly installed and callable in the regular host setups for Linux and OSX-X86.

@conda-forge-admin, please rerender

Finally a successful build!
@murrayrm @repagh @moorepants
This is ready to merge.

Thanks for all of the hard work on this, @bnavigator!


Building sharp with libvips 8.7.1?

I'm running sharp in an Alpine Docker container and libvips has problem writing to /tmp. It looks like this is fixed (by Lovell): https://github.com/lovell/sharp/issues/1436
Setting VIPS_DISC_THRESHOLD to a really high number makes it work, but this doesn't seem like a stable workaround.
Is there any way of building sharp with libvips 8.7.1? Or even better, are there any plans to include 8.7.1 in sharp?
Edit:
BTW, thank you soo much for this awesome library!

Hello, sharp will look for and use a globally-installed version of libvips. If you need libvips v8.7.1 you can build it from source, install globally then rebuild sharp.

http://sharp.pixelplumbing.com/en/stable/install/

Thanks a bunch!
Do you know how building from source would affect my package-lock.json?

sharp will look for a globally-installed version of libvips that meets a required minimum. If it fails to find this it will download and use pre-built binaries of that version. These decisions are logged during npm install.
Installing a specific version of libvips globally before npm install is run against a lockfile will provide a reproducible build.


How to get the depth value of a specific coordinate through the stored depth picture.

I used the Intel RealSense Viewer tool in the SDK of the Intel Realsense D435 camera to store depth images. How do I get the depth value of a point of a specific coordinate of a depth image when processing a picture? For example, the point with coordinates (630,260).

Uploading 2018.7_Depth.raw…

I just got in touch with this camera. I am learning about it. The question I asked may be relatively simple, but please answer a specific point.

As I understood you want to display Depth data (distance ) of each pixel from frame_depth.
rs2::frameset frames;
frames = pipe.wait_for_frames();
// assuming that coordinates of pixel which you want extract depth is i = 600  ( for width) , j = 300 (height)
std:: cout << frame.get_distance(i, j) << endl;
Hope that it will help you, and waiting for your response.

Thank you for your answer.
However, I got some depth images that were previously taken by others using the Intel RealSense Viewer tool and stored as ".RAW" files and ".PNG" files. I want to be able to get deep data directly from these depth images instead of the RealsenseD435 device. How can I open a ".RAW" file or a ".PNG" file and get deep data?

Oki, in this case if you have saved some frames ( images in RGB or DEPTH form) you have to open them and get processing by using OpenCV library

Thank you for your answer.
I have installed the OpenCV library. However, I was unable to find a code example related to Realsense for learning. Can you provide some relevant code examples?
Looking forward to your reply.

Try these:
#include
#include
#include <opencv2/opencv.hpp>
using namespace std;
using namespace cv;
Mat frame;
frame = imread('DIRECTORY_OF_YOUR_IMAGE')
for ( int i=0; i<frame.rows; i++)
for ( int j=0; j< frame.cols; j++)
cout << frame.at(i,j)[0]<< frame.at(i,j)[1]<< frame.at(i,j)[2]<< endl; // TO ACCESS EACH PIXEL FROM DEPTH OR RGB FRAME of each CHANELL
namedWindow( "Display window", WINDOW_AUTOSIZE );// Create a window for display.
imshow( "Display window", image );
return 0;
}

I have solved the problem I have encountered. Thank you very much for your help.
If I have other problems, I will ask questions  on this next time.

[Realsense Customer Engineering Team Comment]
@TAREK-ELOUARET
Thank you for the solution.
@njnydxzc
Glad to see the solution solves your problem, I would like to close this ticket first. In the future if you have other question, please create another new issue, if the new issue related to this one, you can link them together. Is it okay?

Sorry to bother you again.
Our project requirements require specific depth values, at least to the nearest 0.01. However, I did not find the specific depth of each color in the depth image. How can I convert the value of RGB to a specific depth value?

@njnydxzc   I also encountered this problem:one people need save the depth image and others need get the deep from the depth image .How do you  solved the problem ?Please guide！ Thanks!

[Realsense Customer Engineering Team Comment]
Hi @njnydxzc,
Since #2231 is resolved, I will close this issue.

@njnydxzc , How did u solved the problem you encountered earlier ?
I want to get depth data directly from the depth images instead of the RealsenseD435 device. How can I open a ".RAW" file or a ".PNG" file and get depth data? In metres if possible .
Thanks in advance for the help .

Try these:
#include <opencv2/opencv.hpp>
include iostream
include vector
using namespace std;
using namespace cv;
Mat frame;
frame = imread('DIRECTORY_OF_YOUR_IMAGE')
for ( int i=0; i<frame.rows; i++)
for ( int j=0; j< frame.cols; j++)
cout << frame.at(i,j)[0]<< frame.at(i,j)[1]<< frame.at(i,j)[2]<< endl; // TO ACCESS EACH PIXEL FROM DEPTH OR RGB FRAME of each CHANELL
namedWindow( "Display window", WINDOW_AUTOSIZE );// Create a window for display.
imshow( "Display window", image );
return 0;
}

not working properly ... can write a code for depth raw file ?
and how to traverse depth and convert to rgb data ?


DRep Refunds and update evalTransactionBalance

Description
Closes #3645
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

I hope I have got it correct this time :cold_sweat:


[MOB-3251] add header_dir

🔹 Jira Ticket(s)

MOB-3251

✏ Description

add header_dir to the SDK Podspec so that use_frameworks! doesn't need to be in the Podfile anymore

Can you please verify that all our sample apps that use cocoapods are working fine after this change?

Can you please verify that all our sample apps that use cocoapods are working fine after this change?

We don't have any sample apps using Cocoapods, but I did test this with a brand new iOS project beforehand.

Can you please add more details about the solution? Why is this change needed and what does it do?


Trouble configuring Xp / Damage / Hp of wolves upon level up

I have tried multiple times to customize the hp, attack damage, and required experience for each level. For some reason, Whenever I launch the server my changes are reverted back to their default values. I have tried /md reload, and I make all the changes in the config file while the server is closed. For example, if I set the health value at level 2 to 40, when I launch the server the value will be set back to 21 health. Is there any other information I can provide you to help with this issue?

I'm gonna reopen issue #11, so if you could provide me with version of MyDog, server version, and maybe try to put the plugin on Debug, and then please send the the startup logs (use something like Pastebin or Gist).


Refactor MMDiT, add ImageToImage and Inpaint for SD3

This PR includes the following updates:

Refactor MMDiT that by replacing models.Sequential with new MLP layer, simplifying/clarifying the modulation process using new AdaptiveLayerNormalization layer
Add missing docstrings to MMDiT
Update the conversion script and the weights on Kaggle
Introduce ImageToImage task and apply it to SD3
Introduce Inpaint task and apply it to SD3
Fix bugs when calling save_to_preset with nested preprocessors and tokenizers

ImageToImage demo:
https://colab.research.google.com/drive/1Qz6WsLZXiuCtWZdxg_V1LuhkNUMm0E9F?usp=sharing

Reference Image
Generated Image (1024x1024)

Inpaint demo:
https://colab.research.google.com/drive/1uFqXgzGctd5KGygOptq8hGoRpZht0rGW?usp=sharing

Reference Image
Mask
Generated Image

@divyashreepathihalli

I have refactored the arguments for all TextToImage, ImageToImage and Inpaint tasks to use a single inputs, which aligns with CausalLM.
The logic in generate is now similar to that of CausalLM. The downside is that users may need to provide a dict as inputs which could be a bit ambiguous.

This is clearer and more consistent with the other generative models!!


Simplify lambda environment variables

I'm wondering why we are adding individual variables for endpoints etc. to each lambda. We get apiendpoints and adminendpoints and s3endpoints. It all seems a bit excessive and frustrating to use.
I'm wondering why we don't just have an amplifyconfig variable that is essentially the awsconfig.js file in json format...this way we can just pass it to Amplify.config and everything is ready to go...

Thank you for your suggestion. Given that this enhancement hasn't gotten more traction, we're going to be closing this issue for now. If more people are running into this in the future, I'm more than happy to re-open this issue.


Improved Tracing Framework

This change introduces the Tracing type and extends the capabilities of QueryTrace.
The new Tracing type encapsulated if tracing is enabled or not. And when tracing is disabled, performs no-ops in place of the actual tracing operations.
Consider the following example:
public QueryTrace tracedMethod() {
  final Tracing tracing = Tracing.fromBoolean(true);
  final QueryTrace.NamedWatch parentWatch = tracing.watch(QueryTrace.identifier("parent"));

  final QueryTrace.Joiner parentJoiner = parentWatch.joiner();

  {
    final QueryTrace.NamedWatch childWatch = parentWatch.watch(QueryTrace.identifier("one"));
    /* do something that takes time */
    parentJoiner.addChild(childWatch.end());
  }

  {
    final QueryTrace.NamedWatch childWatch = parentWatch.watch(QueryTrace.identifier("two"));
    /* do something that takes time */
    parentJoiner.addChild(childWatch.end());
  }

  return parentJoiner.result();
}

When using Tracing.fromBoolean(false) in the above code, all the code involving tracing would become no-ops (apart from the dynamic dispatch). This makes it easier to write code where potentially expensive tracing can be disabled.
Tracing is serialized as JSON true or false (depending on if it is enabled), making it a drop-in replacement for the existing tracing option, which is a Boolean.

Current coverage is 45.10% (diff: 52.38%)

Merging #115 into master will increase coverage by 0.06%

@@             master       #115   diff @@
==========================================
  Files           596        597     +1
  Lines         15377      15431    +54
  Methods           0          0
  Messages          0          0
  Branches       1581       1586     +5
==========================================
+ Hits           6926       6960    +34
- Misses         7991       8010    +19
- Partials        460        461     +1

Powered by Codecov. Last update 758f2d4...3f2cb91

I'm not sure I fully understand the trace functionality, but this change looks good to me.
+1

@parmus you can see the tracing-type branch for how this is incorporated into the codebase.


Error "Payload 'b10109000001003c0020' failed CRC and checksum" after HA restart

Hello,
first of all, thank you for this great integration!
Since update from 2024.2.3 to 2024.3.1 everytime after Hass restart and also when HA is running an error occurs in the logger and constantly spamming the logger. I´ve tried it 2 times and in every case the error is shown in the log after HA restart an while HA is running. The integration (control the device) works without any problems.
Device in use:
Midea real cool 35 (mobile aircondition)
Error-Log (Screenshot):

Error-Log (Text):
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: msmart.device.AC.device
Quelle: custom_components/midea_ac/coordinator.py:38
Integration: Midea Smart AC (Dokumentation, Probleme)
Erstmals aufgetreten: 05:29:58 (1056 Vorkommnisse)
Zuletzt protokolliert: 09:00:44
Payload 'b10109000001003c0020' failed CRC and checksum. Received: 0x20, Expected: 0xBE or 0x8.
Payload 'b10109000001003c0000' failed CRC and checksum. Received: 0x0, Expected: 0xBE or 0x8.
Payload 'b1010900000100300000' failed CRC and checksum. Received: 0x0, Expected: 0xF3 or 0x14.
System in use (Raspberry Pi 4 8GB)

Maybe its an fault on my side but I didn´t change anything in my environment.
Would be great if there is an bugfix in an future update - thx. a lot!
Regards
Michi

Hi. Thanks for using the integration and sorry about the trouble its causing.
If you don't mind, can you enable debug logging and post the full logs here?
After that, you can try downgrading to 2024.2.3 via HACS to resolve these warnings.

Here the full logfile after enable debug logging. Hope this is helpful. Let me know if I can support you in any way...
home-assistant_2024-03-13T16-08-44.830Z.log

Thanks!
My best guess is it's some device quirk/bug specific to the "new" protocol. The other packets have valid CRCs.
I figure the fix will be detecting when a device sends bad CRCs and disabling the check.

I've got a fixed lined up for you in https://github.com/mill1000/midea-msmart/pull/114
Would you be comfortable testing this? It would require updating the msmart-ng package on your HA instance/container.

Hmmm...thanks, but the problem is that I do not know how to update my container 😬. Would you be so kind and tell me how?

I'll make it easy for you. I've merged the fix into the main branch.
You can just use HACs to install the main branch instead of a specific release

Hi,
thanks for making my life easier ;)
I´ve installed the "main" branch and did some tests (turn on/off, changed modes fan_only/cool), changed fan speed and temperature) an no errors are logged. When I restartet HA an CRC related error occured a few minutes after restart, maybe its not depending to HA restart?!?
home-assistant_2024-03-15T08-01-25.235Z.log
It is not repeatable, sometimes after restart HA the error occurs and sometimes not. Unfortunately I forgot to enable debug messages. I will enable debug logging and stay on this "main" branch. If any error occurs i will report them...
Thx. a lot!

Hi again,
now i have an CRC error logged with debug logging on. The error occurs during using the device (perform some tests).
home-assistant_midea_ac_2024-03-15T08-22-16.597Z.log
The CRC error does not constantly spamming the logger. Hope this logfile helps for further investigation.
Thx. for your effort!!!!

Hi,
also got this error - Unfortunately debug logging was not enabled...
Error from Logger:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: msmart.device.AC.device
Quelle: custom_components/midea_ac/coordinator.py:38
Integration: Midea Smart AC (Dokumentation, Probleme)
Erstmals aufgetreten: 12:03:36 (1 Vorkommnisse)
Zuletzt protokolliert: 12:03:36
Payload 'b10109000001003c0000' failed CRC and checksum. Received: 0x0, Expected: 0xBE or 0x8.
Regards
Michi

Same here. I just enabled debug logging.

Thanks for the logs, at least there's a little improvement.
I guess the solution will need to be a little more involved.

Let me know if you need anything (testing, debug logs,...). As mentioned above, I will stay on main branch till a newer update is available.
Thank you!

Alright just push another update to main that I hope will resolve those final CRC errors.

Okay merci! I redownload the main branch again and report the results.

Hi,
Good news, no errors since last "main" branch update. Several checks (HA restart, device use) performed 👍🏽. For me, you can mark this as closed and I will stay on this main branch till a newer version is available.
Now summer can come 😏
Thank you very much!!

That's great to hear! Could you do me one favor and grab another debug log of the device running for about a minute?
There was one additional minor quirk I addressed and would like to confirm it's fixed

For sure, you will get this debug log in about 5-10 minutes.

I´ve turned on the device in AUTO MODE and change to FAN_ONLY and change some other parameters like temperature, swing mode on/off, swing position, fan speed high/auto and back again till I turned the device off.
Debug-Log:
home-assistant_midea_ac_2024-03-16T07-03-19.629Z.log
Let me know if i can do more for you!

Released in 2023.4.2


graphql api

API updates for parameter and mult

ParameterPageService.deletePage(..) is missing - this is needed for the service tests.


Add version check for Julia 1.1.

Resolves #193

The other thing you will want is: https://github.com/vchuravy/GPUifyLoops.jl/blob/951ddadfecb47b5636129d45467316aa185b32e3/Project.toml#L11


No insiders updates

VSCode Version: 1.4.0-insiders (e3758d2cdaae78082a08a45ae28ea1bed5f47e8c)
OS Version: OSX 10.11.6

Hi awesome VSCode team,
Best part of starting new day was to have a fresh coffee and fresh update of insiders.
For some reason updates of my insiders stopped - is there some problem with auto builds or is it the problem on my side. My version is e3758d2cdaae78082a08a45ae28ea1bed5f47e8c and that commit was from Jul 29.
When I check for updates I get:

During the end game, and until the new build is declared, the insider build represents the release candidate. As we stabelize, there will be only few fixes, and the insider build might not change for a few days. Once the final build is declared, the insider build will return to be a daily build representing the latest development.


Fix RegistryWalker

Walker was improperly appending \ to the key in the registry collector when the subkey was the first portion of the path in the hive, preventing deeper walking.
Fix #700

/azp run


[ELWIC] Infinity Complex - Module crashes on shutdown

Module Information

Identifier: ELWIC
Module Name: Infinity Complex
Version: 6.04

Describe the bug
Module crashes on shutdown
To Reproduce
Steps to reproduce the behavior:

Add module to moduleConfig.json
Start MBBSEmu
CTRL-C and shutdown MBBSEmu
Module crashes on shutdown routine

Expected behavior
Module shuts down normally
Screenshots
2020-09-01 20:12:48.6764 Info MBBSEmu.HostProcess.MbbsHost.<Shutdown>b__18_0 Calling shutdown routine on module ELWIC
2020-09-01 20:12:48.6888 Warn MBBSEmu.Btrieve.BtrieveFileProcessor.SeekByKey Adjusting Query Key Size, Data Size 7 differs from Defined Key Size 25
2020-09-01 20:12:48.6888 Warn MBBSEmu.Btrieve.BtrieveFileProcessor.SeekByKey Adjusting Query Key Size, Data Size 8 differs from Defined Key Size 25
Unhandled exception. System.Exception: Unknown GetOperandOffset MemoryBase
   at MBBSEmu.CPU.CpuCore.GetOperandOffset(OpKind opKind)
   at MBBSEmu.CPU.CpuCore.GetOperandValueUInt16(OpKind opKind, EnumOperandType operandType)
   at MBBSEmu.CPU.CpuCore.Tick()
   at MBBSEmu.HostProcess.ExecutionUnits.ExecutionUnit.Execute(IntPtr16 entryPoint, UInt16 channelNumber, Boolean simulateCallFar, Boolean bypassState, Queue`1 initialStackValues, UInt16 initialStackPointer)
   at MBBSEmu.Module.MbbsModule.Execute(IntPtr16 entryPoint, UInt16 channelNumber, Boolean simulateCallFar, Boolean bypassSetState, Queue`1 initialStackValues, UInt16 initialStackPointer)
   at MBBSEmu.HostProcess.MbbsHost.CallModuleRoutine(String routine, Action`1 preRunCallback, UInt16 channel)
   at MBBSEmu.HostProcess.MbbsHost.Shutdown()
   at MBBSEmu.HostProcess.MbbsHost.WorkerThread()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadHelper.ThreadStart()

Software Information:

OS: Windows 2019 Server Standard
Telnet Client: N/A

API Report
{"UniqueIdentifier":"ELWIC","File":"ELWIC.DLL","Imports":{"DOSCALLS":[89],"PHAPI":[16],"MAJORBBS":[441,574,326,544,65,437,455,571,566,543,158,492,589,331,550,559,601,357,534,757,444,520,456,474,629,463,628,476,403,650,317,485,624,573,335,522,401,229,475,462,225,637,205,565,510,467,420,350,511,486,351,117,162,167,713,230,560,516,433,654,665,113,477,578,584,505,621,313,53,226,94,11,408,77,402,334,718,579,604,582,580,366,377,659,581,603],"GALGSBL":[40,37,59,21,7,72,36]}}

I was able to get the module to init locally.
Delete any .EMU files that might be there from previous versions of MBBSEmu and give it another go.
Just to verify, my local demo version is iNfInItY CoMpLeX v6.04

You are correct, it just crashes on shutdown. -- changed issue

Issue caused by the operation:
{cmp word ptr es:[bx+di],0}
I've added handling for when the Memory Base is BX and the Memory Index is DI to the method GetOperandOffset
Also added the instruction to the error message to help with debugging in the future.
This method can probably be refactored to call Registers.GetValue() on the MemoryIndex value, but I'd want to be able to benchmark the performance impact of making a call from within this method. For now, the switch statement is fine.

Fixed in https://github.com/enusbaum/MBBSEmu/pull/85


Getting Reference ... is unresolved when generating from OAS3

Hi,
I was wondering if OAS3 was supported and gave it a go.
I used code from master, passed this spec as a launch argument.
Getting Thread 1: Fatal error: Reference #/components/schemas/User is unresolved
Not sure if it's a bug or something isn't supported yet.

Thanks for the report @Kastet. I've fixed the unresolved component here https://github.com/yonaskolb/SwagGen/pull/132
That spec still won't generate properly though, as an object schema can't be used as a path parameter. Would does the api expect to send? Just a simple string, or the whole user object encoded in some form?

Hi @yonaskolb ,
Thanks for looking into this. Agree that passing a complex object as a path param doesn't make sense.
However, $ref isn't necessarily an object schema, it can be just a type alias, for example
"UUID": {
        "type": "string"
      }

Would it make sense to allow $ref as path param provided its type is a primitive?

Yeah that should work fine. The reference isn’t the problem (anymore) it’s that the schema type is an object

Awesome!
Just tested and found one minor problem. The UUID schema resolves into a type alias public typealias UUID = String which exactly what I'd expect, but it collides with Foundation's UUID extension in Coding.swift
extension UUID {
    func encode() -> Any {
        return uuidString
    }
}

A simple fix would be changing the template to
extension Foundation.UUID {
    func encode() -> Any {
        return uuidString
    }
}

Thoughts @yonaskolb ?

Hmm, I'm not seeing this. There is a template option to map what ID is generated as (typeAliases.ID). It defaults to UUID
In Coding.swift this is then generated as public typealias ID = UUID.
Are you using the latest release, and the included template?

Yep, using 4.0.0.

And where are you getting the public typealias UUID = String from?

It's a model that gets generated from my a schema, to illustrate
"components": {
    "schemas": {
      "UUID": {
           "type": "string"
      },
      "User": {
        "type": "object",
        "properties": {
          "id": {
            "$ref": "#/components/schemas/UUID"
          },
         .....
    }
}

Oh I see, you have a custom schema that conflicts with Foundation. I would suggest using swaggers inbuilt format: uuid instead of a custom UUID schema (SwagGen will generate this as an ID typealias, which you can change what that resolves to in the template options). Alternatively you can update the template with your Foundation suggestion, but you'll continue to get clashes throughout your codebase.
Either way happy for you to create a PR to add the Foundation.UUID


Implement Create Dataset

This PR adds some initial capability to create a Dataset.
All of the small pieces of functionality added here are largely based on what the Pennsieve API "Create Dataset" endpoint performs. Each of these attempt to stand on their own; there is not yet a single entry point which fully mimics the Pennsieve API "Create Dataset" endpoint -- this function will likely need to be added to the new Datasets Service and/or added in a higher level module or package in Pennsieve Go Core.
Included are some of the surrounding and necessary capabilities to deal with getting and (in some cases) creating:

Dataset Status
Data Use Agreements
Organization Users (workspace membership)
Contributors

There are some ToDo items and refactoring that I would like to get to eventually (this is just a short list):

standardize and centralize Error types
simplify the "not found" Error to a single Error type
add more table-driven data in the tests


filter: add capability to selectively dump request/response state on crash

Description
Added a new configuration option in the Bootstrap to control whether headers and trailers should be included in the state dump during crashes. This feature allows more secure debugging by redacting sensitive information from logs.
Fixes #37793

Commit Message: filter: add capability to selectively dump request/response state on crash
Additional Description: Add new config in Bootstrap to control whether the headers/trailers should be dumped during the crash.
Risk Level: Low
Testing: Added Unit tests
Docs Changes: Added
Release Notes: Added

/assign @phlax


added upgrade documentation for 0.9 to 1.x

included objectives described here: https://github.com/prometheus/client_ruby/pull/95

closing in favor of https://github.com/prometheus/client_ruby/pull/125


Reason for major version bump to 7.x?

First of all, don't get me wrong, I'm really excited about the new release, and appreciate all of the hard work that went into it...
I'm just wondering why the major version was bumped to 7. Looking at the changes from 6.6.0 to 7.0.0, there don't seem to be any breaking changes, as would be indicated by the version bump.

Perhaps @seuros was being overly cautious? I'm not aware of breaking changes, fwiw.

@swrobel , sorry for delay.
We will always bump to a major version when supporting a new version of ActiveRecord.  While support for the versions stayed the same this time. the syntax of some  files changed (Some raw sqls string are now in Arel).
If there was a regression, we won't affect people that locked their version in ~> 6.6.0 while trying to fix the bug.


Linkup READMEs of xenon-slurm intermediate images

For example https://hub.docker.com/r/nlesc/xenon-slurm-abstract/ now has listing of xenon-slurm images these should be replaced with a link to https://hub.docker.com/r/nlesc/xenon-slurm/

Fixed in #21


Update link on community page

I updated the "porting examples" link so it points to the new repo instead of the archived version.

thanks!


0.4.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@4da4d82). Click here to learn what that means.
The diff coverage is 23.07%.

@@            Coverage Diff            @@
##             master      #13   +/-   ##
=========================================
  Coverage          ?   17.88%
=========================================
  Files             ?        5
  Lines             ?      246
  Branches          ?        0
=========================================
  Hits              ?       44
  Misses            ?      202
  Partials          ?        0

Impacted Files
Coverage Δ

subtitles/addic7ed.go
26.08% <0%> (ø)

subtitles/opensubtitles.go
25% <0%> (ø)

subtitles/subdb.go
10.52% <0%> (ø)

subtitles/subtitles.go
10.76% <16.66%> (ø)

subtitles/languages.go
30% <50%> (ø)

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 4da4d82...c338f8d. Read the comment docs.


[Angular-Apollo-Tailwind] Fix readme link in about section

Readme link in the About section should scroll to the README section.

Acceptance

When clicking on the Readme link in the About section it should scroll me to the README section

Nice to have

Display more information in the repo about section (stars, watchers, forks counters with links)

Let's skip the nice to have. Too much scope and makes this showcase inconsistent with others


Document TLS version and ciphersuite configuration for server and proxy

#1225 added support for specifying the TLS version and ciphersuite to use when configuring the proxy and broker. However, this is not documented in the respective configuration files, nor in the user documents. We should add such docs (and verify that they take effect).

This issue was fixed by #3057


ToSchema derives array with items with allOf combination of the types of all the tuple elements

Given e.g.
use utoipa::{OpenApi, ToSchema};

#[derive(ToSchema)]
struct A((Option<String>, String));

#[derive(OpenApi)]
#[openapi(components(schemas(A)))]
struct Api;

fn main() {
    println!("{}", Api::openapi().to_pretty_json().unwrap())
}

we get
{
  "openapi": "3.0.3",
  "info": {
    "title": "utoipa-test",
    "description": "",
    "license": {
      "name": ""
    },
    "version": "0.1.0"
  },
  "paths": {},
  "components": {
    "schemas": {
      "A": {
        "type": "array",
        "items": {
          "allOf": [
            {
              "type": "string",
              "nullable": true
            },
            {
              "type": "string"
            }
          ]
        }
      }
    }
  }
}

which seems to be the schema for a type that fulfills all the requirements at the same time instead of one where each element fulfills one of the requirements.
This happens for both enum and struct fields and it does not seem to matter if the field is named which leads me to conclude that the location of the tuple within the type we derive ToSchema on probably doesn't matter.

Tuples don't seem to be supported exactly in OpenAPI but it would probably be possible to at least use anyOf and minItems and maxItems to get as close as OpenAPI allows the validation to go.
Alternatively if someone uses a tuple and it is not supported by utoipa at all it should probably lead to a compile error.

According to how serde serializes tuples https://serde.rs/json.html see the struct X it will serialize to array of 2 fields. Thus the generated schema is also generated accordingly.

But this schema requires every element of the tuple to satisfy the types of all of them which obviously won't work.

@taladar Ah, true, instead it should serialize as anyOf.

anyOf wouldn't faithfully represent the tuple constraints. My suggestion above would.

True, the limitation should already be present on some tuples though. It should actually set that the array should contain 2 items. But it does not set prefix items though. But it might be that it does not take account all cases. Nonetheless while those min_items and max_items are provided they are only for visual validation and does not really prevent users of providing more or less items if the endpoint was executed e.g. with curl.
https://github.com/juhaku/utoipa/blob/576f6c129010b4f6e6445c06393cfcf2cfee30df/utoipa-gen/src/component/schema.rs#L607-L610

Technically speaking the entire schema does not prevent any client from sending any random data to the endpoint.

Yeah, it just shows "what a good guy should send"

@emersion That is true,
I'll change the tuple implementation out of the allOf thingly. That was a relic from past in the OpenAPI 3.0 which did not conform fully to JSON Schema spec. Since OpenAPI 3.1 it is fully conforming the JSON Schema we can use the prefixItems defined here: https://json-schema.org/understanding-json-schema/reference/array#tupleValidation. This allows full tuple support for OpenAPI as well as stated by @emersion.

Thank you so much!


Using a custom ec2 instance compute name

Hello,
I am using parallelcluster 3.0 and was wondering if there is a way for me to update the name of the compute ec2 instances in the AWS console.  Currently it seems to default to Compute but I would like to make it a bit more descriptive.  Is there a way to do this via tags?  I don't see a tags section for the slurm compute nodes so not sure if this is possible.
Thanks,
-Simran

Hello Simran,
Unfortunately, there is no way to configure the name of the compute nodes. Could you tell us more about why a more descriptive name is useful for you. Would you have a custom name for all compute nodes, or different names for different compute nodes? Knowing your requirement would help us discuss the feature request.
Thank you,
Hanwen

Thanks Hanwen for your response.  I was hoping to have a more descriptive name for the compute nodes since they currently just show up as "Compute".  It would be good to easily identify the compute nodes belonging to a specific pcluster instance in the scenario that we have multiple clusters in the same account.  Also, we have a tagging convention for all of our ec2 instances that would be good to apply for any ec2 instance that is spun up by pcluster.
Regards,
-Simran

parallelcluster-cluster-name: <cluster-name> tag is used to tag instances launched by ParallelCluster. You could filter the instances by the tag for instances belonging to a specific cluster
If you would include other tags on the instances, use the Tags section.
However, I believe you cannot use the name: tag to overwrite the name of compute nodes, because ParallelCluster always set the tag for compute nodes to Compute. With the currently implementation, to change the compute nodes name, you have to manually modify the launch templates created by ParallelCluster. If you would go down this path, I can give you more information.
Our team will discuss this feature request.
Thank you

This is related to: https://github.com/aws/aws-parallelcluster/issues/3238

The Name is a particular tag that can be easily modified by the user to identify a specific instance.
ParallelCluster sets parallelcluster:cluster-name (V3) and ClusterName (V2) tags to all the instances.
We documented existing tags in official documentation:

2.x https://docs.aws.amazon.com/parallelcluster/latest/ug/resources-tags.html
3.x https://docs.aws.amazon.com/parallelcluster/latest/ug/resources-tags-v3.html

The usage of these tags with the possibility to add a new column in the AWS Console to show the tag values should solve this issue.
Thanks for your inputs.


"Visual Studio has encountered an unexpected error" when enabling profiling in VS2019 .NET projects

The title says it all. It doesn't even check out the project from TFS before issuing the error:

I tried with 1.6.622.0 and a co-worker tried with 1.7.624.0. Same problem.
I tried checking out the project file before enabling the profiling. Same problem.
However, it properly enables a C++ project in VS2019.
Is there a workaround?

Hi Serge, the profiler is for native C++ applications only. The tagline on MarketPlace says this explicitely. It can also be enabled for native part of the code of C++ projects (manually).
A better warning is probably required...


NEXT-39412 - Use common PHPStan config from core and update PHP tooling

see https://gitlab.shopware.com/shopware/6/product/platform/-/merge_requests/15444

Codecov Report
Attention: Patch coverage is 63.63636% with 4 lines in your changes missing coverage. Please review.

Project coverage is 80.38%. Comparing base (495db11) to head (f0308e0).

Files with missing lines
Patch %
Lines

...c/Migration/Migration1605167857AddPackLanguage.php
0.00%
2 Missing :warning:

...tion/Migration1708692685AlterPackLanguageTable.php
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #33      +/-   ##
============================================
- Coverage     80.94%   80.38%   -0.57%
- Complexity      111      113       +2
============================================
  Files            19       19
  Lines           572      576       +4
============================================
  Hits            463      463
- Misses          109      113       +4

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


Stylebot reorders my rules on browser restart and wreaks havoc on my page

Upon browser restart, this saved CSS:
@import url(https://fonts.googleapis.com/css?family=Droid+Sans:400,700);
@import url(https://fonts.googleapis.com/css?family=Droid+Sans+Mono:400,700);

:not(.CodeMirror) { font-family: 'Droid Sans'; }
.CodeMirror * { font-family: 'Droid Sans Mono'; }

Gets reordered to this:
.CodeMirror * { font-family: 'Droid Sans Mono'; }
:not(.CodeMirror) { font-family: 'Droid Sans'; }

@import url(https://fonts.googleapis.com/css?family=Droid+Sans:400,700);
@import url(https://fonts.googleapis.com/css?family=Droid+Sans+Mono:400,700);

Needless to say, my page then looks very different.

Resurrecting because this is still an issue. Hopefully with the extension getting new attention this can get fixed

closing as duplicate of #452. will be fixed in upcoming release


Oracle compliant ALTER TABLE ADD/MODIFY deparser

Fixes #1157.

Coverage remained the same at 88.501% when pulling 5fe10c7a37c54367ce58cd046919b2d62a0e80f5 on manticore-projects:master into 5ee6ec9dd7a66bff7460e0b6350d068db1d0a092 on JSQLParser:master.

So should I merge this, or is this still not final?

Please merge, all my PRs are final.
The only confusion comes from merging them upside down, newest first and oldest last :-D
(Also GIT seems to branch differently compared to Mercurial, I need to figure this out.)


Backport status and spec handling in enforced policy

Backport of issue to release 2.5
Refs:

https://github.com/stolostron/backlog/issues/21908

Signed-off-by: Gus Parvin<EMAIL_ADDRESS>

/retest


Version 3.6.2 - If the certificate string already has a prefix, there is no need to add it

Changes:

Added fix for Readdle\AppStoreServerAPI\Util::formatPEM() method. If the certificate string already has a prefix, there is no need to add it;
Minor version update: v3.6.1 -> v3.6.2 .

Totally makes sense, looks fine.
I guess something like this check was lost while refactoring to the new major version.
Thanks!


Template app pages

The commits in this pull request will organize the application pages into templates.
Changes provided in these commits include:

Move HTML to templates directory
Organize HTML into templates

Use layout.html for common header and footer
Update CDN links for latest versions of Bootstrap and DataTables
Use new API key from new gwgnewengland Google Cloud account

Update CSS for map and templates

Set main height in CSS to nest map within <main> (issue #12)
Update CSS for new page layout.

This pull request addresses issues #12 and #37 .
The JavaScript will require refactoring to work with the new back-end API and page templates. I commented out most of the JavaScript files for now, and I will update the JavaScript from a separate branch.

Thank you so much for these changes. A templates directory, along with actual templates, was much needed.
At first glance, the following two issues were found:

Wrong function in template layout.html:
url_for('universities') wouldn't work because the view function name in app.py is colleges.
You should either change the function name in app.py or call url_for('colleges').
This should have caused an Internal Server Error when the application is called. But I think, because of the server from previous runs/tests, you got a cached index page when you fired up the application. I recommend clearing the app's storage from your browser to make sure that you're not getting cached pages in return. You could also set the cache name in the javascript file to dynamically change every time you run the app. This will make sure that all previous caches are deleted (I think).

static/js/index.js is omitted (commented out):
This script is what installs and updates the service worker, so it needs to be added to the layout.html template. Most of the other javascript files can be omitted though.

I'll try and do a much more thorough check later today, once we've put our couch and bed back together. Talk to you soon!

Thanks @AbdouSeck . Sorry I forgot to include my changes to app.py in the last set of commits. This commit fixes the issue with the universities page. I also restored the Service Worker, and renamed the index.js file to sw-install.js, so it's easier to keep track of what it does.

@br3ndonland, thanks for the changes. I'm happy to merge these changes but I wanted to make sure that I mentioned that once these changes make it to the dev branch, the app will no longer be static, and therefore will be impossible to host using GitHub Pages. The good thing about this is that GitHub Pages is still linked to the master branch, which has not yet received any of these changes. So, we'll still to be able to point people to the app until we decide to move changes from dev to master.
If we still are thinking about letting GitHub Pages host the site while the APIs are hosted elsewhere, we may have to do the templating a bit differently: basically still generate the static pages through templating, but nothing more. This means that we use view functions to generate the index.html and universities.html pages and then add, commit and push those HTML pages to GitHub.
If this is not clear, I am happy to discuss it further on Slack later this afternoon (preferably after 3 PM). Otherwise, we can meet next Saturday or Sunday to discuss this and the PDF file you shared with us on Slack. I'd really love to work on implementing those challenges!
Abdou

Also, the following static files are being cached in the server worker, but since most of them won't be needed anymore and some of them have their names changed, I recommend we stop caching them?
https://api-v3.mbta.com/stops
static/js/index.js
static/js/dbCaching.js
static/js/localforage.min.js
static/js/utilities.js

@br3ndonland, let me know what you think. If you would like to remove them from being cached, feel free to modify the server worker file (sw.js, I believe). The staticScripts variable should be edited as follows:
var staticScripts = [
  "https://code.jquery.com/jquery-3.2.1.slim.min.js",
  "https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js",
  "https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js",
  "https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css",
  "https://cdn.datatables.net/1.10.16/css/jquery.dataTables.min.css",
  "https://cdn.datatables.net/1.10.16/js/jquery.dataTables.min.js",
  "https://cdn.datatables.net/responsive/2.2.1/css/responsive.dataTables.min.css",
  "https://cdn.datatables.net/responsive/2.2.1/js/dataTables.responsive.min.js",
  "data/cleaner_universities.json",
  "index.html",
  "static/js/sw-install.js",
];

This should actually reduce the storage footprint of the app.
Abdou

Thanks for your comments @AbdouSeck.

JavaScript

I pushed your recommended changes to the Service Worker. The commit updates the list of cached files, and also updates the API key for our new Google account.
I will continue to refactor and update the Service Worker and other JavaScript files. For example, the map JavaScript will need to be updated to generate markers from our API instead of the data fetched directly from the MBTA API. I will do this from a separate branch.

GitHub Pages

GitHub Pages builds from the master or gh-pages branches. We can safely make changes on the dev branch, but once we merge to master, the static site would no longer work.
To protect the static site in case we push to master, I created a gh-pages branch off of master, and switched the GitHub Pages build to the gh-pages branch. We can maintain the static site there.

Flask, deployment and hosting

You're correct that we won't be able to host the Flask app as a static site anymore. I think we should deploy with full Flask functionality, rather than generating static pages offline.
I'm happy to take on the deployment. I think it should be the last thing we do, after we have a functioning app with all the planned features.
If we deploy onto Google Cloud Kubernetes Engine, I think we can just point our mbtaccess.org domain name there.
If we need another option, I would suggest Netlify. It's mostly used for static sites, but they do have some instructions for Python, and people rave about the great user experience. We can configure Netlify to build from our GitHub repo, and point our mbtaccess.org domain name there.
If Netlify doesn't work, we can manually configure an Apache or Nginx server and clone the app repo onto the server. I have done this before on DigitalOcean.

This week, I'm hoping to refactor all the JavaScript, and get a single Docker container running for the application. A meeting next weekend would be great.

Oh never mind. I was able to add the localhost server URL's and everything seems fine now. I get the following warning from Chrome:
Resource interpreted as Stylesheet but transferred with MIME type application/javascript: "https://cdn.datatables.net/1.10.19/js/jquery.dataTables.min.js".

I am not particularly sure what it's talking about here, but it seems to affect the /universities endpoint fairly severely.
The following is what the universities table now looks like:

Any idea why this is happening?
I also failed to mention that the layout.html page contains the script tag that's importing the Maps API when this is only needed for the index page. Maybe the Maps API code should only be in the index.html template. In fact, if you look at your console when you're on the universities page, it shows a fair bit of Javascript errors below the dataTable.js warning. Could you also please take a look at those errors?

Thanks for your patience on these issues @AbdouSeck, and for checking out the code so thoroughly. Your comments have cleaned up my commits and really improved the app. Going forward, I would suggest we keep this PR focused on templating and deal with the DataTables quirks, and any additional JavaScript changes, in a separate PR.

Templates

I substantially improved the templating today.
I previously had most of the HTML in layout.html, with only the {% block content %} in the middle being different for each page.
I revised layout.html to be a concise master layout for the pages, and added more templates for other parts of the page.
Templating scripts:

I agree that we should only load scripts when they are needed on the page. We should load the maps JavaScript only on the map page, and the universities JavaScript only on the universities page.
To accomplish this, I divided the script tags into those common to all pages, and those unique to a specific page.
The common scripts are stored in scripts.html and loaded with each template using {% include 'scripts.html' %} in layout.html.
The scripts unique to each page are stored in the HTML for the page (index.html or universities.html) inside {% block script %}. The script block is then called in layout.html.

DataTables

The DataTables have started running over the footer on both pages. It started after I set a height for main in the CSS.

I thought it might be ignoring the Flask-templated footer, but I have gotten the same error on the static site without templating.

Upon inspection by dev tools, DataTables seems to be applying a no-footer class.

I applied some CSS to the universities DataTable in a prior commit so it fits above the footer until we figure out the issue. This is why it looks smaller right now.

Hi @br3ndonland,
I think I found what your issue with DataTables is:
 <link rel="stylesheet" href="https://cdn.datatables.net/1.10.19/js/jquery.dataTables.min.js">

This link is inside universities.html, but a link tag should receive a CSS file or something else. Not a javascript file. Maybe changing the href attribute to the actual CSS file would fix the table issues.
Also, you remove the index.html endpoint from app.py, but are still trying to cache index.html inside the sw.js file. This causes an error. You can remove the "index.html" element from the staticScripts variable inside sw.js to avoid this error. Or, you could change the value from "index.html" or "index".
It never hurts to have endpoints that end with .html since it's just a page being served. However, if they cause confusions, then I am definitely for removing them.
Finally, I recommend emptying the browser cache every time you test a page. Sometimes cached pages can make it seem like there are no errors or warnings.
I am heading home, but I'll be adding unit tests for both app.py and utilities.py within the next hour or so. I will make sure I don't touch any files you've already been working on.
Finally, sorry about this long back-and-forth. I am just trying to avoid merging a pull request that may introduce console errors/warnings. Not trying to be too anal.

@br3ndonland I just noticed that you changed the versions for DataTable.js. Now, it looks like the templating branch is using version 1.10.19 while all the other branches are on version 1.10.16. Is it possible for that to be part of the reason that table layouts have changed?

@br3ndonland thanks for the changes. But most of all, thanks for indulging my annoyances. I am going to submit a pull request with unit tests and travis CI hooks. The latter should trigger test runs every time we push commits to GitHub.

Great, thanks @AbdouSeck! I do appreciate your comments in this thread, and I think testing with CI is a great idea.


Issue with rclc_support_init() on STM32H743ZI using FreeRTOS 10.3.1

Hello,
I'm encountering a similar issue as described in tickets #116 and #107 while working with an STM32H743ZI2. Specifically, the problem lies with the rclc_support_init() function, which does not appear to be functioning correctly. I've configured the settings in line with those mentioned in ticket #116.
The issue manifests as follows: after calling the rclc_support_init() function, the MCU exits the Task function but fails to return. When halting the debugger at various points, I've observed that the FreeRTOS functions vTaskSwitchContext() and vPortExitCritical() are being invoked.
It's worth noting that on another STM32 MCU using an older version of FreeRTOS (10.2.1), there were no issues. However, the STM32H743ZI2 MCU comes with FreeRTOS 10.3.1 as the default from MXCube. Since I managed to get micro-ROS working on a similar MCU I am quite certain I followed the right steps. I however suspect something changed in versions or there is some hardware incompatibility. It is mentioned that micro-ROS is compatible with the STM32H743ZI, so I am curious which versions/setup is used to make this work.
This problem appears to be a recurring issue that has been reported multiple times. The most recent suggested solution (#116) involves modifying the allocator functions, but this solution lacks clarity and hasn't resolved the problem for me.
I have attempted to use custom functionsi instead of the microros_xx functions by using the standard C malloc, free, realloc and calloc without improvement.
Also the FreeRTOS pvPortMalloc and vPortFree functions were attempted, but does not solve the problem.
When running the micro-ROS agent no sign of connection can be seen and no session is established, as is the case with my other MCU. The USB is connected since /dev/ttyACM0 is detected.
It's also worth noting that ticket #107 does not contain any suggestions on how to address this problem.
I would greatly appreciate any assistance or suggestions that could help me address this issue conclusively. Thank you in advance for your help.

hello ， I'm having the same problem as you. It seems that the connect with agent is not well established yet. You can try a few more times on rclc_support_init(). That's what I did.
//broke unitl success
   do{
        ret =  rclc_support_init(&support, 0, NULL, &allocator);
        osDelay(1000);
    } while (ret != RCL_RET_OK);

Hello there @danielallstar  encountering the exact same problem with the exact same MCU. Wondering if you fixed it.
Thanks

Hey, I did not solve that problem. You could try the solution of @Hao-Lion-ZJU, but I did not try that myself.

Thanks! Yeah, did try it, does not work and could never stop the problem because the default task never resumes once it has entered rclc_support_init.
Also, tried using default allocators as suggested in  but does not fix the problem. Seems that micro-ros support for the stm32h743 is essentially broken. I wished we didn't design a custom PCB thinking it would work...

Wondering if the maintainer @pablogs9 can help. I'd love to help but not sure in which direction to go there. I'd also be really happy to pay for a bug bounty or some support if it can unlock the issue for everyone

Hello @nikitax75 could you open a PR for fixing the issue you mentioned?


[BUG][INVESTIGATE] "Open failed: EACCES (Premission denied)" error when attaching files

Your Rocket.Chat.Android version: 2.0.3
Mobile device model: Xiaomi Redmi 3
OS version: MIUI 9 (8.4.19) , Developer ROM
When I try to attach a file (any format), I get an error "open failed: EACCES (Premission denied)". In version 2.0.2 after #1047 everything worked fine. But in 2.0.3 it's broke again.

@Pitstopper Is this still happening for you?

Problem solved, thanks!


prettyping: init at 1.0.1

Motivation for this change
Another great script (recently cameo'd in CLI: Improved, Remy Sharp).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions: Ubuntu 17.01

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Heads-up, this will conflict with #46111 since both update maintainers.nix at the same place.

prettyping was already added in #46008.

oops!


Back Button in Team Exercises not working

Describe the bug

To Reproduce

Go to any Team Exercise
Click on the Exercise
Try to navigate to the previous site by using the back button

Screenshots

I was not able to reproduce this, neither from the Tutor Dashboard nor from the Course Management Exercise List. The button always works for me (using a Chromium-based Browser on Win 10).
Could you please provide a more detailed sequence of steps to reproduce and provide details about your system/environment? Are there other conditions that are required for the bug to appear?

I'm also not able to reproduce this, hence closing.
I'm able to assess team exercises and navigate back using the back button.


WIP Fix: no addon install when managed cluster is deleting

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>

/assign @zhiweiyin318
e2e failed because image quay.io/bitnami/golang1.17 is unavailable now.

Working on integrate test.

need to at least add an integration test.

integration test added.PTAL


Form Validation

Describe the bug
The details entered by the user during filling out the information form are not being validated which can lead to insertion errors in the database.
To Reproduce
Steps to reproduce the behavior:

Validate the form in frontend

Expected behavior
The user entered data specified by the type. Ex: entering only 10 digits in phone number or not allowing digits in name.

This issue is handled in #18 pull requests.


change Update() to Patch() request for function update

I update this to use Patch() http request with type:
StrategicMergePatchType PatchType = "application/strategic-merge-patch+json"

cc/ @anguslees @sebgoa

I tested this with http-based func and it worked. Will ask Andres for testing it more

Thanks @anguslees 👍
@andresmgot also confirmed this PR work on his test(s). So I am happy to merge this.


(2.2.13) Changing crop in a growing zone causes pawns to randomly stop sowing

Changing the crop you are trying to grow in a growing zone will cause the pawns to start sowing in "bursts", where they will sow a few plants, then stop for a few seconds, then sow a few plants again, and repeat. Error messages about WildPlantSpawner occasionally appear.
Steps to reproduce the behavior (VERY IMPORTANT)

Create new save
Create a growing zone
Wait for colonists to finish sowing zone
Change the crop to some other plant
See if pawns randomly go idle or stop sowing, if they don't you might have to try changing the crop again a few times.

Error Log
https://gist.github.com/a48769a27e74d7ea3e116d2d50189abf
Mod list (For vanilla report, it has to be same as below list.)

Harmony
Core
Royalty (optional)
HugsLib
RimThreaded

fixed in 2.2.14

Still happens in 2.2.19. Create a new save file, create a growing zone and set to rice. Wait for pawns to finish sowing, then change it to corn, wait to finish sowing, change to rice, etc. Eventually you will see the pawns go idle and they won't sow.

fixed in 2.3.5


Calculate Coordinate in dependence of initial position

Duplicate to issue #24 .
No worries - Just for Documentation.
You can work with this issue, just remember to close the other issue when you're done :)


Do not filter out existing compactions in TestHiveTransactionalTable

Temporary workaround to  hopefully fix https://github.com/prestosql/presto/issues/4089

We need a code comment for this.
Did you try repro this locally?
Maybe we should be setting NO_AUTO_COMPACTION tblproperties ?
https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-TableProperties

We need a code comment for this.

I will let the CI run. If we decide to merge it I will add comment before merging.

Did you try repro this locally?

NO that is a blind shot.

Maybe we should be setting NO_AUTO_COMPACTION tblproperties ?
https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-TableProperties

That is a good idea. Unless we have auto compaction disabled globally in our images. I asked that question to @wendigo and he is checking what is the state.

Unless we have auto compaction disabled globally in our images

I do not think we have.... OTOH i was sure i used NO_AUTO_COMPACTION somewhere, but can't find it... So worth double checking.

@losipiuk @findepi hive.compactor.initiator.on is on on HDP3.1 but it's not set on HDP2.6 (so I guess off by default)

I'm in favour of disabling auto compactions on out test tables and leave HDP configuration as-is.

hive.compactor.initiator.on is on on HDP3.1 but it's not set on HDP2.6

@wendigo transactional tables are not supported with HDP2.6, this test is not run against that env

@findepi makes sense

https://github.com/prestosql/presto/pull/4093 is less agressive and seem to fix the issue https://github.com/prestosql/presto/pull/4093


Update README.md

First change made here...trying

Always try to get another programmer to review your pull requests.


Amplify GraphQL API Schema is failing to compile due to "TypeError: rules.filter is not a function"

Describe the bug
I've got a large, complex schema that I've slowly been iterating on. I'm getting this error when attempting to compile the schema with amplify api gql-compile.:
TypeError: rules.filter is not a function

There are no details provided i.e a line number that it tripped upon. Without this, I'm left sifting through a 700 line schema.graphql file. I've found no other issues raised about this either. It would be good to provide some more details as to what line in the schema is responsible...
Amplify CLI Version
4.44.2
To Reproduce
I'm not releasing this schema currently but if I find the cause of this issue I'll update.
Expected behavior
GraphQL schema to compile or at least have an understanding as to what line caused the issue.

OK, so for anyone running into this issue, it appears that I was missing the [] bracks that encapsulate the array of auth rules 🤦♂
	visibleTo: [String]
		@auth(rules: { allow: private, operations: [create, read, update, delete], provider: iam })

was fixed by updating to:
	visibleTo: [String]
		@auth(rules: [{ allow: private, operations: [create, read, update, delete], provider: iam }])

I still think it should be updated to specify the line number that caused the TypeError.

Hi @kylekirkby we can definitely improve the error messaging around this failure!

My understanding is that the underlying problem is related to https://github.com/graphql/graphql-js/issues/2222 (originally opened by @attilah). If GraphQL expects an array of a specific type, it will accept a scalar of that same type, with the assumption that someone else will coerce it to an array with one element.
I think we have this same problem for any directive that accepts an array, and it is not specific to @auth. I was able to reproduce the problem locally with the @key directive:
@key(fields: [5])    not allowed
@key(fields: 5)      not allowed
@key(fields: "wut")  allowed


Memory leak: 2 calls to new without a delete

There seem two calls to new Pubkey() without delete at those locations in jwks.cc:
https://github.com/google/jwt_verify_lib/blob/40e2cc938f4bcd059a97dc6c73f59ecfa5a71bac/src/jwks.cc#L396
https://github.com/google/jwt_verify_lib/blob/40e2cc938f4bcd059a97dc6c73f59ecfa5a71bac/src/jwks.cc#L456

CC @alexcope @qiwzhang

PubkeyPtr is std::unique_ptr.

Indeed. But in that case it should better be make_unique instead.

We could, but I believe it is only available in certain gcc compiler.  I am not sure if we have compiler version requirement.

I think most compilers supporting C++11 and all supporting C++14.