Incorrect typechain repo in github dependency graph

If you check the dependency graph of any repo that uses Typechain core package, it points to nomadcoders/typechain.
You can see the second last dependency in here.
This may be due to that repo having typechain in it's package.json file, maybe github selects the one that's older. I think having a @typechain/core kind of package for the core package should fix this, since I can see the first dependency @typechain/ethers-v5 correctly mapped to this repo. I understand this is not a serious problem, but it'd be nice to see the correct dependency linked in the dependency graph.

I think there's nothing we can do :( Github shows now that this repo is used by 320 other repos so maybe they fixed it on their end...


Open document list

I did a update today and i preferred the open documents in a list on the left side. Is there a option to put it back like that?

The answer is no, it cannot be anymore

Why not make the menu reside on the left at the regular list and be able to fold it. The list on the right side is just awkward, its not fitting in the design GUI very well. i also see some glitches when you swap the side bar from right to bottom left. The menu list also floats behind this panel sometimes

Its when you first set it to the bottom and then uncheck it. See screengrab

Great Idea!. 🎉

I had a new update and from the images i see the menu looks different. Though on install and reload i still see same menu as above or are the images on the main page older?

The page is old.

I do like that menu bar more than this current one if im honest, ps what is the new update? i dont see any difference in the menu, i thought it was able to fold now. I still see that error with it going behind the main toolbar on the right. But i see other plugins show issues here as well. Sometimes the toolbar shifts to the right leaving a black hole to the right of it. It happens when i move the toolbar to the left and back.
see screengrab

PS i just noticed that bookmark function, is it possible to name these? or add this function?

please try remove "No Distraction" addon.
I'm working in this addon.
What's with the bookmark?

I dont have "No Distractions" addon, if i understand/rad well. Its under main settings see "other" in preferences. Its unchecked and is under view menu, its a bracket system thing. Using or not using this has no effect on that black gab i showed earlier.
About the bookmarks, i see i small icon and see a list of bookmarks, they all show linenumber. I thought perhaps naming them would be nice, but would be a lot of coding i guess. They only acts as a single link, not each bookmark per document is clickable.

current version 5.1.8
enable option ShowWorkingListViewonLeftSidebar > brackets preferences or Custom Work preferences

nice, thanks for updating it.


Add nodeSelector documentation to readme

Fixes #49
Signed-off-by: Martin Kennelly<EMAIL_ADDRESS>

@pperiyasamy is this ok with you?

@martinkennelly  Thanks! I think it would be good if we make the doc example for macvlan cni, because that's a suitable use case where can apply nodeselector label (like  k8s.v1.cni.cncf.io/nodeSelector: master=eno3) based on availability of master interface.

@pperiyasamy better you think?

/lgtm

/lgtm


Single column mode for coupled runs

Currently, choosing a "column" config leads to an error when initializing clima atmos via the coupler atmo_init function. Once this is resolved, we then need to take the atmos boundary space (a point in this case) and use it to make the LSM domain - that function still needs to be written too.

@kmdeck is this still an issue?

oh! I think the issue was just that the coupler only supports spherical runs, but atmos can be run in column mode by changing the command line arg. Not sure if we want to support that option?

Actually, it might be good to have. I think there were plans to do a coupled RCE example at some point. I'll keep this active then, as a low priority item :) thanks!


Uncaught Error: Unexpected value '[object Object]' imported by the module 'AppModule'

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Loading a custom Module from our sdk throws
zone.js:269 Uncaught Error: Unexpected value '[object Object]' imported by the module 'AppModule'

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

This is the custom Module in our SDK.
@NgModule({
    providers:SELFBITS_PROVIDERS,
    imports:[HttpModule]
})

export class SelfbitsAngularModule{
    static initializeApp(config:SelfbitsAppConfig):ModuleWithProviders{
        return {
            ngModule:SelfbitsAngularModule,
            providers:[
                { provide: SELFBITS_CONFIG, useValue: config }
            ]
        }
    }
}

loading it in app.module.ts throws the error above, which seems to originate from missing the @NgModule Decorator. The SDK works fine in ng2-admin from akveo which is build on the angular2-webpack-starter. If I comment out the @NgModule Decorator, then ng2-admin also throws the same error, hence the suspicion that somehow it gets lost during (maybe) bundling.

What is the expected behavior?

Initialize sdk without error

Please tell us about your environment:
Angular version: 2.0.0

maybe related to this https://github.com/AngularClass/angular2-webpack-starter/issues/908#issuecomment-251108356

@aavelyn Did you find solution?

@zeqk seems to not be related.. tested her some tips from there but didnt work.
Anyone has other solutions?
in my case i'm using angular universal with express, so i dont know if is related to that..
Here is explaining more https://github.com/robwormald/ng-universal-demo/issues/21


Python taking 100% of my processor

Hi there, I've been using this workflow and I absolutely love it. I realized it was taking almost 100% of my processor capacity and I had to turn it off to bring it back to normal. The process that was taking all the CPU power was Python.
It also elevated Alfred's energy impact to 151.95
I am not really a programer so I wouldn't be able to point out exactly what was happening.  Is there any fix I should do?
thanks!

Hi,
First and foremost, I am huge fan of this workflow and use it daily! However, I am experiencing the same issue as @arturbenchimol and I've turned it off also :-(
I'm also not an expert programmer but there is a process called "Python" that is consuming ~98% of my CPU. Here are the "Open files and ports" (found via Activity Monitor -> Inspect):
cwd
/Users/justin/Library/Mobile Documents/com~apple~CloudDocs/Alfred 3/Alfred.alfredpreferences/workflows/user.workflow.D41D8E7C-29C4-4B87-A53B-11A0C028D529
txt
/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
txt
/System/Library/Frameworks/Python.framework/Versions/2.7/Python
txt
/usr/lib/dyld
txt
/private/var/db/dyld/dyld_shared_cache_x86_64h
0
/dev/null
1
/dev/null
2
/dev/null
3
/Users/justin/Library/Caches/com.runningwithcrayons.Alfred-3/Workflow Data/com.drive.azai91/com.drive.azai91.log
4
/Users/justin/Library/Caches/com.runningwithcrayons.Alfred-3/Workflow Data/com.drive.azai91/com.drive.azai91.log

Finally, my system specs are below:

Alfred-Drive-Workflow 1.2
Alfred 3.3.2 [818]
macOS Sierra 10.12.4

Please let me know what else I can do to help debug from here.
Justin

@arturbenchimol FYI - give this a try:
https://www.alfredforum.com/topic/10193-python-fix-how-to-fix-python-workflows-hanging-alfred-on-sierra/
https://github.com/deanishe/alfred-fixum

thanks, @justinjm I'll give it a try and report back here. Thanks!

I have the same issue. Alfred Fixum didn't solve the issue unfortunately. Only resolution would be if the workflow get's updated. @azai91 any plans for solving this bug?

I'm facing the same problem. Hope this could be fixed soon.
Thanks!

I added the Fixum workflow and it stopped bothering me.

On Jun 22, 2017, at 16:55, Carlos Yaconi H<EMAIL_ADDRESS>wrote:
I'm facing the same problem. Hope this could be fixed soon.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/azai91/alfred-drive-workflow/issues/23#issuecomment-310500140, or mute the thread https://github.com/notifications/unsubscribe-auth/AIkjqMeB98Hd76Ll0dGZqkj__OW9bNXhks5sGtTfgaJpZM4M6P9L.

Fixed in #22. Download the latest workflow to solve the problem.

@jgarber is just swapping the file for the new version enough?

Sorry I have to ask, but do I run "make" after cloning this to get the workflow updated? I just want to get this update because I'm having the same issue  as mentioned above. Thanks!

Sorry for the noob question here, but I can't find anything online to help me with this...
How do I get this repo "packaged" into an alfred workflow so I can install it? I'm trying to get the latest version. Thanks

@azai91 - please create a release with the most recent version. Thank you.

It is the src directory which is the actual workflow, so if you clone this repository, remove the old workflow (from Alfred’s workflows folder) and create a symbolic link to this repository’s src folder.
Though currently it is still using a version of the alfred-workflow module which is incompatible with Alfred 3.4 but I have submitted a PR for updating it.
I added the new version as a git submodule so use git clone --recursive «repository» when you clone it.

Thank you @sorbits - I appreciate it!

There is now a version 2.0 which is a complete rewrite and no longer relies on the python library that caused this issue.


[Coin3D] Add new ports for simage, Coin, and SoQt

Describe the pull request

What does your PR fix? Fixes issue #4295

This PR adds ports for the Coin3D libraries simage, Coin, and SoQt.

Which triplets are supported/not supported? Have you updated the CI baseline?

The simage port should work on all triplets.
The Coin and SoQt ports do not support ARM and UWP builds due to OpenGL. The CI baseline has been updated accordingly.
The x64-osx support for SoQt requires a fix for issue #9879.
Coin requires a dependency on boost-math until issue #8753 is addressed.

Does your PR follow the maintainer guide?

Yes.

Thank you all for the feedback. Should be integrated now.

I found some linux regressions, please check the logs here.

The error log states, that the file /ci/myagent/_work/1/s/installed/x64-linux/share/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake of package qt5-base contains a reference to file /ci/myagent/_work/3/s/installed/x64-linux/lib/libEGL.so that apparently does not exist on disk.
Apart from the reference to the missing libEGL.so file in /ci/myagent/_work/3/..., all other entries in the log file point to the directory /ci/myagent/_work/1/...?
I've just tested this again on a local Ubuntu 18.04 installation and it compiled without issues.

