Refresh timeout

In the section “Scheduled Refresh Timeout”, in the specific line “ If you encounter this limit, consider reducing the size or complexity of your dataset, or consider breaking the dataset into smaller pieces.”
Last line “Breaking the dataset into smaller pieces” doesn’t make sense and needs to be clarified.

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

ID: 7809469d-1c82-a875-3b77-83038a901f52
Version Independent ID: 5c41e498-26bb-eec4-444e-1c376a2fe87f
Content: Troubleshooting refresh scenarios - Power BI
Content Source: powerbi-docs/connect-data/refresh-troubleshooting-refresh-scenarios.md
Service: powerbi
Sub-service: pbi-data-sources
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @vtitte2020 -- thanks for asking! Assigning to the author to resolve.

Thank you for your input, I've reworded that sentence for clarity.


Make chromeOptions compatible with both JsonWire and W3C protocols

This workaround resolves issue which emerged after #560 .
Newer Selenium servers reject chromeOptions key in capabilities, because it does not contain vendor prefix, what is required as per W3C protocol. However simply updating the prefix would break on the other hand older Chromedrivers - and we want to maintain BC with version 1 of this library.
Ref. #652 #551 #573 #469

Thank


Error during control load

https://github.com/bipinshan/CustomNTONPCFMultiselectLookup/blob/5bf727d0ee87f99c7bd96e59268cf6421425b3be/NToNMultiSelect/index.ts#L177
This cant work, missing blank before the "and":
eq " + (<any>this.contextObj).page.entityId +"and

This is fixed now
Thanks for your feedback.

@bipinshan - is there a new solution version available with this fix?


[Jupyter Extension Feedback]

Whether to provide a new version of the adaptation update

OpenPAI provides the feature of custom reserved ports, which can solve this issue.
protocolVersion: 2
name: siaimes_f83daa2b
type: job
jobRetryCount: 0
prerequisites:
  - type: dockerimage
    uri: 'openpai/standard:python_3.6-pytorch_1.4.0-gpu'
    name: docker_image_0
taskRoles:
  taskrole:
    instances: 1
    completion:
      minFailedInstances: 1
    taskRetryCount: 0
    dockerImage: docker_image_0
    resourcePerInstance:
      gpu: 0
      cpu: 1
      memoryMB: 4096
      ports:
        Jupyter: 1
    commands:
      - pip install jupyterlab
      - >-
        jupyter-lab --ip <IP_ADDRESS> --port $PAI_PORT_LIST_taskrole_0_Jupyter --allow-root &
      - sleep 1d
defaults:
  virtualCluster: default
extras:
  com.microsoft.pai.runtimeplugin:
    - plugin: ssh
      parameters:
        jobssh: true
        userssh:
          type: custom
          value: ''
  hivedScheduler:
    taskRoles:
      taskrole:
        skuNum: 1
        skuType: cpu-machine

Use this configuration file to start a job, you will see the Jupyter port on the job page.

Then, use IP:Jupyter_port in the browser to access Jupyter. If it needs authentication, you can go to stdout or stderr to find the token.
Please note that with the above information, anyone can get your files through the browser.
One way to prevent others from getting the token is to log in to the container and run this command after the job starts:
jupyter-lab --ip <IP_ADDRESS> --port $PAI_PORT_LIST_taskrole_0_Jupyter --allow-root &


stripnl=false is ignored

The minted-option stripnl=false prevents newlines at the end of code snippets to be stripped. I rely on this heavily to align snippets that are shown side-by-side and should have certain lines appear on the same height.
shiki-latex seems to ignore this option and always strips trailing blank lines.

mathescape=true and texcomments are also not handled, yet. I guess the second one is a superset of the first, so I would maybe not need the first one if the second one were available...

I fixed stripnl in 1.1.6 and opened #8 to address mathescape, texcomments, and so forth. As it turns out, minted is calling the syntax highlighter with command-line options that we can pick up and do something about (unlike theme selection, which it’s hiding under LaTeX wizardry).

@h-2: I added support for math escape in 1.2.0. More options to come…


Getting error when making all

Sorry how I can solve this error
make: *** [src/svprops] Error 1
(/home/fi1d18/.conda/onco) [fi1d18@cyan01 svprops]$ make all
g++ -isystem /home/fi1d18/svprops/svprops/src/htslib/ -pedantic -W -Wall -Wno-unknown-pragmas -fno-strict-aliasing -O3 -fno-tree-vectorize -DNDEBUG -D__STDC_LIMIT_MACROS src/svprops.cpp -o src/svprops -L/home/fi1d18/svprops/svprops/src/htslib/ -L/home/fi1d18/svprops/svprops/src/htslib//lib -lhts -lz -llzma -lbz2 -Wl,-rpath,/home/fi1d18/svprops/svprops/src/htslib/
/usr/bin/ld: cannot find -llzma
collect2: ld returned 1 exit status
make: *** [src/svprops] Error 1
(/home/fi1d18/.conda/onco) [fi1d18@cyan01 svprops]$

You need a couple system libraries for svprops such as lzma and boost. If you are using Ubuntu you can install these using:
apt-get install -y build-essential g++ cmake zlib1g-dev libbz2-dev liblzma-dev libboost-all-dev

Sorry I am getting this

(/home/fi1d18/.conda/onco) [fi1d18@cyan01 svprops]$ apt-get install -y build-essential g++ cmake zlib1g-dev libbz2-dev liblzma-dev libboost-all-dev
-bash: apt-get: command not found
(/home/fi1d18/.conda/onco) [fi1d18@cyan01 svprops]$

You need to be root/administrator to install these libraries. Please ask your IT service people.

Thank you
Before asking root to install for me, would I get information like read depth for each sample in the position by delly .vcf files?

The RC genotype field contains the read count for each called SV

But you don't need svprops for that, this is already in the Delly BCF output.

Sorry, before asking admins to install things, does this tool extract information like read depth delly .vcf file?
Thank you for bearing with me

Thank you for bearing with me
I need these columns from called SV
> head(sv_data)
     Sample Type CHROM_1    POS_1 CHROM_2     POS_2 Tumor_Varcount Tumor_Depth Normal_Depth 1   CHC018T  BND    chr1   753734    chr8    327403             22          52          101   <NA>
2   CHC018T  BND    chr1   753747    chr8    327385             17          37          104   <NA>
>

I don't know this format. It's not from delly.

Hello @beginner984 , GitHub issues are not the place to ask for help with the usage. GitHub issues are for problems in the tool's code or issues with the expected behavior. You have already opened multiple posts on Biostars and Bioinfo SE for this exact question, I'd recommend against spamming tool developers on GitHub.


DataStore fails to sync data

Describe the bug
Datastore is falling to sync data from the cloud with decoding errors.
Steps To Reproduce
1. Set up a clean project with the following auth:
   2.1. Cognito as the primary auth and API Key as the secondary.
   2.1. Select to auto merge and resolve conflicts.
2. Complete setup and push
2. Ensure the cloud tables have data items.
3. Start the application.

Expected behavior
To pull and populate local datastore tables with data from the cloud.
Amplify Framework Version
1.17.0
Amplify Categories
API, Auth, DataStore
Dependency manager
Swift PM
Swift version
5.3.2
CLI version
7.6.3
Xcode version
12.4 (12D4e)
Relevant log output
2021-12-15 11:21:50.980256+0000 <APP_NAME>[39863:155273] [RetryableGraphQLSubscriptionOperation<MutationSync<AnyModel>>] APIError: Subscription item event failed with error
Caused by:
jsonParse(nil, Optional(Swift.DecodingError.dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "type", intValue: nil)], debugDescription: "Cannot initialize RealtimeConnectionProviderResponseType from invalid String value connection_error", underlyingError: nil))))

Is this a regression?
No
Regression additional context
No response
Device
iPhone 12 Pro Simulator
iOS Version
iOS 14.4
Specific to simulators
No response
Additional context
Application Log
ApplicationConsolLog.log
schema.graphql
schema.txt
Plugin Configuration within AppDelegate
public var syncDate: Temporal.DateTime? = Temporal.DateTime.init(Date())
`do {
try Amplify.add(plugin: AWSCognitoAuthPlugin())
        let apiPlugin: AWSAPIPlugin = AWSAPIPlugin(modelRegistration: AmplifyModels())
        try Amplify.add(plugin: apiPlugin)

        var syncExpressions: [DataStoreSyncExpression] = []

        //sync two weeks worth of data
        let calendar: Calendar = .iso8601
        let date: Date = calendar.date(byAdding: .day, value: -14, to: Date().startOfWeek())!
        syncDate = Temporal.DateTime.init(date)
        let mealPlanSyncExpr: DataStoreSyncExpression = DataStoreSyncExpression.syncExpression(MealPlan.schema) {
            guard let syncDate = syncDate else {
                return QueryPredicateConstant.all
            }
            return MealPlan.keys.startDateTime.ge(syncDate)
        }
        syncExpressions.append(mealPlanSyncExpr)

        let userProfileSyncExpr: DataStoreSyncExpression = DataStoreSyncExpression.syncExpression(UserProfile.schema) {
            return QueryPredicateConstant.all
        }
        syncExpressions.append(userProfileSyncExpr)

        let datastoreConfiguration: DataStoreConfiguration = DataStoreConfiguration.custom(syncExpressions: syncExpressions, authModeStrategy: .multiAuth)
        let dataStorePlugin: AWSDataStorePlugin = AWSDataStorePlugin(modelRegistration: AmplifyModels(),
                                                 configuration: datastoreConfiguration)

        try Amplify.add(plugin: dataStorePlugin)

        try Amplify.configure()
        logger?.log(type: .debug, category: .app, message: "Initialized Amplify")

    } catch {
        logger?.log(type: .error, category: .app, message: "Failed to initialize Amplify with \(error)")
    }`

Hello,
As a first step, could you please check if API key for your GraphQL API is expired [usually expires within 7 days] or Auth mode is correctly set by checking in the AppSync console? [Go to AppSync Console -> Your API -> Settings]

If not, can you try creating a new key and updating your amplifyconfiguration.json file with the new key?

@thisisabhash Thank you for your response. Unfortunately, this has not worked. In fact, during project initialisation, I did initially set the API to expire in 7 days but then ran API update and changed this to 365.

@skontou what's the output of amplify status in your project directory?

@diegocstn the output indicates all is synced:
Current Environment: dev
| Category  | Resource name  |  Operation | Provider plugin  |
| Auth  | diobeatit****  | No Change  | awscloudformation  |
| Api  |  diobeatit | No Change  | awscloudformation  |
GraphQL endpoint: *********
GraphQL API KEY: *********

@skontou are you able to verify in the AWS console that your API key is still valid?

