The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,616 other followers

Archive for July 25th, 2018

New IP addresses for Bitbucket Cloud | Bitbucket Blog

Posted by jpluimers on 2018/07/25

If you are using bitbucket from behind a firewall, these might be important to you:

What are we doing? We’ll start a gradual rollout of changing our A records in DNS starting at 22:00 UTC on Sunday, July 29 2018 to point to new IP addresses. The rollout is expected to be completed for all our customers two weeks later, i.e by the 15th of August.

How will this affect you?

Most users will not have to do anything special for this migration. Your DNS servers should pick up the new IPs within a few minutes of the migration, and your systems should start using the new IPs right away. We’ll keep the old IPs running for a few weeks afterwards just in case, though.

Firewall considerations

If you control inbound or outbound access with a firewall, then you may need to update your configuration. Please whitelist these new IPs now; you should be able to remove the old IPs after the migration is complete. New destination IP addresses for bitbucket.org, bitbucket.com, api.bitbucket.org, bitbucket.io, bytebucket.org, altssh.bitbucket.org will be: IPv4: 18.205.93.0/25 and 13.52.5.0/25 IPv6: 2406:da00:ff00::0/96

SSH considerations

Our server’s SSH key is not changing, so most SSH clients will continue to work without interruption. However, a small number of users may see a warning similar to this when they push or pull over SSH: Warning: the RSA host key for ‘bitbucket.org’ differs from the key for the IP address ‘18.205.93.1’ The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, remove or comment out those lines, then retry your push or pull.

Additional resources Atlassian Public IP ranges JSON: https://ip-ranges.atlassian.com/ (will be updated with the new addresses as part of the new IPs rollout) https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html (will be updated with the new addresses as part of the new IPs rollout)

From:

–jeroen

Posted in BitBucket, Development, Source Code Management | Leave a Comment »

When learning a new VCS drives you crazy: Plastic SCM indicating it cannot undo changes, but not providing an alternative

Posted by jpluimers on 2018/07/25

User experiences like this drives me crazy, this time in Plastic SCM, when you try to get the most recent files on a branch/label/changeset after you made some changes:

So you go to the pending changes, see it involves additions and you see a big “Undo changes” button that fails to work:

  • 8 of 8 items selected
  • plastic insisting there are none

The undocumented “secret” is at the end of the messages “added and private items” cannot be undone. You have to manually “delete” them, which the message does not tell you.

Of course there is no “Delete” entry in the toolbar. There is no “Delete” entry in the local menu either.

You have to know that you

  • can do “Delete” by using the keyboard,
  • after first manually selecting all the entries in the treeview (so they get blue, which is different than having checkmarks).

How is that for a lack of user-experience?

Versions

This is on a version 6 client with a version 6 server.

Later I found out this bit on versioning, which I totally did not expect, as it does not match semantic versioning:

Version numbering

Starting in Plastic SCM 4.0 the version numbering schema has been modified:

  • major.minor.compatibility.buildnumber
  • Sample: 5.0.44.511 means:
    • 5 -> major release number
    • 0 -> minor release number
    • 44 -> compatibility -> all clients and servers with “44” in the compat number are compatible, even if the build number changes
    • 511 -> internal build number

So I have tried to to switch from

using the download at https://www.plasticscm.com/download/ to

with no difference.

–jeroen

Posted in Development, PlasticSCM, Source Code Management | Leave a Comment »

Some notes on the MT940 format used by various banks to export transactions

Posted by jpluimers on 2018/07/25

I needed the below links to get a feel on how much effort it would be to convert ABNAMRO transactions from MT940 into CSV or XLS extracting as many useful fields as possible.

Maybe it useful for other people as well.

I know there is CAMT.053 as well, but that puts every transaction into a separate XML file but still spreads the description over a multi-line structured field (like :86: below).

Two observations on field :86: (Information to Account Owner) are:

  1. Often it is less than 6 lines; I think it should be specified like “as most 6 lines of maximum 65 characters”
  2. At least ABN AMRO splits up the 65 characters into two columns:
    • part 1: 33 characters (almost always having a space in position 33)
    • part 2: 32 characters
  3. At least ABN AMRO uses this format for these lines:
    1. optional: description not having a semicolon (:) in it
    2. optional repetition of:
      1. mandatory keyword followed by a semicolon (:) and not having spaces in it
      2. mandatory description not having a semicolon (:) in it
      3. space

Searchable main source file of the library and easy browsing of the rest of the files: [WayBack] Mt940Parser.cs in sharpmt940lib located at /Raptorious.SharpMT940Lib | source code search engine

Background: [Archive.isJaco Adriaansen on Twitter: “@jpluimers Op dit moment parse ik 86 niet dieper. De inhoud van 86 is gewijzigd na dat ik het gemaakt heb. Zie: https://t.co/CrMc1OgaB0”

–jeroen

Read the rest of this entry »

Posted in Development, Software Development | Leave a Comment »

Getting the Firebird server version from a client using SQL

Posted by jpluimers on 2018/07/25

Since Firebird 2.1, you can get the first 3 numbers of the version with this SQL statement:

SELECT rdb$get_context('SYSTEM', 'ENGINE_VERSION')
from rdb$database;

You get it in this format:

RDB$GET_CONTEXT                                                                                                                                                                                                                                                
---------------
2.5.7                                                                                                                                                                                                                                                          

Which means you will not get the build number, which for most purposes is still quite OK.

–jeroen

via: [WayBackHow to detect the server version?

Posted in Database Development, Development, Firebird | Leave a Comment »

 
%d bloggers like this: