Some elements are flipping

Great plugin, love it.
One small issue.  When we use the plugin, some elements are being vertically flipped. Is there any trick where w can clone without having to go back and re-flip everything in the cloned page?

Hi @aarondewald thanks for using my plugin! I am so sorry it did this! I will try to get to the bottom of this... If it's okay with you, do you mind sharing the structure of the buttons? I want to replicate the issue so that I can get to the bottom of it :)

Hi Sevanus,  No worries, it's a handy little tool.
It's sitting in a container that looks like this:

It renders like this...

Anything that's in the CTA auto-layout layer is flipped.  We have a variant that contains some text, that gets flipped too.
Thanks again!

Thanks for the elaboration! I'll try to fix it ASAP :) /Steve

Hi @aarondewald, I tried recreating the structure based on your screengrab, and I was unable to reproduce the issue:
https://www.figma.com/file/wf4IDwjoSsksaBxKSZjtKV/PageClone-Debugging?node-id=2%3A2&viewport=519%2C350%2C1
Nonetheless, I have a feeling that I may not have the exact properties as per your design. I am not sure how feasible this is, but is there a chance you can share with me a separate copy of a file containing the problematic design elements? If I can't reproduce it, it's quite difficult for me to debug it properly. You can find my Figma email in my GitHub profile:
https://github.com/stevahnes/
Thanks again!

Hi @aarondewald, I believe the issue is still recurring to you? If yes I really need to be able to replicate it in order to find the root cause. Otherwise, I can't fix it as it works fine in our mockups, both work ones and my personal ones.

Ah! Thanks for following up - I lost track of things. Let me work on getting you a copy so you can see exactly what they are.

On Feb 14, 2021, at 11:52 PM, Stevanus Satria<EMAIL_ADDRESS>wrote:
Hi @aarondewald https://github.com/aarondewald, I believe the issue is still recurring to you? If yes I really need to be able to replicate it in order to find the root cause. Otherwise, I can't fix it as it works fine in our mockups, both work ones and my personal ones.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-778993184, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q.

Ah! Thanks for following up - I lost track of things. Let me work on getting you a copy so you can see exactly what they are.

On Feb 14, 2021, at 11:52 PM, Stevanus Satria<EMAIL_ADDRESS>wrote:
Hi @aarondewald https://github.com/aarondewald, I believe the issue is still recurring to you? If yes I really need to be able to replicate it in order to find the root cause. Otherwise, I can't fix it as it works fine in our mockups, both work ones and my personal ones.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-778993184, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q.

Hello @aarondewald, have not heard from you in a while! I believe the issue is still there? Is it possible to get the sample file? And if it's still reproducible do you observe it in all of your prototypes?

Yes, and I’ve actually encountered some other issues happening as well:
Components are flipping vertically
Transparency is not maintained
Rare, but sometimes the layout massively changes.
This occurs when something is a component and we clone while deleting hidden layers and locking the objects
Can you reach out to me privately so I can invite you to our project for review?

On Mar 11, 2021, at 2:10 AM, Stevanus Satria @.***> wrote:
Ah! Thanks for following up - I lost track of things. Let me work on getting you a copy so you can see exactly what they are.
On Feb 14, 2021, at 11:52 PM, Stevanus Satria @.*** @.***> wrote:
Hi @aarondewald https://github.com/aarondewald https://github.com/aarondewald https://github.com/aarondewald, I believe the issue is still recurring to you? If yes I really need to be able to replicate it in order to find the root cause. Otherwise, I can't fix it as it works fine in our mockups, both work ones and my personal ones.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #13 (comment) https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-778993184, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q.
Hello @aarondewald https://github.com/aarondewald, have not heard from you in a while! I believe the issue is still there? Is it possible to get the sample file? And if it's still reproducible do you observe it in all of your prototypes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-796586592, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMDGPGCCAF5VKVFGZVLTDCCHTANCNFSM4XA2ZS6Q.

Yes, and I’ve actually encountered some other issues happening as well:
Components are flipping vertically
Transparency is not maintained
Rare, but sometimes the layout massively changes.
This occurs when something is a component and we clone while deleting hidden layers and locking the objects
Can you reach out to me privately so I can invite you to our project for review?

On Mar 11, 2021, at 2:10 AM, Stevanus Satria @.***> wrote:
Ah! Thanks for following up - I lost track of things. Let me work on getting you a copy so you can see exactly what they are.
On Feb 14, 2021, at 11:52 PM, Stevanus Satria @.*** @.***> wrote:
Hi @aarondewald https://github.com/aarondewald https://github.com/aarondewald https://github.com/aarondewald, I believe the issue is still recurring to you? If yes I really need to be able to replicate it in order to find the root cause. Otherwise, I can't fix it as it works fine in our mockups, both work ones and my personal ones.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #13 (comment) https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-778993184, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q https://github.com/notifications/unsubscribe-auth/ABUDJMEW4KO4D4WOMT2ZIP3S7DADJANCNFSM4XA2ZS6Q.
Hello @aarondewald https://github.com/aarondewald, have not heard from you in a while! I believe the issue is still there? Is it possible to get the sample file? And if it's still reproducible do you observe it in all of your prototypes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/stevahnes/figma-plugins/issues/13#issuecomment-796586592, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUDJMDGPGCCAF5VKVFGZVLTDCCHTANCNFSM4XA2ZS6Q.

Hi @aarondewald, oh dear that's bad. How can I reach out to you personally? Really wanna get this fixed!

@aarondewald transparency should be fixed in v2.2.11; I missed out copying the values of the parent frames. The others are a bit trickier to debug and this weekend I am quite packed, so didn't have time to trace everything. I suspect it's related to the plugin not handling auto-layout properly. I'll continue working on it :)

@aarondewald the flipping elements bug is fixed v2.2.12; I rewrote the detachInstance logic, so instead of whitelisting items to deep clone I blacklist items to not deep clone. The last one is really tricky. I'll keep working on it!

Hi @aarondewald, been busy with work and looking for a new rental unit, so apologies for the delay with the last bug fix. I will try to get some time this coming weekend.

@aarondewald hello! Apologies for the 3 weeks delay. Finally got the chance to look into it.
I found that the massive layout changes is actually due to the autolayout frames width not being copied properly. The quickest fix, for you, is to select all the "Answer Body" frames and drag it back to the right width, and the layout will be fixed. However, on my end I will definitely be looking into why the width and height aren't copied properly.


!global is redundant

the use of !global here does nothing: https://github.com/zurb/foundation/blob/master/scss/foundation/_functions.scss
and can be removed. $modules is already defined on the global scope and therefore modifications to it within the supports mixin are global.

Are you referring to line 14 or line 18, or both?

both, mine seems to work fine without it there at all.

Check your CSS, you probably have duplicate output. (Try searching for html ,body specifically, since that will definitely output more than once.)
I believe line 14 is unnecessary because accessing the global scope is automatic, but modifying it is not. Load this gist to see an example. If you remove !global from line 7, the change to $var won't be applied globally.

thanks @gakimball for the clarification about how global scope works. This must be a bug in my implementation then (I am not using the canonical implementation). Sorry for the trouble.

Ah yeah, I forgot to mention that libsass doesn't have the changes to variable scope yet; this is only for Ruby Sass. Thankfully our exports() mixin pretty much works the same either way.


Improve error message

This error occurs when the database url isn't filled. We need to throw with a better message before that happens - also take the opportunity to test others for other vague errors

the solutions is to add a try block to line 80 in ./src/index.ts


Added jit_var_loop_update_inner_in to fix aliasing case

This is the required function for 282

FYI, this commit introduced a reference leak fixed in commit 46bf1f05bfc7. Is it possible that you have reference warnings turned off on your end?


Can you place add the slide deck in the link. It does not display any slides now

Can you place add the slide deck in the link. It does not display any slides now

fixed


LoRaWAN Config Request: No CFList on EU868

There are some LoRaWAN devices being sold for regions like Europe, where they only know how to function on 3 channels. This is technically LoRaWAN compliant and therefore we need a way for the user to disable CFList (which otherwise expands the device to use 5 additional channels).

Is that the option you are talking about?

We only support disabling for US915 we would need to add support for EU868

internal ref: 10293

Thanks for raising this issue, we have come up with a plan and have put added it to our backlog.


Are Azure AD B2C's Display Claims still in preview?

In this article, Display Claims have been available and marked as 'in preview' since November 22, 2019 [919f20bb].
According to AD B2C developer notes, the related feature 'Display Controls' has been GA since April 25, 2021 [23add8f2].
Is this note about 'in preview' out of date?
If so, requesting it to be fixed. I can submit a PR with the one line deleted if that is sufficient.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1c33bed9-7e41-92cb-e093-80e5fda0e718
Version Independent ID: 94d903c4-a70f-5357-53b4-6d17afee2aaa
Content: Define a self-asserted technical profile in a custom policy - Azure AD B2C
Content Source: articles/active-directory-b2c/self-asserted-technical-profile.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@lirichard
Thanks for your feedback! We will investigate and update as appropriate.

@lirichard
it is also possible to make these changes yourself, if you are interested. Doing so will improve our documentation, and it will add you as a contributor to the document.
In case you're interested, these are the steps to do so:
Navigate to the page of interest
Select the "Edit" button at the top right of the page
Select the "Pencil" icon on the right
Modify the text within the text box in markdown format - more info: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Name your file change and provide a description, if necessary
Select "Propose file change"
Select "Create pull request" on the 'Comparing changes' page
Select "Create pull request" on the 'Open a pull request' page
You can find a GIF that demonstrates the end-to-end process for submitting changes here: https://aka.ms/editsqldocs.

@lirichard
Thanks for contributing towards enhancement of document. Changes performed by you, will reflect in the document itself, once approve by author.
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Dear @lirichard, thanks for the feedback. I'm updating the article removing the public preview note. A new version will publish later today. If you have any questions or need further information, please open new GitHub issue


Angular: useObjectWrapper gets generated with incorrect input for object

I am interested in helping provide a fix!
Yes
Which generators are impacted?

[ ] All
[X] Angular
[ ] HTML
[ ] Preact
[ ] Qwik
[ ] React
[ ] React-Native
[ ] Solid
[ ] Stencil
[ ] Svelte
[ ] Vue
[ ] Web components

Reproduction case
Can't reproduce in fiddle, it probably uses previous version of Mitosis
Expected Behaviour
Object passed as prop in mitosis jsx is generated correctly in Angular component.
Actual Behaviour
When I use object in mitosis jsx for some prop, example:
tooltipPlacementOptions={{   "positions": ["left", "bottom", "bottom-left"],   "offsets": {       "left": {"topOffset": 0, "leftOffset": -24},       "bottom": {"topOffset": 24, "leftOffset": 0},       "bottom-left": {"topOffset": 24, "leftOffset": 0}   } }}
in generated Angular code it gets generated as input to useObjectWrapper as incorrect js object:
[tooltipPlacementOptions]='useObjectWrapper({ "positions": ["left" }, { "bottom" }, { "bottom-left"] }, { "offsets": {             "left": {               "topOffset": 0 }, { "leftOffset": -24             } }, { "bottom": {               "topOffset": 24 }, { "leftOffset": 0             } }, { "bottom-left": {               "topOffset": 24 }, { "leftOffset": 0             }           } })'
The first array is completely malformed and it makes the generated component impossible to use, as this throws compilation errors.
On very initial investigation it looks like there is some bug in function "handleObjectBindings" for Angular generator.
Additional Information
It looks like only versions 0.2+ are affected. I cannot reproduce this issue neither in Fiddle nor in version 0.1.7, which suggests that this is fairly new bug. "useObjectWrapper" is not generated at all in Fiddle or the mentioned older version.

