App lifecycle problems

Hello, firstly this is a great framework.
I have a problem. When the application goes to the background and comes to the front again, the image or video preview closes and returns to the shooting screen, this is a problem, the second problem is that when I try to shoot again after this scenario, I get a crash.
Why doesn't the app continue where I left off when I put it in the background and then bring it back to the foreground?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> and i get a crash for take a picture after background/foregroung. Because I guess CameraInputView is being recreated.
Thank you

Hey @clbemre, thanks for this ticket!
I'm currently busy developing an update for our other library (NavigationView), but I'll be back here as soon as I finish that task (probably at the end of this week).
I hope it suits you, thanks again for your ticket and have a nice day,
T.K.

Hello again @FulcrumOne, thank you for your interest.
Additionally, when there is a CameraPreview screen displayed, if I display an alert on the screen with MJCameraController().alert { }, the CameraPreview closes. I want to maintain its state and prevent the preview screen from closing unless I close it myself.

Hello again @FulcrumOne, when will you fix these topics? or will?
Thank you.

hey @clbemre,
Sorry, had a lot of work related to our other libraries. In my calendar, work on this library is scheduled to start this Thursday

Apologies for the "communication issues" once again; I believe creating a Discord / Slack channel would help us stay better connected and updated on things related to libraries. I'll try to organize it this week 😉
Have a great day,
Tomasz K.

Thank you @FulcrumOne , I will be waiting for your response.
Thank you for your interest.
Have a nice day.
Best Regards

Hello again, @FulcrumOne , have you started this issues solutions? I'm sorry for bothering you but its a little important for me :)
Thank you again.

Hey, I'm starting this evening😉 Hope it will be ready by the weekend

Hello, firstly this is a great framework.
I have a problem. When the application goes to the background and comes to the front again, the image or video preview closes and returns to the shooting screen, this is a problem, the second problem is that when I try to shoot again after this scenario, I get a crash.
Why doesn't the app continue where I left off when I put it in the background and then bring it back to the foreground?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> and i get a crash for take a picture after background/foregroung. Because I guess CameraInputView is being recreated.
Thank you

hey @clbemre, just to confirm - you're telling that you experienced a crash when you backgrounded the app and then returned to the foreground, correct?

@clbemre, that second problem (with alert and crash I was able to reproduce, so I'll start from this one)

First of all, there are a few problems; after the first startup, it puts it in the background without doing anything, and when it comes back to the foreground, it crashes while trying to take a photo/video. Then, after showing an alert while on the preview screen, both the preview screen disappears and when I try to take a photo or video again, it crashes again, and sometimes it is because of the cameraView superView and sometimes it is because of the blurViews, but I think the problem is common, because as far as I understand, the camera manager is deinit/init and the swiftUI randomly appears on the screen. because of their renderings.
Additionally , independently of these, the snapshot and blurview you showed while flipping the camera are turned landscape.
Sorry for my english, sometimes i use translate :)

hey @clbemre,
No problem, English is not my native language either (it would be nice if we both spoke Polish 😅)
Could you please test the branch called 'patch-1.2.1', it should fix your problem with alert that causes the app to crash?
You should also add this method to your MCameraController - .equatable() (it's a temporary solution)

Hey @FulcrumOne  this temporary solution works. Thank you. 💪🏻
Are we going to continue with this temporary solution or are you continuing to work on resolving the issue at its base? As far as I can see, you are working on memory leaks in particular.

hey @clbemre, thanks for letting me know!
I want to spend some time today and check the library for problems with memory leaks, and then I will move on to fixing this issue with the background mode.

Hey @FulcrumOne , also we have a little problem :) when First launch MCameraController, the system want to permission.  I'll keep you in the loop😉

okey @FulcrumOne  thank you for your response. I'll be wating for you. Good luck :)

Hey @clbemre,
So we have two potential solutions to our problem:
We can move CameraManager to the level above (i.e. the parent view in which MCameraController is implemented, managed by the developer). Additionally if we opt for this option, I would also like to move the functions from the Public+MCameraController file lines 15 -> 43 to the CameraManager initialiser.
We can make CameraManager singleton; this will allow us to avoid major changes to the public API, however, there may be some issues when trying to port the library to iPadOS and macOS.
Therefore, I think that, in the long term, a better solution will be to implement point 1. What do you think?

@clbemre,
The branch named patch-1.2.1-beta contains fixes to the following problems:

MCameraController and error screen
Alert interrupting camera session

Hello, firstly this is a great framework.
I have a problem. When the application goes to the background and comes to the front again, the image or video preview closes and returns to the shooting screen, this is a problem, the second problem is that when I try to shoot again after this scenario, I get a crash.
Why doesn't the app continue where I left off when I put it in the background and then bring it back to the foreground?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> and i get a crash for take a picture after background/foregroung. Because I guess CameraInputView is being recreated.
Thank you

I cannot reproduce this problem unfortunately. However, there is a chance that this branch has already fixed the issue. If not, please let me know

@FulcrumOne Hello, Is the temporary solution not sufficient at the moment?
Also I think long term solution is better.

patch-1.2.1-beta solutions is finished or will?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> It got resolved after applying the equatable() workaround.
Actually after I applying the equatable() all problems resolved. I guess just have a little memory leak, thats all.

Additionally , independently of these, the snapshot and blurview you showed while flipping the camera are turned landscape.

I'm working on this now. If you need a faster solution, I strongly recommend locking the rotation for the current screen (lockOrientation method).

Additionally , independently of these, the snapshot and blurview you showed while flipping the camera are turned landscape.

I'm working on this now. If you need a faster solution, I strongly recommend locking the rotation for the current screen (lockOrientation method).

I noticed this about this problem. When I tested it on the iPhone X, it rotates, but when I tested it on the iPhone 11 Pro Max, it does not rotate. I also completely turned off the device rotation, it only works in portrait mode.

@FulcrumOne Hello, Is the temporary solution not sufficient at the moment? Also I think long term solution is better.

patch-1.2.1-beta solutions is finished or will?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> It got resolved after applying the equatable() workaround.
Actually after I applying the equatable() all problems resolved. I guess just have a little memory leak, thats all.

This temporary solution was a bit unstable and caused other problems (the error screen was not displayed for example). I would therefore recommend using the patch-1.2.1-beta branch 😉

@FulcrumOne Hello, Is the temporary solution not sufficient at the moment? Also I think long term solution is better.

patch-1.2.1-beta solutions is finished or will?
var cameraView: UIView { cameraLayer.superview ?? .init() } -> It got resolved after applying the equatable() workaround.
Actually after I applying the equatable() all problems resolved. I guess just have a little memory leak, thats all.

This temporary solution was a bit unstable and caused other problems (the error screen was not displayed for example). I would therefore recommend using the patch-1.2.1-beta branch 😉

Okey I will, thank you for your interest and for this great library :)

Thanks! If you have any further problems, let me know😉
PS. Check out our other solutions too!

Hello @FulcrumOne , So now we can create MJCameraController(manager: .init()), is it correct?

@FulcrumOne and , I applied patch-1.2.1-beta. but if i remove Equatable and .equatable() modifier, still i am getting crash, I guess, its have to stay, is it correct?

hey @clbemre,

Sorry, my fault I had forgotten to tell you how to use it 😅

This way (or you can use StateObject, it depends on what your view looks like). No, you don't need to use equatable anymore, because throwing that manager out there means that the parent view is responsible for keeping that object alive.

Yes, I'm aware of this problem with UI freezing after changing the output type; it's already fixed, but you have to give me an hour or two, because it's connected to a screen rotation bug fix, and I need test the whole solution first 😉

About using weak self - this will be very controversial, but I did it in this way, because using weak connections to the objects (or optional unwrapping) would mask the potential problems with objects management; in another words, my thinking was it's better to see the app crashing and know that there's a problem with the library than to waste the time locating the source of the problem

@FulcrumOne  Thank you, I'll check, I just wondered createCameraController() like this CameraController(manager: manager)?

@clbemre, exactly. And those attributes you see in the CameraManager initialiser are the initial values with which you start the camera instance

@FulcrumOne I understand. I just wondered again 😀  Is CameraView start point, right? Shouldn't manager be https://github.com/StateObject?

you can use either - it depends on what your view hierarchy looks like 😉

@FulcrumOne thank you I'll be waiting for you, for fix.

I don't know if you noticed but the grid is not visible. :/

There are still some minor UI bugs I'm working on (but the problem with grid should be resolved)

@FulcrumOne I have checked just before and applied. But still;

grid not visible ❌ ( maybe i have missed one thing, i don't know :/ )
UI freezing works correct ✅ ( Im not sure but i guess rarely works wrong)
first open is fast now ✅
flip rotate animation works correct. ✅

thank you 🙏🏻

sorry, also The UI update failure error regarding system permission denial also persists.

are you sure you are using the patch-1.2.1-beta branch? On my phone, I don't see the problems described

Ok, I was able to see the second problem, but the one with the invisible grid I still cannot debug

I have tried it on 2 different real devices, the grids do not appear neither at the first startup nor with the on/off grid button. 😬

I'm sorry :/ but Also, something like this happens, I start recording a video and the screen refreshes at that moment and the video starts recording, normally it would start directly. But now, because the screen is refreshing, the frame before I press the button appears on the screen momentarily and disappears, a UI bug. 😥

could you show me a video please?

https://github.com/Mijick/CameraView/assets/7671284/1fac686b-128a-4ae6-b16e-7340438caa46
@FulcrumOne

Ah sorry, some things its gone my branch, I'll check again.

https://github.com/Mijick/CameraView/assets/7671284/05f85df7-9dd4-4dc5-86ba-504aab3c5cd4
@FulcrumOne
I took a more clear video, focus on the bottom left corner and notice a momentary view appearing and disappearing. , can you take a quick look? because I'm going to delete it :D

sorry, also The UI update failure error regarding system permission deny also persists.

should be fixed now

346579937-05f85df7-9dd4-4dc5-86ba-504aab3c5cd4.mov
@FulcrumOne
I took a more clear video, focus on the bottom left corner and notice a momentary view appearing and disappearing. , can you take a quick look? because I'm going to delete it :D

Oh, now I see it. i'll try to fix it this night, and if I don't fix it then, I'll have to move it to Wednesday unfortunately😉

@FulcrumOne okey thank you again 🙏

Btw, just to be sure, because the both problems (invisible grids and flashing views) are not present in demo app I'm using for testing; are you sure it's not caused by some UI elements of your app?
And if so, could you please prepare the code for me that I can use to reproduce the bug? Thanks in advance! 😅

I can check again, but firstly could you send me your demo project ?

@clbemre,
https://github.com/Mijick/CameraView-Demo, branch patch-2.0.0

@FulcrumOne Hey I have found issue, The problem was caused by me, when I pressed the record button, I was setting captureSession.sessionPreset = .hd1280x720. This was causing a rendering problem on the screen. It was fixed when I deleted the code. Also, the system permission alert problem and the gird visibility problem were solved. Everything is perfect now, thank you very much for your interest. We don't have any other problems that I know of. 🙏🏻🙏🏻

@clbemre,
I'm super glad to hear it! I'll fix some other bugs I noticed and release version 2.0.0. Thanks for your support and see you soon!⚡

Thank you. 🙏 I’ll be waiting for 2.0.0 :) Good luck
Have a nice day.