@diegocstn following @thisisabhash suggestion I generated a new API key to verify

Not sure if this helps but I just removed the project and started from the beginning after running amplify configure and add api. Migrated my schema to use the latest syntax and structure I then ran code gen and push and I noticed the following error:
✔ Generated GraphQL operations successfully and saved at graphql Code generation failed with the following error  ENOENT: no such file or directory, lstat '<PROJECT_FILE_LOCATION>/amplify/#current-cloud-backend/auth/***465c8f7a'. ✔ All resources are updated in the cloud
Xcode build produces the following error (This might be resolved if I upgrade my machine, not ideal but worth a try):
/Users//Library/Developer/Xcode/DerivedData/<PROJECT_BUILD>/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

Not sure if this helps but I just removed the project and started from the beginning after running amplify configure and add api. Migrated my schema to use the latest syntax and structure I then ran code gen and push and I noticed the following error:
✔ Generated GraphQL operations successfully and saved at graphql Code generation failed with the following error ENOENT: no such file or directory, lstat '<PROJECT_FILE_LOCATION>/amplify/#current-cloud-backend/auth/***465c8f7a'. ✔ All resources are updated in the cloud
Xcode build produces the following error (This might be resolved if I upgrade my OS, not ideal but worth a try):
/Users/<USER>/Library/Developer/Xcode/DerivedData/<PROJECT_BUILD>/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

same issue need help

Small Update. Out of curiosity I thought to download the awsconfiguration.json file from the app sync console and realised that my API Key name did not match. Unfortunately I am unable to test if this will resolve my issue due the compilation errors
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/Build/Products/Debug-iphonesimulator/AWSMobileClientXCF.framework/Modules/AWSMobileClientXCF.swiftmodule/x86_64-apple-ios-simulator.swiftinterface:8:8: No such module '_Concurrency'
and
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

Small Update. Out of curiosity I thought to download the awsconfiguration.json file from the app sync console and realised that my API Key name did not match. Unfortunately I am unable to test if this will resolve my issue due the compilation errors
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/Build/Products/Debug-iphonesimulator/AWSMobileClientXCF.framework/Modules/AWSMobileClientXCF.swiftmodule/x86_64-apple-ios-simulator.swiftinterface:8:8: No such module '_Concurrency'
and
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

Small Update. Out of curiosity, I thought to download the awsconfiguration.json file from the app sync console and realised that my API Key name did not match. Unfortunately, I am unable to test if this will resolve my issue due the compilation errors
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/Build/Products/Debug-iphonesimulator/AWSMobileClientXCF.framework/Modules/AWSMobileClientXCF.swiftmodule/x86_64-apple-ios-simulator.swiftinterface:8:8: No such module '_Concurrency'
and Existing open issue - aws-amplify/aws-sdk-ios#3795 /Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

try to use Xcode 13

Small Update. Out of curiosity, I thought to download the awsconfiguration.json file from the app sync console and realised that my API Key name did not match. Unfortunately, I am unable to test if this will resolve my issue due the compilation errors
/Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/Build/Products/Debug-iphonesimulator/AWSMobileClientXCF.framework/Modules/AWSMobileClientXCF.swiftmodule/x86_64-apple-ios-simulator.swiftinterface:8:8: No such module '_Concurrency'
and Existing open issue - aws-amplify/aws-sdk-ios#3795 /Users/<USER_DIR>/Library/Developer/Xcode/DerivedData/<APP_NAME>-fkchuwvzgbhvchfkfrwkeviqnbqn/SourcePackages/checkouts/amplify-ios/AmplifyPlugins/Auth/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift:15:8: Failed to build module 'AWSMobileClientXCF' from its module interface; the compiler that produced it, 'Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'

try with Xcode 13,  hope your Xcode version 12.x.x

@sachithamh thank you for your response unfortunately this is not an option as I am unable to update my OS to the latest version in order to download and in XCode 13 due to other obligations. Also, going by the documentation XCode 11 is the minimum requirement https://docs.amplify.aws/lib/project-setup/prereq/q/platform/ios/

yes, correct @skontou  but that's how it works for me :(  let's wait for good answer

UPDATE:

I have since upgraded my OS to macOS Monterey 12.1 (21C52) to solve the compilation issues.
I have corrected the relationships in my schema to resolve codegen compilation issues
schema.txt
Unfortunately, the same issue still exists with the same errors in the log

@skontou would you mind share your amplifyconfiguration.json redacted of any sensitive data?
Also, was any user signed in when you experienced the issue?

Closing due to inactivity, feel free to reopen if you still need help.


Standardize event data for deposit data

Read our Contributor Guidelines and README.
Parse data from event which fetched on-chain to humman-readable format, for example, now we have user = data[0] and we want to have user = data.user

In method parse_deposit_event
Event data structure - event data

Create Serializers model using pydantic in serializers.py
In method process_deposit_event
substitute fetching data by index Example: user= data[0] to data.user using serializer class

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Software engineering background, python developer, smart contract developer
How I plan on tackling this issue
Using the structure of the event data, make it accessed using dot notation (e.g., data.user).
Define a Pydantic model that reflects the structure of the event data, including attributes like user, amount, etc.
substitute fetching data by index as stated. Work on any feedback & recommendations.
I like oranges

@Josh-121 Feel free to apply to this issue, once you finish your current task, don't forget that you have 24 hours to open our draft PR

@djeck1432 can i work on this ?

hello @djeck1432 i would like to work on this issue :)

Hi @djeck1432 , can I work on this?

Hi @djeck1432 , can I be assigned this?
I like oranges

@Josh-121 Feel free to apply to this issue, once you finish your current task, don't forget that you have 24 hours to open our draft PR
Done ser

@Immanuelolivia1 You didn't create draft PR, during 48 hours, you will be unassigned from this issue.

Hi @djeck1432 , please can I be assigned this?
'I would like to take this task, I love 🍍

Can i be assigned to this issue. I am ready to start working on it. ETA 48hrs


Cilium negative policies

Proposal / RFE
Is your feature request related to a problem?
Describe the solution you'd like
It would be great if it's possible to write a CiliumClusterwideNetworkPolicy that will be applied to all namespaces with the exception of the kube-system and / or default namespace (negative policy). This ensures that a default CiliumClusterwideNetworkPolicy policy will be applied automatically to each new namespace that is created. For example, this can be a policy that only allows egress traffic to kube-system namespace/endpoints.
Calico has developed something called a negative policy: namespaceSelector: has(projectcalico.org/name) && projectcalico.org/name not in {"kube-system", "calico-system", "default"}
Link: https://docs.projectcalico.org/security/kubernetes-default-deny

You can achieve that with something similar as this policy:
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: "rule"
spec:
  endpointSelector:
    matchExpressions:
    - key: io.kubernetes.pod.namespace
      operator: "NotIn"
      values:
        - "kube-system"
        - "default"
  egress:
  - toEndpoints:
    - matchExpressions:
      - key: io.kubernetes.pod.namespace
        operator: "In"
        values:
          - "kube-system"

Awesome, thanks!


Include interface for kind 0 metadata

Profile metadata of kind 0 has a serialized JSON in content, I am suggesting include this interface, which despite being expandable, contains widely used common fields, maybe something like:
export interface ProfileRawMetadata {
    name?: string;
    display_name?: string;
    picture?: string;
    about?: string;
    banner?: string;
    lud16?: string;
    website?: string;
    nip05?: Nip05;

    [customizedField: string]: any;
}

Why don't you just use nostrify.dev? We already have this, and a parser for it: https://nostrify.dev/schema/#kind-0-metadata

nostrify uses nostr-tools as dependecy, why don't put this interface as a core for whole typescript stuff and import it in nostrify from nostr-tools? Just a suggestion

Oh really? I didn't know Nostrify had these. Indeed I think it's better to have these things at a higher level. nostr-tools is already too huge, I should probably remove some stuff because I must know this codebase in order to keep it working and if it gets too big I won't. This has already happened with v1 which had grown so much I couldn't use it myself anymore because it was so confusing, then I was forced to destroy it completely and release v2.

I've added 1b77d6e0805b295cf6bf0f88de2e51c06116c0b8 to the README.

nice


MAINT: optimize: cleanup of TNC code

The first commit is just reindentation and adding missing braces. The rest are:

removal of a static variable in favor of a C standard macro
addition of missing const (not everywhere)
remove unused version printing code, since this is no longer TNC 1.3.

@larsmans, you're not supposed to merge your own PR so quickly without notice. Your work is very appreciated but it has to go through the review process (see doc/MAINTAINERS.rst.txt). Besides the diffstat is quite significant here...

I went through this and it all look good, but @dlax is right. Better to first comment "this is a trivial cleanup and I plan to merge it in two days unless someone stops me". Then people have a chance to look at it.

Sorry. I considered these changes trivial, but I get the point about the diff being big. Won't happen again.


Simplify initialize2DArray

Simplify initialize2DArray [ENHANCEMENT]
No need to use Array.prototype.map and Array.prototype.fill because of native Array.prototype.from callback
What does your PR belong to?

[ ] Website
[X] Snippets
[ ] General / Things regarding the repository (like CI Integration)
[ ] Tests

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (non-breaking improvement of a snippet)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have checked that the changes are working properly
[X] I have checked that there isn't any PR doing the same
[X] I have read the CONTRIBUTING document.

I think tagging as on hold is hepful. Fill is very esoteric, and Array.from is just as esoteric. I have used it once, and that was before NodeList iterators were attached to the type, which I usually just get around by calling or apply the Array Prototype to them.
I think updating to the newer code is helpful, but if we do we should document it a bit more in the snippet markdown, which may make the snippet explanation a bit long. Maybe instead we just include a link to the MDN article for it because once you learn it it's really self explanitory

I really think the new code is a bit hard to understand and requires more effort to figure out if you do not know about the from callbacks. map and fill are a lot more self-explanatory, as you see map creating the arrays and fill filling them like we do for 1D arrays. For consistency's sake and to make things easier to understand, I think we should stay on map and fill.
We could link to an alternate version with fill... Which raises an issue here: could we implement a system that allows for alternate or previously used implementations of snippets to be listed in the website? That sounds like an interesting feature and something that can be useful if you want to learn JS in depth or not have all the features available to you right away.