@lukjab71 can you provide a link to a fiddle containing the broken input, even if the output isn't broken? This will help us reproduce with a concrete example.

cc @sidmohanty11

Hello @lukjab71 thanks for raising this issue. Fiddle uses the latest mitosis version only and you can reproduce this bug if you pass this as a prop to a custom component:
https://mitosis.builder.io/?outputTab=IYOw5grgNsBOQ%3D%3D%3D&code=JYWwDg9gTgLgBAbzgVwM4FMDKMCGN1wC%2BcAZlBCHAEQACARssADYAm6UAdMBAPQjAwIqYKioBuAFAT0AD0iw4bEjmRN4JZADsAxjG6a4AWQCeAYQqRN6TTAAUYcmFQBKRBLhxtETangBtTRwQdAAaOAwYADkg9ABdOABeFAxsPHRbKmx0ADd0KmdJdzgodBhkKANbIo8AHhZgbIA%2Bao84GoAJADEAIThBCDVgMAAFJhxtdGCbAHkwPW9UBIQkKkhheZ8qAC44PyomdBIYKjCqOggYQRAT6nPLigBaA6OqWNOIEhII0R2V5%2BPflRBGBpp8Its4AAGU7%2FUFfUoQh4AJgALIRTncrhCEECICCwQidqiYYcYHDwTtIejbhcrk9Sdjcfj4QC4MTqLCCayqUQiIRGsZkCQajwut1mq02jx6k0igUJIQgA%3D
Will work on a fix soon or please feel free to raise a PR if you would like to contribute, this happens because we are splitting the object with commas "," (we should instead be checking for startBracket - endBracket I think incase of a nested object). Also I don't think we should be using useObjectWrapper for all objects, we should only use it when we are spreading something inside a prop.
https://github.com/BuilderIO/mitosis/blob/main/packages/core/src/generators/angular/index.ts#L126


Add 'npm stop' script and clean up some more processes

This change is

package-lock.json line 43649 at r2 (raw file):
Previously, FoolRunning (Tim Steenwyk) wrote…
 I just want to make sure that was on purpose since I would think orphaned processes would only be a developer problem.

Ooh good catch. Looks like fkill was installed as a dependency, not a devDependency. Matt, would you mind uninstalling fkill and reinstalling with npm install fkill --save-dev or npm install -D fkill (shorthand)? Since fkill isn't used in production, we only need it as a devDependency, meaning it is indicated to run only on build steps and dev stuff and such things.


Incident management API: add "mine" and test_names DB field

[x] Add test_names DB field that accepts an array of strings
[x] Add a boolean "mine" flag to indicate ownership in:
/api/v1/incidents/search - for each incident
/api/v1/incidents/show/<id>

1.0.63~pr700-112 deployed on prod (over 1.0.61~pr697-105)


elf: dump dwarf debug output

When kernel verifier complains, dump the kernel log and also output the dwarf info along with it, so we can correlate the code line that causes issues. Eases development.

Looks like the recent BTF support in LLVM and kernel should facilitate this type of debugging, which makes dwarf support unnecessary.

Yeah, lets close it. llvm-objdump tool will additionally also provide C source annotation, so no need to duplicate this into the loader anymore.


Solved merge conflicts

Description
[Provide a brief overview of the changes made in this PR. Be sure to mention any key functionality, improvements, or bug fixes.]
Related Issue

[ ] Is this related to a specific issue? Is so please specify:

Type of Changes
Use a check for ✓ the following type of changes:

Type

✓
:bug: Bug fix

✓
:sparkles: New feature

✓
:hammer: Refactoring

:100: Add tests

✓
:link: Update dependencies

:scroll: Docs

