错误：za or zA Error

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.8.3
Operating system/version
macOS 13.2.1
Describe the bug
When I enter the za or zA command, I always prompt that I can't find the fold.
And I can't find the file that defines the shortcut key starting with z.
Steps To Reproduce
Go to the name location of the function definition and enter the shortcut key za
Expected Behavior
Realize code folding
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

I solved it.Please close

Can you tell me which file za and zA are defined?

za and zA are internal Neovim keymaps. LazyVim does not change or define those.


ios-11.4\10.2    document.createElement is not a function

Make sure to check the existing issues in this repository
If there is no issue for your problem, tell us about it
Please, ensure your title is less than 63 characters long and starts with a capital
letter.
Which platform(s) does your issue occur on?

iOS
iOS 11.4\10.2
emulator or device. What type of device?

Please, provide the following version numbers that your issue occurs with:

CLI: 4.1.2
Cross-platform modules:

"tns-core-modules": "4.0.1",

Runtime(s):

  "tns-ios": {
      "version": "4.0.1"
    },
    "tns-android": {
      "version": "4.0.1"
    }

Plugin(s):

 "dependencies": {
    "@angular/animations": "~5.2.0",
    "@angular/common": "~5.2.0",
    "@angular/compiler": "~5.2.0",
    "@angular/core": "~5.2.0",
    "@angular/forms": "~5.2.0",
    "@angular/http": "~5.2.0",
    "@angular/platform-browser": "~5.2.0",
    "@angular/platform-browser-dynamic": "~5.2.0",
    "@angular/router": "~5.2.0",
    "apollo-angular": "^1.0.1",
    "apollo-angular-link-http": "^1.0.1",
    "apollo-cache-inmemory": "^1.2.2",
    "apollo-client": "^2.3.2",
    "apollo-link": "^1.2.2",
    "apollo-link-error": "^1.0.9",
    "graphql": "^0.13.2",
    "graphql-tag": "^2.9.2",
    "moment": "^2.22.1",
    "nativescript-angular": "~5.3.0",
    "nativescript-audio-player": "^1.0.3",
    "nativescript-globalevents": "^1.2.1",
    "nativescript-localstorage": "^1.1.5",
    "nativescript-ngx-fonticon": "^4.1.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-ui-calendar": "^3.6.0",
    "reflect-metadata": "~0.1.10",
    "rxjs": "~5.5.5",
    "tns-core-modules": "4.0.1",
    "zone.js": "~0.8.18"
  },

Please, tell us how to recreate the issue in as much detail as possible.
Project launch Flash back, error.
Is there any code involved?
import { Component, OnInit } from "@angular/core";
import { Observable } from "rxjs/Observable";
@Component({
    selector: "koransearch",
    moduleId: module.id,
    templateUrl: "./koransearch.component.html",
    styleUrls: ["./koransearch.component.css"]
})
export class KoransearchComponent implements OnInit {
    sbHint = "Please enter the search content or chapter number";

    constructor() {
        // Use the constructor to inject services.
    }

    ngOnInit(): void {
        // Use the "ngOnInit" handler to initialize data for the view.
    }
    onClear() {
        this.sbHint = "";
    }
}

/shared/graphql.module
import { HttpClientModule, HttpHeaders } from "@angular/common/http";
import { NgModule } from "@angular/core";
import { Apollo, ApolloModule } from "apollo-angular";
import { HttpLink, HttpLinkModule } from "apollo-angular-link-http";
import { InMemoryCache } from "apollo-cache-inmemory";
import { ApolloLink, from } from "apollo-link";
import { onError } from "apollo-link-error";
const uri = "http://<IP_ADDRESS>:5000/graphql";

@NgModule({
    exports: [
        HttpClientModule,
        ApolloModule,
        HttpLinkModule
    ]
})
export class GraphQLModule {

    constructor(
        private apollo: Apollo,
        private httpLink: HttpLink
    ) {
        this.initWare();
    }

    initWare() {
        const http = this.httpLink.create({ uri });

        const authMiddleware = new ApolloLink((operation, forward) => {
            return forward(operation);
        });

        const errorLink = onError(({ graphQLErrors, networkError, response }) => {
            if (graphQLErrors) {
                console.log("graphQLErrors===", graphQLErrors);
            }

            if (networkError) {
                console.log("networkError===", networkError);
            }

        });

        this.createApollo([authMiddleware, errorLink, http]);
    }

    createApollo(params) {
        this.apollo.create({
            link: from([...params]),
            cache: new InMemoryCache(),
            defaultOptions: {
                watchQuery: {
                    fetchPolicy: "network-only",
                    errorPolicy: "all"
                }
            }
        });
    }
}

app.module.ts
import { GraphQLModule } from "./shared/graphql.module";

@NgModule({
    bootstrap: [
        AppComponent
    ],
    imports: [
        AppRoutingModule,
        GraphQLModule,
    ],
    declarations: [
        AppComponent
    ],
    schemas: [
        NO_ERRORS_SCHEMA
    ]
})
export class AppModule { }

@cnqiuxue please try to update to the latest version of nativescript-angular and also update all related dependencies.
rm -rf node_modules platforms
npm i tns-core-modules@latest --save
npm i nativescript-angular@latest --save
./node_modules/.bin/update-app-ng-deps
npm i
tns platform add android@latest
tns run android

As a side note, I am not sure if some of your dependencies are not browser related (e.g. apollo-angular ). Any plugin that is using a DOM-related code (e.g. the document object) is not compatible with the mobile environment in NativeScript and should be ported


[SR-1639][SourceKit] Link SwiftLang libraries to sourcekitd

What's in this pull request?

When building SourceKit on Linux, sourcekitdAPI would not be linked to SourceKitSwiftLang, which caused the following symbols to be undefined:

SourceKit::LangSupport::SynthesizedUSRSeparator
SourceKit::LangSupport::createSwiftLangSupport(SourceKit::Context&)

Link SourceKitSwiftLang to resolve these symbols.
Resolved Related bug number: (SR-1639)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci please test

These changes are still relevant. Looks like @briancroom is cool with this change, so I'll go ahead and merge if the tests pass. If any other committers have thoughts, let me know!
The test run was so long ago, Jenkins must have cleaned up the job page -- it's a 404 now. Re-running to see how things currently stand:
@swift-ci please test

The swift-package-manager failure in JSONTests.testDecoding is obviously unrelated. Merging!


compatibility issues with github

i gave the docker image a try this afternoon, and it produced a results.mp4 file. i uploaded the file to github but the file will not play in firefox, and i've been getting mixed results with chromium based browsers.
github issues seems to only support 10MB attachments but larger mp4 files can be uploaded to gist and linked using <video tags.
https://gist.github.com/ipatch/97c8d10beb66c388082680372a3bb854#gistcomment-4038228
right clicking on the video gives the below raw video URL,
https://user-images.githubusercontent.com/613805/150659922-55274a55-9591-4a0d-8431-631a5135912a.mp4

@ipatch
Yes, there will be problems with image quality. and consumes a lot of memory resources.
So it is recommended to use js to play text and simulate video effects (by google translate)

是的，对于大于一分钟的视频，效果不是很好，并且消耗的内存很大( ffmpeg  部分)，所以，推荐使用 asciinema js 来达到模拟播放视频的目的。

it is more of a the final mp4 file generated by the docker container ie. the results.mp4 does not play with the firefox web browser. i don't think the docker container produces valid mp4 files. or is missing some settings that would allow a web browser such as firefox to play the mp4 file. 🤷♂
i ended up reencoding the mp4 file in shotcut then it was able to play in firefox.

@ipatch  Yes, I also think it's a problem with firefox not supporting
maybe , try this https://stackoverflow.com/questions/40760864/how-to-play-mp4-video-in-firefox .(or ignore)


Move to Reach-UI and add tooltips

Move the custom dropdown/menu to Reach. Also replace react-modal, react-select and popper with Reach. Having components from one source should help with maintenance as upgrades will be simpler to do. It should also help with bundle sizes.

Codecov Report

Merging #4 (abefe46) into master (bdeb5e2) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage     86.69%   86.69%
  Complexity      253      253
=========================================
  Files            26       26
  Lines          1022     1022
=========================================
  Hits            886      886
  Misses          136      136

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 bdeb5e2...abefe46. Read the comment docs.

Total bundle size:

Before 8.12MB
After 7.83MB


[CMake] Export libllbuild target

This will allow other projects to easily link against libllbuild.

@swift-ci smoke test

/cc @compnerd


Concrete definition of all protocol message types

This ended up being a very large change set. There was no good way to do this incrementally, so I decided to just write it all.
It doesn't make sense to review this via diffs, instead the final code at the top commit should reviewed like reading new code.
Here's a summary of the refactor

All protocol level structs like Event, Tag, ReqFilter etc are defined with concrete types. They can serialize and deserialize themselves into protocol json format.
The recommended way to deserialize an Event is via Event::from_str(). The custom definition of from_str() for event ensures that received event data is valid by format, datatype and signature. This ensure we never deal with invalid event data in other parts of the code.
Map structures used in Event and ReqFilter is removed, as they are not needed when we already know how to handle these data efficiently.
Commands and Responses are defined with their own struct (serialization defined). There are three types of commands Close, Event, Subscription. And 2 responses EventResp and NoticeResp. Easy constructors added for them.
All the message structs are moved into one dedicated module messages to keep this part of the code self contained. It can be thought that the entire nostr protocol lives in messages. Any future update to protocol will only require update there.
Basic testing added for all the types.
Minor fixes in error module to use this_error more efficiently.
Auxiliary changes to other part of the code for above refactors.

I hope this is a helpful change. I am already seeing many simplification possible in other parts of the code (main, db etc). The idea is again the old concept of "separation of concerns". The server or database should not have to worry about protocol adherence of the stuffs they are handling. If they get something without panic, that's correct data. And everything "protocol" is contained inside message module.
I tried to cover all the basic testing. More test suggestions are welcome.

First practical problem; event kinds other than 0,1,2 are not accepted.  I think the relay should accept any kind, even those it isn't aware of.  This should be an easier fix (adding a "OtherKind" as a catchall for the EventKind enum).