Addressing using Fill and Map:
It adds a syntactical way to explain how it's working on each element which greatly increases readability. however between map and fill, we're REALLY hitting the performance hard. This could probably be done much better by ForEach to address the performance(in testing, when I got to 2D Arrays of size 1000 x 1000 I started noticing a performance difference that only got more pronounced as the arrays got bigger: https://jsperf.com/foreach-fill-versus-map
While it may not look like it here, there is a significant difference in the time taken. However anyone using Arrays that large.... needs to step back and analyze why. At that point Map creating a secondary Array is of little concern.
The compared ForEach version
const initialize2DArray = (w, h, val = null) =>
  Array.from({ length: h })
  .forEach((_, index, array) =>
    array[index] = Array.from({ length: w }).fill(val)
  );

The proposed version:
While more streamlined it reads as "experienced only" which is a big strike to it due to the auto magic applied to an overloaded function. It just doesn't read syntacically the more I read it, and after having taken some time and coming back I found myself looking up the Array.from documentation again... Which is a bad sign.

forEach and map are virtually identical in the perf you posted, @skatcat31. At least they are for me. I'm not against the forEach modification, but from's callbacks are quite hard to understand. After asking a few colleagues, they all sort of agreed that from's callback magic is a bit weird and that they rarely ever use it, due to not remembering that it exists or that it works that way. So, we should most likely be looking for alternatives other than that.

Then we should leave it as map since it has the most concise syntax and is semantically easy to understand


Broken TCP connection and endless waiting for events from the dark

Found a bug which occurres when the connection is broken: the worker waits until the data is sent from the socket. This is my fault. I have no idea how to solve this problem without losing the data that was not sent before closing the socket.
A possible hotfix would be to set a constant timeout to wait for the socket write buffer to clear.

I implemented a timeout, configurable via constants and with a default of 30 seconds.
@nazarkhanov
Do you think 30 seconds are a reasonable default?
Could you maybe test the changes?
I tried to reproduce this by rate-limiting outgoing packets to Logstash via iptables. This seemed to work but is a rather artificial case.


Near method returns no values for negative center coordinates.

Operating System version: macOS
Firebase library: "firebase-admin": "^8.10.0",
GeoFirestore version: 4.1.0, previously 4.0.1

Hi, I've been having issues with fetching data with negative coordinates ( South, West ) set for center parameter.
It works just fine, when center has positive longitude and latitude values.
Down below there is a code snippet of how data are being saved in firestore, and also how near query is implemented.
functions.firestore
    .document(`${CollectionNames.restaurants}/{restaurantId}`)
    .onUpdate(async (change, context) => {
        const newValue = change.after.data();
        const id = context.params['restaurantId'];

        const geoFirestore = new GeoFirestore(firestore());
        const documentReference = geoFirestore
            .collection(CollectionNames.restaurants)
            .doc(id);
        const document = newValue;

        document['coordinates'] = new firestore.GeoPoint(newValue.latitude, newValue.longitude);

        return documentReference.set(document);
    });

This code updates documents correctly and results in geofirestore related fields being added:

Anyway, when longitude and latitude are positive, there are no issues whatsoever.
However, code below returns no results when lat or long or both are negative.
Also, if one or both restaurant coordinates is negative, these documents are not returned even if radius is set to extra large number (<PHONE_NUMBER>0000000000 etc. ).
import { GeoFirestore } from 'geofirestore';
import {firestore} from "firebase-admin";

const geoFirestore = new GeoFirestore(firestore());

const geoCollection = geoFirestore.collection(CollectionNames.restaurants);

    const geoLocationSnapshot = await geoCollection
        .near({
            center: new firestore.GeoPoint(lat, long),
            radius,
        })
        .get();

So I'm partially able to recreate this issue, and partially unable...
Here is a StackBlitz where I have coordinates of [1, 1], [1, -1], [-1, -1], [-1, 1] (4 quadrants on a plane) and I'm able to query from [0, 0] and get all 4 of them (as well as a few others I did). Pretty much geohashes fall apart with a radius greater than 8587 KM.
Keep in mind geohashes aren't a perfect fix for the lack of proper geoqueries in Firestore. I think I need to know what the center and radius are for your query, as well as what geopoints that you'd expect to have returned.

For reference this distance between San Francisco to London is 8611 KM, just outside of the range supported. Mind you, that's a massive space. I give that as a reference as to how much space can be covered by 8587 KM.


An unhandled exception occurred: Cannot read property 'add' of undefined See "C:\Users\AH55278\AppData\Local\Temp\ng-K2A4IA\angular-errors.log" for further details.

Below are the versions I am using in my project
Angular CLI: 12.1.3
Node: 12.18.1
Package Manager: npm 6.14.5
OS: win32 x64
"dependencies": {
"@angular/animations": "~11.1.0",
"@angular/cdk": "^11.1.0",
"@angular/common": "~11.1.0",
"@angular/compiler": "~11.1.0",
"@angular/core": "~11.1.0",
"@angular/forms": "~11.1.0",
"@angular/material": "^11.1.0",
"@angular/material-moment-adapter": "^11.1.1",
"@angular/platform-browser": "~11.1.0",
"@angular/platform-browser-dynamic": "~11.1.0",
"@angular/router": "~11.1.0",
"@datadog/browser-rum": "^4.44.2",
"@fullcalendar/angular": "^5.6.0",
"@fullcalendar/daygrid": "^5.6.0",
"@fullcalendar/interaction": "^5.6.0",
"@fullcalendar/resource-timeline": "^5.6.0",
"@fullcalendar/timegrid": "~5.6.0",
"@glidejs/glide": "^3.4.1",
"@material-extended/mde": "^3.0.3",
"@ng-bootstrap/ng-bootstrap": "^5.3.0",
"@ngrx/component-store": "^11.1.1",
"@ngrx/data": "^11.1.1",
"@ngrx/effects": "^11.1.1",
"@ngrx/entity": "^11.1.1",
"@ngrx/router-store": "^11.1.1",
"@ngrx/store": "^11.1.1",
"@ngrx/store-devtools": "^11.1.1",
"@types/snapsvg": "^0.5.0",
"@webcomponents/custom-elements": "^1.4.3",
"@webcomponents/shadydom": "^1.6.1",
"@webcomponents/webcomponentsjs": "^2.5.0",
"bootstrap": "^4.6.0",
"classlist.js": "^1.1.20150312",
"core-js": "^2.5.0",
"d3": "^7.0.0",
"d3-zoom": "^3.0.0",
"es6-promise": "^4.2.8",
"isomorphic-fetch": "^3.0.0",
"line-awesome": "^1.3.0",
"mat-timepicker": "^5.1.0",
"material-icons-font": "^2.1.0",
"moment": "^2.29.4",
"moment-range": "^4.0.2",
"moment-timezone": "^0.5.33",
"ng-circle-progress": "^1.6.0",
"ng2-search-filter": "^0.5.1",
"ngx-image-cropper": "^5.0.1",
"ngx-infinite-scroll": "^10.0.1",
"ngx-pagination": "^5.1.1",
"ngx-pipes": "^3.0.0",
"ngx-toastr": "^13.2.1",
"primeicons": "^4.1.0",
"primeng": "^11.2.0",
"ramda": "^0.27.2",
"rxjs": "^6.6.3",
"snap.svg.zpd": "^0.0.12",
"snapsvg": "^0.5.1",
"tslib": "^2.0.0",
"web-animations-js": "^2.3.2",
"whatwg-fetch": "^3.6.2",
"zone.js": "~0.11.3"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.1101.1",
"@angular/cli": "~11.1.1",
"@angular/compiler-cli": "~11.1.0",
"@angular/localize": "^11.1.2",
"@types/d3": "^6.7.5",
"@types/jasmine": "~3.6.0",
"@types/node": "^12.11.1",
"@types/ramda": "github:types/npm-ramda#dist",
"codelyzer": "^6.0.0",
"dotenv": "^10.0.0",
"jasmine-core": "~3.6.0",
"jasmine-spec-reporter": "~5.0.0",
"karma": "~5.2.0",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage": "~2.0.3",
"karma-jasmine": "~4.0.0",
"karma-jasmine-html-reporter": "^1.5.0",
"mv": "^2.1.1",
"protractor": "~7.0.0",
"replace-in-file": "^6.2.0",
"ts-node": "~8.3.0",
"tslint": "~6.1.0",
"typescript": "~4.1.2"
}

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Add support for Erlang

I created a simple plugin to highlight Erlang code

Changes:
1) Attached lang-erlang.js (src/lang-erlang.js)
-- All following contained in diff.txt)
2) Update changelog for you (CHANGES.html)
3) Update documentation to include a link to where lang-erlang.js will reside
post commit (README.html)
4) Update tests so that there is a test case for Erlang
(tests/prettify_test.html)

This applies cleanly against HEAD in my repo

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 28 Aug 2011 at 12:08
Attachments:

lang-erlang.js
diff.txt

committed in 62d129a3


Https scheme fix, merging #12790

Summary of the Pull Request
Merging for #12790
What is this about:
In Powertoy Run some schemes were incorrectly being overwritten with HTTPS. This change fixes this.
What is include in the PR:
Should only be changes to 2 files
How does someone test / validate:
Execute Powertoy Run, type<EMAIL_ADDRESS>you should see the correct scheme (mailto) in the drop down.
Quality Checklist

[x] Linked issue: #12764
[ ] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[x] Installer: Added/updated and all pass
[x] Localization: All end user facing strings can be localized
[x] Docs: Added/ updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

cc: @chrisharris333, @jaimecbernardo


Build failure: Jellyfin 10.10.0 & Jellyfin-ffmeg 7.0.2-5

Steps To Reproduce
Steps to reproduce the behavior:

Be on NixOS 24.11pre698755.807e9154dcb1 (Vicuna) x86_64
Have Jellyfin & Jellyfin-ffmeg installed already
run sudo nixos-rebuild switch OR sudo nixos-rebuild switch --upgrade

Build log
error: builder for '/nix/store/n9vd6qaiyzkyc8jf09ikr07k3vm9wxs2-jellyfin-ffmpeg-7.0.2-5.drv' failed with exit code 2
error: 1 dependencies of derivation '/nix/store/s13zkd4ln6pppk3za5hvl7iq47zk77pq-jellyfin-10.10.0.drv' failed to build

Notify maintainers
Jellyfin
@nyanloutre
@minijackson
@purcell
@jojosch
Jellyfin-FFMPEG
@justinas

Last person to commit to both
@dotlambda
Metadata

system: "x86_64-linux"
host os: Linux 6.11.5, NixOS, 24.11 (Vicuna), 24.11pre698755.807e9154dcb1
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.9
channels(root): "nixos"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Add a :+1: reaction to issues you find important.

Without additional logs it's hard to be definitive, but I think your issue should be fixed since this PR : https://github.com/NixOS/nixpkgs/pull/353198

Without additional logs it's hard to be definitive, but I think your issue should be fixed since this PR : #353198

i did give a honest try to do a pastebin but they claim im posting "potentially offensive or questionable content" so it failed

