Extended Oracle Database Image not running in Docker on colleagues laptop

Hi
I created an image using this command .\buildDockerImage.sh -v <IP_ADDRESS> -s and the linuxx64_12201_database.zip for the installation files.
I then extended that image by setting the parameter MAX_STRING_SIZE to extended following these steps.  I then committed my changes to an image called wazbekker/oracledatabase and pushed it to docker hub with a tag of <IP_ADDRESS>-se2-extended.
I am running this image as a container successfully using the following command:
docker run
 --name oracle-<IP_ADDRESS>-se2-extended
-p 1521:1521
 -p 5500:5500
-e ORACLE_SID=ORCLCDB
-e ORACLE_PWD=oracle
-v oradata:/opt/oracle/oradata wazbekker/oracledatabase:<IP_ADDRESS>-se2-extended.

I am able to connect and create users/schemas and create tables etc without any issues.
The problem comes in when a work colleague pulls the image from Docker Hub and tries to run it with the exact same run command as above.
This is the output of trying to run the image:
Global Database Name:ORCLCDB

System Identifier(SID):ORCLCDB

2019-10-25T11:11:05.410085437Z

SQL*Plus: Release <IP_ADDRESS>.0 Production on Fri Oct 25 11:11:05 2019

2019-10-25T11:11:05.410119290Z

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

2019-10-25T11:11:05.410129239Z

Connected to an idle instance.

2019-10-25T11:11:06.428916968Z

SQL>    ALTER SYSTEM SET control_files='/opt/oracle/oradata/ORCLCDB/control01.ctl' scope=spfile

*

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 0

Session ID: 0 Serial number: 0

2019-10-25T11:11:06.428974643Z

2019-10-25T11:11:06.428978087Z

SQL>    ALTER PLUGGABLE DATABASE ORCLPDB1 SAVE STATE

*

ERROR at line 1:

ORA-01034: ORACLE not available

P2019-10-25T11:11:06.431320012Z

2019-10-25T11:11:06.431323423Z

SQL> BEGIN DBMS_XDB_CONFIG.SETGLOBALPORTENABLED (TRUE); END;

2019-10-25T11:11:06.432850490Z

*

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 0

Session ID: 0 Serial number: 0

2019-10-25T11:11:06.432886010Z

2019-10-25T11:11:06.432889290Z

SQL> Disconnected

mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/spfileORCLCDB.ora': No such file or directory

mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/orapwORCLCDB': No such file or directory

The Oracle base remains unchanged with value /opt/oracle

#####################################

########### E R R O R ###############

DATABASE SETUP WAS NOT SUCCESSFUL!

Please check output for further info!

########### E R R O R ###############

#####################################

The following output is now a tail of the alert.log:

ORCLPDB1(3):Autotune of undo retention is turned on.

2019-10-08T13:36:37.318521+00:00

ORCLPDB1(3):Endian type of dictionary set to little

ORCLPDB1(3):[3320] Successfully onlined Undo Tablespace 2.

ORCLPDB1(3):Undo initialization finished serial:0 start:9585533 end:9585611 diff:78 ms (0.1 seconds)

ORCLPDB1(3):Database Characterset for ORCLPDB1 is AL32UTF8

ORCLPDB1(3):Opatch validation is skipped for PDB ORCLPDB1 (con_id=0)

ORCLPDB1(3):Opening pdb with Resource Manager plan: DEFAULT_PLAN

Pluggable database ORCLPDB1 opened read write

ORCLPDB1(3):Completed: alter pluggable database orclpdb1 open

I then ran this command to connect to the container docker exec -it oracle-<IP_ADDRESS>-se2-extended /bin/bash and did some digging with regards to the errors in the output and found the following:
[oracle@ab98fad78405 ~]$ cd /opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs
[oracle@ab98fad78405 dbs]$ ls -al
total 24
drwxr-xr-x 1 oracle dba      4096 Oct 18 11:16 .
drwxr-xr-x 1 oracle dba      4096 Oct  8 13:33 ..
-rw-rw---- 1 oracle oinstall 1544 Oct  8 13:33 hc_ORCLCDB.dat
-rw-r--r-- 1 oracle dba      3079 May 15  2015 init.ora
-rw-r----- 1 oracle oinstall   24 Oct  8 13:04 lkORCLCDB
lrwxrwxrwx 1 oracle oinstall   49 Oct 18 11:16 orapwORCLCDB -> /opt/oracle/oradata/dbconfig/ORCLCDB/orapwORCLCDB
lrwxrwxrwx 1 oracle oinstall   54 Oct 18 11:16 spfileORCLCDB.ora -> /opt/oracle/oradata/dbconfig/ORCLCDB/spfileORCLCDB.ora

[oracle@ab98fad78405 ORCLCDB]$ cd /opt/oracle/oradata/dbconfig/ORCLCDB
[oracle@ab98fad78405 ORCLCDB]$ ls -al
total 24
drwxr-xr-x 2 oracle oinstall 4096 Oct 18 11:16 .
drwxr-xr-x 3 oracle oinstall 4096 Oct 18 10:45 ..
-rw-r--r-- 1 oracle oinstall  234 Oct 18 11:16 listener.ora
-rw-r--r-- 1 oracle oinstall  789 Oct 18 11:16 oratab
-rw-r--r-- 1 oracle oinstall   53 Oct 18 11:16 sqlnet.ora
-rw-r--r-- 1 oracle oinstall  197 Oct 18 11:16 tnsnames.ora

The symlinks are pointing to files that do not exist and I am not sure why?  These files exist in the container that I am running, using the exact same image.
I have a feeling this might be a problem with the volume but not sure what to do to fix it.
Hopefully someone can point me in the right direction to solve this issue?

Hi @wazbekker,
In short, docker commit doesn't persist anything that's sitting in a volume. So, all the data files and therefore your database is gone once you have committed the new image.
docker commit documentation:

Extended description
It can be useful to commit a container’s file changes or settings into a new image. This allows you to debug a container by running an interactive shell, or to export a working dataset to another server. Generally, it is better to use Dockerfiles to manage your images in a documented and maintainable way. Read more about valid image names and tags.
The commit operation will not include any data contained in volumes mounted inside the container.

See the last paragraph.
The only way around it is to keep the data files inside the image itself and make the database transient (i.e. your database is gone once you drop the container). For that, you will have to remove the VOLUME instruction as described here: https://github.com/oracle/docker-images/blob/master/OracleDatabase/SingleInstance/samples/prebuiltdb/README.md
Of course, there are other ways to get there, but it depends all on what you need.
You could, for example, embed a setup script that does the same and then there is no need for docker commit at all. Or you could just create the DB once and then just use that volume as a "gold image", etc.

Hi @gvenzl
Thank you for the reply and thank you for pointing me in the right direction.
I will take a look at the other options.

Hi @gvenzl
I followed the instructions in the prebuiltdb readme and I was able to create an image that can be reused by others at work.
Thank you for the help.


GH-492: JSON Improvements

Resolves https://github.com/spring-projects/spring-kafka/issues/492
For StringJsonMessageConverter and JsonSerializer

Convey type information in Headers using a Jackson type mapper
Setting addTypeInfo to false disables this feature

For StringJsonMessageConverter (inbound)

If configured with with the default type mapper, no changes - use the inferred type from the method signature
If configured with a type mapper where the TypePrecedence is not INFERRED, use the headers if available.

For JsonDeserializer

use type information from headers, falling back to a default if present

For JsonSerializer and JsonDeserializer

provide configuration (e.g. default type) via kafka properties

Makes sense (future).

Merged as https://github.com/spring-projects/spring-kafka/commit/7cd53119d3841a0e964c6f42186a3affcf9a4ea2.


Dedicated extension for jetty and xstream

Fixes #34
Fixes #33

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/23/


fix: just test-ci-all broken on Linux

Fix #3259

The whole problem is introduced by cargo-nextime being a bit weird in how it works. It does some dynamic libraries loading, etc. which has some weird interaction with nix (and macos security), AFAICT.


Set viewCountView visibility GONE when claim has no view count

i.e. on all places other than channel content.
PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change

PR Type
What kind of change does this PR introduce?

[x] Bugfix

Fixes
Left slightly broken in #248
What is the current behavior?
Due to 4dp marginEnd, publish time view is slightly indented.
What is the new behavior?
Make view GONE so publish time view is not indented.

Diff 584f12e...bf5cd55
New commit message:
Hide claims view count view when getViews() returns null

i.e. on all places other than channel content, or when error occurred.

- Also hide in channel content if there's zero views
- Show "No views" instead of "0 views" in FileViewFragment


Mutation testing should run with empty pytest config.

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

3.0.0
GitHub release

Your semantic-release bot :package::rocket:


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #271 (94e1ca1) into main (2974dfe) will increase coverage by 12.10%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main     #271       +/-   ##
===========================================
+ Coverage   83.33%   95.44%   +12.10%
===========================================
  Files           2        1        -1
  Lines         126      395      +269
  Branches       31       46       +15
===========================================
+ Hits          105      377      +272
+ Misses         21       18        -3

Impacted Files
Coverage Δ

src/index.ts
95.44% <100.00%> (+13.44%)
:arrow_up:

example/src/main.ts

Continue to review full report at Codecov.

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


Upgrade failed to Fabric 1.4.12 since hyperledger/fabric-javaenv:amd64-1.4.12 missing. Make a 1.4.12 release

While upgrading my 1.4.4 Fabric deployment, with Java chaincode, to 1.4.12 the installation of chaincode on the upgraded 1.4.12 peer failed due to the Docker image hyperledger/fabric-javaenv:amd64-1.4.12 not being found.
The specific error follows:
Error: could not assemble transaction,
      err proposal response was not successful, error code 500,
      msg error starting container:
          error starting container:
              Failed to generate platform-specific docker build:
                  Failed to pull hyperledger/fabric-javaenv:amd64-1.4.12:
                      API error (404): manifest for hyperledger/fabric-javaenv:amd64-1.4.12 not found:
                          manifest unknown: manifest unknown

I'd be happy to build this locally if I can and push my own hyperledger/fabric-javaenv:amd64-1.4.12 image to a repository.

