Applying a configuration using approvers and approver_groups has no effect while running against Gitlab 12.3.5-ee.
The config I'm using:
group_settings:
  'very-silly-test-group-for-ldap-and-fun':
    merge_requests:
      approvals:
        approvals_before_merge: 1
        reset_approvals_on_push: false
        disable_overriding_approvers_per_merge_request: false
        merge_requests_author_approval: true
      approver_groups:
        - gitlab
      approvers:
        - waldekm
        - foouser

With the log
$ gitlabform -vvv -c config.yml very-silly-test-group-for-ldap-and-fun
Reading config from: /Users/waldekm/git/config/config.yml
Connected to GitLab version: 12.3.5-ee (9dbaa740018)
Config file is declared to be compatible with GitLab API v4
Reading config from: /Users/waldekm/git/config/config.yml
*** # of groups to process: 1
*** # of projects to process: 1
* [1/1] Processing: very-silly-test-group-for-ldap-and-fun/testy-project
Setting project_settings
Setting project settings: {'only_allow_merge_if_pipeline_succeeds': True, 'only_allow_merge_if_all_discussions_are_resolved': True, 'shared_runners_enabled': True, 'request_access_enabled': True, 'wiki_enabled': False, 'snippets_enabled': False}
Setting merge_requests
Setting approvals settings: {'approvals_before_merge': 1, 'reset_approvals_on_push': False, 'disable_overriding_approvers_per_merge_request': False, 'merge_requests_author_approval': True}
Setting approvers to users ['waldekm', 'foouser'] and groups ['gitlab']
Setting hooks

Gitlabform implementation uses endpoint projects/:id/approvers which has been deprecated:
https://docs.gitlab.com/ee/api/merge_request_approvals.html#change-allowed-approvers
I could just be using it wrong (although I've tried moving the key approvers under approvals and this didn't work either). It might be also that the deprecated endpoint doesn't work anymore.  In any case, adding/removing users to the approvers list and running gitlabform doesn't show in gitlab-rails/api_json.log

I am seeing the same behaviour running against 12.4.2-ee.

The new API - if powerful - is sadly much more complex and involves creating/updating approval rules (which have their own ids).
https://docs.gitlab.com/ee/api/merge_request_approvals.html#create-project-level-rule

On a related note: https://gitlab.com/gitlab-org/gitlab/issues/4816
TL;DR: with MR approvals enabled for a project, Gitlab assumes that all Developers should be notified on any MR.
Gitlabform could be the most feasible workaround for this spammy behaviour.

Hi, thank you for reporting this and sorry for the trouble. I will try to get this fixed in the next 2-3 weeks.

I have tested this some time ago on 12.5.4-ee and have not notices this issue.
I have also tested this with the current  12.6.2-ee in https://travis-ci.com/egnyte/gitlabform/jobs/272436690 (done locally for now, will finish on Travis within a few minutes) and the problem does not exist there anymore.
Please see my test setup, configs and assertions in https://github.com/egnyte/gitlabform/pull/75/files#diff-c92a09cbae0c182205d0cbe7f414ff33 .
Can you please verify if this problem persists with GitLab >= 12.5.4, @weakcamel and @smcgregor83 ?

Ok, so my latests test confirm that there is an issue if you have both users AND groups set as approvers and change any of these lists, for both 12.5.4 and 12.6.2.
(There is NO such problem if you ONLY have users OR only groups as approvers and change them.)
We need to report this to GitLab as even if this API is deprecated it should not have such bugs.

I have come up with a temporary workaround for this bug:

Create GitLab group such as "approvers_group_a" and in GitLabForm assign them members.
Assign ONLY THIS GROUP to your appropriate projects as approver groups with GitLabForm.

Example:
# (...)
group_settings:
  approver_group_a:
    members:
      - user1
      - user2

project_settings:
  some_group/project_a:
    merge_requests:
      approvals:
        approvals_before_merge: 1
        reset_approvals_on_push: false
        disable_overriding_approvers_per_merge_request: true
      approver_groups:
        - approver_group_a

I know that this is not pretty but it should work until this bug is resolved.

Version 1.11.0 is just being built and pushed to PyPI. I contains the group members adding/changing access level (I am trying to be precise here as we cannot yet remove members with gitlabform). So the above workaround should work now. :)

Version 1.12.0 is just being built and pushed to PyPI. It contains new Merge Request Approvals API implementation, so the code above should work now.

Many many thanks @gdubicki
I can confirm that the latest version works within limitations caused by https://gitlab.com/gitlab-org/gitlab/issues/198770 (when I tried, I got the lovely warning about it.
I've voted for the issue and now commented on it as well, fingers crossed it gets some interest from Gitlab people soon.