https://gist.github.com/WesfunOfficial/2c0fc1f77581798ec6caffb57782bb4c

I'm seeing this same failure as the gist
error: builder for '/nix/store/n9vd6qaiyzkyc8jf09ikr07k3vm9wxs2-jellyfin-ffmpeg-7.0.2-5.drv' failed with exit code 2;
       last 25 log lines:
       > CC     libavcodec/libxevd.o
       > CC        libavcodec/libxeve.o
       > CC        libavcodec/libxvid.o
       > CC        libavcodec/libzvbi-teletextdec.o
       > CC    libavcodec/ljpegenc.o
       > CC       libavcodec/loco.o
       > CC   libavcodec/lossless_audiodsp.o
       > CC      libavcodec/lossless_videodsp.o
       > CC      libavcodec/lossless_videoencdsp.o
       > CC   libavcodec/lpc.o
       > CC    libavcodec/lscrdec.o
       > CC        libavcodec/lsp.o
       > CC    libavcodec/lzf.o
       > CC    libavcodec/lzw.o
       > CC    libavcodec/lzwenc.o
       > libavcodec/libxeve.c: In function 'get_conf':
       > libavcodec/libxeve.c:199:27: error: incompatible types when assigning to type 'XEVE_RATIONAL' {aka 'struct _XEVE_RATIONAL'} from type 'long int'
       >   199 |         cdsc->param.fps = lrintf(av_q2d(avctx->framerate));
       >       |                           ^~~~~~
       > libavcodec/libxeve.c: In function 'libxeve_encode':
       > libavcodec/libxeve.c:484:40: error: incompatible types when assigning to type 'int' from type 'XEVE_RATIONAL' {aka 'struct _XEVE_RATIONAL'}
       >   484 |                 avpkt->time_base.den = xectx->cdsc.param.fps;
       >       |                                        ^~~~~
       > make: *** [ffbuild/common.mak:82: libavcodec/libxeve.o] Error 1
       > make: *** Waiting for unfinished jobs....
       For full logs, run 'nix log /nix/store/n9vd6qaiyzkyc8jf09ikr07k3vm9wxs2-jellyfin-ffmpeg-7.0.2-5.drv'.

Stop spamming this issue. If you read the comments you'd now this has been fixed on master.

I’ll admit I missed the linked PR when first reading the issue. My additional comment was far from spam.


npm run start doesn't work on chialisp state tutorial

there's no setup of npm run start command so it doesn't work
please fix docs
https://docs.chia.net/guides/crash-course/state/

Thanks, I added an instruction to install NPM:
https://github.com/Chia-Network/chia-docs/pull/459


Fix AttributeError in two_layer_net_autograd.py

The line w1.grad.data.zero_() (previously line 55, now line 56) raised an "AttributeError: 'NoneType' object has no attribute 'data'".
Indeed w1.grad and w2.grad were None at the first loop iteration. Fixed with the if at line 55.

It is better to do it after the weight updates:
    w1.data -= learning_rate * w1.grad.data
    w2.data -= learning_rate * w2.grad.data
    w1.grad.data.zero_()
    w2.grad.data.zero_()

Fixed in https://github.com/jcjohnson/pytorch-examples/commit/0d8adca7c5ef427c738fe3a484edc76ab6ddc105.


Release 1.2.5

@rultor release it; the tag is 1.2.5.

@rultor release it; the tag is 1.2.5.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it; the tag is 1.2.5.

@rafamizes Done! FYI, the full log is here (took me 1min)


Use model instead of attributes to store Notification options

Extended model
Copy values with help of DB changelog
Remove notification only if everything is false and attributes is empty.
Merge all types of notifications with actual user notifications on server side.

Also tested on MSSQL, works fine.

Have you tested the upgrade script?

Yes, I have tested it on MySQL and MS SQL.

Removed attributes checks and extra spaces.

Merged, thanks.


old b-pagination-nav is missing

Is there any roadmap for b-pagination-nav component? Is it "discarded" or simply not yet implemented?

simply not yet implemented?

This


webpack how to ignore folder for watch

Bug report
I also posted the question on stackoverflow, but with no luck for answers. I'd really appreciate if you don't close it and take a look at this.
What is the current behavior?
Somewhere in my app, I have a function which uses dynamic require.
export default function(path, urlKey = 'static') {

    if (urlKey === 'static') {
        path = require(`~/static${path}`).default;
    }

    urlKey = Object.keys(config.app.urls).includes(urlKey) ? urlKey : 'static';

    return (config.app.urls[urlKey] + '/' + path).replace(/([^:]\/)\/+/g, "$1");

};

As you can see, I am using dynamic require . It's something like require.context. What happens is, while webpack bundling it, it builds all the files in the static folder. As you can see I have ~ which is an alias for the root directory in which i have a static folder.
Now, when using watch mode of webpack, what happens is it never stops building, when it builds the project, it starts it again and again as a loop. Unfortunatelly, I couldn't ignore static folder at all by using watchOptions.ignored or WatchIgnorePlugin.
Here is what I tried:
watchOptions: {
  ignored: /static/
}

And also
plugins:[
        new WatchIgnorePlugin([
            path.resolve(__dirname, '..', 'static')
        ]),
    ]

but with no luck. It still rebuilds infinitely when in watch mode.
The way this starts working(I mean it doesn't compile over and over again is) is by changing require statement
from : path = require(~/static${path}).default;
to : path = require(~/static/${path}).default; (look at one slash addition before ${path})
This solves it, but in my whole app, I use this function in too many places where I pass path that start with / so, I had to also change it to path = require(~/static/${path.substring(1)}).default;
What is the expected behavior?
It  shouldn't rebuild the project infinitelly.
Other relevant information:
webpack version:  4.41.5
Node.js version:  12.14.1
Operating System:  MacOS
Additional tools:

Please use stackoverflow or gitter for questions, it is bug tracker, thanks


Register remote image as a package.

This is a wrapper around manually having to download the image and
registering it. It registers an image based on it's URL, it will
download that image and add it to the PDF. It will however not add it
immediately to the page. This is done by calling Image() with the same
URL.
As discussed in https://github.com/jung-kurt/gofpdf/pull/35, this contains the changes within a single commit.

@stanim

(I propose here also to use fhttp instead of httpfpdf to keep it shorter. So the pattern for contributed packages could be fxxx.)

I agree that we should not include fpdf in the contributed project names. However, do we need the f? I think project names would be cleaner without it.
@jelmersnoeck

(I'm not entirely sure what to do with the common functions in gofpdf_test and httpfpdf_test though)

Let's keep them there for now. When we are satisfied that enough people are using go 1.4 and over, we can use the internal package scheme to factor them into their own internal package.

@jelmersnoeck
Thanks for your nice work and patience.
@jung-kurt
What name would you suggest for this package? I wouldn't use "http" or "image" as that conflicts with the standard library. Using a fprefix has just the advantage to have a clear naming system: f+(name of the main package).
I propose we call the function RegisterHttpImage. (Later maybe somebody adds RegisterFtpImage. RegisterRemoteImage is too general.)

Let's keep them there for now. When we are satisfied that enough people are using go 1.4 and over, we can use the internal package scheme to factor them into their own internal package.

You can create a package called internal in older version, it just won't enforce the rules. I vote to move the common test functions now, since contributors are starting to use contrib.

Using internal for common test functions seems a good strategy to me.
@marcusatbang
Please use the new GetImageInfo method to check if the image is already registered to prevent downloading the same file multiple times.
@jung-kurt
I would propose to change this:
func (f *Fpdf) GetImageInfo(imageStr string) (info ImageInfoType, ok bool)

into this:
func (f *Fpdf) GetImageInfo(imageStr string) (info *ImageInfoType)

which returns nil if the image is not registered yet. I find this more idiomatic.

@stanim
Returning a pointer, possibly nil, is fine in this case. In cases in which structure fields are exported, for example to work with reflection or encoding packages, I prefer returning the structure itself so external packages can not modify internals. I'll make your proposed change.

@jung-kurt
I agree, but RegisterImage already returned that pointer:
func (f *Fpdf) RegisterImage(fileStr, tp string) (info *ImageInfoType)

so it makes it more easy for contributed RegisterImage functions to do the same.

@stanim Good point. Done

@stanim I've updated it to use the GetImageInfo function. I've also renamed it to RegisterHttpImage.
@jung-kurt do you want to keep it fhttp or would you prefer a different name?

@jelmersnoeck Nice work. Regarding the name, I think something like httpimg or webimg would be descriptive since the helper routine involves both. Then I think you could reduce stutter by calling the principal method webimg.Register() rather than webimg.RegisterHttpImage(). However, I will await comments by @stanim since he catches a lot of stuff that I miss.

I was actually just wondering the same. With the example @stanim gave, it would maybe belong in a ftpimg package (and this one in - as you mentioned - a httpimg). Both would then just have a Register() function.

httpimg.Register() would be my preference. Later there can be ftpimg or maybe even httpfont.

@stanim Good -- let's proceed with that.

Cool, I'll refactor this tonight and squash it all into 1 commit.

@jung-kurt @stanim I've renamed the package to httpimg and updated the function to Register(). If you're happy with this I'll squash it into one commit.

@jelmersnoeck
Thanks for your patience ;-) I think you should rename ExampleFpdf_AddHttpImage() to ExampleRegister() in order to make it work for godoc. Please run and check the documenation with:
godoc -http=:6060

I also would propose to rename "Fpdf_AddHttpImage" to contrib_httpimg_Register". Or @jung-kurt, would you prefer it contrib pdfs go in a contrib/pdf subfolder? I would prefer also if there is a cleanup function for contrib generated pdfs, see: https://github.com/jung-kurt/gofpdf/blob/master/fpdf_test.go#L44

@stanim good point about the cleanup! I wasn't sure to copy over more as @jung-kurt mentioned looking into making this more available for contribution packages. I've added that now.
I've renamed the file as well. Just to be clear, at the moment this writes it to it's own folder (so contrib/httpimg/pdf).

I think I prefer to have the generated pdfs central in jung-kurt/gofpdf or jung-kurt/gofpdf/contrib. As than someone can just run:
go test ./...

And quickly compare/inspect the generated pdfs in one folder, rather than scout them in different folders. @jung-kurt What do you think?
We really need to get this right, as this will be the example structure for future contribs.

@jelmersnoeck All these hoops we're having you jump through are because your package is the first to be placed in the contrib directory and we want to get it right. Thanks for bearing with us! Hold off just a little longer and I will commit an example helper package using the internal convention.
@stanim Aesthetically, I like the idea of each contributed package keeping all changes (generated PDFs, for example) in its own directory. However, this being the go language, each contributed package's import path clearly defines where in the gofpdf tree it belongs, so it is not like it can be imported to a location in which the ancestor path is different than what we expect it to be. One problem, not a big one, with putting the example PDFs in the main pdf directory is that they will be removed when fpdf_test is run. This could potentially be unexpected. If we opt for a contrib/pdf, we face a similar problem: who is responsible for cleanup. Would each package clean up only its own PDFs? I guess I vote for putting them into the main pdf directory and accepting a slight impedance mismatch between generation and cleanup.

@stanim

And quickly compare/inspect the generated pdfs in one folder, rather than scout them in different folders.

Is there a chance that gofpdf_test will run after one or more contrib tests and prematurely remove the PDFs?

I just committed a change () in which exampleFilename() (now example.Filename()), summary() (now example.Summary()) and the various font, image and test helper routines have been placed in their own package (internal/example). Running
go test ./...

runs all tests beginning with fpdf_test, which removes all PDF files from the pdf directory.
@jelmersnoeck The test of your package will generate a PDF in the gofpdf/pdf directory. It will locate the relative path automatically.

@jung-kurt updated it with the example package. Thanks for that, it makes it lots easier!
@jung-kurt @stanim just wanted to thank you both as well, as a beginner to the Go language, this is quite interesting and educational!

Thanks, @jelmersnoeck -- I just committed your contribution with a small aspect ratio tweak.

Cool!
Sorry for the clutter (the extra commits). I forgot to squash it into one commit this morning.

I'm new to git. How does one squash commits?

http://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit
@jung-kurt
This is the task of the author the pull request. You just have to merge it after it has been squashed to a single commit.

Very useful article -- thanks!


Can't Vote "NO" on Azorius proposals

When trying to vote for the No option, clicking the "Vote" button does nothing.

This is fixed


service failed to clean up consumer for deleted trigger

I observed an incident where the service became entirely unresponsive (HTTP requests not handled, messages not consumed, triggers not fired). The last meaningful log messages looked like this:
2017-01-08 02:16:45,225 [INFO]: [<TRIGGER>] Cleaning up consumer
%3|1483841836.386|FAIL|rdkafka#consumer-339| sasl_ssl:///<BROKER>/1:
Receive failed: No error
%3|1483841836.386|ERROR|rdkafka#consumer-339| sasl_ssl:///<BROKER>/1:
 Receive failed: No error
%3|1483841862.127|FAIL|rdkafka#consumer-1| sasl_ssl://<BROKER>/0: Re
ceive failed: No error

Incidentally,<PHONE_NUMBER>.386 is approximately 2017-01-08 02:16 so these messages are basically consecutive.
The messages from rdkafka repeat indefinitely and the expected log message Successfully closed KafkaConsumer is never seen.

Theory: There is a bug in the close() function that cannot handle being called simultaneously from separate threads.
Conclusion: The logs from the incidents where this problem has occurred do not show multiple triggers being deleted simultaneously.

Theory: The machine was under heavy CPU or memory load at the time this incident occurred, contributing to the failure to properly close the consumer in a timely fashion.
Conclusion: Grafana logs indicate that the container was under nominal CPU (< 15%) and memory load (< 3%) before, during, and after the incident.

**Theory: ** Kafka brokers were unresponsive when the close() method was invoked.
**Conclusion: ** Using fake brokers resulted in the ability to successfully create and delete a trigger.

**Theory: ** the call to delete a trigger from the database is not thread-safe.
**Conclusion: ** TBD

Theory: A race condition exists when a user tries to delete a consumer from the provider.
Conclusion: TBD

Theory: A defect in the underlying kafka library causes an indefinite hang while calling consumer.close()
Evidence: The logs indicate that the application becomes unresponsive when calling either unsubscribe() or close() on the consumer. Further experiments narrow it down to the close() call by showing that all threads block while calling consumer.close() (see this gist demonstrating the issue)

KafkaConsumer close is blocking forever - edenhill/librdkafka#1002
close() blocks all threads - confluentinc/confluent-kafka-python#107 (opened by me)

Both fixes are scheduled to be released in the respective 0.9.4 versions of these projects. I don't have a release date, but I do see that they have a 0.9.4 RC2 available.


Create Low/Mid-Level Architectural Diagram

Considering the vast code base, it would be incredibly helpful to have a lower level map of how the components interact with each other as programs are executed. There are some higher level diagrams in the papers etc, but having explicit references to files/functions would serve as a handy reference. It would also significantly reduce the on-boarding curve for future collaborators.

Closing for now, but will be ongoing WIP.


Allow a single query from the command line without actually opening the prompt

It would be nice if we could run a single query without opening the prompt application, for example with the -q --query parameter.

Added functionality in version 2.1.2


[Feature] Warn about or fail compilation if component fields are overlap on entity

Actual behaviour:
Given 2 components with field name X
When entity is created with given 2 components
Then Entity will have only 1 field X (from last registered component_2)
So value from component_1 is lost
Expected:
Given 2 components with field name X
When entity is created with given 2 components
Then warn/error(or fail compilation) about there are 2 similar fields registered to not let tricky bugs appear

You're right - it is a place for tricky bugs to appear.
Compilation fails are not possible, as entities can be created in various combinations, but some runtime check would be helpful. Preferably not every time, but only the on the first time the given combination is used.
Will be added in next release, pretty soon I hope.
Thanks for idea! :)

