ValueError: could not convert string to float: Close

hello, don't know if anyone can help me, i keep receiving this Value error message while entering the following syntax:
price_handler = IQFeedIntradayCsvBarPriceHandler(
csv_dir, events_queue, tickers, start_date=start_date
)
After that i tried to modify the source code of qstrader, iq_feed_intraday_csv_bar.py making conversion of Close data of type string to float, but doesn't work at all.  Many thanks!

can you provide the full trace back please?

hi Thanks a lot for your reply!  here is the full version of the track back.  I can provide you with the data, model trained and other related source files if needed :-))
ValueError                            Traceback (most recent call last)
 in ()
83     tickers = ["AREX"]
84     filename = None
---> 85     run(config, testing, tickers, filename)
 in run(config, testing, tickers, filename)
31     end_date = datetime.datetime(2014, 3, 11)
32     price_handler = IQFeedIntradayCsvBarPriceHandler(
---> 33         csv_dir, events_queue, tickers, start_date=start_date
34     )
35
/home/fanglei/venv/qstraderp3/lib/python3.5/site-packages/qstrader/price_handler/iq_feed_intraday_csv_bar.py in init(self, csv_dir, events_queue, init_tickers, start_date, end_date)
33         if init_tickers is not None:
34             for ticker in init_tickers:
---> 35                 self.subscribe_ticker(ticker)
36         self.start_date = start_date
37         self.end_date = end_date
/home/fanglei/venv/qstraderp3/lib/python3.5/site-packages/qstrader/price_handler/iq_feed_intraday_csv_bar.py in subscribe_ticker(self, ticker)
92                 row0 = dft.iloc[0]
93
---> 94                 close = PriceParser.parse(row0["Close"])
95
96                 ticker_prices = {
/home/fanglei/venv/qstraderp3/lib/python3.5/site-packages/multipledispatch/dispatcher.py in call(self, *args, **kwargs)
208             self._cache[types] = func
209         try:
--> 210             return func(*args, **kwargs)
211
212         except MDNotImplementedError:
/home/fanglei/venv/qstraderp3/lib/python3.5/site-packages/qstrader/price_parser.py in parse(x)
37     @dispatch(str)
38     def parse(x):  # flake8: noqa
---> 39         return int(float(x) * PriceParser.PRICE_MULTIPLIER)
40
41     @staticmethod
ValueError: could not convert string to float: 'Close'

To make it easier to read please format your message.
This is easy

Aren't you just passing a string to the parser somewhere?


Error building the app

Sometimes (not sure in what cases exactly) I get the error building the app
Asset: 'Assets/Bugfender/Resources/BugfenderIcon.png'
Asset name: BugfenderIcon
(You are probably referencing internal Unity data in your build.)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

I had it on iOS and Android. Reimporting BugfenderIcon.png helpes, but after this issue may appear again.
Unity 2022.3.10f1
For editor resources better use EditorDefaultResources instead of Resources folder because all Resources folders are embedded to the build and we don't need your editor assets there for sure.

Hi Roman, this seems like an issue with the build process. Have you tried Unity support?

Closing due to inactivity


V3 monitor - should be able to ignore packages that are known to be broken

Some packages can't be fixed. Example: https://github.com/NuGet/NuGetGallery/issues/4199

Issue moved to NuGet/Engineering #601 via ZenHub


fix: Increase file size limit for templates

Description
Fixes #14852
Forking a template was failing due to file size limit. This PR increases the file size limit to 4 MB.
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manually

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=6ffb456

/ok-to-test sha=dff3cd9

/ok-to-test sha=2aced8b

/ok-to-test sha=ed09078


Chrome vs. Safari compatibility for flex-wrap:wrap

Here's one of the test cases. Note that there is no width.

When I run this on chrome, the total width ends up being 30px. When I run it in Safari, it ends up occupying whatever width is available (the document.body width).
When I run the layout algorithm, the total width ends up being 60. That is also what the test case ensures:
https://github.com/facebook/css-layout/blob/1f300a58fb263685ffab17b66665a79f5acd09f4/tests/CSSLayoutFlexWrapTest.cpp#L79
Which one is correct?

There is a comment in the top of this file describing this problem.

Ah, sorry I missed that.


Allows pacifists to throw Items with DamageOnLand

About the PR

Allows pacifists to throw Items with DamageOnLand
Why / Balance

It only hurts the item, not other things. Its for stuff like breaking the spear or bola when you miss.
Technical details

Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: Pacifists can throw bolas.

I think the reason DamageOnLand is blocked is throwing beakers with chemicals inside, clustersoap, and anything made out of glass that turns into a glass shard when thrown, like bottles. We could alternatively make a new component we specificly add to things pacifists should not be able to throw for more precise control.

Wait... what is this allowing pacifists to throw? Plates?
Bola can't be thrown because it blocks the ensuring component too... was this tested?

Wait... what is this allowing pacifists to throw? Plates?

Plates, beakers, bottles, bowls, lights, floor tiles (which deal throwing damage!), clusterbangs, snappops and interestingly tomatos and watermelon.
Bolas are still blocked from throwing due to EnsnaringComponent. But this needs a more general cleanup on what hould and should not be throwable for pacifists. Things like DamageOtherOnHit and ExplosiveComponent for example.

ExplosiveComponent

They should not be able to set off explosives directly, throwing them seems like something they would be able to do in fear. Just getting a grenade away from you seems like something a pacifist would be able to do.

Blocking DamageOtherOnHit is a better idea imho. Stuff that breaks when thrown should be fine to throw as long as it’s not hurting people. (Speaking of which- why is Ensnaring blocked? That’s pretty squarely nonlethal)

as long as it’s not hurting people. (Speaking of which- why is Ensnaring blocked? That’s pretty squarely nonlethal)

Exactly the issue with the trait, what is its objective? Is it to make it so they are passive and can't do combat or is it to prevent them from dealing damage? Half of what we have right now prevents damage while the other half prevents all combat. Stun batons but not Disablers. Glass shards but not bola. C4 charges but not open containers.

I tested it with lightbulbs, so fair call on the bola bit. I'm going to not change ensnaring in this PR though, I'll leave that for later since it seems like more of a balance discussion than a bug fix.


Stuck trying to upgrade to Transformer 2

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.13.1
Amplify CLI Version
8.0.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Amplify Categories
api
Amplify Commands
push
Describe the bug
Hi, we were trying to upgrade from GraphQL Transformer 1 to 2.
During the initial deploy, we got the error that our security token had expired.
Upon trying to redeploy, we now get this error:
An error occurred during the push operation: ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchInstanceCount, OpenSearchInstanceType, OpenSearchDebugStreamingLambda, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchStreamingLambdaRuntime] do not exist in the template"]

Expected behavior
We don't get that error
Reproduction steps
I don't really know how to include this, but:

Upgrade to graphqltransformer2
amplify push
security expiration token error
amplify push

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hey @CodySwannGT :wave: apologies for the delay here but following up on the email you sent it appears this is now resolved after adjusting the project path(?), and the CLI was copying the Elastic* parameters over from the other environment?
@giulioambrogi are you also encountering the issue where Elastic* parameters are missing after migrating?

Hey @giulioambrogi are you still experiencing this?

Hey @josefaidt.  I started getting this error today.  Amplify version 9.1.0.  We migrated our dev environment to v2 a couple of days ago successfully.  Merged to test and started getting this error.  Can't run amplify push at all and completely stuck.

Managed to solve this with the below steps

download the '#current-cloud-backend.zip' from the deployment s3 bucket.
search and replace 'ElasticSearch' with OpenSearch' in all cloudformation files
had to force the python version to 3.8 as well due to it trying to deploy version 3.6 which AWS does not allow anymore
zip and re-upload/overwrite the '#current-cloud-backend.zip' in the deployment s3 bucket.
run amplify push locally

Hey 👋, Closing this because of inactivity. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you.
Thank you!

Experiencing this issue after the amplify pipeline timed out during deployment while adding OpenSearch to our staging environment, it looks like CF continued (the SearchStack exists with a green status), but the amplify S3 bucket does not have the necessary info in it, I keep seeing:
 ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType] do not exist in the template"]
I can't find any of these terms in the amplify files, I have tried rerunning the pipeline as well as running amplify push --iterative-rollback amplify push --force through the cli with no luck always the same error, it looks like it does not know how to recover.
The environment is stuck in a weird state of half deployed, since the backend finished deploying some things, but not all things, and the frontend did not even start deploying. It would be nice if amplify understood how to recover from these types of timeouts.
Any idea how I can fix this?

@josefaidt Having the same issue after adding @searchable to a model in my dev environment and then merging those changes into staging and amplify pushing that. I'm guessing the original issues occurred because of a network timeout/stability during my push which had my new @searchable in it (the CLI hung and died)?
I checked the current-cloud-backend.zip for both my dev env (working) and staging env (not working) and saw that the staging env is indeed missing all these keys from build/cloudformation-template.json.json:
OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType
What should I do here to get my staging env back on track? Is there a way to force re-generate that build/cloudformation-template.json.json file? Should I add the keys manually to my file on staging and zip and upload the current-cloud-backend.zip?

@josefaidt Hey Josef, any pointers from the Amplify team on how to get an environment back from a botched V2 transformer migration as per described by @ssimonsen above? Currently we have some production environments in this corrupted state, where it seems the #current-cloud-backend contains definitions (aka templates) pre-V2 upgrade which is preventing from re-deploying with the above errors.
We have the same issue, and found that replacing the contents of #current-cloud-backend with the latest amplify/backend from the repo and removing all node_module folders work to allow deploying again from the CI/CD pipeline (which does result in CloudFormation stacks getting updated), but we are wary of how this might just be telling Amplify 'the upgrade and deployment went through' and leaving out defined resources from the V2 migration in the environment, so a big unknown-unknown.

