[BUG] Error: Cannot find module 'iltorb'

Environment

chrome-aws-lambda Version: 1.19.0
puppeteer / puppeteer-core Version: 1.19.0
OS: Amazon Linux
Node.js Version: 10.15
Lambda / GCF Runtime: nodejs10.x

Expected Behavior
iltorb should not be missing since it seems to be bundled with the package.
Current Behavior
Error during lambda invocation:
2019-08-09T17:15:36.459Z	34e925fd-e216-5eec-ab6e-703a4e79169f	ERROR	Invoke Error
{
    "errorType": "Error",
    "errorMessage": "Cannot find module 'iltorb'",
    "code": "MODULE_NOT_FOUND",
    "stack": [
        "Error: Cannot find module 'iltorb'",
        "    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)",
        "    at Module._require.o.require (/var/task/serverless_sdk/index.js:9:89041)",
        "    at require (internal/modules/cjs/helpers.js:25:18)",
        "    at inflate (/var/task/node_modules/chrome-aws-lambda/source/index.js:200:14)",
        "    at Function.get executablePath [as executablePath] (/var/task/node_modules/chrome-aws-lambda/source/index.js:159:7)",
        "    at constructMaterialDef (/var/task/src/webpack:/src/trending/generateTrendingMaterialFromMessage.ts:17:29)",
        "    at o.asyncWithScope (/var/task/src/webpack:/src/trending/generateTrendingMaterialFromMessage.ts:32:24)",
        "    at default (/var/task/src/webpack:/genolingo-raven-errors/lib/index.js:82:29)",
        "    at Hub.configureScope (/var/task/node_modules/@sentry/hub/dist/hub.js:278:13)",
        "    at callOnHub (/var/task/node_modules/@sentry/minimal/dist/index.js:17:28)",
        "    at Object.configureScope (/var/task/node_modules/@sentry/minimal/dist/index.js:77:5)",
        "    at a.default.sentryDSN.Promise (/var/task/src/webpack:/genolingo-raven-errors/lib/index.js:81:44)",
        "    at new Promise (<anonymous>)",
        "    at Object.this (/var/task/src/webpack:/genolingo-raven-errors/lib/index.js:81:22)",
        "    at Generator.next (<anonymous>)",
        "    at /var/task/src/webpack:/genolingo-raven-errors/lib/index.js:5:71"
    ]
}

Possible Solution
I noticed this line in the codebase:
 if (iltorb == null) {
    iltorb = require(process.env.AWS_EXECUTION_ENV !== 'AWS_Lambda_nodejs8.10' ? 'iltorb' : `${__dirname}/iltorb`);
  }

Given that i'm running nodejs10.15 I would assume this would have resolved to ${__dirname}/iltorb rather "iltorb" as it seems to have done from the error message.
Edit: read this wrong - it requires iltorb if NOT on 8.10. So am I supposed to be bundling and installing iltorb myself, then?

I patched in iltorb using a layer and now i'm facing the following error:
2019-08-09T17:39:54.620Z	a93274ca-ddc6-54da-b100-210d6fe652f5	ERROR	Error getting browser instance Error: Failed to launch chrome!
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

This seems similar to #37 and so I guess I'll follow that thread for this new problem.
Do let me know if there's an easier way to fix this iltorb issue or if perhaps I missed something when setting this up.

@mtford90 The issue is not (only) iltorb: that would be easy to fix.
The problem is actually the incompatibility with nodejs10.x, as stated in the README:

Due to unmet dependencies, the nodejs10.x AWS Lambda runtime is currently not supported.

You're right that this is related to #37, and I've actually uploaded those dependencies that you need here, but unfortunately it doesn't end there - you'd also need to bundle Fontconfig and at least one font.
Given that this setup is much more complex on 10.x it's probably best to just stick with 8.10 for now.
Closing this as a duplicate of #37.

Looks like the new nodejs runtimes are supported now.
This package works with the nodejs8.10, nodejs10.x and nodejs12.x AWS Lambda runtimes out of the box
I was able to get past the error with npm i iltorb

