chisel3.internal.ChiselException: operand has escaped the scope of the when in which it was constructed

My code have issue of
"""
[info] - should Test: niconicoProc *** FAILED ***
[info] chisel3.internal.ChiselException: operand has escaped the scope of the when in which it was constructed
[info] at chisel3.internal.throwException$.apply(Error.scala:85)
[info] at chisel3.Data.requireVisible(Data.scala:458)
[info] at chisel3.Data.ref(Data.scala:480)
[info] at chisel3.Element.ref(Element.scala:50)
[info] at chisel3.Bits.binop(Bits.scala:201)
[info] at chisel3.Bool.do_$amp(Bits.scala:1126)
[info] at chisel3.Bool.do_$amp$amp(Bits.scala:1160)
[info] at rob.ROB.$anonfun$new$34(rob.scala:150)
[info] at chisel3.Data.$anonfun$$colon$eq$1(Data.scala:522)
[info] at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
"""
Code:
https://github.com/IAMAl/ChiselLivesMatter/tree/main/niconicoProcessor
sbt version: sbt 1.5.5 (AdoptOpenJDK Java 11.0.11)
tester2 version: "chiseltest" -> "0.3.0+"
Type of issue: bug report
Impact: API modification
What is the current behavior?
internal exception
What is the expected behavior?
no internal exception

The main issue is that you are using Reg inside of your Bundle: https://github.com/IAMAl/ChiselLivesMatter/blob/eae7f85bc69781c7442137c505f59578dbcaabde/niconicoProcessor/src/main/scala/nicoproc/rob/rob.scala#L18
You should not use Reg in there, you should use Reg on the outside whenever you instantiate a Bundle:
class Entry extends Bundle {

    val DataWidth   = params.Parameters.DataWidth
    val LogNumReg   = params.Parameters.LogNumReg+1

    val V       = Bool()
    val W       = Bool()
    val WBRN    = UInt(LogNumReg.W)
    val Data    = UInt(DataWidth.W)
}
...

// Power of 2 Depth Circular Buffer Memory
val BUFF        = RegInit {
  val initWire = Wire(Vec(BUFFLENGTH, new Entry))
  initWire.foreach { w =>
    w.V := false.B
    w.W := false.B // Also, I suggest not naming signals `W`, `.W` is a built-in function in Chisel so this is pretty ambigous
  }
}

val PostDat     = Reg(new Entry)                     // Output from Memory

More info on how to partially initialize registers: https://stackoverflow.com/questions/59049673/how-to-initialize-a-reg-of-bundle-in-chisel/59058082#59058082
Note that on newer versions of Chisel you'll get a better error message here.
I recommend updating first to Chisel 3.4.4 (chiseltest 0.3.4), then to Chisel 3.5.2 (chiseltest 0.5.2) -- you are currently on Chisel 3.4.0 (chiseltest 0.3.0, note that + is not doing anything, you need 0.3.+ if you want it to get the newest minor version).


feat(cache-manager): add refreshAllStores option (close #916)

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature & docs update. Closes #916

@meteorlxy - thanks so much for contributing this and I am looking at this now.


Newer library awailable: winsdk

Hello,
Seems 'winrt' is outdated and not supported. There is community substitute and it has exactly same api:
Is that possible to move to newer one?
https://stackoverflow.com/questions/69610231/why-cant-pip-find-winrt
https://pypi.org/project/winsdk/#history

Waiting on this bug that I filed: https://github.com/pywinrt/python-winsdk/issues/20

winsdk was recently fixed and I have now switched over.


Huge size when using the package?

I have a component called ImageLoaderUtil which I'm using to convert raw images to webp and also place lqip placeholders. But I get huge page sizes when Next.js builds the site.
ImageLoaderUtil.jsx Component

Size of the Page with webp and lqip loaders  when Next.js builds the site.

Size of the Page when I removed webp and lqip loaders

Can someone suggest to me a better solution? 🙂

try loading images dynamically without ssr it will remove images from build


Implement the worker and state merkle tree

send a tx to a worker -> the worker returns a list of account which contain the changes of state -> collect this result by schedule.
and now we should add a para of previous state merkle tree root to generate a new block.

чт, 1 февр. 2018 г. в 10:57, EanCusnaivy<EMAIL_ADDRESS>
Closed #33 https://github.com/AElfProject/AElf/pull/33.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AElfProject/AElf/pull/33#event-1452493047, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AiRYj7DCe-GhVKsqeD0R7QTtz_dkVSakks5tQXyBgaJpZM4RkK7_
.

Thanks


Fixed only_upcoming sensor and optimized function gathering to avoid 429 error

Hello @dylandoamaral !
I took some time during holidays to investigate why this integration was taking a lot of time to start during HomeAssistant boot, and I figured out the recommendation and the upcomings calls where made even if it wasn't in my configuration.
I refactored a bit the gathering code to build it dynamicaly, and now, only the necessary calls are made and I'm going from 25 calls to fetch_upcoming and 2 to fetch_recommendation to only 6 calls to fetch_upcoming
Also, for the only_upcoming next_to_watch sensor, we can't exclude the finished show base on aired vs. completed dates, they can be the same even if a new episode is planned for the next day
Thanks man!

Thank you for your work, it will help many people !

My pleasure man, I hope it will :) Have a great new year!