@josefaidt @AnilMaktala Having the same issue after adding @searchable to a model in my dev environment and then merging those changes into staging and amplify pushing that. I'm guessing the issue was caused by a network timeout/instability during my push which had my new @searchable in it during which the CLI hung and eventually died?
I checked the current-cloud-backend.zip for both my dev env (working) and staging env (not working) and saw that the staging env is indeed missing all these keys from build/cloudformation-template.json.json:
OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType
What should I do here to get my staging env back on track? Is there a way to force re-generate that build/cloudformation-template.json file? Should I add the keys manually to my file on staging and zip and upload the current-cloud-backend.zip?

@ssimonsen This is my situation as well, did you ever recover from it ? Mine is my production environment not working though.

@ibussieres Wish I could tell you there was any easy way to resolve this, I don't remember all the details because I had this issue almost a year ago. The easiest way to recover is to create a new env. For prod, this is obviously difficult, mine was a dev env.
For future iterations, I would recommend always doing the auto deploys from a branch, that way making changes like @searchable won't be impacted by your network connection. Sorry I can't be of more help. Amplify tooling is frustratingly tricky and fickle.

@ibussieres Wish I could tell you there was any easy way to resolve this, I don't remember all the details because I had this issue almost a year ago. The easiest way to recover is to create a new env. For prod, this is obviously difficult, mine was a dev env.
For future iterations, I would recommend always doing the auto deploys from a branch, that way making changes like @searchable won't be impacted by your network connection. Sorry I can't be of more help. Amplify tooling is frustratingly tricky and fickle.

Thanks for the reply.
Funny story, it was deployed from a branch. Didn't prevent the timeout !

@ibussieres I'm very sorry to hear you're also facing this issue. With us it was due to the CLI token expiring in the middle of the V2 migration which left the deployment bucket file in a weird halfway state.
We were able to fix our environments with a very ugly and awkward hack, but it worked and the environments have been fine since.
We took the #current-cloud-backend.zip from another environment (if I remember right, from a V1 environment) and manually, carefully replaced all the references to the environment with the broken/target environment.
After that, it's possible your backend resources (appsync, lambda) might be in a like halfway state between your V1 and V2, which you can address by re-deploying all your resolvers and functions.
For resolvers, do:

Set all your @model directives on the schema.graphql file to be @model(queries: null, mutations: null, subscriptions: null). You can use this regex to find all of them and replace them: @model\([\s\S\n]+?\)
amplify push
Restore the schema @model directives to what you mean them to be
amplify push again. This should re-deploy all resolvers

For lambdas, a simple trick is to add a change to their javascript source file so the amplify CLI picks up the change and marks them for updating. We did it as follows:

Replace exports.handler with exports.handler /**/for all files under amplify/backend/function/ (this is just adding an empty comment which is enough)
Add a comment under any part of the lambda layers you might have
Amplify push and wait for the changes to deploy
Revert the changes (maybe with git reset --hard)
Push again. All lambdas should be updated

Hopefully that would put your environment back in working order. Best of luck. This is a very bad issue on Amplify's part imo.

@josefaidt  @ibussieres I am running into this same issue. I added @searchable to a couple entities, then my token expired mid-push and now my project is broken. Is there a way to fix this?


requirement: Is there a demo for utf-16?

I guess if I input a string of utf-8 characters,  when it will be revert direction, it's hard to handle it when it's represented with utf-8. So is there a demo for utf-16 ? I need to process  uyghur characters.

I get some character from a book with OCR and need to encode it into the correct form.

SheenBidi does not revert the direction, but it provides runs in visual order. The client is free to render the string in reverse order by checking the the level of the run.
SheenBidi can also work on UTF-16 if the client provides such string. Only SBStringEncodingUTF16 needs to be provided in that case.


Extrinsic RPC subscription events are capitalized

This is inconsistent with the Polkadot RPC
In Polkadot the ready, inBlock, finalized subscription event keys are not capitalized