Second problem; the event/pubkey tags need to be more flexible.  When used in Kind=3 events (contact list), they can hold 4 values (tagname, pubkey, relay, nickname).
Future kinds could redefine these to do other things.  I really think we need to be able to handle arbitrary future events that meet the structure in NIP-01 (which doesn't prevent e/p tags from having an arbitrary number of elements).

I think I'm OK with the relay rejecting events that are clearly out-of-spec (say, kind=3 with a "p" tag whose 2nd element is not a 64-byte hex string).  However, I think we need to ensure that unknown/future event kinds are parseable without having to explicitly add support for them.
I think pretty much everything else in the patch looks great.

Thanks for the look.
Yes I agree with all of this. We should handle unknown flags gracefully, than just saying "nah, we don't understand it". Although that should also be properly defined in the specs too.

First practical problem; event kinds other than 0,1,2 are not accepted. I think the relay should accept any kind, even those it isn't aware of. This should be an easier fix (adding a "OtherKind" as a catchall for the EventKind enum).

What do you mean by any kind? Is it any other kind defined in NIPs? or any random kind that it doesn't know how to read? I don't think its a good idea to allow existence of "random kinds" without their own NIP. Nostr doesn't have DOS protection and at this stage things should be defined strictly via NIPs. Then we can selectively open up to these NIPs and have our compatibility matrix. That way we can ensure that we don't end up with garbage in our DB while being open to the full set of protocol.
Currently this only supports NIP01. And the next work is to make it compatible with rest of the NIPs.

No plans to merge this one.


Move pledge status table to aid package page

Purpose

The purpose of this PR is to fix #368
Screenshots

TODO:

[ ] Allow updating the status from the donor table status column which is now on the aidpackage page


gk-deploy: Fix missing change to labels in OCP templates

Signed-off-by: Jose A. Rivera<EMAIL_ADDRESS>

This change is

LGTM


Handle account management from web panel

There is currently no way to create a user beyond manual insertion of a hash. We should allow password reset for users who have been manually inserted.
Additionally, we should most likely investigate permission levels on creation.

If that includes Shop accounts as well, I could do it.

These aren't related to shop accounts, and are only related to the panel - thank you though!

Finished as of https://github.com/WiiLink24/room-server/commit/26c27f878540dcfcbec49c6d61949f64c57a4ed0.


Y2K-1544 Fix image on top of team creation wizard

This only addresses the first part of the ticket - once you've selected a picture, it should be that picture.

@jakob223 i'm not sure rest of the wizard is hooked up the to the current flow yet to do this?

I'll wait until Y2K-1543 is in

You could base on jakob/Y2K-1543/integrate-new-team-wizard which has that


Fixes Bug#791 : Chat list scrolls down when a new message arrives in a channel

The bug was that when a new message pops up in the channel the list scrolls down. To fix this the line
        recycler_view.scrollToPosition(0)

was commented. However, further modifications will be needed, like a toast, to notify the user of the new message. Would love to work on the same if deemed necessary by the community.
Closes #791,
Thanks in advance!

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

CircleCI tests show :
Your build has exceeded the memory limit of 4G on 1 container. The results of this build are likely invalid. We have taken a snapshot of the memory usage at the time, which you can find in a build artifact named `memory-usage.txt`. The RSS column in this file shows the amount of memory used by each process, measured in kilobytes.

How should I proceed?
Thanks in advance!

@harisankerPradeep Could you please resolve the conflicts?

@harisankerPradeep I'm sorry the delay again... can you fix the conflicts now? I do plan to merge this PR now.

Closing this PR because it has some conflicts unsolved and this was already fixed in the current version.
Thank you.


[#439] Fix README file

Description:
Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context. List any dependencies
that are required for this change.
Fixes #439
Type of change
Please tick the appropriate option using [x]

[x] Bug fix
[ ] New feature

Checklist:
Please tick the appropriate options using [x]

[ ] My PR includes tests that cover my code changes.
[ ] Lint and formatter run with no errors
[ ] All new and old tests are passing

Hi @Dainerx,
Before we can merge your PR, can you review and sign Murex CLA as explained here?
Thanks!

Ok, let's close this PR and related issue.
@Dainerx my previous comment about reviewing and signing Murex CLA is still valid if you're still planning to contribute to other TCR issues 😃

issue #439 is not relevant

My bad. I had read the diff without color highlighting! We should indeed be merging this PR!

So are we opening this PR?


[Consent to Share Developer Resources] spectral

@davemlz Thanks for suggesting Awesome Spectral Indices be included in Earth Engine's Developer Resources page.
Please:

edit the provided suggestions for how to present your resource
add your name and date to confirm your consent to display your resource
let us know your plans for maintenance and development of your resource

"title": "Awesome Spectral Indices",
"desc": "A standardized ready-to-use curated list of spectral indices that can be used as expressions for computing spectral indices in GEE.",
"url": "https://github.com/awesome-spectral-indices/spectral",
"contactGitHub": "davemlz"
"contactName": "YOUR NAME",
"contactConsent": "YYYY-MM-DD",
"maintenance": "yes" OR "no" OR "maybe",
"development": "yes" OR "no" OR "maybe",

To request changes in the future, ping this issue. Thank you for supporting the Earth Engine developer community!

Thanks a lot, Justin! Here is the requested info. The module is fully operational, maintained, and I will keep adding features in the future! :)
"title": "spectral",
"desc": "A module for accessing and computing spectral indices from Awesome Spectral Indices inside the Code Editor",
"url": "https://github.com/awesome-spectral-indices/spectral",
"contactGitHub": "davemlz",
"contactName": "David Montero Loaiza",
"contactConsent": "2022-09-16",
"maintenance": "yes",
"development": "yes",

Thank you very much, Justin!

It's live! 🚀
https://developers.google.com/earth-engine/tutorials/community/developer-resources
Ping this thread if you want to make changes to the entry in the future.

That was super fast!
Thank you, Justin! :rocket:


Default galaxy installation fails

% ansible-galaxy install twinsnes.pihole
- downloading role 'pihole', owned by twinsnes
[WARNING]: - twinsnes.pihole was NOT installed successfully: Unable to compare role versions (v0.0.2, 0.0.1, v1.0.0) to determine the most recent version due to incompatible version formats. Please contact the role author to resolve versioning conflicts, or specify an explicit role version to install.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.

Successful installation done with
ansible-galaxy install twinsnes.pihole,v1.0.0

Same for me!
I think removing/renaming the release tag 0.0.1 which does not fit the versioning scheme used otherwise may solve this issue.

Hi,
After little bit cleaning  and try to reinstall this role I have same issue. Is it still supported ?
Thanks
`(ansible-env):$ ansible-galaxy install -r requirements.yml
Starting galaxy role install process

downloading role 'pihole', owned by twinsnes
[WARNING]: - twinsnes.pihole was NOT installed successfully: - the specified version (1.0.0) of twinsnes.pihole was not found in the list of available versions ([{'id': 112095, 'url': '', 'related': {},
'summary_fields': {}, 'created': '2019-12-24T08:32:14.093303Z', 'modified': '2019-12-24T08:32:14.093332Z', 'name': '0.0.1', 'version': '0.0.1', 'commit_date': '2019-12-24T03:26:24-05:00', 'commit_sha':
'ddf60f063350631a01c0b8f86acfed4b8db47275', 'download_url': 'https://github.com/TWinsnes/galaxy-role-pihole/archive/0.0.1.tar.gz', 'active': None}, {'id': 112152, 'url': '', 'related': {},
'summary_fields': {}, 'created': '2019-12-27T04:00:19.101673Z', 'modified': '2019-12-27T04:00:19.101701Z', 'name': 'v0.0.2', 'version': '0.0.2', 'commit_date': '2019-12-26T22:58:54-05:00', 'commit_sha':
'2a072472d47eed2954c90ae05fe82cf36361bb6a', 'download_url': 'https://github.com/TWinsnes/galaxy-role-pihole/archive/v0.0.2.tar.gz', 'active': None}, {'id': 114997, 'url': '', 'related': {},
'summary_fields': {}, 'created': '2020-02-02T09:36:43.065967Z', 'modified': '2020-02-02T09:36:43.065996Z', 'name': 'v1.0.0', 'version': '1.0.0', 'commit_date': '2020-02-02T04:33:43-05:00', 'commit_sha':
'8e1bff81cd4b82956b2c4aaa94f938c0c3f1b971', 'download_url': 'https://github.com/TWinsnes/galaxy-role-pihole/archive/v1.0.0.tar.gz', 'active': None}]).`


[BUG] [azure-storage-blob] NullPointerException when calling any methods of BlobItem if it's a "prefix" blob item

Describe the bug
NullPointerException when calling any methods of BlobItem if it's a "prefix" blob item
Exception or Stack Trace
Add the exception log and stack trace if available
java.lang.NullPointerException: Cannot invoke "com.azure.storage.blob.implementation.models.BlobItemPropertiesInternal.getCreationTime()" because "this.internalProperties" is null
        at com.azure.storage.blob.models.BlobItemProperties.getCreationTime(BlobItemProperties.java:61)

To Reproduce
get a BlobItem instance of a "prefix" blob item, then call any of its methods, e.g. getCreationTime(), getProperties().
Code Snippet
Add the code snippet that causes the issue.
BlobItem item = ...
System.out.println(item.getCreationTime())

Expected behavior
No exception or remove this method for "prefix" BlobItem.
Screenshots
Setup (please complete the following information):

OS: [e.g. iOS]
IDE: [e.g. IntelliJ]
Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)]
Java version: [e.g. 8]
App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special]
Frameworks: [e.g. Spring Boot, Micronaut, Quarkus, etc]

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

### Tasks

Hi @wangmingliang-ms
An easy workaround for this is to check if the BlobItem is a prefix (by using BlobItem.isPrefix()), and if not, then you can continue making the calls to inspect getProperties(), getCreationTime(), etc.
For example:
BlobItem item = ...
if (!item.isPrefix()) {   BlobItemProperties properties = item.getProperties();   System.out.println(properties.getCreationTime()); }


Poor scaling for linear MPC example

The following example bilds a function to evaluate the dynamic constraints for a linear MPC problem. The size of the problem can be scaled up and down by modifying N, nx, nu. Already fr rather small problems with 6000 variables, it takes quite long time to build the expressions and making the function
compute cons expression: 2.007440 seconds (9.51 M allocations: 488.824 MiB, 14.34% gc time, 71.54% compilation time)
make_function: 6.885061 seconds (25.78 M allocations: 1.440 GiB, 15.88% gc time, 13.79% compilation time)

but the function takes forever (more than several minutes) to compile.
using FastDifferentiation