@rickertm I will take a look.

I can't repro that regression too, so I rerun the pipeline test.

@ras0219-msft Could you have a look?

The issue with the missing file /ci/myagent/_work/3/s/installed/x64-linux/lib/libEGL.so seems to have been addressed in #10390?

@rickertm We are trying to resolve that.

/azp run

Please resolve linx regression, get log here.

Same issue as before, file libEGL.so is still missing and references folder /ci/myagent/_work/2/... instead of /ci/myagent/_work/3/...
CMake Error at /ci/myagent/_work/3/s/installed/x64-linux/share/cmake/Qt5Gui/Qt5GuiConfig.cmake:15 (message):
  The imported target "Qt5::Gui" references the file

     "/ci/myagent/_work/2/s/installed/x64-linux/lib/libEGL.so"

  but this file does not exist.  Possible reasons include:

Seems to work now after rebase to master.

Done, thank you for the suggestion.

LGTM. Thanks for your PR.

@rickertm what's up with the downloading distfiles for soanydata and sogui, as opposed to setting up ports for them by themselves? I don't think I understand.

soanydata and sogui are submodules that were not included in the tarball archive at the time of this PR, so I followed the canonical way for this case described in https://github.com/microsoft/vcpkg/issues/1036.
The upstream project has since added additional tarball archives that include the submodules, I can update the PR accordingly if you prefer. The patches have also been integrated upstream in the meantime, but there is no new tagged release version yet.

Ah, cool, that's fine then :) just curious.

/azp run

I've added additional patches for simage when linking against libsndfile (FLAC and Ogg/Vorbis order). I've also disabled examples and tests. All patches have been submitted upstream.
On Linux and UPW, the simage port now depends on giflib, libpng etc., as VfW, GDI+, or CGImage are not available.
The Coin port adds features for optional libraries that are linked at runtime, with simage and zlib as default features.

The boost-math dependency in Coin can be removed once #11131 is merged.

/azp run

libqcow:x64-linux regression are not related with this PR.

/azp run

Thanks so much @rickertm :D

Thank you for merging this @strega-nil.


Issue with missing Symbols in TS

I'm running into an issue that developed around the same time yesterday as the regression from 0.26.12. I have now upgraded to 0.26.14 and the TS features constantly crashing has indeed resolved. However, I am now getting a lot of odd TS inference in vs-code such below:

For some added color, you can see below that indeed vs-code complains about the symbol not being available while also providing details on the symbol:

Now I think there is a decent chance that this issue is not related to Volar because I opened up one of my individual packages in the monorepo. The particular package uses TS but not Volar and in this case I am seeing a similar pattern which suggests something else may be in play. That said ... all of this started yesterday at the same time.
Anyway, feel free to close if you can't reproduce this in your repos or feel that it's clearly connected to some other artifact. I am using the insiders edition of VS-Code and it's now on TS 4.5.0 so maybe this is where I'm hitting the wall.

I did roll back to TS 4.3.5 to see if that fixed things but I'm still seeing this behavior

... eslint(import/named)

It's seem eslint extension error report, please try disable eslint / volar respective and check the error still on or not.

Yes you're right, i'm going to close this as it's clearly not a Volar issue but i'm at a loss where to point. The eslint plugin which appears to throw the error is not installed!


[at_onboarding] [MacOS] Need a feature allow user share atSign between apps

In the new onboarding widget, we can give the user an option to share the the keychain between different apps. But this feature is only available in macos.
We need to decide whether adding this feature only on macos will be fine or not.
Currently this feature is disabled.

IMHO - making use of keys that we have available to us to improve their experience is the preferred option.

It would be my suggestion to make sure that the other desktops env all act the same . So that needs investigation. If they do this is a good idea.
I think we should also look into allowing multiple instances of applications so they do no step on each others hive files..

Leaving as a follow-up arch call discussion item

@sonle-geekyants We will have to check a few things here :
Platform that supports share feature:
Desktop Platforms:

[ ] MacOS
[ ] Windows
[ ] Linux

Mobile Platforms:

[ ] Android
[ ] iOS (We will have to create ios app groups and test)

Data Related check:

[ ] We also need to make sure that if we use the share feature on a platform, two apps should not step on each others hive files .

Reducing SP and moving to next sprint.

Would like Gary's input when he's back

@gkc and @sachins-geekyants
Related to this issue:

MacOS: ok
iOS: ok. the app must add Keychain Sharing to Capabilities in XCode
Android: don't support. biometric_storage use KeyStore in Android and can't share between apps
Linux: don't support for now
Windows: ok.

And don't make any impact to hive data if app use share atSign.

Could not be worked on in this sprint, moving to next sprint.

Reducing SP and moving to next sprint for testing and deployment.

This could not be tested in the last sprint. Moving to next sprint.
@tinashe404 can you help us test following branch.
feature/enable-user-sharing of the Wavi app
feature/enable-user-sharing of the Atmosphere app

@sachins-geekyants sure lets have a chat about this when you're back on Wednesday.

I've added a function sharing atSign on Menu Bar in the Wavi app and the Atmosphere app. Please test it @tinashe404 @ayushkumarrojha @sachins-geekyants
https://user-images.githubusercontent.com/88494375/200545608-597881cf-73fe-4dfb-b0f8-985453a6997e.mov

I've tried this our on a simulator and have made the following observations

If you open an app with an already onboarded atSign (in my case atmospherePro) and press start, it will ask if you want to share your atsign. At this point, i'm not sure which atSign is onboarded so i don't know if i want to share it or not. It would be good if we had something that shows which atSign it is. We also need to update the text on this screen, eg remove the @ in atPlatform. I will confirm wording tomorrow.

I pressed yes to allow sharing and then opened wavi. Wavi made me onboard and upload keys. I had assumed that if i had already said yes to sharing then if i opened wavi it would automatically onboard?

What did work was if i added an atSign to one app, and then went to the other app and went to switch atsign, it would appear there too. The same for when i deleted it on one app, it would disappear from the other app under the switch atsign options.

if i choose to share an atSign, all other atSigns that i onboard after that are automatically shared too. should the default be on or off?

I had assumed that if i had already said yes to sharing then if i opened wavi it would automatically onboard?

-> Wavi will automatically onboard when you log in to HomePage -> enable sharing atSign before.

if i choose to share an atSign, all other atSigns that i onboard after that are automatically shared too. should the default be on or off?

-> Default should turn on. Because when allow sharing atSign, the app will share all data. If you don't want to share data, you shouldn't turn on sharing atSign.
@tinashe404

Wording...
Share this atSign with all your atPlatform apps?
You will not be required to re-upload your atKeys when you use @tinashe404 with other atPlatform apps on this device.

Moving to next sprint.

Yes, I don't need to re-upload atKeys because when uploading atKeys in any app, I will save all information of that atSign in device. So I can share them with other atPlatform apps. @tinashe404

@ayushkumarrojha please help me test this ticket.

@sonle-geekyants @ayushkumarrojha can you update this ticket ?

https://user-images.githubusercontent.com/88494375/210534986-7d0e571f-7595-4cbe-b67c-ce452e51a8c6.mov
I've uploaded the video @sachins-geekyants

@sonle-geekyants Can we changes @platform to atPlatform in the message appears on dialog box ?

@sonle-geekyants Can we changes @platform to atPlatform in the message appears on dialog box ?

Okay. I will edit it.

I've changed it @sachins-geekyants
https://user-images.githubusercontent.com/88494375/211784017-e51bc5b9-5993-43fb-bb47-88375d3d6b29.mov

@sachins-geekyants @sonle-geekyants the text still says " when you use @ sign with other apps"....
Shouldnt " @ sign" be the actual atSign that is currently onboarded?

@tinashe404 This message appears before onboarding, so we don't know the atSign yet.

@sachins-geekyants in that case can we change the text to say "when you use this atSign with other"

I've changed it. Could you please check again? @tinashe404

PRs have been raised for the above changes, I will assign it 0 SP till PR is reviewed.

@sonle-geekyants can you check the status of PRs, it's still open.

user sharing is available in at_client_mobile 3.2.9.
atApps needs to be deployed with options to enable sharing atSign info across apps.

@sachins-geekyants @ksanty  Is this still relevant, and something that needs to be worked on?

The implementation is done in at_client_mobile and onboarding_flutter.
This feature is available in atPro desktop also, for other app we can create separate tickets.

user sharing is available in at_client_mobile 3.2.9. atApps needs to be deployed with options to enable sharing atSign info across apps.

Is there a screen shot showing where we find this?

user sharing is available in at_client_mobile 3.2.9. atApps needs to be deployed with options to enable sharing atSign info across apps.

Is there a screen shot showing where we find this?

This sharing atSign option

@sachins-geekyants can you provide guidance on when think this can be deployed?  TY
I think we also need to be mindful this feature is not supported in Android.


Suitable to test 300 Mbit/s download speed ?

All my tests always give under 100 Mbit/s results but using other tools i can get to 280 Mbit/s

I cannot duplicate.  On my 320 Mbit/s connection:
Testing download speed........................................
Download: 189.57 Mbit/s

Depending on time of day and such, I expect these results.
Also see https://github.com/sivel/speedtest-cli#inconsistency

Thank you

I get pretty consistent results over 800Mb/s in a data center on 0.3.2.


bud tool cache clean vs bud tool cache clear

Notion docs show
# Clear the build cache
bud tool cache clear

cli uses clean instead of clear
$ bud version
     bud: 0.1.1
  svelte: 3.47.0
   react: 18.0.0
$ bud tool cache

  Usage:
    cache [command]

  Commands:
    clean  Clear the cache directory