Using chopsticks these event keys are Ready, InBlock, `Finalized

I will put this as "won't fix" for now until one of those happens:

Identify compatibility issue with existing tools due to this
OR some spec is created specifying what's the correct behaviour

There is no spec, but Substrate nodes and now Smoldot will return the non-capitalised event names, so shouldn't chopsticks align with these?
A compatibility issue at present is with Subxt, which understands the smoldot/substrate based camelCase event names and fails for the uppercase names emitted by chopsticks (Rust being more strict on these sorts of things).

we can fix this if it is causing trouble for subxt


Curling Tomcat Version adding White space Ubuntu 16.04.3

OS: Ubuntu 16.04.3 (inline upgrade from 14.10)
Line 671  version=$( curl -s http://tomcat.apache.org/download-80.cgi | grep "<h3 id="8.0" | head -n1 | awk '{gsub("<[^>]*>", "")}1')
Version:                             8.0.47
Downloading and installing latest Tomcat 8
--2017-10-04 11:56:40--  http://www.apache.org/dist/tomcat/tomcat-8/v                            8.0.47/bin/apache-tomcat-                            8.0.47.tar.gz
Resolving www.apache.org (www.apache.org)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to www.apache.org (www.apache.org)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-04 11:56:40 ERROR 404: Not Found.
tar (child): /opt/apache-tomcat-                            8.0.47.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
mv: cannot stat ‘/opt/apache-tomcat-                            8.0.47’: No such file or directory
rm: cannot remove ‘/opt/apache-tomcat-                            8.0.47.tar.gz’: No such file or directory
adding | awk ‘{print $NF’} ) to the end of line 671 as a temporary fix

Fixed (hopefully) in v4.91 which I've just released.


Better type for Future fold

https://github.com/avdosev/either_dart/blob/06b4361e99191008dcf6381555f77aca05a428a1/lib/src/future_extension.dart#L57-L59
I am quite new to dart so I may be wrong here (that's why I am creating an issue rather then pull request) but shouldn't fnL and fnR return FutureOr<T> instead of T?
Future<T> fold<T>(FutureOr<T> Function(L left) fnL, FutureOr<T> Function(R right) fnR) {
  return this.then((either) => either.fold(fnL, fnR));
}

This is what this.then() actually expects and it would allow us to do something like this:
bool success = await getStatusAsync()
  .fold(
    (error) async {
      await saveErrorAsync(error);
      return false;
    },
    (status) async {
      await saveStatusAsync(status);
      return true;
    },
);

(it's just and example and my usecase is actually quite different but I also need to fold both left and right to different futures of the same type)

You are right. Using FutureOr in this case is justified. I will take this point into account and make a new release.

I published a new release, you are welcome to use it.


Base Skeleton Creation

[x] created template
[x] readme
[x] setup python package
[x] tests setup
[x] research directory

done


Update for bevy main

Throwing this draft PR out here in case it's useful, or somebody wants to collaborate on this.
With this PR, the project compiles, but:

Does not display tilemaps
I had to remove MapQuery::get_layer due to a mysterious lifetime-related error
There are some warnings left to clean up.

Okay, probably fixed the "not displaying anything at all" issue, but I have only tested the map example so far.

Thank you for working on this! 👍

example
result

accessing_tiles
ok

animation
ok

atlas_spacing
ok

bench
ok

color
ok

dynamic_map
ok

game_of_life
:x: panic

hex_column
ok

hex_row
ok

improved_iso
ok

iso_diamond
ok

iso_staggered
ok

layers
ok

ldtk
:x: blank screen, warning

map
ok

random_map
ok

remove_tiles
ok

replace_material
:x: compiler error

sparse_tiles
ok

texture_atlas
ok

tiled
ok

visibility
ok

I updated the ldtk map and that example is now working again. ldtk_rust switched to a new json schema in 0.5.3 (main branch is locked at 0.5.2)
game_of_life is panicking the same way on the main branch, so that seems unrelated to this PR / bevy 0.7.

Bevy 0.7 was released, so added some commits that hopefully get bevy_ecs_tilemap ready for  a release.
If you'd prefer any of that be reverted, squashed, or you'd prefer to handle release details, let me know.


[core] Use a frontend framework

I don't know how this will work with crispy forms, but I'd honestly like to axe crispy anyway.
http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/

METEOR!


Highlight mute for a certain time

I would like to suggest a timeout button for highlight sounds (and taskbar flashes) for a certain time, like i.e. WhatsApp has. Either with given values like whatsapp, or a custom timer, or both.
Especially when in online meetings, I often run Chatterino in the background and get distracted by ping sounds once in a while, and disabling the sound manually would need you to enable them by hand again.
Would be a nice QOL feature.

Not labeled, reposted


Support limiting characters in TextField

Suppose we have a feature in which we want to allow users to input up to X amount of characters, there is no way to achieve this now as state is handled internally.

Can you assign this to me?

Yes sure,
Feel free to ask any questions you may have. You can use the updateTextFieldValue and onTextFieldValueChange methods in RichTextState to add this validation. You can use newTextFieldValue.text to get the number of characters of the new typed string.


Use ristretto255 with libsodium-wrappers-sumo instead of elliptic

rely on libsodium for hashing, random scalar, scalarmult, and scalar opertaions
modify tests accordingly, add additional tests
bundle sodium in OPRF and remove other dependencies
update all dependencies to latest version
update package.json
update README.md

Pull Request Test Coverage Report for Build 95

48 of 48 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.5%) to 98.462%

Totals

Change from base Build 77:
-1.5%

Covered Lines:
55

Relevant Lines:
55

💛  - Coveralls


Add a run tests action for folder with tests from test explorer

Hi!
I have been searching for this in case I can find some extension but either I am too new to vscode and I cannot search properly what I am after or there isn't any. In many of my projects, and I would say this is rather common approach, I have all of my tests nested within a main test folder. I have my tests nested within this folder in different subdirectoreis depending on the logic block the tests refer to: cli, api, core... It took me a while to understand how to set up test discovery but everything is now up and running. All tests are discovered and I can run them properly.
Nonetheless I cannot but wonder if I could just run a set of these tests easily from the test explorer. I can go and click in one of my test files to run or debug all tests within it but sometimes I want to launch all tests found in every file within a folder that contains tests. With the same approach, i.e. click on the run button.
This button does not seem to appear for directories, only for files with tests.
Is this something that could be added? Or is there a way to do this I am not aware of?

This is a dupe of #6545


Blog on KUDO and Team

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

nice. I like it. I've read it through once over, like the content, I'll re-read again in a bit looking at phrasing/grammar/etc.


Update Fileshare-to-ODSP-migration-guide.md

Updated to correct link to Microsoft 365 adoption guide in section "Onboarding related resources"

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@scanum @JohanFreelancer9 I just changed the URL and did not change any text in the document. I'm not 100% sure but I believe that copy editing is not necessary.

@panjkov Thank you, looks good. We do not include locales (e.g. en-us) in the links, and also use the full title of the referenced article where possible.

@JoanneHendrickson PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Add TransactionManager Metrics type

Describe the feature
Same as https://github.com/paradigmxyz/reth/issues/684
but a metrics type for the Transactionmanager, which should include

propagated transactions
...?

Additional context
No response

Would love to help out with this.

awesome!

Hi, @mattsse I finished the changes, but I cannot push them to a new branch. I'm getting a permission denied error:
ERROR: Permission to paradigmxyz/reth.git denied to Kuly14.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Is there some problem on my end, or do you need to grant me some permissions? Thanks a lot!

did you fork it?
https://github.com/Kuly14/reth does not exist yet
try:

fork
push to fork
open PR

Oh, of course. Damn, I'm used to just being able to create branches willy-nilly. Thanks for the advice!


How to build Tensorflow 2.x with customerized protobuf version?

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
TensorFlow 2.x
Custom Code
No
OS Platform and Distribution
Linux CentOS7
Mobile device
No response
Python version
3.8, 3.10
Bazel version
using Bazlisk
GCC/Compiler version
have both gcc 7.3.1, clang 7.0.1
CUDA/cuDNN version
No response
GPU model and memory
CPU Only
Current Behaviour?
I am writing MySQL UDF using TensorFlow C Library. But the MySQL8 has a conflict dependency of protobuf version with TensorFlow C Library. By default, MySQL8 needs protobuf 3.6.1 but TF uses higher version. I tried to modify the workspace2.bzl but the patch file is a problem to me. Since I do not have permission to change the building of MySQL8. How can I port a lower version of protobuf with TensorFlow 2.x? Thanks!
Standalone code to reproduce the issue
The actual error I got is below

what():  This program requires version 3.9.0 of the Protocol Buffer runtime library, but the installed version is 3.6.1.  Please update your library.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "bazel-out/k8-opt/bin/tensorflow/core/framework/tensor_shape.pb.cc".)

### Relevant log output

_No response_</details>

Hi @xunzhang ,
Tensorflow allows user to choose protobuf versions within some range.Please refer to protobuf versions required for TF2.13 versions below along with exclusions that may not work.
https://github.com/tensorflow/tensorflow/blob/525da8a93eca846e32e5c41eddc0496b25a2ef5b/tensorflow/tools/pip_package/setup.py#L96
You can install any of the protobuf versions mentioned above for your build.
Thanks!

@xunzhang ,
Unfortunately, It may not possible for the customization of protobuf version other than those mentioned in setup.py as mentioned in above comment.


Problem with deployment

I've just made some changes but having trouble deploying.
I think the problem is related to some recent folder restructuring. Something like ISL-lab-4 now lives under isl.
> julia deploy.jl
  Activating project at `~/.julia/environments/work`
Current working directory: DataScienceTutorials
  Activating project at `~/GoogleDrive/Julia/MLJ/DataScienceTutorials`
ERROR: LoadError: IOError: open("_literate/ISL-lab-4/.CondaPkg/Project.toml", 0, 0): no such file or directory (ENOENT)
Stacktrace:
 [1] uv_error
   @ ./libuv.jl:100 [inlined]
 [2] open(path::String, flags::UInt16, mode::Int64)
   @ Base.Filesystem ./filesystem.jl:121
 [3] open
   @ ./filesystem.jl:113 [inlined]
 [4] sendfile(src::String, dst::String)
   @ Base.Filesystem ./file.jl:998
 [5] cp(src::String, dst::String; force::Bool, follow_symlinks::Bool)
   @ Base.Filesystem ./file.jl:386
 [6] top-level scope
   @ ~/GoogleDrive/Julia/MLJ/DataScienceTutorials/deploy.jl:90
in expression starting at /Users/anthony/GoogleDrive/Julia/MLJ/DataScienceTutorials/deploy.jl:80
```[

Unexpected. Quite sure I deployed after changing folder structure to ensure everything is alright (and back then something broke and I fixed it). I may be afraid that this is mixing ignored files with available ones or something on your machine.
I think what we can do:

[ ] I to try to deploy again and see if I run  into this (and fix if I do)
[ ] Ask you to try to deploy again (using a fresh clone if necessary)

@ablaom I couldn't reproduce by recloning the repo and attempting deploy. deploy.jl produced no such error. You can delete the repo and reclone or try cleanpull() as in the bottom of the README to regenerate the site from scratch.

That said, deployment still fails due to:

This password issue was something I encountered and spent time with few months ago and the answer was to replace the auth token because the previous one was expired. I'm surprised that has come up again. JuliaAI has not changed in any significant way revently, right @ablaom?

I tried cleanpull and still got the same error.

Okay, after recloning I had success from the local end but encountered the same "password" issue as you in the github action.

Updated the deploy GH action, added new public and private keys (one was missing). This seems to have resolved the issue.

Thank you. Have no idea how it had worked previously with one key; I followed the pattern I saw somewhere else back then.

Thank you. Have no idea how it had worked previously with one key;

Yeah. Totally weird.


[6.0] [DebugInfo] Small fixes

Explanation: This PR fixes small debug-info related issues. See the commits for more information.
Scope: Adds debug values in swift passes, fix emitted debug info.
Original PR: #73009 (+ #73084)
Risk: Low, only changes to debug values
Testing: New tests have been added
Issue: None
Reviewer:  @adrian-prantl

@swift-ci please test


Remove extra "in"

Description of changes:
A fix of a typo.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@bonniekeller, thanks for pointing this out. Using GitHub's web editor is not always the best choice to edit sources after all...


Changelog fails when bump uses -d to set a directory.

gommitizen bump -d path/to/project -I PATCH -c

This command will fail.
Bumping version with increment: PATCH
## Running bump in project path/to/project

Version bumped from X.X.X to X.X.X
Error updating Git: error: the file path/to/project/CHANGELOG.md could not be added: exit status 128

        ** gommitizen must be run in the root path of the git repository

Error committing changes with Git: error: the file path/to/project/CHANGELOG.md could not be added: exit status 128

        ** gommitizen must be run in the root path of the git repository

@jaimeph is this solved already?


Ability to persist localOnly values

It would be great to persist some additional data in localStorage only, without updateing it with httpResponse and sending to beckend. By storing in $metadata attribute or by adding prefix $.
example cache object
{
   "_id": "5702c99c4cff28ec26989924",
   "$someLocalAttribute": "Derp"
}

example POST body in this case
{
   "_id": "5702c99c4cff28ec26989924",
}

@demands Do you like that suggestion? I could implement it with tests and propose a PR if agree it is useful.

What an interesting idea! (It's good you tagged me, btw... I just noticed that I'm not "watching" this repository for some reason.)
Anyway, I'm nervous about adding special flags to keys that signify different behavior (like the $ prefix), since I can totally imagine that certain users of this library might actually have a legitimate need to send $someLocalAttribute to the server.
What if there was a way to specify the localOnly keys in the resource definition? Like this:
var Article = $cachedResource('article', '/articles/:id', {
  id: "@id"
}, {
  localOnly: ['$someLocalAttribute', '$metadata'],
});

(@felippenardi @zhakhalov)

@demands I love that!

looks good

Cool. I don't have the bandwidth to implement this right now, but if anyone else does I would gladly accept a pull request.

I don't have the bandwidth to that yet too, but I have it in my list if anyone gets to it before me.


Added link for Final Report (Draft)

I've added link for the draft of final report. Please check if the link works.

Yes, this works.


replace standard bearer token with a hashed subtoken for cluster requests

Current dependencies on/for this PR:

main

PR #270   👈

This stack of pull requests is managed by Graphite.


Add co-signer modal > Need more help?

While creating a wallet when we create a collaborative wallet and click the need help and the modal appears , the "Need more help" button in the modal is hidden currently and must unhide it and then make it redirecting towards the concierge on click

Completed


Can JSON response to remote be processed before validation?

Subject of the issue

The server accepts<EMAIL_ADDRESS>

The server responds: {"data":{"activeROAndFaculty":"0","activeRO":"0","email":"1"},"status":{"code":"200","message":"Transaction is successful"}}

I want to validate the existence of the email address, which requires the processing of the response before validation. However, jquery-validation is only expecting true or false

I have tried using addMethod with an Ajax GET within, but cannot capture the server response within complete, success, error, dataFilter or data etc.
Your environment

version of jquery-validate: 1.19.0
which browser and its version: Firefox 66.05

Steps to reproduce
$.validator.addMethod("uniqueEmail", function(value, element) {
	let base = "https://domain.com/";
	let email = document.getElementById("email");
	let emailTrimmed = email.value.trim();
	let orgName = document.getElementById("orgname");
	let orgNameTrimmed = orgName.value.trim();
	let emailOrgName = "uniqueEmailCheck?emailId=" + emailTrimmed + "&orgName=" + orgNameTrimmed + "&faculty=" + null;
	let emailCheck = base + emailOrgName;
	$.ajax({
		type: "GET",
		url: emailCheck,
		// Want to capture JSON response, extract email value ("1") and then return "true" to jquery-validation.
	});
});

OK, I have this working. The below code processes the server result so that the desired true or false is returned to the plug-in and it provides native Bootstrap 4 validation styling.
$.validator.addMethod("uniqueEmail", function (value, element) {
	let emailOrgName = "yourDomain/uniqueEmailCheck?emailId=" + value;
	let result = false;
	$.ajax({
		type: "GET",
		url: emailOrgName,
		dataType: "JSON",
		success: function (data) {
			if (data.data.email === 1) {
				// console.log(data.data.email + ': This email exists.');
				result = false;
			} else {
				// console.log(data.data.email + ': This email does not exist.');
				result = true;
			}
		},
		async: false
	});
	// console.log(result);
	return result;
});

$("#form").validate({
	rules: {
		email: {
			required: true,
			email: true,
			uniqueEmail: true,
			normalizer: function (value) {
				return $.trim(value);
			}
		}
	},
	messages: {
		email: {
			required: "Please enter your email address.",
			minlength: jQuery.validator.format("Your email address must consist of at least {0} character."),
			maxlength: jQuery.validator.format("Your email address must be no longer than {0} characters."),
			uniqueEmail: "Your Email address is already registered on our system.",
		}
	},

	// Bootstrap 4 native validation containers and classes

	errorElement: "div",
	errorClass: "is-invalid",
	validClass: "is-valid",
	errorPlacement: function (error, element) {
		error.addClass("invalid-feedback");
		if (element.prop("type") === "checkbox") {
			error.insertAfter(element.next("label"));
		} else {
			error.insertAfter(element);
		}
	},
	highlight: function (element, errorClass, validClass) {
		$(element).addClass(errorClass).removeClass(validClass);
	},
	unhighlight: function (element, errorClass, validClass) {
		$(element).addClass(validClass).removeClass(errorClass);
	}
});

Is there a way to handle this use case that doesn't require async: false? Is dataFilter still the recommended solution, cf. #1491?


Issue when set text programmatically

Sometime i want to set text by programmatically but text in animatedtextinput i don't see text. I just only saw placeholder above(To). Can you help me fix this bug.

Have the same issue here. Think this issue only happens when instantiating programatically

You have to:

Init AnimatedTextInput
Set style, type and etc
At the end set text (after all init and customisation)

I can confirm that I got rid of this bug by reordering operations: first all the styling, and only then setting the text.
I have AnimatedTextInput as IBOutlet connected from Storyboard.

Is there a workaround for this issue?  Since the issue is closed, has this been fixed?  I just tried creating a textField programmatically and I'm getting the same issue as the OP.  The attached code is going in my viewDidLoad() function.
`      let textField = AnimatedTextInput(frame: frame)
textField.backgroundColor = .lightGray
    self.view.addSubview(textField)
    textField.placeHolderText = "Email"`

Thanks in advance!

It should be working if you specify the correct frame.
Animated text input uses intrinsic content size to calculate its own height, make sure you give it at least the minimum amount it needs.
I'd also recommend using autolayout, either programatically or using interface builder.


Changing the limit for POST body size

I am using postgraphql exposed Postgres function to process quite a bit amount of data (not storing binary files in db, use case is providing array of objects to db to process), and I have encountered following error reply when doing POST:
{"errors":[{"message":"request entity too large"}]}
It seems that I am hitting default limit of express post body parsing middleware which can be easily changed in code.
Just wanted to check if postgraphql exposing an option/way to configure this which is not mentioned in doc?
If not, I assume the best solution to use postgraphql as a library in custom small nodejs/express server?

We may want to discuss raising the default, otherwise I’m totally open to adding this option 👍
It looks like @guyemerson referenced this PR in a commit to his fork: https://github.com/guyemerson/postgraphql/commit/abbc8006719869e338f113277bcf3ea53443b086. That change looks good, although we may want to change the variable name.

Released in 3.1.0 🎉


genpolicy: add shareProcessNamespace support

Validate the sandbox_pidns field value for CreateSandbox and
CreateContainer.

Implemented upstream https://github.com/kata-containers/kata-containers/pull/8909


Repo creation for "ocp4 prerequisites validator".

Type of repository request
New repository
Requested name for the repository
Proposed name: ocp4-prereqs-validator
Repository Description
This repo aims to be ansible playbooks and roles to validate if the prerequisites for OCP 4 deployment is ok. The final intention is to validate all prerequisites, such as:

DNS
LBs
DHCP (if possible)
Firewall (if possible)
etc.

An initial version already exists and it is working that validates all DNS entries (A/PTR and SRV records). You can see in my github
Admin Access
For now just me (giofontana) and anyone else who wants to collaborate with this project
Write Access
For now just me (giofontana) and anyone else who wants to collaborate with this project
Read Access
For now just me (giofontana) and anyone else who wants to collaborate with this project
Additional details

Review request:
cc: @redhat-cop/container-cop-core

Repository created


Feature/validation flag [LEI-231]

Refs: https://openscience.atlassian.net/browse/LEI-231
Companion to: https://github.com/CenterForOpenScience/isp/pull/76
Purpose
Add the ability to turn validation off for testing.
Summary of changes
If the validate flag is set to false, allow users to continue through the survey without having to answer every question.

Done responding @abought! ☔


TypeError: router.on is not a function

Hi,
I'm trying to update a Ember application from 3.4 to 3.6 or above (I tried with the latest lts 3.20 and some in between versions) but I got this error. The offending line is this: https://github.com/ebryn/ember-component-css/blob/v0.7.4/addon/instance-initializers/route-styles.js#L6
I assume the code is correct, but I cannot find the cause of the error. Any ideas?
Thanks!

Nevermind, I found that we have in our application a service named router and the service lookup was confused about that :sweat_smile:


fix(upgrade): remove deprecation warnings

Upgrade to React 15.5.4 and fixed deprecation warnings.
Closes https://github.com/Hacker0x01/react-datepicker/issues/813

Codecov Report

Merging #822 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #822   +/-   ##
=======================================
  Coverage   92.65%   92.65%
=======================================
  Files          12       12
  Lines         613      613
  Branches      114      114
=======================================
  Hits          568      568
  Misses          8        8
  Partials       37       37

Continue to review full report at Codecov.

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

@obartra do you need any helping hands with this one? I've seen that you transitioned all the classes in your fork. Anything else to do?

I need to take another pass at it. I broke a couple tests in day.jsx but should be easy to fix.
My main concern is on making sure we are ok using transform-class-properties. It's a stage 2 feature but help us get rid of .bind everywhere.

Awesome! I'm using transform-class-properties in my projects too - but eventually @Hacker0x01 has to decide. Ping me if you need help with tedious tasks like putting the binds in the constructor in countless classes :-)

@martijnrusschen can you guys take a look see if this along the lines of what you are looking for?

Looks great! Thanks for the contribution!


Added Exomast API retrieval for Groups and Integrations

Added the basic retrieval functionality. Was thinking maybe in the future, we could break up the model drop down for stellar type, teff, and log(g) into separate buttons and then select the upper or lower limit of allowed values for the models based on whats returned from the API call.

@mfixstsci Is this good to go? Feel free to assign me to review when you're ready. Thanks!

@mfixstsci Is this good to go? Feel free to assign me to review when you're ready. Thanks!


⚠ Bofrost.be has degraded performance

In beea658, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1083 ms

Resolved: Bofrost.be performance has improved in 6b4dfe0 after 52 minutes.


Check in Cargo.lock

It's best practice to check it in for crates with executables: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
Other than it being "the right thing to do", I am currently trying to get Actiserve built using Nix, which is much easier if the lock file is checked in. I'm doing this, because Nix is a very easy way to get a Mastodon server up and experiment with the Mastodon/relay protocol.

thanks!


[AIRFLOW-2739] Always read default configuration files as utf-8

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[X] Here are some details about my PR, including screenshots of any UI changes:
When LC_ALL is not set to utf-8, Airflow crashes on startup on 3.4+ because it can not read the default configuration as ascii (as it contains non-ascii characters). This PR make sure we always read the default configuration files as utf-8.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3593 into master will increase coverage by <.01%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master    #3593      +/-   ##
==========================================
+ Coverage   76.83%   76.84%   +<.01%
==========================================
  Files         204      204
  Lines       15492    15493       +1
==========================================
+ Hits        11904    11906       +2
+ Misses       3588     3587       -1

Impacted Files
Coverage Δ

airflow/configuration.py
83.95% <90.9%> (+0.43%)
:arrow_up:

Continue to review full report at Codecov.

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


Migrate to react-router v6 stable

Feature Suggestion
Migrate to react-router v6 stable. We're currently on 6.0.0-beta.0 and should migrate to the stable release.
Possible Implementation
TBD, created this issue to track progress

Hi @Rugvip can I give it a try?

@snehaljos sure! Bit of a heads up that here be dragons, since we need to make sure that migration of existing projects is smooth. That said it would be valuable to just get the work of having this repo migrated done, it would take us a long way.

I tried to do that in https://github.com/backstage/backstage/pull/10126

Done in #10450 🎉


Custom callbacks are broken with Keras 2.4.Z wheels

While upgrading to Keras 2.4.Z, I got a weird Traceback when using custom callbacks:
Using TensorFlow backend.
Callback defined in keras.callbacks.callbacks
60000 train samples
10000 test samples
2020-06-24 15:06:02.820522: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2020-06-24 15:06:02.820546: E tensorflow/stream_executor/cuda/cuda_driver.cc:313] failed call to cuInit: UNKNOWN ERROR (303)
Traceback (most recent call last):
  File "keras_example.py", line 74, in <module>
    main()
  File "keras_example.py", line 41, in main
    train(x_train, y_train, x_test, y_test)
  File "keras_example.py", line 68, in train
    x_train, y_train, batch_size=120, epochs=10, validation_data=(x_test, y_test), callbacks=[MyCallback()]
  File ".../python3.7/site-packages/tensorflow/python/keras/engine/training.py", line 66, in _method_wrapper
    return method(self, *args, **kwargs)
  File ".../python3.7/site-packages/tensorflow/python/keras/engine/training.py", line 826, in fit
    steps=data_handler.inferred_steps)
  File ".../python3.7/site-packages/tensorflow/python/keras/callbacks.py", line 231, in __init__
    cb._implements_train_batch_hooks() for cb in self.callbacks)
  File ".../python3.7/site-packages/tensorflow/python/keras/callbacks.py", line 231, in <genexpr>
    cb._implements_train_batch_hooks() for cb in self.callbacks)
