CPU only

Hi, congratulations with this nice model
I am wondering if it is possible to run the model using CPU only and if this has been tested?

Was wondering this as well. I think the problem would be that the model would be too slow to run on a normal (consumer grade) CPU.

and if this has been tested?

it wasn't :)

I think the problem would be that the model would be too slow to run on a normal (consumer grade) CPU.

That's my expectation as well - it would be faster/cheaper to rent A100 in cloud rather than using CPU (even server CPU).

I see. :/  However, RoseTTAFold2NA finishes in about 10 mins for me on CPU only on my desktop, having AMD Cezanne, so I have a hard time seeing why Chai-1 would struggle so much more?

Thank Alex for the great work!
I have tried on a single protein with 359 aa, and a ligand with formula "
C88H138N8O65" and molecular weight 2347. It took me 2 hrs and 40 min, I think it may be something wrong taking such a long time. During the running, I checked with nvidia-smi and GPU usage was about 17%, and VRAM usage was only 1.4 G out of total 48 G. I think it must be something going wrong, no?

Hi Robert,
that sounds insanely long, and yes, I'd expect higher mem consumption.

Please share your setup (python, pytorch, GPU).
Other thing to check: did you change params, maybe too many trunk iterations?
Also, we report time taken by trunk and denoising, does it take too long?

Dear Alex,
Here is my setting-up:

conda create -n chai-lab python=3.11
pip install git+https://github.com/chaidiscovery/chai-lab.git

python >>> import torch, error

conda install pytorch==2.3.1 torchvision==0.18.1 torchaudio==2.3.1 pytorch-cuda=12.1 -c pytorch -c nvidia

python >>> import torch; >>>torch.cuda.is_available(), ok
python example/predict_structure.py, ok for your fasta content. It took about a few minutes.
python example/predict_structure.py with my 359 aa protein and oligosialic acid (DP8). It took 2 hrs 40 min on my 13900K CPU, 64G main memory, one NVIDIA GA102GL RTX A6000 GPU, Ubuntu 22.04.5. I am now running with oligosialic acid DP12, and will expect to take more than 3 hrs!

This is screenshot after running 50 mins (python example/predict_structure.py)

This is GPU usage:

Dear Alex, Here is my setting-up:
1. conda create -n chai-lab python=3.11

2. pip install git+https://github.com/chaidiscovery/chai-lab.git

3. python >>> import torch, error

4. conda install pytorch==2.3.1 torchvision==0.18.1 torchaudio==2.3.1 pytorch-cuda=12.1 -c pytorch -c nvidia

5. python >>> import torch; >>>torch.cuda.is_available(), ok

6. python example/predict_structure.py, ok for your fasta content. It took about a few minutes.

7. python example/predict_structure.py with my 359 aa protein and oligosialic acid (DP8). It took 2 hrs 40 min on my 13900K CPU, 64G main memory, one NVIDIA GA102GL RTX A6000 GPU, Ubuntu 22.04.5. I am now running with oligosialic acid DP12, and will expect to take more than 3 hrs!

8. I did not change any of your params. Only place I changed was protein sequence and the ligand smiles (converted from pdb to SMILES by cheminfo.org)

Giving up on CPU for now, I tried Colab (free version), but it seems to interrupt when I try to run the model
!git clone https://github.com/chaidiscovery/chai-lab.git
%cd chai-lab/
!pip install git+https://github.com/chaidiscovery/chai-lab.git
!python examples/predict_structure.py
/usr/lib/python3.10/multiprocessing/popen_fork.py:66: RuntimeWarning: os.fork() was called. os.fork() is incompatible with multithreaded code, and JAX is multithreaded, so this will likely lead to a deadlock.
self.pid = os.fork()
/usr/local/lib/python3.10/dist-packages/transformers/tokenization_utils_base.py:1601: FutureWarning: clean_up_tokenization_spaces was not set. It will be set to True by default. This behavior will be depracted in transformers v4.45, and will be then set to False by default. For more details check this issue: https://github.com/huggingface/transformers/issues/31884
warnings.warn(
Loading checkpoint shards: 100% 2/2 [00:00<00:00,  4.18it/s]
^C

@guruace
Dear Alex,
Here is my setting-up:

conda create -n chai-lab python=3.11
pip install git+https://github.com/chaidiscovery/chai-lab.git
python >>> import torch, error
conda install pytorch==2.3.1 torchvision==0.18.1 torchaudio==2.3.1 pytorch-cuda=12.1 -c pytorch -c nvidia
python >>> import torch; >>>torch.cuda.is_available(), ok
python examples/predict_structure.py, ok for your fasta content. It took about a few minutes.
python examples/predict_structure.py with my 359 aa protein and oligosialic acid (DP8). It took 2 hrs 40 min on my 13900K CPU, 64G main memory, one NVIDIA GA102GL RTX A6000 GPU, Ubuntu 22.04.5. I am now running with oligosialic acid DP12, and will expect to take more than 3 hrs!
I did not change any of your params. Only place I changed was protein sequence and the ligand smiles (converted from pdb to SMILES by cheminfo.org)

Thanks for details, that's very helpful.

Reference numbers from A100 for default example: around a minute on setup +
A6000: I'm looking at spec form nvidia and I don't see bfloat16 flops. My guess: it exists for compatibility, but throughput is actually poor to include in specs.
FASTA issue: please open separate issue for this. U+FEFF may be just a part of your input
GPU memory: I don't see python process with Chai-1, looks wrong.
torch setup - pip version should just work, there is no need in making any installs with conda, you could forget to activate conda env?

@stianale did you use T4 or A100? T4 won't work (ESM can't fit, and no bfloat16 support)

@stianale did you use T4 or A100? T4 won't work (ESM can't fit, and no bfloat16 support)

I only have access to T4, I don't have Colab Pro. :(
Also tried to make Chai1 work in Kaggle, but the "Running into Runtime Error (cutlassF: no kernel found to launch)" puts an end to that. In Kaggle, 2 x T4 and P100 GPU are available.

@guruace
Dear Alex, Here is my setting-up:

conda create -n chai-lab python=3.11
pip install git+https://github.com/chaidiscovery/chai-lab.git
python >>> import torch, error
conda install pytorch==2.3.1 torchvision==0.18.1 torchaudio==2.3.1 pytorch-cuda=12.1 -c pytorch -c nvidia
python >>> import torch; >>>torch.cuda.is_available(), ok
python examples/predict_structure.py, ok for your fasta content. It took about a few minutes.
python examples/predict_structure.py with my 359 aa protein and oligosialic acid (DP8). It took 2 hrs 40 min on my 13900K CPU, 64G main memory, one NVIDIA GA102GL RTX A6000 GPU, Ubuntu 22.04.5. I am now running with oligosialic acid DP12, and will expect to take more than 3 hrs!
I did not change any of your params. Only place I changed was protein sequence and the ligand smiles (converted from pdb to SMILES by cheminfo.org)

Thanks for details, that's very helpful.

Reference numbers from A100 for default example: around a minute on setup + 3sec/iteration for trunk + 0.3 sec/iteration of diffusion
A6000: I'm looking at spec form nvidia and I don't see bfloat16 flops. My guess: it exists for compatibility, but throughput is actually poor to include in specs.
FASTA issue: please open separate issue for this. U+FEFF may be just a part of your input
GPU memory: I don't see python process with Chai-1, looks wrong.
torch setup - pip version should just work, there is no need in making any installs with conda, you could forget to activate conda env?

Here is the detail, I think it must be something wrong with my ligand representation (SMILES string). It took me 12 hours and 20 minutes to produce predicted protein structures, but without ligands on them:

I am now trying to test rdkit to see if it can read my ligand string in SMILES

2 x T4 and P100 GPU are available.

both don't have bfloat16 :/

Hi Alex:
1.Regarding to your question "FASTA issue: please open separate issue for this. U+FEFF may be just a part of your input", the U+FEFF problem occurred when I downloaded xxx.smiles file from cheminfo.org conversion and USED Ubuntu build-in text edit "gedit" to open the xxx.smiles file and to copy the smiles string and pasted into the predict_structure.py which was also opened by gedit. The U+FEFF issue was solved when used 010Editor to open the xxx.smiles & copied the smiles string into predict_structure.py in gedit. This was inspired by GPT-4o.
2.I have checked with my ligand smiles string in rdkit and it is confirmed that rdkit could not create 3D comformer from my ligand (because of too big or too complex?). This is worth noticing since this will happen from time to time.When I used ETKDG of rdkit, it successfully created 3D molecule from my ligand:
from rdkit.Chem import AllChem

# Try embedding with the ETKDG method, which often works better for complex molecules
params = AllChem.ETKDGv3()
result = AllChem.EmbedMolecule(mol_with_hs, params)

if result == 0:
    print("3D conformer successfully generated with ETKDG.")
else:
    print("Failed to generate 3D conformer with ETKDG.")

Very nice model！I wish in the future this will be compatible with AMD series : )


Async: explain  the pattern of Task-returning synchronous methods

It's common that a method may perform all its work synchronously, and the last action is to call a (possibly asynchronous) method that returns a Task or Task<T>:
public async Task SomeMethodAsync()
{
   // some validation or other synchronous work
   await ownedObject.DoAsynchronousThings();
}

In these cases, the code can be simplified (including the generated code) by removing the async modifier, and the await statement:
public Task SomeMethodAsync()
{
   // some validation or other synchronous work
   return ownedObject.DoAsynchronousThings();
}

However, when we explain this optimization, we must be careful to explain when it can cause bugs.  One important case is when the method allocates a Disposable object:
// Danger! Will often throw an AlreadyDisposedException:
public Task SomeMethodAsync()
{
   // some validation or other synchronous work
   using (var resource = AllocateDisposableResource())
   {
      return ownedObject.DoAsynchronousThings(resource);
   }
}