Love the idea of dynamic component fields on entity!


granular access at secret level

Hi, is possible to also give granular access at secret level? E.g. AppA can access SecretA only, AppB can access SecretB only etc..?
thanks

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

ID: abdd8ac9-3e5f-3e4b-06f5-e36bf4461c1e
Version Independent ID: b6888d69-51cc-194b-0af8-7cb00e3b4f01
Content: Secure your key vault
Content Source: articles/key-vault/key-vault-secure-your-key-vault.md
Service: key-vault
GitHub Login: @amitbapat
Microsoft Alias: ambapat

@smoms Thanks for your feedback! We will investigate and update as appropriate.

@smoms This is a great question but unfortunately to grant a user account or app id access to one secret, you have to grant it access to the entire vault and so restricting access to a specific key/secret would mean to put it in two different vaults. We already have this feature request posted as a Product Feedback on Azure Feedback.  You can up-vote the same for the product team to include into their plans.

@smoms Thank you for your feedback. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


filtering received data, toArray never called.

I have a store where all my "cards" data objects are stored. In a detail view i only want to show cards that are assigned to a specific set. I'm pretty new to rx and reudx but shouldnt this work?
Subscribe never gets called, pbl because toArray waits for "done". Or is my approach just wrong?
    @select('cards') cards$:any;
    ngOnInit(){
        this.cards$
            .flatMap(s => s)
            .filter(card => card.setId === "someId" )
            .toArray()
            .subscribe(cards => {
                this.cards = cards
            });
    }
    ngOnDestroy() {
            this.cards$.unsubscribe();
    }

would it fulfill the redux approach better if i create a temporary store for the filtered cards and keep them there?

Oh i was thinking way to complicated. just filter in subscribe.


Add Prometheus Exporter Deployment

The Solr operator should auto-run a prometheus exporter with SolrClouds that generates metrics.
I would imagine that there would be some configuration added to the SolrCloud CRD, like tagging information for Prometheus discovery.
In general we first need an official build of the Prometheus Exporter in a Docker container.
This should probably be added in the official docker-solr repo. I will be creating an issue there to see if we can have builts of the prometheus exporter made automatically.

Maybe this should be implemented as a separate CRD. So solr clouds/standalones can be monitored easily even if they themselves aren't run in kubernetes.

Relies on docker-solr/docker-solr#222


Create an overview with explanations; Primitives tokens and Local styles variables

Here is a link to the overview in Figma: https://www.figma.com/file/l3n8s4OzT2kmY2FIpsYCw4/EDS-2.0-Colours?type=design&node-id=467-15583&mode=design


systemd service example

I tried during hours to properly setup a systemd service using node/npm version of the user, for example:
[Unit]
Description=Flood, web interface for rTorrent
After=network.target

[Service]
User=flood
ExecStart=npm start /srv/flood
WorkingDirectory=/srv/flood/
Restart=on-failure

[Install]
WantedBy=multi-user.target

This user (flood) has /home/flood/.nodenv/versions/10.13.0/ set as default locally and globally.
But using /home/flood/.nodenv/versions/10.13.0/bin/npm instead of npm won't do the trick because /home/flood/.nodenv/versions/10.13.0/bin/npmstarts with #!/usr/bin/env node and also those two lines from the bashrc are not sourced as systemd service is not lauching a login shell:
export PATH="$HOME/.nodenv/bin:$PATH"
eval "$(nodenv init -)"

So my question is simple: can you give us an example of systemd service using node/npm (from nodenv of course).

Some related background on why rbenv (and nodenv) don't officially support shared multi-user installations: https://github.com/rbenv/rbenv/issues/38
What's missing from the above is that the user's shims aren't in PATH:

There is nothing special that users need to do for system install. The steps are:

Install or symlink Ruby versions under RBENV_ROOT/versions
Ensure that processes have RBENV_ROOT/shims in PATH

That's it.

https://github.com/rbenv/rbenv/issues/38#issuecomment-148413842
I'd suggest using systemd's Environment or EnvironmentFile to ensure that RBENV_ROOT/shims is in PATH. (keep in mind, env vars aren't expanded for these).
Alternatively, I believe the only that that should be necessary is to invoke npm in the context of nodenv:
ExecStart=/home/flood/.nodenv/bin/nodenv exec npm start /srv/flood

This works (or should work) because nodenv-exec will ensure the selected node's bin directory is added to PATH when invoking npm.

@jasonkarns Thanks a lot, ExecStart=/home/flood/.nodenv/bin/nodenv exec npm start /srv/flood worked perfectly and is much more simple than what i thought.

I would love a wiki page with an example systemd config if you have the
time :)
On Wed, Nov 28, 2018 at 5:55 PM Alexandre ZANNI<EMAIL_ADDRESS>wrote:

@jasonkarns https://github.com/jasonkarns Thanks a lot, ExecStart=/home/flood/.nodenv/bin/nodenv
exec npm start /srv/flood worked perfectly and is much more simple than
what i thought.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodenv/nodenv/issues/117#issuecomment-442637017, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHUpHhkTwcCXtFZgktniOKiyZ-_6XJ0ks5uzxRPgaJpZM4Y2s5j
.

@jasonkarns Done :heavy_check_mark:  https://github.com/nodenv/nodenv/wiki/Use-nodenv-with-systemd

@noraj thanks!


Improve Documentation please