AttributeError: 'MyCallback' object has no attribute '_implements_train_batch_hooks'

I'm using latest tensorflow version, 2.22.0.
I digged a bit and found that it's not happening with latest Keras version installed from sdist. I installed it using the following pip command: pip install --no-binary ":all:" -U keras.
Callback defined in tensorflow.python.keras.callbacks
60000 train samples
10000 test samples
2020-06-24 15:08:15.681460: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2020-06-24 15:08:15.681477: E tensorflow/stream_executor/cuda/cuda_driver.cc:313] failed call to cuInit: UNKNOWN ERROR (303)
Epoch 1/10

It seems that the Keras wheel also includes a callbacks package that is imported in place of the new module https://github.com/keras-team/keras/blob/master/keras/callbacks.py.
$> unzip -l Keras-2.4.2-py2.py3-none-any.whl
       41  06-17-2020 23:03   keras/callbacks.py
      714  09-17-2019 17:12   keras/callbacks/__init__.py
    45641  10-07-2019 20:07   keras/callbacks/callbacks.py
    16934  09-17-2019 17:12   keras/callbacks/tensorboard_v1.py
     5447  09-17-2019 17:12   keras/callbacks/tensorboard_v2.py

This callbacks package doesn't seems present in the sdist package:
$> tar -tvf Keras-2.4.2.tar.gz | grep callbacks
-rw-r--r-- fchollet/primarygroup   41 2020-06-18 01:03 Keras-2.4.2/keras/callbacks.py
drwxr-xr-x root/primarygroup         0 2020-06-19 06:32 Keras-2.4.2/tests/keras/callbacks/
-rw-r--r-- fchollet/primarygroup 35586 2020-06-18 01:03 Keras-2.4.2/tests/keras/callbacks/callbacks_test.py
-rw-r--r-- fchollet/primarygroup 10186 2020-06-18 01:03 Keras-2.4.2/tests/keras/callbacks/tensorboard_test.py
drwxr-xr-x root/primarygroup          0 2020-06-19 06:32 Keras-2.4.2/docs/site/callbacks/
-rw-r--r-- fchollet/primarygroup  38830 2019-09-18 00:22 Keras-2.4.2/docs/site/callbacks/index.html
-rw-r--r-- fchollet/primarygroup   18342 2019-09-18 00:17 Keras-2.4.2/docs/sources/callbacks.md
-rw-r--r-- fchollet/primarygroup    2234 2019-08-22 18:24 Keras-2.4.2/docs/templates/callbacks.md

