Add type wrapper

Add basic type Wrapper Implementation.
This change allows users to define type wrapper for objects out of their control. An example usage would be to create a ConfigTypeWrapper for Identifier, so mod creators can easily use this to have config values for things in a registry.
This also supports recursive lookups so someone can add their wrapper from Identifier to EntityType and use a provided String to Identifier wrapper.
Limitations that are going to be adressed if this is an acceptable implementation:

Reflective Configs don't support ConfigTypeWrappers
ConfigSections don't support ConfigTypeWrappers, because they don't have access to the ConfigTypeWrapper in the ConfigImpl
NightConfigSerializer doesn't support Child Classes, because it doesn't use the default value in it's  serialization

New maintainer here--I'll get to this PR eventually, but it's going to have to sit on the backburner for a while longer.
I'm currently concerned with a 2.0 branch where i'm experimenting with changes (breaking or not) that improves the current API structure. I'm interested in this feature, but I won't be able to give any feedback until I've figured out this codebase and probably made some big changes.

Bumping this pr for @TheGlitch76

closing this due to inactivity. feel free to reopen if you ever come back to it!


Solr - ulimits increase to avoid container crash

The Problem/Issue/Bug:
Upon using DDEV with Solr, I faced with this problem:
https://superuser.com/questions/1413352/running-jdk-8-in-docker-suddenly-broken-on-arch-linux-with-unable-to-allocate-f/1413390#1413390
The Solr 6.6 container exits immediately after start with this error message:
library initialization failed - unable to allocate file descriptor table - out of memory

in docker log

ddev version v1.8.0
Docker version 18.09.6, build 481bc77
docker-compose version 1.23.2, build 1110ad01
OS: Linux hrabal 5.1.9-300.fc30.x86_64 #1 SMP Tue Jun 11 16:17:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
How this PR Solves The Problem:
It increases the ulimits for the Solr container.
Manual Testing Instructions:
Start a DDEV project with Solr available. See if the Solr container exits immediately or not.
Automated Testing Overview:
If the Solr container is already covered by tests, this configuration is covered as well. If it isn't, it might be out of scope to add the full Solr bootstrapping as a new test for this fix.

Could you say more about your environment? On macOS with Docker Desktop, the solr 6.6 container starts up with 1M of available file descriptors, so this would lower the available FDs significantly.
rfay@rfay-mbp-2017:~/workspace/d8git/.ddev$ ddev ssh -s solr
$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     0
memory(kbytes)       unlimited
locked memory(kbytes) 82000
process              unlimited
nofiles              1048576
vmemory(kbytes)      unlimited
locks                unlimited
rtprio               0

Is it possible that your docker environment is set up with restricted nofiles?

@rfay
Still not sure why I needed this patch.

If I launch the image standalone, it does have a quite high open files limit.
Possibly related to docker-compose then.

Please provide your full docker-compose.solr.yaml (or whatever you call it). And are you working on Linux? If so I can try to recreate there. I'm surprised you don't have the open files issue with a standalone docker run.

@rfay
The docker-compose.solr.yaml
https://pastebin.com/dZ1m8LWR
Yep, I am under Linux:
Fedora 29
Linux villamvonat 5.1.11-200.fc29.x86_64 #1 SMP Mon Jun 17 19:30:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

The YML file is 100% identical to the one in the repository, the only difference is the workaround I made, nothing else.

I tested on Ubuntu 18.04 and got the same result with ulimit -a inside the solr container, open files                      (-n) 1048576

It does sound like this is something unique about your host or docker situation, and I'd love to figure out what that is/was. It doesn't sound like the PR is necessary, but the solving/understanding certainly is.

Should we close this @AronNovak or does it have a future?

@rfay
As you convinced me that it is environment specific and after https://github.com/drud/ddev/pull/1657#issuecomment-506308562 , I'd say it does not worth to dig deeper here.

Well, your effort on this and attention to it are much appreciated. Maybe someday we'll understand what was going on here.


Added hashedComm creation of email and sms

This PR was successfully deployed to production by CircleCI build 268 at 2017-10-18 14:18 BST.


Hide status and IAC buttons and display message if CE closed

 SUS055: UAC cannot be generated if the collection exercise has closed (5)

Attached screenshot to description.

On hold while we investigate the date comparisons.


Update async-mqtt-client dependency version

The dependency AsyncMqttClient is currently set to version 0.5.0 in library.json.  Can it please be updated to 0.8.0 so platformio behaves.