In the case above, the resource is possible still be used by ownedObject.DoAsynchronouseThings after the synchronous method SomeMethodAsync returns. In those cases (and others that manage or capture resources, the async / await keywords ensure that cleanup doesn't happen until the asynchronous work finishes:
// The generated state machine ensures resource cleanup
// only after the asynchronous method has completed its work:
public async Task SomeMethodAsync()
{
   // some validation or other synchronous work
   using (var resource = AllocateDisposableResource())
   {
      await ownedObject.DoAsynchronousThings(resource);
   }
}

Same thing with try catch
try
{
    return AsyncFunc();
}
// Will never catch exceptions thrown from AsyncFunc (unless they are thrown before the function goes async)
catch (...)
{
    ...
}

Adding a note on the comment above.  This pattern with try / catch also requires the state machine, as @BrennanConroy notes. However, this phrase in the comment "(unless they are thrown before the function goes async)" is incorrect.  The catch will never catch exceptions.  See the discussion of local functions for async methods for details.


Build pipeline

Pipeline Configurations

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


datapath: preserve tail call maps in between replacing interface program pairs

To prevent unpinning tail call maps after replacing only one half of an interface's programs, e.g. from-netdev and to-netdev, allow the caller to defer finalizer operations until a batch of interfaces have been replaced.
This avoids short windows of packet drops due to missed tail calls.
Fixes #16561
Also fixed a bug where we specified the wrong bpffs path to the migration code. This causes migrations to not be executed in the currently-released version of 1.11, meaning resizing maps causes endpoints regeneration failures.
Preserve tail call maps during resize to prevent drops during agent upgrade

Did you already test this by adding random tail call somewhere and executing K8sUpdates?

I've tested this by creating a prog array of a different size manually and running the migration commands. Not sure how to work with K8sUpdates.

But I really doubt Kubernetes nodes have a lifespan long enough for this to become an issue.

We can't really assume all k8s nodes are short-lived, as baremetal deployments are a thing as well. However, we only need to resize these maps once in a blue moon and they're rather small. If we do resize them, we should take care to grow them sufficiently (e.g. x1.5) so that adding future tail calls does not require a map migration.

Marked as ready, only known unrelated flakes are hit. This should suffice for 1.11, followups can happen in case any issues become apparent with this approach.

Is this superseding #13032?

Is this superseding #13032?

Yep, I think it does!

As a quick follow-up, we've agreed a while back to implement a GC that would:

scan all prog arrays in backup/
iterate through all BPF programs on the system
scan all existing BPF programs for references to any prog arrays
if no references are found to a given prog array, unpin it

Starting work on this this week.

After some offline discussion, we'll move forward with removing backup/ (where 'old' prog arrays are moved to) when a certain set of programs have been successfully regenerated.

Will unblock existing PRs
Should make upgrade tests pass on changes that grow prog arrays
Should be an improvement in the majority of cases, whereas now there is full connectivity interruption
Can be further iterated on with changes to the loader pipeline throughout 1.12/1.13
Should allow test suite of https://github.com/cilium/cilium/pull/17758 to pass
Can be reasonably backported to 1.11 to improve up/downgrade behaviour

Known issues with this approach:

Pods scheduled during upgrades might still be given an old map that gets cleared soon after the Pod has started. The general advice is to halt pod scheduling during upgrades, but we can document this and treat this as a known issue.
What if the agent is still busy applying datapath version n-1 that happens to include another resize?
-> This should be rare and might be something we can ignore, eventually everything will be regenerated and reconnected.

This should improve the total loss of connectivity during upgrades within a reasonable timeframe.

I couldn't find a suitable point to reliably remove a bpffs backup/ directory, but the main impact seems to be when unpinning a map in between replacing both ends of a program pair of an interface, e.g. replace eth0:from-netdev, , replace eth0:to-netdev.
The ability to defer the unpinning operation until both ends have been replaced has been added to replaceDatapath in the form of a finalizer. It can either be called immediately, or, when called in a loop, deferred.
I also spotted a bug we unfortunately shipped in 1.11, the wrong bpffs path is specified to the migration procedure. The migrations run through init.sh are unaffected. It's not clear what the impact of this is, but I would expect things to break loudly, as the verifier would likely complain about incompatible maps.

/test

/test

Did you perform any upgrade tests other than the CI's? How did you check that it is fixing #16561?

I did not perform my own connectivity tests (I was waiting for some feedback/reviews first), but I did observe the deferred map removal behaviour by watching changes to the bpffs dir during an upgrade, which seems to behave as expected. I'll do some connectivity tests and report back.

I've just done some local upgrade tests, both with and without the second (defer) patch.

Minikube running 4.19.202 under KVM
Deploying an agent Pod flipping CILIUM_CALL_SIZE between 25 and 26 to force prog array re-creation
Running cilium monitor --type=drop in the agent container as soon as the new pod starts
Running hey from my host (not within the VM) against a single nginx Pod inside the cluster at around 10k req/s

There is no noticeable loss of connectivity during the upgrades not even without the patch, and no monitor logs of missed tail calls.
Latency distribution looks good, too. p99 is 0.0034s across 1M HTTP calls.
  0.077 [999857]	|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.155 [37]	|
  0.232 [45]	|
... some buckets omitted ...
  0.774 [3]	|

@brb How can I reproduce this best?

/test

/test

/mlh new-flake Cilium-PR-K8s-1.22-kernel-4.19

@joestringer Addressed your feedback, please take another look.
I've specified the following in the first commit:

This would lead to endpoints continuously failing to regenerate at runtime when map definitions in the ELF differ from their pinned counterparts, e.g. during an agent upgrade.
For example, when resizing CALLS_MAP and trying to replace a program, the old map will be loaded from bpffs, while the program expects to see a map of a different capacity:
~ tc filter replace dev cilium-probe ingress bpf da obj bpf/bpf_lxc.o sec from-container
libbpf: couldn't reuse pinned map at '/sys/fs/bpf/tc//globals/test_cilium_calls_65535': parameter mismatch
libbpf: map 'test_cilium_calls_65535': error reusing pinned map
libbpf: map 'test_cilium_calls_65535': failed to create: Invalid argument(-22)
libbpf: failed to load object 'bpf/bpf_lxc.o'
Unable to load program

/test

All tests are passing and reviews are in. Marking ready to merge.


Add method: Parse(string input, IFormatProvider provider = null)

In order to fix issue #15.
We failed to get method Parse with arguments(string and IFormatProvider)
in PropertyTool to parse a string.
So I just add this method and don't use optional arguments for
Parse(string input, IFormatProvider provider, IUnitProvider
unitProvider)

Looks good, but:

please add a unit test that demonstrates the problem
please create a separate branch/pr for the other defect (and include a test that demonstrates the problem)
please add an github issue first, and # reference the issue in the commit description and PR description

The code looks ok, but from the web/online diffs the indentation looks wrong. If more commits are needed, please create a new branch and include everything in one commit.

I have started a re-build of this pr

Just want to say thank you for handling this. Enjoy your vacation.


Test 1

@venu162 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Don't use a public repository for your tests, use your own fork!


Add json-ld data

Ref #834

Will add website schema when settings will be available: #743

Codecov Report

Merging #858 into master will increase coverage by -0.01%.

@@            Coverage Diff             @@
##           master     #858      +/-   ##
==========================================
- Coverage   58.74%   58.73%   -0.01%
==========================================
  Files         109      113       +4
  Lines        5885     5957      +72
  Branches      722      728       +6
==========================================
+ Hits         3457     3499      +42
- Misses       2289     2315      +26
- Partials      139      143       +4

Impacted Files
Coverage Δ

saleor/product/views.py
78.84% <100%> (+0.41%)
:white_check_mark:

saleor/product/utils.py
82.35% <60%> (-6.02%)
:x:

saleor/userprofile/views.py
37.83% <ø> (-6.07%)
:x:

saleor/cart/utils.py
78.78% <ø> (-2.88%)
:x:

saleor/cart/models.py
87.82% <ø> (-0.65%)
:x:

saleor/userprofile/adapters.py
100% <ø> (ø)

saleor/order/admin.py
57.89% <ø> (ø)

saleor/product/admin.py
100% <ø> (ø)

saleor/userprofile/admin.py
100% <ø> (ø)

... and 6 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 e9e84f0...c8cf6e1. Read the comment docs.


[7.x] Prompts to configure generated namespace

coverage: 92.833% (-0.1%) from 92.955%
when pulling dae89d7eeba70a7d334138afc3810deade1deebc on 7/confirm-namespace-prefix
into de029d2fa4dc0362e236faf45f73a9fef2eefe27 on 7.x.


[firebase_analytics]: in_app_purchase event is not being auto reported for iOS

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Analytics
Which platforms are affected?
iOS
Description
I've noticed that in_app_purchases event stopped being auto reported by Firebase from July 18th.
We are using firebase_analytics ^11.0.0.

Reproducing the issue
This is an auto reported event, so no reproducible code to add here
Firebase Core version
3.0.0
Flutter Version
3.22.2
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments
No response

Hello, thanks for reporting, can you open this issue in https://github.com/firebase/firebase-ios-sdk please? This looks like an issue with the native SDK.

Got it! Thanks @Lyokone 😄

@juanmasilf Could you share the link to the issue in firebase-ios-sdk? Or Have you found any solution to this?
Thanks in advance 😄


Where can I find code for gaze detection in the repository ?

Exactly which part of code is doing gaze detection ?

questions should go to discussions, not issues.
code is in https://github.com/vladmandic/human/blob/main/src/face/angles.ts


Fixes EventQueue minification bug

The EventQueue relies on constructor.name to map OutlineEvent names to registered listeners. It's a good practice not to rely on name because minifiers and obfuscators can change these values. source
This PR updates the EventQueue to use the OutlineEvent constructor instead of relying on the constructor name. The constructor (__proto__) is assigned when the event is instantiated with the new operator and points to the constructor of the specific event.

This looks great! What a nasty bug.
Could we add unit tests? Were we going to add a prod testing configuration on minified code? There are a lot of claims made in this file. We could test that

subscribing all the different OutlineEvents give us the right number of map entries
subscribe and then publish some events.  Make sure we test enqueue's re-entrancy

Good idea. I added tests for OutlineEvent.
I started a separate fix to add Karma browser tests for the minified Cordova build. I'll add you to it when it's ready.

Yeah, I agree. I'm not used to using functions as keys for Maps.
I would rather replace the entire EventQueue with the EventEmitter
https://github.com/primus/eventemitter3 we use in the manager, assuming
that it's reentrant like our custom one. Maybe that's something we can
tackle next week?
On Thu, Feb 4, 2021 at 4:49 PM alalamav<EMAIL_ADDRESS>wrote:

@alalamav commented on this pull request.
In src/www/model/events.ts
https://github.com/Jigsaw-Code/outline-client/pull/952#discussion_r570567167
:

@@ -50,7 +50,7 @@ export class ServerReconnecting implements OutlineEvent {
export class EventQueue {
private queuedEvents: OutlineEvent[] = [];
// tslint:disable-next-line: no-any

private listenersByEventType = new Map<string, any[]>();

private listenersByEventType = new Map<Function, any[]>();

Good point. I guess it's not feasible, even with an added layer of
indirection. It still feels odd to me to key by Function and would rather
use (arbitrary) strings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/outline-client/pull/952#discussion_r570567167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHWN3TNGVMJ5C2LRTIHO63S5MI77ANCNFSM4XDPY6WA
.


systemd or init.d sripts not working (debian)

hi, first of all, thank you very much for making this gogs awesomeness!
I did used your templates from script folder but cannot get it work, Im just keep stuck on error no matter what I do. When I run ./gogs web everything works fine but as soon as I try to run it with systemd or as daemon will just give me errors. Here is my systemctl status gogs -l get following:
root@dev:~# systemctl status gogs -l
● gogs.service - gogs
   Loaded: error (Reason: Invalid argument)
   Active: inactive (dead)

Nov 12 21:02:24 xxx.com systemd[1]: Starting A self-hosted Git service written in Go....
Nov 12 21:02:24 xxx.com systemd[1]: Started A self-hosted Git service written in Go..
Nov 12 21:02:44 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:6] Unknown lvalue '-quiet --retry' in section 'Service'
Nov 12 21:09:30 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:6] Unknown lvalue '-quiet --retry' in section 'Service'
Nov 12 21:09:30 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:6] Unknown lvalue '-quiet --retry' in section 'Service'
Nov 12 21:09:30 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:6] Unknown lvalue '-quiet --retry' in section 'Service'
Nov 12 21:12:05 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:5] Executable path is not absolute, ignoring: [Unit] ; Description=Gogs (Go Git Service) ; After=syslog.target ; After=network.target ; #After=mysqld.service ; #After=postgresql.service ; #After=memcached.service ; #After=redis.service ;  ; [Service] ; # Modify these two values and uncomment them if you have ; # repos with lots of files and get an HTTP error 500 because ; # of that ; ### ; #LimitMEMLOCK=infinity ; #LimitNOFILE=65535 ; Type=simple ; User=debian ; Group=debian ; WorkingDirectory=/home/debian/gogs ; ExecStart=/home/debian/gogs/gogs web ; Restart=always ; Environment=USER=debian HOME=/home/debian ;  ; [Install] ; WantedBy=multi-user.target
Nov 12 21:12:05 xxx.com systemd[1]: gogs.service lacks ExecStart setting. Refusing.
Nov 12 21:12:05 xxx.com systemd[1]: [/lib/systemd/system/gogs.service:5] Executable path is not absolute, ignoring: [Unit] ; Description=Gogs (Go Git Service) ; After=syslog.target ; After=network.target ; #After=mysqld.service ; #After=postgresql.service ; #After=memcached.service ; #After=redis.service ;  ; [Service] ; # Modify these two values and uncomment them if you have ; # repos with lots of files and get an HTTP error 500 because ; # of that ; ### ; #LimitMEMLOCK=infinity ; #LimitNOFILE=65535 ; Type=simple ; User=debian ; Group=debian ; WorkingDirectory=/home/debian/gogs ; ExecStart=/home/debian/gogs/gogs web ; Restart=always ; Environment=USER=debian HOME=/home/debian ;  ; [Install] ; WantedBy=multi-user.target
Nov 12 21:12:05 xxx.com systemd[1]: gogs.service lacks ExecStart setting. Refusing.
root@dev:~#

