commits_.archive is not move to archived folder

There are lots of .commits_.archive files under .hoodie directory but there is no files present under .hoodie/archived.
Environment Description
**Hudi version : 0.9.0
Spark version : 3.0.1
Hive version : 3
Hadoop version : 3.2.2
Storage (HDFS/S3/GCS..) : s3
Running on Docker? (yes/no) : no**
By the way these tables are upgraded from hudi 0.7.

Did you ever configure the archive folder manually ?

@danny0405 No I never configure the archive folder manually. Do I need to config it manually? What is the parameter to config?

Are these files generated by the upgrated table or old version table, you can check the file modification time to get a clue.

@danny0405  It is weird that he latest file is generated  two months ago and I didn't see any new archive files recently.  My question is that can I remove these archive file manually? How to make new archive commit under archived directory?

Did your commit metadata files get archiving in normal progress? I think it is okay you remove these legacy archiving files directly, they are currently useless except for CLI statistics purposes.

@njalan Yes, You can clean up old commit files which got created with 0.7.
The issue here I see that with 0.12, why archive is not happening? Do you see any archival happening from last 2 months after you did the upgrade? Ideally new archival should happen automatically. How many active commits you see in active timeline now? Can you share configuration to triage more why archival is not happening?

metadata is not enable on hudi 0.9. I listed the details for one table in ticket https://github.com/apache/hudi/issues/9751. There are like around 10% of my tables has archive commits files in archived folder. I am using default parameter.  But I didn't face any data issues for these tables without new archiving commits.

@njalan Looks like its more of a upgrade issue. I dont see many active commits in the hoodie file list you pasted in another ticket. Archival will kick in for more than 20-30 commits. Let us know if removal of archived commits from .hoodie directory helped in reducing S3 operations (Your other issue) also.
Please let us know if you dont see archival happening when you have more than 30 commits in the timeline.

@ad1happy2go  After remove these archive files steaming job is getting faster. But storage cluster's cpu is not getting down and it is still high because the count of  http to access s3 is not reduced. Is it possible to tune it? In my case there is only job to upsert one table why it requires hundreds of s3 access for one spark streaming micro batch.


bug: Pinned terraform reusable modules not visible by tfsec

Describe the bug
Hi, I have an app calling a set of reusable terraform modules located in a different internal github repo.  I originally had the source defined as the following:
module "cluster_alb" {
  source = "github.com/<MY-ORG>/<MY-REPO>/terraform/modules/ecs/cluster_alb"
...
}

However, when I ran tflint, it failed, complaining that the terraform module needs to be pinned. See error below:

I then revised that source line to be pinned, like this:
module "cluster_alb" {
  source = "github.com/<MY-ORG>/<MY-REPO>//terraform/modules/ecs/cluster_alb?ref=latest"
...
}

Now tflint passes fine!  But I notice when I ran tfsec on command line with that pinned terraform module, it returned 0 problem found.  See screenshot below:

However, if I revert my pinned terraform module to the original line (without being pinned with "?ref=latest"), my tfscan result returned the following (only showing the last portion of the result as there are many issues found):

My question is why tfsec doesn't seem to recognize the pinned terraform module?
To Reproduce
Steps to reproduce the behavior:
My app is in a private repo, so I cannot share the details here to replicate.  But I am providing the output from 'tfsec --debug' in the attachment, please review details there.
Expected behavior
tfsec should be able to recognize the pinned terraform module located in a remote internal github repo.
Output of your tfsec command with --debug flag
Please see attached file for detailed output.
System Info

tfsec version: v1.22.1
terraform version: v1.2.8
OS: windows 10 enterprise

Example Code

Additional context

tfsec-debug.txt

I am still waiting for tfsec team to respond to this issue.  Please don't close it.

Please remove stale label.  I am still waiting to hear from tfsec team regarding this issue.

this looks like its a problem in the module resolution not handling the explicit version. That is actually in https://github.com/aquasecurity/defsec so I'll get it transferred over there and work on it from there

Hi @wenqiglantz !
I opened the issue in Trivy.
/cc @simar7

Tracking here https://github.com/aquasecurity/trivy/issues/5007


docs: Make "listening to network interface" step clear.

Link to the coversation

Ohhh noooo, this happened to me :smile: :pensive:


test controller statuses

This is simply to add more tests.

Current coverage is 51.98%

Merging #48 into master will increase coverage by +2.87% as of 99b44cf

Powered by Codecov. Updated on successful CI builds.

RFR @zeisss @JosephSalisbury @Nesurion

Lets check the mock stuff together, until then: LGTM


modules/battery: Deprioritize capacity /sys value for battery calculation if other methods are available

Closes #3293
The current code for battery calculation seems to assume that the capacity value returns the non-design battery capacity. This is not the case, and it instead returns the design capacity of the battery.
Currently, the capacity value is used above all other methods if it is present in the /sys directory of the battery. This means that the design capacity of the battery will always be displayed regardless of the design-capacity configuration option.
To remedy this issue, I have restructured the code so that the capacity value is only used if the other possible options for calculation have been exhausted beforehand.
This screenshot shows two instances Waybar while the battery is plugged in at full capacity. The top instance is the current release version, and the bottom instance is the code present in this pull request:

This pull request maintains the functionality of the design-capacity configuration option. Here is the previous screenshot taken again with design-capacity set to true:

Please correct me if I have done anything incorrectly in this pull request, as I am not very familiar with the codebase.

The CI failure appears to be unrelated to the code in this pull request

LGTM


Social Proofs are never valid

All social proofs are flagged as invalid. The webview logs:
Failed to load https://gist.github.com/friedger/d789f7afd1aa0f23dd3f87eb40c2673e/raw: Redirect from 'https://gist.github.com/friedger/d789f7afd1aa0f23dd3f87eb40c2673e/raw' to 'https://gist.githubusercontent.com/friedger/d789f7afd1aa0f23dd3f87eb40c2673e/raw' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.", source: file:///android_res/raw/webview.html (0)
See also https://github.com/blockstack/blockstack-browser/issues/1643

This applies to branch of pull request #85

With j2v8, I managed to verify social proofs in the integration tests.


Node-Red needed help

Hello, will anyone help me change it
https://www.yellownote.nl/blog/index.php/2014/01/18/solarpanel-monitoring-via-rasperry-pi/#comment-522
to Node-Red

Hi, thanks for raising an issue.
If you check out our contribution guidelines you'll see we prefer to handle this sort of thing on the forum or slack team. If its a general how-to type question, you could ask a question on Stack Overflow and tag it node-red.
This allows the whole Node-RED user community to help, rather than rely on the core development team.
Thanks!

ok


Add general theme color css classes

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
A CSS class md-color-primary or md-background-color-primary to reduce the need for custom theme mixins. See material lite. They do this.
What is the current behavior?
You have to create custom theme mixins for this.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Simplicity
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Ng4.1.x, MD beta 6
Is there anything else we should know?

This would be very good to style things that are not contained within a material component.

@mbeckenbach Could you please explain more how should it work?
You mean user define md-color-primary and other colors create based on the chosen color?

@m98 Yes, thats what I mean. Should be quite easy with the sass compiler, shouldn't it?

@mbeckenbach! Okay, I got what you mean.
Thanks for the extra information, I just was not sure at the first if you mean this or not.


better discord doesnt load

hey guys,
i'm having this issue where better discord doesn't load. i checked and it's still installed. it doesn't show any themes, plugins, twitch emotes, or better discord settings.
anyone else experiencing this?

also after reinstalling it, it just shows the loading icon in the corner and it just stays there.

it can easily take up to 20 minutes for it to finsih loading, it's very dependent on your connection
if you still got the issue please join us on the BD support server https://discord.gg/2HScm8j

my connection isnt the problem...now it decides to work now...
thanks for replying!


Make ReplyTo address for bank transfer notification the payer not OC

When someone makes a bank transfer contribution, the host admin gets this email. If they hit reply, it goes to<EMAIL_ADDRESS>since that's the address the notification comes from. But if a host admin hits reply on this, they want to reach the payer, so the replyto address should be the contributor.

Are we sure it's done though? @Betree

This wasn't done. I think there's a confusion with https://github.com/opencollective/opencollective/issues/3740, where we've set reply-to to no-reply for multiple emails.
To provide some specs for this issue:

Either the contributor is an individual, and in this case, we can directly set the email
Or it's an org/fund/... and we then need to fetch the admin emails to include them all in the reply-to

We should start seriously considering all our notifications as a whole
@piamancini sounds like a project issue waiting to happen! using @BenJam 's new template.

Hi @Betree, can I work on this?

