Example VQ-VAE

Another example on generation.
This example demonstrates VQ-VAE. I think it's important because of the recipes it comes with. Besides, being the powerhouse for OpenAI's DALL-E, it also uses codebook sampling which is widely used in generation tasks.
I hope the community will benefit from this. Here's the initial Colab Notebook.

@fchollet added the final files. Ready for you to take over.


[BUG] Reconnect on opensearch connection refused

Data-prepper can't run until opensearch is ready:
data-prepper             | 2022-02-19T13:26:13,300 [main] INFO  com.amazon.dataprepper.plugins.sink.opensearch.OpenSearchSink - Initializing OpenSearch sink
data-prepper             | 2022-02-19T13:26:13,785 [main] INFO  com.amazon.dataprepper.plugins.sink.opensearch.ConnectionConfiguration - Using the trust all strategy
data-prepper             | 2022-02-19T13:26:14,274 [main] ERROR com.amazon.dataprepper.plugin.PluginCreator - Encountered exception while instantiating the plugin OpenSearchSink
data-prepper             | java.lang.reflect.InvocationTargetException: null
data-prepper             | Caused by: java.lang.RuntimeException: Connection refused
data-prepper             | Caused by: java.net.ConnectException: Connection refused
data-prepper             | Caused by: java.net.ConnectException: Connection refused
data-prepper             | 2022-02-19T13:26:14,304 [main] ERROR com.amazon.dataprepper.parser.PipelineParser - Construction of pipeline components failed, skipping building of pipeline [service-map-pipeline] and its connected pipelines
data-prepper             | com.amazon.dataprepper.model.plugin.PluginInvocationException: Exception throw from the plugin'OpenSearchSink'.
data-prepper             | Caused by: java.lang.reflect.InvocationTargetException
data-prepper             | Caused by: java.lang.RuntimeException: Connection refused
data-prepper             | Caused by: java.net.ConnectException: Connection refused
data-prepper             | Caused by: java.net.ConnectException: Connection refused
data-prepper             | 2022-02-19T13:26:14,314 [main] ERROR       com.amazon.dataprepper.DataPrepper - No valid pipeline is available for execution, exiting

Why not wait as Dashboards?

@enp , Thank you for raising this issue. We are already tracking this in #936, so I'll close this issue as a duplicate. Your feedback also helps us with prioritization.


Quickstart instructions broken - "Invalid choice 'service-management'"

[x] Which version of Forseti Security you're using (look in google/cloud/security/__init__.py in your installation).

1.1.10 (also tested on v 1.1.9)

[x] Which module(s) (inventory, scanner, enforcer, explain) you're having trouble with.
setup_forseti.py
[x] Include errors, log output, and host operating system, including installed packages.
[x] Note how you deployed (via Deployment Manager, local system, etc.).

When following the quickstart instructions, deploying using Deployment Manager and Google Cloud Shell, I get the following error:
Enabling the IAM API...
ERROR: (gcloud.alpha) Invalid choice: 'service-management'.
Usage: gcloud alpha [optional flags] <group | command>
  group may be           app | auth | billing | compute | config | container |
                         dataflow | deployment-manager | emulators | endpoints |
                         firebase | functions | genomics | iot | ml |
                         ml-engine | organizations | projects | pubsub |
                         resource-manager | resources | scheduler | services |
                         source | spanner | tasks
  command may be         init | interactive | search-help

(This failure occurs for all of the APIs that the startup script is trying to  enable).
My gcloud has a gcloud service-management command, but not a gcloud alpha service-management one, being version :
Google Cloud SDK 188.0.1
alpha 2017.09.15
app-engine-go
app-engine-java 1.9.61
app-engine-php " "
app-engine-python 1.9.66
app-engine-python-extras 1.9.63
beta 2017.09.15
bq 2.0.28
cbt
cloud-datastore-emulator 1.4.0
core 2018.02.08
datalab 20180119
docker-credential-gcr
gcd-emulator v1beta3-1.0.0
gsutil 4.28
kubectl
pubsub-emulator 2018.02.02

Thanks for opening the issue @paultiplady! @joecheuk will follow-up shortly with our planned next steps to get this resolved for you (and others).

Hi @paultiplady , thank you for opening the issue! We have put in a hotfix to the master branch and everything should be working now. Can you do a git pull in your forseti-security folder to update the files and start the installation process again?

That has resolved the issue, thanks for the quick response!

Hi @paultiplady ,
No problem at all! I will just go ahead and close this issue for now, feel free to reach out if you have more questions!
Best regards,
Joe


Iran has 31 provinces, in TW we only have 30

Steps to reproduce the bug
Geographic areas:
The province of Alborz is lacking.
Could someone include it, please?

Screenshot
No response
Expected behavior
All other provinces of Iran are normal. This one is entirely missing.
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
No response
Browser Used
No response

Another one for the list of missing geographic areas:
Chile has 16 regions, but there are only 15 in TW = Ñuble is missing.

Puno en Peru also - i've setup a request for that independently as 'enhancement'

Santo Domingo de los Tsáchilas Province in Ecuador, also lacking.

Ecuador province of Napo has incorrectly the shapefile for Tungurahua instead.

Napo is Tungurahua and vice-versa:
https://sfg.taxonworks.org/geographic_areas/32140
https://sfg.taxonworks.org/geographic_areas/32141

Ilfov in Romania is lacking.

Osmaniye in Turkey has no shapefile.

Ningxia Hui in China has no shapefile.


Update alz_checklist.en.json (Governance Training Links)

@BeckyHope19 - Would you be able to review this one?

Hi @Azure/fta-alz-vteam do you mind reviewing pls ?

@brsteph what's the linting check complaining about on this run?

Funny, I can't see any JSON error either...

Ah, got it, it is a missing comma in line 134. It possibly went through in a previous PR without anybody noticing?

@alisakina99 are you able to make the quick fix on this one?


(10e-6)/18742 evaluates incorrectly to 5.335610e-1 instead of 5.33561e-10

This seems to be related to trimming trailing zeros on results

fixed by 2c99271108e0d86341837f185a6102363ccee8a6


[CELEBORN-1416] Add CI for helm charts lint and test

What changes were proposed in this pull request?

Add GitHub CI workflow to run lint and unit tests against helm charts.
Move the CI tests/kubernetes-it/docker/helm/values.yaml to charts/celeborn/ci/values.yaml, as this is a common convention, for example prometheus-community/helm-charts.

Why are the changes needed?

CI/CD

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Local test.

@pan3793 Can we allow to run actions/helm-chart-testing in CI.

@ChenYi015 please follow ASF GHA policy https://infra.apache.org/github-actions-policy.html

@pan3793 PTAL, thanks!

Thanks, merged to main for 0.5


Add reader/writer persistence locking support

@baldersheim please review
@geirst FYI
This adds support for concurrent processing of get(), createIterator() and iterate() against the SPI for a single bucket iff no conflicting operations are currently running for the bucket. We can finally do this now that VDS is but a fading memory of the past.
In particular, please verify that Proton handles these changes in SPI call concurrency semantics.

@toregge FYI


IT Picture medium term - outcome of modern tools

Need to clearly explained how the adoption of modern tools will mean changing our processes to seek benefits of such modern tools.
If we don't change our ways, modern tools are useless

Which document is that related to? Is it separate from Long Term vision? @remyb2canada

Confirm what work remains on this task.


Make TFF app interface with IYO verification levels

In IYO, there are different verification levels.
Within TFF app, certain functionalities require different verification levels.
TFF app should be able to check verification level of user and ask to initiate improved verification if needed.
E.g., a hoster should be address verified (ID level 2).

#68


Backport of 'Select archive #226' to 1.0.x

Coverage increased (+0.2%) to 88.791% when pulling 99e49f5ae26f38abe53dbea4779440d18aea8776 on deniszh:DZ-archive-1.0.x into 03eb41ba89f9cea4723f65c37e2c2e887ff3e250 on graphite-project:1.0.x.


Projectile aimbot timing issues

