React Native android build failed because of dependancies

getting above error while building the project
my android/build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "27.0.3"
        minSdkVersion = 16
        compileSdkVersion = 27
        targetSdkVersion = 26
        supportLibVersion = "27.1.1"
    }
    repositories {
        jcenter()
        google()

    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.4'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
    // dependencies {
    //     classpath 'com.android.tools.build:gradle:2.2.+' // <- USE 2.2.+ version
    // }
}

allprojects {
    repositories {
        // Add jitpack repository (added by tipsi-stripe)
        maven { url "https://jitpack.io" }
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        google()
    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '4.4'
    distributionUrl = distributionUrl.replace("bin", "all")
}

this is app/build.gradle
buildscript {
    repositories {
        maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
    }
    dependencies {
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.1, 0.99.99]'
    }
}

apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
apply plugin: "com.android.application"

import com.android.build.OutputFile

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion rootProject.ext.compileSdkVersion
    buildToolsVersion rootProject.ext.buildToolsVersion

    defaultConfig {
        applicationId "com.qualpros"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    compile project(':react-native-onesignal')
    compile project(':tipsi-stripe')
    compile project(':react-native-paypal')
    compile project(':react-native-linear-gradient')
    compile project(':react-native-orientation')
    compile project(':react-native-keep-awake')
    compile project(':react-native-video')
    compile project(':react-native-fs')
    compile project(':react-native-image-resizer')
    compile project(':react-native-image-picker')
    compile project(':react-native-vector-icons')
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation "com.braintreepayments.api:braintree:2.17.0"
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

Environment
"react": "16.6.0-alpha.8af6728",
"react-native": "^0.57.5",
"react-native-onesignal": "^3.2.8",

Please help

@davekedar In your build.gradle files you need to move google() before jcenter() should fix the issue. It is a problem with some cached values from jcenter on your system pointing to packages jcenter is no longer hosting.


Handle GitHub error better when user lacks perms

Closes https://github.com/netlify/cli/issues/151

Coverage remained the same at 100.0% when pulling 2738b2e0004d3e6d9a665bf359391b2d85accd6e on handle-github-error into 4ed87e04d5f5981f6b604d9ce9db8d47dcb285e6 on master.


⚠ Fortnite has degraded performance

In 42d7706, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1622 ms

Resolved: Fortnite performance has improved in 326726f.


Testing improvement: Running initiator and target in the same process

From a technical perspective it should be possible to run an initiator and a target in the same process, connected by an in-process bus. This would be very helpful for testing piscsi against scsidump and vice versa, for instance, without the need for any PiSCSI board. Testing everything could be completely decoupled from any hardware. A test coverage of almost 100% should be possible.
This is roughly the approach: The target code (piscsi_core) is launched in a thread and connects to an in-process bus. This bus essentially just remembers the state of the bus signals and is otherwise passive. The initiator code (e.g. scsidump_core) is launched in another thread or the main process and connects to the same bus. The initiator can now send SCSI commands, which are executed by the target thread. The initiator does not notice any difference compared to real hardware. If something goes wrong this means that there must be a bug either in the PiSCSI target or initiator code.

[x] Implement InProcessBus
[x] Implement in process test driver running scsidump against piscsi
[x] Make timing more platform independent
[x] Support for providing target and initiator command line arguments
[x] Use in-process bus on non Pi platforms
[x] Eliminate busy waiting for SEL with in-process-bus, use a condition variable
[x] Clean up some of the bus-related code in /hal, e.g. remove unused methods and macros

First essentially working build run on a regular Linux PC:
bin/fullspec/in_process_test
SCSI Target Emulator PiSCSI (Backend Service)
Version 23.10 --DEVELOPMENT BUILD--  (Nov  4 2023 09:56:09)
Powered by XM6 TypeG Technology / Copyright (C) 2016-2020 GIMONS
Copyright (C) 2020-2023 Contributors to the PiSCSI project
Connection type: FULLSPEC
[2023-11-04 15:28:20.041] [info] Set log level to 'info'
[2023-11-04 15:28:20.041] [info] Cleared reserved ID(s)
[2023-11-04 15:28:20.041] [info] Validating: operation=ATTACH, device=0:0, type=SCRM, device params='file=/home/us/hatari/zip.hds', vendor='', product='', revision='', block size=0
[2023-11-04 15:28:20.041] [info] Validating: operation=ATTACH, device=6:0, type=UNDEFINED, device params='file=services', vendor='', product='', revision='', block size=0
[2023-11-04 15:28:20.041] [info] Executing: operation=ATTACH, device=0:0, type=SCRM, device params='file=/home/us/hatari/zip.hds', vendor='', product='', revision='', block size=0
[2023-11-04 15:28:20.041] [info] Attached SCRM 0:0
[2023-11-04 15:28:20.041] [info] Executing: operation=ATTACH, device=6:0, type=UNDEFINED, device params='file=services', vendor='', product='', revision='', block size=0
[2023-11-04 15:28:20.041] [info] Attached SCHS 6:0
[2023-11-04 15:28:20.041] [info] +----+-----+------+-------------------------------------
[2023-11-04 15:28:20.041] [info] | ID | LUN | TYPE | IMAGE FILE
[2023-11-04 15:28:20.041] [info] +----+-----+------+-------------------------------------
[2023-11-04 15:28:20.041] [info] |  0 |   0 | SCRM | /home/us/hatari/zip.hds
[2023-11-04 15:28:20.041] [info] |  6 |   0 | SCHS | Host Services
[2023-11-04 15:28:20.041] [info] +----+-----+------+-------------------------------------
+----+-----+------+-------------------------------------
| ID | LUN | TYPE | IMAGE FILE
+----+-----+------+-------------------------------------
|  0 |   0 | SCRM | /home/us/hatari/zip.hds
|  6 |   0 | SCHS | Host Services
+----+-----+------+-------------------------------------
Note: No PiSCSI hardware support, only client interface calls are supported
SCSI Target Emulator PiSCSI (Hard Disk Dump/Restore Utility)
Version 23.10 --DEVELOPMENT BUILD--  (Nov  4 2023 09:56:09)
Powered by XM6 TypeG Technology / Copyright (C) 2016-2020 GIMONS
Copyright (C) 2020-2023 Contributors to the PiSCSI project
----------------------------------------
PiSCSI board ID is 7
----------------------------------------
Target device is 0:0
Vendor:      PiSCSI
Product:     SCSI HD (REM.)
Revision:    2310
Device Type: Direct Access
Removable:   Yes
Sectors:     1280
Sector size: 512 bytes
Capacity:    0 MiB (655360 bytes)
----------------------------------------

Starting dump, buffer size is 1048576 bytes

100% (655360/655360)
----------------------------------------
Transferred 0 MiB (655360 bytes)
Total time: 0 seconds (0 minutes)

@rdmark I don't need a Pi anymore in order to test the core functionality :-).

That’s very handy! Let me try how well this works on native Apple Silicon Linux now (Fedora)
On Sat, Nov 4, 2023 at 11:37 PM, Uwe Seimet @.***(mailto:On Sat, Nov 4, 2023 at 11:37 PM, Uwe Seimet < wrote:

@.***(https://github.com/rdmark) I don't need a Pi anymore in order to test the core functionality :-).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@rdmark It might even be possible to test on regular macos, or maybe sooner or later. The more we are using standard C++ functioinality and remove Linux-specific functionality, the closer we get. The current sources already compile on FreeBSD, where I sometimes test with a VM. They do not link on FreeBSD, though, but this is an issue not related to PiSCSI.
If you can try to compile on macos I would be interested in a logfile if there are compile-time errors.

@rdmark I know now why linking on FreeBSD does not work: It has to do with an unfortunate compiler and library setup/combination on this platform, which prevents linking against the protobuf library. FreeBSD 14.0 (due this month) is supposed to work better.
I once had a macos VM, where I was able to build a working scsictl out of the box. Note that parsing the command line options on macos has a runtime issue, see the respective comment in scsictl_core. All of our binaries are affected by this.

@rdmark My guess is that you would be the one to review the PR for this ticket as soon as the first bookworm release is done. This ticket is based on the changes for tickets #1263, #1278 and #1283. Just reviewing/merging this ticket and not reviewing/merging the other three tickets first is less work. This is why I recommend this approach.
Note that with this ticket the daynaport and handshake timing changes, even though there are still tests (by others) pending. Nevertheless I would like to commit the modified timing to develop. If need should be I will revert it in time for the first release after 23.11.


The directive only works with input tag?

I tried to use in a span tag just to display a data but don't worked.
My question is, this is the expected behavior and is not implemented or i'm doing something wrong? If is the first one, it will be soon?
I'm trying do use this way:
<span
    currencyMask
    [options]="maskOptions"
>
     {{ value }}
</span>

i tried put [ngModel]="value" and no success too

Yes, the directive only works in inputs.


Add docstring warnings and TODOs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0723d8a) 72.85% compared to head (6f6bad9) 72.85%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   72.85%   72.85%
=======================================
  Files          20       20
  Lines         851      851
=======================================
  Hits          620      620
  Misses        231      231

Flag
Coverage Δ

unittests
72.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Replace gopkg.in/yaml.v3 dependency as it is outdated and unmaintained

Describe the bug
There has been no activity on the gopkg.in/yaml.v3 repo from its maintainers for over two years. There are over 100 open PRs and nearly 300 unresolved issues, including one from a contributor offering to take over maintainership. Most of the mentioned issues indirectly affect helm-unittest.
To Reproduce
Go to https://github.com/go-yaml/yaml and see there is no activity from the maintainer.
Expected behavior
helm-unittest uses up-to-date and maintained dependencies.

There is no drop-in replacement.
Example helm uses sigs.k8s.io/yaml which is a wrapper/fork https://github.com/kubernetes-sigs/yaml/tree/master/goyaml.v3

5+ years old unmainted dependent library "https://github.com/dprotaso/go-yit" and 4+ unmainted library ""github.com/vmware-labs/yaml-jsonpath/pkg/yamlpath""

Hello @V02460
Thanks for the feedback.
As mentioned by @ivankatliarchuk there are more libraries outdated.
We have started isolating the libraries, and will make contact to other maintainers to see if they are also willing to update their libraries.
Currently some of the used libraries have functionality where I haven't found a replacement for.
Greetings,
@quintush


Unresolved reference: specRepos

When adding the specRepos block mentioned here in my own project, I get the following error:
e: /<some/path>/shared-app/shared/build.gradle.kts:46:9: Unresolved reference: specRepos
e: /<some/path>/shared-app/shared/build.gradle.kts:47:13: Unresolved reference: url

FAILURE: Build failed with an exception.

* Where:
Build file '/<some/path>/shared-app/shared/build.gradle.kts' line: 46

* What went wrong:
Script compilation errors:

  Line 46:         specRepos {
                   ^ Unresolved reference: specRepos

  Line 47:             url("https://github.com/Kotlin/kotlin-cocoapods-spec.git")
                       ^ Unresolved reference: url

2 errors

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s

What am I missing?

Please reopen if the issue is still present. Also for problems related to integration itself it's better to file an issue in  YouTrack


Create a WebSocket class to get game data in real time

URL: wss://api-v2.blaze.com/replication/?EIO=3&transport=websocket

I will like to take up this issue. Just to clarify, a websocket class to get the real time date and a probably a method on the Baseclient class to call it..

Okay, that is clear...I will like to take it up..


Chaning Tree / Background per level

Hi Everyone,
So I have been editing this game and using it for practice while learning JavaScript so far I have edited it so there are 3 levels (each with different ducks, diffculty etc) I also have the sky change from day to night through the levels the only problem is now the tree / grass is annoying me as when its night the grass it still a bright green. I was wondering is there a way to change the tree / grass etc per level? If so how can this be achieved?
Cheers

I'd suggest doing the same thing you've done in #16, only using the level data to store a path to the image you want to use. Then somewhere near the end of the loadLevel method use jquery to adjust the background-image CSS property. It would look something like this:
$('.grass').css('background-image', 'url(' + this.level.backgroundImage + ')');

Closing this issue, but feel free to reopen if you still have questions!

Hi Matt thank you for the reply, hope you had a great christmas! I was playing around with the code last night / this morning however couldnt get it to work... I understand the same solution as in 16 however can seem to execute it? What would i need to have for each level in level.js? .backgroundImage?... Thank you for your help

Thanks @mckenziedave! I did have a nice Christmas, hopefully you did as well.
Regarding the levels.js additions something like this should work:
    {
        id: 1,
        title: 'Level 1',
        waves: 3,
        ducks: 2,
        pointsPerDuck: 100,
        speed: 5,
        bullets: 3,
        time: 13,
        backgroundImage: 'images/level1back.png'
    }

I haven't tested this out, but it's possible you'll need to override the existing background like this:
$('.grass').css('background', 'url(' + this.level.backgroundImage + ') bottom left no-repeat');

and not like above because of how it's declared in the css file. Also, ensure that you're making that call after this line.
If you have any code snippets or errors available to post I might be able to offer some more suggestions.

I'll leave this issue open until I hear confirmation you've got this working, or one week passes.

Hi Matt, I have added the code within the level.js
var levels = [
{
id: 1,
title: 'Hit all the Crabs',
waves: 1,
ducks: 10,
pointsPerDuck: 100,
speed: 1,
bullets: 20,
backgroundColor: '#F3936B',
time: 30
backgroundImage: 'images/level1back.png'
},
and also added the code within the duckhunt.js for the overide however no background is changed and the the game doesnt seem to start now? (I never see the hit all ducks message and no bullets etc show??) Not sure what has gone wrong?


The specified path to the file is invalid: absolute path is needed.

I'm running this in VBox as a VM.
I'm new to VM's. What is the absolute path needed?

The path to your own logo is only necessary if the qr code is to be used.
The logo just needs to be in a place that Home Assistant can access. It makes no sense to specify a fixed location, as there are too many different installation constellations. The folder /config/custom_components/unifi_voucher/ is over written when the integration is updated. I recommend the persistent folder /config/www/.


tf.layers generates an extra op when not specifying the name

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
pip install
TensorFlow version (use command below):
v1.4.0-rc1-11-g130a514 1.4.0
Python version:
3.5.2
Bazel version (if compiling from source):
NA
GCC/Compiler version (if compiling from source):
NA
CUDA/cuDNN version:
8.0.61
GPU model and memory:
GeForce GTX 1080 Ti, 11GB
Exact command to reproduce:

Describe the problem
When using tf.layers, I notice that an extra op is generated when not specifying the name.
For example, here is an example using tf.layers.dense. "dense_1" is an extra op. Similar problem has been observed for tf.layers.conv2d also.
x = tf.placeholder(tf.float32, [None, 16], name='x')
hidden = tf.layers.dense(x, 32)
hidden = tf.layers.dense(hidden, 32)
y = tf.layers.dense(hidden, 1, name='y')

The graph in tensorboard is as follows.

If I add the name,
x = tf.placeholder(tf.float32, [None, 16], name='x')
hidden = tf.layers.dense(x, 32, name='h1')
hidden = tf.layers.dense(hidden, 32, name='h2')
y = tf.layers.dense(hidden, 1, name='y')

then the graph looks as expected,

@fchollet Could you take a look at this?

I believe this is the same issue as https://github.com/tensorflow/tensorflow/issues/13429
It sounds like a variable scope issue?

I think @fchollet is right . The best solution is to specify name by yourself nowadays.

@facaiy thanks for confirming this. Not really a big issue. Just to make sure I am using it properly.

This appears to be resolved. I'm closing the issue to keep the tracker focused. Feel free to reopen if needed.


Private Dns Zone for Azure Site Recovery

Looks like the Private Dns Zone for ASR should be privatelink.siterecovery.windowsazure.com.  The doc states {region}.privatelink.siterecovery.windowsazure.com
Can you help verify which is the correct zone name?
Example from Azure Portal

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

Thanks for the feedback! We are currently investigating and will update you shortly.

@SenthuranSivananthan Thank you for pointing this. I have updated the doc and it should reflect soon. Thank you!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


NSFS | NC | CLI | Account add/update is failing when uid = 0 and gid != 0 and vice versa

Environment info

NooBaa Version: Master
Platform: NC

Actual behavior

Account add/update is failing when uid = 0 but and gid != 0 and vice versa

Expected behavior

An account can get created/updated  when uid = 0 but and gid != 0 and vice versa

Steps to reproduce
> manage_nsfs.js account add --name foo --email<EMAIL_ADDRESS>--uid 0 --gid 10 2>/dev/null
{
  "error": {
    "code": "MissingAccountNSFSConfigUID",
    "message": "Account config should include UID",
    "detail": {
      "uid": 0,
      "gid": 10,
      "new_buckets_path": "/gpfs/bucket-root"
    }
  }
}

More information - Screenshots / Logs / Other output

re opening for validation

@ramya-c3 can you please provide more details?
Are you running on upstream master / upstream 5.15 / downstream RPM?
it was not backported yet to 5.15 upstream/downstream

downstream RPM - 29/01

@ramya-c3 ok so it makes sense we you can reproduce it, this is also a candidate IMHO to be backported to 5.15 WDYT?
also, would you verify it using upstream master?

@romayalon it is working as expected

Closing per last comment


shallowRef's return type should match ref's

Version
2.7.14
Reproduction link
codesandbox.io
(this is a typescript bug, it's not visible on the sfc's website)
Steps to reproduce

Use shallowRef with a generic type params that's a union : shallowRef<{a:1} | {b:2}>({a:1})
Or use shallowRef and specify argument's type with as: shallowRef({a:1} as {a:1} | {b:2})

What is expected?
The return type should be ShallowRef<{a:1} | {b:2}>.
What is actually happening?
The return type is ShallowRef<{a:1}> | ShallowRef<{b:2}>

This breaks Vue's watch function. The first argument of watch's callback becomes a Ref instead of the value, which will cause a runtime error because Property 'value' does not exist on type '{ a: 1; } | { b: 2; }'
The reproduction link provides a good example of this. If you have any questions just ask me.
I've fixed the issue on my fork and the CI actions completed successfully.
You need to change
function shallowRef<T extends object>(value: T): T extends Ref ? T : ShallowRef<T>;
to
function shallowRef<T extends object>(value: T): [T] extends [Ref] ? T : ShallowRef<T>;
This matched ref's type:
function ref<T extends object>(value: T): [T] extends [Ref] ? T : Ref<UnwrapRef<T>>;
This issue is the same issue as vuejs/core#7852

I've added a better reproduction of the error to show it will lead to runtime error.

奥利给


Update pt_br.json

Fresh from the oven 🧑🍳
I mostly copied the work from the old PR over to this one, so if something is off in the newer versions, point me out. I also added and translated all missing entries from en_us.json. They're at the bottom of the file so you can easily change their position, if you will.
I detected them by using the following command in bash (I thought it would be useful to share):
diff <(jq keys pt_br.json) <(jq keys en_us.json)

Thanks for contributing again with this "resubmission"! :)


Feature Request

I'd like to be able to whitelist/blacklist when using token..replacement. For example, if I''m referencing a file like "allhosts.csv" I want to be able to blacklist a set of hosts with a regex. Possibly an additional parameter like below:
replace server name
token.2.token = (SERVERNAME)
token.2.replacementType = file
token.2.replacement = $SPLUNK_HOME/etc/apps/oidemo/master_eventgen_replace/webhosts.sample:2
token.2.replacementWhitelist.0 = *
token.2.replacementBlacklist.0 = webserver-[0-9]

Totally valid request, but why wouldn't you just modify the source file or create a different copy of it for that token?

I have a few scenarios going at the same time. For example, I need webserver-02 to spike in CPU at 30min past the hour. To do this I create eventgen stanzas and sample files:

An "issue" sample file which spikes the CPU data at 30min past the hour for webserver-02
A noise sample for the first 30min of webserver-02
A problem sample file(s) which runs for the whole hour that generates cpu data for all hosts replacing SERVERNAME from allhosts.sample which has all hosts except webserver-02.

Next I want to do something similar (say a spike in queries and cpu) for dbserver-02 but now I have to create another file with all hosts except dbserver-02 and non-db servers.
As I continue to add scenarios I have to make a lot of files. A white/black list allows me to substantially reduce the number of replace files required and makes it easier to update/maintain.
Make sense?

this is a good idea.  I just don't want to touch that code :).  I'm leaving it open for the time being.

Since this issue has been open for a while and we have released new versions 6.x.x of Eventgen, please recreate the issue if you still see fit.


Azure Private DNS Zone Support

I'm not sure if Azure private DNS is officially supported by BKPR. However it is possible to set jsonnet overrides to make it work. I'm documenting here how this can be done.
Note however that the BKPR installer still creates a non-private DNS zone while the external-dns service will update the private DNS zone correctly.
Configuring the kubernetes external-dns service for private DNS Zone requires additional arguments
--azure-config-file="/etc/kubernetes/azure.json"
When using the Azure provider, specify the Azure configuration file (required when --provider=azure
--azure-resource-group=""     When using the Azure provider, override the Azure resource group to use (required when --provider=azure-private-dns)
--azure-subscription-id=""    When using the Azure provider, specify the Azure configuration file (required when --provider=azure-private-dns)
--azure-user-assigned-identity-client-id=""
When using the Azure provider, override the client id of user assigned identity in config file (optional)
Also the external-dns code https://github.com/kubernetes-sigs/external-dns/blob/ec7c6ba4d792417c44439e1583b45d6a2c7a398c/provider/azure_private_dns.go
at line 61
	authorizer, err := auth.NewAuthorizerFromEnvironment()
Requires that environment variables be set to configure the client.
Here's the kubeprod-manifest.jsonnet that works around the issue.
``
edns+: {
     deploy+: {
        spec+: {
            template+: {
                spec+: {
                    containers_+: {
                        edns+: {
                            env_+: {
                              "AZURE_CLIENT_ID": $.config.externalDns.aadClientId,
                              "AZURE_CLIENT_SECRET": $.config.externalDns.aadClientSecret,
                              "AZURE_TENANT_ID": $.config.externalDns.tenantId,
                              "AZURE_SUBSCRIPTION_ID": $.config.externalDns.subscriptionId
                            },
                            args_+: {
                                "azure-resource-group": $.config.externalDns.resourceGroup,
                                "azure-subscription-id": $.config.externalDns.subscriptionId,
                                "provider": "azure-private-dns",
                                "log-level": "warning"
                            }
                        }
                    }
                }
            }
        }
    }
}

``

Hi,
Thank you very much for contributing! Checking the installer code it seems that it will try to create the DNS Zone, we will check if it is possible to skip the non-private DNS zone creation.


Add documents to Interpretation in 20_interpret

Add documents to Interpretation class

Small nits before Benjamin takes a look

Thanks for the suggestions. I think they make sense, so I commit changes.

A few small things to clean up. Otherwise looks good. Thanks.

Thank you for the suggestion. It looks simpler.

Thanks!


MRG: Add get_picked_points() to _Brain

Add a get_picked_points() function to the _Brain object and updates the feature overview table.
It's an item of #7162
Related to #7959

@bloyl can you give it a try?

thx @GuillaumeFavelier


Fix RFC6587 parsing on UDP.

My earlier fixes to UDP packet parsing broke RFC6587 parsing. By eliminating use of the scanner (and thus the requirement that lines should end with a \n character) I also removed the more functional RFC6587 scanner which does not require a \n but does advance over the length field. This patch restores use of the scanner where it is explicitly specified (currently just RFC6587).
Signed-off-by: Alex Bligh<EMAIL_ADDRESS>

Can you provide a test for this case?

Done. I had to fix up TestTailFile (increased the delay from 100 microseconds to 100 milliseconds) as it was causing a Travis failure. I suspect there may be a more reliable way to do this than arbitrary delays.


Software Module Interface

Define an interface for libraries to be able to plug into GP2040. Would likely have the following traits (plus more I'm sure):

Main module code will run on core1
Modules will likely need their own way to setup() and loop() on the core1 thread
May need to integrate defines in BoardConfig.h
Can rely upon receiving GamepadState to perform actions (flash LEDs, display status, make noise, etc.)

This is now implemented with the GPModule class and some setup logic in the main.cpp file.


runningx: deprecate phases

Motivation for this change
#28910
Things done

[ ] 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/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130478 at a80435da run on x86_64-linux 1

1 package built successfully:

runningx

2 suggestions:

warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/tools/X11/runningx/default.nix:18:3:
   |
18 |   buildPhase = ''
   |   ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/X11/runningx/default.nix:22:3:
   |
22 |   installPhase = ''
   |   ^


Problems installing the package on macOS M1 chip

Hi,
I am having problems to install this package on a macos with M1 chip.
The error:
Could not find <Python.h>. This could mean the following:
* You're on Ubuntu and haven't run apt-get install python3-dev.

* You're on Windows and your Python installation was somehow corrupted
(check your environment variables or try re-installing?)
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> grpcio
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
Environment details

OS type and version: MacOS 12.4 (chip M1)
Python version: Python 3.10.0
pip version: pip 22.3.1

Thanks!

This ilke a problem installing grpcio, not with pandas-gbq. Does pip install grpcio work?

I just tried to reproduce this on an M1 with pandas-gbq==0.17.9 (the closest release to when this bug was opened) and I could not. @davidgarciatwenix I'm going to close this for now, but please reopen with more information (exact command you're running, requirements.txt file if being used) if the issue is still occurring!


[v2] setNativeProps is missing

Version
2.0.0-17
Reproduction
import React from 'react';
import styled from 'styled-components/native';
import { TouchableHighlight, View } from 'react-native';

const Text = styled.Text``;

export default class App extends React.Component {
  render() {
    return (
      <View>
        <TouchableHighlight>
          <Text>Test</Text>
        </TouchableHighlight>
      </View>
    );
  }
}

Expected Behavior
Should not throw any errors.
Actual Behavior
Throw the following error :
invariant.js:44 Uncaught Error: Touchable child must either be native or forward setNativeProps to a native component
    at invariant (invariant.js:44)
    at ensureComponentIsNative (ensureComponentIsNative.js:20)
    at Object.componentDidMount (TouchableHighlight.js:124)
    at Object.chainedFunction [as componentDidMount] (factory.js:531)
    at ReactCompositeComponent.js:265
    at measureLifeCyclePerf (ReactCompositeComponent.js:75)
    at ReactCompositeComponent.js:264
    at CallbackQueue.notifyAll (CallbackQueue.js:76)
    at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)
    at ReactReconcileTransaction.closeAll (Transaction.js:206)

Reason
setNativeProps is missing in StyledNativeComponent in v2 branch.

Confirmed - just hit this 👍

@orta It's being worked on at PR #764


feat: add mipidsi support

add mipi dsi subsystem support.
reference links:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/drm_mipi_dsi.c https://github.com/torvalds/linux/blob/master/include/video/mipi_display.h
Signed-off-by: liushuai25<EMAIL_ADDRESS>Summary
Add mipi dsi subsystem.
Decouple panel driver and chip dsi driver.
Impact
Nothing
Testing

@lupyuen @shuai532209720 provide a general mipi dsi driver framework. Your owrk on A64 may benefit from it.


Xcode 9 crash - Modification requires exclusive access

What you did:
Ran both my app and unit tests that test rudimentary mapping of objects using ObjectMapper using Xcode 9 (tried both Swift 3.2 and Swift 4.0 versions) and it crashes in random places within ObjectMapper during mapping.
The exact same code with the exact same version of ObjectMapper runs fine when compiled with Xcode 8 (iOS 10 SDK).
What you expected:
App and unit tests properly run.
What you got:
#0	0x0000000113e85800 in swift_beginAccess ()
#1	0x0000000108d99d56 in MyObject.myProperty.materializeForSet ()
#2	0x0000000108dad1e2 in MyObject.mapping(map:) at

It also indicates this error: "Simultaneous accesses to 0x%lx, but modification requires exclusive access"
The unit tests run just in one thread so I can rule out any kind of multithreading issue.
I am trying to troubleshoot this issue for multiple days without any luck. Does anyone else encounter the same problem?
Update: I noticed that my app and the unit test target had this setting
SWIFT_ENFORCE_EXCLUSIVE_ACCESS set to "Full Enforcement".
Once I turned it off, the app didn't crash anymore.

Since you have resolved your issue I will close this. Thanks

@tristanhimmelman I haven't resolved the issue, I have worked around it. This is still a problem that need to be solved. By default, Xcode will set this compiler setting. So inside of ObjectMapper something happens that is now considered dangerous.

+1

+1

+1

+1

+1

+1

Is there any update you can provide for this? Or is the project no longer maintained?

Looks like regular updates are being made to the repo. @tristanhimmelman any ETA on this issue since it seems to be impacting quite a large group of people.

@adamkuipers @falkobuttler, unfortunately I do not currently have time to look into this issue. If anybody has a PR with a fix I am happy to accept it.

Turning off enforcement won't prevent real crashes from happening in the wild. This setting you're changing is about always warning you when it might happen.


Recommendation to use package with k8s v0.26.0

In k8s.io/apimachinery v0.25.0 version, k8s.io/apimachinery/pkg/util/clock this package is removed. Redhat operator is using k8s.io/apimachinery v0.23.0 version. Can you please share a recommendation to use redhat-marketplace-operator with k8s.io/apimachinery v0.26.0 version?

Probably change to use k8s.io/utils/clock
redhat-marketplace-operator aligns with Openshift kubernetes releases.
When redhat-marketplace-operator is ready to support Openshift v4.11, it will use k8s.io/apimachinery v0.24

@dacleyra we are using redhat-marketplace-operator as a dependency in our project. We wanted to switch to k8s.io v0.26.0 version. is there any immediate plan for redhat-marketplace-operator to support v0.26.0 version?

clock is now updated in the latest release, but doing a go.mod replace => k8s.io v0.26.0 may still pose a problem as there are still some older apis used like v1beta1batch. vNext will stop using them, in order to bring us up to v0.24


fix log read bug

only workflow logs file need be read.

Codecov Report

Merging #8852 (eafe08b) into dev (e130b82) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #8852   +/-   ##
=========================================
  Coverage     45.30%   45.31%
- Complexity     4077     4078    +1
=========================================
  Files           702      702
  Lines         27112    27113    +1
  Branches       2897     2897
=========================================
+ Hits          12284    12286    +2
+ Misses        13676    13674    -2
- Partials       1152     1153    +1

Impacted Files
Coverage Δ

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...eduler/api/service/impl/AlertGroupServiceImpl.java
90.80% <0.00%> (-0.87%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
31.90% <0.00%> (-0.03%)
:arrow_down:

...heduler/api/service/impl/SchedulerServiceImpl.java
8.62% <0.00%> (ø)

...inscheduler/service/quartz/ProcessScheduleJob.java
0.00% <0.00%> (ø)

...lphinscheduler/plugin/task/dq/DataQualityTask.java
0.00% <0.00%> (ø)

...lphinscheduler/service/quartz/QuartzExecutors.java

...eduler/service/quartz/impl/QuartzExecutorImpl.java
0.00% <0.00%> (ø)

...inscheduler/api/service/impl/UsersServiceImpl.java
74.89% <0.00%> (+0.20%)
:arrow_up:

...i/service/impl/AlertPluginInstanceServiceImpl.java
65.95% <0.00%> (+0.36%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

who can tell why we need add this check?


经过几番捣腾，后台报语法错误：TypeError: '<' not supported between instances of 'tuple' and 'float'`

经过几番捣腾，载入int4的模型OK了，浏览器提交prompt，后台报语法错误如下。
ubuntu：2204
NVIDIA-SMI 530.41.03
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243
`~/MOSS$ python moss_gui_demo.py
Waiting for all devices to be ready, it may take a few minutes...
Running on local URL:  http://<IP_ADDRESS>:6006
Running on public URL: https://7b29d06f6fba682b.gradio.live
This share link expires in 72 hours. For free permanent hosting and GPU upgrades (NEW!), check out Spaces: https://huggingface.co/spaces
Traceback (most recent call last):
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/gradio/routes.py", line 401, in run_predict
output = await app.get_blocks().process_api(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/gradio/blocks.py", line 1302, in process_api
result = await self.call_function(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/gradio/blocks.py", line 1025, in call_function
prediction = await anyio.to_thread.run_sync(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
return await future
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
result = context.run(func, *args)
File "moss_gui_demo.py", line 122, in predict
outputs = model.generate(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 28, in decorate_context
return func(*args, **kwargs)
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/generation/utils.py", line 1571, in generate
return self.sample(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/generation/utils.py", line 2534, in sample
outputs = self(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/good/MOSS/models/modeling_moss.py", line 678, in forward
transformer_outputs = self.transformer(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/good/MOSS/models/modeling_moss.py", line 545, in forward
outputs = block(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/good/MOSS/models/modeling_moss.py", line 270, in forward
attn_outputs = self.attn(
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/good/MOSS/models/modeling_moss.py", line 164, in forward
qkv = self.qkv_proj(hidden_states)
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/good/MOSS/models/quantization.py", line 371, in forward
out = QuantLinearFunction.apply(x.reshape(-1, x.shape[-1]), self.qweight, self.scales,
File "/home/good/anaconda3/envs/moss/lib/python3.8/site-packages/torch/cuda/amp/autocast_mode.py", line 94, in decorate_fwd
return fwd(*args, **kwargs)
File "/home/good/MOSS/models/quantization.py", line 283, in forward
output = matmul248(input, qweight, scales, qzeros, g_idx, bits, maxq)
File "/home/good/MOSS/models/quantization.py", line 254, in matmul248
matmul_248_kernel[grid](input, qweight, output,
File "/home/good/MOSS/models/custom_autotune.py", line 93, in run
self.cache[key] = builtins.min(timings, key=timings.get)
TypeError: '<' not supported between instances of 'tuple' and 'float'`

same issue.

一样的错误。

请查看这个issue https://github.com/OpenLMLab/MOSS/issues/65

参考：ssue https://github.com/OpenLMLab/MOSS/issues/65
注释掉 models/custom_autotune.py 后依然报下面错误：

   except #triton.compiler.OutOfResources:
   return float('inf')

$ python3 moss_cli_demo.py
/usr/lib/python3/dist-packages/requests/init.py:89: RequestsDependencyWarning: urllib3 (1.26.15) or chardet (3.0.4) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
Waiting for all devices to be ready, it may take a few minutes...
triton not installed. Run pip install triton to load quantized version of MOSS.
Traceback (most recent call last):
File "moss_cli_demo.py", line 30, in
raw_model = MossForCausalLM._from_config(config, torch_dtype=torch.float16)
File "/home/good/.local/lib/python3.8/site-packages/transformers/modeling_utils.py", line 1024, in _from_config
model = cls(config, **kwargs)
File "/home/good/MOSS/models/modeling_moss.py", line 612, in init
self.quantize(config.wbits, config.groupsize)
File "/home/good/MOSS/models/modeling_moss.py", line 736, in quantize
from .quantization import quantize_with_gptq
File "/home/good/MOSS/models/quantization.py", line 27, in
@autotune(
NameError: name 'autotune' is not defined

已更新

已更新

还是有一样的问题

我也有一样的问题

我也有一样的问题

https://github.com/OpenLMLab/MOSS/issues/129#issuecomment-1535899953
我通过这个大佬的解决方案搞好了。


Add a Perfectly option for FAMs

What the value should be isn't obvious. There are a lot of different methods. There are a lot of different studies of the methods giving various numbers.
The Lactation Amenorrhea Method (LAM) has up to 92%-100% effectiveness according to some sources:
https://www.ncbi.nlm.nih.gov/books/NBK546661/
https://www.kff.org/womens-health-policy/fact-sheet/natural-family-planning-as-a-means-of-preventing-pregnancy/
Others say 98%:
https://www.nhs.uk/conditions/contraception/natural-family-planning/
Though maybe that method should be ignored because it requires you to have a newborn, meaning most people are unable to use it.
Some sources say the Sympto-thermal/Symptothermal method has 99.6% effectiveness with perfect use:
https://www.kff.org/womens-health-policy/fact-sheet/natural-family-planning-as-a-means-of-preventing-pregnancy/
https://www.aafp.org/afp/2012/1115/od1.html
Others say 98%:
https://www.ncbi.nlm.nih.gov/books/NBK546661/
This site simply says 99% without naming a method:
https://www.nhs.uk/conditions/contraception/natural-family-planning/

Adding a separate entry for LAM may be a different feature request, I'm inclined to hold off on that one for now. As you noted it requires you to already have a newborn. I'm open to adding it, but I think improving the more general case is a better focus for now.
The 76% I currently have on the site is pulled from Planned Parenthood (I err'd on the low end rather than the high end, as it seems to me to be better to be pessimistic when surfacing these numbers).
My current thinking is to add a 3-button toggle option that allows you to switch between the high and low end for FAM generally (between the 76% and 88% quoted from PP) with another option for "Perfectly" at 98%.
@B-u-g-e What do you think about this approach?

Three options is fine. I would probably go with 99% for the top, but I'm not wholly against 98% due to the uncertainty among the sources.


updated GIF, again

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/Bicycle-Leschi-old2.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/Bicycle-Leschi10.gif
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Refactor/check metadata

Refactors checkMetadata:

improvements
error handling instead of logging
render some internal functions public for better flexibility down the line

There are no new additional functions, and they're implicitly tested by the main test case. I can write tests for them, but at that point those will be new additions.

you are right, my bad


Improve async/multithreaded behavior of tellstick code

Description:
The tellstick code has several issues wrt threading behavior. We get a warning printed due to i/o in event loop. The "repetition" stuff is not very user friendly, where the same command needs to be sent multiple times (which takes ~0.8 seconds). If they are queued up, and the user switches the appliance off again, it will start blinking. We are also misusing the local thread from the tellstick library, which does not handle errors very well.
This patch fixes this. (And possibly some more I forgot.)
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

@stefan-jonasson Can you please verify that I do not break your system again with this patch? I do not have any tellstick lights, only switches. It does not seem likely, but then again, it didn't seem likely that I'd break anything last time either.

Nice! 🐬


Expose MergeGlobalParamEntryDefaults so state syncer can use it, update func to take in params instead of utxo view

Merge activity

Feb 20, 1:23 PM EST: @lazynina started a stack merge that includes this pull request via Graphite.


Recover from Kafka::MessageSizeTooLarge exception in async producer.

You can get into a bad unrecoverable state when a Kafka::MessageSizeTooLarge exception is raised.
When we receive this exception, if we're using the sync producer, then we simply re-raise this exception. If we're using the async producer, then we attempt to remove the largest message from the buffer and simply retry. Once retried, if the buffer is still too large, we'll continue removing the largest message until we can successfully flush the buffer.
This will re-raise the exception since it is done synchronously:
DeliveryBoy.deliver('a' * 1_500_000, topic: 'test')

This will remove the largest message and continue to retry:
DeliveryBoy.deliver_async('a' * 1_500_000, topic: 'test')

Would love to get some feedback on this approach.  Specifically @dasch since you had some opinions on the approach here:
https://github.com/zendesk/ruby-kafka/pull/358

Also, ❤

@dasch I dropped the ball here.  Are you still interested in getting this in?  If so, I'll rebase and add the functional test as asked in the next couple weeks.


error exit during start of click/drag in Excel pivot table

When using myrtille (myrtille_v2.9.2) RDP to Windows 10.

Initiate a click drag of a column name in the pivot table configuration dialog in Excel.
myrtille exit.
I tried to use freerdp newest version (v2.3.2), it had solve this problem.
https://github.com/FreeRDP/FreeRDP/issues/6101

Would it be solved soon in myrtille ?
Thank you.

Thanks for your report, indeed I have to update FreeRDP into next releases

Thanks for your report, indeed I have to update FreeRDP into next releases
Thanks for your quick response.

Hello. I am facing the same issue.
I tried to build freerdp 2.5 to insert it to Myrtile but failed utterly.
The use of Pivot Tables is important for the project I am working on.
Does anyone have any pointers or an ETA on the new version of Myrtile (with the new version of FreeRDP), before I have to start the whole project again based on Guacamole :-( ?

anyone  get any solution of above exit issue

cedrozor pls help

Thanks for your report, indeed I have to update FreeRDP into next releases

any update?


EACCES: permissoin denied

Global installation
$ sudo npm install -g marko-devtools
npm WARN deprecated<EMAIL_ADDRESS>to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/usr/bin/marko -> /usr/lib/node_modules/marko-devtools/bin/marko
/usr/lib
└──<EMAIL_ADDRESS>
marko create
$ marko create marko-test
fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: EACCES: permission denied, open '/usr/lib/node_modules/marko-devtools/src/commands/test/util/browser-tests-runner/.21733.1488780531669.page-template.marko.js'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Object.fs.writeFileSync (fs.js:1333:33)
    at compile (/usr/lib/node_modules/marko-devtools/node_modules/marko/node-require.js:60:16)
    at Object.markoRequireExtension [as .marko] (/usr/lib/node_modules/marko-devtools/node_modules/marko/node-require.js:120:27)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)

$ marko and $ marko test cause the same error.
$ sudo marko create works, but resulting files are owned by root.
Folder denied access
$ ls -al /usr/lib/node_modules/marko-devtools/src/commands/test/util/browser-tests-runner/
total 36
drwxr-xr-x 2 nobody jordan 4096 Mar  6 00:08 .
drwxr-xr-x 4 nobody jordan 4096 Mar  6 00:08 ..
-rw-r--r-- 1 nobody jordan 2194 Mar  4 13:29 BrowserContext.js
-rw-r--r-- 1 nobody jordan 8005 Mar  4 13:29 index.js
-rw-r--r-- 1 nobody jordan  814 Mar  4 13:29 .jshintrc
-rw-r--r-- 1 nobody jordan   19 Mar  4 13:29 mocha-run.js
-rw-r--r-- 1 nobody jordan  393 Mar  4 13:29 page-template.marko
-rw-r--r-- 1 nobody jordan 1683 Mar  4 13:29 setup.js

Version info
$ lsb_release -d
Description:	Ubuntu 16.04.2 LTS

$ node -v
v6.10.0

$ npm -v
4.3.0

Local installs work fine
$ node_modules/.bin/marko create marko-test

No errors.

@jordanbtucker This is due to the way you have npm set up, which I would recommend fixing.
That said, since this is common, I'm leaving this open until we can take a look and see if we can do anything on our side.

Changing the owner or permissions of /usr/local is not a fix, it's a poor workaround. The permissions are set the way they are for a reason.
This is the first package that's caused this issue for me, and like you said, this is common, so I think the onus is on you to fix it, not suggest that the official Node.js installer is at fault.

I do think the Node.js OSX installer should behave differently, installing from a package manager on a Linux distribution or using the Windows installer does not result in requiring sudo for global package installs (because they are installed "globally" to the user, rather than to the system).
That said, I hope I did not come off as blaming you for the issue and it is something we want to look into.

Installs from a package manager on Linux do require sudo to install global packages. At least it does in Debian-based distros, including the official Ubuntu packages and the NodeSource packages.
Specifying a user-writable path in ~/.npmrc is a better solution than changing the permissions of /usr/local (/usr/lib/ in some environments). However it's still a workaround for this bug.
nvm is a great tool, but it's also just a workaround for this bug.
Thanks for committing to looking into this issue. And I don't feel like you blamed me :)

Nvm its a workaround?

Why not instead of change the permissions of /usr/local only change the permissions of browser-tests-runner folder?
For me, this's been a temporally solution.
Info
Distro version:	Ubuntu 16.04.2 LTS
Node version: v6.11.0
npm version: 3.10.10

Before manage access permissions
$ ls -al /usr/lib/node_modules/marko-devtools/src/commands/test/util/
total 20
drwxr-xr-x 4 nobody davidenq 4096 jun 18 17:52 .
drwxr-xr-x 3 nobody davidenq 4096 jun 18 17:52 ..
drwxr-xr-x 2 nobody davidenq 4096 jun 18 17:52 browser-tests-runner
-rw-r--r-- 1 nobody davidenq 3680 may 19 12:45 loadTests.js
drwxr-xr-x 2 nobody davidenq 4096 jun 18 17:52 server-tests-runner

After manage access permissions

$ sudo chmod 775 /usr/lib/node_modules/marko-devtools/src/commands/test/util/browser-tests-runner/

$ ls -al /usr/lib/node_modules/marko-devtools/src/commands/test/util/
total 20
drwxr-xr-x 4 nobody davidenq 4096 jun 18 17:52 .
drwxr-xr-x 3 nobody davidenq 4096 jun 18 17:52 ..
drwxrwxr-x 2 nobody davidenq 4096 jun 18 17:52 browser-tests-runner
-rw-r--r-- 1 nobody davidenq 3680 may 19 12:45 loadTests.js
drwxr-xr-x 2 nobody davidenq 4096 jun 18 17:52 server-tests-runner

I believe managing the permissions and/or installing node w/o sudo is probably the best option here.

The best option is to stop writing to node_modules.

@jordanbtucker I could be wrong but I don't believe we are writing to node_modules any more. It's possible the chromedriver or other dependency is though. We've also recently separated all commands into their own executable which should help alleviate that issue at least for the create command.
Are you still able to reproduce this issue?

A similar error, yes.
$ sudo npm i -g @marko/create
/usr/bin/marko-create -><EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 116 packages from 59 contributors in 3.742s

$ marko-create marko-test
? Choose a template …  Use ↑ and ↓. Return ⏎ to submit.(node:11452) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/@marko/create/dist/examples-cache'
    at Object.mkdirSync (fs.js:841:3)
    at mkdirp$2 (/usr/lib/node_modules/@marko/create/node_modules/degit/dist/index-26d8486e.js:14725:8)
    at Degit._cloneWithTar (/usr/lib/node_modules/@marko/create/node_modules/degit/dist/index-26d8486e.js:15094:3)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Degit.clone (/usr/lib/node_modules/@marko/create/node_modules/degit/dist/index-26d8486e.js:14878:4)
    at async downloadRepo (/usr/lib/node_modules/@marko/create/dist/index.js:115:3)
    at async exports.getExamples (/usr/lib/node_modules/@marko/create/dist/index.js:59:3)
(node:11452) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

It's trying to create the directory /usr/lib/node_modules/@marko/create/dist/examples-cache.

@jordanbtucker thanks for working with me on this, I just published a new version of create (5.0.2) which should now write the example cache to the tmp dir. Hopefully that should fix the above?

Yes, it is fixed now. Thanks!


Update debug-modern-pages.md

documented debugging webparts by comiling without the --ship parameter
Category

[ ] Content fix
[ ] New article
Related issues: fixes #X, partially #Y, mentioned in #Z

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
(DELETE THIS PARAGRAPH AFTER READING)

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
(DELETE THIS PARAGRAPH AFTER READING)

Guidance

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.
(DELETE THIS PARAGRAPH AFTER READING)

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/debug-modern-pages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 53682dd:
:clock10: Preparing: average preparing time is 1 min(s) 7 sec(s)

Small adjustments... but in general good to go. Thx @russgove and sorry for the massive delay for processing this one.

OPS Build status updates of commit 53682dd:
:clock10: Incremental building: average incremental building time is 46 sec(s)

OPS Build status updates of commit 53682dd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/debug-modern-pages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


export-all.macro

What you did:
made https://github.com/lifeiscontent/export-all.macro
What happened:
tried to use this as a template, couldn't figure out how to publish
Reproduction repository:
https://github.com/lifeiscontent/export-all.macro
Problem description: I'd like to make an export-all.macro
Suggested solution: figure out what I need to change about kcd-scripts/.travis.yml to get it to deploy.

Looking at the travis build log I saw this:
[release] semantic-release ERR! pre The GitHub user of the "GH_TOKEN" has not authenticated Travis CI yet. Go to https://travis-ci.com/, login with the GitHub user of this token and then restart this job.

My guess is if you do that then you can make it work.
Good luck.

@kentcdodds how do you generally bootstrap a project to inject the tokens into CI? I believe when you call semantic-release-cli setup it does it, but I'm not sure if the same hooks with catch with kcd-scripts

I use semantic-release-cli setup.

@kentcdodds sorry, last question. how in a macro can I check what is the current file I'm using the macro in? I think right here: https://github.com/lifeiscontent/export-all.macro/blob/551bfce73ddff831b78aba350926680080db0cac/src/macro.js#L34-L36
I should filter the list of exports if you're trying to export the file you're in.

I think this is what you're looking for: https://github.com/lifeiscontent/export-all.macro/blob/551bfce73ddff831b78aba350926680080db0cac/src/macro.js#L26

Hey @kentcdodds, thanks for your help. I've been able to fix all the bugs in the code. I also updated travis with the tokens, but for some reason semantic release says there are no relevant changes to the code so it won't release a new version. Any ideas what this is about?


Instead of failing log a waring if PoET is missing during migration

Motivation
If a PoET isn't in the config of the node during local DB migration the migration will fail. This changes the code to only print a warning in this case and removing the PoET registration from the state.
Description
mainnet-poet-2 has been removed from code in #5640 causing a migration of the local state to fail when the node still has a registration for that PoET.
NOTE: If a user hasn't setup their config correctly this change will not migrate their local state correctly - possibly causing them to lose an epoch of rewards, while before the node would fail with an error during startup.
Test Plan
existing tests were updated for the new behavior.
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge

bors cancel

bors merge


Build failed to complete successfully.

Build succeeds, but console reports that "Build failed to complete successfully."
region: us-east-2
app Id: d4kqileokj5kp
AWS Amplify
2021-09-13T02:55:05.238Z [INFO]: # Cloning repository: git@github.com:GraphVisualizer/graph-visualizer.git
2021-09-13T02:55:05.269Z [INFO]: Agent pid 133
2021-09-13T02:55:05.295Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-09-13T02:55:05.461Z [INFO]: Cloning into 'graph-visualizer'...
2021-09-13T02:55:05.747Z [INFO]: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2021-09-13T02:55:06.234Z [INFO]: # Switching to commit: 163bb913963904d34e2e4bd490ce9806b238b239
2021-09-13T02:55:06.250Z [INFO]: Agent pid 146
2021-09-13T02:55:06.251Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
                                 Note: switching to '163bb913963904d34e2e4bd490ce9806b238b239'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at 163bb91 change contact name
2021-09-13T02:55:06.257Z [INFO]: Successfully cleaned up Git credentials
2021-09-13T02:55:06.257Z [INFO]: # Checking for Git submodules at: /codebuild/output/src318770854/src/graph-visualizer/.gitmodules
2021-09-13T02:55:06.280Z [INFO]: # Retrieving environment cache...
2021-09-13T02:55:06.305Z [INFO]: # Retrieved environment cache
2021-09-13T02:55:06.305Z [INFO]: ---- Setting Up SSM Secrets ----
2021-09-13T02:55:06.305Z [INFO]: SSM params {"Path":"/amplify/d4kqileokj5kp/master/","WithDecryption":true}
2021-09-13T02:55:06.336Z [WARNING]: !Failed to set up process.env.secrets
2021-09-13T02:55:06.344Z [INFO]: # Retrieving cache...
2021-09-13T02:55:06.579Z [INFO]: # Extracting cache...
2021-09-13T02:55:06.587Z [INFO]: # Extraction completed
2021-09-13T02:55:16.959Z [INFO]: ## Starting Backend Build
                                 ## Checking for associated backend environment...
                                 ## No backend environment association found, continuing...
                                 ## Completed Backend Build
                                 ## Starting Frontend Build
                                 # Starting phase: preBuild
                                 # Executing command: npm ci
2021-09-13T02:55:27.766Z [INFO]: ><EMAIL_ADDRESS>postinstall /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/babel-runtime/node_modules/core-js
                                 > node -e "try{require('./postinstall')}catch(e){}"
2021-09-13T02:55:27.808Z [INFO]: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                                 The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
                                 > https://opencollective.com/core-js
                                 > https://www.patreon.com/zloirock
                                 Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2021-09-13T02:55:27.838Z [INFO]: ><EMAIL_ADDRESS>postinstall /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/ejs
                                 > node ./postinstall.js
2021-09-13T02:55:27.874Z [INFO]: Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
2021-09-13T02:55:28.041Z [INFO]: ><EMAIL_ADDRESS>install /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/webpack-dev-server/node_modules/fsevents
                                 > node install.js
2021-09-13T02:55:28.078Z [INFO]:
2021-09-13T02:55:28.078Z [INFO]: Skipping 'fsevents' build as platform linux is not supported
2021-09-13T02:55:28.106Z [INFO]: ><EMAIL_ADDRESS>install /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/watchpack-chokidar2/node_modules/fsevents
                                 > node install.js
2021-09-13T02:55:28.143Z [INFO]:
2021-09-13T02:55:28.143Z [INFO]: Skipping 'fsevents' build as platform linux is not supported
2021-09-13T02:55:28.287Z [INFO]: ><EMAIL_ADDRESS>postinstall /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/core-js
                                 > node -e "try{require('./postinstall')}catch(e){}"
2021-09-13T02:55:28.673Z [INFO]: ><EMAIL_ADDRESS>postinstall /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer/node_modules/core-js-pure
                                 > node -e "try{require('./postinstall')}catch(e){}"
2021-09-13T02:55:28.817Z [INFO]: added 2010 packages in 11.11s
2021-09-13T02:55:28.832Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
2021-09-13T02:55:28.833Z [INFO]: # Executing command: npm run build
2021-09-13T02:55:28.987Z [INFO]: ><EMAIL_ADDRESS>build /codebuild/output/src318770854/src/graph-visualizer/graph-visualizer
                                 > react-scripts build
2021-09-13T02:55:30.263Z [INFO]: Creating an optimized production build...
2021-09-13T02:55:53.314Z [INFO]: Compiled successfully.

You need to make sure that their IAM role associated to the Amplify App has access to Secrets Manager and KMS keys to decrypt the secrets.

Hello, attaching a service role to the app solved this problem, but only partially. At first I got the following message:
There was an issue connecting to your repo provider, click "Reconnect repository" in General Settings, and then try your build again.
I In order to fix this problem, I tried adding several permissions to the service role:

SecretsManagerReadWrite
AWSCodeCommitFullAccess
AWSCodeDeployFullAccess
AWSKeyManagementServicePowerUser
AWSCodeBuildAdminAccess
AdministratorAccess-Amplify

This made the initial message go away, but the build is still failing successfully. Is there a reason for this? Thanks so much for your help.

Additional help would be highly appreciated, if they could be given! I really have no idea what's happening when the logs show that the build completes successfully.

i am facing th same issue

2022-01-05T08:15:07.687Z [INFO]: Git SSH Key acquired
2022-01-05T08:15:07.758Z [INFO]: # Cloning repository: git@github.com:Quidich-Innovation/stats-platform.git
2022-01-05T08:15:07.858Z [INFO]: Agent pid 136
2022-01-05T08:15:07.883Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2022-01-05T08:15:08.089Z [INFO]: Cloning into 'stats-platform'...
2022-01-05T08:15:08.799Z [INFO]: Warning: Permanently added the ECDSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2022-01-05T08:15:11.160Z [INFO]: # Switching to commit: 44eba4fc4e7b1b42e359bfc02d384de87cbfaafd
2022-01-05T08:15:11.258Z [INFO]: Agent pid 149
2022-01-05T08:15:11.259Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
Note: switching to '44eba4fc4e7b1b42e359bfc02d384de87cbfaafd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 44eba4f update built auth and CI CD in amplify
2022-01-05T08:15:11.265Z [INFO]: Successfully cleaned up Git credentials
2022-01-05T08:15:11.265Z [INFO]: # Checking for Git submodules at: /codebuild/output/src317879887/src/stats-platform/.gitmodules
2022-01-05T08:15:11.284Z [INFO]: # Retrieving environment cache...
2022-01-05T08:15:11.336Z [INFO]: # Retrieved environment cache
2022-01-05T08:15:11.336Z [INFO]: ---- Setting Up SSM Secrets ----
2022-01-05T08:15:11.336Z [INFO]: SSM params {"Path":"/amplify/d3fnr419kkzs0s/staging/","WithDecryption":true}
2022-01-05T08:15:11.365Z [WARNING]: !Failed to set up process.env.secrets
2022-01-05T08:15:11.366Z [WARNING]: ! Unable to patch packages...
2022-01-05T08:15:11.374Z [WARNING]: !TypeError: Cannot read property 'trim' of undefined
2022-01-05T08:15:11.375Z [ERROR]: !!! TypeError: Cannot read property 'trim' of undefined
2022-01-05T08:15:11.375Z [INFO]: # Starting environment caching...
2022-01-05T08:15:11.375Z [INFO]: # Uploading environment cache artifact...
2022-01-05T08:15:11.440Z [INFO]: # Environment caching completed
Terminating logging...

Try this guide if you don't already have a service role for Amplify deployments: https://docs.aws.amazon.com/amplify/latest/userguide/how-to-service-role-amplify-console.html


pytest --pyargs is broken by test_examples.py

To Reproduce
Steps to reproduce the behavior:

pip install --pre napari[pyqt5,testing] in a fresh environment
run pytest --pyargs napari

Error:
 $ NAPARI_POPUP_TESTS=1 pytest --pyargs napari
============================= test session starts ==============================
platform darwin -- Python 3.8.5, pytest-6.2.1, py-1.10.0, pluggy-0.13.1
PyQt5 5.15.2 -- Qt runtime 5.15.2 -- Qt compiled 5.15.2
rootdir: /Users/jni
plugins: napari-plugin-engine-0.1.9, timeout-1.4.2, qt-3.3.0
collected 1610 items / 1 error / 1609 selected

==================================== ERRORS ====================================
_ ERROR collecting conda/envs/napari-043rc/lib/python3.8/site-packages/napari/_tests/test_examples.py _
conda/envs/napari-043rc/lib/python3.8/site-packages/_pytest/python.py:1309: in _idval
    generated_id = idfn(val)
conda/envs/napari-043rc/lib/python3.8/site-packages/napari/_tests/test_examples.py:39: in <lambda>
    ???
conda/envs/napari-043rc/lib/python3.8/pathlib.py:1038: in __new__
    self = cls._from_parts(args, init=False)
conda/envs/napari-043rc/lib/python3.8/pathlib.py:679: in _from_parts
    drv, root, parts = self._parse_args(args)
conda/envs/napari-043rc/lib/python3.8/pathlib.py:663: in _parse_args
    a = os.fspath(a)
E   TypeError: expected str, bytes or os.PathLike object, not NotSetType

I'm not sure what the best fix is... The quick fix is to remove test_examples.py from the distribution. I don't think the examples themselves are even packaged?
We should also create an element in the test matrix to test in this way, to make sure we catch this in the future. I think we had one but I guess it was lost in the move to GitHub Actions. I'm not quite sure how to do this with tox, though. My guess is to add an entry pyargs here that does cd; pytest --pyargs napari, and then add an entry to the test matrix that adds that tox setting? CC @tlambert03

good catch, sorry about that.
for fixing the test itself, we could either exclude test_examples.py in MANIFEST.in as you say ... or we can add a pytest.skip marker to the test if it doesn't find the examples folder.  preference @jni?
I'm working on the best way to test it.  This is made kind of tricky at the moment, because we are temporarily skipping test_examples on CI due to segfault issues that need to be figured out (#2094).  So, we need to make that skip a little more refined, otherwise pytest --pyargs napari will work no matter what we do.  options include:

have a github actions test where we skip the checkout step, and simply pip install directly from github, specifying the commit sha: pip install pip install git+git://github.com/${{ github.repository }}.git@${{ github.sha }}#egg=napari[all,testing] (here is an example of that ... currently passing because of the CI skip mentioned above)
do something with tox.  I don't think the cd strategy is going to work (tested locally, still passed)... Interestingly, this is an argument for having a src directory in the repo (ugly though it may be).  There is a very good blog post (and links) on this exact issue here, and advice from pytest here (these have led me to adopt the src layout in other packages with more complicated builds).
we could go ahead and include the examples as a seperate package in the sdist!  rename them to napari_examples (so they are next to napari in the site-packages folder)... we could also modify our cli so that someone could do napari demo add_image

thoughts @jni?

good catch, sorry about that.
for fixing the test itself, we could either exclude test_examples.py in MANIFEST.in as you say ... or we can add a pytest.skip marker to the test if it doesn't find the examples folder.  preference @jni?
I'm working on the best way to test it.  This is made kind of tricky at the moment, because we are temporarily skipping test_examples on CI due to segfault issues that need to be figured out (#2094).  So, we need to make that skip a little more refined, otherwise pytest --pyargs napari will work no matter what we do.  options include:

have a github actions test where we skip the checkout step, and simply pip install directly from github, specifying the commit sha: pip install pip install git+git://github.com/${{ github.repository }}.git@${{ github.sha }}#egg=napari[all,testing] (here is an example of that ... currently passing because of the CI skip mentioned above)
do something with tox.  I don't think the cd strategy is going to work (tested locally, still passed)... Interestingly, this is an argument for having a src directory in the repo (ugly though it may be).  There is a very good blog post (and links) on this exact issue here, and advice from pytest here (these have led me to adopt the src layout in other packages with more complicated builds).
we could go ahead and include the examples as a seperate package in the sdist!  rename them to napari_examples (so they are next to napari in the site-packages folder)... we could also modify our cli so that someone could do napari demo add_image

thoughts @jni?

we could go ahead and include the examples as a separate package in the sdist! rename them to napari_examples (so they are next to napari in the site-packages folder)... we could also modify our cli so that someone could do napari demo add_image

I like this idea, or something similar, I think shipping the examples is nice and a good way to get someone started with napari.

we could go ahead and include the examples as a separate package in the sdist! rename them to napari_examples (so they are next to napari in the site-packages folder)... we could also modify our cli so that someone could do napari demo add_image

I like this idea, or something similar, I think shipping the examples is nice and a good way to get someone started with napari.


Run CI on Perlmutter

Action Items

[ ] Rename https://github.com/buildtesters/buildtest/blob/devel/.gitlab/cori.yml file to something like nersc.yml
[ ] Rename https://github.com/buildtesters/buildtest/blob/devel/tests/test_cori.py to test_nersc.py and add method to run on Perlmutter
[ ] Make use of new gitlab runner to run jobs via user bdtest

This looks like a duplicate of #1302, could these issues be combined if you're just going to make it a big checklist?

So this task depends on #1302 and will require a fair bit of development, code-review whereas #1301 is a special type of issue that doesn't require any contribution to buildtest. It just requires setting up the gitlab runner/jacamar so that we can perform this task. Typically all issues have contribution to project that can be linked with MR, but in this case we just need to setup runner.
I'd prefer these tasks be separate to make it easier for @prathmesh4321 to work on smaller set of changes.


This code repository does not support CentOS！

Because Playwright is not supported on it.

Emm... sorry about this.
We use Playwright since it is probably the easiest-to-use screenshot-taking tool.
If you have other suggestions, feel free to share them with us!


[WIP]feat(datasync): add TTL

This PR adds TTL for datasync
TODO

[ ] Docs

Looks good so far. Let's get docs fixed first. Then we can updated docs in this PR.
I do not want to loose this change (being undocumented etc.)

Can we get that in. I would love new alpha for testing


How to include the scrape configs in conf.d in Prometheus main configuration?

@raphink I'm a bit confused about this... the tool generates the scrape configs in the conf.d directory but how are these expected to be included into prometheus main configuration?
AFAIK, there's no include option in prometheus (except for rules and file_sd targets).
Am I missing something?

Well I just saw your relabeling comment after the release of v0.6.0. I didn't know we can override metrics_path and scheme that way (is it also possible for credentials?).
I think it's a good idea, so that we only have one target file and we don't touch the main configuration file. I'll try to implement this in the next release (unless you want to do it first). But at least, now we can have more than one exporter per node.

These are the internal labels I'm sure we can manipulate through relabeling:
MetricNameLabel = "__name__"
SchemeLabel = "__scheme__"
AddressLabel = "__address__"
MetricsPathLabel = "__metrics_path__"

source: https://github.com/prometheus/common/blob/0d5de9d6d8629cb8bee6d4674da4127cd8b615a3/model/labels.go#L32-L46
However, there's also the __param label prefix, which I believe can be used to set the authentication values (i.e. username, password) by adding the following labels to the targets, like so:
- targets:
  - x.x.x.x:1234
- labels:
    __param_password: 'somepass'
    __param_username: 'someuser'

I have not tested/validated this, but I believe this may work.
In any case, this needs to done/considered very carefully as this will include the credentials in the sd files...

@dannyk81 I close this issue as I think it is not relevant anymore. Please feel free to reopen if it is not the case.


Boolean radio buttons

The generated boolean radio buttons look a bit weird, especially the second one.
Shouldn't booleans be handled as checkboxes? (just personal preference)

@Mythos please check now it might be working.

It's fine now, thanks.


Antivirus software false positive?

Brief Description: Emsisoft antivirus sees the installer as a virus.
Operating System (OS and version): Windows 10
OpenBazaar version (shown on About OpenBazaar page in menu): 2.0.11
Hardware:
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Always
Steps to reproduce:

Execute installer with Emsisoft antivirus

Observed Behavior: False positive, file gets quarantined

This is due to the Squirrel auto-updater, sometimes anti-virus software flags it as a virus.
It's a known issue, we haven't found a way around it yet.


Port to Firefox

Hi @dutiyesh,
Thanks for your work.  This extensions is pretty cool.
Are you interested in any way to port this extension to Firefox or would you accept a pull request that does that?
The API's are pretty much the same and the hole process is painless. Here's a couple links with documentation:

https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension/
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs

Thanks!

Thank you @petre2dor ,
I am planning to add Firefox support but I can also accept a pull request.

https://addons.mozilla.org/en-US/android/addon/navigate-netflix-with-keyboard/

@dutiyesh like most Chrome extensions it just worked in Firefox. It had a warning regarding persistent false https://github.com/dutiyesh/netflix-navigator/blob/0c30b48dbdeaf59ec177de47cc7e271b86af7c45/public/manifest.json#L14


Why is this result?

Hi,
This code raises an InvalidOperationException.
I have not deleted the entity.
public class NewBehaviourScript : MonoBehaviour
{

    // Use this for initialization
    void Start ()
    {
        var context = Contexts.sharedInstance.game;
        var newEntity = context.CreateEntity ();
        newEntity.AddGameObject (gameObject);

        var entities = context.GetEntitiesWithGameObject (gameObject);
        foreach (var e in entities)// InvalidOperationException: HashSet have been modified while it was iterated over
        {
            e.RemoveGameObject ();
        }
    }
}

[Game]
public class GameObjectComponent : IComponent
{
    [EntityIndex]
    public GameObject gameObject;
}

Thanks :)

For performance reasons context.GetEntitiesWithGameObject returns the internal hashset used to store the entities. As with many other collections, you cannot modify them while iterating over them. There are 2 recommended options:
1.
var group = context.GetEntitiesWithGameObject(gameObject);
foreach (var e in group.GetEntities()) {
    e.RemoveGameObject();
}

This returns a new array which makes it safe to modify the hashset. The array is cached, meaning if you call GetEntities() multiple times without while the group hasn't changed you don't allocate unnecessary memory. However, a new array will be created once the group changes.

// instance var
readonly List<GameEntity> _buffer = new List<GameEntity>();

var group = context.GetEntitiesWithGameObject(gameObject);
foreach (var e in group.GetEntities(_buffer))
{
    e.RemoveGameObject();
}

This will fill the buffer. Useful if the group is expected to change often. You manage the memory manually with the buffer, avoiding to create many arrays

Thank you for the quick response.
I understood your intentions.
By the way,
var group = context.GetEntitiesWithGameObject(gameObject);

Is this function generated automatically?

Yes, because you use [EntityIndex]
You can do gameObject - entity relations with EntityLink

To me, the group type looks like a HashSet.
Where are GetEntities() defined?

🤦♂ sorry :) I was somewhere totally different in my head. It's not about groups, it's about the entity index, my bad.
Just use ToArray()
var entities = context.GetEntitiesWithGameObject(gameObject);
foreach (var e in entities.ToArray()) {
    e.RemoveGameObject();
}```

This problem was resolved thanks to your support.

Great to hear!


Set human readable time format for logger

Signed-off-by: sahare<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/25372

@sahare we also need this cherrypicked in 2.6 so it gets picked up by the 2.6.1 stream

/cherry-pick release-2.6


Display bug in the main menu in the software.

Type: Bug
In the latest update, the window action icons in Windows (close minimize and expand) hide part of the top menu in the software, and prevent access to the file tab.

VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:36:10.600Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

same issue here, I didn't see this issue ticket was open before I opened mine so there is a duplicate one

Duplicate of #159813 (newer but has a more descriptive title)


TabSet does not follow parent return values. Affects all versions.

Hi, I noticed that TabSet doesn't appear to be consistently following the return values of it's parent class CompositeField for a few methods of interest to me, particularly ->insertBefore() and ->insertAfter(). The framework's API is already very limited with respect to the ability to recursively find fields, so I ended up needing to resort to these methods to see if a composite field existed (for my unit testing) since only DataFields can currently be found recursively.
Anyway -- I noticed that even though it appears that FieldList and CompositeField were returning a non-null value if it was able to insert before/after, I should be good -- but no matter what, I could never get the result I needed. Here is the reason: https://github.com/silverstripe/silverstripe-framework/blob/3/forms/TabSet.php#L154
The end of this method isn't returning anything, so that completely mitigates most situations where at least I could find this useful (e.g. ->getCMSFields() which always has a TabSet if I recall).
Question: I can fix this easily. What branch should I put this in? I'm currently using 3.1.

I'll let someone else decide where a change like this should go, but I feel your pain on form field traversal. See https://groups.google.com/forum/#!topic/silverstripe-dev/c3RajiT7gMI for some ideas about this and feel free to reply there if you have anything to add. If we can get some discussion going on it maybe we can get to RFC stage and improve the situation for 4.0.

@jonom Ok thanks. I'm going ahead with just 3 since nothing else is going really into 3.2 (since it's almost "stable" I guess, even though I think this would make it more stable) nor are items going into 3.1 unless they're serious, so 3 is the safest bet for now.
Yeah this is definitely in need of an API overhaul due to the legacy nomenclature clashing with other methods (unrelated, but using different prefixes like "find" or suffixes like "ByName"). I was thinking a recursive function could be like ->findByName() but you end up with with another method that is confusingly similar but implements dot notation (->fieldByName()). I don't even want to get started on that . . .
This is a very common issue. So much so, in fact, that you've got loads of duplicated code to accomplish similar tasks when all you'd need to do is abstract that functionality and just reuse it internally/externally. Boom. Cleaner code and less hacks. For now, I'll proceed with my unit tests by using ->insertAfter() which does the work for me and (for the love of god) hope that my PR https://github.com/silverstripe/silverstripe-framework/issues/4664 gets released into the wild soon so I'm not maintaining so many hacks! Even then it's a bit of a hack. :tired_face:

@jonom  By the way it may make sense to submit a new issue about that as well. Since technically it would be an API change, I'm sure it could go into master (v4) and of course then that might require an API change and open a can of worms and... I can tell I'm talking myself out of it already.

3 is a good default branch for new changes. that's why it's the default for the github repo. :)

@patricknelson The discussion policy for SilverStripe is a bit confusing, but I think issues are only meant for bug reports and RFCs, so might not be appropriate to raise an issue to discuss improving something. I've tried to summarise where to discuss what here as I think it can be confusing for everyone: https://groups.google.com/forum/#!topic/silverstripe-dev/DeLEi8yl0ew

Closing since this has been merged! Thanks @jonom and @tractorcow (do you ever sleep?)


Support PKCE for OAuth 2.0 in our OAuthBackend class

Beginning working on a backend for Airtable, I faced an issue that our OAuthBackend doesn't support the authorization parameter rules, which are mandatory for Airtable.
It turned out those rules are a part of the PKCE extension of OAuth. And it looks like those rules might become a part of the backends we might decide to support in the future. So it would be nice if we could support the PKCE extension of OAuth and allow backends to opt it in.

We should definitely support this. Not sure if in the OAuthBackend or in a subclass (PKCEOAuthBackend?), it depends on how different it is from the current flow. The code you linked to is too much code to process, what are the actual differences of PKCE?


fix non standard implementation of getattr

According to the the docs, a __getattr__ magic method should either return a value for the requested attribute name, or raise AttributeError.
A __getattr__ method was added to the TokenUser class that allows accessing keys on the token as if they were attributes of the TokenUser class.  In the current implementation, if the requested attribute name is not a key in the token dictionary, then None is returned instead of raising AttributeError.
When Django's auth backend ModelBackend does permission checks on a user object, it first checks for an attribute named _perm_cache with hasattr, then builds the cache if it doesn't exist.  Since hasattr incorrectly returns True for a TokenUser instance, the cache (which would have resolved to an empty set) is never created.  This ultimately results in a TypeError because None is not Iterable.

Not sure if this is backwards compatible, but makes sense.

This will break backwards compatibility in the specific case where you try to access an attribute on a token user instance when that attribute does not exist on the instance itself and does not exist as a key in the token.  This is a case that should be handled defensively using an exception handler, a hasattr check, or a getattr call with a default value.
In the case where the name of the attribute is known to always exist on the token, this is not a breaking change.
In my case, I was updating the dependencies of an older Django application, and the addition of the __getattr__ method caused the app to crash on has_perm checks for non admin users.  If this fix ins't accepted, my other option is to use the TOKEN_USER_CLASS setting to subclass TokenUser and just fix it in my project.