Updates
Before
[If applicable, include a picture of the behavior before the changes were made. I.e. a screenshot of the behavior before the changes were made.]
After
[I.e. a screenshot of the behavior after the changes were made.]
Testing Steps / QA Criteria
[Describe the steps taken to test upcoming changes. Describe any additional testing that needs to be done beyond the steps outlined above. This might include manual testing, exploratory testing, or other types of testing that can't be easily automated.]
Checklist:

[ ✓] This PR is up to date with the development branch, and merge conflicts have been resolved
[ ✓] My code follows the style guidelines of this project
[✓ ] I have executed npm run lint and resolved any outstanding errors.
[ ✓] I have performed a self-review of my own code
[ ✓] I have commented my code, particularly in hard-to-understand areas
[ ✓] My changes generate no new warnings

Package.json and package-lock.json merge conflict errors required manual intervention. Client/package-lock.json needed to be reset to the ancestor to resolve the merge conflict. Commit's successfully merged. Thank you @isomer04 !!


how to log sql script in development environment.

Description
when use Z.EntityFramework.Plus.EFCore how to log sql script to terminal in development environment.
in development environment when I use Microsoft.EntityFrameworkCore, I can find sql script in terminal.
Further technical details

EF Core version: 3.0
EF Plus version:  3.0.13

Hello @netcore-jroger ,
At this moment, we do not use yet Interceptor introduced in EF Core 3.x
However, we will look if that's possible.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Is there some hacking skills to do?


Fixed functions-simulate command

I would like to see if we can avoid the version warnings entirely, but I do not believe it is a blocker for merging this PR, given there are many Solidity compiler warnings already that users should ignore.
I will let Justin give final approval for the PR before merging, just in kase 😉 he knows the solution.


Make KAST preprocessing pipeline explicit in _module_to_kore

Define class KompilerPass
Implement KAST preprocessing steps in terms of KompilerPass
Refactor simplified_module to use a Sequence[KompilerPass]

LGTM. I see that it seems the only non-SingleModulePass are AddAnywhereAtt and AddPrioritiesAtt? The anywhere attribute one could likely be solved by requiring the user to add it to the symbol that is an anywhere symbol, similar to how we do macro or alias, perhaps? But maybe that's not always possible with the uses of that attribute, which we'd have to audit.

The anywhere attribute one could likely be solved

Opened an issue:

runtimeverification/k#4132


5/20 presentation

Pdf와 ipynb 파일 올렸습니다!

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

@guichana99 님 오늘 훌륭한 발표 감사합니다!


Invoke s2n_verify_host_fn callback for SAN URI

Now when this field is encountered in the remote cert during hello,
the callback is invoked for validation purposes.
Issue # (if available):
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (san_uri_validate_test@0db5475). Click here to learn what that means.
The diff coverage is n/a.


Migrating Angular Material to v12 does not remove old import syntax

Which @angular/* package(s) are the source of the bug?
upgrade
Is this a regression?
No
Description
I upgraded my Angular app to v12, and since I am using Material, I upgraded Material as well.
In the v12 announcement article you said that Material now expose new @use syntax and upgrade should migrate syntax automatically. You also added code example of the new VS old syntax.
So basically @import '~@angular/material/theming; should be replaced with @use '~@angular/material' as mat;.
When I checked changes after upgrade finished successfully, I noticed that in the styles.scss the @use '~@angular/material' as mat; line were added, BUT @import '~@angular/material/theming; line was NOT removed. So now, I have both @use and import in my styles.scss file.
Shouldn't @import '~@angular/material/theming; be removed? As I understand, it will import the same thing twice, so it can only increase the size of the file.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
Angular CLI: 12.2.13
Node: 14.15.1
Package Manager: npm 6.14.15
OS: win32 x64

Angular: 12.2.13
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.13
@angular-devkit/build-angular   12.2.13
@angular-devkit/core            12.2.13
@angular-devkit/schematics      12.2.13
@angular/cdk                    12.2.12
@angular/material               12.2.12
@schematics/angular             12.2.13
rxjs                            6.5.5
typescript                      4.3.5

Anything else?
No response

The @import usages should've been removed, but it's possible that your code was written in a way that our migration didn't for. You should be able to remove the @import yourself.

I think the code had pretty basic structure. Here is the diff of changes applied after the upgrade:

You can see that @import '~@angular/material/theming; was the first code in the file.
Tnx for the answer. I will remove @import myself.

I suspect that the comment might have thrown it off.

I wasn't able to reproduce it in our unit tests. I suspect that you might've been running an older version of the migration that didn't include https://github.com/angular/components/pull/23004.


Can't Import using "import discord"

The Program just spits out "ModuleNotFoundErroe: No module named 'discord'
Please fix when possible as I'm trying to run a discord bot from my 3ds.

Did you copy over the discord module and dependant modules to your device?


[community:r] add 'quit-with-status' argument to BiocCheck

This PR will add an argument for the proper exit code from BiocCheck("*.tar.gz", 'quit-with-status'=TRUE).
Without it, all checks will have a 0 exit code whether or not the tests fail.
cc-JJJJ: @jimhester @joepvd @jeroen @joecorcoran

bump
@jimhester @joecorcoran @joepvd @jeroen


Convert wkt types to geo types

For conversions that fail I use a custom function try_into_geometry instead of custom TryInto trait to not generate conflicts when TryInto will be stable

bors r+

excited to have this!


Dont require email confirmation for new users using google auth with …

…domain restriction
We use G Suite for all our users, we have restricted logins to our own domain only via the "registration restrict" setting and so we don't want to use verification emails.
This is the most basic implementation (which we're now using), please let me know if there is any appetite for this change and if so, if you'd like any extra settings. For example perhaps we could just have an extra setting like "Don't use verification emails with Google login when using domain restriction" ?

Similar change made in #966 disabling email verification for social logins

Thanks for offering this pull request @thomseddon and sorry I never replied to this earlier, I could swear I had posted my thoughts but it appears not.
I didn't accept this implementation since:

It's very google specific and I'm trying to avoid provider specific options where possible.
It infers that all admins will always trust google auth fully and does not provide the option to still have emails confirmed as an extra layer.

Since the time this was opened an alternative approach has been implemented which allows auto-confirmation of each social service. You could enable this functionality by adding:
GOOGLE_AUTO_CONFIRM_EMAIL=true

to your .env file.
Details of this can be found here.
Sorry again for my lack of response.

No problem, that's perfect! Thanks


fixes for ConsMarkovModel, example, tests

Introducing DiscreteDistribution broke the ConsMarkovModel
This PR addresses #632 and (currently, partially) #627

PR pileup strikes again.  We need to remove the reference to timeFwd() in the test.


fixed timestamp parsing method for communication_disabled_until

changed the first if condition so that timestamps without dots will be parsed right, like this one: 2022-01-12T13:56:05+00:00.
this could be a thing to be added to unit tests.
hopefully it doesn't break something :)
fixes #203

has this been tested and does it break other timestamp formats with the . part?

i've tested it with member.joined_at and this has worked

i've now tested it with:
json j;
	j["test1"] = "2022-01-12T13:56:05+00:00";
	j["test2"] = "2022-01-12T13:56:05.32409+00:00";
	time_t t;
	dpp::set_ts_not_null(&j, "test1", t);
	cout << "Parsed time 1: " << t << endl;
	dpp::set_ts_not_null(&j, "test2", t);
	cout << "Parsed time 2: " << t << endl;
	```
and they both print

Parsed time 1:<PHONE_NUMBER>
Parsed time 2:<PHONE_NUMBER>

looks good to me, thanks so much for the effort spent in identifying and fixing this!


Nefarious WizOps [April Fools]

About the PR

Adds Magic to the Uplink.
For regular Syndicates, they recieve the ability to purchase the RGB Staff. RGB to the People!
For Nuclear Operatives, they recieve the ability to purchase
Spellbooks (Knock, Forcewall, Blink, Smite, Fireball, Spawn), typically being the most expensive.
Staffs (Healing, Entrance, RGB), residing in the middle, price-wise.
Wands (Fireball, Smite, Entrance, Polymorph, Cluwne-ification), being in the lower-to-middle area of Price.
And Misc Magic Items, (Wizard Hardsuit, Magical Lamp, Rune Scroll, Wand Belt), for varying prices, usually being cheap.
Also contains the tweaks from https://github.com/space-wizards/space-station-14/commit/979bdfcfa69d0c9e1199e3b6a9393a86a43c5417 and https://github.com/space-wizards/space-station-14/commit/311a027797fd6f8c515e029b4e358bf32fdedbe1, since they still need to be added to keep us up-to-date :godo:
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: blankmann, and Whisper

add: The Syndicate and the Space Wizard's Federation have made a temporary pact to supply their Agents and Operatives with cool thingamabobs. "...It would be funny, I think...", says a Wizard's Federation representative.
fix: CentCom has changed clothing suppliers. CentCom clothing will no longer appear in wardrobe restock boxes from cargo.

You're gonna need to rebase this PR off of april-fools-release.


Generated relationship missing

Thanks for your Great work Matt!
I am testing
https://github.com/oktadeveloper/generator-jhipster-ionic/releases/tag/v4.0.0-beta.2.
It generated the  nms-alert-type.model.ts
export class NmsAlertType implements BaseEntity {
    constructor(
        public id?: number,
        public level?: number,
        public name?: string,
        public colour?: string,
        public soundName?: string,
      public **domain**?: BaseEntity,
      public **tenant**?: BaseEntity,
    ) {
    }
}

(Note: doesn't generate the **domain** just domain)
and in the  nms-alert-type-update.ts
this.form.patchValue({
            id: nmsAlertType.id,
            level: nmsAlertType.level,
            name: nmsAlertType.name,
            colour: nmsAlertType.colour,
            soundName: nmsAlertType.soundName,
         nmsDomain: nmsAlertType.**nmsDomain**,
         nmsTenant: nmsAlertType.**nmsTenant**,
       });

gives this error
ERROR in src/app/pages/entities/nms-alert-type/nms-alert-type-update.ts(72,37): error TS2551: Property 'nmsDomain' does not exist on type 'NmsAlertType'. Did you mean 'nmsdomain'?
If I change nms-alert-type.model.ts
public domain?: BaseEntity,
public tenant?: BaseEntity,
to
public nmsDomain?: BaseEntity,
public nmsTenant?: BaseEntity,
Solves the error :-)
Is it difficult to implement in the generator?

Do you have a JDL file with your entitities that I can use to try and reproduce this problem? If not, can you run ”jhipster info” on your JHipster project and paste the output in this issue?

On Jun 23, 2019, at 01:15, Ines Gomes<EMAIL_ADDRESS>wrote:
Thanks for your Great work Matt!
I am testing
https://github.com/oktadeveloper/generator-jhipster-ionic/releases/tag/v4.0.0-beta.2.
It generated the nms-alert-type.model.ts
export class NmsAlertType implements BaseEntity {
constructor(
public id?: number,
public level?: number,
public name?: string,
public colour?: string,
public soundName?: string,
public domain?: BaseEntity,
public tenant?: BaseEntity,
) {
}
}
(Note: doesn't genererte the domain just domain)
and in the nms-alert-type-update.ts
this.form.patchValue({
id: nmsAlertType.id,
level: nmsAlertType.level,
name: nmsAlertType.name,
colour: nmsAlertType.colour,
soundName: nmsAlertType.soundName,
nmsDomain: nmsAlertType.nmsDomain,
nmsTenant: nmsAlertType.nmsTenant,
});
gives this error
ERROR in src/app/pages/entities/nms-alert-type/nms-alert-type-update.ts(72,37): error TS2551: Property 'nmsDomain' does not exist on type 'NmsAlertType'. Did you mean 'nmsdomain'?
If I change nms-alert-type.model.ts
public domain?: BaseEntity,
public tenant?: BaseEntity,
to
public nmsDomain?: BaseEntity,
public nmsTenant?: BaseEntity,
Solves the error :-)
Is it difficult to implement in the generator?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Matt this is a short version
/**
 * The AlertType entity.
 * level Integer required, 1,2,3,4
 * name  String required, ASSIST,CALL,PRIORITY,EMERGENCY, Crash...
 */
entity NmsAlertType {
  level Integer required,
  name String required,
  colour String,
  soundName String
}

entity NmsDomain {
  name String required,
  latitude String,
  longitude String,
  address String,
  domainEmail String,
  tag String,
  description String,
  notes String,
  domain String,
  selfAdmin Boolean, // "User Zone Self-Admin" with 2 Options - Allow or Deny
  timeZone String, // List all zones (UTC), not just London, Paris, Helsinki
  ipApi String,
  ipCancel String,
  loginExtension String,
  emailWelcome Blob,
  emailRenewPassword Blob,
  emailAccessToPatient Blob,
  lastModifiedDate ZonedDateTime,
  lastModifiedBy String
}

/**
 * The Tenant entity.
 * a Tenant refers to a unit in the domain.
 * it is a more or less independant part of the domain, possibly a building belonging to the domain.
 */
entity NmsTenant {
  name String required,
  latitude String,
  longitude String,
  address String,
  timeZone String,
  selfAdmin Boolean, // User Zone Self-Admin" with 2 Options - Allow or Deny
  domainOwnership String,
  restrictLoginsToIP String,  // Restrict Logins to IP Address:
  lastModifiedDate ZonedDateTime,
  lastModifiedBy String,
  active Boolean
}

relationship ManyToOne {
  NmsAlertType{domain} to NmsDomain,
  NmsAlertType{tenant} to NmsTenant
}

I have sent the complete model through Linkedin
Is really big ...  When I run the first yo jhipster-ionic:entity command, it prompts me for the existing app and path, then it prompts me to update the entity. When I hit the last question, it stops responding to my input and I'm unable to proceed. Did you experience this issue? I'm unsure how to get passed it.
yo jhipster-ionic:entity NmsDomain

The entity NmsDomain is being created.

? Do you want to generate this entity from an existing app? Yes
? Enter the path to your app's root directory: ../backend

Found the .jhipster/NmsDomain.json configuration file, entity can be automatically generated!

? Do you want to update the entity? This will replace the existing files for this entity, all your custom code will be o
verwritten (Use arrow keys)
❯ Yes, re generate the entity
  Yes, add more fields and relationships
  Yes, remove fields and relationships
  No, exit

@mraible I was experiencing that and to solve it I have to upgrade yo

@Entrecampos I tried to fix it in #103. It likely fixes the compilation issues. Here's how to try it locally:
git clone -b entity-relationships https://github.com/oktadeveloper/generator-jhipster-ionic.git
cd generator-jhipster-ionic
npm link

yo jhipster-ionic
cd ionic4j # (where ionic4j is the name of your app)
npm link generator-jhipster-ionic
yo jhipster-ionic:entity $entityName


FIXED - District name typos for Jammu & Kashmir

Description of PR
Fixed the names of 5 districts of Jammu & Kashmir which were spelled incorrectly.
District Names Fixed
Bandipore => Bandipora,
Baramula => Baramulla,
Badgam => Budgam,
Punch => Poonch,
Shupiyan => Shopian
Reference
Wikipedia

@tauseefsshah Thank for the PR, but please read this as well https://github.com/covid19india/covid19india-react/issues/662#issuecomment-609377552.
Only changing the name in the map files will break data association with the API. For example, you can see that after your changes, Baramulla will no longer be coloured on the map. This requires changes in the API as well


Using helm to install Prometheus tooltip errors

[root@k8s-master01 prometheus-operator]# helm install --name kube-prometheus --namespace=monitoring helm/kube-prometheus
Error: found in requirements.yaml, but missing in charts/ directory: alertmanager, prometheus
[root@k8s-master01 prometheus-operator]# pwd
/root/prometheus-operator
[root@k8s-master01 prometheus-operator]# ls helm/
alertmanager  grafana  kube-prometheus  prometheus  prometheus-operator
Error as above, I don't know where there is a problem. I have the directory below helm directory, but still prompted errors,help me...

I have some trouble.

There are some known issues with the helm charts, I recommend reading through this article: https://itnext.io/kubernetes-monitoring-with-prometheus-in-15-minutes-8e54d1de2e13

@brancz Following that article doesn't solve the problem mentioned above. I'm getting this also

@gianrubio ^ I think you have the most experience, could you maybe look into this?

comment the lines 2 to 9 on kube-prometheus/requirements.yaml and run the command again. This will be fixed after #676 merged.

Also, helm upgrade --install --namespace=monitoring --set rbacEnable=false kube-prometheus helm/kube-prometheus
Fails, as the required Helm charts don't get passed rbacEnable=false. Is there a way to pass this down, or does this essential make the flag useless?

@rawkode Use --set exporter-kube-state.rbacEnable=false.

@rawkode #776 fixed the helm dependencies.

@gianrubio Yeah, so the Helm install works now - but sadly none of the kube-exporters ever enter a healthy state and there are no endpoints for prometheus or alertmanager services.

# values.yaml
prometheus:
  rbacEnable: false

exporter-kube-state:
  rbacEnable: false

# CI
- helm init --client-only
- helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- helm upgrade --install --namespace=monitoring -f values.yaml kube-prometheus coreos/kube-prometheus

Am I just missing configuration, am I just being silly? I'm really keen to get this working and willing to help in anyway, if it's not just me being daft.

@rawkode can you elaborate what you mean by "a healthy state"? Are the pods crashlooping?

NAME                                                   READY     STATUS              RESTARTS   AGE
alertmanager-alertmanager-0                            0/2       ContainerCreating   0          12h
grafana-grafana-5fdf676c68-fftsx                       2/2       Running             0          15h
kube-prometheus-exporter-kube-state-659754647d-fnc5w   0/2       ContainerCreating   0          10s
kube-prometheus-exporter-node-4jr7v                    0/1       CrashLoopBackOff    1          10s
kube-prometheus-exporter-node-927lq                    0/1       CrashLoopBackOff    1          10s
kube-prometheus-exporter-node-9zn72                    0/1       CrashLoopBackOff    1          10s
kube-prometheus-exporter-node-rkc5v                    0/1       Error               1          10s
kube-prometheus-exporter-node-xsjdw                    0/1       CrashLoopBackOff    1          10s

Can you check the logs of one of those containers? Sounds like something is actually mis-configured.

The only error in the logs is the one mentioned above, every exporter is the same

I believe that was introduced by this PR: https://github.com/coreos/prometheus-operator/pull/754
I think we may have missed the v in the tag.

AlertManager logs also
  Warning  FailedMount            28s (x10 over 4m)  kubelet, gke-production-preemptible-pool-2aeb813f-28kc  MountVolume.SetUp failed for volume "config-volume" : secrets "alertmanager-alertmanager" not found
  Warning  FailedMount            20s (x2 over 2m)   kubelet, gke-production-preemptible-pool-2aeb813f-28kc  Unable to mount volumes for pod "alertmanager-alertmanager-0_monitoring(9050459e-d032-11e7-8074-42010a84003b)": timeout expired waiting for volumes to attach/mount for pod "monitoring"/"alertmanager-alertmanager-0". list of unattached/unmounted volumes=[config-volume]
  Warning  FailedSync             20s (x2 over 2m)   kubelet, gke-production-preemptible-pool-2aeb813f-28kc  Error syncing pod

That one looks like the alertmanager configuration is not created. @gianrubio are you aware whether the charts create the alertmanager config Secret?

@gianrubio are you aware whether the charts create the alertmanager config Secret?
Not sure if the ./helm upgrade command can handle the change, just installed a fresh chart using helm install and it created the secret. However the node-exporter are in a crashLoopbackOff state.

I'll submit a PR to fix that, #754 broked that.
 ./kubectl logs -n monitoring kube-prometheus-exporter-node-70n1w
flag provided but not defined: -path.procfs
Usage of /bin/node_exporter:

PR submitted
https://github.com/coreos/prometheus-operator/pull/781

Any idea how to resolve the secret problem? It looks like the operator should be creating this

Regarding the Secret problem, can you check whether a Secret called alertmanager-<alertmanager-object-name> exists in the same namespace as the Alertmanager object?

It does
NAME                           TYPE                                  DATA      AGE
alertmanager-kube-prometheus   Opaque                                1         36m

but the pod is looking for alertmanager-alertmanager

That's curious, from the templates it looks like the Alertmanager name, should be the same as the helm release name. And the Secret also seems to be correctly templated.

I don't know if it's useful, but this is the output of describe alertmanager kube-prometheus
Name:         kube-prometheus
Namespace:    monitoring
Labels:       alertmanager=kube-prometheus
              app=alertmanager
              chart=alertmanager-0.0.5
              heritage=Tiller
              release=kube-prometheus
Annotations:  <none>
API Version:  monitoring.coreos.com/v1
Kind:         Alertmanager
Metadata:
  Cluster Name:
  Creation Timestamp:             2017-11-23T09:45:56Z
  Deletion Grace Period Seconds:  <nil>
  Deletion Timestamp:             <nil>
  Resource Version:               12855941
  Self Link:                      /apis/monitoring.coreos.com/v1/namespaces/monitoring/alertmanagers/kube-prometheus
  UID:                            1abb7e56-d033-11e7-8074-42010a84003b
Spec:
  Base Image:    quay.io/prometheus/alertmanager
  External URL:  http://kube-prometheus-alertmanager.monitoring:9093
  Paused:        false
  Replicas:      1
  Resources:
  Version:  v0.5.1
Events:     <none>

StatefulSet config looks incorrect:
Name:               alertmanager-alertmanager
Namespace:          monitoring
CreationTimestamp:  Sat, 18 Nov 2017 18:20:23 +0000
Selector:           alertmanager=alertmanager,app=alertmanager
Labels:             alertmanager=alertmanager
                    app=alertmanager
                    chart=alertmanager-0.0.4
                    heritage=Tiller
                    release=alertmanager
Annotations:        <none>
Replicas:           1 desired | 1 total
Pods Status:        0 Running / 1 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  alertmanager=alertmanager
           app=alertmanager
  Containers:
   alertmanager:
    Image:  quay.io/prometheus/alertmanager:v0.7.1
    Ports:  9093/TCP, 6783/TCP
    Args:
      -config.file=/etc/alertmanager/config/alertmanager.yaml
      -web.listen-address=:9093
      -mesh.listen-address=:6783
      -storage.path=/etc/alertmanager/data
      -web.external-url=http://alertmanager-alertmanager.monitoring:9093
      -web.route-prefix=/
      -mesh.peer=alertmanager-alertmanager-0.alertmanager-operated.monitoring.svc
    Requests:
      memory:     200Mi
    Liveness:     http-get http://:web/api/v1/status delay=0s timeout=3s period=10s #success=1 #failure=10
    Readiness:    http-get http://:web/api/v1/status delay=3s timeout=3s period=5s #success=1 #failure=10
    Environment:  <none>
    Mounts:
      /etc/alertmanager/config from config-volume (rw)
      /var/alertmanager/data from alertmanager-alertmanager-db (rw)
   config-reloader:
    Image:  quay.io/coreos/configmap-reload:v0.0.1
    Port:   <none>
    Args:
      -webhook-url=http://localhost:9093/-/reload
      -volume-dir=/etc/alertmanager/config
    Limits:
      cpu:        5m
      memory:     10Mi
    Environment:  <none>
    Mounts:
      /etc/alertmanager/config from config-volume (ro)
  Volumes:
   config-volume:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  alertmanager-alertmanager
    Optional:    false
   alertmanager-alertmanager-db:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
Volume Claims:  <none>
Events:         <none>

There seems to be no concept of using the release name within the alertmanager, or prometheus, operators:
https://github.com/coreos/prometheus-operator/blob/master/pkg/alertmanager/operator.go#L283

There seems to be no concept of using the release name within the alertmanager, or prometheus, operators:
https://github.com/coreos/prometheus-operator/blob/master/pkg/alertmanager/operator.go#L283

That code is unrelated. The Prometheus Operator just uses the name you give the objects, which is the release name as that's what's templated via the helm charts.

@rawkode I just reproduced all the steps and I can't reproduce the alertmanager error. Can you do a clean install and see if this solve your issue? I'm working on to have a better helm integration, it will take few days.

@gianrubio What values.yaml did you use?

@gianrubio OK, I worked out why I have this problem. The operators / statefulsets aren't removed during helm delete --purge, so I assume they were a hangover from before the charts repo

The operators / statefulsets aren't removed during helm delete --purge, so I assume they were a hangover from before the charts repo

Can you fill a new issue about that, we should add a warning about the delete --purge behaviour.

Can you fill a new issue about that, we should add a warning about the delete --purge behaviour.

Starting with Kubernetes 1.8 and v0.14.0 of the Prometheus Operator, this problem will disappear as all resources have the appropriate OwnerReference meaning that when helm delete --purge is run, then the objects will be garbage collected.

I've actually purged everything and deployed again. I've still got the node-exporters failing until the repo is updated.
I can't seem to browse to alertmanager using http://localhost:8001/api/v1/proxy/namespaces/monitoring/services/kube-prometheus-alertmanager:9093
Hopefully this is finally me being silly :joy:
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "no endpoints available for service \"kube-prometheus-alertmanager\"",
  "reason": "ServiceUnavailable",
  "code": 503http://localhost:8001/api/v1/proxy/namespaces/monitoring/services/kube-prometheus-alertmanager:9093
}