next error was Failed to launch Chrome! which I was able to fix (locally) using
                executablePath: undefined
            })```

next error was Failed to launch Chrome! which I was able to fix (locally) using
const browser = await chromium.puppeteer.launch({
     executablePath: undefined
})

For code that works locally and in production, you can try this
            const browser = await chromium.puppeteer.launch({
                executablePath: process.env.NODE_ENV !== 'production'
                ? undefined
                : await chromium.executablePath,
            })

source: https://github.com/alixaxel/chrome-aws-lambda/issues/82#issuecomment-565575479


nodejs sensor triggers deprecation warning in Fastify

There is an issue with the instana nodejs sensor and Fastify:
When the instana-nodejs-sensor is activated and this is executed
https://github.com/instana/nodejs-sensor/blob/4a9e07fbc46db384f312d6139e2d6679423b28ef/packages/core/src/tracing/instrumentation/frameworks/fastify.js#L100
this deprecation warning in Fastify is triggered over and over:
Warning: basePath is deprecated. Use prefix instead. See: https://www.fastify.io/docs/latest/Server/#prefix

PR: https://github.com/instana/nodejs-sensor/pull/164

Closed via #164, efb7063 and fix released in 1.71.2.


New grid with multi-row does not initialize correctly

Hi,
Thanks for the angular port. I cloned the demo and tried to set #scope.widgets to include one of the default items on the second row, i.e:
$scope.widgets = [{"x":"1","y":"1","width":"1","height":"1"},{"x":"1","y":"0","width":"3","height":"1"}];
However when I refresh both items are on the first row. I was hoping this worked like the serialization demo page.

The demo is using gs-item-autopos="1" and thus automatically reordering added items to save space. If you don't want this, set gs-item-autopos to zero.

Perfect, thank you so much.


Support single line comments toggle with //

Is it possible to support single line comment in editor:toggle-line-comments even for languages that define editor.commentEnd ?
https://github.com/jroesch/language-scala/issues/6
The logic is already there
https://github.com/atom/atom/blob/v0.129.0/src/language-mode.coffee#L45
https://github.com/atom/atom/blob/v0.129.0/src/language-mode.coffee#L67

@MasseGuillaume Why did you close this issue?  It's a real problem for CSS, and as you mentioned, buggy.


3bot deployment: screen #3 branch name step should just be removed

why do i have to name it? will it matter if i just deploy on development branch as default? as a user i want to know why i should create a branch. what is branch?. if its not necessary we could just use 'development' as default and remove this step

i still feel weird about this one. perhaps it can be an advanced option instead?

addressed in https://github.com/threefoldtech/js-sdk/issues/783


Remap ThetaJoin condition in ReifyIdentities.

If a ThetaJoin branch carries an IV map, we need to remap value access to that side in the join condition.
Also adds a nicer error message for the unimplemented case tracked in #3114.

I attempted to add some integration tests that would trigger the issue fixed here, but the queries that I think will do so won't compile at the moment (see #3309).
I'll make sure to include tests for these cases in the main ReifyIdentities testing PR.


[docker] test docker image before pushing

This adds a step in the docker workflow that runs script/test inside a container created using the newly built siliconlabsinc/ot-efr32-dev image before pushing the image to Docker Hub.
Other Changes:

[actions] use cache for lfs pull in docker workflow

(related to openthread/ot-efr32#336)

[script] update script/bootstrap java version due to SLC requiring Java 17
[script] update script/generate_cmake.py to work when repo sources are not in a git environment (ie when downloaded as a .zip)

(related to openthread/ot-efr32#566)

@jwhui can you review this please?


Update aboutus

Add my detail to AboutUs.md

See my comment here

It is recommended that all PRs have a corresponding issue. Also, see my comment here

Thanks for pointing out, made corresponding changes!


problem with precomputed NetVLAD

I want to use the matching data we had already computed for netVLAD  or CALC:
(And I wonder  what you mean about the 'matching data' ?  Is that the precomputed retrieval results? )
python main.py -em 0 -sm 0 -dn corridor -ddir datasets/corridor/ -mdir precomputed_matches/corridor/ -techs NetVLAD_Precomputed
but  errors like below:
File "/VPR-Bench/performance_comparison.py", line 256, in compute_matches     if (retr in ground_truth_info[itr][1]): IndexError: index 111 is out of bounds for axis 0 with size 111

Yes, precomputed_matches are the retrieval results.
I used the same command that you have copied here python main.py -em 0 -sm 0 -dn corridor -ddir datasets/corridor/ -mdir precomputed_matches/corridor/ -techs NetVLAD_Precomputed for the clone of this remote repository but it works fine for me. I cannot reproduce this error on my end.

Yes, precomputed_matches are the retrieval results.
I used the same command that you have copied here python main.py -em 0 -sm 0 -dn corridor -ddir datasets/corridor/ -mdir precomputed_matches/corridor/ -techs NetVLAD_Precomputed for the clone of this remote repository but it works fine for me. I cannot reproduce this error on my end.

fine，maybe  blame on my python environments, Thanks !


Fix dependency upgrades

Apart from an updates set of dependencies, which required a set of adjstments (see mainly https://github.com/enram/vptstools/issues/43), this PR also switches the inventory reader to a block-based loop reading a subset of lines a time. As these inventory files are from varying size and sometimes really big, this saves a lot of memory to process the inventory files.

Squaqh/merge this myself as it mainly fixes the currently failing CI.


Upgrade to node 20

Service still starts in docker-chs-dev.
Will need to amend pipeline tasks and check it starts in ECS e2e.
IDVA3-753

CI: Security warnings found!

CI: Security warnings found!


add vertical response

http://www.verticalresponse.com/

Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id l1csp352198wev;
        Thu, 20 Mar 2014 16:27:15 -0700 (PDT)
X-Received: by <IP_ADDRESS> with SMTP id z62mr22437076yhf.111.1395358035487;
        Thu, 20 Mar 2014 16:27:15 -0700 (PDT)
Return-Path<EMAIL_ADDRESS>Received: from mkt4-sf.verticalresponse.com (mkt4-sf.verticalresponse.com. [<IP_ADDRESS>])
        by mx.google.com with ESMTP id t70si3899043yhi.105.2<IP_ADDRESS>.27.14
        for<EMAIL_ADDRESS>        Thu, 20 Mar 2014 16:27:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>       dkim=pass<EMAIL_ADDRESS>Return-Path<EMAIL_ADDRESS>DKIM-Signature: v=1; a=rsa-sha1; d=vresp.com; s=dkim; c=simple/simple;
	q=dns/txt<EMAIL_ADDRESS>t=1395358034;
	h=From:Subject:Date:To:MIME-Version:Content-Type;
	bh=gYnLSshhswY7CZwNA2CJ+4uIdqI=;
	b=NUj6/yxAsGM6NZ5+XZaiAD4GqlUkgrjgAEtRcjHx0uQkylNIU5JNqCkWALynMlN8
	f/aU1+9IQ5VTfr8q99lXXgOXoYwA5z428/OZhkiRDMYsWMXWbe63Q00WOyhafWCU
	nUyXrCQ1a8I0PpFwbTlKZE20+6K/RAwtIlJG4hR5wE0=;
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
	s=mkt; d=vresp.com;
	h=Received:Message-Id:Content-Transfer-Encoding:Content-Type:MIME-Version:X-Mailer:Date:Subject:From:X-Priority:X-Vr-Email-Origin:Sender:To;
	b=Efz0RttqkWxxMouW/DhwIQ5/D4vWZJZiA3CcxGfD+SNPBidQizPWMsQPhygHGsgO
	lHyowM3XuF+v7VDpVUr/YbKtUcyDf+Q9c4xvD+xs91bNlAI2DaeiGO0tIsLvlSrm
	oT7HimyelaYNXMFT63KkoDUG1nz+xVAWg3ro8SpGocY=
Received: from [<IP_ADDRESS>] ([<IP_ADDRESS>:52040] helo=vm-api08.sf.verticalresponse.com)
	by napa (envelope-from<EMAIL_ADDRESS>	(ecelerity <IP_ADDRESS>536 r(41536)) with ESMTP
	id 15/E5-22080-2597B235; Thu, 20 Mar 2014 16:27:14 -0700
Received: from vm-api08.sf.verticalresponse.com (localhost.localdomain [<IP_ADDRESS>])
	by vm-api08.sf.verticalresponse.com (8.13.8/8.13.8) with ESMTP id s2KNREkd011986
	for<EMAIL_ADDRESS>Thu, 20 Mar 2014 16:27:14 -0700
Received: (from vr@localhost)
	by vm-api08.sf.verticalresponse.com (8.13.8/8.13.8/Submit) id s2KNRE5V011985;
	Thu, 20 Mar 2014 16:27:14 -0700
Message-Id<EMAIL_ADDRESS>Content-Transfer-Encoding: binary
Content-Type: multipart/alternative; boundary="_----------=_1395358034119800"
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.74; T1.16; A1.77; B3.07; Q3.07)
Date: Thu, 20 Mar 2014 23:27:14 UT
Subject: Action Required: Confirm Your Sign-Up
From: "TechStars"<EMAIL_ADDRESS>X-Priority: 3
X-Vr-Email-Origin: perl VR::Email
Sender<EMAIL_ADDRESS>To<EMAIL_ADDRESS>

https://github.com/nquinlan/Email-Intelligence/pull/21


feat: 🎸 Allow optional memo field while creating instruction

JIRA Link
DA-435
Changelog / Description

Allow optional memo field while creating instruction
Also, returns the memo value in InstructionModel

Checklist -

[x] New Feature ?
[x] Updated swagger annotation (if API structure is changed) ?
[x] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Irrelevant information in the sign up help page

Environment
IS standalone pack
JDK -1.8
DB - postgres sql 9.6
Steps to recreate the Issue

Start IS server
Go to login page and click "Sign-In" option

Observations
sign in user guide contains outdated information

Expected Results
The above highlighted outdated content and irrelevant content should be corrected

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Yikes!

Hi @jeanwalshie! Can you provide more information including the version of Windows and the version of Internet Explorer where you saw this?

sorry, @jswedko, of course. this was with IE Version 9 and Windows 7 Enterprise.

Thanks for the additional detail! Should help me reproduce.

Didn't mean to close this.
Apologies for the delay, was on vacation, but this should be addressed. Let me know if you still see this bug! Please close this issue if you do not.

thanks @jszwedko ! it's fixed!


Add centos C++ artifacts

Some projetcs might need a C++ library compiled for CentOS7.
The new workflow generates static and dynaic libraries using a container.
Closes #19

I recommend splitting centos.yml into 2 files:
* One for Sirius

* One for OR-Tools

I don't this this is possibe.
We build Sirius in order to use it right after to build ortools. If I use two separate workflows I'd need to retrieve sirius in a different way. The best option would be to have an official release of Sirius and download the release asset but this does not seem to be coming soon.


FrontEnd Template Switch (Dark / Light Mode)

Add method to let users switch between two different templates from frontend. (Typically used to achieve a dark / light mode feature). This feature can be configured (enable/disable/set dark + light template) within the admin backend on "design" page at the "menu tab".
Remember: to get this to work as intentioned,  at least two two templates with different settings must be created.

Feature frontendSwitch (light / dark mode) done for now.


new favicon added

Fixes #194
####new favicon added

It still seems to me a bit cluttered, and the "C" and "V" aren't particularly visible..

What about something more similar to this? Just something simple, with big, bold, and obvious letters, which can be seen clearly when the image is scaled down significantly.
Of course, this was just thrown together quickly, and I don't intend for it to be the final product, as there are jagged edges, and imperfect angles.

I like @blane1257 logo, maybe we should have a poll after we shortlist some of them.


Read/Write on shadowsocks/conn should be thread safe

GoDoc on net.Conn says Multiple goroutines may invoke methods on a Conn simultaneously.
shadowsocks/conn doesn't follow the thread-safe assumption, this may break some code in future use.

I did not understand what's wrong.

When multiple goroutines invoke Read/Write simultaneously, there will be race conditions loading/assigning on Cipher, readBuf and writeBuf. There's no any lock mechanism protecting this.
It wouldn't cause any problems so far because shadowsocks seems not using Conn anywhere in concurrent context.
I'm just suggesting that Conn should eventually be thread-safe because that's how a net.Conn interface behaves.


< and > are inverted

Hello, it's me again :3
It appears that < and > are inverted, and is a bit confusing when using LDLC's keyboard.
[EDIT] To be closed, it's actually LDLC who f*d up

Wow that's funny. I don't think it's possible to take out the key and rotate it. Maybe you can buy some AZERTY amélioré stickers from the German website?

Even if it were possible, rotating the key would be pointless; the signs would still be in the same position. Cue the sad trumpet.
Either it's possible to buy some stickers in order to cover this mistake, either it's possible to contact LDLC who will send a new keycap that will replace the former.

Indeed, good catch.
LDLC will provide a new key to anyone willing to receive one.
Presumably, with a proof of purchase.
I received mine a few days ago.
I must admit I did not identify this mistake and it is not really disturbing for day to day usage.

Hello, it's me again :3
It appears that < and > are inverted, and is a bit confusing when using LDLC's keyboard.
[EDIT] To be closed, it's actually LDLC who f*d up

I noticed the same issue on the LDLC keyboard ^^;; I don‘t want to throw to much shade on them, it’s nice to have at least one keyboard with the new layout.
… stil, #YouHadOneJob ^^;;;
I didn’t know they sent a replacement key, thanks for the tip!


Add postman collection

Resolves: OBNB-463

I see. Then we need to review this behavior and documentation which I have captured a task 471.


Reserve IP subpool for a site

Prerequisites

[x] Have you tested the operation in the API directly?
[x] Do you have the latest Terraform provider version?

Describe the bug
Its not really a bug but more of a question maybe an enhancement.
When reserving an IP pools I need to reference  site_id,
but site_id are only after a DNAC site is configured.  So it makes the automation a bit more difficult to achieve:

resource "dnacenter_reserve_ip_subpool" "example" {
   provider = dnacenter
   depends_on = [ dnacenter_global_pool.example ]

   parameters {
    ...
     name               = "Cape_Town_Corp_VN"
     site_id            = "5812a67c-4939-44f9-92cc-81ceac6019cc" **<<<<<<<<<<<<<<<<<<**
     type               = "Generic"
  }
}

Is it not possible to reference "site_name_hierarchy" = "Global/SouthAfrica/CapeTown" - instead of site_id ?
This would make it much more easier to use.

I think you can solve it without an enhancement doing something like this:
resource "dnacenter_site" "example" {
  provider = dnacenter
  parameters {
    site {
      building {
        name        = "testBuilding"
        address     = "255 China Basin Street, San Francisco, California 94158, United States"
        parent_name = "Global"
        latitude    = 37.77178651716143
        longitude   = -122.39062051589885
      }
    }
    type = "building"
  }
}
resource "dnacenter_reserve_ip_subpool" "example" {
   provider = dnacenter
   depends_on = [ dnacenter_global_pool.example ]

   parameters {
    ...
     name               = "Cape_Town_Corp_VN"
     site_id            =  dnacenter_site.example.0.id
     type               = "Generic"
  }
}

Try it and let us know if works and it's what you want.

@fmunozmiranda  I've tried it:
resource "dnacenter_site" "building" {
  provider = dnacenter
  depends_on = [ dnacenter_site.area ]
  parameters {
    site {
      building {
        name = var.building
        address     = "63 Victoria Rd, Camps Bay, Cape Town, 8040, South Africa"
        latitude    = -33.9508898420
        longitude   = 18.377273855178373
        parent_name = "Global/SouthAfrica"
      }
    }
    type = "building"
  }
}

resource "dnacenter_reserve_ip_subpool" "building" {
  provider = dnacenter
  depends_on = [ dnacenter_global_pool.example ]

  parameters {
    ...
    name               = "Cape_Town_Corp_VN"
    site_id            = dnacenter_site.building.item.0.id
    type               = "Generic"
  }
}

And get this error:

@fmunozmiranda  - Yes that's exactly what I wanted - Thanks!

@fmunozmiranda   - Yes that's exactly what I wanted - Thanks!


iOS: Notifications received (in popup) but app interface doesn't update to reflect new notifications until manual refresh

I successfully got the iOS app working and loading and receiving notifications, which is amazing and awesome. Though, I noticed that while it can receive notifications without issue the app interface in and of itself doesn't update 'live' when new notifications come in.
If I manually refresh (pull down refresh) it'll load them up just fine, but it won't do that by itself.
Expected behavior:
When a new notification is received, that topic's information should automatically update on the app interface.

Hey thanks for using ntfy.
This is a known bug in iOS that I thought I had fixed in #267, but clearly not. I have the same problem sometimes with my iPhone but it doesn't always happen. I'll fix it eventually, but right now I'm a little bit clueless as to why this happens.

So my guess is that this is caused by two things:

The first message is received via Firebase/APNS and persisted to Core Data. Messages received via APNS run in the Notification Service Extension (NSE), not in the main app. They do, however, persist to the same Core Data database.
The second message is received from the polling mechanism: Every 20 minutes or so, the app receives a "poll all topics" message on the internal ~poll topic. That will instruct the main app to poll for new messages. To find out the last message it received, it uses the lastNotificationId field and then polls using /mytopic/json?since=$id. This ID is coming from Core Data.

The issue is this (this is a GUESS!): The Core Data database is not properly in sync between the main app and the NSE, which means the lastNotificationId is out of sync, so messages are delivered/displayed twice. This is bug https://github.com/binwiederhier/ntfy/issues/316.
This causes another bug too, where the UI does not reflect all messages all the time (this is: https://github.com/binwiederhier/ntfy/issues/337). It is annoying and it just shows that I don't know how Core Data works internally. It could also be a bug, but it's annoying.
Again, this is just a guess.
Debugging this is next to impossible, because

(a) You'll have to compile and run the iOS app yourself and hook it up to Firebase and APNS. It doesn't work in a Simulator because Firebase doesn't work in a simulator.
(b) Because the NSE is a separate process, the logs for it do not show up in the log console of Xcode. You have to manually attach a debugger and such. It is surpremely annoying.

Before you ask "what the heck": 90% of this is Apple's fault, of how the NSE and all that work. The problem with Core Data is obviously my fault, but I have no time currently to debug this or spend any time with it.

Hello,
I can confirm having this issue too with my iPhone 12 Pro Max iOS 14.4.1. Thanks.

Hello,
I can confirm having this issue too with my iPhone 12 Pro Max iOS 14.4.1.
The issue only happens when not using the mesh vpn or when being inside the ntfy app. If I'm connected to the mesh vpn, and and I receive the notification, when I click on the notification, it does take me to the app where the notification is showing without a manual refresh. I hope it can be fixed to make the functionality more consistent.
Thanks.

:loudspeaker:  A new version of the ntfy iOS app is currently in TestFlight. This version (hopefully) fixes the issues with the UI not properly refreshing, as well as fixes for subscriptions "getting lost". It contains no other fixes. More to come. To test the app, please use this TestFlight link: https://testflight.apple.com/join/P1fFnAm9


Allow any bond (smiles ~) recognition in CDXML

Fixes #7357

@greglandrum a simple fix for adding ~ bond perception to CDXML


Consider adding support for openlm-research/open_llama_7b and _3b

Much larger universe of people who can use truly open Llama variants such as the two models above.  Limiting the code to Facebook-approved academics severely limits its value and reach.

@RDouglasSharp thank you for this suggestion! I've just added a new script to import Open LLaMA weights from HF. Even though all parameters are mapped and copied, I was not able to generate a correct response. I didn't have time to investigate the reason, so please keep it in mind when playing with the Open LLaMA weights.


Bug: Saving array of dates as an array of strings

Parse saves array of dates [new Date()] as an array of Strings.
In database:

we've got: ["2016-02-04T09:23:40.280Z"]
Instead of: [{"__type":"Date","iso":"2016-02-04T09:23:40.280Z"}]

// on server

user.set("dates", [new Date()])
user.save().then(function() {
  return user.fetch()
}).then(function() {
  var dates = user.get("dates")
  console.log(dates[0] instanceof String) // true
})

@flovilmart just to be clear, old Parse saves dates like this: [{"__type":"Date","iso":"2016-02-04T09:23:40.280Z"}], while new parse-server saves them as strings.
This causes crashes, like here:
var date = user.get("dates")[0];
date.getTime(); // crash, date is string

So it's incompatible with old Parse and breaks the code.
I'm not sure if enhancement is a good label here.

@FilipZawada does it occur only on array of dates?

I just ran that unit test:
it('should save an array of dates', (done) => {
    let object = new Parse.Object('Object');
    let dates = [];
    while(dates.length != 5) {
      dates.push(new Date());
    }
    let objectId;
    object.set('dates', dates);
    object.save().then(()=> {
      objectId = object.id;
      let q = new Parse.Query('Object');
      return q.get(objectId);
    }).then((object) => {
      console.log(object.toJSON());
      console.log(object.get('dates')[0].getTime());
      done();
    })
  })

And this is the response I got:
{ dates:
   [ { __type: 'Date', iso: '2016-03-15T14:18:57.888Z' },
     { __type: 'Date', iso: '2016-03-15T14:18:57.888Z' },
     { __type: 'Date', iso: '2016-03-15T14:18:57.888Z' },
     { __type: 'Date', iso: '2016-03-15T14:18:57.888Z' },
     { __type: 'Date', iso: '2016-03-15T14:18:57.888Z' } ],
  updatedAt: '2016-03-15T14:18:58.630Z',
  createdAt: '2016-03-15T14:18:58.630Z',
  objectId: 'iMr8iONkOo' }
1458051828816

The dates are properly stored as objects like in the old parse server. And I can properly access the date object.

Closing this as it seems like we have a test case that covers this, and it's working. @FilipZawada if you are still seeing this problem, please open a new issue that includes a complete failing test case.


Update CHEBI import.

TODO: find out why the biochebi GCIs change from 'transports or maintains localization of' to 'regulates levels of'.


Support Env Var setup

For dynamic deployment setup, without code changes, it would be useful to have environment variables to define the rules map.

Yes. I think that's a good option to add


Copy ruxitagentproc.conf config into upper-dir (#2668)

Description
cherry pick of #2668
How can this be tested?
same as #2668
Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
Attention: 14 lines in your changes are missing coverage. Please review.

Comparison is base (e9619f3) 67.72% compared to head (3115c68) 67.72%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

...kg/controllers/csi/driver/volumes/app/publisher.go
64.28%
5 Missing and 5 partials :warning:

pkg/controllers/csi/metadata/path_resolver.go
0.00%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2677      +/-   ##
==========================================
- Coverage   67.72%   67.72%   -0.01%
==========================================
  Files         250      250
  Lines       13616    13637      +21
==========================================
+ Hits         9222     9235      +13
- Misses       3590     3593       +3
- Partials      804      809       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


docs(createAlgoliaInsightsPlugin): rewrite docs

This rewrites the createAlgoliaInsightsPlugin docs.

Broken unit tests are caused by https://github.com/algolia/autocomplete/commit/752afd80793060bcc86b5d52afe3410734a5773a which broke the build.

How about adding a "Related" section at the end that links to the guide?
I also feel like we sould give examples for onItemsChange, onSelect and onActive.

How about adding a "Related" section at the end that links to the guide?
I also feel like we sould give examples for onItemsChange, onSelect and onActive.

Handled in 9a927be5, lmk what you think.


DCR endpoint does not support all the attributes mentioned in the dcr yaml file

Description:
In the dcr yaml file, we have mentioned these attributes https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.api.server.dcr/src/main/resources/api.identity.oauth.dcr.endpoint.yaml#L260. Doc also says so [1]. But from backend, we support only  the following attributes [2].

redirectUrisclientName
granttypes
tokenType
consumerKey
consumeSecret
spTemplateName
backchennellogoutUri

[1]https://docs.wso2.com/display/IS511/apidocs/OAuth2-dynamic-client-registration/#!/models#RegistrationRequest
[2]https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/v6.5.2/components/org.wso2.carbon.identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/bean/ApplicationRegistrationRequest.java

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Update  cdk8s+ getting started python code on  index.md

PR contains:

Changed  the cdk8s Index.md's 'Getting started' document. Specifically, the python code previously used kplus.Container to define a container within a deployment, which is incorrect. The new version uses kplus.ContainerProps instead.

Thank you @camba1 for catching this error! Your commit just needs to be signed off as per our Developer Certificate of Origin policy. See https://github.com/cdk8s-team/cdk8s/pull/746/checks?check_run_id=4121305258 for instructions on updating your PR.

Thanks for letting me know @Chriscbr ! I made the change and the DCO check is now successful. Let me know if there is anything else I need to do,


SIGSEGV on Linux when actual page size is not 4k

JVM crashes on attach if actual page size is 64k. The solution is to get is from OS instead of hardcoding in arch.h.
Other platforms suffer as well.

Makes sense. Thanks for pointing this out.
I'll accept the PR after I verify it introduces no regression.

I realized that sysconf() is POSIX so I've updated PR to check 'unix'. This should work on macOS X either now.

This means #ifdef is not needed then. Profiler is not supposed to work on non-POSIX systems so far.

I found that initializing a global variable in a header file is not the best approach, since the initialization code is repeated in all places that include this .h file.

I've reimplemented the fix. Please verify that it works as expected.

Great, it works.


print score rather than return; add command line test

Thanks Martin. New CLI successfully ran to completion on my machine. If tests pass, this looks good to me.

hey success, the new test rediscovered the missing fire dependency 😄


Update to InkScape 1.0 + License request

hi,
fixed to code to make it work with InkScape 1.0
and it would be cool if you could provide a license to this repo. regards, Mario

Thank you for the pull request!
I have no excuse for why this took so long to merge so I want to apologize for that. I hadn't looked at the project in years, I wanted to have a fresh look at it before merging anything so I just put it off until I forgot about the whole thing.


Selection in RichEditBox returns wrong properties in some cases while word wrap enabled

Describe the bug
In a Richeditbox if word wrap is enabled, a line which is of higher length than of the control width it is divided into multiple parts. If a mouse click is done at the end of the first part the selection property returns property for the beginning of the next part. Also the position at which cursor starts blinking isn't part of the document(there is no way to reach that position through arrow keys).
Steps to reproduce the bug
Steps to reproduce the behavior:

First insert a RichEditBox control and make a status bar at the bottom of the app to show the selection coordinates.

<Grid>
        <Grid.RowDefinitions>
            <RowDefinition Height="*"/>
            <RowDefinition Height="Auto"/>
        </Grid.RowDefinitions>
        <RichEditBox Grid.Row="0" x:Name="SampleRichEditBox" ScrollViewer.VerticalScrollBarVisibility="Auto" TextWrapping="Wrap" SelectionChanged="SampleRichEditBox_SelectionChanged"/>
        <StackPanel  Grid.Row="1" Orientation="Horizontal">
            <TextBlock Text="X: " Margin="10,0,10,0"/>
            <TextBlock x:Name="XC"/>
            <TextBlock Text="Y: " Margin="10,0,10,0"/>
            <TextBlock x:Name="YC"/>
        </StackPanel>
    </Grid>

Change the value of (x, y) coordinates with selection changed event:

private void SampleRichEditBox_SelectionChanged(object sender, RoutedEventArgs e)
        {
            SampleRichEditBox.Document.Selection.GetRect(Windows.UI.Text.PointOptions.ClientCoordinates, out var rect, out var _);
            XC.Text = rect.X.ToString();
            YC.Text = rect.Y.ToString();
        }

Insert a line which will be wrapped.
Click at the end of the line and note the selection coordinates.
Now travel through arrow keys to get the above noted coordinates.

Expected behavior
On clicking at the end of the first part selection coordinates should be at the end of the first part.
Screenshots

Result of Step-4 :

Result of Step-5 :

Version Info

NuGet package version: 2.3.200213001

Windows 10 version
Saw the problem?

Insider Build (19564)
Yes

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Looks like a RichEdit bug.

@soumyamahunt  Two things here.  First, I am going to assume in your example here that there is a space that exists between jpvbc at the end of the first displayed line and the vzhj at the start of the second.  I believe that to be the case because if there wasn't we would have layout as many characters as possible to fill the full width of the text box and not arbitrarily inserted a line break.
Second, if that is the case then this is functioning as by design. Let me explain a little bit about the position at the extreme end of one line and the beginning of the next.  In terms of the character that they are point at, they are the same thing.  However, depending on how you get to that character position, they can visually point to two different places.  Lets take a simple example of a string of digits with a space in the middle ("01234 56789") and assume that they are displayed in a RichTextBox that is narrow enough (or the font large enough) they will not fit and must line break.  What would see in the display is:
01234
56789
But let's not forget.  There is an invisible space at the end of that first line which I will represent with an underscore.  So it would be:
01234_
56789
Now, if the user clicks beyond the end of the first line, we assume that the user will want to interact with that first line and so we put the insertion point after the space:
01234_|
56789
But if they click before the second line, then they want to interact with the second line and we put the insertion point at the beginning of it.
01234_
|56789
But they both refer to the same character position.  So if you were to press the back arrow from this position, you expect it to go back one character position, which is to before the space
01234|_
56789
And if you press right arrow, you expect to go forward one character position.  Now technically  this could either be after the space or before the 5, but it can't be both.  So the implementation choice that was made was that we move to the next line an put it before the 5.  I wasn't around for the original implementation, but it seems to make the most sense to do it this way as the cursor is adjacent to the next character you are going to interact with if you are going to extend the selection or press delete.   So you cannot ever (via the keyboard) get to the end of the first line position.
01234_
|56789
In the case where there is no space, it still works the same way.  Assume there is no space in our digit string.  "0123456789" We would get:
01234
56789
Clicking at the end of the first line would put the cursor at the last character in that line.
01234|
56789
And clicking at the beginning of the second line would put it before the five.
01234
|56789
But again, they are same character position so back from here is:
0123|4
56789
And then forward is
01234
|56789
There is no way to get the cursor (via the keyboard) to that position after the 4.
And just for completeness's sake.  Let go back to where we clicked beyond the end of the first line:
01234|
56789
When you press the right arrow from here, where would you expect it to go.  It has to move one character so it can't go to before the 5.  Instead it will end up.
01234
5|6789
Anyway, I hope this helps explain why we consider this by design behavior.  I will leave this issue open for a couple a days to see if there is something I missed.  For example, if in your example, that really was continuous string with no embedded space, then there is something going wrong because there is 1) no reason for the line to break there and 2) no reason for the caret to be offset that far for the last displayed character.  But if that is the case, then if you could include a small repro demonstrating it, I can take a look.
Thanks.

Thanks @JJBrychell for the response, unfortunately I am no longer developing for Windows platform, and no longer have Windows device as well. @0x7c13 do you still need this or are you good with @JJBrychell's explanation.


Log appropriate error message if RUNMODE is not set on initial startup.

This package requires the user to choose the mode of operation. If it's not set it was just barfing without a useful message. This adds a more helpful message as to why it didn't start.

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


Ensure maximum tint before drawing the GUI on the main canvas

This darkens the GUI when the tint is non-white. Calling tint(255) solves it. But it shouldn't darken the GUI at all, it shouldn't require the user to reset the tint before the end of draw(). Let's reset the tint ourselves while drawing the GUI then.
    public void draw() {
        tint(gui.colorPicker("tint", color(255, 255, 255, 255)).hex);
        image(gui.gradient("gradient"), 0, 0);
    }

maybe there's a way to push / pop this? to avoid changing anything on the user's side

Yes! Tint can be controlled with pushStyle() and popStyle().
`PImage img;
void setup() {
size(1333, 1000);
img = loadImage("PXL_20240523_112838077.png");
}
void draw() {
pushStyle();
tint(255, 0, 0);
popStyle();
image(img, 0, 0);
}`


objint::to_int to call int

Question: Removing PyInt and PyFloat matches or not?
float.__int__ in #885

Codecov Report

Merging #887 into master will increase coverage by <.01%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master     #887      +/-   ##
==========================================
+ Coverage   63.73%   63.73%   +<.01%
==========================================
  Files          88       88
  Lines       14771    14777       +6
  Branches     3270     3274       +4
==========================================
+ Hits         9414     9418       +4
  Misses       3214     3214
- Partials     2143     2145       +2

Impacted Files
Coverage Δ

vm/src/obj/objint.rs
84.45% <77.77%> (-0.37%)
: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 88e52ef...357e95e. Read the comment docs.

I'm not sure whether to remove the PyFloat case. @cthulahoops what do you say? I suggest to remove the PyFloat case, since we already have float.int. We might as well use that function.

All test passes without PyFloat match. I think performance is the only reason to keep the line.

Removing the line will be better for now. Original code doesn't pass the following test code:
https://github.com/RustPython/RustPython/pull/887/files#diff-2bc1a6ee243d9eabcfcf2fa3bc66239dR110


[WIP] Store motif area in section configuration

Still contains all commits from #1580
REDMINE-17966

Coverage remained the same at 99.193% when pulling 69a15f2a95ada4347e6a5aa756af0103ac6d2e3c on tf:section-motif into 4b6d674fb5c164e736a005d10cdf463a36096394 on codevise:master.

see #1582


fix: repayment lock queries reactivity

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5720

PR #5721   👈

This stack of pull requests is managed by Graphite.


Fix Expected Number with value, got String error

Hi, I'm starting with vue.js and I implemented star-rating. Everything is working fine: I can get the rating value from database and update it by clicking on the stars.
But I get this message when page loads and on click event:
[Vue warn]: Invalid prop: type check failed for prop "rating". Expected Number with value 2, got String with value "2".
my code:

        <star-rating @rating-selected="setRating(item.id, item.rating)" v-model='item.rating'></star-rating>

let app = new Vue({
    el: '#app',
    data: {
        city: 'mycity',
        hosters: null,
        selectedImage: null,
        openModal: false,
        showTour: false,
        tourSelect: '',
        rating: 0
    },
    created: function () {
        this.searchHoster()
    },
    methods: {
        searchHoster: function () {
            axios.post('searchHoster.php', { "city": this.city }).then((response) => {

                this.hosters = response.data.hosters;
                console.log(this.hosters);

            }).catch((error) => {
                console.log(error);
            });
        },
        setRating: function (id, rating) {
            axios.post('updateRating.php', { "id": id, "rating": rating }).then(res => {
                console.log(res);
            });
        }
    }
});

I've tried to declare rating as a prop but it didn't work. May I get your help? Thank you!

Sorry I didn't get back to you on this. I'm sure you've solved this by now, but please feel free to re-open if you're still having trouble.

Yep. I'm returning a number from database instead of a string. Thanks.

My best guess is that your rating is actually being represented as a string, something like:
      this.hosters = [{
        id: 1,
        rating: "5"
      }, {
        id: 2,
        rating: "3"
      }]
    }

so you're going to need to use parseInt(). The easiest way would be to use a computed to map the array:
    hostersSanitized() {
      return this.hosters.map(item =>
        Object.assign(item, {
          rating: parseInt(item.rating)
        })
      )
    }

Now you can use v-for on the computed instead:

      <star-rating v-model="item.rating" />

Here's the JSfiddle: https://jsfiddle.net/craig_h_411/nvtcjyqh/


Limit aether.connector.http.connectionMaxTtl to 120 seconds

... and some workarounds to get aether.connector.http.connectionMaxTtl honored

I am not going to wait for the examples. They use their own mvnw anyway.


about high samplerate training

I want to retrain vocoder for higher samplerate,do you have plan to update the vocoder training ?how about the vocoder preprocessing?

Since you now have access to the training code for the ASR and F0 models, you can replace the preprocessing with whatever you like and train a vocoder with that too - you can adjust the preprocessing code of the PWG repo as you see fit.
But you'd have to train all models from scratch with your new settings.

Can you provide the preprocess.py for PWG training?Thank you very much! @Kreevoz


bessel functions

I would assume these two print statements to be equivalent:
import numpy as np
from scipy.special import j1
x = .1
print(j1(x))
print((np.sin(x)/x**2 - np.cos(x)/x))

Output is (they're not):
0.440050585745
0.30116867894

Bessel function j1
There is no documentation as to what the Bessel function should be (i.e. if some constant prefactors are added). Either documentation needs to be improved or function fixed (if this is indeed an error). Any suggestions?
thanks!
julien

np.sin(x)/x**2 - np.cos(x)/x is the first spherical Bessel function, which is related to the Bessel functions of the first kind of order 3/2. See spherical_jn.

Thanks!
Perhaps it's a good chance to add a small line of documentation? (See Also, etc)

Documentation clarifications are always welcome, do you have time to make a
PR?

Added (see PR above). The following text would have made it easier for me, but there may be better wording. thanks!


Added a Bubble Game made in JS

This is a simple game we have to press the number provided in the hit box above each correct hit will give the player a +10 score.


2.0.0-rc1.json (and -without-$id) JSON Schema is invalid

You can use an external JSON Schema validator in order to see if those files are valid or not.
I've test it, and both seem invalid.

2.0.0-rc1.json: https://www.jsonschemavalidator.net/s/r114nPn0
2.0.0-rc1-without-$id.json: https://www.jsonschemavalidator.net/s/gocJb7o3

Originally posted by @smoya in https://github.com/asyncapi/spec-json-schemas/pull/452#discussion_r1405333403
I believe that rc1 was created having as metaschema the Draft-04, because then it seems valid.
But for some reason, most probably because of https://github.com/asyncapi/spec-json-schemas/issues/454, the $schema field points to the draft-07.
Can any owner answer if 2.0.0-rc1 version was based on JSON Schema Draft-04? I believe it is, as the Schema definition uses Draft-04. But need to confirm.
Pinging owners: @fmvilas @derberg @dalelane @char0n
cc @jonaslagoni

v2 was suppose to be valid against draft 7
see the schema for rc1 when it was still in the same repo that the spec -> https://github.com/asyncapi/spec/blob/2.0.0-rc1/versions/next/schema.json#L3

I assumed that v2 was supposed to be done in JSON Schema Draft 7 (07), due to the simple fact that the AsyncAPI 2.x primarily uses Draft 7 as well.
All the definitions uses proper JSON Schema identification using $schema keyword. If it doesn't validate against Draft 7, it just needs to be fixed. It's probably remnants from creating it from v1?
"$schema": "http://json-schema.org/draft-07/schema#"

I assumed that v2 was supposed to be done in JSON Schema Draft 7 (07), due to the simple fact that the AsyncAPI 2.x primarily uses Draft 7 as well.

Howerver, I would never make such assumption based on that. We are talking about release candidates and not final versions.
In fact, if you check the Schema Object definition in rc1, you see references to JSON Schema Draft-04 that don't exist in rc2. See https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/2.0.0-rc1.json#L373-L443
Anyway, rc1 was created with Draft-07 indeed, as demonstrated by @derberg in the previous comment.

Then this issue is solved, right?

@smoya ?

these are really old schemas, not even of main release but RC
instead of fixing them I vote to remove them

these are really old schemas, not even of main release but RC instead of fixing them I vote to remove them

I like to delete things.
Pinging the rest of maintainers (which includes as well some maintainers from the spec repo): @fmvilas @dalelane @char0n @GreenRover @jonaslagoni @pakisan WDYT?

agreed - I've got no objection to removing release candidates


[New Theme Request] Jellyseerr

https://github.com/Fallenbagel/jellyseerr
This is a fork of Overseerr that also works with Jellyfin and Emby.
It looks like it's 99.95% done using the overseer theme but there are some oddities like the top header and request page, the request pop up with the season selection.

I'm going to look into this. :+1:
It's the one app that I still need to theme :smiley:


Add Travis CI build

First pass at a Travis CI build with basic Python syntax checking.
Fixes #35.

Closing so this can be merged into develop instead.


Check view is initialised in ngOnChanges

Closes IBM/carbon-components-angular#1250
Avoid errors for this.view being undefined if it has yet to be initialised

@theiliad  I've force pushed the changes again to include the keyword for the semantic build release


Extension not being recognized by python

Type: Bug
From 1 month,I'm facing the extenxsion issue.Python cannot recgnize the packages,hence solve my issue as fast as possible.
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

This issue is related to VS Code, please file it in  https://github.com/microsoft/vscode/issues


ContainerLabelTagMapping: Empty labels can break refresh

https://bugzilla.redhat.com/show_bug.cgi?id=1358257 (master, darga clone TBD)
An attempt to use #7460 by manually editing ContainerLabelTagMapping table uncovered a bug:
Kubernetes labels can legally have an empty value.
kubectl label/oc label won't let you assign a foo= label, but it's possible with oc edit:
metadata:
  annotations:
    # ...
  creationTimestamp:  # ...
  labels:
    foo: ""   # <---

Together with an any-value mapping for this label:
cat = Classification.create_category!(name: "label_foo", description: "Automatically set from `foo` kubernetes label", read_only: true, single_value: true)
ContainerLabelTagMapping.create!(label_name: 'foo', label_value: nil, tag: cat.tag)
ContainerLabelTagMapping.drop_cache

it errors during refresh when trying to create a Tag + Classification for the :
["last_refresh_error", "Validation failed: Description can't be blank, Name can't be blank"]

I'm not yet sure where the exception was caught and to what degree refresh gets aborted but it's certainly more than just the tagging by labels as that code doesn't catch exceptions.
EDIT: It seems it aborts EmsRefresh.refresh entirely, judging by stacktrace below.
@miq-bot add-label providers/containers, bug
@miq-bot assign cben

Fails here in create_tag.
[----] E, [2016-07-10T14:26:49.202199 #15296:2ad1bb027990] ERROR -- : [ActiveRecord::RecordInvalid]: Validation failed: Description can't be blank, Name can't be blank  Method:[rescue in block in refresh]
[----] E, [2016-07-10T14:26:49.202238 #15296:2ad1bb027990] ERROR -- : /usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/validations.rb:78:in `raise_validation_error'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/validations.rb:50:in `save!'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/attribute_methods/dirty.rb:30:in `save!'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/transactions.rb:324:in `block in save!'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/transactions.rb:395:in `block in with_transaction_returning_status'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/connection_adapters/abstract/database_statements.rb:232:in `block in transaction'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/connection_adapters/abstract/transaction.rb:189:in `within_new_transaction'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/connection_adapters/abstract/database_statements.rb:232:in `transaction'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/transactions.rb:211:in `transaction'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/transactions.rb:392:in `with_transaction_returning_status'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/transactions.rb:324:in `save!'
/usr/local/lib/ruby/gems/2.2.0/gems/activerecord-5.0.0.rc1/lib/active_record/suppressor.rb:45:in `save!'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:88:in `create_tag'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:71:in `create_specific_value_mapping'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:62:in `block in tags_for_name_type_value'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:61:in `map'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:61:in `tags_for_name_type_value'
/home/bpaskinc/miq/darga-tagging/app/models/container_label_tag_mapping.rb:52:in `tags_for_label'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:423:in `block in save_tags_generated_from_labels'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:423:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:423:in `collect_concat'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:423:in `save_tags_generated_from_labels'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:414:in `save_labels_and_tags_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:107:in `block in save_child_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:107:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:107:in `save_child_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:54:in `block in save_inventory_multi'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:52:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_helper.rb:52:in `save_inventory_multi'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:30:in `save_container_projects_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:13:in `block in save_ems_container_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:12:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory_container.rb:12:in `save_ems_container_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/save_inventory.rb:7:in `save_ems_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:122:in `save_inventory'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:86:in `block in refresh_targets_for_ems'
/home/bpaskinc/miq/darga-tagging/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/home/bpaskinc/miq/darga-tagging/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:86:in `refresh_targets_for_ems'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:21:in `block (2 levels) in refresh'
/home/bpaskinc/miq/darga-tagging/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/home/bpaskinc/miq/darga-tagging/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:21:in `block in refresh'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:11:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh/refreshers/ems_refresher_mixin.rb:11:in `refresh'
/home/bpaskinc/miq/darga-tagging/app/models/manageiq/providers/base_manager/refresher.rb:10:in `refresh'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh.rb:78:in `block in refresh'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh.rb:77:in `each'
/home/bpaskinc/miq/darga-tagging/app/models/ems_refresh.rb:77:in `refresh'
(irb):49:in `irb_binding'
/usr/local/lib/ruby/2.2.0/irb/workspace.rb:86:in `eval'
/usr/local/lib/ruby/2.2.0/irb/workspace.rb:86:in `evaluate'
/usr/local/lib/ruby/2.2.0/irb/context.rb:379:in `evaluate'
/usr/local/lib/ruby/2.2.0/irb.rb:489:in `block (2 levels) in eval_input'
/usr/local/lib/ruby/2.2.0/irb.rb:623:in `signal_status'
/usr/local/lib/ruby/2.2.0/irb.rb:486:in `block in eval_input'
/usr/local/lib/ruby/2.2.0/irb/ruby-lex.rb:245:in `block (2 levels) in each_top_level_statement'
/usr/local/lib/ruby/2.2.0/irb/ruby-lex.rb:231:in `loop'
/usr/local/lib/ruby/2.2.0/irb/ruby-lex.rb:231:in `block in each_top_level_statement'
/usr/local/lib/ruby/2.2.0/irb/ruby-lex.rb:230:in `catch'
/usr/local/lib/ruby/2.2.0/irb/ruby-lex.rb:230:in `each_top_level_statement'
/usr/local/lib/ruby/2.2.0/irb.rb:485:in `eval_input'
/usr/local/lib/ruby/2.2.0/irb.rb:395:in `block in start'
/usr/local/lib/ruby/2.2.0/irb.rb:394:in `catch'
/usr/local/lib/ruby/2.2.0/irb.rb:394:in `start'
/usr/local/lib/ruby/gems/2.2.0/gems/railties-5.0.0.rc1/lib/rails/commands/console.rb:65:in `start'
/usr/local/lib/ruby/gems/2.2.0/gems/railties-5.0.0.rc1/lib/rails/commands/console_helper.rb:9:in `start'
/usr/local/lib/ruby/gems/2.2.0/gems/railties-5.0.0.rc1/lib/rails/commands/commands_tasks.rb:78:in `console'
/usr/local/lib/ruby/gems/2.2.0/gems/railties-5.0.0.rc1/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
/usr/local/lib/ruby/gems/2.2.0/gems/railties-5.0.0.rc1/lib/rails/commands.rb:18:in `<top (required)>'
bin/rails:4:in `require'
bin/rails:4:in `<main>'

I saw 2 plausible behaviors, neither I nor @moolitayer were sure which is better:

ignore empty-value labels (foo= label equivalent to not having any foo label)
map them to Foo : <emtpy value> (or something similar) tags

In #9747 I implemented (1).
My logic was you have entities with "known foo property", that you want tagged as  Foo : this and Foo : that, and some with "unknown Foo", which it was perhaps easier to label with foo= than not label at all, but still it makes little sense to have any "Foo" tag.
However empty doesn't necessarily mean "unknown".
Other considerations in favor of (1):

You can always override it by creating a specific-value rule mapping to a specific tag.  You wouldn't be able to override (2) this way.
If we later decide to change code to (2), it will just work.  Whereas once you run (2) and encounter empty values, it's "sticky": specific-value foo= -> Foo : <emtpy value> mappings are in place, and will not disappear if we switch code to (1).

All that said, (2) would be more consistent and easier to document.

After discussion on PR, switched to behavior (2).

Now we decided to switch back to behavior (1) in #11806.


Docs

Closes #890

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cdf9347). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #904   +/-   ##
=========================================
  Coverage          ?   83.67%
=========================================
  Files             ?       75
  Lines             ?     5083
  Branches          ?        0
=========================================
  Hits              ?     4253
  Misses            ?      582
  Partials          ?      248

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 cdf9347...39af785. Read the comment docs.


How to obtain {train,dev,test}.english.v4_gold_conll?

Following the steps presented in https://conll.cemantix.org/2012/data.html, I can only obtain separate conll files like cctv_0000.v4_auto_conll. How can I obtain files like dev.english.v4_gold_conll?

You have to combine the OntoNotes data from LDC with the skeleton files you have downloaded. This repo has more detailed instructions: https://github.com/vdobrovolskii/wl-coref

请问获得了吗？wl-coref中直接获得了json文件，没有trainconll文件，请问怎么获得


use ffmpeg instead sndfile-convert for wav conversion

ffmpeg builds are easily available in more systems than sndfile-convert (i am expecially thinking to Windows).
The check should be like this:
CONVERT="`which ffmpeg ` -v quiet -i"
if [ $? -eq 1 ]; then
  echo "Cannot find 'ffmpeg' executable, is 'ffmpeg' installed?"
  exit -1
fi

agree.. something like that.. did you test it?

yes, i've just tested it and it works!

This is an issue not a PR.. if you update the README as well, then I'll be happy to merge it!


beans backpacks causes a crash when another mod adds curios

tested in 1.20.1 with beans backpacks 0.6-v2, forge 47.1.3 and curios 5.5.0
i tried this independently with supplementaries (quiver and key are both curios) & gigaherz' Tool Belt v1.20.0 (the toolbelt itself is a curio)
here is the log from testing w/ tool belt:
latest.log
if this cannot be fixed perhaps there could also be a config option to disable the curios backpack slot in favor of your own backpack slot (which i think works quite well for how the backpacks function here and i personally prefer this). it wouldn't fix the problem but might still allow people to work around it

I just made a simple mistake in the code, literally one character caused this. This'll be fixed in 20.1-0.7-v2 & 20.2-0.8-v2. Probably will be released tmrw night.

Posted 20.1-0.7-v2 & 20.2-12-v2 with the fix. It shouldn't crash when you're just using curios.


x-rh-identity tests 3rd part

Description
changes all positive cases in handler tests to use XRH identity (positive cases == good/valid auth token), negative cases coming in next PR
Fixes # (issue)
Type of change
Please delete options that are not relevant.

Refactor (refactoring code, removing useless files)
Unit tests (no changes in the code)

Testing steps
make before_commit
Checklist

[x] make before_commit passes
[x] updated documentation wherever necessary
[x] added or modified tests if necessary
[x] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch and project coverage have no change.

Comparison is base (9ef2286) 69.36% compared to head (2494d8d) 69.36%.

:exclamation: Current head 2494d8d differs from pull request most recent head a888ca1. Consider uploading reports for the commit a888ca1 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1061   +/-   ##
=======================================
  Coverage   69.36%   69.36%
=======================================
  Files          25       25
  Lines        3626     3626
=======================================
  Hits         2515     2515
  Misses        851      851
  Partials      260      260

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


 Weird thing is that https://reddit.com/r/investing.json?raw_json=1 does exist. Any ideas

import (
	"fmt"
	"time"

	"github.com/turnage/graw/reddit"
)

func main() {
	userAgent := "graw:doc_demo_bot:0.3.1 by /u/datlolbot"
	script, _ := reddit.NewScript(userAgent, time.Second)
	fmt.Println(script.Thread("r/investing"))
}

I reproduced locally. It looks like reddit has changed a policy and is denying access to that path based on the client.


Validate translation field

How Can i validate a translation field?
use Doctrine\ORM\Mapping as ORM;
use Knp\DoctrineBehaviors\Model as ORMBehaviors;
use Em\Bundle\CmsBundle\Entity\Metatag;
use Symfony\Component\Validator\Constraints as Assert;

/**
 * @ORM\Entity
 * @ORM\Table(name="zona_translation")
 */
class ZonaTranslation
{
    use ORMBehaviors\Translatable\Translation ;

    /**
     * @ORM\Column(type="string", nullable=true)
     * @Assert\NotBlank()
     */
    private $title;

I would like to reopen this issue, because now I run into same question. How translatable entities is supposed to be validated? How I should declare FormType for translatable entity?

ha, an idea comes to my mind: you need to add a @Assert\Valid on the translatable field, in order to let the validator walker walk through the children.
Otherwise, it's a typical form.

Adding a validation.yml to the bundels config appears to work:
Class\Of\Translatable\Entity:
    properties:
        translations:
            - Valid: ~

Taken from https://github.com/a2lix/TranslationFormBundle/issues/104#issuecomment-62743276

not work


403 Error

I followed the instructions on this page with a File.. New Asp.Net 4.6.2 site but when I try to access the site (via the IP given using docker inspect and port 8000) I get 403 - Forbidden: Access is denied
I'm not sure if this is a copy of https://github.com/Microsoft/Virtualization-Documentation/issues/181
but if not to repro follow the steps as outlined in the readme.md using a default 4.6.2 file new (MVC) project from Visual Studio

Is your image on DockerHub? I can pull it down locally and have a look?
(Sorry for the late reply)

hey there, a little bit late but maybe it helps:
you can add a local user to the admin group of the container and browse/access your iis app with it

Hey there, I am still stuck at this too. The image is built and ran properly, but whenever i visit the binded port, it always gives me 403 error. Is there anyway we can resolve this via commandline?

issues i faced where also 403, i resolved it the following way:

Adding a user so i can connect trough IIS Manager:

RUN	NET USER testing "Password01!" /ADD
RUN	NET LOCALGROUP "Administrators" "testing" /add

Grant Permissions:
RUN icacls "C:\IIS\*" /grant everyone:(OI)(CI)F /T

Install neccassary features

RUN powershell Install-WindowsFeature Web-Mgmt-Service
RUN powershell Install-WindowsFeature Web-Windows-Auth
RUN powershell Install-WindowsFeature NET-Framework-45-ASPNET
RUN powershell Install-WindowsFeature Web-Asp-Net45
RUN powershell Install-WindowsFeature NET-WCF-HTTP-Activation45

Start Service and make it autorun

RUN net start wmsvc
RUN sc config WMSVC start= auto

RUN powershell -NoProfile -Command \
Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\WebManagement\Server -Name EnableRemoteManagement -Value 1

Expose Ports

EXPOSE 80
EXPOSE 8172
EXPOSE 443

Last step:
On the IIS Server Node, go to "Feature Delegation" and give Read/Write permissions to missing stuff

never the less it strongly depends how your application work, regards autorization and so on, also i would aktivate error pages to see what kind of 403 it is, there are like 3 or 4 different kinds.
hope this helps

I was stuck on this issue until I determined my app was not being published to an accessible folder. Note: I only ran into this problem using the windowsservercore image. My COPY line was incorrectly:
COPY . .

I changed it to the line below and it worked perfectly:
COPY . /inetpub/wwwroot

Hope this helps a few people running into the 403 error. Note: you still have to hit the container ip directly by running docker ps and copying the container hash and then running docker inspect -f "{{ .NetworkSettings.Networks.nat.IPAddress }}" HASH to find the container ip address.

Hi All, This is Ravi, my docker engine runnin gon windows 2016 physical machine. I pulled all images like iis, dotnet, aspnet, sql ... I successfully deployed musicstore application on the same machine. Now, I am trying to my In-house application containerization. i can able to build the image and run successfully. I am getting 403 error while the same by using container IP. Could you please help me to overcome this problem? Thanks in Advance.

It's hard to diagnose why you might be getting a 403 without more information. If you have your image pushed to DockerHub, I can pull it down and have a look?
My first guess with no additional information is that your file ACLs might prevent the AppPoolIdentity from accessing your application contents. Try ensuring the IUSRS group has access to the folder where your application exists.

Hi Shirhatti... Thanks for your reply.... Could you please provide your mail id to share all my work. or please send test mail to<EMAIL_ADDRESS>and i will reply for the same. Thanks a lot n lot. Please do the need.

Hello Sourabh, I have sent mail to you. Could you please check? Please do the need. Thanks in Advance

Hello Sourabh, Did you try at your end? Can u please do the need?

Hello All, Any inputs on my query? Please .....

@scrambledheads I'm going to close this issue since it's probably stale at this point. Feel free to open an issue if your issue persists

Make sure that your files not ignore in .dockerignore
copy this Dockerfile
`
FROM microsoft/aspnet
WORKDIR /inetpub/wwwroot
COPY . /inetpub/wwwroot

Give Full Access To Folder
RUN icacls 'c:/inetpub/wwwroot' /grant 'Everyone:(OI)(CI)F'
Check that the files have been successfully copied
RUN dir
`
3) docker build -t test .
4) docker run -p 8001:80 test

Make sure that your files not ignore in .dockerignore
copy this Dockerfile

FROM microsoft/aspnet
WORKDIR /inetpub/wwwroot
COPY . /inetpub/wwwroot
# Give Full Access To Folder
RUN icacls 'c:/inetpub/wwwroot' /grant 'Everyone:(OI)(CI)F'
# Check that the files have been successfully copied
RUN dir

docker build -t test .
docker run -p 8001:80 test

Anyone share the solution to this error. No Solution provided above is working

Make sure that your files not ignore in .dockerignore
copy this Dockerfile

FROM microsoft/aspnet
WORKDIR /inetpub/wwwroot
COPY . /inetpub/wwwroot
# Give Full Access To Folder
RUN icacls 'c:/inetpub/wwwroot' /grant 'Everyone:(OI)(CI)F'
# Check that the files have been successfully copied
RUN dir

docker build -t test .
docker run -p 8001:80 test

your solution is also not working for me. Can you please help me with this problem??

i think microsoft fix there problems in diffrent docker images
best way to check it is to use last version of visual studio 2019 and add docker support from there
its create for you dockerfile & dockerignore file

I am not able to add docker support for existing project. I can get that option for new project but I don't find that option on existing project.

I'm having the same issue.
I think it might be related to windows 2019.  I built it in my local on Windows 10 and it works.  However, when I try to build it in Windows Server 2019 I get the same error.
I tried changing the permissions but it didn't work
icacls c:\MyApps /grant Everyone:(OI)(CI)F /T

I'm having the same issue.
I think it might be related to windows 2019.  I built it in my local on Windows 10 and it works.  However, when I try to build it in Windows Server 2019 I get the same error.
I tried changing the permissions but it didn't work
icacls c:\MyApps /grant Everyone:(OI)(CI)F /T


fix: nil client causes panic

This PR

fixes #407

related to: https://github.com/open-feature/go-sdk/issues/238

Thanks @bacherfl and @thisthat !


Provide non-fatal errors in QoS metric events

As a Pillarbox developer I want to be able to better understand non-fatal playback errors that might negatively affect the playback experience.
Acceptance criteria

Non-fatal errors are provided in Pillarbox metric events.

Tasks

[ ] Report error log events in Pillarbox metric events.

Since too many useful changes were made in #924 I will start the work on a branch 927/warnings created on top of the existing branch for #924, currently in code review.
We will then cherry-pick the commits into the branch associated with #927 once the PR for #924 has been merged.

Until we can use AVMetrics all errors fetched from the error log, whose severity is unknown, will be reported as warnings. We might therefore have duplicate a warning also received from the log when a fatal error is encountered, but this should be acceptable.


Update tracing_subsciber to 0.3 which uses 'time' instead of 'chrono'

Signed-off-by: Lukasz Woznicki<EMAIL_ADDRESS>Proposed changes
Use latest tracing_subscriber which has moved to crate time.
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@makr11st there are merge conflicts, can you rebase this on latest main, please? :smiley:


[identity] DefaultAzureCredentials do not work properly under a proxy environment

Package Name: @azure.identity
Package Version: 4.0.0
Operating system: Windows 11 Enterprise 22H2
[ ] nodejs

version: v20.11.1

[ ] browser

~name/version:~

[ ] typescript

version: 4.9.5

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
The DefaultAzureCredential will attempt to authenticate via the following mechanisms in order:

Environment -> Workload Identity -> Managed Identity -> Azure Developer CLI -> Azrue CLI -> Azure PowerShell

However, when under a proxy environment, the DefaultAzureCredential is unable to utilize mechanisms beyond Managed Identity. Specifically, within a proxy environment, authentication with Managed Identity fails because it attempts to access the Managed Identity endpoint (<IP_ADDRESS>) and encounters an error, which prevents it from proceeding to the Azure Developer CLI credentials.
debug.log
To Reproduce
Steps to reproduce the behavior:
"Note: Use Fiddler as an alternative to Proxy."

Save the following source code.

const { DefaultAzureCredential } = require("@azure/identity");

async function main() {
  const credential = new DefaultAzureCredential();
  const token = await credential.getToken(
    "https://management.azure.com/.default"
  );

  console.log("Token:", token.token);
  console.log("Expires On:", token.expiresOnTimestamp);
}

main().catch((error) => {
  console.error("An error occurred:", error);
});

Open Command Prompt.
Set the environment variables:

set AZURE_LOG_LEVEL=verbose
set https_proxy=http://localhost:8888/ # For Fiddler
set http_proxy=http://localhost:8888/ # For Fiddler

Launch Fiddler.
Execute the file from step 1

node main.js

Expected behavior
The behavior should be the same as when not under a Proxy environment.
Attempting authentication using the credentials of Azure Developer CLI -> Azure CLI -> Azure PowerShell, without stopping at Managed Identity.
Additional context

Setting the environment variable AZURE_POD_IDENTITY_AUTHORITY_HOST to empty can circumvent the issue.
Although I cannot reproduce it in my environment, I have confirmed that in a different proxy environment, a 403 error occurs, and it stops at the authentication with Managed Identity.

For some reason, the proxyPolicy isn't used for the internal IdentityClient?

Hiya @iamkdada - You're quite right that Managed Identity does not work with a proxy as documented in our TROUBLESHOOTING guide
The bug you described, however, is actually slated to be fixed in our next GA release (4.5.0) which will go out in October. We will ensure ManagedIdentityCredential throws the correct error, so that DefaultAzureCredential is able to continue to the next credential in the chain. Appreciate your patience and I apologize for the delay in answering here


Terminal does not close upon exit when preference is set

I have the terminal installed in Atom 1.6 on OS X 10.11.4. I have the preference set to close the terminal when the session exits. This does not work. I open a terminal session, type "exit", and the terminal window is still open.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Invalid, this works and its obsolete Atom and pio-ide-terminal, @ivankravets please close


revamp kexec test and a fix for op-test --list-suite option

There are three patches to improve kexec tests
OpTestKexec: add test suite for kexec
OpTestKexec: revamp kexec test cases
OpTestKexec: simplify setUp function
And a patch that fixes and issue with --list-suite option
op-test: Align doc string for system access suite

@sourabhjains I will run these tests and verify

@sourabhjains I will run these tests and verify

Thanks, it will be helpful.

@sourabhjains I will run these tests and verify

I did run the testcases . I executed all cases successfully .  Total time taken was approximately 42 minutes for all testcases including multiboot scenarios with  10 iterations. May be need some updates to logging
Run the testsuite:
#time ./op-test -c machine_lp6-rhel93-ltcever7x0.config --run testcases.OpTestKexec
.
.
.
.
Ran 5 tests in 2475.558s
OK
2023-09-05 12:57:11,111:op-test::INFO:Exit with Result errors="0" and failures="0"
[console-expect]#
real    42m2.234s
user    0m3.212s
sys     0m0.371s

@sourabhjains I will run these tests and verify

I did run the testcases . I executed all cases successfully . Total time taken was approximately 42 minutes for all testcases including multiboot scenarios with 10 iterations. May be need some updates to logging

Thanks for the effort @SACHIN-BAPPALIGE.
Were you able to able to run kexec test individually?

Sourabh

Few updates to the pull request:

update test description
update test_kexec_in_loop to log a message every time kexec is performed (as per @SACHIN-BAPPALIGE )

Link to compare the above changes:
https://github.com/open-power/op-test/compare/c77d5cd614cb097d46e6ad609896afbf528d2f5a..6bf9b6b0ee7e6770b9b28ba7a1950abd0f8e56ef
Thanks
Sourabh

Two changes as per @abdhaleegit

use existing library function to find distro name instead to writing our own.
Update execute_kexec_cmd function to provide option to close console post command execution via console

Diff: https://github.com/open-power/op-test/compare/6bf9b6b0ee7e6770b9b28ba7a1950abd0f8e56ef..6a249c769838ba62677f0c5893eab6efb47c569e

@abdhaleegit Please find my ACK with this message. Thank You.

@SACHIN-BAPPALIGE waiting for latest logs

@SACHIN-BAPPALIGE test logs for RHEL and SLES

@sourabhjains  @abdhaleegit  :  Test failed with this signature . Please check
ERROR: test_kexec_in_loop (testcases.OpTestKexec.OpTestKexec)
Traceback (most recent call last):
File "/root/kexec_sourabh_latest/op-test/testcases/OpTestKexec.py", line 128, in setUp
self.populate_kernel_initrd_image()
File "/root/kexec_sourabh_latest/op-test/testcases/OpTestKexec.py", line 78, in populate_kernel_initrd_image
distro = self.op_test_util.distro_name()
File "/root/kexec_sourabh_latest/op-test/common/OpTestUtil.py", line 2160, in distro_name
res = host.host_run_command("cat /etc/os-release")
File "/root/kexec_sourabh_latest/op-test/common/OpTestHost.py", line 211, in host_run_command
return self.ssh.run_command(i_cmd, timeout, retry)
File "/root/kexec_sourabh_latest/op-test/common/OpTestSSH.py", line 225, in run_command
return self.util.run_command(self, command, timeout, retry)
File "/root/kexec_sourabh_latest/op-test/common/OpTestUtil.py", line 1748, in run_command
output = self.try_command(term_obj, command, timeout)
File "/root/kexec_sourabh_latest/op-test/common/OpTestUtil.py", line 1768, in try_command
pty = term_obj.get_console()
File "/root/kexec_sourabh_latest/op-test/common/OpTestSSH.py", line 205, in get_console
self.connect(logger)
File "/root/kexec_sourabh_latest/op-test/common/OpTestSSH.py", line 185, in connect
self.check_set_term()
File "/root/kexec_sourabh_latest/op-test/common/OpTestSSH.py", line 201, in check_set_term
self, setup_term_flag)
File "/root/kexec_sourabh_latest/op-test/common/OpTestUtil.py", line 1643, in setup_term
msg="Getting login and sudo not successful, probably connection issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="command-line line 0: Unsupported option "afstokenpassing"
Activate the web console with: systemctl enable --now cockpit.socket
Register this system with Red Hat Insights: insights-client --register
Create an account or view all your systems at https://red.ht/insights-dashboard
Last login: Fri Sep  8 08:49:28 2023 from <IP_ADDRESS>
"
Expect After Buffer="<class 'pexpect.exceptions.EOF'>"
Message="Getting login and sudo not successful, probably connection issue, retry"
Ran 5 tests in 925.546s
FAILED (errors=1)
2023-09-08 09:04:55,192:op-test::INFO:Exit with Result errors="1" and failures="0"
2023-09-08 09:04:55,251:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2023-09-08 09:04:55,251:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /root/kexec_sourabh_latest/op-test/test-reports/test-run-20230908084808/debug
2023-09-08 09:04:55,251:op-test.common.OpTestUtil:dump_versions:INFO:

@sourabhjains @abdhaleegit : Test failed with this signature . Please check

Can you please share the command you used to run the test.
Thanks,
Sourabh

Made a small change in kexec in loop test, print the loop count from 1 to n instead of 0 to n-1. n is loop count configured by user.
Changes done:
https://github.com/open-power/op-test/compare/6a249c769838ba62677f0c5893eab6efb47c569e..2389faf5bef38c29e2a3cac65caf057562b1c8dc

@sourabhjains @abdhaleegit  I completed  kexec testsuite execution  in 2 methods  as shown below . It passed

./op-test -c machine_lp6.config --run testcases.OpTestKexec
Logs for review available at TestNode:/root/kexec_sourabh_latest/op-test/test-reports/test-run-20230910212728

./op-test -c machine_lp6.config --run-suite kexec-suite
Logs for review available at Testnode:/root/kexec_sourabh_latest/op-test/test-reports/test-run-20230910210517

@sourabhjains Thanks for the PR

@sourabhjains @abdhaleegit I completed kexec testsuite execution in 2 methods as shown below . It passed

./op-test -c machine_lp6.config --run testcases.OpTestKexec
Logs for review available at TestNode:/root/kexec_sourabh_latest/op-test/test-reports/test-run-20230910212728
./op-test -c machine_lp6.config --run-suite kexec-suite
Logs for review available at Testnode:/root/kexec_sourabh_latest/op-test/test-reports/test-run-20230910210517

@SACHIN-BAPPALIGE Thanks for testing the patch multiple times.
Thanks @abdhaleegit for accepting the patch.


Update raycast-arcade extension

Description
✨ It's update time! Get ready for new features, new games, fixes, and more!
Game Search
Don't want to have all of the games cluttering your Raycast? Introducing Game Search, a centralized place to access all your games. Read a bit about the game, see highlights, and more!
Games are still available as commands, so you can pick and choose by disabiling them in Raycast Settings.
New Games

🔢 2048: The number merging game you just can't miss! The beautiful design is nearly identical to the original, and you're sure to have a blast with this one.

🐍 Snake: Have fun navigating your snake through a board to grab apples! Try not to hit the walls or your own tail, though!

New Features

🎨 Game Icons: Each game now has its unique icon... huge thank-you to Krishna AR on Slack for designing the original icons!
🟩 Wordle: Grab your dictionary, because Wordle just got better. By an Unlimited amount! Play Wordle infinitely in the new mode, and check statistics on both modes with the new Statistics tab!

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Not too sure how to resolve this merge conflict 😅
It says that its too complicated to resolve in web editor. What should I do?

Hi @EvanZhouDev 🔥
You're on fire! Looks like you have a lot of merge conflicts, could you resolve it?
Maybe it would be a cool idea to only have it in one command, or at least diable all commands in the root, does that make sense?

@pernielsentikaer I’m not too sure how to resolve the merge conflicts! It doesn’t let me do it in the web editor.
Also, having it in “one command” what the new Search is for. You can choose to have it all in one command, or have it split. The user has to control it in their own Raycast settings.

Can you help me understand how to resolve these conflicts? And how to avoid them in the first place?

Did you use the publish command when you pushed? Maybe running npx @raycast/api@latest pull-contributions before publish would do it.
If it goes all wrong, get your extension from the store and fork it, move your new code over in that folder 🙂

@pernielsentikaer running npx @raycast/api@latest pull-contributions does nothing...
Can you elaborate a bit more on your second solution?

Remove the old extension with Manage Extensions and then download it from the Store and use this command

@pernielsentikaer I tried it, and it doesn't work. Still getting the same issue. Any ideas?

And you forked it? Let's close this PR and try to publish again 🙂


When using with Jest, EISDIR: illegal operation on a directory

I have tried starting to use  this package, but running problems on very beginning.
I have test file like this:
// __tests__/index.test.jsx

import { render, screen } from '@testing-library/react'
import { withMockAuth } from '@tomfreudenberg/next-auth-mock/jest'
import Home from '../pages/index'
import '@testing-library/jest-dom'

describe('Home', () => {
  it('renders a heading', () => {
    render(<Home />)

    const heading = screen.getByRole('heading', {
      name: /welcome to next\.js!/i,
    })

    expect(heading).toBeInTheDocument()
  })
})

And when I run jest to test that, I get following error:
 FAIL  __tests__/index.test.jsx
  ● Test suite failed to run

    EISDIR: illegal operation on a directory, read

       6 | import '@testing-library/jest-dom'
       7 |
    >  8 | describe('Home', () => {
         |               ^
       9 |   it('renders a heading', () => {
      10 |     render(<Home />)
      11 |

      at Runtime.readFile (node_modules/jest-runtime/build/index.js:2574:21)
      at Object.<anonymous> (__tests__/index.test.jsx:8:15)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.421 s
Ran all test suites related to changed files.

This problem appears whenever I have import for withMockAuth present, ie this line:
import { withMockAuth } from '@tomfreudenberg/next-auth-mock/jest'

If I remove that line, all works as expected (I get error that useSession needs to be wrapped within SessionProvder). Adding that withMockAuth inside render() call doesn't change output in any way from EISDIR error.
I've wiped my node_modules and installed things again, but hasn't changed outcome. Any ideas for further fixing this issue?

Hi @kerbe - thanks for using this component and posting an issue.
I will check that and give you feedback.
Any chance that I may access your sources or at least package.json to check with same conditions?

I stripped code to bare minimum, and pushed to public repo so you can see:
https://github.com/kerbe/next-auth-mock-eisdir-error
That has same package.json as my project. Biggest notepoint might be that it is using NextJS 12.2.2, and not 13.
Actual code is same structure as my project, but stripped down. That index.test.jsx still gives error when withMockAuth is imported, and doesn't when that line isn't present. Actual test in that file would fail, as it is old placeholder I started to update for real Home component structure.
When I was reducing code for that repo, I thought that maybe ChakraUI and it's ChakraProvider might cause problems, but doesn't seem to be the case. Even when I took Chakra out, and had even when removing MainLayout, problem still remained. So left those for clarity, if there are something rising during this bug hunt, that those cause.

Pretty cool, thanks for your invest!
I will check that today

Any update on this @TomFreudenberg?

Hi @kerbe
sorry for late reply, I was on a project-trip for the last time. I will follow up starting new year.
Cheers
Tom


Feature/steps embeds a Dockerfile inside a image resource field

Still needs to resolve env var inside the dobifile. But its working.
implements idea from https://github.com/dnephin/dobi/issues/51

This is still failing to write hidden files to the tarball

@dnephin Can you take a look at this? Let me know if there is anything I improve upon.

Yes, I'd like to get this merged, but I'm still not really liking the []map[string[string.
I'd like to use just a string, like this https://github.com/dnephin/dobi/commit/8f0c5b317e54a330d61232630ecc2fd05f5f816e
I'm waiting for https://github.com/docker/docker/pull/31236 to get merged, so that we can re-use a lot of the same code.

Cool, I think I have already fixed this
https://github.com/dnephin/dobi/blob/bef9b4573f27f786d71215d0423a1f9df072f7c4/config/image.go#L40
I will take a look a the upstream PR!

Thank you again for starting this work! This is a really cool feature.
I opened #94 which includes your commits (squashed). I updated it to use the code from docker/cli for reading a dockerfile from stdin, and reading the dockerignore file.


[FEATURE] Workflow for Auto-assigning a reviewer to a PR

Description
A gh actions workflow for auto-assinging a set reviewer to a PR will increase the efficiency of work & make the process of reviewing fast!
Screenshots
No response
Additional information
No response

Creating a PR for this one


Improve popup behavior

@jmandel wrote:

For the "open in new window" button, for me at least it'd be great to have the ability to open this in a new tab in my existing window (by default, or else by detecting when I ctrl-click). This can be accomplished by omitting the height/weidth/menubar options to window.open. This is helpful for me at l least when I'm sharing a single window on my desktop and want to show the launcher in action (otherwise the patient picker "escapes" the screenshare).

This is a great idea but more more complicated than it looks. Several problems to consider:

Most people are already used to a popup version
Yes, popups are bad, I know...
New tab is not currently an option because the patient browser detects that it is not within a popup or frame and renders as normal patient browser instead of picker dialog (no OK/Cancel buttons and no way to send the selection back to the opener). This may be easy to change but I am afraid to touch it now, until I am ready and have the time to do major dependencies update of that 5+ years old app...

All that said, I think the only solution that addresses everything is to put the dialog within an artificial iframe popup. Feels like a popup, renders within the same window and even closes with Esc (unless the focus is within the iframe).


what kind of framework dose this project use ?

There seems not django or similar framework adopted in this project ,any one can tell ne what kind of technology used here ?

Please visit our developer document at https://developers.home-assistant.io

Please do not post off-topic message. Feel free to open a discussion either on our forums or discord channel. For Chinese information, you can visit unofficial Chinese forums


1.0.4 broke older nightlies

error[E0658]: the unsafe_op_in_unsafe_fn lint is unstable
--> /b/workspace/PVT_DCB214_AUTO_EVPN/obj/common/build/rust/cargo_home/juniper/registry/src/cdo-jss-artifactory.juniper.net-97e0f04ae14acc60/semver-1.0.4/src/lib.rs:66:50
|
66 | #![cfg_attr(not(no_unsafe_op_in_unsafe_fn_lint), deny(unsafe_op_in_unsafe_fn))]
|                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #71668 https://github.com/rust-lang/rust/issues/71668 for more information
= help: add #![feature(unsafe_block_in_unsafe_fn)] to the crate attributes to enable

This crate does not support old nightly compilers. In general it is not reasonable to expect crates to support arbitrary old nightly compilers.


serving 🦕 Sauropod emoji in header

SO.... as this is a P0 I rushed to do this.  But when I ran it in my dev server node died.  Very disappointed, very lame.  Do we protest quit programming?!??!?
(node:1279) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["dyna-powered"]
    at ServerResponse.setHeader (_http_outgoing.js:473:3)
    at setHeader (/c/Users/ryan/Documents/projects/boring/src/lib/init-hooks/core-hooks/boring_header.js:12:11)
    at deferedMiddleware (/c/Users/ryan/Documents/projects/boring/src/lib/server/appUseOverride.js:46:7)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Maybe if I convert that to Unicode... but how many browsers will melt

K, my last commit fixed the issue by converting it to a buffer and calling toString('binary') format.


ZF 2.4.0 form validation BC break

I don't see any documentation notes about form validation BC break.
Here's the case:
    $form = new \Zend\Form\Form();
    $form->add(array(
        'type' => 'Text',
        'name' => 'email',
    ));
    $form->getInputFilter()->add(array(
        'name' => 'email',
        'required' => false,
        'allow_empty' => false,
        'continue_if_empty' => false,
    ));

    $data = array(
        'foo' => 'bar',
    );

    $form->setData($data);
    if ($form->isValid()) {
        echo "Valid\n";
    } else {
        echo "Invalid\n";
        var_dump($form->getMessages());
    }

Output:
ZF 2.3.7
   Valid

ZF 2.4.0
   Invalid

   array (size=1)
     'email' =>
       array (size=1)
         'isEmpty' => string 'Value is required and can't be empty' (length=36)

This break is caused by PR #4567. The exact issue you are experiencing was already mentioned in the comments in that PR: https://github.com/zendframework/zf2/pull/4567#discussion_r4659825

That would allow this to work -- but it also means that order of operations becomes critical -- you would be required to set the "allow empty" flag after setting the required flag if you wanted to set it to false.

Unfortunatelly it was only said in words it was fixed, but no tests have been added to actually show it was fixed :disappointed:
isValid() returns false:
$input = new \Zend\InputFilter\Input();
$input->setName('email')
      ->setRequired(false)
      ->setAllowEmpty(false)
      ->setContinueIfEmpty(false);
var_dump($input->isValid()); // false

different ordering and now isValid() returns true:
$input = new \Zend\InputFilter\Input();
$input->setName('email')
      ->setAllowEmpty(false)
      ->setContinueIfEmpty(false)
      ->setRequired(false);
var_dump($input->isValid()); // true

@Martin-P From https://github.com/zendframework/zf2/pull/4567#issuecomment-19606897 (the answer to your quoted comment):

I believe the correct way to solve is [...] to set "allow empty" flag to the reverse of "required" by default. In fact, the factory was already doing this if the user didn't explicitly specify allow_empty.
I've updated the factory too to ensure that regardless of the order of the specification, the allow_empty flag specified by the user (if any) is always respected..

So, at first glance, order of specifications should not matter.

@Pittiplatsch The problem is exactly the quote you are referring to. By explicitely setting allow_empty in the setRequired() method it creates the ordering problem. I fixed this in Zend\InputFilter\Input, but it also needs fixing in Zend\InputFilter\Factory.
Some specific parameters can only be set at the end when all parameters have been set. That way we avoid getting dependent on the ordering of parameters.

This is fixed with #7474.


(FM-5893) - Adding multinode functionality

This is adding multinode functionality. A new function has been created that allows a puppet run on all of the nodes rather than limiting it to only one node. Tests have also been extended for this function.
It is now possible to run:
execute_manifest_on(hosts, manifest, opts={}) to apply the manifest on all nodes.
It is still possible to run on the default node by using:
execute_manifest(manifest, opts={})
I created sample tests in NTP to run to ensure it is possible to actually use this function and the existing function.
The following is an example of a test I ran:
it 'applies cleanly on' do
execute_manifest_on(hosts, pp, :catch_failures => true) do |r|
expect(r.stderr).not_to match(/error/i)
end
end
it 'applies cleanly' do
execute_manifest(pp, :catch_failures => true) do |r|
expect(r.stderr).not_to match(/error/i)
end
end
I can confirm that when calling execute_manifest the manifest is only applied to the default node and when I run execute_manifest_on the manifest is applied to all of the nodes in the nodeset.

Otherwise +1

I have now created a new section in the README to outline how to use the multi node functionality.


Expand filter after see more

For now, in the datasets filter when we click on See more organizations for example, the page will reload, and the filter accordion doesn't open. It should stay expand.

The filter accordion stays open after page reload