For the users that might be impacted, you can add replace the keras line in your requirements.txt file by:
keras --no-binary=keras

It also works with a version specifier:
keras>2.4.0 --no-binary=keras

Interesting catch. There was also a mismatch with backend objects. This is now fixed. It was a file cache issue.


[protopuf] Update to 2.1.0

Describe the pull request

What does your PR fix?
Update protopuf to 2.1.0

Which triplets are supported/not supported? Have you updated the CI baseline?
All, and it is a header-only library.

Does your PR follow the maintainer guide?

Yes

The cnl regressions will be resolved by another PR.

Waiting for #18767 merge.

@JackBoosY Hello, can this PR be merged now?

@PragmaTwice Yes.

Thanks for the update!


Adding useFullAllowList for node-exporter

For Linux Node integration to work fully, the set of metrics collected by node exporter needs to be extended.
To asbtract the complexicity from the customer and allow for a smaller command to activate the right list of metrics on the helm chart, this is adding a new flag to Values.yaml, which should be used to activate the Linux Node integration.
The customer will need to run:
helm upgrade --install grafana-k8s-monitoring  grafana/k8s-monitoring --namespace "default" --set metrics.node-exporter.service.useFullAllowList=true --reuse-values

Closing as this will be addressed in: https://github.com/grafana/k8s-monitoring-helm/pull/326


Streamlined site enrollment / event registration / game signup flow

The difference between enrolling a Warhorn account, registering for an event, and signing up for a game is not well enough understood. Players new to Warhorn often think they have signed up for a game when they have only registered for the event. And the process requires a number of clicks and form submissions. The process should be simpler, more coherent, and better explained.

Released!


fix aliases feature

The aliasses feature doesn't work, eg when you try to import lodash it imports like lodash instead of the default _.
I fixed this by adding parents here although I am not familiar with coffescript.

@jfromaniello whoops sorry I didn't get a notification for this! Merging now! Please @tnrich me in any further issue so I for sure get a notification


Q: How to use PostgreSQL sink from Java akka?

Any hint would be fantastic to see how PgStream#insertStreamToTable can be used as sink from a Java perspective?
Thanks, Niko

Almost one year late, but insertStreamToTable is a Flow so you would need to combine it (to) with a sink (Ex: Sink.ignore) to obtain a Sink.


Use dynamic template for test results email

Related Issue or Background Info

part 3 of #1950 using dynamic template

Changes Proposed

use dynamic template to send test result email

Screenshots / Demos
Checklist for Author and Reviewer
UI

[x] Any changes to the UI/UX are approved by design
[ x] Any new or updated content (e.g. error messages) are approved by design

Testing

[x] Includes a summary of what a code reviewer should verify

Changes are Backwards Compatible

[x] Database changes are submitted as a separate PR

[x] Any new tables that do not contain PII are accompanied by a GRANT SELECT to the no-PHI user
[x] Any changes to tables that have custom no-PHI views are accompanied by changes to those views
(including re-granting permission to the no-PHI user if need be)
[x] Liquibase rollback has been tested locally using ./gradlew liquibaseRollbackSQL or liquibaseRollback
[x] Each new changeset has a corresponding tag

[x] GraphQL schema changes are backward compatible with older version of the front-end

Security

[x] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[x] Any dependencies introduced have been vetted and discussed

Cloud

[ ] DevOps team has been notified if PR requires ops support
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

@bmaden-usds It seems like we have 2 emails that are still using the html template. I made this ticket #2865  to clean them up


Move the existing dashboard to NREL's template

Minimal changes to existing code, this simply copies the existing dashboard to the style/format in the NREL template.

Next steps:
-Change docker scripts to use e-mission config files, so that they only run the notebooks relevant to their deployment.
-Change notebooks and dashboard to read/write from a hosted, shared volume. S3?

Made some changes to support the dynamic configs PR: https://github.com/e-mission/em-public-dashboard/pull/51

Addressed all except for start-date, need to discuss that one

Now the date list should populate from the date in the dynamic configs. Currently using numeric date for convenience, but could add a map from numbers to months.

Added DoE logo and text near bottom of page, to match the example more closely we could write some text at the top, or also the DoE logo could be at the top near the NREL logo. This is what ended up looking cleanest.

dropdowns are now in two rows instead of one.
Differences between

NREL site 1
NREL site 2
NREL site 3
CanBikeCO site

Collapsed
Expanded

Malformatted choices
integer values (non padded)

** Fixed now!! **

Replaced in the text

Replaced in the value

Note that we display the mode of interest in the internal representation, not in the potentially translated representation.
Instead, the mode of interest should be outside the intro (it is not intro specific) and the translation(s) can be in the intro section, where we have translations for both Spanish and English.
Added to https://github.com/e-mission/e-mission-docs/issues/788

At this point, the only tasks left are:

read the study name from an environment variable
create a production environment which copies all the files into the image

note that this needs to also be configured to accept the environment variable above.

oh wait, we also remove the hardcoding on the initial set of slots.

NOW, we can finally work on creating the production dockerfiles/docker-compose.

@zackAemmer https://github.com/e-mission/em-public-dashboard/pull/50/commits/e267dcda2fde5d763e9bb316da50331d00937d38 is not actually a typo - it was an experiment to see where I needed to put the ticks. Once I figured it out, I didn't go back and change it.
Thanks for making it consistent with the others!

My changes approved by @zackAemmer


When no tasty tests called, test-options passes to QuickCheck instead of tasty

If no tasty tests called, OPTS from cabal test --test-options=OPTS somehow gets to quickcheck, not to tasty, which seems like a bug.

I think this is the default behaviour for tasty, but it's certainly weird and needs investigating.

@Renegatto Could you provide a simple example of the  behavior you're experiencing (i.e. the OPTs you're passing and the output you're seeing)? I believe that would help me track down the cause of this.

@gnumonik no, at the moment I don't have any project to trigger this issue on.
Just pass this way any tasty flag that QickCheck wouldn't expect, and you'll get QickCheck error.

@gnumonik I think the best solution is to 'swallow' those flags, assuming that we can do this. If not, I actually feel this might be a tasty bug; if that's the case, there's not a lot we can do about it other than report.

@Renegatto After digging through the tasty source, it seems very likely that the issue is on their end. I'm reasonably sure that Koz is right and that this is the default behavior, and that there is not an easy way to override it. I believe that it has to do with the way the Tasty typeclass instances are defined in the tasty quickcheck module, I can elaborate more if you'd like.
I could pursue this more if you wish; there may be a less-obvious or not-so-easy way to alter Tasty's behavior. Let me know if you think that would be worthwhile. If not, I'll file an issue report upstream.