As far as I can tell, the documentation for the test-with-actions lesson template is very out of date.
The steps from 8 - 10 cannot be followed. The language doesn't match what is actually seen on the screen. Not only that but no prompt is given to create a new branch or Create a pull request.
Perhaps I'm just misunderstanding the instructions but regardless, despite my best faith attempt at following the lesson, I cannot seem to make sense of the instructions as listed below.

Click Start commit, and choose to make a new branch named ci.
Click Propose a new file.
Click Create pull request.

@Lauro235 Thanks for opening an issue. We are currently updating the Skills courses, I'll go ahead and triage this for review.

Looking back I can see my 'issue' may not be helpful to everyone, but I broadly I feel that the more accurate the instructions, the less the user has to worry about learning the GUI interface and the more they can focus on the content of Github actions. I appreciate the response and the updating of documentation.

@m-den-01A Thank you for the suggestions! I can confirm that screenshots will be updated as we roll through updating the courses in general. We appreciate your suggestions on the matter!
@Lauro235 Feedback is always helpful! Thank you again for sharing with us.

@cmwilson21 do you have a solution for how to get the step 1 action to move on to step 2? I someone has no experience with actions they will not know how to inspect the actions in place to get them to pass and move on to the next step making this course unusable.

Resolved in #51

Thanks for the very helpful feedback, folks. I think this course has gotten some improvements since it was opened and, although still not perfect, the feedback in this issue may be outdated now.


Change alarm status breach status