Thanks for the heads up Blake! This has been fixed in docs.


Change facet options sort order if not by count

When counts are suppressed, facet options need to be sorted some other way (related to issue #883 ). Maybe this should be something that is configurable.

This feature has been implemented by #694 PR (original issue: #690) and is documented in here.
It seems like when I implemented this feature I forgot to properly document it in the annotation document, so I did it as part of https://github.com/informatics-isi-edu/ermrestjs/commit/31b765b158aa356258c0f2b582a815994eacd59b commit.
To summarize, in order to remove the count request from the scalar facets we would have to hide the option and also change the sort so it's not based on "number of occurrences". So for example,
{
    "source": [{"outbound": ["s", "fk1_cons"]}, "f1_text"],
    "entity": false,
    "hide_num_occurrences": true,
    "order": [
        {"column": "f1_text", "descending": false}
    ]
}


Provide both, "compact" and "extended" mode for chat

Some people prefer the chat to have more spacing, others prefer the "compact" style. Provide both.

Not just the chat but also the user list.


Android callbacks not working with DCE full

Hi. I'm trying this on NME.
I needed to add @:keep before each function _on...
https://github.com/SempaiGames/extension-facebook/blob/5d531ab512883c94730bd9e386da835148f274fe/extension/facebook/android/FacebookCallbacks.hx#L29
to fix the callbacks when using DCE.
Thanks!!

hmmm, which haxe version are you using?
I wonder if this happens with every haxe version... If this is the case, maybe every extension we have will require the @keep to the callback functions

Hi. I was using the nightly build 858482b from 12/12/16, but I will update and check again. Thanks


Using Records with Primary Constructors instead of Class for Commands…

… / Queries #116 Using Records with Primary Constructors instead of Class for Command
@davidfowl  can you please review my changes.
This fixes open issue  #116 - Using Records with Primary Constructors instead of Class for Command

Thanks @captainsafia  for merging my changes


Suggestion to include better description and package method documentation

Hi,
I am new to using the Kubernetes API and GKE and I just spent a considerable amount of time this morning looking at this package to create a deployment. It was not until I read the documentation here on the API organisation and structure until I realised that I need to use the Kubertnetes API and a node-client to make deployments. It would be a good idea to warn people that they can only do cluster management with this package and perhaps change the description of the repo to something more descriptive than "Deploy, manage, and scale containerized applications on Kubernetes, powered by Google Cloud." perhaps removing the Deploy word altogether.
I also had to dig into the code to view all of the methods that were exposed for GKE engine API. It would be nice to have these documented in the Readme or somewhere more front and foremost.
Good luck!

addressed by https://github.com/googleapis/nodejs-cloud-container/pull/207 once it lands.


Prepared Statements wanted - Creation of execution plans takes too much time if same query is executed many times

My Environment

ArangoDB Version:        3.3.12
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start in Docker
Configuration:               ...
Infrastructure:               own
Operating System:        Ubuntu 18.04
Used Package:              Official docker image

Component, Query & Data
Affected feature:
AQL
Problem:
I have a foxx microservice which does graph traversal. On each iteration it performs a complex but efficient query. The problem is that the same query is executed many times and query parsing and creation and optimization of execution plan happens every time and it slows the traversal significantly.
Statistics from one such traversal:
Query is executed 27 471 times.
Combined time spent in db._query() function calls is 24 126 ms.
Time spend in non-execution phase of query calls is 15 246 ms (sum of all profiling times except of 'executing').
63% of query time is spent on non-execution phases even though resulting execution plans are same every time.
Expected result:
I believe there should be a possibility to cache execution plan so that if I know the query will be executed many times in succession non-execution phases can be cached and skipped. The cache should not be invalidated if bind parameters change (or there should be a parameter to disable this).
var stmt = db._createStatement(...);
stmt.cachePlan(); // new suggested function
stmt.bind(...);
stmt.execute(); // parsing and creation of the plan happens
stmt.bind(...);
stmt.execute(); // only 'executing' phase happens

The query plan cache feature has been merged and will be part of 3.12.4


add memcmp bench and fix some lints

Codecov Report
Base: 80.54% // Head: 80.40% // Decreases project coverage by -0.13% :warning:

Coverage data is based on head (67322b1) compared to base (8e60a90).
Patch coverage: 55.69% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #121      +/-   ##
==========================================
- Coverage   80.54%   80.40%   -0.14%
==========================================
  Files         102      101       -1
  Lines       12257    12288      +31
==========================================
+ Hits         9872     9880       +8
- Misses       2385     2408      +23

Impacted Files
Coverage Δ

xngin-compute/src/arith.rs
76.72% <ø> (ø)

xngin-datatype/src/konst.rs
58.82% <ø> (ø)

xngin-frontend/src/ast.rs
93.13% <ø> (ø)

xngin-frontend/src/parser/ddl.rs
100.00% <ø> (ø)

xngin-frontend/src/parser/dialect.rs
50.00% <ø> (ø)

xngin-frontend/src/parser/expr/tests.rs
100.00% <ø> (ø)

xngin-frontend/src/parser/util.rs
100.00% <ø> (ø)

xngin-index/src/epoch/atomic/inline.rs
48.14% <0.00%> (ø)

xngin-index/src/hot/node_impl.rs
75.96% <0.00%> (ø)

xngin-index/src/hot/partial_key.rs
19.44% <0.00%> (ø)

... and 14 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Descriptor set copies

We currently only support descriptor set updates via writes. Updating via copying is missing at the moment.

Note that copies are now implemented on Vulkan and D3D12.


Fix builtin_embree=no build linking the wrong version of Embree

Fallout of #88783, pretty self-explanatory.
Should fix #90586.

PS: I can confirm this PR fixes the issue on Fedora 39.


DBZ-6089 Expose sequence in postgres parser

https://issues.redhat.com/browse/DBZ-6089

@y5w Applied, thanks


Allow function calls as function arguments

Would resolve #248
Since calls are already allowed in expresions like lhs = 1 + func() it seems reasonable to allow them as call arguments as well (or not allow either) but I'm not 100% sure of the implications in cases of extents. A critical review is appreciated.

bors try

bors try

bors try


Included orphan option with o365group list command

@waldekmastykarz/@VelinGeorgiev
Could you please review this pull request for Issue #959?
I need to fix one additional test case to get 100% coverage. I would like to get feedback/help from you on that.
Thank you.

Coverage decreased (-0.005%) to 99.995% when pulling 3ec2a61c58463c64e396ca1570dec5108b75608b on sprider:orphan-groups into 9c2b66553399a2db863b63352f2f84f662cb7d61 on pnp:dev.

If you look at the coverage report, it seems like there is no test for orphan groups with owners:

@waldekmastykarz/@VelinGeorgiev, Could you please guide me how to write the test case for that line? Any examples?

Have a look at other test cases for this command that return dummy items. The returned items must meet the criteria of the if condition.

Sure, could you please check now?

Will do! Thank you!

@waldekmastykarz
Thank you for your feedback. Looks good to me. Am I doing anything wrong?

Do you have access to an MOD tenant that you could use to see if you can get the same results as I do?

MOD

Do you have access to an MOD tenant that you could use to see if you can get the same results as I do?

@waldekmastykarz Sorry, I do not have. Let me check if I can run against a different tenant to validate but if you can share some credentials I can double confirm.

You should be able to request a demo tenant from demos.microsoft.com

I think we can request demo tenant as a partner but I donot have a partner account. Let me try in a different tenant.

@VelinGeorgiev,
I have fixed the filter condition issue and now it works fine. Could you please review the test cases and let me how to fix the coverage issue? Thank you.

Thanks @sprider! I'll have a look at it shortly. With regards to coverage, it seems like you're missing a test case where a group has no owners:

@waldekmastykarz, Yes I noticed that but not sure how to fix this. Can you help me on that?

The orphan switch doesn't seem to be working as expected, unless I misunderstand something. When I use the --orphan switch, the command lists groups that have 1 or more owners (added logging the number of owners for clarity):
$ o365 graph o365group list --orphan
legal: 3
salesandmarketing: 1
finance: 3
marketingcampaigns: 2
employeeadvocacy: 1
hr: 4
leadershipconnection: 3
newhires: 4
productionline: 3
dg-2000feedback: 4
innovationcorner: 1
quadcopterenthusiasts: 1
LiveAtContoso: 1
BusinessDevelopment: 2
productlaunchevent: 4
Marketing: 3
IT: 3
Engineering: 1
X1050LaunchTeam: 4
VideoProduction: 3
Sales: 3
Retail: 3
ResearchAndDevelopment: 3
ElectronicEvents: 3
Contoso02: 2
Mark8ProjectTeam: 3
NewYork03: 2
Warehouse02: 2
DG-2000ProductTeam: 3
BizDev: 1
id                                    displayName              mailNickname
------------------------------------  -----------------------  ---------------------
5a791941-2cfa-468c-a06f-359de408831b  Sales and Marketing      salesandmarketing
86848b27-6e21-4243-8744-435625dc32a7  Marketing Campaigns      marketingcampaigns
6c8b8a11-8d97-4828-a8ac-b521c0130e0a  HR                       hr
8088cb70-5b82-4d97-a8d4-dcd5979bda36  New Hires                newhires
ad563096-383f-4bd1-a67f-b488450f017d  DG-2000 Feedback         dg-2000feedback
2fb4ef65-ea67-4f3f-b493-8bbf1a8249a9  Quad Copter Enthusiasts  quadcopterenthusiasts
f81f529c-3eae-4f73-888d-e3edc60e9b35  Business Development     BusinessDevelopment
fc461fbb-efa5-4643-a1be-29cb00b9d2b2  Marketing                Marketing
4bd6decc-1f1b-45e4-9c4c-ebfb567647a8  Engineering              Engineering
c0db8f16-592c-415f-a8d5-b4aac9e58910  Video Production         VideoProduction
059266a4-f945-4935-a116-84df317f5ef3  Retail                   Retail
5145eed4-29d6-47de-8e56-2aaa3e7deeb6  Electronic Events        ElectronicEvents
28c893d6-dc3b-4ccc-bd7e-686b8562f377  Mark 8 Project Team      Mark8ProjectTeam
e05b7c3b-ad5c-4b08-9502-0c052a00db33  Warehouse #02            Warehouse02
9d54030b-4313-4cd4-8d09-1f4f509adffe  BizDev                   BizDev

This is fixed.

If you for example look at this test,
https://github.com/pnp/office365-cli/blob/95f9e766a094d71a3f2963dbe257be1b16fd5f9b/src/o365/graph/commands/o365group/o365group-list.spec.ts#L419-L423
it says that it lists groups without owners, but both groups returned by the mocked response, contain owners. So instead, one of the groups in the mocked response should return an empty array for the owners property. Hope this helps.

Thank you @waldekmastykarz. This is fixed. Please test and proceed with merge.

Will do! Thank you!

Hey @sprider, how can I test this command? When I try to remove the last owner, I'm getting an error, that a group must have at least one owner. How did you test it?

Hi waldek,

create a test user with office 365 license in admin center
create a new team and make the user created in first step as a owner
go to admin center and remove the user created in step 1 to make the newly created team as a orphan team
execute the group space list command with orphan parameter.

Hope this helps.

Merged manually. Thank you once again! 👏

Thank you.


refactor: Change embed-grid and embed-chart to redirects

Publishing an alpha with the embed-refactor label so we can test with a local DHC build
This changes embed-grid and embed-chart to just be simple redirects to /iframe/widget. This should reduce our footprint in the install size as this is about half of the size we contribute currently.
BREAKING CHANGE: @deephaven/embed-grid does not handle messages to the iframe for filtering or sorting the grid any more

Changed this to just use vite to build embed-grid and embed-chart still. All it does is copy the index into the build folder. This way there's no issues of people accidentally committing stale build artifacts since the folder was being un-ignored with the first change.
Will publish an alpha and test everything is working properly

Just tested again w/ the latest commit alpha and ./gradlew prepareCompose and the redirect works as expected


Maybe connection leak?

Environment
HikariCP version: 2.7.7
JDK version     : 1.8.0_91
Database        : MySQL
Driver version  : 6.0.6

Sping Boot: 2.0.0.BUILD-SNAPSHOTS / 2.0.0.RC1
Hibernate-core: 5.2.13.Final

Have you searched the CLOSED issues already? How about checking stackoverflow?
Yes, there are lots of answers in stackoverflow & issues relevant to connections or leaks, however, my problem is a bit different. Hikari tried to kill connections that over max-life-time, but mysql doesn't know it. All closed connections are shown as SLEEP in mysql and at the end hikari cannot get any more connection from mysql (or have to wait till mysql free some resources)
mysql screen cut (part of)

logs
hikari.log
Appreciate for your help.

@mogudy Thank you for the logs.
First, I see no signs of leaks, which is good.
Every connection that I checked in the log was created and retired within your 30 minute maxLifetime setting.
Ideally, HikariCP should never encounter a Communications link failure when retiring a connection.  However, it appears that this error is encountered on some connections that are retired within the maxLifetime interval.
This indicates that MySQL (or some network component in-between) is terminating the connection.
I suggest making sure that the MySQL timeouts are explicitly defined.  For example, if HikariCP maxLifetime is set to 1800000 milliseconds (30 minutes) as your log indicates, set the MYSQL timeouts to slightly longer:
[mysqld]
interactive_timeout=1900
wait_timeout=1900

If you cannot change the MySQL timeouts, for example if you do not manage the server yourself, then I would suggest decreasing the HikariCP maxLifetime to 30-90 seconds shorter than the MySQL settings.


Updating FAQ

Changed it to use assertWithMatcher:grey_notNil instead of performAction:grey_tap()

👍

Adding the following to the FAQ

Clarification on best way to check if an element exisits
Resolution for dyld: could not load EarlGrey.framework error.


Raphaelmelancon/athmospheric scattering

Adds an atmospheric scattering lighting effect to the render system. This feature is marked as Beta.

The effect is only displayed with 3d geolocated iModels with DisplayStyleSettings.backgroundMap set to a backgroundMap with [BackgroundMapSettings.globeMode]core/common/src/BackgroundMapSettings.ts) equal to GlobeMode.Ellipsoid. It wouldn't make sense to display it otherwise.
The effect can be turned on/off with ViewFlags.atmosphericScattering.
The effect can be controlled using AtmosphericScattering.Settings. It is also reactive to the sun's position defined at DisplayStyle3dSettings.lights.
The effect work in both camera and orthogonal perspective.
The effect is implement directly into the existing techniques using the addAtmosphericScatteringEffect.
Fixes https://github.com/iTwin/roadmap/issues/3
Issues:

https://github.com/iTwin/itwinjs-core/issues/4471
https://github.com/iTwin/itwinjs-core/issues/4472
https://github.com/iTwin/itwinjs-core/issues/4475

Is it still true that it heavily impacts performance?

@RaphaelMelancon thanks for your work on this. The PR will require some further cleanup around the API and to resolve the identified issues. I will add my comments with the assumption that someone on  the display team will address them. I may have specific questions for you about the implementation.

If both skybox and atmosphere are enabled, the atmosphere takes precedence (always using a black sky) - right? Please document this.

I reorganized the SkySphere shader to only draw the atmosphere if its enabled. All the gradient and texture specific SkySphere code isn't added at all in this case.
I also added comments on Environment and SkyBox to convey that this behavior is intended.


build.gradle is empty??

The build.gradle file in this project is empty.

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


proceedings

Proceedings for ACAT 2017

Proceedings for ACAT 2017

guys, since there are several of us following this repo, let's follow commit messages guidelines: https://chris.beams.io/posts/git-commit/


Stop flight at end of island area

Could you please add a feature that lets players get creative flight while on their island only (and if they leave their island area, they lose flight but don’t take fall damage during the fall to the ground)?
I’d love if there were a permission for this (e.g., simpleskyblock.fly) so that it could be unlocked with a rank. This would be perfect for my server, which is in development.
Is this something you could implement? If so, that’d be wonderful! :)

Thanks!


Add "modified_timestamp" field to clinical_property and clinical_vocabulary

The modified_timestamp field is required to sync specification files with the https://github.com/labsyspharm/ExperimentTracker repository.

to facilitate the BRT update workflow

resolved in https://github.com/labsyspharm/biospecimen-disease-research-terminology/releases/tag/1.1.0


Add support for Azure for US Government to the emulator

Added a few things:

'Runtime' capability to read the channelService out of the .bot file and use it to change how JWT tokens are created, because it's different for US Gov AAD
Added UI to configure/edit a .bot file to add this setting (checkbox)
Added UI to provide a checkbox to turn this on when creating a new .bot file

Pull Request Test Coverage Report for Build 1344

6 of 16 (37.5%)  changed or added relevant lines in 4 files are covered.
53 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 55.021%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/emulator/core/src/facility/botEndpoint.ts
0
2
0.0%

packages/app/client/src/ui/dialogs/botCreationDialog/botCreationDialog.tsx
0
4
0.0%

packages/app/client/src/ui/shell/explorer/endpointExplorer/endpointEditor/endpointEditor.tsx
5
9
55.56%

Files with Coverage Reduction
New Missed Lines
%

packages/emulator/core/lib/facility/botEndpoint.js
21
12.77%

packages/emulator/core/lib/utils/botFrameworkAuthentication.js
32
9.59%

Totals

Change from base Build 1336:
-0.2%

Covered Lines:
4413

Relevant Lines:
7224

💛  - Coveralls


Global installation of Cypress

Hello,
Anyway to handle Cypress installed globally?
I have a prebuilt devcontainer shared across the team where cypress is installed globally, so it is available for any type projects, and I can use that same container in the pipeline.
But here it assumes Cypress is installed locally.
Thanks,

Might be better to ask in the cypress repo https://github.com/cypress-io/cypress.
But maybe this will help?
https://docs.npmjs.com/downloading-and-installing-packages-globally

I don't have any issue with installing Cypress or Cypress in general.
My issue is to be able to use this package, laracasts/cypress, Cypress needs to be installed locally, otherwise it can't be initialized.

Happy to accept a PR. Otherwise, right now, it expects that Cypress is installed locally.


[batch_int] Revamp control methods

The OpenProblems v1 repo has the following control methods:

No integration (Simply return PCA embedding)
Random integration:

Permute features
Permute graph
Permute PCA embedding

Permute per celltype

Permute features within cell types
Permute graph within cell types
Permute embedding within cell types

Permute per batch

Same

Defining negative control methods is easy -- simply permuting the features, graph or PCA embedding should do the trick. To define the positive control, we'll need to take a look at how to define positive controls to target specific metrics.
This was already done in v1 -- we should look for the discussion on how this was tackled in the v1.

Going off what we have on the v1 website, these are all batch integration baselines:

Out of these, we're currently missing:

No integration
Random integration by cell type
Random integration by batch
Random graph by cell type