[[
Fedoraware Version Date:
Config used:

Description:

projectile aimbot is shooting slightly further into futhere then enemy sis going so it shoots slightly further then he would go.
Steps to reproduce:

[x] I am able to consistently reproduce this error

use projectiles
Steps to reproduce the behavior:

enable projectile aimbot and use it.


Getting a 403 when using the conventions in lambda.go but not when creating a session per AWS docs?

Hi... I was getting a 403 AccessDeniedException repeatedly when running nuclearpond in my environment.
I've successfully deployed via terraform and can test the lambda via CLI and Python boto3, getting expected results.
However, when running nuclearpond the invokeFunction was always failing and returning a 403 / AccessDenied.
I looked at https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/lambda-go-example-run-function.html and since I was getting desperate, I changed the code to more or less exactly match what was there.
I was a little surprised when that actually worked. I'm not sure the difference but using the following implementation for invokeFunction gave me no errors at all. Can anyone else reproduce this behavior or is this a "me" thing?

 Can you provide the full output of the error, perhaps it is the function that's receiving that message? Not sure. Thanks for creating the issue!

Sure, it was a bit weird actually I just got a HTTP 403 that seemed to be associated with how the session was created. I can manually invoke the function via CLI, execute it via boto3, but in the standard nuclearpond method I get a AccessDeniedError when executing the lambda. No extra error info. When I run the above code instead, it works every time.
I do 0 golang in my day job so I just tried cut and paste the standard AWS tutorial code and was a bit surprised to find out it works. I'll add a screenshot to this as soon as I get back in there.


Move "client" out of haas.cfg to somewhere less icky

I noticed that running "project_apply" from anywhere other than the directory containing 'haas.cfg' causes the client to spit out a "ConfigParser.NoSectionError: No section: 'client'" error.  The 'client' information should probably be stored in a different configuration in a more sensible location.

This can be done via setting the HAAS_ENDPOINT env variable now.


Bug: sdk selfupdate command invalid

Bug report

Documentation states that to update SDKMAN! itself that the command sdk selfupdate should be used. when I execute that command it reports "Invalid command:  selfupdate" and Usage does not include the selfupdate command as an option.
To reproduce

install the latest SDKMAN!
run sdk selfupdate

$ sdk selfupdate

Invalid command: selfupdate

Usage: sdk <command> [candidate] [version]
       sdk offline <enable|disable>

   commands:
       install   or i    <candidate> [version] [local-path]
       uninstall or rm   <candidate> <version>
       list      or ls   [candidate]
       use       or u    <candidate> <version>
       config
       default   or d    <candidate> [version]
       home      or h    <candidate> <version>
       env       or e    [init|install|clear]
       current   or c    [candidate]
       upgrade   or ug   [candidate]
       version   or v
       broadcast or b
       help
       offline           [enable|disable]
       update
       flush             [tmp|broadcast|metadata|version]

   candidate  :  the SDK to install: groovy, scala, grails, gradle, kotlin, etc.
                 use list command for comprehensive list of candidates
                 eg: $ sdk list
   version    :  where optional, defaults to latest stable if not provided
                 eg: $ sdk install groovy
   local-path :  optional path to an existing local installation
                 eg: $ sdk install groovy 2.4.13-local /opt/groovy-2.4.13

System info

OS
-- OS Name:                   Microsoft Windows 10 Enterprise
-- Version:                10.0.19044 N/A Build 19044
Shell (git-bash)
-- GNU bash, version 5.1.16(1)-release (x86_64-pc-msys)
sdk version
-- SDKMAN 5.16.0

adding sdkman_selfupdate_feature=true to $HOME/.sdkman/etc/config fixed it for me

@ben-wing just curious, but how did you install SDKMAN? We have a feature flag in SDKMAN that disables selfupdate if it is installed by package managers such as brew. In cases like that, the package manager will handle any updates.

the way i installed SDKMAN was
bash <(curl -sSL "https://get.sdkman.io")
followed pretty much immediately by
mkdir -p $SDKMAN_DIR/etc \
  && echo 'sdkman_auto_answer=true' > $SDKMAN_DIR/etc/config \
  && source $SDKMAN_DIR/bin/sdkman-init.sh \
  && sdk selfupdate force

part of a script that my work provided to install their standard corporate development environment.
it appears that i should suggest we add
  && echo 'sdkman_selfupdate_feature=true' >> $SDKMAN_DIR/etc/config \

Okay, right. The problem is in your second line:
  && echo 'sdkman_auto_answer=true' > $SDKMAN_DIR/etc/config \

You are overwriting the etc/config file using >.
This effectively clears out all the default configs, including this entry:
sdkman_selfupdate_feature=true

If this value is not set, it defaults to false and the selfupdate subcommand and all its references disappear.
Hope this helps!

I'm removing the bug label because this is a usage issue.


cannot get started

cd offline-quickstart-lab/app
npm install
node server.js
Error: Cannot find module '.../PWA/pwa-training-labs/server.js'
node -v
v11.10.0

Error: Cannot find module '.../PWA/pwa-training-labs/server.js'

This means node server.js is looking in .../PWA/pwa-training-labs/ for server.js, which implies your cd offline-quickstart-lab/app command was unsuccessful.
You just need to cd into the correct location (.../PWA/pwa-training-labs/offline-quickstart-lab/app)
If you feel unsure about how to navigate in the command line or don't know what "cd" does, check out some of these resources to learn more about it:

basic Windows commands
navigating files and directories in unix


Program/gui calculator

GUI Based Calculator Added

Can you shift calc to center of output screen for better UX?

It's possible

fixed the width and height of calculator @cveal1 @Jones-Mutua


Port the fixes from lint-python script in Apache Spark

This PR ports the changes in lint-python script at Apache Spark:
https://github.com/apache/spark/commit/ed8a260749e3d26d82829986c3b36bc9043d854a#diff-ccd847a0316575dde31bd89786bbe1f2
https://github.com/apache/spark/commit/5c71304b43b33ace517ba2f38c768f74528fdbbe#diff-ccd847a0316575dde31bd89786bbe1f2
https://github.com/apache/spark/commit/561e9b968821ca3e501aa5cba7ba5ceaa45796ea#diff-ccd847a0316575dde31bd89786bbe1f2
https://github.com/apache/spark/commit/20c60a43ccebd6fc05e18b4a0bd4ddbd0ed658f9#diff-ccd847a0316575dde31bd89786bbe1f2
https://github.com/apache/spark/commit/0ce5519f179a8f88a688dece754596c3166528b7#diff-ccd847a0316575dde31bd89786bbe1f2

Codecov Report

Merging #1345 into master will decrease coverage by 2.25%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1345      +/-   ##
==========================================
- Coverage   95.15%   92.90%   -2.26%
==========================================
  Files          34       34
  Lines        7472     7540      +68
==========================================
- Hits         7110     7005     -105
- Misses        362      535     +173

Impacted Files
Coverage Δ

databricks/koalas/usage_logging/__init__.py
24.32% <0.00%> (-71.18%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50.00% <0.00%> (-50.00%)
:arrow_down:

databricks/conftest.py
88.67% <0.00%> (-7.55%)
:arrow_down:

databricks/koalas/__init__.py
78.72% <0.00%> (-6.39%)
:arrow_down:

databricks/koalas/frame.py
93.43% <0.00%> (-3.28%)
:arrow_down:

databricks/koalas/namespace.py
86.26% <0.00%> (-1.50%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0.00%> (-0.96%)
:arrow_down:

databricks/koalas/testing/utils.py
78.26% <0.00%> (-0.73%)
:arrow_down:

databricks/koalas/indexing.py
94.82% <0.00%> (-0.22%)
:arrow_down:

databricks/koalas/groupby.py
91.25% <0.00%> (-0.18%)
:arrow_down:

... and 6 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 e4e5a1c...90b8ccb. Read the comment docs.

Let me just merge @ueshin, there were not so many conflicts here.


Add kubectx/kubens

https://github.com/ahmetb/kubectx
I guess everybody knows about this so not much to say.

added


Add pgvector 0.6.0

Update the current pgvector extension version 0.5.1 to 0.6.0 to include parallel index build
https://github.com/pgvector/pgvector/releases/tag/v0.6.0

Waiting for Autoscaler team, requires more memory in shmem.

Reopening the issues, as it's not done yet, and blocked by https://github.com/neondatabase/autoscaling/issues/800

The blocker is basically that we do not have enough for memory for many use cases, and we run out of memory.
To avoid that, we need to enable swap. From there we autoscale up.

Current blockers:

Swap changes (proposed for May 20th)
Increase max_worker_processes

Release scheduled for week 22, 2024.


Show Who Can Loot Mob

Need to investigate if we can show who loot belongs to with the BC APIs we have access to.

Not possible with current API.


global Title mapping

Consider eg LOD CBMAA Titles.csv that includes eg this record:
ObjectID=     197
TitleID=      6,716  (someone printed the ID with a decimal separator, silly)
Title=        From "Album Unique" formerly in the collection of the Duke of Portland
TitleTypeID=  4
TitleType=    Group Title
DisplayOrder= 2
DataDate=     12/23/2015

The global Title mapping http://review.americanartcollaborative.org/entity/E22_Man-Made_Object#field_1-search_0 has the following problems:

doesn't specify the URLs, which has allowed the mapping implementers to botch it like this: https://github.com/american-art/cbm/issues/58 items 1 and 2 (TWO wrong URLs in one mapping!)
The title type (eg http://data.americanartcollaborative.org/page/cbm/object/197/title_type) mixes SKOS (skos:prefLabel) and CRM (crm:E55_Type) in an undisciplined way
There's no relation of title type to AAT. Whenever you need a concept like Group Title, write to Patricia and she'll add it. (AFAI remember, CCO has such a concept)
DisplayOrder is not modeled but often it is important
(@azaroth42: back to the discussion whether using rdf:List is appropriate for this. crm:P102_has_title cannot point to a rdf:List)
A more subtle problem: Group Title reflects a collection of objects so it should be modeled as crm:E78_Collection

We can't use crm:E78_Collection, because there's not an explicit collecting plan.
Even if there were an AAT term, the museum has not reconciled their internal thesaurus to the AAT yet, so it's valid to use local thesauri.
I don't see any issues using both SKOS and CRM together.
It may have been the wrong decision, but I didn't think it was my responsibility (as the developer of the Browse app) to specify the URL patterns for the mappings. I can work with whatever, as long as they're conceptually valid.  I agree that the mappings here are not valid, and will need to be fixed, but I didn't want to impose my preferences on how they should be assigned on ISI.
I'm not going to touch the displayOrder issue.  That conversation is out of my league.

I agree that CRM is broken when it comes to ordering. That's a tradeoff of choosing CRM. displayOrder as a global property is also broken, it needs to be an overlay similar to ore:Proxy or schema:ListItem.
The issues with the definition of CRM's Collection are well understood and unsolvable.
Propose close.

@azaroth42 Should I post any issues at all then?

As discussed, our target model is fixed for the current project. So any model changes are not in the scope of work for 2017 for AAC. Feel free to post issues, but expect not to get much traction on solutions.

All issues that I post in this project are for a future version.
But you take them all as "propose to close" (not relevant? wrong? insurmountable?)
So I'm wondering if I should bother to post any.
If we continue a specific discussion in this issue: CRM is not broken when it comes to ordering. CRM merely lacks ordering. The source data has a field DisplayOrder, which is often important, so it should be mapped.
There are many ways to implement ordering:

CO: http://purl.org/co/, which is used by SPAR (eg http://www.sparontologies.net/examples#fabio_2)
OLO: http://smiy.sourceforge.net/olo/spec/orderedlistontology.html
rdf:List, which IMHO is not the best way for the reasons explained before (most importantly, rdf:next*/rdf:first is not guaranteed to return them in a specific order)
a custom prop right in the Title. Because Titles are not shared between objects, that's an adequate and the simplest solution.


⚠ Turnos 24x7 has degraded performance

In 6021d8d, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 2910 ms

Resolved: Turnos 24x7 performance has improved in d5d7d37.


[UI] Enhance navbar

📋 Description
This pull request enhances the navbar in the CampX web application to provide a better user experience and improved accessibility.
🔨 Changes Made

Implemented responsive design enhancements to ensure the navbar adapts seamlessly across all screen sizes.
Added hover effects and improved the link arrangement for better clarity and usability.
Introduced dropdown menus for better organization of content.

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings.
[x] I have tested it locally and it works fine.
[x] I have commented my code, particularly in hard-to-understand areas.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[x] UI enhancement (non-breaking change which enhances UI) 🎨

📸 Screenshots
Large Screen:

Medium Screen:

Small Screen:

Thank you for contributing to VigneshDevHub! We look forward to reviewing your PR and getting it merged!

Hey @Vignesh025 ,
I noticed the auto labeler is failing with the error: HttpError: Resource not accessible by integration. It seems like a permissions issue with the GitHub Action. Could you check the configuration or token permissions? Thanks!

Your code is breaking. Please undo all the deletions made in the app.js file.

The code is still breaking, and it's showing that currentpath is not defined in navbar.ejs. Please check and resolve this issue.

The issue with currentPath not being defined in navbar.ejs is resolved. I added a middleware in app.js to pass currentPath to all views, ensuring it can be properly accessed and used throughout the application.

Thankyou for Contributing!


Raspberry DLL error: tls-client-arm64.so: wrong ELF class: ELFCLASS64

Raspberry-pi 4B+ is running under aarch64 arch. This file may not work, and there is no tutorial on how to compile hown arch, or even what you have compiled.

If you wanna build tls_client by yourself.
# clone the repository
git clone https://github.com/bogdanfinn/tls-client.git

# go into build folder
cd tls-client/cffi_dist

# compile
GOOS=linux CGO_ENABLED=1 GOARCH=arm GOARM=7 CC="gcc" go build -buildmode=c-shared -o ./dist/tls-client-arm64.so

# moove it into python
mv ./dist/tls-client-arm64.so /home/pi/.local/lib/python3.9/site-packages/tls_client/dependencies/
mv ./dist/tls-client-arm64.h /home/pi/.local/lib/python3.9/site-packages/tls_client/dependencies/

if i wanna build it for rpi0 i should just change build options to arm32?

Probably

if i wanna build it for rpi0 i should just change build options to arm32?


Improve support for sinope Calypso and Eco Mode

Proposed change

Code cleanup for calypso controller.
Add support for Eco Mode on thermostats, Eco Sinopé
Add  many attributes for sensor and light in manufacturer cluster

Additional information

Checklist

[x] The changes are tested and work correctly
[x] pre-commit checks pass / the code has been formatted using Black
[ ] Tests have been added to verify that the new code works

It was an error as the TankSize finally is not in the attribute but only in Neviweb cloud. It is not used by the Calypso. I've left the attribute there as other could be able to find out the usage.
I have many other attribute that are still unknown. is it better to leave them out until I find the usage or put them in the quirks so other have access to play with them.

I'm thinking of splitting the 4 files into specific file for each device model.

Generally yeah, it's nicer to have different device types separated. For example, switch.py has smart plugs, valve controllers, ... from what I can see. IMO, it's still fine for these, as there aren't too many models, but we're open for a "cleanup PR" if you want.

I have many attributes found in manufacturer cluster but still need to find out the use. Generally I don't add them to the quirks but could it be better to add them as unknown_attr_xx so other can try to understand the usage for them so we can put a name on them ?

many attributes found in manufacturer cluster but still need to find out the use. Generally I don't add them to the quirks but could it be better to add them as unknown_attr_xx

I don't have a real preference. If they're likely not needed, I wouldn't add them, but it should also be fine if you do add them.


Error with input length

I have successfully run the exact same code with exact same data last night, but it gave me the following error tonight.
The code and error are shown below, thank you!

The transformers library was just updated to v3.0.0 yesterday.    I've tested sentence pair classification with v3.0.0 on MRPC dataset and everything still works.  So, I wasn't able to reproduce this problem. All other ktrain v0.17.3 tests pass with v3.0.0 of transformers, as well.
If you're using transformers==3.0.0, can you try downgrading to 2.11 and let me know what happens?

The transformers library was just updated to v3.0.0 yesterday. I've tested sentence pair classification with v3.0.0 on MRPC dataset and everything still works. So, I wasn't able to reproduce this problem. All other ktrain v0.17.3 tests pass with v3.0.0 of transformers, as well.
If you're using transformers==3.0.0, can you try downgrading to 2.11 and let me know what happens?

After I downgrade transformers to 2.11.0, I can run the code.

Are you training on a publicly available training set that you can share?

Are you training on a publicly available training set that you can share?
I think this is a bug in the v3.0.0 of transformers, but I'm not able to reproduce it on my end.

Here is the link for the publicly available training set I used:
https://figshare.com/articles/RumourEval_2019_data/8845580
Thanks

Thanks - I looked at the link briefly, but it wasn't immediately clear to me how you preprocessed this dataset for sentence pair classification with three classes.  It sounds like encode_plus method in transformers==3.0.0 isn't correctly truncating to max_length for at least one example in your dataset.
If you have x_test available and post it somewhere as CSV or something, I can look into it.  (It looks like the problematic example is in x_test.)
Otherwise, you can maybe add a print statement and post the text of the example that is throwing the error.
Thanks.

Thanks - I looked at the link briefly, but it wasn't immediately clear to me how you preprocessed this dataset for sentence pair classification with three classes. It sounds like encode_plus method in transformers==3.0.0 isn't correctly truncating to max_length for at least one example in your dataset.
If you have x_test available and post it somewhere as CSV or something, I can look into it. (It looks like the problematic example is in x_test.)
Otherwise, you can maybe add a print statement and post the text of the example that is throwing the error.
Thanks.

Hi, I have put the test data here:   https://github.com/YLi999/Test-data

Thanks for help @YLi999 .  I found the cause of the problem after trying your CSV:  default truncation strategy in transformers==3.0.0 was changed which breaks sentence pair classification.    The simple fix is to explicitly provide the truncation strategy. I've updated ktrain, so transformers==3.0.0 should work with v0.17.4 of ktrain.


regression add sync and check the count of table after load

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

close this, https://github.com/apache/doris/pull/18945 have add sync


typo: buisness -> business

@nschonni : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-docs/desktop-directquery-data-sources.md
:white_check_mark:Succeeded

powerbi-docs/desktop-latest-update.md
:white_check_mark:Succeeded

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

Reviewed editorial correction.


Fix Issue #26

Modifies Parser so that the allowedValues for an option are honoured and
an error thrown on illegal values
Includes unit test which verifies the improve behaviour

I've now forked my own variant of airline with this and various other changes I wanted so I am closing this pull request since this is no longer a self-contained feature in my fork

Why did this never get fixed? It's causing me problems right now...

@cread My fork at http://github.com/rvesse/airline has this and many other fixes that have never been accepted here


Update specs2-core to 4.20.0

About this PR
📦 Updates org.specs2:specs2-core from 4.19.2 to 4.20.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.specs2", artifactId = "specs2-core" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

Superseded by #314.


Helm Installs Don't Honor Timeout

I have tried to install Spinnaker via Helm many times. Most fail. A lot of them with this error:
$ helm install stable/spinnaker --namespace spinnaker --wait --timeout 1500
E0224 13:38:51.978584   19536 portforward.go:175] lost connection to pod
Error: transport is closing

Note that they fail in just a couple of minutes, not the 25 minutes specified. Shouldn't they be honoring the specified timeout?

I wonder if the port forwarder also needs to be given the timeout window. @adamreese do tunnels close if idle for some amount of time?

@technosophos Tunnels will remain open until closed
@pluttrell Did the pod restart?  I wonder if the connection dropped becuase the pod was killed.

No I am not seeing the pods restart.

I have the same problem without any using helm. Just issuing this to connect openshift:
oc -n podify port-forward postgresql-1-hal3g. It seems it is able to work at least about an hour then it starts failing.

So this may be an upstream issue rather than a Helm-specific one. Can we get a list of Kubernetes versions/distributions that this is showing up in?

Having the same problem, helm upgrade --wait --timeout 600 times out after 5 minutes. I see the following:
+ helm upgrade --install --wait --set minReplicas=1 --set maxReplicas=16 --set env=stage --values values.json --timeout 600 --debug --version 0.0.16 --recreate-pods merlin jiff/docker-compose
[debug] Created tunnel using local port: '38247'

[debug] SERVER: "localhost:38247"

[debug] Fetched jiff/docker-compose to /root/.helm/cache/archive/docker-compose-0.0.16.tgz

E0810 20:32:00.022184     135 portforward.go:178] lost connection to pod
Error: UPGRADE FAILED: transport is closing

Helm version: 2.5.1
Kubernetes version: 1.6.2

As @bacongobbler suggested I'm summarize my experience with the same problem here.
helm 2.6.1 client and server
k8s 1.7.4 (same behavior with 1.7.0 also)
When I run helm delete --purge xxx helm reports
portforward.go:178] lost connection to pod
Error: transport is closing

Yet the delete seems to have succeeded. All the k8s resources defined by the chart are cleaned up as expected. The tiller log looks like this:
[storage] 2017/09/28 14:14:19 getting release history for "xxx"
[tiller] 2017/09/28 14:14:19 uninstall: Deleting xxx
[tiller] 2017/09/28 14:14:19 executing 0 pre-delete hooks for xxx
[tiller] 2017/09/28 14:14:19 hooks complete for pre-delete xxx
[storage] 2017/09/28 14:14:19 updating release "xxx.v1"
 (many lines of "Starting delete for yyy" and "Using reaper for deleting yyy" omitted here)
[tiller] 2017/09/28 14:16:42 executing 0 post-delete hooks for xxx
[tiller] 2017/09/28 14:16:42 hooks complete for post-delete xxx
[tiller] 2017/09/28 14:16:42 purge requested for xxx
[storage] 2017/09/28 14:16:42 deleting release "xxx.v1"

That's the end of the log. It contains no errors or exceptions.
k8s reports no restarts of the tiller pod.
The elapsed time, from outside and from the log, is about 2m 30s, well under the default timeout value for the delete operation.
Also, on https://github.com/kubernetes/helm/issues/2983 @bacongobbler asked "Can you check on the load balancer fronting your kubernetes master API ...?" To my knowledge in this dev cluster there is no LB in front of the master, but I'll double-check and if there is, is there anything specific I  should be looking for?

This was fixed in 2.8.0 and now 2.8.2 is coming out with a improved version of that (the transport closing fixes)

It might've been fixed by proxy, but I don't think this was directly fixed. Same error, different area of the code

@bacongobbler oh hmm which part? When I was running into transport closed issues it was with portforward as well since AWS NAT Gateways were closing it (#3182), that's why I am curious what area it is

We fixed helm init --wait timeout issues, but not specifically helm install --timeout.
install --timeout uses the helm.InstallTimeout option, whereas init --wait uses the helm.TillerConnectionTimeout option.

they're sorta confusing but essentially:

TillerConnectionTimeout specifies the timeout duration to connect to tiller
InstallTimeout specifies the timeout to wait for resources to become ready during helm install

I'm having all kinds of timeout, both on tiller and on install (transport is closing as well), using helm 2.9.0. It's really annoying, there's azure LB involved, but I already set the idle timeout to 10 minutes.
Even using --wait --timeout 600 and --tiller-connection-timeout 600 doesn't seem to fix the problem.

Still encountering the same problem with install --timeout (however I think the timeout is much shorter than 5 minutes, it's non-configurable 1 or 2 minutes).
Nobody is looking at this?

/remove-lifecycle stale

/remove-lifecycle rotten

as far as I understand, nobody in the community is currently looking into this particular issue.

From what I can tell, the timeout is only not honored when attempting to do things remotely.  If I log into one of my kubernetes nodes and issue the commands from there, it will sit there until the operation completes fully, whereas if I try to do it remotely it times out fairly quickly.... this lends credence to the theory that the issue lies with whatever loadbalancer is in front of kubernetes.

i hit this as well, its kinda annoying since we have a big deployment.

Still getting this error when tries to upgrade helm release with --wait option.
helm upgrade release-name app --wait
E0612 15:28:57.991943   12415 portforward.go:233] lost connection to pod

helm version
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}

The only workaround that I found is to add your tiller service address as --host option:
helm upgrade release-name app --wait --host=<IP_ADDRESS>:44134

We are also seeing similar issue when we do helm install/upgrade/delete/ls. Any fix?
For Example:
# helm upgrade  -i app app/ncs --version 10.4.3318-2 --namespace ns
E0716 17:44:58.671861   11327 portforward.go:178] lost connection to pod
Error: UPGRADE FAILED: transport is closing

# helm version
Client: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

@gvenka008c have you had a look at https://github.com/helm/helm/issues/2025#issuecomment-447348731?

@bacongobbler Yes, checked that. We have one node where helm is installed and tiller runs on our k8 cluster nodes (3 nodes). we do all helm install from this server which talks to k8 cluster. Not sure if our proxy is blocking the traffic or timing out. Let me check on that. Thanks.

@bacongobbler Yes, checked that. We have one node where helm is installed and tiller runs on our k8 cluster nodes (3 nodes). we do all helm install from this server which talks to k8 cluster. Not sure if our proxy is blocking the traffic or timing out. Let me check on that. Thanks.

any progress?

what is the update ?

try with helm 3.0 ;-)

I wouldn't hold out on upgrading to 3.0 being the fix. If @kotamahesh and @torubylist are experiencing the same issues as @badloop described back in 2018 (https://github.com/helm/helm/issues/2025#issuecomment-447348731), then the issue isn't with Helm, but it's with the load balancer fronting the Kubernetes API server that's closing the long-running connection too early.
It's worth giving a shot, at the very least.

@torubylist and @kotamahesh, if you wouldn't mind sharing your experiences, that would be more helpful. That way we can help try to diagnose the issue you are seeing, and try to direct you towards a potential solution.

@bacongobbler, Thanks for the response,
I think helm upgrade won't resolve the issue, even I suspect this was due to connectivity issues in between Kube API and LB, as our lab has some network issues. I will get back to you if I can reproduce the issue after network problem is resolved.

Hi @bacongobbler  after the network issues are resolved, I am unable to reproduce the issue.
what you said "but it's with the load balancer fronting the Kubernetes API server that's closing the long-running connection too early. " was right.

Running into similar issue with AWS EKS, and helm (2.16.1) upgrade with --timeout set to 604800 (7d). I have a Job running as post-install/pre-upgrade hook, which requires few hours to complete, but Helm reports the deployment has failed:
INSTALL FAILED
PURGING CHART
Error: Failed to deploy release-name
Successfully purged a chart!
Error: Failed to deploy release-name