I'm very happy if it will be just reported to tasty, it looks like the cleanest solution.
You're free to close this issue as soon, as you think you're done.


Srcset for background image.

Would be great if the srcset option could be extended to background images.
Depending on the screen size there isn't always the need to get the full image and serving a smaller image for the background would help.

Browsers don't have the technology to understand a srcset in a background image... yet.
There's a working draft named image-set but it's currently just a draft.

I was referring at a feature that will allow a similar functionality, for example setting multiple images (srcset like) and depending on screen size (width or height) lazy loading the one that fits the best.

That wouldn't be a lazy load, but a totally different thing. My script has only the purpose to load images (or iframes) as they enter the viewport. Maybe you should look for something else.


Add syntax highlighting to JSX and TSX files

After #319 lands, users will be able to compile JSX and TSX files.
However, there is currently not any syntax highlighting support other than red squiggles on errors (still helpful though).
Close this issue when syntax highlighting is supported for both JSX and TSX files.

Completed in https://github.com/google/playground-elements/pull/323


Support streams of objects that need cleanup

Streams are great for primitives and simple data, but they can be hostile against objects that need cleanup. Parts of the stream contract allow buffering and discarding events, which can leave a gap in the chain of custody and let objects that need cleanup leak. While such objects could be served using a callback scheme or a custom controller/sink/stream trinity, it becomes unfortunate to reimplement so much and lose async*/await for syntax.
Example use case:
import 'dart:async';

class MyAllocatedResource {
  ...
  Future<void> close() async {
    ...
  }
}

/// Consumers must close received objects.
Stream<MyAllocatedResource> multiOpen(...) async* {
  for (...) {
    yield MyAllocatedResource(...); // I'm likely to leak. Protect me.
  }
}

/// ADDENDUM: This is oversimplified; see #issuecomment-1530060075
Stream<...> myConsumer(...) async* {
  await for (final resource in multiOpen(...)) {
    try {
      ...
      yield ...; // I can be cancelled too.
    } finally {
      unawaited(resource.close());
    }
  }
}

In cases where the event is discarded, the resource leaks.
This can be worked around without abandoning the use of Stream, but it would be nice for this use case to be first-class. Workarounds are also complicated by bugs/inconsistencies in the async* implementation.
My current workaround looks like this. I may try to punt the allocation into onListen to try to avoid the yield* pitfall described below, but differences in error handling (try/catch vs. forwarding to Stream) may hinder that further.
Two issues in particular complicate workarounds:

yield on a cancelled async* behaves differently on VM and web

#48749 (web)
#49451 (VM; closed, but same as the above)
This can be worked around using a sync StreamController to clear onCancel and deliver objects atomically.

When yield* acts like return, it can drop the RHS stream without ever listening to it. While this is less egregious than a full-on leak, it does not seem to adhere to the spec and complicates the sync StreamController workaround as the case where the entire stream is dropped needs to be handled separately.

https://github.com/dart-lang/language/blob/main/accepted/future-releases/async-star-behavior/feature-specification.md

A yield* e; statement listens on the stream that e evaluates to and forwards all events to this function's subscription. If the subscription is paused, the pause is forwarded to the yielded stream. If the subscription is canceled, the cancel is forwarded to the yielded stream, then the yield* statement waits for any cancellation future, and finally it acts like a return; statement. If the yielded stream completes, the yield statement completes normally. A yield* is always an asynchronous operation.

Similar but differently worded in other specs
This can be worked around by wrapping yield* of the above StreamController in a try/finally, or deferring allocation until onListen.

Related use cases:

#51241

Possibly related:

#48695
#49623
#49621

Versions/platforms:

Dart SDK Version: 3.0.0-204.0.dev (dev) / DartPad stable, master
Platforms: Windows (unit testing), web (Chrome), Android

Possible related wishlist item: if StreamController.add could return a Future that completes when the event is delivered or dropped. There are obviously details that need to be hammered out (e.g. something like orCancel, and what about broadcast streams).

I can see that the async* (and its various difference in implementation) are not very useful or predictable.
You generally cannot know whether a stream event is received. There is an asynchronous gap between sending and it being received, and the receiver can always cancel in that gap.
The one thing that I think can be made completely certain is a synchronous single-subscription stream controller.
It delivers the event immediately when you call add if the listener is not paused, and you can know whether it's paused before you send the event.
I'd probably build an abstraction on top of that, with the ability to give feedback on whether an event is delivered or not, rather than add extra overhead to the normal stream controller.
Something like:
import "dart:async";
import "dart:collection";

/// Stream which allows registering events, to ensure delivery.
///
/// Creates a stream by calling [source] with a `register` function.
/// Events sent by the stream can be registered using the `register` function,
/// and if the stream is cancelled before the event has been delivered,
/// the `undelivered` function is called for each undelivered registered event.
///
/// Not all events need to be registered, but registered events *must* be sent
/// in the same order they are registered.
/// The `register` function returns the event again, to allow writing, e.g.,
/// `yield register(event);`.
///
/// Example usage:
/// ```dart
/// /// Allocates chunks of memory every second as long as anyone wants them.
/// Stream<Allocation> allocations() => ensureDelivery((register) async* {
///   while (true) {
///     await Future.delayed(const Duration(seconds: 1));
///     yield register(Memory.allocateChunk()); // Must not be forgotten
///   }
/// }, undelivered: Memory.freeChunk);
/// ```
/// If a listener cancels the allocations stream after a chunk has been
/// allocated, but before it has been delivered, then the chunk is passed
/// to `Memory.freeChunk` when the stream has been cancelled.
Stream<T> ensureDelivery<T>(Stream<T> Function(T Function(T) register) source,
    {required void Function(T) undelivered}) {
  final c = StreamController<T>(sync: true);
  c.onListen = () {
    final sentEvents = Queue<T>();
    final subscription = source((T event) {
      sentEvents.add(event);
      return event;
    }).listen(null);
    c
      ..onPause = subscription.pause
      ..onResume = subscription.resume
      ..onCancel = () => subscription.cancel().whenComplete(() {
            while (sentEvents.isNotEmpty) {
              undelivered(sentEvents.removeFirst());
            }
          });

    subscription
      ..onData((T value) {
        if (sentEvents.isNotEmpty && identical(value, sentEvents.first)) {
          sentEvents.removeFirst();
        }
        c.add(value);
      })
      ..onError(c.addError)
      ..onDone(c.close);
  };
  return c.stream;
}