@weakcamel and everyone affected: I am happy to report that the issue is resolved in v1.14.0 that has been released just now.
(But less-than-happy to learn that it was caused by something that I consider a GitLab issue more than a GitLabForm issue - see #90 and the linked GitLab issue for more info.)

@gdubicki  this is amazing! I'm definitely going to give it a try as soon as I can :)

Works like a charm!
👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍


Review spacing around subscript/superscript tags when importing PMC BioC documents

When parsing the PMCOA BioC format, consider adding spaces before the superscript and subscript tags to separate the sub/super-scripted text from the regular text. For example, in PMID:31040849, the three tokens Hif1-α ΔIEC mice where the ΔIEC is superscripted, should be separated by spaces when the plain text version of the document is created. Currently, at least in the case of this document, no spaces are added before the superscripted text and the plain text ends up being Hif1-αΔIEC mice.
This issue is also noted when parsing the Medline XML in https://github.com/UCDenver-ccp/Translator-TM-Provider-Pipelines/issues/49.

It turns out that the typography information is not present in the BioC format, so there is no way to adjust spacing. Also, as it turns out, we didn't end up modifying spacing when revisiting handling of sub/sup tags in the Medline XML.
If we want to track sub/sup tags in PMCOA in the future, we will likely need to make use of the PMC OA XML files.


AffectsSavedGames = 0, Mod Settings now Persist

CHANGES

AffectsSavedGames is now 0 (can load/unload mod without affecting saves - fix for #15 )
Corrected issue with mod settings not persisting between game loads, etc.
Changed version to 2.0, don't typically plan to rev the major version number, however I thought it reasonable to do with the AffectsSavedGames change.

TESTING

Started game, played a few turns, added items to the build queue, changed a CQUI setting (display luxuries on top panel).  Saved game.
Quick back to Main menu, disabled mod.  Loaded the save.  Confirmed the queue still had the things in it.  Played 1 turn, saved game.
Quit Civ6 back to desktop.  Launched Civ6 again.  Re-enabled mod.  Re-loaded most recent save.  Verified settings were correct.  Verified build queue still had things in it.

btw - since we have the 1 approval, I did publish this to the workshop.  I don't think I can approve my own PR so we need to find a way to recruit some other folks that can at least do code reviews :)

I was just trying it now from master. Should I do anything other than just start to use it?
I ask because it seems things are broken. I have the repo cloned in the My Games\Sid Meier's Civilization VI\Mods location, I tried that first. Then I got rid of that one and tried the one from workshop, the issues exist there too. The CQUI settings button doesn't do anything. The Lua.log file says there are errors.
In game I see the diplomacy banner stuff seems okay. The city production ques seems okay. The city banner doesn't show additional housing growth available. I think other stuff might also be broken. I just wanted to post since you said you published it to workshop, and I am afraid it might have broken other peoples mods too.
Here are the DLCs I have:
Australia
Aztec
Poland
Viking
Gathering Storm
Rise and Fall

Additional info on what I tried.

Disable all community mods other than CQUI
Start a new game
Build city
See issues mentioned above.

Then I tried to load a game that I had CQUI from when it had the AffectSavedGames set to 1.
That one seems to work better, I can go to settings, I can see the city banner properly.
Attaching my Lua.log incase that helps.
Lua.log


Adding to dictionnary does not work for me

Whenever I add a new word to dictionnary (user, folder, grammarly), at the next restart of VS Code, new words are not recognized anymore. How can debug to see what happens ?

I have the same issue as the original OP.
MacOS, newest version of the Grammarly extension, free account.
When I run Grammarly: Login, I get a bunch of redirects which I confirmed.
In the end, I get a message in the VSC that I am logged in successfully, however:

I don't get the option to add a word to the dictionary in the quick-fix menu
I don't have the "Grammarly:User words" setting in my VS code settings
If I add the setting manually to settings.json they are ignored.

What am I doing wrong and how can I fix that?

Same issue.  I am logged in, but I do not get the add to personal dictionary option.


Add simple SConscript/variant_dir vs VariantDir example

Here, or cookbook?  Now we've got two it's getting confusing...


Tests: handle missing python-lmdb gracefully

Fix issue mentioned here: https://github.com/caffe2/caffe2/commit/875a9850c15f7bbc4466aec6054f25f327793bcd#commitcomment-22773221
Unblocks https://github.com/caffe2/caffe2/pull/817
/cc @tomdz

@tomdz I'm assuming your existing test infrastructure can't gracefully handle tests which raise unittest.SkipTest exceptions? If you could share how you run Python tests internally, I can adjust the TravisCI scripts and our own internal CI scripts to match more closely so we have fewer conflicts like this.

Alternatively, we can make lmdb a first-class requirement and I can add it to the list of packages I install on Travis. I'm trying to keep the list as small as possible since I have nothing to go off of, but if you create a requirements.txt file, I'll happily use that instead.

Ugly, but fine.


Optimal solution does not satisfy constraints consisted of priced variables.

Hi,
Thanks to your advise so far, I have completed building my branch-cut-price model.
However, I found the optimal solution does not satisfy some constraints, especially when they have priced variables.
For example, I have a constraint such as

eq1 :  \sum_{i} x_i <= y

where y is an original binary variable and x_i are priced binary variables. These constraints are defined as modifiable = True.
I added a new variable using
self.model.addVar(vtype="B",  obj = optimal_m, name= newVar_name, pricedVar=True)
and added this new variable to the above constraint
self.model.addConsCoeff(eq1, newVar, 1 )
However, the optimal solution is  y=0 and x_i=1 for some i, which does not satisfy the above constraint.
When I wrote out the model into .cip file, I can see the constraints changed properly.
I tried to read the file again within the SCIP console, however, there was an error saying that x_i variables (priced variables) were not defined in the cip file.
What am I missing here?

can you share some (hopefully small) code to reproduce?

closed due to inactivity


Fix disabled cursors

When a client requests to disable a cursor, the last compositor cursor is displayed instead.
This PR also allows compositors to hide cursors by calling wlr_output_cursor_set_image with a NULL buffer.
Test plan: open weston-terminal, start typing, the cursor should disappear. Move the cursor, it should appear again.

Why a separate flag? Can't you check if the cursor is enabled whenever you need to know this (invalid texture or no surface buffer) instead of keeping up with the extra state?

Can't you check if the cursor is enabled whenever you need to know this (invalid texture or no surface buffer) instead of keeping up with the extra state?

That doesn't work with cursors without a surface. These cursors have a renderer and a texture instead, and we create them only once. Also consider the case of a cursor with a renderer and a texture and a call to wlr_output_cursor_set_surface with a NULL surface that disables the cursor.


[MM-14593] Add password type for Interactive Dialogs

Summary
Added password type for Interactive Dialogs by passing secureTextEntry prop
Ticket Link
Fixes #10460
Checklist

[x] Added or updated unit tests (required for all new features)
[x] Has UI changes

Device Information
This PR was tested on: [Pending]
Screenshots
[Pending]

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

@enahum Can someone from the Apps team help build the APK for me? The one I tried using the Build Apps for PR label failed. Thanks!

@prapti will do soon.. I'll ping you once is done

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2998/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2998/Mattermost_Beta.plist

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2998/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2998/Mattermost_Beta.plist

Can this be merged?

@hanzei Yes! Please merge it :)

For some reason I can't merge the PR.
@jwilander @ali-farooq0 Would you please take care of this?

Merged


merge table formatting fix

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/scripts/concepts/errors-and-warnings.md
:white_check_mark:Succeeded

BingAds/scripts/reference/AdGroupBidding.md
:white_check_mark:Succeeded

BingAds/scripts/reference/KeywordSelector.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Implement additional ACL for wiki write permissions

Currently only the wiki owner can edit a wiki. Implement a data structure that provides an additional permission group for editors, which may be a subset of the read-only viewers.

I might suggest using the write_pages permission as a workable solution for the short term. Long term we need to make the permissions system a bit more extensible.

I had originally planned to do exactly this, so I have some checks for "write_pages" permissions in the code already; the downside to this is that if you want Bob to be able to read Wiki1 and Wiki2, but you only want him to have write permissions on Wiki2, you're out of luck. For the first iteration this limitation might be acceptable, but it also wouldn't be hard to add another ACL for write permissions using the set_iconfig() function. Or am I missing some subtlety about this additional ACL?

Is the extensible permissions framework complete enough now to try using it for this purpose?


unpacking values causes SyntaxError

I have a following file:
contract Test {
    function Test() {
        var (x, y) = doTest();
    }

    function doTest() returns (uint, uint) {
        return (1, 2);
    }
}

which causes an error:
An error occured while running the linter on contracts/test.sol:
Error: An error occured while parsing the source code:
SyntaxError: Expected ")" but "," found. Line: 3, Column: 15

I guess this error is internally in the solparse library, but I'm not sure.

Correct, this is a feature missing in solparse. It doesn't recognise var (x,y).
Thanks a ton for reporting this!

Solved in v0.1.14


[POC] Avoid non-sensible labels

[Actual Results]: When refreshed the web browser some labels are broken. Displaying the i18n key and not the value of the label
[Expected results]: The system should avoid to display non-sensible labels such as system specific label keys
[Steps to reproduce]: Throughout the system

 Avoid non-sensitive labels

@ynurmahomed and @larslemos the changes in 3044fc7 is breaking Patient Programs detalis, an error clicking view button:

Strange that its working on 7354ec59540d3ce93a100fcb9409d15e9c8d8be3.

@valvijo can you try again after clearing your browser's cache?

Working now after a fresh login, not sure what the problem was.


In general, to play a podcast I'm finding I have to click the play button once, pause it, and then play it again to hear sound.

Same


Add GLFW_CENTER_CURSOR window hint

Implement a hint for positioning the cursor in the center of the window.
Fixes #749

Does this flag achieve something that can't be done simply by using existing APIs to get the monitor size, calculate its center, and position the cursor?

I rebased around a handful of changes. Let me know if there's anything else you need. I believe I've removed anything that related to disabled cursors.

@elmindreda forgot to ping back, do the changes look good now?


Question: Wishlist #8 Validating Task inputKeys and outputKeys

I was hoping I would be able to contribute to this open source project, and I wanted to ask if what I had planned for the validation would be enough or was there more to the validation that was intended for this. What I had planned is simply adding a @NotEmpty(message = "") On the inputkeys and outputKeys fields on TaskDef.java file.My reasoning for doing something so simple is because in your documentation on the fourth bullet point it states that

In the future, this can be extended to be a strict template that all task implementations must adhere to ...

My understanding was that users creating tasks would need to have these fields populated to be able to document what is needed for a task to be run and what you can expect it to output once finished, making it easier for re-use. Looking forward to your response, Thank you.

We are looking for this feature as well. @cclulu  I think we need to think through some details.

How do we ensure backward compatibility when we introduce validation?
How to have strict validation? For example, the data structure of an input/output key.

@cyzhao @apanicker-nflx @mashurex @kishorebanala @mudit3774 Thoughts?

What do you mean the data structure of the input/output key? Do you mean change the input/output keys to be something similar to what the input field is for StartWorkflowRequest is? Was there something else that you meant? From what I understand it doesn't seem that is much we can validate, just that they have something there. Since what the task can input is different depending on what the task does, I am not sure how much validation we can make on whats there, but only that they have something there. Am I missing understanding something here? If I am, i would be glad to learn more.
As far as backward compatibility goes, I had not thought about about. If we just add the validation that I had mentioned, then backwards compatibility would be as simple since it changes the model of the taskdef. I would have to think more about this one. Any ideas would be great.

@cclulu Thanks for the proposal. As @naveenchlsn mentioned and you quoted in your proposal, the eventual goal would be to enforce a strict template for both input and output of a task. This would mean, the task inputs and outputs would need to be typed, so that re-use of tasks can allow for type-safety constraints.
To ensure backward compatibility for existing tasks, this could be rolled out in phases.
Phase 1:

Add a new field to TaskDef , say "inputVariables" and "outputVariables" which could be a Map<String, Class> where the key in the map is the inputKey/outputKey and the value is the type (must be either a primitive type or JsonNode(?)[This part needs to be hashed out more]).
This field can be enforced for all new task definitions.
Deprecate the inputKeys and outputKeys fields.
Minor version bump of Conductor release.

Phase 2:

Next major version release of Conductor would remove the inputKeys and outputKeys fields and enforce this typed contract.

@cclulu @naveenchlsn Please let me know your thoughts regarding this.

This looks good to me @apanicker-nflx .
We can use JsonSchema to let the users input the schema definition of task inputs and outputs.

JsonSchema is a good approach towards implementing this. It additionally allows the task definition owner to specify if certain fields are required/optional, while not compromising on type-safety.

sounds like there is a plan, I would be excited to try to implements this, I have never used JsonSchema before so I look forward to learning something new. If this is the implementation that everyone agrees with I would like to get started on this is that is alright with everyone? Also if I have any more question should I just post them on the gitter or post to this thread?

@cclulu Please feel free to get started with on this, and continue to update here with regards to questions and design choices. Thank you very much for the contribution.

Hello @cclulu,
Me and my team, we are currently using JSON schema to make validation possible on some inputs. And my feedback is really positive. Allow to describe workflow inputs and task inputs with JSON schema, can give the possibility to perform a wide and deep validation, on types, constraints and even conditional dependencies among inputs.

I would think that using something more flexible than an annotation on the classes would be required for input/output keys, as they're dynamic to each task defined in the system. Using JSON Schema or having a way to describe validation requirements on the task def (or in the workflow def) would make this much more flexible.
For our custom implemented tasks, we validate task inputs in the start and/or execute methods. A few times we've created a data validation tasks that sit between two 'real' tasks in the workflow for this very purpose as well.


Starknet cairo compile not working

Starknet cairo compile is not working. I have failed to fetch message. please help

Thanks a lot for the report! Could you give us more details? (screenshot of browser console, Remix console, network tab...)

Вот такая ошибка когда жмешь Compile

@Kuper8, спасибо, мы проверим это как можно скорее

@0xtradeall, @Kuper8, can we ask you for a few more details of this behaviour? We suspect CORS-related problem, but to be clear, would you like to fill in the details as per below?
To Reproduce
Steps to reproduce the behavior (from a clean start):

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Cairo files
Please include the Cairo source file.
Starknet Remix Plugin details

Are you using the default Starknet plugin from Remix marketplace, or any self-configured plugin instance?
What Environment are you using (Remote/Local Devnet, a wallet configuration)?

Host system (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari], any nonstandard browser plugins/adblocks
Version [e.g. 22]

@0xtradeall, @Kuper8, can we ask you for a few more details of this behaviour? We suspect CORS-related problem, but to be clear, would you like to fill in the details as per below?
To Reproduce Steps to reproduce the behavior (from a clean start):

Go to '...'
Click on '....'
Scroll down to '....'
See error

NOTE: Please clearly indicate the time (with timezone or in UTC) when you have observed the error.
Screenshots If applicable, add screenshots to help explain your problem.
Cairo files Please include the Cairo source file.
Starknet Remix Plugin details

Are you using the default Starknet plugin from Remix marketplace, or any self-configured plugin instance?
What Environment are you using (Remote/Local Devnet, a wallet configuration)?

Host system (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari], any nonstandard browser plugins/adblocks
Version [e.g. 22]

Hello ! I tried again,  but a new error appeared. No buttom to compile, attached a screenshots a below. See error

My browser is Chrome version 116.0.5845.188

Windows 11, no plugins/adblocks

i am facing same issue except am running windows 10

I have the same problem - Windows 11

OK, we have been experiencing outages on the plugin backend, but this all now seems to have been rectified. Would you like to repeat your attempts and confirm if the compilation works as expected now?

Everything is all right now. THX.

Od: "stranger80" @.>
Komu: "NethermindEth/starknet-remix-plugin" @.>
Dátum: 26.09.2023 20:45
Predmet: Re: [NethermindEth/starknet-remix-plugin] Starknet cairo compile not working (Issue #127)

OK, we have been experiencing outages on the plugin backend, but this all now seems to have been rectified. Would you like to repeat your attempts and confirm if the compilation works as expected now?
—
Reply to this email directly, view it on GitHub https://github.com/NethermindEth/starknet-remix-plugin/issues/127#issuecomment-1736092263, or unsubscribe https://github.com/notifications/unsubscribe-auth/A54MY7RPM5C5OC4BW7TDQ4LX4MPGDANCNFSM6AAAAAA5DS3AY4.
You are receiving this because you commented.Message ID: @.***>

OK, we have been experiencing outages on the plugin backend, but this all now seems to have been rectified. Would you like to repeat your attempts and confirm if the compilation works as expected now?

After compilation this error:
Error from IDE : [TIMEOUT] Timeout for call writeFile from Starknet try deleting the files: NethermindEth/StarknetByExample/listings/ch00-introduction/constructor/src/artifacts/lib.json and Nethermind...
And I don't know what to write in these fields: "names" and Smart contract"


Add new easings

Feature:

[ ] step
[ ] bezier
[ ] physics (tension, spring)

Hey! Thanks for the handy lib. Perhaps have the option of passing in a function to the easing prop? One could then import default easing functions (say an easeInOut / spring fn exported by animate-value) and apply it as needed, or be able to pass in a user defined fn.

I like this idea, not a difficult thing to implement I guess.
It would have to be an easing functions that returns a value between 0 - 1

For sure, I guess that can be documented. I guess it would just receive current time as an argument?

value between 0-1 which recalculates it via easing to 0-1

PR always welcome btw :)


Update mdatp-6-systemconfigurationprofiles.png

Change in the screenshot as deployment channel is available now

@JohanFreelancer9 Please copy review

issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7095

Thanks, I think we want to also work in/breadcrumb the What's New guidance/details here as well please @msbemba https://docs.microsoft.com/en-us/mem/intune/fundamentals/whats-new#new-deployment-channel-setting-for-custom-device-configuration-profiles-on-macos-devices

@Dansimp Please merge this PR. Thanks

issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7194


ip pool

Hello
i have added ip pool but how can i check that whether it is working all the ip's or not?
i think it's working only default server ip and i have many ip address so i want to rotate that ip for better inbox deliverability. Please tell me how i can check that ip is working or not?
thanks

You'd have to set sending email and look at the headers.
I don't believe there is another way but it is safe to say, if a few work, they generally all will otherwise it'll be a system issue than software.

Out of interest, what leads you to the impression that using multiple IPs will increase the deliverability of your messages? I believe the only way to know for sure is simply to send a batch of emails to yourself and look at the headers of the received emails. It definitely should work if the mail server is configured to use the pool.

Because ISPs will limit simultaneous sender connections or messages allowed per connection by IP address.  Therefore, if you want any delivery scale, you need to be sending via multiple IPs.  Waiting for retry periods is way too inefficient.

Hey, I checked and postal is using the primary IP address (my eth0) to send the emails.  I have multiple IP addresses on server as alias (eth0:1, eth0:2, eth0:3....) and as said above I want postal to rotate the IPs for a particular domain. Is this function available in Postal?  For example in pmta I can assign the IPs to a virtual MTA and pmta keep on sending the emails from all assigned IPs.  This would be a great feature in Postal if its not there.

@sandeep28saxena https://github.com/atech/postal/wiki/Configuring-IP-Pools

Hey Guys, I created an IP pool and then assigned it to an organization.  Checked the settings of the mail server in this org and same pool is assigned to the server.  But when I send emails from this mail server it is going from the other IPs on the server which are not part of the pool.   Any clues what can be wrong ?

Hey Guys, Is any one facing similar issue ? Any clues what can be wrong. I checked everything as far as I can and did not see anything missing.

Any news about this ?
I configured 3 local ips that each are routed per different public ip addresses, tested with links:
links -bind-address <IP_ADDRESS> www.cualesmiip.com
links -bind-address <IP_ADDRESS> www.cualesmiip.com
links -bind-address <IP_ADDRESS> www.cualesmiip.com

But when sending a test message, is always routed by "main IP".
Thanks.

hello,
try to add dns of your IP Pool or you can use /etc/hosts
for example:
xx.zz.yy.97	ip1-pool.example.com
xx.zz.yy.98	ip2-pool.example.com
xx.zz.yy.99	ip3-pool.example.com
xx.zz.yy.100	ip4-pool.example.com

also you can test to create IP Rules, like example
Any message sent from<EMAIL_ADDRESS>Will be sent using: IP-Pool1
its work for me, previously on different environment i don't have this issue but when i installing on different environment i facing this issue

Hello guys. Any one can help me with this. I dont know how to get an ip address for an IP pool. I need it for Postal. Everything is set up with my real IP... but i want to use the pool Ips. How can i do, make or cook that?   Thank you very much!!!

@andresagui you will need to get more IP addresses from your server provider which typically requires extra configuration on the server as well. Once you have done that, you will be able to enable the IP Pools feature and set it up as you desire. Please open a new issue if you have more questions rather than commenting on closed issues.

You just can try this article simply: How to set up IP Pool for the Postal SMTP server? (Latest Updated Guide)

You just can try this article simply: How to set up IP Pool for the Postal SMTP server? (Latest Updated Guide)

Nice, but 5 years late.


Tweak CSS for mobile view / narrow screens

There's too much padding / margin on narrow screens, not enough space for plots.
Also, the referrer / path plots do not display well on narrow screens because of the fixed legend width.

Done via https://github.com/jgehrcke/github-repo-stats/pull/7.


Fix crash when PPLs in virtual folders are replaced

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Move PPLs out of the Includes virtual folder during cloning to avoid crash when the PPLs are replaced.
Why should this Pull Request be merged?
LabVIEW fairly consistently crashes when the PPLs inside the virtual folder are replaced. This change prevents that crash.
What testing has been done?
Ran the template tool multiple times and did not see a crash. Previously crashed 4 out of 5 times.

Do you need to close the Project Item references? Or is calling Delete sufficient?

Delete closes the reference.


CMP_RecTypesHelper fix

Critical Changes
Changes
Issues Closed
Fixes #280

@dospromptman This pull request has been open for three weeks... It'd be nice if we could clean up the pull requests queue a bit...

@ceiroa i'm not sure that i'm the best one to be reviewing this (or HEDA PRs in general), since I don't really know anything about HEDA code


feat(command): configure plugin

todo: configure plugin as an api exported member (facilitate usage)

Closing, changes moved here: https://github.com/pmizio/typescript-tools.nvim/pull/167


sourceMap error in css-loader and postcss-loader dependencies

Hello everyone,
After updating angular to the latest version I'm facing a sourceMap issue, everytime I try "ng serve" get an error related with css-loader and I don't know if I'm wrong but I get it as a dependency<EMAIL_ADDRESS>Thank you!
Versions
"dependencies": {
    "@angular/animations": "^5.0.0",
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.0.0",
    "@angular/forms": "^5.0.0",
    "@angular/http": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "@angular/router": "^5.0.0",
    "base-64": "^0.1.0",
    "codemirror": "^5.23.0",
    "core-js": "^2.4.1",
    "enhanced-resolve": "3.4.1",
    "jquery": "^3.1.1",
    "jquery-ui-dist": "^1.12.1",
    "jquery.scrollbar": "^0.2.11",
    "materialize-css": "^0.100.2",
    "rxjs": "^5.5.2",
    "web-animations-js": "^2.2.2",
    "zone.js": "^0.8.4"
  },
  "devDependencies": {
    "@angular/cli": "1.5.4",
    "@angular/compiler-cli": "^5.0.0",
    "@types/jasmine": "2.8.2",
    "@types/node": "~8.0.53",
    "codelyzer": "~4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "protractor": "~5.2.0",
    "ts-node": "~3.3.0",
    "tslint": "~5.8.0",
    "typescript": "2.4.2"
  }

Observed behavior
ERROR in ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader/lib?{"ident":"postcss","sourceMap":false}!./node_modules/sass-loader/lib/loader.js?{"sourceMap":false,"precision":8,"includePaths":[]}!./src/styles.scss

We'll need some additional information to help track down the issue.  Can you provide the command that was run that generated the error?  Also the contents of styles.scss would be helpful, if possible.
Since the project was updated in place, executing an npm update may also be prudent to ensure the latest versions of all dependencies are installed.

Hi @clydin and thanks for your help.
As it is an "old project"  I was trying to update my dependencies, with the following steps:

Run npm update
npm install -g npm-check-updates
ncu -u
Which generates:

{
  "name": "backtracking-admin",
  "version": "0.0.0",
  "license": "MIT",
  "angular-cli": {},
  "scripts": {
    "start": "ng serve --port 8300",
    "lint": "tslint \"src/**/*.ts\"",
    "test": "ng test",
    "pree2e": "webdriver-manager update",
    "e2e": "protractor",
    "build:dev": "ng build --environment=dev",
    "build:master": "ng build --environment=master --target=production",
    "build": "ng build --environment=prod --target=production"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.0.3",
    "@angular/common": "^5.0.3",
    "@angular/compiler": "^5.0.3",
    "@angular/core": "^5.0.3",
    "@angular/forms": "^5.0.3",
    "@angular/http": "^5.0.3",
    "@angular/platform-browser": "^5.0.3",
    "@angular/platform-browser-dynamic": "^5.0.3",
    "@angular/router": "^5.0.3",
    "@omt/angular-common": "^1.2.5",
    "base-64": "^0.1.0",
    "codemirror": "^5.23.0",
    "core-js": "^2.4.1",
    "jquery": "^3.1.1",
    "jquery-ui-dist": "^1.12.1",
    "jquery.scrollbar": "^0.2.11",
    "materialize-css": "^0.100.2",
    "rxjs": "5.5.2",
    "web-animations-js": "^2.2.2",
    "zone.js": "^0.8.4",
    "enhanced-resolve": "3.4.1"
  },
  "devDependencies": {
    "@angular/cli": "1.5.4",
    "@angular/compiler-cli": "^5.0.3",
    "@types/jasmine": "2.8.2",
    "@types/node": "~8.0.53",
    "codelyzer": "~4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "protractor": "~5.2.0",
    "ts-node": "~3.3.0",
    "tslint": "~5.8.0",
    "typescript": "2.4.2"
  }
}

Then I change typescript to "2.4.2" because angular
npm install

And when trying to run the project I get the error
ERROR in ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader/lib?{"ident":"postcss","sourceMap":false}!./node_modules/sass-loader/lib/loader.js?{"sourceMap":false,"precision":8,"includePaths":[]}!./src/styles.scss Module build failed:  @import "../node_modules/materialize-css/sass/components/mixins"; ^       File to import not found or unreadable: ../node_modules/materialize-css/sass/components/mixins. Parent style sheet: stdin       in /home/user/Documents/my-app/src/styles.scss (line 6, column 1) Error:  @import "../node_modules/materialize-css/sass/components/mixins"; ^       File to import not found or unreadable: ../node_modules/materialize-css/sass/components/mixins. Parent style sheet: stdin       in /home/user/Documents/my-app/src/styles.scss (line 6, column 1)     at options.error (/home/user/Documents/my-app/node_modules/node-sass/lib/index.js:291:26)  @ ./src/styles.scss 4:14-191  @ multi ./node_modules/jquery-ui-dist/jquery-ui.min.css ./node_modules/codemirror/lib/codemirror.css ./node_modules/codemirror/addon/hint/show-hint.css ./node_modules/codemirror/addon/merge/merge.css ./src/styles.scss
Additionally The content of styles.scss
/* You can add global styles to this file, and also import other style files */
@charset "UTF-8";

// Mixins
// @import "components/prefixer";
@import "../node_modules/materialize-css/sass/components/color";
// Reset
@import "../node_modules/materialize-css/sass/components/normalize";

/**
 * Variables: this is the custom file to configure theme variables, define it in each project
 */
@import "app/utils/sass/variables";

// components
@import "../node_modules/materialize-css/sass/components/global";
@import "../node_modules/materialize-css/sass/components/icons-material-design";
@import "../node_modules/materialize-css/sass/components/grid";
@import "../node_modules/materialize-css/sass/components/navbar";
@import "../node_modules/materialize-css/sass/components/roboto";
@import "../node_modules/materialize-css/sass/components/typography";
@import "../node_modules/materialize-css/sass/components/cards";
@import "../node_modules/materialize-css/sass/components/toast";
@import "../node_modules/materialize-css/sass/components/buttons";
@import "../node_modules/materialize-css/sass/components/waves";
@import "../node_modules/materialize-css/sass/components/forms/forms";
@import "../node_modules/materialize-css/sass/components/table_of_contents";
@import "../node_modules/materialize-css/sass/components/preloader";

.primary {
    background-color: $primary-color;
    &.dark {
        background-color: $primary-color-dark;
    }
    &.darker {
        background-color: darken($primary-color-dark, 15%);
    }
    &.light {
        background-color: $primary-color-light;
    }
    &.lighter {
        background-color: lighten($primary-color-light, 15%);
    }
}

... more class styles

Don't know what else to add. Thank you so much for your help :)

Looks like version 0.100.2 of materialize-css no longer contains a _mixins.scss file.  (contents of package). Are you using that file in your project somewhere?

Hi @clydin thank you so much for your help! yes, you're right materialize-css add new values that aren't defined in my styles and also deleted some stylesheets. Just got confused by the {"sourceMap":false,"importLoaders":1}!
Sorry, It was my fault for no research a bit more :)