With the following accompanying tiller log:
[tiller] 2020/04/02 12:47:11 warning: Release release-name post-install chart-name/templates/helm-hook-job.yaml could not complete: Failed to deploy release-name

As per hook configuration the job isn't deleted by Helm, and in Kubernetes it continues to actually run, and completes in a couple of hours though.
I tend to think this is caused by what @andreychernih mentioned above in https://github.com/helm/helm/issues/2025#issuecomment-359223071, but how could I verify that this is actually AWS EKS API web server which terminates the "watch" operation for the job and fails the helm deployment?

You could start a pod inside of your cluster, install the Helm client there, and run the deployment entirely inside of the cluster. That would only rule in/out some things (like whether a load balancer in the middle was terminating the connection), but it is at least a good debugging step that should provide some useful information.

Still getting this error when tries to upgrade helm release with --wait option.
helm upgrade release-name app --wait
E0612 15:28:57.991943   12415 portforward.go:233] lost connection to pod

helm version
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}

The only workaround that I found is to add your tiller service address as --host option:
helm upgrade release-name app --wait --host=<IP_ADDRESS>:44134

@andrvin Any clue on why specifying the --host would workaround the problem ?

Hi @technosophos
This issue might be similar to what is reported in this issue: https://github.com/kubernetes/kubernetes/pull/67817
we were running into this issue as well, and fixed it with this PR: https://github.com/proofpoint/helm/pull/16
I would be more than happy to submit the PR here if that looks ok.
Thanks

This issue should (finally) be fixed with https://github.com/helm/helm/pull/8507, which will become available in Helm 3.4.0. Let us know if that does not fix the issue present here. Thanks!