Adding all these alarms leaves them in unknown status if there is no status read out when missing (Config rules don't fire all the time, only on event). It's better to just have them on 'good' rather than breaching, no? It defaults to missing.
Adding treat_missing_data to the aws_cloudwatch_metric_alarm resolves this as per this MR.
https://www.terraform.io/docs/providers/aws/r/cloudwatch_metric_alarm.html#treat_missing_data

@Prophecy67 I agree missing data should be treated as GOOD here, thanks!


Dreambooth: RuntimeError: expected scalar type Half but found Float Traceback (most recent call last):

Describe the bug
Everything was working for previous runs, but now getting this error each time I try and run the training.
I see this issue raised and closed by someone running locally:
https://github.com/ShivamShrirao/diffusers/issues/117
But I can't see where to upgrade diffusers package on Colab as it looks like is being downloaded fresh each time in the "install requirements with:
%pip install -qq git+https://github.com/ShivamShrirao/diffusers
Reproduction
No response
Logs
No response
System Info
Colab Notebook

Should be fixed now. 3a21df300312708dbc1304633d6a96280043aa31

@ShivamShrirao Its still broken if you are using full precision training: https://github.com/ShivamShrirao/diffusers/issues/123


Use the absolute URL for twitter card images

If you don't, then the twitter card won't render correctly.

Thank you for the PR, twitter card feature is not fully tested, mime and GFW's fault  :)


fix(locale): remove hard coded strings

Related to #2959
Summary

Remove hard coded strings and added language translations for the the following components:

Component
Language(s)

Markdown widget
en, jp

Image widget
en, jp

File widget
en, jp

Optional
en, pl

BitBucket Authentication Page
en

GitHub Authentication Page
en

GitLab Authentication Page
en

Proxy Authentication Page
previously added but not updated

Test Authentication Page
previously added but not updated

Sample previews

Choosing an image

Choosing a file

Markdown Widget

Took me a while to figure out how netlify-cms-core is connected to the widgets, but now I have a pretty good understanding of how the app works
Credit to @pniedzwiedzinski for removing hard coded string for optional and adding polish translations.

This @tiuweehan and @pniedzwiedzinski! This looks very good. I fixed a small issue that was failing the tests by passing the t function to the raw editor.

@erezrokah Thanks for helping to review this! I'll try to add more language translations as well.

This @tiuweehan and @pniedzwiedzinski! This looks very good. I fixed a small issue that was failing the tests by passing the t function to the raw editor.

@erezrokah Thanks for helping to review this! I'll try to add more language translations after this.

I added polish in #3197


Theme widget upgrade

ThemeData has a lot of stuff going on: the color scheme alone has about 50 different fields, not to mention the potentially limitless theme extensions.
It isn't exactly feasible to put every theme aspect into an enum like what we did with MediaQuery, and non-enum classes unfortuantely have some extra difficulties.
final Set<Object> items = {};

items.add(WidgetState.hovered);
items.contains(WidgetState.hovered); // true

items.add(Object());
items.contains(Object()); // false

For const objects, adding == and hashCode implementations is unnecessary bloat, since they're identical by definition.
But classes with const constructors also sometimes have non-constant instances, and without == / hashCode, a single Theme.of(context) call could add a separate aspect every time the widget is rebuilt.

Proposal
InheritedFilter – a subclass of InheritedWidget that notifies dependents when a filter's output changes, using the Equality API.
The inherited element's "aspect" is a set of filters that clears when the widget rebuilds. This would be similar to what we saw in #107112, but it only applies to the subclass—existing inherited widgets are unaffected.

Closing as "not planned", at least for now:

https://github.com/flutter/flutter/pull/157253


julia: Remove version 0.7 and 1.1

Motivation for this change
Everyone using 0.7 are strongly recommended to switch to 1.0 LTS. 1.1 can be removed because there is already 1.3, and 1.1 is not an LTS.
Things done

N/A

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

See #91930.

Since there is already 1.3. Then 1.1 should be removed as well.

cc: @doronbehar

:+1:.

Bump.  Could somebody please merge this, or else provide a path forward of what must happen first?

cc: @7c6f434c

This pull request would help with Zero Hydra Failures: #97479, as these packages are currently broken

builds are broken

IIRC all julia builds are broken, due to failing tests. Would it make sense to doCheck = false to all of them?

@jonringer I added the deprecation notice.

builds are broken

IIRC all julia builds are broken, due to failing tests. Would it make sense to doCheck = false to all of them?

I think regardless if it were building, we would still want to remove EOL versions

I'm experimenting a more broad change to the situation at https://github.com/NixOS/nixpkgs/pull/98043 . There, only the derivations julia_lts and julia will be left, and hopefully they will build at some point, with most of our deps used instead of upstream's.


Adding images to ZPL

Hi,
How do I add an Image (base64 encoded string) to the ZPL using your utility ?
Basically the scenario is like, the user will upload an image and I will convert them to base64 encoded string and that image needs to be printed through ZPL commands on the label.
Any suggestions ?
thanks,
Karthik. N

Thanks for your feedback.
At this moment you need to prepare the raw ZPL code:
renderEngine.Add(new ZPLRaw("~DGd:o.x,t,w,data"));
I am thinking a good way to allow jpg image directly, do you have any suggestions?

I'm currently using ~DYE command to process the Image data. Converting the image data to Bytes and then to ASCII HEX. But sometimes it is taking too much of time for the conversion. Looking for better alternatives.

How about something like this:
http://www.jcgonzalez.com/zpl-ascii-hex-representation-image-generator
Given a image stream and monochrome ZPL code is generated.

Try the new commit
https://github.com/BinaryKits/ZPLUtility/commit/519c89f21868edec9c1c4a5da3b0f4625d17dafb

Thanks for the update. Anyway to disable the scaling of image alone when I give source and target DPI.

Do you mean the physical dimensions on the label  should remain the same regardless of dpi?

Yes, When I tried your code to process the image, after scaling the image size seems to be bigger whereas the texts are scaled properly and fitting into the Label dimension.

How can I convert the image to Gray scale instead of Black and White ? Because converting it to Black and White loses the image quality and the contents are also not clear.

okay let me combine those. Takes sometime I am traveling

Due to the nature of ZPL printer (black and white dots only, no gray scale), we need to apply "Halftone" or "Dithering" to the original image. http://paint.net.amihotornot.com.au/Features/Effects/Plugins/Render/Dither/
This is an image process issue and should be done in Photoshop or Paint.net, as it requires many parameters.


Required Help initializing Cascading Drop-down

I am looking for sample code for initializing 3 parameters
Criteria (left operant), Operator and value(right operant)
I am trying to implement React Query builder with react redux form in which I have 3 fields
Criteria drop-down having
[{id: 1 name:'city' ,type'dropdown'},{id: 2 name:'something' ,type'listbox'}]
on change I am loading Operator drop-down
which need to load data from API
also loading type of components like text box or select or anything
I need help to initialize state and trigger change event for criteria for binding other components and finally loading dynamic components text box text area

Hi @sushantraje2000, this kind of question is better suited to StackOverflow.
And since it will be helpful to ask there with some sample code: try using the Fields component, which should give you control over what happens to operator/value when criteria is changed.

will fields onchange event get auto trigger on initial state?


⚠ Bofrost.lu has degraded performance

In e9f7acf, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1292 ms

Resolved: Bofrost.lu performance has improved in 29a74af after 6 minutes.


databases in database_annotation.pl do not match README

Hi,
lines 14-19 of database_annotation.pl do not currently match the README docs, for example ExAC is:
my $ExAC="$cwd/../external_databases/ExAC.r0.3.sites.vep.vcf.20150421.vcf.gz";

but should be:
my $ExAC="$cwd/../external_databases/ExAC.r0.3.1.database.vcf";

if following the example from the README I think. Maybe these paths should not be hardcoded or if so the format_index commands should name the files themselves instead of the user?
Also the following file ../external_databases/hg19_random.fa does not exist (line 14), And is not mentioned in the docs as far as I could tell, Is this the entire hg19 build assembly?

Hi @zlskidmore
Thank you for your comments.  We will look at these shortly.
Q

Corrected file name for ExAC database in  database_annotation.pl.
Yes, hg19_random.fa is the entire hg19 build assembly.  We added information on how and where to downloaded hg19 build assembly.  Thank you,


Multiple instances of Fuel

At the moment everything is hard-coded to singletons. Would it be possible to make this usable as separate objects?
A lot of applications require the use of more than just a single API, so being able to set variables like base URL for each of the APIs would be useful.

If you don't want to use the Singletons, you can do
val manager = FuelManager()
manager.basePath = "http://httpbin.org"
manager.request(Method.GET, "/get")

val manager2 = FuelManager()
manager2.basePath = "http://example.com"
manager2.request(Method.POST, "/post")

FuelManager can be instantiated and used in any way you can possibly think of. Do you think that would help you solve your problem?

I am sorry, donno how I missed that!
Thanks for your response

So can I use "http://www.google.com".httpget() or  fuel.get("http://www.google.com") way in Multiple instances of Fuel? And How?


fixed the error described in https://github.com/fourkitchens/czdap-tools...

This fixed the issues/7 for me.

I fixed the issue, the problem was my ip address, sorry.


feat(#8): Support a different service.name for the tests

fixes #8

@nikordaris there was no unit tests for the input parts of this action. Probably worth adding some in a new PR

cc @v1v

Thanks @pragmaticivan , I'll run some tests in my end between today and tomorrow, and I'll keep you updated with the status, thanks for this!

@pragmaticivan release-please action is merged in and i think this PR is ready to merge once we fix the conflict

@nikordaris rebased


Added Bounding Box support to geojson type sources

Refactored the code to override the Vector Source's
loader function. This allows SDK to interpret how features
should be added to the source inside of the OpenLayers update
cycle (specifically needed for BBOXes).
Added test to prove the URL will fetch with a bbox.

Refs: SDK-661

Coverage increased (+0.2%) to 98.021% when pulling fef9c77969dff626e92f67e048519c6d41aebbc6 on theduckylittle:feature/geojson-bbox into d7522d659049b87f41739fc6cf6846beb4aa2f18 on boundlessgeo:master.

Reviewing this one now (after my first coffee ;-))

Coverage increased (+0.2%) to 98.026% when pulling 9d97ecb12fb0ab1be8d85a0f3847d882ad5ef951 on theduckylittle:feature/geojson-bbox into d7522d659049b87f41739fc6cf6846beb4aa2f18 on boundlessgeo:master.

Coverage increased (+0.2%) to 98.023% when pulling<PHONE_NUMBER>aa9b4d89f10ebd857930caf492bacd on theduckylittle:feature/geojson-bbox into c872d08be6dca51992d0286fb0eb30d49cd8f844 on boundlessgeo:master.

Coverage increased (+0.2%) to 98.023% when pulling<PHONE_NUMBER>aa9b4d89f10ebd857930caf492bacd on theduckylittle:feature/geojson-bbox into c872d08be6dca51992d0286fb0eb30d49cd8f844 on boundlessgeo:master.

Coverage increased (+0.2%) to 98.023% when pulling<PHONE_NUMBER>aa9b4d89f10ebd857930caf492bacd on theduckylittle:feature/geojson-bbox into c872d08be6dca51992d0286fb0eb30d49cd8f844 on boundlessgeo:master.


fix(cart): importing magento driver module breaks app builds

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

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

What is the current behavior?

Importing DaffCartMagentoDriverModule and using it in an app will break the build with error:
Error during template compile of 'MagentoModule'
  Function calls are not supported in decorators but 'DaffCartMagentoDriverModule' was called.

What is the new behavior?
The app using the module will correctly build.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@griest024 In theory, this should be breaking the demo app. Can you determine why it isn't? I'd like to be able to verify this behavior and prevent future regressions.

@damienwebdev I don't think that demo is even importing the Magento module.

@griest024 can we import this into demo (even if we don't use the driver) and validate that this bug is in-fact fixed?


[Fix] Add support for other Org.OData.Core.V1.RevisionKind enum values

OData has 3 supported Revision Kinds:

Added
Modified
Deprecated

Currently, version 1.4.0-preview2 only supports the annotation Org.OData.Core.V1.RevisionKind/Deprecated.
A CSDL with the below annotation which includes the Added RevisionKind annotation currently throws a System.InvalidOperationException exception: "The kind of the revision must be Deprecated."
<Annotations Target="microsoft.graph.endWorkingTime(microsoft.graph.workingTimeSchedule)">
  <Annotation Term="Org.OData.Core.V1.Description" String="Triggers the policies associated with the end of working hours." ags:OwnerService="Microsoft.Teams.WorkingTime" />
  <Annotation Term="Org.OData.Core.V1.Revisions" ags:OwnerService="Microsoft.Teams.WorkingTime">
    <Collection>
      <Record>
        <PropertyValue Property="Date" Date="2023-04-05" />
        <PropertyValue Property="Kind">
          <EnumMember>Org.OData.Core.V1.RevisionKind/Added</EnumMember>
        </PropertyValue>
        <PropertyValue Property="RemovalDate" Date="2023-10-04" />
        <PropertyValue Property="Version" String="2023-04/PrivatePreview:TeamsWorkingTime" />
      </Record>
    </Collection>
  </Annotation>
</Annotations>

We need to modify the lib. to support the other revision kinds.

I'm pretty sure that this is just a case of the team not knowing how they are supposed to add that annotation.

Currently this is how the Deprecated revision kind is been added:
<Record>
  <PropertyValue Property="Date" Date="2023-03-02" />
  <PropertyValue Property="Description" String="Private preview for EPM AUthorization Systems APIs" />
  <PropertyValue Property="Kind">
    <EnumMember>Org.OData.Core.V1.RevisionKind/Deprecated</EnumMember>
  </PropertyValue>
  <PropertyValue Property="RemovalDate" Date="2023-05-30" />
  <PropertyValue Property="Version" String="2023-03/PrivatePreview:epmauthorizationsystems" />
</Record>

The Added revision kind would also be added in a similar way...
<Record>
  <PropertyValue Property="Date" Date="2023-04-05" />
  <PropertyValue Property="Kind">
    <EnumMember>Org.OData.Core.V1.RevisionKind/Added</EnumMember>
  </PropertyValue>
  <PropertyValue Property="RemovalDate" Date="2023-10-04" />
  <PropertyValue Property="Version" String="2023-04/PrivatePreview:TeamsWorkingTime" />
</Record>

What we currently have in the conversion lib at the moment, is a way of only reading the Deprecated revision kind annotations. So, when retrieving this revision kind for a given element, and the first one that is found is not of kind Deprecated, the library throws an exception, as expressed here


Add contribution Guide

Maybe we need to add contribution guide for help people to contribute.

Hey, I can take a stab at this. Anything specific or just a general guide?

General guide, + must be creating unit test I think


[FEATURE] Start Upload directly after either drag & drop or after choosing a file via dialog

Is your feature request related to a problem? Please describe.
It was unclear to some users that you have to hit the "+" button when dragging files to the upload dialog or when choosing from the file open dialog before they actually get uploaded.
Describe the solution you'd like
It would be best to start the upload right away after either dragging it to the place or after choosing it from the dialog.
Additional context
https://youtu.be/DngypsuOAXE?si=I3lpLNzyJorafhIW&t=390

Solved with commit 7a0bd375b8b0f5fa376a0eea8d568a4ab837efc2.


about Tests : Don't find pytest in the root directory

Tests (optional)
After adding the datasets run pytest in the root directory to run all tests.

gammar error 'don't=>'didn't'
Plz install pytest first which is a python package.

Gammar 错误 'don't=>'don't 请先安装 pytest，这是一个 python 包。

How to use it after installation？


Tab Switcher: the switcher background can be tapped in lieu of 'Done' bar button to dismiss

The tab switcher continually gives me the impression that I can tap the background to return to the tab I was at (e.g., dismiss the switcher as I would if I tapped the 'Done' button).
This might sound silly, but I'm constantly tapping the background expecting this behavior. Not sure if this is my own problem or not, so I'm opening this (low-priority) issue for feedback, as well as submitting a PR for the team to try out.

Alternately, swapping the location of the Settings-Cog nav-bar button and the Done tab-bar button may be enough.
In iOS, bar buttons with state transitions are more often found at the top of the screen, for example:

a search field with a results controller and a Cancel button that dismisses the search modal;
when you're editing a list in a table view and the Edit/Done nav-bar button

As per comment on the PR - this area is about to get some TLC and we don't want to change the UX at this time.  Thanks for the suggestion!


Enable git server without a GUI

It's more lightweight; expose a 'GUI' option to use the Gitea GUI. they should be identical otherwise.
Look into this: https://spartanengineer.com/nixos/2017/09/25/basic-git-server-with-nixos.html

This is silly - it's not really useful or usable without a gui unless i'm backing up with git-lfs

This is silly - it's not really useful or usable without a gui unless i'm backing up with git-lfs


Create webhook to automatically update online documentation

What is wrong?
Documentation should automatically be deployed to http://py-evm.readthedocs.io when things land in master or when new tags are created.
How can it be fixed
Integrate via webhook. May also need a .readthedocs.yml file.

Done


fix(Spring CodeGen): Update and move naming-related logic into utils

This PR updates and moves three pieces of naming-related logic in spring codegen into util methods:

getSpringPropertyPrefix (e.g. com.google.cloud.vision.v1.spring.auto.image-annotator)

Replaced earlier use of libname due to ambiguity (see comment)

getLibName (e.g. vision)

Intended for descriptive purposes
Includes three options considered by design doc - currently this PR implements option 2 (parse from package name) with the intention to switch to option 3 (parse from default host) in alignment with SampleGen

getSpringPackageName (e.g. com.google.cloud.vision.v1.spring)

Since this was also used in a couple of places, extracted to util in case of future need to update

Dependencies:

#1059 should be adjusted to use these util methods (merge order should be after this PR)

Two questions for perhaps an initial review related to the code changes here:

Would we prefer to have this PR wait on the switch to parseDefaultHost in getLibName, or make the change later in a separate PR?
I saw that the work in #1057 also needs things like the client library name (descriptive title vs. short name), group, and version. Would it make sense for these parsing logic (or at least the tentative version) to also be added under Utils?

In parsing version, for example, perhaps we could also align with SampleGen’s approach:https://github.com/googleapis/gapic-generator-java/blob/d222af10cd6345e0a3660353d7d667e917be67ec/src/main/java/com/google/api/generator/gapic/composer/Composer.java#L194-L205

I think it makes sense to make the change later in a separate PR, consider parseDefaultHost exposure may need to wait a bit.
As for #1057, I would suggest you not to worry about it in this pr. I will align later in that pr separately when possible. The client library coordinates likely needs to be acquired outside of gapic-gen from sources like this metadata, and the library name in Spring Starter to produced can align with parseDefaultHost in getLibName.

@zhumin8 Sounds good! In that case I’ll keep both items as out of scope for this PR and mark it ready for review.
(Side note for Sonar: the missing code coverage for these utils should improve after #1059 adds package info composer tests)


Live Photos

It would be awesome to have the ability to view Live Photos in a chat (if technically possible)

Done. added an endpoint for fetching the live photo. And added an attachment payload flag for it


lnwallet+channeldb: store minimal info in revocation log bucket

This PR removes the redundant data found in the revocation log bucket. Fixes #6317.
Some background knowledge.
The current workflow of revocation
                  ┌────────┐  ┌─────────────┐  ┌───────────┐
revoke_and_ack => │ lnwire │->│ channelLink │->│ channeldb │
                  └────────┘  └─────────────┘  └───────────┘
      ┌─────────────────────┐                           │
      │  openChannelBucket  │  (write RemoteCommitment) │
   ┌─>│ revocationLogBucket │<──────────────────────────┘
   │  └─────────────────────┘
   │
   │(read RemoteCommitment -> create BreachResolution)
   │
 ┌──────────┐  ┌──────────────┐
 │ lnwallet │<-│ chainWatcher │ <= detect funding output spent
 └──────────┘  └──────────────┘
        ┌───────────┐ │                       ┌───────────────┐
        │ server.go │<┘                     ┌>│ BreachArbiter │─────┐
        └───────────┘                       │ └───────────────┘     │
            │ (deliver ContractBreachEvent) │                       │
            └───────────────────────────────┘                       │
                                                                    │
                     ┌───────────────────┐  (write retributionInfo) │
                     │ retributionBucket │──────────────────────────┘
                     └───────────────────┘

How justice tx is carried out currently?
contractcourt.chainWatcher watches any spent event of the funding outpoint. When it's spent by the remote party using a previous version of the commitments, we will create a lnwallet.BreachResolution and a lnwallet.AnchorResolution, and dispatch the info via contractBreach.
When creating the BreachResolution, it will query the breached version of the channel commitment, for the following info,

commitment tx hash, used for creating the outputs
commitment tx's TxOut, used to determine our and their outpoint indexes
Commitment tx's FeePerKw, used to decide whether any of the HTLCs is a dust
commitment's local and remote balances
all the HTLCs in this commitment, used to create HTLC retributions, for each HTLC, we need,

htlc.Incoming
htlc.Amt
htlc.RefundTimeout
htlc.Rhash
htlc.OutputIndex

This info is used to create a contractcourt.ContractBreachEvent inside server.go, which is then sent to our contractcourt.BreachArbiter, via the go channel ContractBreaches. Upon receiving the event, the BreachAribiter will then process the event by creating, publishing and monitoring the justice tx. Meanwhile, it also saves the retribution info to the bucket retribution.
Changes
Several obvious fields are removed from the revocation log, with additional fields such as,

CommitTx, this tx can be large. It was needed to compute the to local/remote output indexes. It's now replaced with a CommitTxHash, with the local/remote indexes precomputed and saved.
FeePerKw, although only takes 8 bytes, it's no longer needed as the dust HTLCs are never saved.

Here's my analysis(estimated bytes, need more research),
before
For ChannelCommitment,
{'bytes': 747573,
 'fields': [{'bytes': 8, 'name': 'CommitHeight', 'type': 'uint64'},
            {'bytes': 8, 'name': 'LocalLogIndex', 'type': 'uint64'},
            {'bytes': 8, 'name': 'LocalHtlcIndex', 'type': 'uint64'},
            {'bytes': 8, 'name': 'RemoteLogIndex', 'type': 'uint64'},
            {'bytes': 8, 'name': 'RemoteHtlcIndex', 'type': 'uint64'},
            {'bytes': 8, 'name': 'LocalBalance', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 8, 'name': 'RemoteBalance', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 8, 'name': 'CommitFee', 'type': 'btcutil.Amount'},
            {'bytes': 8, 'name': 'FeePerKw', 'type': 'btcutil.Amount'},
            {'bytes': 20994, 'name': 'CommitTx', 'type': 'wire.MsgTx'
             'note': 'use max number of HTLCs, assume option anchor'},
            {'bytes': 73, 'name': 'CommitSig', 'type': '[]byte',
             'note': 'assume max, shnorr uses 64/65'},
            {'bytes': 726434, 'name': 'Htlcs', 'type': '[]HTLC',
             'note': '2 bytes to encode the length and use max number of HTLCs'}],
 'name': 'ChannelCommitment',
 'note': 'assume max HTLCs used'}

For a single HTLC,
{'bytes': 1504,
 'fields': [{'bytes': 73, 'name': 'Signature', 'type': '[]byte',
             'note': 'assume max, shnorr uses 64/65'},
            {'bytes': 32, 'name': 'RHash', 'type': '[32]byte'},
            {'bytes': 8, 'name': 'Amt', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 4, 'name': 'RefundTimeout', 'type': 'uint32'},
            {'bytes': 4, 'name': 'OutputIndex', 'type': 'int32'},
            {'bytes': 1, 'name': 'Incoming', 'type': 'bool'},
            {'bytes': 1366, 'name': 'OnionBlob', 'type': '[]byte',
             'note': 'onion packet size is 1366 bytes'},
            {'bytes': 8, 'name': 'HtlcIndex', 'type': 'uint64'},
            {'bytes': 8, 'name': 'LogIndex', 'type': 'uint64'}],
 'name': 'HTLC',
 'note': 'a single htlc serialized record'}

after
{'bytes': 23798,
 'fields': [{'bytes': 8, 'name': 'LocalBalance', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 8, 'name': 'RemoteBalance', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 4, 'name': 'LocalOutputIndex', 'type': 'uint32'},
            {'bytes': 4, 'name': 'RemoteOutputIndex', 'type': 'uint32'},
            {'bytes': 32, 'name': 'CommitTxHash', 'type': 'chainhash.Hash'},
            {'bytes': 73, 'name': 'CommitSig', 'type': '[]byte'
             'note': 'assume max, shnorr uses 64/65'},
            {'bytes': 23669,
             'name': 'HTLCEntries',
             'note': '2 bytes to encode the length and use max number of HTLCs',
             'type': '[]HTLCEntry'}],
 'name': 'RevocationLog',
 'note': 'assume max HTLCs used'}

For a single HTLC,
{'bytes': 49,
 'fields': [{'bytes': 1, 'name': 'Incoming', 'type': 'bool'},
            {'bytes': 8, 'name': 'Amt', 'type': 'lnwire.MilliSatoshi'},
            {'bytes': 4, 'name': 'RefundTimeout', 'type': 'uint32'},
            {'bytes': 32, 'name': 'RHash', 'type': '[32]byte'},
            {'bytes': 4, 'name': 'OutputIndex', 'type': 'int32'}],
 'name': 'HTLCEntry',
 'note': 'a single htlc entry serialized record'}

Once some feedback is received, I'll proceed to the following TODOs,

[ ] add migration
[ ] add unit tests
[ ] add itests?

Still need to check, but I think we could go even further to only save the final justice tx and its variants stored in db using their update height keys. When the channel is breached at a given commitment height, we can then broadcast the transactions. Looks like the anchor resolution is independent of breach retribution. Will find out more.

        {'bytes': 32, 'name': 'RHash', 'type': '[32]byte'},

If we wanted to compress things even further, then we can take advantage of the fact that this payment hash may be present on several other channels (MPP payment splitting and even just a normal route), so we can potentially de-duplicate this even further.
One way to do this would be to maintain a mapping of uint64 -> payHash and store that uint64 instead here. FWIW, in the WitnessBeacon we already maintain a mapping of every pre-image we've ever seen, so it seems feasible for us to leverage that existing store if we chose to go this path (ofc only works for payments that were fully settled).

If we wanted to compress things even further, then we can take advantage of the fact that this payment hash may be present on several other channels (MPP payment splitting and even just a normal route), so we can potentially de-duplicate this even further.

I do find similar info is saved in multiple places such as HTLC update logs and payment circuits, while the historical info might be not? For instance I thought I'd derive HTLCs from the payment circuits upon a breach event but later realized the payment circuits are deleted for settled HTLCs. Need check again on all the fields we saved in the revocation log and make sure it's indeed minimal.

In that case, we'd use the justiceTxVariants.spendHTLCs here right?

Yeah exactly. Even aside from that though, it's possible only some of them go to the second level, in which case we'd create custom spends for them here: https://github.com/lightningnetwork/lnd/blob/262591c3331c2170697fe89b8c49ab857db0adf7/contractcourt/breacharbiter.go#L570

I do find similar info is saved in multiple places such as HTLC update logs and payment circuits, while the historical info might be not

Good point, this is the case for most areas, but right now we never clean up the witness beacon (there's an issue for this in the tracker). Ultimately, we'd need to gauge if this extra logic is really worth it, given the large relative gain we're achieving in this PR alone.

@yyforyongyu, remember to re-request review from reviewers when ready

@yyforyongyu, remember to re-request review from reviewers when ready

@yyforyongyu, remember to re-request review from reviewers when ready

The latest 3 commits now depend on #6421. Something I realized while writing the unit tests - we could leverage BigSize to save us more bytes, plus there's no need to write an empty hash. Let me know if this is overkill. Still need to address @Crypt-iQ 's comments re the zero indexes.

Also itest fails, will check that too.

Actually we should use btcutil.Amount instead of  lnwire.MilliSat for HTLCEntry.Amt since we need to floor the msat into sat when creating the justice tx any, together with BigSize could save us more bytes.

It seems like the old deprecated bucket could instead be removed via a migration to the new bucket format and we can reclaim that diskspace immediately

yeah another PR is coming to do the migration, quite large already so I think it's better to use a different PR.

@yyforyongyu, remember to re-request review from reviewers when ready


check yarn integrity

What
Disable check_yarn_integrity on development environment.
Why
yarn check --integrity is run on rails c, thereby causing the rails console to err.
How
Remove the environment specific check_yarn_integrity setting and fallback to webpacker default.

Duplicate


How appium flutter driver perform open notifications?

Hello everyone i have issue with appium flutter driver how to perform open notification on appium flutter driver? Thanks for any help

NATIVE_APP context may help for it

@KazuCocoa thanks for help, but i've another question. how i can switch from flutter to UiAutomator2 for interact with xpath locator. thanks

Did you try out NATIVE_APP context? (of for the contexn api itself?)
https://github.com/appium-userland/appium-flutter-driver#example
  if (process.env.APPIUM_OS === 'android') {
    await driver.switchContext('NATIVE_APP');
    await (await driver.$('~fab')).click();
    await driver.switchContext('FLUTTER');
  } else {
    console.log('Switching context to `NATIVE_APP` is currently only applicable to Android demo app.')
  }

https://appium.io/docs/en/2.0/guides/context/


Error when creating first tag

Current Behaviour
When clicking on Tags for the first time, I get and empty page
Expected behaviour
The tag form to be shown

can't reproduce


update jemalloc version

A strange situation occurs in a service in our environment, where the memory increases by 1 GB in the case of no load. The service is developed using Tokio. The current jemallocator version is 0.3. 0, and the jemalloc version carried by the service is 5.1.0.
Version 5.1.0 has a terrible  problem
https://github.com/jemalloc/jemalloc/issues/1497

Use tikv instead.
https://github.com/tikv/jemallocator


dbt: use more modern entry_points, update supported manifest versions

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.51%. Comparing base (7d7c715) to head (54046c5).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3278      +/-   ##
==========================================
+ Coverage   85.00%   86.51%   +1.50%
==========================================
  Files          54       40      -14
  Lines        3142     2061    -1081
==========================================
- Hits         2671     1783     -888
+ Misses        471      278     -193

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

#3277