I've actually purged everything and deployed again. I've still got the node-exporters failing until the repo is updated.

When the helm charts are merged to master they are not automatically updated, I'm also working on this :)

Any thoughts on why I can't browse to the service?

Not sure, I realise that kube-prometheus is creating a new service that it's already generated by alertmanager (I promisse to fix all this issue).
Could you list the service and endpoints at this namespace?
kubect get svc,ep -n monitoring.

Thanks for your continued help with this, @gianrubio - it's appreciated a whole lot and I'm happy to help with the Helm charts, if possible:
NAME                                      TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
svc/kube-prometheus-alertmanager          ClusterIP   <IP_ADDRESS>   <none>        9093/TCP   1h
svc/kube-prometheus-exporter-kube-state   ClusterIP   <IP_ADDRESS>   <none>        80/TCP     1h
svc/kube-prometheus-exporter-node         ClusterIP   <IP_ADDRESS>   <none>        9100/TCP   1h
svc/kube-prometheus-prometheus            ClusterIP   <IP_ADDRESS>     <none>        9090/TCP   1h

NAME                                     ENDPOINTS        AGE
ep/kube-prometheus-alertmanager          <none>           1h
ep/kube-prometheus-exporter-kube-state   <IP_ADDRESS>:8080   1h
ep/kube-prometheus-exporter-node                          1h
ep/kube-prometheus-prometheus            <none>           1h

I missed one step on the helm packaging, PR will come at the end of the day ;)
Contribution to the helm charts are always welcome.

Thanks :+1:

Curious: are these charts supposed to spin up Grafana also?

@rawkode I don't think it is installed with the kube-prometheus chart today, I believe the Grafana one is separate currently. Feel free to change that :slightly_smiling_face: .

@gianrubio Any update on the node exporters?

It'll be update after #784 be merged

Hi. I Try to install prometeus operator using helm, step by step using this article https://itnext.io/kubernetes-monitoring-with-prometheus-in-15-minutes-8e54d1de2e13.
kubectl create ns monitoring git clone git@github.com:coreos/prometheus-operator.git cd prometheus-operator - This fine.
helm install --name prometheus-operator --set rbacEnable=true --namespace=monitoring helm/prometheus-operator - This fine.
helm install --name prometheus --set serviceMonitorsSelector.app=prometheus --set ruleSelector.app=prometheus --namespace=monitoring helm/prometheus helm install --name alertmanager --namespace=monitoring helm/alertmanager helm install --name grafana --namespace=monitoring helm/grafana - This fine.
helm install --name kube-prometheus --namespace=monitoring helm/kube-prometheus - And here I have error.
Error: found in requirements.yaml, but missing in charts/ directory: alertmanager, prometheus, exporter-kube-api, exporter-kube-controller-manager, exporter-kube-dns, exporter-kube-etcd, exporter-kube-scheduler, exporter-kube-state, exporter-kubelets, exporter-kubernetes, exporter-node, grafana
Maybe I missed some step? Or some step missed in article? Or this is kind of issue?
kubectl get pods --namespace monitoring NAME                                                       READY     STATUS    RESTARTS   AGE alertmanager-alertmanager-0                                2/2       Running   0          10m grafana-grafana-5fdf676c68-mzrgm                           2/2       Running   0          10m prometheus-operator-prometheus-operator-5d86ffb9bf-zw8rm   1/1       Running   0          11m prometheus-prometheus-0                                    2/2       Running   0          10m
All previous step seems work fine.

@xpowerman please see the comment https://github.com/coreos/prometheus-operator/issues/717#issuecomment-343531797
I'm still working to fix all this helm issues

Still same problem for me.
I've just tried to install prometheus-operator from this repo master:
https://github.com/coreos/prometheus-operator
On a GCLoud Kubernetes cluster with autoscaling min nodes 4 max 6.
commands on the new created cluster:
helm init
kubectl create clusterrolebinding permissive-binding --clusterrole=cluster-admin --user=admin --user=kubelet --group=system:serviceaccounts;
kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin<EMAIL_ADDRESS>(after cloning repo)
cd prometheus-operator
kubectl apply -f bundle.yaml
kubectl create namespace monitoring
cd helm
helm install --name prometheus-operator --namespace monitoring --set exporter-kube-state.rbacEnable=false ./kube-prometheus/
And the result still the same as @rawkode
kubectl get pods --namespace=monitoring
NAME                                                       READY     STATUS              RESTARTS   AGE
alertmanager-alertmanager-0                                0/2       ContainerCreating   0          3s
alertmanager-kube-prometheus-0                             1/2       Running             0          3s
dashboard-kubernetes-dashboard-7ffc6f67d4-z4bzt            1/1       Running             0          33m
grafana-grafana-5fdf676c68-gtw67                           2/2       Running             0          11m
kube-prometheus-exporter-kube-state-79886f7544-6jnmq       2/2       Running             0          10m
kube-prometheus-exporter-node-b88xm                        0/1       CrashLoopBackOff    7          11m
kube-prometheus-exporter-node-bv6jt                        0/1       CrashLoopBackOff    7          11m
kube-prometheus-exporter-node-jz9nj                        0/1       CrashLoopBackOff    6          10m
kube-prometheus-exporter-node-npzss                        0/1       CrashLoopBackOff    7          11m
kube-prometheus-exporter-node-xbfhz                        0/1       CrashLoopBackOff    6          11m
kube-prometheus-grafana-5cb5c9cdb8-9zkwr                   2/2       Running             0          11m
prometheus-kube-prometheus-0                               2/2       Running             0          11m
prometheus-operator-prometheus-operator-5d86ffb9bf-fn4c2   1/1       Running             0          12m
prometheus-prometheus-0                                    2/2       Running             0          11m

kubectl describe pod --namespace monitoring kube-prometheus-exporter-node-b88xm
Name:           kube-prometheus-exporter-node-b88xm
Namespace:      monitoring
Node:           gke-xussof-cluster-default-pool-9c62e8bb-f6lr/<IP_ADDRESS>
Start Time:     Mon, 11 Dec 2017 14:29:00 +0100
Labels:         app=kube-prometheus-exporter-node
component=node-exporter
controller-revision-hash=204858866
pod-template-generation=1
release=kube-prometheus
Annotations:    kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"DaemonSet","namespace":"monitoring","name":"kube-prometheus-exporter-node","uid":"3f901855-de77-11e7-90c4-...
Status:         Running
IP:             <IP_ADDRESS>
Created By:     DaemonSet/kube-prometheus-exporter-node
Controlled By:  DaemonSet/kube-prometheus-exporter-node
Containers:
node-exporter:
Container ID:  docker://33c1bc317cd70c786e0f5576916ffc43f316673ec829bc7264f08c97c6007353
Image:         quay.io/prometheus/node-exporter:v0.14.0
Image ID:      docker-pullable://quay.io/prometheus/node-exporter@sha256:b376a1b4f6734ed610b448603bc0560106c2e601471b49f72dda5bd40da095dd
Port:          9100/TCP
Args:
--path.procfs=/host/proc
--path.sysfs=/host/sys
--web.listen-address=<IP_ADDRESS>:9100
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    2
Started:      Mon, 11 Dec 2017 14:39:46 +0100
Finished:     Mon, 11 Dec 2017 14:39:46 +0100
Ready:          False
Restart Count:  7
Limits:
cpu:     200m
memory:  50Mi
Requests:
cpu:        100m
memory:     30Mi
Environment:
Mounts:
/host/proc from proc (ro)
/host/sys from sys (ro)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-mhvd8 (ro)
Conditions:
Type           Status
Initialized    True
Ready          False
PodScheduled   True
Volumes:
proc:
Type:  HostPath (bare host directory volume)
Path:  /proc
sys:
Type:  HostPath (bare host directory volume)
Path:  /sys
default-token-mhvd8:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-mhvd8
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     :NoSchedule
node.alpha.kubernetes.io/notReady:NoExecute
node.alpha.kubernetes.io/unreachable:NoExecute
node.kubernetes.io/disk-pressure:NoSchedule
node.kubernetes.io/memory-pressure:NoSchedule
Events:
Type     Reason                 Age                From                                                    Message

Normal   SuccessfulMountVolume  11m                kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  MountVolume.SetUp succeeded for volume "sys"
Normal   SuccessfulMountVolume  11m                kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  MountVolume.SetUp succeeded for volume "proc"
Normal   SuccessfulMountVolume  11m                kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  MountVolume.SetUp succeeded for volume "default-token-mhvd8"
Normal   Pulled                 11m (x4 over 11m)  kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  Container image "quay.io/prometheus/node-exporter:v0.14.0" already present on machine
Normal   Created                11m (x4 over 11m)  kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  Created container
Normal   Started                11m (x4 over 11m)  kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  Started container
Warning  BackOff                11m (x5 over 11m)  kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  Back-off restarting failed container
Warning  FailedSync             1m (x48 over 11m)  kubelet, gke-xussof-cluster-default-pool-9c62e8bb-f6lr  Error syncing pod

@xussof we're waiting #784 be merged, for now you could edit the node-exporter daemonset and apply the changes #781

Anybody able to come up with solution on this..?
helm install bitnami/kube-prometheus prometheus --values /tmp/prometheus.values --namespace monitoring
Error: failed to download "prometheus" (hint: running helm repo update may help)
Same problem


Broken for @conn based forms