PC Algorithm (#368)

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

@zacandcheese it seems the tests are not passing. Can you please check why?
@afard Can you please review the code?
@ansleis Can you please review the description of the new features?

I will try to do it by the end of the week.

Sorry, I closed the PR by mistake!

@afard any news on this one?

Unfortunately, I was busy last week. Hopefully, I'll review it this week.

@oualib, I think the tests for Python 3.8 fail because the default version of matplotlib on 3.8 has changed from 3.5.3 to 3.6.1. Apparently, many of our tests rely on internal structures of matplotlib that can be frequently changed between their versions. Can you please look at the failed tests and improve them?

The failing tests on Python 3.8 have been addressed on master. Therefore, updating this branch with master will make the tests pass.

@zacandcheese you still have errors in your unit tests, can you please have a look?

This PR needs an entire review. We need to adapt the code to the new architecture. @zacandcheese if you want we can work together on this.


[tools]: adopt the lit analyzer

We should investigate whether the @lit-labs/analyzer package is ready for our use, and develop a list of missing features or bugs

https://github.com/lit/lit/pull/4148
https://github.com/lit/lit/pull/4135
https://github.com/lit/lit/pull/4132
https://github.com/lit/lit/pull/4126
https://github.com/lit/lit/pull/4075
https://github.com/lit/lit/pull/4065
https://github.com/lit/lit/pull/4006
https://github.com/lit/lit/pull/3812
https://github.com/lit/lit/pull/4167
https://github.com/lit/lit/issues/4152 (workaround implemented in pfe)

blocked on lit analyzer not being ready yet


[Fixed] highlighting of two nav-icon on click of about icon

Description of PR
two nav icons are highlighted i.e. about and blog icon.
Relevant Issues
Fixes #2156
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

Seems to have been fixed already


Spotify Rebuilding Error

Information

2.2.4
Linux (Kali Linux)
Spotify Apk from APKPure (Original Playstore Version)

Stacktrace/Logcat
Logcat attached below
Steps to Reproduce

apktool d -f -o Spotify /root/Desktop/Spotify\ Music_v<IP_ADDRESS>1_apkpure.com.apk
apktool b Spotify -vvv

APK
https://download.apkpure.com/b/apk/Y29tLnNwb3RpZnkubXVzaWNfMjA5NzIzMzRfNTIwNDcxZGY?_fn=U3BvdGlmeSBNdXNpY192OC40LjkuMjcxX2Fwa3B1cmUuY29tLmFwaw%3D%3D&k=fc37aa73e69ccaea35c8a49217032a155989a597&as=a394fc3c341e2bdb5043352cfeb19fe95987030f&_p=Y29tLnNwb3RpZnkubXVzaWM%3D&c=1|MUSIC_AND_AUDIO
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything?
Yes
If you are trying to install a modified apk, did you resign it?
I can't rebuild it
Are you using the latest apktool version?
Yes, the version 2.2.4

spotifylog.txt

➜  Bug1581 apktool d com.spotify.music_v<IP_ADDRESS>1-20972334_Android-4.0.3.apk
I: Using Apktool 2.2.4 on com.spotify.music_v<IP_ADDRESS>1-20972334_Android-4.0.3.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: /home/ibotpeaches/.local/share/apktool/framework/1.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling classes.dex...
I: Baksmaling classes2.dex...
I: Baksmaling classes3.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
➜  Bug1581 apktool b com.spotify.music_v<IP_ADDRESS>1-20972334_Android-4.0.3
I: Using Apktool 2.2.4
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether sources has changed...
I: Smaling smali_classes3 folder into classes3.dex...
I: Checking whether sources has changed...
I: Smaling smali_classes2 folder into classes2.dex...
I: Checking whether resources has changed...
I: Building resources...
I: Copying libs... (/lib)
I: Building apk file...
I: Copying unknown files/dir...
➜  Bug1581

Couldn't duplicate. From your error log, there was no error. Execution simply stopped and died out. There isn't any error to look for. Perhaps execution took too long and something killed the binary from running?

I don't know, I wasn't running nothing else and facebook app which tooks me more time to rebuild than the spotify one works perfectly


Simplify live demo

This is more of an idea than an issue, when i was using the demo app, i was annoyed with the way that i had to go back to the main transitions page, hitting back multiple times or changing the url by hand is not a very nice experience, so i decided to just put a link to the main transitions page to avoid this, then i found out that multiple different apps are being build for each transition, is there any good reason why ?
why not do something like this https://codesandbox.io/s/04mloy8xlw
its very common to have multiple different transitions in the same app, and using it like this is a nice way to work with them, if css-modules were supported it would be even better.

Hi, thanks for the PR. Let's move the discussion to https://github.com/trungdq88/react-router-page-transition/pull/37#pullrequestreview-99133271 and close this issue.
Feel free to reopen if necessary.


Improve Mentions Example

Right now, the textarea example is quite limited and not very "gist-able". More comments should follow on how to improve the example. Currently, the plan is to mimic the simple example in draft-js-plugins.

This should be much improved after #26


Fixes #541

We could do that but not sure if someone expects to scrape the CLI output instead of using the API. If yes, removing some lines from CLI output could impact their screen scraping logic … but maybe there aren’t any customers that do that OR we anyway do not support anyone to do CLI screen scraping since they should only be using API for automation.
Also, this is not the only place … fmt.Printf() is used throughout this file in places where a debug log may have been appropriate. Should there be a separate issue opened to track which all Printf()s should be changed to logs ?
From: Abhinandan prativadi <notifications<EMAIL_ADDRESS>Reply-To: contiv/netplugin <reply<EMAIL_ADDRESS>Date: Monday, October 17, 2016 at 1:16 PM
To: contiv/netplugin <netplugin<EMAIL_ADDRESS>Cc: srampal <srampal<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>Subject: Re: [contiv/netplugin] Fixes #541 (#578)
@abhinandanpb commented on this pull request.

In netctl/netctl.gohttps://github.com/contiv/netplugin/pull/578#pullrequestreview-4517900:

@@ -65,7 +65,7 @@ func inspectPolicy(ctx *cli.Context) {
tenant := ctx.String("tenant")
policy := ctx.Args()[0]

  fmt.Printf("Inspeting policy: %s tenant: %s\n", policy, tenant)

  fmt.Printf("Inspecting policy: %s tenant: %s\n", policy, tenant)

I think its time to make this a debug log. .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/contiv/netplugin/pull/578#pullrequestreview-4517900, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIL80NttQYvR3eHf3TmrMXhiqTGqdyQRks5q061ygaJpZM4KWPoO.

LGTM other than minor comments. Thanks for taking care of the comments. Please squash all your commits into one.

LGTM. Please squash and resubmit.

This should not have been merged. It failed the test. Who merged it and how?

My bad .. I intended to do squash-commit and apparently ended up doing squash-commit-merge or something like that …
I had already tested my changes several times. The additional 1-line change was from Gaurav.
Rgds,
Sanjeev
From: jojimt <notifications<EMAIL_ADDRESS>Reply-To: contiv/netplugin <reply<EMAIL_ADDRESS>Date: Friday, October 28, 2016 at 1:20 AM
To: contiv/netplugin <netplugin<EMAIL_ADDRESS>Cc: srampal <srampal<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [contiv/netplugin] Fixes #541 (#578)
This should not have been merged. It failed the test. Who merged it and how?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/contiv/netplugin/pull/578#issuecomment-256838683, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIL80AeHA_fqdofBSJXr4n0D9uQdKBIsks5q4YY1gaJpZM4KWPoO.

@srampal the top of the tree is broken with compile error. Can you please take care of it ?


Poll Interval Info(milliseconds->seconds) and Value(500->60) modified

poll interval value poll in asus_fanmode.conf was set to 500 (probably assuming it to be milliseconds). But, in asus_fanmode.cpp it is being passed to usleep() as poll * 1000 which actually makes the time as poll seconds since it is again multiplied by 1000 to convert milliseconds to seconds. Hence, I've changed the poll value to 60 (i.e. 60 seconds) and the comment is modified to # Poll interval in seconds

usleep() - https://man7.org/linux/man-pages/man3/usleep.3.html
poll * 1000 is used to convert from milliseconds to microseconds.

usleep() - https://man7.org/linux/man-pages/man3/usleep.3.html
poll * 1000 is used to convert from milliseconds to microseconds.


Building PHP docker image for interop tests sometimes fails

Probably the most common cause of interop tests these days is failure to build PHP docker image. That is probably because PHP's build_interop.sh script does actions that can be flaky? Can installing prerequisites be move to the Dockerfile itself? That would also speed up PHP docker build which would be nice - PHP seems to take the most time.
https://grpc-testing.appspot.com/job/gRPC_interop_master/1323/console
Package "__uri/Protobuf" dependency "pear.php.net/Console_CommandLine" has no releases
__uri/Protobuf requires package "pear/Console_CommandLine" (version >= 1.1.0)
No valid packages found
install failed
+ EXITCODE=1
+ docker rm -f build_grpc_interop_php_d9473f0c-b49d-44d2-9d9d-0a6b18fc42d5
build_grpc_interop_php_d9473f0c-b49d-44d2-9d9d-0a6b18fc42d5
+ exit 1

FAILED: build_docker_php [ret=1, pid=20039]

Similar issue:
https://grpc-testing.appspot.com/job/gRPC_interop_master/1507/console
Loading composer repositories with package information

  [Composer\Repository\InvalidRepositoryException]
  No valid composer.json was found in any branch or tag of https://github.com/stanley-cheung/Protobuf-PHP, could not load a package from it.

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [packages1] ... [packagesN]

+ EXITCODE=1

I've this one several times today:
https://grpc-testing.appspot.com/view/Pull requests/job/gRPC_interop_pull_requests/677/console
Starting to download Console_CommandLine-1.2.0.tgz (39,740 bytes)
.........done: 39,740 bytes
install ok: channel://pear.php.net/Console_CommandLine-1.2.0
install ok: channel://__uri/Protobuf-1.0
Failed to clone the git@github.com:stanley-cheung/Protobuf-PHP.git repository, try running in interactive mode so that you can enter your GitHub credentials

  [RuntimeException]
  Failed to execute git clone --mirror 'git@github.com:stanley-cheung/Protobuf-PHP.git' '/root/.composer/cache/vcs/git-github.com-stanley-cheung-Protobuf-PHP.git/'

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [packages1] ... [packagesN]

+ EXITCODE=1

Lifting to P0 as this seems to be failing too often and slowing down our progress during the fixit. Let's talk today about what we can do.

This probably have to do with the github rate limit. One thing I had previous success on, is to add a file ~/.composer/auth.json with the following content:
{
    "github-oauth": {
        "github.com": "<a 40-char github personal token>"
    }
}

Just happened again: https://grpc-testing.appspot.com/job/gRPC_interop_master/1532/console

Can we somehow make it not clone the git@github.com:stanley-cheung/Protobuf-PHP.git github repo always? Perhaps we could override the cloning source to clone from a local copy of the repo (that would be cached in the base Docker image).
Btw, exact command from https://github.com/grpc/grpc/blob/master/tools/jenkins/grpc_interop_php/build_interop.sh is actually triggering this?

Leaving this open to see if #4371 helps.

Still seeing a similar problem. Occuring repeatedly.
https://grpc-testing.appspot.com/job/gRPC_interop_pull_requests/876/console
Loading composer repositories with package information
Failed to update git@github.com:stanley-cheung/Protobuf-PHP.git, package information from this repository may be outdated (Failed to execute git remote set-url origin 'git@github.com:stanley-cheung/Protobuf-PHP.git' && git remote update --prune origin

)
                                                                                Reading composer.json of datto/protobuf-php (codegen_add_options_param)Reading composer.json of datto/protobuf-php (master)                                                                       Installing dependencies (including require-dev)
  - Installing firebase/php-jwt (v3.0.0)
    Downloading: Connecting...    Failed to download firebase/php-jwt from dist: Could not authenticate against github.com
    Now trying to download from source
  - Installing firebase/php-jwt (v3.0.0)
    Cloning fa8a06e96526eb7c0eeaa47e4f39be59d21f16e1

  - Installing react/promise (v2.2.1)
    Downloading: Connecting...    Failed to download react/promise from dist: Could not authenticate against github.com
    Now trying to download from source
  - Installing react/promise (v2.2.1)
    Cloning 3b6fca09c7d56321057fa8867c8dbe1abf648627

  - Installing guzzlehttp/streams (3.0.0)
    Downloading: Connecting...    Failed to download guzzlehttp/streams from dist: Could not authenticate against github.com
    Now trying to download from source
  - Installing guzzlehttp/streams (3.0.0)
    Cloning 47aaa48e27dae43d39fc1cea0ccf0d84ac1a2ba5

  - Installing guzzlehttp/ringphp (1.1.0)
    Downloading: Connecting...    Failed to download guzzlehttp/ringphp from dist: Could not authenticate against github.com
    Now trying to download from source
  - Installing guzzlehttp/ringphp (1.1.0)
    Cloning dbbb91d7f6c191e5e405e900e3102ac7f261bc0b

  - Installing guzzlehttp/guzzle (5.2.0)
    Downloading: Connecting...    Failed to download guzzlehttp/guzzle from dist: Could not authenticate against github.com
    Now trying to download from source
  - Installing guzzlehttp/guzzle (5.2.0)
    Cloning 475b29ccd411f2fa8a408e64576418728c032cfa

  - Installing google/auth (dev-master b2d0e7b)
    Cloning b2d0e7bdcbe8ccdd0f83a7527ef23bcc202e331a

  - Installing datto/protobuf-php (dev-master c3831c8)
    Cloning c3831c8ef5053f7d9ff2a4f1d3d4082579f2de36
    Failed to download datto/protobuf-php from source: Failed to execute git clone --no-checkout 'git@github.com:stanley-cheung/Protobuf-PHP.git' '/var/local/git/grpc/src/php/vendor/datto/protobuf-php' && cd '/var/local/git/grpc/src/php/vendor/datto/protobuf-php' && git remote add composer 'git@github.com:stanley-cheung/Protobuf-PHP.git' && git fetch composer

    Now trying to download from dist
  - Installing datto/protobuf-php (dev-master c3831c8)
    Downloading: Connecting...

  [Composer\Downloader\TransportException]
  Could not authenticate against github.com

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [packages1] ... [packagesN]

Similar problem seen again at https://grpc-testing.appspot.com/job/gRPC_interop_master/2174/console

@stanley-cheung , we still keep seeing this one  and it's really impacting the reliability of our interop test suite. Let's talk about how to finally resolve this problem.


Avoiding InstancesPOC on final DAM.

Avoiding InstancesPOC on final DAM.

Please, @szenzaro take a look.

Current coverage is 32.01%

Merging #191 into master will decrease coverage by -0.03% as of be18ce3

@@            master    #191   diff @@
======================================
  Files          319     319
  Stmts        11662   11663     +1
  Branches      1465    1465
  Methods          0       0
======================================
- Hit           3737    3734     -3
- Partial        385     387     +2
- Missed        7540    7542     +2

Review entire Coverage Diff as of be18ce3

Powered by Codecov. Updated on successful CI builds.

+1 . Merging


SOME/IP integration tests needed

An SOME/IP integration test should

start databroker
start the feeder
start the example SOME/IP publisher
-(do we need to start a "test subscriber for databroker)

and make sure the system runs, and (correct?) data really is published to databroker. Should support both subscribe and request/response patterns.
Idea: Publish a know number of known data  via the SOME/IP example publisher (e.g. count from 0 to 999), have a test subscriber in databroker subscribe and log every received value. After SOME/IP publisher finishes check, whether test subscriber output contains all expected values.

No one seems to be that interested in SOME/IP, closing it


how to populate data from database in Excel??

Hi
I am beginner for Laravel
Could you please help me, how to populate data from database when creating Excel?
I followed below link. but not clear.  I need to export data from DB table.
Can anyone show me an example code.
http://www.maatwebsite.nl/laravel-excel/docs/export#export
my function code
public function exportMembersList(){
Excel::create('Filename', function($excel) {
})->export('xlsx');
}
I am getting excel sheet with blank. How to get database table in this function??

I found the solution

@shanka12  So what was the solution ?


In viewer in notebooks, if you change camera, the view gets blank

The view also gets blank the first time you load the model until you click play.

@aymanhab This should be solved in dev right now. I just tested on one of the notebooks with a model containing three cameras that was failing before and it works now. Can you confirm if it works for you?

Thanks @AlbertoCasasOrtiz I tested it using an old gltf file with multiple cameras and it seemed to work properly. However for the workshop I'll continue to not embed cameras in gltf files since it's not emphasized in the demo anyway and we have only limited testing cycles to put on it. Thanks for the fix 👍


⚠ Bofrost.fr has degraded performance

In c00841e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1596 ms

Resolved: Bofrost.fr performance has improved in 3de9abc.


Introduce new tag in libvirt_manager

This tag is mostly used in the reproducer case, when we want to iterate
on a deploy without having to wait for the libvirt steps to pass again
(when it's already deployed). It's allowing a faster run.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

recheck

unrelated failure, apparently linked to cert-manager...

recheck

May be interesting to documents the tags we have and their purpose

May be interesting to documents the tags we have and their purpose

I'd like to get the #631 in so that I can update it directly. That's a tag dedicated for the reproducer anyway

May be interesting to documents the tags we have and their purpose

actually, there's already a list of tags of interest in the doc - just updated it :).

/lgtm

/approve


Add support for Rails 4.1 secrets.

This is a first spike for that @josevalim proposed on #2821. Upgrade existing apps will be simple - developers just need to move their keys to the secrets.yml - but on fresh apps its required to add the secret_key key manually. We could still generate a token inside the initializer as a fallback (so the app can boot without this step) or figure out an automatic way of placing the token on the application configuration.

:heart:


Appstudio update test-component-pac-kams

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-kams-on-pull-request has failed.

StatusDurationName

❌ Failed
29 seconds
init

Failure reasontask init has the status "TaskRunImagePullFailed":
The step "init" in TaskRun "test-component-pac-kams-on-pull-request-f9m52-init" failed to pull the image "". The pod errored with the message: "Back-off pulling image "registry.redhat.io/openshift4/ose-tools-rhel8:v4.12@sha256:253d042ecfad7b64593112a4aa3f528d39cb5fe738852e44f009db87964cf051"."

Pipelines as Code CI/test-component-pac-kams-on-pull-request has failed.

StatusDurationName

❌ Failed
29 seconds
init

Failure reasontask init has the status "TaskRunImagePullFailed":
The step "init" in TaskRun "test-component-pac-kams-on-pull-request-f9m52-init" failed to pull the image "". The pod errored with the message: "Back-off pulling image "registry.redhat.io/openshift4/ose-tools-rhel8:v4.12@sha256:253d042ecfad7b64593112a4aa3f528d39cb5fe738852e44f009db87964cf051"."


Using prism within React's dangerouslySetInnerHTML

Is there a way I can highlight the code which is set in React's dangerouslySetInnerHTML?
For some reasons it seems that Prism doesn't see that code. Any advices?

@florinpop17 Can you provide on online example reproducing your issue?

@florinpop17 It worked nicely for me. Make sure you have  and  tags rendered with correct classes.

There's not much we can do without an online example, so I'm closing this issue.


bugfix:TCC branchCommit/branchRollback, branchId is null

Ⅰ. Describe what this PR did
TCC branchCommit/branchRollback, branchId is null
Ⅱ. Does this pull request fix one issue?
fix #1034
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1035 into develop will not change coverage.
The diff coverage is 0%.

@@            Coverage Diff             @@
##             develop    #1035   +/-   ##
==========================================
  Coverage      38.23%   38.23%
  Complexity      1046     1046
==========================================
  Files            218      218
  Lines           8701     8701
  Branches        1086     1086
==========================================
  Hits            3327     3327
  Misses          4953     4953
  Partials         421      421

Impacted Files
Coverage Δ
Complexity Δ

...ava/io/seata/rm/tcc/api/BusinessActionContext.java
0% <0%> (ø)
0 <0> (ø)
: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 c13f832...9a395b4. Read the comment docs.


Acknowledgments

The PDF has an acknowledgment of financial support for DMZ, but no author has those initials.

@drroe
Was this supposed to be your financial support statement? Should this say DRR? No one else would have funding from an NIH grant.
Or is this a mistake entirely? I noticed that the exact same statement is found in the other LiveCoMS best practices guide that you contributed to (https://github.com/dmzuckerman/Sampling-Uncertainty/blob/master/main.pdf) where Daniel M. Zuckerman (DMZ) was an author. So maybe this got copied over by mistake.

I definitely didn't add it (I don't get grants from the NIH since I work for the NIH :smiley:). Seems like a copy/paste error and can be removed.


Type Definitions of operators are less friendly than RxJS v4

I think this would diminish the usability of static typing solutions (e.g. compilation, or autocomplete). As my feeling which was working to migrate my project to RxJS v5, autocomplete and type inference.
For example:

Observable.crate() = Function is too generic type.

It is recognized as just a Function. So autocomplete cannot suggest a callback signature. This is a frustration...

zip()/combineLatest() type definitions are any.

In RxJS v4, they have more descriptive type definitions:

https://github.com/Reactive-Extensions/RxJS/blob/master/ts/core/linq/observable/zip.ts
https://github.com/Reactive-Extensions/RxJS/blob/master/ts/core/linq/observable/combinelatest.ts

But at now, v5's one are still poor if we pass a many observables to them.

https://github.com/ReactiveX/RxJS/blob/7a679b64893eccf402e3705b40322021d1015951/src/Observable.ts#L283
https://github.com/ReactiveX/RxJS/blob/7a679b64893eccf402e3705b40322021d1015951/src/Observable.ts#L199-L201

And in the range my worked, Observable.race()'s type definition is different from RxJS v4's one and it caused my frustration (But fortunately, we may be able to fix the case of race() easily).
These difference would be able to be a regression point of full-rewrittned v5.
How we can resolve this problem?

You may want to check PR https://github.com/ReactiveX/RxJS/pull/1087 especially problem # 2 you have addressed.
It is known current codebase of RxJS5 has some level of weakness to deal with type definitions, trying to enhance it as much as possible. For general type definition enhancements effort, there's PR https://github.com/ReactiveX/RxJS/pull/826 and https://github.com/ReactiveX/RxJS/pull/667 is being considered to have correct interface when interface's composed.
If you have particular enhancement have in mind currently, creating PR to be always welcomed.
Is this answers (at least partially) for you?

@kwonoj
Thank you for your quickly replying.
I wanted to confirm 1) do we have any concrete approach to resolve this problem? 2) How do we have a progress about it?.

If you have particular enhancement have in mind currently, creating PR to be always welcomed.

Of course, I'll send a pull request if I success to crate a nice patch!

Is this answers (at least partially) for you?

At least, I'm trying to fix the issue of race().
And I have not read #826 and #667. I might write some comment to them.
Lastly, do we have any meta tracking issue this problem?

both, by nature of type definition there won't be single concrete resolution could solve it all. For instance, like operator has 1 to N possible argument (problem # 2) could be resolved via definition generators. Else operators which doesn't have correct type definition while it's composed, it may need to be hand crafted per cases.

For latter and prior both, having test covering type definition will help those in general since it'll make code contributor should verify its type definition while updating codebases.
There are couple of issue filed per each cases to track,
https://github.com/ReactiveX/RxJS/issues/661 - test coverage for type definition
https://github.com/ReactiveX/RxJS/issues/642 - type definition errorneus behavior for rx.kitchensink
https://github.com/ReactiveX/RxJS/issues/1060 - general roadmap issue includes type definition enhancement

I've been working to help the team plug some of the typing declaration holes.  The only thing I haven't sat down and looked at "what would this take to fix" is Observable.create/Subject.create since they both have unique signatures, but essentially share the same static field.

Can we identify specific type signatures that we need to improve and create separate issues for them? This issue is so generic I'm not sure how it could be "resolved" completely. There are likely going to be ongoing tweaks to type signatures across the library.
@saneyuki can we close this and set up more specific issues?

@blesh
okay. I'll close this, and file a issue if I find a new compatibility issue.


Pull the latest opae-libs into master.

Coverage remained the same at 63.536% when pulling 5231798cb4294bb591cb0038e6b4f8ba9c373885 on tswhison/pull-libs into c224d5f74f198a245a61849b468b850c449cbfe9 on master.


CO - ELR Message error to DB

From<EMAIL_ADDRESS>This is an automatic email from the CDPHE Electronic Lab Reporting (ELR) system. There was an issue with a file or message submitted by your organization.
Issue Report: Cannot insert the message into the database due to the following reason:

The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.

Common causes for the failure to write a message to the database include the following:

The message contained an end-of-line character in the middle of the record.
The message contained a value that was incompatible with the field's datatype (e.g., an invalid date or a string where there should be a date).

Message ID: AEC70DFB-50CE-485C-AD23-E8C4E9136742
Received by: CDPHE ELR Onboarding
Received on: 2022-07-23 07:30:26
File source: CDC PRIME
File name: covid-19-e93414a5-4446-410e-84c8-2c6269b762ff-20220723073027.hl7
Please review, correct, and resubmit the message.
Please contact<EMAIL_ADDRESS>if you have any questions about this email.
Describe the bug
Message error not reaching data base
Expected behavior
Message sent without error for reporting/resubmission

This is an automatic email from the CDPHE Electronic Lab Reporting (ELR) system. There was an issue with a file or message submitted by your organization.
Issue Report: Cannot insert the message into the database due to the following reason:

The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.

Common causes for the failure to write a message to the database include the following:

The message contained an end-of-line character in the middle of the record.
The message contained a value that was incompatible with the field's datatype (e.g., an invalid date or a string where there should be a date).

Message ID: 90829E4C-0669-4E2E-9D82-23B6CB5BC05C
Received by: CDPHE ELR Onboarding
Received on: 2022-07-29 13:30:21
File source: CDC PRIME
File name: covid-19-feb977ec-d2c6-4383-9dd9-2f1cdd2b15b0-20220729133022.hl7
Please review, correct, and resubmit the message.

@BerniXiongA6 @sarahnw
Over the weekend we received 44 error messages from Colorado. "Error: Missing or Invalid Observation ID". I will add all the message ids in a separate comment.

-----Original Message-----
From<EMAIL_ADDRESS><EMAIL_ADDRESS>Sent: Sunday, July 31, 2022 9:32 PM
To: Report Stream (CDC<EMAIL_ADDRESS>Subject: [CDPHE ELR Onboarding] Error: Missing or Invalid Observation Id
This is an automatic email from the CDPHE Electronic Lab Reporting (ELR) system. There was an issue with a file or message submitted by your organization.
Issue Report: The record submitted contained the following invalid observation identifiers:

95409-9
30525-0

Every record submitted must have at least one observation identifier recognized as valid by CDPHE ELR. (For HL7-formatted files, the lab result must be uniquely identified as a LOINC code in OBX 3.1 in the Order Observation group.)
Common causes for a missing or invalid observation identifier:

For HL7 files, the record is missing an OBX segment or is missing a value in OBX 3.1, or the OBX 3.1 value provided is not recognized by CDPHE ELR (i.e., is not a recognized LOINC).
For flat files, the record contains an escaped () character, or the fields in the message do not match Colorado's standard flat file format.

Message ID: D80D405B-BB71-3388-B93B-241B9FA9DAC9
Received by: CDPHE ELR Onboarding
Received on: 2022-08-01 01:30:47
File source: CDC PRIME
File name: covid-19-fc822788-b4ff-45bd-9d49-dea87294fac9-20220801013048.hl7
Please review, correct, and resubmit the message.
Please contact<EMAIL_ADDRESS>if you have any questions about this email.

-----Original Message-----
From<EMAIL_ADDRESS><EMAIL_ADDRESS>Sent: Sunday, July 31, 2022 9:32 PM
To: Report Stream (CDC<EMAIL_ADDRESS>Subject: [CDPHE ELR Onboarding] Error: Missing or Invalid Observation Id
This is an automatic email from the CDPHE Electronic Lab Reporting (ELR) system. There was an issue with a file or message submitted by your organization.
Issue Report: The record submitted contained the following invalid observation identifiers:

95409-9
30525-0

Every record submitted must have at least one observation identifier recognized as valid by CDPHE ELR. (For HL7-formatted files, the lab result must be uniquely identified as a LOINC code in OBX 3.1 in the Order Observation group.)
Common causes for a missing or invalid observation identifier:

For HL7 files, the record is missing an OBX segment or is missing a value in OBX 3.1, or the OBX 3.1 value provided is not recognized by CDPHE ELR (i.e., is not a recognized LOINC).
For flat files, the record contains an escaped () character, or the fields in the message do not match Colorado's standard flat file format.

Message ID: AEA6118C-B69C-355F-906A-22D6ACB35366
Received by: CDPHE ELR Onboarding
Received on: 2022-08-01 01:30:47
File source: CDC PRIME
File name: covid-19-fc822788-b4ff-45bd-9d49-dea87294fac9-20220801013048.hl7
Please review, correct, and resubmit the message.
Please contact<EMAIL_ADDRESS>if you have any questions about this email.

 These are Cue messages that went to the secondary feed.
First 2 appear to be bad DOBs.
Remainder from 8/1 appear to be ok. Asked for assistance with tracking down what the issue might be.

From CO DPH:
Thank you for checking on these error messages.  The first two were generated from our Onboarding system, which is used for testing.  Given that those were test transactions, I do not think that we need to worry about them.  We could work with how these errors are sent.  We currently have the error messages sent to<EMAIL_ADDRESS> We can add additional email addresses or different addresses for the test environment and the production environment.  Let us know if you would like to make that change.
For the third transaction, you are correct 95409-9 is a valid reportable LOINC code that is now listed on our system.  If the file were submitted today, it should pass.  Unfortunately, our system only holds on to 21 days worth of files, so this file will need to be resubmitted.

Further conversation with Nancy Kesco:

You can tell where the message originated from the "Received by:" line.  As I looked at it just now, all three of these errors were from the test environment.  So, you really do not need to resubmit any of them.

Received by: CDPHE ELR Onboarding
Followed up with Sharon so we know what to look for on these now. Per Nancy we don't need to resubmit. Closing ticket.


Cannot get proper errors

I am trying out a query with ferry and flutter 0.3.2
  await Hive.initFlutter();

  final box = await Hive.openBox<Map<String, dynamic>>("graphql");
  await box.clear();
  final store = HiveStore(box);
  final cache = Cache(store: store);
  final link = HttpLink("http://optimus.thelocaldukan.com");
  final client = Client(
    link: link,
    cache: cache
  );

  return client;
}

now

`logger.i(response.hasErrors);`  -> true
`logger.i(response.graphqlErrors);` -> null

How can i get the errors printed out?

There are both GraphQL errors and link errors on the response object.

There are both GraphQL errors and link errors on the response object.