Support Ingress controllers with mTLS on them

Please describe the Improvement and/or Feature Request
Blindly allow traffic to flow into the ingress controller, however add mTLS to the http sessions from the controller to the servers that the ingress forwards to.
public -> (allow *) (nginx) ->  (OSM mTLS) webservers
I want to inject OSM into the ingress controller, and annotate it with please pass through data to ingress controller, however do mTLS on outgoing sessions.
Scope (please mark with X where applicable)

New Functionality          [x ]

Possible use cases
In my usecase

I have already authenticated traffic being proxied into the ingress controller (and is being secured with my own mTLS ).

I need OSM to ignore this "inbound" traffic (ingress controller will decap the mTLS session)

I then need outbound traffic from the ingress controller to use OSM mTLS sessions.

** Problems **

I don't know how to communicate to envoy blindly ignore traffic on inbound port, yet pass it through to application that has been injected with sidecar
I do not know how ingress rules will play with traffic policies.

If I setup a TrafficTarget to allow ingress controller to talk to my backend webservers, and an ingress rule to proxy traffic from ingress controller to backend webservers, what happens to mTLS?

This is done, and the changes have been backported to release-v0.9 to be available in the v0.9.1 release.
Relevant documentation:

Inbound port exclusion: https://release-v0-9.docs.openservicemesh.io/docs/tasks/traffic_management/iptables_redirection/#inbound-port-exclusions
Ignore an ingress resource: https://release-v0-9.docs.openservicemesh.io/docs/tasks/traffic_management/ingress/#ignoring-an-ingress-resource


Flick to dismiss causes animations to break

Flicking to dismiss view controllers breaks the animations. You can get stuck between two states. I was able to repro using Modal Transition example and Pinterest example easily.

Modal Example: Flick the icon up; notice animation is stuck.
Pinterest Example: Dismiss a view controller by flicking down. Again animation gets stuck.

I can provide video if you are not able to repro it. Other than this issue; it looks great; Awesome job by the team! keep it up!!

Hey @aveace, thanks for your feedback! I'll look into it a.s.a.p. to see if I can reproduce it.

I managed to reproduce the issue. The cause for the animation to get stuck is that after interaction (i.e. the flick), the animation layers are started or continued, depending on their animation range relative to the current fractionComplete (see animate(_:) in the TransitionDriver). There's one layer in particular for which it is essential that it continues: the progressLayerAnimator is a non-visible layer with a full animation range, added by the TransitionDriver to guarantee a layer that animates over the full length of the transition. This is the only animation layer (aside from the sharedElementAnimator) of which the completion is monitored by the completionCoordinator, an object that basically wraps a dispatch group, ensuring the overall transition completion is only called when everything is done.
Back to the animate(_:) function: that progressLayerAnimator will have a range that "contains" the current overall fractionComplete, and will be active because its fractionComplete has been adjusted and it has been paused the moment the interaction began (two reasons why a UIViewPropertyAnimator enters the active state). Therefore the TransitionDriver will call continueAnimation(...) on it. For a reason I do not yet understand, this doesn't always actually continue the animation. It seems that only with vigorous flicks the animation gets stuck, but all velocity-related properties are valid values (the velocity used in the AnimationTimingParameters, the fractionComplete upon moving to the animation phase, the durationFactor passed in continueAnimation(...)). Explicitly calling startAnimation() also doesn't make a difference.
Since the progressLayerAnimator isn't continued (nor is any other animation layer except the sharedElementAnimator), it never completes, and therefore the whole transition never completes.
I must say I'm unsure why this happens, and will continue to investigate in the moments I can spare time for it, which at the moment unfortunately isn't much. 🤞🏻

Release 1.1.0 packs several fixes for issues #5 #6 #1 which cover this issue too.


Add tags to existing guides

Summary
In order to make the best of the automated related resources section in the dev site, we need to tag existing guides. This is currently done via frontmatter under a tags key. We have a few pages already tagged. You can see an example for the Collect data from any source page.
#539 has a good approach for tagging that was done to test out tags and search
What type of documentation change are you suggesting?
Additional tags for existing guides.
Motivation
Tags will help influence related content for each page and should help us improve those results.

I added tags to all the pages that didn't have them... and committed them. Just realized someone might have liked to review those.

@mmfred what PR did you commit the tag changes in? I can glance at them now.


MTS implementation

Implementation, testcases and doc of algorithm in paper Lin-Yu Tseng and Chun Chen, 2008

Codecov Report

Merging #95 (15789a9) into master (80b76e4) will increase coverage by 1.97%.
The diff coverage is 95.69%.

@@            Coverage Diff             @@
##           master      #95      +/-   ##
==========================================
+ Coverage   68.42%   70.39%   +1.97%
==========================================
  Files          36       37       +1
  Lines        2714     2925     +211
==========================================
+ Hits         1857     2059     +202
- Misses        857      866       +9

Impacted Files
Coverage Δ

src/Nonconvex.jl
100.00% <ø> (ø)

src/algorithms/common.jl
84.09% <80.00%> (-1.21%)
:arrow_down:

src/algorithms/mts.jl
96.37% <96.37%> (ø)

src/models/vec_model.jl
72.34% <100.00%> (+3.29%)
:arrow_up:

src/wrappers/hyperopt.jl
93.50% <100.00%> (ø)