Seems to be worse than that. Not only is release 0.5.0 no longer available to download (I'm using the Arduino IDE), trying to use v0.8.0 gives other errors:
n file included from C:\OD\arduino\sketches\libraries\async-mqtt-client-0.8.0\src/AsyncMqttClient.h:4:0,

                 from C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1\src/Homie.hpp:5,

                 from C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1\src/Homie.h:4,

                 from C:\OD\arduino\sketches\Homie2\Homie2.ino:1:

C:\OD\arduino\sketches\libraries\async-mqtt-client-0.8.0\src/AsyncMqttClient.hpp:8:25: fatal error: ESPAsyncTCP.h: No such file or directory

 #include <ESPAsyncTCP.h>

                         ^

compilation terminated.

Multiple libraries were found for "Homie.h"
 Used: C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1
 Not used: C:\OD\arduino\sketches\libraries\homie-esp8266-1.5.0
exit status 1
```

Have you installed the ESPAsyncTCP library?
Le 17 juin 2017 4:39 PM, "Julian Knight"<EMAIL_ADDRESS>a
écrit :

Seems to be worse than that. Not only is release 0.5.0 no longer available
to download (I'm using the Arduino IDE), trying to use v0.8.0 gives other
errors:
n file included from C:\OD\arduino\sketches\libraries\async-mqtt-client-0.8.0\src/AsyncMqttClient.h:4:0,
             from C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1\src/Homie.hpp:5,

             from C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1\src/Homie.h:4,

             from C:\OD\arduino\sketches\Homie2\Homie2.ino:1:

C:\OD\arduino\sketches\libraries\async-mqtt-client-0.8.0\src/AsyncMqttClient.hpp:8:25: fatal error: ESPAsyncTCP.h: No such file or directory
#include <ESPAsyncTCP.h>
                     ^

compilation terminated.
Multiple libraries were found for "Homie.h"
Used: C:\OD\arduino\sketches\libraries\homie-esp8266-2.0.0-beta.1
Not used: C:\OD\arduino\sketches\libraries\homie-esp8266-1.5.0
exit status 1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/marvinroger/homie-esp8266/issues/358#issuecomment-309218999>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA8eNbb2chGHDsYJZPLswseFgYUNxWctks5sE-UzgaJpZM4N9MBa>
.

Urg! OK, missing dependency - thanks. Appears to be working now without any changes and with v0.8.0 as expected.

Fixed: https://github.com/marvinroger/homie-esp8266/commit/cd2fa9f88bbd9e2746901cf846e5894785663d79


Provide a vue-cli-plugin to write vue plugin out of box

What problem does this feature solve?
Vue-cli 3.x is really a big progress for start a vue program instantly, but today when I want to write a vue plugin, things seems still tough. Since vue plugin is not the same with vue program, I need to config webpack, postcss, etc. The documents in vuejs.org says that how to write a plugin, but there was no docs about how to config when I am writing plugin.
I've find a vue-cli 2.0 template for this purpose: https://github.com/posva/vue-plugin-template . In Vue-cli 3.x, It seems we can provide a vue-cli-plugin to solve this problem. Could anyone give me some advice? Thank you very much!
What does the proposed API look like?
Provide a vue-cli-plugin, we could select it in the prompt when we use vue create awesome-plugin.

vue-cli 3 gives you all of the basic tools to compile a plugin as a lib, see here:
https://cli.vuejs.org/guide/build-targets.html#library
For additional boilerplate / preconfiguration, a plugin from the community can be provided - especially using rollup to compile the plugin, like the template that you linked to does, is out of scope of vue-cli itself - we focus on webpack.

I also find out that vue-cli build-target could do that, thank you for your patiently answer.


WriteCopytoURL usage is leading to more crashes on next launch

Hi,
I have been trying to use the writeCopyToURL when the app is going to background, this is reducing the Realm file size, but when i re-launch the app there are places where i m creating a Realm instance inside a dispatch queue those are not getting created and ignoring the complete code, and its crashing due to some old references, i have been trying to figure out to fix this but unable to.
my app has become more unstable and don't know when it crashes, it might to trying to refer to some of the old realm references.
code:
if (![RLMRealm defaultRealm].inWriteTransaction) {

//        [[RLMRealm defaultRealm] invalidate];
    __block BOOL copySuccess = NO;
    NSURL *realmURL = [[RLMRealmConfiguration defaultConfiguration] fileURL];
    NSString *copyPath = [realmURL.path<EMAIL_ADDRESS>    @autoreleasepool
    {
        [[NSFileManager defaultManager] removeItemAtPath:copyPath error:nil];
        copySuccess = [[RLMRealm defaultRealm] writeCopyToURL:[NSURL URLWithString:copyPath] encryptionKey:nil error:nil];
    }

    if (copySuccess && [[NSFileManager defaultManager] removeItemAtPath:realmURL.path error:nil])
    {
        NSError *err;
        [[NSFileManager defaultManager] copyItemAtPath:copyPath toPath:realmURL.path error:&err];
    }

}

can someone guide me with best practise please.
Realm version: 100.0
Xcode version: 7.2
iOS/OSX version: 9.0.2

Hi @slreddy1137, as a best practice, I'd recommend not replacing the Realm file as you're accessing it. This is likely to cause file corruption and depending on timing, a variety of crashes.
To use a compacted copy of the Realm file, I'd recommend performing the copy as the very first step in your application, before any other code has had the chance to access the Realm file.
Or alternatively, don't replace the Realm file you're accessing, just start using Realms at the new location.

Hi @jpsim , i have not created any Realm files from the project, i m directly using the "Default Realm" instances which internally creating the Realm file.

To perform copy as the very first step : shall i do it in "didFinishLoading" everytime ?

Alternate approach : as the default Realm is in Documents folder, can u please suggest me how to start using Realms at new location.

shall i do it in "didFinishLoading" everytime ?

That depends, do you have any code accessing the Realm that runs before this? Like default property values in your view controllers loaded by storyboards?

Alternate approach : as the default Realm is in Documents folder, can u please suggest me how to start using Realms at new location.

There's a handy Realm initializer that takes in a location: https://realm.io/docs/objc/latest/api/Classes/RLMRealm.html#/c:objc(cs)RLMRealm(cm)realmWithURL:
Or you can set a value on the configuration: https://realm.io/docs/objc/latest/api/Classes/RLMRealmConfiguration.html#/c:objc(cs)RLMRealmConfiguration(py)fileURL

i m loading the data in viewDidLoad for few controllers, which is increasing the realm file size, in between of the app running i cannot make a copy right ?
Alternate approach:
do  i need to create realm file in a new location, if so how about the classes which are referring to old realm and its data.
sorry, to ask you more.

i m loading the data in viewDidLoad for few controllers, which is increasing the realm file size, in between of the app running i cannot make a copy right ?

I must be misunderstanding you here, you obviously can't run your application code in between runs of your application...

do i need to create realm file in a new location, if so how about the classes which are referring to old realm and its data.

If you create a new Realm file, you'll probably want to update any previous Realm-related objects to point to the updated version. This is very similar to the initial problem of replacing the Realm file while pre-existing objects were still accessing the previous file.

sorry, to ask you more.

No need to be sorry to ask for help, that's what we're here for! 😄

since the both approaches doesn't suit my scenario, how can i get the realm file size reduced, its increasing dramatically around 180MB and more

How about compacting the Realm file before any of your application code has a chance to access it? Performing the compaction prior to your UIApplication being created could work, as long as the compaction isn't so time consuming as to jetsam your app:
// main.m
#import <UIKit/UIKit.h>
#import "AppDelegate.h"
#import <Realm/Realm.h>

void CompactRealmFile() {
    __block BOOL copySuccess = NO;
    NSURL *originalURL = [[RLMRealmConfiguration defaultConfiguration] fileURL];
    NSURL *copyURL = [originalURL URLByAppendingPathExtension:@"copy"];
    NSFileManager *fileManager = [NSFileManager defaultManager];
    if (![fileManager fileExistsAtPath:copyURL.path] ||
        ([fileManager removeItemAtURL:copyURL error:nil])) @autoreleasepool {
        copySuccess = [[RLMRealm defaultRealm] writeCopyToURL:copyURL encryptionKey:nil error:nil];
    }

    if (copySuccess && [[NSFileManager defaultManager] removeItemAtURL:originalURL error:nil]) {
        NSError *err;
        if (![[NSFileManager defaultManager] copyItemAtURL:copyURL toURL:originalURL error:&err]) {
            NSLog(@"error copying Realm file: %@", err.localizedDescription);
        } else {
            NSLog(@"compacted Realm file");
        }
    }
}

int main(int argc, char * argv[]) {
    @autoreleasepool {
        @autoreleasepool { CompactRealmFile(); }
        return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
    }
}

I ll try this for sure, but my Realm file initially on the first time app launch it will not be available and this realm objects are loaded heavily by making service calls and fetch the data.

@slreddy1137 did you get this to work? any reason to keep this ticket open?

Hi,
Even after trying this approach I m seeing more unknown crashes, figuring out ways to get it fixed.
Sent from my iPhone

On 20-May-2016, at 7:33 PM, JP Simard<EMAIL_ADDRESS>wrote:
@slreddy1137 did you get this to work? any reason to keep this ticket open?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Even after trying this approach I m seeing more unknown crashes, figuring out ways to get it fixed.

If you show us how we can trigger crashes like these, we're happy to lend our time to look into them and help 😄 😄 😄

Sure, I ll get more details soon.
Sent from my iPhone

On 20-May-2016, at 8:00 PM, JP Simard<EMAIL_ADDRESS>wrote:
Even after trying this approach I m seeing more unknown crashes, figuring out ways to get it fixed.
If you show us how we can trigger crashes like these, we're happy to lend our time to look into them and help 😄 😄 😄
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@jpsim , we are still testing after making this changes in main.m for optimising the realm file, please give us 2 more days to confirm on the fix.

Looking forward to your results @slreddy1137!

Hi Simard,
I see the build is stable now, extensive testing is going on, I can confirm that it's a solution for me, the ticket can closed.
Sent from my iPhone

On 26-May-2016, at 2:46 PM, JP Simard<EMAIL_ADDRESS>wrote:
Looking forward to your results @slreddy1137!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

I'm thrilled to hear this @slreddy1137! Thanks for the update.

Thanks a lot for your support .
Sent from my iPhone

On 26-May-2016, at 5:54 PM, JP Simard<EMAIL_ADDRESS>wrote:
Closed #3513.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


feature request: edit a cells in a row

Hey, Shayan! Your tabiew is great ! It works fine, it opens and processes big parquet files. What do you think about editing feature? I know that parquet not allow update operations directly, but because of fact that opened parquet file already loaded into memory (as I think) (because of memory usage not a problem in modern computers), may you please add feature like that: a user in "v" mode see a row as a sheet, edit a cell field in opened sheet, toggle "v" and in rendered table mode we may see text changes? Then a user may export existing modified table as usual or reset changes. What do you think about that ?

This is pull request


Cannot test Web Extensions in WSL2 or Dev Containers

Type: Bug
Following instructions from here to start web extension in desktop VSCode from WSL2:

from here: https://code.visualstudio.com/api/extension-guides/web-extensions#test-your-web-extension
or here: https://github.com/microsoft/vscode-extension-samples/tree/main/lsp-web-extension-sample.

The extension is built fine but it's not shown when running Developer: Show Running Extension in [Extension Development Host] window and trying to run Hello World command fails saying that it is not found (even though command is visible in command palette).
Trying both VS Code desktop and @vscode/test-web options yields the same results.
Running non-web hello-world extension sample is working as expected though.
I also cannot find any relevant logs.

Maybe there's a problem with your main file?
Check the dev tools to see if there are any error messages.

I tested that running the hello world web extension works.

npm i -g yo generator-code
yo code, New Web Extension
open in code insiders, Run Web Extension from the debug viewlet
Run the command Hello World

Tried again, now using clean insiders install:

npm i -g yo generator-code
yo code, New Web Extension, name: repro, agreed to npm install
open in code insiders, Run Web Extension from the debug viewlet

On first launch I see this:

And then the launched Extension Development Host has no repro extension installed:

DevTools logs(Extension Development Host):

Dev

Note: this only happens with running from WSL or Dev Containers. Doing the same using windows terminal is working fine.

Also doing the same using VSCode installed directly in WSL (using WSLg) also works.
And my current workaround is to run VSCode CLI from WSL distro and use the web UI instead of connecting through Remote WSL extension.

Ah, sorry, now I understand. You want to run a web extension that is on a remote.
Maybe caused by https://github.com/microsoft/vscode/issues/144513

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

should this be closed? @alexdima @aeschli

Running a web extension in a remote setup is currently not supported.
You can use test-web instead.

1/ Your statement is only for the development scenario? So if I am developing a web extension + WSL => I cannot test it in VS Code.
Or 2/ the statement applies also for the runtime scenario. I.e. I published a web extension. And a user that tries my extension in WSL =>it won't work.

Running a web extension in a remote setup is currently not supported.

Yeah... That's a bummer. I am currently using VSCode through code --serve-web and the development experience here is pretty limited.

Running a web extension in a remote setup is currently not supported.

At our company we have the same issue and have been using Dev Containers for all our extension projects up until now, so this incompatibility is quite inconvenient. It's also taken me a while to figure out that this is an unsupported debugging scenario since it isn't documented elsewhere. It would be good if a statement could be added to this documentation for example before the feature becomes available.


Report issues for OpenMP within the ROCm compiler

Could you reproduce the following issues for offloading to an AMD GPU using OpenMP within the ROCm compiler ? When you can run any of the applications in my report successfully using your OpenMP within the ROCm compiler, please list them here. Then there may be some issues with my installation and/or build commands for these applications.
In each program with the suffix "-omp", there is a "Makefile.aomp". Please take a look at the file, and modify it for your environment. To build and run a program, go to a directory (e.g. all-pairs-distance-omp) and type
make -f Makefile.aomp run

Thanks.
The GPU results don't match the CPU results for the following OpenMP programs.
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/all-pairs-distance-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/compute-score-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/fft-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/amgmk-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/scan-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/axhelm-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/fpc-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/knn-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/lud-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/myoctye-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/nw-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/particlefilter-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/ccsd-trpdrv-omp
https://github.com/zjin-lcf/oneAPI-DirectProgramming/tree/master/crc64-omp
./main 10 5 33554432
Running 10 tests with seed 5
Loading global '_ZL11crc64_table' (Failed)
Libomptarget fatal error 1: failure of target construct while offloading is mandatory
make: *** [Makefile.aomp:65: run] Aborted (core dumped)

Thanks @zjin-lcf for reaching out.
Can you please respond with below answers.
/opt/rocm/bin/rocminfo
/opt/rocm/opencl/bin/clinfo
/opt/rocm/bin/rocm-smi

Hi @zjin-lcf
When I tried the first sample on my Radeon7 card, I got the below output.
/opt/rocm/llvm/bin/clang++ -std=c++14 -Wall  -O3 -target x86_64-pc-linux-gnu -fopenmp -fopenmp-targets=amdgcn-amd-amdhsa -Xopenmp-target=amdgcn-amd-amdhsa -march=gfx906 -c main.cpp -o main.o
/opt/rocm/llvm/bin/clang++ -std=c++14 -Wall  -O3 -target x86_64-pc-linux-gnu -fopenmp -fopenmp-targets=amdgcn-amd-amdhsa -Xopenmp-target=amdgcn-amd-amdhsa -march=gfx906 main.o -o main
./main
PASS
FAIL
Makefile.aomp:65: recipe for target 'run' failed
make: *** [run] Error 238

I omitted the outputs of these programs, which directly/indirectly indicate CPU/GPU results mismatch, when reporting the issues for clarity.  Thanks for bringing my report to AOMP developers.
Number of platforms:                             1
Platform Profile:                              FULL_PROFILE
Platform Version:                              OpenCL 2.0 AMD-APP (3204.0)
Platform Name:                                 AMD Accelerated Parallel Processing
Platform Vendor:                               Advanced Micro Devices, Inc.
Platform Extensions:                           cl_khr_icd cl_amd_event_callback
Platform Name:                                 AMD Accelerated Parallel Processing
Number of devices:                               1
Device Type:                                   CL_DEVICE_TYPE_GPU
Vendor ID:                                     1002h
Board name:                                    Vega 20 [Radeon VII]

Agent 2

Name:                    gfx906
Uuid:                    GPU-246660c172fd62df
Marketing Name:          Vega 20 [Radeon VII]
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    1
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 26287(0x66af)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1801
BDFID:                   8960
Internal Node ID:        1
Compute Unit:            60
SIMDs per CU:            4
Shader Engines:          4
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    16760832(0xffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx906
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

In regards to all-pairs-distance-omp, the failure is a result of the compiler choosing to execute the second offload region as a SPMD kernel, which in turn makes the dist array become thread private instead of team private.  When the reduction occurs, thread 0 will only see an entry in dist[0] and everywhere else will be zeroed as it cannot see changes from other threads. This causes the check to fail due to having partial results.
This should be a generic kernel as there is user code in between the target teams pragma and parallel region. Clang is explicitly looking over the int dist[THREADS] declaration because it is of a trivial type. For demonstration purposes if you add 'dist[0] = 0;' after line 151, the kernel will be generic and the test passes.
Looking into filing a clang bug.

In regards to all-pairs-distance-omp, the failure is a result of the compiler choosing to execute the second offload region as a SPMD kernel, which in turn makes the dist array become thread private instead of team private.  When the reduction occurs, thread 0 will only see an entry in dist[0] and everywhere else will be zeroed as it cannot see changes from other threads. This causes the check to fail due to having partial results.
This should be a generic kernel as there is user code in between the target teams pragma and parallel region. Clang is explicitly looking over the int dist[THREADS] declaration because it is of a trivial type. For demonstration purposes if you add 'dist[0] = 0;' after line 151, the kernel will be generic and the test passes.
Looking into filing a clang bug.

I don't know what a generic kernel means, and if "user code exists or not between the two parallel regions" matters.  Thank you for explaining the issues in any case.

I don't know what a generic kernel means, and if "user code exists or not between the two parallel regions" matters.  Thank you for explaining the issues in any case.

Hi @zjin-lcf
The reported issues are fixed long back. Request to check with the latest ROCm 5.0.
Closing this, as the failures are not seen anymore.
Thank you.


Hide ecc validation plugin with peer wrapper

Description
In order to use a FPC chaincode, our custom validation plugin must be used by setting it in the chaincode definition with -V ecc-vscc . For example:
${PEER_CMD} lifecycle chaincode approveformyorg -C ${CHAN_ID} --package-id ${PKG_ID} --name auction_test --version ${CC_VERS} -V ecc-vscc

As this may change in the future we would like to hide the use of ecc-vscc by embedding it into the peer wrapper script.
See discussion:

Wouldn't it be better to add the validation plugin inside the peer cli?  Mid/long-term some of these plugins will change for FPC, so it would be cleaner/easier from a functional interface point of view as the interface is simpler and would be the same even if we would move to MSP/X509 style validation.  As we anyway do not allow any user-provided plugins, the peer cli of course should also barf if any plugins provided (which it currently doesn't, e.g., if you provide an endorsement plugin, which by itself is also a bit of a problem?)

Originally posted by @g2flyer in https://github.com/hyperledger-labs/fabric-private-chaincode/pull/371
Link to dependent issues
#371 re-enables custom validation plugins for ecc and ercc

Shouldn't this be in Tech Preview milestone, not MVP? It defines the functional interface and so would be related to #358 !


test of linter

This pull request...

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

closing because this was created to debug github pull request actions,


add support for gdb path substitution

When debugging a binary, if the build environment is different from the debugging environment (e.g., built in Docker, debugging locally) you might see errors where the debugger isn't able to find the source files that match up with the binary.  This manifests in the extension as error messages in the debug console along the lines of "No source file named ...".
GDB solves this problem with "path substitutions" in a variable.  So if you build a binary in /root and want to debug it in /home/username you need to issue the command set substitute-path /root /home/username.
This PR adds a configuration option for launch.json that lets you set this.

Thanks for the suggestions.  I've made them all, and also added support for LLDB (with the caveat that I don't currently have it set up and can't test it thoroughly.)

Good catch, thanks.  Fixed the typos


TRAV-11 - Create interactive map for visualizing activities accommodations and transportation options

Conflicts to resolve.

Fixed the conflicts.


Handle groupBy and having clauses in the RelationSplitter

Removes the need to handle them in the MultiSourceGroupByConsumer and
will make the migration to real sub-query data structures in the
MultiSourceSelect easier.

Codecov Report

Merging #5538 into master will increase coverage by 0.08%.
The diff coverage is 87.5%.

@@             Coverage Diff              @@
##             master    #5538      +/-   ##
============================================
+ Coverage     82.69%   82.78%   +0.08%
- Complexity    11439    11454      +15
============================================
  Files          1360     1360
  Lines         44430    44427       -3
  Branches       5534     5535       +1
============================================
+ Hits          36741    36778      +37
+ Misses         5112     5079      -33
+ Partials       2577     2570       -7

Impacted Files
Coverage Δ
Complexity Δ

...e/planner/consumer/MultiSourceGroupByConsumer.java
100% <ø> (ø)
2 <0> (-4)
:arrow_down:

...a/io/crate/analyze/relations/RelationSplitter.java
96.42% <87.5%> (-0.55%)
42 <0> (+2)

...n/java/io/crate/exceptions/JobKilledException.java
0% <0%> (-66.67%)
0% <0%> (-1%)

.../java/io/crate/exceptions/ValidationException.java
57.14% <0%> (-14.29%)
2% <0%> (-1%)

...crate/executor/transport/TransportShardAction.java
72.97% <0%> (-13.52%)
8% <0%> (-1%)

.../java/io/crate/blob/TransportDeleteBlobAction.java
75% <0%> (-5%)
4% <0%> (-1%)

...in/java/io/crate/breaker/RamAccountingContext.java
81.66% <0%> (-3.34%)
20% <0%> (-2%)

...admin/indices/create/BulkActiveShardsObserver.java
71.87% <0%> (-3.13%)
7% <0%> (-1%)

...c/main/java/io/crate/exceptions/SQLExceptions.java
67.67% <0%> (-3.04%)
33% <0%> (-2%)

...ration/collect/collectors/LuceneBatchIterator.java
88.04% <0%> (-2.18%)
37% <0%> (ø)

... and 25 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 51b066c...a2de066. Read the comment docs.


Update Babel and React versions, removed autoprefixer-loader.

Hi,
Sorry I did not realize that running gulp would issue a warning message. Updating to a recent version of babel fixes this (ran npm install --save-dev babel-core babel-loader babel-preset-es2015 babel-preset-react to get that version). I also updated packages.json to use the latest React version, and removed autoprefixer-loader, although I don't know if it is actually used.
Thanks again to the team for the work on this module, and great examples!
Commit message :
Updating Babel version fixes a warning message displayed when
running gulp to build extension :
(node:13366) DeprecationWarning: loaderUtils.parseQuery() received a
non-string value which can be problematic, see
https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major
version of loader-utils.

Updating to React 15.5.0 does not harm anything, and all of the
generated extensions can be run.
Removed 'autoprefixer-loader' as I do not know if it is actually
used and displays a warning message when runnin npm install :
npm WARN deprecated<EMAIL_ADDRESS>Please use postcss-loader
instead of autoprefixer-loader

node version : v7.8.0
npm version : 4.2.0

Looks good! Thanks for doing this cleanup!


integration with Meteor

Hi, wonderful work! I was wondering if there're plans to integrate react.rb with Meteor: www.meteor.com
Thanks.

@miguelalarcos I don't believe meteor integration is in the scope of this project.

This issue was moved to reactrb/reactrb#56


Incorrect parameter range for HomeSeer Floodlight Sensor HS-FLS100+

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
Unable to input parameter value of zero due to incorrect range in homeseer_template.json file.  Current parameter min to max is 10 to 900, but actual parameter min-max is 0 to 255.
For HomeSeer HS-FLS100+, Lux_Trigger_Threshold, allowed values are 0, 30-200, 255. Value 0 will NOT activate floodlight. Value 30 represents 10 lux, Value 200 represents 900 lux. Value 255 will activate floodlight regardless of ambient light level
What do you observe?

What did you expect to happen?
Per the manual (located at - https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/2947/HS-FLS100-user-manual2b-A501112779R.pdf )

Parameter file needs to be updated as follows:
"lux_trigger_threshold": {
	"label": "Light Level Threshold",
	"description": "Allowed values are 0, 30-200, 255. Value 0 will NOT activate floodlight. Value 30 represents 10 lux, Value 200 represents 900 lux. Value 255 will activate floodlight regardless of light level",
	"valueSize": 2,
	"minValue": 0,
	"maxValue": 255,
	"defaultValue": 50,
	"unsigned": true
},

Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '...'
See error

Device information
Manufacturer: HomeSeer
Model name: HS-FLS100+
Node ID in your network:
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:
zwavejs2mqtt branch:
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
No Log file needed

The same template is shared by the HS-FLS100-G2 which actually uses the range stated there. We'll rather need a second template with the 0..255 range.

Thank you for looking at this... I figured that the template was mis-applied.  Is there any more information that you need from me?

No but if you like to help, providing a PR with the changes will speed things up

So... I'm not a programmer, I'm a Systems engineer (EE degree).  I thought this was a "PR".  I listed the code changes above... (but not sure if that is the correct format to allow the non-contiguous range of 0, 30-200, 255).

No, this is an issue. A PR (Pull Request) means making the changes in your copy of the repo and providing them so they can be merged.
We also have some documentation on contributing device file changes and predefined environments to make this easier for you.
If this is out of your league, let me know.

Please go ahead and fix it correctly… I know the technical info, but may not format it right.
Robert Apodaca
From: @.>
Sent: Monday, November 15, 2021 3:29 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [zwave-js/node-zwave-js] Incorrect parameter range for HomeSeer Floodlight Sensor HS-FLS100+ (Issue #3701)
No, this is an issue. A PR (Pull Requesthttps://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#about-pull-requests) means making the changes in your copy of the repo and providing them so they can be merged.
We also have some documentationhttps://zwave-js.github.io/node-zwave-js/#/config-files/contributing-files on contributing device file changes and predefined environments to make this easier for you.
If this is out of your league, let me know.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/zwave-js/node-zwave-js/issues/3701#issuecomment-968647708, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWOTKEBA52S45G56OJUM4O3UMDAGLANCNFSM5H5LSVPQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Just updated to 2022.2.0 and the Integrations show my device changed from HS-FLS100+ to a HS-FLS100-G2 which is incorrect.  The Z-Wave JS Config DB still needs to be updated as described in the bug report above.
Issue was NOT fixed by PR #4110.

FYI - Updated to 2022.2.0 mine still shows as HS-FLS100+ but still cannot set correct parameters

You have to reinterview the device to pickup a new device file.

Thanks.  I did re-interview, and then went to configure but still can't put in "0" for parameter 2.  Parameter 2 also still shows up as "LUX" units, and it should be unit-less values of 0, 30-200, 255.

Currently on CORE 2022.2.1; SUPERVISOR 2022.01.1; HOME ASSISTANT OS 7.2

I'm on Frontend version: 20220203.0 ; core-2022.2.2 ; OS 7.2 (latest updates)
Did a re-interview successfully with the same results as above...

Yeah, the core versions are irrelevant. You need to wait for the addon to pickup the right zwavejs version, then update it, then reinterview.

Got ya... makes perfect sense should have realized that, Thanks!!

@blhoward2 - Thanks!  Does that happen automatically or can I do re-boot or re-start of something to force it?

I don’t know as none of us run Supervised. I believe that you have to manually check for updates somehow in the Supervisor. Addon releases happen apart from core releases though, so it may have been out a while ago or not out yet. It’s just when they get around to updating.

If you go to the Supervisor screen, then go to the “Add-on Store” tab, on the top right there are 3 dots. Click those, and in the menu that opens, click “Check For Updates” that will trigger an update of all addon repositories but there are none yet.

Thanks... just checked the ADD-ON STORE for my version of Z-Wave JS (0.1.52) and it is pointing to 8.10.2 and this fix isn't until database 8.11.2
Z-Wave JS
Current version: 0.1.52
Bump Z-Wave JS to 8.10.2

Just an FYI and a BIG THANKS! I upgraded today and got the new database re-interviewed and re-started all is wonderful! Just want to thank you guys for a great product and the support!!

Is this still working for everyone? I am unable to set any parameters on my HS-FLS100+. They always revert to default . I have no issues with setting params on other devices
I am on the latest HA and latest zwave js ui. Running on an RPi 4

HS-FLS100-zwavejs.log
It was suggested on HA forums that the zwave-js device configuration would need to be updated to disable "Supervision with Configuration CC" since other Homeseer devices also require this
https://github.com/zwave-js/node-zwave-js/blob/13c509216bd653abd74d43a6bcd3498367bba20f/packages/config/config/devices/0x000c/hs-wd200.json#L130-L140
I tried to create my own device config and put in store/config with the changes, but it would never load the file. I can create a PR to get the device config updated if that is needed
Thanks

@devWaves that might be the case. I only have the FLS100-G2 variant and there Supervision seems fixed.

I tried to create my own device config and put in store/config with the changes, but it would never load the file.

Did you re-interview?

@AlCalzone thanks! I was missing the templates folder and I was able to add the custom device config now. I didn't see that mentioned here https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files
Adding the code to disable "Supervision with Configuration CC" as mentioned above works and I am now able to set the parameters without errors
I will open a PR to change the device config. Thanks again


Fixing GOG achievements for public profiles

Currently SuccessStory cannot get GOG achievements at all, this fixes it if your profile is public. When debugging the regex that was being used wasn't returning any values. I have changed the regex and now it returns correctly.
Here is a regexr script that shows it matches properly on the achievements regexr.com/89bbj.
I have attached a picture of my IDE getting the response correctly as well, the contents of jsonDataString contains the achievement data

Thanks for identifying the problem.
Wouldn't it be better to do so?
string pattern = regexForward + @"(\[?{.*}\]?)[;]?[<]?";
In order to break other calls to this function?

Yeah that would probably be better, I was mainly focused on getting the GOG achievements working again, but checked the Regex you provided and it seems like a better one than I provided. Also renaming the "regexForward" variable is a good idea since it's putting us into the brackets

have updated the regex and the variable name as discussed

Possible error in Tools.GetJsonInString, Playnite crashes when logging into steam

Have raised a PR to fix this, sorry
https://github.com/Lacro59/playnite-plugincommon/pull/139


flowchart designed json response

I've designed a workflow using flowchart.js How can I get its response.
Can I get events for start/stop clicks..

Sorry, I don’t understand

Sorry, I don’t understand

I've designed the above workflow using drag and drop from left side controls.
Can I get the response(json) of the designed work flow?
My requirement is to save the workflow in db.
I've some additional requirements as well. Considering start/Task/End as buttons in the above designed workflow, I want click events of the buttons.
Can you please help in implementing these features?
Thanks!

I’ve never seen this UI 🤷♂
flowchart.js uses a text representation to generate a chart like here: http://flowchart.js.org

https://github.com/visionfortech/Draw-flowchart-with-drag-and-drop-in-HTML-and-JavaScript
From the above source, I've downloaded and ran the html file

I get this. Can you please take this reference

Sorry, looks like this is not the same library.
Try to create an issue here: https://github.com/visionfortech/Draw-flowchart-with-drag-and-drop-in-HTML-and-JavaScript/issues

Sorry to trouble you Adrai
Thanks


fred:// Protocol

In template/static/styles/site.flatly.css:1 the webfont is requested via the protocol fred://
This shows up as an error in Chrome and is simply ignored in Firefox.
The same protocol is also used in docstrap/template/jsdoc.conf.json:22. (Is this setting even used? It is not documented.)

Default protocol is already html://. Someone should close this

closing, please come back if this shouldn't be closed.


feat(python-option): Make it possible to run Prowler from Python

The --python option enable prowler to be called by a python program to manipulate findings directly
Context
Hello, It would be nice to be able to use prowler from python. In this way it's possible to have the type hint of the checks and manipulate them on the fly. Maybe with an additional PR we could also change the code to return the findings with a yield keyword and get them in real time.
To run prowler from python:
# inside the root directory of the project
pip install .

And then with a script:
from prowler import __main__
from prowler.lib.check.models import Check_Report_AWS
from typing import List

arguments = ["aws", "--region", "eu-west-1", "--python", "-c", "account_maintain_current_contact_details"]
findings: List[Check_Report_AWS] = __main__.prowler(args=arguments)
for finding in findings:
    print(finding.status)
    print(finding.check_metadata)

Description
No dependencies are required for this PR. The PR make it possible to run prowler directly from python. Let me know if it's something that you think is useful for your project, or I'll close the PR. A redesign of the main.py would be needed to make it a bit cleaner :D
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @meowmeowxw, this is a great addition to Prowler but I'm concerned about all the places where if we catch a critical error Prowler exits the execution, since it will cause to exit the father Python process usign Prowler as a library, causing some abrupt errors instead of the ability to catch the exception.
What do you think?
Also, as I can see this option does not provide a full compatibility with all Prowler's features right?

Hello @jfagoagas ,
Thank you for the reply.

Also, as I can see this option does not provide a full compatibility with all Prowler's features right?

Yes just some of them, but I think the most important one is the ability to collect findings. The other flags of prowler are mostly just to get a list of checks/services/options right?

I'm concerned about all the places where if we catch a critical error Prowler exits the execution, since it will cause to exit the father Python process usign Prowler as a library, causing some abrupt errors instead of the ability to catch the exception.

I'll check better the codebase and see what I can do.
What do you think if I focus only on the findings gathering part? Would it suits you or would you like to enable python for everything? (It would require a major refactoring for most of the functions to not print results directly)

Also, as I can see this option does not provide a full compatibility with all Prowler's features right?

Yes just some of them, but I think the most important one is the ability to collect findings. The other flags of prowler are mostly just to get a list of checks/services/options right?

There are flags to export findings to Security Hub, to select the output format you want, etc. You can check it running prowler aws/azure/gcp --help.

What do you think if I focus only on the findings gathering part? Would it suits you or would you like to enable python for everything? (It would require a major refactoring for most of the functions to not print results directly)

I think focusing only on the findings gathering part would be great as a first approach to this new feature, I think the yield part can be really useful here at least to try it.
Thanks!

hi @meowmeowxw, if I may ask, what is the use case for this feature? Is it by any chance to run it as a Lambda function?

Hi @toniblyx ,
Yes it would enable an easier integration into lambda instead of using subprocesses.
It would also be possible to manipulate the findings in real time, and add type hinting (in this way you don't have to load the json and convert it back to Check_Report_AWS)

Hi,
I will close this PR since I don't have time to work on this.
Thanks for the ping :smile:


Different Behavior of tf.raw_ops.DivNoNan+tf.raw_ops.Asin with jit_compile=True

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
11.8
GPU model and memory
GPU 0: NVIDIA GeForce RTX 2070 GPU 1: NVIDIA GeForce RTX 2070 GPU 2: NVIDIA GeForce RTX 2070 GPU 3: NVIDIA GeForce RTX 2070
Current behavior?
When the tf.raw_ops.DivNoNan+tf.raw_ops.Asin operation is invoked within a tf.function with JIT compilation enabled (jit_compile=True), it produces different results compared to the same operation called without JIT compilation. This inconsistency is observed when the code is executed on a CPU device.
Standalone code to reproduce the issue
import tensorflow as tf
import traceback

def replace_special_values(tensor):
    # Convert tensor to tf.float32 if it's not a supported dtype
    supported_dtypes = [tf.float16, tf.float32, tf.float64, tf.bfloat16]
    if tensor.dtype not in supported_dtypes:
        original_dtype = tensor.dtype
        tensor = tf.cast(tensor, tf.float32)
    else :
        original_dtype = None

    # Replace NaNs with zeros
    tensor = tf.where(tf.math.is_nan(tensor), tf.zeros_like(tensor), tensor)

    # Replace positive infinities with a large number (e.g., 1e30)
    tensor = tf.where(tf.math.is_inf(tensor), 100, tensor)

    # Replace negative infinities with a small number (e.g., -1e30)
    tensor = tf.where(tf.math.is_inf(tensor) & tf.math.less(tensor, 0), -100, tensor)

    # Convert tensor back to its original dtype
    if original_dtype is not None :
        tensor = tf.cast(tensor, original_dtype)
    return tensor

class Network(tf.Module):
    def __init__(self):
        super().__init__()

    @tf.function(jit_compile=True)
    def __call__(self, x):
      dic = {'ele': [[-921600.0, -499712.0, 638976.0, 344064.0]], 'size': [1, 4], 'dtype': tf.bfloat16}
      x = tf.raw_ops.DivNoNan(y=x, x=tf.constant(dic['ele'], dtype=tf.as_dtype(dic['dtype'])))
      x = tf.raw_ops.Asin(x=x, )
      return x

m = Network()
dic = {'ele': [[688128.0, -344064.0, -778240.0, -532480.0], [-466944.0, -888832.0, 843776.0, -172032.0], [-704512.0, -389120.0, -827392.0, -188416.0], [778240.0, 32768.0, 794624.0, 761856.0], [-122880.0, -110592.0, -811008.0, 139264.0], [-561152.0, 106496.0, -389120.0, -548864.0], [909312.0, -94208.0, -499712.0, 811008.0]], 'size': [7, 4], 'dtype': tf.bfloat16}

inp = {
    "x": tf.constant(dic['ele'], dtype=tf.as_dtype(dic['dtype'])),
    }

with tf.device('/CPU:0'):
    tf.config.run_functions_eagerly(True)
    no_op_res = m(**inp)
    tf.config.run_functions_eagerly(False)
    with tf.device('/CPU:0'):
        op_res = m(**inp)
    no_op_res = replace_special_values(no_op_res)
    op_res = replace_special_values(op_res)
    tf.debugging.assert_near(tf.cast(no_op_res, tf.float64), tf.cast(op_res, tf.float64), atol=0.001, rtol=0.001)

Relevant log output
File "/home/guihuan/LLM/results/tf-2/2023-10-22-20-21/test.py", line 53, in <module>
    tf.debugging.assert_near(tf.cast(no_op_res, tf.float64), tf.cast(op_res, tf.float64), atol=0.001, rtol=0.001)
  File "/home/guihuan/.conda/envs/night/lib/python3.9/site-packages/tensorflow/python/util/traceback_utils.py", line 153, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/guihuan/.conda/envs/night/lib/python3.9/site-packages/tensorflow/python/ops/control_flow_assert.py", line 102, in Assert
    raise errors.InvalidArgumentError(
tensorflow.python.framework.errors_impl.InvalidArgumentError: Expected 'tf.Tensor(False, shape=(), dtype=bool)' to be true. Summarized data: b''
b'x and y not equal to tolerance rtol = tf.Tensor(0.001, shape=(), dtype=float64), atol = tf.Tensor(0.001, shape=(), dtype=float64)'
b'x (shape=(7, 4) dtype=float64) = '
0.0, 0.0, -0.9609375, ...
b'y (shape=(7, 4) dtype=float64) = '
0.0, 0.0, -0.95703125, ...

Hi @zoux1a ,
I have replicated the behaviour with jit_compile=True. With jit_compile=False and also by commenting out the code tf.config.run_functions_eagerly(False) the problem does not persist. Attached gist for reference.
Thank you!

However, we think the different behaviors between eager mode and jit_compiled should be corrected in the future. Will it be fixed?

Hi @zoux1a ,
The difference in outputs is only minor precisional change which is expected with XLA due to internal fusions and conversions from bfloat16 to float32 etc.
I have changed the rtol to 0.01 from 0.001 and executed the code 10 runs and it executed successfully. Please refer attached gist.


Question about running intern tests

Hello, I'm attempting to write a new feature branch, and have managed to get my head around typescript and the new test framework.  I've got some failing tests, which is a good start.
However, I'd like to do some console.log debugging, and can't figure out how to access the console in the tests.  I've seen that you can start intern in browser mode with yarn start, but I cannot access any of the tests there.
Can you provide any hints please?

Hi @ianwhite

I've got some failing tests, which is a good start.

🎉 😄

However, I'd like to do some console.log debugging, and can't figure out how to access the console in the tests.

IIRC I think I may have come across the same issue. Rather than debug the test suite, I think I added console.log to the source where necessary. I then simulated the test code manually by running yarn start, opening http://localhost:9000/fixtures/navigation.html (for example) in a browser window, and clicking around. I hope that makes sense?

Excellent, navigating to the fixture is the info I needed.  I'm new to intern testing, and pretty rusty on JS testing.  Thank you @domchristie!


Retain original window size when moving out of FancyZone

Summary of the new feature/enhancement
When moving a window out of a fancy zone it should resize to it's original size before being snapped into the fancy zone. This would operate like the existing Windows snap feature.
Proposed technical implementation details
Perhaps add this as an option as the current implementation may be preferred by some.

Hi @logictom
this was also proposed by https://github.com/microsoft/PowerToys/issues/227
keeping this open since #227 is not stating the proposal in the title.

I found a temporary workaround, while I don't like it, works. When dragging into a zone make sure your window is touching the edge of the desktop so if FancyZones weren't active it would snap regularly. FancyZones however takes precedence and resizes it to the correct size and puts in the correct location, but when dragging the window away from where you placed it it will resize back to as it was before.
Gif for clarity

@logictom @MindSwipe
I didn't realize there was also issue https://github.com/microsoft/PowerToys/issues/282 for the same feature request.
Please add you comments there.
I'm closing this one as duplicate.

More awkwardly described, but that's exactly what I wanted to say :)
The "FancyZones" are fantastic. That's what I was looking for.
I miss a function that would make working much easier for me.
I definitely want to use "FanyZones" to store remote computers in a grid.
So reduced, I can see what's happening and pull out the appropriate window to keep working on it.
But it would be important for FancyZones to remember how big the window was before I put it in the FancyZone. Otherwise I have to restore the size manually.
It would be great if this function could be added.


Fix Unrestricted File Upload

Fix Unrestricted File Upload vulnerability.
Note that this code change alone might not be enough because (at least):

another php script (index.php) shows all upload filenames
in some situations, php code can be injected into "seemingly legit" images (e.g. see this)

My suggestion is to prevent php execution in any folder but the root one. Note that how to do this depends on the web server used.

Intanto GRAZIE MILLE


thumbdrives: init at 0.3.1

Description of changes
USB mass storage emulator for Linux handhelds. https://sr.ht/~martijnbraam/thumbdrives/
Tested on my oneplus-enchilada.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/727


Update README.md

Added two articles links regarding authentication with server-side Blazor.

Hello! Thank's for the submission.


JobClient supports map of filename->inputstreams to create attachments while submitting jobs.

JobClient supports map of filename->inputstreams to create attachments while submitting jobs.

Coverage decreased (-0.07%) to 89.286% when pulling 9f3b98b655a7d740c93a0708c1dbce35f9c55f7f on amitsharma1981:develop into 553f161abe4a628e5a3865eac1b435105996cc1b on Netflix:develop.

Part of #162


Server crashes when executing copy (select * from test order by a) to :'filename'

What happens?
Server crashes when executing the script below
PostgreSQL build:
CFLAGS='-Og' ./configure --enable-tap-tests --with-openssl --enable-debug --enable-cassert --with-icu --with-lz4 --with-libxml

To Reproduce
create extension pg_mooncake;

\set filename :abs_builddir '/results/test.csv'
copy (select * from test order by a) to :'filename';

backtrace
#0  RangeVarGetRelidExtended (relation=0x0, lockmode=1, flags=0, callback=0x0, callback_arg=0x0) at namespace.c:457
#1  0x00007da5446fbcb4 in DuckdbCopy (pstmt=0x5e19d4a08f60,
    query_string=query_string@entry=0x5e19d4a07fc0 "copy (select * from test order by a) to ':abs_builddir/results/test.csv';", query_env=query_env@entry=0x0,
    processed=processed@entry=0x7fffcd368f50) at ../../src/pgduckdb/utility/copy.cpp:203
#2  0x00007da544703040 in DuckdbUtilityHook (pstmt=0x5e19d4a08f60, query_string=0x5e19d4a07fc0 "copy (select * from test order by a) to ':abs_builddir/results/test.csv';",
    read_only_tree=<optimized out>, context=PROCESS_UTILITY_TOPLEVEL, params=0x0, query_env=0x0, dest=0x5e19d4a09320, qc=0x7fffcd369220) at ../../src/pgduckdb/pgduckdb_hooks.cpp:208
#3  0x00005e19d3d0831e in ProcessUtility (pstmt=pstmt@entry=0x5e19d4a08f60, queryString=<optimized out>, readOnlyTree=<optimized out>,
    context=context@entry=PROCESS_UTILITY_TOPLEVEL, params=<optimized out>, queryEnv=<optimized out>, dest=0x5e19d4a09320, qc=0x7fffcd369220) at utility.c:519
#4  0x00005e19d3d05865 in PortalRunUtility (portal=portal@entry=0x5e19d4a93ec0, pstmt=pstmt@entry=0x5e19d4a08f60, isTopLevel=isTopLevel@entry=true,
    setHoldSnapshot=setHoldSnapshot@entry=false, dest=dest@entry=0x5e19d4a09320, qc=qc@entry=0x7fffcd369220) at pquery.c:1158
#5  0x00005e19d3d05b2e in PortalRunMulti (portal=portal@entry=0x5e19d4a93ec0, isTopLevel=isTopLevel@entry=true, setHoldSnapshot=setHoldSnapshot@entry=false,
    dest=dest@entry=0x5e19d4a09320, altdest=altdest@entry=0x5e19d4a09320, qc=qc@entry=0x7fffcd369220) at pquery.c:1315
#6  0x00005e19d3d05e9f in PortalRun (portal=portal@entry=0x5e19d4a93ec0, count=count@entry=9223372036854775807, isTopLevel=isTopLevel@entry=true, run_once=run_once@entry=true,
    dest=dest@entry=0x5e19d4a09320, altdest=altdest@entry=0x5e19d4a09320, qc=0x7fffcd369220) at pquery.c:791
#7  0x00005e19d3d020fe in exec_simple_query (query_string=query_string@entry=0x5e19d4a07fc0 "copy (select * from test order by a) to ':abs_builddir/results/test.csv';")
    at postgres.c:1278
#8  0x00005e19d3d0403e in PostgresMain (dbname=<optimized out>, username=<optimized out>) at postgres.c:4767
#9  0x00005e19d3cfd63c in BackendMain (startup_data=<optimized out>, startup_data_len=<optimized out>) at backend_startup.c:105
#10 0x00005e19d3c57dc8 in postmaster_child_launch (child_type=child_type@entry=B_BACKEND, startup_data=startup_data@entry=0x7fffcd369444 "",
    startup_data_len=startup_data_len@entry=4, client_sock=client_sock@entry=0x7fffcd369480) at launch_backend.c:277
#11 0x00005e19d3c5c4c3 in BackendStartup (client_sock=client_sock@entry=0x7fffcd369480) at postmaster.c:3593
#12 0x00005e19d3c5c73d in ServerLoop () at postmaster.c:1674
#13 0x00005e19d3c5ddaf in PostmasterMain (argc=argc@entry=3, argv=argv@entry=0x5e19d49c2020) at postmaster.c:1372
#14 0x00005e19d3b7f61b in main (argc=3, argv=0x5e19d49c2020) at main.c:197

OS:
Ubuntu 24.04
pg_mooncake Version:
d90665fd63755f776b866c667e578b4f20a9a76b
Postgres Version:
REL_17_STABLE
Are you using pg_mooncake Docker, Neon, or the extension standalone?
pg_mooncake extension standalone
Best regards,
Egor Chindyaskin
Postgres Professional: https://postgrespro.com/

Thanks for the bug report!
It is now fixed in https://github.com/Mooncake-Labs/pg_mooncake/commit/acda6eeb4c719d280d2ee324ef8a29644f9446fa


add specific titles to partials

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

Other information:

Pull Request Test Coverage Report for Build 2393

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.09%) to 92.378%

Files with Coverage Reduction
New Missed Lines
%

xclim/subset.py
3
62.5%

Totals

Change from base Build 2388:
-0.09%

Covered Lines:
3224

Relevant Lines:
3490

💛  - Coveralls


Cannot access raw artifacts from GitLab any more

GitLab, at least with its current version, doesn't send a correct Content-Type any more if one tries to fetch the result from e.g. https://git.tech.rz.db.de/api/v4/projects/146691/jobs/artifacts/master/raw/trivy-results.json?job=scan_oci_image_trivy. Instead, it sends a Content-Type: text/plain now, which will not be parsed by the explorer.

Thanks to @jschirrmacher this should be fixed now! I cannot test it at the moment, so feel free to give feedback.


Release 2023-09-19

Release 2023-09-19
Please merge this PR using 'Create a merge commit'!

Resolved merge conflicts in

pageserver/src/walingest.rs
test_runner/regress/test_vm_bits.py

(took everything from main)


fix: oracle client + servers [BLO-804]

In This PR

I identify flakiness from server_test and remedy it, specifically

I implement a blocking feature on the client so that tests can be executed with a server that is available, and a client that is fully connected to the server
I close the underlying grpcServer along with the reverse-proxy to ensure that direct GRPC connections (connections not over HTTP), are handled gracefully on closures

This PR is not targeting main

That is intentional, re the slack msg, this fixes CI failures from a prev. PR


std::out_of_range occured when B=3

Hi,
I also found a bug when choosing B=3, which is a common parameter according the paper. I call it a bug because it is more serious which terminates the program. Same main function:
int main()
{
  //Vector that stores the patterns to search
  std::vector<std::string> v;
  v.push_back("01000");
  v.push_back("00011");

  //Wu Manber -wrapper- class
  WuManber wu;

  //Construction of the tables required by the algorithm
  wu.initialize(v);

  //List with the detail of every match found
  auto hits = wu.search("0000110000", 0);
  for (auto& hit : hits)
  {
    std::cout << hit.pattern << std::endl;
  }
  return 0;
}

libc++abi.dylib: terminating with uncaught exception of type std::out_of_range: basic_string

Thanks, nice job!


rw duplicates goals for metavariables appearing in the rewritten expression

Prerequisites
Please put an X between the brackets as you perform the following steps:

[x] Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues
[x] Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries.
[x] Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)

Description
When rewriting a term that contains metavariables, this metavariable is added as a new goal in the tactic state, even if it already is a goal. This clutters the tactic state and is confusing.
Context
Question on Zulip
Steps to Reproduce
The example provided on Zulip is:
example : ∀ d g, d = g → exists x : Nat, x = d := by
  intros d g H1
  constructor
  rewrite [H1,←H1,H1,←H1,H1]
  -- rotate_left; exact g; rfl

Expected behavior: [Clear and concise description of what you expect to happen]
The goal
dg: Nat
H1: d = g
⊢ Nat

should still appear only once after the rewrites
Actual behavior: [Clear and concise description of what actually happens]
The goal appears 6 times after the 5 rewrites.
Versions
4.7.0 (works on any version)
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

I've made a fix for it here: #4383

Either this has regressed, or the fix wasn't exhaustive: see #6407


Fixed namespace conflict in C++/CLI.

Just was going through the codes and found the TODO in UTF16 Test....
Added CLI generation for the test and one of the problems that i encountered was same as #365
.
This pull solves that. But, it is totally a naming convention thing. So please see if this would be carried out or not. @tritao

Well, like you said this is a naming convention thing. I don't think we want to add "WrapperClass" to the class that is generated automatically.
Me and @ddobrev fixed the original in a different way in https://github.com/mono/CppSharp/commit/cf472f526c87e9807a9f9868e7cbc07376efcbb6.


Use assert_nil in tests

instead of assert_equal nil, because it produces errors with activesupport >= 5.1.3.

@pvalena Thanks for the contribution.  Would up inadvertently duplicating this in PR #665 .  So I'm closing this PR.


search is broken, when files are present with wrong extensions

@rultor release, tag is 0.0.2

@rultor release, tag is 0.0.2

@rultor release, tag is 0.0.2

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


Prettier cannot format azuredeploy.json when Azure ARM tools installed

When Azure ARM tools installed and enabled my default code formatter (Prettier) is unable to format any json file which contains an ARM schema definition. When formatting is attempted the following message is visible in the toolbar: "Extension 'Prettier - Code Formatter' cannot format 'azuredeploy.json'"
If the Azure ARM tools extension is disabled then Prettier is able to format the document as expected. Something about the Azure ARM tools extension is preventing Prettier from being able to format the document.

@neilpeterson Would it be worth it to find the formatting extensions in vscode that support JSON and make sure they support arm-template?

@StephenWeatherford as discussed I will look closer a this and compare with some similar extensions.

I tried to configure prettier to use the arm-template` language using the following setting:
[arm-template]": {
     "editor.defaultFormatter": "esbenp.prettier-vscode"
},