⚠ RPC server - Binance BSCT has degraded performance

In 3af95a0, RPC server - Binance BSCT ($BINANCE_BSCT_RPC_URL) experienced degraded performance:

HTTP code: 502
Response time: 474 ms

Resolved: RPC server - Binance BSCT performance has improved in dca0acb.


Small files: adding "big" small files or adding many small files does not work

Adding many files or large files (below the limit) leads to an instable network and peers may stop working completely.
It results in

losing the user profile
version fork
channel closed exceptions
...

With how many peers are you testing? Currently, there is a bug in tomp2p with the replication in a network with fewer peers than the replication factor (5).
Could you run another test to check if this happens again?
Adding / removing multiple files concurrently can lead to version forks of the user profile, although it theoretically shouldn't with the vDHT approach and the UserManager...

We definitely have more than 5 peers.
Regarding concurrency: on a single client or between multiple clients? We already experimented with lowering the concurrency and it seems to help, but eventually it just postpones the crash so far...
We further investigate this issue with Thomas tomorrow. He also suspects some memory (exceptions related to reference counting occurred as well)

Regarding concurrency: on a single client or between multiple clients?

Especially multiple clients. Concurrency on single client should be handled for the UserProfile.

We further investigate this issue with Thomas tomorrow. He also suspects some memory issues (exceptions related to reference counting occurred as well).

Since we still use Memory-based storage, this could probably be the reason for lost content. If disk-based storage is more reliable, we definitely need to switch or at least allow its configuration.

I'm still observing endless replication loops at the peers after some time. Content is moved forth and back all the time until the peers are crippled. This blows up the network and data is lost, what might probably also be what you observed. I need to re-check the issue with @tbocek.


ToggleDefaultStatus isn't working (build 3114)

For a few Sublime Text updates now, the ToggleDefaultStatus command hasn't been working, and the ', Line x, Column y' can be seen at all times on the status bar. Is there any workaround
through that?

May you try to replace \0 to \n in https://github.com/shagabutdinov/sublime-status-message/blob/master/status_message.py#L58 ?
I'm using latest version of sublime (build 3126) on Linux and I don't see this bug...

I just did it, but now instead of shifting ', Line x, Column y' slightly to the left and right, ToggleDefaultStatus does nothing.
I've tried this with a few builds, including the current, and using both win 7 and 10

While messing with  https://github.com/shagabutdinov/sublime-status-message/blob/master/status_message.py#L58 , I found out that the ToggleDefaultStatus command does work with whatever is in there instead of \0. I mean, the command is working, but whatever it works on, it's not the ', Line x, Column y'.

This is differences of sublime behaviour for Linux, Windows and MacOS... The \0 hack was used to hide the rest of string but seems it does not work anymore for you OS/version.
I don't have ideas how to hide default status message. Maybe you may try to insert several thousands of spaces instead of example but I'm not sure it'll help.

well, inserting spaces did work, except it also bumped tab/space size and file type out of the status bar

I don't know how to help you... there are only three probable variants could work (\n, \0 and spaces) and they all don't work; sorry :(

it's okay, at least spaces helps with it. I really enjoy SublimeStatusMessage, so I wouldn't like to stop using it. I'll try and see if I can get people who use windows and if they know a workaround for this. thanks for helping, nonetheless :)

Sure, no problem; I glad you like my plugin :)) I close this issue for now but let me know if you'll find a workaround, I'll include it repository.


Several UI changes

[x]  Display particle movement during search ?
[x] Forbid second search to launch
[ ] Divide "Hide" button into two toggles : trail and bodies.

Divide "Hide" button into two toggles : trail and bodies ==>Not planned


docs: delete de.yml and fr.yml under the language dir

As is the title.
These yaml files unnecessary.
e.g.  https://hexo.io/fr is 404.
Check List

[x] Others (Update, fix, translation, etc...)

Languages:
[ ] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

These files may be useful if one day we release the navy theme separately like https://github.com/hexojs/site/pull/1729

public/fr is related to source/fr, not themes/**/fr


1.3.6 Subscribe returns no items