N = 100
nx = 40
nu = 20
ny = 20
Ts = 0.01
x = make_variables(:x, nx, N+1)
u = make_variables(:u, nu, N)
x0 = make_variables(:x0, nx)

function rollout(f, x0::AbstractVector, u)
    T = promote_type(eltype(x0), eltype(u))
    x = zeros(T, length(x0), size(u, 2)+1)
    x[:, 1] .= x0
    rollout!(f, x, u)
end

function rollout!(f, x, u)
    for i = 1:size(x, 2)-1
        x[:, i+1] = f(x[:, i], u[:, i])
    end
    x, u
end

const A = 0.1randn(nx,nx)
const B = randn(nx,nu)

f(x, u) = A*x + B*u

function dynamics_cons(x, u)
    xp, _ = rollout(f, x0, u);
    vec(xp .- x)
end

@time "compute cons expression" c = dynamics_cons(x, u);

vars = [x0; vec(x); vec(u)]

@time "make_function" fun = make_function(c, vars; in_place=false)

v = randn(length(vars))
@time fun(v);

There is obviously a lot of structure in this problem, perhaps this structure could be utilized to create more efficient functions?

I used the function number_of_operations (not exported from FastDifferentiation but maybe it should be) to count the number of operations in this function. I adjusted the parameters downwards from your original numbers:
#your original numbers
 # N = 100
    # nx = 40
    # nu = 20
    # ny = 20
    # Ts = 0.01
#new numbers giving smaller graph size
    N = 40
    nx = 40
    nu = 2
    ny = 2
    Ts = 0.01

With the smaller numbers the graph had 134,440 operations; generated code size becomes an issue around this size. With your original parameters the expression would be enormous by the standards of FD.
FastDifferentiation does not currently support looping directly so instead it unrolls all loops. Somewhere in the range of 1e5 to 1e6 operations the generated functions become large enough that FD takes a while to process them.
This limitation on expression graph size is mentioned in the limitations section of the documentation but perhaps it should be emphasized. And maybe I should export number_of_operations so people can measure size accurately.
The compilation time that took several minutes is entirely LLVM. There's no FD processing involved at that stage. I can't do anything about that.
But I can do something about the size of the generated code. I have several ideas for addressing this looping problem but it will be months before you see any of them released.

I noticed that you aren't computing any derivatives. It might still make sense to compute derivatives of this function since it appears to be quite sparse.
I don't know which parameters you want to differentiate with respect to but I computed this derivative
 jac = sparse_jacobian(c, vec(x))

for these parameters
 N = 2
    nx = 40
    nu = 2
    ny = 2
    Ts = 0.01

and got sparsity of .0083. Doubling the N parameter reduces sparsity to .005. At the scale of your original problem the sparsity might be a very small number although it would probably take a long time to compute the Jacobian.
This looks like one of those problems where the Jacobian that FD produces might take just a small constant times the number of operations of the original function.
If preprocessing time is a barrier then FD may not work for your application. However, I would not be surprised if the alternative AD algorithms are much slower at run time than the FD generated Jacobian.

One last comment. For reasons I don't fully understand the FD graph processing is very slow. This is almost completely unoptimized because I wanted to make the code correct and feature complete before worrying about optimization. But over the next few months I will be looking at this. There won't be miracles but speed might increase by 5x-10x. Won't help with the LLVM compile times though.

Does this address your issue? If it does I'll close it.

I did slightly modify the problem structure to make it a whole lot more sparse, the following takes
compute cons expression: 0.059047 seconds (135.67 k allocations: 5.062 MiB, 85.24% compilation time)
make_function: 0.032015 seconds (365.44 k allocations: 23.127 MiB, 44.90% gc time)
first function call: 40.128536 seconds (1.33 M allocations: 62.672 MiB, 0.03% gc time, 100.00% compilation time)
Benchmark:  5.016 μs (2 allocations: 55.11 KiB)

N = 80
nx = 8
nu = 2
ny = 2
x = make_variables(:x, nx, N+1)
u = make_variables(:u, nu, N)
x0 = make_variables(:x0, nx)

const A = 0.1randn(nx,nx)
const B = randn(nx,nu)

f(x, u) = A*x + B*u

function dynamics_cons(x0, x, u)
    c = similar(x)
    c[:,1] = x0 - x[:, 1]
    for i = 1:size(x, 2)-1
        c[:, i+1] = f(x[:, i], u[:, i]) - x[:, i+1]
    end
    vec(c)
end

@time "compute cons expression" c = dynamics_cons(x0, x, u);
vars = [vec(x); vec(u)]
jac = sparse_jacobian(c, vars)
@time "make_function" fun = make_function(jac, vars; in_place=false)
v = randn(length(vars))
@time "first function call" fun(v)
@btime $fun($v);

The first function call (LLVM) time is still very high. The resulting code benchmarks reasonably fast, but considering it's essentially just computing
    Ax = kron(speye(N + 1), -speye(nx)) + kron(spdiagm(-1 => ones(N)), Ad)
    Bu = kron([spzeros(1, N); speye(N)], Bd)
    Aeq = [Ax Bu]

it should be possible to reduce the LLVM compilation time substantially by recognizing this structure
Here's the manually coded Jacobian for completeness
using SparseArrays
speye(N) = spdiagm(ones(N))
function manual_jacobian(N, Ad, Bd)
    (nx, nu) = size(Bd)
    Ax = kron(speye(N + 1), -speye(nx)) + kron(spdiagm(-1 => ones(N)), Ad)
    Bu = kron([spzeros(1, N); speye(N)], Bd)
    Aeq = [Ax Bu]
end
jac_m = manual_jacobian(N, A, B)
jac_a = fun(v)
@assert norm(jac_m - jac_a) == 0 # test that they are equal

I'm exploring he use of FastDifferentiation for this since once you add slack variables and some other niceties to this problem, manually coding the Jacobians for the QP becomes extremely tedious and error prone. To feasibly rely on FD for this. I need it to scale to much larger problem sizes that what it currently does. It may very well be that FD is not the right tool for the job, and that's okay as well, I'm just exploring what's possible :)

I'm considering two methods for tackling the scaling problem. The first is what's called rerolling, recognizing indexing patterns in unrolled code and then automatically generating loops from that pattern. It's not necessary to completely undo the unrolling back to the original expression, just to reduce the expression size enough so that LLVM doesn't choke at the compilation stage.
The second is a general framework for differentiating tensor expressions. This uses a different form of the derivative graph which requires some wedging to fit into the FD framework. But, it can automatically and efficiently handle all the common matrix operations, convolution, and so forth. Anything which can be written as a tensor contraction on formulas of indices. This method has the advantage that there is no loop unrolling so expressions remain compact.
How big are your problems, in terms of number of operations?

The latest code above is very representative of linear model-predictive control, small such problems have perhaps nx = 4, N = 10, large problems can easily have nx = 100, N=1000, in particular if the system comes from a PDE discretization. In addition to the above, it's common to add slack variables, which can be thought of as doubling nx.

What LLVM compilation time would be acceptable? That will give me a target to shoot for.
Do you only have to compute the symbolic derivative once or does it change over time? If it changes over time does the structure of the function remain unchanged? This would be the case, for example, if variable coefficients change but the structure of the equation doesn't. I may be able to do something in this case that would process the constants specially so they can be updated without having to recompute the symbolic derivative and remake the function.