src/wrappers/percival.jl
83.07% <0.00%> (+0.81%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80b76e4...15789a9. Read the comment docs.

Looks good overall. I left a few minor comments.


KDL 2.0 compliance

KDL 2.0.0-draft.3 is now generally available (https://github.com/kdl-org/kdl/pull/286), and with it, we've decided to encourage existing implementations to start working towards 2.0 support and send feedback and suggestions for anything you might run into, so I'm making this tracking issue. :)

KDL 2.0.0 has been released (https://github.com/kdl-org/kdl/releases/tag/2.0.0)

Nice, I'll look into updating this grammar soon w/ those changes. I'd probably keep the grammar backwards-compatible for v1


can't use s3 in contabo.com https://contabo.com/en/object-storage/

What type of bug is this?
Unexpected error
What subsystems are affected?
Standalone mode
What happened?

What operating system did you use?
ubuntu
Relevant log output and stack trace
No response
How can we reproduce the bug?
see this in slack

@xxaier We will fix it in v0.4, it will be released next week.
Thanks for your report.

Fixed in #2308  and will be released in v0.4


Create new post should initiate a "pull request" workflow

Note: The action of creating a new item should map onto the Github concept of a PR.

Create new item == create a branch
Submit item for review == Submit pull request
Mark as OK to go live == Approve and merge pull request
Publish == Master deployed

Acceptance criteria:

[ ] Creating a new post should create a branch in the repository
[ ] Branched items should be noted in the UI as "Draft"
[ ] A user can click a button to mark the post as "For review", flagging the branch as a PR that is ready for approval
[ ] A user can click a button to mark the post as "Ready to go live", approving the PR and merging it into master (but not actually live!).
[ ] A user can click a button to publish the post, deploying master.

Technicalities of when PR is merged in are up to implementer - the stuff I said are just suggestions - it might make some sense to simply use a comment on a PR to note if something is "good to go live" rather than merge at that point, but I'll let those that know best decide. :)

Some thoughts around this:
Right now the way we show entries in the list view, is looking at our config.yml, determining which collections we have and what folders/files they correspond to, and then loading those from the main branch of the repository.
This will still work fine for the "Published" cards in the list below the dashboard in this view: https://phae.github.io/netlify-sketch/
However, for the 3 columns of Drafts, Waiting for review, Waiting to go live - we need some other way of handling the git integration.
One idea: we pick a branch naming convention (netlify-cms-entry-2016-08-10-some-thing) that lets us generate this list by querying the branches in the repository.
This would handle the Drafts column.
I'm a bit in doubt about the two next columns, it seems that these columns would be pull requests from branches following our naming pattern, but how do we determine which ones are waiting for review and which one are waiting to go live?

Could you use the commit subject line or description + a naming convention to flag those other types of status?

Or git notes? 😕 https://git-scm.com/docs/git-notes


Support for other backCompat settings?

According to https://github.com/Khan/KaTeX/issues/664 , Jest sets document.compatMode = 'BackCompat' and there isn't an option to override.  This is not a great choice for modern web apps.  Could there be support for modifying this setting in configuration/command line?
(I'm coming from the KaTeX development side, so I'm a little lost on the sense in which Jest even has a web browser in it... DOM simulation perhaps?  Apologies if this issue is actually farther upstream, or if there already is an option to override...)

Jest uses JSDOM to emulate browser environment and it doesn't actually work in real browsers currently. Currently we render nothing as a document, hence the quirk mode.
@cpojer any special reason, why we're doing this?
changing undefined to '<!DOCTYPE html> should fix this and doesn't break anything in our test suite.
this.document = require('jsdom').jsdom('<!DOCTYPE html>', {
  url: config.testURL,
});

@edemaine would you like to send a PR with that fix?

Duplicate of https://github.com/facebook/jest/issues/2460


fix(scanner): upload correct offline vulns for 4.5+

Description
Scanner release offline vulnerability bundle update was failing because in 4.5 we switched over from a vulns.json.zst file to a vulnerabilities.zip file. This was not accounted for in the offline vuln updater CI job. See https://github.com/stackrox/stackrox/actions/runs/9893807082/job/27329862714 for an example.
This PR checks for vulns.json.zst in 4.4, otherwise vulnerabilities.zip.
User-facing documentation

[x] CHANGELOG update is not needed
[x] Documentation is not needed

Testing

[x] inspected CI results

Automated testing

[x] contributed no automated tests

How I validated my change
Made this run on the PR prior to merge. You can see https://definitions.stackrox.io/v4/offline-bundles/scanner-v4-defs-4.5.zip is there, and it did not exist prior to this PR.

See similar workflow for a more idiomatic way of doing this.

Good idea. I made changes in https://github.com/stackrox/stackrox/pull/11970/commits/bfcbf67c8de3478c8dba060e507645526a8199d1 if you want to take another look


Blob field reading causes pointer being freed was not allocated error

I am tring to read a vector layer from geopackage data which has a blob field.
After reading several rows nodejs throw errors like this:
node(9501,0x10ce4edc0) malloc: *** error for object 0x102b23e50: pointer being freed was not allocated
node(9501,0x10ce4edc0) malloc: *** set a breakpoint in malloc_error_break to debug

When ignore the blob field, everything is ok.

@warrenwyf Can you post the code and the file that reproduces the issue?

@warrenwyf Can you post the code and the file that reproduces the issue?

const gdal = require('gdal-next');

const srcDataset = gdal.open(require.resolve('./points.gpkg'));
const layer = srcDataset.layers.get(0);

let feature,
  count = 0;
while (feature = layer.features.next()) {
  count++;

  const obj = { geom: feature.getGeometry().toWKB() };

  obj['name'] = feature.fields.get('name');
  obj['blob'] = feature.fields.get('blob');

  console.log(obj);
}

console.log(count);

Unzip the attachment, save the script, and run it.
points.gpkg.zip
What I got:

@warrenwyf Thanks - seems pretty straightforward, I'll put this on my TODO list and try to look into it this weekend or at the start of next week.

https://github.com/contra/node-gdal-next/pull/33


MSID: 98747 Version: 1 DOI: 10.1101/2<IP_ADDRESS>2588

MSID: 98747
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2588
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98747
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2588

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98747v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2588
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98747/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [article-email-corresp-author-count-equivalence] The number of corresponding authors (2: Syeda Nayab Fatima Abidi; Christian W Siebel) is not equal to the number of distinct email addresses (1: abidis1@gene.com). Is this correct?


t.classList is undefined sidebar.js:335:12

After replacing
<EMAIL_ADDRESS>(v4)
by
https://unpkg.com/@coreui/coreui@3.0.0/dist/js/coreui.min.js(v3)
since i been using version 3 and not version 4
the sidebar dropdown is broken, i get this error below
Uncaught TypeError: t.classList is undefined
sidebar.js:335:12
I think its a versioning problem, anyone knows which v3 is currently working, thank you

fixed by using v3.4.0 instead
https://unpkg.com/@coreui/coreui@3.4.0/dist/js/coreui.min.js(v3.4.0)


Fix panic with  double close() of channel on /-/quit/

Fix #8144
=== RUN   TestHandleMultipleQuitRequests
    web_test.go:492:
        	Error Trace:	web_test.go:492
        	            				asm_amd64.s:1374
        	Error:      	Received unexpected error:
        	            	Post "http://localhost:9090/-/quit": EOF
        	Test:       	TestHandleMultipleQuitRequests
    web_test.go:492:
        	Error Trace:	web_test.go:492
        	            				asm_amd64.s:1374
        	Error:      	Received unexpected error:
        	            	Post "http://localhost:9090/-/quit": EOF
        	Test:       	TestHandleMultipleQuitRequests
--- FAIL: TestHandleMultipleQuitRequests (5.00s)
FAIL
FAIL	github.com/prometheus/prometheus/web	5.026s
FAIL

Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

:+1:


Pushing back to view 1 shows up a blank map page

I'm submitting a ...  (check one with "x")
[ X ] question
[ ] any problem or bug report
[ ] feature request
The plugin version:  (check one with "x")
[ X ] 2.0-beta3 (github)
[ ] 2.0 (npm)
If you choose 'problem or bug report', please select OS:  (check one with "x")
[ ] Android
[ X ] iOS
I have an ionic app where in view 1 I have the map, when I push view 1 to view 2 then when I try to go from view 2 to view 1 I get a blank view !
I believe the reason is that the map has a unique id and when pushing from view 2 to view 1 maybe it create another map with the same it (or something like this....)

Please share your project files on github.
I'm really busy person. Please save my time as much as possible.

Here is it on BitBucket, you may reproduce the issue<EMAIL_ADDRESS>

Thank you. I appreciate.

Could you upload package.json file?
I need to install the package one by one.

Done

True, just discovered that, but that doesn't cause the issue.
I've already edited it and posted a commit, please update app.module.ts

I can only see these commits. Did you push it?

Yes, can yo please your app.module.ts ?

This is the correct one anyway :
    import { BrowserModule } from '@angular/platform-browser';
    import { ErrorHandler, NgModule } from '@angular/core';
    import { IonicApp, IonicErrorHandler, IonicModule } from 'ionic-angular';
    import { SplashScreen } from '@ionic-native/splash-screen';
    import { StatusBar } from '@ionic-native/status-bar';
    import { MyApp } from './app.component';
    import { HomePage } from '../pages/home/home';
    import { AboutPage } from '../pages/about/about';
    import { GoogleMaps, Geocoder } from '@ionic-native/google-maps'

    @NgModule({
      declarations: [
        MyApp,
        HomePage
      ],
      imports: [
        BrowserModule,
        IonicModule.forRoot(MyApp)
      ],
      bootstrap: [IonicApp],
      entryComponents: [
        MyApp,
        HomePage,
        AboutPage
      ],
      providers: [
        StatusBar,
        SplashScreen,
        {provide: ErrorHandler, useClass: IonicErrorHandler},
        GoogleMaps,
        Geocoder
      ]
    })
    export class AppModule {}`

Yes, there is the same file (I just git pull and run it), but I still get the error.
Please prepare the perfect work project files.

That's weird, I don't get that error at all, I have the exact same project files

Sorry, I'm not ionic user.
Until you solve this error, I can not test your app.

Can you please try to re-create it again, I am using the same repo in my local machine and it runs with no issues

Okay, I got the reason. This error occurs when I reload your app from the web inspector.
However, your app runs fast, so without reloading, I can not see the console.log.

In your code,
  constructor(private googleMaps: GoogleMaps, public platform: Platform, public navCtrl:NavController,private reverseGeocode : Geocoder) {

    // Wait the native plugin is ready.
    platform.ready().then(() => {
          this.mapElement = document.getElementById('map');  <-- This might be null because view is not ready.
      this.loadMap();

         this.map.addEventListener(GoogleMapsEvent.CAMERA_MOVE_START).subscribe((position)=>{
          console.log('Lat ', position.target.lat, ' lng ', position.target.lng)
         })

    });

  }

Got it, but did you discover the issue ?
this.mapElement = document.getElementById('map'); is placed inside platform.ready().then() to ensure that the DOM is fully loaded.

platform.ready().then() is not guaranteed to complete thr view, because it is the wrapper of the deviceready event of cordova.
ionViewEntered is the signal that DOM is ready completely.

I also tried to put this.mapElement = document.getElementById('map'); inside ionViewDidEnter but it didn't work, you may try it in the repo you have

Unfortunately your app does not runbat all.
I can not see anything on your app, only white page.
And if I reload your app, I get the error.
So how can I debug your app?????
Until you fix the error when I reload your app, I don't work for this anymore. I'm so busy person. I can not waste my time further.

After several hours I found that the homePage has lazyLoading, I removed it and it worked fine !
Thanks for your time and for this great plugin !

You are welcome. I appreciate if you buy me a beer


Improve compiler.

Codecov Report

Merging #33 (6e0af87) into main (8ba1308) will decrease coverage by 1.42%.
The diff coverage is 41.05%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
- Coverage   57.12%   55.70%   -1.43%
==========================================
  Files          10       10
  Lines         835      921      +86
  Branches      384      425      +41
==========================================
+ Hits          477      513      +36
- Misses         46       74      +28
- Partials      312      334      +22

Impacted Files
Coverage Δ

include/lisp/evaluator.h
57.79% <ø> (ø)

include/lisp/vm.h
83.87% <ø> (ø)

src/vm.cpp
56.15% <38.77%> (-9.76%)
:arrow_down:

src/compiler.cpp
52.38% <43.47%> (-5.12%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ba1308...6e0af87. Read the comment docs.


allow prefix to also be used as args in kue-dashboard script

kue-dashboard script should allow the user define the prefix of queue

There is PR for this https://github.com/Automattic/kue/pull/1028/files

merged @rturk


virustotalv3:feature - add reputation checks cache

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ x] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ x] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ x] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

There is now the option of caching the results of reputation checks actions.

In the asset configuration page, there are three(3) new options.

boolean - "cache_reputation_checks" - enables or disable caching
numeric - "cache_expiration_interval" - how many seconds until the cached entry expires and is purged
numeric - "cache_size" - maximum number of entries in cache

Cached entries are stored in the asset state file across invocations, so management of the cache_expiration_interval and
cache_size is important. If the cache grows too large it will affect execution times of the action.
Two new actions are provided:

clear cache- purges all entries. from the cache
get cached entries - reports back the state of the cache

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

all reputation checks
What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Closing because of changes. Now its pull request #16


No tests are run during the release job

Describe the bug
We probably should run tests against a release that is being cut. It would be possible for the build to be failing on main, but a release workflow would complete with no errors.
Relying on PR runs will allow a certain class of bugs to get through, as it is possible for a bug to be on main that was the result of a PR merge.

Fixed.


Added "Rule Break"

Added ability to add custom options for line breaks after each rule. Some front end developers prefer an additional line break after reach rule for enhanced readability.
My experience in Python is very limited, so I apologize in advance.

I'd love to see this merged!

+1 for this.

+1 as this is the only thing I feel this plugin lacks. It's the best CSS formatter for Sublime Text I've found, but I'd like expand-bs not to force linebreaks between rules.

First of all, I am very sorry that I have been especially busy in the past two years to deal with this problem until now.
Thank you very much for your patience, and the code you submitted has been merged.


GPG smart card not working

GPG not working when using smart card.
gpg: apdu_open_reader: failed to open driver `libpcsclite.so.1': libpcsclite.so.1: cannot open shared object file: No such file or directory
gpg: card reader not available
gpg: OpenPGP card not available: general error

Expected to fetch information from smart card.
Tested on Microsoft Windows [Version 10.0.14393]
Steps to reproduce:
gpg --card-status

@XIAZY - Thanks for using WSL and the feedback. Unfortunately, hardware devices such as USB card reader, GPU etc. not yet exposed and supported by WSL. For example, see the user voice post for supporting USB drives and this one for GPU. If you would like to see better support for smart card reader, we would recommend opening up a new user voice post for that (if there is not one already). We definitely look at our user voice page for prioritizing feature implementation.

Thank you. I just voted to libusb and smart card support. Shall I leave this issue open?
2016年12月19日 -0500 PM6:13 Sunil Muthuswamy<EMAIL_ADDRESS>@XIAZYhttps://github.com/XIAZY - Thanks for using WSL and the feedback. Unfortunately, hardware devices such as USB card reader, GPU etc. not yet exposed and supported by WSL. For example, see the user voice post for supporting USB driveshttps://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13717092-mount-usb-sd-removable-storage-devices and thishttps://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/16108045-opencl-cuda-gpu-support one for GPU. If you would like to see better support for smart card reader, we would recommend opening up a new user voice post for that (if there is not one already). We definitely look at our user voice page for prioritizing feature implementation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BashOnWindows/issues/1521#issuecomment-268106238, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIVPXzBtRBmqSePIGviEOn4--EEZxYc4ks5rJw-XgaJpZM4LRP0z.

Thanks! Yes, feel free to leave this open. I have already marked it with the "feature" tag.

Thanks. I am marking this duplicate of #412 and closing it out. Let me know if that does not cover the use case here and I am happy to reopen this one.

Will WSL2 be the remedy?

@mdddev Considering it has access to system calls, I'm inclined to say yes, but I am only updating now.


warning: setlocale: LC_ALL: cannot change locale (en-US) on linux

Brief Issue Summary
When compiling my code using cmake and Ninja generator, i get the following warning
[build] [435/436  99% :: 19.510] Linking CXX executable puzzle/puzzle
[build] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US)
[build] [435/436  99% :: 19.554] Linking CXX shared library vendor/bullet3/src/BulletSoftBody/libBulletSoftBody.so.3.05
[build] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US)
[build] [436/436 100% :: 19.565] Creating library symlink vendor/bullet3/src/BulletSoftBody/libBulletSoftBody.so
[build] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US)
[build] Build finished with exit code 0