OS: debian 8 (jessie - 8.6) - all up to date.

UPDATE: Never mind, I did write my own gogs.service file and managed to get it work :)
Please close this issue as resolved. Thanks.

Hi! Can you provide your gogs.service file? I think others might be interested :)
Btw: You should be able to close issues you've created yourself.

@jhasse hi sure, sorry for late reply, been busy as duck...
Mine is short and sweet ;)
[Unit]
Description=Gogs (Go Git Service)
After=syslog.target
After=network.target
#After=postgresql.service
#After=nginx.service

[Service]
Type=simple
User=git
Group=git
WorkingDirectory=/home/git/gogs
ExecStart=/home/git/gogs/gogs web
Restart=always
Environment=USER=debian HOME=/home/git

[Install]
WantedBy=multi-user.target


Adding TravisCI and Scrutinizer integration

Closed in favor of https://github.com/Nosto/php-sdk/pull/15


MatHttpClientExtension has conflict with Microsoft.AspNetCore.Components.HttpClientJsonExtensions

Describe the bug
Extension collision with Microsoft library: Microsoft.AspNetCore.Blazor.HttpClient.GetJsonAsync
When calling GetJsonAsync, will cause build error ambiguous with Microsoft.AspNetCore.Components.HttpClientJsonExtensions
One workaround is just use the new library from Microsoft...
To Reproduce
Steps to reproduce the behavior:

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

Blazorfiddle link
Please provide a mock implementation of your code on www.blazorfiddle.com - this makes it a lot easier for us and you can get faster feedback on your issue 😉
Hit save and post the URL under this header.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots or .GIF captures to help explain your problem
Additional context
Add any other context about the problem here.

Can you please describe the workaround more thoroughly? You mention to 'just use the new library from Microsoft"... which library are you talking about?

According to blazor wasm preview 3 release note:
extension methods are now available in preview with the System.Net.Http.Json package and they will replace the existing helper methods in the Microsoft.AspNetCore.Blazor.HttpClient package
The old one will have conflict.
The new ones have different name. Here's the table
Microsoft.AspNetCore.Blazor.HttpClient	System.Net.Http.Json
GetJsonAsync	GetFromJsonAsync
PostJsonAsync	PostAsJsonAsync
PutJsonAsync	PutAsJsonAsync

Currently this bug breaks all .net5 builds.
 DepartmantShow.razor(40, 37): [CS0121] The call is ambiguous between the following methods or properties: 'Microsoft.AspNetCore.Components.HttpClientJsonExtensions.GetJsonAsync<T>(System.Net.Http.HttpClient, string)' and 'MatBlazor.MatHttpClientExtension.GetJsonAsync<T>(System.Net.Http.HttpClient, string)'
Cause:
https://github.com/SamProf/MatBlazor/blob/41cbda732c38ece77554cac436c548c2edc18b12/src/MatBlazor/Helpers/MatHttpClientExtension.cs
Can you please remove this if not needed or rename it to not conflict with the blazor framework?

Currently this bug breaks all .net5 builds.
 DepartmantShow.razor(40, 37): [CS0121] The call is ambiguous between the following methods or properties: 'Microsoft.AspNetCore.Components.HttpClientJsonExtensions.GetJsonAsync<T>(System.Net.Http.HttpClient, string)' and 'MatBlazor.MatHttpClientExtension.GetJsonAsync<T>(System.Net.Http.HttpClient, string)'
Cause:
https://github.com/SamProf/MatBlazor/blob/41cbda732c38ece77554cac436c548c2edc18b12/src/MatBlazor/Helpers/MatHttpClientExtension.cs
Can you please remove this if not needed or rename it to not conflict with the blazor framework?

i agree with you

Can you please describe the workaround more thoroughly? You mention to 'just use the new library from Microsoft"... which library are you talking about?

my workaround : downgate matblazor to 2.4.3