But prettier fails then, not sure who is to blame but I wouldn't be surprised if the prettier extension has the json or jsonc language hard-coded somewhere...

I commented on the issue on the vscode prettier extension on how to actually fix this in prettier itself. The other option is to use the .prettierrc to override.
{
  "overrides": [
    {
      "files": "azuredeploy.json",
      "options": {
        "parser": "json"
      }
    }
 ]
}

@ntotten Thanks. because the ARM template file name can be anything and not just azuredeploy.json, the 2nd provided workaround is unfortunately not very practical for most repos.
I've tried to open a new PR in prettier, can you have a look please: https://github.com/prettier/prettier/pull/8274

Closing this in lieu of the PR on the prettier project. Thanks for opening this and working with the prettier project.


refactor data step script into library (API) and consumer (CLI)

There are some pain points with the current data step.

user is not able to select output path

MLflow places artifacts in the working directory, under mlruns. It uses 2 long random strings.

the mlflow run CLI is clunky

Appears restrictive -- no mutually-exclusive options?
CLI is partially defined with argparse in cmip26.py, partially with MLflow (via MLproject, which gets used by mlflow run) i.e. some positional arguments are upgraded to (required) options in MLflow

the top-level data step is defined in a Python script, cmip26.py

It does clean module calling inside, but as is it's not ready to be packaged up.