When you define a form with connection data (i.e. <%= form_for @conn, Formulator now fails as it expects a validations key in the source, but a connection does not have validations.
The failure happens on this line

Fix was released with v0.1.7.


feat: vyper support

#5934 Starting with forge, the goal is to be able to compile Vyper contracts and run tests against them. Until stability is reached, a feature flag will gate it.

I'd like to loop in @mattsse & @onbjerg so they can chime in here as well. My personal view is:

Yes, we want this! It's exciting that vyper's getting rust bindings.
Maybe not now—this requires a large refactor in most areas of the project, and we're just undergoing a major refactor regarding types right now, albeit we will be done somewhat soon, but we don't have the bandwith atm.

I greatly appreciate the hard work going into the refactor! I have no other obligations in life at the moment so I can work on the integration all day. Even if it takes a little time, I should be able to do a vast majority of the work

Superseded by https://github.com/foundry-rs/foundry/pull/7953 and https://github.com/foundry-rs/foundry/pull/7981 :)


1.10 Release notes [WIP]

Description

Urgency

[X] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

Will beta releases have their own persistent releases notes? It looks like the URL for the notes might be the same as what I would expect for the 1.10.0 stable release.


Use customElements.get rather than referring to the global for Polymer.DomModule

Reviewed and approved in person by @sorvell


Registers in Tutorial 01

Summary
This PR adds a bit more information on the register naming in the first tutorial.
Details
Added a bit of extra markdown to clarify the register naming.

This PR addresses part of #2

Nice clarifications, thanks Daniel. Looks good to me except for some minor typos.


Benchmark v2

This PR adjusts the benchmark tasks, so they are no longer exploratory, but require large compute.
Running benchmark on SLURM
Big thanks to @LaraFuhrmann for providing the expertise!
I used the command:
$ sbatch --mail-type=END --mem-per-cpu=2000 --time=72:00:00 -o snake.out -e snake.err snakemake --profile ~/simplesnakemake/  --rerun-incomplete -prk --cores 50 -s workflows/WORKFLOW_NAME.smk

together with the snakemake profile (in ~/simplesnakemake/config.yaml):
cluster:
  mkdir -p logs/{rule} &&
  sbatch
    --parsable
    --job-name=bmi-{rule}-{wildcards}
    --cpus-per-task={threads}
    --mem-per-cpu="$(( {resources.mem_mb} / {threads} ))"
    --time="{resources.runtime}"
    --tmp={resources.disk_mb}
    --output=logs/{rule}/{rule}-%j.out.log
    --error=logs/{rule}/{rule}-%j.err.log
default-resources:
        # - partition=<name-of-default-partition>
        # - qos=<name-of-quality-of-service>
  - mem_mb=2000
  - runtime=15
restart-times: 3
max-jobs-per-second: 10
max-status-checks-per-second: 1
local-cores: 1
latency-wait: 60
jobs: 30
keep-going: True
rerun-incomplete: True
printshellcmds: True
scheduler: greedy
# use-conda: True

As today discussed, these are the changes we want to make:
Typos

Binormal -> bivariate normal
Bimodal gaussians -> Bimodal (or think about another name)

Students (dimx, dimy, dof)
Note: all students have identity matrix.
1, 1, 1: 0.22

asinh

2, 2, 1: 0.43

asinh
2, 2, 2: 0.19

3, 3, 2: 0.29

asinh

3, 3, 3: 0.18
5, 5, 2: 0.45

asinh

5, 5, 3: 0.30
Multivariate normal
In the sparse case, drop the blocks XX and YY and name them 2-pair.
Transformed tasks

Replace asinh Student's (the last three)  with the new ones
What to do with spirals: adjust speed by /dimension (mean of chi-squared with the dof = dimension)
Drop the rotated distributions
Drop wiggly

Future work

We don't add multi-wiggly, but think about them for the future work.
Mini-benchmark for normalization

i think this looks pretty mergeable right now, no? lets not make it grow too big


CHEBI:36163, CHEBI:60530, heme a, adding the missing chiral information

Hi Adnan,
I just discovered that the only chiral centre in heme a compounds in ChEBI are flat.
The paper pmid:16204889 elucidates that this is in fact (S). The ligand HEA cited in CHEBI:24479 (heme a) also shows this bond in (S).
So please update all children of CHEBI:24479 with this information.
Curiously, an (S)-ferriheme a (CHEBI:134067) has been created. I suggest to merge this with CHEBI:36183 as all heme a compounds should be in (S) configuration.
The relevant compounds to update are:
CHEBI:36183 ferriheme a
CHEBI:83281 ferriheme a3
CHEBI:83282 ferriheme a3(1-)
CHEBI:60532 ferriheme a(1-)
CHEBI:36163 ferroheme a
CHEBI:61715 ferroheme a(2-)
Cheers,
Kristian

I have now submitted updated structures for all compounds except for CHEBI:61715 where I get an error when loading "Edit Structure"

All of the above entries have now been updated with new structures. Thanks.


Cargo.lock not updated/committed for 0.22.0

trying to build with --locked reports an error, because the version wasn't bumped in the lockfile:
error: the lock file acmed-0.22.0/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

Thank you for the report, I completely missed that.

I just released the version 0.22.1, which should fix this.
Also, I updated the script I use to release a new version so it won't happen again.

that was fast, thanks!


App Clean-Up June 2022

Hi All,
As discussed in the last Solid team meeting, I'm cleaning up the Solid App (https://solidproject.org/apps) page.
I've created notes for each app listed here (https://docs.google.com/spreadsheets/d/1p0opUBL0vRpEdNzDuB8mVy5XTrAbhSdMIzytqn-ef-M/edit?usp=sharing), and I've reached out to each of the developers to alert them of their app's status.
Apps were evaluated based on the criteria listed at the bottom of the apps page (https://solidproject.org/apps). The criteria for an app to be Solid-compatible are:

If identifying users is necessary, they must be able to login using their WebID and pointing to the Identity Provider of their choice
Data consumed by the app should be fetched from Solid Pods if possible
Data generated by the app should be stored in Solid Pods
The interaction between the app, pods, and Identity Provider(s) must be compliant with the Solid specification

Based on this, I sorted the apps into 4 categories:
Super Feature
Super Featured apps will be listed at the top of the "Featured" category. Each of these apps is compatible with both the Old authentication standard, the new authentication standard, and the new-new (2022) authentication standard. Developers of super featured apps received the following in their email:

Your app, {App Name}, is fantastic and I’m going to move it into the featured section.

Feature
Featured apps were compatible with at least one authentication standard but not all, and they had a usable UI that would give a decent first-impression for people exploring Solid for the first time. Developers of featured apps received the following in their email:

Your app, {App Name}, may not work on the most recent version of Solid's auth. Upgrading to https://www.npmjs.com/package/@inrupt/solid-client-authn-browser should make it compatible, and you can test to see if it works by logging into the next-gen community server at https://solidweb.me.

Keep
Apps labeled keep were compatible with at least one authentication standard but not all. Developers of "keep" apps received the following in their email:

Your app, {App Name}, may not work on the most recent version of Solid's auth. Upgrading to https://www.npmjs.com/package/@inrupt/solid-client-authn-browser should make it compatible, and you can test to see if it works by logging into the next-gen community server at https://solidweb.me.

Remove
Apps marked as "Remove" either failed to meet the criteria listed on the apps site in some way or the criteria was un-testable. There were a few standard reasons for this, and I was sure to stress that the decision could be disputed before the page was updated.
Some apps didn't have an option to log in with other Solid servers and forced users into a specific server, thus violating rule 1. Developers received this message in their email:

Your app, {App Name}, may be Solid compatible, but there is no option to log into other Solid compatible Pods, so I’m planning on removing it from the list. You can always reach out to me and tell me if I’m wrong in that assessment. I’ll be happy to add it back.

Some apps encountered errors when testing that prevented me from testing rules 2-4. Developers received this message in their email:

In my testing, your app, {App Name}, encountered some problems that prevented me from being able to use it. {Describe the Error} I am planning on removing it from the list. You can always fix the problem or let me know if I’m incorrect. I’ll be glad to add them back.

Some apps were not Solid-Specific apps. They may have been linked-data related but lacked the ability to work with a Solid Pod. Alternatively, a few were simply landing pages for an organization and not apps.  You can always reach out to me and tell me if I’m wrong in that assessment. I’ll be happy to add it back.

Some apps were not able to authenticate with any Solid server. Developers received this message in their email:

Your app, {App Name}, encountered an error while authenticating with any Solid server, including legacy ones, so I’m planning on removing it from the list. You can always fix the problem or let me know if I’m incorrect. I’ll be glad to add them back.

Some apps linked to sites that did not load. Developers received this in their email:

Your app, {App Name}, doesn’t seem to load, so I’m planning on removing it from the list. You can always fix the problem or let me know if I’m incorrect. I’ll be glad to add them back.

Some apps did not have a deployed instance and required a user to clone a git repository and host the app locally. This prevented the app from being tested. Though, this criteria was appealed and instead of removing these apps, I'll now add them to a new section called "Self-Installed." Developers received this in their email:

Your app, {App Name}, doesn’t have a deployed instance, so I’m planning on removing it from the list. You can always create a deployed instance and contact me, and I’ll be glad to add them back.

The following is the current standings for the App Update. I will leave this up for two weeks for comment, then make a pull request to update the document:
Super Feature:

Solid IDE
Penny
Solid File Manager
Media Kraken
PodPro
graphMetrix

Feature:

Linked Pipes Applications
OhMyPod!
Liqid Chat
drive
PoPock

Keep:

WebID Profile editor
Plume
Solid Profile Viewer
Solid Groups
Tiddlywiki
Solid authorization Widget
Solid File Widget
OEdit
Hello World
Golf Companion Assistant
OpenLink Structured Data Editor (OSDE)
ODS-Briefcase
OpenLink Structured Data Sniffer (OSDS)
URIBurner
OpenLink Smart Data Bot (OSDB)
OpenLink YouID
Solid Geolocation Challenge Entries
Solid Chat Challenge Student Projects
Dokieli
Solid LBS
Taisukef
Notepod
Poddit
Spoggy

Self-Install Category

KNoodle
Solid Signup app
Inbox
Solid Weather
Solid Calendar
Solid Health
SolidVC
Assemblage

Remove

Solidbase Site doesn't load
Warp Not a Solid app
Contacts Site doesn't load
Darcy Not a Solid App
Solidarity Propertly logs in but when attempting to send a message the error: TypeError: b is undefined is given
Holon Tabs break after clicking one of them
Twee-Fi Uncaught ReferenceError: $rdf is not defined when you click submit
File Extractor Encounters an Error when trying to extract the file
File Extractor for Pods Site does not load
Form Integration Redirects to a different site
Friend Requests Exploration Removed at the request of Inrupt
SNS Is not a Solid App
Firefly-iii not a Solid App
Solid Shell Not an App
SPARQL Fiddle Can't log into a Pod
OChat Site errors
Mark Book Site does not load
Mysilio Garden Requires the user to use a specific Pod host
Solid Focus Can't create a workspace "o is null" and removed at the request of the creator
Linked Beer Searching beers does not work.
Solid Chess Removed by the request of the creator
Tadanime Removed by the request of the creator
Solid RSS Not a usable app
RiseFor Mobilisation Site does not load
LongChat Error: Error recording your partipation: Exception in update: Error: Update: Can't make changes in uneditable https://solidos.solidcommunity.net/Team/SolidOs team chat/index.ttl
Snap Site does not load
Solid Notify Site does not load
Launcher Exploration Removed by the request of the creator

The new apps were merged in with #727


❓ Question: "This link is already in use"

🙋♂ Question
Hello,
I was uploading when I suddenly had a crash, so the upload was not finished.
I tried re-uploading the file I wanted to, then I had the error "Link already in use". I decided to go to my docker file and go to:
/pingvin-share/data/uploads/shares ,there I deleted the file I was uploading before the crash, but I still have the same error "Link is already in use".
How can I fix this ?
Thanks for taking the time to read.
Gabriel

The share is still in the database but after an hour unfinished shares should get deleted automatically. Can you try again?

The share is still in the database but after an hour unfinished shares should get deleted automatically. Can you try again?

Hello,
Thanks for the answer, I tried, but the error message is still here.

Oh sorry, only the files of an unfinished get deleted, the database entry stays. I'll try to fix this.

Unfinished shares should now get deleted after 24 hours.


[SPWebAppPeoplePickerSettings] SearchActiveDirectoryDomains - CustomFilter

The Ressource SPWebAppPeoplePickerSettings does not support the following Properties for SearchActiveDirectoryDomains

CustomFilter
ShortDomainName

The Parameters of MSFT_SPWebAppPPSearchDomain should be extended by:

Parameter
Attribute
DataType
Description
Allowed Values

CustomFilter
Write
String
Sets a customized query filter to send to Active Directory

ShortDomainName
Write
String
NetBIOS name of the domain or forest

I'd like to create a pull request with the needed changes.
I've checked the current code and the Set function only seems to add a SPPeoplePickerSearchActiveDirectoryDomain if it can not find one with the given DomainName and IsForest Property.
As far as i can see the current implementation would not change the AccessAccount Property of an existing SPPeoplePickerSearchActiveDirectoryDomain.
Currently the existing code would only apply a change, if the required parameters FQDN and IsForest change, but not the optional ones.
Since i'd also need that for the other optional parameters - is there another ressource which is a good code example?

I would add an Else statement here in which I check all properties if they are correct and update then if not:
https://github.com/dsccommunity/SharePointDsc/blob/fe2111d3c911e2b5ddd7f14855f1a17c32ff0047/SharePointDsc/DSCResources/MSFT_SPWebAppPeoplePickerSettings/MSFT_SPWebAppPeoplePickerSettings.psm1#L216


fix: Bump glob-all to remove vulnerable minimist version

Fixes #63
glob-all included a vulnerable version of minimist as a nested dependency. This is removed in glob-all3.2.1.

Coverage remained the same at 95.402% when pulling ce474d5665735072bfec98fa64f4fb791eb4cc71 on rajivshah3:fix/minimist into fdd5f9111515e2f4490068d05536ccc6311e3f2d on iandotkelly:master.

@iandotkelly can you please release this?

@iandotkelly sorry for pinging you again. Do you think you can give me publish permissions on NPM, so that I would publish this for you? https://www.npmjs.com/~hypnosphi

I have published the latest master as a scoped package @hypnosphi/nlf


I tried the plugin but everything shows in black and white only

I tried the plugin but everything shows in black and white only. Is there anything I am missing?

Can you give more details? Which platform are you using? What is your code? Otherwise it's difficult to help

Please open a new issue with an example and more details if the problem still exists


Replaced the getAttribute target rel by data-list for HTML5 validation

Sweet! Added your commit but made a minor change. Set the attribute to data-sort instead of data-list

Glad you agreed !
And now list.js is W3C valid.
Isn't it fantastic ?!

Yey, it's feeling nice ;)


generate-POAM-inventory script should emit unique identifiers needed for August ConMon (small task)

In order to meet FedRAMP requirements, the monthly inventory first column needs to have an identifier unique within the document.  Here's how they look now:

A TR emailed us to note:

Inventory - Unique Asset Identifier column does not contain UNIQUE identifiers

So the script generate-POAM-inventory.py should do that. Ideally it would match the names in the Nessus report, but if that's not possible, a name+IPaddr would suffice.
Example Nessus report host naming:

Acceptance Criteria

[x] first column of generate report has unique ids

Security considerations
Compliance requirement.

Changes made in a branch - PR: https://github.com/cloud-gov/cg-scripts/pull/136

Thanks for taking care of this @ChrisMcGowan


intercept dataset landing pages

What

Add the ability to intercept legacy and new (filterable) dataset landing pages

How to review

Checkout, build and run all of the following services: dp-frontend-router, dp-frontend-dataset-controller, dp-frontend-filter-dataset-controller, dp-frontent-renderer all on branch feature/intercept-datasets
Ensure you have sixteens, zebedee and babbage all running
Ensure you have go-ns checked out on feature/zebedee client
navigate your browser to http://localhost:20000/economy/economicoutputandproductivity/productivitymeasures/datasets/labourproductivitybyindustrydivision to test the legacy dataset landing page
navigate your browser to http://localhost:20000/datasets/1234/editions/5678/versions/2017 to test the new dataset landing page (note this is a completely stubbed page with no frontend model as yet)
Related reviews:

https://github.com/ONSdigital/dp-frontend-renderer/pull/55
https://github.com/ONSdigital/dp-frontend-filter-dataset-controller/pull/6
https://github.com/ONSdigital/dp-frontend-dataset-controller/pull/1
https://github.com/ONSdigital/dp-frontend-router/pull/26
https://github.com/ONSdigital/go-ns/pull/11
Who can review
Anyone

There's a few bits we probably want to look into before merging this into cmd-develop. I'm happy to go through these together if that's easier:
Breadcrumb is outside the page-intro block
This seems to be in the header.tmpl file but it should probably live within the static dataset landing page template. In the future we won't have a breadcrumb on each page template so it'll need to be done on a template by template basis. It also breaks the styling (the breadcrumb should have the same colour background colour as the rest of the page intro).

Link to view data for whole taxonomy text is missing
The link works fine but the text seems to be missing:

Doesn't work when running Zebedee CMS
As discussed, I think you get a 401 on  some request/s when running Zebedee CMS instead of Zebedee reader. This is possibly one for another ticket, but might be worth mentioning to someone who creates and prioritises stories to it can be recorded it on the backlog?


3243 PHMSA transmission part J

Overview
Closes #3243.

add yearly_miles_of_pipe_by_decade to file_map, page_map, page_part_map, skiprows, skipfooter
add raw_phmsagas__yearly_miles_of_pipe_by_decade asset to ETL
add column map file

Testing
How did you make sure this worked? How can a reviewer verify this?
I ran the ETL, then ran:
from dagster import AssetKey
from pudl.etl import def
asset = defs.load_asset_value(AssetKey("raw_phmsagas__yearly_miles_of_pipe_by_decade"))

And looked at some of the data:

The spike in gathering miles in 2022 appears to be due to "Onshore Type C" pipes finally getting reported starting in 2022:

Not sure if there's any specific tests I should write about the raw data.
# To-do list
- [ ] Make sure full ETL runs & `make pytest-integration-full` passes locally
- [ ] For major data coverage & analysis changes, [run data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation)
- [ ] If updating analyses or data processing functions: make sure to update or write data validation tests
- [ ] Update the [release notes](../docs/release_notes.rst): reference the PR and related issues.
- [ ] Review the PR yourself and call out any questions or issues you have

I'll make it onshore_type_a, it matches the PDF more closely!


Back button dosen't work in MessagesCreateNoticeActivity.

graph TB
	A{start}---B(input)
	B --> C[?]
	C -->|Yes|D[load]
	C -->|No|E[unload]

[] ddaf
[x] dafdaf

https://github.com/DAA233/EasyEcard/commit/919815e5b3448f2ecd4dbd00dadf3fa2aba073fb


I uninstall the extension from vscode but the changes I have done with the help of tabnine has been erased while deleting it.

please complete the following information:

OS version: [e.g. Win 10, Mac Catalina]
Editor version [e.g. 1.45.0-insider]:
Programming language: [e.g. js, ts, c++]
TabNine extension version:

If the issue is related to TabNine failure, please provide log files:
Type TabNine::config in your editor, the logs are located at the bottom of the page
Editor console logs:
Help -> Toggle Developer Tools
Issue Details:
gz#35361(related to Zendesk ticket #35361)

@lagunxayush What is the issue? Please elaborate


Docker images not building correctly

MatrixStats is not being installed in Mcp-counter image, other images are also not running properly.

I fixed this using the bioconductor docker images


Sharing when app is in background

When app is not in background/killed, sharing works fine, but when app is in recents/background,
nothing happens, app remains in the state it was before.

Same here. Android not working. Showing white screen and stuck. But in IOS device it works like perfect.


Argument matches weirdness around time with activesupport

Using rspec-expectations 3.5.0 on ruby 2.3.3
it "should fail" do
  my_double = double
  expect(my_double).to receive(:call).with(time: Time.utc(2016, 8, 8, 0, 0, 24))
  my_double.call time: "2016-08-08T00:00:24Z"
end

This fails as expected when used without activesupport. If you require "activesupport/all" (I tried versions 4.2 and 5.0), the spec begins to pass though.
I couldn't find any documentation on how to make method expectation perform exact match and had to come up with the following workaround:
RSpec::Matchers.define :exactly do |expected|
  match { |actual| actual == expected }
end

expect(my_double).to receive(:call).with(exactly(time: Time.utc(2016, 8, 8, 0, 0, 24)))

I believe this behavior can produce dangerous bugs and undermine developers confidence in their test setups. I also think that exact match should be an option or if it already is, it should be better discoverable in documentation.

Time.utc (in your expectation) returns a Time object, but your call is passing a string.  I would not expect your expectation to pass, but it appears that activesupport does some monkeying with Time#== or Time#=== (RSpec tries both internally when matching) to have them return true when the string version of a time is provided.  That seems like strange behavior in activesupport, TBH.

Right, I fully realize that this is a direct result of activesupport's "freedom patching" (tm).
I'm saying that there should probably be an option to have exact arguments match that behaves similarly to the workaround I came up with. It could maybe have a different method like this:
expect(thing).to receive(:foo).with_exactly(*args)

Also, Rspec is very popular in Rails community and this behavior seems like a bug that should be addressed spmehow in the long run.

You can already do this:
expect(thing).to receive(:foo).with(an_object_eq_to(other_thing))

an_object_eq_to is an alias of eq that does only == matching.
What I don't understand is how this fixes your problem: if activesupport has redefined == when loaded, why does it improve things for you to use a matcher like this that avoids the === check that it normally does?

I'm not sure what exactly activesupport does to cause this kind if behavior:
irb(main):001:0> require "active_support/all"
=> true
irb(main):002:0> time = Time.now
=> 2016-12-15 11:03:05 -0800
irb(main):003:0> time == time.iso8601
=> false
irb(main):004:0> time === time.iso8601
=> false
irb(main):005:0> time.iso8601 === time
=> false
irb(main):006:0> time.iso8601 == time
=> false

Can you provide a repo with a reproducible example?

Sure, gimme a minute

https://github.com/rwz/rspec-as-time-example

OK, I understand what's going on now.  I traced through activesupport to get the minimal set of monkey patches that trigger this behavior.  Here it is:
require 'date'

class DateTime
  # Layers additional behavior on DateTime#<=> so that Time and
  # ActiveSupport::TimeWithZone instances can be compared with a DateTime.
  def <=>(other)
    if other.kind_of?(Infinity)
      super
    elsif other.respond_to? :to_datetime
      super other.to_datetime rescue nil
    else
      nil
    end
  end
end

class String
  BLANK_RE = /\A[[:space:]]*\z/

  # A string is blank if it's empty or contains whitespaces only:
  #
  #   ''.blank?       # => true
  #   '   '.blank?    # => true
  #   "\t\n\r".blank? # => true
  #   ' blah '.blank? # => false
  #
  # Unicode whitespace is supported:
  #
  #   "\u00a0".blank? # => true
  #
  # @return [true, false]
  def blank?
    BLANK_RE === self
  end
end

class Time
  # Layers additional behavior on Time#<=> so that DateTime and ActiveSupport::TimeWithZone instances
  # can be chronologically compared with a Time
  def compare_with_coercion(other)
    # we're avoiding Time#to_datetime cause it's expensive
    if other.is_a?(Time)
      compare_without_coercion(other.to_time)
    else
      to_datetime <=> other
    end
  end
  alias_method :compare_without_coercion, :<=>
  alias_method :<=>, :compare_with_coercion
end

class String
  # Converts a string to a DateTime value.
  #
  #   "1-1-2012".to_datetime            # => Sun, 01 Jan 2012 00:00:00 +0000
  #   "01/01/2012 23:59:59".to_datetime # => Sun, 01 Jan 2012 23:59:59 +0000
  #   "2012-12-13 12:50".to_datetime    # => Thu, 13 Dec 2012 12:50:00 +0000
  #   "12/13/2012".to_datetime          # => ArgumentError: invalid date
  def to_datetime
    ::DateTime.parse(self, false) unless blank?
  end
end

That comes from 3 different activesupport files.  With it in place, it makes Time#<=> coerce non-time objets to date-time objects via to_datetime.  Comparable defines == in terms of <=> so it gets involved.  String has a to_datetime patch that allows it to be coerced.  DateTime likewise coerces the time to a datetime.  As a result, Rails has decided that a time object and a string representation of it should be considered equal, as long as you call == on the time (it won't work the other way around).
This seems like crazy pants.  Strings and times aren't the same, but rails, in the name of convenience, has decided they should be, but only if you do the comparison with activesupport loaded, and only if you do the comparison a certain way.
Your IRB example does not demonstrate the issue because of your use of Time.now; the current time includes milliseconds, but those are lost when it roundtrips via iso8601 and the comparison fails.  But if you construct the time using Time.utc you'll see the same behavior as in your spec.
Honestly, I don't think we should do anything about this.  We've documented our matchers to say what protocols they rely on.  Each object gets to decide what equality means for it.  If an object decides to implement == a certain way, as Rails has decide for time objects, we have to respect that.  It would be confusing for our matching logic to return false when a user can see time == string_time return true.

BTW, the reason using an_object_eq_to(time) fixes the problem is because of how eq is defined: it uses actual == expected which results in string_time == time:
https://github.com/rspec/rspec-expectations/blob/f6a03426a39b2555c8ad67818b6ac99a69ec25c3/lib/rspec/matchers/built_in/eq.rb#L34-L36
I'd say that's an implementation detail, though; == is a protocol that RSpec expects to be symmetric (e.g. the truthiness of a == b should be the same as b == a for all a's and b's).  The fact that Rails implements a non-symmetric version of == is fundamentally broken, IMO.

I don't think theres anything sane we can do about this

I've complained to Rails, but I don't actually expect them to do anything about it without making backwards incompatible changes.
This is really sad. 😢

Thanks for reporting upstream.
Agreed it's frustrating.
Closing.


Input Layer

@JustSteveKing This is an initial implementation for the Input Layer.
To finish this I'll need the DI container, so IDK if you want to merge this or leave this open and we merge after we have the DI container so I can work on the thins missing in this PR

Damn, I'm seeing a lot of changes that I didn't have when I started this 😢
I'll have to review the PR and update it


bug fixes databasename and aws namespace

Hello,
this pull request fixes two issues:

influx_database property is not recognized
if other metrics like SQS or EC2 of the AWS/* namespace should be used the custom fetcher is not selected and an exception is thrown. For example for ELB the namespace is AWS/ELB

Greetings,
Rainer

Hi, hope it's better now.


STOP_LOSS_LIMIT & TAKE_PROFIT

Hi tiagosiebler,
I have wrote an Algo, I am struggling to implement to following. I want to create a STOP_LOSS_LIMIT order and when that one is succesful, it should create a TAKE_PROFIT inmediately.
I have the following params;
    let type = "STOP_LOSS_LIMIT";
    let side = "BUY"
    let quantity = dataObject.amountCoin;
    let price = dataObject.entryPrice;
    let stopPrice = dataObject.stopPrice;

How do I set a STOP_LOSS_LIMIT order on Futures market.. I set my leverage and margin type (isolated) already. That works like a charm. But I can't create the above order.
And how do I set a the following order TAKE_PROFIT ?
// let typeProfit = 'TAKE_PROFIT';
// let sideProfit = 'SELL';
// let takeProfitPrice = dataObject.exitPrice;
// // -------------------------------------------
// params2 = { 'stopPrice': takeProfitPrice }

I can't seem to figure out howto. Could you explain please?
Regards,
The Alpha Centauri Ninja

I've admittedly not used this mechanism as I just use limit reduce orders for TPs. Did you figure this out? Sounds like a useful example to add. If you're still stuck you could try asking how the request should look in the binance API telegram:
https://t.me/binance_api_english

Hi TiagoSiebler,
I managed the following:
/api/v3/order?symbol=VETUSDT&side=BUY&type=STOP_LOSS_LIMIT&timeInForce=GTC&quantity=825&price=0.1131&stopPrice=0.1120&newOrderRespType=RESULT&timestamp=1633422601488&signature=83d725fb12ac4e1c37778e45013c766951f58c95e40a99866f0523aeb01df1fe&recvWindow=60000
However I get the following error back : data: { code: -1022, msg: 'Signature for this request is not valid.' }
I manage to create the signature the following way:
serverTime = await binance.futuresTime();

let query_string = `timestamp=${serverTime}`
let secretKey = crypto.signature(query_string);

------------ FUNCTION IMPORT ---------------------
const apiSecret = process.env.EXCHANGE_SECRET_KEY
function signature(query_string) {
return crypto
.createHmac('sha256', apiSecret)
.update(query_string)
.digest('hex');
}

Do you have an idea what I am doing wrong?
Regards,
Ninja

Difficult to say with a fresh implementation. Why not use the library for this? If it's just api/v3/order for spot markets, then this should be the method:
const binanceApi = new MainClient({
  ...,
  recvWindow: 60000,
})

try {
  const result = await binanceApi.submitNewOrder({
    symbol: 'VETUSDT',
    side: 'BUY',
    type: 'STOP_LOSS_LIMIT',
    timeInForce: 'GTC',
    quantity: 825,
    price: 0.1131,
    stopPrice: 0.1120,
    newOrderRespType: 'RESULT',
  });
} catch (e) {
  // log/handle error
}

Thanks, I will try that :D

Is this resolved?

Can USDMClient  use STOP_LOSS_LIMIT config ?  if new orrder request activated with stop_price & profit_price ?

STOP_LOSS_LIMIT

@ChenYCL the futures docs does not mention STOP_LOSS_LIMIT as a type for new orders, so maybe not. You can try asking in the binance api support channel on telegram: https://t.me/binance_api_english

STOP_LOSS_LIMIT

@ChenYCL the futures docs does not mention STOP_LOSS_LIMIT as a type for new orders, so maybe not. You can try asking in the binance api support channel on telegram: https://t.me/binance_api_english

Thank you. Is there a way to add take profit & stop loss in  orders?
eg. new order use market type and get orderId reponse.

Perhaps using batch orders (treating them as separate orders):
https://binance-docs.github.io/apidocs/futures/en/#place-multiple-orders-trade
In my case I manually maintain/cancel/replace a TP limit order anytime I see a position update from the user data websocket.
For API/workflow questions not specific to only this connector though I really recommend asking in the api telegram community I've linked to above. You're more likely to get that kind of guidance there. Once you know which parameters to use with which endpoint, you can make those API calls using this connector.

Perhaps using batch orders (treating them as separate orders): https://binance-docs.github.io/apidocs/futures/en/#place-multiple-orders-trade
In my case I manually maintain/cancel/replace a TP limit order anytime I see a position update from the user data websocket.
For API/workflow questions not specific to only this connector though I really recommend asking in the api telegram community I've linked to above. You're more likely to get that kind of guidance there. Once you know which parameters to use with which endpoint, you can make those API calls using this connector.

👍 ok,i think it can achieve my goal, make new order then websocket get message .


Different output compared with other runtimes when running the same wasm file.

I constructed a wasm binary with an exported function called "main". I used the following command and compared the outputs of WAMR with other runtimes.
filea3220.zip
The outputs of WAMR are different from other runtimes.
The outputs are as follows:

I have analyzed it and I think the error may occured at line 18 of its wat file.

Please try #2715, thanks.

Please try #2715, thanks.

OK, thank you


fix applicationId

I'm sorry, this slipped me... :-( In the other PRs, this is already included

It's fine. I've fixed that. Thanks for noticing.


Nixify project

This takes the approach outlined in this upcoming blog post to provide an unobtrusive Stack + Nix integration with versioning provided by niv.

@marcosh I didn't have time to find a different solution to parcel, so I'd rather have 30 min to try and debug it with you if you're still having problems since it's a rather simple setup.
I'll add some documentation to it though! :+1:

Just for visibility: I re-based this branch on main and removed the build scripts, so we can merge the nix stuff separately. I'll submit the build scripts & relevant documentation changes as a new PR based on this one.

I tried this. Some observations:

it would be nice to have some minimal instructions on how to use the Nix environment in the README.
if I run nix flake check, I get

error: Package ‘python3.10-pyopenssl-22.0.0’ in /nix/store/4ax73lz8i9v7jl6llsaqb1lnwal3w1qr-source/pkgs/development/python-modules/pyopenssl/default.nix:73 is marked as broken, refusing to evaluate.

       a) To temporarily allow broken packages, you can use an environment variable
          for a single invocation of the nix tools.

            $ export NIXPKGS_ALLOW_BROKEN=1

        Note: For `nix shell`, `nix build`, `nix develop` or any other Nix 2.4+
        (Flake) command, `--impure` must be passed in order to read this
        environment variable.

       b) For `nixos-rebuild` you can set
         { nixpkgs.config.allowBroken = true; }
       in configuration.nix to override this.

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
         { allowBroken = true; }
       to ~/.config/nixpkgs/config.nix.
(use '--show-trace' to show detailed location information)

if I run nix shell, I get

error: flake 'git+file:///home/marcosh/projects/tweag/servant-template' does not provide attribute 'packages.x86_64-linux.defaultPackage.x86_64-linux', 'legacyPackages.x86_64-linux.defaultPackage.x86_64-linux' or 'defaultPackage.x86_64-
linux'

if I run nix develop and then stack test, I get

postgresql-libpq                 > running .stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/LibPQ_hsc_make failed (exit code 1)
postgresql-libpq                 > rsp file was: ".stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/hsc2hscall52489-3.rsp"
postgresql-libpq                 > output file:".stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/LibPQ.hs"
postgresql-libpq                 > command was: .stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/LibPQ_hsc_make  >.stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/LibPQ.hs
postgresql-libpq                 > error: .stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/Database/PostgreSQL/LibPQ_hsc_make: /nix/store/jcb7fny2k03pfbdqk1hcnh12bxgax6vf-glibc-2.33-108/lib/libc.so.6: version `GLIBC_2.34' not found
 (required by /nix/store/pfiay68nw57kcrkqkhssawcwcc0zdkay-openssl-1.1.1o/lib/libcrypto.so.1.1)

@marcosh I can reproduce the issues with nix flake check and nix shell, and will investigate those soon, but I wasn't able to reproduce the stack test failure so I'm not sure how to proceed there. :thinking:

@matthew-healy I solved the issue with stack test by removing the .stack/setup-exe-cache folder. It was the same issue I had with https://github.com/tweag/haskell-training

@marcosh I pushed a commit silencing the broken package error. nix flake check works fine for me now.
I'm wondering - what do you think the behaviour of nix shell should be here? If I understand correctly, the general intention of that command is to drop you into a shell with the flake's output pre-built, but the current flake deliberately avoids knowing how to build the actual project. The intention as I understand it is for developers using Nix to be able to run nix develop, get a shell, then do the actual building with stack. With that in mind, it's not clear what the behaviour of nix shell should be other than to error.

I don't really know how such commands are supposed to work. Personally, I would prefer to have nix shell to produce something useful, even if just the same thing as nix develop does.
Anyway, I'll leave it up to you. If you think that giving an error is more appropriate, I'm OK with it. And we could also improve it later


Dump labels

Dump labels/categories.

A quick changelog:

Labels
Label filter ability
Label clickables
Label form
Removable label items
Faster searching
Faster deleting from DOM
Graphical tweaks
Fadein/popOut properly

Closes #1
Creates foundation for #26

NOOOO WAY THIS IS AWESOME! :DDDDDD Pulling it in!


[BUG] There is no Global Properties that sets try-timeout to retry.fixed

Describe the bug
As you may see the following doc, there is no Global Properties that sets try-timeout to retry.fixed.
https://microsoft.github.io/spring-cloud-azure/4.3.0/reference/html/appendix.html#global_proeprties
To Reproduce
Please use settings in Code Snippet section.
spring.cloud.azure.retry.fixed.try-timeout=10s # not work
#spring.cloud.azure.storage.retry.try-timeout=2s # work but no global properties.
Code Snippet
src/main/resources/application.properties
spring.cloud.azure.retry.mode=fixed
spring.cloud.azure.retry.fixed.max-retries=108
spring.cloud.azure.retry.fixed.delay=7s
spring.cloud.azure.retry.fixed.try-timeout=10s
#spring.cloud.azure.storage.retry.try-timeout=2s

Information Checklist

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

Hi @YusukeTobo thanks for reaching out. This is actually by design, since for some HTTP-based clients, like Key Vault, don't have a tryTimeout. So we add this only for AMQP-based clients and Storage. So there's no global properties for all the SDK clients, but there's one spring.cloud.azure.retry.amqp.try-timeout. The one for storage is an exception for HTTP-based client.

Hi @saragluna , thank you for letting know that design. I understand HTTP-based clients generally don't support tryTimeout.

@YusukeTobo could we close this issue now?

@saragluna yes you cloud. BTW, spring.cloud.azure.client.http.connect-timeout=30s is not override default timeout 10s in Netty HTTP client. Should I create another issue?

@YusukeTobo yes please. Could you create the issue in the azure-sdk-for-java repo?

@saragluna building on this issue, I've filed 2 reports related to Connect Timeout. If possible, could you look into them?

https://github.com/Azure/azure-sdk-for-java/issues/31051
https://github.com/Azure/azure-sdk-for-java/issues/31052

Thanks @YusukeTobo for filing them, we will look into these two issues.


Listen for change event for bound values

When you call localStorageService.bind, an event listener is now
registered that is fired when the value of the local storage key
changes, which updates the value and calls scope.$apply(). fixes #166

Are changes still required here? I wanted to start work on this, but saw the PR already existes for this functionality.

+1 for this feature.

+1 too :)

This won't actually work because storage events are only fired on other windows/tabs, not the window/tab originating the event. I've modified the PR to listen to internal events to do this instead, which seems to be working fine.

+1 as well