I can already kind-of do these things with Symbolics.jl, and am looking elsewhere due to their poor compile times, so it should be substantially faster than symbolics. In my experience, users (I'm developing software exposed to users though a GUI) really loose patience once you start exceeding 20-30s, I also need to compile not only the constraint Jacobian, but also the Hessian of the lagrangian, so ideally the total time is smaller than that.
The structure never change for these problems, but I do repeatedly compute Jacobians with different parameter values

If the times in your first message in this thread are representative of this problem class then the FD processing times are acceptable but the LLVM compile times are not.
Looks like FD will have to produce substantially smaller runtime generated functions to get those LLVM times where you want them. It will happen but as I said it will be a few months.

when you say x,u change do you mean these are the variables you take derivatives with respect to. And you use different values of x0 for the same structural Jacobian?
If this is the case there might be a relatively straightforward fix. his is something I can see being generally useful. The initial compile times would still be very long but you wouldn't have to recompute the Jacobian or re-compile the function just because the values for x0 changed. Let me think about this for a few days.

when you say x,u change do you mean these are the variables you take derivatives with respect to. And you use different values of x0 for the same structural Jacobian?

Correct. In general, there may be several problem-specific parameters that can change between calls to the MPC controller. The gradient is not taken w.r.t. those parameters, but they do change between instances. Setting the initial condition of the MPC controller each iteration is one use cases of this kind of non-differentiated parameter,  https://github.com/brianguenter/FastDifferentiation.jl/issues/13#issuecomment-1590412452 lists some other

I noticed that the Jacobian of c is contant so all the runtime generated function does is set constant values in an array.
The current FD code generator creates an assignment statement for each value. Don't know why it takes LLVM so long to compile code like this. But it wouldn't be that hard to detect long contiguous sequences of these values and write them more like this:
vals = [1.0,2.0,3.0,.....]

I did a simple test and found LLVM can process a 100,000 element array like this in .5 seconds on my laptop.
Unfortunately either the Julia compiler or LLVM seems to have a length limit that prevents compiling expressions in the range of 1e6 array elements.
But this would make it possible to scale to N=100, n=40 (number of non-zeros in jacobian = 172040) with FD times still in the seconds and LLVM time perhaps less than 1 second.
And I might be able to break the array definition into pieces somehow so larger expressions could be handled.
If I can do this would this be useful to you? Several other people have posted problems where the Jacobian is constant and large so this might be a generally useful optimization.
This is the symbolic output for N=2,n=2:
julia> test1()
6-element Vector{FastDifferentiation.Node}:
                                                                                (x01 - x1_1)
                                                                                (x02 - x2_1)
 ((((0.11526751354123002 * x1_1) + (0.11328140931571995 * x2_1)) + ((-0.8473378533858925 * u1_1) + (0.3686082615748242 * u2_1))) - x1_2)
 ((((0.018098192854194988 * x1_1) + (-0.1514665274098452 * x2_1)) + ((-0.4202610942649159 * u1_1) + (1.160902750563023 * u2_1))) - x2_2)
 ((((0.11526751354123002 * x1_2) + (0.11328140931571995 * x2_2)) + ((-0.8473378533858925 * u1_2) + (0.3686082615748242 * u2_2))) - x1_3)
 ((((0.018098192854194988 * x1_2) + (-0.1514665274098452 * x2_2)) + ((-0.4202610942649159 * u1_2) + (1.160902750563023 * u2_2))) - x2_3)

The jacobian of this function with respect to (x,u) is constant.
6×10 Matrix{FastDifferentiation.Node}:
                  -1                    0.0                  0.0                    0.0  0.0  0.0  …                  0.0                  0.0                  0.0
                 0.0                     -1                  0.0                    0.0  0.0  0.0                     0.0                  0.0                  0.0
 -0.1484629505332367  -0.039882977729197897                   -1                    0.0  0.0  0.0       1.226063017934781                  0.0                  0.0
 0.07205232591435677     0.1767138131541932                  0.0                     -1  0.0  0.0     0.08761872050648517                  0.0                  0.0
                 0.0                    0.0  -0.1484629505332367  -0.039882977729197897   -1  0.0                     0.0   0.7512839281234882    1.226063017934781
                 0.0                    0.0  0.07205232591435677     0.1767138131541932  0.0   -1  …                  0.0  -0.3737496248908396  0.08761872050648517

Is this what you intended? I tried this for several values of N,n, and all the jacobians are constant so all the runtime generated function does is fill in constant values in the jacobian array. Was this your intention or is there something missing from the functions?

The tensor differentiation code ideas I have would be much cleaner but those are months away. Whereas changing the code generation to handle constant array initialization could be a few days to a week.

My example here used a linear dynamics model (linear MPC), in which case the Jacobian is indeed constant, given by this manually coded Jacobian
function manual_jacobian(N, Ad, Bd)
    (nx, nu) = size(Bd)
    Ax = kron(speye(N + 1), -speye(nx)) + kron(spdiagm(-1 => ones(N)), Ad)
    Bu = kron([spzeros(1, N); speye(N)], Bd)
    Aeq = [Ax Bu]
end

Linear MPC is already a very useful problem to solve, but for nonlinear MPC (which is even more interesting), the Jacobian is not constant. It will, however, typically have the same sparsity structure.

If I can do this would this be useful to you?

That would certainly be very useful. Even for nonlinear MPC where the jacobian is non-constant, a significant part of the jacobian is still likely to be constant, so such an optimization could likely be useful even in this case.

I'm going to convert this to a discussion item. I don't have time to address this problem right now but I also don't want it to be buried in closed issues.


🚀 Feature: Add Support to YugabyteDB

🔖 Feature description
Hi, Please Add support to YugabyteDB because it can be scaled very easily and it is cloud native and also postgres compatible.
🎤 Pitch
YugabyteDB is Distributed SQL Database and it is a replacement for postgres db , it is cloud native so can be used in docker and scaled up or down according to the usage. It can be scaled to a very high transactions per second, so it will be easier to scale the appwrite system. Also it is open source.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@vaishakhpj I think this issue should be in https://github.com/appwrite/appwrite

Ok Thank you, will be posting there.

Closing as a duplicate of https://github.com/appwrite/appwrite/issues/5412


Add Build Dependencies to MakeFile

Adding dependencies command to make file.  Using this command to install all dependencies needed for TravisCI build.
The goal is to :

make it it easy to setup dev environment
make it easy to sync dependencies when new ones are added
ensure our build process & dev environment are similar

LGTM


Silence false positive UnconsumedParameterWarning

UnconsumedParameterWarning is emitted even if parameters are correctly consumed.
Description
There are two cases when UnconsumedParameterWarning is false positive:

camelCase or parameters with dashes in name are not correctly recognized when cfg parser is used.
Some parameters are defined in core section of config (autoload_range, no_configure_log), but are not needed in class instance (as must be used before class is initialized).

Motivation and Context
False positive UnconsumedParameterWarning forced me to completely disable this feature as any output to stderr is treated as error in pipelines.
Have you tested this? If so, how?
I've added unitests and tested this branch in my pipeline.

@andresgomezfrr Do you have any idea how to fix codecov?

@andresgomezfrr Do you have any idea how to fix codecov?

Could you try to update this branch with master?

Branch was updated, I've forced CI to retest PR.

Apologies for not merging this sooner!

I am using Luigi 3.5.2, the latest. But I still have these warnings!


pkg/broadcastwriter: avoid alloc w/ WriteString

This PR makes broadcastwriter avoid converting a string to a slice of bytes first before writing. This helps with #9139.
benchmark                    old ns/op     new ns/op     delta
BenchmarkBroadcastWriter     1178209       1147391       -2.62%

benchmark                    old MB/s     new MB/s     speedup
BenchmarkBroadcastWriter     21.00        21.56        1.03x

benchmark                    old allocs     new allocs     delta
BenchmarkBroadcastWriter     1510           1505           -0.33%

benchmark                    old bytes     new bytes     delta
BenchmarkBroadcastWriter     64724         64482         -0.37%

@jfrazelle I've added this to the 1.6.0 milestone because it's a very small change and it's useful. Please feel free to remove it from the milestone or tell me to do it if you think we shouldn't include this change.

LGTM
Very isolated change.
Ping @jfrazelle

LGTM


Create 'fluo list' command to list all Fluo applications within a Fluo instance

At a minimum, the command should list all applications configured in Zookeeper.  The command could also look up and print the state (stopped, running, etc) of each application.

#524 should probably be completed before this issue as the fluo list command should use instance.props.


Fix panic in pending_runtime_api with Aura consensus env (#814)

Rel MOON-1909

This changes the user error when the header cannot be unwrapped from:
for all runtime APIs
"Runtime api access error: {:?}", e

to
Cannot get header for block {:?}

Before we were just assuming the header could be unwrapped (wrong) and now handle that error specifically. Runtime api access error message still the same.

Thanks for explaining! As far as I understand

Before we were just assuming the header could be unwrapped (wrong) and now handle that error specifically.

We handle header not being unwrapped by returning the client error Cannot get header for block {:?}

Runtime api access error message still the same.

Now I think the runtime API access error is not emitted if the header cannot be unwrapped

So this PR applies https://github.com/paritytech/frontier/pull/842 to our frontier fork
I'm still not sure what this has to do with pallet-randomness::on_initialize being introduced in 1802...

So this PR applies https://github.com/paritytech/frontier/pull/842 to our frontier fork

Not really, or not only. This PR avoids the unwrap thing, but also builds the pending block over parent instead of best. And that's the main issue:
api.initialize_block(&best, &header) VS. api.initialize_block(&parent_hash, &header)

interesting, when is best != parent_hash?

when is best != parent_hash?

Always. best is the tip of the canonical chain, and in this case parent is best's parent.


Create com_wrappers.md

Changes proposed:
-Add a list of community wrappers at the bottom of the docs to allow developers to find them.

Thanks @Skillz4Killz!
@bguilder Bri - Wanna take this one and merge it in? I think we had some SDK stuff at one point, maybe this is more clear.

@genexp @bguilder Happy to help :) but I think it got done yesterday or the day before with a bunch of docs updates. I see all of this in there already. I kind of like the one thats in there, its cleaner than mine i suggest closing this and keeping it as is.

@Skillz4Killz - Thanks for the help! We lost the SDK's page for a little bit, but have it back now. Please let us know if you notice anything else that should be changed with the docs. Cheers!

Done!


Useful options and performance improvements for Pool

This is an improved version of the previous PR(#1591). It's more readable and offers useful options and improved performance. Please work with this PR when you're ready to merge this feature later.

Useful options
It offers more useful options like Commons DBCP.

Option
Default
Description

testOnBorrow
true
Indicates whether the connection is validated before borrowed from the pool.

testOnBorrowInterval
20000
The number of milliseconds that indicates how often to validate if the connection is working since it was last used.

initialSize
0 (off)
The initial number of connections that are created when the pool is started.

maxIdle
10
The maximum number of connections that can remain idle in the pool.

minIdle
0 (off)
The minimum number of connections that can remain idle in the pool.

maxReuseCount
0 (off)
The maximum connection reuse count.

timeBetweenEvictionRunsMillis
0 (off)
The number of milliseconds to sleep between runs of examining idle connections.

minEvictableIdleTimeMillis
1800000
he minimum amount of time the connection may sit idle in the pool.

numTestsPerEvictionRun
3
The number of connections to examine during each run of the eviction timer.

See Readme.md
Improved performance
Performance is improved by over 80% without doing anything.

Before
After

Executions per second
5,691
10,263

See benchmark code
More readable code
Focused on making the code easier to read and maintain for the following contributors, and tidy up wrong and unused logics.

I know that it's really hard to apply this right away because of people who use it in the wrong way such as accessing private underscore-prefix properties. Please consider it when major update is available later.

So I did at least try to start reviewing, but quickly started to notice this is not backwards-compatible at all. I then noticed your note at the bottom of the pull request to consider it on the next major, so my bad! I deleted those comments :)

I think it's too difficult to contribute a little big change. It seems to be prudent because many people use this module. I fully understand and agree on your thought.
So, I guess it'd be better to create a new module that can operate independently without changing mysql module. I'll try on it.
You can close this PR or refer to this concept later on for your next improvement.

I would love to see this merged, the perf boost alone is 🔥
@ifsnow is there a way you think you can split up the changes in either multiple PRs or multiple commits? I think that would make it easier to review and merge

As far as I can tell, the biggest part of the perf boost is simply because with this PR, the connections are no longer always validated when you fetch them (the validation only happens every so often). Basically trading off some extra perf for a greater chance to end up with a bad connection from the pool. I'm not sure if that is a good trade off.

BTW, isn't there already an independently operating pool module? generic-pool or somethibg like that?

sequelize and knex both use generic-pool

Ah, which based on help questions is a largr number of this module's users. I wonder: does it make sense for us to just use that module instead od trying to maintain out own pool implementation?
For example:

Should this module even provide a pool at all?
If it should, should it just be a precreated generic-pool instance?
If this module should have a pool buy not use generic-pool, what are the benefits?

oh if that is the tradeoff then that seems like a no go :P
providing a pool option in the lib is super useful and seems like a good and expected thing to have
the common module you are refering to is probably https://www.npmjs.com/package/generic-pool

@dougwilson I agree with your opinion, but I don't think it's efficient to validate the connection every time. That's because it's very unlikely that expected problems with a recently used connection will occur. So some guys say that turning off this option is recommended in many cases.
http://pubs.vmware.com/vfabric53/index.jsp?topic=/com.vmware.vfabric.tc-server.2.9/admin/manual-high-concurrency-jdbc.html
https://confluence.atlassian.com/adminjiraserver071/tuning-database-connections-802592189.html
I know about generic-pool. The reason I did not think about this is because I don't want to modify existing code.
If there is a difference of opinion, we don't need to discuss further.

mysql-pool-booster is for those who want to use experimental features of the pool.
I'm going to try various improvements about the pool in this project.


Write up instructions on how to add: CP, contributors

Step 1:  Fork / clone repo
Step 2:  Go to file xxx
Step 5:  copy and edit text within ::: [3 colons]; insert text above last :::: [4 colons]
:::{grid-item}

<img alt="Image for contributor template" src="../../_static/contributors_2022_07/carlo_dll.jpeg" class="rounded-circle">

Carlo Domenico Longo de Lemos

São Paulo, São Paulo (Brazil)

[{fab}`github`](https://github.com/vitaliset)
[{fab}`linkedin-in`](https://www.linkedin.com/in/carlo-lemos)
:::

cc:  @symeneses @OriolAbril

I added extensive comments to the file, they don't appear on the markdown preview or website but can be seen when reading the raw text which is what should be used to copy the template. It can help with this: https://raw.githubusercontent.com/pymc-devs/pymc-data-umbrella/main/2022-07_sprint/sprint_parties/contributors.md


Query alsa to determine the sound channels

Use alsa::snd_pcm_query_chmaps to get the available sound channel mappings.

The required functions where added in ALSA 1.0.27, while Travis unfortunately has 1.0.25.

Duplicate of: https://github.com/tomaka/cpal/pull/67 :)

And conflicts with #84
I don't really know how to handle that except by dynamically loading dlopen and dispatching depending on the version.

Ah I see! Should look through the issues more carefully next time ;)


Rancher 2.6 - Catalog not working throughout proxy

Rancher Server Setup

Rancher version: 2.6.0
Installation option (Docker install/Helm Chart): Docker install
Proxy/Cert Details: proxy set with environment variable set on docker run (HTTP_PROXY, HTTPS_PROXY, NO_PROXY)

Information about the Cluster

Kubernetes version: 1.20
Cluster Type (Local/Downstream): Local

Describe the bug
Add catalog from ui / terraform not working because of it try to access on direct, without use proxy.
Get "https://helm.elastic.co/index.yaml": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
or
Get "https://helm.elastic.co/index.yaml": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

To Reproduce
Block internet access with Firewall and set proxy when you run rancher with docker:
docker run --privileged \
-e "HTTP_PROXY=http://proxy:8080" \
 \
-e "HTTPS_PROXY=http://proxy:8080" \
 \
-e "NO_PROXY=localhost,<IP_ADDRESS>" \
\
-p 80:80 \
 \
-p 443:443 \
 \
-v /data/rancher-server:/var/lib/rancher \
--restart=unless-stopped \
--name rancher-server \
rancher/rancher:v2.6.0

Go to rancher ui -> your k8s cluster -> Apps & Marketplace -> Chart repositories -> Create
name: elastic
url: https://helm.elastic.co

Result
Timeout because it try to access on direct without use proxy
Expected Result

Download / sinc catalog without error
Screenshots

Additional context
<!--Add any other context about the problem here.—>

I think is not provide HTTP_PROXY, HTTPS_PROXY and NO_PROXY on deployement cattle-cluster-agent, namespace cattle-system


swift-module-digester: reenable test for Json serialization diagnostics.

preset=buildbot,tools=R,stdlib=RD,smoketest=macosx,single-thread
@swift-ci Please test with preset macOS

preset=buildbot,tools=R,stdlib=RD,smoketest=macosx,single-thread
@swift-ci Please test with preset macOS

@shahmishal any idea why the preset test runner has thrown exception twice in a row? I'd like to run a smoke test with the same setting here: https://ci.swift.org/job/oss-swift_tools-R_stdlib-RD_test-simulator/.

preset=buildbot,tools=R,stdlib=RD
@swift-ci Please test with preset macOS

@swift-ci please smoke test


Axis won't use decimal point values for scaling

Hey guys, I want to make the y axis ticks be in the step size of the max value (e.g. if the max value is 10, the ticks are 0, 2.5, 5, 7.5, 10). However it's rounding up and I'm not sure how to prevent that. Option used:
Expected Behavior
Steps to have decimal values: [0, 2.5, 5, 7.5, 10]
Current Behavior
Steps get rounded up to : [0, 3, 5, 8, 10].
Steps to Reproduce (for bugs)

Make sample chart  with any data and use the following scale option: scales: {      yAxes: [{        ticks: {          min: 0,          max: 10,          stepSize: 2.5,          display: true,          beginAtZero: true        }      }]    }

Context
I want to be able to set the step size to any value I want and be able to scale properly. Currently when it automatically rounds up, it looks off and it's not the result I want anyway.
Environment

Chart.js version: 2.6
Browser name and version: Nodejs 9

@serratedserenade its likely the format function that is removing the decimal place. You could try a custom format function that uses a fixed number of decimal places and see if that changes things

This is resolved by #4841. Set ticks.precision to 1.

This was not fixed in #4841 because ticks.precision is effective only if stepSize is not specified. I created a new PR #5786.


third_party/icu/data missing big-endian conversion data files

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
tf 2.11
Custom Code
Yes
OS Platform and Distribution
Linux Ubuntu 20.04 s390x
Mobile device
No response
Python version
3.10
Bazel version
5.3.0
GCC/Compiler version
gcc 9
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Two of the unicode unit tests fail on s390x due to the icu_conversion_data.c.gz.* files being in little-endian format.

Could big-endian formatted versions of the icu_conversion_data.c.gz.* files be added so that they can be selected when building on s390x?

Standalone code to reproduce the issue
The unit tests:

* //tensorflow/python/kernel_tests/strings_ops:unicode_decode_op_test
* //tensorflow/python/kernel_tests/strings_ops:unicode_transcode_op_test

fail on s390x.

Relevant log output
======================================================================
ERROR: testDecodeWithDifferentEncodings5 ('SHIFT-JIS', ['Hello', 'こんにちは']) (__main__.UnicodeDecodeTest)
UnicodeDecodeTest.testDecodeWithDifferentEncodings5 ('SHIFT-JIS', ['Hello', 'こんにちは'])
testDecodeWithDifferentEncodings('SHIFT-JIS', ['Hello', 'こんにちは'])
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jalbrecht/.cache/bazel/_bazel_jalbrecht/d88fb95a52e214eb99836e3d1a65a951/execroot/org_tensorflow/bazel-out/s390x-opt/bin/tensorflow/python/kernel_tests/strings_ops/unicode_decode_op_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1378, in _do_call
    return fn(*args)
  File "/home/jalbrecht/.cache/bazel/_bazel_jalbrecht/d88fb95a52e214eb99836e3d1a65a951/execroot/org_tensorflow/bazel-out/s390x-opt/bin/tensorflow/python/kernel_tests/strings_ops/unicode_decode_op_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1361, in _run_fn
    return self._call_tf_sessionrun(options, feed_dict, fetch_list,
  File "/home/jalbrecht/.cache/bazel/_bazel_jalbrecht/d88fb95a52e214eb99836e3d1a65a951/execroot/org_tensorflow/bazel-out/s390x-opt/bin/tensorflow/python/kernel_tests/strings_ops/unicode_decode_op_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1454, in _call_tf_sessionrun
    return tf_session.TF_SessionRun_wrapper(self._session, options, feed_dict,
tensorflow.python.framework.errors_impl.InvalidArgumentError: Could not create converter for input encoding: SHIFT-JIS
         [[{{node UnicodeDecode/UnicodeDecode}}]]

Hi @jonathan-albrecht-ibm ,
Could you please confirm the bazel command you have used for the tests?  Thankyou!

Hi @SuryanarayanaY, here is the bazel command I used that will run the failed tests:
TF_SYSTEM_LIBS="boringssl" bazel --host_jvm_args="-Xms1024m" --host_jvm_args="-Xmx2048m" test --build_tests_only --build_event_json_file=../logs/bazel-build-events-unicode.json --define=tflite_with_xnnpack=false -- //tensorflow/python/kernel_tests/strings_ops:unicode_decode_op_test //tensorflow/python/kernel_tests/strings_ops:unicode_transcode_op_test

Note that when building on s390x, there are some extra changes required for ssl (TF_SYSTEM_LIBS="boringssl") and xnnpack (--define=tflite_with_xnnpack=false since not available on s390x) that are unrelated to the unicode tests.
I've dug into it a bit more and I'll add some more info in a follow up comment.

Hi @SuryanarayanaY,
Following the instructions in https://github.com/tensorflow/tensorflow/blob/6537d7f689b234c7f945fe3b5d094317716148b0/third_party/icu/data/BUILD.bazel#L16-L43 I was able to generate the big-endian format files on a little-endian x86_64 VM with icu version release-69-1.
After creating icudt69l_dat.c:

generate the big-endian .dat file with icupkg -tb ./icudt69l.dat icudt69b.dat
generate the big-endian icudt69b_dat.c file with genccode icudt69b.dat
add the conversion wrapper function with echo "U_CAPI const void * U_EXPORT2 uprv_getICUData_conversion() { return icudt69b_dat.bytes; }" >> icudt69b_dat.c

Then the icudt69b_dat.c can be gzip'd and split to a set of eg. icu_conversion_data_big_endian.c.gz.* files.
The conversion_files filegroup (https://github.com/tensorflow/tensorflow/blob/6537d7f689b234c7f945fe3b5d094317716148b0/third_party/icu/data/BUILD.bazel#L44-L47) can also be updated to select the big-endian files on s390x. Something like this:
filegroup(
    name = "conversion_files",
    srcs = select({
        "@org_tensorflow//tensorflow:linux_s390x": glob(["icu_conversion_data_big_endian.c.gz.*"]),
        "//conditions:default": glob(["icu_conversion_data.c.gz.*"]),
    }),
)

With those changes in place, the unicode tests all pass and I didn't see any regressions in other tests when running the full test suite.

Hi, Could you please check the comment on the above linked PR and explain on handling big-endian conversion( which is solved in your case).

H @sachinprasadhs, Thanks for helping with this.
Your PR also needs to include the big-endian conversion which can be generated from the little-endian .dat file. My comment above (https://github.com/tensorflow/tensorflow/issues/59935#issuecomment-1466304945) explains how to do that:
You will need to follow all of the existing instructions to generate the little-endian conversion files in: https://github.com/tensorflow/tensorflow/blob/6537d7f689b234c7f945fe3b5d094317716148b0/third_party/icu/data/BUILD.bazel#L16-L43
then follow these instructions to generate the big-endian conversion files.

After creating icudt69l_dat.c:

generate the big-endian .dat file with icupkg -tb ./icudt69l.dat icudt69b.dat
generate the big-endian icudt69b_dat.c file with genccode icudt69b.dat
add the conversion wrapper function with echo "U_CAPI const void * U_EXPORT2 uprv_getICUData_conversion() { return icudt69b_dat.bytes; }" >> icudt69b_dat.c

Then the icudt69b_dat.c can be gzip'd and split to a set of eg. icu_conversion_data_big_endian.c.gz.* files.

Finally the new big-endian conversion files will need to be included in your PR.
Let me know if you have any questions and I will try to help.

Thanks for pointing me to the details, would you be interested to work on this PR, since you already have the workflow ready. I can go ahead and close the PR.

Hi @sachinprasadhs, I'll need to get internal approval on my side before I can submit a PR and it could take some time. I appreciate your time looking at this. If you are still interested I could work with you to help you generate the big-endian files otherwise I will try to get approval to create a PR.

Yes please, I would need your help in making this PR, since I have limited knowledge on this topic.

Thanks for offering to help @sachinprasadhs! The first step would be to generate the little-endian data file using the instructions at: https://github.com/tensorflow/tensorflow/blob/6537d7f689b234c7f945fe3b5d094317716148b0/third_party/icu/data/BUILD.bazel#L16-L43
If you have any specific questions I'd be happy to help.

@nitins17 , Can you take a look into this request or help me connecting with the right person who can look into it. Thanks!

Thanks for flagging this issue and sorry about the late reply! Unfortunately, I do not have familiarity with the failing tests so I don't think I can review your PR.
@rohan100jain Do you think someone from your team would be a better fit to review this?

@mihaimaruseac hope you don't mind my reaching out directly but from looking at the git history, I think you might be able to help with this third_party/icu issue.
Due to internal reasons, I'm not going to be able to open a PR for this anytime soon. I figured out how to generate the big-endian format data files on amd64 and added the details above.
Would generating the big-endian data files and adding them into third_party/icu/data be something you would have time to do? Any help would be greatly appreciated but I certainly understand if time or other reasons won't allow.

Unfortunately I not longer work in TF (left the team nearly a year ago). I am consulting from time to time (especially on security topics, but also on OSS), and might contribute here and there with some PRs, but my main bulk of work is no longer in TF. So it will take some time until I can handle this.

Thanks @mihaimaruseac, I appreciate it!

I'm starting to think that the solution here might be to just generate the conversion files at build time, instead of storing them in the repo. There are several requirements that could be pushing towards that

Adding @MichaelHudgins for visibility

Thanks for the ping @mihaimaruseac.  I think if we could move towards generation at build time instead of storing all of those conversion in third_party that would be best.

Hi @MichaelHudgins, just wanted to check if there were any updates on this issue?

Unfortunately no update IIRC the person working on this had trouble getting a build rule that worked on this for all systems in a timely manner and no longer works on the project.  Its unfortunately not a very high priority right now so no new progress has been made.

Thanks for the quick reply @MichaelHudgins

"Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space."

@LavanyaKV1234 this issue is still relevant


Added support for storing assets on S3

This PR adds the ability to push assets up to an S3 bucket rather than an FTP server.
I'm using the grunt-aws package to do most of the heavy lifting. Sadly this does not yet support true syncing, so while it will push up assets it doesn't remove assets from the bucket that have been deleted locally.
The command to push assets to S3 is:
npm run images:s3
Breaking change I've renamed the npm run images task to npm run images:ftp so that we're being explicit about the storage target.
I'll put together some documentation for the wiki before this gets merged in.

Just chiming in about updating the documentation as well. :)
Here and here.

I've updated the wiki with the S3 documentation. Merging this in now.


Update the setup.py file

Proposed changes
The setup.py file is out of date. It needs to be updated for this new version release.
Context
We have changed some of the dependencies, such as using httpx instead of aiohttp to make http requests. The author is also out of date. Basically, this needs a possible rewrite due to the significant number of changes we are making for v3.
Possible Implementation
Research what is needed in a setup.py file and make appropriate changes.
Other information
Need to consider the version - this needs to stay in sync as the SDK is updated.

This should be fixed in this PR
https://github.com/deepgram/deepgram-python-sdk/pull/172

updated in this PR:
https://github.com/deepgram/deepgram-python-sdk/pull/182

This PR should address the requirements updates. All dependencies are contained at the root of the repo.
https://github.com/deepgram/deepgram-python-sdk/pull/182


feat: Design for an empty list or no results found

Type of feature
🍕 Feature
Current behavior
Design is required for an empty list or no results found. It's related to issue #778.
Suggested solution
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

cc: @getaheaddev

Hey @isabensusan, Would it be ok to use something similar to what we have here

and update the copy for both repositories and contributors table to also fix https://github.com/open-sauced/app/issues/1280


Update text input border values to gray-60 to match Design Manual standard

https://github.com/cfpb/design-manual/pull/503/ updates the standard to grey-60 (used to be gray-40). This makes the change in Capital Framework.
Same change over at cfgov-refresh: https://github.com/cfpb/cfgov-refresh/pull/3218
Changes

Change input-border variable to grey-60 to match latest Design Manual updates for text inputs and checkboxes

Sorry, totally forgot this needs an entry in the unreleased section of https://github.com/cfpb/capital-framework/blob/canary/CHANGELOG.md to get scooped up!


Document identifier pattern for "copublished" documents is "IEC/ISO {stage}" not "IEC/ISO/{stage}"

From source issue: https://github.com/metanorma/metanorma-iso/issues/648

In ISO, the document identifier pattern for "copublished" documents is "IEC/ISO {stage}" not "IEC/ISO/{stage}", e.g. https://www.iso.org/standard/56572.html.

Current presentation xml:
<docidentifier type="ISO">IEC/ISO/PWI 83000</docidentifier>
<docidentifier type="iso-undated">IEC/ISO/PWI 83000</docidentifier>
<docidentifier type="iso-with-lang">IEC/ISO/PWI 83000(E)</docidentifier>
<docidentifier type="iso-reference">IEC/ISO/PWI 83000:2022(E)</docidentifier>

Source adoc: https://github.com/metanorma/iso-iec-smart-terms

Relaton ISO and PubID-ISO generates the correct PubIDs.
I think we need to now clarify this properly. The types of these identifiers are not properly distinguished. In addition, we are also missing the dated form "IEC/ISO PWI 83000:2022".
Maybe we should do something like this:
<docidentifier type="urn:pubid:iso:dated">IEC/ISO PWI 83000:2022</docidentifier>
<docidentifier type="urn:pubid:iso:dated:lang">IEC/ISO PWI 83000:2022(E)</docidentifier>
<docidentifier type="urn:pubid:iso:undated">IEC/ISO PWI 83000</docidentifier>
<docidentifier type="urn:pubid:iso:undated:lang">IEC/ISO PWI 83000(E)</docidentifier>

When the Publisher element contains a “slash” (“/”), the separation in front of the document stage will be converted into an empty space.

Yes. See ISO DIR 2. You never knew this!?

I am not seeing documentation of how to do so in the readme or the rspec. @mico I will need exemplars of how to use this gem to generate an identifier given publishers, stages, numbers, etc.

Posted to https://github.com/metanorma/pubid-iso/issues/54 . @mico can you please provide documentation and examples?

This is not ready for actioning.

I'm trying to encourage a discussion. If you are happy with what is proposed, we will implement that in pubid-iso (and across pubid gems as a whole.)

Proceed. Issue on hold until https://github.com/metanorma/pubid-iso/issues/54 is done.

With pubid-iso in place and documented (to the degree needed), I am replacing ID generation code in metanorma-iso with pubid-iso.

https://github.com/metanorma/pubid-iso/issues/70
The pubid-iso generator remains unfit for purpose. This ticket is put back on hold.

Remaining blocker is https://github.com/metanorma/pubid-iso/issues/125, everything else appears to be done.

Blocker now becomes https://github.com/metanorma/pubid-iso/issues/130

Test again.

Cannot test again, current branch is buggy. Will not action anything until there is a working branch

Now pending:
https://github.com/metanorma/pubid-iso/issues/189
https://github.com/metanorma/pubid-iso/issues/192
https://github.com/metanorma/pubid-iso/issues/193
With FYI on:
https://github.com/metanorma/pubid-iso/issues/191

Work on this is now concluded. @mico please contact @andrew2net to arrange release of pubid-iso, and notify me when done, so I can merge the metanorma-iso PR. This will again need to be a major version release (0.4.0), and I note that the removal of the with_date option is now crashing relaton-iso.


Small performance issue with simple_usertype.

There's a small performance issue I noticed with sol::simple_usertype. You are using std::map for storing variables and functions and performing lookups, which even though works fine for a small number of elements, it starts degrading performance when it comes to larger usertypes, making it slightly slower than old sol.
Changing these two typedefs to use std::unordered_map instead provides a significant performance increase (as illustrated below). There are no benefits to using the ordered std::map implementation in this case anyway, so std::unordered_map would be the better choice.
With std::map and 4 member variables:

With std::unordered_map and 4 member variables:

With std::map and 50 member variables:

With std::unordered_map and 50 member variables:

Please ignore the plain C results as I didn't adapt their benchmarking code.

I accidentally submitted this issue without a description. I've written the description now, sorry for that.

https://github.com/ThePhD/sol2/releases/tag/v2.14.0
Backported. Thanks for checking it for me!

This is going to sound strange, but you should initialize the unordered
maps with a size that "makes sense" given the average simple type. The
default implementation can lead to massive memory usage for no gain as more
are added over time. If necessary, make it configurable, if not, don't!
Sent from a mobile device.
On Sep 14, 2016 00:12, "The Phantom Derpstorm"<EMAIL_ADDRESS>wrote:

Closed #216 https://github.com/ThePhD/sol2/issues/216.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ThePhD/sol2/issues/216#event-788586915, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AASdHV9hLwWllzoh4SZ0iDu8MAA9_zKMks5qp3QygaJpZM4J8Ez4
.


Compile error when RealmSwift bridge Objective-C ++

ViewController.mm
#import "ViewController.h"
#import "TestMMC-Swift.h"

NSString *const kJoyrunCacheDocumentPath = [[NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) lastObject] stringByAppendingPathComponent:@"message"];

@implementation ViewController

- (void)viewDidLoad {
    [super viewDidLoad];
    // ...
}
@end

XMMessage.swift
class XMMessage: Object, HandyJSON {
    @objc dynamic var sequnce = 0
    @objc dynamic var packetId = ""

    override static func primaryKey() -> String? {
        return "packetId"
    }
}

Compile error:
In file included from /Users/weiminghua/Documents/test/TestMMC/TestMMC/ViewController.mm:10:
/Users/weiminghua/Library/Developer/Xcode/DerivedData/TestMMC-esgjzclasjgelictgaogrncmaypv/Build/Intermediates.noindex/TestMMC.build/Debug-iphonesimulator/TestMMC.build/DerivedSources/TestMMC-Swift.h:217:24: error: cannot find interface declaration for 'RealmSwiftObject', superclass of 'XMMessage'
@interface XMMessage : RealmSwiftObject

I have tested calling a Realm Object declared in Swift from ObjC and did not encounter issues.
Could you please answer the following:

How are you including the RealmSwift dependency? Pods? Carthage? SPM?

Also, sending along a self contained project with your issue would be helpful.

Apologies, I misunderstood that you were calling this from ObjC++.
It is not possible to call Swift from ObjC++: https://stackoverflow.com/questions/24042774/can-i-mix-swift-with-c-like-the-objective-c-mm-files.
I would recommend following the advice of that issue:

You cannot import C++ code directly into Swift. Instead, create an Objective-C or C wrapper for C++ code.


Enabling "Grayscale" on Android Device does not display grayscale when mirrored

This also occurs with color inversion and color correction. Unsure if this would be a feature request or bug.

Android probably applies the filter afterwards (not on the surface which is encoded).

that is how andorid's grey-scale and color inversion works.
to reconfirm take a screenshot in grey-scale view the screenshot in it will be in color

yeah a screenshot does exhibit that behavior. Oh well, it is likely more trouble than it is worth/could just run Windows in grey-scale. Thank you.


v0.15 is more stable

I wanna continue using the stable v0.15. v0.15 is not perfect but it feels more like professional quality software. And I believe v0.15 should be offered side by side the latest version as the stable version. I have used the latest version v0.18 and it is very unstable and not fit for use. Thank you.
And can we not see this notification in the future?

I strongly believe people should at the other end of stable software. They should not be given alpha software.
And the second point I want to make is...
If somebody is happy using an old version they shouldn't be pushed, forced and shoved until they install the new version. The user should be in control.

@kaecy
I feel your pain.
When I know about PicoTorrent in May 2016, there is only one missing feature to me Labes #278. But author start this infinity migration on different frontend (wx, qt). But instead of speeding up the introduction of new features, it has led to a deterioration in the quality of existing functionality.
Rechecking torrent in #407 not fixing 3 year (oh, I'm forgot that with start so long).
Open .torrent files not alwayes handle by PT.
And more, and more...
It's very sad :-(

So, I can somewhat understand your opinions and if I had infinite time to pour into the development of PicoTorrent I would do things differently.
Unfortunately, though, this is not my day job, and that means I have to try to make my life as easy as possible when it comes to whatever time I can put into this project. I'm trying different frontends to make my life easier - wxWidgets was easier than WinAPI, but Qt is way easier than wxWidgets, and that's where we are today.
I know there has been issues dragging on for way too long, and I know things are a bit unstable here and there. I'm working on it, and I hope I can wrap everything up in a few more minor releases so I can release a 1.0 later this year.
The harsh truth is, I do this for fun, I have no obligations to support anything for anyone. If you're happy with a version, feel free to keep using it. If you want to maintain that version, feel free to fork it and add/remove whatever features and bugs you like. Everything is open source, which means you have that power.
If you want to help improve PicoTorrent (i.e help me move forward) you are more than welcome to engage in issues, @ me to ask for comments, guidance or whatever you might need. Send pull requests (which you've done @birkoffe and I'm very happy for it!).
Reach out and be constructive. We are rolling forward, and I'm not maintaining multiple versions.

Thanks @kaecy I tried version 0.15 and it works great
Before that I tried the latest version 0.18 and it crashes due to the cyrillic-paths
I think version 0.18 brought back old issues.
P.S. How many years Qt and it still cannot work normally with non-Latin paths in windows?

@Geograph-us can you share an example of the issues you’re experiencing with Cyrillic paths?

Video example and crashdump
Desktop 2020.03.23 - <IP_ADDRESS>.mp4.zip
c0edd019-7a9d-4140-b531-4ae601e49c9c.zip

Thanks @Geograph-us! That really helps!

As long as this post helped one person that's good enough. If you love v0.15 share it.

@Geograph-us The issue you mentioned should be fixed in #831


[Snyk] Upgrade @aws-sdk/client-s3 from 3.429.0 to 3.445.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @aws-sdk/client-s3 from 3.429.0 to 3.445.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 10 versions ahead of your current version.
The recommended version was released 22 days ago, on 2023-11-07.

Release notes

Package name: @aws-sdk/client-s3

3.445.0 - 2023-11-073.445.0(2023-11-07)
Chores

codegen:

update smithyVersion to 1.40.0 (#5462) (aa2e38fd)
bump codegen version to 0.19.0 (#5450) (5538f3be)

New Features

clients:  update client endpoints as of 2023-11-07 (46616b4f)
client-dlm:  Added support for pre and post scripts in Amazon Data Lifecycle Manager EBS snapshot lifecycle policies. (eafa4171)
client-dataexchange:  Updated SendDataSetNotificationRequest Comment to be maximum length 4096. (8292e07d)
client-rds:  This Amazon RDS release adds support for the multi-tenant configuration. In this configuration, an RDS DB instance can contain multiple tenant databases. In RDS for Oracle, a tenant database is a pluggable database (PDB). (c28ec75c)

Bug Fixes

cloudfront-signer:  add tslib (#5460) (54cc5c4b)
core:  add tslib (#5459) (35a1aed1)

For list of updated packages, view updated-packages.md in assets-3.445.0.zip

3.441.0 - 2023-11-013.441.0(2023-11-01)
Chores

client-sqs:  create coercing serializers for awsQueryCompat (#5440) (88213abe)

New Features

client-rds:  This release adds support for customized networking resources to Amazon RDS Custom. (0c0921a9)
client-global-accelerator:  Global Accelerator now support accelerators with cross account endpoints. (e4aa35f2)
client-connect:  Adds the BatchGetFlowAssociation API which returns flow associations (flow-resource) corresponding to the list of resourceArns supplied in the request. This release also adds IsDefault, LastModifiedRegion and LastModifiedTime fields to the responses of several Describe and List APIs. (6e0eda33)
client-sagemaker:  Support for batch transform input in Model dashboard (1725b9ce)
client-redshift:  Added support for Multi-AZ deployments for Provisioned RA3 clusters that provide 99.99% SLA availability. (1ef476e4)
lib-dynamodb:  large number handling (#5427) (4c7fe9cf)

For list of updated packages, view updated-packages.md in assets-3.441.0.zip

3.440.0 - 2023-10-313.440.0(2023-10-31)
New Features

client-translate:  Added support for Brevity translation settings feature. (98b75672)
client-m2:  Added name filter ability for ListDataSets API, added ForceUpdate for Updating environment and BatchJob submission using S3BatchJobIdentifier (d6cf6653)
client-application-insights:  Automate attaching managed policies (2320c7c7)
client-amplify:  Add backend field to CreateBranch and UpdateBranch requests. Add pagination support for ListApps, ListDomainAssociations, ListBranches, and ListJobs (df2f16b2)
client-neptunedata:  Minor change to not retry CancelledByUserException (1c2b78d2)
client-ec2:  Capacity Blocks for ML are a new EC2 purchasing option for reserving GPU instances on a future date to support short duration machine learning (ML) workloads. Capacity Blocks automatically place instances close together inside Amazon EC2 UltraClusters for low-latency, high-throughput networking. (5f73bcda)

Bug Fixes

middleware-sdk-s3:  remove error name check to allow for region redirect for HEAD operations (#5425) (eed5dcc6)

For list of updated packages, view updated-packages.md in assets-3.440.0.zip

3.438.0 - 2023-10-27

3.437.0 - 2023-10-26

3.436.0 - 2023-10-25

3.435.0 - 2023-10-24

3.433.0 - 2023-10-20

3.431.0 - 2023-10-18

3.430.0 - 2023-10-17

3.429.0 - 2023-10-16

    from @aws-sdk/client-s3 GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

get it later


Breaks with Python option enabled: error: no matching function for call to 'evalScript'

/usr/bin/c++ -DPLI_DLLESPEC="" -DPLI_DLLISPEC="" -DSURELOG_WITH_PYTHON -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src -I/disk-samsung/freebsd-ports/cad/surelog/work/.build/generated/src -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/antlr4_fast/runtime/Cpp/runtime/src -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/flatbuffers/include -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/googletest/googletest/include -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/googletest/googlemock/include -I/usr/local/include/python3.8 -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/UHDM/third_party/capnproto/c++/src/capnp/.. -I/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/third_party/UHDM/third_party/capnproto/c++/src/kj/.. -isystem /disk-samsung/freebsd-ports/cad/surelog/work/.build/third_party/UHDM/generated -O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -fno-omit-frame-pointer  -isystem /usr/local/include -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free  -O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -fno-omit-frame-pointer  -isystem /usr/local/include -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -Wall -O3  -DNDEBUG  -std=gnu++17 -MD -MT CMakeFiles/surelog.dir/src/ErrorReporting/ErrorContainer.cpp.o -MF CMakeFiles/surelog.dir/src/ErrorReporting/ErrorContainer.cpp.o.d -o CMakeFiles/surelog.dir/src/ErrorReporting/ErrorContainer.cpp.o -c /disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src/ErrorReporting/ErrorContainer.cpp
/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src/ErrorReporting/ErrorContainer.cpp:254:15: error: no matching function for call to 'evalScript'
        tmp = PythonAPI::evalScript("__main__", "SLformatMsg", args,
              ^~~~~~~~~~~~~~~~~~~~~
/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src/API/PythonAPI.h:57:22: note: candidate function not viable: cannot convert argument of incomplete type 'void *const' to 'PyThreadState *' (aka '_ts *') for 4th argument
  static std::string evalScript(std::string module, std::string function,
                     ^
/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src/API/PythonAPI.h:60:15: note: candidate function not viable: requires 3 arguments, but 4 were provided
  static void evalScript(std::string function, SV3_1aPythonListener* listener,
              ^
/disk-samsung/freebsd-ports/cad/surelog/work/Surelog-0.0-3950-g88ae53316/src/API/PythonAPI.h:70:15: note: candidate function not viable: requires 2 arguments, but 4 were provided
  static bool evalScript(std::string script, Design* design);
              ^

clang-12
python-3.8

Pretty much everybody has ran away from the Python API of Surelog, it is not maintained.
Why do you want to use it?
UHDM is a far superior API.

Why do you want to use it?

I didn't know that Pretty much everybody has ran away from the Python API of Surelog, it is not maintained.

Please use the UHDM API.

FYI, I fixed a compilation issue in Python since there was another inquiry.
Maybe that fix your issue too.


fix: ensure that error is a string to check error codes

previously we were assuming that error is a string
which has the method includes
in some cases however it is an error object and
has to be converted into a string
fixes #257

Thanks @rburgst ! Much appreciated 😄
This is published in<EMAIL_ADDRESS>


WIP: Fix OSX plotting

Closes #2157.
I need to test to see if this actually works, but it follows suggestions in https://github.com/matplotlib/matplotlib/issues/1852. I have a feeling it will not fix our immediate problem.

Ok let us know.  Thx

Should be fixed now @dengemann please give it a try

Note that this also fixes a stupid issue that we've been having with Travis, where conda was installing libpng-1.6 which isn't compatible with our old build of matplotlib. I can split that into a separate PR if necessary, but both of these changesets can be backported to 0.9 so it should be okay if the review burden is not too high.

Thanks !

FYI I pushed these three commits to maint/0.9 so tests can pass there too


.news

try bbc.news:
error:
dial tcp: lookup news.whois-servers.net: no such host

I think must be whois.nic.news
https://www.iana.org/domains/root/db/news.html

Hello @mhf-ir
Thanks for feedback, I will fix it.

Hello @mhf-ir
This has been fixed, please try the latest version.

If you think this repository is helpful, please share it with friends, thanks.


Help

how do i solve the error?

Hi zNightLastTR,
In the tank-game directory, you need to run the audit comment:(noted: It will install some vulnerablilites package)

npm audit fix --force

After that you can use the start command

npm start

Hope that it work for you.
Herca


Multiple Thermostat Card Instances

It appears that only one instance is supported.    A separately defined card with a different entity does not get rendered.

Multiple thermostat cards definitely work. I have 3 defined in my config. Please double check.


Fix bug when passing twig to Kirby->trigger

Fixes https://github.com/lemmon/kirby-portfolio-theme/issues/2

https://github.com/lemmon/kirby-portfolio-theme/issues/2#issuecomment-664144702


Cannot disable agent if enabled in cloned template configuration

Hi,
I'm encountering an issue with the agent configuration.
When the agent is enabled in the configuration of the cloned template, i cannot disabled it.
The VM is created without error but the agent stay enabled.
I do have the line agent = 0 in my main definition file.
It work perfectly fine in the other way, if the agent is disabled in the cloned tempate, it does get enabled with agent = 1.
Could it be a problem with the proxmox API rather than this provider ?
I'm planning to investigate more next week, but i wanted to know if anyone had seen something similar ?
Version :

Terraform = 1.4.6
Proxmox provider = 2.9.14
Proxmox = 8.0.3

I come back way later than anticipated to make an update.
I've done more tests while inspecting the requests sent to proxmox (with mitmproxy).
When the agent option is enabled on the VM template, terraform don't set the agent options in the urlencoded part of the POST request sent to  https://<@IP>:8006/api2/json/nodes/<node_name>/qemu/<vmid>/config
I'm not a developper so i won't be able to really investigate further sorry.


Disable job buttons and show tooltips

Soundscape

[ ] disable the create button
[ ] show tooltip “Currently disabled due to maintenance.”

RFM

[ ] disable the create classification button
[ ] disable the create new training job button
[ ] show tooltip “Currently disabled due to maintenance.”
If the training set isn't working, disable the add new training set with tooltip too.

Disable additional create buttons

[ ] PM
[ ] AED
[ ] Clustering


cleanup minikube docker image in non terminating test

What does this PR do?:
Removes the docker image being tested in the check_non_terminating.sh script after the container has been checked for termination.
This is needed because in the case where the list of images being tested is large (nightly runs or merging to main), the images are all downloaded to the Github runner and consumes all the disk space.
Removing the image after is has been marked as successful allows all the images to be tested in the same Github workflow run.
Which issue(s) this PR fixes:
fixes https://github.com/devfile/api/issues/1135
PR acceptance criteria:

[x] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[x] Test automation
Does this repository's tests pass with your changes?
[x] Documentation
Does any documentation need to be updated with your changes?
[x] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:
Tested on fork here: https://github.com/mike-hoang/registry/actions/runs/5334469263/jobs/9666282880
Diff from fork: https://github.com/mike-hoang/registry/commit/30784fea0a31dc16052b7cf053e7cae91ba4e643

/retest


Adds sample script to list empty folders in spo. Closes #2985

Adds sample script to list empty folders in spo. Closes #2985

The script only reports the empty folders. It does not report the empty files.
Based on the output returned by m365 spo folder list, the output is restricted to report FolderName, FolderPath, CreatedDate, ModifiedDate

Thank you @nanddeepn, we'll try to review it ASAP!

Manually merged. Thx


optionally allow output world name when importizing

Allow specifying output world name when importizing. This would allow multiple importized worlds to be merged.

Thanks!


Button for root users to invalidate the cache for an account

Core team members often have to make direct changes in the database (eg. to change some info about a contribution, create connected accounts, etc). A challenge that comes with this is the cache, we usually need to update Redis and Cloudflare which requires connecting to each service and manually invalidating each entry.
I'd like to be able to do something like this in my shell to clean all caches in one command:
heroku run scripts/clear-cache.ts COLLECTIVE_SLUG

Thinking about it more, this should rather be a root action in the frontend as it can be useful for other team members

yes to that last comment

Implemented in https://github.com/opencollective/opencollective-frontend/pull/6768


Postlight Reader | URLs broken

Expected Behavior
After I use the Postlight Reader Extension, I expect all links in the cleaned article to be functional.
Current Behavior
In the cleaned document (presented by the Postlight Reader extension), Links go from
/path (relative url)
to
chrome-extension://oknpjjbmpnndlpmnhmekjpocelpnlfdi/path.
Steps to Reproduce

Open a web page containing relative URL

Parse with Postlight Reader Extension
First link stops working, as the website domain changes to the chrome extension domain, all relative urls break

Possible Solution
While the article is being cleaned, retrieve the domain name and suffix all relative urls (href="/path") with the domain (href="domain.com/path").

Cool stuff, thank you :)

Yes, I have the same issue, relative url breaks in many other contexts too. Absolute url is needed.


Having trouble compiling using C++

According to the docs, it should be possible to compile duktape.c with a C++ compiler.  I want to do this so that exceptions generated by my callback functions can safely traverse the duktape code.  Maybe I'm doing something wrong, but I'm getting lots of errors trying to build 1.0.1 with g++.
The bulk of the problems have to do with how DUK_LOCAL_DECL causes data types to have extra definitions in the combined C code.  This is because code like the following is legal in C, but not C++:
static const char x[3];
static const char x[3] = { 'a', 'b', 'c' };

This trips up dozens of internal statics in duktape.c (duk__date_equivyear just to pick a representative example)  Should I be defining DUK_LOCAL differently when building under C++?
There was one other more straightforward error in duk__to_buffer_raw():
        dst_data = duk_push_buffer(ctx, src_size, buf_dynamic);

C++ requires an explicit cast there since duk_push_buffer() returns a void*
(See: #75, #55)

First version of this provided by #499.
In the initial implementation Duktape will use try-catch internally in place of setjmp/longjmp which allows automatic destructors in Duktape/C functions. You can also use C++ exceptions inside your Duktape/C functions but the initial implementation won't support propagating your own exceptions through Duktape (see a lot of discussion about the problems with this above). If you allow an exception to propagate into Duktape code, it will be caught using catch (...) and will be converted into a Duktape error (and won't therefore "come out of Duktape" at the other end).


Enable cpu/xpu support for the benchmarking suite

Enable Intel CPU and Intel XPU support for Benchmark Suite.
Many customers use deepspeed on CPU and XPU for LLM models, and this benchmark suite helps them to debugging communication issues on their environment.
an screenshot for two nodes run of all_reduce.py

@louie-tsai please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree [company="{Intel}"]

@louie-tsai the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree

and
@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree [company="{Intel}"]

@microsoft-github-policy-service agree [company="{Intel}"]

@louie-tsai the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree

and
@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree company="Intel"

@microsoft-github-policy-service agree company="Intel"

@microsoft-github-policy-service agree company=Intel

@louie-tsai, can you confirm if this PR is ready for review, I noticed that output (e.g., Gbps) is incorrect/missing.

@louie-tsai, can you confirm if this PR is ready for review, I noticed that output (e.g., Gbps) is incorrect/missing.

The output issue is related to the duration calculation from event.
if I used time.time to measure instead of XPU event.  it looks good.

I will escalate the XPU event issue and ask for a fix.


Cannot open multiple scratchpads at the same time

For those who want to troubleshoot on this: This apperently only applies for scratchpads with enabled animations.

Ping @K4rakara for any insight

Awestore shouldn't case this afaik, could it have to do with the scratchpads being on different tags? helpers.client.turn_on appears to do something with the tags.
Unsure why that would only occur for scratchpads with animations...

Perhaps if the subscriptions for the animation is applied after helpers.client.turn_on(c) it would work?
Since subscribing to a store (except signal stores like my_tweened.ended) will immediately run the subscriber function.


Promotion of the Toronto Tile from Yellow to Green is broken

When the Toronto Tile is upgraded to a Green Tile, it breaks due to the Tile not having a "Destination" City.
Added the functionality to add a Revenue Center as "Temporary" to a tile (when it is upgraded) when the new tile does not have one for the Destination by default. It will remove any Temporary Centers when the Tile is upgraded again (from Green to Brown, or Brown to Grey).
Need to confirm for tiles placed on empty map cells that any destinations are added.

Update when placing a new Tile on the Map (not upgrading) to add a Destination City onto the Tile.