This PR largely rewrites the data step. Unused code is removed. Stateful operations (globals) are moved into functions. The top-level script is now just a CLI and a handful of operations, mirroring how one would use it directly in Python.

CLI is cleaner

You may also pass a YAML file with the CLI options in instead. (Makes sharing configurations much easier.)

Internals are clearer and safer, using Python typing stuff

e.g. BoundingBox, CO2 increase handling

Whole step functionalized: Python interface is clear, though not explicitly documented

Some of the training step is touched too. Larger refactoring will be in another changeset.
Not done:

Loading and processing of dataset is somewhat general, but various internals still expect CM2.6 (and various CM2.6 coordinates/data variables).
Jupyter notebooks are not updated. MLflow running will not work properly -- they should be replaced by explicit python calls and explicit data locations instead of run IDs.

To-dos:

[x] Move from new.
[x] Move training step refactoring
[x] Tweak training step subdomain loading
[x] Re-add prints, progress bars
How to make --co2-increase flag work in MLproject

Appears to be a limitation -- rewritten readme to use direct invocation example

[x] Update CLI invocations in documentation

Related work to do post-merge:

Update Jupyter notebooks

I think the data step is ready, just needs some touching up before review. I'm adding some work on the training step here too, I'll move it out before review.

I can't seem to get the MLflow interface working nicely with the simplified CLI. By simplified, I mean --global_ {0,1}, --co2 {0,1} being replaced with --cyclize, --co2-increase. But that type of no-value option aren't supported by MLproject. I can't tell why, it seems like a very simple feature.