I think I oversimplified my reduced example so that it no longer clearly shows the leak, and probably cannot leak as-is on VM (but does leak on dart2js due to #48749) so long as the consumer behaves like await for and pauses the stream while handling the event. However, it is very easy to violate this requirement; here's an example that does leak on VM as well.
import 'package:async/async.dart';

class MyAllocatedResource {
  static int unclosedInstances = 0;

  MyAllocatedResource() {
    ++unclosedInstances;
  }

  void close() {
    --unclosedInstances;
  }
}

Stream<MyAllocatedResource> multiOpen() async* {
  yield MyAllocatedResource();
}

void main() async {
  await for (final resource in StreamGroup.merge([
    multiOpen(),
    multiOpen(),
  ])) {
    try {
      break;
    } finally {
      resource.close();
    }
  }

  print('unclosedInstances: ${MyAllocatedResource.unclosedInstances}'); // 1
}

where an event is dropped because both async generators get to their yield before the StreamGroup is paused.

Also in case it helps, on Discord user @abitofevrything graciously surveyed the current behavior and deviations from the spec on different platforms:
https://gist.github.com/abitofevrything/56e5d0b7b5c3bc25462bca5f334c4cb2

Even with a correctly implemented async* function, it's always possible to end up with a computed value that won't be delivered. The yield e; statement will evaluate e first, before the yield checks whether the stream is cancelled. If it was cancelled, that event won't be delivered. The only way to know that an event was delivered is that code after the yield is executed. (If implemented correctly!)
That's an inherent design in the async* implementation, it only synchronizes with the stream subscription at the yield statements. Code between those runs obliviously to whether someone is waiting for another event or not.
It's only when the event is completely evaluated and ready to send that the yield will check whether there is a receiver.
That's not easily changed. I wouldn't even know where to start.
It is a place where async* functions are inferior to code written directly using a StreamSubscription, which can get callbacks immediately when someone calls pause or cancel on the subscription. The only way for an async* function to get information is to do a yield. (A yield* won't work, because there is always a delay after it, so the information you get from it running can be stale before you can use it.)
So maybe we should allow async* functions to register such callbacks, somehow? Or get access to the underlying stream controller, or at least something which exposes enough of it, while still being safe. (Not an easy thing to design properly.)
Just for the record, as specified (I hope, that was the intent), a yield doesn't have to pause the surrounding stream at a yield if it can deliver the event synchronously. It does mean that it must synchronously call the onData callback of the current invocation's associated stream subscription, then check right after whether the stream is paused or cancelled. If not, it's OK to continue synchronously executing the async* function body.
If the subscription is paused after the synchronous event delivery returns, then the sync* body should suspend at the yield and wait for a resume or cancel. It can then resume at (or probably at some time after) a resume or cancel, with the cancel behaving like return and the resume just continuing after the yield.
The function can also deliver the event asynchronously, and then it must suspend the async* function body until the event has been delivered, which is ... tricky to know if using a plain StreamController. Good thing it doesn't. (I'd recommend just delivering synchronously.)


Desktop Version

In the About page, how do I make JavaScript, html, css be in a square shape?

Kwamy you need to fix the size of the height and width, it'll fix your problem.

Hi @Kwamay,
I suggest using CSS Flexbox and aligning them perfectly using the proper flexbox property.


Add --subset option and domain+country annotation for wmt18+wmt19

There are surprising differences in BLEU scores between different domains (topics),
but most researchers ignore this because there is no simple way how to analyze it.
Now it is as simple as adding --detail to the sacrebleu command (see test.sh).
In addition to 6 domains: business, crime, entertainment, politics, scitech, sport, world,
this PR adds metadata about the main country/region for each news article:
EU, GB, US, OTHER (OTHER is further subclassified, but this annotation is not shown in --detail).
This annotation can be useful for disentangling the effect of translationese (original language) and domain/topics.
For such analysis, it would be nice to add domain+country annotation for some originally non-English documents.
I've tried to implement (and name) the --subset option in a relatively versatile way,
so it can be used for other purposes in future if someone adds other annotation.
Versioning the annotation (document metadata missing in the original sgm files)
in the source code is not elegant, but it is practical because

sacrebleu.py can still be used without installing (if portalocker is installed)
the annotation is tied with SacreBLEU's version
it is just 10-20 lines of "code" per wmt testset (original English docs only).

Thanks for merging. If time allows, I will try lxml.
Regarding the speed issues, I started answering it here, but then moved it to #46.

Sounds good! I'm going to do some full testing and then I'll release version 1.4.0 to pypi.

Hi Martin, how are the annotations sourced?


session.login fails on MacOS Sonoma

I'm trying to figure out how to login to a PKCS11 session on my new operating system. This used to work. I've update to the latest version of this crate.
This is the line of code that's failing:
let result = session.login(UserType::User, Some(&secret_pin));

This is the error message that's printed:
Assertion failed: (ret == 0), function digest_final, file boringssl_crypto_digests.m, line 41.

	mov    x2, x8
	bl     0x104f28a88                ; symbol stub for: memcpy
	ldr    x0, [sp, #0x8]
	ldr    x8, [sp, #0x58]
	adrp   x1, 9843
	add    x1, x1, #0xf48             ; rustc_hex::CHARS + 15760
	bl     0x104559c54                ; <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual at result.rs:1960
	b      0x104560f50                ; <+536> at session_management.rs:61:6
	ldr    x8, [sp, #0x10]
	ldr    x2, [sp, #0x28]
	ldr    x1, [sp, #0x20]
	ldr    x0, [sp, #0x18]
	ldr    x9, [sp, #0x50]
	ldr    x3, [x9, #0x8]
	str    x3, [x9, #0x40]
	blr    x8
	bl     0x1045557a0                ; <cryptoki::error::rv::Rv as core::convert::From<u64>>::from at rv.rs:19
	ldr    x8, [sp, #0x58]
	bl     0x104556794                ; cryptoki::error::rv::Rv::into_result at rv.rs:131
	b      0x104560f50                ; <+536> at session_management.rs:61:6
	ldr    x8, [sp, #0x58]
	adrp   x0, 9843
	add    x0, x0, #0xf30             ; rustc_hex::CHARS + 15736
	bl     0x104559f38                ; <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual at result.rs:1960
	b      0x104560f50                ; <+536> at session_management.rs:61:6
	ldp    x29, x30, [sp, #0x1b0]
	ldp    x28, x27, [sp, #0x1a0]
	add    sp, sp, #0x1c0

Can add more detail as a find it, but if anyone has ideas that'd be super helpful. Thanks!

Hi,
I've tried running your code for reproducing, and it didn't crash for me - though this was on an M1 MacBook Air with MacOs Ventura. Let me upgrade to Sonoma, try again, and I'll get back to you on that.

I seem to remember having the same issue. It occurred after upgrading my Homebrew openssl version to 3.2.0. Somehow, that doesn't seem to be working well with the Homebrew version of SoftHSM.
I solved it by installing SoftHSM via the nix package manager. A team member solved it by compiling SoftHSM from source, pointing to the Homebrew openssl version: ./configure<EMAIL_ADDRESS>Weirdly, that does work. No idea why.
Good luck!

@kristian1108 I didn't run into that problem, but if I run your boring-reproduce example I too get a segmentation.


feat: reduce library bundle size

I'm submitting a...
[ ] Bug Fix
[x] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[x] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[ ] Tests for the changes have been added

Description
At that moment, css and html within components cannot be optimized by the consumers by using Webpack, Angular Build Optimizer or any other tool that bundles simply because these optimization have to happen at a library level when the the transformation happens that turns these assets into strings in the JS file
Reduce final bundle size by;

Using cleanCss this will remove comments, new lines, extra quotes among others
Remove new lines in HTML templates as these don't have any effect in the browser

Other component libraries are doing the same. Apart from preserveWhitespaces (Which in this case the library develop can do)
https://github.com/angular/material2/blob/73bc948faaf4f3a566256e5e733109f9847bb252/src/lib/button/button.ts#L73
they also have the trim breaklines
https://github.com/angular/material2/blob/73bc948faaf4f3a566256e5e733109f9847bb252/tools/package-tools/inline-resources.ts#L53
https://github.com/angular/material2/blob/73bc948faaf4f3a566256e5e733109f9847bb252/tools/package-tools/gulp/build-scss-task.ts#L14
example
    SkeletonComponent.decorators = [
        { type: core.Component, args: [{
                    selector: "obg-skeleton",
                    template: "
Sample
\n\n
some text
",
                    styles: [":host {\n  display: block; }\n"]
                },] },
    ];

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Closes: https://github.com/dherges/ng-packagr/issues/614

@dherges can you please have a look at this as well?

When you have some time can you have a look at this? This sill reduce the bundle size of ui libs quite a bit

@dherges When you have some time can you have a look at this? This sill reduce the bundle size of ui libs quite a bit

@dherges can you please let me know what to do about this? As for me its kinda critical to reduce the bundle size mainly due to css and new lines.

I take only the stylesheet minification in, ok? I still think newlines in html account for whitespace in browser rendering

Fair point, thanks for sharing that. And doing the push.


MongoDB support

Is there a timeline for supporting mongodb?

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

is #998 relevant for this?

+1

+1

+1

+1

+1

@cworks Thanks for the 1000th star. Please get in touch by email...

Howdy Axel,
1000 stars…I’d say folks want Mongo in the mix :-)
Just starting to look at flyway and work through some tutorials.  I’m not a DBA but have a Java background and I love love love the usefulness, simplicity and flexibility of flywaydb.  Hoping to introduce it into our development environment at work.
Good stuff…keep up the good work,
~Corbett

On Oct 24, 2015, at 7:32 PM, Axel Fontaine<EMAIL_ADDRESS>wrote:
@cworks https://github.com/cworks Thanks for the 1000th star. Please get in touch by email...
—
Reply to this email directly or view it on GitHub https://github.com/flyway/flyway/issues/810#issuecomment-150876235.

+1

+1

+1

+1

+1

+1

+1

+1

+1

<body

+1

+1

+1
https://dzone.com/articles/mongodb-incremental-migration

+1

How many +1 must a man write down, befooore he gets Mongo migration support...
The answer my friend is flyway in the wind, the aaaanswer is flyway in the wind....

+1

+1

+1

+1

+1

+1

For the interested, as it seems that this issue is not going to get fixed in the short run, I have created a "mongo schema migration tool" that, although of course not sophisticated as flyway, it does what it needs to do:  https://github.com/rinoto/migramongo

I've been working on adding mongo integration, if anyone is interested in checking it out or has any recommendations on what can be added, you can find it here: https://github.com/brennan-collins/flyway/tree/mongoIntegration

+1

+1

Working with @brennan-collins to finish this up. Almost there. Please refer to https://github.com/khatkar/flyway/tree/jsMongoMigration

Mongo migration feature is now production ready.  https://github.com/risksense/flyway/tree/release-4.0.3-mongodb
@axelfontaine Can you please take a look? Feedback will be appreciated.

+1 @axelfontaine Is there a chance that this feature can included in the next release? Seems to me that there is a lot of demand for this and as many of us shift from relational to NOSQL DBs this will be even more popular. MongoDB is in Gartner's magic quadrant so that will be a clear benefit for Flyway.

+1

+1

Is this working

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 any news?

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

https://github.com/flyway/flyway/issues/810#issuecomment-264031798

+1

+1

+1

+1

+1

We should get this. Has been open for a very long time.

+1

+1

+1

+1

+1

+1

+1

+1

@khatkar Great point.
@flyway / @boxfuse / @axelfontaine or any active maintainers - Would a feature that implements NoSQL support in an extendable fashion (starting with MongoDB & DynamoDB) be considered for review & merge?  Any additional dependencies to support this would be strictly optional.

Anyone tried https://github.com/mongeez/mongeez, is it good?
I haven't checked it out yet. But a migration tool fro NoSQL is definitely a NEED!!

@jamesjieye check the latest commit there (2016 year) seems like not supported properly...
Right now there is no supported solutions for migration tool for MongoDB.

@Hronom Thank you for the heads up.
Just wondering what makes supporting migration of NoSQL database like MongoDB, DocumentDB so hard? Is it because of the schema-less?
For us, we always create $jsonSchema to define the structure of the document in each collection. Schema-less doesn't mean that we do not need to properly define database's structure. That would make the migration really hard. On the other hand, when we have not strictly, but properly defined schema by using $jsonSchema, would migration still be that hard?
The steps of how Flyway migrates described here https://flywaydb.org/getstarted/how is very similar to how we are managing the migration of MongoDB schema right now, although we do that manually, which is not ideal.
Anyone interested in building a migration tool specific for MongoDB, DocumentDB?

https://github.com/cloudyrock/mongock forked from mongobee. Springboot issues :(

+1

+1

+1 for dynamodb

+1

+1

+1

+1

To all the "+1" people: Have you checked out Mongock? I guess that's what you are looking for.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Use PostgreSQL with jsonb column instead. Works fine.

@Barry-RG, seems the dependency suggested in the guide is broken as it relies on the library that could not be found anywhere except for direct download from the JetBrains.com website
Here is output trying to follow the guide:
test-project:main: Could not find com.github.kornilova203:mongo-jdbc-driver:1.18.
Required by:
    project : > org.flywaydb:flyway-database-mongodb:10.4.0

The problematic code from the pom.xml file in https://github.com/flyway/flyway/blob/main/flyway-maven-plugin/pom.xml:
<dependency>
            <groupId>com.github.kornilova203</groupId>
            <artifactId>mongo-jdbc-driver</artifactId>
            <version>1.18</version>
</dependency>

The missing dependency seems to be mongoDb driver from this page: https://www.jetbrains.com/datagrip/jdbc-drivers/
Not sure where exactly it is supposed to be downloaded from, I've tried couple of Jetbrains repositories from this page https://plugins.jetbrains.com/docs/intellij/intellij-artifacts.html#specify-the-repository-url but none of them seem to contain desired library.
This happens both when you do
implementation("org.flywaydb:flyway-database-mongodb:10.4.0")

in your build.gradle(.kts) configuration and when trying to build this library from source.


Add setCommitStatus option

Fixes #135

@stevschmid Thanks for this PR and sorry for my late replay.
LGTM 👍


Maintainers for Stable Releases.

Lifted from https://github.com/envoyproxy/envoy/pull/15942#issuecomment-822124188, so there is a chance that people will read it:
@mattklein123 @htuch @duderino @lizan we don't have any maintainers for Stable Releases. Could you find any volunteers?

Dupe of #16027.


RenderProxySliver

Description
This PR consolidates common methods from new sliver classes into RenderProxySliver, making SliverOpacity, SliverIgnorePointer, and SliverOffstage subclasses.
Related Issues
Fixes #46031
Tests
Tests for SliverOpacity, SliverIgnorePointer and SliverOffstage all work now as subclasses of RenderProxySliver
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[x] No, this is not a breaking change.

Can you fix Cirrus?

Cirrus is still unhappy :(


Debug levels and scoped to modules unreliably works

I wondering if it is just me. I want to change (and also have set) log levels through local storage (in Chrome). It is described here.
On occasion that I have managed to get levels and scoping to work, I have to set BOTH the log level and the scoping. This isn't documented.
For example, I have a module 'Loader' that I want to exclude:
eg I set these values in Chrome > Dev tools > Application > Local Storage < [site]:
key       | value
log        |  debug
debug  | *,-Loader
Does this resonate with anyone? Cheers in advance
ps I load ulog via anylogger

Hi @toddb
Please get my phone number (see your other issue) so we can talk directly via What's App (or at least, so you will be able to ping me when I don't respond) because I have dozens of repos here on github and many times I just don't notice new issues and they just sit here gathering dust... I get so many notifications from Github that I cannot see the forest from the trees.
ulog is important to me and you are (for me) an important user because you are actually reporting issues and providing valuable feedback. So for you I am willing to go the extra mile, like you have for this project.
That being said I want to close this issue. Because v2 is... well just broken atm. I have been completely rewriting it and the current state is a mess. So for the short term, I would suggest to use ulog v1, or v2-beta.7 (8 once you do your thing) but without relying on the new features.
Once v2 is finished, it will work like this, given modules my:lib-a, my:lib-b, my:ignored-lib:
DEBUG=my:*,-my:ignored-lib

will force the log level to debug for all modules starting with my:, except for my:ignored-lib
This is basically exactly what debug does.
LOG=my:*,-my:ignored-lib=info; another=lib=warn

will set the log level to info for the same set of modules and set it to warn for another-lib. So it basically works almost exactly the same as the config for debug, except that you can specify a level value and include multiple configs by separating them with semicolons.
The combination of the two:
DEBUG=my:*,-my:ignored-lib
LOG=my:*,-my:ignored-lib=info; another=lib=warn

will force the log level to debug for all modules starting with my:, except for my:ignored-lib (so overriding the level configured in the LOG setting) and still set the level to warn for another-lib.
There will be a setting to configure formatters as well and it will work in the same way as LOG setting.
However, as it stands this functionality is not (completely) working as expected in the betas. And I just want to get v2 out based on anylogger so I don't want to spend any time on it now. So I want to close it for now, but if you still find such issues once v2 is out, please do report them (and ping me if I don't respond) and I will fix them all. Promised!

Should work as described now.

@Download I have tried and tried and I still don't get this functionality working. Do you have it working and perhaps in a pen? This is the killer feature I need (oh, as well as typescript support #37 :-) )

@toddb Have you checked out the tutorial?
Or, maybe the other way around, have you got a pen or repo for me where I can see what you are doing so I can maybe find the bug in ulog, or where you are using it wrong?

I hadn't seen that tutorial before but apart from the lazy loading, it all looks familiar. It could be my build chain and bundling.

If you share a project / repo / codepen, I can have a look.
It would be better if it was so easy you would not need my guidance, but I did not succeed in making it easy enough.
Ulog v2 has been in beta for 2 years now (!) but I don't care if it stays in beta for another 2 years, as long as I keep getting valuable feedback like this so I can actually improve it to the point where you can just pick it up and use it and it all works as you expect. It's clearly not there yet. But I'm stubborn and will keep going at this 😄

Oh and if you are building with webpack it may help to look at ulogs webpack config file, because that's basically the build for the tutorial project.

Documentation says that caps DEBUG can be used to set the log levels. In local storage, keys are case sensitive.
Note: in the log form log level is case insensitive.
This issue would also relate to the complete list log, warn, info, error.
Expected Behaviour
Logging based on levels changes when local storage switches are changed
Actual Behaviour
In Chrome/Firefox/Safari, only lower case key (eg debug) is respected.
Steps to Reproduce

Add to local storage case insensitive key/value pairs for logging configuration
Refresh browser and see expected log messages

Solutions
Change:

the documentation

note case sensitivity
add a BNF
step out behaviours separately from configuration (eg log versus loglevel forms)
there is no documentation on the order of precedence in the rules. Looks to be that the 'lowest' level rules (eg if I add a rule for debug and error on a module, debug always wins)

the behaviour

check case insensitive which probably include title case

@toddb Yes I will try to update the docs based on your feedback. I don't think accepting case-insensitive keys on localStorage is a good idea. Honestly, I wish env vars would also simply be case sensitive as it's much simpler (especially as, afaik, there is no easy way to access env vars in a case insensitive manner on Node JS when running on Linux, because you access it like process.env['some_string'], where 'some-string' is de-facto case sensitive... But probably explaining this better in the docs can help. About the BNF, I'm not exactly sure what you would like to see there... Can you elaborate?
Of course a PR would be super helpful here, but I understand if you don't have the time for that.

@Download

I don't think accepting case-insensitive keys on localStorage is a good idea.

My point is that current behaviour should be documented as clearly as possible for library users. Clean and clear interfaces.

About the BNF, I'm not exactly sure what you would like to see there... Can you elaborate?

I put a link there. The configuration has a syntax which can be systematically documented. Inside it there are enumerations, defaults and optionals. You explanation is in natural language and has a particular logic. I would also like something concise and systematic.

Do you mean literally? And if so, which ticket?

I'll create one so that future users can resolve the issue until the documentation is resolved.


Duplicated thumbnails

If you set loop:true when using lightGallery(); with the slider, the first and last thumbnails are duplicated.
"All photos (x number)" also counts 2 more photos than there is, because of the two duplicated thumbs.

Hi,
When we set loop:true and mode:'slide' lightslider will duplicate first and last slides for enabling carousel functionality.
All cloned slides will have class .clone and all other slides will have .lslide class.
You can use lightGallery's selector option to avoid cloned slides.
Ex:

$('#imageGallery').lightSlider({
        gallery:true,
        onSliderLoad: function(el) {
            el.lightGallery({
                selector: '#imageGallery .lslide' // only #imageGallery .lslide will be added in to the lightGallery
            });
        }
    });

Yep, that solved it. Thank you!

The plugin is in conflict, when enlarging the image the thumbnails multiply, followed the instructions of configuration and at first it went well, but in looping of the DB they multiply, but the amount of images in the page is correct. many .clones


subtree: Need a tutorial for new layer

The subtree doc is great and introduce the develop flow on existing openbmc.
But I do not know how to add a new layer to the combo, e.g. if a (new) system vendor foo adds a new machine bar.
To do it right with openbmc's subtree:

They will have their own repo meta-foo with machine layer meta-bar.
They need to know how to correctly add this subtree into openbmc

This issue is to ask for an introduction about the above 2, so system vendors know how to do it correctly based on openbmc's subtree work flow.

FYI @dcobbley

@mine260309 您好，对于厂商没有提供meta-foo(yocto方式构建)的方案，需要怎么做？ 个人可以移植吗 ？

@geissonator How to add a new meta-foo with new cpu ? Thx.

@WangKaiwh Please use English so that all the community could read the comments.
As far as I know, when a new layer is added, Brad takes care of the subtree. Hopefully @bradbishop could share some information about this.

We no longer use subtrees.


Trigger manifest validation/update on client reported hash mismatch

Description of the new feature/enhancement
This feature represents the back-end services work to support https://github.com/microsoft/winget-cli/issues/870 Provide mechanism to report SHA256 mismatch represents the client work to provide notification for hash mismatches.

Exclude for github.com. Because it is different URL when the newer version releases.


Enabling JSON column for groupBy in time series and proper handling f…

Commit enables JSOn column in groupBy expressions.
Avoid divide by zero exception by checking step second for 0.
Validated the changes manually.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (738c738).
Report is 1119 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (738c738). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (738c738)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14141       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Consider pandas.NA

As an alternative to ss.INT_NAN, could reuse pd.NA:
https://pandas.pydata.org/docs/user_guide/integer_na.html

Tested, too slow