It appears after every line and is very annoying.
When building from command line, i dont have issues like this, and it works great.
This warning makes sense as en-US is not a locale available in my linux environment. Why is it attempting to set it ? I have the following available
λ ~/src/c-gamedev/ master* locale -a
C
en_US.utf8
POSIX

This is the command that it builds with
[main] Building folder: c-gamedev
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/djmittens/src/c-gamedev/build --config Debug --target all -- -j 14

Im closing this issue because it turns out to be an issue with electron,
here is a link that has a solution in it, in case someone else runs into this.
https://github.com/microsoft/vscode/issues/110491

Thank you for linking to the solution.


refresh data locales & get locales

i'll add reload feature in next version.
Thank you for pull request.


Body Diagram on Home page should be selectable using keyboard

Users should be able to interact with the body diagram (scroll through items in organ list) using 'tab' on the keyboard.

Obsolete


[WIP] Reduce device memory alignment size

Not sure if there's any other design decisions that I overlooked, but according to @jrhemstad in https://github.com/cupy/cupy/pull/3212#discussion_r396686736 the documented alignment is 256 bytes, not 512 bytes.
Also, it seems like 512 is hard-coded in pinned memory as well? I didn't touch it in this PR, though.
@okuta Any comments? I'm trying to tracing back to the original commit. Thanks.

TODO: measure performance changes, if any.

Original PR: #176

at least 256 bytes. Does this means that 512 is valid too?

I have no idea! Jake said it is unsafe to rely on it being anything larger. @jrhemstad could you enlighten us when you have time? The alignment size in CuPy was set almost 3 years ago, and it doesn't seem we hit any issue for that.

If something is aligned to 512 bytes, won't it be aligned to 256 bytes too?

I should add that using the code mentioned in the old changes https://github.com/cupy/cupy/pull/3219/files#diff-0cb5dfa3212da5a58c698548f2df2f68L680, I also see 512 bytes for a Tesla V100. Checking for cudaDeviceProp.textureAlignment seems to confirm that too:
Using Device 0: Tesla V100-SXM2-32GB
cudaDeviceProp.textureAlignment: 512
Alignment: 512

I must say that @jrhemstad works much more in the memory level than I do, so he may have additional information that I don't regarding alignment, so we should wait for his comment before deciding how to proceed with this PR.

To be clear, 512B is a perfectly valid alignment within the requirement that device memory allocations always be at least 256B aligned (any power of two larger than 256B is valid).
So if CuPy's allocator is aligning to 512B, that's perfectly okay!
However, what is unsafe is relying on the pointer returned from any variant of cudaMalloc to have an alignment larger than 256B.

What @jrhemstad said makes sense, the problem is indeed the assumption that cudaMalloc will be aligned to at least 512 bytes. Therefore, the change makes sense.

Thanks, Jake & Peter, for the discussion! I tried to see if this has any performance impact, but I didn't see any. Do you folks have good suggestion or insight for what workload would make the alignment change differ a lot in performance?

Thanks, Jake & Peter, for the discussion! I tried to see if this has any performance impact, but I didn't see any. Do you folks have good suggestion or insight for what workload would make the alignment change differ a lot in performance?

I would very surprised if this change had any impact on performance. There's no GPU instruction I'm aware of that works on 512B alignment but doesn't work on 256B alignment.

I see, thanks for confirming, Jake!
We used to have an issue with the struct for complex numbers not properly aligned, and it hurt the performance by a lot. But we fixed it a while ago, and even for that case the needed alignment was less than 256B, so as you said nothing should be impacted by this change.

If nothing is impacted by this change, is it ok if we don't merge it?

Yeah I am fine with closing it, but just for my curiosity, @emcastillo could you kick off the CI for me and see if this change induces any error?

Let’s roll
Jenkins, test this please

Jenkins CI test (for commit 9c459a5edf78bced3482e85d0a5bc56c7d9db499, target branch master) failed with status FAILURE.

Thanks, Emilio! Looks like those are simple bookkeeping errors. Closing this PR. Also thanks to everyone for joining the discussion 🙏


memcached: 1.5.18 -> 1.5.19

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/memcached/versions.
meta.description for memcached is: '"A distributed memory object caching system"'.
meta.homepage for memcached is: '"http://memcached.org/"

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

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

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

found 1.5.19 with grep in /nix/store/miiwdlq19wmapx1k70cn8n0vv7wb02sj-memcached-1.5.19

directory tree listing: https://gist.github.com/8344d7961c86d2eb860ec5965c3116d4

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

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
memcached

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/miiwdlq19wmapx1k70cn8n0vv7wb02sj-memcached-1.5.19 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A memcached https://github.com/r-ryantm/nixpkgs/archive/a08a84d70e35d7bcea8be25ca705bea7ae5355bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/miiwdlq19wmapx1k70cn8n0vv7wb02sj-memcached-1.5.19
ls -la /nix/store/miiwdlq19wmapx1k70cn8n0vv7wb02sj-memcached-1.5.19/bin

cc @coreyoconnor for testing.

@GrahamcOfBorg test memcached


generate.sh run into error: expected value of type 'NoneType or depset' for parameter 'user_compile_flags'

Hi, there,
I'm trying to run this tool on the bazel cpp tutorial project.
Here is my command to reproduce the error:
$git clone git clone https://github.com/bazelbuild/examples/
$cd examples/cpp-tutorial/stage1
$curl -L https://github.com/grailbio/bazel-compilation-database/archive/0.3.3.tar.gz | tar -xz
$./bazel-compilation-database-0.3.3/generate.sh
ERROR: /playground/bazel_examples/cpp-tutorial/stage1/main/BUILD:1:1: in //bazel-compilation-database-0.3.3:aspects.bzl%compilation_database_aspect aspect on cc_binary rule //main:hello-world:
Traceback (most recent call last):
	File "/playground/bazel_examples/cpp-tutorial/stage1/main/BUILD", line 1
		//bazel-compilation-database-0.3.3:aspects.bzl%compilation_database_aspect(...)
	File "/playground/bazel_examples/cpp-tutorial/stage1/bazel-compilation-database-0.3.3/aspects.bzl", line 88, in _compilation_database_aspect_impl
		cc_common.create_compile_variables(feature_configuration = feature_..., <2 more arguments>)
expected value of type 'NoneType or depset' for parameter 'user_compile_flags', in method call create_compile_variables(feature_configuration feature_configuration, CcToolchainInfo cc_toolchain, list user_compile_flags) of 'cc_common'
ERROR: Analysis of aspect '//bazel-compilation-database-0.3.3:aspects.bzl%compilation_database_aspect of //main:hello-world' failed; build aborted: Analysis of target '//main:hello-world' failed; build aborted
INFO: Elapsed time: 0.059s
INFO: 0 processes.

And my environment is Ubuntu 16.04 and bazel version 0.17.2.

It seems my old version 0.17.2 has some compatible issue. The user_compile_flags requires depset type in the 0.17.2 version but the passed value is a list. It could be solved by:

upgrade the bazel to latest verion (0.24).
wrap the ctx.fragments.cpp.copts list by depset in aspects.bzl

 88    compile_variables = cc_common.create_compile_variables(
 89        feature_configuration = feature_configuration,
 90        cc_toolchain = cc_toolchain,
 91        user_compile_flags = depset(ctx.fragments.cpp.copts),
 92    )