Hello again @FulcrumOne , in CameraManager, you add observers but you don't remove. maybe you can add
deinit{
NotificationCenter.default.removeObserver(self, name: .AVCaptureSessionWasInterrupted, object: captureSession)
}

@clbemre,
Ahh, you're literally a life saver. I totally missed it. Thanks!

@FulcrumOne
Haha, every time, thank you too:)

@clbemre,
Fixed! I also changed the rotation animation a bit + fixed some other issues. Could you please check the latest commits and give me your feedback? Thanks a lot!

@FulcrumOne Hey, I'll check as soon as. Thank you for the information.

@FulcrumOne Hello again, everything is good. but just i want to say something.
When I rotate to landscape mode my phone, the camera lens changes and goes into close-up mode. It would be better if this was optional, because I don't want it to go into close-up mode when I rotate it landscape. If there is a option, I don't know, I didn't see. :) Other than that, everything is fine, well done.

Hey, could you show me the video of the problem you described? Thanks!

@FulcrumOne Sorry I had turned some things off. So I couldn't re-run the error scenario. If I encounter this error again, I will let you know.

@clbemre, thanks!


Advice on clicking on a folder in a directory

Currently, for folders with folder notes, the click effect is to open the folder notes.Considering that the indicator for expanding the folder is on the far left, it is inconvenient to click and it is often mistakenly touched. I hope to add the option of clicking on the folder to directly open the subdirectory of the folder.

Nice plugin!
On IOS (iPad) it's a bigger problem: the indicator isn't even visable. Maybe the UI action 'click = show folder note' can be removed or made optional in the settings. You can allways use a command to see the folder note


for AAD Account，I found AccountName is available and domainname is not available

[Enter feedback here]
for AAD Account，I found AccountName is available and domainname is not available

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

ID: b1b43b0d-fdbc-11ae-d1e1-6c8cc98121de
Version Independent ID: 98d20ec7-1f93-8e21-15d9-5b0bfa20385c
Content: User.GetPropertiesAsync(IReadOnlyList<String>) Method (Windows.System) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.System/User.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @hickeys
Microsoft Alias: hickeys

Thanks for submitting your feedback and we apologize for the delayed response. I see that updates have not been made since the creation of this Issue, so I went ahead and created an internal work item to engage with our engineering folks, find the answers, and resolve this doc bug. The timeline for this may vary, so I will go ahead and close this and circle back when the changes are live.
We have moved to a new feedback system, and I want to ensure that we don't lose access to the feedback in our open issues. Though the Issue will be marked as Closed, we will monitor any replies that come afterwards so treat this like an open Issue. Many thanks.


add some samples to docs

samples like cdr,phonenumber,quickcall.

Merged, thank you for your contribution Kevin!


Package.swift seems invalid for Swift 4.2.1

After this commit, I cannot build the repository with swift build and Swift 4.2.1.
The issue seems to be a breaking change between the PackageDescription APIs 4 and 4.2.
I'm not sure if changing the first line to say // swift-tools-version: 4 would help, maybe then the old format would be selected.

I've attempted to fix this issue in v2.2.1. Could you please give it a try?

@lukaskubanek works, thank you!


I WANT TO SET THE PANEL HEIGHT TO ZERO AND PANEL HEIGHT TO ACTION BAR HEIGHT WITH ANIMATION

hi,
i want to do a animation on touch of the screen ,(ie)if i touch the main fragment i want to hide the panel at the top with animation and setting the duration to it, as far wat i did was on touch i setting the panel height to action bar height and on alternate touch i am setting the panel height to 0 ,in this way  ican show and hide panel like the action bar , kindly suggest if i could attach animation duration  to it so it runs soomthly
My code is something like this
if(SlidingFragmentEN.isslidingshown){

				Log.e("isslidingshown",""+SlidingFragment.isslidingshownar);
				SlidingFragmentEN.isslidingshown =false;

//					SlidingFragment.mLayout.setOverlayed(true);
				SlidingFragmentEN.mLayout.setPanelHeight(160);

				SlidingFragmentEN.mLayout.setParalaxOffset(30);
				SlidingFragmentEN.mLayout.setClipPanel(false);
			//	SlidingFragment.mLayout.setPanelState(PanelState.DRAGGING);
				SlidingFragmentEN.mLayout.setCoveredFadeColor(Color.argb(0, 0, 0, 0));
			}else{

				SlidingFragmentEN.isslidingshown =true;

				new ScaleInAnimation(categorybutton).animate();
				SlidingFragmentEN.mLayout.setParalaxOffset(0);
				SlidingFragmentEN.mLayout.setPanelHeight(0);
				SlidingFragmentEN.mLayout.setClipPanel(true);
				SlidingFragmentEN.mLayout.setCoveredFadeColor(Color.TRANSPARENT);

			}

I'm not exactly understanding what you are trying to achieve. can you provide a screenshot?


Total Epoch training in cifar10

Hi, thanks your great job, could you tell me the Total Epoch training in cifar10 when training WRN-70-16 with “Diff. 50M”?

Hi @demon2036, we trained for 2000 epochs following the original diffusion-augmented adversarial training paper (Table 1 in the paper).


committing a dummy change for PR

Summary by CodeRabbit

Chores

Minor code cleanup performed with no impact on functionality.

@coderabbitai review


Feature request: keep state globally

Currently, the highlighting only applies to the current page in the current tab.
Would be great to have the highlighting globally enabled (all pages, all tabs).

Another nice idea. Thanks again!
I've added this functionality. Global highlighting can be applied on the extension's options page.
The update should be available shortly for Firefox, pending the corresponding extension review. It will be some more time until it's available on Chrome, as my update from yesterday is still in review, and it's seemingly not possible to make edits while this is occurring (even though I have a newer extension ready which obviates the need for the existing review).

Global highlighting is not working.
When I updated to 1.9.0 I seem to remember that it did, but the truth is that I'm not sure...

I was not able to replicate the issue on Firefox 74 of Firefox 75 on Ubuntu.
Can you try with freshly loaded tabs, by clicking the empty highlighter for global highlighting?
I've found that Firefox may unload tabs to conserve memory, or may not reload all tabs when restarting the browser. These tabs are unable to be globally highlighted, but tabs that are loaded in memory are working fine in my experiments.


syncer: remove syncer dependency from shardddl

What problem does this PR solve?

Issue Number: ref #4287
What is changed and how it works?

combine ddl.go and shardddl.go
shardddl only manages its own state and does not rely on syncer

Note: some code will be refactor in later pr

some callback(handleJobFunc...) will be removed
some state should only be use in shardddl but not in syncer, like onlineddl...

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

Codecov Report

Merging #6782 (48061e0) into master (2ea67ba) will decrease coverage by 4.7404%.
The diff coverage is 39.8850%.

Flag
Coverage Δ

cdc
?

dm
52.0379% <36.9592%> (-0.0038%)
:arrow_down:

engine
62.7241% <78.6885%> (+0.1879%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6782        +/-   ##
================================================
- Coverage   59.2138%   54.4734%   -4.7405%
================================================
  Files           780        417       -363
  Lines         88405      51638     -36767
================================================
- Hits          52348      28129     -24219
+ Misses        31415      20810     -10605
+ Partials       4642       2699      -1943

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-dm-integration-test

/run-dm-integration-test

/run-all-tests

/run-all-tests

PTAL @D3Hunter @buchuitoudegou

/merge

/run-kafka-integration-test


CUDA GPU is too old

Hello.
First of all, thanks for bringing us this awesome project!
I have a pretty old GPU, Nvidia GTX 970, but it used to work fine with Ollama 0.1.15.
Now I upgraded to 0.1.20 and I get the following error:
2024/01/14 19:50:06 gpu.go:88: Detecting GPU type
2024/01/14 19:50:06 gpu.go:203: Searching for GPU management library libnvidia-ml.so
2024/01/14 19:50:06 gpu.go:248: Discovered GPU libraries: [/usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1]
2024/01/14 19:50:06 gpu.go:94: Nvidia GPU detected
2024/01/14 19:50:06 gpu.go:138: CUDA GPU is too old. Falling back to CPU mode. Compute Capability detected: 5.2
2024/01/14 19:50:06 routes.go:953: no GPU detected

Im running Ollama in docker with GPU pass through and it seems to show up within the container:
root@a84d0bca74d1:/# nvidia-smi
Sun Jan 14 20:03:51 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.36                 Driver Version: 546.33       CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 970         On  | 00000000:01:00.0  On |                  N/A |
| 60%   29C    P8              13W / 151W |    566MiB /  4096MiB |      3%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+

I realize my GPU is old, but it used to work.
Do you know if there's a way to make it work again? I'd prefer to not be stuck on 0.1.15, if possible 😅
I'm happy to build the docker image from source, if thats needed.
Thanks in advance!

I tried building the docker image locally, it seems to build ollama from source, but still the same :/

@tlaanemaa sorry about that – we're working on making sure Ollama works with compute capability 5 cards in this issue #1756

My GPU is RTX 2060 Super, but it still prompts [0] CUDA GPU is too old. Compute Capability detected: 1.0


Huge amount of upload errors on Grafana Cloud: resource_exhausted push rate limit

Every few seconds pyroscope client using the reference config in README errors with:
upload profile: failed to upload. server responded with statusCode: '422' and body: '{"code":"unknown","message":"pushing IngestInput-pprof failed resource_exhausted: push rate limit (0 B) exceeded while adding 70 KiB"}'

We're not talking about hundreds of apps here; it's only 19-20.
What limit am I hitting and what config should I use to prevent/mitigate it?
//Edit:

Turns out 20 apps running for 4 days == 50G of data. How can I limit the sampling/reporting rate because this is insane

Thank for reporting the issue @f0o. Indeed, Go profiles can be quite large depending on the workload.
The upload rate can be changed via the UploadRate configuration option. By default profiles are collected and uploaded every 15 seconds. If the application behaviour and load are stable (profiles do not change significantly), you could try to increase it up to, e.g, 30 seconds.
I'm wondering which profile types are enabled. Napkin math shows that each of the apps generates ~100KB of profiling data (uncompressed) every 15 seconds – this is an unexpectedly high data rate. Could you please tell us more about the workload? I'd also like to clarify how many individual processes you're profiling, and what you mean by apps – do you mean 20 instances (processes/hosts/pods) of the same service, or 20 logical services, represented by some fleet?

Hi @kolesnikovae
I'll look into the UploadRate parameter and tweak it once the retention expires those old profiles.
I'm using:
			ProfileTypes: []pyroscope.ProfileType{
				// these profile types are enabled by default:
				pyroscope.ProfileCPU,
				pyroscope.ProfileAllocObjects,
				pyroscope.ProfileAllocSpace,
				pyroscope.ProfileInuseObjects,
				pyroscope.ProfileInuseSpace,

				// these profile types are optional:
				pyroscope.ProfileGoroutines,
				pyroscope.ProfileMutexCount,
				pyroscope.ProfileMutexDuration,
				pyroscope.ProfileBlockCount,
				pyroscope.ProfileBlockDuration,
			},

With:
		runtime.SetMutexProfileFraction(5)
		runtime.SetBlockProfileRate(5)

And for clarification it's 3 services amounting to 19-20 pods, each very small in resource consumption (we're talking 0.05 cpu and 32-64mb memory). The workload is best described with signal/data forwarding without processing. I was about to write the processing service when I noticed these errors and started disabling profiling everywhere instead.

Hi @f0o, and thank you for the feedback. I'll double-check everything and report back soon. In the meantime, please consider disabling goroutine, mutex, and block profiles.


Cannot add my own custom attributed text to the label

Seems like all of my attributed texts have the same attribute as the first one.

We are experiencing the same issue

FYI this issue is still persisting in the latest version 1.1.0.


[Plugin] Segment Analytics Module

Summary
Similar to the google analytics module there should exist an implementation of the AnalyticsApi interface for Segment which can be used for client side metric tracking and forwarding events to multiple downstream connections (like Google Analytics).
The plugin should implement and handle the general set of functionality that the Google Analytics module does

configuration/setup of the necessary dependencies
identify events
navigate events
general event tracking

These events should be translated to the necessary segment actions of identify, page, and track
Project website (if applicable)

Context
We have our own internal version of this module that we would like to open source. We'e also been in conversations with the Backstage owning team over at Segment/Twillio who are interested in maintaining and owning this plugin long term

Hey all! 👋 Twilio Segment eng here to give this a big ➕ and offer to address any comments/questions/concerns y'all might have.
We've already cleared this with our internal Analytics.js team and are excited and available to assist however we can. ✅
Huge thank you to James and everyone at Brex for their work on this and gracious offer to open source the plugin. 🙏


update c_src Makefile

use rebar3 new cmake to update the c_src/Makefile. With newer OTP versions (OTP-26 for sure), the order of the arguments to the erl -eval calls is important.

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


Applying Migrations without database result in error

When I try to apply migrations without having an existing empty database, it simply crashes with this error

CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Users\Abhishek SiddhuCatalystApp.mdf'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Looking at the error it looks like a simple missing of ending slash in default path
Steps to reproduce
It's pretty consistent. I have tried it on several projects in the last few months and it gives the same error

PM> update-database
Executing DbCommand [Parameters=[], CommandType='Text', CommandTimeout='60']
CREATE DATABASE [CatalystApp];
Failed executing DbCommand (14ms) [Parameters=[], CommandType='Text', CommandTimeout='60']
CREATE DATABASE [CatalystApp];
Microsoft.Data.SqlClient.SqlException (0x80131904): CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Users\Abhishek SiddhuCatalystApp.mdf'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at Microsoft.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean isAsync, Int32 timeout, Boolean asyncWrite)
at Microsoft.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry, String methodName)    at Microsoft.Data.SqlClient.SqlCommand.ExecuteNonQuery()    at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQuery(RelationalCommandParameterObject parameterObject)    at Microsoft.EntityFrameworkCore.Migrations.MigrationCommand.ExecuteNonQuery(IRelationalConnection connection, IReadOnlyDictionary2 parameterValues)
at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQuery(IEnumerable`1 migrationCommands, IRelationalConnection connection)
at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Create()
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.UpdateDatabase(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabaseImpl(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabase.<>c__DisplayClass0_0.<.ctor>b__0()
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
ClientConnectionId:037c3501-8ad6-484d-aefb-3188be1b1c0d
Error Number:5123,State:1,Class:16
CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Users\Abhishek SiddhuCatalystApp.mdf'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Further technical details
EF Core version: 3.0.0 but i get this error in 2.1 as well
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET Core 3.0
Operating system: Windows 10
IDE: Visual Studio 2019 & 2017

Looks like a path issue, more than anything C:\Users\Abhishek SiddhuCatalystApp.mdf where EF definitely won't be able to write into the Users dir, I assume it should be C:\Users\Abhishek Siddhu\CatalystApp.mdf

@Inzanit This is exactly what i thought looking at the error, but the path is generated by the tooling, and the connection string is pretty straightforward

"ConnectionStrings": {
"Database": "Server=(localdb)\mssqllocaldb;Database=CatalystApp;Trusted_Connection=True;"
}

You need to apply the latest SQL Server 2017 CU to your LocalDB installation! (Known issue with the RTM version)

I was unable to apply the latest CU KB4515579 (some configuration issues at my end) so I uninstalled and then reinstalled SQL server 2017 LocalDB, still getting the same error, applied the update, still the same error

Did the update succeed? run:
SELECT @@VERSION

and share the text result

yes

Microsoft SQL Server 2017 (RTM-CU17) (KB4515579) - 14.0.3238.1 (X64)   Sep 13 2019 15:49:57   Copyright (C) 2017 Microsoft Corporation  Express Edition (64-bit) on Windows 10 Enterprise 10.0  (Build 18362: ) (Hypervisor)

@abhisheksiddhu Please post a small, runnable project/solution that reproduces the behavior you are seeing.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

@ajcvickers I am unable to reproduce it in .net core 3.1 preview-1, it's working fine now.


[Fix #112] Fixes issue with obsolete Rubocop changes

Fixes issue reported here: https://github.com/igrigorik/http-2/issues/112

This change is

@Tr4pSt3R any luck on your end?

@igrigorik there are some issues which are dependant on some PRs from Rubocop's end being pushed through. I am monitoring the situation.

@Tr4pSt3R cool, thanks for the update!

@Tr4pSt3R any updates? :-)

@igrigorik I have been away on vacations for about a month

@Tr4pSt3R nice! No rush, just wanted to check-in..

@Tr4pSt3R Can you please provide an update? Will you have time to complete this PR?

@ioquatix I will find time to look into this again and update you accordingly

We have updated rubocop. If you have further improvements, please create a new PR. Thanks so much for your past efforts and attention.


🌐 Add Chinese translation for Tutorial - Security - OAuth2 with Password (and hashing), Bearer with JWT tokens

@maoyibo @yanever @RunningIkkyu Please take a look.

Awesome! Thank you @waynerv ! :bow: :cake:
And thanks for the reviews @Zxilly and @Laineyzhang55 ! :coffee: :nerd_face:


Add optional gutterWidth to typescript interface

Fixes issue: https://github.com/JSxMachina/react-grid-system/issues/109

gutterWidth is a number though :smiley:

gutterWidth is a number though

Thanks! :+1:  fixed in https://github.com/JSxMachina/react-grid-system/pull/110/commits/d0bfd9675de137bf40089e38b8d22aaac029b25e


Obsolete uncleaned_roots in accounts index.

Problem
In PR#4044, we no longer filter clean by uncleaned_roots. All slots that are older than the max_root_to_clean are considered in clean.
The concept of uncleaned_roots is now obsolete. And we should remove it.
Summary of Changes
Remove uncleaned_roots from account index.
Fixes #

Rebase to pick up #4147.

Graph of open append_vec number from dev2 running with this PR for two days on mainnet. Its number looks normal.


Add Dialog Boxes extension

Closing as other files were not reverted, just easier to open a new one.


Support EVM address to display Contracts in addition to Contract Id

Problem
When navigating to https://hashscan.io/testnet/account/CONTRACT_EVM_ADDRESS the page display information as if it is an account instead of a contract.
example: https://hashscan.io/testnet/account/0x0000000000000000000000000000000002eAE879
Solution
It would be useful if the explorer could detect if the address is a contract and display contract-related data like bytecode and such.
Alternatives
No response

In fact, it does detect it, and provides a link allowing to navigate to the ContractDetails view.

Which redirects to this https://hashscan.io/testnet/contract/0x0000000000000000000000000000000002eAE879
With a Invalid contract ID: 0x0000000000000000000000000000000002eAE879 error. Not sure it is a very good UX.
Navigating to /address already redirect automatically to /account https://hashscan.io/testnet/address/0x0000000000000000000000000000000002eAE879
Maybe it would be interesting not to have to navigate, stay under /address and display contract info like on other explorer like Etherscan

The navigation to the ContractDetails view is broken, we are going to fix this ASAP.
Beyond that, we could indeed consider merging the AccountDetails and ContractDetails views.
Thanks for reporting this and for your feedback.

We now support <explorer-url>/testnet/contract/<evm-address> as well as  <explorer-url>/testnet/contract/<id>
<explorer-url>/testnet/account/ and  <explorer-url>/testnet/contract/ are native explorer routes which will continue to show respectively an account view and a contract view, since account and contract are distinct entities in the native Hedera context
For user flows originating from the Ethereum world, the exposed route is:  <explorer-url>/testnet/address/<evm-address> which will automatically route to a contract view or an account view as appropriate, and to an Inactive EVM Address page when the address has not yet been created.


Disable orphaned order cancel btn

fixes https://github.com/AugurProject/augur/issues/314

Coverage remained the same at 55.437% when pulling fe5728dace7d6121a6394d8e1df827d21717c2f1 on disable-orphaned-order-cancel-btn into 8d5e9bad026ab4c888953d898a80e161928a1298 on master.


Sorting current stock can make app unresponsive

Build Number: 30
Description: Title doesn't really explain it - but if you have a long list of stock in 'Current Stock' and you sort it, it may take a few seconds to sort (which is fine). But if your user is impatient and thinks it hasn't worked they may click it multiple times. And mSupply will sort it multiple times before allowing the user to make any other commands such as moving back a page. (And your user may keep clicking it as it sorts, and you end up waiting for it to sort the list 100 times!)
Reproducible: Yes
Reproduction Steps: Go to a long stock list, click to sort by quantity and keep clicking.
Comments:
Not a major issue as we can tell people not to do it, and even if they do they can terminate the app and restart (not sure whether this may have a negative impact on any processed data in the app though?)

Thanks Andrew,
You are right, if someone gets carried away and spams the sorting (as many would given delay) it'll make jam up the app. There are a few approaches and optimisations that could fix this.

Debounce the sort function so it doesn't stack up calls when spammed
Cheeky hack/optimisation, if the sort direction (isAscending) is just being switched on the same column, the array of records being displayed should just be reversed rather than bothering with other sorting/filtering going on.

I think I erroneously tagged this as fixed in a commit

I think this is related to the data table performance issues which has enough issues currently and has a rewrite coming in hot. Closing this issue


Display new facet Scientific Name in Object tab.

Problem Description:
YPM has new meta-classifications for additional faceting. Rather than displaying these new meta-classifications under Categorized As they would like a separate facet to be created
Expected Behavior/Solution:
Create new facet Scientific Name and display all new YPM meta-classifications.
Requirements:

New facet Scientific Name will be displayed on Object tabs.
Must display under Categorized As (TBD/Need to check)
Facet must contain all new YPM meta-classifications.
YPM meta-classifications must not appear under Categorized As.

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[ ] Wireframe/Mockup - Mike
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Are new regression tests required for QA - Amy
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

https://lux-front-sbx.collections.yale.edu/view/results/objects?q={"AND"%3A[{"text"%3A"bombus"%2C"_lang"%3A"en"}%2C{"text"%3A"new"%2C"_lang"%3A"en"}%2C{"text"%3A"haven"%2C"_lang"%3A"en"}%2C{"text"%3A"remington"%2C"_lang"%3A"en"}%2C{"text"%3A"1982"%2C"_lang"%3A"en"}%2C{"text"%3A"Westville"%2C"_lang"%3A"en"}]}&sq=bombus+new+haven+remington+1982+Westville.

Dependencies/Blocks:

Blocked By:

Related Github Issues:
N/A
Related links:
Bugherds: https://www.bugherd.com/projects/284041/tasks/2605
Wireframe/Mockup:
Current:

Expected:

Per the UX/BA 10/16 meeting @miketullo95 will need some example options to create the mockup.

@kkdavis14 - on https://lux-front-tst.collections.yale.edu/view/results/objects?q={"text"%3A"horseshoe"%2C"_lang"%3A"en"}&sq=horseshoe
Is this how the facets would be divided?
Categorized As

three-dimensional(14157)
Fossils(13689)
hypotype(472)
Biological specimens(398)
Books(127)
archival materials(44)
Numismatics(24)

Taxonomic Rank

Eurypterus(3584)
Eurypterida(2788)
Eurypterus remipes(1984)
Hughmilleria socialis(765)
Eurypterus lacustris(738)
Bellinurus danae(537)
Xiphosurida(446)
Synziphosurina(340)
Erieopterus(302)
Eurypterus pittsfordensis(272)
Hughmilleria(243)
Pterygotus (Acutiramus) macrophthalmus(148)
Limulus polyphemus(145)
Tremaglaspis(107)
Paracarcinosoma scorpionis(103)
Pterygotidae(100)
Waeringopterus apfeli(86)
Eurypterus remipes lacustris(83)
Acutiramus cummingsi(73)
Erieopterus microphthalmus(70)
Hutchinsoniella macracantha(60)
Dolichopterus macrocheirus(52)
Dolichopterus(51)
Eurypterus dekayi(51)
Dolichopterus jewetti(47)
Aglaspida(38)
Eurypterus remipes remipes(37)
Pseudoniscus(35)
Carcinosomatidae(35)
Erettopterus osiliensis(34)
Stylonuracea(29)
Erettopterus(23)

@prowns lgtm!

@kkdavis14 - Will that be in the data or does front-end need to do something?  Trying to identify example for @miketullo95  to use in the mockup.

@prowns the data constants are in the data now, yes. each taxon is classified as something, which has a meta-classification/data constant of a wikidata.

For TF - need to clarify what is expected from YPM on this facet and what the label ought to be.   Is it set of classifications pulled out if they are taxonomic? If so, this has nothing to do with the data constants.

@prowns - should this be a topic for next weeks agenda? Unsure who is able to clarify what is needed from YPM, would that be @kkdavis14 ?

@roamye - I am checking with YPM.

@roamye @prowns
Generally we create Advanced Search terms alongside facets. This is not a hard requirement, but if we would like and Advanced Search term I think we should do both at the same time.
I have questions about this:

There will just be one 'Scientific Name' field, correct? We are not going to have separate facets for 'Species', 'Genus', 'Order', etc?
Do we want 'Categorized As' to still include Scientific Names in its list of categories? Or should 'Categorized As' be changed to exclude Scientific Names?

@clarkepeterf the answer to the second question is (with 99% certainty) exclude Scientific Names from Categorized As--as the point of this work was to de-clutter this facet :)

@kkdavis14 sounds good.
Further questions here would be:

Do we want to also make the Categorized As search term in Advanced Search exclude Scientific Name?
Do we want to modify Categorized As for People & Groups to have similar exlusions (Categorized As would exclude Nationality, Gender, Occupation)

@clarkepeterf These are good questions.
I would think yes to the first question, but no the second, which is inconsistent. Maybe a conversation to bring to a larger group for input?

@kkdavis14 - are you expecting that biological taxa, such as Kingdom, Species, Order, etc, appear as a separate facet as well?  Or will those not be offered to users as a facet option?
cc: @clarkepeterf and @roamye

@prowns no, it seems from Gary's comment in Teams YPM is looking for one facet--"Scientific Name". I'm only expecting whatever their requirement is :)

I am changing the name of this ticket.
From:
"Display new facet Scientific Name in Object tab of Simple and Advanced Search"
To:
"Display new facet Scientific Name in Object tab"
Reason:
facets always display in both Simple and Advanced Search, we don't need to call them out in the title.

@miketullo95 - two wireframes are needed on this issue. Please see: this comment for details on available options within the Scientific Name facet.


Event resource

This big pull requests brings the Clojure REST resources (based on Cal's work for CIMI) into SlipStream.

First use from Java world is with the Event resource, that receives messages from Run resource  (creation, state change, abort, scaling).
This Event resource is currently internal (redirection proxy in Restlet was not included as authentication still missing).
The persistence for Clojure resources uses the same database as Java server.

@loomis @schaubl @mebster @konstan @rbf

I will have a look to this pull request.

The Java part looks ok.
The following files has no "real" change, so they may be excluded from this pull request:

RootApplication.java (https://github.com/slipstream/SlipStreamServer/pull/278/files#diff-be0e31281a464eedd440e785b644a372
UserListResource.java (https://github.com/slipstream/SlipStreamServer/pull/278/files#diff-473bc3276f0b7856f58d481ac4a6df83)
Java dependencies may be moved to the SlipStream parent.

I will let somebody else do the review of the Clojure part @loomis ? @rbf ?

Following @schaubl advice, files with no real changes were reverted back (https://github.com/slipstream/SlipStreamServer/commit/8ff29f2bbb399fde4e483fd7c626121772e380cd).


When added invoice for next month the month is not updating in invoice number

Describe the bug
Added invoice for may month , the invoice number was generated successfully.

While adding invoice for June month, the month was not updated in invoice number. Month should be displayed as 06 for june, but it was displayed as 05

Testing was done in UAT environment

Closing this issue as it has been fixed through https://github.com/ColoredCow/portal/pull/1396
Please refer screenshot for reference


Implement Age filter

Information is currently in this sheet
and on the database in Service information
Pls add steps to complete here

I mean, it is implemented @jbeard4 we are still adding ages so it needs consistent refresh


support swift 3 soon ?

Realm version: ?
2
Xcode version: ?
8
iOS/OSX version: ?
10.12

Swift 3 works in master! We've been keeping it up-to-date with each beta release. For example, we migrated to Swift 3 Beta 6 just days after it launched. https://github.com/realm/realm-cocoa/pull/3965

Great work~ i will try it again~

target 'TestRealm' do
  # Comment this line if you're not using Swift and don't want to use dynamic frameworks
  use_frameworks!

  # Pods for TestRealm
  pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master’,:submodules => true
  pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master’,:submodules => true
end

Xcode 8 will convert realmswift.framework some code  such as Results.swit

@liufsd Don't run the migrator. Everything should work property. There's a bug in the Swift migrator where it will try to also migrate code in the else section of #if swift(>3) #else #endif blocks.

oh？you mean i don't need convert swift 3? (I need select convert latter)

You shouldn't need to convert Realm's codebase (if it prompts you to). You may or may not want to update your code to Swift 3. We currently do support Swift 2.x still.

I'm working a new project,so I used Xcode 8 swift 3~ and realm is my best choice ~

Cool, Realm (w/ master) should be compatible with that configuration 😄

@liufsd Are you still having issues getting it to build?

sorry~

by the way , i use Xcode 8 beta 6~

Which version of CocoaPods are you using?

pod version 1.0.1

It looks like CocoaPods prior to v1.1.0 (currently in beta) does not set the SWIFT_VERSION setting on pod targets. The absence of this setting results in the Xcode error you're seeing. See CocoaPods/CocoaPods#5521 for how to explicitly set SWIFT_VERSION with existing versions of CocoaPods.

Yes~ done~  really thanks ~
i put this and work~
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['SWIFT_VERSION'] = '3.0'
        end
    end
end

I have test pod and carthage ~ and all of this work success~  great work~ thanks ~
and my cocoa project here: https://github.com/liufsd/PhotoCloud (branch:swfit 3.0) ,the ios project will open source latter~

When will swift 3 be released as an official Cocoapods version on trunk?

We've maintained support for Realm Swift across Xcode 8 betas since WWDC, making adjustments to continue compiling and passing tests for Swift 2.2, 2.3 and 3.0 as new betas came out.
However, due to the amount of churn Swift 3 has seen in the last 3 months, we held off on thoroughly reviewing all our Swift 3 API changes and accommodating both Xcode 7.3.1 and Xcode 8 into our continuous integration, testing, docs and release packaging processes.
With Xcode 8 GM last week, we decided to make a push to finalize our Swift 3 APIs along with the other integration points mentioned above.
That work is now mostly complete and we're preparing a 1.1.0 release for tomorrow, at which point our Swift 3 APIs will be final, binaries will be made available for Swift 2.3 and 3.0 in our release zips, and docs will be updated to reflect the new APIs.
Thanks for your patience.
JP

Awesome, thanks for all the hard work @jpsim and team

Would it be possible to point this out in you official documentation? I think a lot of other devs are currently migrating and would be happy to find this in your docs.

@ogezue
mac:  https://github.com/liufsd/PhotoCloud/blob/master/Cartfile
ios:  put this in your Podfile
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['SWIFT_VERSION'] = '3.0'
        end
    end
end

@ogezue you can see doc here: https://realm.io/docs/swift/latest/

Howdy! Any estimate when there would be a cocoapods release of RealmSwift for Swift3? The current 2.0.2 (as of today) does not compile due to several errors as such:
/Users/matti/src/foo/Pods/RealmSwift/RealmSwift/LinkingObjects.swift:123:29: error: extraneous argument label 'index:' in call         return notFoundToNil(index: rlmResults.index(of: object.unsafeCastToRLMObject()))                             ^~~~~~~~
I'm in the process of updating a major customer app and would not prefer to go using the branch: 'master' mechanism.

Matti


surface partial order with candidate ties to users

Addresses issue https://github.com/pivot-libre/pivot/issues/184


[Gesell] SCS community purged Turbinenplatz from CommunityMap

Probably a cause of #370.
There is now only one pin on the map:

Which is very close to the misplaced pin of the Turbinenplatz community. See #370.

Most likely, they fall into the same geohash bucket, which is the Turbinenplatz is overwritten.

the reason is that the pin location is derived from cid information only, which doesn't have such a good resolution. So this is not a bug. it's acceptable. Moved the test community formerly known as "turbineneplatz" to "adriana" in the adriatic sea


Genomics England parser refactoring and rewrite

As part of the process of rewrite of the platform and, more specifically, remodelling of the evidence, GenomicsEnglandPanelApp.py must be rewritten following the new version of the JSON schema.

To-dos based on the review of the fields coming from the data sources:

[ ] Add a functionalConsequenceId field. Action needed: manual mapping from the Mode of Inheritance column to a SO code (different values described here). 2 options:

Store these mappings in a Config file;
Have the logic within the parser

[ ] Should we populate the diseaseFromSourceId field with the OMIM codes that are sometimes present or leave it blank?

@ireneisdoomed let me clarify a point in the comment above. The field that would go into functionalConsequenceId after SO term mapping would be the Mode of pathogenicity not the Mode of inheritance. The linked ticket does therefore not add too much info into this task.
As you can see this information is not very frequent (~1%) so it's really not high priority
❯ sed '1d' All_genes_20200928-1959.tsv | cut -f 9 | sort | uniq -c
58162
  60
   1 FALSE
 570 Loss-of-function variants (as defined in pop up message) DO NOT cause this phenotype - please provide details in the comments
  31 Loss-of-function variants (as defined in pop up message) DO NOT cause this phenotype -please provide details in the comments
 163 Other
1611 Other - please provide details in the comments
 165 Other - please provide details in the comments
   1 gain-of-function
   4 loss-of-function (truncating variants and curated list of variants)
   4 other - please provide details in the comments

The first iteration of the script is done. Plans for the second iteration:

[ ] Review the integration of multiprocessing when making requests to OnToma. I have not seen any improvement in performance over the previous parser.
[ ] Revamp the function that removes duplicates.
[ ] Integrate a better logging system as agreed (see here)
[ ] Map Mode of pathogenicity to an SO code to populate  functionalConsequenceId
[ ] Minor fixes commented in the code

The first iteration of the script is done. Plans for the second iteration:

[ ] Review the integration of multiprocessing when making requests to OnToma. I have not seen any improvement in performance over the previous parser.
[ ] Revamp the function that removes duplicates.
[ ] Integrate a better logging system as agreed (see here)
[ ] Map Mode of pathogenicity to an SO code to populate  functionalConsequenceId
[ ] Minor fixes commented in the code

work is completed.


Turning resolution up to 11...I mean 16

How hard would it be to add a level of resolution to h3? I'm not a c native speaker but most of the code I've poked around in simply has a raise when a resolution higher than allowed is given.
I know the index would have to exceed 64 bits in this instance but that could be a price worth paying for those of us with high precision observations.
I suppose what I'm asking is: Is the problem small enough that someone with pretty basic C could have a play or is it going to involve some heavy lifting from either a "proper" programmer or a mathematician?  I'm trying to assess if it's worth me having a go.

So the subdivision algorithm could go all the way to the planck length and not really have any issues, but to represent anything beyond resolutions 0-15 you need to store things in a C struct instead of an integer. Very early on in the life of this project there was such a representation, but there are many issues with interoperability with structs that it was eliminated.
Basically, each CPU architecture your code is compiled to can have a slightly different layout of your C struct (some can handle simple byte alignment, while others prefer addresses to be 32 or 64 bit spaced apart, so an int8 would have 24 bits of padding afterwards on those platforms), meaning that while you can write C code that uses that struct and you can write bindings to another language that uses that struct, you cannot use that struct as an interchange format. Different machines will be unable to properly process the raw bytes of the struct from other machines.
That eliminates a whole class of uses, as an H3 struct can only be used as internal implementation details of the program using it.
We have discussed in the past creating a new H3 index mode that implies a second 64-bit integer that could add ~21 more resolutions (0-36) or even a nearly unbounded index that declares the next n 64-bit integers for storing parent-child traversal information, but had not seen a use-case as commercial GPS is not as accurate as res 15. The issue with these is that the 64-bit integer is no longer valid, the array of such integers is the valid index, so it makes parsing, operations on them, and especially indexing on them (eg in a database) more difficult.
There is one final option: when you look at the raw bitfields of the H3Index you may notice that there is both a resolution field and the values for all 16 resolutions possible, and if you look at the specification of the resolution parent->child traversal rules, 0-6 are valid while 7 is invalid (hence why most H3 indexes end in a bunch of fs, 7 decimal == 111 binary and f in hexadecimal is also all 1s). So there's some redundancy of information -- it would be possible to free up the bits from the resolution field and take the reserved bits and get one or two more resolutions packed into the H3 index (more on this in a bit).
This would definitely also require a new mode to represent it separately from the currently valid H3 indexes, which should not be broken, but if you take both sets of 3 bits to get two extra resolutions we would not be able to create a similarly restructured directed edge index (indexing the traversal from one h3 index to a neighbor), while if we take only the bits from the resolution field we could add a directed edge mode for these newer, finer grained indexes.
Is it worth the churn to the API to do this for a single extra resolution? That I am far less certain about. Since GPS can't resolve that accurately, we would really like to know what your use-case is for something like this before pushing forward on one of the solutions listed above (or something similar but different; one I didn't talk about was an "index modifier" index, such that the first 64-bits is a valid H3 index as currently defined while a modifier index has a special mode set and implies that it affects the prior index in the array -- this still has all of the indexing downsides of the greater-than-64-bit indexing, but at least the first 64-bit integer would be considered a valid index by existing code and if it just filters out "invalid" indexes, you'll still get partial precision out of the actual set of locations you're encoding).

@isaacbrodsky @nrabinowitz You two are effectively the steerers of this project now, would definitely like your thoughts on this.
@datamacgyver I forgot to ask: can you tell us more about why you need a finer resolution?

So the subdivision algorithm could go all the way to the planck length and not really have any issues

To go significantly higher resolution you would likely need to switch to long double for all floating point representations and operations. That has some potential issues: the C standard doesn't require long double to actually be more precise than double; there might be a performance hit; and it might affect portability if there are languages that don't support more precise floating point representations. It's also possible there are places where integer overflow might occur at higher resolutions, requiring you to go to long int. This could have similar issues as going to long double.
@datamacgyver the short answer is probably that this task might be a bit much for "someone with pretty basic C". :)

My thoughts here:

This would introduce a significant amount of complexity for what I'd guess is a very small number of use cases.
We'd likely run into greater FPE concerns at the finer resolutions. We already have bugs after res 12 for certain algos that compare lat/long points.
I doubt that there's a significant benefit to using H3 for this - the fine resolution areas are no longer truly geographical, don't actually require spherical geometry, and won't get the benefits of the standard H3 index format.

I'd guess that most use cases that need res > 15 should actually be using two coordinate systems - a fine coordinate system based on a cartesian grid, and H3 to geolocate the origin of the fine coordinate system. E.g. an address might look like <h3index, i, j> where i, j are the 2D coords of a regular hexagon grid of fixed edge length with 0,0 at the  h3index center. At fine zoom levels, assuming limited area, the difference between a cartesian grid and a geo grid should be negligible, and a cartesian grid is fairly easy to implement in the language of your choice.

So the subdivision algorithm could go all the way to the planck length and not really have any issues

To go significantly higher resolution you would likely need to switch to long double for all floating point representations and operations. That has some potential issues: the C standard doesn't require long double to actually be more precise than double; there might be a performance hit; and it might affect portability if there are languages that don't support more precise floating point representations. It's also possible there are places where integer overflow might occur at higher resolutions, requiring you to go to long int. This could have similar issues as going to long double.
@datamacgyver the short answer is probably that this task might be a bit much for "someone with pretty basic C". :)

I forgot that we eliminated the long doubles from the code. :/

Wow guys! I was just curious but they are some really thoughtful comments, much appreciated! I definitely think my eyes are bigger than my belly in terms of trying to do any of that in C (maybe one for the "future projects" list!) but I will think upon your suggestion @sahrk.
In answer to your use-case question, it's an interesting one! I work in agriculture so we have data collected by expensive GPS rigs on tractors, often helped by user base stations or transmitting systems. The leaflets say you can do 10s of cm with some kit. On top of that we have things like applicators that will tell you what's being sprayed from each nozzle of the tractor as it drives along,  cool stuff but a challenge to make sense of.
For analysis and mapping we are evaluating a few different tools but, given the investment in getting something running, I thought I'd make sure I'd dug into everything I need to. Definitely don't break your system for my sake but, as I say, I really appreciate the thoughts!

Closing this, as we're not likely to take further action on it, but thanks for bringing up the use case!

@datamacgyver if you need a higher resolution hexagonal global grid you might want to look at DGGRID. Feel free to contact me if you have any questions.

A business use case for higher resolution: zooming in onto a shelf of products in a shop.
.5m edge is suddenly a little large. Doable, but a bit large.


remove sources tag from jsk_hogehoge packages

We realized that our frequent commits to the repository consumes many job resources to your jenkins.ors.org resources, I'm not sure but if removing sources tags stops executing ros-$ROS_DISTRO-devel-jsk- jobs and that reduces cunsuming ros.org resources, I'm very happy about that.

Removing the source entry will also prevent users to use rosinstall_generator with the --upstream(-development). They can still use rosinstall_generator using the latest release from the gbp repo though. If that is ok for you I can merge this.
In the future (when the new build farm is deployed) we will be able to disable the devel job without affecting the availability of the entry.

thanks you for explanation, that's ok for me. Please merge this.
2015年7月29日水曜日、Dirk<EMAIL_ADDRESS>
Removing the source entry will also prevent users to use
rosinstall_generator with the --upstream(-development). They can still
use rosinstall_generator using the latest release from the gbp repo
though. If that is ok for you I can merge this.
In the future (when the new build farm is deployed) we will be able to
disable the devel job without affecting the availability of the entry.
—
Reply to this email directly or view it on GitHub
https://github.com/ros/rosdistro/pull/8997#issuecomment-125676699.


Plugin system for grammar styles

Describe the behavior you would like added to Foyer
After discussions with @umesh-timalsina and @daico007 , It occurred to me that we might be able to include various grammars as plug-ins for foyer to use when graph matching.
Describe the solution you'd like
Assuming the various chemical perception grammars could be represented as some type of compatible grammar for the lark-parser, this could enable different types of graph matching like SMIRKS, SMARTS, etc.
Describe alternatives you've considered
N/A
Additional context
This would be a tremendous amount of work, and is not yet ready for actual implementation until much later after #358 . This also will require expert-level domain knowledge of grammar parsing and development.

I've been working on a something that overlaps with this issue for the past few days. Because of some future goals I have with FF in foyer, I wanted to be able to use a broader set of SMARTS features than is currently implemented. I played with generalizing the GRAMMAR, but didn't think myself up to making those changes and all the changes elsewhere in the code that would be needed. Instead, focusing on atom types for chemical elements (not non-element '_' atoms), I just use a boolean switch in the call to FF.apply to select some new functionality and pass slightly modified SMARTS strings from the forcefield directly to rdkit to use its SMARTS substructure matching. The experimental code I have so far seems to work and can type all of the test OPLSAA molecules.  The benefit is immediate access to almost the entire SMARTS grammar. For example,
This:
<Type name="opls_145" class="CA" element="C" mass="12.01100" def="[C;X3;r6]1[C;X3;r6][C;X3;r6][C;X3;r6][C;X3;r6][C;X3;r6]1" overrides="opls_141,opls_142" doi="10.1021/ja9621760"/>
can become:
<Type name="opls_145" class="CA" element="C" mass="12.01100" def="[c]1ccccc1" overrides="opls_141,opls_142" doi="10.1021/ja9621760"/>
This works fine to type benzene. Definitions based on other atom types, for example in the aromatic H on carbon:
<Type name="opls_146" class="HA" element="H" mass="1.00800"  def="[H][c;%opls_145]" overrides="opls_144" desc="benzene H" doi="10.1021/ja9621760"/>
works as "recursive smarts" is used and the above def is internally converted to: [#1][c;$([c]1ccccc1)].
The current defs in oplsaa.xml continue to work when passed through the new system. As evidenced in the above aromatic H defintion ( [H] --> [#1]), I had to do some ad hoc modifications to get the non-SMARTS-standard (or at least non-rdkit-SMARTS-standard) use of explicit H's to play nice with the rdkit implementation.
The current code is experimental, non-optimized, kludgy, without proper Exceptions or much validation, etc., but it seems to work just fine. Except for handling the boolean to turn this feature on/off, no changes to the code were made except in atomtyper.py and that is mostly additions. Of course, one must turn off FF validation if new defintions are to be used. The SMARTSGraph is replaced with a simple object that just holds the smarts_string, typemap, etc. and has a simple find_matches method that builds an rdkit molecule and calls rdkit substructure matching. I have an idea about how this might possibly be extended to non-element atoms, but that is unimplemented or tested.
It seems that something like this approach could be a valuable expansion of foyer capabilities without the work involved in an expanded GRAMMAR. Let me know if this is of interest to the developers.


No phar file for release v2.7.0

Latest release does not have phar file in "Assets" section. And direct download link https://github.com/php-coveralls/php-coveralls/releases/download/v2.7.0/php-coveralls.phar from documentation does not work too.
Was there some some problem with phar file generation or does documentation contain obsolete download link?

Hey. I added the misisng phar file.
I see that there is some deprecation notice, i think from Sf? if you up for it, feel free to fix it


Adoption/Maintenance offer

Hi Marius,
Looks like this plugin still has a fair amount of interest, would you like some help maintaining it? I'd be happy to curate the pending PRs and tend to issues if you could provide me the commit bit.
Cheers,
Peter

Thank you so much for your offer Peter. Would love to have you help out. I will add you with full access to the repo.
Thanks,

Marius -

Done!


Fix #4317 to update jms documentation for pooling and XA support (#4323)

Suppress by https://github.com/jboss-fuse/camel-quarkus/pull/208


Unresolved reference 'OVHCloudEmbeddings'

When running the RAGStreamingChatbot from the python-langchain-chatbot project, for me, it can`t find the OVHCloudEmbeddings reference.

I installed all the requirements from the requirements.txt.
I think the error is caused by a missing requirement in the requirements.txt.

Strange because the dependency is in the official langchain_community dependency : https://github.com/langchain-ai/langchain/blob/langchain-core%3D%3D0.2.37/libs/community/langchain_community/embeddings/ovhcloud.py
And this dependency is downloaded by the langchain_community dependency in the requirements.txt
Could you try to see in your venv if the dependency is downloaded as for myself?
cd venv/lib/python3.12/site-packages/langchain_community/embeddings
 ll ovh*
-rw-r--r--  1 sphilipp  staff   3.4K Jul 19 10:56 ovhcloud.py

On my side I'll test by cleaning all my venv to test if I can reproduce the problem 😉

Oh, sorry, I made a mistake with my IDE. Everything is fine now!


Increase maxRecvMsgSize in grpc server of mako-stub

This should mitigate the #694
/assign grantr
/area test-and-release

/cc @srinivashegde86
/cc @Fredy-Z
/uncc

/cc @adrcunha

/approve
I'll defer LGTM to Victor.

Out of curiosity can the mako results be streamed? (ie. use multiple messages)

@dprotaso not sure, this depends on mako client i think


fix(ci): lint ci fail

This pr fixed a small lint error and added lint-fix to Makefile, introducing a convenient way for developers to fix make lint errors

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Thanks @levisyin ❤ , but the correct solution I think is to uncomment lint-format Makefile target https://github.com/cometbft/cometbft/pull/2049, not to introduce yet another target.


Tracing with logging, authentication and static ThreadLocal

What is the goal of this PR?
To make GrablTracing more flexible for users, allowing testing of tracing-enabled applications without a full Grabl server.
The use case that has already been encountered is that it is very difficult to setup and test simulation when it is hard-coded to require a secure connection to grabl-tracing.
Other use cases include tests, including mocked servers and clients, or when the user simply does not want tracing to run (if it is causing issues in an application due to bugs that are difficult or impossible for the user to fix at the time).
What are the changes implemented in this PR?

Removed some redundant dependencies
Slight refactors (package renames, interface extraction)
Added no-op, logging, secured and unsecured variations of GrablTracing.
Added static tracing, which allows clients to do static level tracing with metadata trace and context passing via ThreadLocal stacks.
Fixed some tracing bugs

I do think the title of this PR can be improved to represent the significance of the changes made. 🤔

I've renamed this PR title to an even better one, @adammitchelldev : "Tracing with logging, authentication and static ThreadLocal". Useful to have succinct and descriptive titles, not only for ease of understanding when reading logs, but also for beautiful release notes (that are automatically generated from PRs).


Refactor frontend-search plugin

This PR refactors and cleans up the frontend-search plugin, and improves the documentation.
The changes include:

Use of an associative array to define the necessary URLs.
This makes it trivial to add another search context: just append a new entry to the urls array, add the alias and update the help messages .
Uses all arguments passed instead of just the second, to enable for multiword queries.
Now frontend <context> multiple words or a whole phrase will also work.
Clarifies the README and removes duplicate information.
Includes a better help message adapting it from PR #2930.
This is how it looks:

Fixes #2930
/cc @willmendesneto

+1. Great job @mcornella, thanks!

/cc @robbyrussell

Tested! @robbyrussell could you merge this, please?


Use warnings module for warning about ignored anisotropy in geometric kriging.

Currently, the print warning does not benefit from the warnings functionality.
E.g. if geometric kriging is done in loops, the warning will flood the standard output.
What I did to fix this:

added a check to see if there's really anything ignored.
use warnings module to allow user to use standard warning handling.

Looks good to me, thank you!
P.S: we are "Squashing and merging" PRs, so in the future it's better to make PR from another branch than the master of your fork (that you could later delete)...  Let me know if you encounter issues with it..

Thanks for merging and the suggestion, still getting used to git!


Support Force 90Hz

From a recent Reddit post on r/oneplus:

It is necessary to change 2 numbers.
Line 41 of the RefreshRateService.kt would need to be changed from if (currentStatus == "2") { to if (currentStatus == "0") {.
Line 44 of the RefreshRateService.kt would need to be changed from return this.setStatus(2) to return this.setStatus(0).

It's also necessary to change line 44 of RRTileService.tk from if (rateStatus == "2") to if (rateStatus == "0") to properly detect forced 90hz instead of auto 90hz when showing 60/90hz for the tile text.

Sir thanks for the app it is working in latest one plus 8t also.
**can you change tile name from 90 to 120 as 8 pro and 8t has 120 hrz


Text.span doesn't support all the same props as Text

Describe the bug
Text.span should use all the same props as the Text component according to documentation.
To Reproduce
https://codesandbox.io/embed/o7konm53v5
Expected behavior
Either the Text.span component should support the display prop or the documentation should be updated that this component's display prop cannot be modified.
Rimble UI Version

0.7.1 (latest)

Resolved in 0.8.1


Update setup-guides-for-microsoft-365.md

Title and description update that includes Intune Suite.

[heart]         Josh Gutierrez (EXPERIS) reacted to your message:

From: Kelley Vice @.>
Sent: Friday, November 15, 2024 11:23:38 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Josh Gutierrez (EXPERIS) @.>; Author @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Update setup-guides-for-microsoft-365.md (PR #13671)
Merged #13671https://github.com/MicrosoftDocs/microsoft-365-docs/pull/13671 into public.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/pull/13671#event-15319077534, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BM66LJVGRL4NV7UWUZZKLJT2AZ67VAVCNFSM6AAAAABR4CWDA6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGMYTSMBXG42TGNA.
You are receiving this because you authored the thread.Message ID: @.***>


Another style issue with Select2 multiple and Adminlte

I have a problem using select2 multiple in the edit page, when I press the backspace key, blank spaces are shown at the beginning (always show 49 spaces), in the photo it is better appreciated.

On the other hand, in the create page, it works normally, without blank spaces... that's how I want the edit page to work.

Edit view:
<select class="form-control select2" name="branches_id[]" id="branches_id" multiple>           @foreach ($branches as $branch)                      <option value="{{ $branch->id }}"                                 {{ in_array($branch->id, old('branches', [])) || $user->branches->contains($branch->id) ? 'selected' : '' }}>                                 {{ $branch->name }}                      </option>           @endforeach     </select>
Controller
public function edit(User $user)     {         $branches = Branch::all();         return view('users.edit', compact('user', 'branches'));     }
I already broke my head and I have not been able to solve it.
Any ideas to solve the issue. all help will be greatly appreciated and received.

@juanyrascon That's a really particular and strange situation. I don't believe it's related to this package or to AdminLTE. The only difference between a create and an edit form is that in the edit form the select2 input may already contain data. I suggest you to try to enclose the issue, for example:

Test with an initially empty select2 component in the edit form and check whether the issue persist:

<select class="form-control select2" name="branches_id[]" id="branches_id" multiple>
    {{--
    @foreach ($branches as $branch)
        <option value="{{ $branch->id }}" {{ in_array($branch->id, old('branches', [])) || $user->branches->contains($branch->id) ? 'selected' : '' }}> {{ $branch->name }} </option>
    @endforeach
    --}}
</select>

Test with a set of hardcoded data in the select2 component in the edit form and check whether the issue persist:

<select class="form-control select2" name="branches_id[]" id="branches_id" multiple>
    <option value="1" selected>val1</option>
    <option value="2" selected>val2</option>
    <option value="3">val3</option>
    <option value="4">val4</option>
</select>

If in those cases, you don't observe the issue, then the problem is related to how you fill the options in the @foreach loop (maybe data comes with hidden characters from the database, \t or something like that). If the issue persist in those cases, you may try updating the plugin files to a newer version.

Finally, the problem was the vscode setting, "the length of line wrap size: 80", I changed it to "the length of line wrap size: 280".

@dfsmania   Muchas gracias por tu ayuda.


Add --low_mem option to use less memory when copying files on memory constrained devices

Added: v1.0.2


[BUG] Running the Roblox Studio (Bloxstrap) shortcut opens the Discover page instead of launching Roblox Studio

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
When trying to run the Roblox Studio (Bloxstrap) shortcut created after installing Bloxstrap, it doesn't launch Roblox Studio and instead opens the https://www.roblox.com/games page
Roblox Studio runs fine when launched from the original shortcut
I am using the latest release version from Actions (https://github.com/pizzaboxer/bloxstrap/actions/runs/7226398711)

You downloaded a debug build of a version that's yet to be released and you're opening an issue complaining that it's not working properly.
Yes

Also I downloaded the one that said Release

That's still prerelease

Yes I know I'm downloading the actual release (from the Releases tab) now

There's no Bloxstrap shortcut for Studio there how quaint
Oh well 🤷♂

And don't treat people like they know everything about your app btw :3

And don't treat people like they are supposed to know everything about your app btw :3

Mate, this isn't about the app it's about GitHub. You should know what actions folder is used for in GitHub, after that there is a wiki.
Respect Pizzaboxer for his work.

There was nothing saying that there will be no support given for pre-release builds that's why I retaliated

There was nothing saying that there will be no support given for pre-release builds that's why I retaliated

Mate, what are you saying.
Everyone knows that there isn't or almost no support for prerelease.
It's like saying that a beta software is the official release.

And don't treat people like they are supposed to know everything about your app btw :3

There was nothing saying that there will be no support given for pre-release builds that's why I retaliated

I think anybody would reasonably assume that complaining about an in-progress version that hasn't been finished yet of which you went out of your way to intentionally download is a stupid thing to do. What were you expecting?

I assumed it was fine because most of the apps I use are fine with reporting bugs for an in-dev version 🤷♂

The difference betweel all those here is that this is not actively being worked on. I can't actively work on this. The last actual commit on main done by me was two months ago. It's insanely frustrating to receive complaints about unfinished work that I am obviously well aware of doesn't currently function properly.
I hope you see where I'm coming from with this. I apologize if I was explosive at first, but I really think this should've been self-explanatory to anyone.
(by the way, comparing this to the linux kernel? really?)

I assumed it was fine because most of the apps I use are fine with reporting bugs for an in-dev version 🤷♂

No way you actually just compared a personal project against projects with TONS of developers and stars, this repo and project is only maintained by one person nobody else.

I assumed it was fine because most of the apps I use are fine with reporting bugs for an in-dev version 🤷♂

Bro did he compare a Linux project to a GitHub project built with the community??
Mate Linux prerelease is different, they keep most of it until it's nearly ready.
💀


Source control repository missed a repository if we have multiple with same name

Issue Type: Bug
With the recent update 1.66, where the release note mentions that repositories are listed in alphabetical order in source control tab.
But, this created another bug where if we have 2 repros with same name under a folder, one of them will miss in the list.
Steps to reproduce:

Create root folder and project1 and project2 as sub folder under it
Create a git  repo name with 'test' under each project1/2
Now add root folder to the project explorer. And you will notice only one test git repo listed under source control tab

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Remote OS version: Linux x64 5.4.0-90-generic

/assign @lszomoru

@lszomoru I've already pointed one duplicate to this. I think a fix needs to be considered for recovery.

@gjsjohnmurray, yeah, I am currently looking at this and I will make sure that it is in the next recovery release.


$afterInsert

Just a simple question not an issue, is $afterInsert part of the Object.query().insert()?
ie
will
await Object.query().insert()

wait until $afterInsert is complete?

In particular, we can to know how this will behave when run in AWS lambda serverless environment. Just worry that $afterInsert won't have a chance to run / finish if it does its work asynchronously behind the scene independent of insert.

$afterInsert can be async as it is clearly said in the documentation.


Test for slicing/splicing past boundaries

Need a test that checks how slicing and splicing will work past list/string boundaries, due to the JavaScript implementation performing the wrapping and limits automatically, but the C version needing to calculate the results exactly.
Ex:
var x = {1, 2, 3, 4, 5}
say x[-100:1000]

etc

fixed:
https://github.com/voidqk/sink/commit/26bcd4916a3bfd2cd6febf66bb10b87defd04b47


Create a Docker container for the application

Not needed when we are going to microservices. This library will be turned into a package to help create the REST API for microservices.


Cover images don't show in single post view.

The update broke something in the single post view.

I didn't modify the relevant code. Did you set this? https://g1eny0ung.site/hugo-theme-dream/#/params-configurations?id=showsummarycoverinpost-true

Yes, that has been set. I returned to the past version of the single html and it's ok but the current file didn't work for me. I'll test again and report back.

Yes, that has been set. I returned to the past version of the single html and it's ok but the current file didn't work for me. I'll test again and report back.

👌🏼


Fold divide and multiply by same value.

We want to fold code like (x*y)/x and other permutations of this.
Fixes #1531.

According to https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#spirvenv
The Nan is not a problem because of the line "NaNs may not be generated. Instructions that operate on a NaN may not result in a NaN."
The denorms might be an issue.  There is some wiggle room because it says "Any denormalized value input into a shader or potentially generated by any instruction in a shader may be flushed to 0."  This indicates (but does not formally allow) a lack of precision when dealing with denorms.  We can try to get clarification on this.


isnt it correct to set optimizer and lr_scheduler's "name" to "type" ?

Hi~! I'm trying to start training but I got an simple error "
KeyError: "cfg or default_args must contain the key 'type', but got {'name': 'Adam', 'lr': 0.01, 'betas': [0.5, 0.999], 'eps': 1e-06, 'params': [{'params': <filter object at 0x7fca95bd3f98>}]}\nNone"
So I changed "name" to "type" of "optimizer" and then I got another error.
KeyError: "cfg or default_args must contain the key 'type', but got {'name': 'StepLR', 'step_size': 2, 'gamma': 0.5, 'optimizer': Adam (\nParameter Group 0\n    amsgrad: False\n    betas: [0.5, 0.999]\n    eps: 1e-06\n    lr: 0.01\n    weight_decay: 0\n)}\nNone"
So, I again changed "name" to "type" of "lr_scheduler".
and then it seems no more error but, there is no progress on trainning. just got stuck from scratch.
2022-05-25 11:38:49,545 - using gpu: 2
2022-05-25 11:38:49,546 - => creating model ...
580 images found.
I used my custom images/depth/ so on which are fit to NOCS format and I already passed running the data_processing.py script.
Please help me~!

The problem may be caused by the version of gorilla-core.

You could try pip install gorilla-core==<IP_ADDRESS>.


Add NewSeleniumServiceV4 to support cli args for selenium version 4

Selenium V3 seems to now be considered legacy (https://www.selenium.dev/documentation/legacy/selenium_3/). This PR adds NewSeleniumServiceV4 which sets up the service using the new format for v4. During my (admittedly limited) testing it seems to work as a drop-in replacement for Selenium V3 implementation.

Would it be possible to merge this? @minusnine

I'm also not sure that this is correct. The PR uses /wd/hub as the urlPrefix (which is a suffix btw), which doesn't seem to be used by selenium 4:
GET http://localhost:4444/wd/hub
->
{
  "value": {
    "error": "unknown command",
    "message": "Unable to find handler for (GET) \u002fwd\u002fhub",
    "stacktrace": ""
  }
}

(same for POST)

Can confirm this is working for me with https://github.com/SeleniumHQ/selenium/releases/download/selenium-4.1.0/selenium-server-4.1.1.jar
I think the urlPrefix is named thus because there are other routes called, eg: /wd/hub/session etc.

Hm, ok. Do you specify a prefix? Or do you omit it? Would you mind posting a quick example where it's running for you? Would help tremendously!


Prism doesn't handle nullable fields properly in mocked responses

When I specify nullable fields in a OAS3 file, I expect prism to be able to return null values in mocks for these fields. Example spec:
components:
  schemas:
    Pagination:
      description: "Defines an object containing information for cursor based pagination."
      type: object
      properties:
        ending_before:
          type: string
          nullable: true
          default: null
        starting_after:
          type: string
          nullable: true
          default: null

Prism output:
pagination: { ending_before: "", starting_after: "",
Note prism is sending empty strings, not nulls. SwaggerUI seems to be handling this OK, however, so I'm pretty sure our spec is OK:

Hey @LesterTheTester,
I've verified this — we're missing the nullable option in our code to see if we're generating an example. We'll look into this. //cc @philsturgeon


GCC warnings don't go away until manual recompile

Brief Issue Summary
I'm not sure if this is an issue with CMake Tools or cpptools, or if it's a bug at all, but GCC warnings reported by the CMake Tools output parser don't go away until I manually recompile through CMake Tools. The error reporting by cpptools works as I type, but it seems like that's just for hard syntax errors, not warnings.
Expected:

Fix problem reported by GCC warning
Save file
Automatic recompile occurs, removing the squiggle and the entry in the problems pane

Apparent Behavior:

Fix problem reported by GCC warning
Save file
Nothing happens
Run the "build target" action
Squiggle and warning goes away

CMake Tools Log
There isn't any activity after saving a file, so I don't think there are relevant logs
Platform and Versions

Operating System:  Windows host, RHEL7 remote SSH connection
CMake Version:  3.17.5
VSCode Version:  1.56.2
CMake Tools Extension Version:  1.7.3
Compiler/Toolchain:  gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)

Thank you for opening this report. We may not be able to fix this behavior exactly since it is controlled by VSCode but we will brainstorm for possible solutions and workarounds.

any updates? This problem also bothered me for a long time.


add seko

RE-CHECK!

Automated adapter checker
ioBroker.seko

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "seko" in latest repository
[ ] :eyes: [W515] Why you decided to disable i18n support?

Add comment "RE-CHECK!" to start check anew

see Telegram, welcome :-)


Change Mission Statement

Some wording to indicate that we are Infrastructure as Code for other 3rd parties and that we should always make sure to be open for extension.

I'll copy in here what I said in slack on this topic :-)
"I would be nervous about doing that until we've finalised the docs on how to run it. I don't want another of these: https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/626 - it's fairly safe now (if you skip a couple of tags) and the Vagrant files are in place to make it easier to deploy in VMs but the docs aren't fully up to date and I think it still tries to change the hostname on the machine."
Once the docs are happy, and safeguards are in place, and a few people have tested them I'd be totally happy with such a change and it's definitely where we'd like to be :-)

The documentation around Vagrant (and PBTests) has been greatly worked on since the latest comment. I believe (from my look at the wikipedia article) that we are 'infrastructure as code', so I don't think it's unreasonable to put it in the docs now :-)


In-app camera does not record location

Steps to reproduce:

Make sure the app is able to use the GPS, for instance by opening the "Nearby" activity.
In the main activity, tap the "+" button then tap the camera icon
Take a picture, try to upload it. At the "Media details" step, the latitude/longitude button is not visible, which means that the picture is considered to have no latitude/longitude associated with it.
Outside the app, use the phone's camera app to take a picture, then try to upload it to Commons. At the "Media details" step, the latitude/longitude button is visible.

I tried these steps 3 times, always with the same issue.
The in-app camera should record location.

I could confirm that the in-app shots don't appear to have any location associated with them.
Just for the note to anyone who picks this up, we need to ensure the app doesn't accidentally upload in-app camera images with location when the user has turned it off by disabling "Location" option via Settings > Manage EXIF Tags.

@nicolas-raoul, Can I look into this?

@Pratham2305 Yes thanks! 🙂

I have noticed, this only happens when the app's location permission is not available otherwise it is working as expected when both commons and camera app have location permission.

Interesting!
That presumably happens when the user has no interest in Nearby.
So maybe ask for user permission when starting the in-app camera? Preferably with a message such as:

Location data helps Wiki editors find your picture, making it much more useful.
We suggest you let the app attach location information to the pictures taken via this button.
Thank you for your contributions!
Yes, great! / No, do not attach location

I have noticed, this only happens when the app's location permission is not available otherwise it is working as expected when both commons and camera app have location permission.

Interesting indeed. For some reason, this doesn't appear to be the case at least in my device. i.e., the in-app camera doesn't seem to be capturing the location even when both the app and camera app have the location permission granted and GPS is turned one. Not sure how that's the case. Anyways, let me know in case any specific information is needed to debug this. I'll be happy to share it.

Interesting! That presumably happens when the user has no interest in Nearby. So maybe ask for user permission when starting the in-app camera?

Yes, that would be great!

Interesting indeed. For some reason, this doesn't appear to be the case at least in my device. i.e., the in-app camera doesn't seem to be capturing the location even when both the app and camera app have the location permission granted and GPS is turned one. Not sure how that's the case. Anyways, let me know in case any specific information is needed to debug this. I'll be happy to share it.

@sivaraam Can you just confirm that your camera is recording location when used normally?. Thanks!

Can you just confirm that your camera is recording location when used normally?.

Yes, it does.

@Pratham2305 Any progress on this, maybe? It would be a really great bugfix :-) But if you are busy, don't worry!

My initial report was with a Samsung S10 device.
Now I switched to Pixel 6 and can not reproduce the issue anymore.

Here's a screen recording link of the issue which I am able to always reproduce on my OnePlus Nord running Android 12: https://drive.google.com/file/d/1X35a7cbXBCFz62v_hdudXLlYhIeEAPCt/view?usp=sharing


Rename ‘c-mini’

The ‘c-mini’ representation is becoming increasingly poorly named, as medium term plans are for it to encompass C++, Rust, etc.  My mild preference is for this to become known as the intermediate representation (IR), or some variant.  Maybe Fuzzable Intermediate Representation (FIR).

It’s now called ‘fir’ (fuzzer intermediate representation).


compile packages with clang 9 in linux?

Hi, I don't know yet why but after this commit I got a ~30% speedup in the similarity searches when compiling FPSim2 with clang (I'm developing in mac and I later found that the speedup didn't occur in Linux/gcc).
It works well in azure pipelines (ubuntu 18.04, clang-9). With this configuration in a Linux laptop I got the same speedup.
Could it be possible compile the packages with clang-9?
Many thanks again for building the conda packages.

Closing this for now. I'll try to send a PR after I make things a bit clearer and tidy up the code.