From what I can see the control methods are not organised in the same hierarchy that you listed here @rcannood, but I think it might be useful to do that, so we don't get confused with the naming. This will require reorganising the v1 code as well as the number of the control methods, unless we come up with a way  to compute a method and process the different outputs (feature, embedding, graph) differently based on 1 outcome, complicating things.


P2P and IPFS APIs

Briefly skim and review when I get the tests up. Also will need a refactor for runner.py and scheduler.py
There's an alternative Kademlia module that has native callback support. Will look into after tests.

Closing for now since the Blockchain Client will be a superset of these utils.


Issue using the sort method

Hi! I'm trying to change the sort order using the sort method but I'm getting an error from the server, this is what I want to do:

ardb.search('transactions')
        .limit(limit)
        .from(owners)
        .max(maxHeight)
        .tags(tags)
        .sort("HEIGHT_ASC")
        .find().then((res) => {
            // Do something
        })
        .catch((error) => {
          // Do something
        });

I'm receiving the next error message (from browser console):
 {"errors":[{"message":"Expected type SortOrder, found \"HEIGHT_ASC\". Did you mean the enum value HEIGHT_ASC or HEIGHT_DESC?","locations":[{"line":34,"column":10}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}]}
Thanks in advance! ArDB rocks!

Hey @luckyr13 , thanks for reporting!
Solved in version 1.0.8 🎉

thank you! works awesome


api: CSDS should report status per resource, not per resource type

The current CSDS protos have the status and client_status and fields at the resource-type level, not the level of individual resources.  They also provide the SotW system version (for LDS, RDS, CDS, and EDS), which is effectively a per-resource-type version.
This representation doesn't seem capable of representing the underlying reality, because the transport protocol allows the client to ACK/NACK a strict subset of resources at a given system version.  Here are some scenarios that are not made clear by this representation:

Server sends RDS response containing resources A and B at system version 1, and client ACKs.  Then resource B is updated, so server sends RDS response containing resource B at system version 2, and client NACKs.  At this point, client has ACKed resource A at system version 1 but has NACKed resource B at system version 2 (so is still using resource B at system version 1).
Client subscribes to LDS resources A and B.  Server sends both resources at version 1, and client ACKs.  Now client subscribes to resource C.  Server sends a new LDS response containing resources A, B, and C, all still at system version 1.  Resource C is invalid, so client NACKs.  At this point, the client is actually using the current version of resources A and B, but it has NACKed C, all at the same version.
Pretty much any scenario using the incremental protocol variants.  Unlike the SotW protocol variants, the incremental variants do not use the system version at all; instead, they report a version for each individual resource, and ACK/NACK is based on that version instead of the system version.

I think CSDS should be changed to report both version and status on a per-resource basis instead of a per-resource-type basis.  When using the SotW API, the per-resource version can actually be the system version, but it should still be reported on a per-resource basis, since it can be different for different resources.
For bonus points, in the case where a resource was NACKed, it might be useful to report both the version that was NACKed and the older version that is actually still being used (if any).
CC @fuqianggao @htuch

Actually, it looks like the version is per-resource, so it's just the status that's the problem.

@fuqianggao WDYT? I seem to remember some confusion over this, e.g. whether we report only the latest acked version vs. earlier ones, but this seems to make sense for finer grained reporting.

From the xDS client's perspective, it seems like it would make sense for the protos to look something like this:
message ResourceStatus {
  // The identity of the resource.
  // type_url may be unset for new-style names, where the type is included in the name.
  string type_url = 1;
  string name = 2;

  // If any version of this resource has been ACKed, these fields indicate the version and
  // contents of the resource.
  string version_acked = 3;
  google.protobuf.Any current_resource = 4;

  // If the most recent version of this resource has been NACKed, these fields indicate
  // the version and error message.
  string version_nacked = 5;
  string nack_error = 6;
}

message CsdsResponse {
  repeated ResourceStatus resource_status = 1;
}

This seems a lot easier to understand than what is in CSDS today.

Yeah, I agree finer grained reporting is useful, and necessary for deltaXds. As long as there is no breaking change, it SGTM.

There is a similar design in config_dump.proto that the listener dump can have active state or error state. In the error state, it stores the received-but-nacked version of listener resource. However, this pattern is not carried over to routes, clusters, and endpoints.

Is adding the UpdateFailureState to other xDS resources an option?
Or do we prefer to simplify the CSDS responses? We could add it as a separate RPC method. It definitely helps to reduce the complexity of the CSDS implementation.

The current CSDS protocol is really bloated, but I guess we shouldn't break backward compatibility.  Let's just make the changes we need in the current API.  I think this includes two things:

We need to add a field for per-resource status.
We need to report two versions on a per-resource basis: the current version actually being used on the client (which corresponds to the resource contents reported by the client) and the most recent version seen by the client.  (Those two versions will be different in the case where the client has NACKed the current version and is still using a previous version.)  Presumably, the existing version field in the API should be one of these (I'm not sure which one, but we should figure it out and document it), but we should add a new field for the other one.

@lidizheng, can you put together a PR proposing these new fields, and we can iterate on that?  Thanks!

The current CSDS protocol is really bloated, but I guess we shouldn't break backward compatibility.  Let's just make the changes we need in the current API.  I think this includes two things:

We need to add a field for per-resource status.
We need to report two versions on a per-resource basis: the current version actually being used on the client (which corresponds to the resource contents reported by the client) and the most recent version seen by the client.  (Those two versions will be different in the case where the client has NACKed the current version and is still using a previous version.)  Presumably, the existing version field in the API should be one of these (I'm not sure which one, but we should figure it out and document it), but we should add a new field for the other one.

@lidizheng, can you put together a PR proposing these new fields, and we can iterate on that?  Thanks!

Sent out PR https://github.com/envoyproxy/envoy/pull/14689 to add an error_state field to all dynamic resources in config dump proto. The missing expressiveness in existing config dump is that if a resource has a newer NACKed version, there isn't a way to tell.
The error_state fields are using type UpdateFailureState, which already existed in config_dump.proto. This PR extends UpdateFailureState with an extra version_info field to record the latest rejected version.
message UpdateFailureState {
  // What the component configuration would have been if the update had succeeded.
  google.protobuf.Any failed_configuration = 1;
  // Time of the latest failed update attempt.
  google.protobuf.Timestamp last_update_attempt = 2;

  // Details about the last failed update attempt.
  string details = 3;

  // This is the version of the rejected resource.
  string version_info = 4;
}

I think the solution is better than offering per-resource synchronization status (not to mention the potential circular dependency issue). For ACKed resource, this field will be empty; for NACKed resource, this field will store the NACKed version with several meta information.

Sent out PR https://github.com/envoyproxy/envoy/pull/14689 to add an error_state field to all dynamic resources in config dump proto. The missing expressiveness in existing config dump is that if a resource has a newer NACKed version, there isn't a way to tell.
The error_state fields are using type UpdateFailureState, which already existed in config_dump.proto. This PR extends UpdateFailureState with an extra version_info field to record the latest rejected version.
message UpdateFailureState {
  // What the component configuration would have been if the update had succeeded.
  google.protobuf.Any failed_configuration = 1;
  // Time of the latest failed update attempt.
  google.protobuf.Timestamp last_update_attempt = 2;

  // Details about the last failed update attempt.
  string details = 3;

  // This is the version of the rejected resource.
  string version_info = 4;
}

I think the solution is better than offering per-resource synchronization status (not to mention the potential circular dependency issue). For ACKed resource, this field will be empty; for NACKed resource, this field will store the NACKed version with several meta information.


Add a tools used page under /contributing

Context
The website currently gives little insight into what we are using to provide the framework and all related tools.
Solution
Provide a list of technologies/frameworks used with a short description where they are used. There should be a link back to the respective repositories.

reminder: Description tool logo name

The big ones are:

typescript: basis language used
react: documentation website
svelte: history website
fastify: history microservice
docker: prebuild
eslint: every project part
chai: every project part
mocha: every project part
cypress: websites
stylelint: websites

find links for the above via their github

new tool:

markmap-render: mindmap

new tools:

vue: desktop
elektron: desktop
express: website-builder


Feat - input mode

Zinc is a very helpful plugin for extending the capabilities of DAWs and accomplishing things they don't always let you do by default. Similar to its goal of providing additional audio outputs to any plugin host, providing additional audio inputs would also aid in performing tasks that DAWs sometimes make hard.
I understand that if Zinc were to provide a way of receiving audio from JACK, it couldn't run in hard Zinc mode. This is fine, as it would still enable more levels "DAW hacking" than are currently possible. Also, I think in most cases where this is needed, it is more important to have the input from JACK to begin with than it is to have it synced with the host audio thread.

this is outside the scope of the project, and should be something handled somewhere else.
I have no intentions on working on this, as a way to set a nice and simple scope for this particular project.
sorry

Maybe some day we'll see Cobalt for inputs :D


Audio for Cross company hackathon

http://owaspsummit.org/Working-Sessions/Security-Crowdsourcing/Cross-Company-Hackathons.html
Cross-Company-hackathons.mp3.zip
Hi @Ambg05 can you try to make sense of this audio and convert it into a Working Session description?

Hi, I just created a PR for this file #593.
Let me know if you're happy with what I did.  The audio quality was fine, it just takes me a little longer to transcribe & check that I've got everything. I'll get to the other files tomorrow or on Monday.

It looked great :)
Thanks

@Ambg05 can you change it a little bit to make it clear that this is supposed to happen between companies.
I believe it shows in the title, but it is not clear in the text

Hi @DinisCruz
Just to clarify my own understanding of a cross company hackathon: do you mean that one company that has new products etc. will invite other companies to try and hack the new products? So it is an inter-company hackathon rather than an intra-company hackathon?
Thanks.

yes it is a multi-company agreement where they organise events where participants (from security team and developers) from both companies (two or more)
The idea of doing this for new products is that it is more realistic with the flow of development in companies, and provides a new fresh target for tests
@ante-gulam can you share some of you views? (as you can see by this thread you can do it with audio)


Fix misconfigured request path check in interceptor

Closes #454

Can you please finish this PR with the following changes:

Same apiBase change should also happen at line 47
With this change, it seems like get apiPath() is no longer necessary. Please investigate and remove if needed


⚠ ClamAV has degraded performance

In 0330eed, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 89 ms

Resolved: ClamAV performance has improved in 3584873 after 18 minutes.


Cannot reference Xamarin.Auth and Microsoft.Azure.Mobile.Client in the same Xamarin.iOS Project

With the latest version (4.0.0) of the Azure Mobile SDK, I can no longer build my project. I'm also referencing Xamarin.Auth, and here's the error that occurs when I try to build for a physical device:
Error MT4116: Could not register the assembly 'Xamarin.Auth': error MT4118: Cannot register two managed types ('Xamarin.Controls.ProgressLabel, Xamarin.Auth' and 'Xamarin.Controls.ProgressLabel, Microsoft.Azure.Mobile.Client') with the same native name ('Xamarin_Controls_ProgressLabel'). (MT4116)

Hi @mjo151!
Thanks for reporting. Actually, on my test app it is just a warning, but I see that this should be fixed. I created PR to resolve this issue.

Thanks!

@MatkovIvan Is a pre release / release version available? When I only use the AccountStore from Xamarin.Auth, can I use that from the Azure MobileService Client and kick the Xamarin.Auth package out? Wha t can I do instead, revert to v.3.1.0? Don't know if I would not run in other issues in XF utilizing a .NET Standard,Version=1.4 library......

Hi @ericbrunner. We plan to nuget release with these changes at this week. We include Xamarin.Auth as internal, so if you need anything from it you should use it directly.

@MatkovIvan Sounds good. Thank you for your reply.


Using assert_fails() from a timer causes hit-enter prompt

Steps to reproduce

Run vim --clean
Run :call timer_start(0, {-> assert_fails('call', 'E471:')})
A hit-enter prompt appears

Expected behaviour
No hit-enter prompt
Version of Vim
9.0.813
Environment
Operating system: Arch Linux
Terminal: kitty
Value of $TERM: xterm-kitty
Shell: fish
Logs and stack traces
No response

Maybe assert_fails() needs to set no_wait_return?


Change Sell Method to check for negative amounts

The Sell methods all call the Order method, which in turn call the MarketOrder method.  The MarketOrder method creates a new MarketOrder type which derives from the Order type.  If the Quantity property is > 0 the OrderDirection is set to Buy and if the Quantity < 0, the OrderDirection is set to Sell.
So in an algo, when I called Sell(_symbol, 100m), QuantConnect executed a Market buy order.  This method name seems counter intuitive to me.  When an algorithm writer calls the Sell method, (s)he would expect the algo to try and sell the security.
I believe the 4 Sell methods should check the sign of the quantity and convert it to negative, so that the method will always try to execute a Sell.  The logic should be

        public int Sell(string symbol, decimal quantity)
        {
            var qty = quantity;
            if (quantity > 0)
            {
                 qty = qty * -1;
            }
            return Order(symbol, qty);
        }

If all agree, I would be happy to make this change and will do a fork, pull for the issue.

Thanks @bizcad, good suggestion, please issue a pull request with the fix. You might want to use Math.Abs instead to reduce if branching :)


🔧 Build fail in case frame processor is enabled how ever I need to use frame processor.

How were you trying to build the app?
npx react-native run android
Build fail
and when I run example app in package folder I get this build error
info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor
FAILURE: Build failed with an exception.

What went wrong:
java.io.UncheckedIOException: Could not move temporary workspace (C:\Users\dufit\Desktop\Development\Projects\react-native-vision-camera\package\example\android.gradle\8.6\dependencies-accessors\423f0288fa7dffe069445ffa4b72952b4629a15a-03ab3ad9-4e6c-4a7f-a4b5-27245af1b5a2) to immutable location (C:\Users\dufit\Desktop\Development\Projects\react-native-vision-camera\package\example\android.gradle\8.6\dependencies-accessors\423f0288fa7dffe069445ffa4b72952b4629a15a)

Could not move temporary workspace (C:\Users\dufit\Desktop\Development\Projects\react-native-vision-camera\package\example\android.gradle\8.6\dependencies-accessors\423f0288fa7dffe069445ffa4b72952b4629a15a-03ab3ad9-4e6c-4a7f-a4b5-27245af1b5a2) to immutable location (C:\Users\dufit\Desktop\Development\Projects\react-native-vision-camera\package\example\android.gradle\8.6\dependencies-accessors\423f0288fa7dffe069445ffa4b72952b4629a15a)

Full build logs
> Task :react-native-vision-camera:configureCMakeDebug[arm64-v8a]
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...

> Task :react-native-vision-camera:buildCMakeDebug[arm64-v8a]
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: VisionCamera: Frame Processors: ON!
C/C++: VisionCamera: Linking react-native-worklets...
C/C++: ninja: error: manifest 'build.ninja' still dirty after 100 tries

> Task :react-native-vision-camera:buildCMakeDebug[arm64-v8a] FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
550 actionable tasks: 38 executed, 512 up-to-date

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vision-camera:buildCMakeDebug[arm64-v8a]'.

Project dependencies
"dependencies": {
    "@react-native-async-storage/async-storage": "^1.23.1",
    "@react-native-picker/picker": "^2.7.6",
    "@react-navigation/bottom-tabs": "^6.5.11",
    "@react-navigation/native": "^6.1.9",
    "@react-navigation/native-stack": "^6.9.18",
    "@supabase/ssr": "^0.3.0",
    "@supabase/supabase-js": "^2.39.3",
    "buffer": "^4.9.2",
    "events": "^3.3.0",
    "expo-file-system": "^16.0.9",
    "expo-gl": "^13.6.0",
    "expo-gl-cpp": "^11.4.0",
    "i": "^0.3.7",
    "npm": "^10.5.2",
    "patch-package": "^8.0.0",
    "postinstall-postinstall": "^2.1.0",
    "process": "^0.11.10",
    "react": "18.2.0",
    "react-native": "0.73.1",
    "react-native-background-fetch": "^4.2.5",
    "react-native-canvas": "^0.1.40",
    "react-native-crypto": "^2.2.0",
    "react-native-device-info": "^11.1.0",
    "react-native-fast-image": "^8.6.3",
    "react-native-fast-tflite": "^1.2.0",
    "react-native-get-random-values": "^1.11.0",
    "react-native-international-phone-number": "^0.7.6",
    "react-native-intersection-observer": "^0.2.0",
    "react-native-linear-gradient": "^2.8.3",
    "react-native-loader-kit": "^2.0.8",
    "react-native-modal": "^13.0.1",
    "react-native-navigation-bar-color": "^2.0.2",
    "react-native-permissions": "^4.1.4",
    "react-native-push-notification": "^8.1.1",
    "react-native-qrcode-svg": "^6.3.1",
    "react-native-randombytes": "^3.6.1",
    "react-native-reanimated": "^3.12.0",
    "react-native-safe-area-context": "^4.9.0",
    "react-native-screens": "^3.30.1",
    "react-native-sound": "^0.11.2",
    "react-native-splash-screen": "^3.0.6",
    "react-native-svg": "^15.4.0",
    "react-native-url-polyfill": "^2.0.0",
    "react-native-vector-icons": "^10.1.0",
    "react-native-view-shot": "^3.8.0",
    "react-native-vision-camera": "^4.3.2",
    "react-native-walkthrough-tooltip": "^1.6.0",
    "react-native-webrtc": "^118.0.0",
    "react-native-webview": "^13.10.3",
    "react-native-wheely": "^0.6.0",
    "react-native-worklets-core": "^1.3.3",
    "react-router-dom": "^6.21.3",
    "react-router-native": "^6.22.0",
    "readable-stream": "^1.0.33",
    "simple-peer": "^9.11.1",
    "socket.io-client": "^4.7.3",
    "stream-browserify": "^1.0.0",
    "text-encoding": "^0.7.0",
    "toastify-react-native": "^5.0.0",
    "util": "^0.10.4",
    "vision-camera-resize-plugin": "^3.1.0",
    "vm-browserify": "^0.0.4",
    "zustand": "^4.5.4"
  },

VisionCamera Version
^4.3.2
Target platforms
Android
Operating system
Windows
Can you build the VisionCamera Example app?
No, I cannot build the Example app either
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Clean your Gradle cache and try again.


Hot reload does not work with complex configuration vim

Env:

Ubuntu 24.04 LTS
dora-cli 0.3.4

When editing a source file using the vim editor, the following events will occur:
>>> recv an event: Ok(Event { kind: Modify(Name(From)), paths: ["/home/rayylee/github/code-test/rust/dora-test/python-operator-dataflow/plot.py"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None })
>>> recv an event: Ok(Event { kind: Modify(Metadata(Any)), paths: ["/home/rayylee/github/code-test/rust/dora-test/python-operator-dataflow/plot.py"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None })
>>> recv an event: Ok(Event { kind: Remove(File), paths: ["/home/rayylee/github/code-test/rust/dora-test/python-operator-dataflow/plot.py"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None })

The ModifyKind::Data event will not occur.

Thanks for reporting!
Apparently vim is replacing the file with a new one when saving it, instead of modifying it. See https://github.com/notify-rs/notify/issues/247 and https://github.com/notify-rs/notify/issues/113. So it looks like we have to watch the directory instead.

I opened a PR to hopefully fix this issue: https://github.com/dora-rs/dora/pull/532. Could you please try whether it works for you? Thanks!


Presto template processor functions are not available in Trino

Hi,
We are in the process of migrating from Presto to Trino and noticed template processor functions don't work with Trino.  We have a lot of datasets using  first_latest_partition function.
How to reproduce the bug
Below is working for presto driver, however, it doesn't work for Trino.
SELECT *
FROM foo
WHERE ds='{{ presto.first_latest_partition('foo') }}'

Expected results
Template processor function should also work for Trino.
Actual results
When using Trino driver, an error is thrown because there are not template processor functions for Trino.
https://github.com/apache/superset/blob/master/superset/jinja_context.py#L553
Screenshots
Environment

superset version: 1.3.0

I looked at master code, it seems like this will also be an issue for 1.4.0
Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

@pashkash no, the workaround is to use
max(ds)

but I believe that will scan all partitions.

This is at risk of being closed as stale, but meanwhile, hopefully @dosu-bot can give us a little added insight.


wasm-pack npm module fails with build but not dev

A sample repository with this error is available at: https://github.com/hschimke/rxing-sveltekit
When testing, everything works correctly and the program works as expected (npm run dev).
When building for production, however, I receive the following output:
><EMAIL_ADDRESS>build
> vite build

vite v4.1.4 building SSR bundle for production...
transforming (55) node_modules/esm-env/prod-ssr.js"BarcodeResult" is imported from external module "rxing-wasm" but never used in "src/lib/BarcodeFormatSelect.svelte", "src/routes/encode/+page.svelte", "src/lib/BarcodeResultDisplay.svelte" and "src/routes/decode/+page.svelte".
✓ 60 modules transformed.
5:50:13 PM [vite-plugin-svelte] ssr compile done.
package     	files	 time	   avg
rxing-online	    9	0.51s	56.2ms

vite v4.1.4 building for production...
✓ 58 modules transformed.
5:50:20 PM [vite-plugin-svelte] dom compile done.
package     	files	 time	  avg
rxing-online	    9	1.11s	0.12s
.svelte-kit/output/client/_app/version.json                                        0.03 kB
.svelte-kit/output/client/vite-manifest.json                                       5.00 kB
.svelte-kit/output/client/_app/immutable/assets/rxing_wasm_bg.5d0754f0.wasm    2,134.16 kB
.svelte-kit/output/client/_app/immutable/assets/_page.5db5c4c8.css                 0.20 kB │ gzip: 0.14 kB
.svelte-kit/output/client/_app/immutable/assets/_layout.17415654.css               0.21 kB │ gzip: 0.14 kB
.svelte-kit/output/client/_app/immutable/assets/_page.9695604d.css                 0.71 kB │ gzip: 0.29 kB
.svelte-kit/output/client/_app/immutable/entry/_layout.ts.984db11e.js              0.07 kB │ gzip: 0.09 kB
.svelte-kit/output/client/_app/immutable/chunks/2.872816d4.js                      0.08 kB │ gzip: 0.10 kB
.svelte-kit/output/client/_app/immutable/chunks/1.4d3c8aca.js                      0.08 kB │ gzip: 0.10 kB
.svelte-kit/output/client/_app/immutable/chunks/_layout.da46b06b.js                0.14 kB │ gzip: 0.14 kB
.svelte-kit/output/client/_app/immutable/chunks/0.f477c1b7.js                      0.14 kB │ gzip: 0.13 kB
.svelte-kit/output/client/_app/immutable/chunks/3.4247acb8.js                      0.18 kB │ gzip: 0.17 kB
.svelte-kit/output/client/_app/immutable/chunks/4.072bf200.js                      0.18 kB │ gzip: 0.17 kB
.svelte-kit/output/client/_app/immutable/entry/error.svelte.b81d9fff.js            0.93 kB │ gzip: 0.55 kB
.svelte-kit/output/client/_app/immutable/entry/_layout.svelte.bb542569.js          1.30 kB │ gzip: 0.71 kB
.svelte-kit/output/client/_app/immutable/entry/_page.svelte.a5469000.js            1.60 kB │ gzip: 0.78 kB
.svelte-kit/output/client/_app/immutable/chunks/singletons.82538ad9.js             2.57 kB │ gzip: 1.35 kB
.svelte-kit/output/client/_app/immutable/entry/encode-page.svelte.c9960a24.js      3.73 kB │ gzip: 1.77 kB
.svelte-kit/output/client/_app/immutable/chunks/rxing_wasm_bg.b7cb131b.js          6.20 kB │ gzip: 2.57 kB
.svelte-kit/output/client/_app/immutable/entry/app.5813da2d.js                     6.22 kB │ gzip: 2.43 kB
.svelte-kit/output/client/_app/immutable/chunks/index.57a8573d.js                  7.62 kB │ gzip: 3.06 kB
.svelte-kit/output/client/_app/immutable/entry/decode-page.svelte.df8ae59f.js      8.70 kB │ gzip: 3.26 kB
.svelte-kit/output/client/_app/immutable/entry/start.fa90f705.js                  22.04 kB │ gzip: 8.91 kB
Error [ERR_MODULE_NOT_FOUND]: Cannot find package '/home/henry/sandbox/barcode_web/rxing-online/node_modules/rxing-wasm/' imported from /home/henry/sandbox/barcode_web/rxing-online/.svelte-kit/output/server/entries/pages/decode/_page.svelte.js
    at new NodeError (node:internal/errors:399:5)
    at legacyMainResolve (node:internal/modules/esm/resolve:202:9)
    at packageResolve (node:internal/modules/esm/resolve:781:14)
    at moduleResolve (node:internal/modules/esm/resolve:843:20)
    at defaultResolve (node:internal/modules/esm/resolve:1058:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:416:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
    at link (node:internal/modules/esm/module_job:75:36)
file:///home/henry/sandbox/barcode_web/rxing-online/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:53
					throw new Error(format(details));
					      ^

Error: 500 /decode
    at file:///home/henry/sandbox/barcode_web/rxing-online/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:53:12
    at save (file:///home/henry/sandbox/barcode_web/rxing-online/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:355:4)
    at visit (file:///home/henry/sandbox/barcode_web/rxing-online/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:204:3)

Node.js v19.6.1
[vite-plugin-sveltekit-compile] Failed with code 1
error during build:
Error: Failed with code 1
    at ChildProcess.<anonymous> (file:///home/henry/sandbox/barcode_web/rxing-online/node_modules/@sveltejs/kit/src/utils/fork.js:68:13)
    at ChildProcess.emit (node:events:512:28)
    at ChildProcess._handle.onexit (node:internal/child_process:293:12)

linux:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"

npm:
npm --version
9.4.0

node:
node --version
v19.6.1

It has nothing to do with this plugin. Your code is importing the wasm-pack package from Node.js (not from web, not in Vite's bundle, directly from your Node.js) but the package generated by wasm-pack has no "main" field, which is required by Node.js.
Adding "main" and "type" fields resolves this error:
{
  // ...
  "module": "rxing_wasm.js",
  "main": "rxing_wasm.js",
  "type": "module",
  // ...
}

You also need --experimental-wasm-modules for importing WASM file directly from Node.js: export NODE_OPTIONS=--experimental-wasm-modules.

Thanks for taking a look, much appreciated!

Additionally, this plugin should works with SSR and SvelteKit (the server bundle should work). I don't use SvelteKit but when debugging with others' SvelteKit project I didn't find it's running your code directly in Node.js. Maybe you should check your SvelteKit configuration, which I can't help...

This is likely because I have mine configured to disable SSR. The intended target of the app is an Azure Static Web Site. The expected behavior is bundling and loading in the browser from the _app/immutable/assets path.
I had hoped that the update to wasm-pack and wasm-bindgen would resolve some of my issues but I'm still blocked on their sideEffects bug (and reading through other bug reports it looks like adding "main" and "type" aren't in the next build either).

But, thanks to your help, I created a properly configured package.json and posted a new version of the rxing-wasm module. Everything seems to work correctly now, thank you again for your help!


Battery works better with last update but there is still some problems...

Hello,
first of all thanks for your hard work!
I've already tested your latest version of EFI and battery works lot better, it recognize when it is plugged in or not etc...
But my battery settings still shows what my battery need assistance and it seems I did more than 400 cycles of charges. That's impossible, of course. And I think there is a mistake with battery capacity.
I attach a screenshot of coconut battery

Hope it helps, regards

Can't do more at the moment as EC is not fully working

Hello, I tried to update OpenCore files, drivers, config and kexts with OcAuxiliaryTools (latest version for OpenCore 0.7.8) but then the touchpad doesn't work anymore. Any tip/help?
Thanks
Regards

Have you ever changed VoodooPS2 kext?

no, I've just updated your working Efi folder with OcAuxiliaryTools...I don't have so many knowledge to change VoodooPS2 kext...I attach the image of updates found from OcAuxiliaryTools. Maybe I have an idea: is is possible that when I click on "check for updates" it downloads all kexts from the net again and vanish your changes? It shouldn't but it is the only thing that for me has a sense...or it change the config in an inappropriate way...I don't know
Thanks for your help

update: I was able to upgrade to 0.7.8 deselecting everything on the left side a part the ones with red squares. So now everything should be updated and it seems that everything works well


Add ability in site configs to remove 'view query' buttons

As it does not work properly on forks:
Gives this link: https://cloud.hasura.io/public/graphiql?endpoint=undefined&query-ect ect

Added: displayQueries: true to site config


spotlight: PMID: 30602572

Association of mitochondria with microtubules inhibits mitochondrial fission.
Published in  J. Bil. Chem.
http://www.jbc.org/content/294/10/3385
(not quite ready to go live)

(not quite ready to go live)

Is it ready now?  There are annotations on the main site: https://www.pombase.org/reference/PMID:30602572
I've added the images to Git so adding the Spotlight will be quick.

oh yes please!

Done!


To lazy to show a exemple usage like capawesome?

To lazy to show a exemple usage like capawesome?
import { FileOpener } from '@capawesome-team/capacitor-file-opener';

const open = async () => {
  await FileOpener.openFile({
    path: 'file:///var/mobile/Containers/Data/Application/22A433FD-D82D-4989-8BE6-9FC49DEA20BB/Images/test.png'
  });
};

@onigetoc this is an open source project and I put my personal unpaid time for it, so I have limited resources for it. Your PR will be welcomed.

@onigetoc I have added Usage section to README


TypeError: Right-hand side of 'instanceof' is not an object

Hi,
I am using jsdom-global when running tests and I am receiving the following error when using ResizeObserver:
TypeError: Right-hand side of 'instanceof' is not an object

I tracked down the problem to this line in the isSVGGraphicsElement function:
...
return target => (
    target instanceof getWindowOf(target).SVGElement &&
    typeof target.getBBox === 'function'
);

It seems that SVGElement is possibly not defined on the window. Would adding a check to see if SVGElement is defined interfere with the functionality here in any way?
To be honest I am not quite sure if this is an issue with the polyfill or rather with me using jsdom. I would be happy to have some guidance here and contribute if I can.
Thanks!

As the function is only called in this check
https://github.com/que-etc/resize-observer-polyfill/blob/3e689695e0fff99b15f3cbaf833c3c3ede6d33b9/src/utils/geometry.js#L190-L194
It seems to be "future proof" (past proof? :) to check for SVGElement and return false if this is not available. So the code for HTML handling will be called which seems a good solution.


Roles/Permissions are lost when reload the page

Hi,
I retrieved the role/permissions when user login, but found if the user reload the page, the values in RoleStore and PermissionStore are lost, the page became blank.
Is there any way to fix it?
Thanks

Do you have some example about maintain the current state ?


missing annotation on rpc25 page

I can't see why?
/GO="aspect=P; term=transcription initiation from RNA polymerase III promoter; GOid=GO:0006384; evidence=ISO; db_xref=GO_REF:0000024; with=SGD:S000001627; date=20170608"

ignore,  I now remember I cam across it last night for a totally different reason
(the term slimmer wasn't recognising it because it was using a secondary GO ID, so I fixed it...should be sorted tomorrow)


Packed Update

About the PR
Nothing drastic just a collection of fixes that were requested awhile back and some up to date content changes:

Added a table and windoor between hydroponics and kitchen as well as between kitchen and bar so chef can serve people directly.
Added windoor to bar directly so they no longer have to climb over or go through kitchen.
Added 4x drones to engineering.
Extended LV cables at arrivals so they fully reach the exterior doors.
Changed airlocks at arrivals so they're all now docks.
Removed that obnoctious wall thing at arrivals that stopped shuttles getting in close to dock.
Generally redesigned window layout at arrivals (see screenshot) to reduce the likelihood of it being spaced. Also added caution decals to the plating in the airlocks.
Fixed the SMES wiring so that the substation in engineering is now on the distribtion side rather than the generation side.
Added a new substation in atmos to reduce the load on the engineering substation.
Added spawn for QM.
Added spawns for salvage and changed the airlocks in the mining room to all be salvage locked now.
Medbay now has shutters to stop people climbing over tables.
Added box of bodybags to morgue.
Added correct atmos fix markers to the nitrogen and oxygen atmos tanks so they roundstart with gas rather than vacuum now.  Bar and kitchen have windoors now so they have better access.
tweak: Medbay has shutters to stop the greytide. Engineering now have drones. Salvage have their own room and spawns now.
tweak: Arrivals has been tweaked to have shuttle docks! And more resistance to being spaced.

need @TimrodDX approval

Here is my review. The only changes I do not approve of are the ones to arrivals and some of the ones to the kitchen and bar.
The arrivals change I disapprove of because the whole "grass inside glass" thing is a hallmark of the post-Metastation mapping era, and Packed is from well before that was ever a thing. I get that arrivals being spaced is an issue, but that's an issue that will largely be resolved once the arrivals shuttle is in place.
The bar changes I also disapprove of because that's not how they are on the original map. The way the kitchen is laid out was a quick-fix to a couple of early issues that arose because there was no windoor keyed to both kitchen and bar access. What you could do (and what I would gladly accept) is adding that windoor and changing the area to look like the original map:

The table between the kitchen and botany can stay though. That's perfectly fine.

Here is my review. The only changes I do not approve of are the ones to arrivals and some of the ones to the kitchen and bar.
The arrivals change I disapprove of because the whole "grass inside glass" thing is a hallmark of the post-Metastation mapping era, and Packed is from well before that was ever a thing. I get that arrivals being spaced is an issue, but that's an issue that will largely be resolved once the arrivals shuttle is in place.
The bar changes I also disapprove of because that's not how they are on the original map. The way the kitchen is laid out was a quick-fix to a couple of early issues that arose because there was no windoor keyed to both kitchen and bar access. What you could do (and what I would gladly accept) is adding that windoor and changing the area to look like the original map:

The table between the kitchen and botany can stay though. That's perfectly fine.

Largely reverted arrivals but had no image to work from. Converted it to more reinforced walls and a double window in the center. Let me know if it's still too much and I'll load up a clean copy to copy off.
Also removed the changes to the kitchen area and followed your screenshot. Added the kitchen/hydro and kitchen/bar windoor types so that it's all workable.
In addition to these changes since my glass doors PR got merged I changed the HoP, CMO and RD doors to glass variants since the whole front of their offices is glass anyway and changed most of the external doors where there's a dock, including the docks to glass variants so people have some chance of docking etc. See screenshots above.


Cannot find module error when module is available, hides whatever the true error is

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Linux Arch
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

1.0.0-beta.30
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

npm install --save angular2-websocket-service

Then in a file in my project added:
import { WebSocketService } from 'angular2-websocket-service'

When I save the file I get:
ERROR in /path/removed/for/privacy/app.module.ts (6,34): Cannot find module 'angular2-websocket-service'.)

I don't understand why webpack can't find a module I just installed. If there's some other error preventing webpack from finding the module then it's being unhelpfully hidden.
The log given by the failure.

Normally this include a stack trace and some more information.

Covered above

Missing "typings" entry in package.json caused this.


Suggest changing Figure 11 y-axis label and legend to just 'Estimated age-1 fish'

And not say 'recruitment', as elsewhere recruitment is used for age-0 recruitment (e.g. as specified Figs 15 and 16).
Presumably when just 'recruitment' is used it refers to age-0. i.e. recruitment residual in 2015 refers to new fish in 2015. I can fix, just double checking first...

Good idea.
Done in commit 201c8de.


update google analytics

Fixes
Fixes #1027  by @annatuma
Description
Update the google analytics code. If ccsearch. or search. as subdomains track to the GA production ID UA-2010376-33 else use UA-2010376-36
Technical details
Tests

Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

One note—it appears that the ccsearch. subdomain will be redirected to the primary search. subdomain. The current code still works fine, just an fyi: https://github.com/creativecommons/tech-support/issues/563


FingerFlex dataset colab-notebook

Problem description
EDIT - for clarification, the FingerFlex notebook was accessed from here.
In the notebook course-content/projects/ECoG/load_ECoG_fingerflex.ipynb, running the cell titled 'Data Loading' results in an error:
import numpy as np

alldat = np.load(fname, allow_pickle=True)['dat']

# Select just one of the recordings here. This is subject 1, block 1.
dat = alldat[0]

print(dat.keys())
#  AttributeError: 'numpy.ndarray' object has no attribute 'keys'

The array dat is an ndarray, rather than a dictionary (or a NumPy records array).
Proposed bug-fix
In accordance with the comment in the code - a possible solution would be the to change the line dat = alldat[0] into dat = alldat[0][0] so dat would be assigned the dictionary that stores the data from the first block of the first subject.
Thanks!

Good catch, thanks. https://github.com/NeuromatchAcademy/course-content/pull/830 fixed it.


Fixed problem with segmentation fault

Fixed issue with segmentation fault:
https://curl.haxx.se/libcurl/c/CURLINFO_RESPONSE_CODE.html

Fixing issue:
https://github.com/nlohmann/crow/issues/42

Pull Request Test Coverage Report for Build 318

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.617%

Totals

Change from base Build 314:
0.0%

Covered Lines:
44

Relevant Lines:
47

💛  - Coveralls


Added Cybersec professionals

Hello Mesrenyame,
I have added myself and professionals I know to the list. Thank you for doing this!
Sincerely,
Dickson

Hey @dagbemazi, kindly check the attached comment here:
https://github.com/mesrenyamedogbe/made-in-ghana/pull/5/files#r1152749853


torrentfreak.com

::: /etc/pihole/list.41.hosts.ubuntu101.co.za.domains (1 results)
<IP_ADDRESS> torrentfreak.com

Thanks @xxcriticxx seems our false positives are getting less and less slowly but surely.