'Microsoft.AspNetCore.Components.HttpClientJsonExtensions.GetJsonAsync’ is the msft lib
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From<EMAIL_ADDRESS>Sent: Friday, August 7, 2020 4:21 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [SamProf/MatBlazor] MatHttpClientExtension has conflict with Microsoft.AspNetCore.Components.HttpClientJsonExtensions (#595)
Currently this bug breaks all .net5 builds.
DepartmantShow.razor(40, 37): [CS0121] The call is ambiguous between the following methods or properties: 'Microsoft.AspNetCore.Components.HttpClientJsonExtensions.GetJsonAsync(System.Net.Http.HttpClient, string)' and 'MatBlazor.MatHttpClientExtension.GetJsonAsync(System.Net.Http.HttpClient, string)'
Cause:
https://github.com/SamProf/MatBlazor/blob/41cbda732c38ece77554cac436c548c2edc18b12/src/MatBlazor/Helpers/MatHttpClientExtension.cs
Can you please remove this if not needed or rename it to not conflict with the blazor framework?
i agree with you
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SamProf/MatBlazor/issues/595#issuecomment-670781171, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3FBMUQFFVEASQYXZWISATR7SD6FANCNFSM4NS6THLQ.

I have a workaround for this "The call is ambiguous" problem:
First, I have created a new static class, named HttpClientHelper, adding the following code:
using Microsoft.AspNetCore.Components;
using System.Threading.Tasks;

namespace MyProject.WebGui
{
    public static class HttpClientHelper
    {
        public static Task<T> GetJSONAsync<T>(this System.Net.Http.HttpClient client, string url)
        {
            return client.GetJsonAsync<T>(requestUri: url);
        }
    }
}

Then I iterated through the project's Error List to find the GetJsonAsync references and replaced them with GetJSONAsync. For example:
firma = await HttpClient.GetJSONAsync<Firma>(url.ToString());
Now I'm able to use 2.7.0.
Cheers

I came across this issue when upgrading my project to .NET 5. This can be fixed by just removing Microsoft.AspNetCore.Blazor.HttpClient and replace affected methods such as SendJsonAsync with PostAsJsonAsync. They're not that different and it's not a lot of work.
That's all I need to do to resolve this.

I came across this issue when upgrading my project to .NET 5. This can be fixed by just removing Microsoft.AspNetCore.Blazor.HttpClient and replace affected methods such as SendJsonAsync with PostAsJsonAsync. They're not that different and it's not a lot of work.
That's all I need to do to resolve this.


Multiple plugins in one directory/repo recently broke.

Did you check docs and existing issues?

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

Neovim version (nvim -v)
0.10.0
Operating system/version
Ubuntu 22.04 (WSL)
Describe the bug
mini.nvim is a large collection of plugins within a single repository: https://github.com/echasnovski/mini.nvim
Until now, I have been using the following lazy.nvim configuration in order to download mini.nvim as one repo, but lazily load each of the individual pieces:
{
    "echasnovski/mini.nvim",
    version = "*",
},
{
    name = "mini.splitjoin",
    main = "mini.splitjoin",
    dir = "mini.nvim",
    opts = {
        mappings = {
            toggle = "gs",
        },
    },
    keys = {
        { "gs", nil, mode = {'n', 'x'} },
    },
},
{
    name = "mini.align",
    main = "mini.align",
    dir = "mini.nvim",
    opts = {},
    keys = {
        { "ga", nil, mode = {'n', 'x'} },
        { "gA", nil, mode = {'n', 'x'} },
    },
},

Now, it appears that Lazy will only recognize a single plugin located in a particular directory. Using git bisect, I tracked this issue down to this commit: https://github.com/folke/lazy.nvim/commit/75ffe56f70faac43f077796b91178d2f1419f8ce
Steps To Reproduce

Paste the contents of the repro file below into a file named "repro.lua".
In the directory with that file, run nvim -u repro.lua
--> When the Lazy window shows up, you will see that only one of mini.align or mini.splitjoin are recognized.

Expected Behavior
Previously, both mini.align and mini.splitjoin would be properly loaded.
If support for this loading strategy was intentionally removed, there should be a warning or error message that one of the plugins is ignored.
If there is a better way of solving this, please let me know!
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

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

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

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "echasnovski/mini.nvim",
    version = "*",
  },
  {
    name = "mini.splitjoin",
    main = "mini.splitjoin",
    dir = "mini.nvim",
    opts = {
      mappings = {
        toggle = "gs",
      },
    },
    keys = {
        { "gs", nil, mode = {'n', 'x'} },
    },
  },
  {
    name = "mini.align",
    main = "mini.align",
    dir = "mini.nvim",
    opts = {},
    keys = {
      { "ga", nil, mode = {'n', 'x'} },
      { "gA", nil, mode = {'n', 'x'} },
    },
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

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

I'm sorry, but it was actually a bug that this used to work.
It could actually give all sorts of issues.
The rewrite fixed this.

@folke Is there another recommended way to deal with plugins like this? I've searched through documentation/examples, but haven't been able to find any. As far as I can tell, my options are:

Manually reimplement the lazy-loading logic present in Lazy.nvim via autocmds and custom bindings.
Try to get a second plugin manager (perhaps mini.deps) working alongside Lazy.nvim.
Download each submodule of mini.nvim separately, and somehow ensure that when one is updated, any dependencies are updated to the same version.

None of those options seem particularly great. Am I missing something?

Nope, that's just not supported.


feat: Add smart handling of mounted apps

The old one did not handle mounted apps and always returned the prefix in that case.
Elastic APM code was found at https://github.com/elastic/apm-agent-python/blob/527f62c0c50842f94ef90fda079853372539319a/elasticapm/contrib/starlette/init.py#L242 and is licensed under BSD-3 Clause.

Thank you, @LordGaav


librealsense: 2.11.0 -> 2.11.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/librealsense/versions.
These checks were done:

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.11.1 with grep in /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1

directory tree listing: https://gist.github.com/020e7e6cfc0e9cc89911d68349e47bc7

du listing: https://gist.github.com/dfc212b0151822573970980eb31f8289

meta.description for librealsense is: '"A cross-platform library for Intel® RealSense™ depth cameras (D400 series and the SR300)"'.
cc @brian-dawn for testing.

Failure on aarch64-linux (full log)
Attempted: librealsense
Partial log (click to expand)
FAILED: third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/rostime/src/duration.cpp.o
/nix/store/1biwi46m53fm0h24i6pv8gax0x3xsmsx-gcc-wrapper-7.3.0/bin/g++  -DBUILD_EASYLOGGINGPP -DHWM_OVER_XU -DRS2_USE_V4L2_BACKEND -DUNICODE -isystem /nix/store/mn783a6nvhkipjymzd6k3b2mrkby05m9-libusb-1.0.22-dev/include/libusb-1.0 -I../third-party/realsense-file/rosbag/console_bridge/include -I../third-party/realsense-file/rosbag/cpp_common/include -I../third-party/realsense-file/rosbag/rosbag_storage/include -I../third-party/realsense-file/rosbag/roscpp_serialization/include -I../third-party/realsense-file/rosbag/rostime/include -I../third-party/realsense-file/rosbag/roscpp_traits/include -I../third-party/realsense-file/rosbag/roslz4/include -I../third-party/realsense-file/rosbag/msgs -I../third-party/realsense-file/boost -I../third-party/realsense-file/lz4/lib -std=c++11 -pthread -fPIC -pedantic -g -Wno-missing-field-initializers -Wno-switch -Wno-multichar -Wsequence-point -Wformat-security -mssse3 -O3 -DNDEBUG -MD -MT third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/rostime/src/duration.cpp.o -MF third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/rostime/src/duration.cpp.o.d -o third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/rostime/src/duration.cpp.o -c ../third-party/realsense-file/rosbag/rostime/src/duration.cpp
g++: error: unrecognized command line option '-mssse3'
[84/87] Building C object third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/roslz4/src/xxhash.c.o
FAILED: third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/roslz4/src/xxhash.c.o
/nix/store/1biwi46m53fm0h24i6pv8gax0x3xsmsx-gcc-wrapper-7.3.0/bin/gcc -DBUILD_EASYLOGGINGPP -DHWM_OVER_XU -DRS2_USE_V4L2_BACKEND -DUNICODE -isystem /nix/store/mn783a6nvhkipjymzd6k3b2mrkby05m9-libusb-1.0.22-dev/include/libusb-1.0 -I../third-party/realsense-file/rosbag/console_bridge/include -I../third-party/realsense-file/rosbag/cpp_common/include -I../third-party/realsense-file/rosbag/rosbag_storage/include -I../third-party/realsense-file/rosbag/roscpp_serialization/include -I../third-party/realsense-file/rosbag/rostime/include -I../third-party/realsense-file/rosbag/roscpp_traits/include -I../third-party/realsense-file/rosbag/roslz4/include -I../third-party/realsense-file/rosbag/msgs -I../third-party/realsense-file/boost -I../third-party/realsense-file/lz4/lib -pthread   -fPIC -pedantic -g -D_BSD_SOURCE   -mssse3 -O3 -DNDEBUG -MD -MT third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/roslz4/src/xxhash.c.o -MF third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/roslz4/src/xxhash.c.o.d -o third-party/realsense-file/CMakeFiles/realsense-file.dir/rosbag/roslz4/src/xxhash.c.o   -c ../third-party/realsense-file/rosbag/roslz4/src/xxhash.c
gcc: error: unrecognized command line option '-mssse3'
ninja: build stopped: subcommand failed.
builder for '/nix/store/6nvigv0w4yhnmv7mvpa8d5yb1r4lsyb2-librealsense-2.11.1.drv' failed with exit code 1
error: build of '/nix/store/6nvigv0w4yhnmv7mvpa8d5yb1r4lsyb2-librealsense-2.11.1.drv' failed

Success on x86_64-linux (full log)
Attempted: librealsense
Partial log (click to expand)
ldconfig: Can't create temporary cache file /nix/store/27x7pinqdsl9f3rpbm8bsszd9fhwq266-glibc-2.27/etc/ld.so.cache~: Permission denied
-- Installing: /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1/lib/librealsense-file.a
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1
shrinking /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1/lib/librealsense2.so.2.11.1
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1/lib
patching script interpreter paths in /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1
checking for references to /build in /nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1...
/nix/store/qyy6s8nbpifg33h0hvnpf3fizwdycpvz-librealsense-2.11.1

Success on x86_64-darwin (full log)
Attempted: librealsense
Partial log (click to expand)
-- Installing: /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib/cmake/realsense2/realsense2Config.cmake
-- Installing: /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib/cmake/realsense2/realsense2ConfigVersion.cmake
-- Installing: /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib/pkgconfig/realsense2.pc
-- Installing: /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib/librealsense-file.a
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib
patching script interpreter paths in /nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1
/nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1/lib/librealsense<IP_ADDRESS>.dylib: fixing dylib
/nix/store/mxpi08j8n1yy8qml099ql3qqzc5133px-librealsense-2.11.1


V0.3

Coverage decreased (-13.3%) to 82.73% when pulling 1274fe8e6532e268dfa168a25a78afc1f606c1d8 on v0.3 into b4d6fb05c82f77bf4d6318dd84d9aa5fa989509a on master.

Coverage decreased (-14.9%) to 81.064% when pulling a7ba99337723de55b320eab96d27d33a40d6a00a on v0.3 into b4d6fb05c82f77bf4d6318dd84d9aa5fa989509a on master.

Coverage decreased (-14.9%) to 81.064% when pulling 761343b575098aac12be83599a41b10b270beba2 on v0.3 into b4d6fb05c82f77bf4d6318dd84d9aa5fa989509a on master.

Coverage decreased (-14.9%) to 81.064% when pulling 6437d49e0cede0d20abd61873de5d42ff30bab44 on v0.3 into b4d6fb05c82f77bf4d6318dd84d9aa5fa989509a on master.


phoneStateBackgroundCallbackHandler never responds

It run
"await PhoneStateBackground.initialize(phoneStateBackgroundCallbackHandler);"
and  completed without any problem,  but phoneStateBackgroundCallbackHandler never responds to phone calls.
I added
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
  <uses-permission android:name="android.permission.READ_CALL_LOG" />
  <uses-permission android:name="android.permission.CALL_PHONE" />
  <application
....
      <receiver android:name="me.sodipto.phone_state_background.PhoneStateBackgroundServiceReceiver"
          android:exported="false">
          <intent-filter>
              <action android:name="android.intent.action.PHONE_STATE" />
          </intent-filter>

to AndroidManifest.xml,   what else did I miss?

I had the same issue it turns out I didn't call the _init method, as in the given example it was called by the button.
my code snippet that made it work is this, you can also check in he debug console if you are receiving the messages from the kotlin part like Phone State event IDLE or Fatal: No callback registered to check things out.
`
        Future<void> startMyApp() async {
          await _hasPermission();
          await _init();
        }

        @override
        void initState() {
          WidgetsBinding.instance.addObserver(this);
          startMyApp();
          super.initState();
        }

        Future<void> _init() async {
          if (!hasPermission || listening) return;

          await PhoneStateBackground.initialize(phoneStateBackgroundCallbackHandler);
          listening = true;
        }

`


Refactor to a single Makefile

Currently there appears to be a Makefile for each go package in the project.  This is not really sustainable and adds overhead to refactors.  Packages should be buildable with go build, and there should be a single make target (in kubernetes, we call this make all) that builds all the go packages in the project.

@pmorie I both agree and disagree with this. Makefile per package certainly does sound bad, but I think what's really going on here is a Makefile per distinct component or binary, and that does make some sense to me.

I'll try to summarize how, and why, we ended up with the current setup. At first we had only 'go build' setup. The downsides were:

default package (and binary) names go build picks
no support for Docker image build, in-docker build etc.

Doing some research I kept coming across examples of single-Makefile setups which only had a single binary per repo (so it wasn't quite a fit for our needs, having multiple binaries, Docker images etc.).
So after some trial, error, and incremental reduction in boilerplate I managed to figure out a way where each binary component only contributes few basic things and rest is delegated to shared include makefiles. I found particularly desirable the ability to build individual artifacts -- I have come across attempts to optimize makefiles to correctly spell out target dependencies but it is not pretty, so one way to enable build of individual binaries (and faster builds) is to enable 'make build' or 'make test' in that component's directory
I am not opposed to improvements, nor am I against single-makefile setup if it can allow for

controlling of binary names
docker, in-docker builds, coverage, test, ...
build of all packages at once, or with a finer granularity (and with a simple mnemonic such as 'make build-controller' or some such)

I sense it may be doable to achieve this, perhaps by structuring the top makefile as:
BIN=xxx-bin
PKG=xxx-pkg
include "boilerplate.mk"
BIN=yyy-bin
PKG=yyy-pkg
include "boilerplate.mk"
...
but as I try to imagine what the boilerplate.mk would look like, I am seeing something quite gnarly.

fwiw, I have been down the same road that @martinmaly is describing. It isn't a trivial proposition to avoid DRY exceptions where the commonalities among the builds for n > 1 components in a single repo are concerned while also allowing each build to be adequately customized for each component's needs.

So after some trial, error, and incremental reduction in boilerplate I managed to figure out a way where each binary component only contributes few basic things and rest is delegated to shared include makefiles.

That is generally where I have landed after similar attempts on other projects.
I think that what I'd propose here is that we let this issue sit for now-- let the current build process marinate for a bit while we all get accustomed to it. We can continue to improve it incrementally, but any big refactoring such as what's proposed here should probably occur only after we all have the benefit of greater familiarity on our side.

We don't have to do this right now, but it will have to happen naturally as the codebase expands.

@krancour @martinmaly k8s has a system that allows you to:

Build many or single individual binaries from a single makefile; example: make all WHAT=cmd/hyperkube
Deterministically give generated binaries the names you desire
Not worry about makefiles for individual packages (which is my biggest motivation, I think that is a very strong anti-pattern smell, personally)
Supports local and in-docker build

I think this is an area that has been explored thoroughly upstream -- why doesn't one of you (or both of you) own this and do some investigation upstream?

Walking the chain of how the local build works in Kube:

Makefile:85
hack/make-rules/build.sh:27
hack/lib/golang.sh:466

Docs on docker build: http://releases.k8s.io/HEAD/build-tools/README.md

@pmorie something that concerns me a little bit here is that the volume and complexity of build-related scripts in k8s is a bit of a put-off (for me, personally, at least). I know we have all agreed to be like k8s wherever possible, but I have to ask whether we objectively believe that the way k8s does this is ideal. (This is not at all to say that what we're doing now is any better.) The bottom line is I'm looking for some defense for why the way k8s does it is the right way. I'm not opposed to putting some of my own effort into this as long as we can all agree we're heading in the right direction.

Let me amend the statement above to say that I have an appreciation (a fondness even) for k8s' approach to this. If we can take the same approach, but pare it down to the essentials, I would be ok with it.

This was closed by #182


Add ability to search senders using the 'search' filter

The /senders/ endpoint was updated to support a new search param called search which filters senders by:
the sender name of the a transfer bank details object
    OR
the cardholder name of a debit card details object
    OR
the sender email of a debit card details object

retest this please

retest this please

retest this please


Port collision with primary webserver process

Hello, I was wondering about the decision to include PORT as the default here. My understanding might be wrong but if I have a webserver like Unicorn or Puma I probably have 'PORT' defined in my environment already. When starting the metrics server from my Unicorn process (for example) the metrics server would fail to start due to port collision with the already running unicorn. So I pretty much have to define 'PROMETHEUS_EXPORTER_PORT=9394' even if I'm okay with the default port number.
I'm happy to write up a PR for this change but thought I'd ask about the usage or thoughts behind this line of code first.
Thanks much! Really appreciate this project and your work!
https://github.com/yabeda-rb/yabeda-prometheus-mmap/blob/5edb9f1ca61f3bc0799c83feb624ef2d733ab69d/lib/yabeda/prometheus/mmap/exporter.rb#L25

Hey and sorry for the late response.
In case of web servers, you can use web server itself to expose metrics on different port. For Puma there is built-in support in yabeda-puma-plugin, see Exposing metrics on a different port section in its README.


Add project to SensioInsightLabs

Parent #39

Start
https://insight.sensiolabs.com/projects/b96214d3-35ed-423a-8275-8dc794de7f96/analyses/2

Now on each commit you will have a build that will check for lot of interesting point.
One really nice feature, is that it looks on all known security issue, and I got my build down because my twig version was known to have critical security issue.
to fix it I only had to change the twig version from X.XXX to X.XXY ...I Don't have the time to check for all known security issue, but sensioInsight bots can do it for us :)
Once the technical debt removed, you'll also be able to proudly add the sensioInsgiht badge on your project :)
Really happy to see your project on insight.
It's free for open source projects, but it is really expensive if you have a business / private project.
This cost is not so expensive when you know what it does :)....
To finish, did you know that phpstorm can be free for open source contributors?
https://www.jetbrains.com/buy/opensource/
I am a yellowlabtools member and I am really proud to use my free open source licence when I work on it...If you didn't know about it you I really recommand you to try.
As I can see, you are the third contributor of Gentellela ...So thank you for your really nice work...with this project you should try to get it...
Really happy to work with Gentellela project contributor Great work Really :)

| To finish, did you know that phpstorm can be free for open source contributors?
I've got own private licence.


Add table bitbucket_audit_log

References
Add any related links that will help us understand the resource, including vendor documentation, related GitHub issues, and Go SDK documentation.

Not getting any direct API at Bitbucket level to capture audit logs. However, there is an Atlassian org level API available to fetch the audit log of events.
Reference: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-orgs/#api-orgs-orgid-events-get
https://developer.atlassian.com/cloud/admin/cookbook/#automate-audit-log-backup-exports
@rajlearner17 can you please check once & confirm whether we can use this API


Illegal xargs error shown in Mac OS X

Hi,
Firstly, thanks for your script, which helps me a lot!
But I've got an issue when I run it under OSX, it shown me like this:
JacksonHuMac:bash-onedrive-upload Jackson$ ./onedrive-upload -d -f "temporary" /Volumes/Hu/Photos/2015/xyz/*
2016-01-02 17:21:29 Acquiring new access token
2016-01-02 17:21:39 Searching for 'temporary' in root
2016-01-02 17:21:48 api_folder_id is now 'B*************6!5****5'
xargs: illegal option -- -
usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements]] [-J replstr]
             [-L number] [-n number [-x]] [-P maxprocs] [-s size]
             [utility [argument ...]]

But when I ran the script with the same path and same files under Debian Linux in my virtual machine, it works pretty fine. Also I checked about some articles and someone said the xargs in OSX is not exactly the same as the one in Linux. Maybe that should be the problem, but I don't know how to fix it.
See: http://www.linuxforums.org/forum/newbie/193120-linux-command-macosx-options-xargs.html
Anyway, thanks and happy new year!
Regards,
Jackson

It looks like xargs in OSX supports only the short parameter name for --max-procs. Luckily xargs in Linux supports both parameter versions.

Yep, thanks for your update, I will check it later.

@fkalis Hi, I've found there is still a bug there, which it shown me like this:
./onedrive-upload -f "xyz" -d /Volumes/Untitled/OneDrive/xyz/Backup.MOV
2016-01-04 09:29:20 Acquiring new access token
2016-01-04 09:29:21 Searching for 'xyz' in root
2016-01-04 09:29:23 Creating folder 'xyz' in ''
2016-01-04 09:29:25 api_folder_id is now 'B*************!5*******'
du: illegal option -- b
usage: du [-H | -L | -P] [-a | -s | -d depth] [-c] [-h | -k | -m | -g] [-x] [-I mask] [file ...]
./onedrive-base: line 407: [: -gt: unary operator expected
2016-01-04 09:29:25 Size of Backup.MOV is less than or equal to 104857600 bytes, will use simple upload
2016-01-04 09:29:25 Acquiring new access token
2016-01-04 09:29:26 Uploading '/Volumes/Untitled/OneDrive/xyz/Backup.MOV' as 'Backup.MOV' into B****************16%21*****7
An error has occurred while uploading '/Volumes/Untitled/OneDrive/xyz/Backup.MOV' (Code: 413)

I checked about this, it seems that some of the UNIX systems such as Apple Mac OSX does not support "du -b", you may need to change it to "du -B" instead.
This issue article may helps: https://github.com/lrsjng/h5ai/issues/154
Regards,
Jackson

@fkalis  BTW, the MOV file I mentioned above is nearly 900MB, so it shouldn't use the "simple upload" due to the limitation of M$'s OneDrive API.

Also I've tested on Debian and MinGW Msys in Windows, it works fine for transmitting huge video files.

The simple upload was chosen because du was unable to determine the filesize.
I will have a look at Macs implementation of du tomorrow.

Okay thanks. Also sorry for that I don't know much about bash script.

Hi @fkalis ,
I've just set a pull request with my patch. I use "stat -f%z" instead of "du -b" when it detects the user's OS is Mac OSX.
Regards,
Jackson


TS-4803 Removes the config/support for proxy.config.dns.url_expansions

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/658/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/553/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/669/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/564/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/687/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/583/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/585/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/689/ for details.


Background processes not spawning for bash

Can't create background processes from tasks.json . Basically if I append & to a command it doesn't work …
tasks.json
  "tasks": [
    {
      "type": "shell",
      "label": "start webpack",
      "command": "cd bin && ./startWebpack.sh &"
    },
]

startWebpack.sh
#!/bin/bash
echo "Starting webpack-dev-server"
cd .. && cd client && yarn debug &

Example recording
I start the command just by itself in bash & the script runs, if I start it from vsc it doesn't. This setup still worked yesterday …

When your shell is bash, tasks are run like this:
bash -c cd bin && ./startWebpack.sh &

If you can get your command to run like that, then that's great. However, tasks does provide easier mechanisms for what you're trying to do.
If you want to run a task without showing it and start it in a different directory, try something like this:
		{
			"type": "shell",
			"label": "start webpack",
			"command": "./startWebpack.sh",
			"options": {
				"cwd": "${workspaceFolder}/bin"
			},
			"presentation": {
				"reveal": "never"
			}


PAGA plotting: ValueError: If root is a string, it needs to be one of [None] not 'neoblast 1'

Will try to get to that, but can't guarantee it: https://github.com/theislab/paga/issues/14

You can transfer issues between repos. I transferred it to #909


Added folder structure and first epicsawrap R function

unit tests currently fail
there are a large number of opencdms legacy functions and tests. These will be removed in a future PR

@dannyparsons Please could you give me permissions to merge PRs in this repo?
thanks

I've given you permission. Can you see if you can merge now?

@dannyparsons merged! thanks


initial commit - integrate lighthouse

Draft PR for lighthouse integration

Relevant Issues : (compulsory)
Relevant PRs : (optional)
Type of change :

[ ] New feature

@ptrthomas - this is draft work - something on the lines of progress so far -
Summary -

This solution relies on lighthouse module installed on the local machine - which possibly could be dockerized for docker based images.

axe-core has a selenium driver integration library. From my understanding, Karate implements its own drivers - hence some work will be required to implement axe-core integration libraries. Otherwise axe provide node based api's - required to be installed locally - more here -> https://www.deque.com/axe/core-documentation/integrations/

Lighthouse exposes cli or node module based api's for programmatic integration - nothing possibly in devtools protocol that we can use out-of-the-box. I believe, lighthouse starts its own devtools protocol sessions and has rules builtin to create reports / numbers out of the raw data fetched from devtools session.

This is just a sample - wanted to pick your brain before going too further with this. Please let me know, Thank you for the opportunity.


Fix compile errors and hints

The PR fixes compile errors for FPC, Delphi 7-2007 and hints for Delphi 7-XE5.

FPC: CreateFontIndirect() requires PLogFont
Delphi 7-2007: IsSurrogate used Char=AnsiChar instead of WideChar
Delphi 7-2007: The unit "Character" doesn't exist, but it isn't used anyway
Delphi 7-XE5: The compiler doesn't detect that "totalHeight" is always set in TChunkedText.DrawText(). The "while true do" loop was replaced by a "repeat ... until false" loop.
Delphi 7-XE: FontSorterProc doesn't match the exact function prototype ("const" is not part of the prototype). Interestingly XE2 and newer allow it to be different, if "const" is used on primitive parameter types.

I've incorporated the fixes here into my own revision.


feat(popover): render pop-over at component DOM-level

Adds a prop attachAnchorEl to pop-over
component, that when true, will render
the pop-over at the component DOM-level
and not in the root layer which is by default.
Issue ticket number and link

Fixes #230

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have verified that the code builds perfectly fine on my local system
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have verified that my code follows the style already available in the repository
[x] I have made corresponding changes to the documentation

It might be worth thinking about document.fullscreenElement as well. I just realized that you could do this as well
// Render the pop-over at the same DOM-level as anchorEl
if (document.fullscreenElement !== null) {
  return popOverElement
}

Looks ok by me

LGTM.


BigQuery's unnest function implementation overrides and breaks this function for other dialects

If bigquery is installed, the unnest function (defined here) it overrides the unnest function for all dialects.
In PostgreSQL usage of unnest is allowed with column identifiers (unnesting the an array contained in a table column). But the global re-definition of unnest caused by bigquery makes code like this  sa.func.unnest(some_column) fail with TypeError: The argument to unnest must have an ARRAY type. because, obviously, a column is not an array literal.
In my case I really do need many dialects installed at the same time.

The best fix I can think of is to move the logic from this class to the visitor that renders functions in the BQ dialect implementation

Sorry to hear that you are running into this issue. Thank you submitting this bug/feature request.
If you happen to have code OR a patch that you would like to submit to address this issue feel free to submit a PR.
In the meantime, I will consider this feature request and explore where it should fit in our priority list based on current staffing and workloads.

Is there an ETA on this? This is complicating our upgrade to sqlalchemy 2.
In case this helps anyone else experiencing this issue, our workaround was to always unregister the unnest function before connecting to postgresql and then always register it again before connecting to bigquery.

Is deprecation acceptable? Couple of options I was poking at:

Set package = "bigquery" as described in the docs - implementation moves to sqlalchemy.func.bigquery.unnest
Export an unnest wrapper that applies this validation, then returns plain old sqlalchemy.func.unnest - the postgres dialect does something similar for array_agg (link here)

I didn't really see a good way to do this without a deprecation period though - I looked at this suggestion:
https://github.com/googleapis/python-bigquery-sqlalchemy/issues/882#issuecomment-1643662580
but it seems like once we're about to render the function, its too late to apply this validation.


Moya_Logger: [01/12/2019 11:25:49] Response: Received empty network response

what's this mean?
same url same request method , postman get response, but moya show this log, I don't know why

Before Moya 14 the logger's behavior was to log Received empty network response for <target> if the request resulted with an error, regardless of the error. That means this would be logged for a connection error like a timeout, but also for a validation error (checking the http code). In the first case logging an empty response could make sense, but in the second case It could not as the API may have returned some data with the http error.
In Moya 14.0.0-beta.1 the logger have been reworked and this behavior corrected.

all message should be shown no matter which type error
I receive this response regardless of  online or offline, even change request method, how can I log  more valuable message

You have multiple options:

Update to Moya 14 beta 1 or later to include the new logger.
Stay on your version of Moya and copy/paste the new logger into your project and replace your actual logger by the new one in the plugins list.
Stay on your version of Moya and create your own plugin that will logs event according to your needs.

thank you, I'll try it


Allow port configuration of the server

Hello,
The server will automatic bind to <IP_ADDRESS>:8080. Do you think it would be to much work to make the port configurable?
Thanks a lot :-)

I think some of the variables should be extracted and exposed to the user as a custom variable. I don't know which ones yet but this can be one of them.
You can also set the server port using simple-httpd directly before starting the server.
(require 'simple-httpd)
(setq httpd-port 8888)

but it would be much more convenient with a custom variable.

Thanks for the answer! I guess this is enough for my use case :-)

Added port as a customizable variable.
For example;
(use-package org-roam-server
  :ensure t
  :config (setq org-roam-server-port 8888))


[Bug] 打包时候，error: failed to get tauri-plugin-window-state as a dependency of package `app v0.1.0 (C:\Users\hitime\AppData\Roaming\npm\node_modules\pake-cli\src-tauri)

Search before asking

[X] 我在 issues 列表中搜索，没有找到类似的内容。
I searched in the issues and found nothing similar.

Pake version
2.3.3
System version
wind10
Node.js version
20.8.0
Minimal reproduce step
当我执行打包命令后日志如下，网络正常可以访问谷歌等墙外网站，管理员权限cmd
✼ No icon given, default in use. For a custom icon, use --icon option.
✼ The first use requires installing system dependencies.
✼ See more in https://tauri.app/v1/guides/getting-started/prerequisites.
✺ Installing package...
up to date, audited 226 packages in 1s
69 packages are looking for funding
run npm fund for details
1 low severity vulnerability
Some issues need review, and may require choosing
a different dependency.
√ Package installed!
✼ The first packaging may be slow, please be patient and wait, it will be faster afterwards.
✸ Building app...

<EMAIL_ADDRESS>build
npm run tauri build --release
✶ Building app...

<EMAIL_ADDRESS>tauri
tauri build
✺ Building app...
error: failed to get tauri-plugin-window-state as a dependency of package app v0.1.0 (C:\Users\hitime\AppData\Roaming\npm\node_modules\pake-cli\src-tauri)

Caused by:
failed to load source for dependency tauri-plugin-window-state
Caused by:
Unable to update https://github.com/tauri-apps/plugins-workspace?branch=v1#5b814f56
Caused by:
failed to fetch into: C:\Users\hitime.cargo\git\db\plugins-workspace-fd0259fcb18f51ad
Caused by:
could not execute process git fetch --force --update-head-ok https://github.com/tauri-apps/plugins-workspace +5b814f56e6368fdec46c4ddb04a07e0923ff995a:refs/commit/5b814f56e6368fdec46c4ddb04a07e0923ff995a (never executed)
Caused by:
program not found
Error failed to build app: failed to build app
file:///C:/Users/hitime/AppData/Roaming/npm/node_modules/pake-cli/dist/cli.js:375
reject(new Error(${code}));
^
Error: 1
at file:///C:/Users/hitime/AppData/Roaming/npm/node_modules/pake-cli/dist/cli.js:375:24
at C:\Users\hitime\AppData\Roaming\npm\node_modules\pake-cli\node_modules\shelljs\src\exec.js:145:9
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:514:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)
Node.js v20.8.0
What did you expect to see?
我希望她是正确的执行
What did you see instead?
不知道现在这个问题是什么情况
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

似乎是没安装git的问题，安装了git后正常打包了


_has Parameter

I can't seem to be able to figure out how to implement a _has parameter. I've tried declaring the parameter in a search annotated method, but it doesn't recognize the signature. Is there a sample somewhere?
The practitioner example here is exactly my use case:
https://groups.google.com/forum/#!topic/hapi-fhir/xYw7XH49unU

The JPA server's resource providers should be a good guide:
http://hapifhir.io/xref-jpaserver/ca/uhn/fhir/jpa/rp/dstu2/PatientResourceProvider.html
(ps- please close this ticket if this is just a question and not a bug)


Internationalization

Hi !
Amazing job on this library, it is so usefull.
Howerver I'm strugling will one thing : does the ToString function support units in other languages ?It does support english units (KB, MB, GB), but I'm having trouble with french.
In french a byte is called an "octet", so the units are writen like "Ko", "Mo", "Go"...

I can do something like
myByteSize.ToString("GB").Replace("GB", "Go")
but it's not very clean.
Am I missing something ?
If not, any chance to see an internationalization feature in the future ?
Thanks :)

FYI: It's "ko" or "Kio", not "Ko" (https://fr.wikipedia.org/wiki/Octet) ;-)

@NJullienSweet, yes I accept PRs and have accepted multiple ones already. The one in May has my feedback on it which needs to be addressed by the author before I merge it in.
If you have time to implement i18n, happy to review and merge it in.


[SPARK-6123] [SPARK-6775] [SPARK-6776] [SQL] Refactors Parquet read path for interoperability and backwards-compatibility

This PR is part of [SPARK-6774] 2, which aims to ensure interoperability and backwards-compatibility for Spark SQL Parquet support.  And this one fixes the read path.  Now Spark SQL is expected to be able to read legacy Parquet data files generated by most (if not all) common libraries/tools like parquet-thrift, parquet-avro, and parquet-hive.
Major changes:

CatalystConverter class hierarchy refactoring

Replaces CatalystConverter trait with a much simpler ParentContainerUpdater.
Now instead of extending the original CatalystConverter trait, every converter class accepts an updater which is responsible to propagate the converted value to some parent container. For example, appending array elements to a parent array buffer, appending a key-value pairs to a parent mutable map, or setting a converted value to some specific field of a parent row. Root converter doesn't have a parent and thus uses a NoopUpdater.
This simplifies the design since converters don't need to care about details of their parent converters anymore.

Unifies CatalystRootConverter, CatalystGroupConverter and CatalystPrimitiveRowConverter into CatalystRowConverter
Specifically, now all row objects are represented by SpecificMutableRow during conversion.

Refactors CatalystArrayConverter, and removes CatalystArrayContainsNullConverter and CatalystNativeArrayConverter
CatalystNativeArrayConverter was probably designed with the intention of avoiding boxing costs. However, the way it uses Scala generics actually doesn't achieve this goal.
The new CatalystArrayConverter handles both nullable and non-nullable array elements in a consistent way.

Implemented backwards-compatibility rules in CatalystArrayConverter
When Parquet records are being converted, schema of Parquet files should have already been verified. So we only need to care about the structure rather than field names in the Parquet schema. Since all map objects represented in legacy systems have the same structure as the standard one (see [backwards-compatibility rules for MAP] 1), we only need to deal with LIST (namely array) in CatalystArrayConverter.

Requested columns handling
When specifying requested columns in RowReadSupport, we used to use a Parquet MessageType converted from a Catalyst StructType which contains all requested columns.  This is not preferable when taking compatibility and interoperability into consideration.  Because the actual Parquet file may have different physical structure from the converted schema.
In this PR, the schema for requested columns is constructed using the following method:

For a column that exists in the target Parquet file, we extract the column type by name from the full file schema, and construct a single-field MessageType for that column.
For a column that doesn't exist in the target Parquet file, we create a single-field StructType and convert it to a MessageType using CatalystSchemaConverter.
Unions all single-field MessageTypes into a full schema containing all requested fields

With this change, we also fix [SPARK-6123] 3 by validating the global schema against each individual Parquet part-files.

Merged build triggered.

Merged build started.

Test build #36553 has started for   PR 7231 at commit 3581497.

Test build #36553 has finished for   PR 7231 at commit 3581497.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36554 has started for   PR 7231 at commit 9b87903.

Test build #36554 has finished for   PR 7231 at commit 9b87903.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36557 has started for   PR 7231 at commit 8be4723.

Test build #36557 has finished for   PR 7231 at commit 8be4723.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@rdblue As usual, you're always welcome to help reviewing this :-) As you suggested, the main part of this PR (CatalystRowConverter) takes parquet-avro as the reference and mostly resembles AvroIndexedRecordConverter.
@scwf It would be nice if you can help testing this PR against your legacy Hive data. It should fix the Parquet compatibility issue you mentioned to me. Thanks!
@Sephiroth-Lin Also would like to know whether this fixes your issue behind SPARK-8811. Thanks!

@liancheng, thanks! I'll make some time to look at it this week. Most likely Wednesday.

Merged build triggered.

Merged build started.

Test build #36593 has started for   PR 7231 at commit 8216e95.

Test build #36593 has finished for   PR 7231 at commit 8216e95.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Build triggered.

Build started.

Test build #36672 has started for   PR 7231 at commit e94cb1c.

Test build #36672 has finished for   PR 7231 at commit e94cb1c.

This patch fails RAT tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Build triggered.

Build started.

Test build #36710 has started for   PR 7231 at commit 9c91c8a.

Test build #36710 has finished for   PR 7231 at commit 9c91c8a.

This patch fails RAT tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Build triggered.

Build started.

Test build #36721 has started for   PR 7231 at commit 1941766.

Test build #36721 has finished for   PR 7231 at commit 1941766.

This patch fails RAT tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36722 has started for   PR 7231 at commit 440b543.

Test build #36722 has finished for   PR 7231 at commit 440b543.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DecisionTreeClassificationModel(DecisionTreeModel):
class RandomForestClassificationModel(TreeEnsembleModels):
class GBTClassificationModel(TreeEnsembleModels):
class DecisionTreeModel(JavaModel):
class TreeEnsembleModels(JavaModel):
class DecisionTreeRegressionModel(DecisionTreeModel):
class RandomForestRegressionModel(TreeEnsembleModels):
class GBTRegressionModel(TreeEnsembleModels):

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36724 has started for   PR 7231 at commit fdc106a.

Test build #36724 has finished for   PR 7231 at commit fdc106a.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36729 has started for   PR 7231 at commit 6e29706.

Test build #36729 has finished for   PR 7231 at commit 6e29706.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36730 has started for   PR 7231 at commit d1ca5ed.

Test build #36730 has finished for   PR 7231 at commit d1ca5ed.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36732 has started for   PR 7231 at commit 54bfeb3.

Test build #36732 has finished for   PR 7231 at commit 54bfeb3.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36738 has started for   PR 7231 at commit 497cbe0.

Test build #36738 has finished for   PR 7231 at commit 497cbe0.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36747 has started for   PR 7231 at commit 7946ee1.

Test build #36747 has finished for   PR 7231 at commit 7946ee1.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36764 has started for   PR 7231 at commit 926af87.

Test build #36764 has finished for   PR 7231 at commit 926af87.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36767 has started for   PR 7231 at commit 598c3e8.

Test build #36767 has finished for   PR 7231 at commit 598c3e8.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36769 has started for   PR 7231 at commit c6fbc06.

Test build #36769 has finished for   PR 7231 at commit c6fbc06.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #36819 has started for   PR 7231 at commit 360fe18.

Will probably merge this soon after Jenkins says OK as it blocks other work.  More compatibility tests need to be done, but I'd like to leave them to follow-up PRs (ordered by importance):

Compatibility tests for older versions of Spark SQL
More patterns of nested complex types
Avro enum
Possibly compatibility tests for parquet-protobuf

Test build #36819 has finished for   PR 7231 at commit 360fe18.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@yhuai Thanks for the review! I'm merging this to master now.
@rdblue Please feel free to comment from the perspective of the Parquet spec and compatibility. Thanks!


VerificationEnroll function does not work in NET 6.0

Hi,
I am enrolled in the Speaker Recognition capability and very eager to try out this functionality. However when I try to compile the example method VerificationEnroll I get the following error in Visual Studio for Mac 2022 Preview:

If I change phraseResult into a normal variable within the function scope, the code compiles but crashes on the "Speak the passphrase" console printout since phraseResult.Phrases does not exist.
I get these results for client, profile and phrasesResult
client -> {"Properties":{},"IsDisposed":false}
profile -> {"Id":"","Type":2,"IsDisposed":false}
phrasesResult -> {"ResultId":"DC8162328FA142ED85EFF0265A8D7672","Reason":1,"Phrases":null,"Properties":{}}
What am I doing wrong?
regards,
Djim
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 90378d9c-eeb4-f8c5-2f38-a5132a7f303f
Version Independent ID: a2e20d39-eb18-e7d2-749c-6955bf739d2c
Content: Speaker Recognition quickstart - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/get-started-speaker-recognition.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @eric-urban
Microsoft Alias: eur

@djimmo I think the issue in this case is the list of phrases are not returned. The list of phrases should be the following mentioned here. This may be an issue with the SDK if you are provided access to the functionality and the API does not return the phrases. I have noticed 1 user reported similar issue with Xamarin SDK with the speech SDK repo.
I think it would be great if you could post the issue on SDK repo too, so the SDK team could address any potential bug. Thanks!!

https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1356

@djimmo - I'll close this as duplicate of the issue you opened in the samples repo. I see there is already traction / progress over there. Thanks!

#please-close


Crash on TSPLib dimension 1 probleme

NAME: vroom
TYPE: ATSP
DIMENSION: 1
EDGE_WEIGHT_TYPE: EXPLICIT
EDGE_WEIGHT_FORMAT: FULL_MATRIX
EDGE_WEIGHT_SECTION
0
EOF

Good point. The check for dimension over 2 is only present in the osrm loader...


build: Disable compiler warning maybe-initialized.

This is causing warnings in some uses of absl::optional.
Signed-off-by: Greg Greenway<EMAIL_ADDRESS>Risk Level: Low
Testing: Compiled https://github.com/envoyproxy/envoy/pull/2793 with this change, verified that build was fixed.

@ggreenway not sure about CI issues. Can you also note "fixes" in the description for the issue tracking this?

Looks like this is failing on clang due to errors about unknown option name. I'll sort out how to fix.


Set minimum django version

This adds django 2.2 to the requirements list. Without it listed like this, dependency management tools will think that this versions > 3.0 of django extensions can be installed on older versions of django. In our case, dependabot recommended that we upgrade to version 3.11 of this library, but we do not have a compatible version of django (yes, I know, we should; we're getting there!)
It'd be great to get this small fix in place so that dependabot and other compatibility checkers can ensure that only compatible versions are installed.

Coverage decreased (-0.2%) to 70.949% when pulling 07db3f6cf83010a6ab576d575bceb6883e9dbcc0 on mlissner:patch-1 into 01b6ea80af90d3d848a44d7e72157ae6db3d5e0b on django-extensions:master.

Thanks for the PR and sorry for the delay.
There where some reasons in the past why I didn't add it but I cannot find a good reason not to add the minimum requirement today ;-)
New release should be out (relatively) soon.
However this would only solve this issues in the future... let me try to create a 3.1.1post1 as well...

https://pypi.org/project/django-extensions/3.1.1.post1/
Hope this works for dependabot (etc), the post1 release should indicate to them they should use the new package metadata... https://pythonpackaging.info/07-Package-Release.html


Store log-files in a cloud

Currently, log files are stored localy on the execution environment. This prevents easy access to the log files for all developers.
Change
Implement an interface to the google drive API, so that the daily created log files can automatically be stored in the developer cloud.
Prerequisite
Issue #16 & #27

Will be done manually.


ACE icons limitations

Category

[ ] Content fix
[x] New article

What's in this Pull Request?
The article describes ACE platform limitations for Fluent UI Iconography and provides a list of supported icons.

merging - running validations and updating as needed as part of the 1.18 release update


[DO NOT MERGE] Empty commit to trigger review app :warning:

Context
Ticket: https://dfedigital.atlassian.net/browse/CPDLP-3084
Empty commit to trigger a review app so the ticket above can be PO tested.

Ticket has been PO tested and was moved to Done.


⚠ SceneTime has degraded performance

In 72599e6, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 6164 ms

Resolved: SceneTime performance has improved in edb4a47 after 5 minutes.


Added UI for edit environment.

:nut_and_bolt: Description: What code changed, and why?
We need to add UI for EDIT Environment

:chains: Related Resources
#4545
:+1: Definition of Done
Added edit functionality for Environment in which we can edit:

cookbook constraints
Attributes: default, override

:athletic_shoe: How to Build and Test the Change
STEP 1
inside the hab studio

[default:/src:0]# build components/automate-ui-devproxy/
[default:/src:0]# start_automate_ui_background
[default:/src:0]# start_all_services

STEP 2
open new window
go to automate UI path

$ cd components/automate-ui
and run the command

npm run serve:hab

To add data https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views
Steps:

Go To  Infrastructure -> Chef Servers -> click server name-> click on org name -> Environment
Click on and Environment name -> Cookbook constraint Tab -> click on edit button for editing cookbook.
Click on Attribute tab -> click on edit button for default or override  attribute.

:white_check_mark: Checklist

[ ] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[ ] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

Add no preview image in attributes tab if no JSON available
Change border-size of details box 1px.
When we click the button of edit or expand we have to click twice then the pop-up visible. need to update this.
Edit, Expand, collapse buttons are not keyboard accessible.


Apidya not in games.txt

As a user of Zaparoo (ex Tapto) I want to start Apidya via NFC Reader Card but there is no entry of the game in the games.txt :-(
Go on
Thanks

Duplicate of #204


Scope Studio not compiling or submitting job

Type: Bug
I have followed install instructions and tried to submit a script in my repo. The script submits and executes successfully using Visual Studio 2022, but not in VS Code. I am submitting to cosmos15: asimov.partner.ptp.
I see nothing that happens after I right click on my script and try to compile it or submit a job.
I see a persistant prompt on the bottom bar that says "SCOPE: click to select account". After I click it and select my preferred account, the prompt does not go away.
I have tried signing out and in of my Microsoft account, and I have tried uninstalling and reinstalling Scope Studio.
Extension version: 0.1.0
VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:26:35.552Z)
OS version: Windows_NT x64 10.0.25393
Modes:

System Info

Item
Value

CPUs
AMD Ryzen Threadripper PRO 3945WX 12-Cores      (24 x 3992)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
63.86GB (40.84GB free)

Process Argv
--crash-reporter-id e5878a29-eec0-4e01-bb23-931812133a2b

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
282f8724:30602487
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
24365598:30736109
pythonfmttext:30731395
pythoncmv:30756943
fixhidewlkth:30730051
showsbindicator:30760979
pythongtdpath:30739704
dh2dc718:30763024
pythonnosm12tcf:30765602

The root cause should be did not install the dependencies, to trigger the install(if not install automatically), you need open/create a new SCOPE script or try any command of SCOPE below in command pallete.

I've tried this. I uninstalled SCOPE Studio and deleted the cached directory within .vscode/extensions on my system. I reinstalled SCOPE Studio and did as you suggested, but no dependencies were downloaded.

SCOPE VS Code introduces a new vc format [cluster].[vcname]. And it is incorrectly parsed here...
A workaround is to open .scope/scriptSettings.json and change account from cosmos15.asimov.partner.ptp to vc://cosmos15/asimov.partner.ptp and reload window.

It should be good with v0.1.1-preview now.

Great, I think this issue is resolved.


7.1.0 elasticsearch error

I've just tried updating 7.0.9 to 7.1.0 but exceptionless app fails:
Starting Elasticsearch...

chown: invalid user: 'elasticsearch:elasticsearch'
Could not execute because the application was not found or a compatible .NET SDK is not installed.
Possible reasons for this include:
  * You intended to execute a .NET program:
      The application 'Exceptionless.Job.dll' does not exist.
  * You intended to execute a .NET SDK command:
      It was not possible to find any installed .NET SDKs.
      Install a .NET SDK from:
        https://aka.ms/dotnet-download

I'm using a similar config as https://github.com/exceptionless/Exceptionless/blob/master/samples/docker-compose.yml
E: Downgrading to 7.0.9 makes it run again.

@ejsmith Can you take a look into this.

I could update Elastic itself to 7.14.0 while running 7.0.9 app + job. It seems a bit odd that App tries to run Job, in 7.0.9 this DLL is not present. Maybe the image is mistaken for the all in one?

Would you mind sharing your configuration file minus the connection strings.

Here's the file (now at 7.0.9 again)
version: '3.7'

services:
  app:
    depends_on:
      - elasticsearch
      - redis
    image: exceptionless/app:7.0.9
    environment:
      EX_AppMode: Production
      #ASPNETCORE_URLS: http://+;https://+
      #ASPNETCORE_HTTPS_PORT: 5001
      #ASPNETCORE_Kestrel__Certificates__Default__Password: password
      #ASPNETCORE_Kestrel__Certificates__Default__Path: /https/aspnetapp.pfx
      EX_RunJobsInProcess: 'false'
      EX_EnableAccountCreation: 'false'
      EX_EnableArchive: 'false'
    ports:
      - 15080:80
      - 15443:443
    volumes:
      - exceptionless_appdata:/app/storage
      - exceptionless_ssldata:/https

  jobs:
    depends_on:
      - app
    image: exceptionless/job:7.0.9
    environment:
      EX_AppMode: Production
      EX_BaseURL: http://localhost
    volumes:
      - exceptionless_appdata:/app/storage

  elasticsearch:
    image: exceptionless/elasticsearch:7.14.0
    environment:
      discovery.type: single-node
      xpack.security.enabled: 'false'
      bootstrap.memory_lock: 'true'
      ES_JAVA_OPTS: -Xms2g -Xmx2g
    ports:
      - 19200:9200
      - 19300:9300
    volumes:
      - exceptionless_elastic7:/usr/share/elasticsearch/data

  redis:
    image: redis:6.2.5-alpine
    ports:
      - 16379:6379

@ejsmith Did you take a look at it?

@PhyxionNL this has been fixed in the latest docker images. Sorry, I thought we replied in here already. Can you try the latest images and let me know how it goes?

No problem 😁 It's working now, thanks 🎉


Uncaught TypeError: Cannot read property 'startsWith' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.23.0-beta0 x64
Electron: 1.6.15
OS: Mac OS X 10.13.1
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'startsWith' of undefined
At /Applications/Atom Beta.app/Contents/Resources/app/node_modules/tree-view/lib/tree-view.js:187

TypeError: Cannot read property 'startsWith' of undefined
    at /Applications/Atom Beta.app/Contents/Resources/app/node_modules/tree-view/lib/tree-view.js:187:41
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:25:20)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:141:34)
    at atom.confirm.buttons.Move to Trash (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/tree-view/lib/tree-view.js:1226:37)
    at ApplicationDelegate.module.exports.ApplicationDelegate.confirm (/Applications/Atom Beta.app/Contents/Resources/app/src/application-delegate.js:229:55)
    at AtomEnvironment.module.exports.AtomEnvironment.confirm (/Applications/Atom Beta.app/Contents/Resources/app/src/atom-environment.js:1031:45)
    at TreeView.module.exports.TreeView.removeSelectedEntries (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/tree-view/lib/tree-view.js:1213:25)
    at HTMLElement.tree-view:remove (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/tree-view/lib/tree-view-package.js:32:66)
    at CommandRegistry.handleCommandEvent (/Applications/Atom Beta.app/Contents/Resources/app/src/command-registry.js:388:36)
    at CommandRegistry.dispatch (/Applications/Atom Beta.app/Contents/Resources/app/src/command-registry.js:273:23)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchContextMenuCommand (/Applications/Atom Beta.app/Contents/Resources/app/src/atom-environment.js:1399:34)
    at EventEmitter.outerCallback (/Applications/Atom Beta.app/Contents/Resources/app/src/application-delegate.js:348:31)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:194:7)

Commands
     -0:39.6.0 core:move-down (input.hidden-input)
     -0:38.6.0 docblockr:parse-enter (input.hidden-input)
     -0:38.6.0 editor:newline (input.hidden-input)
     -0:32.7.0 core:save (input.hidden-input)
     -0:29.3.0 core:copy (input.hidden-input)
     -0:28.1.0 core:paste (input.hidden-input)
     -0:27.7.0 core:backspace (input.hidden-input)
     -0:26.3.0 autocomplete-plus:confirm (input.hidden-input)
  2x -0:25.3.0 core:move-down (input.hidden-input)
     -0:24.6.0 core:move-left (input.hidden-input)
     -0:24.3.0 editor:select-to-beginning-of-word (input.hidden-input)
     -0:24.2.0 datatip:toggle (input.hidden-input)
     -0:24.1.0 core:select-right (input.hidden-input)
     -0:22 editor:move-to-end-of-screen-line (input.hidden-input)
     -0:21.9.0 core:save (input.hidden-input)
     -0:04.6.0 tree-view:remove (span.name.icon.icon-file-directory)

Non-Core Packages
atom-ide-ui 0.5.4
blame 0.12.0
busy-signal 1.4.3
docblockr 0.13.2
editorconfig 2.2.2
file-icons 2.1.13
haskell-grammar 0.4.0
highlight-selected 0.13.1
hyperclick 0.0.0
ide-flowtype 0.17.4
ide-php 0.6.10
intentions 1.1.5
language-babel 2.78.0
language-docker 1.1.8
language-gherkin 1.0.4
language-graphql 0.9.0
language-ini 1.19.0
language-lua 0.9.11
language-nginx 0.8.0
language-pug 0.0.21
language-rust 0.4.12
language-swift 0.5.0
language-terraform 0.8.1
language-thrift 1.0.2
language-vue 0.23.1
linter-php 1.5.1
linter-phpcs 1.6.8
linter-phpmd 2.0.0
MagicPython 1.0.12
php-cs-fixer 4.1.1
php-debug 0.2.5
php-integrator-annotations 1.2.0
php-integrator-autocomplete-plus 1.6.1
php-integrator-base 3.1.0
php-integrator-refactoring 1.4.1
php-integrator-symbol-viewer 0.6.4
php-twig 4.0.0
project-manager 3.3.5
set-syntax 0.4.0
sort-lines 0.18.0

Thanks for the report!  Can you confirm a few things for us?

what were you doing at the time of the error?
is the error is reproducible?
if reproducible, do you see the error in safe mode (atom --safe)?

Just got this on Win7 when trying to delete a folder from the tree view.
Not sure if relevant, but I did have the file inside (index.js) opened in Atom the first time I tried to delete it. This beautiful GIF is from the consecutive tries, after closing the file:

Whoops.  getPath() can return undefined on Untitled editors.  Working on a fix now.


The button text does not center vertically

Version
0.6.15
Environment
0.6.x, chrome65
Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-setup-fpbch6?file=app/app.component.html
Steps to reproduce

Open the site page.
Show the button text

What is expected?
The button text should be center vertically.
What is actually happening?
The button text below the middle.
Other?

Later, I'll commit a pr to fix it.

Ok, thanks~