Hi,
I upgraded to 1.3.6 but my subscriptions no longer work. No errors in the console but no matter what i do they are blank. My shared code can be seen at https://ide.c9.io/eba_sfdc/booker
Basically, i publish "Items" and try to subscribe to them with the below code (which works until 1.3.5 and I have "items" served):
angular.module('booker').controller('AdminCtrl', ['$scope',
     '$rootScope','$translate', '$reactive',
    function ($scope, $rootScope, $translate, $reactive) {
      $reactive(this).attach($scope);
      $scope.item = {
        itemName : '',
        tags : []
      };
      $scope.perPage = 3;
      $scope.page = 1;
      $scope.sort = {
        name: 1
      };
      $scope.orderProperty = '1';
      $scope.searchText = '';

      this.helpers({
        items: () => {
          return Items.find({}, { sort : $scope.getReactively('sort') });
        },
        isLoggedIn: () => {
          return Meteor.userId() !== null;
        },
        currentUserId: () => {
          return Meteor.userId();
        },
        images: () => {
          return Images.find({});
        }
      });

      this.subscribe('images');

      this.subscribe('myItems', () => {
        return [
          {
            limit: parseInt($scope.perPage),
            skip: parseInt(($scope.getReactively('page') - 1) * $scope.perPage),
            sort: $scope.getReactively('sort')
          }
        ]
      });
...
...

I probably missed something during the upgrade but couldn't figure out what.
Thanks for your advices,
Burock.
PS, I have about 3 meteor apps now excluding this playground app, all behave the same, subscribe does not return any collections

Have you somewhere some code which is referring to old version as '$meteor.object`or '$auth.require' and so on ?
Because once I rewrite my app entirely with the new API 1.3.6, everything was working again.

Unfortunately I did a file search and found nothing.. I have a suspicion about this package, though...
dburles:mongo-collection-instances  upgraded from 0.3.4 to 0.3.5
I also checked server side, when I use getReactively the server is not triggered despite I can see on the client that it requests and it does return empty collection. I dont want to reset mongodb assuming that's not effected.
Thanks
burock

I'm experiencing the same problem. The issue seems somehow related to the package<EMAIL_ADDRESS>.

@burock @dapids can you provide the actual app so I can try it locally?
Thanks

you can try mine from here: https://ide.c9.io/eba_sfdc/booker
thanks

Same here. seems somehow related to the package<EMAIL_ADDRESS>After update this package and angular package from 1.3.5 to 1.3.6 it occurred.
One interesting thing here,
this occur only when my publish have more than one cursor.

Can it be this line by ozsay on an update to angular-meteor-data where he renames angular-meteor.utils as:
'angular-meteor.utilities',

but under angular meteor packages it is actualy still utils..

@burock There are 2 modules for utilities. One legacy and one for current code.

ok.. saw it.. sorry, was reading the code.. i'll be more careful.

it's ok :) we are all here to help.
BTW can you clone the repo from c9 to github so I could look at it ?

here it is.. if you've a c9 user the one over there is already public https://ide.c9.io/eba_sfdc/booker ..
thanks
burock

@dotansimha,
Thanks for your help. Unfortunately I can't share my app.
I'll try to give more details as soon as I can.
Cheers.

@burock I have the same problem on 1.3.7 --
removing the line
$reactive(this).attach($scope);
and replacing this with $scope in my code seems to fix it.

yep, thanks a lot @jeroensmeets .. Commenting out that line $reactive(this) did really solve.
But, I think I will still stick with version 1.3.4 which looks the most stable, since the docs/tutorials and usage seem to be out-of-sync.
Cheers,

still got some problems randomly with subscription in 1.3.7 when a user is logged

Related to #1272
@Urigo It's a $scope - controller mixing thing. This issue can be closed because the other one is much more readable :eyeglasses:

great, closing


[enhancement]Add table python interfaces for TF running

Add table python‘s Interfaces which are for TF running. So you can run TF training or inferencing with python like this.
`    stream_env = StreamExecutionEnvironment.get_execution_environment()
num_worker = 2
num_ps = 1
python_file = "/python_file.py"
func = "func"
property = {}
zk_conn = "localhost:2181"
env_path = None
zk_base_path = None
table_env = None
input_table = None
output_schema = None
train(num_worker, num_ps, python_file, func, property,
          env_path, zk_conn, zk_base_path, stream_env, table_env, input_table, output_schema)

inference(num_worker, num_ps, python_file, func, property,
          env_path, zk_conn, zk_base_path, stream_env, table_env, input_table, output_schema)`

However，these are all based on pyflink, which means these all based on at least Flink 1.9 version.

How to use the Python APIs?

First of all, you should build pyflink. To clone Flink release-1.9 branch, enter
git clone -b release-1.9 https://github.com/apache/flink.git.
Then,
mvn clean install -DskipTests -Dfast
after that, build Pyflink by entering
cd flink-python; python3 setup.py sdist bdist_wheel
sudo pip install dist/*.tar.gz
which is described in https://ci.apache.org/projects/flink/flink-docs-master/flinkDev/building.html.
Secondly, we need to update the flink-ai-extend based on Flink 1.9-SNAPSHOT, see pull request
https://github.com/alibaba/flink-ai-extended/pull/23
Then, We need to put the modules and their dependencies into jars and put them in the pyflink lib library.
We can use the Python APIs now.


Add note about accessor instance creation

This is an attempt at clarifying accessor docs to help with the confusion I had in #3205. I'm not sure how many other xarray doc pages use .. note:: but it seemed useable here. I'm not sure this is worth the explanation or if it is worded the best, but thought this could start the discussion.

[ ] Closes #3205
[ ] Tests added
[ ] Passes black . && mypy . && flake8
[ ] Fully documented, including whats-new.rst for all changes and api.rst for new API

Thanks @djhoese, this is definitely worth noting!


Fix for CI test

Fix for CI test

PASS ./index.test.ts (229.257 s)
  ✓ can create a basic project (49528 ms)
  dev
    ✓ start keystone in dev (13113 ms)
    chromium
      ✓ init user (1004 ms)
      ✓ change name of admin (2891 ms)
      ✓ create post (1497 ms)
    webkit
      ✓ init user (1033 ms)
      ✓ change name of admin (1504 ms)
      ✓ create post (101074 ms)
    firefox
      ✓ init user (871 ms)
      ✓ change name of admin (1067 ms)
      ✓ create post (939 ms)
  prod
    ✓ build keystone (29259 ms)
    ✓ start keystone in prod (2545 ms)
    chromium
      ✓ init user (568 ms)
      ✓ change name of admin (636 ms)
      ✓ create post (502 ms)
    webkit
      ✓ init user (812 ms)
      ✓ change name of admin (881 ms)
      ✓ create post (732 ms)
    firefox
      ✓ init user (656 ms)
      ✓ change name of admin (699 ms)
      ✓ create post (582 ms
      ```

     ```
         webkit
      ✓ init user (1033 ms)
      ✓ change name of admin (1504 ms)
      ✓ create post (101074 ms)
      ```
      Something is up, @mitchellhamilton is this similar to what was happening on https://github.com/keystonejs/keystone/ ?


Update set-up-cluster-federation-kubefed.md

Fix https://github.com/kubernetes/website/issues/6377

This change is

Hold. I don't think we should be calling out GKE specifically in this way.

@stewart-yu do you want to close this, since the issue has been fixed in #6432 instead?


"Clear view" is getting rid of some options selected while filtering through SQL

Steps:

Import populated places (for example), create a map
Apply a query: SELECT * FROM ne_10m_populated_places_simple_1 limit 100 for example
Go to map view, edit color of the points, enable some columns for the infowindows
Clear query: Everything OK
Apply again the query, add another column in the infowindows
Clear query: the column for the infowindows is deactivated

Extra: it has been reported that the styles are also removed when the query is cleared, but I'm not been unable to reproduce the issue yet.

Yep, I just tested my steps above and the infowindow column went out after clearing the query the 2nd time

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Log rotation not present?

No.
AixLog is meant to be simple, but extensible. You can easily create a file logger with log rotation: https://github.com/badaix/aixlog#advanced-usage
Log rotation is already too special: when to rotate, filenameing, zipping of old log files, ...


Debug Draw

Hello! Is there a way to turn on debug draw in fxgl ? If it is, so how i can do this?

You can enable debug views in Dev mode via ctrl+0, then select view ->
debug. It only shows hit boxes, nothing else.
Let me know what things you want to be able to see.
On Sat, 10 Mar 2018 at 7:06 am, Łukasz<EMAIL_ADDRESS>wrote:

Hello! Is there a way to turn on debug draw in fxgl ? If it is, so how i
can do this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AlmasB/FXGL/issues/516, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADbZ9mb-Xmivz_AiKtdnX87GOzNT8w1Cks5tc3uPgaJpZM4SlLGN
.

I wanted to see fixtures for player, like on this example (ground sensor):

Done in 0.5.2


[TEVA-2166] - Remove references to TF workspaces

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-2166
Changes in this PR:

Removed bin/terraform-* legacy abstractions
Updated documentation to remove references to workspaces

Review app deployed to https://teaching-vacancies-review-pr-3161.london.cloudapps.digital


Android App Link doesn't work when use FB App Invite feature

Hi,
I implement Facebook App Invites. I am able to share app invite on the FB, but when click on the invite in the Android FB app, I got redirect to the Google Play Store, instead of my app. That redirect does not supply any information to the application. In the logs (adb logcat) from the Android FB app I see the following:

E fb4a.1jb: Native application url did not specify Android key hash.
ActivityManager: START u0 {act=android.intent.action.VIEW dat=market://details?id=MY-APP-BUNDLE-ID&referrer=utm_source=apps.facebook.com&utm_campaign=fb4a

Note: MY-APP-BUNDLE-ID is right one, I replaced it to post here.
SHA256 certificate fingerprint is supplied via Branch's dashboard.
In the Open Graph Object Debugger an app link looks reasonable, but doesn't contain app key hash:

my-app-prefix://referrer_player_id/8c1c19d0-7c18-11e6-b564-595eb34adaf7?link_click_id=link-367670459015568204

It looks like App Link construction goes wrong and does not add required fields, at least the Android FB app says that. I don't know it happens in the Unity plugin, Android library, or on Branch's servers, but it makes FB App Invites useless. At the same time, direct links, i.e. xxxx.test-app.link/..., works as expected, they open application directly through select app dialog.
I appreciate any help, thanks in advance!
P.S. I made support ticket as well.

Hi @featalion , thanks for report.
We have started investigation of that issue.

@featalion do you use last version of Branch SDK?
If no - try to update Branch SDK please.

@antonargunov yeah, I use the latest version of SDK

@antonargunov do you need more information about FB app configuration, AndroidManifest.xml, etc.?

After update to Unity3D 5.5 from 5.3 the bug disappeared.

@featalion thanks for report!


Problem in recursive Component of SPA

We can assume that: we have a SPA application consist of a profile page and a followerList page. The state tree is as shown in the following:
{
  profile: { name: xx, sex: xx },
  followerList: []
}

We can open a follower list page from a profile page A, and then open a profile page B from the follower list page. In my application, page A and page B share the same reducer profile.
Here is the problem: when page B rendered, the profile in state tree has been changed by B's info; when it returns back to page A, it is supposed to keep A's info, but it has also been rendered by B's info.

So far I've got two solutions:

Using a profileList to keep all profile pages have been opened. It means that I have to keep a list for every page which can be opened recursively.
Re-rendering the profile page when the page is returned. I don't think it's an elegant way.

How can I solve this problem?

I’d suggest using a profileList. Apart from solving this problem, it also helps with caching profile data. When a user opens the page B, closes it and then opens it again, the data is already available (it may require refreshing, but old data is better than no data).
As to recursively opened pages, I don’t think it’s a big concern unless a user opens several hundred pages in a row. And even if they do, you could start removing the data for the earliest opened pages and simply reload the data when a user returns to them.

This looks like a general usage question, rather than an issue with Redux.  Please post this over on Stack Overflow - you're likely to get better answers there.

@iamakulov Thank you for your advice. Caching profile data is really a good method, which is also very helpful to cut the request. But it means that I have to make the state tree more complex, and inject more concept (e.g. reselect). As I'm building the architecture of our app, increasing the complexity is not friendly to other developer.
Now I gave each page a new store, which is not recommended in redux, to solve this problem. This method is not so elegant, but really works....
Thank you for your advice again, and I will give a careful reconsideration of caching data.


Scheduler Tests

Very early days on this. Not sure I'm hitting all the correct aspects of Scheduler.

Coverage seems to be generated: https://codecov.io/gh/seanoshea/material-motion-runtime-android/src/927c5b92ab7386ebf7fbcf007c380a31caec6eae/library/src/main/java/com/google/android/material/motion/runtime/Scheduler.java

Current coverage is 45.72% (diff: 100%)

Merging #25 into develop will increase coverage by 45.72%

@@           develop        #25   diff @@
=========================================
  Files            6          6
  Lines          269        269
  Methods          0          0
  Messages         0          0
  Branches        48         48
=========================================
+ Hits             0        123   +123
+ Misses         269        126   -143
- Partials         0         20    +20

Powered by Codecov. Last update baa0f95...2c63f48

What is the ordered schedulers testing? Is it just adding code coverage?

@pingpongboss - for the testAddOrderedMultipleSchedulerListeners - I wanted to be able to add two plans to a scheduler and have them both be active.

Not sure I've got a good feel for how to test animations in unit tests for testDelegatePlanPerformanceSchedulerState.
When debugging the unit tests in Android Studio, the following lines of code are never hit:
            public void onAnimationStart(Animator animation) {
              token = tokenCallback.onDelegatedPerformanceStart(DelegatedPerformer.this);
            }

Makes me think that SchedulerTest needs to be some kind of async test.

Could perhaps use some of the logic in https://github.com/nhaarman/ListViewAnimations/blob/master/lib-core/src/androidTest/java/com/nhaarman/listviewanimations/appearance/ViewAnimatorTest.java in these animator tests?

Let's submit this PR without the test for animations in testDelegatePlanPerformanceSchedulerState(). The rest looks good to me.

Sounds good to me @pingpongboss. Perhaps Robolectric could help out with animation tests with APIs like:
ShadowAnimation animation = Robolectric.shadowOf(textView.getAnimation());
animation.invokeEnd();

Yup! Also, we can test DelegatedPerformance without an underlying animation.


[BACKEND] Add barrier after assert op to avoid race condition

Add a barrier to avoid a race condition in case an assert is followed by an op that may trap if the assert condition is true. Since the tensor in those two operations may have different layout we need to make sure all the threads are done executing the assert before going to the next op.

After this commit (and @peterbell10's https://github.com/triton-lang/triton/pull/5037, which turns debug=True back on for the test_side_effectful_reduction test), test_side_effectful_reduction and test_side_effectful_scan are hanging for me

After this commit (and @peterbell10's #5037, which turns debug=True back on for the test_side_effectful_reduction test), test_side_effectful_reduction and test_side_effectful_scan are hanging for me

hmm I wonder if we end up with barrier in control flow? @peterbell10 would this op be lowered within control flow?

ah, it makes sense that they are as we are effectively doing a sync inside an if statement lol
Not sure what's the best way to tackle this tho. We could make https://github.com/triton-lang/triton/pull/4811 less general, and just edit with the mask the asserts in the region, as we may have this issue with any function that calls sync inside a region passed to reduce / scan

end up with barrier in control flow

yes, #4811 introduces predicated asserts


Classic Bluetooth Scan not working correctly

Hi,
I'va got an ESP32_Wrover with External RAM enabled.
Classic bluetooth scan (AT+BTSTARTDISC) do not work correctly.
Endeed, sometimes wrong characteres are send to the uart.
For instance:
+BTSTARTDISC:98:9c:57:82:a9:2c,øÿÿ?EI P8 lite 2017,-73,2,0x2d0
We see that there are somme characteres "øÿÿ?" who should not be here.
the real name of the device is "HUAWEI P8 lite 2017"
An other issue is that the name buffer is not clear between two messages.
For exemple, I get this:
+BTSTARTDISC:00:06:66:77:7e:ca,øÿÿ?EI P8 lite 2017,-48
+BTSTARTDISC:00:06:66:77:7e:ca,PRECIA_i5-7ECA 2017,-43
=> the "2017" should not be here for the "PRECIA_i5-7ECA" device. It seems it comes from the previous device "HUAWEI P8 lite 2017"
And an other issue is that MAC address do not always match the device name...
In the previous exemple, both devices have the same MAC address but in fact HUAWEI have "98:9c:57:82:a9:2c" and "PRECIA_i5-7ECA" have "00:06:66:77:7e:ca"
So there is many many bugs in bluetooth scanning.

Did you find something ?

up

@Arti4ever
Please pull the latest master branch


[RFE] Introduce a regression test to ensure we respect liveness probes checks.

Current situation
Currently nodes with a high number of pods can result in liveness probe check failure e.g #940 resulting in timing out of kubectl deploy
Ideal future situation
We should have a basic regression testing at each change to see if default liveness proble is respected with 110 pods. 110 being default kubelet maximum pods.
Implementation options

Create a minikube cluster.
Deploy a nginx deployment with 110 replicas.
Deploy gadget.
Make sure the deployment from [3] doesn't timeout.

Hey @mqasimsarfraz
I tried to test this on a standard GKE cluster and here's the observation. If I'm targeting a node and creating a nginx deployment with 110 replicas, then this is what I'm seeing in the events. Some of the pods are not starting because of resource constraints.

Will the machines that we are using in CI will be able to support 110 pods on a single node?
I've only verified that the gadget daemonset on the respective node, and the gadget pod is not breaking. Does this issue require something else to test?

Hi @kranurag7 , Thanks for having a look at this issue. Please find my response below:

Will the machines that we are using in CI will be able to support 110 pods on a single node?

We can use --max-pods to ensure we don't hit OutOfpods. Given we use minikube in the CI it allows passing a flag like --extra-config=kubelet.max-pods=200 should do it in the CI. Also, alpine/sleep inf might be better choice for test deployment?

I've only verified that the gadget daemonset on the respective node, and the gadget pod is not breaking. Does this issue require something else to test?

That should be it. Since we have all the infra to deploy IG and test pods in integration. The idea was to add an automated test to verify readiness probe is respected at scale!
I hope it makes sense. Please feel free to let me know if you any more questions!

Closed in favor of https://github.com/inspektor-gadget/inspektor-gadget/issues/1394


005 create /about command

User input:
“/about”
Bot answer:
“(c) 2023 Alexei A Danilov, Igor A Khitrov”

created new function "/about"


Review against tslint-ban-snippets

Origin = https://github.com/mrseanryan/tslint-ban-snippets

[ ] includePaths

[ ] excludePaths

[ ] up README - examples


"block recieved too late" happens on honest network

log message:
Warn: Not rebroadcasting block $state_hash because it was received "6 slots too late"
happens on a fully honest network

I think catchup will broadcast old blocks right now...

We also have a bug where blocks are (or appear to be) late by exactly delta
slots for some reason. And I mean they arrive 2*delta slots after their
actual slot, they're not considered late if they're <= delta slots after
their slot.
On Mon, Jul 22, 2019 at 6:01 PM Corey Richardson<EMAIL_ADDRESS>wrote:

I think catchup will broadcast old blocks right now...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodaProtocol/coda/issues/2954?email_source=notifications&email_token=AAAPATIDG4JNVNPMKXRB3ITQAZKAHA5CNFSM4IF6TYX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2RTEGI#issuecomment-514011673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPATJDRLIWVCWY72YACN3QAZKAHANCNFSM4IF6TYXQ
.

This message is fine. It merely indicates that the system chose to not rebroadcast some blocks that were acquired during ledger catchup, which is what we want it to do. I think the fix here is to make this log message a lower level, such as debug.

https://github.com/CodaProtocol/coda/blob/master/src/lib/coda_lib/coda_lib.ml#L477
code for reference

I’m cool with the message and log level, more referring to why it’s being triggered as a bug (sounds like something in catchup, plus blocks arriving late by some multiple of delta?). Will edit body to make clear referring to that

What I meant before is that this is actually not a bug an is expected behavior. That is why I recommended downgrading the log message. This is the intended behavior which is triggering at the intended location. However, we could try and update the code to have more granularity for this log. For instance, this point in the code cannot differentiate between the source of transitions, which could be useful for identifying issues with the transition frontier controller in the future.


fix non-arc, cannot create __weak reference

i am sorry about i don't know how to modify old pull request,
so i create a new pull request again.

To update a pull request, just update your branch on github, it will then see the updates.

This seems to have multiple changes not related to the __weak usage.  Please just do a PR for that?

remove import of GDataBooks from GData
it seems be removed from project
while i compiled the code it would cause error

https://github.com/google/gdata-objectivec-client/pull/195  I think batch fixed a bunch of these issues.

thank you
i think i did it in a wrong way
i should not merge my change first
and i think i should delete my fork and fork from master again to keep my fork clear
i will delete this pull request later
thanks again


AKS supports windows server 2022

@ShiqianTao We need to add a new checkin test "AKS Windows VHD Build - PR check-in gate (build_vhd_2022_containerd build)" later


Using database in Schedule

Hi,
I wanted to create dynamic scheduling jobs so I have used model in Kernel.php like below
protected function schedule(Schedule $schedule) {$tasks = \App\Model\Task::where('enabled', true)->get();}
It works on local But when deploying to production it throws following error.
`>> Illuminate\Foundation\ComposerScripts::postAutoloadDump

@php artisan package:discover

In Connection.php line 664:
could not find driver (SQL: select * from tasks where enabled = 1)  `
If I remove the model query from kernel.php and define static schedule it works fine as expected. But I need to query database in Schedule to setup it dynamic.
Can any one guide me what is missing in production environment?

Hi there,
Looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
Discord
Larachat
IRC
StackOverflow


Can't use const constructors with mixins

Consider this code:
class Superclass {
  const Superclass(this.foo);
  final int foo;
}

abstract class Mixin {
  factory Mixin.fixed(int baz) = _FixedMixin;
}

class _FixedMixin extends Object with Mixin {
  _FixedMixin(this.baz);
  final int baz;
}

class Subclass extends Superclass with Mixin {
  Subclass(int foo, this.bar) : super(foo);
  final int bar;
}

I want the Mixin.fixed and Subclass constructors to be const, but today that isn't possible. It's not clear why.

The main reason why these constructors cannot be const is that certain constructors are omitted when mixin application occurs. For example:
In order for _FixedMixin(this.baz); to be a correct constructor, it must include a superinitializer (that is, a clause that causes a constructor in the superclass to be invoked during instance creation). In your example that superinitializer is implicit because there is no explicit superinitializer, but it corresponds to having _FixedMixin(this.baz): super();.
The superclass of _FixedMixin is Object with Mixin, i.e., it is a class which is introduced by mixin application rather than a class which is introduced by a regular class definition. Such a class is implicitly equipped with some constructors (spec section 'Mixin Application'):
For each generative constructor named $q_i(T_{i1}$ $ a_{i1}, \ldots , T_{ik_i}$ $ a_{ik_i}),
i \in 1..n$ of $S$ that is accessible to $L_M$, $C$ has an implicitly declared
constructor named $q'_i = [C/S]q_i$ of the form

  $q'_i(a_{i1}, \ldots , a_{ik_i}):\SUPER(a_{i1}, \ldots , a_{ik_i});$.

Decrypting the LaTeX and considering the same example, what we get is _owm(): super(), where _owm is the actual (generated) name for the class that I previously called Object with Mixin.
There is a problem here: The implicitly declared constructor is non-const, even in the case where its superinitializer invokes a const constructor (in which case the implicitly generated constructor could itself also have been const).
So, unfortunately, there is no way to obtain a complete chain of const constructors up to Object when some (direct or indirect) superclass is created by mixin application.
This is a known problem, and the overly simple implicit generation of constructors creates some other problems as well (see #9745, #15101). The problem has been known for a long time, and it hasn't had enough urgency to be fixed so far (and the fix isn't necessarily trivial), but it is certainly on the agenda at this point and this issue helps pushing it upwards.
I'll close this issue as a duplicate of #9745, and refer to this issue from there.

You're looking for #32223, which is a request for implementation of this feature (this is area-language). You might say that we should have had a meta-bug for keeping track of these connections, but that didn't happen because the original request is so old.

The current specification for Dart 2 says that a mixin application of a mixin derived from a class with no field declarations, on top of a class with a const constructor, should make the forwarding constructor const.
That might not be implemented yet, but it should be eventually.

might not be implemented yet ..

Right, but it is requested in #32223, so that's the place to check out the current implementation status (and also to advocate for getting it done, if the current priority assigned to this task appears to be too low).


[Feature] Make ionic 2 PWA seo-friendly

Ionic version:  (check one with "x")
[ ] 1.x
[ x] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[ x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Currently, when navigating through the app pages the URL stays the same, and it's impossible for search engines to index specific page / route.
Expected behavior:
Just like Angular 2, when a route is assigned, the page URL is changing and it's possible to redirect user to specific page in the application. The Ionic Deep Links plugin has no effect for in-browser urls and it's impossible to share a link to an user profile page (such as mysite.com/user/theunreal), for example.
Steps to reproduce:
Irrelevant
Related code:
Irrelevant
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
C ordova CLI: 6.5.0
Ionic Framework Version: 2.3.0
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.2.2
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.2
Xcode version: Not installed

Hello, thanks for opening an issue with us. You can use our Deeplinker to get URL's for PWA's.

Hey @jgw96, Thanks for the great reference! Any idea why a number sign appears in the URL?
Example: http://localhost:8100/#/my-page

@jgw96 thanks, link is no longer working, right now it is here: https://ionicframework.com/docs/2.2.0/api/navigation/DeepLinker

I think IonicPage ([see here] (https://ionicframework.com/docs/api/navigation/IonicPage/)) makes the PWA SEO-friendly. To confirm !

First of all, sorry for my poor English.
After searching through Deep Web (joking), I found the solution. And the coolest solution was that I was able to integrate my Pioneer Ionic application with Firebase Hosting using Cloud Functions.
After reading the following topic:
https://github.com/firebase/firebase-tools/issues/33
The @TheRoccoB user explains how to host the static Web application in Firebase Hosting and redirect traffic from a URL to Cloud Functions.
What I did was map the routes that I have to index as:
{
        "source": "/ shop / **",
        "function": "ssr"
      },
      {
        "source": "/ * / promotions / **",
        "function": "ssr"
      }
Since "ssr" is the name of my function in Cloud Functions. So I used the library https://github.com/prerender/prerender-node to check if the request is from a google crowler, in case I redirect the request to a https://github.com/prerender/prerender server.
const prerender = express ();
prerender.use (cors);
prerender.use (
    require ('prerender-node')
    // .set ('prerenderServiceUrl', 'http: // localhost: 3000')
    .set ('prerenderToken', '** TOKEN **')
);
prerender.use (require ('prerender-node'). set ('beforeRender', function (req, done) {
    // do you need to do?
    console.log ('Rendering URL:', req.path);
done ();
}));
prerender.use (require ('prerender-node') set ('afterRender', function (err, req, prerender_res) {
    // do you need to do?
    console.log (req.path + 'rendering completed!');
    console.log ('Errors:', err);
}));
prerender.get ('*', (req, res) => {
    console.log ('Calling function for URL:', req.path);
    res.set ('Cache-Control', 'public, max-age = 300, s-maxage = 600');
    res.status (200) .send (fs.readFileSync ('./ www / index.html'). toString ());
});
exports.ssr = functions.https.onRequest (prerender);


fix: get_devices only checks for the first type

When testing this in Homeassistant with an XT2 Plus, i noticed, that the get_devices() function checks the type by checking if the type is found in the parameter generic_type. But for this to work and check for the type ids used in XT2 etc, we need to fix this to not only check for the first entry in the passed list.
Otherwise Homeassistant throws the following error:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 304, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/lupusec/switch.py", line 33, in setup_platform
    for device in data.lupusec.get_devices(generic_type=CONST.TYPE_SWITCH):
  File "/usr/local/lib/python3.10/site-packages/lupupy/__init__.py", line 315, in get_devices
    if device.type is not None and device.type in generic_type[0]:
TypeError: 'in <string>' requires string as left operand, not int

When this is merged, we also need to update the homeassistant integration part, since there are parts where the parameter is passed in a wrong / inconsistent way.
Thank you for your work!

This fixes the error indeed!
This PR should be merged.

In the meantime, I have created a PR in home-assistant to account for this bug:
https://github.com/home-assistant/core/pull/103583
Once the bug is fixed, the changes need to be reverted.


Shared build of mfem on Windows

Is mfem interested in being able to build as a shared library (i.e. a dll) on Windows/msvc?
The axom project has been working on automating its Windows build, which requires building its third-party libraries, including mfem, in shared mode.
Details:
One of the main differences between gcc/clang and msvc in their treatment of shared libraries has to do with how symbols are exported.  gcc/clang export all symbols by default, while msvc exports none of the symbols by default.
The CMake flag -- WINDOWS_EXPORT_ALL_SYMBOLS -- gets you most of the way there, but it does not export symbols for global variables, e.g. extern variables or static const class members.
I think this flag is available in<EMAIL_ADDRESS>I've developed a partial solution for this in https://github.com/LLNL/axom/pull/213 in the form of a patch to get<EMAIL_ADDRESS>to link to axom (see https://github.com/LLNL/axom/blob/aaac337f2e6d3168d550c92094d633fc9864cb9b/scripts/uberenv/vcpkg_ports/mfem/export-extern-vars.patch ).  This solution requires very few changes to mfem. I think this only covers the symbols that are currently used by axom, and I haven't tried building mfem's examples or tests, so there is likely more work to be done.
My understanding is that shared mode is also required for Python support, so this might have relevance to a Windows build of https://github.com/mfem/PyMFEM, or it might already be a solved issue (?)

I believe @acfisher and maybe @v-dobrev have some experience with this.

I've never tried this -- configuring cmake with -DBUILD_SHARED_LIBS=ON on windows with msvc. Also, I don't remember any issues on github about that.
@kennyweiss, if you want we can make a PR with the changes you have in the patch and do some testing. Maybe we can setup an appveyor test for a shared build?

I haven't tried it with msvc, but I've built DLLs on intel/windows using both cmake and a hand rolled nmake file.  I had to do some contortions to get the nmake solution to work.  It's probably worth having a look at your changes to see if we can generalize it and test it like @v-dobrev  suggested.

Thanks @v-dobrev  and @acfisher.
I created #1401 which builds and links the exec target and passes all tests locally.  I was able to build and test locally on linux, but ran into an issue with the travis job related to the new auto-generated file mfem_export.h

@kennyweiss, do you want us to merge #1401? If so, can you mark it with the ready-for-review label?

@tzanio -- I ran into a problem testing this on windows through azure in early April, and unfortunately haven't had a chance to get back to it.
It worked with the current azure script in mfem@master (using static builds on Windows), but had errors when I tried to add a shared library build to the CI.  Maybe I was doing something wrong in the CI script?
https://github.com/mfem/mfem/pull/1401/files#diff-11c909939117928998b102a1fff7d363R40-R55
The shared windows build worked for me on my local system.
Perhaps someone else with a windows machine can try to build this?

@acfisher, can you give ☝ a try by any chance on your Windows machine?

ping: @acfisher

Yeah, I'll give it a spin.


Reference index - rebase of #9170

#9170 rebased with additional fixes:

Objects listed in the usage report now have their titles hidden if the user doesn't have edit access for them
The title text on those links now correctly reflects the content type, rather than always being "Edit this page"
Indexing base models such as Page (in rebuild_references_index and elsewhere) no longer wrongly removes references belonging to child models
Document links in rich text are now picked up (the document link handler was missing extract_references)
Usage link on the snippet edit page (previously unstyled in the form body) is now moved to the status side panel

Merged in 4c7e1ea1ce4c842ce30905c6539437fdf21be6df