[FEATURE] Dl-Delect - new UI request

Is your feature request related to a problem? Please describe.
The dl select UI can be improved with:
1- The menu when opening the dl select should be rounded not square.

2- the slot 'after-options' have left and right padding which make it impossible for the seperator to be full width

Describe the solution you'd like
for point 1 : make it rounded
for point 2 :remove the padding

Border radius should be: 2px


Creating documentation for Image component

🚧Work in progress 🚧
[LEVEL]/[COMPONENT]
TASK: Added a documentation for Image component
Types of changes

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

Description, Motivation and Context
I thought that Next-UI didn't have any Image component ,as it wasn't mentioned in documentation !Later I asked the community and they confirmed me Next UI has its Image component too!
So I am thinking to add a documentation for Image component

Please don't merge this , I am working on this 🚧🚧

Amazing 🚀 , thank you so much @devgossips looking forward to this

Hey @heysagnik any updates on this?

I was busy these days , So can't be active too much . I will soon update it

Hey @heysagnik, sorry but we had to implement this by ourselves, thank you anyway ✋🏻


feat: upgrade browser-lang

Closes #155
Closes #89
Browser lang to updated to support the case of de matching de-de

@jimmyn :pray:


[Bug]: OOM when a large project is compiled for the first time when generating BIRs

