Multiplot/fetch_multi changes

Made a number of fixes/enhancements to the finder:

Graphite requires the datapoints returned by the finder to be
equidistant in time, (interleaved with Null datapoints if necessary.)
We weren't doing this so the timescale was off on graphs with sparse data.

Improved performance significantly by switching to fetch_multi/multiplot.
(Note this required updating the graphite-api code from version 1.0.1 to
Head of master.  Since we also had to patch that code I created a new repo
for it here: https://github.com/rackerlabs/graphite-api/tree/george/fetch_multi_with_patches

One other detail about fetch_multi is that it has to take the multiplot limits into
account.  Multplot allows only 100 metrics per call, and has implicit limit of around
7000 json characters. So my changes batch up each of graphite-apis fetch_multi() calls
into to the minimum number of multiplot calls that still abide by those limits.

Now supports specificy specific submetric names in the config file, (rather
than just assuming "average", "num_points" or "latest" as we were before.
This required changes on both the search side, and the fetch_multi side.
This work was based on the changes suggested and created by Alex Weeks:
https://github.com/aweeks

Finally added a bunch of tests to get coverage of this file up to 93%:
https://23282e1499f9e238db58e26751fc6d96be63cc17-www.googledrive.com/host/0B28IWTWKORCkfnlLYmljbW1NQ295NWhWbmtfbDJ1UXYwQm9xdlVuMjN0NFV1QTNmcDltY2M/x/blueflood.html

Coverage decreased (-0.08%) to 51.34% when pulling a0d8e812fbda821afb9885031c79d59458031b77 on george/add_fetch_multi2 into 7072b54f3ab80cf16fba5a0c4759e2220f123732 on master.

Coverage decreased (-0.01%) to 51.43% when pulling c21dd403edc118ffe614324f143c433185acd5d3 on george/add_fetch_multi2 into acc39a6045440c03128b1c9684c071a229302cba on master.

These files have been updated per the review from chinmay-gupte.

Tried to simplify the find_nodes() method a bit by splitting
it out into 2 separate methods depending on whether submetrics are
used or not.

Changed the term "cache" to "dictionary"

No longer sorts timestamps, because they are sorted from BF.

Chinmay suggested that we rollup metrics that coexist in the same
"step", (instead of dropping all but the first.)  However, this
problem only occurs when full res metrics have sub-second frequencies.
Since that seems to be a rare case, I've just documented the problem
for now, and will fix it when it actually becomes a problem

Note that if you only want to see the diffs since the initial
version of this PR, you can see them like so:
git diff 6e7e811 c21dd40

The lastest diffs:
https://github.com/rackerlabs/blueflood/compare/c21dd403edc118ffe614324f143c433185acd5d3...george/add_fetch_multi2

Coverage remained the same at 51.44% when pulling 22d4dd7f203b28d4906f94d3a1cf4e9b8bf0334e on george/add_fetch_multi2 into acc39a6045440c03128b1c9684c071a229302cba on master.

+1 after my last comment has been addressed.


Verify notification handling on cold launch

Check that the app also executes the associated action when the app wasn't yet running when the user interacted with the notification.

Test instructions: this one is hard to test due to the due dates often being 1 year in the future.


Doesn't handle escaped imports properly

It says the first import is unused. It's wrong. Quick fix is there https://github.com/shyiko/ktlint/pull/6
import org.mockito.Mockito.`when`
import org.mockito.Mockito.mock

class LinterFailure {
    fun foo() {
        val bar = mock(LinterFailure::class.java)

       `when`(bar.foo())
    }
}

Thank you for the PR! Included in 0.1.2 (which should become available through Maven Central within the next 2 hours).


Added module config opts to complement PR in ZF2

Added module config opts to complement PR in ZF2

Reviewed and merged into master, thanks!


feat: Handle splitted next-auth.session-token cookie

🔗 Linked issue

#139
#160
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Module options fills the runtimeConfig (private and public).
RuntimeConfig typings updated.
useAuth's sessionToken returns the cookie handled by makeSessionCookie (handles splitted session token).
NuxtAuthHandler uses getAuthJsSecret if receives no token from AuthConfig.
getServerToken uses makeCookiesFromHeaders to manage cookies.
Added end edited some utils:

A - getAuthJsSecret: gets the secret from runtime or env vars.
A - getConfigBaseUrl: gets the baseUrl from runtime or env vars.
M - checkOrigin: uses getConfigBaseUrl
M - getServerOrigin: uses getConfigBaseUrl.
A - mergeCookieObject: merges cookies.
A - makeSessionCookie: gets the next-auth.session-token (handles splitted session token).
A - makeCookiesFromHeaders: manage multiple 'set-cookie' and makes native Headers.
M - makeNativeHeaders: made it an utility.
M - makeNativeHeadersFromCookieObject:  uses makeNativeHeaders.

Added some tests.

Resolves the 'getServerToken returns null issue'.

#139
#160
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Any progress on this PR? I am having the issue with getServerToken returning Null 😿
Thanks for this wonderful package, I hope to continue to use this.

@Hebilicious Any progress on this PR? I am having the issue with getServerToken returning Null on the current npm version 😿
Thanks for this wonderful package, I hope to continue to use this.

Hello there.
The problem is that I don't personally use auth.js anymore and I have no easy way to test if this PR will break existing code ...
I'm also no longer maintaining this package, as the auth.js team never moved forward with their plans.
Now issues are piling up and I don't have the time, the incentive or the desire to fix them.
If someone is willing to test this PR, I would merge it.


#937 - Solution proposal

Waiting for comment, all tests passed.
I will add tests for this feature after it's approval.
Before

After:

Alright super close! This definitely resets the animation but I think it also prevents advancing to the next screen. When I tried it out using the green "right" arrow to advance through the lesson, I just got stuck in the loop of going to the reset button -> back to the original starting point, but I could never advance to the next part of the lesson.
I think this is because that positive method just puts us in a loop. I think we would need to do something like this:
onResetButtonClick: () => {
  this.demonstrated = false;
  this.takeControl();
}

and then just wire up the button click

Yeah, sorry for that. I completely forgot to check it🤦🏻♂. Should be fixed with the last commit.
I am glad the rest is okay, and I am not sure if I should add some tests.

Looks great! Going to do two little polish things (change it to "Reset Animation" and maybe fade it out a bit) but thanks so much :D


Just saying thanks

@homer0, I'm dropping by to express my immense gratitude for creating this plugin! It's become an indispensable tool for keeping my JSDoc comments clean and consistent.
I'm currently using it with JavaScript and TypeScript and it works wonders. And the ability to create extend the plugin for specific formatting needs is chef's kiss! 🤌
I can't thank you enough for your hard work and dedication to this project.

@toridoriv thank you so much :D!! I'm really happy to hear it's helpful for you!


watch 命令不支持 https

Describe the bug

测试服务器为nginx，在nginx服务器启用kyanos（最新版本）
客户端使用wrk 发起https请求
watch没有显示相关连接信息，辅助tcpdump抓包能够捕获数据请求

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Information (please complete the following information):

OS:

Your pictures were not uploaded correctly.


⚠ SolarOscp has degraded performance

In b4e383b, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 400 ms

Resolved: SolarOscp performance has improved in 07c87cd after 26 minutes.


Change content of account registration email

Per @mjstealey
We’ve had some issues with some mail services, google in particular, automatically flagging emails from HydroShare as spam.
At RENCI the SPF portion of the DNS entry for mail.hydroshare.org in Media Temple has been updated to better account for this, but it was advised that we also change the contents of the generated email.

We use Mezzanine's email template out-of-the-box as content of our registration signup verify email as shown here: https://github.com/stephenmcd/mezzanine/blob/280642c8d0e7e41b90398c974a15533f6df20049/mezzanine/accounts/templates/email/signup_verify.txt
If we can come up with a better content language for our registration verify email, I can try to override the default mezzanine email content template and direct Mezzanine to use our own email language instead. @dtarb @horsburgh Suggestions on the registration email content to avoid being flagged as spam by email servers?

Please use:
Welcome to HydroShare.  This email address was used to request an account on HydroShare.  If you originated the request, please use the link below to verify your email address and activate your account.  If you did not originate this request you may ignore this email and the account request will expire.
The HydroShare team.

The part about the request expiring is likely to be untrue. Unless you have some customization place I have not seen, Mezzanine's registration and account verification has no expiration. An unresponded verification email could remain valid forever.

OK.   Lets delete "and the account request will expire.".  I do think we need an expiry clean up process that runs say every 24 hours and deletes account requests older than 24 hours (so a request could persist 24 to 48 hours) because otherwise if a person makes a legitimate request but does not respond and loses the email that email address is locked out forever.

@dtarb @ironfroggy I have override default Mezzanine email verification content with the suggested one and also changed subject of email verification from "Activate your account" to "Activate your account in HydroShare". I also found out the verification link does expire in the same way as the password reset link since the token generated is time stamped and will expire in a time duration set up by PASSWORD_RESET_TIMEOUT_DAYS variable with the default value being 3 days and we can set it to be 1 day to make it expire in 24 hours. My only question related to this issue is how we should clear up the inactive user being created if the user does not click the link in the verification email within 24 hours. I can add clean-up code to delete the inactive user when this email verification link is clicked beyond 24 hours, but not sure whether this is sufficient and whether it is worth the effort since it does not cover the case where the email verification link is never clicked which will leave some inactive users hanging around in our system. In addition, in django documentation https://docs.djangoproject.com/en/1.4/topics/auth/, it states that we recommend that you set this is_active flag to False instead of deleting accounts; that way, if your applications have any foreign keys to users, the foreign keys won’t break. Of course, system admin can always go to admin page to clean up inactive users periodically as needed. So I am not sure what is the common practice for this scenario. @ironfroggy any suggestions/advice?

I think if you set the link to expire you should still leave the account. If they want back in they should be able to re-enable the account by a password reset.

@ironfroggy OK. Sounds good, then I don't have to do anything extra and can create a PR for code review now.

@dtarb @ironfroggy @mjstealey  Tested on dev and everything works as expected. However, this activation email is initially flagged as spam by gmail, and I have to remove the spam label initially to have it moved into inbox onward. Not sure what else we can change to make the email more legitimate without being flagged as spam by different email service providers.

That's always a difficult thing and there are not easy answers.

@dtarb This has been deployed to www. You can test it out on either www or dev and see whether this issue can be closed. See the comment thread for this issue which provides context for the current implementation.

@hyi @dtarb would you please close this issue if you think it is fixed? Thanks

@hyi please change the email as follows

Welcome to HydroShare. This email address was used to request an account on HydroShare www.hydroshare.org.

If you originated the request, please use the link below to verify your email address and activate your account.

https://www.hydroshare.org/accounts/verify/...

If you did not originate this request you may ignore this email and the account request will expire in 24 hours.

The HydroShare Team

Please check on the last issue.  @ironfroggy noted that the expiring is unlikely to be true. I think we should implement expiring when possible (a separate issue) but not state it in the email in case we are unable to.  Please add "The HydroShare Team" at the end.

@dtarb Expiring in 24 hours has already been implemented, so the statement "the account request will expire in 24 hours" is already true in our current implementation. See my detailed info above in this issue thread for details. So I will change email message slightly as you detailed above, i.e., replace HydroShare with www.hydroshare.org and add "The HydroShare Team" at the end while keeping the expiration statement. Will create a PR shortly.

Using a gmail account the following email was received when creating a new account.
Of note is that it was flagged as spam

Still need to verify that the 24 hour timeout expiration is as advertised (will perform this on another VM as dev gets rebuilt frequently).

Even with expiry implemented I think we should delete the words "and the account request will expire in 24 hours." from the email.
With respect to SPAM, I receive emails sent to<EMAIL_ADDRESS> A huge number of these are spam marketing better health and libido products.  I wish there was a way to stop them, but somehow this email address has gotten on a list that attracts these.  I do not know whether this is related to the legitimate emails we send being flagged as spam.

@dtarb @mjstealey Could you test to see whether this issue has been addressed adequately for now and close if the answer is yes?

Verified


Docker: Disable Grafana and co.

Done.


chore: omnipool runtime integration

This PR adds following pallet to hydradx runtime:

pallet-uniques
pallet-nft
pallet-omnipool

pls add Uniques and NFT to call filter, so these pallets cannot be used by users directly

It is already in the filter.


Feat: Add functionality to specify the Vikunja volumes using the volumeSpecification utility.

Follow example of Nocodb: create-files--for-nocodb.nix
Steps:

Add configuration options that allow users to configure how to specify the volumes.
In the Docker compose file creation, use the volumeSpecification utility to generate the volume information based on the configuration.

Added the changes with this commit: Commit - 856d7c4

Added a fix for the code in this commit: Commit - cc7c240


Parquet list reader not reading correct element lengths

Describe the bug
This is https://issues.apache.org/jira/browse/ARROW-13120 moved here, with a bit more details.
The issue is that the list reader does not check repetitions to calculate the correct number of values to read in order to correctly compose a list.
To Reproduce
Given an array:
{"list": [1, 2, 3]}
{"list": [4, 5]}

Reading 2 values should return the 5 child values, but only 1 and 2 are returned.
Expected behavior
List reader should calculate the correct number of child values to read, then return those values instead of slicing between arrays.
Additional context
This bug seems to have existed before the new arrow reader contributed by @yordan-pavlov

@mcassels I've opened this issue to track the bug that you identified

@helgikrs  has been recently working on some fixes for this type of issue in https://github.com/apache/arrow-rs/pull/1187 https://github.com/apache/arrow-rs/pull/1166 and https://github.com/apache/arrow-rs/pull/1185 . I wonder if someone could check if it is still an issue

This does not appear to be an issue anymore, possibly closed by #1588 or some prior pr


Proposal War support with Gradle

Towards #431, here's my proposal to support "WAR" project with Jib.
If the "webAppRoot" is filled, these layers are relocated as following :
- "resources"  --> webAppRoot/WEB-INF/classes
- "classes"  --> webAppRoot/WEB-INF/classes
- "dependencies" --> webAppRoot/WEB-INF/lib
- "snapshot dependencies" --> webAppRoot/WEB-INF/lib
I've created 3 more layers :
- "webapp" for JSP files, assets, angular generated files, ...
- "meta-inf" for files like "context.xml"
- "web-inf" for files like "web.xml", etc...
I'm going to rebase tonight on master to replace my implementation of "entrypoint" with yours.
Upon validation, I will consolidate with more tests, clean-ups and maybe an implementation for the maven plugin.
I've performed some real life tests with 10 different  "Tomcat" projects.~~

Thanks for your contribution!
We've done and reviewed an internal design for WAR support, and our design has one main difference from yours: we decided that we will use and rely on WAR assembly plugins to package a WAR instead of packaging ourselves from the webapp source directory, compiled .class files, etc. Below are some rationales for the decision.
We thought that it is impractical to extend Jib to become another complicated WAR-packaging plugin. We also believe conforming to the de-facto WAR-packaging plugins provides more complete support for real-world WAR-use cases. Note some examples of what the maven-war-plugin does:

Adding arbitrary external web resources with <webResources>

Can configure where to pull (<directory>) and place (<targetPath>) resources
Can also configure <includes>/<excludes> and <filtering> (interpolating property values in some files).

web.xml filtering with <filteringDeploymentDescriptors> (interpolating properties values)
Sharing common resources across multiple web applications (overlays)
Including and excluding files from the final WAR with <packagingIncludes> and <packagingExcludes>
Placing dependency JARs under WEB-INF/lib depending on <scope> or <optional> values of <dependency>s in pom.xml.

That said, could you revise your PR to use and take the final WAR produced by the Gradle WAR Plugin? We've recently checked in the ZipUtil class into your codebase, which you can use to unpack a WAR. You'll be able to see ZipUtil once your merge with the HEAD.

I signed it!
Le lun. 3 sept. 2018 à 15:59, Chanseok Oh<EMAIL_ADDRESS>a
écrit :

Thanks for your contribution!
We've done and reviewed an internal design for WAR support, and our design
has one main difference from yours: we decided that we will use and rely on
WAR assembly plugins to package a WAR instead of packaging ourselves from
the webapp source directory, compiled .class files, etc. Below are some
rationales for the decision.
We thought that it is impractical to extend Jib to become another
complicated WAR-packaging plugin. We also believe conforming to the
de-facto WAR-packaging plugins provides more complete support for
real-world WAR-use cases. Note some examples of what the maven-war-plugin
does:

Adding arbitrary external web resources with

Can configure where to pull () and place ()
resources
Can also configure / and
(interpolating property values in some files).

web.xml filtering with
(interpolating properties values)
Sharing common resources across multiple web applications (overlays)
Including and excluding files from the final WAR with
 and
Placing dependency JARs under WEB-INF/lib depending on  or
 values of s in pom.xml.

That said, could you revise your PR to use and take the final WAR produced
by the Gradle WAR Plugin? We've recently checked in the ZipUtil class
into your codebase, which you can use to unpack a WAR. You'll be able to
see ZipUtil once your merge with the HEAD.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleContainerTools/jib/pull/923#issuecomment-418123723,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD5az-HLebtNdv0asxJPQSva45jhhtx1ks5uXTXCgaJpZM4WXPwm
.

If I understood you correctly (sorry I'm French ), you want a design like this :

let gradle generate the war file (with the standard plugin)
unzip it in a temporary folder (with com.google.cloud.tools.jib.plugins.common.ZipUtil)
and then, create the "dependencies", "classes", "snapshot dependencies", "webapp" layers

It's an another solution but it creates a lot of duplicate/temporary files. The Gradle plugins avoid generating this usually.
Nevertheless I agree with you, it would be better to rely on the information given in the war definition.

If I understood you correctly (sorry I'm French ), you want a design like this:

Yes, exactly. It would have been nice if there were a way to avoid unpacking the WAR, but I couldn't really find such a way so far. (Not that I really looked into Gradle thoroughly for this.)

Also, I think it's better to let the user define the webapp root in the container.

Our design did not allow this, at least for the very first implementation (we were exploring if there could be a way of zero-configuration), but I guess allowing to configure the webapp location in an image may actually be useful to quickly support arbitrary base images. We will discuss this approach internally.

3.and then, create the "dependencies", "classes", "snapshot dependencies", "webapp" layers

Oh, forgot to mention that we think

WEB-INF/classes/***/*.class go into the "classes" layer (probably excluding non-.class files)
WEB-INF/lib/*-SNAPSHOT.jar into "snapshot dependencies"
Other WEB-INF/lib/*.jar into "dependencies"
All other files into "resources"

I'm wondering if you also think this makes sense.

@CyrilleH just checking in, as I haven't heard back from you for a while. Are you working on this?
And just a heads-up: we had an internal discussion about the webAppRoot configuration parameter, and we decided we won't add it, at least in this PR.

I thought you rejected my proposal.
Since it works very well for us, I decided to wait a little bit to understand the direction you take.
Do you want to support only Jetty (for example) ? Do you want to implement only one webapp layer ?

Ok, I'll try to implement something this weekend.

exploding a war shouldn't be too hard: https://github.com/GoogleCloudPlatform/app-gradle-plugin/blob/master/src/main/java/com/google/cloud/tools/gradle/appengine/standard/ExplodeWarTask.java

Yes, "Sync Task" is the best way to explode a War with Gradle.
If I understand this (issue)[https://github.com/GoogleContainerTools/jib/issues/964] correctly, I have to change my "jib.container.webAppRoot" parameter into "jib.container.appRoot".

If I understand this issue correctly, I have to change my "jib.container.webAppRoot" parameter into "jib.container.appRoot".

I am taking care of #964 with #984. You might want to merge with that branch.

Ok thanks.
Maybe I could use something like that (and work directly with the war file) :
`
import java.nio.file.FileSystem;
import java.nio.file.FileSystems;
final FileSystem zipfs = FileSystems.newFileSystem(war.getArchivePath().toPath(), JavaLayerConfigurations.class.getClassLoader());
Path dependenciesFiles = zipfs.getPath("/WEB-INF/lib");
try (Stream stream = Files.list(dependenciesFiles)) {
stream.forEach(dependenciesFiles::add);
}
`
I'm going to do some tests to see if it's a good solution.

Please let me know if it's good enough for you.
When your branch will be merged on master, I will rebase my branch.

@CyrilleH thanks for your time for implementing this. Haven't looked into the code yet, but I think we're going to the right direction. Once #964 is merged into master, we will be able to start reviewing this PR in detail. So I will have to ask you to merge with master later once #964 is done. I'll try to get #964 in ASAP.

@chanseokoh I've rebased on your branch.

@CyrilleH thanks! I just noticed that I need to further change JavaLayerConfigurations to allow configuring layers with more flexibility (#1007). I'll work on #1007 on top of #984.

Yes, my code is not ideal in JavaLayerConfigurations :
          Path subPath = Paths.get(extractionPath);
          if (layerType.equals(LayerType.RESOURCES)
              && layerFile.getParent() != null
              && layerFile.getParent().endsWith(WEB_INF)) {
            pathInContainer = subPath.resolve(WEB_INF).resolve(layerFile.getFileName());
          } else {
            pathInContainer = subPath.resolve(layerFile.getFileName());
          }

@CyrilleH  just an update. Sorry for the delay. Fixing #1007 needed some more thoughts, as it is about changing the API to be general.

#1007 is fixed. Please merge with master. Hopefully you won't need to tinker with JavaLayerConfigurations and JavaDockerContextGenerator anymore.

Thanks. Looks like this is in a good shape for review. @GoogleContainerTools/java-tools falks, PTAL.

There are test failures. You can run the tests locally with ./build.sh.

Yes, it is an empty directory which is not commit.

Yes, it is an empty directory which is not commit.

Yeah, AFAIK, it is not possible to commit an empty directory in Git. There's the trick to add .gitignore, but I guess it's not applicable to us to work as a test case. I think you'll need to revise the test case that doesn't deal with an empty directory, unfortunately.

We use a .gitkeep file to keep an empty directory, such as in the jib-core/src/test/resources/directoryA.

What do you think about this code in setUp() :

The empty directory is created in the build folder so for me it's good enough.

OK, seems we can create it that way. Just remove the if (Files.notExist()). Generally tests should be decisive with no ambiguity or uncertainty.

But, it's mandatory. If we don't test the directory existence, we can't re-play the test without cleaning the project.

@coollog thanks for your code review.
I pushed a fix.

Didn't look into every test detail, but this looks OK-ish. I'd like to update some Javadocs/comments, rename variables, refactor some code, but I think I can take care of those things after merging this.
@coollog if you are good with the new way that the default base image and appRoot is set (see https://github.com/GoogleContainerTools/jib/pull/923/files#diff-9266d6136413955a86ce0592f20891f6R44 and https://github.com/GoogleContainerTools/jib/pull/923/files#diff-aef8bf567c91df6622aa0ea29ed0c682R133), I think we can merge this soon?

Okay LGTM. We should add an integration test for a Gradle war project to JibPluginIntegrationTest but that can be in a follow-up PR.

About adding integration tests, we are keeping track of it, so we're good: https://github.com/GoogleContainerTools/jib/issues/431#issuecomment-422827669
I'll merge this PR maybe on Monday. Anyone can review this until then. I will be working on some cleanups on my side on top of this PR.


Implement v1 branch seeding

This commit takes a cut at implementing seeding in the v1 branch. I originally submitted a PR to https://github.com/99xt/dynamodb-migrations/pull/6, but it looks like that project is being deprecated by this version of serverless-dynamodb-local.
My serverless.yaml file looks like this:
dynamodb:
   start:
     seed: true
   seed:
     domain:
       sources:
       - table: widgets
         sources: [./widget-table-data.json]

     test:
        sources:
        - table: users
          sources: [./fake-test-users.json]

> sls dynamodb seed --seed=domain,test

Basically what's going on is that after the tables are spooled up, we will scrape the sources in the for seeds, which represent rows in Dynamo. If the files are arrays, each object is a seed, if the files are objects, then it's a seed.
I'd like to think of a way that predicates the loading of these things: My thought ways maybe have a loadStage array in each seed config that would conditionally use the sources based on the current stage variable. This would allow users to load stuff like domain data into production databases, but only load mocked up data in development or integration. What do you guys think?
I wanted to avoid including the seed data here for a couple of reasons: domain data and test data are not configuration by nature, and in some cases the test data could be pretty large. In my case, I have about 15mb going into a table.
This commit also corrects the promise sequencing and offline-hook setup at startup. I was running into an issue where this plugin would not start up prior to serverless-offline.

The codacy check here is interesting. Most of the issues it has are with single-quote strings, but the code was written with single quote strings already. I can fix that if you guys want, but I think it would make sense to use eslint in the package build itself to ensure that code follows the style you expect.

So another option would be to give each seeding source a category, and define a runtime opt to seed certain categories. e.g.
dynamodb:
   start:
     seed: true
   seed:
     locations:
       - table: domain
         sources: [./domain-table-data.json]
         category: domain
       - table: users
         sources: [./fake-test-users.json]
         category: test

And then invoking it:
> sls dynamodb seed --category=domain,test

LGTM.  👍
Thanks @darthtrevino for the wonderful PR.

@darthtrevino Thanks for the PR. There are few merge conflict due to delay in merging and the fault is from our side. Will you be able to resolve the conflicts and update the PR?

I can resolve the merge conflicts later today
On Wed, Feb 22, 2017, 1:14 AM Ashan Fernando<EMAIL_ADDRESS>wrote:

@darthtrevino https://github.com/darthtrevino Thanks for the PR. There
are few merge conflict due to delay in merging and the fault is from our
side. Will you be able to resolve the conflicts and update the PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/99xt/serverless-dynamodb-local/pull/77#issuecomment-281612246,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG7iKVoOMS94Pl1LaqR-6E-iSkgEPhjks5re_x2gaJpZM4MFa4e
.

This looks okay on my end, let me know if you need anything else

I use node 4.3.2(The node version AWS Lambda uses) to match my development environment as closely to the live environment as possible.
This merge doesn't seem to work with that node version.
  Syntax Error -------------------------------------------      Unexpected token {      For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.   Stack Trace -------------------------------------------- SyntaxError: Unexpected token {     at exports.runInThisContext (vm.js:53:16)     at Module._compile (module.js:373:25)     at Object.Module._extensions..js (module.js:416:10)     at Module.load (module.js:343:32)     at Function.Module._load (module.js:300:12)     at Module.require (module.js:353:17)     at require (internal/module.js:12:17)     at C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:59:22     at Array.forEach (native)     at PluginManager.loadPlugins (C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:58:13)     at PluginManager.loadServicePlugins (C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:86:10)     at PluginManager.loadAllPlugins (C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:54:10)     at C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js:64:28     at process._tickCallback (node.js:364:9) From previous event:     at processImmediate [as _immediateCallback] (timers.js:383:17) From previous event:     at C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\bin\serverless:15:28     at Object.<anonymous> (C:\Users\Niels\AppData\Roaming\npm\node_modules\serverless\bin\serverless:27:4)     at Module._compile (module.js:409:26)     at Object.Module._extensions..js (module.js:416:10)     at Module.load (module.js:343:32)     at Function.Module._load (module.js:300:12)     at Function.Module.runMain (module.js:441:10)     at startup (node.js:134:18)     at node.js:962:3   Get Support --------------------------------------------      Docs:          docs.serverless.com      Bugs:          github.com/serverless/serverless/issues      Please report this error. We think it might be a bug.   Your Environment Information -----------------------------      OS:                 win32      Node Version:       4.3.2      Serverless Version: 1.7.0

@nielslanting That's fair, according to the Node LTS schedule, v4 will be maintained for about another year. After that point, it will make sense to switch to v6 syntax.

The serverless-offline project was just updated to support a shutdown hook, this PR has support for the shutdown hook implemented.

This is great.

When do you think this could be merged into the v1 branch?


fix: update imports for latest version of griffe

This PR fixes the adaptor to work with the latest version of griffe, which tweaked where two classes live.

Raised an issue in beartype to check on the error message, in case there's a way to tweak the error messages when dispatch has trouble resolving an annotation
https://github.com/beartype/beartype/issues/245


Unable to see consoles

I've connected my switch (exploit failed the first time, but on the second attempt it works).
I used "consoles" to get connected console, but I only get
switch> consoles

switch>

Are you sure it's connected? Can I see the log?

Here is the Debug log (After first attempt failed)


feat: use context-based tracing

Which problem is this PR solving?

Fixes #777

Short description of the changes

Use context and propagation APIs for all span creation

lgtm, looking forward to discuss about the simplification of the initialisation of the global APIs

@vmarchaud me too. it is becoming quite cumbersome and I would like to have something simpler before we launch beta. I was thinking we would have some function on the tracer provider that would initialize sane defaults (e.g. NodeTracerProvider.initGlobals() would init AsyncHooksScopeManager and HttpTraceContext with the global API). This is just a rough idea though and I need to think more about the various cases we need to solve.

Codecov Report

Merging #816 into master will increase coverage by 1.75%.
The diff coverage is 94.33%.

The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #816      +/-   ##
=========================================
+ Coverage   94.05%   94.4%   +0.34%
=========================================
  Files         245     245
  Lines       10567   10787     +220
  Branches     1029    1024       -5
=========================================
+ Hits         9939   10183     +244
+ Misses        628     604      -24

Impacted Files
Coverage Δ

packages/opentelemetry-tracing/src/config.ts
100% <ø> (ø)
:arrow_up:

packages/opentelemetry-tracing/src/Tracer.ts
97.91% <ø> (+19.48%)
:arrow_up:

packages/opentelemetry-api/src/trace/NoopTracer.ts
100% <ø> (ø)
:arrow_up:

packages/opentelemetry-api/test/api/api.test.ts
96.66% <ø> (ø)
:arrow_up:

...-api/test/noop-implementations/noop-tracer.test.ts
100% <ø> (+46.42%)
:arrow_up:

...telemetry-tracing/test/BasicTracerRegistry.test.ts
100% <100%> (ø)
:arrow_up:

...opentelemetry-node/test/NodeTracerProvider.test.ts
100% <100%> (ø)
:arrow_up:

...kages/opentelemetry-plugin-dns/test/utils/utils.ts
33.33% <0%> (-26.67%)
:arrow_down:

...ages/opentelemetry-plugin-http/test/utils/utils.ts
33.33% <0%> (-26.67%)
:arrow_down:

...kages/opentelemetry-metrics/test/mocks/Exporter.ts
33.33% <0%> (-16.67%)
:arrow_down:

... and 41 more

Codecov Report

Merging #816 into master will increase coverage by 0.34%.
The diff coverage is 100%.

 It's a big change and there will be a lot of follow up work to be done before beta so I don't want it to sit for too long.

@mayurkale22 I believe I've addressed all your concerns now

I think this is good to merge.


Device name clash with Alexa core commands

I have set up HA Bridge and all works well, however I am seeing an issue with naming which I am hoping someone can help with.
I have connected my Harmony Hub and set up a command for favorite channels - e.g. Cbeebies / BBC 1 to send the remote command to the hub and to the TV (e.g. 1, 0, 6, enter)
This works very occasionally, but usually Alexa returns "I have no media skills activated, please set up your media skill in the Alexa app..." or something along those lines.
I'm assuming it works when internet access is restricted or takes too long for Alexa to see the servers, but does anyone know a way to force your device to be the priority?
Thanks

How are the problematic devices exactly configured? (Names, Commands)
Do i assume correct that you try to simulate the channel number input? When it doesn't work, does Alexa always say so or does she simply say "ok" sometimes and the desired action still doesn't happen? If it is the later it could also be a problem with your sequence, maybe you send the button presses to fast or something else..

I'm assuming it works when internet access is restricted or takes too long for Alexa to see the servers, but does anyone know a way to force your device to be the priority?

If there is a problem with the internet Alexa doesn't work at all, because all speech analysis (besides the wake word) is done online on amazon servers. Without a sufficient internet connection she doesn't know what you're saying.
I don't know of a way to give your device priority, you just have to avoid ambiguous names AT ALL COST.
 Which one did you mean?". A question you cant really answer with anything she'll understand. Or if the device name sounds just to similar to a known stock or skill action she simply tries that instead.
If names are unique the only thing you have to have in mind is that the Echo has a timeout for command durations. I think it is 5 seconds.  This can especially be annoying for devices that act as a sort of scene. (I ran into problems with a device that does something like slowly dim ceiling light -> harmony activity -> slowly activate ambient lighting)

Hi @FloFoer
In the example I give, the name/description is:
Cbeebies / Cbeebies, but I have also tried variants (C-Bee-bees / See Bee Bees) etc [nb. See Bee Bees actually work but you have to talk like you have a stutter else it picks up the core command.
When it doesnt work (90% of the time - funnily enough it's worked the few times I've tried it this morning)
I noted the exact phrase she usually says tho - the full phrase she says is
"I couldnt find any enabled Video Skills. Go to the Music, Video and Books section of the Alexa app, enable the video provider you want  and then link your account and complete setup"
It seems ambiguity is the issue here because it clashes with a core command, it's a shame, but there isn't really a natural way around it, and the wife doesnt do unnattural commands ;)

Media skills are not enabled. I found that I had to find names for media things that didn't conflict with reserved words and phrases that Alexa has. Switch on Netflix didn't work, switch movie time on, does work. You arenbattling reserved words, find new phrases e.g. change cbeebies to switch on kids TV perhaps ?

@rodders99 yeah - think that's where I'm leaning towards - it's just that the wife already has the Xbox commands (Xbox Watch Cbeebies) in her head and I'm trying to steer her away from that so I can separate my Xbox and TV!


Fix issue 4335

I think this closes #1234? Not sure if there are more changes I need to make.

Backend checklist

[ ] Formatted my code by running ruff check --select I --fix . && ruff check . && ruff format . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[ ] All tests pass
[ ] Run the backend locally and it works
[ ] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

Web frontend checklist

[ ] Formatted my code with make format
[ ] There are no warnings from make lint
[ ] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[ ] Clicked around my changes running locally and it works
[ ] Checked Desktop, Mobile and Tablet screen sizes

I think this closes #1234?

That's the wrong issue it seems

OK i fixed them


Cannot parse resign

see https://github.com/gcp/leela-zero/issues/306
Resignation was recently turned on and LeelaWatcher crashes on it.

Are you using the latest release?

The latest version of LeelaWatcher should parse the resignation.

Duplicate of #13


README has one tiny problem

In the inline example of README
fontStyle: 'italics'  is not working,  change to  fontStyle: 'italic' will work.

Thank you noticing and thanks to @squiddle for fixing it.


Proposal: TestScope helper

Is there an existing proposal for this?

[X] I have searched the existing proposals

Is your feature request related to a problem?
We have a lot of lines like this:
        logger.info("==============================================");
        logger.info("BEGIN Testing SessionIT queue flush down.");
        logger.info("==============================================");

We might want to standartize this to avoid errors.
Describe the solution you'd like
I propose to make a helper class for this, the usage should look like this:
class ComponentIT {

  public testStress() {

    TestScope scope = new TestScope(this, "testStress");
    // should log:
    // ==================================
    // #BEGIN_TEST ComponentIT testStress
    // ==================================

    scope.step("Open session");
    // should log:
    // Step 1. Open session

    scope.step("Close session");
    // should log:
    // Step 2. Close session

    scope.end();
    // should log:
    // ==========================================
    // #END_TEST ComponentIT testStress - 13.21 s
    // ==========================================

  }

}

Alternatives you considered
No response

@sgalichkin what do you think?
By the way, I don't want to add another indentation level just everywhere with try-with-resources for TestScope. And there is no guaranteed destructor call in Java to help us to auto-close it in the end.

@678098 in the past I was thinking of one of the following option:

In methods annotated with @Before and @After use TestName rule to print the name of executing test
See the following links:
https://junit.org/junit4/javadoc/latest/org/junit/Before.html
https://junit.org/junit4/javadoc/latest/org/junit/After.html
https://github.com/junit-team/junit4/wiki/Rules#testname-rule
Implement a TestWatcher:
https://junit.org/junit4/javadoc/4.12/org/junit/rules/TestWatcher.html

In both cases we do not need to use try-with-resources.
I like the second option because we may implement the class only once (in util namespace) and then just use a final object with @Rule annotation in all test files. Since junit creates test class object for each test, we may include printing spent time calculation in TestWatcher.
On another hand, we still may use TestScope (as a final object field) to print steps


Nice Modal integration with Material UI

When we use Nice Modal with the Material UI library the theming of MUI is not passed down to the Dialog.
tsx
// use case
NiceModal.show(CustomDialog, {usedBeforeActivity: true});

// CustomDialog
const CustomDialog = () => {
  return <Dialog {/* config... */}>/* … */</Dialog>
}

// CustomDialog
const CustomDialog = (props) => {
  return <Dialog {...props} {/* config... */}>/* … */</Dialog>
}

@supnate sorry for the late reply, but Material UI components receive theme from context not props. Here is a sandbox to replicate the issue: https://codesandbox.io/s/mui-theme-not-working-with-nice-modal-j272g1?file=/demo.tsx:808-1029

Running into this issue - is there a solution?


Workspace - Incomplete message appear when add more characters to Workspace "<my workspace"

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to staging.new.expensify.com
Create New Workspace
Click on Settings
Change the workspace name to "<my workspace"
Check the notification message in #admin room history
Navigate back to Settings and add more characters to "<my workspace" ( <my workspace 123)
Check the notification message in #admin room history

Expected Result:
Proper message that contains full names of the Workspace should be displayed, like in Step 5 - Updated the name of this workspace from "Gocemate Workspace" to "<my workspace"
Actual Result:
Incomplete message appears - "Updated the name of this workspace from "" when change the Workspace name adding more characters to "<my workspace" name
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome
[ ] MacOS / Desktop

Version Number: 1.3.56-18
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/591f2450-5fa2-4f9a-a842-565bae9763bf
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013170955ac054b190
Upwork Job ID:<PHONE_NUMBER>651683840
Last Price Increase: 2023-08-29

I think the ideal way to do this is probably to encode the HTML from the back-end.

Just checked this. Agreed it if it comes from the backend it will be better.  We do encode the contents of the comment.

Haven't had a chance to look into the back-end fix yet. Not super urgent, but will get to it eventually.

Haven't got to it yet. Still on the list.

@mananjadhav I'm going to go ahead and remove you since this is a back-end issue.

Still on the list. I'll get to it eventually.

Still on the list. I'll get to it eventually.

Still on the list, but not at all urgent. I'll get to it eventually.

Still on the list, but not at all urgent. I'll get to it eventually.

I'm thinking this bug isn't worth fixing at this time. If we find that users want to name workspaces like this, we can update. Going to close for now, but reopen if you disagree!


Add instructions for test setup/recreating scale-ci jobs on any jenkins

This commit:

Instructions to setup jenkins locally pretty quickly and test/recreate
the scale-jobs on the test instance using scale-ci-watcher.
Adds a link to the scale-ci-properties repo where we maintain the
properties files for the OCP large scale and per sprint test runs.
Adds a scale-ci workflow image.

Will add instructions around creating JJB templates soon ( Separate PR ).

Thanks for the feedback @sjug, made changes to address the comments. PTAL.


Model.OutputPort.setValue(boolean value) fails beacuse of wrong argument type

In this commit we switched from using boolean to Boolean (boxed type) as it enables us to use a 3rd value (null). We use null to indicate if a Node cannot be evaluated because of no or invalid inputs. However we forgot to change Model.OutputPort.setValue(boolean value) to accept the boxed version as parameter. This results in a sneaky error (java.lang.NullPointerException) when a null (an otherwise valid) value is passed as argument. Java tries to coerce Boolean to boolean which then of course fails.
I propose fixing this and all future issues like this by switching to Optional<Boolean> - a more functional pattern - that explicitly expresses the 3rd state. It would also prevent unexpected type coercions.

Have not really heard about Optional<> yet, but sounds reasonable, especially in our case.


RHIDP-4193 Create new RHDH Plugin titles in the docs repo

IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s):
1.3
Issue:
RHIDP-4193 Create new RHDH Plugin titles in the docs repo
Link to docs preview:

Reviews:

[ ] SME: @ mention assignee
[ ] QE: @ mention assignee
[ ] Docs review: @ mention assignee
[ ] Additional review: @mention assignee (by writer)

Additional information:
This PR is just to create new RHDH dynamic plugin titles as part of our product docs restructuring.
This PR will enable us to create Pantheon the new titles.
Each title will be reviewed when content is added.

/cherrypick release-1.3


[WFLY-10520] Transform classes to replace deprecated API method call, with changes from Gail Badner, Guillaume Smet, Martin Simka, Scott Marlow

https://issues.jboss.org/browse/WFLY-10520
https://issues.jboss.org/browse/EAP7-999 (JPA 2.2 tracker)
https://issues.jboss.org/browse/JBEAP-14854 (Hibernate migration documentation)
https://issues.jboss.org/browse/WFLY-10455 WF JPA 2.2 container doc changes.
https://github.com/wildfly/wildfly/pull/11430 (previously closed pr)

Thanks, weird that I lost that.  Will figure out why.

I need to update jpa/hibernate-transformer/pom.xml to reference 14.0.0.Beta2-SNAPSHOT, doing this now.

@simkam @mjurc is this good to go now or do you need to do some more testing?

@scottmarlow JDK10 failures https://ci.wildfly.org/viewLog.html?buildId=115141&buildTypeId=WF_PullRequest_LinuxJdk10

I'll see if I can recreate the jdk10 failure locally.

I'm not exactly sure of the root cause.  The server.log is at

@scottmarlow  I found https://github.com/remondis-it/remap/issues/56 and added a commit to bump the version to 6.2.1. At least VerifyHibernate51CompatibilityPropertyEnabledTransformerTestCase passes with this bump

Retest this please

I am moving the upgrade into https://issues.jboss.org/browse/WFLY-10801 / https://github.com/wildfly/wildfly/pull/11493


Display a warning if preserve static IPs are enabled with pod network mapping

Reference:https://issues.redhat.com/browse/MTV-1503
In case there is no critical error for a plan and in addition, the plan is set to enable the preserve static IPs for the VMs while at least one of the destination network mappings is set to 'Pod Networking' type => then display a warning alert at the head of plan page.
Screenshots

Screencast from 2024-11-13 21-35-45.webm

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.16%. Comparing base (13484d0) to head (545b4b8).
Report is 122 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1387      +/-   ##
==========================================
- Coverage   36.81%   36.16%   -0.65%
==========================================
  Files         158      158
  Lines        2548     2577      +29
  Branches      599      600       +1
==========================================
- Hits          938      932       -6
- Misses       1428     1630     +202
+ Partials      182       15     -167

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

cc: @RichardHoch
Please review the warning message displayed in the screenshot within main comment:
https://github.com/kubev2v/forklift-console-plugin/pull/1387#issue-2656585530

@metalice please review


pypi uses token

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

fixes https://github.com/AgnostiqHQ/covalent-staging/issues/419


callers of task_mgr::spawn: some top-level async blocks were missing tenant/timeline id

Looking at logs from staging and prod, I found there are a bunch of log
lines without tenant / timeline context.
Manully walk through all task_mgr::spawn lines and fix that using the
least amount of work required.
refs https://github.com/neondatabase/neon/issues/4222

(I wouldn’t mind if someone else reruns flaky tests and hits squash&merge)

rerunning...

e2e test fails because we are running out of docker pull limit
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Let's merge this next week 🙈

I'm waiting for e2e build failures to be resolved, see https://neondb.slack.com/archives/C03438W3FLZ/p1684747576440749 to

I've been rerunning this PR for several times but it never passes 🤣

@koivunej 's review in https://github.com/neondatabase/neon/pull/4317#discussion_r1203715636 pointed out that we should be using parent: None + `follows_from.
Quoting him:

For the causal relationships it might be beneficial to start recording Span::follows_from which here would mean ... rather ugly:
-            .instrument(tracing::info_span!("attach", tenant_id=%tenant_id))
+            .instrument({
+                let span = tracing::info_span!(parent: None, "attach", tenant_id=%tenant_id));
+                span.follows_from(Span::current());
+                span
+             }),

