MCLog not playing nice with CocoaLumberjack

I noticed that log statements were not be output to my console a short time after starting my run. In my app delegate's didFinishLaunching I call:
[DDLog addLogger:[DDASLLogger sharedInstance]];
[DDLog addLogger:[DDTTYLogger sharedInstance]];

I see a few log statements appear, but then they stop. Perhaps MCLog is changing up the TTY logger at some point after launch? I haven't looked into the source code for either project.

same problem here..

Yes, it's better to support CocoaLumberjack. But I'm busy these months... I'll add this feature to my TO-DO list.

Also miss the log text color (XcodeColors plugin) randomly.


TST upgrade mypy

I've upgraded mypy to latest version. Most changes are related to None handling. Probably we can drop custom attrs decorator now, but I haven't done it here.

Test failures are addressed here: https://github.com/TeamHG-Memex/eli5/pull/284


Optimize darwin different from x86_64-linux-gnu

curve_fit throwing OptimizeWarning in Linux but not in OsX
Reproducing code example:

Example to reproduce
from scipy.optimize import curve_fit
from numpy import exp

x = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59]
y = [399, 399, 494, 689, 964, 1302, 3349, 3341, 4651, 5461, 6736, 10532, 12722, 15677, 18483, 20677, 23139, 24881, 26965, 28532, 29659, 29612, 43437, 48175, 49030, 49847, 50338, 50633, 49665, 48510, 48637, 46439, 46395, 45044, 43252, 41603, 39572, 36829, 34617, 32610, 30366, 28174, 25904, 23972, 22628, 21207, 19486, 18247, 16993, 15593, 14407, 13171, 11755, 10421, 9557, 8685, 7751, 6988, 6285, 5715]

def asymmetric_gauss_func(x, a1, b1, c1, a2, b2, c2):
    d1 = - ((x - b1) ** 2)
    d2 = - ((x - b2) ** 2)
    f1 = a1 * exp( d1 / (c1 ** 2) )
    f2 = a2 * exp( d2 / (c2 ** 2) )
    return f1 + f2

popt, pcov = curve_fit(asymmetric_gauss_func, x, y)

print("popt: {}".format(popt))
print("pcov: {}".format(pcov))

On OsX (correct result):

popt: [ 3.32157119e+04  2.62584285e+01 -1.17428460e+01  2.23066311e+04
  3.69562236e+01 -1.85921830e+01]
pcov: [[ 6.93534299e+07  1.59895838e+03 -8.81310056e+03 -5.04020896e+07
   3.03792117e+04  8.12001957e+03]
 [ 1.59895838e+03  2.54754760e-01 -2.57971673e-01 -1.69508933e+03
   5.94315393e-01 -2.68080675e-01]
 [-8.81310056e+03 -2.57971673e-01  1.23398553e+00  6.65665964e+03
  -3.86198991e+00 -9.63561077e-01]
 [-5.04020896e+07 -1.69508933e+03  6.65665964e+03  3.83016483e+07
  -2.18597988e+04 -4.69705666e+03]
 [ 3.03792117e+04  5.94315393e-01 -3.86198991e+00 -2.18597988e+04
   1.34766839e+01  3.77199019e+00]
 [ 8.12001957e+03 -2.68080675e-01 -9.63561077e-01 -4.69705666e+03
   3.77199019e+00  2.17827288e+00]]

On Linux (OptimizeWarning):
.../python3.7/site-packages/scipy/optimize/minpack.py:808: OptimizeWarning: Covariance of the parameters could not be estimated
  category=OptimizeWarning)
popt: [ 1.39457182e+04 -1.21115587e+02 -1.57952383e+01  4.85869110e+04
  2.99980106e+01 -1.61902865e+01]
pcov: [[inf inf inf inf inf inf]
 [inf inf inf inf inf inf]
 [inf inf inf inf inf inf]
 [inf inf inf inf inf inf]
 [inf inf inf inf inf inf]
 [inf inf inf inf inf inf]]

Scipy/Numpy/Python version information:
On OsX
>>> import sys, scipy, numpy; print("\n".join([scipy.__version__, numpy.__version__, str(sys.version_info)]))
1.4.1
1.18.1
sys.version_info(major=3, minor=7, micro=6, releaselevel='final', serial=0)

On Linux
>>> import sys, scipy, numpy; print("\n".join([scipy.__version__, numpy.__version__, str(sys.version_info)]))
1.4.1
1.18.1
sys.version_info(major=3, minor=7, micro=7, releaselevel='final', serial=0)

On trying with Python 3.10 and numpy 1.23.2, scipy-1.9.0 the Linux and macOS versions (both aarch64) gave fairly similar outputs, with no warnings.
I can't repeat with an earlier version of Python because it's not easy to get back to Python 3.7. I would suggest trying again with a newer version of Python, and newer versions of scipy and numpy. If the problem persists please reopen this issue.


[sai-gen] Support merging SAI specs.

This change added the SAI spec merging support. This is to ensure any new SAI attribute changes will follow the rules below to help ABI compatibility:

All new attributes or action enum values will be added in the end of the list.
Existing attributes will be updated inline. In the future, we can add more check here, e.g., type changed in non-compatible way and etc.
All old attributes will be marked as deprecated instead of removed.

Recently, the tunnel APIs are added, but because it merged with the SAI spec PR together without rebase, it is not captured in the previous SAI spec. With SAI spec merging, we can see the changes are showing up in the expected sequence. This would be an example that demos the several usages of SAI spec.

Request to @marian-pritsak for assistance


Fix: Proper requirements for enabling BDA extensions

This would fix #1751, but as the next Vulkan SDK will use Xcode 14 anyway apparently, this is just for people who compile MoltenVK themselves. I can imagine many compiling MoltenVK manually, and interestingly enough there's a PR for Mesa that would build MoltenVK in their CI. This essentially makes {KHR,EXT}_buffer_device_address to only be available when MoltenVK to be built with Xcode 14, the host is running macOS 13 or iOS 16, and (which was already there) argument buffers tier 2 to be supported. I hope this is the correct way to do it.
Also, I've upped the requirement in the MVKExtensions.def to macOS 13.0 as the Apple docs say it's available for macOS 13+, and not the 12.5 we had previously.

I just tested this by using the artifacts which are built with Xcode 13 and I indeed do not see {KHR,EXT}_buffer_device_address listed in VulkanCapsViewer, verifying that this indeed works.


feat: angular 11 support

update all dependencies to latest version
update sandbox to ng 11
install schematic as a devDependency

closes #49

Thank you!


You MUST have a  config.json file

Have to have a config.json - every other project does....

+1 for complying with the industry standards.


Lefthand and sneaking fixes

Description

Fixes #361
Fixed sneaking not working

Testing

Sneaking in-front of other players work.
Switching between left and right handed is shown on the client.
Hit animation swings with right arm for both self and others.

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings: cargo clippy
[x] All unit tests pass: cargo test

Looks good.
Thanks @Alvsch


'Paste as geolocation' does NOT work in 5.0.2

Got the error below in console while trying to paste a geolocation:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'app')
    at eval (plugin:obsidian-map-view:37868:45)
    at Generator.next (<anonymous>)
    at fulfilled (plugin:obsidian-map-view:67:58)

which refers to the following lines of code:
if (clipboardLocation)
    insertLocationToEditor(this.app, clipboardLocation.location, editor, file, settings);

Thanks, will fix soon!


Suggestion : Aspire for Desktop  Or Aspire Standalone App

Aspire seems to be promising in terms of developer productivity. Recent time many article that describe bit internal details about it and if look at the code it has many separate components.
Recently while looking at Aspire host application that run in browser and if we look at main purpose of aspire to provide developer productivity then running apphost each time many be complex or sometime time consuming for large project. When I look at docker for desktop, It has nice UI and it allow to start and stop container from that window and many other functionality.
In this direction, if something like cross platform application or extension to VS Code that allow to do this like manage of app running and start and stop specific project, it allow to look at the metrics, log and trace etc. I think this is good option.

The dashboard is currently being updated to support running standalone, separate from AppHost projects (#1003). In this mode, it can be passed a gRPC endpoint URL where the details required for the "Resources" page can be retrieved. It will also continue to host an OTLP endpoint and display any telemetry (logs, traces, metrics) that is sent to it. The dashboard will be made available as a docker container image to enable anyone to host it themselves. Separately we have an existing request to support stopping/restarting resources from the dashboard (#295) but that's not currently a priority for our initial release.


Tooltip not working for the second node

only the first nodes have tooltip enabled.

Hi michimau
I am going to add an option that can do this like the first nodes
Thanks

any news on this?

I'm very busy now, sorry


Improve map view in app

Please check out how others are implementing map views e.g. Google.
Issues below. Please find more:

[ ] use area on top, left and right in app view
[ ] expand map to button area and avoid sidebar scrolls if it is not needed

merged into https://github.com/fossasia/open-event-webapp/issues/57


Add slf4j + logback framework

Inputs from https://github.com/jenkinsci/plugin-installation-manager-tool/issues/263
Let's get rid of System.out as soon as possible
Will also in the future to add some --debug (more logs and different log format) or --verbose option (more logs)
Testing done

Submitter checklist

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Thanks!


Window is blank right after start

I tried running the counter example on my system (Fedora Silverblue 41), but on first start the window is completely blank, until I click on one of the two buttons to change the state of the counter:
Screencast From 2024-11-24 15-11-44.webm
I tired to debug this issue a bit and I noticed that, on start, the app got two RedrawRequested events. So, I tried to comment this line and the issue got away (but obviously the window stopped redrawing).
Unfortunately I don't know how the debug this further.

Appreciate the insight! This definitely looks like a difference on Linux (as you mention maybe it has something to do with the extra RedrawRequested?)

Potentially related https://github.com/actuate-rs/actuate/issues/78
The current render logic may actually be rendering a blank Scene the second redraw 🤔 a new element tree should fix this by changing the paint pass

Closed in favor of https://github.com/actuate-rs/actuate/pull/79


Pass failing test

@proteamer can you add me as a contributor on your fork?

closing for now, I fixed and squashed on a new PR in the main repo, thanks!


Dropdown for Campaign and make it optional

Hi,
In most of the scenarios, campaign is not a must because normally the user sends regular messages so please make it optional and don't force the user to enter campaign.
Also, please make it optional DROPDOWN list instead of text with an option to add so if the user sends regular Marketing Campaign then why he needs to type the word Marketing every time and sometimes he will have spelling mistake so it will come under two campaign.so best option is...

Keep it an dropdown list
Allow the user to add items to the drop down list
and Make it optional not mandatory

Thanks,
Jassim

Thanks for the feature request @jrahma. Tapping in @jwargo to take a closer look at this one.

@jrahma what we're considering doing is enabling customers to resend a notification - would that work for you?

Yes, that will be great..

@jrahma Thank you very much for your feedback on App Center Push. We announced yesterday in a blog post that we’re retiring the Push service later this year and recommending customers transition to Azure Notification Hubs instead. The good news is that the same team operates both App Center Push and Azure Notification Hubs, so all customer feedback and feature requests have been transferred to the Azure Notification Hubs roadmap.


Remove deprecated calls to beforeObserver

This should address #86. Unfortunately this involves creating properties called oldContent and oldSelection. Are those names good? Is there a better approach to this?

Err, I guess I should've ran the tests before sending this. Looking.

never mind!


Fix Payment Intent Dropdown

Found this issue: '~/plugins/cryptoPaymentMetadataApi', is not included in the nuxt.config.js
Other Comments:

add leading / here https://github.com/circlefin/payments-sample-app/blob/master/lib/cryptoPaymentMetadataApi.ts#L40

we don't want to display the request/response sections on the right as we do with other api calls

In this case we can remove to add the data to the store https://github.com/circlefin/payments-sample-app/blob/master/plugins/cryptoPaymentMetadata.ts#L16

These issues could have been found locally. Please try to test locally before merging PRs like #242

You're right, my bad and will make sure not to let this happen in the future. Thank you for your help and reviews 🙏


storing scheduled tasks on global

Pull Request Test Coverage Report for Build 273

14 of 14 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 268:
0.0%

Covered Lines:
262

Relevant Lines:
262

💛  - Coveralls


Added base group chat using Flow class

Description: Added base group chat using Flow class

this addresses #83

This is a WIP


Add center dropdown list when adding new acquisition

Add option of dropdown list with predefined centres (e.g. paris, unf, twh, etc.) when adding new acquisition in the DB

also do dropdown for:

contrast
study

For contrast we have a big variability (t1_* , t2_* ,  t2s_*) because of the mgh-3t connectome scans. Here are all contrasts listed in DB:
dmri
dwi
fmri
mt
t1
t1_ax_fl_mtv_10
t1_ax_fl_mtv_10_0017
t1_ax_fl_mtv_20
t1_ax_fl_mtv_20_0016
t1_ax_fl_mtv_30
t2
t2_hypersignal
t2s
t2_sag_tse
t2s_ax_fl_mtv_04_0018
t2s_ax_fl_mtv_4
Should we modify them and only keep a short list ? Here is an example:
dmri
dwi
fmri
mt
t1
t2
t2s
For study & center, are we going with a dropdown menu & the possibility of adding the field is it's not in the list ?

@alexfoias i would go with:
dwi
fmri
t1
t2
t2s

note that dwi and fmri could, in principle, be 3D or 4D, so it would be great to add a field that specifies if the data is 3D or 4D (could you open an issue-- not that this could be found automatically from the image header-- as done for the orientation).
for study/center: yes, dropdown menu with possibility to add. BTW: it would be important to get have somewhere the relation between the short and long center definition (e.g. mgh = massachusetts general hospital, boston, usa). Creating a dictionary would be a good approach. Could you pls open an issue? thx!

I would like to solve this issue step by step based on the individual issues:

Contrast dropdown list
Center dropdown list
Study dropdown list
fMRI data dimension

This issue is very old. We have abandoned this system. We can close the issue.


Notify Service Feature Request

Notification service feature requirement :
API Endpoints :
/fcmToken - to save fcm token to the DB so that we can notfiy each devices.
/notify - to send the notification.

Please add proper description like this https://github.com/Real-Dev-Squad/website-backend/pull/1738


WIP fix review app deployment

Hoping this is just an issue with slipping node versions

Cool yeah looks like this was it. FYI @aleksharma12

Nice, thanks for looking into that!


docs: add workflow example of tool

Added a detailed example of how to use the tool with the google takeout interface while ensuring all data is captured and given the correct metadata. This was the workflow I came up with after much frustration in trying to migrate my messy Google Photos to iCloud.

@mattwilson1024 there are a few open PR's that seem to add great features, hope you're still active and can review them!


Simultaneous Mouse and multi-touch input Crash

Describe the bug
Simultaneous Mouse and multi-touch input causes an ...... Unhandled exception at 0x00007FF8408A26DB (Microsoft.InputStateManager.dll) in ***.exe: Fatal program exit requested.
Steps to reproduce the bug
Run a Windows App SDK 1.2.2 App
Simultaneously use the Mouse and two figures .
App crashes...
Expected behavior
App does not crash!!!
Screenshots

NuGet package version
WinUI 3 - Windows App SDK 1.2.2: 1.2.221209.1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Closing as dupe of https://github.com/microsoft/WindowsAppSDK/issues/3257

Correction: This is a dup of #7622.


1Password: op-ssh-sign nowhere in PATH

Commit signing with 1Password requires op-ssh-sign. Up until now, I found that it was linked in /run/current-system/sw/share/1password/op-ssh-sign, which wasn't in PATH either, but at least it wasn't a file directly from the store. However, a recent update has wiped this symlink (the entire folder), and rebuilding doesn't recreate it. I had to include a path to a file in the store directly in my git config, which is not too clean.
All the 1Password binaries are in path except for this one. Isn't it possible to add this to some folder in PATH?
Steps To Reproduce
Steps to reproduce the behavior:

run which op-ssh-sign
Not found

Expected behavior
The program should be found
Notify maintainers

@timstott
@savannidgerinel
@maxeaubrey
@SebTM

Metadata
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.27, NixOS, 23.05 (Stoat), 23.05pre481202.3e313808bd2`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(cabero): `"home-manager, nixpkgs"`
 - channels(root): `"nixos, unstable"`
 - nixpkgs: `/home/cabero/.nix-defexpr/channels/nixpkgs`

Nevermind, I am new to nix. I realized I could just link it as "{pkgs._1password-gui}/share/1password/op-ssh-sign"...

Ah, that feature seems to have a bit of a subpar UX right now, I wonder if 1p would be open to fixing that on Nix specifically. See #230767 for a fix, lemme know if that works.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/cant-commit-with-git-after-installing-1password/34021/1


DO NOT MERGE [BEAM-5143]/stop showing deps unable upgrading in report

Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


V20220226: stale (?) OpenCore version in left upper corner (0.7.8)

I boot my computer with OpenCore 0.8.2, but still see the following

Please see here: https://github.com/ic005k/OCAuxiliaryTools/issues/246

The problem apparently persists, even with the current version of OCAT (2023-004).


[MM-48104] upgrade core-js

Summary

Upgrade core-js to its latest version (minor updates):

From version
To version
Changelog
Notes

3.23.3
3.26.0
changelog
-

Ticket Link

https://mattermost.atlassian.net/browse/MM-48104
Release Note

NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

Thanks @trilopin . Maintenance/version-health indeed.

@m1lt0n I'm not very familiar with core-js and I might ask a stupid question... but is it normal for core-js to not appear used in the code? is it used more internally by the bundler and that's why I don't find it?
After a regular search, I tried with depcheck:
➜  mattermost-webapp git:(master) depcheck
Unused dependencies
* buffer
* core-js
* emoji-datasource
* emoji-datasource-apple
* process

@m1lt0n I'm not very familiar with core-js and I might ask a stupid question... but is it normal for core-js to not appear used in the code? is it used more internally by the bundler and that's why I don't find it?
After a regular search, I tried with depcheck:
➜  mattermost-webapp git:(master) depcheck
Unused dependencies
* buffer
* core-js
* emoji-datasource
* emoji-datasource-apple
* process

It wont show up in the actual bundler code directly since its used by babel internally to poly fill code based on the browsers list we have give.
it is being used here in babel config https://github.com/mattermost/mattermost-webapp/blob/master/babel.config.js#L14
So essentially it would have poly filled Array.includes if we were to support ie11. But we are not so its not adding that poly fill

/e2e-test

A pipeline with the same environment variables is already running.
Please cancel it first with /e2e-cancel, or specify different environment variables.

@M-ZubairAhmed I've triggered e2e tests and a test server to just do some random manual checks. Feel free to review. Also, I've checked the bundle size and there is no measurable change with the old and new version of core-js.


Discussion: emirge's role

After some back-and-forth on Slack, I noticed we still have some differing thoughts on emirge, so I wanted to start up one final (hah) discussion in an attempt to iron this out.
In emirgecom, we (tentatively) agreed that emirge should no longer parse mirgecom's requirements.txt. However, there seem to still be two views on what role emirge should play:
View A: emirge is a tool that installs an environment (for our purposes, a CEESD environment).
View B: emirge is a CEESD environment.
In View A, emirge would take as parameters: (some of these are optional) 1) a conda environment name, 2) a list of conda packages, 3) a requirements.txt, and 4) an installation directory. It would create the conda environment, install the conda packages in that environment, and install the pip packages in the specified installation directory. Everyone would use the master branch and construct their own requirements.txt for whatever package versions they want to use. These would exist outside of emirge (i.e., not tracked). (@MTCam please let me know (or edit this directly) if I've gotten any of this wrong.)
View B is much like View A, but a given branch in emirge would encode a set of CEESD package versions via a single tracked requirements.txt. Users would maintain different environments by creating branches with different versions of this file. Installation would be performed once*, with CEESD packages going into the emirge directory. Switching between environments would be done by: 1) checking out a different branch of emirge, and 2) running a helper script to go into the package directories and check out the branches specified in emirge's requirements.txt. (No conda environment switching is done as there is only one environment needed.)
(* Multiple installations are still supported via separate clones, as with anything else.)
I lean towards View B. I think there is a need for something to sit at the top level and keep track of our soon-to-be many different development environments, and now that it looks like mirgecom isn't going to fill that role anymore it has left a bit of a void. I don't think the approach in View A alone can be made to deal with the issues discussed in #53, and manually passing around requirements.txts when someone wants to share an environment or move to a different machine sounds like a mess.
As I understand it, the primary motivation for View A is that this could become something useful in a more general sense (i.e., to install things other than just a CEESD environment). This may be true, and I don't want to discourage that from being explored; but I don't think it needs to be emirge that does this, per se. We can extract that functionality into a separate package (with a more appropriate name; there isn't really anything "mirge" about it when it's installing something else) and then have emirge depend on it.
Thoughts?

I think that version B is just version A with some default environments included.   For example, one for people who intend to develop packages, and one for those who just want to run stuff.

I think that version B is just version A with some default environments included. For example, one for people who intend to develop packages, and one for those who just want to run stuff.

No, that doesn't cover it at all. Suppose I'm working on something that requires branch x of meshmode, branch y of grudge, and branch z of mirgecom (because I'm changing something that impacts all three). Then say I have another change that just requires branch m of mirgecom. Then somebody else asks for help debugging something that uses branches i, j, k, etc... 😱
Defaults don't cover this. We either encode this in git or manually pass these requirements.txt files around.

I think that version B is just version A with some default environments included. For example, one for people who intend to develop packages, and one for those who just want to run stuff.

No, that doesn't cover it at all. Suppose I'm working on something that requires branch x of meshmode, branch y of grudge, and branch z of mirgecom (because I'm changing something that impacts all three). Then say I have another change that just requires branch m of mirgecom. Then somebody else asks for help debugging something that uses branches i, j, k, etc... 😱
Defaults don't cover this. We either encode this in git or manually pass these requirements.txt files around.

There is imho a simpler third option: Telling users to run pip install -r requirements.txt inside the mirgecom dir whenever they checkout a new mirgecom branch.

I

I think that version B is just version A with some default environments included. For example, one for people who intend to develop packages, and one for those who just want to run stuff.

No, that doesn't cover it at all. Suppose I'm working on something that requires branch x of meshmode, branch y of grudge, and branch z of mirgecom (because I'm changing something that impacts all three). Then say I have another change that just requires branch m of mirgecom. Then somebody else asks for help debugging something that uses branches i, j, k, etc... 😱

We agree on this, @majosm .  I am not arguing against continuing to use version control with emirge, and being able to modify the "requirements.txt" file there, and check that in as a branch.  To me VersionB still looks like VersionA, but with source control. I've never advocated that any of our files should be taken out of source control - and I missed that about your initial description of VersionA.
My real issue is dealing with the case where a single user needs to run multiple versions of the code at the same time on the same machine.  I just need emirge to have enough functionality to allow that use case.  That's the case behind all of my issues with emirge.  emirge@master currently works for me - I just want to retain some of its behaviors.

We agree on this, @majosm . I am not arguing against continuing to use version control with emirge, and being able to modify the "requirements.txt" file there, and check that in as a branch. To me VersionB still looks like VersionA, but with source control. I've never advocated that any of our files should be taken out of source control - and I missed that about your initial description of VersionA.

Ok, cool. Slack comments seemed to suggest otherwise, but I'm glad we're on the same page now.

My real issue is dealing with the case where a single user needs to run multiple versions of the code at the same time on the same machine. I just need emirge to have enough functionality to allow that use case. That's the case behind all of my issues with emirge. emirge@master currently works for me - I just want to retain some of its behaviors.

Does that come from this part:

ABATE wakes up and reads a file that tells it what projects to test (currently I test mirgecom@mtc/euler only - but each "project" is a branch of mirgecom for us)

?
To me, this isn't the approach ABATE/TEESD should be taking in a post-#72 world. Part of what I was trying to get at above and in Slack is that emirge's (or whatever "top-level" package we decide on) requirements.txt should be considered the official source for an environment's package version information, not mirgecom's. Trying to circumvent it to use mirgecom's instead is the wrong way to go about it IMO.
Can ABATE/TEESD be adjusted such that its projects can be branches of emirge (or whatever "top-level") instead of mirgecom? It would be nice if we could create a branch in emirge with a specified set of package versions, then just tell TEESD, "Hey, go test this emirge branch".

Can ABATE/TEESD be adjusted such that its projects can be branches of emirge (or whatever "top-level") instead of mirgecom? It would be nice if we could create a branch in emirge with a specified set of package versions, then just tell TEESD, "Hey, go test this emirge branch".

Yes.  That is how it works now, and how I would like for it to continue working.  I misspoke before, each project is a different branch of emirge, not mirgecom.   But each version of emirge that I test is associated with a particular branch of mirgecom.   I was using emirge@teesd for that - but since all the emirge changes, I have switched to emirge@master and specify the --branch option to get a particular branch.   I'm ok if this changes, it is sort of orthogonal to the troubles I have. As long as emirge@some_branch can install mirgecom@a-branch - any branch I need, then I'm fine with that.
If I limit the testing to one branch, this all works fine.  If I need more than one version of the code to be running at the same time on the same platform (e.g. like during prediction or when testing changes or testing multiple branches) - that's when the trouble starts for me.
The feature of emirge that allows the multiple simultaneous installs to work is its ability to install each mirgecom installation into its own environment using a common conda.  Current emirge does this.  I seek to retain this behavior, and I don't think this feature runs afoul of our collective vision for emirge

It is my understanding that since only one version of each package can be used at the same time in any given environment - that this situation requires multiple installations of mirgecom , each in its own environment. Is that true?

I believe that's true.

ABATE wakes up and reads a file that tells it what projects to test (currently I test mirgecom@mtc/euler only - but each "project" is a branch of mirgecom for us)

?
To me, this isn't the approach ABATE/TEESD should be taking in a post-#72 world. Part of what I was trying to get at above and in Slack is that emirge's (or whatever "top-level" package we decide on) requirements.txt should be considered the official source for an environment's package version information, not mirgecom's. Trying to circumvent it to use mirgecom's instead is the wrong way to go about it IMO.

Uhh, I think this would be hard to do. How would you keep emirge's requirement.txt in sync with whatever branch X of mirgecom requirements.txt describe?

It is my understanding that since only one version of each package can be used at the same time in any given environment - that this situation requires multiple installations of mirgecom , each in its own environment. Is that true?

I believe that's true.

Then I would like if emirge could (continue to) do that.

Uhh, I think this would be hard to do. How would you keep emirge's requirement.txt in sync with whatever branch X of mirgecom requirements.txt describe?

I think I can just check out emirge@xyz, and know that it install the version of mirgecom that I need. Can't I?

It is my understanding that since only one version of each package can be used at the same time in any given environment - that this situation requires multiple installations of mirgecom , each in its own environment. Is that true?

I believe that's true.

Then I would like if emirge could (continue to) do that.

Ok, I think the current version of PR #72 can do that.

Uhh, I think this would be hard to do. How would you keep emirge's requirement.txt in sync with whatever branch X of mirgecom requirements.txt describe?

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with the PR) is to manually select a branch of mirgecom, or just clone mirgecom@master, run git checkout <mybranch>, and run pip install -r requirments.txt (to get the correct version of dependencies).

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with PR #72) is to manually select a branch of mirgecom, or just tell emirge to install mirgecom@master, run git checkout <mybranch> in mirgecom/, and run pip install -r requirements.txt (to get the correct version of dependencies).

Wouldn't it amount to just checking out emirge, make a branch, edit the requirements.txt to be the version of mirgecom that I want and then just check that back in as a branch of emirge?  What would stop me from doing that?

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with PR #72) is to manually select a branch of mirgecom, or just tell emirge to install mirgecom@master, run git checkout <mybranch> in mirgecom/, and run pip install -r requirements.txt (to get the correct version of dependencies).

Wouldn't it amount to just checking out emirge, make a branch, edit the requirements.txt to be the version of mirgecom that I want and then just check that back in as a branch of emirge? What would stop me from doing that?

Are you going to make a branch in emirge for every branch in mirgecom? That seems... not good...

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with PR #72) is to manually select a branch of mirgecom, or just tell emirge to install mirgecom@master, run git checkout <mybranch> in mirgecom/, and run pip install -r requirements.txt (to get the correct version of dependencies).

Wouldn't it amount to just checking out emirge, make a branch, edit the requirements.txt to be the version of mirgecom that I want and then just check that back in as a branch of emirge? What would stop me from doing that?

Are you going to make a branch in emirge for every branch in mirgecom? That seems... not good...

Naw, just the ones I want to share or be able to recreate remotely. Like if I need you or Matt to look at something (for the umpteenth time), then I can just check in an emirge branch that will install exactly the packages you need to recreate my environment.   Look at it, run it, then blow it away.

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with PR #72) is to manually select a branch of mirgecom, or just tell emirge to install mirgecom@master, run git checkout <mybranch> in mirgecom/, and run pip install -r requirements.txt (to get the correct version of dependencies).

Wouldn't it amount to just checking out emirge, make a branch, edit the requirements.txt to be the version of mirgecom that I want and then just check that back in as a branch of emirge? What would stop me from doing that?

Are you going to make a branch in emirge for every branch in mirgecom? That seems... not good...

Naw, just the ones I want to share or be able to recreate remotely. Like if I need you or Matt to look at something (for the umpteenth time), then I can just check in an emirge branch that will install exactly the packages you need to recreate my environment. Look at it, run it, then blow it away.

That seems like a very labor-intensive process and would also duplicate the the requirements in two different files, like I mentioned above.

I think I can just check out emirge@xyz, and know that it install(s) the version of mirgecom that I need. Can't I?

I don't think there is currently a way to do this automatically, and I struggle to imagine even a theoretical way how to do that automatically. The manual way to do this (either in emirge@master or with PR #72) is to manually select a branch of mirgecom, or just tell emirge to install mirgecom@master, run git checkout <mybranch> in mirgecom/, and run pip install -r requirements.txt (to get the correct version of dependencies).

Wouldn't it amount to just checking out emirge, make a branch, edit the requirements.txt to be the version of mirgecom that I want and then just check that back in as a branch of emirge? What would stop me from doing that?

Are you going to make a branch in emirge for every branch in mirgecom? That seems... not good...

Naw, just the ones I want to share or be able to recreate remotely. Like if I need you or Matt to look at something (for the umpteenth time), then I can just check in an emirge branch that will install exactly the packages you need to recreate my environment. Look at it, run it, then blow it away.

That seems like a very labor-intensive process and would also duplicate the the requirements in two different files, like I mentioned above.

I don't follow that it is labor intensive, or the duplication concern.  I'm not saying there would be a new requirements file - just that the requirements file can differ between emirge branches, like any other file can differ between branches.

I don't follow that it is labor intensive, or the duplication concern. I'm not saying there would be a new requirements file - just that the requirements file can differ between emirge branches, like any other file can differ between branches.

Regarding the labor intensity: Imagine you create a branch X in mirgecom, and have to create a corresponding branch X in emirge. Some days later, you change the requirements in mirgecom's branch X, and have to remember to make the corresponding changes in emirge's branch X.
Regarding the duplication: instead of the relatively coarse-grained dependencies tracked in the #72 PR, you now need to track every change to mirgecom requirements.txt (whether to the master branch or another branch) in a file outside mirgecom (emirge's requirements.txt).

I don't follow that it is labor intensive, or the duplication concern. I'm not saying there would be a new requirements file - just that the requirements file can differ between emirge branches, like any other file can differ between branches.

Regarding the labor intensity: Imagine you create a branch X in mirgecom, and have to create a corresponding branch X in emirge. Some days later, you change the requirements in mirgecom's branch X, and have to remember to make the corresponding changes in emirge's branch X.

This seems like the required amount of labor to me.   Iff I want/need emirge to be able to install my branch directly, then yes - I make a branch of emirge that does it (simply by editing the emirge/requirements.txt), and then checking that branch in.
In many cases (including for our personal individual use), simply checking out emirge@master and installing will be enough, because we can easily ( some of us more easily than others ) switch between our branches for our current environment.  No need to make an emirge branch for that.

Regarding the duplication: instead of the relatively coarse-grained dependencies tracked in the #72 PR, you now need to track every change to mirgecom requirements.txt (whether to the master branch or another branch) in a second file that is outside mirgecom (emirge's requirements.txt).

Sorry, I still don't follow where this external requirements.txt is coming from.  The requirements.txt file I've been thinking about is the one in emirge.

Edit: I agree with everything you just said @majosm about the functionality and motivation of emirge. However the motivation behind our continued discussions about the functionality isn't about whether emirge can be used as an external, or more general tool, but remaining general enough to support one of my use cases - but I think it's an important one.
What does a person do when there is a need to run multiple simulations at the same time with different versions of the code? This is often faced by our main end-user (e.g. the person doing the prediction).
It is my understanding that since only one version of each package can be used at the same time in any given environment - that this situation requires multiple installations of mirgecom , each in its own environment. Is that true?

Gotcha. Right, I think you'd want to clone emirge several times and install each into a separate environment. If #72 doesn't currently allow this, it should be fixed up to do so.

That seems like a very labor-intensive process and would also duplicate the the requirements in two different files, like I mentioned above.

I don't see it as being very labor intensive. Keep in mind, this type of duplication already exists, e.g.: if you want to use a different branch of loopy, you already need to modify requirements.txt for meshmode, grudge, and mirgecom. This just adds one more step in the chain.
Also, emirge's requirement.txt may not always remain a simple duplication of mirgecom's. It's possible we may add some extra packages that are useful within the center, but aren't strictly required for mirgecom, etc.

I don't follow that it is labor intensive, or the duplication concern. I'm not saying there would be a new requirements file - just that the requirements file can differ between emirge branches, like any other file can differ between branches.

Regarding the labor intensity: Imagine you create a branch X in mirgecom, and have to create a corresponding branch X in emirge. Some days later, you change the requirements in mirgecom's branch X, and have to remember to make the corresponding changes in emirge's branch X.

This seems like the required amount of labor to me. Iff I want/need emirge to be able to install my branch directly, then yes - I make a branch of emirge that does it (simply by editing the emirge/requirements.txt), and then checking that branch in.
In many cases (including for our personal individual use), simply checking out emirge@master and installing will be enough, because we can easily ( some of us more easily than others ) switch between our branches for our current environment. No need to make an emirge branch for that.

Ok, fair enough.

Regarding the duplication: instead of the relatively coarse-grained dependencies tracked in the #72 PR, you now need to track every change to mirgecom requirements.txt (whether to the master branch or another branch) in a second file that is outside mirgecom (emirge's requirements.txt).

Sorry, I still don't follow where this external requirements.txt is coming from. The requirements.txt file I've been thinking about is the one in emirge.

We'll need to duplicate changes in mirgecom's requirements.txt to  emirge's requirements.txt.

Keep in mind, this type of duplication already exists, e.g.: if you want to use a different branch of loopy, you already need to modify requirements.txt for meshmode, grudge, and mirgecom. This just adds one more step in the chain.

I don't think we need to modify meshmode's etc. requirements.txt if we want to use a different branch of loopy. This will come in automatically if we change mirgecom's requirements.txt.

Also, emirge's requirement.txt may not always remain a simple duplication of mirgecom's. It's possible we may add some extra packages that are useful within the center, but aren't strictly required for mirgecom, etc.

Certainly, and PR #72 already has such a facility, by using requirements.txt for "our" packages (such as loopy), and requirements_dev.txt for nice-to-have packages such as flake8.

I don't think we need to modify meshmode's etc. requirements.txt if we want to use a different branch of loopy. This will come in automatically if we change mirgecom's requirements.txt.

Oh good, then we don't need to change mirgecom's either, we can just change emirge's. 😄

Certainly, and PR #72 already has such a facility, by using requirements.txt for "our" packages (such as loopy), and requirements_dev.txt for nice-to-have packages such as flake8.

I'm not really talking about optional dev packages, I was thinking more along the lines of things we would use in our simulations that fall outside of the scope of mirgecom as a solver-focused package.

I don't think we need to modify meshmode's etc. requirements.txt if we want to use a different branch of loopy. This will come in automatically if we change mirgecom's requirements.txt.

Oh good, then we don't need to change mirgecom's either, we can just change emirge's. 😄

Not really, since mirgecom's requirements.txt should reflect accurate requirements as well. Not everyone will use emirge to install mirgecom.

Certainly, and PR #72 already has such a facility, by using requirements.txt for "our" packages (such as loopy), and requirements_dev.txt for nice-to-have packages such as flake8.

I'm not really talking about optional dev packages, I was thinking more along the lines of things we would use in our simulations that fall outside of the scope of mirgecom as a solver-focused package.

Ok, we could add another file, requirements_sim.txt or so.

Not really, since mirgecom's requirements.txt should reflect accurate requirements as well. Not everyone will use emirge to install mirgecom.

Nor will everyone use mirgecom to install meshmode or grudge. 🙂
To clarify one thing: I don't think every dependency of mirgecom should go in emirge's requirements.txt. It should just contain our CEESD packages (and maybe a few odds and ends that don't make sense as dependencies of any particular subpackage). Other dependencies will get installed by the package that needs them.

Ok, we could add another file, requirements_sim.txt or so.

Why?

Not really, since mirgecom's requirements.txt should reflect accurate requirements as well. Not everyone will use emirge to install mirgecom.

Nor will everyone use mirgecom to install meshmode or grudge. 🙂

Sure, but wouldn't that be the responsibility of the meshmode etc. package then? Just to clarify: If you need a different loopy branch due to a change in mirgecom, changing the requirements.txt in mirgecom should be enough; you normally don't need to change the other packages that also happen to require loopy.

To clarify one thing: I don't think every dependency of mirgecom should go in emirge's requirements.txt. It should just contain our CEESD packages (and maybe a few odds and ends that don't make sense as dependencies of any particular subpackage). Other dependencies will get installed by the package that needs them.

Right, and thats the situation with #72 currently (minus the setup.py vs. requirements.txt shenanigans), right?

Ok, we could add another file, requirements_sim.txt or so.

Why?

To make them easier to install (optionally)?

This might call for a few model use cases - especially the ones we all think we want and/or need.   Maybe we can tweak our use cases and the proposed solution i.e. PR #72 (if any tweaking is needed), until they meet up.   I have some expectation that my use case may be part of what needs "debugged" here.
But here it is:
Multiple working installs for the end-user.
The end-user has some additional packages to install to their environment specified by conda_extra_package_names.txt and pip_extra_requirements.txt.  Assume the user has already tailored those lists for platform compatibility. The end-user requires two different branches of mirgecom, say branch1, and branch2.   These two branches are already assumed to have working, valid requirements.txt files inside - indicating whatever branches of subprojects, etc.
Install 1:

git clone git@github.com:/illinois-ceesd/emirge emirge.branch1
cd emirge.branch1
./install.sh --conda-path= --env-name=branch1.env --branch=branch1 --conda-pkgs=conda_extra_package_names.txt --pip-pkgs=pip_extra_requirements.txt

Some explaining of the arguments:

--conda-path= is required because two different installations of conda fight with each other when installed side-by-side
--env-name=branch1.env is really optional, end-user could let this default to "dgfem", but he opts to name the environment (the only requirement is that this environment is named other than the one used for Install 2)
--branch=branch1 is also optional because end-user can always just install master, and switch the branch manually, but the option is there, and it works so he uses it [ this option is removed in #72 ]
--pip-pkgs=pip_req.txt - Optional, could apply manually [ option removed by #72 ]
--conda-pkgs=conda_extra.txt - This is optional, end-user could apply them manually

After #72 and the removal of those options - the user must either follow either:
manual install path 1:  install miregecom@master in editable then switch branch(es) -or-
manual install path 2: edit the<EMAIL_ADDRESS>to indicate the branch he needs, branch1, and optionally add the additional pip packages he needs
Question: In (manual install path 1), does the switch of mirgecom branch automatically take care of switching the sub-package branches if required in<EMAIL_ADDRESS>Now the end-user has a fully working mirgecom@branch1 installed on the platform using <common conda> with environment named branch1.env.
Install 2

git clone git@github.com:/illinois-ceesd/emirge emirge.branch2
cd emirge.branch2
./install.sh --conda-path= --env-name=branch2.env --branch=branch2 --conda-pkgs=conda_extra_package_names.txt --pip-pkgs=pip_extra_requirements.txt

After #72, the user will have used one of the manual install paths, MIP1, or MIP2 or some combo thereof.  I contend that MIP2 is superior because:
Now the user wants to take his simulations or a portion of those say from Quartz to Lassen, or share his setup with others (which he does).  Having followed MIP2, then he can just check in his emirge changes in a branch (e.g. emirge@eu_branch1).
In this sense, MIP2 seems superior even to emirge@master.  Additionally if the user wants to automate this process later, it is easier because the automaton can just checkout emirge@eu_branch1 and "hit go", instead of scripting manual steps.


added contributor image in readme

PR for issue #21

check it again

@AnshuPathak-88825 Add the hr tag

done @Susmita-Dey check it again


Update starter code for spaceflights to mirror tutorial changes

Changes to spaceflights starter to mirror changes in issue on Kedro Framework

[ ]  https://github.com/kedro-org/kedro/issues/1874

Motivation and Context
We want people that use the tutorial to be able to replicate exactly the code we are walking them through. Since I've removed a bunch of the more complex stuff (such as namespacing) I have had to revisit the starter to remove it from there too.
How has this been tested?
Rebuilt a project with this new starter code and tested it
Compared against a version of the tutorial code I created from scratch
Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Assigned myself to the PR
[ ] Added tests to cover my changes

@merelcht @noklam Please can I get review on this starter now I've resolved the pinned dependencies issue.


wip

Project organization

Closes
Related
Dependant on

Description

How to test

Checklist

[ ] Base branch of the PR is dev
[ ] Update docs if necessary

@antho1404 what is this PR about? Can you update its name and description or otherwise just close it.


Allow depending on byteorder 1.5

Update the macros dependency to allow byteorder 1.5 to be used, which was released ~6 months ago.  This is needed to make usbd-hid usable with other crates that use byteorder 1.5 in their macros.

If it works, feel free to just pin it to 1.5 or greater. I assumed youve tested this?
I can merge whenever, but I won't be able to cut a new crates release till i get back from denver in ~days.

Sorry for the slow reply.  I had wanted to get this working on some actual hardware to do more testing, and that took longer than planned.  I have confirmed it works fine on some real hardware now, and the cargo test tests pass.
I can go ahead and update this to just depend on 1.5 if that is the preferred approach.

I just updated this to depend simply on 1.5
Note that it looks like the master branch is currently broken.  The most recent commit is trying to call an EndpointIn::maybe_write() method that doesn't exist.

I’m moving today/tomorrow but will once things are good I can merge and cut a new release. My main computer with crates.io creds is in a box at the bottom of the pile


Change the Twitter API call to follow a UserId set

Background information
For the use case of tracking a user's tweets/replies/mentions, the filter.keywords property can be exploited to scan for tweets containing the user's Twitter handle. This is supported by the "track" request paramater of the API endpoint, and can sometimes perform acceptably for mentions and replies.
But to select for a user's tweets themselves, only in the rare case that a user's tweet contains their own username will it be captured—since the matching keywords must appear somewhere in the tweet body. Otherwise, the connector currently has no way of tracking tweets originating from a given account.
However, the API also provides us with a follow request parameter (see the doc referred to above), which can bring to bear the desired tweets.
Implementation summary

Add a configuration option that is a set (maybe empty) of Twitter UserId values to follow
Add the UserId set to the FilterQuery via its follow method

Before & after
After this change, the filter.userIds property, a comma-separated list of UserId values will be allowed (which could be an empty string, which is the default), and if specified will allow the connector to follow tweets originating from, replying to, or mentioning the listed users.
In addition, the connector will continue to track all other tweets that contain any specified filter keywords in their text.

nice 👍

Sorry about the delay. This is merged and will be in the next release.


Add keys to change extrinsic matrix in perception viewer

You can change the extrinsic matrix of the camera while the perception viewer runs. It should help with calibrating the camera.
The controls are as follows:
M - change rotation mode or go back to normal mode
In rotation mode:
W,S - rotate forward, backward (around the axis perpendicular to the direction of the car)
A,D - rotate left, right (around the direction of the car)
Q.E - rotate left, right (around the vertical axis)
N - change translation mode or go back to normal mode
W,S - forward, backward
A,D - left, right
Q,E - up, down
Z - save the matrix to /apollo/extrinsics.yaml

@jinghaomiao Should I make a new clean PR with only the latest commit, or is this fine?

This should be fine. But it's pending on the review from some of our engineers.


Building for Android is a quest

I have Android SDK 23 and 24 installed. Adding this plugin and then building my app (powered by Ionic) via ionic build android does not work.
The build instruction spits out this error
Running: /Users/distiller/redacted-app/platforms/android/gradlew cdvBuildDebug -b /Users/distiller/redacted-app/platforms/android/build.gradle -Dorg.gradle.daemon=true

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':_debugCompile'.
   > Could not find any version that matches com.android.support:support-v13:23+.
     Searched in the following locations:
         https://repo1.maven.org/maven2/com/android/support/support-v13/maven-metadata.xml
         https://repo1.maven.org/maven2/com/android/support/support-v13/
     Required by:
         :android:unspecified

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

BUILD FAILED

The required dependency is not found on Maven. When removing cordova.system.library.1=com.android.support:support-v13:23+ from platforms/android/project.properties (so that it does not longer look on Maven for said dependency) the build still fails, as the required classes are still not found.
:compileReleaseJava/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:18: error: package android.support.v4.app does not exist
import android.support.v4.app.NotificationCompat;
                             ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:220: error: package NotificationCompat does not exist
    private void createActions(Bundle extras, NotificationCompat.Builder mBuilder, Resources resources, String packageName) {
                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:244: error: package NotificationCompat does not exist
    private void setNotificationCount(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                       ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:254: error: package NotificationCompat does not exist
    private void setNotificationVibration(Bundle extras, Boolean vibrateOption, NotificationCompat.Builder mBuilder) {
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:272: error: package NotificationCompat does not exist
    private void setNotificationMessage(int notId, Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:369: error: package NotificationCompat does not exist
    private void setNotificationSound(Context context, Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:384: error: package NotificationCompat does not exist
    private void setNotificationLedColor(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                          ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:403: error: package NotificationCompat does not exist
    private void setNotificationPriority(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                          ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:419: error: package NotificationCompat does not exist
    private void setNotificationLargeIcon(Bundle extras, String packageName, Resources resources, NotificationCompat.Builder mBuilder) {
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:448: error: package NotificationCompat does not exist
    private void setNotificationSmallIcon(Context context, Bundle extras, String packageName, Resources resources, NotificationCompat.Builder mBuilder, String localIcon) {
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:466: error: package NotificationCompat does not exist
    private void setNotificationIconColor(String color, NotificationCompat.Builder mBuilder, String localIconColor) {
                                                                          ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:124: error: package NotificationCompat does not exist
        NotificationCompat.Builder mBuilder =
                          ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:125: error: package NotificationCompat does not exist
                new NotificationCompat.Builder(context)
                                      ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:290: error: package NotificationCompat does not exist
                NotificationCompat.InboxStyle notificationInbox = new NotificationCompat.InboxStyle()
                                  ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:290: error: package NotificationCompat does not exist
                NotificationCompat.InboxStyle notificationInbox = new NotificationCompat.InboxStyle()
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:300: error: package NotificationCompat does not exist
                NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                  ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:300: error: package NotificationCompat does not exist
                NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:310: error: package NotificationCompat does not exist
            NotificationCompat.BigPictureStyle bigPicture = new NotificationCompat.BigPictureStyle();
                              ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:310: error: package NotificationCompat does not exist
            NotificationCompat.BigPictureStyle bigPicture = new NotificationCompat.BigPictureStyle();
                                                                                ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:322: error: package NotificationCompat does not exist
            NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                              ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:322: error: package NotificationCompat does not exist
            NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                                                            ^
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:408: error: cannot find symbol
                if (priority >= NotificationCompat.PRIORITY_MIN && priority <= NotificationCompat.PRIORITY_MAX) {
                                ^
  symbol:   variable NotificationCompat
  location: class GCMIntentService
/Users/distiller/redacted-app/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:408: error: cannot find symbol
                if (priority >= NotificationCompat.PRIORITY_MIN && priority <= NotificationCompat.PRIORITY_MAX) {
                                                                               ^
  symbol:   variable NotificationCompat
  location: class GCMIntentService
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
23 errors
 FAILED

Having Googled a bit around I've found some solutions hinting to install “Android Support Library", yet that already was the case. Another solution mentioned android-support-v13.jar, which contains the required classes.
I've found a Cordova Plugin that contains this .jar file: https://github.com/nnexai/cordova-plugin-android-support-v13. When installing said plugin (cordova plugin install https://github.com/nnexai/cordova-plugin-android-support-v13) – in addition to the removal of the line cordova.system.library.1=com.android.support:support-v13:23+ from project.properties – the build now works fine.
I was wondering: is it possible to not inject the cordova.system.library.1=com.android.support:support-v13:23+ requirement, and – instead – require https://github.com/nnexai/cordova-plugin-android-support-v13?

Exploring this repo a tad further it seems like android-support-v13.jar – at a given moment – was indeed included in this project, but then got replaced by a Maven requirement: https://github.com/phonegap/phonegap-plugin-push/commit/6b5bebb85c94cca0a734c743b37a50fccc57c8c7

@bramus Yes, I used to included the android-support-v13.jar file in the plugin but that is not the correct way to do things. If more than one plugin includes this jar you will get Dexopt errors while compiling since the jar was included more than once. If you go back through the plugins issues you will find this was a common complaint.
The proper way to include this jar as of Android Studio/Android 5/Gradle/Maven is via the framework tag. This gets around the multi jar problem and is the way Google is doing things going forward so I'm not going backwards. In fact I'll be removing gcm.jar and replacing it with another framework in the near future.
I'd rather not depend on an external plugin for this functionality as I'm not sure when they update their jar version. Instead I will document how to install the jar locally so your build will just work.

https://github.com/phonegap/phonegap-plugin-push#compiling

Hey Simon,
Thanks for the quick response.
I've checked and I had ”Android Support Library” already installed, yet things were still going wrong: the dependency could not be resolved.
Looking a bit further I found this interesting note on https://developer.android.com/tools/support-library/setup.html:

Note: If you're developing with Android Studio, select and install the Android Support Repository item instead.

When looking at the screenshot above you seem to also have this installed, yet I hadn't. Installing “Android Support Repository” (the latest: v20) eventually fixed it for me.
Regards,
B!

@bramus thanks for the heads up, I just updated the README.

:+1:

Its still a quest (atleast for me)
build errors i am getting -
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:18: error: package android.support.v4.app does not exist
import android.support.v4.app.NotificationCompat;
                             ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:220: error: package NotificationCompat does not exist
    private void createActions(Bundle extras, NotificationCompat.Builder mBuilder, Resources resources, String packageName) {
                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:244: error: package NotificationCompat does not exist
    private void setNotificationCount(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                       ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:254: error: package NotificationCompat does not exist
    private void setNotificationVibration(Bundle extras, Boolean vibrateOption, NotificationCompat.Builder mBuilder) {
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:272: error: package NotificationCompat does not exist
    private void setNotificationMessage(int notId, Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:369: error: package NotificationCompat does not exist
    private void setNotificationSound(Context context, Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:384: error: package NotificationCompat does not exist
    private void setNotificationLedColor(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                          ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:403: error: package NotificationCompat does not exist
    private void setNotificationPriority(Bundle extras, NotificationCompat.Builder mBuilder) {
                                                                          ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:419: error: package NotificationCompat does not exist
    private void setNotificationLargeIcon(Bundle extras, String packageName, Resources resources, NotificationCompat.Builder mBuilder) {
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:448: error: package NotificationCompat does not exist
    private void setNotificationSmallIcon(Context context, Bundle extras, String packageName, Resources resources, NotificationCompat.Builder mBuilder, String localIcon) {
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:466: error: package NotificationCompat does not exist
    private void setNotificationIconColor(String color, NotificationCompat.Builder mBuilder, String localIconColor) {
                                                                          ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:124: error: package NotificationCompat does not exist
        NotificationCompat.Builder mBuilder =
                          ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:125: error: package NotificationCompat does not exist
                new NotificationCompat.Builder(context)
                                      ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:290: error: package NotificationCompat does not exist
                NotificationCompat.InboxStyle notificationInbox = new NotificationCompat.InboxStyle()
                                  ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:290: error: package NotificationCompat does not exist
                NotificationCompat.InboxStyle notificationInbox = new NotificationCompat.InboxStyle()
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:300: error: package NotificationCompat does not exist
                NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                  ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:300: error: package NotificationCompat does not exist
                NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:310: error: package NotificationCompat does not exist
            NotificationCompat.BigPictureStyle bigPicture = new NotificationCompat.BigPictureStyle();
                              ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:310: error: package NotificationCompat does not exist
            NotificationCompat.BigPictureStyle bigPicture = new NotificationCompat.BigPictureStyle();
                                                                                ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:322: error: package NotificationCompat does not exist
            NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                              ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:322: error: package NotificationCompat does not exist
            NotificationCompat.BigTextStyle bigText = new NotificationCompat.BigTextStyle();
                                                                            ^
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:408: error: cannot find symbol
                if (priority >= NotificationCompat.PRIORITY_MIN && priority <= NotificationCompat.PRIORITY_MAX) {
                                ^
  symbol:   variable NotificationCompat
  location: class GCMIntentService
<cordova_root>/platforms/android/src/com/adobe/phonegap/push/GCMIntentService.java:408: error: cannot find symbol
                if (priority >= NotificationCompat.PRIORITY_MIN && priority <= NotificationCompat.PRIORITY_MAX) {
                                                                               ^
  symbol:   variable NotificationCompat
  location: class GCMIntentService
<cordova_root>/platforms/android/src/org/apache/cordova/facebook/ConnectPlugin.java:133: error: cannot access Fragment
        shareDialog = new ShareDialog(cordova.getActivity());
                      ^
  class file for android.support.v4.app.Fragment not found
Note: <cordova_root>/platforms/android/src/org/apache/cordova/facebook/ConnectPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
24 errors
:compileDebugJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileDebugJava'.
> Compilation failed; see the compiler error output for details.

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

BUILD FAILED

Total time: 7.62 secs

<cordova_root>/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
Error code 1 for command: <cordova_root>/platforms/android/gradlew with args: cdvBuildDebug,-b,<cordova_root>/platforms/android/build.gradle,-Dorg.gradle.daemon=true
ERROR building one of the platforms: Error: <cordova_root>/platforms/android/cordova/build: Command failed with exit code 1
You may not have the required environment or OS to build this project
Error: <cordova_root>/platforms/android/cordova/build: Command failed with exit code 1
    at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:131:23)
    at ChildProcess.emit (events.js:110:17)
    at maybeClose (child_process.js:1015:16)
    at Process.ChildProcess._handle.onexit (child_process.js:1087:5)

I do have required files -

and here's my plugins -
<plugin name="cordova.plugin.googleplus" spec="https://github.com/EddyVerbruggen/cordova-plugin-googleplus"/>
<plugin name="cordova-plugin-whitelist" spec="^1.0.0"/>
<plugin name="cordova-plugin-customurlscheme" spec="^4.0.0">
	<variable name="URL_SCHEME" value="xxxxxx"/>
</plugin>
<plugin name="cordova-plugin-google-analytics" spec="^0.8.0"/>
<plugin name="cordova-plugin-dialogs" spec="^1.1.1"/>
<plugin name="cordova-plugin-statusbar" spec="^1.0.1"/>
<plugin name="cordova-plugin-facebook4" spec="^1.3.0-0">
	<variable name="APP_ID" value="xxxxxxxxxxxxxx"/>
	<variable name="APP_NAME" value="xxxxx"/>
</plugin>
<plugin name="phonegap-plugin-push" spec="^1.3.0"/>
<plugin name="cordova-plugin-device" spec="^1.0.1"/>

what i have tried -

copy {android_sdk_path}/extras/android/support/v13/android-support-v13.jar to libs/
got multiple dex files error after this
removed cordova.system.library.5=com.android.support:support-v13:23+ from project.properties
now build is successful

haven't tested push functionality yet. will report if everything is working fine.

Guys I need help, I am new to Mobile App Development, and I am trying add notifications for a sample project using cordova. When try to build the application I am getting the following error.

Please help me to get get rid of this. I have added Android sdk path and Java sdk path to environment variables,

mine claims that the NotificationCompat package does not exist. what's wrong


Update README.md

The original command didn't work for me through command prompt on Windows, so I added the command that worked.

Thanks, I generally don't download python projects from the internet so I'm not that well-versed with that lol


License Permission table access from an extension

Could you please open the License Permission system table to extensions?

Yes, that would be a really very good idea. We would also need access to this table when implementing our solutions in order to determine the effective access to objects.


Support audit['create']

If there is a 'create': true field in the audit data, always create a new point for a dataset entry, instead of trying to find an OSM counterpart.

Done in 768c8c35d242f802dae2bac23c8ebc52e54e0d55


Unsigned decimal fix

Hi @perepechaev , can you show me another test with table schema defined and a real query (like insert into tbl values ) ?

Sorry for the late response, I just have a long vacation for Chinese Spring Festive. :smile:

@perepechaev , I just try to fix new decimal bug, but not use your code here. The old parsing way for new decimal is referred from python-mysql-replication and mysql decimal, sorry that I could not understand your below code:
for i := 0; i < binSize; i++ {
	data[pos+i] ^= 0xff
}

btw, you can checkout the newest master and help me test again.
Thank you.

my tests pass with your changes
my magic: http://play.golang.org/p/F0xzh1ikdm

:smile:


deploy running immediately after promote without merging

I have three coffeeshop microservice repos setup with webhooks to run the build-push-deploy pipeline and then i have three devops repos setup with webhooks to run the deploy-kustomize. When I run the new build-push-deploy pipeline the deploy-kustomize pipeline runs immediately after. I believe the correct behavior is the deploy-kustomize should only run after the devops PR is merged.
@kvijai82 was going to check with the tekton team about this, "Maybe I need to have a conditional check before driving deploy"

Added a conditional check before driving deploy pipeline to only execute the task for push to master.

Not seeing this anymore with the changes from @kvijai82


Preview of files in collection editor is incorrect

Artifact nodes with filters on a parent node do not include those filters in their preview queries.

Added an additional check to the query builder, that includes ALL facets in the hierarchy above the node that the query was requested for.
This will yield different queries when requesting a query for an artifact node directly VS building the subquery for the same artifact node in the context of the full collection query.
Fixes the issue.


Ver 82275 protocol version update

Note. The basic.js example as @jonathanl-bq mentioned was failing. I'm not sure how/when that regression got in, possibly used regression tool using wrong protocol_version. Regardless, confirmed this PR fixes that regression


download files

implement as a subcommand
shbin dl https://github.com/Shiphero/pastebin/blob/main/mgaitan/7f6GRGhBtDg.md
shbin dl main/mgaitan/7f6GRGhBtDg.md
shbin dl mgaitan/7f6GRGhBtDg.md
shbin dl 7f6GRGhBtDg.md    # assume user

it would be cool to be able to download a full directory, right?


Code/Performance improvements in image captioning notebooks - in memory file buffers, batching

Performance improvement:
Using in-memory/file buffers instead of saving/reading masked images locally for getting image captions.
Based on the debugging/logging mechanism used, this step could be integrated into the logging mechanism.

Performance improvement:
Using in-memory/file buffers instead of saving/reading masked images locally for getting image captions.
Based on the debugging/logging mechanism used, this step could be integrated into the logging mechanism.

@anusham1990 Could you point out the exact points that you would like to change? Ir would you be interested in making PR?


Add missing commas, correction of spelling errors

This PR fixes #
Checklist

[x] I have signed the CLA
[x] I have updated/added any relevant documentation

Description
What's the goal of this PR?
Add missing commas, correction of spelling errors

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


Missing a dependency for AdotCollectorAddOn

Describe the bug
const addOns: Array<blueprints.ClusterAddOn> = [
    new blueprints.addons.CloudWatchAdotAddOn(),
    new blueprints.addons.ArgoCDAddOn(),
    new blueprints.addons.CalicoOperatorAddOn(),
    new blueprints.addons.MetricsServerAddOn(),
    new blueprints.addons.ClusterAutoScalerAddOn(),
    new blueprints.addons.AwsLoadBalancerControllerAddOn(),
    new blueprints.addons.VpcCniAddOn(),
    new blueprints.addons.CoreDnsAddOn(),
    new blueprints.addons.KubeProxyAddOn(),
    new blueprints.addons.EbsCsiDriverAddOn(),
];

const cluster = blueprints.EksBlueprint.builder()
    .account(account)
    .region(region)
    .addOns(...addOns)
    .useDefaultSecretEncryption(true) // set to false to turn secret encryption off (non-production/demo cases)
    .build(app, 'k8-test');

Expected Behavior
Adot addon installing
Current Behavior
DEBUG Core add-on vpc-cni is at version v1.12.6-eksbuild.1
DEBUG Core add-on coredns is at version v1.9.3-eksbuild.3
DEBUG Core add-on kube-proxy is at version v1.24.10-eksbuild.2
DEBUG Core add-on aws-ebs-csi-driver is at version v1.18.0-eksbuild.1
AssertionError [ERR_ASSERTION]: Missing a dependency for AdotCollectorAddOn for k8-test
Reproduction Steps
cdk diff
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.79.0 (build e4a2c01)
EKS Blueprints Version
1.7.3
Node.js Version
v19.8.1
Environment details (OS name and version, etc.)
Darwin
Other information
No response

When I try to install it manually thru EKS console, I get Create failed as well.
K8sResourceNotFound | cert-manager is not installed on this cluster. During preview, you are required to have previously installed cert-manager.

I guess I need to recreate the cluster

@NinoSkopac  you need to add AdotCollectorAddOn to the list of the add-ons, as specified in the error message. Please make sure that Adot collector addon is above the CloudWatchAdotAddOn in the list.

Hi @shapirov103
Thanks for your help!
However, I still can't synthesize.
const addOns: Array<blueprints.ClusterAddOn> = [
    new blueprints.addons.AdotCollectorAddOn(),
    new blueprints.addons.CloudWatchAdotAddOn(),
    new blueprints.addons.ArgoCDAddOn(),
    new blueprints.addons.CalicoOperatorAddOn(),
    new blueprints.addons.MetricsServerAddOn(),
    new blueprints.addons.ClusterAutoScalerAddOn(),
    new blueprints.addons.AwsLoadBalancerControllerAddOn(),
    new blueprints.addons.VpcCniAddOn(),
    new blueprints.addons.CoreDnsAddOn(),
    new blueprints.addons.KubeProxyAddOn(),
    new blueprints.addons.EbsCsiDriverAddOn(),
];

Error:
AssertionError [ERR_ASSERTION]: Missing a dependency for CertManagerAddOn for k8-test

I think I might've found a working order of Addons (it synths)
const addOns: Array<blueprints.ClusterAddOn> = [
    new blueprints.addons.ClusterAutoScalerAddOn(),
    new blueprints.addons.AwsLoadBalancerControllerAddOn(),
    new blueprints.addons.CertManagerAddOn(),
    new blueprints.addons.AdotCollectorAddOn(),
    new blueprints.addons.CloudWatchAdotAddOn(),
    new blueprints.addons.ArgoCDAddOn(),
    new blueprints.addons.CalicoOperatorAddOn(),
    new blueprints.addons.MetricsServerAddOn(),
    new blueprints.addons.VpcCniAddOn(),
    new blueprints.addons.CoreDnsAddOn(),
    new blueprints.addons.KubeProxyAddOn(),
    new blueprints.addons.EbsCsiDriverAddOn(),
];

Indeed, cert manager is required for ADOT and hence all the OT based addons like CloudWatch.
As of version 2.5 of AWS Load balancer controller, it is mandatory for  any addon and/or workload that uses service of type LoadBalancer. It makes sense to include it as the first add-on.

Yep, the code I pasted above worked.
Thank you for your help!
Now I'm trying to figure out how to actually see my application's logs (running in pods)


Design proposal for delayed certificate activation

Pull Request Motivation
https://github.com/cert-manager/cert-manager/issues/7012
Kind
/kind design
Release Note
NONE

@jaingeet I added your PR to the 1.17 milestone. That way we don't forget to take a look at this PR before the end of the milestone.


Latex_Intro

Introduction to Latex files (instruction and the slides) added for November 2016 session.

Hi @Andromedanita. I think you may have opened this PR to the wrong fork. When you open a PR to us, you need to make sure the "base fork" is ours, UofTCoders/studyGroup. This repo is the upstream source for our website, but doesn't contain any of our own lessons.
Also, I'm not sure you included any of your own commits?


Add vis-2-widgets-weather-and-heating to latest

Please add my adapter ioBroker.vis-2-widgets-weather-and-heating to latest.
This pull request was created by https://www.iobroker.dev c0726ff.

RE-CHECK!

Thanks for spending your time and providing a new adapter for ioBroker.
Your adapter will get a manual review as soon as possible. Please stand by - this might last one or two weeks. Feel free to continue your work and create new releases. You do NOT need to close or update this PR in case of new releases.
In the meantime please check any feedback issues logged by automatic adapter checker and try to fix them.
You will find the results of the review and eventually issues / suggestings as a comment to this PR. So please keep this PR watched.
If you have any urgent questions feel free to ask.

First of all - THANK YOU for the time and effort you spend to maintain this adapter.
I would like to give some feedback based on my personal oppinion. @Apollon77 might have additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him if you cannot follow my suggestions or want to discuss some special aspects.

[ ] adapt testing to supported node releases
Tests for node 18 are mandatory.
Tests for node 20 are mandatory as this is the recommended node version.
Tests for node 22 are mandatory unless you already know incompatibilities which cannot be fixed immidiatly. In this case please create a issue stating the problem and fix as soon as possible.
So the recommended testmatrix is [18.x, 20.x, 22.x] depending on engines requirments setting at package.json
Tests must be performed at all supported platforms (linux, windows, mac) unless special hardware or software restrictions prohibit this.

Thanks for reading and evaluating this suggestions.
McM1957

reminder 15.9.2024

correction
As this is a onlyWWW adapter without code running in adater context running tests at different platforms seems to be not necessary.

This adapter has been released to latest repository and should be visible within 24h maximum.
Please create a thread at https://forum.iobroker.net/category/91/tester titled like "Test Adapter " to collect some user feedback and provide a link to this topic when requesting addition to stable repository later.
Note: If an other testing topic already exists, it' OK to continue using this topic too.


Update import of storage class UIDs

In the next pydicom release, storage class UIDs will become importable from pydicom.uid (see https://github.com/pydicom/pydicom/blob/master/pydicom/_storage_sopclass_uids.py) and the private _storage_class_uid.py module will be deprecated. We should consider updating highdicom once pydicom 2.3 is out.

It's tangentially related, and I apologize for the distraction, but do you guys know:

what is the process that keeps UIDs in pydicom.uid in sync with the standard?
why there is no equivalent for uid.AllTransferSyntaxes for storage SOP classes?

This was addressed in #163, closing


How do we switch out framework 7 with other frameworks like quasar or onsenui?

How do we switch out framework 7 with other frameworks like quasar or onsenui?
Another Question. If I wanted to add a cordova plugin, how do I import/integrate it? Thanks!

To import/integrate more cordova plugins you just need to follow this way in your project folder:
cordova plugin add cordova-plugin-geolocation


Feature Request: Legendary Action/Resistance Prompts

Note sure it's possible, but I'd love to see prompts added to use both Legendary Actions and Legendary Resistances if charges are available. Legendary Resistances would be prompted any time the creature fails a save (or is forced to make a save if that's easier) and Legendary Actions would be at the end of another creatures turn.

It would be possible to utilize the upcoming Lair Actions features to do a similar thing for Legendary Actions.
The legendary resistance is a bit harder due to the disconnect between something forcing you to make a save, and the resulting roll of the save.

Added for legendary actions in 1.11.0


livebook gets unresponsive after large amount of data in a cell

Environment

Elixir & Erlang/OTP versions (elixir --version):
Operating system:
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc):
Livebook version (use git rev-parse HEAD if running with mix):
Browsers that reproduce this bug (the more the merrier):
Include what is logged in the browser console:
Include what is logged to the server console:

Current behavior
Paste large amount (195KB in my case) of data into one cell can cause the whole livebook unresponsiable.
Expected behavior
Give a nice error to throttle the size of content
a.txt

+1
I've also experienced the same problem. In my case, it was an API call that was returning large data.

@howard0su looks like Monaco tries to tokenize and highlight the line, even though it's extremely long. This is actually a bug and I reported it in https://github.com/microsoft/monaco-editor/issues/3025.
@vishal-h do you have an example to reproduce it? You said it was an API call, so I assume the problem would be the cell output, but inspect should limit the printed data and we also use line virtualization, so I'd need a specific example to figure out where the bottleneck could be :)

having same problem while trying to open a notebook with "Persist outputs" enabled (plotting vega lite chart with large data object)
even though the loading hit timeout, the beam process will keep 100% cpu until restarted
<!-- livebook:{"output":true} -->

```vega-lite
{"$schema":"https://vega.github.io/schema/vega-lite/v5.json","data":{...

What is your Livebook version? We had issues in the past related to parsing the Markdown itself, but it should be fixed on more recent versions.

hi! the versions:
Livebook 0.5.2
Elixir 1.13.2
Phoenix 1.6.6

Hey @fc1943s, could you share the notebook (or the relevant output part)?

to reproduce i opened the vegalite notebook sample, changed these lines of the first chart to increase file size
- |> Vl.data_from_series(iteration: 1..100, score: 1..100)
+ |> Vl.data_from_series(iteration: 1..5000, score: 1..5000)

then saved to a file with persist outputs enabled
after restarting the livebook server, selecting the new file then clicking the open button, it disables for 30~40s then refreshes the page, allowing the file to be selected to open again
here's a snapshot/gist
https://gist.github.com/fc1943s/7545bfae78204afe66c9c7f6a953c022

FTR here's the corresponding PR https://github.com/RobertDober/earmark_parser/pull/100

@fc1943s I've just bumped earmark_parser on main and it should work as expected :)

Closing this as the remaining bug is upstream!


Use Legacy "New Document" Interface is grayed out and ticked/enabled

Photoshop version
CC2021
Describe the bug*
Use Legacy "New Document" Interface is grayed out and ticked/enabled
To Reproduce
Steps to reproduce the behavior:

Go to Preferences
Use Legacy "New Document" is grayed out

Expected behavior
Easily turn off Legacy New Doc interface
Screenshots

System informations

Distro : Ubuntu 22.04
GPU : (NVIDIA GTX 1050)
WINE version : 8.0.2 (Installed Photoshop with 7.0)

FIxed by upgrading to 2022 version

It's international because the normal interface can crash 2021.
I would recommend sticking to 2021 as 2022 isn't stable


Redesigned for plugins and aliases support

Decomposed Rimokon code into core and plugins. Introduced aliases.
Resolves #13

Oops, forgot about the README and the /help command


bump sdi to use sborl

WIP PR for testing the SDI updates from here, which refactors some relation handling and enables unit-based data transfers

abandoned


Authentication and Authorization

Users must be able to login and logout of the system. Upon login they must be assigned a role. They must only be able to access areas of the application and run actions that are allowed by their role.

Epic consists of:

[x] login #14
[x] logout #15
[x] admin assigning roles #17
[x] disable / enable accounts #6
[x] change password #7


Fork Strap

https://github.com/jodylent/project-show-animal/blob/8aa5a191fc71dc016023017d7cd4f7cda4fbdbe7/new_mac.sh#L78-L84
I think this might be better served by forking strap (or trying to make a PR). In the fork the script to be parameterized.

Looks like Strap will not support SSH (HTTPS only) per https://github.com/MikeMcQuaid/strap/issues/17 .
Since everything else has been addressed, I'm leaving the two 'sed s/https/ssh/g' lines as-is and closing the issue.


Widget

This currently will attempt to perform a database migration on new installs which is unnecessary.

The TrackMode enum could also have an option to select a Track Group to show. If the group has more than 6 (or whatever I decide to set the limit to) tracks, only show the first 6.

I'm not sure about this, but I think maybe the app extensions should use just NSPersistentContainer instead of NSPersistentCloudKitContainer?

I'm not sure about this, but I think maybe the app extensions should use just NSPersistentContainer instead of NSPersistentCloudKitContainer?

I actually don't think I should do this because the Cloud Kit container is required for recordID(for:). The reason I thought I might want to do this is because the app extensions don't seem to be able to actually use the CloudKit sync and give lots of console output that appears to be the same as when I run a CloudKit container in a simulator that isn't signed in to iCloud.
This could still potentially be done if all tracks' recordIDs are cached to disk to be referenced later by the widget extension.

This post seems to indicate it's fine to just use the CloudKit container.


9 Dependencies errored.

ian@ian-Latitude-E7440:~$ julia
_
_       _ ()_     |  Documentation: https://docs.julialang.org
()     | () ()    |
_ _   | |  __ _   |  Type "?" for help, "]?" for Pkg help.
| | | | | | |/ ` |  |
| | || | | | (| |  |  Version 1.11.1 (2024-10-16)
/ |_'|||_'_|  |  Official https://julialang.org/ release
|__/                   |
(@v1.11) pkg> add https://github.com/mncrowe/QGDipoles.jl.git
Cloning git-repo https://github.com/mncrowe/QGDipoles.jl.git
Updating git-repo https://github.com/mncrowe/QGDipoles.jl.git
Updating registry at ~/.julia/registries/General.toml
Resolving package versions...
Updating ~/.julia/environments/v1.11/Project.toml
[192f05a4] ~ QGDipoles v1.0.0-DEV https://github.com/mncrowe/QGDipoles.jl#main ⇒ v1.0.0-DEV https://github.com/mncrowe/QGDipoles.jl.git#main
Updating ~/.julia/environments/v1.11/Manifest.toml
[192f05a4] ~ QGDipoles v1.0.0-DEV https://github.com/mncrowe/QGDipoles.jl#main ⇒ v1.0.0-DEV https://github.com/mncrowe/QGDipoles.jl.git#main
Precompiling project...
✗ SpecialFunctions
✗ Jacobi
✗ CUDA → SpecialFunctionsExt
✗ ForwardDiff
✗ ForwardDiff → ForwardDiffStaticArraysExt
✗ NLSolversBase
✗ LineSearches
✗ NLsolve
✗ QGDipoles
0 dependencies successfully precompiled in 47 seconds. 133 already precompiled.
9 dependencies errored.
For a report of the errors see julia> err. To retry use pkg> precompile
(@v1.11) pkg> instantiate
Precompiling project...
✗ SpecialFunctions
✗ Jacobi
✗ CUDA → SpecialFunctionsExt
✗ ForwardDiff
✗ ForwardDiff → ForwardDiffStaticArraysExt
✗ NLSolversBase
✗ LineSearches
✗ NLsolve
✗ QGDipoles
0 dependencies successfully precompiled in 46 seconds. 133 already precompiled.
9 dependencies errored.
For a report of the errors see julia> err. To retry use pkg> precompile
(@v1.11) pkg>

likely installation issue. Closed unless further details received.


[S2GRAPH-127] Refactor ExceptionHander Object into Class.

To publish all incoming requests(WALLOG) into kafka topic.
To publish failed mutations when Storage failed to mutate into backend storage.

looks good to me!