Description
This is originally observed when the openhealth projects are build for the first time. When we first compile a project the dependencies are downlaoded as Bala (source files) projects and compiled locally and the BIRs are generated locally. We cache these BIRs in ModuleContext and in BPackageSymbol for all the modules (dependencies) and consumes a lots of memory to keep these BIRs. If the project is big enough, there is a possibility that the program goes OOM.  for example, the below code snippet can cause a OOM
import ballerina/io as _;
import ballerinax/health.fhir.r4 as _;
import ballerinax/health.fhir.r4.international401 as _;
import ballerinax/health.hl7v2 as _;
import ballerinax/health.hl7v2.utils.v2tofhirr4 as _;
import ballerinax/health.hl7v23 as _;
import ballerinax/health.hl7v2commons as _;

We have done further optimisations on memory usages on lambda functions from the compiler frontend side and still we see OOM occurring due to compilation and BIR generation. Initially we saw that the OOM happened due to the capturedClosureEnv variable in lambda functions which we keep them unnecessarily. Once the links to those variables are removed now the OOM occur at the later stage. After analysing the heap dump, we saw that the cause for the OOM is the number of lambda functions. This is due to the number of module level annotations written. Each annotation is wrapped with a lambda function in compiler side. But if we further dig into the lambda functions, what actually take up the most of the memory is the body of the lambda functions, which are the annotation themselves.

In the above image, 1, 2, 3 are the ModuleContext, BPackageSymbol and the BIRPackage, which take up the most of the memory.
In ModuleContext, srcDocContextMap takes up the majority of the memory and the compilationUnit inside it, has lots of typeDefinitions and these type definitions have annotations which are represented by record literals. There is no way to remove those record literals as they are the real representation of the annotations. See the image below, there are a large number of DocumentContexts in a single ModuleContext.

In BPackageSymbol, We have the BIR stored as a field. This BIR mostly contains BIRFunctions mostly. Some module may have thousands of BIRFunctions due to annotation desugaring. But what takes up the memory is not the function itself, but the body of the function, which is the annotation itself. By looking at the Retained memory and comparing that to the shallow memory taken up by the function, I don't think removing the lambda functions will solve the problem.

With the front end changes we did to the compiler, the OOM occur only for a fresh build (Easily reproducible if we delete the BIR cache and keep the Bala cache). So to fix the OOM happening for such large projects, we have to either increase the memory allocation per JVM with the current design or we have to change the way we compile the dependencies and keeping them in the cache (right now we compile all the dependencies and keep their BIRs in the memory)
Adding @hasithaa @sameeragunarathne @az
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

[ ] Fix for 2201.7.x from compiler FE: https://github.com/ballerina-platform/ballerina-lang/issues/41448
[ ] Fix for 2201.8.x from compiler FE
[ ] Fix for master from compiler FE


Way of creating Delta table from pyspark as well as spark scala code.

[Enter feedback here]
I think someone should update the documentation to include how one can create a delta table using the column mapping feature using pyspark or spark scala code.
Only thing that one has to do is to add and option clause and set the option to set the column mapping property as below:
df.write.format("delta").option("delta.columnMapping.mode","name").saveAsTable("tableName")
This would be helpful to lot of people using this feature.

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

ID: 64f1b2b5-fb65-4bea-e7b9-7c5fb8de929b
Version Independent ID: 64f1b2b5-fb65-4bea-e7b9-7c5fb8de929b
Content: Column mapping on Azure Databricks - Azure Databricks
Content Source: databricks/delta/delta-column-mapping.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

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

@nikunjkakadiya2010
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)

@Naveenommi-MSFT did this content got added to the doc. Just wanted to make sure because i don't see that. Am i missing something that needs to be done here to get that added to the doc.


Run a different set of checks for java dependencies

We have a couple of modules running in /java/ folder. We should have a separate set of checks to perform the proper verification. No need to run the operator checks, just a quick compile check would suffice in this case.

@squakez I'll take care of it.


HELP

Hello, could you please share your environment configuration with me? I'm encountering a version compatibility issue with the mmcv version you mentioned earlier. For example, when I try to import to_tensor using from mmcv.transforms import to_tensor, I get the error "No module named 'mmcv.transforms'." I've been trying to resolve this for a long time without success. I would appreciate your help.

这个是我的环境配置：
cuda  ：11.3，
cudnn：8.2.1
pytroch：1.10.1
mmdet 2.14.0,
mmcv 1.4.0
mmdet3d 0.16.0


The new Style method tried to instantiate BootStyle twice when not creating Tk object first ( 1.0 api conversion )

The new Style method was created to return a singleton of the Bootstyle class, which is itself a subclass of ttk.Style

Fixed.  I was trying to update the background of the Tk object, but this was causing an instance of BootStyle to get created before the previous was instantiated.  I made a fix in how the legacy tk widgets are updated and this issue was fixed as a result.


[OP] Move reshape and flatten to nnvm

The FCompute directly calls IdentityCompute while the backward node uses _backward_copy. Also, nnvm::Tuple<int> is used as the type of shape, which may contain negative values.

Do we have tests for flatten and reshape?

We have test for Reshape but not for Flatten.

@piiswrong Test of Flatten has been added


Travis CI no longer have free plans, move to GitHub Actions?

Travis CI has cancelled their free plans (https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing). Open source projects (accounts?) now have limited build time, and have to apply for more credits (on a case-by case basis, meaning that it probably has to be applied for again and again and again and ...) .
The following post on Julia discourse outlines how to move to GitHub Actions (still free, as of today): https://discourse.julialang.org/t/easy-workflow-file-for-setting-up-github-actions-ci-for-your-julia-package/49765
@Datseris, shall we make the move to GitHub Actions?

moving to github actions would be great, I simply have no idea how to do it or how to make the docs buildable there as well

moving to github actions would be great, I simply have no idea how to do it or how to make the docs buildable there as well

As of now, the docs won't build at all on Travis, because the limit of built time is already reached for the JuliaDynamics organization. I will therefore attempt to make the transition to Github Actions straight away. It seems we just need to add a configuration file to the repo.
If migrating to Github Actions is successful for Entropies.jl, then we can start moving the rest of the JuliaDynamics packages too.

I got CI to run.

Testing works. I updated the badge on the Readme page.
The documentation for new tags is not being built, because the DOCUMENTER_KEY token can't be found. There's some access gotcha here that I haven't found yet. WIP.

So where do we see the tests? Like, if there is a test failing, where can we see it?

So where do we see the tests? Like, if there is a test failing, where can we see it?

@Datseris Copy pasting my comment from the other thread:
Go to https://github.com/JuliaDynamics/Entropies.jl, then in the menu, next to "Pull requests", go to "Actions". That page lists all workflows specified in the .github/workflows/ folder and their status. If you're quick now, you can see that a build got triggered for my latest push to master.
Otherwise, everything should behave as before - we just don't need to go to Travis to check the status of the builds.