I think this problem was discussed in context of some earlier PR adding context to spawns but it got merged before I could comment. This might only be observable from jaeger/otel.
Aah nevermind this already sets up the normal parent child relationship so not needed. I had assumed we wouldn't do parent/child relationships for non-joined spawned but it probably has it's benefits..
tracing_subscriber::fmt() does not do anything for follows_from relationships.
Yeah, changed my above from suggestion to patch, no need to change this now.

Should we hold up this PR and apply these fixes here?
At the very least, parent: None makes sense for most task_mgr::spawn that outlive the caller.

Merged latest main into this branch. I think the remaining changes in here are good enough. We can have another round of task_mgr::spawn audits for parent: None + follows_from` in the future. cc @koivunej in case you get bored ;)

I merged latest main, mostly trivial merge conflicts.
@koivunej  I don't understand your "other lines must go" comments. To me the changes in this PR are simply moving existing lines around.


chore(deps-dev): Update loom requirement from 1.2.3 to 1.3

Summary

Information

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed).
[x] This PR is not a code change (e.g. documentation, README, examples, ...).

Checklist

[x] I have searched the open pull requests for duplicates.
[x] If code changes were made then they have been tested.

lemme do that quickly, and also update other deps while I'm at it

this looks good to me, you?

this looks good to me, you?

Yeah, now I'm going to change the PR title.


Use new handyman.mergeConf method

Can one of the admins verify this patch?

Odd, thought I had fixed this, as 0.3.0 of handyman only has mergeConf...
https://github.com/kenzanlabs/pipeline-handyman/blob/0.3.0/src/index.js#L15
Not sure how this repo would not have been failing the builds?
cc: @csharon
ok to test

Ready to merge, I tested it and is working. I'm trying to find what happened with these names before, really odd.

I changed the name a couple releases ago.  Just wondering how pipeline-validate-js was using 0.3.0 (latest release) but with the deprecated name.

Is there anything else I need to do before this gets merged? Once it's merged, what's the process for getting it released?

The build didn't fail because you only hit the problematic line if you pass in a config object:
  if (options) {
    config = handyman.updateConf(config, options);
  }

and gulpfile.js does not pass one in.
Actually, I don't need to pass in a config object either, so I'm not blocked by this bug.

Ah ha!  Great catch @dloehr .
Thank you for reporting this.  I will release this anyway, as 0.3.1.


Duplicate log record on setting basic config

Package Name: azure-monitor-opentelemetry
Package Version: ^1.6.0
Operating System: Mariner
Python Version: 3.9.7

Describe the bug
I am seeing duplicate logs in AKS for the python application after enabling formatting on the logger that I create for each module. There are two logs for each logging call in the AKS container logs one with default format and one with customized format that I defined.
To Reproduce
Create logger using below code:
configure_azure_monitor(
      enable_live_metrics = True,
      disable_offline_storage = True
  )

def get_logger(name: str, level = logging.INFO):
    logger = logging.getLogger(name)
    logger.setLevel(level)
    logging.basicConfig(
        format="%(asctime)s - %(name)s - %(levelname)s - %(message)s",
    )
    return logger

logger = get_logger(__name__)

logger.info("hello suspicious duplicate")

The other approach I tried was modifying get_logger as below:
console_handler = logging.StreamHandler(sys.stdout)
console_formatter = logging.Formatter("%(asctime)s - %(name)s - %(levelname)s : %(message)s")
console_handler.setFormatter(console_formatter)
logger.addHandler(console_handler)

This also results in duplicate logs
Expected behavior
Only my custom log should get printed

@king-11
Please pass in the name of the Python logger you would like to track telemetry for like in this example. Keep in mind that every logger that is in the same namespace as the name passed in will also be tracked.
i.e., if I use logger_name="azure.app", the loggers with example names azure.app.test, azure.app.webapp and azure.app.function will be tracked but azure.testing will not.

@lzchen passing in the logger_name="anomaly_detection" which is the parent package name also results in duplicate logging. I was just wondering if there is any way to format the log using opentelemetry distro as I think two stream handler are being created here on using the format options I have tried.

adding more details which I recently found the two log records being generated differ in details apart from the message

sdkVersion
customDimensions
operation_Id
client_Browser
cloud_RoleName

ulm_py3.9.19:otel1.25.0:ext1.0.0b27
{"code.filepath":"/usr/lib/python3.9/site-packages/anomaly_detection/handlers/inference_handler.py","code.function":"execute_inference","code.lineno":"105"}
ecd6e2a7c786da27c0e3097b37d8c6df
Other
impact-service

py3.9.19:oc0.11.4:ext1.1.13
{"process":"MainProcess","module":"inference_handler","fileName":"/usr/lib/python3.9/site-packages/anomaly_detection/handlers/inference_handler.py","lineNumber":"105","level":"INFO"}
00000000000000000000000000000000
Python Requests 2.32
main.py

cloud role name is incorrect for the later sdk which is the duplicate record being generated

@king-11
The second sdk is for the opencensus python sdk which will be deprecated in September.

@lzchen so it comes along with azure monitor distro is it? Because I remember removing it when migrating to open telemetry.

@king-11
It does not come with the distro. Opencensus should be completely separate from Open Telemetry. Please make sure you are not using the old opencensus sdk and that you are not querying old data from before your testing. Also please try out your app outside of an AKS environment to see if the issue persists.

@king-11
opencensus packing existing but not being used in your code should not cause export of logs from the opencensus azure monitor sdk. Please make sure that you are not using it anywhere in your code. I would also uninstall the package as it is deprecated.

Closing this issue thanks for help @Izchen one of our dependencies was pulling in opencensus and using it for creating an exporter.


Change hostname and run multiple instances

Copied as requested

Hi,
Fantastic use of Docker on this one - really impressed!
Would it be possible to setup a new instance at something other than wocker.dev e.g. mysite.dev?
Thanks
John

The URL of WordPress is saved in the Docker image. Therefore, to setup another one is not very easy.
If you are familiar with Docker and Dockerfile, it's possible.
Here's the repository of the Dockerfile of Wocker: https://github.com/wckr/wocker-dockerfile/tree/master/wheezy.

Modify "wocker.dev" both in the Vagrantfile and Dockerfile.
Build your own Docker image from the Dockerfile you modified.
Use your own Docker image to $ wocker run.

e.g.
$ wocker run --name mysite jcpeden/mysite

In this case, jcpeden/mysite was your own Docker image.


Add AllowThousands flag to all integer type TryParse calls in DefaultConverter

Description

Fixes #4945
By default int.TryParse (and others) do not accept the thousands separator where float/double do accept them, I think we should have parity between them.
How Has This Been Tested?

Manually
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

@just-the-benno I've added the requested tests. Testing the invariant culture (comma separator) and German culture (period separator)

@henon
I think this PR is ready to merge.  What are your thoughts?

Thank you @valincius for your contribution and @just-the-benno for the guidance!


Table classes generated with "package package" on first line - jack/java8/gradle2.2

DBFlow Version: 4.0.0-beta1
Issue Kind (Bug, Question, Feature): Bug
Description:
Generated table code seems to be including the word package twice e.g.
package package com.project.model;
Forgive me if this is just a configuration error, but I wondered if it's something to do with the setup which is:

gradle:2.2.2
jack compiler enabled for Java 8 support

My build file looks like this:
    compileSdkVersion 25
    buildToolsVersion "24.0.2"
    defaultConfig {
        applicationId "com.project"
        minSdkVersion 19
        targetSdkVersion 24
        versionCode 1
        versionName "0.1"
        jackOptions {
            enabled true
        }
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

   ...

  dependencies {
    ...
    annotationProcessor "com.github.Raizlabs.DBFlow:dbflow-processor:4.0.0-beta1"
    compile "com.github.Raizlabs.DBFlow:dbflow-core:4.0.0-beta1"
    compile "com.github.Raizlabs.DBFlow:dbflow:4.0.0-beta1"
  }

I'm also using Lombok. I've tried cleaning etc, but it always seems to include the word "package" twice.

Having the same issue. Also on 4.0.0-beta1.

Screenshot:

Jack compiler is not tested/supported yet. I am going to look into it to see what the issue is. Most likely a JavaPoet issue.

Do you have an update on this? I'm starting a new project and would like to use Jack + DBFlow.

@Glurt I would recommend you use the normal tool chain with retrolambda over jack. Still a good deal of unknowns not to mention it being a decent bit slower than the normal tool chain.

Guys, about this issue, we have news?

fixed. in develop now.

it was the difference of manager.elements.getPackageOf(element)?.qualifiedName?.toString()?: "" and manager.elements.getPackageOf(element).toString(). The second one prepended a "package" to the class file for some odd reason in Jack, while normal APT doesn't do that.


Add Execs, coordinator and editorial to project dictionary before re-importing

Created a new list for support team - support_title.txt
Next will need to import and merge both into one dataframe.

Change the new list to a json file and concat it to the existing DataFrame


Missing python wrapping of ctkCheckableHeaderView

While using Slicer I noticed that the python wrapping for the ctkCheckableHeaderView was missing.
There was ctkCheckableHeaderViewEventPlayer() and ctkCheckableHeaderViewEventTranslator(), but the main widget was missing.

Could you please send a pull request that fixes the problem?

The problem occurs because ctkCheckableHeaderView constructor does not have the desired signature (as specified by ctkWrapPythonQt.py).
Please advise about the desirable solution to this. Here are the options that I can think of:

Adding another constructor to ctkCheckableHeaderView with default parameters and correct order needed for python wrapping.
Changing ctkWrapPythonQt.py itself so that in future other cases might be handled correctly. (Although this seems to be a bit more difficult)

Adding a constructor that does not require any input arguments sounds like a simple solution.

I encountered the same problem.
@lassoan  It is a little problematic to add a constructor that doesn't require any input argument as ctkCheckableHeaderView(QWidget *parent = nullptr) inherits from QHeaderView(Qt::Orientation orientation, QWidget *parent = nullptr) and QHeaderView orientation must be set while one initializes the object (in constructor) as it doesn't have something like QHeaderView::setOrientation(Qt::Orientation orientation).
I solved this by creating two classes (one for horizontal header and another for vertical by analogy with QHBoxLayout and QVBoxLayout) that inherit from ctkCheckableHeaderView:

ctkCheckableHHeaderView(QWidget *parent = nullptr) : QHeaderView(Qt::Orientation::Horizontal, parent)
ctkCheckableVHeaderView(QWidget *parent = nullptr) : QHeaderView(Qt::Orientation::Vertical, parent)

This solution would mean that from C++ one is free to use any of 3 ctk header views while in python there are only 2 classes would be available.
Also there are at least two methods that ctkCheckableHeaderView adds to public but not to public slots (thus they are unavailable in python):

Qt::CheckState checkState(int section)const;
bool checkState(int section,Qt::CheckState& checkState )const;
and probably:
ctkCheckableModelHelper* checkableModelHelper()const; (I don't know what it is yet)

I think we should move them to public slots section
If you agree or have some sugestions I could make a PR

Creating the extra classes sounds like a good solution to the constructor issue.
The other two you listed do look like they should be slots, but ctkCheckableModelHelper* checkableModelHelper()const; may be better as either a Q_PROPERTY or just a method decorated with Q_INVOKABLE so it will be python wrapped.

Do not create new classes if you just want to a make additional constructors accessible from Python! Just add the appropriate decorator methods. There are several examples for this in CTK.
Do not export checkableModelHelper, as it sounds like an internal helper class.
To make simple properties (int, string, string list, enum,...) accessible from Python, it is preferable to declare them as properties as @pieper suggested above.

Today I have achieved some success in understanding PythonQt decorator's staff (mostly from this article) and I think tomorrow I will try to implement it in ctkCheckableHeaderView PR

Thanks for posting the link to that article, somehow I never saw it before (wish I'd read it years ago!).

Closed by fa1732f6845d90c2c1076147ccce3ca2920dcc53.


Update CodeceptJS version on docker hub

What are you trying to achieve?
I want to pull CodeceptJS 3.XX from docker hub by using docker pull codeception/codeceptjs:3.0.0
What do you get instead?
manifest for codeception/codeceptjs:3.0.0 not found
The latest version of CodeceptJS on https://hub.docker.com/r/codeception/codeceptjs is 2.6.4.
Details

CodeceptJS version: 3.0.0
NodeJS Version: 13.8.0
Operating System: Windows

same issue here! now going back to 2.6.4 :|

Same issue here! Pump!

Fixed in 3.0.5 https://hub.docker.com/r/codeceptjs/codeceptjs


option to abort if import library has an exception

In my opinion I would much rather robot aborts immediately when an import can't be found instead of trying to continue and getting a confusing "keyword could not be found" later.

Have you tested --exitonerror option?

Thats exactly what I want, thankyou.

This option is documented very vaguely, it will exit running if anything logs as error, ie robot.api.logger.error.
To anyone that finds this, you can use BuiltIn()._context.fail(msg) to report a failure instead of an error.

logger.error() signals that an error has occurred. You can use logger.warn() if that's a problem. Anything starting with an underscore is at least somewhat private and may change in the future.

I need to be able to log multiple failures within a keyword that's implemented in python, and BuiltIn.fail will exit the keyword immediately. see #3706


Action.pop() in drawer side menu is not working

when i'm Login use  Actions.sideMenu() go to Drawer Side Menu
But I can't Logout by Actions.pop() when I click in Drawer side menu
for go to login
I need to help
Thank you
This is my route stack
<Router hideNavBar={true}>
   <Scene key='root' >
       <Scene key="login" component={LoginPage} connectLogin={connectLogin}  initial={true}  />
           <Scene key='sideMenu' component={NavigationDrawer}  open={false}  >
             <Scene key="main" >
                <Scene key="shop" component={Shopmain} />
                <Scene key="shopdetail" component={ShopDetail}  />
                <Scene key="empty" component={EmptyView}  />
             </Scene>
          </Scene>
    </Scene>
 </Router>

My package.json

react-native-router-flux v^3.35.0
react-native v0.33.0
react-native-drawer v^2.3.0

I have this problem too.Did you solve this?

i have the same problem


CB-14570 New endpoint on FreeIPA service to trigger CCM upgrade flow

Add new operation PUT /v1/freeipa/internal/upgrade_ccm (nickname internalUpgradeCcmByEnvironmentV1) to FreeIpaV1Endpoint. This is an internal-only endpoint that triggers the CCM upgrade workflow for the FreeIPA cluster associated with a given environment. The stack must be AVAILABLE for the invocation to succeed.

The underlying FreeIpaUpgradeCcmService is only a skeleton; the actual flow trigger and stack status update will be added later (see CB-14571).

Testing:

UT.
freeipa Swagger UI in local CB.

Holding off with merging in order to clarify if the authz approach here is indeed appropriate.

who will be the caller of this endpoint? the endpoint looks good from authz point of view, although we cannot tell for sure until it is not clear what would be the process in this case (for example UI cannot call endpoint afaik, so the caller is important to decide the authz of the endpoint)

caller is Environment Service
On Mon, 8 Nov 2021 at 09:46, Adam Horvath @.***> wrote:

who will be the caller of this endpoint? the endpoint looks good from
authz point of view, although we cannot tell for sure until it is not clear
what would be the process in this case (for example UI cannot call endpoint
afaik, so the caller is important to decide the authz of the endpoint)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/hortonworks/cloudbreak/pull/11722#issuecomment-962930611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWG3TZTRYNTK2EDFBPE3J3UK6E5PANCNFSM5HRIEPKA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Denes Berger | Staff Software Engineer
t. +36 (70) 330 2910 <+36+70+330+2910>
cloudera.com https://www.cloudera.com/
[image: Cloudera] https://www.cloudera.com/
[image: Cloudera on Twitter] https://twitter.com/cloudera [image:
Cloudera on Facebook] https://www.facebook.com/cloudera [image: Cloudera
on LinkedIn] https://www.linkedin.com/company/cloudera
https://www.cloudera.com/

is there any reason for not merging this? if yes please convert it to draft


Log sales to and from vendors

Adds new "Group trash items" toggle in the optionso for use with the vendoring view.

Progress update:

Selling items to the vendor works and detects the sales accurately, even with addon automation.
Buying works, when not using addons to automate the process.

Status update: All features complete and reliable, even when subjected to addon automation.


Unable to customize favicon

Just to say... this is an Open Source project I really admire; thank you so much for your time in building, releasing, and open sourcing this project.

Describe the bug
Currently the favicon of any status page cannot be changed and defaults to:

Expected behaviour / proposed solution
A public or static folder option to deploy files that overwrite default files. In here you could place a favicon.ico file that overwrites the default.

👍🏻

Have you tried this? https://upptime.js.org/docs/configuration/#custom-favicons
Or is the use case more general-purpose? I think we need to document this better, but AFAIK the assets directory will serve static files: https://upptime.js.org/docs/configuration/#theme


Should the ocean grid of HadGEM3 and UKESM1 models be eORCA1 instead of ORCA ?

@matthew-mizielinski @durack1 I have just talked to my local ORCA specialist (@oliviermarti) and read #457, because I was wondering why UK Academic Community PMIP4 models stated Ocean grid: 360×292 (ORCA1) x L75 and why the CV for the same models say ORCA1 [...] 360 x 330 longitude/latitude;
Olivier told me that if you mention a 360 x 330 grid, you should then use the eORCA1 grid name instead of ORCA1 . So maybe this should be corrected for the appropriate UK models
And the additional question is: will the UKESM1-0-LL and HadGEM3-GC31-LL used for PMIP4 use 360x292 or 360x330 ?

@durack1, The following code should make the required changes.
models = [
    'HadGEM3-GC31-HH', 'HadGEM3-GC31-HM', 'HadGEM3-GC31-LL',
    'HadGEM3-GC31-LM', 'HadGEM3-GC31-MH', 'HadGEM3-GC31-MM',
    'UKESM1-0-LL', 'UKESM1-0-MMh']

for model_source_id in models:
     source_id[model_source_id]['model_component']['ocean']['description'] = \
         source_id[model_source_id]['model_component']['ocean']['description'].replace('ORCA', 'eORCA')
     source_id[model_source_id]['model_component']['seaIce']['description'] = \
         source_id[model_source_id]['model_component']['seaIce']['description'].replace('ORCA', 'eORCA')

@matthew-mizielinski thanks for the code snippets, makes my job a lot easier! Take a peek at CMIP6_source_id.html and let me know if any further tweaks are required.

Hi Matthew
What is the significance of the eORCA – I assume this isn’t just a resolution issue as we are defining ORCA025 and ORCA1 for ES-DOC.  I’ll need to get these realigned so that the file headers are correct.  Do you have a link to some additional information on this, or somebody in the NEMO team that can explain it to me.
Mark
From: Matthew Mizielinski<EMAIL_ADDRESS>Sent: 05 April 2018 10:49
To: WCRP-CMIP/CMIP6_CVs
Cc: Elkington, Mark; Mention
Subject: Re: [WCRP-CMIP/CMIP6_CVs] Should the ocean grid of HadGEM3 and UKESM1 models be eORCA1 instead of ORCA ? (#494)
@jypeterhttps://github.com/jypeter, you are probably correct on this issue it hadn't occurred to me that the extended ORCA grid should be referred to differently. I suspect you are correct in that we should replace ORCA with eORCA in all of the HadGEM3 and UKESM1 descriptions. I'll confirm this with our ocean modelling teams and get back to you asap.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/WCRP-CMIP/CMIP6_CVs/issues/494#issuecomment-378880906, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFTIJySF9jZziA-Jl1Ti9aXgj9dqgTI6ks5tleiBgaJpZM4TFWDd.

ORCA grids have a southern limit at about 78°S. eORCA grids are identical to ORCA grids, except that they add points under the Antartic ice shelves up to about 86°S.
I don't know about any official documentation about that. Could NEMO system team provide a reference ?
Olivier


Fix odo project delete output to clearly indicate the project name

/kind bug
What versions of software are you using?

Be logged in or logged out of a cluster (does not matter).
odo project delete non-existent-project

Actual behavior
➜ odo project delete unknown
 ✗  The project unknown does not exist. Please check the list of projects using `odo project list`

Expected behavior
➜ odo project delete unknown
 ✗  The project 'unknown' does not exist. Please check the list of projects using `odo project list`

Any logs, error output, etc?

/close
Fixed by #5149


[9.4.x] ISPN-10463 Server uses disabled features

https://issues.jboss.org/browse/ISPN-10463
Use the infinispan-commons classloader to look up the features
properties file.

ExecutionAuthorizationTest hanging in build 2 was unrelated.

Merged, thanks!


Release

Thank you for contributing react-native-themed-styled-system package 🤗
Type of change
Please delete options that are not relevant.

[x] Release (merge into main branch)

:tada: This PR is included in version 2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Swap to use UTF-8 for resource hints instead of ASCII

Allows for a tighter specification as to the encoding of the bytes

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lostluck @damccorm

R: @tvalentyn

I think we used ASCII due to v1beta3  JSON API limitations of what can be stored in a string inside a struct.
This may break the translation in Dataflow backend while v1beta3 is still used by Dataflow internals.


Support newer version of knex

Closed in favor of #100 @acofer Thank you for your contribution :+1:


JSON parser doesn't parse all inputstream if a stream contain multiple inputStream.

Overview.
The following configuration gets JSON data using HTTP results
It outputs nine entries, But the current parser outputs three entries only.
in:
  type: http
  url: http://express.heartrails.com/api/json
  params:
    - {name: method, value: getStations}
    - {name: x, value: 135.0}
    - {name: y, value: "35"}
  cursor:
    request_parameter_cursor_name: name
    response_parameter_cursor_json_path: '$.response.station[0].next'
  parser:
    type: json
    root: '/response/station'
    flatten_json_array: true

out: {type: stdout}

Envnironment

Embulk: v0.11.0
embulk-input-http 16a4adf94e60caddc0ce590e16332a7111043a4b forked version.
embulk-parser-json: 0.4.0

The reason.
The results are separated by multiple HTTP responses. Those results are independent JSON objects like multiple files.
However, It constructs a single FileInputInputStream which contains multiple InputStreams.
embulk-parser-json just parses the first inputStream, as a result, It outputs three entires only.
It is the same issue embulk-parser-jsonpath

Most plugin's TransactionalFileInput has only one file (input stream), but the embulk specifications also supports  multiple files (input streams) .
In the latter case, only the first file(input stream) is read in the current implementation.

* Connected to express.heartrails.com (<IP_ADDRESS>) port 80 (#0)
> GET /api/json?method=getStations&x=135.0&y=35 HTTP/1.1
> Host: express.heartrails.com
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Thu, 24 Aug 2023 00:38:05 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 572
< Connection: keep-alive
< Server: nginx
< Expires: Thu, 01 Dec 1994 16:00:00 GMT
< Pragma: no-cache
< X-Runtime: 1
< ETag: "952bd603b2f475e0e56ae31927adb679"
< Cache-Control: private, max-age=0, must-revalidate
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET, OPTIONS
< Access-Control-Allow-Headers: *
<
{"response":{"station":[{"name":"日本へそ公園","prefecture":"兵庫県","line":"JR加古川線","x":134.997633,"y":35.002069,"postal":"6770039","distance":"320m","prev":"比延","next":"黒田庄"},{"name":"比延","prefecture":"兵庫県","line":"JR加古川線","x":134.995733,"y":34.988773,"postal":"6770033","distance":"1310m","prev":"新西脇","next":"日本へそ公園"},{"name":"黒田庄","prefecture":"兵庫県","line":"JR加古川線","x":134.992522,"y":35.022689,"postal":"6790313","distance":"2620m","prev":"日本へそ公園","next":"本黒田"}]}}
* Connection #0 to host express.heartrails.com left intact

{
  "response": {
    "station": [
      {
        "name": "日本へそ公園",
        "prefecture": "兵庫県",
        "line": "JR加古川線",
        "x": 134.997633,
        "y": 35.002069,
        "postal": "6770039",
        "distance": "320m",
        "prev": "比延",
        "next": "黒田庄"
      },
      {
        "name": "比延",
        "prefecture": "兵庫県",
        "line": "JR加古川線",
        "x": 134.995733,
        "y": 34.988773,
        "postal": "6770033",
        "distance": "1310m",
        "prev": "新西脇",
        "next": "日本へそ公園"
      },
      {
        "name": "黒田庄",
        "prefecture": "兵庫県",
        "line": "JR加古川線",
        "x": 134.992522,
        "y": 35.022689,
        "postal": "6790313",
        "distance": "2620m",
        "prev": "日本へそ公園",
        "next": "本黒田"
      }
    ]
  }
}

% curl -Lv 'http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E9%BB%92%E7%94%B0%E5%BA%84'
*   Trying <IP_ADDRESS>:80...
* Connected to express.heartrails.com (<IP_ADDRESS>) port 80 (#0)
> GET /api/json?method=getStations&x=135.0&y=35&name=%E9%BB%92%E7%94%B0%E5%BA%84 HTTP/1.1
> Host: express.heartrails.com
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Thu, 24 Aug 2023 00:39:18 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 192
< Connection: keep-alive
< Server: nginx
< Expires: Thu, 01 Dec 1994 16:00:00 GMT
< Pragma: no-cache
< X-Runtime: 1
< ETag: "3be1f77accfba140aa48670d77eb6e97"
< Cache-Control: private, max-age=0, must-revalidate
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET, OPTIONS
< Access-Control-Allow-Headers: *
<
{"response":{"station":[{"name":"黒田庄","prefecture":"兵庫県","line":"JR加古川線","x":134.992522,"y":35.022689,"postal":"6790313","prev":"日本へそ公園","next":"本黒田"}]}}
* Connection #0 to host express.heartrails.com left intact

{
  "response": {
    "station": [
      {
        "name": "黒田庄",
        "prefecture": "兵庫県",
        "line": "JR加古川線",
        "x": 134.992522,
        "y": 35.022689,
        "postal": "6790313",
        "prev": "日本へそ公園",
        "next": "本黒田"
      }
    ]
  }
}

....
Example reproduce outputs
2023-08-24 18:00:12.915 +0900 [INFO] (main): m2_repo is set as a sub directory of embulk_home: /Users/user/.embulk/lib/m2/repository
2023-08-24 18:00:12.918 +0900 [INFO] (main): gem_home is set as a sub directory of embulk_home: /Users/user/.embulk/lib/gems
2023-08-24 18:00:12.918 +0900 [INFO] (main): gem_path is set empty.
2023-08-24 18:00:12.918 +0900 [DEBUG] (main): Embulk system property "default_guess_plugin" is set to: "gzip,bzip2,json,csv"
2023-08-24 18:00:13.049 +0900 [INFO] (main): Started Embulk v0.11.0
2023-08-24 18:00:14.752 +0900 [INFO] (0001:transaction): Gem's home and path are set by system configs "gem_home": "/Users/user/.embulk/lib/gems", "gem_path": ""
2023-08-24 18:00:15.364 +0900 [INFO] (0001:transaction): Loaded JRuby runtime <IP_ADDRESS>
2023-08-24 18:00:15.395 +0900 [INFO] (0001:transaction): Loaded plugin embulk/input/http from a load path
2023-08-24 18:00:15.487 +0900 [INFO] (0001:transaction): Loaded plugin embulk-output-stdout
2023-08-24 18:00:15.538 +0900 [INFO] (0001:transaction): Loaded plugin embulk-parser-json
2023-08-24 18:00:15.687 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2023-08-24 18:00:15.724 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2023-08-24 18:00:15.860 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35"
2023-08-24 18:00:15.985 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E9%BB%92%E7%94%B0%E5%BA%84"
2023-08-24 18:00:16.007 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E6%9C%AC%E9%BB%92%E7%94%B0"
2023-08-24 18:00:16.029 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E8%88%B9%E7%94%BA%E5%8F%A3"
2023-08-24 18:00:16.050 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E4%B9%85%E4%B8%8B%E6%9D%91"
2023-08-24 18:00:16.085 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35&name=%E8%B0%B7%E5%B7%9D"
{"prefecture":"兵庫県","distance":"320m","line":"JR加古川線","next":"黒田庄","prev":"比延","x":134.997633,"y":35.002069,"postal":"6770039","name":"日本へそ公園"}
{"prefecture":"兵庫県","distance":"1310m","line":"JR加古川線","next":"日本へそ公園","prev":"新西脇","x":134.995733,"y":34.988773,"postal":"6770033","name":"比延"}
{"prefecture":"兵庫県","distance":"2620m","line":"JR加古川線","next":"本黒田","prev":"日本へそ公園","x":134.992522,"y":35.022689,"postal":"6790313","name":"黒田庄"}
2023-08-24 18:00:16.162 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2023-08-24 18:00:16.167 +0900 [INFO] (main): Committed.
2023-08-24 18:00:16.167 +0900 [INFO] (main): Next config diff: {"in":{},"out":{}}

Hmm, does the same happen in older versions?

Forked version of the embulk-input-http by trocco use InputStreamFileInput.IteratorProvider
(As far as I know, there is no input plugin that uses InputStreamFileInput.IteratorProvider except this plugin)
The original embulk-input-http doesn't use it. So the input plugin requested just one HTTP GET.

embulk-input-httpd: 0.25.0 (rubygems version)
embulk-parser-jsonpath: 0.4.0

2023-08-25 10:21:30.748 +0900: Embulk v0.9.25
2023-08-25 10:21:31.645 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2023-08-25 10:21:33.555 +0900 [INFO] (main): Gem's home and path are set by default: "/home/user/.embulk/lib/gems"
2023-08-25 10:21:34.286 +0900 [INFO] (main): Started Embulk v0.9.25
2023-08-25 10:21:34.432 +0900 [INFO] (0001:transaction): Loaded plugin embulk-input-http (0.25.0)
2023-08-25 10:21:34.556 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2023-08-25 10:21:34.568 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2023-08-25 10:21:34.615 +0900 [INFO] (0015:task-0000): GET "http://express.heartrails.com/api/json?method=getStations&x=135.0&y=35"
{"prefecture":"兵庫県","distance":"320m","line":"JR加古川線","next":"黒田庄","prev":"比延","x":134.997633,"y":35.002069,"postal":"6770039","name":"日本へそ公園"}
{"prefecture":"兵庫県","distance":"1310m","line":"JR加古川線","next":"日本へそ公園","prev":"新西脇","x":134.995733,"y":34.988773,"postal":"6770033","name":"比延"}
{"prefecture":"兵庫県","distance":"2620m","line":"JR加古川線","next":"本黒田","prev":"日本へそ公園","x":134.992522,"y":35.022689,"postal":"6790313","name":"黒田庄"}
2023-08-25 10:21:34.936 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2023-08-25 10:21:34.941 +0900 [INFO] (main): Committed.
2023-08-25 10:21:34.941 +0900 [INFO] (main): Next config diff: {"in":{},"out":{}}


Create sudoko.py

@chaudharyaditya1 please star the repo if u think this helped u for hacktoberfest :)


Switch to use CommonMark instead of MarkdownDeep

The main reason to do this is that MarkdownDeep.NET does not provide a nuget package that has a .NET45 assembly (only a NET35). By switching to use CommonMark, we can then reference the HTML reporter from project.json, allowing us to transition the service to ASP.NET 5.
This change also updates everything to use NuGet 3 - makes reasoning about dependencies easier.

LGTM

Just a general comment as well about CommonMark.NET - it provides an awesome way to access the AST created during the conversion so we can hook in and change nodes: https://github.com/Knagis/CommonMark.NET/wiki

LGTM. :)


Use placeholder in textarea example

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea#attr-placeholder
Closes #5

Sample result after the change -


Google Api Error: forbidden: Cannot update a published APK.

In my flutter project when i try to upload new apk to play store i get this error
....
....
....
[01:57:18]: Preparing apk at path '../build/app/outputs/apk/release/app-release.apk' for upload...
+-------------------------------------+----------------+
|                     Lane Context                     |
+-------------------------------------+----------------+
| DEFAULT_PLATFORM                    | android        |
| PLATFORM_NAME                       | android        |
| LANE_NAME                           | android deploy |
| GRADLE_ALL_APK_OUTPUT_PATHS         | []             |
| GRADLE_ALL_AAB_OUTPUT_PATHS         | []             |
| GRADLE_ALL_OUTPUT_JSON_OUTPUT_PATHS | []             |
| GRADLE_ALL_MAPPING_TXT_OUTPUT_PATHS | []             |
+-------------------------------------+----------------+
[01:58:43]: Google Api Error: forbidden: Cannot update a published APK. - Cannot update a published APK.

+------+-----------------------+-------------+
|              fastlane summary              |
+------+-----------------------+-------------+
| Step | Action                | Time (in s) |
+------+-----------------------+-------------+
| 1    | default_platform      | 0           |
| 2    | clean assembleRelease | 50          |
| 💥   | upload_to_play_store  | 87          |
+------+-----------------------+-------------+

[01:58:43]: fastlane finished with errors

[!] Google Api Error: forbidden: Cannot update a published APK. - Cannot update a published APK.

I'm seeing the same issue. Any luck?

@dandre-hound Add new release and upload apk manually for the first time. After that fastlane works.
Still, I am not sure is this the right way.

I have the same problem. Any solution?

@lorenamelor I was unknowingly uploading an apk with a build number that had already been published. I just incremented the version code (using fastlane-plugin-versioning_android) and the error went away. Hopefully this helps you!

Thanks for the answer @dandre-hound , but I didn't understand the problem.
What build number do you refer to? Can you contextualize me a little more, please?

Sure. By the way I actually meant version code, not build number. Your version code should be defined in app/build.gradle as versionCode. Try incrementing this number by 1 and uploading again. I had already uploaded an android apk file (the bundled application) with a version code of 716 when I ran into this error. Once I set the versionCode to 717, I was able to upload successfully. I only brought up fastlane-plugin-versioning_android because it automatically increments this number for you whenever you run fastlane. Does this help?

Yes, I understood, thank you so much! Everything went well now.


google_compute_engine: Add Fedora support to compat module

For all intents and purposes, we can pretend Fedora works like Enterprise Linux 7 systems, such as Red Hat Enterprise Linux and CentOS.
Signed-off-by: Neal Gompa<EMAIL_ADDRESS>

Please update your pull request to diff against the development branch (which also fix your linter issues).

@illfelder I've rebased and retargeted accordingly.

@illfelder test case added


Merchant Account Information "02" to "25" should be a primitive data objects

Hi,
I have been provided some reserved merchant account information within  the range of fields "02" to "25". The object provided is a primitive data object and not in a template. It seems in your code you are assuming "02" to "51" as Merchant Account Information Templates. However "02" to "25" are referred to in the EMVCO spec as primitive data objects.
Happy to help contribute in code. However this is an interesting structural change as "02" to "51" are all Merchant Account Information but since some return primitives and some return templates there would need to be some separation of gets, sets and adds.
Maybe a getMerchantAccountInformation() for "02" to "25" and a getMerchantAccountInformationTemplates() for "26" to "51"

Hi,
Thanks for the contribution, your observation makes total sense.
I will mark it as a bug and follow through with the fix.
Any other point of improvement or problem, let me know.
Thanks,

Hi @waggyza,
I used the same approach as the previous one, adding this segregation by MerchantAcountInformation Reserverd and ReserverdAdditional, in order to maintain a better compatibility with what already exists.
In the example, this is explicit. Can evaluate.
I await your suggestions.
Thanks,

Thanks for the fast turn around @mvallim
Its working as expected.


Added example configuration for syslog handler

Changed the logging.yml to include example configuration for syslog handler.  Also included configuration example for class I wrote to override the built-in syslog handler to work around issue where long log entries get dropped.

thanks. can you add information about syslog logging to the container guide and let Jamie + CEI + ops know. This should be tested in a larger setting.


Implement product identifier using dxp-components.

What is the motivation for adding/enhancing this feature?

Add a product identifier card in settings so that the user can change the identifier of the products displayed in app as per his/her requirement.
What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

Here is the PR for this - https://github.com/hotwax/fulfillment-pwa/pull/273/files