On testing, this produces forcing data ~x4 larger than currently. Not sure what sort of errors would result in that, but I can go through the changes again. Lines that touch gaussian_filter and further up the call chain seem most likely.

There were many small mistakes! I'm now getting identical outputs to main for the same configuration. Need to clean up the history and rejig some code I re-messied.

Cleaned up history and logging/debugging setup, sorted all the to-dos I can (prior-existing ones that I'm unsure how to resolve are annotated and left). Ready for review.

yoooo it automatically merged? I had no idea that would happen. I rebased dev onto data-step-refactor locally and pushed, and that's been processed as a merge on GitHub!


Minor Implosion on JoystickInitWithUdev during release make (Linux)

The make command for *nix fails at the end due to undefined references.
Steps to reproduce:

git clone https://github.com/nvMcJohn/apitest.git
cd apitest
mkdir _release
cd _release
cmake -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" ..
make

[100%] Linking CXX executable ../../bin/apitest
../thirdparty/SDL2-2.0.1//libSDL2.a(SDL_sysjoystick.c.o): In function `JoystickInitWithUdev':
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:331: undefined reference to `SDL_UDEV_Init'
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:336: undefined reference to `SDL_UDEV_AddCallback'
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:342: undefined reference to `SDL_UDEV_Scan'
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:337: undefined reference to `SDL_UDEV_Quit'
../thirdparty/SDL2-2.0.1//libSDL2.a(SDL_sysjoystick.c.o): In function `SDL_SYS_JoystickQuit':
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:860: undefined reference to `SDL_UDEV_DelCallback'
../thirdparty/SDL2-2.0.1//libSDL2.a(SDL_sysjoystick.c.o): In function `SDL_SYS_JoystickDetect':
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:382: undefined reference to `SDL_UDEV_Poll'
../thirdparty/SDL2-2.0.1//libSDL2.a(SDL_sysjoystick.c.o): In function `SDL_SYS_JoystickQuit':
/home/beau/Code/Misc/apitest/thirdparty/SDL2-2.0.1/src/joystick/linux/SDL_sysjoystick.c:861: undefined reference to `SDL_UDEV_Quit'
collect2: error: ld returned 1 exit status
src/CMakeFiles/apitest.dir/build.make:1344: recipe for target '../bin/apitest' failed
make[2]: *** [../bin/apitest] Error 1
CMakeFiles/Makefile2:253: recipe for target 'src/CMakeFiles/apitest.dir/all' failed
make[1]: *** [src/CMakeFiles/apitest.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

System Information for Reference
OS

Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful

Video Device

*-display
description: VGA compatible controller
product: GK104 [GeForce GTX 760]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:31 memory:f6000000-f6ffffff memory:e8000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:c0000-dffff

Driver Version/Info

filename:       /lib/modules/4.13.0-46-generic/updates/dkms/nvidia_384.ko
alias:          char-major-195-*
version:        384.130
supported:      external
license:        NVIDIA
srcversion:     586B4E0CF4083A6BC41A33B
alias:          pci:v000010DEd00000E00svsdbc04sc80i00*
alias:          pci:v000010DEdsvsdbc03sc02i00
alias:          pci:v000010DEdsvsdbc03sc00i00
depends:
name:           nvidia
vermagic:       4.13.0-46-generic SMP mod_unload
parm:           NVreg_Mobile:int
parm:           NVreg_ResmanDebugLevel:int
parm:           NVreg_RmLogonRC:int
parm:           NVreg_ModifyDeviceFiles:int
parm:           NVreg_DeviceFileUID:int
parm:           NVreg_DeviceFileGID:int
parm:           NVreg_DeviceFileMode:int
parm:           NVreg_UpdateMemoryTypes:int
parm:           NVreg_InitializeSystemMemoryAllocations:int
parm:           NVreg_UsePageAttributeTable:int
parm:           NVreg_MapRegistersEarly:int
parm:           NVreg_RegisterForACPIEvents:int
parm:           NVreg_CheckPCIConfigSpace:int
parm:           NVreg_EnablePCIeGen3:int
parm:           NVreg_EnableMSI:int
parm:           NVreg_TCEBypassMode:int
parm:           NVreg_UseThreadedInterrupts:int
parm:           NVreg_EnableStreamMemOPs:int
parm:           NVreg_MemoryPoolSize:int
parm:           NVreg_RegistryDwords:charp
parm:           NVreg_RegistryDwordsPerDevice:charp
parm:           NVreg_RmMsg:charp
parm:           NVreg_AssignGpus:charp

I had also the same problem and I solved by commenting out all those lines..

Specifying SDL compile definitions in root CMakeLists.txt is probably a more elegant solution:
add_subdirectory( thirdparty/SDL2-2.0.1 )

target_compile_definitions(SDL2 PRIVATE SDL_USE_LIBUDEV=0)
target_compile_definitions(SDL2-static PRIVATE SDL_USE_LIBUDEV=0)


Post release automated changes for network releases

Post release automated changes for azure-arm-network

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-network


Fix Client.fromHttpApp does not drain bodies

Fix #7018

Awesome, thanks for this! Sorry, I should have mentioned: do you mind rebasing and targeting your PR at series/0.23 branch? The process we use is to do most work (fixes, compatible features) on series/0.23. PRs for main are for breaking changes.

Sure, but do you mind if I move not only my changes but the whole .run method to series/0.23, because the current implementation runOrDispose method at series/0.23 doesn't allow handling this case properly. I need to distinguish the request and the response disposing stage, run in main makes it much easier than runOrDispose at series/0.23.

Sure, whatever it takes to fix it! :)

It seems that ChunkAggregator is broken now. I will try to figure out what is the cause.

Ok let's merge this before we think of anything else to do 😂


Fix ContentPresenter property field types

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0020382-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

This is a breaking change so will remove backport-candidate.


Invite to Discord is invalid or has expired

I tried this link: https://discord.gg/26wMygt
Can someone fix it?

Strange. For me it works fine, can you post a screenshot of what you see?

Would you mind posting that screenshot on the forum: https://forum.gekko.wizb.it/ Thanks!


EXDEV rename error still happening on Windows

I"m still getting rename error running  on Windows (when running my node from a different drive than the operating system temp folder one)
I found a more robust and less hacky way to fix this by using the multipart options.
// process.env.TMPDIR = 'tmp'; // we don't need this anymore
var multipartMiddleware = multipart({ uploadDir:'tmp' }); // specify the upload directory
By using the option, it stops the multipart code from using the operating system temp folder and make sure the rename operation is not crossing devices.

···
var multipartMiddleware = multipart({ uploadDir:'tmp' });
···
this can fix https://github.com/flowjs/flow.js/issues/17 on windows, thx

thanks @omengye for the feeback.
@AidasK what do you think?


Cleanup: use Address type within proofs

Now that the Note type contains the complete Address rather than several address components, the proof code can be simplified to work on Address types.

I think we can further simplify by just using the Note type since Note is a Value and an Address now, e.g. https://github.com/penumbra-zone/penumbra/blob/main/crypto/src/proofs/transparent.rs#L121


Bug: Search broken in front end build

When using the production build of the front end, locally and on heroku, all of the search forms give 404. The search is fine when using npm start to serve the front end locally FYI. Maybe something in the front end build requirement?

Additional info, there is no error in the back end and I can get a good API response using /api/opportunities?search= directly from the API.

Did a quick fix for opportunities and partners in #147. Pushed to heroku. We need to fix users and tags searching.

@stevenabadie I believe we fixed this issue? I will close. Let me know if it isn't resolved and we can re-open.


Client Allocation Request for: Mgame

Client Allocation Questions
Core Information

Name: Mgame
Website / Social Media: https://www.mgame.com/
Region: Asia (excl. Greater China)
DataCap Requested: 20TiB
Addresses to be Notarized: f1wie3vdkcg23eoqhdgnx2kv33yghvjqpafuz7oay
Notary Requested: MasaakiNawatani

@Hailey-Li Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

@MasaakiNawatani Hi, this is related to https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/2125. Thanks!

Got it @Hailey-Li
Let us review your information on #2125. Thanks!


GIDSignIn.signIn getting "keychain error" for some users

Hello,
We are using GoogleSignIn for a few years. Suddenly, some users start to get "com.google.GIDSignIn / error code: -2 / keychain error" and we can't sign them in to our application.
To fix this, I have to enable "keychain sharing access" in my project settings (we have never enabled this and it was working as expected for a long time) and add "com.google.GIDSignIn" as keychain group.
Here is the screenshot;

If I use my own bundle id here I still get the same error, I have to add com.google.GIDSignIn specifically.
This is not one of the steps to integrate the SDK and I don't know why it is neccessary to add "com.google.GIDSignIn" keychain sharing access in my project.
Can you help with the issue?
Thank you.

Can you tell me what version of Google Sign-In you're using when you see this behavior?  The version of GTMAppAuth you're building with would also be relevant, as well as the version(s) of iOS you're seeing this on.

We are having the same problem here.

GMTAppAuth: 1.2.3
iOS version 15.5 (notice that it happens to some phones not happen with some other phones)

Also seeing this with iOS 15.5, GTMAppAuth 1.2.3. It was reported today. Still looking to see if the version of iOS is a determining factor. This is an app that is in the store.

GoogleSignIn (6.1.0)
GTMAppAuth (1.2.2)

The device I debugged was iOS 15.5 but there are many users who reported the issue, I don't know the OS versions of all.

I'm also having the same issue. Any suggestions would be great.

If you can reproduce this in a debug build, try setting a breakpoint in GTMAppAuth's GTMKeychain implementation in the -setPasswordData:forService:accessibility:account:error: method and check the return value of the SecItemAdd call.  A non-zero value of status could provide some insight into what type of a Keychain error we're dealing with.

The "keyChain Error" is not shown in an updated version of GTMAppAuth (1.3.0).
Just updated to the newest version to resolve the error.

If you can reproduce this in a debug build, try setting a breakpoint in GTMAppAuth's GTMKeychain implementation in the -setPasswordData:forService:accessibility:account:error: method and check the return value of the SecItemAdd call. A non-zero value of status could provide some insight into what type of a Keychain error we're dealing with.

The status returned in GTMAppAuth (1.2.2). is errSecDuplicateItem.

@zaidhafeez thanks for the feedback.
For anyone who is (or was) experiencing this behavior, could you tell me all the third-party libraries you're using and how they're being built / linked (SPM, CocoaPods, XCFrameworks, etc).  I'm looking for a potential source of conflicting Keychain operations.

GoogleSignIn(5.0.2)   iOS 15.4.1

I can verify that "keychain error" doesn't occur on GTMAppAuth version (1.3.0).
It still persists on 1.2.2 though.

@alperkayabasi could you let me know which (if any) third-party libraries you're using in addition to Google Sign-In?  Please see my previous comment.

@petea We're using a lot of 3rd party frameworks but I'll try to list major ones.
pod 'Alamofire'

pod 'Firebase/Database'
pod 'Firebase/Auth'
pod 'Firebase/Analytics'
pod 'Firebase/Performance'
pod 'Firebase/Crashlytics'
pod 'GoogleAppMeasurement'

pod 'Google-Mobile-Ads-SDK'
pod 'GoogleSignIn'

pod 'FBSDKCoreKit'
pod 'FBAudienceNetwork'
pod 'FBSDKLoginKit'

pod 'Adjust'
pod 'AppsFlyerFramework'

pod 'CryptoSwift'
pod 'KeychainSwift'
pod 'TikTokOpenSDK'
pod 'SwiftyVK'

Upgrade to 6.2.2 solve my keychain error problem.

@iyouqiang
I use same version.
I resolved by upgrading 6.0.0 version. but I don't wanna upgrade.
I deleted the app once, but I can't login.
Although I logged in with 6.0.0 version and logout, I can't login with 5.0.2.
Anyone can resolved?

I am also getting the same error for my application. It was working well before.

Same here, got the issue on my phone with multiple accounts

I have the same problem

GoogleSignIn (6.1.0):

AppAuth (~> 1.4)
GTMAppAuth (~> 1.0)
GTMSessionFetcher/Core (~> 1.1)

For those who are still seeing this issue, please let me know which versions of GoogleSignIn and GTMAppAuth you're building with.

GoogleSignIn  -> 6.1.0
GTMAppAuth  -> 1.0
在 iOS 15.4 和 iOS 15.0 都遇到了

Upgrade to Google signin 6.2.2 without this problem. The following is the corresponding version

GoogleSignIn (6.2.2):

AppAuth (~> 1.5)
GTMAppAuth (~> 1.3)

Also seeing this issue on iOS 16 beta:
GoogleSignIn (6.1.0):
- AppAuth (~> 1.4)
- GTMAppAuth (~> 1.0)
- GTMSessionFetcher/Core (~> 1.1)

We're running version 6.1.0 and some of our users are experiencing this issue in too.
Is there a version that you recommend to upgrade to solve this?
Thanks

Update to latest version which has GTMAppAuth  ~> 1.3 will fix the issue

Update to latest version which has GTMAppAuth ~> 1.3 will fix the issue

Thanks a lot Simon!

Updating to latest version solved the issue!

After updating my pods to Installing AppAuth 1.6.0 (was 1.5.0) Installing GTMAppAuth 1.3.1 (was 1.3.0) Installing GoogleSignIn 6.2.4 (was 6.2.2)
I reproduced the issue on a Mac Silicon with Mac OS Ventura (13.0 (22A380)). But It works on iPad OS 16.1.

Same here.
Facing the issue in MacOS testflight builds, but works fine in iOS devices.

What I am seeing is here...
TestFlight Build (with latest SignIn SDK)
iPhone 13 / iOS 16.1 - working fine
iPhone XR / iOS 15.6 - working fine
iPhone 6S / iOS 15.6.1  - working fine
AppStore Build (with old SignIn SDK)
iPhone 13 / iOS 16.1 - Keychain error
iPhone XR / iOS 15.6 - working fine
iPhone 6S / iOS 15.6.1  - working fine

I am facing the same issue even upgraded to GoogleSignIn version 7.0.0 and GTMAppAuth version 2.0.0. But it happening in TestFlight builds and not reproduced in App Store builds yet.

For those who are still seeing this issue, please let me know which versions of GoogleSignIn and GTMAppAuth you're building with.

Still I am facing this issue in some devices. Here are the versions of GooglrSignIn

GoogleSignIn (7.0.0):

AppAuth (~> 1.5)
GTMAppAuth (< 3.0, >= 1.3)
GTMSessionFetcher/Core (< 4.0, >= 1.1)

I am facing the same issue even upgraded to GoogleSignIn version 7.0.0 and GTMAppAuth version 2.0.0. But it happening in TestFlight builds and not reproduced in App Store builds yet.

Add "com.google.GIDSignIn" to Keychain Sharing section of Project Capability, and try again.

I am facing the same issue even upgraded to GoogleSignIn version 7.0.0 and GTMAppAuth version 2.0.0. But it happening in TestFlight builds and not reproduced in App Store builds yet.

Add "com.google.GIDSignIn" to Keychain Sharing section of Project Capability, and try again.

I am not using Keychain Sharing capability in the project, so should I add this capability and add this com.google.GIDSignIn ?

I also encounter this issue,  I attached my Podfile.lock at the end.
After I add Keychain Sharing in Signing  & Capabilities, also a com.google.GIDSignIn in Keychain Groups, it solved my issue.
Cheers!

Xcode: Version 14.2 (14C18)
Minimum Deployments: macOS 10.15

com.google.GIDSignIn
Podfile.lock:
PODS:
  - AppAuth (1.6.0):
    - AppAuth/Core (= 1.6.0)
    - AppAuth/ExternalUserAgent (= 1.6.0)
  - AppAuth/Core (1.6.0)
  - AppAuth/ExternalUserAgent (1.6.0):
    - AppAuth/Core
  - GoogleSignIn (7.0.0):
    - AppAuth (~> 1.5)
    - GTMAppAuth (< 3.0, >= 1.3)
    - GTMSessionFetcher/Core (< 4.0, >= 1.1)
  - GTMAppAuth (2.0.0):
    - AppAuth/Core (~> 1.6)
    - GTMSessionFetcher/Core (< 4.0, >= 1.5)
  - GTMSessionFetcher/Core (3.1.0)

DEPENDENCIES:
  - GoogleSignIn

SPEC REPOS:
  trunk:
    - AppAuth
    - GoogleSignIn
    - GTMAppAuth
    - GTMSessionFetcher

SPEC CHECKSUMS:
  AppAuth: 8fca6b5563a5baef2c04bee27538025e4ceb2add
  GoogleSignIn: b232380cf495a429b8095d3178a8d5855b42e842
  GTMAppAuth: 99fb010047ba3973b7026e45393f51f27ab965ae
  GTMSessionFetcher: c9e714f7eec91a55641e2bab9f45fd83a219b882

PODFILE CHECKSUM: acca47bd2cac4d151d614ba463a75f598493389b

COCOAPODS: 1.12.0

OMG, I'm still experiencing the issue on macOS and because of the workaround with the keychain, I see this keychain permission alert.
Has anyone found another workaround that could help avoid that alert?

For those of you who added com.google.GIDSignIn to the keychains and the error still occurs. Try to remove the bin and obj folder from the project and relaunch the app. It worked for my iOS simulator.

After updating from GoogleSignIn (7.0.0) to GoogleSignIn (7.1.0) on a macOS app target I got Error Domain=com.google.GIDSignIn Code=-2 "keychain error" UserInfo={NSLocalizedDescription=keychain error}. Adding Keychain Sharing entitlement and com.google.GIDSignIn group to it did not help. After downgrading to GoogleSignIn (7.0.0) and removing the Keychain Sharing all is fine, no errors and everything works as expected.

Don't spend too much time on this. The record the SDK made in Keychain had to be deleted. There are two questions for me:

Did the auth record broke when the SDK created it?
Can the SDK do something if the record is broken?
It is totally fine if the error occurs during development, which means the end users have little chance to experience it. And in any case if it is possible to recover in such situation - it will be great.

I don't think the auth record broke when it was saved. My tentative hypothesis is that it was created with a missing entitlement or that your sample on the previous run was missing the entitlement.
This case is tricky to remedy because, IIRC, we cannot set a password to the keychain if that item already exists. This is why we have to try to remove it.

So the SDK created the auth record with missing entitlement and at some point in time it decided, that an entitlement is needed. That still does not explain why only switching back and forth between 7.0.0 and 7.1.0 without changing anything else in the project resulted in working with 7.0.0 and failing with 7.1.0

For anyone having the same issue on Flutter MacOS, I solved by using this dependency override:
dependency_overrides:
google_sign_in_ios: 5.7.5
which uses GoogleSignIn 7.0.0

@apaolino Thanks so much I was stuck for few hours!

Why is this marked closed when the issue still persist in the latest version?


Show warning message if try to serialize non basic data type objects

I happen to meet this issue while upgrading Rails from 3 to 4.
Before upgrade, we have:
Dalli::Client.new(host, namespace: "namespace", compress: false, serializer: JSON)

After upgrade, it stores "weird" data to Memcache, like "\"#<User:0x007f83dc017248>\"", instead of "{\"id\":1,\"name\":\"al\"}".
Rails changes are:

https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#json-gem-compatibility
https://github.com/rails/rails/blob/3-2-stable/activesupport/lib/active_support/core_ext/object/to_json.rb#L15
https://github.com/rails/rails/blob/master/activesupport/lib/active_support/core_ext/object/json.rb#L36

I think it'd be better to show a warning message when try to cache non basic data type objects.
BTW, different kinds of JSON serializers have different behaviors. Some of them:
struct = Struct.new(:name).new("alex")
JSON.dump(struct) # "\"#<struct name=\\\"alex\\\">\""
Yajl.dump(struct) # "\"#<struct name=\\\"alex\\\">\""
Oj.dump(struct)   # "{\"^u\":[[\"name\"],\"alex\"]}"

@hlcfan Thanks for the PR, but I don't think this would be a good addition to Dalli.  Specifically:

It would add an unnecessary warning in lots of success cases (when the object being inserted is serializable, but not one of the types you're detecting
It adds overhead to all insertions

So I'm going to close this PR without merging.  Thanks.


Tilemap Editor - Wall tool should allow for Tile Fill

Should provide a way to use the Fill tool with the Wall property on all of the same Tiles in the canvas.  Drawing wall overlay is taxing...

Love it!!!  Thanks 🥇

fixed! Thanks Jacob :D


s3 backup fails when its size more than 5 GB

Hello
I use mysql-operator v0.4.0-rc.1
I tried to request s3 backup for huge db (100gb backup file size) but it failed with error "final move failed"
My investigation shows that if s3 backup is more than 5GB it can not be renamed from .gz.tmp to .gz it caused failing backup
I found related rclone issue:
https://github.com/rclone/rclone/issues/3682

I tried to update rclone from 1.48 to 1.52 but now it failed with error:
"streaming uploads using chunk size 5M will have maximum file size of 48 GB"
but I can not update this parameter because there isn't release with this fix: https://github.com/presslabs/mysql-operator/pull/520

Do you plan to upgrade rclone ?
When do you plan release rclone extra args issue fix ?

Hi @anikievev, thank you for this bug report.
Yes, definitely we should update Rclone.  We already released version 0.4.0 including #520.
Please feel free to open a PR with the rclone version update, if you already tried that. :smile:


Card not rendered when using paste

When I paste a card number into the form and use only the mouse (no keyboard events) the card is not rendered correctly. No numbers appear on the card graphic however formatting is done to the pasted value.

Hi all, thanks for your input!
This issue doesn't appear in Chrome, but I'm guessing it may be related to #165. I'm closing in favor of that issue — if it's something different, please re-open with more information!

@jessepollak this is a different issue. Please reopen.
There are several ways to reproduce this one:

Right-click on any field and select Paste.
Fill one any field (with the keyboard), then select it (using the mouse), right-click and choose Cut (or Delete).
Select some text somewhere and click-drag the selection onto any field.
On Linux (maybe on Mac too), select some text somewhere and then middle-click onto any field (this is an alternative way of pasting text).

Again, please consider using the oninput event. It is supported in all browsers, even in IE9. After adding the oninput event, feel free to remove any keyboard-related event handler, as they are not needed anymore.

I tried this small patch, but it didn't fix the issue completely because of payment.coffee, which still has several keyboard-related handlers. The fix to this issue #37 and also to the other issue #165 depends on changing/updating/fixing jessepollak/payment as well.
--- a/src/coffee/card.coffee
+++ b/src/coffee/card.coffee
@@ -162,10 +162,10 @@ class Card
       el = this["$#{name}"]
       if QJ.val(el)
         # if the input has a value, we want to trigger a refresh
-        QJ.trigger el, 'paste'
+        QJ.trigger el, 'input'
         # set a timeout because `jquery.payment` does the reset of the val
         # in a timeout
-        setTimeout -> QJ.trigger el, 'keyup'
+        setTimeout -> QJ.trigger el, 'input'

   handle: (fn) ->
     (e) =>
@@ -226,7 +226,7 @@ class Card
     QJ.on el, 'blur', ->
       QJ.removeClass el, 'jp-card-focused'

-    QJ.on el, 'keyup change paste', (e) ->
+    QJ.on el, 'input', (e) ->
       val = (QJ.val(elem) for elem in el)

       join = opts.join(val)


Add generic code to parse the filter object into a odata query url

The js-grid supports odata, which is very cool, however manually creating the odata Url is difficult.
Maybe this javascript library can be used : https://odatasamples.codeplex.com/documentation ?

Since composing urls is controller logic, which is implemented by developer, feel free to use any library or helper for this.

I am using breezejs (http://www.getbreezenow.com/) now, it works perfect in combination with js-grid

Glad to hear that! I personally love breezejs!


Drush 10 support

Drush 10 has been out for a while. I was wondering if it was gonna be supported?

Drush 10 is supported AFAIK?

Alright, I didn't know it was tested against that already :)


new icons

I'm sorry, but I changed the current icons to the ones provided by the Paper icon theme.