@kencodible thanks for the report;
The quickest solution would be to pull down the last fabric-javaenv at 1.4 (https://hub.docker.com/layers/hyperledger/fabric-javaenv/1.4.8/images/sha256-93bebc77e0e5c998b0a3dad5cdb1ff82011f15154b191671a0c8b42b7db44d2e?context=explore) and retag that as the 1.4.12
As version 2 is now the LTS stream we aren't releasing new versions of the 1.4 chaincode. libraries.

Thought so. Thanks @mbwhite, I'll try that first.


[wip] add banner for calicon

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 28b238a2982845a5c4ab56b176b48f132f3e938e
https://deploy-preview-2958--calico.netlify.com

The little X that dismisses the banner doesn't seem to work

Easy fix. I removed the X.
Tried fixing it but it was more effort than it's worth.


Fix native stacktraces (chrome only). Make more robust to future chan…

…ges.

Jenkins, retest this.


HTTP 1.x compat

Update HTTPDownloads to be compatible with HTTP 1.x.

Hi @c42f, could you please review this PR?


issue

https://github.com/DataAccess2020/Capstone_project_Zaccaro/blob/e0ac646fd3cbc4d73f0da23296ffd08d6571659e/scripts/r_script_3.R#L23
@DeAngelisA how can I solve?

actually i have noticed that the combined for FDI gives me 5 tweets nd the single word "giovani" gives me 8 tweets.
 How is it possible?!


TensorFlow 2.16 / Keras 3 have undocumented breaking API changes

Issue type
Documentation Feature Request
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.16.1
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
With the (documented) switch to Keras 3, TensorFlow 2.16 has introduced undocumented API-breaking changes that derogate to SemVer and results in unexpected code maintenance costs for depending projects.
While I understand the interest of switching to Keras 3 (and acknowledge the possibility to keep using Keras 2 as backend, albeit non-trivial to impose on end-users of a third-party solution that uses TensorFlow as dependency), I would have expected some kind of effort on documenting parts of the API that changed due to the switch. This Keras issue and this guide are presented as listing breaking changes, but seem not to be covering everything that changed, especially when calling keras from TensorFlow rather than as a primary endpoint for setting up models (agnostic to the computation backend).
As I put effort in updating custom code that calls TensorFlow / Keras code, I notably noticed that:

tf.keras.Model.weights (and its variants) as well as tf.keras.optimizers.Optimizer.variables no longer return a list of tf.Variable instances, but instead return a list of tf.keras.Variable that themselves wrap tf.Variable instances.
Some losses were dropped / renamed, e.g. tf.keras.losses.deserialize("mse") no longer works, but was to the best of my knowledge never reported to be deprecated in previous versions.
tf.keras.optimizers.Optimizer.variables() has been removed in favor of tf.keras.optimizers.Optimizer.variables.

These changes can be adjusted for, but require a lot of if hasattr(tf.keras, "version") and tf.keras.version().startswith("3"): branching to keep supporting not-so-old versions while adding support for newer TF versions, and, most importantly, require some tedious experiments to find out what has changed and how. As such, I categorize his issue as "Documentation Feature Request" as I obviously do not expect changes to be rolled back, but believe that it would be a sensible gesture towards the community to publish a clearer and more exhaustive guide as to what has changed with the introduction of Keras 3, and how to accommodate third-party code that does not want to impose on end-users the choice of a single TF version.
Standalone code to reproduce the issue
As a single example of what I am talking about:
This works with TensorFlow 2.15:
import tensorflow as tf

optim = tf.keras.Adagrad()
grads = [tf.zeros((32, 1)), tf.zeros((1,))]
optim.build([tf.Variable(tf.zeros_like(g), name=f"{i}") for i, g in enumerate(grads)])
state = {v.name: v.value() for v in optim.variables()}
assert len(state) == 2

But it fails for numerous reasons in TensorFlow 2.16.1 (with Keras 3 backend):

state = {v.name: v.value() for v in optim.variables()} should be replaced with state = {v.path: v.value.value() for v in optim.variables}...
... and in fact this will not work because the names have not been propagated and all accumulator variables have the shame name/path, hence to put them in a dict I have to deterministically set names, e.g. based on indices, which drops some information.

Relevant log output
No response

It looks like you're encountering issues related to changes in the TensorFlow/Keras API, particularly with the switch to Keras 3 in TensorFlow 2.16. The changes you've highlighted, such as the return types of tf.keras.Model.weights and tf.keras.optimizers.Optimizer.variables, as well as the removal of tf.keras.optimizers.Optimizer.variables(), can indeed require adjustments to existing code.
Here are some suggestions to address these changes:

Handling return types: Since tf.keras.Variable wraps tf.Variable, you may need to modify your code to work with this change. For example, instead of directly accessing attributes of tf.Variable, you may need to use the corresponding methods or properties of tf.keras.Variable.

Renamed losses: For losses that have been dropped or renamed, you'll need to update your code to use the new names or alternatives. Check the TensorFlow documentation or release notes for information on the new names or replacements for the dropped losses.

Updated optimizer variables: With the removal of tf.keras.optimizers.Optimizer.variables(), you'll need to find an alternative way to access the optimizer's variables. One approach could be to maintain a separate list or dictionary of the optimizer's variables in your code.

Documentation and guidance: It's important to consult the TensorFlow documentation and release notes for guidance on how to update your code for these API changes. Additionally, forums and community discussions can be helpful in understanding the changes and finding solutions.

Conditional branching: As you mentioned, you may need to use conditional branching (if statements) to handle different versions of TensorFlow/Keras in your code. This can help you maintain compatibility with older versions while adding support for newer versions.

It's unfortunate that these changes have resulted in unexpected maintenance costs for your project. Providing feedback to the TensorFlow/Keras development team about the documentation gaps and difficulties in adapting to the changes could help improve the situation for the community.

Sorry, but this is as unhelpful an answer as it gets. Points 1, 2, 4 and 5 are merely repetitions of my issue description, and your conclusion literally prompts me to do what I just did by opening this issue.
As for point 3, the all point of my opening this issue is to point out that there is a lack of documentation regarding these changes, which means everyone has to spend time figuring out what is broken or not, and how to adjust to API changes. I managed to do it in my specific case with a few hours' effort, but the parts I use in my software only cover a small part of the entire TensorFlow/Keras API, hence I expect others will not only encounter the same issues as me, but probably more undocumented issues.
Hence my call for a broader migration guide, that would help developers adjust their code to the recent changes with limited effort.

(it's an answer generated by an LLM, just spam)

The LLM generated spam comment has been removed silently.
But for TF 2.16, see https://github.com/tensorflow/tensorflow/issues/69586 for a history of how things got so back

@mihaimaruseac Thank you for your reply. The discussion you linked is mostly about a distinct (albeit relevant) issue, but the details about the RC process having been rushed is (sadly) interesting.
I am struck by your comment stating that

Everyone that cared about full support of TF is no longer in the team.

Does it mean that we should expect TensorFlow to be progressively dropped, and/or to become a backend project for Keras? If so, this is sad to learn. TensorFlow has come a long way since the version 2 beta, and although there have been caveats and some changes along that path, as far as I can tell it has mostly been stable, notably after version 2.5.
Is there any documentation, or do you have any shareable insight, as to the planned future of TensorFlow and/or its articulation with other libraries in the ecosystem (notably Keras, Jax and Flax)?

I cannot say much, but Jax is the ecosystem of choice now. With Keras 3 you can easily switch between Jax and PyTorch as backend.

OK, thank you for the insight.


Cm offline api additional fields

Hi Álvaro,
Please review the additional fields I've added for the CM Offline API.
Regards,
Brian

Question related to how the customVariable field was constructed for this uploader:
how is the structure required in BigQuery for this to work? as a struct?
Best,
Artur

Yes. I clarified and added sample data to the wiki
https://github.com/google/megalista/wiki/Campaign-Manager-Offline-Conversions
:
Sample code pasted below for convenience:
Copyright 2021 Google LLC

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
SELECT *
FROM UNNEST(
ARRAY<STRUCT<
uuid STRING,
matchId STRING,
value INT64,
quantity INT64,
customVariables ARRAY<STRUCT<type STRING, value STRING, kind STRING>>>>[
(generate_uuid(), 'abc', 10, 2, [
('U1', '123', 'dfareporting#customFloodlightVariable'),
('U2', '456', 'dfareporting#customFloodlightVariable')
]),
(generate_uuid(), 'def', 20, 4, [
('U1', '987', 'dfareporting#customFloodlightVariable'),
('U2', '654', 'dfareporting#customFloodlightVariable')
])
])
Regards,
Brian
On Mon, Aug 23, 2021 at 11:31 AM Artur Mangabeira Soares <
@.***> wrote:

Question related to how the customVariable field was constructed for this
uploader:
how is the structure required in BigQuery for this to work? as a struct?
Best,
Artur
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/megalista/pull/41#issuecomment-903878113, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARO5L3PCFVVFVHX44SKMKXLT6JSVHANCNFSM5CH6Q55Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

--
Brian Levitan @.***> | Customer Solutions Engineer | gPS |
212-565-7911


don't put ui/bindata.go in ui/bindata.go

No need to put Go code in bindata files.
For @fabxc ?

An other, aguably nicer, option would be to put the .go files in a different path. Up to you.

This looks fine to me. We can merge this, but it will be fixed with the new ui (See ui-rewrite).
If you don't mind I would close here and wait for the new ui to be merged soon.
@alicebob @fabxc What do you think?

Oh, there will be a new GUI, nice. I'll close this one then. Thanks!


Upgrade external-provisioner to v5.0.2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Added new ConfigMap for openshift xray template

Added ConfigMap for Xray xray_config.yaml file with 'sslInsecure: false' setting.
Included above xray_config.yaml in all 5 xray microservice components.
Updated the initContainer to deploy this config file in xray installation path.

Added stdOutEnabled:true setting to xray_config.yaml
Please confirm. Thanks.


Canonical key to identify locations

I'm looking at locations.json and am trying to figure out what to use as a primary key to canonically identify locations in my consumer library.
It seems like the name field serves as a primary key in practice, but I'm worried it might change because its's a human-readable, localized name.
I was hoping I could use featureId as a key – it's particularly useful because I can easily obtain names in many language for each location. But 355 out of 4414 locations don't have a featureId:

Locations with missing featureId
countyId | stateId      | countyId     | name
iso1:ES  | iso2:ES-AN   |              | Andalusia, Spain
iso1:ES  | iso2:ES-AR   |              | Aragon, Spain
iso1:ES  | iso2:ES-AS   |              | Asturias, Spain
iso1:ES  | iso2:ES-IB   |              | Balearic Islands, Spain
iso1:ES  | iso2:ES-CN   |              | Canary Islands, Spain
iso1:ES  | iso2:ES-CB   |              | Cantabria, Spain
iso1:ES  | iso2:ES-CM   |              | Castile-La Mancha, Spain
iso1:ES  | iso2:ES-CL   |              | Castile and León, Spain
iso1:ES  | iso2:ES-CT   |              | Catalonia, Spain
iso1:ES  | iso2:ES-CE   |              | Ceuta, Spain
iso1:ES  | iso2:ES-VC   |              | Valencian Community, Spain
iso1:ES  | iso2:ES-EX   |              | Extremadura, Spain
iso1:ES  | iso2:ES-GA   |              | Galicia, Spain
iso1:ES  | iso2:ES-MD   |              | Community of Madrid, Spain
iso1:ES  | iso2:ES-ML   |              | Melilla, Spain
iso1:ES  | iso2:ES-MC   |              | Region of Murcia, Spain
iso1:ES  | iso2:ES-NC   |              | Navarre, Spain
iso1:ES  | iso2:ES-PV   |              | Basque Country, Spain
iso1:ES  | iso2:ES-RI   |              | Rioja, Spain
iso1:PA  | iso2:PA-8    |              | Panamá, Panama
iso1:PA  | iso2:PA-1    |              | Bocas del Toro, Panama
iso1:PA  | iso2:PA-4    |              | Chiriquí, Panama
iso1:PA  | iso2:PA-2    |              | Coclé, Panama
iso1:PA  | iso2:PA-3    |              | Colón, Panama
iso1:PA  | iso2:PA-5    |              | Darién, Panama
iso1:PA  | iso2:PA-EM   |              | Comarca Emberá-Wounaan, Panama
iso1:PA  | iso2:PA-KY   |              | Comarca Guna Yala, Panama
iso1:PA  | iso2:PA-6    |              | Herrera, Panama
iso1:PA  | iso2:PA-7    |              | Los Santos, Panama
iso1:PA  | iso2:PA-NB   |              | Comarca Ngäbe Buglé, Panama
iso1:PA  | iso2:PA-10   |              | Panamá Oeste, Panama
iso1:PA  | iso2:PA-9    |              | Veraguas, Panama
iso1:GP  |              |              | Guadeloupe
iso1:MQ  |              |              | Martinique
iso1:GF  |              |              | French Guiana
iso1:RE  |              |              | Réunion
iso1:YT  |              |              | Mayotte
iso1:FX  | iso2:FR-GES  | iso2:FR-10   | Aube, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-11   | Aude, Occitania, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-12   | Aveyron, Occitania, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-13   | Bouches-du-Rhône, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-NOR  | iso2:FR-14   | Calvados, Normandy, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-15   | Cantal, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-16   | Charente, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-17   | Charente-Maritime, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-18   | Cher, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-19   | Corrèze, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-21   | Côte-d'Or, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-BRE  | iso2:FR-22   | Côtes-d'Armor, Brittany, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-23   | Creuse, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-24   | Dordogne, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-25   | Doubs, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-26   | Drôme, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-NOR  | iso2:FR-27   | Eure, Normandy, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-28   | Eure-et-Loir, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-BRE  | iso2:FR-29   | Finistère, Brittany, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-30   | Gard, Occitania, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-31   | Haute-Garonne, Occitania, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-32   | Gers, Occitania, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-33   | Gironde, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-34   | Hérault, Occitania, Metropolitan France
iso1:FX  | iso2:FR-BRE  | iso2:FR-35   | Ille-et-Vilaine, Brittany, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-36   | Indre, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-37   | Indre-et-Loire, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-38   | Isère, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-39   | Jura, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-40   | Landes, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-41   | Loir-et-Cher, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-42   | Loire, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-43   | Haute-Loire, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-PDL  | iso2:FR-44   | Loire-Atlantique, Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-CVL  | iso2:FR-45   | Loiret, Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-46   | Lot, Occitania, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-47   | Lot-et-Garonne, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-48   | Lozère, Occitania, Metropolitan France
iso1:FX  | iso2:FR-PDL  | iso2:FR-49   | Maine-et-Loire, Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-NOR  | iso2:FR-50   | Manche, Normandy, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-51   | Marne, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-52   | Haute-Marne, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-PDL  | iso2:FR-53   | Mayenne, Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-54   | Meurthe-et-Moselle, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-55   | Meuse, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-BRE  | iso2:FR-56   | Morbihan, Brittany, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-57   | Moselle, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-58   | Nièvre, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-HDF  | iso2:FR-59   | Nord, Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-HDF  | iso2:FR-60   | Oise, Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-NOR  | iso2:FR-61   | Orne, Normandy, Metropolitan France
iso1:FX  | iso2:FR-HDF  | iso2:FR-62   | Pas-de-Calais, Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-63   | Puy-de-Dôme, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-64   | Pyrénées-Atlantiques, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-65   | Hautespyrenees, Occitania, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-66   | Pyrénées-Orientales, Occitania, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-67   | Bas-Rhin, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-68   | Haut-Rhin, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-69   | Rhône, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-70   | Haute-Saône, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-71   | Saône-et-Loire, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-PDL  | iso2:FR-72   | Sarthe, Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-73   | Savoy, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-74   | Upper Savoy, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-75   | Paris, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-NOR  | iso2:FR-76   | Seine-Maritime, Normandy, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-77   | Seine-et-Marne, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-78   | Yvelines, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-79   | Deux-Sèvres, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-HDF  | iso2:FR-80   | Somme, Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-81   | Tarn, Occitania, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-82   | Tarn-et-Garonne, Occitania, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-83   | Var, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-84   | Vaucluse, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-PDL  | iso2:FR-85   | Vendée, Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-86   | Vienne, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-NAQ  | iso2:FR-87   | Haute-Vienne, New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-88   | Vosges, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-89   | Yonne, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-BFC  | iso2:FR-90   | Territoire-de-Belfort, Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-91   | Essonne, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-92   | Hauts-de-Seine, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-93   | Seine-Saint-Denis, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-94   | Val-de-Marne, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  | iso2:FR-95   | Val-d'Oise, Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-01   | Ain, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-HDF  | iso2:FR-02   | Aisne, Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-03   | Allier, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-04   | Alpes-de-Haute-Provence, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-05   | Hautes-Alpes, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-PAC  | iso2:FR-06   | Maritime Alps, Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-ARA  | iso2:FR-07   | Ardèche, Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-GES  | iso2:FR-08   | Ardennes, Grand Est, Metropolitan France
iso1:FX  | iso2:FR-OCC  | iso2:FR-09   | Ariège, Occitania, Metropolitan France
iso1:FX  | iso2:FR-COR  | iso2:FR-2A   | South Corsica, Corsica, Metropolitan France
iso1:FX  | iso2:FR-COR  | iso2:FR-2B   | Haute-Corse, Corsica, Metropolitan France
iso1:FX  | iso2:FR-GES  |              | Grand Est, Metropolitan France
iso1:FX  | iso2:FR-OCC  |              | Occitania, Metropolitan France
iso1:FX  | iso2:FR-PAC  |              | Provence-Alpes-Côte d'Azur, Metropolitan France
iso1:FX  | iso2:FR-NOR  |              | Normandy, Metropolitan France
iso1:FX  | iso2:FR-ARA  |              | Auvergne-Rhône-Alpes, Metropolitan France
iso1:FX  | iso2:FR-NAQ  |              | New Aquitaine, Metropolitan France
iso1:FX  | iso2:FR-CVL  |              | Centre-Loire Valley, Metropolitan France
iso1:FX  | iso2:FR-BFC  |              | Bourgogne-Franche-Comté, Metropolitan France
iso1:FX  | iso2:FR-BRE  |              | Brittany, Metropolitan France
iso1:FX  | iso2:FR-PDL  |              | Pays de la Loire, Metropolitan France
iso1:FX  | iso2:FR-HDF  |              | Hauts-de-France, Metropolitan France
iso1:FX  | iso2:FR-IDF  |              | Ile-de-France, Metropolitan France
iso1:FX  | iso2:FR-COR  |              | Corsica, Metropolitan France
iso1:FX  |              |              | Metropolitan France
iso1:US  | iso2:US-MA   | fips:25007+fips:25019 | Dukes County, Nantucket County, Massachusetts, United States
iso1:GB  | iso2:GB-SCT  | iso2:GB-SCB  | Scottish Borders, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-DGY  | Dumfries and Galloway, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-FIF  | Fife, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-CLK+iso2:GB-FAL+iso2:GB-STG | Clackmannanshire, Falkirk, Stirling, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-ABD+iso2:GB-ABE+iso2:GB-MRY | Aberdeenshire, Aberdeen City, Moray, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-GLG+iso2:GB-EDU+iso2:GB-ERW+iso2:GB-IVC+iso2:GB-RFW+iso2:GB-WDU | Glasgow City, East Dunbartonshire, East Renfrewshire, Inverclyde, Renfrewshire, West Dunbartonshire, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-HLD+iso2:GB-AGB | Highland, Argyll and Bute, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-NLK+iso2:GB-SLK | North Lanarkshire, South Lanarkshire, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-EDH+iso2:GB-ELN+iso2:GB-MLN+iso2:GB-WLN | City of Edinburgh, East Lothian, Midlothian, West Lothian, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-ZET  | Shetland Islands, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-ANS+iso2:GB-DND+iso2:GB-PKN | Angus, Dundee City, Perth and Kinross, Scotland, United Kingdom
iso1:US  | iso2:US-AK   | fips:02020   | Anchorage Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02261+fips:02150+fips:02122 | Gulf Coast Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02068+fips:02290+fips:02240+fips:02090 | Interior Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02170   | Mat-Su Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02188+fips:02180+fips:02185 | Northern Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02282+fips:02230+fips:02105+fips:02275+fips:02100+fips:02195+fips:02198+fips:02220+fips:02130+fips:02110 | Southeast Economic Region, AK, USA
iso1:US  | iso2:US-AK   | fips:02060+fips:02164+fips:02013+fips:02070+fips:02016+fips:02158+fips:02050 | Southwest Economic Region, AK, USA
iso1:RU  | iso2:RU-MOW  |              | Moscow, Russia
iso1:RU  | iso2:RU-MOS  |              | Moscow Oblast, Russia
iso1:RU  | iso2:RU-SPE  |              | Saint Petersburg, Russia
iso1:RU  | iso2:RU-SAM  |              | Samara Oblast, Russia
iso1:RU  | iso2:RU-SA   |              | Sakha Republic, Russia
iso1:RU  | iso2:RU-SVE  |              | Sverdlovsk Oblast, Russia
iso1:RU  | iso2:RU-KGD  |              | Kaliningrad, Russia
iso1:RU  | iso2:RU-KIR  |              | Kirov Oblast, Russia
iso1:RU  | iso2:RU-NVS  |              | Novosibirsk Oblast, Russia
iso1:RU  | iso2:RU-KYA  |              | Krasnoyarsk Krai, Russia
iso1:RU  | iso2:RU-TAM  |              | Tambov Oblast, Russia
iso1:RU  | iso2:RU-LIP  |              | Lipetsk Oblast, Russia
iso1:RU  | iso2:RU-TVE  |              | Tver Oblast, Russia
iso1:RU  | iso2:RU-KHA  |              | Khabarovsk Krai, Russia
iso1:RU  | iso2:RU-TYU  |              | Tyumen Oblast, Russia
iso1:RU  | iso2:RU-TUL  |              | Tula Oblast, Russia
iso1:RU  | iso2:RU-PER  |              | Perm Krai, Russia
iso1:RU  | iso2:RU-NIZ  |              | Nizhny Novgorod Oblast, Russia
iso1:RU  | iso2:RU-KDA  |              | Krasnodar Krai, Russia
iso1:RU  | iso2:RU-VOR  |              | Voronezh Oblast, Russia
iso1:RU  | iso2:RU-KEM  |              | Kemerovo Oblast, Russia
iso1:RU  | iso2:RU-KK   |              | Republic of Khakassia, Russia
iso1:RU  | iso2:RU-MUR  |              | Murmansk Oblast, Russia
iso1:RU  | iso2:RU-KO   |              | Komi Republic, Russia
iso1:RU  | iso2:RU-KLU  |              | Kaluga Oblast, Russia
iso1:RU  | iso2:RU-IVA  |              | Ivanovo Oblast, Russia
iso1:RU  | iso2:RU-ZAB  |              | Zabaykalsky Krai, Russia
iso1:RU  | iso2:RU-TOM  |              | Tomsk Oblast, Russia
iso1:RU  | iso2:RU-ARK  |              | Arkhangelsk Oblast, Russia
iso1:RU  | iso2:RU-RYA  |              | Ryazan Oblast, Russia
iso1:RU  | iso2:RU-ULY  |              | Ulyanovsk Oblast, Russia
iso1:RU  | iso2:RU-YAR  |              | Yaroslavl Oblast, Russia
iso1:RU  | iso2:RU-PNZ  |              | Penza Oblast, Russia
iso1:RU  | iso2:RU-BEL  |              | Belgorod Oblast, Russia
iso1:RU  | iso2:RU-KHM  |              | Khanty-Mansiysk Autonomous Okrug – Ugra, Russia
iso1:RU  | iso2:RU-LEN  |              | Leningrad oblast, Russia
iso1:RU  | iso2:RU-ORE  |              | Orenburg Oblast, Russia
iso1:RU  | iso2:RU-SAR  |              | Saratov Oblast, Russia
iso1:RU  | iso2:RU-TA   |              | Tatarstan, Russia
iso1:RU  | iso2:RU-KGN  |              | Kurgan Oblast, Russia
iso1:RU  | iso2:RU-KB   |              | Kabardino-Balkaria, Russia
iso1:RU  | iso2:RU-CHE  |              | Chelyabinsk Oblast, Russia
iso1:RU  | iso2:RU-STA  |              | Stavropol Krai, Russia
iso1:RU  | iso2:RU-BRY  |              | Bryansk Oblast, Russia
iso1:RU  | iso2:RU-UD   |              | Udmurtia, Russia
iso1:RU  | iso2:RU-NGR  |              | Novgorod Oblast, Russia
iso1:RU  | iso2:RU-CR   |              | Republic of Crimea, Russia
iso1:RU  | iso2:RU-BA   |              | Bashkortostan, Russia
iso1:RU  | iso2:RU-CE   |              | Chechen Republic, Russia
iso1:RU  | iso2:RU-PRI  |              | Primorsky Krai, Russia
iso1:RU  | iso2:RU-VGG  |              | Volgograd Oblast, Russia
iso1:RU  | iso2:RU-ORL  |              | Oryol Oblast, Russia
iso1:RU  | iso2:RU-PSK  |              | Pskov Oblast, Russia
iso1:RU  | iso2:RU-ROS  |              | Rostov Oblast, Russia
iso1:RU  | iso2:RU-BU   |              | Buryatia, Russia
iso1:RU  | iso2:RU-MO   |              | Republic of Mordovia, Russia
iso1:RU  | iso2:RU-DA   |              | Republic of Dagestan, Russia
iso1:RU  | iso2:RU-SAK  |              | Sakhalin Oblast, Russia
iso1:RU  | iso2:RU-KOS  |              | Kostroma Oblast, Russia
iso1:RU  | iso2:RU-SMO  |              | Smolensk Oblast, Russia
iso1:RU  | iso2:RU-AD   |              | Republic of Adygea, Russia
iso1:GB  | iso2:GB-SCT  | iso2:GB-NAY+iso2:GB-EAY+iso2:GB-SAY | North Ayrshire, East Ayrshire, South Ayrshire, Scotland, United Kingdom
iso1:RU  | iso2:RU-OMS  |              | Omsk Oblast, Russia
iso1:RU  | iso2:RU-IRK  |              | Irkutsk Oblast, Russia
iso1:RU  | iso2:RU-AMU  |              | Amur Oblast, Russia
iso1:US  | iso2:US-RI   | fips:44001   | Barrington, Bristol County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44001   | Bristol, Bristol County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Burrillville, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Central Falls, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Charlestown, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44003   | Coventry, Kent County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Cranston, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Cumberland, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44003   | East Greenwich, Kent County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | East Providence, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Exeter, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Foster, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Glocester, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Hopkinton, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Jamestown, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Johnston, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Lincoln, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Little Compton, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Middletown, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Narragansett, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | New Shoreham, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Newport, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | North Kingstown, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | North Providence, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | North Smithfield, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Pawtucket, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Portsmouth, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Providence, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Richmond, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Scituate, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Smithfield, Providence County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | South Kingstown, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44005   | Tiverton, Newport County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44001   | Warren, Bristol County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44003   | Warwick, Kent County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44003   | West Greenwich, Kent County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44003   | West Warwick, Kent County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44009   | Westerly, Washington County, Rhode Island, United States
iso1:US  | iso2:US-RI   | fips:44007   | Woonsocket, Providence County, Rhode Island, United States
iso1:BR  | iso2:BR-AC   |              | Acre, Brazil
iso1:BR  | iso2:BR-AL   |              | Alagoas, Brazil
iso1:BR  | iso2:BR-AP   |              | Amapá, Brazil
iso1:BR  | iso2:BR-AM   |              | Amazonas, Brazil
iso1:BR  | iso2:BR-BA   |              | Bahia, Brazil
iso1:BR  | iso2:BR-CE   |              | Ceará, Brazil
iso1:BR  | iso2:BR-DF   |              | Federal District, Brazil
iso1:BR  | iso2:BR-ES   |              | Espírito Santo, Brazil
iso1:BR  | iso2:BR-GO   |              | Goiás, Brazil
iso1:BR  | iso2:BR-MA   |              | Maranhão, Brazil
iso1:BR  | iso2:BR-MT   |              | Mato Grosso, Brazil
iso1:BR  | iso2:BR-MS   |              | Mato Grosso do Sul, Brazil
iso1:BR  | iso2:BR-MG   |              | Minas Gerais, Brazil
iso1:BR  | iso2:BR-PR   |              | Paraná, Brazil
iso1:BR  | iso2:BR-PB   |              | Paraíba, Brazil
iso1:BR  | iso2:BR-PA   |              | Pará, Brazil
iso1:BR  | iso2:BR-PE   |              | Pernambuco, Brazil
iso1:BR  | iso2:BR-PI   |              | Piauí, Brazil
iso1:BR  | iso2:BR-RN   |              | Rio Grande do Norte, Brazil
iso1:BR  | iso2:BR-RS   |              | Rio Grande do Sul, Brazil
iso1:BR  | iso2:BR-RJ   |              | Rio de Janeiro, Brazil
iso1:BR  | iso2:BR-RO   |              | Rondônia, Brazil
iso1:BR  | iso2:BR-RR   |              | Roraima, Brazil
iso1:BR  | iso2:BR-SC   |              | Santa Catarina, Brazil
iso1:BR  | iso2:BR-SE   |              | Sergipe, Brazil
iso1:BR  | iso2:BR-SP   |              | São Paulo, Brazil
iso1:BR  | iso2:BR-TO   |              | Tocantins, Brazil
iso1:RU  | iso2:RU-ALT  |              | Altai Krai, Russia
iso1:RU  | iso2:RU-VLA  |              | Vladimir Oblast, Russia
iso1:RU  | iso2:RU-VLG  |              | Vologda Oblast, Russia
iso1:RU  | iso2:RU-KL   |              | Republic of Kalmykia, Russia
iso1:RU  | iso2:RU-ME   |              | Mari El, Russia
iso1:RU  | iso2:RU-CU   |              | Chuvashia, Russia
iso1:IN  | iso2:IN-AP   |              | Andhra Pradesh, India
iso1:IN  | iso2:IN-AN   |              | Andaman and Nicobar Islands, India
iso1:IN  | iso2:IN-BR   |              | Bihar, India
iso1:IN  | iso2:IN-CH   |              | Chandigarh, India
iso1:IN  | iso2:IN-CT   |              | Chhattisgarh, India
iso1:IN  | iso2:IN-DL   |              | Delhi, India
iso1:IN  | iso2:IN-GA   |              | Goa, India
iso1:IN  | iso2:IN-GJ   |              | Gujarat, India
iso1:IN  | iso2:IN-HR   |              | Haryana, India
iso1:IN  | iso2:IN-HP   |              | Himachal Pradesh, India
iso1:IN  | iso2:IN-JK   |              | Jammu and Kashmir, India
iso1:IN  | iso2:IN-KA   |              | Karnataka, India
iso1:IN  | iso2:IN-KL   |              | Kerala, India
iso1:IN  | iso2:IN-LA   |              | Ladakh, India
iso1:IN  | iso2:IN-MP   |              | Madhya Pradesh, India
iso1:IN  | iso2:IN-MH   |              | Maharashtra, India
iso1:IN  | iso2:IN-MN   |              | Manipur, India
iso1:IN  | iso2:IN-MZ   |              | Mizoram, India
iso1:IN  | iso2:IN-OR   |              | Odisha, India
iso1:IN  | iso2:IN-PY   |              | Puducherry, India
iso1:IN  | iso2:IN-PB   |              | Punjab, India
iso1:IN  | iso2:IN-RJ   |              | Rajasthan, India
iso1:IN  | iso2:IN-TN   |              | Tamil Nadu, India
iso1:IN  | iso2:IN-TG   |              | Telangana, India
iso1:IN  | iso2:IN-UT   |              | Uttarakhand, India
iso1:IN  | iso2:IN-UP   |              | Uttar Pradesh, India
iso1:IN  | iso2:IN-WB   |              | West Bengal, India
iso1:RU  | iso2:RU-AST  |              | Astrakhan Oblast, Russia
iso1:RU  | iso2:RU-MAG  |              | Magadan Oblast, Russia
iso1:RU  | iso2:RU-SEV  |              | Sevastopol, Russia
iso1:GB  | iso2:GB-SCT  | iso2:GB-ORK  | Orkney Islands, Scotland, United Kingdom
iso1:GB  | iso2:GB-SCT  | iso2:GB-ELS  | Western Isles, Scotland, United Kingdom
iso1:IN  | iso2:IN-AS   |              | Assam, India
iso1:IN  | iso2:IN-JH   |              | Jharkhand, India
iso1:RU  | iso2:RU-KRS  |              | Kursk Oblast, Russia
iso1:RU  | iso2:RU-SE   |              | Republic of North Ossetia-Alania, Russia
iso1:IN  | iso2:IN-AR   |              | Arunachal Pradesh, India
iso1:RU  | iso2:RU-YAN  |              | Yamalo-Nenets Autonomous Okrug, Russia
iso1:RU  | iso2:RU-YEV  |              | Jewish Autonomous Oblast, Russia
iso1:RU  | iso2:RU-IN   |              | Ingushetia, Russia
iso1:RU  | iso2:RU-KAM  |              | Kamchatka Krai, Russia
iso1:IN  | iso2:IN-TR   |              | Tripura, India
iso1:RU  | iso2:RU-KR   |              | Republic of Karelia, Russia
iso1:RU  | iso2:RU-KC   |              | Karachay-Cherkessia, Russia
iso1:RU  | iso2:RU-TY   |              | Tuva Republic, Russia
iso1:IN  | iso2:IN-NL   |              | Nagaland, India
iso1:IN  | iso2:IN-ML   |              | Meghalaya, India
iso1:RU  | iso2:RU-NEN  |              | Nenets Autonomous Okrug, Russia
iso1:RU  | iso2:RU-CHU  |              | Chukotka Autonomous Okrug, Russia
iso1:US  | iso2:US-MI   | fips:26163   | Detroit City, Wayne County, Michigan, United States
iso1:RU  | iso2:RU-AL   |              | Altai Republic, Russia
iso1:IN  | iso2:IN-DN   |              | Dadra and Nagar Haveli, India

I noticed that there is a bunch of logic in src/events/processor/find-features/index.js to generate featureId fields, so I'm assuming this could possibly be fixed to cover 100% of locations.
Finally, I tried using [countryId, stateId, countyId] triplets, but they don't uniquely identify locations either:

> require('./locations.json').length
4414
> new Set(require('./locations.json').map((l) => `${l.countryId},${l.stateId},${l.countyId}`)).size
4372

Any thoughts?

Hi @joliss - hm, the triplets should actually be correct, b/c together they should identify the location.  Moreover, in Li, we're still using those triplets, so they'll likely be the best ID.  Can you let me know what triplets have dups, and perhaps give me some more detail about them?

 For example, Detroit City has a city field, but no cityId to key on:
    {
      "state": "Michigan",
      "country": "United States",
      "sources": [
        {
          "name": "Michigan Department of Health & Human Services"
        }
      ],
      "url": "https://www.michigan.gov/coronavirus/0,9753,7-406-98163-520743--,00.html",
      "aggregate": "county",
      "city": "Detroit City",
      "county": "Wayne County",
      "rating": 0.5098039215686274,
      "countryId": "iso1:US",
      "stateId": "iso2:US-MI",
      "countyId": "fips:26163",
      "name": "Detroit City, Wayne County, Michigan, United States",
      "level": "city"
    }

Thanks very much, this is great.
If I recall correctly, the Alaska ones are tricky ... they changed things around with their reporting, using some strange region codes.
For the others which have city, do you know if the city values roll up to the state values, or are contained in them?  If so, perhaps it would be best to ignore level: city data points.  We don't have many of those, and don't have good geo data for them, iirc.

For US counties, there should be exactly one county per fips code, it should identify uniquely. Here is the US Census reference document for fips codes <> names: https://www2.census.gov/programs-surveys/popest/geographies/2018/all-geocodes-v2018.xlsx
For cities, I believe they need to be 4-tuples, including city name or city slug of some sort.
So for example "North Kingstown, Washington County, Rhode Island, United States" would be
iso1:US,iso2:US-RI,fips:44009,north_kingstown, but that is just my idea. They need 4-tuples for sure.

I just looked at the Excel table you linked; it seems that the unique FIPS code is the 2nd + 3rd column combined, correct?
I was hoping there might be some way to get unique numeric city identifiers, perhaps from the "Place Code (FIPS)" or "Consolidtated City Code (FIPS)"[sic] columns, but at the very least they'd need to be used in conjunction with other columns to be unique. For example here are all lines containing "03220":
Summary Level,State Code (FIPS),County Code (FIPS),County Subdivision Code (FIPS),Place Code (FIPS),Consolidtated City Code (FIPS),Area Name (including legal/statistical area description)
162,01,000,00000,03220,00000,Autaugaville town
162,02,000,00000,03220,00000,Anderson city
061,17,097,03220,00000,00000,Avon township
061,26,157,03220,00000,00000,Arbela township
061,33,001,03220,00000,00000,Barnstead town
061,38,053,03220,00000,00000,Arnegard city
162,38,000,00000,03220,00000,Arnegard city
061,46,085,03220,00000,00000,Bailey township

Or maybe you've looked into this already and it's just possible?

No, I haven't looked into cities and I don't know anything about them. The 5 digit fips code is a standard, look at Wikipedia or anywhere else, they are used in many places. Even the NYT and JHU datasources use the 5 digit one. For cities, I have no idea but Wikipedia lists something for cities.

Thanks @hyperknot for jumping in.
@joliss - unless you specifically need city-level data, see if you can roll them up, or use only the state-level data.  We don't have reliable/useful city-level data, and most scrapers/sources don't report on that.  Can you give that a shot and LMK how it works out?


Added pie button to the snakecalc and updated the screenshot image

Pie Button added to the snakecalc.
Updated the screenshot image.

Merging for now, in the future please keep irrelevant changes to different PRs or at least different commits (i.e. changes to snake calc and a documentation screenshot)

Ok will keep that in mind next time👍

Hi, sorry for not saying this earlier, but after #70 we're not going to be doing any more additions to snakecalc.
Also, this was clearing all text and replacing it with 3.14, I think what you mean to do was use self.append_text() to append the pi value instead of replacing everything with it


Building errors with VS 2019 under Windows

Bug description
Error while building the FAST project with:

Windows 10
GIT verified commit ebff1b46c802c0839b43d5f83aa296c19a8a9c14.
Visual Studio 2019
Latest Intel Fortran compiler from here.
Latest Intel C++ compiler from here.

To Reproduce
Steps to reproduce the behavior:

Cloned GIT verified commit ebff1b46c802c0839b43d5f83aa296c19a8a9c14.
Re-targeted projects as for:

Let Debug as solution configuration with platform Win32.
Build FAST project from given (re-targeted) solution.
Unexpected errors found, with build logs attached below in the additional content section:

Expected behavior
Error free building.
Screenshots, if applicable

OpenFAST Version
Cloned from GIT verified commit ebff1b46c802c0839b43d5f83aa296c19a8a9c14.
System Information (please complete the following information):

OS: Windows 10.
Compiler: Latest Intel Fortran (2<IP_ADDRESS>) and C++ (2<IP_ADDRESS>) compilers. See links above.
Compiler settings: No modification to provided VS solution.

Additional context

From FASTlib:

Build started: Project: FASTlib, Configuration: Debug|Win32

Deleting intermediate files and output files for project 'FASTlib', configuration 'Debug\|Win32'.
Performing Pre-Build Event...
call ..\CreateGitVersion.bat
The system cannot find the path specified.
The system cannot find the path specified.
FASTlib : error PRJ0019: A tool returned an error code
FASTlib - 1 error(s), 0 warning(s)

From FAST:

Build started: Project: FAST, Configuration: Debug|Win32

Deleting intermediate files and output files for project 'FAST', configuration 'Debug|Win32'.
Performing Pre-Build Event...
..\CreateGitVersion.bat
The system cannot find the path specified.
The system cannot find the path specified.
FAST : error PRJ0019: A tool returned an error code
FAST - 1 error(s), 0 warning(s)

I cannot extract more information from the build logs htm files. Apparently it stop with error while:
Performing Pre-Build Event...

Concerning the gitVersionInfo.h file: It does appear under the header files of the FASTlib project, though marked as ignored:

Its content is as follows:
#define GIT_VERSION_INFO 'v3.0.0-1-gebff1b46-dirty'

P.S. Thanks for pointing out the compiler switch while re-targeting ;-)

Thanks for checking that. I see in your screenshots that your Fortran projects have the text "(IFORT)" on them. I have not seen this before and am wondering if this is just due to the version of Fortran compiler you installed or if there was some issue with the VS2019 integrations when you installed the it. (I usually see the parenthesis on C/C++ projects where I have multiple compilers installed and am not using the default one, but I've not seen this on the Fortran projects, even with multiple versions installed.)
Could you check to see what Fortran compilers Visual Studio thinks you have installed? And that you do in fact have a 32-bit Fortran compiler? In Visual Studio, navigate to Tools > Options > Intel Compiler and Libraries, then Visual Fortran or something similar (you have a newer version of Fortran than I have installed, so it may be named differently), and check to see what version of the compiler you have selected.

If there are multiple Fortran compilers, maybe try using a different one. Or you can try clicking the "Reset..." button there to make sure the paths to files the compiler needs are set properly.
This may help, too: https://www.intel.com/content/www/us/en/developer/articles/training/intel-fortran-compiler-in-ms-visual-studio.html

I do have installed two Fortran compilers:

Intel® Fortran Compiler Classic (IFORT).
Intel® Fortran Compiler Beta (IFX).

Up to now, no matter which compiler I tried, even switching Win32 to x64 for IFORT will help avoiding the very same error.
Any further help iv very much appreciated.

@edaniele-tpi, can you try to build a single Fortran source file? For example, in the FASTlib project, right-click on the NWTC_Base.f90 file in the Solution Explorer window (it's under the NWTC_Library Source File directory), and select Compile.

What does that do?

@bjonkman if I try what you suggested with Intel® Fortran Compiler Classic 2021.5.0 the following errors popped out:
------ Build started: Project: FASTlib, Configuration: Debug|Win32 ------

Compiling with Intel® Fortran Compiler Classic 2021.5.0 [IA-32]...
NWTC_Base.f90
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(25): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [PRECISION]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(38): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(39): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(40): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(42): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(43): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(47): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(48): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(49): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(50): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(51): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(53): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90(56): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
compilation aborted for C:\Users\e.daniele\GitHub\NREL\openfast\modules\nwtc-library\src\NWTC_Base.f90 (code 1)

Build log written to  "file://C:\Users\e.daniele\GitHub\NREL\openfast\vs-build\FASTlib\Debug\BuildLog.htm"
FASTlib - 14 error(s), 0 warning(s)

---------------------- Done ----------------------

Okay, great. That tells us that the problem with the path isn't actually coming from a issue with the compiler install. If you build SingPrec.f90 first, then the errors from the NWTC_Base.f90 build should go away.
Can you open CreateGitVersion.bat and add this line before the EXIT statement there (on line 8):
ECHO *********** End of CreateGitVersion.bat ***********

Then, when you build the project, do you see that text in the Visual Studio Output window?

I can confirm that, compiling in sequence SingPrec.f90 and NWTC_Base.f90 leads to no error.
After changing the CreateGitVersion.bat file as suggested, its echo message is actually printed, and the following appears in VS output window:
Build started...
1>------ Build started: Project: FAST_Registry, Configuration: Release Win32 ------
1>data.c
1>gen_c_types.c
1>gen_module_files.c
1>misc.c
1>my_strtok.c
1>registry.c
1>reg_parse.c
1>sym.c
1>symtab_gen.c
1>type.c
1>Generating code
1>Previous IPDB not found, fall back to full compilation.
1>All 75 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
1>Finished generating code
1>FAST_Registry.vcxproj -> C:\Users\e.daniele\GitHub\NREL\openfast\build\bin\Registry.exe
2>------ Build started: Project: MAP_dll, Configuration: Debug Win32 ------
2>Performing Custom Build Tools
2>======================================================================
2>
2>----- FAST Registry --------------
2>----------------------------------------------------------
2>input file: ..\..\modules\map\src\MAP_Registry.txt
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt
2>opening ..\..\modules\map\src/MAP_Fortran_Registry.txt in usefrom mode
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
2>generating ..\..\modules\map\src/MAP_Types.f90
2>CUSTOMBUILD : Registry warning : derived data type LinInitInp of type lin_initinputtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitInp of type lin_initinputtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type Ver of type progdesc is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitOut of type lin_initoutputtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type Ver of type progdesc is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitOut of type lin_initoutputtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type LinParams of type lin_paramtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinParams of type lin_paramtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type PtFairDisplacement of type meshtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type PtFairDisplacement of type meshtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type ptFairleadLoad of type meshtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type ptFairleadLoad of type meshtype is not passed through F-C interface
2>The system cannot find the path specified.
2>
2>----- FAST Registry --------------
2>----------------------------------------------------------
2>input file: ..\..\modules\map\src\MAP_Fortran_Registry.txt
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt
2>generating ..\..\modules\map\src/MAP_Fortran_Types.f90
2>The system cannot find the path specified.
2>
2>Registry for MAP completed.
2>
2>======================================================================
2>bstraux.c
2>bstrlib.c
2>dpmpar.c
2>enorm.c
2>enorm_u.c
2>lmder.c
2>lmpar.c
2>qrfac.c
2>qrsolv.c
2>freedata.c
2>jacobian.c
2>lineroutines.c
2>mapapi.c
2>maperror.c
2>mapinit.c
2>numeric.c
2>outputstream.c
2>residual.c
2>simclist.c
2>Generating Code...
2>lmroutines.cc
2>   Creating library ..\..\build\bin\MAP_Win32.lib and object ..\..\build\bin\MAP_Win32.exp
2>MAP_dll.vcxproj -> C:\Users\e.daniele\GitHub\NREL\openfast\build\bin\MAP_Win32.dll
2>Done building project "MAP_dll.vcxproj".
3>------ Build started: Project: FASTlib (IFORT), Configuration: Debug Win32 ------
3>Performing Pre-Build Event...
3>The system cannot find the path specified.
3>The system cannot find the path specified.
3>*********** End of CreateGitVersion.bat ***********
3>FASTlib : error PRJ0019: A tool returned an error code
3>Build log written to  "file://C:\Users\e.daniele\GitHub\NREL\openfast\vs-build\FASTlib\Debug\BuildLog.htm"
3>FASTlib - 1 error(s), 0 warning(s)
4>------ Build started: Project: FAST (IFORT), Configuration: Debug Win32 ------
4>Performing Pre-Build Event...
4>The system cannot find the path specified.
4>The system cannot find the path specified.
4>*********** End of CreateGitVersion.bat ***********
4>FAST : error PRJ0019: A tool returned an error code
4>Build log written to  "file://C:\Users\e.daniele\GitHub\NREL\openfast\vs-build\FAST\Debug\BuildLog.htm"
4>FAST - 1 error(s), 0 warning(s)
========== Build: 2 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

For some reason, it looks like that batch file isn't working properly on your system. I'd guess that it doesn't like the IncludeFile, but you'd have to do some more debugging to determine if that is correct and how to fix it. Since you do have a gitVersionInfo.h file, you could just comment out the lines in CreateGitVersion.bat so that it will get through that step to allow you to compile. Just remember that the version number wouldn't necessarily be correct on the executable you build.

By commenting out lines within CreateGitVersion.bat in this way:
@ECHO off
::SET IncludeFile=..\gitVersionInfo.h

::<NUL SET /p IncludeTxt=#define GIT_VERSION_INFO '> %IncludeFile%
::FOR /f %%a IN ('git describe --abbrev^=8 --always --tags --dirty') DO <NUL SET /p IncludeTxt=%%a>> %IncludeFile%
::git describe --abbrev^=8 --always --tags --dirty > NUL
::IF %ERRORLEVEL%==0 ( ECHO '>> %IncludeFile% ) else ( ECHO Unversioned from $Format:%H$ '>> %IncludeFile% )
ECHO *********** End of CreateGitVersion.bat ***********
EXIT /B 0

I encounter a slightly different error while building, namely a single instead of a double statement The system cannot find the path specified. for both FASTlib and FAST projects, as reported in the VS output window:
Build started...
1>------ Build started: Project: FAST_Registry, Configuration: Release Win32 ------
1>data.c
1>gen_c_types.c
1>gen_module_files.c
1>misc.c
1>my_strtok.c
1>registry.c
1>reg_parse.c
1>sym.c
1>symtab_gen.c
1>type.c
1>Generating code
1>Previous IPDB not found, fall back to full compilation.
1>All 75 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
1>Finished generating code
1>FAST_Registry.vcxproj -> C:\Users\e.daniele\GitHub\NREL\openfast\build\bin\Registry.exe
2>------ Build started: Project: MAP_dll, Configuration: Debug Win32 ------
2>Performing Custom Build Tools
2>======================================================================
2>
2>----- FAST Registry --------------
2>----------------------------------------------------------
2>input file: ..\..\modules\map\src\MAP_Registry.txt
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt
2>opening ..\..\modules\map\src/MAP_Fortran_Registry.txt in usefrom mode
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
2>generating ..\..\modules\map\src/MAP_Types.f90
2>CUSTOMBUILD : Registry warning : derived data type LinInitInp of type lin_initinputtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitInp of type lin_initinputtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type Ver of type progdesc is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitOut of type lin_initoutputtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type Ver of type progdesc is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type LinInitOut of type lin_initoutputtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type LinParams of type lin_paramtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type LinParams of type lin_paramtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type PtFairDisplacement of type meshtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type PtFairDisplacement of type meshtype is not passed through F-C interface
2>CUSTOMBUILD : Registry warning : derived data type ptFairleadLoad of type meshtype is not passed through C interface
2>CUSTOMBUILD : Registry warning : derived data type ptFairleadLoad of type meshtype is not passed through F-C interface
2>The system cannot find the path specified.
2>
2>----- FAST Registry --------------
2>----------------------------------------------------------
2>input file: ..\..\modules\map\src\MAP_Fortran_Registry.txt
2>opening ..\..\modules\nwtc-library\src/Registry_NWTC_Library.txt
2>generating ..\..\modules\map\src/MAP_Fortran_Types.f90
2>The system cannot find the path specified.
2>
2>Registry for MAP completed.
2>
2>======================================================================
2>bstraux.c
2>bstrlib.c
2>dpmpar.c
2>enorm.c
2>enorm_u.c
2>lmder.c
2>lmpar.c
2>qrfac.c
2>qrsolv.c
2>freedata.c
2>jacobian.c
2>lineroutines.c
2>mapapi.c
2>maperror.c
2>mapinit.c
2>numeric.c
2>outputstream.c
2>residual.c
2>simclist.c
2>Generating Code...
2>lmroutines.cc
2>   Creating library ..\..\build\bin\MAP_Win32.lib and object ..\..\build\bin\MAP_Win32.exp
2>MAP_dll.vcxproj -> C:\Users\e.daniele\GitHub\NREL\openfast\build\bin\MAP_Win32.dll
2>Done building project "MAP_dll.vcxproj".
3>------ Build started: Project: FASTlib (IFORT), Configuration: Debug Win32 ------
3>Performing Pre-Build Event...
3>The system cannot find the path specified.
3>*********** End of CreateGitVersion.bat ***********
3>FASTlib : error PRJ0019: A tool returned an error code
3>Build log written to  "file://C:\Users\e.daniele\GitHub\NREL\openfast\vs-build\FASTlib\Debug\BuildLog.htm"
3>FASTlib - 1 error(s), 0 warning(s)
4>------ Build started: Project: FAST (IFORT), Configuration: Debug Win32 ------
4>Performing Pre-Build Event...
4>The system cannot find the path specified.
4>*********** End of CreateGitVersion.bat ***********
4>FAST : error PRJ0019: A tool returned an error code
4>Build log written to  "file://C:\Users\e.daniele\GitHub\NREL\openfast\vs-build\FAST\Debug\BuildLog.htm"
4>FAST - 1 error(s), 0 warning(s)
========== Build: 2 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

I switched to compilation with cmake on Unix or WSL under Windows, so I don't see the need to keep this issue open.


fix(ui): Change code color to black

@johno has forced the background in the code view to be white. Thus, I have adjusted the code color to black so that it doesn't inherit it from the current theme.

Fixes #73

🙏


libphpcpp.so: undefined symbol: zend_next_free_module in Unknown on line 0

php -v
PHP 5.5.23 (cli) (built: Mar 20 2015 07:50:26)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
php-config
--version           [5.5.23]
--vernum            [50523]
PHP-CPP v1.2.2 doesn't have any problem.
I try to mark out the "start()" from module.h with
//_entry->module_number = zend_next_free_module();
(PHP-CPP v1.3.2) The problem is sovled and everything goes fine.
ps. I have tested v1.3.1 & 1.3.. Same as v1.3.2

This is a really odd problem. The zend_next_free_module() function should just be available. Nevertheless, I will try to create a workaround.


[DLP] Implemented sample for Reidentify Free TextWith Fpe Using Surrogate

Fixes #issue

It's a good idea to open an issue first for discussion.

[X] I have followed Sample Format Guide
[X] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] API's need to be enabled to test (tell us)
[X] Environment Variables need to be set (ask us to set them)
Need to set the environment variable "DLP_DEID_UNWRAPPED_KEY" for this sample
[X] Tests pass:   mvn clean verify required
[X] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[X] Please merge this PR for me once it is approved.

@micheldavid As we have introduced new environment variable "DLP_DEID_UNWRAPPED_KEY", the test checks will fail. Please help us setting the mentioned environment variable.


Lazy loading changes output path of assets

When enabling lazy loading the output path of assets inside engines changes as everything is put inside an engines-dist folder. Is there a way to have the output path be the same or do I need to create a helper/util for that manually? How are others solving this?
I.e. with lazy loading:

without lazy loading:

There's no way to make these things equal @sebastianhelbig because they're different on output level. You can see that on the Ember Engines Guides. What you can do is create a helper with a simple if/else to cover these two and easy scenarios - lazy and eager engines ; )


Deadlock in WritingThread in queueFrame

I found a case when deadlock happens in this library when length of frame queue is limited.
WritingThread could trigger user's callbacks. For example onConnected callback here: https://github.com/TakahikoKawasaki/nv-websocket-client/blob/master/src/main/java/com/neovisionaries/ws/client/WebSocket.java#L3292
If onConnected callback is triggered from WritingThread and in this callback user sends a lot of data to WebSocket then frame queue could become full. In this case we could call wait() in WritingThread (https://github.com/TakahikoKawasaki/nv-websocket-client/blob/master/src/main/java/com/neovisionaries/ws/client/WritingThread.java#L192). If WritingThread is waiting until the queue gets space then it's a deadlock, because only WritingThread could send data to socket.

@avasenin Thank you for your pointing it out. I didn't imagine that programmers would try to send a lot of data in the context of onConnected(). I feel like adding a warning in the document instead of changing the source code of nv-websocket-client.

Typical scenario: offline queue. When you are disconnected then you store all messages in queue and send them when become online. In this case user will get deadlock if the number of frames == length of frame queue. In my case length of frame queue is limited by 1024. Is my scenario too specific for WebSocket library usage?


Update Minitest to 5.6.x

Update minitest to 5.6.x

I’ll merge this but then I plan to cleanup the way we specify development dependencies.
spec.add_development_dependency "minitest", "~> 5.6", ">= 5.6.0"

This line is redundant. ~> 5.6 implies >= 5.6 (as well as < 6).
Also, IMHO, development dependencies should be specified in the Gemfile not in hurley.gemspec. Bundler allows much more precise grouping of gems (e.g. development vs. test), as well as platform-specific dependencies (e.g. jruby-openssl for JRuby). Thus, I’d propose making the only development dependency:
spec.add_development_dependency "bundler", "~> 1.0"

Then we can manage everything else through the Gemfile. I’ve done this with most of the other gems I manage (including faraday) and have been pleased with the results. The only downside is that you can’t install development dependencies with the command:
gem install hurley --development

In my experience, nobody actually does gem development this way. Most people clone the repo and then run:
bundle install

I’m going to make this change, unless there are any strong objections.


darwin.adv_cmds: fix build

Also disable pgrep that depends on pkill

Motivation for this change
Closes: #82640
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

So installation was broken when implemented 4f522648cbb80a3f733ac33898191106c5eb1ec2, but I suppose it would only fail the build after #72347. Other places seem to have been fixed (e.g. ed6148726b9e9b2f6edf38e889dc39c28648dda4):
# grep -r 'install -D $f' .
./pkgs/os-specific/darwin/apple-source-releases/shell_cmds/default.nix:        install -D $f $out/usr/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/network_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/adv_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/text_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/basic_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/system_cmds/default.nix:          install -D $f $out/share/man/man$n/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/developer_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/diskdev_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
./pkgs/os-specific/darwin/apple-source-releases/file_cmds/default.nix:        install -D $f $out/bin/$(basename $f)
#

# grep -r 'install -D $file' .
#


CI: Some Go 1.13.10 updates that were missed

This file was still on Go 1.13.8, which caused it to be missed when updating Go 1.13.9 to 1.13.10

Codecov Report

Merging #4175 into master will increase coverage by 3.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4175      +/-   ##
==========================================
+ Coverage   42.40%   45.70%   +3.30%
==========================================
  Files         133      119      -14
  Lines       15225    12212    -3013
==========================================
- Hits         6456     5582     -874
+ Misses       7836     5698    -2138
+ Partials      933      932       -1

Flag
Coverage Δ

#linux
45.70% <ø> (ø)

#windows
?

Impacted Files
Coverage Δ

remotes/docker/fetcher.go
54.11% <0.00%> (-5.41%)
:arrow_down:

remotes/docker/auth.go
63.82% <0.00%> (-3.97%)
:arrow_down:

remotes/docker/status.go
21.42% <0.00%> (-3.58%)
:arrow_down:

remotes/docker/errdesc.go
28.12% <0.00%> (-2.65%)
:arrow_down:

remotes/docker/errcode.go
47.61% <0.00%> (-1.60%)
:arrow_down:

filters/scanner.go
81.35% <0.00%> (-0.85%)
:arrow_down:

platforms/platforms.go
79.41% <0.00%> (-0.81%)
:arrow_down:

platforms/cpuinfo.go
3.57% <0.00%> (-0.72%)
:arrow_down:

errdefs/grpc.go
77.46% <0.00%> (-0.04%)
:arrow_down:

log/context.go
100.00% <0.00%> (ø)

... and 76 more

Continue to review full report at Codecov.

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


Merge get_optics to develop

Implement support for get_optics() getter

Coverage increased (+0.07%) to 95.369% when pulling dc47e07e172c1e7ca46cfb188a2a395ae323ed2f on get_optics into 5fa0a79fa98f828474168c8a765baa9d4583c1f7 on develop.


#221: strip xml/html from data to POST to Aeon

Resolves #221, if you're ok with this being a object method rather than a helper function.... probably to be refactored as a cross-application helper in the future, to eliminate duplicate code with https://github.com/RockefellerArchiveCenter/pisces/issues/507.  But, that will be short lived if we do allow HTML rendering per https://github.com/RockefellerArchiveCenter/pisces/issues/508, and/or if Atlas fixes the issue with properly escaping HTML in Aeon.

closing this in favor of #225


Wrong version produced when changing version.json

Hey hey! First off, love the project, it's solving almost all my versioning issues! I hit a thing that might or might not be a bug (or maybe I'm missing something, dunno)...
I have about 10 projects in a repo, and I'm following the instructions at https://github.com/AArnott/Nerdbank.GitVersioning/blob/master/doc/cloudbuild.md#set-them-from-just-one-project to set the cloud build variables from only one project. I have a version.json in the root like this:
version.json at root:
{
  "$schema": "https://raw.githubusercontent.com/AArnott/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json",
  "version":  "1.0",
  "publicReleaseRefSpec": [
    "^refs/heads/master$",
    "^refs/heads/v\\d+(?:.\\d+)?$"
  ],
  "cloudBuild": {
    "setVersionVariables": false,
    "buildNumber": {
      "enabled": false
    }
  },
  "inherit": false
}

version.json in all project subdirectories except MasterProject:
{
    "$schema":  "https://raw.githubusercontent.com/AArnott/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json",
    "inherit":  true
}

version.json in MasterProject:
{
  "$schema": "https://raw.githubusercontent.com/AArnott/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json",
  "cloudBuild": {
    "setVersionVariables": true,
    "buildNumber": {
      "enabled": true
    }
  },
  "inherit": true
}

It all works great except that I moved the projects down one subdirectory. The root version.json file has not been changed. After this move, all theprojects have their versions bumped correctly in a local build (from 1.0.9 to 1.0.10) EXCEPT for the MasterProject, which misteriously got stamped with 1.0.0. If I take out the the cloudBuild section in the MasterProject, it gets versioned correctly. Looks like it thinks that the version.json file in the MasterProject has changes that affect the version?

Ah, cool, I'll try that, thanks!

So your root version.json is and always has been in the repo root, right?
Can you share the repo or whip up a repro repo that you can share?

@AArnott Yeah, the version.json in the root was never touched. The repo is https://github.com/spoiledcat/UnityTools, but I've moved some other things around and suddenly it's versioning things correctly, I can't reproduce it anymore. I have no idea what was happening or why it stopped happening :-/

Well, that's good---ish.  ;-p
One thing that frequently trips up people is that changes to version.json must be committed for everything to apply properly. Maybe when you were seeing the unexpected behavior, you only had local changes that hadn't been committed yet.

Maybe, could have been that. If it happens again, I'll try to isolate it. Thanks!


support Chinese?

does this model support Chinese language?

Hi,
Thanks for interest in our work! The support for Chinese language comes with native multilingual ability from language backbones (LLaMA, Vicuna, Yi). However, we did not fine-tune additional Chinese datasets for more advanced Chinese ability. Based on our personal experiences, the model understands and can respond in Chinese. Feel free to try it and share your experience with us. We are also hoping to support more advanced multilingual in future releases if possible.


fix: e2e twap flakiness

Background
e2e twap is flaky. needs fixing
https://github.com/osmosis-labs/osmosis/actions/runs/6041573925/attempts/3?pr=6256
Acceptance Criteria

fix
run 5 times to make sure fixed

Previously when we had a similar issue, this was the solution: https://github.com/osmosis-labs/osmosis/pull/4359
Based on the review of twap history, there weren't any module changes that could break the above fix: https://github.com/osmosis-labs/osmosis/commits/main/x/twap
There were some instances that looked similar. A change was attempted but proved to be irrelevant: https://github.com/osmosis-labs/osmosis/pull/6269
Next, proceeded to review CI history.
Taker fee https://github.com/osmosis-labs/osmosis/pull/6034 was the first PR where I observed the failure.
I have 2 guesses:

Taker fee in e2e is sometimes set before the e2e test (since tests are parallel). As a result, it non-deterministically breaks the twap tests. Attempted fix: https://github.com/osmosis-labs/osmosis/pull/6271
Protorev in-parallel backruns the CL geo twap pool (haven't validated this, low-to-medium confidence on this

To be extra sure, attempting to remove the e2e taker fee changes: https://github.com/osmosis-labs/osmosis/pull/6272

fixed


Implement muting on Bancho

To match feature parity with osu, you should be able to place multiple mutes on a player with the reason and duration.

Put on backburn while looking into mute packets.


Dense hash map hangs(assert in debug) when find() on non-existent

Hi there. Was testing dense_hash_map and found it would hang on a certain test configuration
Load factor = 1
Completely fill map with items
delete an item
find() for that item
The find() should return failure but find_position never exits. It seems that find_position (in densehashtable) only exits when it finds the item or finds an empty item. If all items are either deleted or existing then it will never exit.
Now I'm not sure if the intention is to ensure there are always empty items by having more buckets than items (Never actually being loadfactor=1), or if it's an issue with find_position that needs to take into account hash tables full of only deleted and valid items. My fix took the latter approach
Below is one way to reproduce the error.
	GOOGLE_NAMESPACE::dense_hash_map<int, int> google_dense;
	google_dense.set_empty_key(0);
	google_dense.set_deleted_key(1);
	google_dense.max_load_factor(1);

	size_t bc = google_dense.bucket_count();
	for (int t = 0; t < bc; ++t)
	{
		google_dense.insert({ t + 2, t });
	}
	google_dense.erase(2);
	google_dense.find(2);

My fix was to insert after ++num_probes the following. This may or may not suit the aims of the container in general
	  // We've searched everything, not found it, but we did find a deleted bucket.
	  if (num_probes == bucket_count() && insert_pos != ILLEGAL_BUCKET)
	  {
		  return std::pair<size_type, size_type>(ILLEGAL_BUCKET, insert_pos);
	  }

You're compiling with "-DNDEBUG"?
I get an assertion (on the C++11 version) without it.
Assertion failed: num_probes < bucket_count() && "Hashtable is full: an error in key_equal<> or hash<>", file google/sparsehash/internal/densehashtable.h, line 873

Well with debug off, the thing loops forever. Debug on it asserts. However neither should be happening AFAIC. If I have deleted items from a hashmap, then want to look for an item I should get a return indicating "failed to find" not loop forever.

Issue is setting the load factor to 1 and allowing the dense_hash_map to be completely filled. Easy fix would be to add the following in sh_hashtable_settings::set_resizing_parameters:
if (grow > 0.95f)
grow = 0.95f;


Add integration tests for renaming namespaces with the MongoDB DocManager

This change adds integration tests for MongoDB to MongoDB command replication on renamed namespaces and fixes the replication of such commands because of the typo in '$cmd' added here https://github.com/mongodb-labs/mongo-connector/pull/601/files#diff-9e5fc676a1f3b77e19871877266b4cf0R240.
Also, removes the namespace_set attribute from the MongoDB DocManager which is never initialized. namespace_set was added in version 1.2 https://github.com/mongodb-labs/mongo-connector/commit/bdfe9aad2db8b4adb6616b22fcc71a4e24feb26b but the initialization seems to have been unintentionally removed in version 2.0 https://github.com/mongodb-labs/mongo-connector/commit/6b8a6649e9008397ef2eb4fe1183541b90e2de5b#diff-ca51c2fabfa279cb1d2902ff6c2d8152L371

Merged.


Cant use it with init()

Hi,
I am trying to use your pod but not able to lazy load it..
I am not able to do
var textField = B68UIFloatLabelTextField()
but I had to do
var textField = B68UIFloatLabelTextField(coder: NSCoder.empty())
and further had to write an extension of
extension NSCoder {
class func empty() -> NSCoder {
let data = NSMutableData()
let archiver = NSKeyedArchiver(forWritingWithMutableData: data)
archiver.finishEncoding()
return NSKeyedUnarchiver(forReadingWithData: data)
}
}
Can you please update it to use the default init method

This is on purpose. Please the use init(frame:). This is consistent with the default text label.

Can you share an example.
I am tryind to do
var field:B68UIFloatLabelTextField = B68UIFloatLabelTextField()
but I never see the option of frame init method at all!


GEODE-10250: Drop lock request if member departed

If a member requests a distributed lock, then departs the distributed
system, the grantor shouldn't grant that request. If so, it'll get
into a state where the lock is held by a member that has departed.

For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Do we need unit tests? or already exists...

We definitely need unit tests, but this fix doesn't work yet. The distributed tests are timing out because of this change. I want it to work before I write any unit tests for it.

There might be some new or old corner case that prevents the memberDeparted event from clearing the lock.
Originally, the dlock service would grant the lock and then check if the member is still present in the local view -- if not release it. If the member was still in the local view, then it would own the lock. Afterwards, a memberDeparted event or a releaseLock message would release that lock.

Its definitely a corner case.
Here is the sequence:

The lock requesting server requests a lock
Before the grantor server processes that request, the lock requesting server leaves the distributed system
The DistributionManager in the grantor server removes the member and logs the Member gracefully left message
The DLockGrantor in the grantor server begins to process the lock request
The DLockGrantor's membersDepartedTime map is updated with an entry for that member
The grantAndRespondToRequest method calls isCurrentMember which returns true because the member is still in the view
The DLockGrantor grants the lock
The view is updated to remove the departed member

At the end of this sequence, the lock is held by a member who has departed.
Here is some logging that shows the sequence from the grantor server's point of view.
Original view:
[vm1] [warn 2022/04/28 12:57:27.594 PDT server-1 <unicast receiver,host-47928> tid=0x27] XXX MembershipView.<init> view=View[host(locator-0:46041:locator)<ec><v0>:41001|2] members: [host(locator-0:46041:locator)<ec><v0>:41001, host(server-1:46042)<v1>:41002{lead}, host(server-2:46043)<v2>:41003]

Lock requesting server departs:
[vm1] [debug 2022/04/28 12:57:29.201 PDT server-1 <Pooled High Priority Message Processor 3> tid=0x4f] DistributionManager: removing member <host(server-2:46043)<v2>:41003>; crashed false; reason = shutdown message received

[vm1] [info 2022/04/28 12:57:29.201 PDT server-1 <Pooled High Priority Message Processor 3> tid=0x4f] Member at host(server-2:46043)<v2>:41003 gracefully left the distributed cache: shutdown message received

The membersDepartedTime map is updated:
[vm1] [info 2022/04/28 12:57:29.221 PDT server-1 <Pooled Waiting Message Processor 1> tid=0x2f] XXX DLockGrantor.recordMemberDepartedTime recorded membersDepartedTime owner=host(server-2:46043)<v2>:41003; currentTime=1651175849221; membersDepartedTimeSize=1; membersDepartedTime={host(server-2:46043)<v2>:41003=1651175849221}

The grantAndRespondToRequest method checks is current member which returns true:
[vm1] [warn 2022/04/28 12:57:29.259 PDT server-1 <Pooled Waiting Message Processor 1> tid=0x2f] XXX DLockGrantToken.grantAndRespondToRequest currentMember=host(server-2:46043)<v2>:41003; isCurrentMember=true

The DLockGrantor grants the lock:
[vm1] [debug 2022/04/28 12:57:29.260 PDT server-1 <Pooled Waiting Message Processor 2> tid=0x4f] Sending (DLockRequestProcessor.DLockResponseMessage responding GRANT; serviceName=__PRLS(version 3); objectName=testRequestDistributedLockWhileClosingCache_lockName; responseCode=0; keyIfFailed=null; leaseExpireTime=9223372036854775807; processorId=21; lockId=21) to 1 peers ([host(server-2:46043)<v2>:41003]) via tcp/ip

The view is updated:
[vm1] [warn 2022/04/28 12:57:29.532 PDT server-1 <unicast receiver,host-47928> tid=0x27] XXX MembershipView.<init> view=View[host(locator-0:46041:locator)<ec><v0>:41001|3] members: [host(locator-0:46041:locator)<ec><v0>:41001, host(server-1:46042)<v1>:41002{lead}]  shutdown: [host(server-2:46043)<v2>:41003]

Closing this out due to age.


Create Unreal Engine 4: How to Fix Tiling on a Landscape Material Usi…

…ng Megascans

Hey, what's this PR about?
For now, I'm going to close it.


appflowy: 0.0.2 -> 0.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AppFlowy-IO/appflowy/releases.
meta.description for appflowy is: "An open-source alternative to Notion"
meta.homepage for appflowy is: "https://www.appflowy.io/"
meta.changelog for appflowy is: "https://github.com/AppFlowy-IO/appflowy/releases/tag/0.0.3"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3/bin/appflowy had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.0.3 with grep in /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3
found 0.0.3 in filename of file in /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
appflowy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A appflowy https://github.com/r-ryantm/nixpkgs/archive/8e666465186f058f0be8a01e496f421c157033b3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3
ls -la /nix/store/0g02ppdxh91wzx58i2pq0v4aj28rp4p0-appflowy-0.0.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

appflowy

Maintainer pings
cc @DarkOnion0 for testing.

@NixOS/ofborg eval