@MlkMahmud sure! You can check the local Maildev server (http://localhost:1080/#/) to get details about sent emails.


✨ [WIP] Support for Apple Silicon (arm64) Macs

Updating dependencies to pick up support for Apple Silicon (arm64).
Relevant PRs:
https://github.com/Quick/Nimble/pull/827
https://github.com/xcconfigs/xcconfigs/pull/98
This will aid in enabling arm64 support for https://github.com/mas-cli/mas/issues/308.
FYI @phatblat @fabriceb

Thanks for that @chris-araman !

Thanks for that @chris-araman !

Does anything else need to be done before this can be merged?

Does anything else need to be done before this can be merged?

@elliottwilliams, I think we have everything we need here now that @ikesyo has released Quick 3.0.1. Removing the [WIP] tag. Ready for your review.

I've picked up @ikesyo's fix for arm64 with Quick 3.1.0. (Thanks, @ikesyo!)
@elliottwilliams, this is now ready for your review and release.


Fix auto rapid

Codecov Report

Merging #124 (c00b60e) into master (62af4b9) will decrease coverage by 0.02%.
The diff coverage is 17.85%.

@@            Coverage Diff             @@
##           master     #124      +/-   ##
==========================================
- Coverage   29.63%   29.61%   -0.03%
==========================================
  Files          71       71
  Lines       14823    14845      +22
  Branches      253      253
==========================================
+ Hits         4393     4396       +3
- Misses      10177    10196      +19
  Partials      253      253

Impacted Files
Coverage Δ

src/clj/skylobby/fx/mod_sync.clj
3.58% <0.00%> (-0.02%)
:arrow_down:

src/clj/spring_lobby.clj
11.67% <12.00%> (-0.01%)
:arrow_down:

src/clj/skylobby/fx/download.clj
55.00% <100.00%> (ø)

src/clj/spring_lobby/http.clj
25.24% <100.00%> (+0.18%)
:arrow_up:

Continue to review full report at Codecov.

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


Theme error - build failing

I have a (Gitlab) CI pipeline set up for a project where one of the stages builds Sphinx docs (currently, Sphinx version 7.2 in the Gitlab runner) on the branch for any given commit (the Sphinx Makefile build target is called). Usually this never fails, until recently when I started seeing this:
...
Theme error:
An error happened in rendering the page index.
Reason: AttributeError("'TocTree' object has no attribute 'get_toctree_ancestors'")
...

I'm using the Pydata theme (defined in conf.py), and the index.rst ToC directive, which hasn't changed, is below:
.. toctree::
   :maxdepth: 2
   :caption: Contents:

I note the recent version change in Sphinx. I've never seen this before with earlier versions of Sphinx, e.g. 7.0.2, 7.1.2 etc.
I'm not sure if it is Sphinx, or Pydata. Can someone please look at this?

I changed the Sphinx version in the runner to 7.1.2 and the error went away.

So looks like a Sphinx issue after all
https://github.com/sphinx-doc/sphinx/issues/11604

The fix is already merged into main of the theme, but we haven't had a chance to cut a new release yet. Pinning to Sphinx<7.2 is the right fix for now. Unfortunately this Sphinx issue came up at the last minute before their release, and we have a couple of blocking issues that prevent us from an immediate release of the theme.

This ought to be fixed in Sphinx 7.2.1.
A


Assets path helper for Less files

I saw the example forcss.ejs file is working but not for LESS.
Assuming this is not yet supported. I am trying to figure it out but for now, I found a workaround to get the project in production.

Looks like Mincer should support what you are trying to do: https://github.com/nodeca/mincer#using-helpers

@blakevanlan Thanks. Checking it out. Would be great if you support it however.


Is it possible to do semantic role labelling with INCEpTION?

https://en.wikipedia.org/wiki/Semantic_role_labeling#:~:text=In natural language processing%2C semantic,the meaning of the sentence.

@reckart Thank you! I suddenly find I post issue wrongly in this repo. I should post it in INCEpTION project instead.
BTW: can CoNLL-U format contain or are there some other format contain semantic role labelling data?


Throw warnings for exceeding known platform limitations

Not sure if this belongs here or in alexa-app-server.
I spent the last three and a half weeks discovering/troubleshooting the 24k response size limit. Could warnings be thrown in the console so developers would have some clue that the same code will fail on an Alexa device?
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-interface-reference
Response Format
This section documents the format of the response that your service returns. The service for an Alexa skill must send its response in JSON format.
Note the following size limitations for the response:
The outputSpeech response cannot exceed 8000 characters.
All of the text included in a card cannot exceed 8000 characters. This includes the title, content, text, and image URLs.
An image URL (smallImageUrl or largeImageUrl) cannot exceed 2000 characters.
The token included in an audioItem.stream for the AudioPlayer.Play directive cannot exceed 1024 characters.
The url included in an audioItem.stream for the AudioPlayer.Play directive cannot exceed 8000 characters.
The total size of your response cannot exceed 24 kilobytes.
If your response exceeds these limits, the Alexa service returns an error.

Definitely. I think this belongs here, appreciate a PR.

Thanks. Is that something I would do? I'm eager to get involved but a bit of a noob.

Give it a try! See https://github.com/alexa-js/alexa-app/blob/master/CONTRIBUTING.md.

I'll take a stab. I created the fork and now it looks like I have some tuts to catch up on testing, but this seems like a good spot for me to get started. Thanks for the link.

I'll add another related case.  Only certain characters are allowed to be spoken within SSML responses, and if invalid characters are passed it errors the response. I've run into a number of times when pulling data from other APIs that include user input.
As a (very) rough illustration, I've been using the following RegEx/JavaScript blacklist to filter out some bad characters.  It might be worth it to automatically clean the SSML code to make sure it will be valid, perhaps with a good whitelist.
It would likely be optional or a secondary function such as .validatedSay(), given there are a variety of ways to either substitute or remove the text.  Would maybe be best as an add-on library even.
Example:
text = (text || '').replace(/[^\w\s/<>.,-"']/gi, '').replace('&', 'and').replace('=', 'equals').replace('@', 'at');


[MATLAB] Use bit::unpacked_as_ptr in timestamp_array.cc

Describe the enhancement requested
When GH-36250 is merged, remove the local getUnpackedValidityBitmap function from timestamp_array.cc and use the shared utility bit::unpacked_as_ptr.
Component(s)
MATLAB

This issue is no longer relevant because we re-implemented the TimestampArray proxy in terms of the NumericArray proxy. See #36734.


Missing license file in NPM distribution

Hello, is it possible to incorporate the LICENSE file inside the npm package ? Now it's missing. It's implied by MIT license that if licensed under the MIT the source code must be accompanied by full license text. If the license file is not in the npm package a lot of people cannot use it because it's a proprietary code at that point. Patch release with containing a LICENSE file will fix this.
Thank you very much

We'd welcome a PR for this.

There should be no need for PR. If you're using at least<EMAIL_ADDRESS>it will always include the license inside the bundle, and there is now way how to tell npm no to do so.

We publish from the lib/ subdirectory to offer cleaner imports. We do not currently copy LICENSE into that directory before publishing.

Ok get it, I'll provide a PR.


Add a docstring/description property to the pipelines

🛰 Feature
Description
One of the key points of PADL is the integration of the preprocessing and postprocessing into the dl pipeline, so we don't need to track these steps down in the original model and ensure we apply them when inferring.
However, sometimes we still need to inspect our pipeline either because it's been shared by a colleague or it's been some time since we worked with it to check the type of input that it's expecting, the steps that it's making or the meaning of the output. So, in order to enhance and complement the previous property of the PADL pipelines, it could be helpful to allow including a description of the pipeline that could specify the pipeline purpose, the type of input and the meaning of the output.
For example:
my_pipeline = some_prep >> batch >> layer >> unbatch >> some_post
my_pipeline.description =
"""
f is a model for image classification which expects a 3x256x256 torch Tensor and outputs a
dictionary with the three top labels and its score with the format

{
    'label_1': score_1,
    'label_2': score_2,
    'label_3': score_3
}
"""

Good idea.


add policy module migrations when disabled

When we change the parameter on modules.policy.type from one value to another:

kyverno to none
gatekeeper to none
gatekeeper to kyverno not supported
kyverno to gatekeeper not supported

@Al-Pragliola on the rules, how can I get the starting state to configure unsopported?
@nutellinoit if you want to move from "gatekeeper" to "kyverno", is not enougth to remove "gatekeeper" and let furyctl install "kyverno" and vice versa?

I will merge this, fixes have been done on #157


Switch case lib due to bug with ruby style X1Y1Class shapes

By switching from heck to convert_case we auto-fix this issue. The test case shows what was previously not working and how convert_case does work. I spent some time going through the heck library but convert_case seems very popular and "just works" out of the box.
Closes https://github.com/film42/sidekiq-rs/issues/30

Published as v0.9.0.


Sankaku won't go past 1000 images on nightly

Bug description
Sankaku won't go past 1000 images on nightly build
Steps to reproduce

Fresh download of Nightly, deleting everything in appdata to ensure defaults
Sign in to Sankaku, test says "successful"
Try to grab something with 1000+ images (In this case, 2000 images)
Downloads first 1000 images, then sits there forever while trying to populate the next 1000 images.
Even setting packing_enable=false still produces this issue, it will grab 20 at a time until ~1000 then stop.

Expected behavior
Download all images

Did this same setup on non-nightly (deleting appdata again for default settings), and this does not happen, however the 2nd page seems tends to grab ~20 images, then skip 4 image in a row, and repeats this pattern forever.

Bionus, you should take a look at this Sankaku downloader. It uses the beta version of the site and somehow does not have any problems, nor does it need any delays. I ripped 2000 images from Sankaku in about an hour with it. Maybe you can look at the code and figure out how to implement something like that in grabber?
https://github.com/CryShana/Sankaku-Channel-Downloader

Well it is indeed still using the html API instead if the json API. There is already some code for it but it hasn't been completed. Things such as image count, page count and tag category's are all broken in it.


Foundry 0.7.4 Multilevel toksen duplication with Furnace

When I tried to make a macro run with Multilevel tokens in 0.7.4 I realised that there are two of everything related to Multilevel tokens, as you can see from the pictures, and every option (cloning, teleport, triggers, etc.) is on by default.
When I set a macro for example in one of the posssible locations, it overwrites it with the combination of the two locations.
For example I write Macro1 in the first Macro region and Macro2 in the second, I update reopen Multilevel tab and both regions are overwritten as Macro1,Macro2.
It seems to be caused by The Furnace module, but these two worked together with 0.6.6.
Not sure if it needs to be fixed in your side or Furnaces side, but I will post this to both.

### ### ### __

See https://github.com/kakaroto/fvtt-module-furnace/issues/62

Closing as I believe this is now fixed in Furnace 2.3.1


Error that only occurs when the production flag is set

Please provide us with the following information:

OS?
Chrome Beta 54.0.2840.61, Android 6.0.1

Versions.
angular-cli: 1.0.0-beta.16
node: 4.2.6
os: linux x64

The log given by the failure.
main.8a96c9f….bundle.js:386              Uncaught TypeError: Cannot read property 'parse' of undefined

I have a rather large project that was generated a couple weeks ago with beta.16, and I've just now realized it doesn't work at all on my phone when building with the -prod flag. This doesn't occur when building with the development flag or running ng serve.
When the error occurs, Angular doesn't seem to load at all since I get stuck at the "Loading..." screen, and I can't really debug it as the file is concatenated, minified and all that.

Edit
After further investigation I can conclude that the error has a pretty big chance (about 50/50) to occur after a fresh -prod-build. If it occurs, I can just refresh the site a couple times and it will magically start working without any errors or warnings. Makes me think that there's some race condition coupled with a cache issue.
If I add the --aot-flag it will still have a chance of failing on mobile, but it will produce a different stacktrace that may be of more help.
main.d701279….bundle.js:formatted:14885EXCEPTION: b.b is not a constructort.handleError @ main.d701279….bundle.js:formatted:14885
main.d701279….bundle.js:formatted:14887ORIGINAL STACKTRACE:t.handleError @ main.d701279….bundle.js:formatted:14887
main.d701279….bundle.js:formatted:14888TypeError: b.b is not a constructor
    at e.get [as _DomRootRenderer_25] (http://localhost/main.d701279f1b428ae845d4.bundle.js:1460:12227)
    at e.get [as _RootRenderer_26] (http://localhost/main.d701279f1b428ae845d4.bundle.js:1460:12528)
    at e.get [as _ViewUtils_29] (http://localhost/main.d701279f1b428ae845d4.bundle.js:1460:13158)
    at e.getInternal (http://localhost/main.d701279f1b428ae845d4.bundle.js:1460:21435)
    at e.get (http://localhost/main.d701279f1b428ae845d4.bundle.js:659:1227)
    at t.create (http://localhost/main.d701279f1b428ae845d4.bundle.js:43:2267)
    at e.bootstrap (http://localhost/main.d701279f1b428ae845d4.bundle.js:435:4327)
    at http://localhost/main.d701279f1b428ae845d4.bundle.js:435:2642
    at Array.forEach (native)
    at e._moduleDoBootstrap (http://localhost/main.d701279f1b428ae845d4.bundle.js:435:2613)

Well isn't this awkward. After some further testing I realized index.html was cached for 120 seconds in Apache, resulting in index.html pointing to the wrong main- and style-files (because they have a hashed filename). The short expiration time also explains why it would magically work after a "few refreshes".

Glad to hear you got it sorted!


how to add host ip(Environment Variable) for container ?

I create labels local.ip at machine,and if I add Service(multi container in different machine) ,every container can read host ip on running host

if use entrypoin  -eEUREKA_INSTANCE_IP=$(curl rancher-metadata/latest/self/host/agent_ip)
alway stop

now  I use entrypoint.sh (http://rancher-metadata/latest/self/host/agent_ip),but only can use with  rancher stack,can't use in custom container.

The way your getting it from metadata is the way to do it in Rancher.
An alternate approach would be to use confd to generate some env file to source. That would allow you just launch a container with different prefixes, but query different backends... (http://rancher-metadata/latest/self vs. http://etcd-cluster/v3/). I'd say it is overkill for a single env var though.
Also, in metadata you can grab /self/host/labels/local.ip if you need to.

thanks，I have resolved

@Dreampie  How did you resolve this issue? Please share how did you read the host IP from Rancher label?

@garjunan http://rancher-metadata/latest/self/host/agent_ip

Thanks. I will check this out.
On 8 February 2017 at 17:21, Dreampie<EMAIL_ADDRESS>wrote:

@garjunan https://github.com/garjunan http://rancher-metadata/
latest/self/host/agent_ip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/5412#issuecomment-278307326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AItjMqcoo1j1wqCrHZLGH6UCb1mJ3NQGks5raaw3gaJpZM4JLQSA
.


Consider unique app name

I think it would be a good idea if the app had a unique name, rather than just "Calendar Widget". At the moment it's hard to point someone accurately to your app by mentioning its name in spoken conversation (obviously easier electronically due to URLs).
If nothing else, maybe "+1 Calendar Widget".

Maybe "Another Calendar Widget" ?!

Maybe Calendar Instance Widget... Something that identifies it does
multiple calendars widgets, as that is a unique feature that not all
calendar widgets do.
On May 7, 2017 4:15 PM, "Yuri Volkov"<EMAIL_ADDRESS>wrote:

Maybe "Another Calendar Widget" ?!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/plusonelabs/calendar-widget/issues/256#issuecomment-299735456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUM1FDQB_1F71LOCR1MmjbdBihiqIhMmks5r3jRegaJpZM4NTQOG
.

Since this year the app has the "ToDo Agenda" name. It's quite unique...


Implemented the benchmark to observe the effect of middleware over service-client jobs

I couldn't test this scenario with rmw_zenoh but in my measurements, Seems rmw_fastrtps is little bit faster than rmw_cyclonedds.
Edit: Btw i have realised now that i haven't add documentation.
Edit2: Added documentation

Now, this PR is on the way @sjahr , could you take a look at it when you're available?

Let's tag in a cool way. @sjahr Would you review again? I'm ready. Btw industrial CI gives failure without any reason. So, i have created this PR to solve this problem. PR is here ( https://github.com/CihatAltiparmak/moveit_middleware_benchmark/pull/23 ).


Implement HasChanges flag

Issue #1198
StateManager keeps count of entities that need processing by SaveChanges and hence can report this without scanning.

@rowanmiller for API and doc review

:shipit:

Docs look good


Can't use "highcharts-more"! How to use it? nothing works

I'm trying to create a "xrange" graph and I am getting an error of missing module.
So I'm trying to use the Highcharts-More and I am still getting errors no matter how I am trying to use it.
I tried to do like in the demo and still doesn't work.
<vuecharts :options="chartOptions" :highcharts="Highcharts" ref="chart"></vuecharts>
import Highcharts from 'highcharts'
import { Chart } from 'highcharts-vue'

import More from 'highcharts/highcharts-more'
More(Highcharts)

components: {
      vuecharts: Chart
 },

Any suggestions???
Any guide to how to do it?

Did you get this to work in the end?


[Telink]: Use docker image 0.5.74

Problem

Issue with plic_set_priority under irq_connect_dynamic.

Change overview

Use docker image 0.5.74

Testing
Tested manually with chip-tool.
Steps:
Run: $ chip-tool pairing ble-thread <...>
Wait till success
Run: $ chip-tool accesscontrol write acl <...>
Wait till success
Run: $ chip-tool binding write binding <...>
Wait till success
Press manually switch button
Check if end device perform command

Lets make the change across the board. Using a single docker image for all builds seems more consistent than each platform using a separate build.
I believe only o.5.75 compiled fully on all platforms.

@andy31415
Do you mean switch our platform from chip-build-telink into chip-build-vscode?

@andy31415 Do you mean switch our platform from chip-build-telink into chip-build-vscode?

I mean update all references in yaml files to updated versions: instead of just changing telink, also change linux/efr/esp/ameba/qpg/etc. Also vscode default and cloudbuild.
Something like:
rg --no-ignore --hidden ':0\.5\.\d\d' | cut -f1 -d: | uniq | xargs sd ':0\.5\...' ':0.5.75'

Done in #18673


It works now (upd dependencies and fix crud_user )

Here I updated some dependencies to make this project able to up.
Also fixed crud_user to make update without password possible.

added a big commit with changes from https://github.com/pyb4430/full-stack-fastapi-postgresql

Please merge this branch, everything is set up with no warnings, we can start from @da-maltsev work in order to maintain it.

Hi @da-maltsev, thanks a lot for your fixes and updates. I tried for hours to get the original template running.

@da-maltsev Hey tysm for updating this! I seem to be getting issue on backend python 3.10 dependencies. Not sure if there were breaking changes to python since this pr.
Full Stack trace:
2023-04-09 14:48:38 Checking for script in /app/prestart.sh
2023-04-09 14:48:38 Running script /app/prestart.sh
2023-04-09 14:48:39 Traceback (most recent call last):
2023-04-09 14:48:39   File "/app/app/backend_pre_start.py", line 6, in <module>
2023-04-09 14:48:39     from app.db.session import SessionLocal
2023-04-09 14:48:39   File "/app/app/db/session.py", line 7, in <module>
2023-04-09 14:48:39     from app.core.config import settings
2023-04-09 14:48:39   File "/app/app/core/config.py", line 11, in <module>
2023-04-09 14:48:39     class Settings(BaseSettings):
2023-04-09 14:48:39   File "pydantic/main.py", line 197, in pydantic.main.ModelMetaclass.__new__
2023-04-09 14:48:39   File "pydantic/fields.py", line 506, in pydantic.fields.ModelField.infer
2023-04-09 14:48:39   File "pydantic/fields.py", line 436, in pydantic.fields.ModelField.__init__
2023-04-09 14:48:39   File "pydantic/fields.py", line 557, in pydantic.fields.ModelField.prepare
2023-04-09 14:48:39   File "pydantic/fields.py", line 831, in pydantic.fields.ModelField.populate_validators
2023-04-09 14:48:39   File "pydantic/networks.py", line 591, in __get_validators__
2023-04-09 14:48:39   File "pydantic/networks.py", line 578, in pydantic.networks.import_email_validator
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/email_validator/__init__.py", line 6, in <module>
2023-04-09 14:48:39     import dns.resolver
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/dns/resolver.py", line 39, in <module>
2023-04-09 14:48:39     import dns.query
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/dns/query.py", line 58, in <module>
2023-04-09 14:48:39     import httpx
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpx/__init__.py", line 2, in <module>
2023-04-09 14:48:39     from ._api import delete, get, head, options, patch, post, put, request, stream
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpx/_api.py", line 4, in <module>
2023-04-09 14:48:39     from ._client import Client
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpx/_client.py", line 29, in <module>
2023-04-09 14:48:39     from ._transports.default import AsyncHTTPTransport, HTTPTransport
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpx/_transports/default.py", line 30, in <module>
2023-04-09 14:48:39     import httpcore
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/__init__.py", line 1, in <module>
2023-04-09 14:48:39     from ._api import request, stream
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/_api.py", line 5, in <module>
2023-04-09 14:48:39     from ._sync.connection_pool import ConnectionPool
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/__init__.py", line 1, in <module>
2023-04-09 14:48:39     from .connection import HTTPConnection
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/connection.py", line 13, in <module>
2023-04-09 14:48:39     from .http11 import HTTP11Connection
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/http11.py", line 44, in <module>
2023-04-09 14:48:39     class HTTP11Connection(ConnectionInterface):
2023-04-09 14:48:39   File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/http11.py", line 140, in HTTP11Connection
2023-04-09 14:48:39     self, event: h11.Event, timeout: Optional[float] = None
2023-04-09 14:48:39 AttributeError: module 'h11' has no attribute 'Event'

Did you update Vue version to the Vue 3?

Did you update Vue version to the Vue 3?

it does not look like it:
https://github.com/tiangolo/full-stack-fastapi-postgresql/pull/491/files#diff-8e05a756917525deabbc34b1a252d87191abf4dcf7fbb87497ea5147f4db6879R17

Thanks @da-maltsev! :coffee:
This was refactored in a few other PRs, with some gradual upgrades, etc. So I'll close this one, but thanks for all the effort! :cake:


Is is possible to send message

Hello,
Is this library supported or willing to support to send a message from Telegram? Thanks

This is only for Telegram Passport. To make your own Telegram client, see https://github.com/tdlib/td.


refactor(es/minifier): Respect toplevel and module options

Description:

BREAKING CHANGE:

Related issue (if exists):

Yeah, TSC tests need update. It would be one thousand lines of update, mostly removing top level use strict.

It's weird. I cannot reproduce the CI failure, seems like it's comparing to pre updated tests.

I'll update them by myself. Thank you again for the work!

I'll fix CI with another PR because I'm not sure about the way to reproduce test failure locally


Bump to v0.3.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.075%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2263

Relevant Lines:
2660

💛  - Coveralls


[WOR-536] Add steps for new Terra users

Notes for reviewers:
This wizard is only displayed when the user has no billing projects. When you create a Terra account on dev, you are automatically given access to a billing project, and thus the sandbox site cannot be used for testing.
You can instead use this bee-- https://terra.bee-yunip20-eager-civet.bee.envs-terra.bio
After you create an account, you will see the wizard and can go through the steps. When you are prompted to reauthenticate to elevate permissions (Step 3), you can reauthenticate with the Hermione account<EMAIL_ADDRESS>to switch to an account with Google billing accounts; this also gets around the issue that most email addresses are blocked.
https://broadworkbench.atlassian.net/browse/WOR-536

@yunip20 I would suggest you make this a draft PR while you work out the testing issue.
And speaking of testing, we do want all new code to include unit tests. This is an experiment, but it is still code that will be in production and users will see, so I think it makes sense to test it. Can you please create a unit test for the state transitions and other trickier parts of the logic?

@yunip20 I would suggest you make this a draft PR while you work out the testing issue.
And speaking of testing, we do want all new code to include unit tests. This is an experiment, but it is still code that will be in production and users will see, so I think it makes sense to test it. Can you please create a unit test for the state transitions and other trickier parts of the logic?

Got it, I'll leave this as a draft PR while I work on the unit tests.

You shouldn't see this when selecting a billing project you don't own-- you should see the workspaces for that billing project. This is the cause of the integration test failure as well.

Hey folks, I love the work!
A couple of things regarding A11y accessibility, and feel free to correct me as I may be wrong.

It probably needs a visually hidden text indicating what this is and how many steps there are. Example here.
If we add a way to go back, making sure that it works on the keyboard would be nice. It could be a tab selection.
The stepper needs an aria-selected for each section. Docs here.
The radio buttons that become disabled needs aria-disabled and probably an aria-selected as well.
The first step should probably have an aria-checked for the state of whether the user clicked on it. Docs here.
For the billing dropdown, I haven't checked, but it should have a listbox role or similar. This PR may be a bit out of scope as it's an existing component.

@yunip20 on step 3, the second choice shouldn't be "I have a billing account", should it? I would expect it to be something like "I have added terra-billing as a billing account user".
There's also something funky going on with the keyboard navigation… perhaps that is related.

@gabedemattos @petesantos if you want to give the wizard a whirl, see the PR description for a bee deployment that you can use!


fix negative slice index error in keymutex

xref: https://github.com/kubernetes/kubernetes/issues/73858
The keymutex's slice index could be negative which should not happened.
This PR aims to make the index always positive.
/assign @thockin @dims

weird, why cla check failed ?

@danielqsj can you please sign the CLA? See https://github.com/kubernetes/community/blob/master/CLA.md for instructions and trouble shooting steps

@dims I signed the CLA for CNCF a long time ago. And also checked again.
I'm also a member of kubernetes. So is there some issues about the check here because my PRs in k/k can pass CLA check.

@danielqsj you used a different email id :)

https://patch-diff.githubusercontent.com/raw/kubernetes/kubernetes/pull/72336.patch
https://patch-diff.githubusercontent.com/raw/kubernetes/utils/pull/84.patch

@dims  oops, thank you so much.

@danielqsj is there some kind of test we could add?

/lgtm

/approve


Control [options] does not respect myModel?.MyAttrib throwing "Cannot read property 'length' of null"

I'm loading all option values async, so controls needs to wait with binding.
This works for all standard controls, using model**?**.age or what ever.
But it seems that the angular2-select does not respect this but needs a defined model by default making it impossible to load model async.
Can this be fixed or is there a workaround/option to deal with this?
Best regards, Peter Meldgaard

@mulgurul I usually fix this by setting something like  *ngIf="optionsLoaded" so the select menu doesn't build until the options show up.

True, I have the same issue and the same "solution". It would be nicest if the select either used the same method as the material2 appraoch (i.e. passing a list of options in the HTML using a repeat instead of passing them as an attribute property), or if the supplied list could be an observable.

@cmkramer Could you please provide some code to illustrate your issue? I am not sure if I correctly understand you. I thought that @mulgurul 's issue would have been solved in the beta release, but apperantly this is not the case.
I would say that passing the options as HTML repeat only makes sense if you want your options to be customizable HTML (for example adding an icons to your options). For this component only strings are required (customized HTML options are not supported). So with a HTML repeat, you would need to have a list with strings that you provide to the HTML repeat, so why not immediately provide these strings to the select component?
The supplied list is not an observable, but changes are detected (by angular). It is detected if the list is being replaced with a new list, not if an existing list is modified, see #60 for more details.

Closing this issue for now.

Well it seems that with your current version it no longer crashes when the form control aready has a value, but the list isn't loaded yet, which is nice. Still, when the forrmcontrol already has a value set, while retrieving the option list asynchronously, the option is not properly selected after the list is loaded. You can see this effect here:
https://plnkr.co/edit/jdFI1xprLKp1tX9lTsAX?p=preview
This still forces the user to explicitly delay adding the select component to the page until after the option list has been loaded, to avoid its value not being displayed properly.

@basvandenberg would you like me to create a new issue for this?

I am not sure if this is an issue. If I understand you correct, you try to set a value of an option that is not there (because the options are not yet loaded). In my opinion, the expected behavior is that no option is selected in that case, which is what currently happens.
Instead of letting the component 'remember' what value was set, and then setting it as soon as options are set (this could lead to confusing situation and is in my opinion not very intuitive), the user should set the value after he has set the options. So for example:

Add the control with an empty list of options, and without setting a value.
At the same, start asynchronous loading of the options (which returns an observable).
Subscribe to the observable and when the data is loaded:

Replace the empy list of options with the loaded options.
Now set the control's value.

I adjusted your plunker a bit to illustrate this:
https://plnkr.co/edit/K2F2cCXbJajUijSIYIc6?p=preview
setTimeout(() => {
    this.options0 = opts.slice(0);
    this.singleSelectDisabled = false;
    setTimeout(() => { this.form.controls['selectSingle'].setValue('0'); });
}, 2000);

Additionally I disabled the select component as long as the options are not set. After two seconds the options are set and the component is enabled.
And then set the value.
However, as you can see this is done within a zero delay setTimeout. This looks strange and I guess it is a bit of a hack, but you'll see it quit often in angular2 apps. This is to make sure that angular's change detection detected the updated list of options before setting the value. It won't work without the zero delay setTimeout.
(by using a zero-delay setTimeout, the setValue task is pushed to the end of the task queue, guarantied to be behind the task that handles the change detection)

Thank you for thinking along. I am indeed aware of how a setTimeout can force something out of the current digest cycle and push it into the next. I'm glad you also realize this is a hack. Seeing it often doesn't make it right, so I'd rather use it less often than more often.
I'd like to picture this case as follows:
I have a persisted record, that I serve through a restful resource. My Angular application has access to this record and has a corresponding reactive form that allows me to edit the record. Since the record is served through a singleton ResourceStore, Collection or whichever name fits (comparable to ReactJS's Redux), there's always one truth, both when it comes to the record, and its corresponding form. This also means that the form itself, in it's initial state, is loaded when the record is loaded. So at that point control values are set to the currently persistent values as known by the server.
Now all the component has to do is present the user with an interface that allows them to edit the current state of the resource. In my perspective it makes sense that any component used to represent a form item, should take care of synchronizing its own resources. In this case it takes more than one resource to work, i.e. the control value and the option list. So which of the two is initialized first, or second should not stop the component from providing the one thing that it is created for. It doesn't sound right the programmer using the form editing component has to build logic into every encapsulating component in order for it to work, while it doesn't add any value to the encapsulating component itself. This means duplicate code everywhere, while it could be taken care of by the form editing component itself.
Either way, shouldn't a component strive behave the same regardles of the sequence or timing in which properties are loaded?

That's an interesting view, haven't thought about it like that. I do see some practical issues though. But I'll have to come back to you about this later, because I don't have much time now and I will be away for some days.

Awesome, can't wait to see what you'll do :).


WebServerInstance Create_Failed

Attempted to follow CellNet WebApp walk-through found in the supplemental from https://doi.org/10.1101/614594. At Step 4- 'specify an Amazon S3 template URL' I used the one listed: https://s3.amazonaws.com/cahanlab/remy.schwab/Stack_Templates/CellNet_publicStackTemplate.json.  After creating the stack, it threw these errors.

Specifically- The image id '[ami-8e2b0eeb]' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.NotFound; Request ID: f4dadc19-18cd-4687-84c8-e099e69b37de), and The following resource(s) failed to create: [WebServerInstance]. . Rollback requested by user.
Is there a new stack template URL to use on AWS CloudFormation?

I encountered the same error. I think it's because the image is only available on AWS us-east-1 (N. Virginia), not on us-east-2 (Ohio). When I switched to N. Virginia, made a new security group, and retried, it did create the stack.


Error: Failed to load plugin import: Cannot find module 'eslint-plugin-import'

Is this a bug report?
Yes
Repo demonstrating the problem. It is a a freshly bootstrapped react app. I then installed react-testing-library. The same problem shows if I install enzyme instead.
https://github.com/tmclayson/create-react-app-eslint-plugin-import-error
Yes, tried deleting node_module and package-lock.json.
npm version: 6.8.0-next.2
Have tried multiple different versions however.
Which terms did you search for in User Guide?
I read the Test Utilities page, but the both the both suggestions for enzyme and react-testing-library failed for me. I've tried installing the package individually, but then something else is missing.
Environment
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Binaries:
Yarn: 1.13.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.8.0-next.2 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 42.17134.1.0
npmPackages:
react: ^16.8.1 => 16.8.1
react-dom: ^16.8.1 => 16.8.1
react-scripts: 2.1.3 => 2.1.3
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

npx create-react-app testing
npm install --save-dev react-testing-library
npm start

Expected Behavior
Compile and load the base react app without issues.
Actual Behavior
Starting the development server...
Failed to compile.
./src/index.js
Error: Failed to load plugin import: Cannot find module 'eslint-plugin-import'
Referenced from:
at Array.forEach ()
at Array.reduceRight ()
Reproducible Demo
https://github.com/tmclayson/create-react-app-eslint-plugin-import-error
npm start

Hi @tmclayson,
from a quick CodeSandbox test everything seemed to work normally: https://codesandbox.io/s/lxpwjno9r7
Sounds like a intermittent issue with npm . Have you tried cleaning the cache?

I met the same problem on my MacOS on the Vscode editor.

Using yarn to manage everything instead of npm solved the issue for me.

Great, Yarn works for me too.


Fix/prebuildify path lookup

Right two issues

The path lookup is looking at the root of the project folder, and not in the node_modules directory

env var LOG_LEVEL doesn't affect logging of the FFI native module, as that uses DEFAULT_LOG_LEVEL or the user provided instead ofcurrentLogLevel which was modified to take account of the env var LOG_LEVEL

simple test of the standalone and ffi
const pact = require('@pact-foundation/pact-core')
pact.createServer()
 .delete()
 .then(function() {
  console.log('pact ruby standalone server created and deleted')
 });

const consumerPact = pact.makeConsumerPact(
    'foo-consumer',
    'bar-provider',
    4 ,// v3 spec,
    'TRACE'
  );
const interaction = consumerPact.newInteraction('some description');

interaction.uponReceiving('a request to get a dog');
interaction.given('fido exists');
interaction.withRequest('GET', '/dogs/1234');
interaction.withResponseBody(
JSON.stringify({
    name: 'fido',
    age: 23,
    alive: true,
}),
'application/json'
);
interaction.withStatus(200);

port = consumerPact.createMockServer('<IP_ADDRESS>');
// port = consumerPact.createMockServer('localhost'); // Error in native callback - JSON.parse(ffi.pactffiMockServerMismatches(port))
console.log(port)
consumerPact.mockServerMatchedSuccessfully(port)
const mismatches = consumerPact.mockServerMismatches(port);
console.log(mismatches)

npm install @pact-foundation/pact-core
LOG_LEVEL=debug node test.js
You can see the lookup path is  /Users/yousaf.nabi/dev/fooscratch/prebuilds/darwin-arm64 but it should be ` /Users/yousaf.nabi/dev/fooscratch/node_modules/@pact-foundation/pact-core/prebuilds/darwin-arm64
[11:46:08.471] DEBUG (10503<EMAIL_ADDRESS>Attempting to find pact native module : loading native module from:

 - /Users/yousaf.nabi/dev/fooscratch/prebuilds/darwin-arm64
   source: pact-js-core binding lookup

 - You can override via PACT_PREBUILD_LOCATION

[11:46:08.473] DEBUG (10503<EMAIL_ADDRESS>Supported platforms are:
 - darwin-arm64
 - darwin-x64
 - linux-arm64
 - linux-x64
 - win32-x64
We detected your platform as:

 - darwin-arm64

[11:46:08.474] ERROR (10503<EMAIL_ADDRESS>Failed to initialise native module for darwin-arm64: Error: No native build was found for platform=darwin arch=arm64 runtime=node abi=93 uv=1 armv=8 libc=glibc node=16.20.0
    loaded from: /Users/yousaf.nabi/dev/fooscratch

[11:46:08.474] DEBUG (10503<EMAIL_ADDRESS>{supportedPlatformsMessage}
We detected your platform as:

 - darwin-arm64

      We looked for a supported build in this location /Users/yousaf.nabi/dev/fooscratch/prebuilds/darwin-arm64

      Tip: check there is a prebuild for darwin-arm64

      check the prebuild exists at the path: /Users/yousaf.nabi/dev/fooscratch/prebuilds/darwin-arm64

      Wrong Path?: set the load path with PACT_PREBUILD_LOCATION ensuring that $PACT_NODE_NAPI_LOCATION/prebuilds/darwin-arm64 exists

      - Note: You dont need to include the prebuilds/darwin-arm64 part of the path, just the parent directory

      - Let us know: We can add more supported path lookups easily, chat to us on slack or raise an issue on github
[11:46:08.474] INFO (10503<EMAIL_ADDRESS>Removing all Pact servers.
/Users/yousaf.nabi/dev/fooscratch/node_modules/@pact-foundation/pact-core/src/ffi/index.js:94
        throw new Error(`Failed to load native module, try setting LOG_LEVEL=debug for more info \n. ${error}`);
        ^

Error: Failed to load native module, try setting LOG_LEVEL=debug for more info
. TypeError: Cannot read properties of undefined (reading 'pactffiInitWithLogLevel')

LOG_LEVEL=debug PACT_PREBUILD_LOCATION=$PWD/node_modules/@pact-foundation/pact-core node test.js
2023-07-06T10:41:20.317521Z DEBUG ThreadId(01) pactffi_create_mock_server_for_pact{pact=PactHandle { pact_ref: 1 } addr_str=0x16f8e5958 tls=false}: pact_mock_server::mock_server: Started mock server on <IP_ADDRESS>:51574
2023-07-06T10:41:20.317539Z TRACE ThreadId(01) pactffi_create_mock_server_for_pact{pact=PactHandle { pact_ref: 1 } addr_str=0x16f8e5958 tls=false}: pact_ffi::mock_server::handles: with_pact after - ref = 1, inner = RefCell { value: PactHandleInner { pact: V4Pact { consumer: Consumer { name: "foo-consumer" }, provider: Provider { name: "bar-provider" }, interactions: [SynchronousHttp { id: None, key: None, description: "a request to get a dog", provider_states: [ProviderState { name: "fido exists", params: {} }], request: HttpRequest { method: "GET", path: "/dogs/1234", query: None, headers: None, body: Missing, matching_rules: MatchingRules { rules: {PATH: MatchingRuleCategory { name: PATH, rules: {} }} }, generators: Generators { categories: {} } }, response: HttpResponse { status: 200, headers: Some({"Content-Type": ["application/json"]}), body: Present(b"{\"age\":23,\"alive\":true,\"name\":\"fido\"}", Some(ContentType { main_type: "application", sub_type: "json", attributes: {}, suffix: None }), None), matching_rules: MatchingRules { rules: {BODY: MatchingRuleCategory { name: BODY, rules: {} }} }, generators: Generators { categories: {} } }, comments: {}, pending: false, plugin_config: {}, interaction_markup: InteractionMarkup { markup: "", markup_type: "" }, transport: None }], metadata: {"pactRust": Object {"ffi": String("0.4.0")}}, plugin_data: [] }, mock_server_started: true, specification_version: V3 } }
51574
[
  {
    method: 'GET',
    path: '/dogs/1234',
    request: { method: 'GET', path: '/dogs/1234' },
    type: 'missing-request'
  }
]
[11:41:20.320] INFO (10256<EMAIL_ADDRESS>Deleting Pact Server with options:
{"dir":"/Users/yousaf.nabi/dev/fooscratch","pactFileWriteMode":"overwrite","ssl":false,"cors":false,"host":"localhost"}
pact ruby standalone server created and deleted

hmm there should a third commit fixing the linting 🤔

hmm there should a third commit fixing the linting 🤔

ahh synced now


Project title Animated Wave Banner

Project title:
Animated Wave Banner
Project Description:
Animated banners add a touch of creativity and interactivity to your website, making it visually appealing and engaging. With the power of HTML and CSS, you can bring static elements to life with smooth and eye-catching animations. Through this a beginner would explore the art of crafting an animated wave banner – a versatile and attention-grabbing element that can elevate the web design to new heights.
Stack:
[ ] Html
[ ] CSS

please assign it to me..

please add level label..and assign so that I could make changes ASAP

please assign..


Anyone use Direct Line API in V3?

I can Send Message (conversationId, from, text) in V1 but I got 500 error in V3. However, I was told that NuGet package (Microsoft.Bot.Connector.DirectLine) is ok in V3. Anyone use Direct Line API in V3?
According to http://docs.botframework.com/en-us/restapi/directline/#!/Conversations/Conversations_GetMessages, I am a little bit confused.
_The client may send messages to the bot by calling POST on https://directline.botframework.com/api/messages/conversationId.
The client may retrieve messages sent by the bot by calling GET on https://directline.botframework.com/api/messages/conversationId. The JSON structure returned contains a watermark that can be sent on subsequent requests to skip old messages.__
The URLs are different from what I used in V1. So are these new URLs?

Ok. I found out where the problem is. What I saw 500 error when I 'Send Message' is due to Direct Line can't access my endpoint (403 error). Since Bot Framework upgraded from V1 to V3, Microsoft uses different IPs to access my endpoint.


Fix issue with opn library

Noticed this while running tests, the open(...) command doesn't return an exit status on MacOS (see: https://github.com/sindresorhus/opn/issues/92).
Thus the test for clasp open was hanging up even though it successfully opened.
Signed-off-by: campionfellin<EMAIL_ADDRESS>
[x] npm run test succeeds.
[x] npm run lint succeeds.

Just as sidenot. I tried the same in one of my projects.
Calling process.exit does not trigger opn on Windows and immediately closes the application.

opn returns a promise so something like
await opn('https://www.ueberbit.de/jobs/' + job)
process.exit(0)

or
opn('https://www.ueberbit.de/jobs/' + job)
setTimeout(()=>process.exit(0),300)

should do the trick.
As the promise does not resolve only option 2 works on both platforms.

Try opn(target, {wait: false}).

Try opn(target, {wait: false}).

@campionfellin Could we await opn?

@campionfellin Could we await opn?

This will not help here as it will never resolve.

As the promise does not resolve only option 2 works on both platforms.

But https://github.com/google/clasp/pull/242#issuecomment-410847584 is probably better.

OK, let's
opn(target, {wait: false})
@DanielRuf Can you open a new GitHub issue for this?


Tengai ni Mau, Iki na Hana [PCSG01180]

App summary

App name: Tengai ni Mau, Iki na Hana
App serial: PCSG01180
App version: 1.0

Vita3K summary

Version: v0.1.5
Build number: 2723
Commit hash: https://github.com/vita3k/vita3k/commit/c32ac263
CPU backend: Dynamic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game plays with no characters in gameplay
Screenshots:

Log
vita3k.log
Recommended labels

Ingame +
Graphics bug

Sprites show up (screenshots in above report are during scenes with characters who don't actually have an in-game sprite so not seeing a sprite is intended).
Label should be playable.

Characters with sprites for reference (and they do display properly):


For IE, always use 32-bit driver since 64-bit driver doesn't work.

The 64-bit IE driver has been broken for over a year.
Note: this request depends on protractor PR #2406 to be pulled, which it looks like it will

... and protractor has merged my PR so this can be merged as well:
https://github.com/angular/protractor/pull/2406


Update alerts severity option to match newly created AlertsManager setup

Note: reverted commit a4bdb45 as it would have been released as part of this PR, and we don't have the release infrastructure setup for the 'deployment-build' branch for this repo. Will un-revert commit after our release on 02/12


About CamVid dataset

I have downloaded the CamVid dataset, but the labels are RGB format and 32 classes, I want to convert the labels to 11 classes and index, how can i do it?

Maybe you can use the dataset in this repo: https://github.com/alexgkendall/SegNet-Tutorial/tree/master/CamVid

Maybe you can use the dataset in this repo: https://github.com/alexgkendall/SegNet-Tutorial/tree/master/CamVid

But the images and annotations in that repo are of size 360x480, different from the origin size (720x960). How did you deal with this issue?
Thank you!


Lines from outline of filled boundary plot don't line up with edges on filled boundary plot

Kevin Roe showed me an image where he had both a filled boundary plot and a filled boundary plot with outline set. The lines for the outline didn't match the edges from the filled boundary plot. There was in many cases a pixel of background separating them (which was white and was quite noticeable). The gap was above in some cases and on the side in other cases.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 2499
Status: Pending
Project: VisIt
Tracker: Bug
Priority: High
Subject: Lines from outline of filled boundary plot don't line up with edges on filled boundary plot
Assigned to: -
Category: -
Target version: 3.0
Author: Eric Brugger
Start: 01/07/2016
Due date:
% Done: 0%
Estimated time:
Created: 01/07/2016 12:31 pm
Updated: 01/19/2016 06:38 pm
Likelihood: 3 - Occasional
Severity: 3 - Major Irritation
Found in version: 2.10.0
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Kevin Roe showed me an image where he had both a filled boundary plot and a filled boundary plot with outline set. The lines for the outline didn't match the edges from the filled boundary plot. There was in many cases a pixel of background separating them (which was white and was quite noticeable). The gap was above in some cases and on the side in other cases.
Comments:

Given how the wireframe mode of FilledBoundary/Subset plots work (edges extracted, shift factor applied to bring the edges slightly towards the camera), I can see how this might occur.  Hard to come up with a fix without a reproducer. Might be due to extreme spatial extents.


Update the MSRV

The reasoning is the same as in https://github.com/AleoHQ/snarkOS/pull/2408.

The CI error is unrelated.


preview cuts off tabline

it seems that the preview cuts of the tabline - you can see with preview a lot less tabs are shown even though there would be space.
also very fun idea since I'm running out of space for all my pickers: how about mulitple rows/cols and navigating with hjkl or something? 😂
Thanks a ton 🙏

I'll try to fix the hide-behind-results situation 😁
Stacking the tabs sounds good.. but I'd keep the keybindings opt-in since I feel like C-jklh are usually used otherwise in the telescope environment..
At least adding a 'per_row' in the configs should be easy 👍🏻


Issue with Flash.Code Build on Sterile CentOS7

Describe the bug
Building FLASH with AMUSE results in an error despite: all other codes working perfectly; FLASH being in the correct directory thanks to Torch; and being in a sterile CentOS 7 environment.
To Reproduce
See included singularity recipe file.
Expected behavior
For the file to be found and the build to proceed.
Logs
+ make flash.code
/usr/local/anaconda/bin/python setup.py -v build_code --inplace --clean=yes --code-name=flash
running build_code
cleaning src/amuse/community/flash
make -C src/amuse/community/flash clean
make[1]: Entering directory `/opt/amuse/src/amuse/community/flash'
rm -f -f *.so *.o *.pyc worker_code.cc worker_code.h #flash.par
rm -f *~ flash_worker worker_code.f90
make -C src clean
make[2]: Entering directory `/opt/amuse/src/amuse/community/flash/src'
rm -f *.o *.a
make[2]: Leaving directory `/opt/amuse/src/amuse/community/flash/src'
make[1]: Leaving directory `/opt/amuse/src/amuse/community/flash'
building libraries and community codes
build, for logging, see 'build.log'
[18:28:04] building flash
make -C src/amuse/community/flash all
make[1]: Entering directory `/opt/amuse/src/amuse/community/flash'
/opt/amuse/build.py --type=f90 interface.py FlashInterface -o worker_code.f90
make -C src all
make[2]: Entering directory `/opt/amuse/src/amuse/community/flash/src'
mpif90 -g -O2 -fPIC -c -o test.o test.f90
rm -f libflash.a
ar ruv libflash.a test.o
ar: creating libflash.a
a - test.o
ranlib libflash.a
make[2]: Leaving directory `/opt/amuse/src/amuse/community/flash/src'
mpif90 -g -O2 -fPIC -Isrc/FLASH4.6.2/object -c -o base_grid_interface.o base_grid_interface.F90
base_grid_interface.F90:417.6:

  use Grid_interface, only : Grid_getBlkIndexLimits
      1
Fatal Error: Can't open module file 'grid_interface.mod' for reading at (1): No such file or directory
make[1]: *** [base_grid_interface.o] Error 1
make[1]: Leaving directory `/opt/amuse/src/amuse/community/flash'
[18:28:05] building flash, failed, see 'build.log' for error log
Environment variables
================================================================================
AMUSE_DIR	/opt/amuse
BOOSTLIBS
CC	gcc
CFLAGS	-g -O2 -fPIC
CUDA_LIBDIRS	-L/usr/local/cuda/lib -L/usr/local/cuda/lib64
CUDA_LIBS	-lcuda  -L/usr/local/cuda/lib64 -lcudart
CUDA_SDK	/TOBEFIXED
CUDA_TK	/usr/local/cuda
CXX	g++
CXXFLAGS	-g -O2 -fPIC
F90	gfortran
FC	gfortran
FFLAGS	-g -O2 -fPIC
FFTW_FLAGS
FFTW_LIBS	-lfftw3 -lm   -lfftw3_threads
FORTRAN	gfortran
GSL_FLAGS
GSL_LIBS	-lgsl -lgslcblas -lm
JAR
JAVA	/bin/java
JAVAC
MPICC	mpicc
MPICXX	mpicxx
MPIF90	mpif90
MUSE_PACKAGE_DIR	/opt/amuse
OPENMP_CFLAGS	-fopenmp
OPENMP_FCFLAGS	-fopenmp
PYTHON	/usr/local/anaconda/bin/python
SAPPORO_LIBS	-L/opt/amuse/lib/sapporo_light -lsapporo
Community codes not built (because of errors):
================================================================================
 * flash
================================================================================
0 out of 1 codes built, 0 out of 0 libraries built

Environment (please complete the following information):
# Torch Container                                             #
# =====================                                             #
#                                                                   #
# This container offers a build of Torch of of CentOS 7             #
# from the official Dockers containers.                             #
#                                                                   #
# singularity build centos8_torch.simg torch.recipe                 #
#                                                                   #
#####################################################################
Bootstrap: docker
From: centos:7

%help
  Helpful information to come. This container is running the following:
  - CentOS      7.0.0
  - HDF5        1.8.12
  - Hypre       2.11.2
  - netCDF CXX  4.2.8
  - netCDF C    4.3.3
  - netCDF F90  4.2-16
  - zlib        1.2.7
  - FLASH       4.6.2
  - OpenMPI3    3.1.3

%labels
  CREATOR Joe Glaser

%runscript
exec echo "The runscript is the containers default runtime command!"

%files
  FLASH4.6.2.tar.gz /opt/
  singularity.centos7/Makefile.h /opt/

%environment
SHELL=/bin/bash
export SHELL
export PATH="/usr/local/anaconda/bin:$PATH"
export AMUSE_DIR=/opt/amuse
export FLASH_DIR=/opt/FLASH4.6.2
export TORCH_DIR=/opt/torch
export PYTHONPATH="/opt/amuse/src:$PYTHONPATH"
module load mpi

%post
  echo "The post section is where you can install, and configure your container."
# Install the EPEL Repo
  yum search epel-release
  yum info epel-release
  yum -y install epel-release
# Do an Update and Upgrade
  yum -y update
  yum -y upgrade
# Install Useful Commands
  yum -y install sudo which nano wget bzip2 git cmake \
    ca-certificates libglib2.0-0 libxext6 libsm6 libxrender1

# Install AMUSE Base Requirements
  yum -y install curl libcurl* devtoolset-8 gettext* zlib*
# Install OpenMPI3 and Append the Path Variable
  yum -y install openmpi3*
  export PATH=/usr/lib64/openmpi3/bin:$PATH
# Install HDF5 with OpenMPI3 Support
  yum -y install hdf5 hdf5-devel hdf5-openmpi3*
# Install NetCDF (No OpenMPI Support Due to Dependence on v1.10)
  yum -y install netcdf netcdf-devel \
    netcdf-cxx-devel netcdf-cxx-static netcdf-cxx \
    netcdf-fortran-devel netcdf-fortran-static netcdf-fortran
# Install FFTW
  yum -y install fftw fftw-devel fftw-libs*
# Install GSL, GMP & MPFR
  yum -y install gsl gsl-devel gmp gmp-devel mpfr mpfr-devel

# Install FLASH Requirements
  yum -y install hypre hypre-devel papi papi-devel papi-static libIDL libIDL-devel

# Install CUDA
  wget https://developer.download.nvidia.com/compute/cuda/11.1.1/local_installers/cuda-repo-rhel7-11-1-local-11.1.1_455.32.00-1.x86_64.rpm
  rpm -i cuda-repo-rhel7-11-1-local-11.1.1_455.32.00-1.x86_64.rpm
  yum clean all
  yum -y install nvidia-driver-latest-dkms cuda
  yum -y install cuda-drivers

# install anaconda
  if [ ! -d /usr/local/anaconda ]; then
    wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh \
      -O ~/anaconda.sh && \
      bash ~/anaconda.sh -b -p /usr/local/anaconda && \
      rm ~/anaconda.sh
  fi

# Set Anaconda Path
  export PATH="/usr/local/anaconda/bin:$PATH"

# install the bare minimum
  pip install numpy scipy astropy matplotlib
  env MPICC=/usr/lib64/openmpi3/bin/mpicc pip install mpi4py
  pip install h5py pytest docutils quilt gsl
  conda install gmp mpfr nose
  conda clean --tarballs

# Install AMUSE
  cd /opt
  git clone https://github.com/amusecode/amuse.git
  cd amuse
  ./configure --enable-cuda
  make framework
  make kepler.code
  make ph4.code
  make seba.code
  make smalln.code
  pip install rebound

# Install FLASH
  cd /opt
  tar -zxvf FLASH4.6.2.tar.gz
  cd FLASH4.6.2
  mkdir sites/singularity.centos7
  mv /opt/Makefile.h sites/singularity.centos7/Makefile.h
  ./setup -auto -3d Sedov --site=singularity.centos7
  #cd object
  #make

# Install Torch
  cd /opt
  git clone https://bitbucket.org/torch-sf/torch.git
  cd torch
  export AMUSE_DIR=/opt/amuse
  export FLASH_DIR=/opt/FLASH4.6.2
  export TORCH_DIR=/opt/torch
  yes | ./install.sh

# Install AMUSE FLASH_Worker
  export FLASH_DIR=/opt/FLASH4.6.2
  cd /opt/amuse/
  make flash.code

Additional context
Add any other context about the problem here.

Describe the bug Building FLASH with AMUSE results in an error despite: all other codes working perfectly; FLASH being in the correct directory thanks to Torch; and being in a sterile CentOS 7 environment.
To Reproduce See included singularity recipe file.
Expected behavior For the file to be found and the build to proceed.
Logs
+ make flash.code
/usr/local/anaconda/bin/python setup.py -v build_code --inplace --clean=yes --code-name=flash
running build_code
cleaning src/amuse/community/flash
make -C src/amuse/community/flash clean
make[1]: Entering directory `/opt/amuse/src/amuse/community/flash'
rm -f -f *.so *.o *.pyc worker_code.cc worker_code.h #flash.par
rm -f *~ flash_worker worker_code.f90
make -C src clean
make[2]: Entering directory `/opt/amuse/src/amuse/community/flash/src'
rm -f *.o *.a
make[2]: Leaving directory `/opt/amuse/src/amuse/community/flash/src'
make[1]: Leaving directory `/opt/amuse/src/amuse/community/flash'
building libraries and community codes
build, for logging, see 'build.log'
[18:28:04] building flash
make -C src/amuse/community/flash all
make[1]: Entering directory `/opt/amuse/src/amuse/community/flash'
/opt/amuse/build.py --type=f90 interface.py FlashInterface -o worker_code.f90
make -C src all
make[2]: Entering directory `/opt/amuse/src/amuse/community/flash/src'
mpif90 -g -O2 -fPIC -c -o test.o test.f90
rm -f libflash.a
ar ruv libflash.a test.o
ar: creating libflash.a
a - test.o
ranlib libflash.a
make[2]: Leaving directory `/opt/amuse/src/amuse/community/flash/src'
mpif90 -g -O2 -fPIC -Isrc/FLASH4.6.2/object -c -o base_grid_interface.o base_grid_interface.F90
base_grid_interface.F90:417.6:

  use Grid_interface, only : Grid_getBlkIndexLimits
      1
Fatal Error: Can't open module file 'grid_interface.mod' for reading at (1): No such file or directory
make[1]: *** [base_grid_interface.o] Error 1
make[1]: Leaving directory `/opt/amuse/src/amuse/community/flash'
[18:28:05] building flash, failed, see 'build.log' for error log
Environment variables
================================================================================
AMUSE_DIR	/opt/amuse
BOOSTLIBS
CC	gcc
CFLAGS	-g -O2 -fPIC
CUDA_LIBDIRS	-L/usr/local/cuda/lib -L/usr/local/cuda/lib64
CUDA_LIBS	-lcuda  -L/usr/local/cuda/lib64 -lcudart
CUDA_SDK	/TOBEFIXED
CUDA_TK	/usr/local/cuda
CXX	g++
CXXFLAGS	-g -O2 -fPIC
F90	gfortran
FC	gfortran
FFLAGS	-g -O2 -fPIC
FFTW_FLAGS
FFTW_LIBS	-lfftw3 -lm   -lfftw3_threads
FORTRAN	gfortran
GSL_FLAGS
GSL_LIBS	-lgsl -lgslcblas -lm
JAR
JAVA	/bin/java
JAVAC
MPICC	mpicc
MPICXX	mpicxx
MPIF90	mpif90
MUSE_PACKAGE_DIR	/opt/amuse
OPENMP_CFLAGS	-fopenmp
OPENMP_FCFLAGS	-fopenmp
PYTHON	/usr/local/anaconda/bin/python
SAPPORO_LIBS	-L/opt/amuse/lib/sapporo_light -lsapporo
Community codes not built (because of errors):
================================================================================
 * flash
================================================================================
0 out of 1 codes built, 0 out of 0 libraries built

Environment (please complete the following information):
# Torch Container                                             #
# =====================                                             #
#                                                                   #
# This container offers a build of Torch of of CentOS 7             #
# from the official Dockers containers.                             #
#                                                                   #
# singularity build centos8_torch.simg torch.recipe                 #
#                                                                   #
#####################################################################
Bootstrap: docker
From: centos:7

%help
  Helpful information to come. This container is running the following:
  - CentOS      7.0.0
  - HDF5        1.8.12
  - Hypre       2.11.2
  - netCDF CXX  4.2.8
  - netCDF C    4.3.3
  - netCDF F90  4.2-16
  - zlib        1.2.7
  - FLASH       4.6.2
  - OpenMPI3    3.1.3

%labels
  CREATOR Joe Glaser

%runscript
exec echo "The runscript is the containers default runtime command!"

%files
  FLASH4.6.2.tar.gz /opt/
  singularity.centos7/Makefile.h /opt/

%environment
SHELL=/bin/bash
export SHELL
export PATH="/usr/local/anaconda/bin:$PATH"
export AMUSE_DIR=/opt/amuse
export FLASH_DIR=/opt/FLASH4.6.2
export TORCH_DIR=/opt/torch
export PYTHONPATH="/opt/amuse/src:$PYTHONPATH"
module load mpi

%post
  echo "The post section is where you can install, and configure your container."
# Install the EPEL Repo
  yum search epel-release
  yum info epel-release
  yum -y install epel-release
# Do an Update and Upgrade
  yum -y update
  yum -y upgrade
# Install Useful Commands
  yum -y install sudo which nano wget bzip2 git cmake \
    ca-certificates libglib2.0-0 libxext6 libsm6 libxrender1

# Install AMUSE Base Requirements
  yum -y install curl libcurl* devtoolset-8 gettext* zlib*
# Install OpenMPI3 and Append the Path Variable
  yum -y install openmpi3*
  export PATH=/usr/lib64/openmpi3/bin:$PATH
# Install HDF5 with OpenMPI3 Support
  yum -y install hdf5 hdf5-devel hdf5-openmpi3*
# Install NetCDF (No OpenMPI Support Due to Dependence on v1.10)
  yum -y install netcdf netcdf-devel \
    netcdf-cxx-devel netcdf-cxx-static netcdf-cxx \
    netcdf-fortran-devel netcdf-fortran-static netcdf-fortran
# Install FFTW
  yum -y install fftw fftw-devel fftw-libs*
# Install GSL, GMP & MPFR
  yum -y install gsl gsl-devel gmp gmp-devel mpfr mpfr-devel

# Install FLASH Requirements
  yum -y install hypre hypre-devel papi papi-devel papi-static libIDL libIDL-devel

# Install CUDA
  wget https://developer.download.nvidia.com/compute/cuda/11.1.1/local_installers/cuda-repo-rhel7-11-1-local-11.1.1_455.32.00-1.x86_64.rpm
  rpm -i cuda-repo-rhel7-11-1-local-11.1.1_455.32.00-1.x86_64.rpm
  yum clean all
  yum -y install nvidia-driver-latest-dkms cuda
  yum -y install cuda-drivers

# install anaconda
  if [ ! -d /usr/local/anaconda ]; then
    wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh \
      -O ~/anaconda.sh && \
      bash ~/anaconda.sh -b -p /usr/local/anaconda && \
      rm ~/anaconda.sh
  fi

# Set Anaconda Path
  export PATH="/usr/local/anaconda/bin:$PATH"

# install the bare minimum
  pip install numpy scipy astropy matplotlib
  env MPICC=/usr/lib64/openmpi3/bin/mpicc pip install mpi4py
  pip install h5py pytest docutils quilt gsl
  conda install gmp mpfr nose
  conda clean --tarballs

# Install AMUSE
  cd /opt
  git clone https://github.com/amusecode/amuse.git
  cd amuse
  ./configure --enable-cuda
  make framework
  make kepler.code
  make ph4.code
  make seba.code
  make smalln.code
  pip install rebound

# Install FLASH
  cd /opt
  tar -zxvf FLASH4.6.2.tar.gz
  cd FLASH4.6.2
  mkdir sites/singularity.centos7
  mv /opt/Makefile.h sites/singularity.centos7/Makefile.h
  ./setup -auto -3d Sedov --site=singularity.centos7
  #cd object
  #make

# Install Torch
  cd /opt
  git clone https://bitbucket.org/torch-sf/torch.git
  cd torch
  export AMUSE_DIR=/opt/amuse
  export FLASH_DIR=/opt/FLASH4.6.2
  export TORCH_DIR=/opt/torch
  yes | ./install.sh

# Install AMUSE FLASH_Worker
  export FLASH_DIR=/opt/FLASH4.6.2
  cd /opt/amuse/
  make flash.code

Additional context Add any other context about the problem here.

Hi, you have to execute these lines after the flash ./setup command:
cd object
make
this error occurs because "use Grid_interface" expect a compiled object/module.


Remove implementation dependency on tasks

Reported by @meichstedt
There are several places where the implementation assumes that an instance has at least one task. This is not assured anywhere, so it must either be assured, or the implementations need to be safe in case of an empty list.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2580. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2580. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


Rename isAt* functions in SwiftParser to at*

We have the at(_: TokenSpec) functions to check if we are at a token but some of the more complex at functions like isAtStartOfPostfixExprSuffix start with isAt. To be consistent, we should remove is here.

Tracked in Apple’s issue tracker as rdar://113237445

@ahoppen, I'll grab these next — expect a PR by Friday ;)

First findings
There are _quite a few functions and propertiesthat followisAt*` notation. Focusing on just the functions, here's the list that I'll rename first:

[ ] Lexer.Cursor.isAtStringInterpolationAnchor — private, so I'll rename it and change any spots where it's invoked. Deprecating the existing function should not be necessary.
[ ] Lexer.Cursor.isAtEscapedNewline — same as above.
[ ] Parser.Lookahead has two fileprivate functions isAtStartOfPostfixExprSuffix and isInBindingPatternPosition — I think it's best to rename both of them so the code in that particular extension is consistent. It would be weird to have atStartOfPostfixExprSuffix and isIn*.
[ ] Parser.isAtPythonStyleInheritanceClause
[ ] In Parser/Statements.swift we have Parser.Lookahead extension with isAtStartOfSwitchCase, isStartOfStatement, isStartOfConditionalSwitchCases.

These are not market as private, so I think we should keep the original version and deprecate it.
Should I rename isStartOf* as well for consistency?

Questions
In some cases, there are isAt* funcs side by side with isSomethingElse, and it's tempting to go over them as well, so the language of the API is consistent, but I also want to keep the scope of this manageable and easy to review.
Does the list above look good for the first PR, @ahoppen? I'm happy to support the migration to the new notation further if we will choose to.


Question: AzureAppServicesDiagnosticsSettings.OutputTemplate is not available in core 2.0 ?

Hello.
I use AspNetCore2.0 in azure apps with Microsoft.Extensions.Logging.AzureAppServices 2.0.0
I want to output custom format log in Azure apps application logs and log streaming.
So that, I configure  AzureAppServicesDiagnosticsSettings.OutputTemplate.
Following my startup.cs
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {

            loggerFactory.AddConsole(Configuration.GetSection("Logging"));
            loggerFactory.AddAzureWebAppDiagnostics(
                new AzureAppServicesDiagnosticsSettings
                {
                    OutputTemplate = "{Timestamp:yyyy-MM-dd HH:mm:ss zzz} [{Level}] {RequestId}-{SourceContext}: {Message}{NewLine}{Exception}"
                }
            );

but, Application log doesn't output above format.
And I find  that OutpuTemplate doens't use at AzureAppServicesLoggerFactoryExtensions.cs .
Please tell me AzureAppServicesDiagnosticsSettings.OutputTemplate is available ?
Thanks.

I'm having this same problem also. This has stopped working from when I upgrade 1.0 to 2.0 Core. It does work for the BlobName setting.

We stopped using serilog as a logger for App Services diagnostics and lost an ability to edit OutputTemplate unfortunately we forgot to remove/obsolete property itself.

So, to get the output template, we need to use Serilog then?

Yes


terraform init  error

➜  pass git:(main) ✗ terraform init
Initializing modules...
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
╷
│ Error: Invalid quoted type constraints
│
│   on .terraform/modules/tf-fc/variables.tf line 69, in variable "service_log_config":
│   69:   type        = "list"
│
│ Terraform 0.11 and earlier required type constraints to be given in quotes, but that form is now deprecated and will be removed in a future version of
│ Terraform. Remove the quotes around "list" and write list(string) instead to explicitly indicate that the list elements are strings.
╵
╷
│ Error: Invalid quoted type constraints
│
│   on .terraform/modules/tf-fc/variables.tf line 75, in variable "service_vpc_config":
│   75:   type        = "list"
│
│ Terraform 0.11 and earlier required type constraints to be given in quotes, but that form is now deprecated and will be removed in a future version of
│ Terraform. Remove the quotes around "list" and write list(string) instead to explicitly indicate that the list elements are strings.
╵
➜  pass git:(main) ✗ terraform init
Initializing modules...
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
╷
│ Error: Invalid quoted type constraints
│
│   on .terraform/modules/tf-fc/variables.tf line 69, in variable "service_log_config":
│   69:   type        = "list"
│
│ Terraform 0.11 and earlier required type constraints to be given in quotes, but that form is now deprecated and will be removed in a future version of
│ Terraform. Remove the quotes around "list" and write list(string) instead to explicitly indicate that the list elements are strings.
╵
╷
│ Error: Invalid quoted type constraints
│
│   on .terraform/modules/tf-fc/variables.tf line 75, in variable "service_vpc_config":
│   75:   type        = "list"
│
│ Terraform 0.11 and earlier required type constraints to be given in quotes, but that form is now deprecated and will be removed in a future version of
│ Terraform. Remove the quotes around "list" and write list(string) instead to explicitly indicate that the list elements are strings.
╵

This issue seems to have been fixed in this commit but there is no release generated. 🤦🏼


Hermes issues related to Tendermint-Go & SDK

Summary
This is a meta-issue capturing various problems we encountered in Hermes. Solving them requires some tendermint-go familiarity (or even other dependency), requires further context, and may be potentially blocked until an upstream fix appears in tm-go.
Sub-issues
The issues below are relatively high importance (we don't document here long-standing problems or wishes). Most of them should be fixed within 1-2 months ideally.

[x] #1264

The full context for this issue is as follows:

Our initial attempt at a solution is here #1349

This PR attempt to solve the problem by this logic:

parsing the error code which the chain replies to Hermes whenever the relayer uses the wrong sequence number, ref here;
upon encountering the predefined error code, Hermes re-fetches the sequence number by contacting the full node

This PR, however, does not take into account a more severe problem w.r.t. to the sequence number, which can be reproduced cf. this comment.
To solve the more severe problem, it seems we cannot rely on the information which the full node provides, i.e., step (2) in the logic above is not an appropriate fix.
Different solutions, such as avoiding caching altogether and always querying the full node for the seq. nr, also also not appropriate. The full node cannot be trusted, because one of Hermes' transactions remains stuck in that node's mempool, thus the node mistakenly believes Hermes should use a higher sequence number.
The only fix we know about is as follows: the relayer operator must restart the full node & explicitly flush the mempool, then Hermes has to reconnect to the full node

To summarize, we cannot solve this problem by making Hermes query the full node for the up-to-date seq. number, since the full node provides us with an incorrect value. Hermes cannot rely either on the deliverTx error message (which reflects the seq. number as the rest of the network sees it), because the full node which Hermes talk to will refuse that sequence number. For a principled fix, we need to get a deeper understanding of the mempool, and potentially submit a new feature request to tm-go mempool maintainers. This comment comprises some further ideas, but they are incomplete.

[x] #1299

Status:

We solved (part of) the problem on the tendermint-rs side

cf. https://github.com/informalsystems/tendermint-rs/pull/975

We are still aware of another websocket-related problem, which is awaiting a fix on tendermint-go side

https://github.com/tendermint/tendermint/issues/6729

Thane proposed to partially address 6729 with this PR https://github.com/tendermint/tendermint/pull/7230#issuecomment-961473954, which will be available on tm-go 0.34.x (SDK 0.44.x line); this has the potential of solving our base problem highlighted in #1299

[ ] #1400

[x] #1462

[x] https://github.com/informalsystems/tendermint-rs/issues/1021

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Closing this issue to reduce admin burden. There is only one last outstanding item (#1400) that we're handling individually.


Add xgcm module

Towards #3 - currently, takes approach of explicitly assembling the grid as opposed to adding extra metadata. Open to other suggestions.

This should be able to be closed in favor of the CF/COMODO attrs used in https://github.com/NCAR/xwrf/pull/14 (which should also work in general rather than here which just works when lat and lon can correspond to dimension coordinates), rather than marked as draft or "In Progress." Any opinions the other way?

@jthielen that sounds reasonable!! I can go ahead and close this if that is okay with everyone!


Fixing the spec file writer

There are a few problems with the current implementation of the spec file writer.  I will enumerate them here and submit three separate PRs; one per heading.
Bad #L line (fixed by #392)
The spec files that are currently being written do not actually work correctly because we are writing extra things on the #L line but not in the data table that immediately follows the #L line.  Example:
from bluesky.tests.utils import setup_test_run_engine
from bluesky.plans import DeltaScanPlan, AbsScanPlan, Count
from bluesky.examples import motor, det, det2
from bluesky.callbacks.core import LiveSpecFile
RE = setup_test_run_engine()
RE.ignore_callback_exceptions = False
!rm out.spec
dscan = DeltaScanPlan([det, det2], motor, -1, 1, 10)
ascan = AbsScanPlan([det, det2], motor, -1, 1, 10)
ct = Count([det])
RE(dscan, [LiveSpecFile('out.spec')])
!cat out.spec

and the output:
#F out.spec
#E<PHONE_NUMBER>.2857118
#D 2016-03-21 14:05:12.285712
#C test_owner  User = test_owner
#O0 No Positioners Were Given

#S 1 dscan motor -1 1
#D 2016-03-21 14:05:12.285712
#T -1 (Seconds)
#P0 -inf -inf -inf -inf
#N 5
#L motor    Epoch  Seconds  det  det2  motor
0.0<PHONE_NUMBER>.4079819 -1 1.0 1.764993805169191
0.2222222222222222<PHONE_NUMBER>.725613 -1 0.9756109800648459 1.764993805169191
0.4444444444444444<PHONE_NUMBER>.8443232 -1 0.9059551911095096 1.764993805169191
0.6666666666666666<PHONE_NUMBER>.9804332 -1 0.8007374029168081 1.764993805169191
0.8888888888888888<PHONE_NUMBER>.1254492 -1 0.6736384553447268 1.764993805169191
1.1111111111111112<PHONE_NUMBER>.261288 -1 0.5394075072376265 1.764993805169191
1.3333333333333333<PHONE_NUMBER>.3805876 -1 0.41111229050718745 1.764993805169191
1.5555555555555554<PHONE_NUMBER>.5015962 -1 0.29823409618142166 1.764993805169191
1.7777777777777777<PHONE_NUMBER>.6174684 -1 0.20592424643419874 1.764993805169191
2.0<PHONE_NUMBER>.732594 -1 0.1353352832366127 1.764993805169191

Note that motor is listed twice in the #L line but only appears once in the data table.  There are six elements on the #L line but only 5 entries in the data table.
Acquisition time not being represented accurately
Even when you pass in the acquisition time to dscan it is not being propagated to the spec file writer.
from bluesky.global_state import gs
from bluesky.spec_api import dscan
from bluesky.examples import motor, det
from bluesky.callbacks import LiveSpecFile
! rm out.spec
specwriter = LiveSpecFile('out.spec')
gs.DETS = [det]
gs.RE.md['owner'] = 'test'
gs.RE.md['group'] = 'test'
gs.RE.md['beamline_id'] = 'test'
gs.RE.md['config'] = {}
dscan(motor, -1, 1, 10, 1, specwriter)

uid is
['68c03b49-966c-4904-a4ed-577bd4d44b28']

and the spec file looks like:
#F out.spec
#E<PHONE_NUMBER>.9367123
#D 2016-03-21 14:20:01.936712
#C test  User = test
#O0 No Positioners Were Given

#S 6 dscan motor -1 1 (10,)
#D 2016-03-21 14:20:01.936712
#T -1 (Seconds)
#P0 -inf -inf -inf -inf
#N 4
#L motor    Epoch  Seconds  det  motor
-1.0<PHONE_NUMBER>.2141356 -1 0.6065306597126334
-0.8<PHONE_NUMBER>.277252 -1 0.7261490370736908
-0.6<PHONE_NUMBER>.3425076 -1 0.835270211411272
-0.3999999999999999<PHONE_NUMBER>.4054952 -1 0.9231163463866359
-0.19999999999999996<PHONE_NUMBER>.472727 -1 0.9801986733067554
0.0<PHONE_NUMBER>.5365283 -1 1.0
0.20000000000000018<PHONE_NUMBER>.5991907 -1 0.9801986733067553
0.40000000000000013<PHONE_NUMBER>.665147 -1 0.9231163463866358
0.6000000000000001<PHONE_NUMBER>.7268472 -1 0.835270211411272
0.8<PHONE_NUMBER>.7940352 -1 0.7261490370736908
1.0<PHONE_NUMBER>.8567617 -1 0.6065306597126334

The acquisition time of 1 in the dscan(motor, -1, 1, 10, 1, specwriter) invocation is not seen in the scan invocation line (#S) and it is showing up as the default value of -1 in the #T line and in the data table.  This appears to be because this information is not being captured in metadatastore.
db['68c03b49-966c-4904-a4ed-577bd4d44b28'].start.plan_args

output:
{'detectors': '[reader: det]',
 'motor': 'mover: motor',
 'num': '11',
 'start': '-1',
 'stop': '1'}

Yikes!  This happens on the live set up at CHX too.  See scan 'fa616713-2397-428c-8a11-92c8da73b94b'. Lutz says that this was created with the command: dscan(s1.yc,-.05,.05,5,1)
Capturing the position of relevant motors on the beamline before the scan starts
This is essentially the output of wh_pos, but formatted for spec's consumption.  There are three places where this needs to be performed.

In the header of the spec file (note that the spec file header is distinct from the scan header) with the #O0 line. This line is the 'human readable' set of motor names
Also in the header of the spec file with the #o0 line. This is the name of the motor that you would type in spec. The equivalent would be the Python variable names in the IPython session
In the header of each scan with the #P line. This is the current value of the motor. It needs to be in the same order as in #O and #o.

cc @danielballan @lweigart @afluerasu @vivekthampy

The acquisition time is not being stored in metadatastore.

Yes. The acquisition time is not in plan_args because it is part of the object's configuration, not part of the plan (just like num_images, for example). In the SPEC-style API, we do accept a time argument. Every device that has a count_time attribute gets set to this time. Any devices that don't (including area detectors) are currently ignored. None of this is part of the Plan.
The way forward:

Add a count_time attribute to all detectors that sets the actual EPICS signals (acquire_time, acquire_period, num_images, ...) appropriately.
Include 'count_time' in the detector's configuration_attrs so that it is stored in metadatastore.
Program the SPEC callback to read the time from the metadatastore:

# start with some field_name like xray_eye1_stats1_total
obj_name = descriptor['object_names'][field_name]
config = descriptor['configuration'][obj_name]  # the result of obj.read_configuration() was stored here
count_time = config['count_time']

Capturing the position of relevant motors before the scan starts

This information will be recorded in a separate event stream. There is a PR in bluesky waiting to merged at the end of this cycle. Users will probably provide some different list of detectors (and motors) in some new field like gs.BASELINE_DETS. For now, I suggest we keep inserting a placeholder and wait to do this right -- first thing at the end of the cycle.

@tacaswell During deployment, did you put a count_time signal on the detector(s) at CHX? That would be the last piece of this issue.

No

Turns out CHX wants to interpret "count_time" as what we can "num" --- not det.num_images, but num as in the integer argument to count. So to them time is a dimensionless integer, not something that has units of seconds. To each their own!
This concludes the issues with the SPEC callback mentioned in this issue.


Missing pack/module still allows to start up a blog

This happens when bc_main is not loaded before the offending pack/module.

Related issue: #128
Currently a custom code has been added in the master to check for installed pack versions.

Link to implementation:
https://github.com/rla/blog-core/blob/058ee9abf13cdb3465f4cf191f52d103095147fa/prolog/bc/bc_dep.pl


text/1607-style-rfcs.md: Markdown formatting fix

The previous rendering had half the page trapped in an unterminated code block (old version rendered, new version rendered).

Looks like a good and straightforward fix. Thanks!


Update latest version

update combat width ref: https://hoi4.paradoxwikis.com/Terrain
set min division width to 8

@kailniris please review my mr

@apichaikub Thanks for your contribution!

@apichaikub Thanks for your contribution!

it's ok, this tool is very helpful for me as well.
btw, my best width is 15 and 18w for now :)


Mustache blocks not exhibiting conditional behaviour

I have the following context:
var context = { Results: [
    { Name: "Store A", Distance: "3.14"},
    { Name: "Store B", Distance: "2.71"}
] };

...and Mustache template

{{#Results}}

    {{Name}}
    {{#Distance}}
    {{Distance}} miles away
    {{/Distance}}

{{/Results}}

If rendered using Mustache the {{#Distance}} block acts as a conditional. The span will be rendered with the value of Distance, e.g. "Store A 3.14 miles away".
Handlebars renders it as "Store A miles away" even when Distance has a value. The {{Distance}} in the span is not being rendered.
Is this a known issue? Do you have a workaround?

Looks like Mustache's sections inherit the parent's scope, while Handlebars' sections overwrite it.
http://jsfiddle.net/zvNMf/

Relevant section from Mustache docs:

Non-False Values
When the value is non-false but not a list, it will be used as the context for a single rendering of the block.
Template:

{{#person?}}
  Hi {{name}}!
{{/person?}}

Hash:

{
  "person?": { "name": "Jon" }
}

Output:

Hi Jon!

So sounds like mustache.js is violating the mustache spec? Or am I reading it wrong?

The spec says nothing about inheriting contexts, but the original implementation in Ruby deals with a stack of them. If the property isn't defined on the object given to the block, it bubbles up.
Here's the code that renders the section for non-booleans, and here is the name lookup function.

This is what happens in mustache.js:
{{#person}}
  {{name}}
{{/person}}

{
  "person": "Yehuda",
  "name": "Come on"
}

The "stack of contexts" explanation explains what's happening here, but it is decidedly not in the spec. The spec says:

When the value is non-false but not a list, it will be used as the context for a single rendering of the block.

I suppose that we could make blockHelperMissing treat "non-false but not a list" like a conditional, but it really seems like mustache.js is violating the spec, and not us.

It's worth noting that Handlebars provides a mechanism for pointing at the parent context:

{{#Results}}

    {{Name}}
    {{#Distance}}
    {{../Distance}} miles away
    {{/Distance}}

{{/Results}}

Additionally, using {{#if Distance}} would clear up the ambiguity and result in Handlebars not entering a new context.

I'm closing this issue for now, because Handlebars is in compliance with the Mustache.js spec here, and Handlebars provides several mechanisms for dealing with this situation that make the stacks-of-context solution unnecessary.


cannot load such file -- google/api_client

I am having an issue with this gem on Mac with High Sierra 10.13.6 and Ubuntu 18.04 Bionic Beaver.
irb(main):001:0> require 'google/api_client'
Traceback (most recent call last):
        4: from /home/localadmin/.rbenv/versions/2.5.1/bin/irb:11:in `<main>'
        3: from (irb):1
        2: from /home/localadmin/.rbenv/versions/2.5.1/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
        1: from /home/localadmin/.rbenv/versions/2.5.1/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
LoadError (cannot load such file -- google/api_client)

google-api-client (0.23.4)

There is no "google/api_client" file. Instead, require the file corresponding to the API you want to use. e.g. to use version v2 of the "drive" API client, do:
require "google/apis/drive_v2"