Small red/orange/green circles also appear next to all commits/PRs/stuff that we test using some workflow.

I really don't understand. Typically, when the tests are run, a buttload of information is being printed, about which test is run, which test is passing, which test is failing. When I click on the CI badge now, it just shows a badge image.
Like, where are the tests actually done...?

The markdown code for the badge is
![CI](https://github.com/juliadynamics/Entropies.jl/workflows/CI/badge.svg)

This checks the status of the CI workflow. If the CI is successful, then the badge will appear green, I think. To check tests, you actually need to go to the "Actions" tab in the menu on github to check the status of each build.

If you click on either build in that list, you'll get to inspect the logs. For example:

I will give the workflow stages more informative names. Now they are called "Julia 1.5", "Julia 1" and "Documentation", but they should be called "Tests: Julia 1.5", "Tests: Julia 1.0", and "Documentation.

I will see if there is a way on GitHub Actions to get a link to the status of the most recent build. It would be nice to get redirected to the correct logs when pressing the badge.

Alright, thanks a lot. (BTW there is no reason to test on Julia 1)

The badge aside, I think we can conclude that this is working now.
Steps for moving to GitHub Actions from Travis (WIP)

Do using YourPackage, DocumenterTools, and run DocumenterTools.genkeys(YourPackage). Add the private key, naming it "DOCUMENTER_KEY" to "Secrets" in the repo settings (the name is irrelevant, but must match what appears in the workflow files below).  Then, add the public key to "Deploy keys" in the repo settings (call it "Documenter", for example).

Create a file called ci.yml in the .github/workflows/ folder of the repo. It should contain the following:

name: CI
on:
  pull_request:
    branches:
      - master
  push:
    branches:
      - master
    tags: '*'
jobs:
  test:
    name: Tests, Julia ${{ matrix.version }} - ${{ matrix.os }} - ${{ matrix.arch }} - ${{ github.event_name }}
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        version:
          - '1.5' # Replace this with the minimum Julia version that your package supports. E.g. if your package requires Julia 1.5 or higher, change this to '1.5'.
        os:
          - ubuntu-latest
        arch:
          - x64
    steps:
      - uses: actions/checkout@v2
      - uses: julia-actions/setup-julia@v1
        with:
          version: ${{ matrix.version }}
          arch: ${{ matrix.arch }}
      - uses: actions/cache@v1
        env:
          cache-name: cache-artifacts
        with:
          path: ~/.julia/artifacts
          key: ${{ runner.os }}-test-${{ env.cache-name }}-${{ hashFiles('**/Project.toml') }}
          restore-keys: |
            ${{ runner.os }}-test-${{ env.cache-name }}-
            ${{ runner.os }}-test-
            ${{ runner.os }}-
      - uses: julia-actions/julia-buildpkg@v1
      - uses: julia-actions/julia-runtest@v1
      - uses: julia-actions/julia-processcoverage@v1
      - uses: codecov/codecov-action@v1
        with:
          file: lcov.info
  docs:
    name: Documentation
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: julia-actions/setup-julia@v1
        with:
          version: '1'
      - name: Instantiate and install dependencies
        run: |
          julia --project=docs -e '
            using Pkg
            Pkg.develop(PackageSpec(path=pwd()))
            Pkg.instantiate()
            ENV["PYTHON"] = ""
            Pkg.build("PyCall")
            using Conda
            Conda.add("scipy")'
      - name: Generate documentation and deploy
        env: # needed for pushing to gh-pages branch
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          DOCUMENTER_KEY: ${{ secrets.DOCUMENTER_KEY }}
        run:
          julia --project=docs docs/make.jl
      - name: Doctests
        run: |
          julia --project=docs -e '
            using Documenter: doctest
            using Entropies
            doctest(Entropies)'

Including the following lines allows for the use of PyPlot in the docs.
ENV["PYTHON"] = ""
Pkg.build("PyCall")
using Conda
Conda.add("scipy")

Delete the original .travis.yml file from the repo.

Do a dummy PR to check that the preview documentation is being generated for the branch at https://juliadynamics.github.io/YourRepo.jl/previews/PRXX/. If you get an error saying that DOCUMENTER_KEY or GITHUB_TOKEN is not found in the logs for the documentation build stage, do a dummy commit to the gh-pages branches and re-trigger the build. Then it should work.

I will update this comment once I figure out how to link the badges, and fix codecov. For now, it should be enough to get CI up and running again.

@kahaaga do you know if you can modify the build to also test on windows?

I haven't tried yet, so I don't know. Do you need it for the rest of JuliaDynamics? If so, I can have a stab at it right away, while this is fresh in memory.

I only need it for DrWatson to be honest, the rest i only test on linux

I only need it for DrWatson to be honest, the rest i only test on linux

Ok, I'll make a test branch to see if I can get Windows builds up and running on Entropies.jl. It would be useful to have this piece of knowledge myself for the future.  Then you can just copy that for DrWatson.

Ok, I'll make a test branch to see if I can get Windows builds up and running on Entropies.jl. It would be useful to have this piece of knowledge myself for the future. Then you can just copy that for DrWatson.

@Datseris It was actually super easy. You just need to supply a list of systems for which to test on. See #46 for an open PR that uses testing on Linux, macOS and Windows (and feel free to close the PR - not merge - once you're happy inspecting).
I updated the example above to include testing for macos, windows and linux. Adjust as needed. A full list of available systems can be found at https://docs.github.com/en/free-pro-team@latest/actions/reference/specifications-for-github-hosted-runners

Anyways: I'm happy just testing on Linux for this repo, so I'm closing the issue.

thanks, wonderful.

@kahaaga I've checked this section here https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#GitHub-Actions  on TagBot, which is important. Would you mind adding to your master post above that one should add the line
          ssh: ${{ secrets.DOCUMENTER_KEY }}

to the with section of the TagBot action file? Otherwise you don't get documentation builds for the stable releases (which quite often are the most important)

Otherwise you don't get documentation builds for the stable releases (which quite often are the most important)

Ah, yes, sorry! Forgot to add that. That bit is actually the crucial part that took some time to figure out. Thanks for spotting!

One thing that may missing here that travis handled:
The CI action is triggered when the PR is created—fine. If another commit is pushed to the branch whilst the CI tests are still unning, a second action triggers new tests (good), but does not cancel the original (no longer required).
Think it's possible to organise these actions to cancel the obsolete run?

@Libbum Yes, that is possible. Adding the following first step before the tests, and before the doc builds, does precisely that:
- name: Cancel ongoing documentation builds for previous commits
        uses<EMAIL_ADDRESS>        with:
          access_token: ${{ github.token }}

I made a test PR (#48) that does this for this repo. Check the list of actions for the repo.
You'll see that when I push a new commit before the tests/doc build from the previous commit were finished, those ongoing builds were cancelled when pushing a new commit. The builds that were cancelled will have a grey symbol with an exclamation mark next to them, instead of the regular green "success" or red "failure" symbols, like so:

I updated the example above, so that both doc builds and tests are cancelled on new commits.

Awesome. Great job sorting this out!


Save FitData to Excel file

One should be able to save FitData object to an excel file. Example code:
from eddington import linear, FitData
from pathlib import Path

data = FitData.random(linear)
output_path = Path("/path/to/output.xlsx")

data.save_excel(output_path)

I'm on it

In what format do you want the FitData object to be saved?
Option 1:

x
xerr
y
yerr

rec. 1

rec. 2

rec .3

rec .4

Option 2:
Export to excel the full raw data property, along with the other properties (records_indices, column indicators, etc.)

Option 1, but extended. here's an example:
from collections import OrderedDict
from pathlib import Path

from eddington import FitData

raw_data = OrderedDict(
    [
        ("a", [1, 2, 3]),
        ("b", [4, 5, 6]),
        ("c", [7, 8, 9]),
        ("d", [10, 11, 12]),
        ("e", [13, 14, 15]),
        ("f", [16, 17, 18]),
    ]
)
fit_data = FitData(
    data=raw_data, x_column="b", xerr_column="c", y_column="a", yerr_column="f"
)
output = Path("/path/to/output.excel")
fit_data.save_excel(output)

As you can see, we have the selected columns which are a, b, c and f (not in that order), but also have additional columns d and e. The output excel file should contain all of those columns, d and e included.
The reason is that if I want to reload the data later, like that:
...   # later in the code
new_fit_data = FitData.read_from_excel(output, sheet_name)

I'll get the exact same data that I saved.
The same goes for #53 .


feat(Order/Max): add IsTop.isMax_iff and IsBot.isMin_iff

Upstreamed from the Carleson project.
Co-authored-by: Floris van Doorn

bors r+


ci: GitHub workflows fail to build container-images for multiple architectures

#89 changed how architectures are passed to the GitHub workflows. It seems that #91 was built only on one platform, instead of linux/amd64, linux/arm64 and linux/arm/v7.
For some reason the secrets.BUILD_PLATFORMS does not seem to be set for GitHub Actions?

Maybe there is some GitHub access limitation:

You can use and read encrypted secrets in a workflow file if you have access to edit the file.

The user creating the PR, will not have access to edit the file directly. Creating a PR from a branch in the local repository (#90) did work. That branch might have "access to edit the file"?

The behaviour is intentional and documented in a GitHub security guide:

Workflows triggered using the pull_request event have read-only permissions and have no access to secrets.

We'll need to think of an other way to limit building for multiple platforms.

Yes due to security reason its done, sorry i forgot about it :( do we need to revert back to the PR introduced this one?

Yes due to security reason its done, sorry i forgot about it :( do we need to revert back to the PR introduced this one?

Reverting is probably not needed. The builds after merging build all platforms, so that is fine for now.
I'd like some way of configuring it in a single place, so that it is easy to adjust in forks of this repo. Just not sure what/where that configuration should be done.


Feature: allow speccy to watch and resolve

Detailed description
Many cli tools allow you to -w watch changes to a specified file and re-run execution for the differences.
I propose adding a -w flag to speccy allowing similar behaviour.
speccy resolve -w -v -j myspec.yml -o ~/elsewhere/projects/specs/myapi.yml

Context
Proposed documentation workflow is roughly:

Define a spec + schema
'resolve' the spec into an output asset. Publish (somewhere)
External docs  (static site, using redoc to inline API specs)

This workflow would allow a smoother edit-and-preview workflow for the above toolchain.
Current toolchain uses speccy 0.7.2+

Alternative / Workaround
It is possible to set this up as an npm run command using npm-watch:
{
  ...
  "watch": {
    "test": {
      "patterns": ["**/*"]
    }
  },
  "scripts": {
    "test": "node_modules/.bin/speccy lint myspec.yml -j",
    "watch": "npm-watch"
  },
  "devDependencies": {
    "npm-watch": "^0.3.0",
    "speccy": "^0.7.2"
  }
  ...
}

This can then be invoked as npm run watch as part of your in-IDE editing.
This could then limit this feature request to "Provide a useful progress bar for # of lint failures" so that npm-watch is able to give you an idea of how far through fixing things are you.

Is this really a common CLI feature?  Sounds more like a job for an external utility that watches for changes to a file, as opposed to something that's embedded into Speccy.

Agreed with @bburtin, this was a nice idea but it's a big effort and will distract from other priorities. If somebody finds a nice simple way to bake it in then yay, otherwise it's not going to happen for a long time.

I've added a pull request to add watch details to the README file.
https://github.com/wework/speccy/pull/362


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 1380 ms

Resolved: Bofrost.fr performance has improved in fa8e27c.


Allow for header based auth.

This should allow a Dispatch to be able to respect a given header as it's the source of identity.
If you are bringing your own authentication layer you can set DISPATCH_AUTH_HEADER_KEY to the email address of the user making the request. e.g. (x-amzn-oidc-identity for ALBs, https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-authenticate-users.html)

cc @willbengtson


Prevent partially configured jobs from breaking the scheduler

This is a fix for #125.

@matuusu: Thanks for your feedback & coming up with an initial fix. I spent some time to implement this "jobs schedule themselves" approach we chatted about in this PR. Any thoughts on this?


pinning distro

Over a long period of time, there are going to be base upgrades that will break Binders. The easiest to see is upgrading our base image in such a way that breaks apt.txt. We are probably going to need to allow users to specify the base distro, as Travis has done with image: trusty, etc., and make transitions in our base image extremely infrequent.
Even if we eventually drop support for an old base image, allowing users to specify it will at least have a reproducibility pointer, indicating what they were building on.

Should we make this an 'apt.yaml'?

It seems to me that a binder.yaml is going to make the most sense, rather than proliferating numerous small files.

@minrk I feel like the repo2docker repo is a better place to discuss this. I'm gonna look over there to see if this conversation is already happening, and if not then I'm gonna open there and close this.

closing this in favor of: https://github.com/jupyter/repo2docker/issues/166


Update parent only when present in db

'Quick fix' to get rid of the "NoMethodError: undefined method `tag_type' for
nil:NilClass" error, see here:
https://github.com/alphagov/panopticon/blob/master/app/queue_consumers/tagging_updater.rb#L56
We should investigate why the item is not present in Panopticon's db.

👍 from me, would like one other review though.

This seems legit. I'd be curious to see the items where this failed though, do you have an example?

@tijmenb https://errbit.publishing.service.gov.uk/apps/52f0ceeb0da1152f0b000003/problems/578754826578637e7abf0000

Merging.


[use case] Edit project information

[ ] Edit various project details

For now, in #151, you can edit just the name and the lane of a certain project. (validations on the formulary are not being made)

https://github.com/fastlane/ci/pull/182


Handle begin & end block channel events

Closes: #1793
Description
This PR is mostly based on the code that was removed in PR #1172.

PR author checklist:

[x] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[x] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

[x] Reviewed Files changed in the GitHub PR explorer.
[x] Manually tested (in case integration/unit/mock tests are absent).

Tested hermes listen with the following patch (https://github.com/agoric-labs/cosmos-sdk/tree/mfig-endblock-ibc-event) and it seems to work.
diff --git a/x/staking/module.go b/x/staking/module.go
index b5e778755..624b33a49 100644
--- a/x/staking/module.go
+++ b/x/staking/module.go
@@ -23,6 +23,7 @@ import (
        "github.com/cosmos/cosmos-sdk/x/staking/keeper"
        "github.com/cosmos/cosmos-sdk/x/staking/simulation"
        "github.com/cosmos/cosmos-sdk/x/staking/types"
+       channeltypes "github.com/cosmos/ibc-go/modules/core/04-channel/types"
 )

 var (
@@ -171,12 +172,21 @@ func (am AppModule) BeginBlock(ctx sdk.Context, _ abci.RequestBeginBlock) {
 // EndBlock returns the end blocker for the staking module. It returns no validator
 // updates.
 func (am AppModule) EndBlock(ctx sdk.Context, _ abci.RequestEndBlock) []abci.ValidatorUpdate {
-       // FIGME: Raise an event in end block.
-       AttributeValueCategory := "ibc_channel"
+       ctx.EventManager().EmitEvents(sdk.Events{
+               sdk.NewEvent(
+                       channeltypes.EventTypeChannelOpenInit,
+                       sdk.NewAttribute(channeltypes.AttributeKeyPortID, "transfer"),
+                       sdk.NewAttribute(channeltypes.AttributeKeyChannelID, "channel-0"),
+                       sdk.NewAttribute(channeltypes.AttributeCounterpartyPortID, "transfer"),
+                       sdk.NewAttribute(channeltypes.AttributeCounterpartyChannelID, "channel-0"),
+                       sdk.NewAttribute(channeltypes.AttributeKeyConnectionID, "connection-0"),
+               ),
+       })
+
        ctx.EventManager().EmitEvents(sdk.Events{
                sdk.NewEvent(
                        sdk.EventTypeMessage,
-                       sdk.NewAttribute(sdk.AttributeKeyModule /* channeltypes. */, AttributeValueCategory),
+                       sdk.NewAttribute(sdk.AttributeKeyModule, channeltypes.AttributeValueCategory),
                ),
        })
        return EndBlocker(ctx, am.keeper)

I think the PR is ready, but let's let @michaelfig test it out against Agoric devnet and give the final approval.

Thanks, everybody, for your work on this!
This is high up on my list of priorities.  @dckc and I are doing IBC testing, so we'll be able to try a programmatic outbound channel init from an Agoric (dynamic IBC) smart contract in the next day or three.
Will keep you posted!

good news / bad news:
We were able to initiate a channel using JavaScript:
hermes_1  | 2022-02-02T15:55:16.352132Z DEBUG ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: starts processing Some(
hermes_1  |     OpenInitChannel(
hermes_1  |         OpenInit(
hermes_1  |             Attributes {
hermes_1  |                 height: Height {
hermes_1  |                     revision: 0,
hermes_1  |                     height: 11213,
hermes_1  |                 },
hermes_1  |                 port_id: PortId(
hermes_1  |                     "port-4",
hermes_1  |                 ),
hermes_1  |                 channel_id: Some(
hermes_1  |                     ChannelId(
hermes_1  |                         "channel-2",
hermes_1  |                     ),
hermes_1  |                 ),
hermes_1  |                 connection_id: ConnectionId(
hermes_1  |                     "connection-1",
hermes_1  |                 ),
hermes_1  |                 counterparty_port_id: PortId(
hermes_1  |                     "transfer",
hermes_1  |                 ),
hermes_1  |                 counterparty_channel_id: None,
hermes_1  |             },
hermes_1  |         ),
hermes_1  |     ),
hermes_1  | )

but then
2022-02-02T15:55:21.496369Z DEBUG ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: resolving channel version by retrieving destination chain app version chain_id=cosmoshub-testnet port_id=transfer ctx=ChanOpenTry

2022-02-02T15:55:57.279753Z  WARN ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: cannot resolve channel version for unknown port id 'port-4'

hermes_1  | 2022-02-02T15:55:55.768779Z TRACE ThreadId(18) fetching header height=0-204
hermes_1  | 2022-02-02T15:55:57.279380Z DEBUG ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: [agoric -> cosmoshub-testnet:07-tendermint-141] MsgUpdateAnyClient from trusted height 0-203 to target height 0-11221
hermes_1  | 2022-02-02T15:55:57.279575Z DEBUG ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: resolving channel version by retrieving destination chain app version chain_id=cosmoshub-testnet port_id=transfer ctx=ChanOpenTry
hermes_1  | 2022-02-02T15:55:57.279753Z  WARN ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: cannot resolve channel version for unknown port id 'port-4'
hermes_1  | 2022-02-02T15:55:57.279872Z ERROR ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: Failed ChanInit with error: failed during a query for the app version to chain id cosmoshub-testnet: failed to fetch application version: could not resolve channel version because the port is invalid: port-4
hermes_1  | 2022-02-02T15:55:57.279946Z ERROR ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: aborting after encountering fatal error: Worker failed after 7 retries
hermes_1  | 2022-02-02T15:55:57.279978Z  INFO ThreadId(35) channel{channel=channel::channel-2/port-4:agoric -> cosmoshub-testnet}: terminated

In short, this particular PR looks good and does what it says it should.
Go ahead and land!


Lineage not shown after Databrick hive metadata is scanned to Purview

Followed documentation of scanning Databrick hive metadata store at location https://learn.microsoft.com/en-us/azure/purview/register-scan-hive-metastore-source
I could see the hive assets being scan and showed up, but the lieange of a joined table does not show up.
Please help

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

ID: 686544b4-81d2-923e-27d6-992132ac0feb
Version Independent ID: 9ef5f254-a64f-c223-73e6-cf8e54ee4d3a
Content: Connect to and manage Hive Metastore databases - Microsoft Purview
Content Source: articles/purview/register-scan-hive-metastore-source.md
Service: purview
Sub-service: purview-data-map
GitHub Login: @linda33wj
Microsoft Alias: jingwang

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

@blacklabnz -
Can you tell us what version of Databricks you're using? It needs to be version 8.0 or higher, or you may have errors/missing data when you scan your source.
We can work together here to discover what is going on, but you can also reach out to Azure Support. They have folks in all timezones that can help troubleshoot an issue, while our team monitoring the documentation is much smaller.

@whhender
hi mate, thanks for responding, the version of databricks cluster is 11.1, I dont believe there is anything missed, because he autoscan did capture the assets in hive metastore. It was just the lineage that was now shown.
I ma not sure that if I missed anything the scan would probably not even work at all.
happy to find other more info needed for further troubelshooting. cheers

@blacklabnz - thanks for bringing up the issue. Lineage is supported between tables and views; there is no lineage among tables.
If you meant you don't see lineage on a view, to further troubleshoot your case, could you file a support ticket? We'd need to collect more context of your scan run, logs and Databricks table/view definition there to check what went wrong.

hi @linda33wj, thanks for attending this, I will put the code in to show what I am doing:
First I created two table with data
df_trip = (spark.read
    .options(header="True")
    .csv("abfss://land@xxxx.dfs.core.windows.net/trip_data/green_tripdata_2019-12.csv.gz"))

df_trip = (spark.read
    .options(header="True")
    .csv("abfss://land@xxxx.dfs.core.windows.net/trip_data/green_tripdata_2019-12.csv.gz"))

Then I joined those tables together to simulate a transformation
%sql
create or replace table riki.nyctaxi_curated_tbl using delta
as(
  with a as (
    select
      lpep_pickup_datetime as pickup_time,
      lpep_dropoff_datetime as dropoff_time,
      PULocationID,
      DOLocationID,
      z.Zone as pickup_zone,
      z.LocationID as pickup_zone_id,
      x.Zone as dropoff_zone,
      x.LocationID as dropoff_zone_id
    from riki.nyctaxi_trip t left join riki.nyctaxi_zone z on t.PULocationID = z.LocationID left join riki.nyctaxi_zone x on t.DOLocationID = x.LocationID
  )
select pickup_time, dropoff_time, pickup_zone, dropoff_zone from a);

When scannning the hive metadata store, I could see those tables scanned as assets but I could not see the lineage.
Did I do something wrong here ?
Thanks

@blacklabnz - Since you're just using two tables, I don't think you'll pick up any lineage. If the data was represented in a view, you would see the lineage between the table and the view, but lineage between just two tables isn't supported.
@linda33wj - please do confirm that I have a correct understanding as well.

hi @whhender
I am using two tables to join together and form another table, if you look through my previous code sample. I would expect a lineage relationship to be present like the following at least:
table a  --
                \
                  --- table c
                /
table b --

hope this makes helps and let me know if further explanation is needed. cheers

@blacklabnz - I have confirmed that at this time there is no lineage between tables. There is only lineage between tables and views.
You can make a feature request for table-to-table lineage here on our feedback page.

#please-close


Reorder how context transforms are applied

Doodle currently applies the inner most ContextTransform. E.g.
circle(10).fillColor(Color.red).fillColor(Color.blue)
will produce a red circle. A more sensible semantics is to produce a blue circle.

Additionally circle(10).fillColor(Color.red).lineWidth(10.0) and circle(10).lineWidth(10.0).fillColor(Color.red) both produce circle with standard line width (fill color seem to be overlay/override it). Without fillColor the line width is correct

Fixed in 0.9


create_channel does not work with ChannelType::Category

I was attempting to create a category using serenity::model::GuildId::create_channel:
let guild = msg.guild_id().unwrap();
let res = guild.create_channel("test-category", ChannelType::Category);
match res {
    Ok(e) => println!("Worked out because {}", e),
    Err(e) => println!("Failed because of {}", e)
}

create_channel works with the other channel types, and seems to only fail with ChannelType::Category.
Looking a step deeper, I tried creating a category with serenity::http::create_channel, mirroring what is done in GuildId::create_channel:
let guild = msg.guild_id().unwrap();
let _category = create_channel(guild.0, &json!({
    "type": ChannelType::Category.name(),
    "name": "voice-category".to_string(),
}));

As should be expected, this also fails.
However, again, switching to a different type works fine:
let guild = msg.guild_id().unwrap();
let _voice = create_channel(guild.0, &json!({
    "type": ChannelType::Voice.name(),
    "name": "voice-category".to_string(),
}));

If I switch out the ChannelType::Category with 4 or ChannelType::Category as i64 I am able to create a category.

Ah yeah, type doesn't have a string based "category" type like "voiceand "text" do.
Anyway will fix this in a moment.

e57b510.


Fixed match() return type of all Value impls

Fixes #968

Current coverage is 95.89%

Merging #1010 into master will decrease coverage by -0.10% as of c0e0740

@@            master   #1010   diff @@
======================================
  Files           74      74
  Stmts         9078    9100    +22
  Branches      1713    1713
  Methods          0       0
======================================
+ Hit           8714    8726    +12
+ Partial        106     105     -1
- Missed         258     269    +11

Review entire Coverage Diff as of c0e0740

Powered by Codecov. Updated on successful CI builds.


Exception Received for Host Value Parsing During Build

$ coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/build.cfg -t
Traceback (most recent call last):
  File "inquisition.py", line 172, in <module>
    main()
  File "inquisition.py", line 159, in main
    erudite.startAnomalyDetectionEngine()
  File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 153, in startAnomalyDetectionEngine
    self.hostStore.append(hostEntry['host_val'])
KeyError: 'host_val'
Traceback (most recent call last):
  File "inquisition.py", line 172, in <module>
    main()
  File "inquisition.py", line 159, in main
    erudite.startAnomalyDetectionEngine()
  File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 153, in startAnomalyDetectionEngine
    self.hostStore.append(hostEntry['host_val'])
KeyError: 'host_val'

It appears that for some reason, the query is returning data from a previous query:
            while True:
                # read in list of already known hosts
                # clear current master host list
                self.hostStore = []

                # fetch fresh host list from inquisition DB
                self.lgr.info('fetching list of already known hosts')
                freshHostStore = self.fetchKnownHostData()
                # traverse through list of host records to add raw host_val entries to master host list
                for hostEntry in freshHostStore:
                    print('HE: ' + str(hostEntry))
                    self.hostStore.append(hostEntry['host_val'])

$ coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/bad_build.cfg -t || sh -c "exit 0"
HE: {'field_name': 'host'}
Traceback (most recent call last):
  File "inquisition.py", line 172, in <module>
    main()
  File "inquisition.py", line 159, in main
    erudite.startAnomalyDetectionEngine()
  File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 159, in startAnomalyDetectionEngine
    self.hostStore.append(hostEntry['host_val'])
KeyError: 'host_val'

The data that's being printed is from this function, also in Erudite:
    def fetchKnownHostData(self):
        """
        Fetches known host records from inquisition DB and inserts them into the local host store

        :return: dict
        """

        # define sql
        sql = """
                SELECT
                    host_val
                FROM
                    KnownHosts
              """

        # execute query
        with self.inquisitionDbHandle.cursor() as dbCursor:
            dbCursor.execute(sql)

            # fetch results
            hosts = dbCursor.fetchall()

        return hosts

Even weirder, this issue only happens during some calls :/
$ coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/bad_build.cfg -t || sh -c "exit 0"
H: ()
H: ()
H: ()
H: ()
H: ()
H: ()
H: ()
H: [{'field_name': 'host'}]
HE: {'field_name': 'host'}
Traceback (most recent call last):
  File "inquisition.py", line 172, in <module>
    main()
  File "inquisition.py", line 159, in main
    erudite.startAnomalyDetectionEngine()
  File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 159, in startAnomalyDetectionEngine
    self.hostStore.append(hostEntry['host_val'])
KeyError: 'host_val'
H: ()
H: [{'field_name': 'host'}]
HE: {'field_name': 'host'}
Traceback (most recent call last):
  File "inquisition.py", line 172, in <module>
    main()
  File "inquisition.py", line 159, in main
    erudite.startAnomalyDetectionEngine()
  File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 159, in startAnomalyDetectionEngine
    self.hostStore.append(hostEntry['host_val'])
KeyError: 'host_val'

This seems to be either a bug in pymysql or mysql itself, OR mysql running on Travis. I'm not able to reproduce on my local machine, so we'll code around this issue for now unless it's able to be reproduced elsewhere.

Fixed in commit https://github.com/magneticstain/Inquisition/commit/8fb7a2d1344714abd0fd097724628878ac1dbc72


kill command and specifiable authkeys arg

The specified keys allows running the server like server --authorizedkeys c:\\users\\christopher\\.ssh\\id_rsa.pub <IP_ADDRESS>:44444 which means you dont need to copy/create an adjacent authorised keys file. Just slightly easier, especially for debugging but also conceivably in regular scenarios.
The kill command wipes a connected client, which can be useful if the same client is connected multiple times for whatever reason and teh user wants to tidy things.

This looks good! Only change I'd like to make is that the client is explicitly instructed to kill itself. As you can ask clients to reconnect if server connection is lost.
Currently, if a client is set to reconnect killing wont close the program.

Cool! I've switched to using a channel to send a kill command, rather than closing the connection.

Why are you pausing in both the server and client?
Also on the server side, you should still kill the connection (in case is unresponsive)

Why are you pausing in both the server and client?
Also on the server side, you should still kill the connection (in case is unresponsive)

if i try to kill the connection on the server side it will error about trying to re-use a closed connection. i suppose i could catch and discard that error, taking it as proof of success?
the double pause is so the server waits until the client is dead before reporting success


About Dialog Can be Resized

About Dialog can be resized causing peculiar states like this:

Also, there is no space between Help and About


Ignore errors about bad autocomplete values

eh? why?

Well, the thought was that it doesn't tend to break anything beyond autocomplete itself, so it's not usually germane to whatever JS/CSS bug the testcase was submitted for, kinda like the other stuff we already ignore (https://github.com/cvrebert/lmvtfy#deliberately-ignored-errors ). The fact that the spec'd values didn't validate also wasn't helping.
But since that validator bug has now been fixed, this isn't nearly as necessary anymore.


Extend server client ResetStatistics() to reset all client statistics not only channel...

Currently the class MqttClientStatus => ResetStatistics() resets only channel related stats (BytesSent and BytesReceived) but object itself contains more statistic values..
The pull request extend behaviour to reset all contained statistic as SentPacketsCount,ReceivedPacketsCount, SentApplicationMessagesCount, ReceivedApplicationMessagesCount
So if you call  ResetStatistics(); all stats for particular client gets reseted from its stat object....
Original MqttClientStatus object...
    public sealed class MqttClientStatus
    {
        public MqttClientStatus(MqttClient client);

        public MqttSessionStatus Session { get; set; }
        public long SentPacketsCount { get; }
        public long ReceivedPacketsCount { get; }
        public long SentApplicationMessagesCount { get; }
        public long ReceivedApplicationMessagesCount { get; }
        public DateTime LastNonKeepAlivePacketReceivedTimestamp { get; }
        public long BytesSent { get; }
        public DateTime LastPacketSentTimestamp { get; }
        public DateTime ConnectedTimestamp { get; }
        public MqttProtocolVersion ProtocolVersion { get; }
        public string Endpoint { get; }

        public string Id { get; }
        public DateTime LastPacketReceivedTimestamp { get; }
        public long BytesReceived { get; }

        public Task DisconnectAsync();
        public void ResetStatistics();
    }

 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.:x: damikun sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Im having issue to sign
Error
There is no CLA to sign for dotnet/MQTTnet

(<!DOCTYPE html>   <meta charset="utf-8"> <title>Error</title>
MongoTopologyClosedError: Topology is closed
    at processWaitQueue (/home/site/wwwroot/node_modules/mongodb/lib/sdam/topology.js:608:46)
    at Topology.selectServer (/home/site/wwwroot/node_modules/mongodb/lib/sdam/topology.js:317:9)
    at /home/site/wwwroot/node_modules/mongodb/lib/operations/execute_operation.js:18:29
    at maybePromise (/home/site/wwwroot/node_modules/mongodb/lib/utils.js:496:5)
    at executeOperation (/home/site/wwwroot/node_modules/mongodb/lib/operations/execute_operation.js:16:37)
    at FindCursor._initialize (/home/site/wwwroot/node_modules/mongodb/lib/cursor/find_cursor.js:54:50)
    at next (/home/site/wwwroot/node_modules/mongodb/lib/cursor/abstract_cursor.js:445:16)
    at /home/site/wwwroot/node_modules/mongodb/lib/cursor/abstract_cursor.js:177:13
    at maybePromise (/home/site/wwwroot/node_modules/mongodb/lib/utils.js:496:5)
    at FindCursor.next (/home/site/wwwroot/node_modules/mongodb/lib/cursor/abstract_cursor.js:173:41)
    at Collection.findOne (/home/site/wwwroot/node_modules/mongodb/lib/collection.js:232:76)
    at /home/site/wwwroot/node_modules/connect-mongo/build/main/lib/MongoStore.js:207:50
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
   )

Thank you for your contribution. Good work 👍


Decouple aliases from pass names

We should decouple the alias mechanism from pass names. An alias should also configure compiler options like the sharing thresholds. This will let us define things like “-opt-size” which configures the pass pipeline to reduce the resource usage as aggressively as possible.
This will require some redesign of the pass manager but that is long overdue anyways with other UX issues.

Sounds wise!


Add namespace service to catalog broker capabilities

ECS has the capability to create a new namespace where an application owner can create/delete his/her own buckets for fun & [company] profit.  The ECS broker, rather than creating only buckets, can also support the creation of namespaces.  This would be pretty cool.
The service for a namespace would be configured in the catalog, just like bucket services/plans are now, with many similar options.  configuration for this might looks something like:
catalog:
  services:
    - id: f3cbab6a-5172-4ff1-a5c7-72990f0ce2ab
      name: ecs-namespace
      description: Elastic Cloud Namespace
      bindable: true
      planUpdatable: true
      tags:
        - namespace
        - object
      metadata:
        displayName: ecs-namespace
        imageUrl: http://www.emc.com/images/products/header-image-icon-ecs.png
        longDescription: EMC Elastic Cloud Storage (ECS) namespace for creating object storage buckets and CAS pools.
        providerDisplayName: EMC Corporation
        documentationUrl: https://community.emc.com/docs/DOC-45012
        supportUrl: http://www.emc.com/products-solutions/trial-software-download/ecs.htm
      plans:
        - id: 8e777d49-0a78-4cf4-810a-b5f5173b019e
          name: limited
          free: true
          description: Free Trial
          quota-limit: 20
          quota-warning: 18
          bucket-limit: 5
          expiration: {days: 30}
          metadata:
            costs:
              - amount:
                  usd: 0.0
                unit: MONTHLY
            bullets:
              - Shared object storage
              - 20 GB Storage
              - Ability to create up to 5 buckets

For more info on this, be sure to take a look at PR #51 which is the WIP for this feature.  Since we're adding a new service definition, we're going to be changing the configuration format (for the better), so prior to completion, we'll be updating the docs.


Custom input and object in v-model

Vue.js version
2.0.2
Reproduction Link
http://jsfiddle.net/df4Lnuw6/129/
Steps to reproduce
When using an object in v-model of a custom input and then I try to clean it, it doesn't work. In a native input it cleans but still not printing the emitted value {{ form. email }}. If I declare all properties in the form variable like this:
data() {
  form: {
    name: null,
    email: null,
  }
}`

the problem is solved, but for me, the main advantage of using objects in this case is not to have to declare all form fields.
Am I doing something wrong or this is the only way to bind data using v-model and objects? I'd like the object values were updated as the same way normal variables do.

This is because you didn't declare form.name when you set it as an empty object so it's not even reactive. Fixed: http://jsfiddle.net/df4Lnuw6/130/


Release: 2.1.1

@hutchic can we close this PR?

Closing this PR, as we're a few patch versions ahead of this now.


chore: make examples work on the repo-local versions of packages

Which problem is this PR solving?
My intention was to set up the examples so that those can be run with the unreleased versions of the packages local to the repo(using lerna bootstrap) and thus make it easier for anyone to hack on and contribute to the project.
I ran into an issue that probably comes from patching the module loading and detecting which instrumentations to load. There is no active context when I run examples/http/server.js, which makes me believe @opentelemetry/plugin-http was never loaded.
Has anyone ever experienced similar symptoms / issues with plugin detection?
Short description of the changes

The package names in examples had to be unified so that the exclusions for publishing could be applied easier for examples, which we never want to publish as packages.

Poking around a little more I see that indeed PluginLoader is unable to find the module:
PluginLoader#load: trying to load<EMAIL_ADDRESS>PluginLoader#load: applying patch to<EMAIL_ADDRESS>using @opentelemetry/plugin-http module
PluginLoader#load: could not load plugin @opentelemetry/plugin-http of module http. Error: Cannot find module '@opentelemetry/plugin-http'
Require stack:
- /packages/opentelemetry-instrumentation/build/src/platform/node/old/PluginLoader.js
- /packages/opentelemetry-instrumentation/build/src/platform/node/old/autoLoader.js
- /packages/opentelemetry-instrumentation/build/src/platform/node/index.js
- /packages/opentelemetry-instrumentation/build/src/platform/index.js
- /packages/opentelemetry-instrumentation/build/src/autoLoader.js
- /packages/opentelemetry-instrumentation/build/src/index.js
- /examples/http/tracer.js
- /examples/http/server.js

Getting closer..

Solutions that do not involve changing the code, since we wouldn't want to leak our repo plumbing into published packages:

Create links of each of the packages into packages/node_modules: packages/node_modules/@opentelemetry/plugin-http --> packages/opentelemetry-plugin-http, etc, and maintain that list of packages that need to be referenced OR
Rename all the directories inside packages and add the folder to NODE_PATH for examples.

Nr 2 seems a lot more reasonable and less hacky to me. Would that be acceptable?
@dyladan @obecny @vmarchaud

What about using local paths to reference local versions ? That would means they only works within the repo but i don't expect users to copy/paste package.json anyway

That is a possibility but makes the decision to either work with a published version OR a local one for the developer(for the latter). I was hoping to find one that does not, so that someone who just wants to run an example, not even build the whole thing, which, I must admit, is somewhat cumbersome, can do that by npm install; npm run and that's it!
Since the @opentelemetry/plugin-http resolves from the example code but not from the instrumentation code, I have another alternative: How about we preregister the plugin in the example code?
Something roughly in the lines of api.register('http', require('@opentelemetry/plugin-http')); and then short-circuit in the plugin loader if it's already registered. Not sure if the API is already there or not.

Nr 2 from the previous post is not going to work because the folder has to contain scope "@opentelemetry" and making NODE_PATH relative would be a tiny bit more involved than I'd like.

As a POC, I committed a version that is actually changing the behaviour of module loading and is also immune to the symlinks as long as the package is present in the main module - which makes total sense.

This is only a problem with the plugins. I believe the instrumentations should not suffer from this and should symlink just fine.

:crossed_fingers: I intended to double-check, but got busy today. If that's alright I will leave this PR open for now with a note that most of what's here will be deprecated anyways.
When will the old plugin code be removed?

Thanks!
The getting started guide still uses the old plugins and autoloads(meaning the developer doesn't have to require plugins/instrumentation) the instrumentation.
As I understand, enabling an instrumentation without manually requiring it first will not be possible in the future?

As I understand, enabling an instrumentation without manually requiring it first will not be possible in the future?

We also have a set of autoinstrumentation packages which automatically enable all instrumentations

That does touch upon https://github.com/open-telemetry/opentelemetry-js-contrib/issues/422 a bit (one of the commits), but it's not really relevant anymore.


Ability to compose domain files

Description of Problem:
Currently there's no opinions that Rasa enforces about being able to split the domain file into multiple files (unlike stories e.g.).
We ran into this issue when trying to model a rule based system within a chatbot where we ended up with 3000+ slots and 1000+ actions for that functionality within the chatbot. This main the domain file increasingly frustrating to add to and work with.
Overview of the Solution:
Spent some time last night writing a domain composer for our use case and wanted to get thoughts from the community about it.
here's the structure of my data/ folder:
├── domain.yml
├── domains
│   ├── hotel_booking
│   │   ├── actions.yml
│   │   ├── forms.yml
│   │   ├── intents.yml
│   │   └── slots.yml
│   ├── common
│   │   ├── actions.yml
│   │   ├── forms.yml
│   │   ├── intents.yml
│   │   └── slots.yml
│   ├── flight_booking
│   │   ├── actions.yml
│   │   ├── forms.yml
│   │   ├── intents.yml
│   │   └── slots.yml
└── stories.md

when a dev runs make build:domain which uses the composer script aforementioned they get a data/domain.yml file, which can then be used for training, that looks like this:
actions:
  <all action values>
forms:
  <all form values>
intents:
  <all intent values>
slots:
  <all slot values>

Questions

Wondering if this should be natively supported within the rasa training toolchain similar to how splitting up stories into multiple files is supported
What are the limitations of doing this?

Thanks for submitting this feature request 🚀@MetcalfeTom will get back to you about it soon!✨

Hi @moaazsidat, like the idea :+1:
How exactly does the training data importing work here?  Does your stories.md contain stories from all three of the domains in your example?
Seems like your solution deals implements two features here:

I like the domain-splitting for larger projects.  Seems like an intuitive way of making large projects digestible.

The other feature you're proposing is the unification of a multi-skill assistant.  This is already in the code, but is still experimental

Unfortunately we merged the ability to make custom Training Data Importers with rasa==1.1.8 and I think your implementation is already covered by this functionality.  Give it a test and let us know if you have any feedback 😄I wonder if you could instead be searching for these domain files and unifying them automatically by passing a domain directory, rather than a make command.


Remove support for SHA1 certificates from clickonce manifest signing utilities

Support for SHA1 certificates in clickonce verification is being deprecated.

@clairernovotny, for the cli branch this is resolved by https://github.com/dotnet/sign/pull/473.