Thanks! I suspected as much. I do not make this project backward compatible with older versions of bazel, and I am not tracking the minimum supported bazel version. Thank you for your patience.

My pleasure:) And thanks for your project!
And one more question is why Bazel don't have the compilation database generation feature officially?


Support Delta Lake DeleteCommand

Fixes #7281.
This adds support for deleting data from Delta Lake tables via the DeleteCommand physical plan node.  Code is derived from DeleteCommand.scala in the https://github.com/delta-io/delta project for the various versions we support, and adapted the same code for Databricks based on visible semantics of the behavior.
This implementation is relatively straightforward, mostly using the same logic as the CPU with the following changes:

Creating a GpuOptimisticTransaction so the writeFiles call is leveraging a GPU columnar write rather than a CPU write.
Leveraging equivalent RAPIDS accelerated UDFs for updating SQL metrics to avoid falling back to the CPU for the original CPU UDFs.

I realize this is a bit late for 23.02, but posting it for that release per a request from @sameerz.  New functionality is specific to Delta Lake, does not touch code outside of Delta Lake support, and is disabled by default.

build

build

CI failed in 312db due to:
[2023-02-01T14:55:01.282Z] Traceback (most recent call last):
[2023-02-01T14:55:01.283Z]   File "/home/ubuntu/spark-rapids/integration_tests/runtests.py", line 17, in <module>
[2023-02-01T14:55:01.283Z]     from pytest import main
[2023-02-01T14:55:01.283Z] ModuleNotFoundError: No module named 'pytest'

rekicking.

build

build

build

build


⚠ Bofrost.lu has degraded performance

In 00187c7, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1369 ms

Resolved: Bofrost.lu performance has improved in 490f7cb.


Fixed 3 broken links.

Using relative links --
Services/getting-started-with-cam-enable-managed-provider.md), [Automatic Discovery of Resources](../../Cloud Application Manager/Getting Started/register-existing-instance.md) and [Analytics](../../Cloud Application Manager/Analytics/cloudapplicationmanageranalyticsui.md). The services toggles that were available in the Edit Provider dialog has been moved to a new tab called Services in the provider details page, where you can manage them and see additional details such as the status of your Managed Services Anywhere enabled locations.


feature request: determine timezone offset for local timestamp

I'd like a feature where I submit a date and local time (without a timezone) and get, if possible, the timezone for this time and/or a fully tz-aware timestamp.
This is a bit ugly since it has edge cases: timestamps can either not be valid or ambigious, e.g. when they fall in a DST switch. For me, erroring out would be acceptable behavior in both cases.

I'm not sure I understand. If you have a date like 2017-06-24 and a time like 10:00 then it could be in any timezone. What is the piece of information you want to use to determine which timezone it's in?

Sorry –  in combination with a location of course. Right now I can get from a location query like /api/geocode?input=Portland,+OR  or http://atlas.p3k.io/api/timezone?latitude=45.5118&longitude=-122.6433 the local time and timezone offset right now, but not the timezone for a local time in the future (which might be different due to DST).

Gotcha, yes that'd be great. I think this would make the most sense as another parameter to the /timezone API call, e.g.
http://atlas.p3k.io/api/timezone?latitude=45.5118&longitude=-122.6433&localtime=2017-06-24T10:00:00

which also suggests the /timezone API should accept a text input that is first run through the geocoder. technically that's basically the /geocode API but being able to request a local time would make sense to happen here


Issues with ovs on dell servers

I was trying to install OpenNESS 20.06 which was released recently. I tried this on two different kind of servers. There are two setups, one is with server1(node) and other with server(2). In both cases the controller is a VM.
Now the issue is in server 1, the installation is successful with all the bridges getting created and are properly working.
But the second server(dell 640 power edge) is behaving a little strange. The installation is successful but the brodges are not getting created and are getting destroyed. The ovs bridge is not stable in this one. Most of the times it is unable to find the db.sock which hampers with the pods creation.
In the previos versions too we have faced similar problems.
The server details are as below
1st Node server details (pizza box server)
Manufacturer : Boston supermicro server
Product name : sys-6019p-mit
Bios revision: 5.14
Vendor: american megatrends inc
Os  centos 7.6.1810
Hdd 256 gb
Ram 64 gb
2nd node server details(dell poweredge 640 series)
Dell server
Intel xeon gold 6226 processors
2.7 ghz 12 cores 24 threads
19.25m cache, 3.7 max turbo frequency
64 gb , 1tb hdd
Quad port 10G nics
Os centos7.6.1810
Could someone please help. If more details or logs are required let me know. Thanks

Hi @archie95, Can you list all the pods running in the cluster and the logs of the failing pods?
$ kubectl get pods -A -o wide
$ kubectl describe <failing-pod-name> -n <namespace>
$ kubectl logs <failing-pod-name> -n <namespace>

Following are the screenshots from our setup which you asked for:
Image 1 shows the output of command "ovs-vsctl show" on workernode(Supermicro server) where OpenNESS setup is working fine.

image 1
Image 2 shows the output of above command on dell server.

image 2
Image 3  shows the output of "kubectl get pods -A -o wide"

image 3
Image for shows logs for ovs-ovn pod

image 4
Image 5 shows logs for kube-ovn-cni pod

image 5)

@amr-mokhtar please find above the logs and details from our setup. @mehashu has uploaded them on my behalf. As you can see the ovs is not running at the node end. Even after manually starting it, the liveliness remains for a very short period.

@amr-mokhtar We were able to bypass the issue on dell servers by disabling the use of kubeovn with dpdk in group_vars/all/10-defaults.yaml. On debugging the issue in ovs, we found certain discrepancies in the logs. We suspect that the issue is regarding dpdk socket mem allocation. Please find attached the ovs-vswitchd.log and the error line.

Hello,
This issue might be caused because of wrong memory settings.
I can see from the logs that your server has 2 NUMA nodes:
2020-07-05T12:08:20.649Z|00015|dpdk|INFO|EAL : Detected 2 NUMA nodes
I am wondering if a configuration in
https://github.com/open-ness/openness-experience-kits/blob/master/group_vars/all/10-default.yml#L104
takes this into account.
It should be something like:
kubeovn_dpdk_socket_mem: "1024,1024"
Can you please try with the memory set for the second NUMA node?
Thanks,
Krzysztof

Hi Krzysztof,
We tried setting the above configuration as suggested by you but we are still facing the same issue. Please find attached the ovs-vswitchd.log .

Regards,
Archit

Hi Archit,
Can we ask for all of your configuration files?
It might be a risk that there is not enough memory for huge pages, I would recommend setting 2G for each of those 2 NUMA nodes.
2048,2048 instead of 1024,1024.
Thanks,
Krzysztof

Hi Krzysztof,
We tried setting the above parameters as recommended by you, but getting timeout errors due to pending ovs-ovn pods. I will be attaching the configuration files and logs for your perusal.
Regards,
Archit
10-default_controller.txt
10-default_edgenode.txt
10-default_all.txt

ansible logs.txt

Hi Archit,
Could you do some changes to your configuration and check if that is fine?
Overall let the configuration should be like that:
Hugepage configuration for NUMA nodes in MB, i.e. "1st_numa_memory,2nd_numa_memory"
kubeovn_dpdk_socket_mem: "1024,1024"
Core bitmask for datapath packet processing. 0x4 selects core 2
kubeovn_dpdk_pmd_cpu_mask: "0x4"
Core bitmask for DPDK initialization. 0x2 selects core 1
kubeovn_dpdk_lcore_mask: "0x2"
Hugepage size to be used with DPDK: 2Mi or 1Gi
kubeovn_dpdk_hugepage_size: "1Gi"
Overall amount of hugepages available to DPDK
kubeovn_dpdk_hugepages: "4Gi"
OVS pods memory resource requests
kubeovn_dpdk_resources_requests: "2Gi"
OVS pods memory resource limits
kubeovn_dpdk_resources_limits: "2Gi"
Thanks,
Krzysztof

Hi Krzysztof,
Thank you so much for your help. The bridges are getting created now. The issue was because of hugepages only. Using the above configurations we were able to install OpenNESS 20.06 on dell servers. You may please go ahead and close this issue.
Thanks and Regards,
Archit


Angular 2 + Zone.js + Common js module: IF statement anomaly, code is executed even in false case

I tried a ton of checks. This definitely is an anomaly. I have an Angular 2 service that loads a @type definition (typescript 2) which in turn loads a commmon.js module (visionmedia/debug). Inside the common.js module I have a simple if statement that triggers an error even if the condition is false and code should not be executed. I used system.js to import modules in my app.
Regular Code if (false) { console.log('This code is not executed') }
Normal behavior, nothing happens
Anomaly Code: if (false) { exports.humanize = require('ms'); } It triggers
Error: zone.js:101 GET http://localhost:8002/ms.js 404 (Not Found)
The error itself is valid. Indeed that script is not to be found. What is deeply wrong is that it should not appear in the first place. It should be blocked by the false if condition. It seems to me that zone.js somehow parses the the instruction even if the case is false. What can I do to avoid this? I need to check wheter to require one path or another depending if the same script is called on server or on frontend.
Bigger picture inside the CJS module:
// Trying to detect if environment is node.js
// In backend (no zones) everything works as expected
// In frontend, the require('ms') statement is executed event if condition is false.
// I checked manually if process is defined, it's not.
// Event the basic `false` condition also fails to block code.
if (typeof process === 'undefined') {
    exports.humanize = require('node_modules/ms/index.js');
    console.log('Browser');
} else {
    exports.humanize = require('ms'); // If I comment this code works as intended
    console.log('Node');
}

Issue solved. It looks like zone.js has nothing to do with this issue. I have received help from system.js comunity. Check this answer.
@guybedford

This is the way that dependency analysis in SystemJS works via static parsing of CommonJS requires - it is the only way to make CommonJS support asynchronous loading. Try adding:

System.config({
	map: {
		ms: '@empty'
	}
});


Cannot successfully install with Obsidian 1.4.13

After upgrading to Obsidian 1.4.13, I cannot get this plugin to install any more (it was working in a previous version of Obsidian).
When I install the plugin, Obsidian says it successfully installed it, however it does not show in the list of installed plugins and I cannot connect via the local rest API through either https://coddingtonbear.github.io/obsidian-local-rest-api/ or the Obsidian Web chrome plugin.
Other community plugins install correctly.
The Obsidian developer console shows these errors, prior to the attempted installation, not sure if those are 'normal' errors or whether something is messed up in my install:
app.js:1 SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at e.<anonymous> (app.js:1:2032250)
    at app.js:1:237030
    at Object.next (app.js:1:237135)
    at a (app.js:1:235853)
(anonymous) @ app.js:1
app.js:1 SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at t.<anonymous> (app.js:1:706510)
    at app.js:1:237030
    at Object.next (app.js:1:237135)
    at a (app.js:1:235853)

Has anyone been successful with 1.4.13? Or perhaps something is messed up in my installation?

I updated to Obsidian 1.4.14 and the problem went away. Closing this. Thanks for this plugin!


Garbage characters in File menu

I think that's supposed to be the down-arrow symbol for the drop-down menu. This happened just after loggin in. I think I've seen that before, may be systematic. Reloading fixes it.


feat(example): add new example template

Description:

I think make the icons colorful and add some styles to the Getting Started would be better


Support for callback function

Is it possible to have a function which is called every iteration? And is it possible to make a break condition based on the output of that function?

Well, I was thinking maybe I could write the chain to file as I'm going along, or maybe calculate some other quantity every x steps, or maybe implement some kind of early stopping criterion. Right now I've been bootstrapping it by putting that all into the log likelihood function which isn't that elegant.


[Proposal] Setup unit tests to cover model configurations

Proposal
The model configuration needs to be tested to make sure that they are able to loaded by the hooked transformer.
Motivation
To test model configuration in isolation.
Pitch
Alternatives
Additional context
The configurations are already all being tested in a way via the build docs script. This loads the models configs into a table, and sometimes generates errors. The unit test should be very similar to this, and it should use the same array as the basis for the test params in order to make it easy to identify when a model is misconfigured.
Checklist

[x] I have checked that there is no similar issue in the repo (required)

Will set these up


Live stage downtime

Sometimes I notice my lambdas are called but no invocation is logged in the local sst dev log. It is not that the log fails, but rather the connection between the lambda and the local server that silently fails. Just restarting the sst dev process fixes the issue, but it is not always clear when it is happening.
Any ideas why this happens?
Also, given usage reports and observed behavior, it seems that the lambdas that failed to call home keep running doing nothing up until their timeout, which in some cases, is very wasteful. Even if the server is restarted, running lambdas wait all their timeout before trying to connect again.
Maybe this can be improved somehow?
Some ideas:

Short bridge timeout, aborting earlier with clear feedback
When the local server restarts, if the bridge is still running it should connect right away
Make the bridge return ok to avoid stuck retry loops
Sum of the above, but configurable

* This has been happening with several versions, but I have yet to test 0.0.403.
** Not sure if it is the correct term, but by "bridge" I mean the code that the lambda executes in live mode to connect with the local server.

Yeah I guess let's first figure out why the connection is getting dropped. Can you share some logs for when that happens? Both on the Cloudwatch side and locally?
Or if you have any clues as to when this happens. Are you leaving the CLI running overnight?

Can you share some logs for when that happens? Both on the Cloudwatch side and locally?

Ok, I'll look for it next time it happens.

Or if you have any clues as to when this happens. Are you leaving the CLI running overnight?

Not overnight, just normal usage for a few hours.
* But some of the suggestions above came from an unfortunate incident from my initial experimentations where I left in a hurry and didn't notice the sst remove failed, so a single lone sqs message with a consumer without proper redrive kept tearing my dev account free tier and gave me an unexpected bill, so it would be nice to have a more budget-friendly behavior when the dev server for a live stage is not running. If you want to focus this issue on the disconnection issue, I preffer to open another issue for this portion instead. Please let me know.

It disconnects quite often for me too, not sure why.
✓  No changes
   api: https://******.lambda-url.us-east-1.on.aws/

time=2024-06-06T15:31:54.429+02:00 level=INFO msg="INFO unlocking app=*** stage=***"
time=2024-06-06T15:31:54.850+02:00 level=INFO msg="file event" path=***/sst-env.d.ts op=CHMOD
time=2024-06-06T15:31:54.850+02:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-06-06T15:31:54.850+02:00 level=INFO msg="checking if code needs to be rebuilt" file=***/sst-env.d.ts
time=2024-06-06T15:31:54.971+02:00 level=INFO msg="waiting for file changes"
time=2024-06-06T15:32:39.140+02:00 level=INFO msg="mqtt connection lost" error="websocket: close 1006 (abnormal closure): unexpected EOF"
time=2024-06-06T15:32:39.140+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:32:40.111+02:00 level=INFO msg="mqtt connected"
time=2024-06-06T15:33:40.115+02:00 level=INFO msg="mqtt connection lost" error="websocket: close 1006 (abnormal closure): unexpected EOF"
time=2024-06-06T15:33:40.117+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:33:41.021+02:00 level=INFO msg="mqtt connected"
time=2024-06-06T15:34:41.022+02:00 level=INFO msg="mqtt connection lost" error="websocket: close 1006 (abnormal closure): unexpected EOF"
time=2024-06-06T15:34:41.022+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:34:42.023+02:00 level=INFO msg="mqtt connected"
time=2024-06-06T15:35:42.029+02:00 level=INFO msg="mqtt connection lost" error="websocket: close 1006 (abnormal closure): unexpected EOF"
time=2024-06-06T15:35:42.030+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:35:42.942+02:00 level=INFO msg="mqtt connected"
time=2024-06-06T15:36:42.981+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:36:42.981+02:00 level=INFO msg="mqtt connection lost" error="websocket: close 1006 (abnormal closure): unexpected EOF"
time=2024-06-06T15:36:44.820+02:00 level=INFO msg="mqtt reconnecting"
time=2024-06-06T15:36:46.499+02:00 level=INFO msg="mqtt reconnecting"

hey was this resolved?

@thdxr Not sure, it looks like it was intermittent, but I have yet to experience it again since opening this issue. Was it addressed somehow in the later versions?

Might be, I'll close this for now. Feel free to reopen.

I am still having problems with lambdas not invoking the local live server. Here are the logs:
sst dev
time=2024-06-27T16:33:08.247-03:00 level=INFO msg=iot topic=ion/project/candrew/02ff98b3f7ed49efaa08b8f966b1667f/init
time=2024-06-27T16:33:08.247-03:00 level=INFO msg="running function" runtime=nodejs20.x functionID=CronEveryHourHandler
time=2024-06-27T16:33:08.247-03:00 level=INFO msg="starting worker" env="...redacted..."
time=2024-06-27T16:33:08.248-03:00 level=INFO msg="worker died" workerID=02ff98b3f7ed49efaa08b8f966b1667f

lambda cloudwatch
INIT_REPORT Init Duration: 10009.14 ms	Phase: init	Status: timeout
2024/06/27 19:33:06 INFO getting endpoint
2024/06/27 19:33:07 INFO found endpoint endpoint url="...redacted..."
2024/06/27 19:33:07 INFO signed request url="...redacted..."
2024/06/27 19:33:07 INFO connecting to iot clientID=02ff98b3f7ed49efaa08b8f966b1667f
2024/06/27 19:33:07 INFO mqtt connected
2024/06/27 19:33:07 INFO prefix prefix=ion/project/candrew/02ff98b3f7ed49efaa08b8f966b1667f
2024/06/27 19:33:07 INFO get lambda runtime api url=<IP_ADDRESS>:9001
2024/06/27 19:33:07 INFO connecting to lambda runtime api
2024/06/27 19:33:07 INFO waiting for response
INIT_REPORT Init Duration: 300022.10 ms	Phase: invoke	Status: timeout
START RequestId: 5a0a218a-1b42-49a9-bf7b-1004e9447011 Version: $LATEST
2024-06-27T19:38:06.127Z 5a0a218a-1b42-49a9-bf7b-1004e9447011 Task timed out after 300.04 seconds

END RequestId: 5a0a218a-1b42-49a9-bf7b-1004e9447011
REPORT RequestId: 5a0a218a-1b42-49a9-bf7b-1004e9447011	Duration: 300042.37 ms	Billed Duration: 300000 ms	Memory Size: 128 MB	Max Memory Used: 18 MB```

@jayair @thdxr Do the above logs have any useful info?


DNS resolution failed in dbless mode.

Recently, i often got an error below in dbless mode. It will return to noraml when restarting kong.

2020/01/09 12:05:19 [error] 42406#0: *151691 [lua] balancer.lua:917: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)upstream_8:(na) - cache-miss","upstream_8:33 - cache-miss/scheduled/querying/dns server error: 3 name error","upstream_8:1 - cache-miss/scheduled/querying/dns server error: 3 name error","upstream_8:5 - cache-miss/scheduled/querying/dns server error: 3 name error"], client: <IP_ADDRESS>, server: kong, request: "POST /hr/1 HTTP/1.1", host: "gateway.corp.com:8000"

@SunshineYang could you confirm which Kong version are you testing this with? Thanks!

@SunshineYang could you confirm which Kong version are you testing this with? Thanks!

1.4.0 and 1.4.1

@SunshineYang Does this happens in the beginning when your configuration is (re)loaded or after it is running for a while?
Also, does reloading the configuration (via the /config endpoint) fix the problem? (without having to restart Kong)

I'm not using Kubernetes. It happens after running for a while, and it will not fix unless restarting kong not reloading configuration via /config endpoint.

run into this after upgrade from 1.4.2 to 2.0.2 (db-less mode)
with the exact environment, exact amount of traffic, nothing changed except kong version
just after a while, log start flooding with DNS resolution failed: dns server error: 3 name error.
And the problem keep getting worse, eventually no request can be finished.
reproducible in our prod env
[ingress-kong-7679db7945-nd99v proxy] 2020/02/27 20:13:56 [error] 30#0: *1496 [lua] balancer.lua:921: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)vm-victoria-metrics-cluster-vminsert.zeus.http.svc:(na) - cache-miss","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.kong.svc.cluster.local:33 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.svc.cluster.local:33 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.cluster.local:33 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.maas:33 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc:33 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.kong.svc.cluster.local:1 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.svc.cluster.local:1 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.cluster.local:1 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.maas:1 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc:1 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.kong.svc.cluster.local:5 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.svc.cluster.local:5 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.cluster.local:5 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc.maas:5 - cache-hit/stale/in progress (async)/dns server error: 3 name error","vm-victoria-metrics-cluster-vminsert.zeus.http.svc:5 - cache-hit/stale/in progress (async)/dns server error: 3 name error"], client: **.**.**.**, server: kong, request: "POST /insert/999/prometheus HTTP/1.1", host: "*****"

wait, I think mine case was completely different.
the failing domain contains a wierd .http.
they should be vm-victoria-metrics-cluster-vminsert.zeus.svc.
/etc/resolve.conf looks good. No idea where this come from.
@hishamhm Any insight? I review recent code change but found nothing related...
I can confirm there is nothing changed but the kong image.

No idea where this come from.

@Ehekatl Kong doesn't concatenate segments to the DNS resolved values like that, so this must be coming from somewhere else... I spot .maas in your domains, perhaps it is MAAS's domain resolution configuration that is doing that? (I have no firsthand experience with it, but could be a place to look)

@hishamhm I've post the detail in https://github.com/Kong/kubernetes-ingress-controller/issues/560
I believe there are serveral issue involed:

for some reason, get_balancer can fail and return nil even though backend are health
e.g. In a db-less kong cluster, When I run into this problem, only one pod have the issue, the rest are good, which means other pods think the upstream have healthy targets.

when get_balancer fail and get nil result, kong start fail back to dns resolution, but seems it never switch back, when dns resolution is not working, it unable to recover from the loop

dns resolution fail because in db-less mode, kong ingress controller named service in domain.port format, result in unresolvable domain.

@Ehekatl,
Hi, I just discussed this with @javierguerragiraldez as we are investigating the issue. Thank you for the further info in that Kubernetes ticket.
I believe the problem lies in this commit:
https://github.com/Kong/kong/commit/5d8c87959cad18ae82518003199df010bc2c6a5c
If you change that line back to:
if last_equal_index == new_size and new_size > 0 then

Does it fix your issue?
I believe what it tried to fix is ok for the fix, but it needs to be reworked. I might be that:
new_size == old_size

may hold true but it still doesn't mean we should not apply the history. Or perhaps that:
and new_size > 0

Needs to be added back. @javierguerragiraldez is investigating it further, but if you can try to change the line to:
Before Fix
if last_equal_index == new_size and new_size > 0 then

and then try (which could fix the issue it tried, but not break what you are seeing):
if last_equal_index == new_size and new_size == old_size and new_size > 0 then

@bungle after changed to if last_equal_index == new_size and new_size == old_size and new_size > 0 then for several hours
we haven't found any issue so far.
but maybe need more testing (i.e. endpoint updates, ingress updates, etc)

@bungle @javierguerragiraldez
after running for 14 hours, it happens again on 2 of 5 kong pods.
really weird, the targets IP aren't change
I see no endpoints update in ingress controller log
still investigating, will try change it to if last_equal_index == new_size and new_size > 0 then and see

@bungle @javierguerragiraldez one more thing
when I use /upstreams/id/targets/all/ to check the upstream targets
I got Not Found once for every three requests ( while ingress controller have no log saying endpoint updates

got the same problem after change it to if last_equal_index == new_size and new_size > 0
seems unrelated...
I'm rolling back to 14.3

@Ehekatl great feedback! Let us know if it happens with 1.4.2 too.

@bungle it doesn't, it only happen after upgrade to a higher version

@Ehekatl
Hi~
Have you made progress since the last comment?
I also met the same problem.
I use kong 2.0.2 , ingress-controller:0.7.1, and dbless mode
I also use codedns in another namespace. There are no error log about this.
2020/03/24 01:25:54 [error] 23#0: *1497383 [lua] balancer.lua:921: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)service1.namespace.8080.svc:(na) - cache-miss","service1.namespace.8080.svc.namespace.svc.cluster.local:33 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.svc.cluster.local:33 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.cluster.local:33 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.openstacklocal:33 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc:33 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.namespace.svc.cluster.local:1 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.svc.cluster.local:1 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.cluster.local:1 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.openstacklocal:1 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc:1 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.namespace.svc.cluster.local:5 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.svc.cluster.local:5 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.cluster.local:5 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc.openstacklocal:5 - cache-hit/dns server error: 3 name error","service1.namespace.8080.svc:5 - cache-hit/dns server error: 3 name error"], client: <IP_ADDRESS>, server: kong, request: "GET /favicon.ico HTTP/1.1", host: "<IP_ADDRESS>", referrer: "http://<IP_ADDRESS>/api"

@novajung without luck, I'm sticking with 1.4.2 for now.

confirm that @SunshineYang 's approach does eliminate the issue
by change it to if dns_cache_only and target.balancer ~= nil then balancer = target.balancer

I think I figured out what the issue is, but I'm not familiar with the base code so I'll just share my findings, without creating a pull request yet.
In /kong/runloop/balancer.lua, when the cache key "balancer:upstreams" is being invalidated, inside get_all_upstreams the cache callback load_upstreams_dict_into_memory returns an empty dictionary, this value being saved into the cache.
If I force to invalidate the cache key again when the dictionary is empty it seems to work, on the next execute function call, though the first one will fail with "name resolution failed".
maybe you can judge better wether it should wait for singletons.db.upstreams to be re-populated or something to do with the cache TTL.
`get_all_upstreams = function()
local upstreams_dict, err = singletons.core_cache:get("balancer:upstreams", opts,
load_upstreams_dict_into_memory)
if err then
return nil, err
end
if #upstreams_dict == 0 then
  singletons.core_cache:invalidate_local("balancer:upstreams")
end

return upstreams_dict or {}

end`

@uflorin did you eliminate the issue with the above changes?
@bungle @Tieske @locao @hishamhm do you have any thoughts?

This is also an issue for us running Kong 2.0 in DBless mode inside of Kubernetes with 0.8.0 version of the ingress controller.

Same problem here. Using kong 2.0.3 db-less.
Kong tried to resolve my upstream as a DNS :(
errorlog.log

Re-opening for this comment: https://github.com/Kong/kubernetes-ingress-controller/issues/560#issuecomment-625018858

cc @guanlan

https://github.com/Kong/kong/pull/5926#issuecomment-632146319

Hi all,
We've verified the issue is reproducible on 2.0.4 (and below), but not reproducible on 2.1.0-alpha1. Here are the steps we took:

Run a Kong 2.0.4:

docker run -ti -d --name kong -e "KONG_DATABASE=off" \ -e "KONG_PROXY_LISTEN=<IP_ADDRESS>:8000" -e "KONG_ADMIN_LISTEN=<IP_ADDRESS>:8001" -e KONG_PROXY_ERROR_LOG=/logs/error.log -e KONG_PROXY_ACCESS_LOG=/dev/null \ -p 8000:8000 \ -p 8001:8001 \ -v "$PWD/logs:/logs" \ kong:2.0.4

Start a shell loop sending POST requests to /config:

for i in $(seq 1 500); do http :8001/config<EMAIL_ADDRESS>done

(Find kong.yaml here).

In a separate terminal window, send requests to the proxy port:

for i in $(seq 1 5000); do curl -s -o /dev/null -w "%{http_code}\n" localhost:8000; done

This will print the status code of all requests; lots of 503s will be seen. The logs in logs/error.log will contain errors like the following:
2020/06/01 15:52:18 [error] 22#0: *19380 [lua] balancer.lua:929: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)upstream1:(na) - cache-miss","upstream1:33 - cache-hit/dns server error: 3 name error","upstream1:1 - cache-hit/dns server error: 3 name error","upstream1:5 - cache-hit/dns server error: 3 name error"], client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "localhost:8000"

If the same is attempted against 2.1.0-alpha1 (or with Kong master branch), no 503s will occur.
Note that the issue is also not reproducible in Kong master, since it includes https://github.com/Kong/kong/pull/5831.
Once again, thanks for all the feedback on this!

This issued was fixed by https://github.com/Kong/kong/commit/29a731a7d7f442e104720a3ef6fbdc8ca44c9b13, present in master and 2.1-beta. Closing this as resolved.

Recently, i often got an error below in dbless mode. It will return to noraml when restarting kong.

2020/01/09 12:05:19 [error] 42406#0: *151691 [lua] balancer.lua:917: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)upstream_8:(na) - cache-miss","upstream_8:33 - cache-miss/scheduled/querying/dns server error: 3 name error","upstream_8:1 - cache-miss/scheduled/querying/dns server error: 3 name error","upstream_8:5 - cache-miss/scheduled/querying/dns server error: 3 name error"], client: <IP_ADDRESS>, server: kong, request: "POST /hr/1 HTTP/1.1", host: "gateway.corp.com:8000"

Has the problem been solved？

Sorry for commenting on the closed issue and also am using the older version of kong.
But i also faced the same in the plugin we have written for kong, can be viewed here:
https://github.com/Kong/kong/issues/6350

Still reproduced in my production environment with hybrid deployment mode (Kong version 2.1.3, deployed into kubernetes cluster).  I have five DP pods, and one of them ran into this error suddenly. Recreating pods fixed this issue temporarily, and I'm trying @Ehekatl's answer as a workaround.

Run into the same problem with DB-less mode(kong version 2.1.0).
After I add a service via admin API,  One of my three DP nodes got this error,  continued for more than  two minutes, then I delete the service via admin API, everything is well.
Maybe sync config between cp and dp lead to cache invalid, and cache is not rebuild or rebuild failed?

I think I figured out what the issue is, but I'm not familiar with the base code so I'll just share my findings, without creating a pull request yet.
In /kong/runloop/balancer.lua, when the cache key "balancer:upstreams" is being invalidated, inside get_all_upstreams the cache callback load_upstreams_dict_into_memory returns an empty dictionary, this value being saved into the cache.
If I force to invalidate the cache key again when the dictionary is empty it seems to work, on the next execute function call, though the first one will fail with "name resolution failed".
maybe you can judge better wether it should wait for singletons.db.upstreams to be re-populated or something to do with the cache TTL.
get_all_upstreams = function()
    local upstreams_dict, err = singletons.core_cache:get("balancer:upstreams", opts,
                                                load_upstreams_dict_into_memory)
    if err then
      return nil, err
    end

    if #upstreams_dict == 0 then
      singletons.core_cache:invalidate_local("balancer:upstreams")
    end

    return upstreams_dict or {}
  end

This will make traffic poxy pretty slow, tested :(

This issues has already been solved in commit https://github.com/Kong/kong/commit/dc8c1258aeed2a9649e9a4533ec575b1da16e488

Thanks for the update @huaerfan!
I'm closing this, feel free to reopen if the issue happens again.

how to solve this bug and not upgrade kong version ?
kong version: 1.2.1

Hello Guys,
Seeing the same issue in our environment, where we are running the Kong gateway in EKS with Postgres backend. The version of kong we are using is 2.3.3.
2021/04/06 21:25:05 [error] 24#0: *14737 [lua] balancer.lua:1071: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)testapp.v1.upstream:(na) - cache-miss","testapp.v1.upstream.kong.svc.cluster.local:33 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.svc.cluster.local:33 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.cluster.local:33 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.ec2.internal:33 - cache-hit/dns server error: 3 name error","testapp.v1.upstream:33 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.kong.svc.cluster.local:1 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.svc.cluster.local:1 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.cluster.local:1 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.ec2.internal:1 - cache-hit/dns server error: 3 name error","testapp.v1.upstream:1 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.kong.svc.cluster.local:5 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.svc.cluster.local:5 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.cluster.local:5 - cache-hit/dns server error: 3 name error","testapp.v1.upstream.ec2.internal:5 - cache-hit/dns server error: 3 name error","testapp.v1.upstream:5 - cache-hit/dns server error: 3 name error"], client: 172.x.x.x, server: kong, request: "GET /testapp/prod/testApp HTTP/1.1", host: "dev-private-api.services.7-eleven.com"
172.x.x.x - - [06/Apr/2021:21:25:05 +0000] "GET /testapp/prod/testApp HTTP/1.1" 503 36 "-" "Apache-HttpClient/4.5.10 (Java/11.0.10)"


AH-1: Module 2 - Week 1 - Numpy

There is a problem with the sonar, but it will not be resolved because it is a question in the exercise.


Enable progressive web app

This will allow installing this as an app, and should address #11.
This installs just fine, but the cache doesn't seem to be working for offline use.

Offline cache thing is working now, turns out it had to do with scoping.
One problem, though, is that something horrible goes wrong when I install this using Firefox mobile. With the way Pixel 8s work, you are supposed to swipe up to get out of the app, but this app basically is eating all the gestures for some reason, making it impossible to exit from. I had to trigger assistant and tell it to open the home screen. Probably best to fix that ASAP.

I tried looking into this a bit and I have no idea what's causing it or how to fix it. So I guess if you install the PWA just install it from chrome...


LUA Error after Update Today

Addon Version
v0.3.9
World of Warcraft Version
Retail
Describe the bug
After logging in, I get this Lua Error and my Bag Shows Empty:
Message: Interface/AddOns/BetterBags/core/async.lua:49: ...nterface/AddOns/Blizzard_ObjectAPI/Mainline/Item.lua:121: bad argument #1 to 'GetItemGUID' (Usage: local itemGUID = C_Item.GetItemGUID(itemLocation)) Time: Tue Sep  3 18:00:33 2024 Count: 1 Stack: Interface/AddOns/BetterBags/core/async.lua:49: ...nterface/AddOns/Blizzard_ObjectAPI/Mainline/Item.lua:121: bad argument #1 to 'GetItemGUID' (Usage: local itemGUID = C_Item.GetItemGUID(itemLocation)) [string "@Interface/AddOns/BetterBags/core/async.lua"]:49: in function worker'
[string "@Interface/AddOns/BetterBags/core/async.lua"]:65: in function DoWithDelay' [string "@Interface/AddOns/BetterBags/core/async.lua"]:74: in function Do'
[string "@Interface/AddOns/BetterBags/core/async.lua"]:102: in function Batch' [string "@Interface/AddOns/BetterBags/data/loader.lua"]:111: in function Load'
[string "@Interface/AddOns/BetterBags/data/items.lua"]:799: in function ProcessContainer' [string "@Interface/AddOns/BetterBags/data/items.lua"]:515: in function RefreshBackpack'
[string "@Interface/AddOns/BetterBags/data/refresh.lua"]:144: in function StartUpdate' [string "@Interface/AddOns/BetterBags/data/refresh.lua"]:227: in function cb'
[string "@Interface/AddOns/BetterBags/core/events.lua"]:49: in function <Interface/AddOns/BetterBags/core/events.lua:47>
[string "=[C]"]: ?
[string "@Interface/AddOns/BetterBags/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua"]:19: in function <...ags/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
...
[string "@Interface/AddOns/Blizzard_UIParent/Mainline/UIParent.lua"]:422: in function UIParentLoadAddOn' [string "@Interface/AddOns/Blizzard_UIParent/Mainline/UIParent.lua"]:627: in function MajorFactions_LoadUI'
[string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_WarWithinLandingPage.lua"]:96: in function SetUpMajorFactionList' [string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_WarWithinLandingPage.lua"]:89: in function RefreshMajorFactionList'
[string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_WarWithinLandingPage.lua"]:84: in function RefreshOverlay' [string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_WarWithinLandingPage.lua"]:76: in function <...pansionLandingPage/Blizzard_WarWithinLandingPage.lua:72> [string "=[C]"]: in function CreateFrame'
[string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_WarWithinLandingPage.lua"]:48: in function CreateOverlay' [string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_ExpansionLandingPage.lua"]:78: in function RefreshExpansionOverlay'
[string "@Interface/AddOns/Blizzard_ExpansionLandingPage/Blizzard_ExpansionLandingPage.lua"]:37: in function <...pansionLandingPage/Blizzard_ExpansionLandingPage.lua:35>
Locals: success = false
err = "...nterface/AddOns/Blizzard_ObjectAPI/Mainline/Item.lua:121: bad argument #1 to 'GetItemGUID' (Usage: local itemGUID = C_Item.GetItemGUID(itemLocation))"
task =  {
ctx =  {
}
thread =
}
events =  {
modules =  {
}
defaultModuleLibraries =  {
}
name = "BetterBags_Events"
orderedModules =  {
}
_eventArguments =  {
}
_bucketCallbacks =  {
}
_bucketTimers =  {
}
_eventQueue =  {
}
_messageMap =  {
}
_eventHandler =  {
}
enabledState = true
baseName = "BetterBags"
_eventMap =  {
}
moduleName = "Events"
defaultModuleState = true
}
delay = 0
`
Steps to reproduce
Just Log In...

Please update to the latest verison : https://github.com/Cidan/BetterBags/releases/tag/v0.3.10

Please update to the latest verison : https://github.com/Cidan/BetterBags/releases/tag/v0.3.10

Thats what I did and got that Lua Error

My bags are completely gone after the update

You are on v0.3.9. v0.3.10 has been released (still waiting for Curse to update, I guess) and resolves this issue.

You are on v0.3.9. v0.3.10 has been released (still waiting for Curse to update, I guess) and resolves this issue.

Ok your Right it must be Curse for some reason.
Used the Link for the Update above and all working again.

v0.3.10 is now available on Curse.


Unable to install in macOS

After setting the CC and CXX path and hacking the binutils, I'm finally hitting below error.
Note : I manually symlinked ar, ld, ranlib etc under .../includeos/bin/x86_64-elf-*
>>> Building IncludeOS
~/ws/IncludeOS/build_x86_64 ~/ws/IncludeOS
-- Target CPU x86_64
-- Target triple x86_64-pc-linux-elf
-- Using vanilla CPU features: SSE3. CAPABS = -msse3 -mfpmath=sse
-- Init git submodule: mod/GSL
-- Init git submodule: mod/http-parser
-- Init git submodule: mod/uzlib
-- Init git submodule: mod/rapidjson
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/kspviswa-vz/ws/IncludeOS/build_x86_64
[100%] Built target PrecompiledLibraries
[  2%] Performing build step for 'diskbuilder'
[  4%] Performing build step for 'vmbuild'
[  8%] Built target PrecompiledLibraries
[  8%] Built target botan
[  8%] Linking CXX static library libcrtn.a
[  8%] Linking CXX static library libcrti.a
Error running link command: No such file or directory
make[2]: *** [src/arch/x86_64/libcrtn.a] Error 2
make[1]: *** [src/arch/x86_64/CMakeFiles/crtn.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Error running link command: No such file or directory
make[2]: *** [src/arch/x86_64/libcrti.a] Error 2
make[1]: *** [src/arch/x86_64/CMakeFiles/crti.dir/all] Error 2
[100%] Built target vmbuild
[100%] Built target elf_syms
[  8%] Performing install step for 'vmbuild'
[100%] Built target diskbuilder
[  9%] Performing install step for 'diskbuilder'
[100%] Built target vmbuild
[100%] Built target elf_syms
Install the project...
-- Install configuration: ""
-- Up-to-date: /Users/kspviswa-vz/includeos/includeos/bin/vmbuild
-- Up-to-date: /Users/kspviswa-vz/includeos/includeos/bin/elf_syms
[100%] Built target diskbuilder
Install the project...
[ 10%] Completed 'vmbuild'
-- Install configuration: ""
-- Up-to-date: /Users/kspviswa-vz/includeos/includeos/bin/diskbuilder
[ 10%] Completed 'diskbuilder'
[ 12%] Built target vmbuild
[ 14%] Built target diskbuilder
make: *** [all] Error 2
>>> Sorry <<<
Could not install from bundle.

Did you ever get this resolved?

No feedback. I assume this is resolved. The installation docs have been reworked. Feel free to reopen if you cannot get it working.

Yeah Sorry for late reply. It is resolved.


Add the ability to change a published report name on powerbi

Update: The REST API for PowerBI does not support such ability at the moment.


ERROR in node_modules/angular-split/lib/module.d.ts:4:25 - error TS1149

Describe the bug
A clear and concise description of what the bug is.
Please specify library version.
Running into compilation issues with angular-split on Angular9 -
ERROR in node_modules/angular-split/lib/module.d.ts:4:25 - error TS1149: File name '/node_modules/angular-split/lib/directive/splitarea.directive.d.ts' differs from already included file name '/node_modules/angular-split/lib/directive/splitArea.directive.d.ts' only in casing.
import * as ɵngcc2 from './directive/splitarea.directive';
It does look like the report is legitimate. The file name is indeed splitArea.directive.d.ts with a capital A while the reference in the module is all lower case.
I have tried this in my tsconfig.json - "forceConsistentCasingInFileNames": false, but it is not helping looks like.
Version used
"angular-split": "3.0.3",
To Reproduce
Create a Stackblitz demoing the bug/issue:
https://stackblitz.com/
Unable to demonstrate the compilation issue on stackblitz.

@shankarvn I released a new beta<EMAIL_ADDRESS>can you please verify if that still has the issue?
If so, please provide a repro so we can reopen the issue and look at fixing it.


Add RTL support feature

This should support languages that have the RTL direction, or how can we style the pages to support this

Happy to open a PR for it?

Yes, of course I'll try

I've tried to do that, I can now change direction successfully, but I didn't find a good way to deal with styles (text-align,padding,margin...)

Could you open a PR so we can take a look at it?

Yes I did #825

@bdrtsky has included that feature inside #909 ; I would happily gather your feedbacks on this implementation once I got a running deployment of it @boussadjra.


I'm just considering the case of a possible ConnectionFailed (DNS failure in my case), and in such case, retry 3 times, and then die with an error that can be interpreted by the browser rather than an error 500.

:+1:


feature request: Support "acyclic" constraint on relationships

Related to #173
I want to be able to model a DAG (Directed Acyclic Graph) in cypher. So I need to be able to ensure that when a relationship is created then it doesn't create a loop.
I guess it could be done by remembering to code all the creates in a transaction, something like
# start transaction
match (a:T {key:'val1'}), (b:T {key:'val2'}) create (a)-[:R]->(b)
match p = (a:T {key:'val1'})-[:R*]-(a) return p limit 1
# abort transaction if there's now a loop

But that feels really clumsy and prone to developer errors.  NB. see also https://github.com/neo4j/neo4j/issues/8667
It would be much nicer to be able to say something like
create constraint on ()-[r:R]-() assert acyclic(r)

and have match (a:T {key:'val1'}), (b:T {key:'val2'}) create (a)-[:R]->(b) throw an error automatically if it would make a loop.

That is an interesting idea. I would say that being acyclic is a property of a path rather than of a relationship, so I think I would formulate the constraint as (see #166):
CREATE CONSTRAINT acyclic_R FOR p=()-[:R*]-() REQUIRE acyclic(p)

Sure, acyclic is relative to the path. But is it beneficial to get hung up on making the constraint syntax "path like"?  I'd say that only the relationship label is the interesting/relevant bit, so it could be simplified to
CREATE CONSTRAINT [:R] REQUIRE ACYCLIC

square brackets denoting a relationship. It might be easily confused with a node constraint but
CREATE CONSTRAINT (:T) REQUIRE ACYCLIC

doesn't make any sense so could be written to return a helpful error message "...did you mean [:T]?" or some such.

It is beneficial to reuse the standard Cypher pattern syntax in the constraint definition body, I think. The shortened version [:R] would require specialised knowledge to understand that this actually represents a path of any number of relationships of exactly that type. Tobias' suggestion of p = ()-[:R*]-() tells a person who reads Cypher exactly that directly. That way the constraint expression becomes self-explanatory, which is a nice feature.
This is a bit longer to type, but typically constraint definitions are not typed down very often, so I wouldn't see this as that large a drawback.

That would be fine. I just want to be able to enforce a DAG with this and #173
CREATE CONSTRAINT enforce_dag_acyclic_for_R_links
FOR p = ()-[:R*]-()
REQUIRE acyclic(p)

Another very similar idea would be request a relationship type to be only used in a linear way, i.e. for organizing nodes in a list. Is that a common use scenario?

Updated the original comment with the name of the CIR


IGNITE-18232 : [IEP-80] Remove of CacheMetricsMXBean legacy JMX bean, v3 : keep JCache beans

Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[ ] There is a single JIRA ticket related to the pull request.
[ ] The web-link to the pull request is attached to the JIRA ticket.
[ ] The JIRA ticket has the Patch Available state.
[ ] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[ ] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[ ] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

Can we keep one of CacheClusterMetricsMXBeanImpl or CacheLocalMetricsMXBeanImpl and implement in it JCache interfaces to reduce changes? It seems like new classes in general just a copy of existing.

It seems like new classes in general just a copy of existing.

JCache's interfaces are smaller, contain fewer methods. JCache's CacheStatisticsMXBean has 11 statistics methods. It doesn't have Ignite's getEntryProcessorHits or getRebalancingKeysRate. And many others from CacheMetrics. To support JCache, we don't need entire old CacheClusterMetricsMXBeanImpl. Also, regarding to JCache spec, CacheMXBean and CacheStatisticsMXBean are separated beans. And are enabled/disabled separately by CacheManager#enableManagement() and CacheManager#enableStatistics(). Now we have 2 implementations of these beans not exposed.

Yes. We should cleanup existing MXBeans and keep only methods required by JCache specification.

Yes. We should cleanup existing MXBeans and keep only methods required by JCache specification.

It is done in the new beans

We don't need to copy code from existing to those new classes. Please, revert removal of existing JMX class and keep required methods in it.

We don't need to copy code from existing to those new classes. Please, revert removal of existing JMX class and keep required methods in it.

Done. I keep CacheClusterMetricsMXBeanImpl. But I think we violate S principle of SOLID. CacheStatisticsMXBean and CacheMXBean should be split and created separately on demand. The old beans implements the both interfaces. However, we pass JCache spec tests


Insufficient colour contrast

Some text  has an insufficient contrast ratio and is failing WCAG 2.0 conformance criteria.
White chapter text on chapter indicators
Green link colour (e.g. Twitter link on articles) and hover colour (article label and headings hover on landing page) on beige
Captions (in article) and promo text (on landing page) on beige background
Article page example:
https://next.wellcomecollection.org/articles/eels-and-feels
Landing page:
https://next.wellcomecollection.org/explore

@Norvard any thoughts?

Yea I noticed this also some time ago. I think we need to up the darkness of this copy. We changed the background colour some months back and the light text needed to follow that

Hello All im new at github would like to help out am I in the right place? If so is this your problem that needs solved.

@tomi do you have suggestions for the colour changes, thanks

When we darkened the beige background, it affected some of legibility. So I think we actually have to lighten the background a tiny bit, and then also darken some of the text elements, plus include a dark text link teal to our colour palette so that smaller links such as the Twitter handle work.
I have checked the below colours against an accessibility checker so they should be kosher.
New beige background colour: f0ede3
All text, including image captions, should be set to our black: 1d1d1d
New darker text link teal: 034e44
Unfortunately, due to the fact that we lighten the beige background, on weaker monitors the contrast between this and our white background does not register. Its a loss but it does not affect legibility as white is only used as a container.

As for the digital story title card... not really sure how to go about working with that. @gestchild  Is the legibility due to the blue background, or the image, or both?

It's the white (#fff) on the turquoise (#5cb8bf)

If that container does not pass accessibility, then we need to rework the design of that a bit. We cant just simply change the colours as those are our digital brand colours.
Its a weird case as there is both colour bars and dark image behind the type...

@gestchild @Norvard Can I just confirm that the problem that remains is just the digital story navigation, and that other contrast issues have been fixed?

@jennpb yep, that sounds right to me

Let's do a bit of research on the digital story nav first (as in #786) to see whether this warrants a redesign at this stage. @hthair @Heesoomoon


Add design package

Investigate style components / material UI / ant design works with semantic HTML
AC:

[ ] add MUI
[ ] add emotion

Done in https://github.com/ericloureiro/schedules-challenge/issues/17


something is wrong with check_version in the launch script

It is crashing out and giving me:
FAILED!!! (signal: 0, exit code: 1)

Thanks for reporting, @Data-drone
This was due to an issue with DNS name resolution within the docker container. I'm not sure why it happens but I've implemented a workaround to ensure it doesn't fail due to this problem. Also improved the error handling so that, if it fails, it'll show a descriptive message.