initial README

Something easy to get me started on this 😉
Fixes #19
@chuckha I made some assumptions for Versioning, Maintenance, and Compatibility; if it is too early for making decisions about this, I can remove this paragraph
/assign @chuckha
/cc @amy

/assign @chuckha

/retest

@chuckha comments addressed

I remove Useful Link section and also code of conducts (I noticed there is a separated file for this)

thank you @fabriziopandini !! Welcome aboard :)


Minimal improvements

This PR

lets repository links open the actual subfolder of the package on GitHub
fixes the changelog's style of the last sidekick release
adds empty new lines at the end of some changelogs/pubspec.yamls
updated changelogs and versions for sidekick and sidekick_plugin_installer (some changes on main haven't been published yet, maybe after merging this PR? 🙂)

Thanks: Will release the updates over time


SSL configuration is Running - [BRIEF DESCRIPTION]

App Id: d38xjv1kjalne7
Region: ap-southeast-1
Step: SSL configuration
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Our records indicate that this domain is available c********.z********.com


Unable to get logging output from OneLogin:RubySaml::Logger

Hi there.  I've tried to follow the instructions to get logging output to a custom file from the readme.  I've tried placing the following:
OneLogin::RubySaml::Logging.logger = Logger.new(File.open('/var/log/ruby-saml.log', 'w'))

... in a rails initializer, or in  my rails environments file, or in the SAML application controller, but nothing seems to work.
I see the file getting created, but nothing is ever logged to it.  I currently have SAML logins using the gem working and I see log entries go to standard out, but am just unable to use this custom logging setting to divert saml logs to a file.
Any help is appreciated.
(btw using 1.6 of the gem under rails5 with ruby 2.4.0)

I got the same situation.
I changed intializer like a following line, and it may be solved this problem.
OneLogin::RubySaml::Logging.logger = Logger.new('/var/log/ruby-saml.log')

(This would not be the problem from this gem, but from the usage of Ruby default logger.
ref: https://ruby-doc.org/stdlib-2.4.0/libdoc/logger/rdoc/Logger.html#class-Logger-label-How+to+create+a+logger)


Contributors heading is included in search results

As you can see below, the "Contributors" heading is included in the search results. This is not a huge problem, but can be confusing when it's the first result, such as in this case:

@dzello, is this something that can be easily fixed in our Algolia config?

Yes! I've fixed it by adding an entry to selectors_exclude in webpack's DocSearch config. I also updated the start_urls property to reflect the recent navigation changes. The config has been deployed and the live search reflects the changes.

Thanks for the quick fix!!


Fix bug# 14546 - Make the druntime documentation buildable again.

This makes it so that ClockType isn't actually used in core.time in the
documentation build (since if it is, it triggers static assertions,
since none of the systems support all of the ClockTypes, but they all
have to be defined for the documentation build in order to show up in
the docs).

Thanks.

Auto-merge toggled on


[desktop] Make Seeding settings apply also for finished HTTP downloads.

Now that we have easy one-click sharing on both Transfers and Library, and one click seeding for finished HTTP downloads on Transfers, we can auto seed these downloads if the user has seeding turned on.

Finally!


ViewStates and process kill

Hi, is it possible to restore view states afrer process kill. For example, after working with activity user turn it and come back after hour. There is big chance that Android kill process. How to restore that view states?

Hi, Moxy doesn't solve this problem =( But you can tell for your Presenter that activity go to save/restore instance state and Presenter is able to restore self state. But then you should restore your Interactor's state, at the same time it's not Presentation layer's responsibility.
In my mind, you should restore state of your Interactor by any persistant storage, firstly. And then restore state of Presenter by the Interactor rules.

Clear, thanks


Rewrite WPE (Widget Parser Engine)

❓Current situation
💡Solution
🗺 Roadmap

Update: 07/01/2023

Create new repo for rewriting WPE


Some tweaks on #2579 to more closely match the getambassador.io site

Description
Some tweaks on #2579 to have the Getting Started/Quick Start page more closely match the getambassador.io site.
Related Issues
#2579
Testing
Manual tests looking at page locally on Macintosh with gatsby develop
Tasks That Must Be Done

[ ] Did you update CHANGELOG.md?
[ ] Did you add or update tests?
[ ] Did you update documentation?
[ ] Were there any special dev tricks you had to use to work on this code efficiently?

[ ] Did you add them to DEVELOPING.md?

Here's a snippet from the "other install options" page:


[Bug]: Can't open Mainland China's Honkai Impact 3rd Page

Affected Version
1.70.15
Bug Behavior
Open Honkai Impact 3rd Mainland China page, and here is the error
Hi3Helper.Http.HttpHelperUnhandledError: HttpResponse for URL: "https://sdk-static.mihoyo.com/bh3_cn/mdk/launcher/api/content?key=SyvuPnqL&filter_adv=false&language=zh-cn&launcher_id=4" has returned unsuccessful code: NotFound
at Hi3Helper.Http.Http.GetSessionStream(HttpResponseMessage response)
at Hi3Helper.Http.Http.GetSessionAsStreamAsync(String URL, Nullable1 OffsetStart, Nullable1 OffsetEnd, CancellationToken Token)
at Hi3Helper.Http.Http.DownloadFromSessionStreamAsync(String URL, Nullable1 OffsetStart, Nullable1 OffsetEnd, CancellationToken ThreadToken)
at CollapseLauncher.MainPage.TryGetSingleLangResourceProp(CancellationToken Token, PresetConfigV2 Preset)
at CollapseLauncher.MainPage.FetchLauncherLocalizedResources(CancellationToken Token, PresetConfigV2 Preset)
at CollapseLauncher.MainPage.TryLoadResourceInfo(ResourceLoadingType resourceType, PresetConfigV2 preset)
Expected Behavior
The page can be opened
Steps to reproduce
Choose  Honkai Impact 3rd Mainland China
Related Issues
No response
Screenshot(s)
No response
Additional Information
This appears to be a server error rather than my network error. Also, is it a better option to have the page display when fetching server resources fails?

Thank you for sending the issue, seems like the launcher resource page has changed for CN release. Will investigate and send update as soon as fix is available

Same problem, and it makes it impossible to switch to another game's startup page

If you can't use Collapse for other games because of this change, you can edit the config.ini file in C:\Users\%USERNAME%\AppData\LocalLow\CollapseLauncher
Edit the Game Region string to Global

Issue Identified
Launcher resource URI changed, working on Collapse Metadata update

Metadata Update Pushed
Please restart Collapse and let it do metadata update. If the error persists, try restarting Collapse once again.
If there is problem regarding HI3 6.9 update for Collapse, feel free to chime in here.

HI Bagusnl,
Thanks for the quick fix regarding official resources change.
But for Collapse public preview I am using, it still shows Paimon failed after I restarted Collapse a few times.
From log I can see there is no metadata update:
[Schm]  Running Collapse Launcher [1.71.6], [Preview], under Windows 11 (build: 22621.0), as
[Schm]  Runtime: .NET 7.0.9 - WindowsAppSDK 1.3
[Schm]  Locale file: en-us.json loaded as English by neon-nyan, CryoTechnic
[Schm]  Locale file: es-419.json loaded as Español (LATAM) by BloodDragooner, d-l-n, IhoFox
[Schm]  Locale file: id-id.json loaded as Bahasa Indonesia by neon-nyan, bagusnl
[Schm]  Locale file: ja-jp.json loaded as 日本語 by Vermilion-Shinsha
[Schm]  Locale file: ko-kr.json loaded as 한국어 by despenser08
[Schm]  Locale file: pt-pt.json loaded as Português (Portugal) by gablm
[Schm]  Locale file: ru-RU.json loaded as Русский by ChocolateNao
[Schm]  Locale file: vi-vn.json loaded as Tiếng Việt by kleqing
[Schm]  Locale file: zh-cn.json loaded as 简体中文 by misaka10843, imgradeone, SatoSouta
[Schm]  Locale file: zh-TW.json loaded as 繁體中文 by Seria Ati
[Info]  Welcome to Collapse Launcher v1.71.6 - Windows 11 (build: 22621.0)
[Info]  Getting CDN Content from: Cloudflare at URL: https://r2.bagelnl.my.id/cl-cdn/notification_preview.json
[Info]  Getting CDN Content from: Cloudflare at URL: https://r2.bagelnl.my.id/cl-cdn/squirrel/preview/RELEASES?arch=x64&os=windows&id=Collapse&localVersion=1.71.6
[Info]  Cur. Session Region Hash: -1280661324<PHONE_NUMBER> - Honkai Impact 3rd - Southeast Asia)
[Info]  Cur. Session Region Hash: -1860019383<PHONE_NUMBER> - Honkai Impact 3rd - Global)
[Info]  Cur. Session Region Hash: -291162813<PHONE_NUMBER> - Honkai Impact 3rd - Mainland China)
[Info]  Cur. Session Region Hash: 944405822<PHONE_NUMBER> - Honkai Impact 3rd - TW/HK/MO)
[Info]  Cur. Session Region Hash: -1488390735<PHONE_NUMBER> - Honkai Impact 3rd - Korea)
[Info]  Cur. Session Region Hash: -551936613<PHONE_NUMBER> - Honkai Impact 3rd - Japan)
[Info]  Cur. Session Region Hash: -585101950<PHONE_NUMBER> - Genshin Impact - Global)
[Info]  Cur. Session Region Hash:<PHONE_NUMBER><PHONE_NUMBER> - Genshin Impact - Mainland China)
[Info]  Cur. Session Region Hash: 66146565<PHONE_NUMBER> - Honkai: Star Rail - Global)
[Info]  Cur. Session Region Hash: -1801903224<PHONE_NUMBER> - Honkai: Star Rail - Mainland China)
[Schm]  Initializing Honkai Impact 3rd - Mainland China...
[Warn]  Loading Game: Honkai Impact 3rd - Mainland China has timed-out (> 15 seconds). Retrying...
[Warn]  Loading Game: Honkai Impact 3rd - Mainland China has timed-out (> 20 seconds). Retrying...
[Warn]  Loading Game: Honkai Impact 3rd - Mainland China has timed-out (> 25 seconds). Retrying...
[Warn]  Loading Game: Honkai Impact 3rd - Mainland China has timed-out (> 30 seconds). Retrying...
[Warn]  Loading Game: Honkai Impact 3rd - Mainland China has timed-out (> 35 seconds). Retrying...
[Info]  Getting CDN Content from: Cloudflare at URL: https://r2.bagelnl.my.id/cl-cdn/preview/fileindex.json
[Info]  Getting CDN Content from: Cloudflare at URL: https://r2.bagelnl.my.id/cl-cdn/metadata/metadatav2_previewstamp.json
```
Please share with us if there is a force way to refresh the latest metadata, thanks.

@sino1641 Seems like currently Collapse wants to load the Region first before trying to update metadata, we will look on this soon. But to mitigate your current issue you can edit Collapse's config.ini in C:\Users\%USERNAME%\AppData\LocalLow\CollapseLauncher
Change its GameRegion and/or GameCategory to anything other than Maindland China // Honkai Impact 3rd then relaunch Collapse. Collapse will soon then reload to another region and tries to download the latest metadata.
You can also download the metadata here https://r2-render.bagelnl.my.id/cl-cdn/metadata/metadatav2_previewconfig.json and overwrite the metadata.json file inside your Collapse Data folder with everything inside the new file
We are sorry for the inconvenience this have caused


ArgumentError for OpenID with OmniAuth 1.0.0.rc2

Rails message
Received wrong number of arguments. [#<OpenID::Store::Filesystem:0x000000040b98d0 @nonce_dir=#<Pathname:/tmp/nonces>, @association_dir=#<Pathname:/tmp/associations>, @temp_dir=#<Pathname:/tmp/temp>>]
I use 1.0.0.rc2 OmniAuth with middleware init in development.rb
  Rails.application.config.middleware.use OmniAuth::Builder do
    provider :openid, OpenID::Store::Filesystem.new('/tmp'), :name => 'openid'
    provider :openid, OpenID::Store::Filesystem.new('/tmp'), :name => 'google', :identifier => 'https://www.google.com/accounts/o8/id'
  end

This dump maybe helpful
/home/tamias/.rvm/gems/ruby-1.9.2-p180/bundler/gems/omniauth-bfc873792c89/lib/omniauth/strategy.rb:136:in `initialize' rack (1.3.5) lib/rack/builder.rb:78:in `new' rack (1.3.5) lib/rack/builder.rb:78:in `block in use' rack (1.3.5) lib/rack/builder.rb:130:in `call' rack (1.3.5) lib/rack/builder.rb:130:in `block in to_app' rack (1.3.5) lib/rack/builder.rb:130:in `each' rack (1.3.5) lib/rack/builder.rb:130:in `inject' rack (1.3.5) lib/rack/builder.rb:130:in `to_app' /home/tamias/.rvm/gems/ruby-1.9.2-p180/bundler/gems/omniauth-bfc873792c89/lib/omniauth/builder.rb:30:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.3.5) lib/rack/etag.rb:23:in `call' rack (1.3.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/flash.rb:243:in `call' rack (1.3.5) lib/rack/session/abstract/id.rb:195:in `context' rack (1.3.5) lib/rack/session/abstract/id.rb:190:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/cookies.rb:331:in `call' activerecord (3.1.1) lib/active_record/query_cache.rb:62:in `call' activerecord (3.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:477:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' activesupport (3.1.1) lib/active_support/callbacks.rb:392:in `_run_call_callbacks' activesupport (3.1.1) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.1.1) lib/action_dispatch/middleware/callbacks.rb:28:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/reloader.rb:68:in `call' rack (1.3.5) lib/rack/sendfile.rb:101:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/remote_ip.rb:48:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/show_exceptions.rb:47:in `call' railties (3.1.1) lib/rails/rack/logger.rb:13:in `call' rack (1.3.5) lib/rack/methodoverride.rb:24:in `call' rack (1.3.5) lib/rack/runtime.rb:17:in `call' activesupport (3.1.1) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.3.5) lib/rack/lock.rb:15:in `call' actionpack (3.1.1) lib/action_dispatch/middleware/static.rb:53:in `call' railties (3.1.1) lib/rails/engine.rb:456:in `call' railties (3.1.1) lib/rails/rack/content_length.rb:16:in `call' railties (3.1.1) lib/rails/rack/log_tailer.rb:14:in `call' rack (1.3.5) lib/rack/handler/webrick.rb:59:in `service' /home/tamias/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service' /home/tamias/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run' /home/tamias/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread'

OpenID is 100% options driven in 1.0, try:
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :openid, :store => OpenID::Store::Filesystem.new('/tmp'), :name => 'openid'
  provider :openid, :store => OpenID::Store::Filesystem.new('/tmp'), :name => 'google', :identifier => 'https://www.google.com/accounts/o8/id'
end

Also, this is on the wrong repo! Any OmniAuth::OpenID issues should be reported on the omniauth-openid repo! :)

Thanks for great software. Your solution  with :store => OpenID::Store::Filesystem.new('/tmp') works fine.


Big Tent ideology

There will be new ideology added to the game - being mutually exclusive with conservatives - Big Tent to house "Big Tent" political parties, that has a diverse ideological framework, allowing for "Blue-Red states" america, as the Republican will be a Big Tent party - properly colored red.

United Russia is also a big tent.


Organization URL must end in zulip.com

I have a user on Android Pixel 2 who installed the most recent version of Zulip mobile.  He reports that he cannot enter the organization url we use because the field is pre-populated with ".zulip.com" and he cannot edit that portion of the field.  Another user also reports this problem, though I don't know what platform she is on.
Is there another way to specify the URL?  Or is this a UI bug?
Thanks!

Hey @jvasile
We do support arbitrary URLs (non zulip.com/zulipchat.com)
We used to have this issue a few versions ago. Ask the user to check if they have the latest version (16.2.96) and if not to update.
Once updated, ask the user to just write the whole URL, once they type a dot we will not auto-add the domain.

I am curious to know what happened. It would be great if they were on an older version.
If the input was just confusing, we need to address that.

The version is indeed 16.2.96 and it isn't actually buggy.  We got it to work after mass confusion.  It wasn't until the fifth person tried to enter it that we figured it out.
The confusion was that the field is pre-populated, and you can't edit the end of it.  You also can't paste into it.  If you type the URL, when you get to the 'dot', it will remove the 'zulip.com' part of the field, but all of us stopped typing before we got there.  We mistakenly expected different behavior in such fields, which is that when you start typing, the original default text goes away.
File this one under 'user error' but also under 'confusing ui'.
Thanks!

I guess that this issue can be closed then. @gnprice

Closing based on discussion above.


missing dependencies and compilation failed

after adding the the restyGwt maven dependency to my maven project gwt starts to failed to compile with the following errors :
--- gwt-maven-plugin:1.0-rc-6:compile (default-compile) @ depends-sample-client ---
[INFO] Compiling module com.test.sample.AppClientModule
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveByteArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveByteArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 47: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 52: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.MapJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/MapJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 80: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 75: Nullable cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.VoidJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/VoidJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 56: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveLongArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveLongArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.UUIDKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/UUIDKeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 50: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.ToStringKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/ToStringKeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 42: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.NumberKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/NumberKeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 48: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.BooleanKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/BooleanKeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 48: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.StringJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/StringJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.BaseNumberJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/BaseNumberJsonSerializer.java'
[INFO]          [ERROR] Line 99: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 121: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 126: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 223: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 198: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 53: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 251: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 75: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 245: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 193: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 171: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 149: Nullable cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.IterableJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/IterableJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 65: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 60: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveIntegerArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveIntegerArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.UUIDJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/UUIDJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 46: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveBooleanArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveBooleanArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveCharacterArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveCharacterArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.KeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/KeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 65: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveCharacterArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveCharacterArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveByteArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveByteArrayJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 47: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 52: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.RawValueJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/RawValueJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 46: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.BaseDateJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/BaseDateJsonSerializer.java'
[INFO]          [ERROR] Line 134: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 111: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 150: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 24: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 88: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 23: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 57: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveFloatArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveFloatArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.CharacterJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/CharacterJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 53: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 48: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.Array2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/Array2dJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 59: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 64: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.JavaScriptObjectJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/JavaScriptObjectJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 46: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveShortArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveShortArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveShortArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveShortArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.EnumJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/EnumJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 46: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.bean.AbstractBeanJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/bean/AbstractBeanJsonSerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 97: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.JsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/JsonSerializer.java'
[INFO]          [ERROR] Line 128: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 121: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 140: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.ArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/ArrayJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 59: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 64: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveBooleanArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveBooleanArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveLongArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveLongArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveDoubleArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveDoubleArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.DateKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/DateKeySerializer.java'
[INFO]          [ERROR] Line 49: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.BooleanJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/BooleanJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveIntegerArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveIntegerArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.PrimitiveDoubleArrayJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/PrimitiveDoubleArrayJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.CollectionJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/CollectionJsonSerializer.java'
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 65: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 60: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.ObjectKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/ObjectKeySerializer.java'
[INFO]          [ERROR] Line 43: Nonnull cannot be resolved to a type
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.array.dd.PrimitiveFloatArray2dJsonSerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/array/dd/PrimitiveFloatArray2dJsonSerializer.java'
[INFO]          [ERROR] Line 46: Nullable cannot be resolved to a type
[INFO]          [ERROR] Line 20: The import javax.annotation.Nullable cannot be resolved
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 51: Nonnull cannot be resolved to a type
[INFO]    Tracing compile failure path for type 'com.github.nmorel.gwtjackson.client.ser.map.key.EnumKeySerializer'
[INFO]       [ERROR] Errors in 'jar:file:/home/u343/.m2/repository/com/github/nmorel/gwtjackson/gwt-jackson/0.13.0/gwt-jackson-0.13.0.jar!/com/github/nmorel/gwtjackson/client/ser/map/key/EnumKeySerializer.java'
[INFO]          [ERROR] Line 19: The import javax.annotation.Nonnull cannot be resolved
[INFO]          [ERROR] Line 48: Nonnull cannot be resolved to a type
[INFO]    [ERROR] Aborting compile due to errors in some input files

i have been trying to add the messing dependencies with no luck.

Dupe of #324

Thanks,
i have found that issue and made the workaround, but will this remain as the solution, or it is a workaround until a fix is applied?


Update games.json

Added Tom Clancy’s Rainbow Six® Extraction

Please stick to the existing Anti-Cheat names (keep the AC as simply Denuvo)

Thx for the help 😎

Thx for the help 😎

Thanks for the Pull Request ^^


I dont have the file but its saying i do

I am having the same problem with version 1.2.1 on W10 Pro 22H2

Have you tried looking for it in the uninstall menu of the windows settings to see if you haven't had an instance of it before?

Yes, I had not installed any version of this software before trying 1.2.1. I ended up installing 1.2.0 with no issue


spirv-opt: Add pass to remove unused input attributes, shorten input attribute arrays

It feels like the RemoveUnusedInterfaceVariablesPass may be a little aggressive given that it doesn't look at multiple stages to determine if it can remove an input/output. I assume that's why GLSLang doesn't use it as part of it's optimization pass.
However it seems like it would be safe to add a pass that removes:

Unused vertex input attributes.
Reduce the size of input attribute arrays to the size of the highest element used.

This at least would free up input attribute resource usage. Any chance in this getting added, or is it already in another pass that GLSLang isn't yet using?
Thanks

--eliminate-dead-code-aggressive will remove totally unused inputs for all stages.
I will also add a new optimization --eliminate-unused-input-components to eliminate unused components of input variables for all stages. This first implementation will just remove trailing unused components from input arrays.


Try to add KVM support on mainline kernels

Unfortunately, there is not KVM support on armhf platform yet (https://github.com/torvalds/linux/search?utf8=✓&q=HAVE_KVM).
I suggest to use qemu / lxc

But the new servers do. KVM support would be great!

@Sveeeeeen, I released new bootscripts earlier this week with KVM support
You can switch to a newer bootscript to get new features.
If you still miss some modules, just ping me here :)


Add Note Field to Affiliation Transfer Tool

Add "Note" Field to Affiliation Transfer Tool

This has been released


score best match rather than first match; other odds and ends

Rather than score the first match of the abbreviation, this implementation evaluates all matches and picks the one with the highest score. I will be the first to admit that it is not efficient in how it currently does so, though neither is it totally braindead.
Performance in ops/sec drop an order of magnitude. This is still 10,000s of ops/sec, but obviously a big hit. If you would rather wait for a more efficient implementation to merge, let me know. I know what next steps to take, but might not come back to this really soon.
Thanks again for releasing this project.

Nice. I'm glad you took the initiative to tackle this. I'll take a closer look as soon as I can.
The performance degradation does concern me a bit. A solution with recursion concerns me the most, but I need to inspect deeper. I wrote liquidmetal because all the other solutions were terribly slow -- and they were all written using recursion.  When long strings are used, libraries that used recursion would send browsers spinning.  Performance was one of the main design goals for liquid metal. For example, see test/benchmark_vs_quicksilver.html.  It looks like this pull request is still pretty fast though. Liquidmetal (first-match) completes that test in 0ms on my laptop, but the quicksilver library takes upwards of 2000ms. Your changes bump that test up to 2ms -- nearly infinite performance degradation. :wink:

You might be surprised to hear that the iterative version of the best match scoring procedure actually performs slightly worse than the recursive one. My hunch is that the js call stack actually outperforms explicit array pops and pushes needed to maintain the stack in the iterative version. I haven't done any formal profiling though.
I'm going to experiment more and see about optimizing the recursive version too. It may be the slowdown is simply the price to pay for best matches. I'll push any further commits to this pull request.

@shelhamer Interesting.  Thanks for your efforts on this.  I'm going to merge these changes in. I won't publish an official release just yet.  If you have the time, continuing to work on the performance would be a huge help.


[BEAM-3851] Option to preserve element timestamp while publishing to Kafka.

KafkaIO sink support for setting Kafka message timestamps based on element timestamp. Otherwise there is no way for user to influence the timestamp of the messages in Kafka sink.
The implementation for for normal sink (KafkaWriter.java) is trivial: Just need to read the timestamp from the context. But EOS sink (KafkaExactlyOnceWriter.java) changes are a bit more involved.
In the case of the latter, the elements go through couple of shuffles and we need to include timestamp along with the the actual value. The implementation wraps timestamp and input KVs in TimestampedValue<>. This changes serialization of the elements shuffles. As a result EOS changes are not backward compatible (with upgrade or while using save points). I think the use of EOS sink is pretty minimal and this will have very little impact. I am not sure what the best practice is for handling such incompatibility in Beam. Ideally we want to error out early if a pipeline with exactly-once sink is being updated from version 2.3 to 2.4. PLMK. I can move timestamp support in EOS to Beam 3.0.

R: @XuMingmin
cc: @aljoscha, @chamikaramj

I would suggest to make the change together, but I would prefer to a TimestampFn instead of ctx.timestamp(), --I find ctx.timestamp() of earlyFiring/lateFiring/ontimeFiring is quite complex and is not what I want sometime.

Added .withPublishTimestampFunction() (this is lambda friendly). Also retained withInputTimestamp() which makes it simpler for users to use element timestamp.

retest this please

run java precommit

Seems the failure is not related with this change, @rangadi can you help to double check?

@XuMingmin, yep, they seem unrelated.


Feature/setup cloud9

Ticket
N/A
Purpose
Add Cloud9 setup script and README
Summary of changes
Add setup directory
Testing notes
Create a Cloud9 account and follow the README instructions

Coverage remained the same at 14.074% when pulling 04d146a643494803ca2d2591ef21a66843f463ed on binoculars:feature/setup-cloud9 into e16575a7195eaf21f0f1a5fffae5a87636c6d386 on abought:develop.

Coverage remained the same at 14.074% when pulling c18eb7992fe1bd9ca51a7b9e764ea5f505ae80d3 on binoculars:feature/setup-cloud9 into e16575a7195eaf21f0f1a5fffae5a87636c6d386 on abought:develop.


Update dependency on cardano-ledger-specs

The serialisation of the Shelley ledger was changed in
https://github.com/input-output-hk/cardano-ledger-specs/pull/1816, hence the
updates to the golden tests.

Draft because https://github.com/input-output-hk/cardano-ledger-specs/pull/1848 still needs to be merged.

bors merge


Slow performance

This plugin is super great but it is also super slow as every save causes a new Maven process to be launched, spotless to be run, invoking formatters and in the end the file is updated. Compared to the built in IntellIj formatter, the experience is totally different.
Do you have any ideas on how to improve the performance significantly? Keep something running in the background or similar?

Greetings @Artur- !
The thing is, Spotless is a tool that allows you to use different formatters with their own configurations. That’s why there’s no way to call the Spotless apply function apart from a Gradle/Maven task. And yes, it’s not as fast as native IntelliJ tasks, especially for Maven.
The way to significantly improve performance is to integrate Spotless natively, which is a huge amount of work because it's essentially like integrating a new build system - https://github.com/diffplug/spotless?tab=readme-ov-file#other-build-systems


3 members circular dependency issue

I want to make an object graph with classes A, B and C.
A has a strong ref to B, B has a strong ref to C and C has a weak ref to A
I'm trying to make my assembly like this:
public func assemble(container: Container) {
    container.register(A.self) { _ in
        let b = container.resolve(B.self)!
        return A(b: b)
    }
    .inObjectScope(.weak)

    container.register(B.self) { _ in
        let c = container.resolve(C.self)!
        return B(c: c)
    }
    .inObjectScope(.weak)

    container.register(C.self) { _ in
        return C()
    }
    .initCompleted { r, c in
        let a = r.resolve(A.self)!
        c.a = a
    }
    .inObjectScope(.weak)
}

When I resolve A, the object graph is properly created BUT the weak ref from the C instance to the A instance is nil.
I understand that since I'm using the weak scope, the A instance resolved in initCompleted is immediately lost since the first call to resolve A hasn't returned yet (At least that's my guess, am I right or could this actually be a bug?).
How could I make this work? (Preferably without using optional types)

I ended up doing it like this:
public func assemble(container: Container) {
    container.register(A.self) { _ in
        let b = container.resolve(B.self)!
        return A(b: b)
    }
    .initCompleted { r, a in
        let c = r.resolve(C.self)!
        c.a = a
    }
    .inObjectScope(.weak)

    container.register(B.self) { _ in
        let c = container.resolve(C.self)!
        return B(c: c)
    }
    .inObjectScope(.weak)

    container.register(C.self) { _ in
        return C()
    }
    .inObjectScope(.weak)
}

Any comment?

Hello @alexisbronchart,
This looks like a bug indeed - as you mentioned, instance of A assigned to the C is immediately discarded, as no strong references exist to it.
I guess the expected behaviour would be such that even .weak object scope instances do not discard during graph resolution.
Any help fixing this would be welcome 😉


2022.1 holding site updates.

Put information around intended event with link to Sessionize. Have left a placeholder for the actual Mailchimp form to be dropped in. Removed old 2020 information.

Incorrect push to master - need to fix first and resubmit.


Fix: update zwijndrecht name

ID
CLBV-930
Description
Update the zwijndrecht name from Zwijndrecht-edit to Zwijndrecht.
How to test
Go to mock-login and verify zwijndrecht now has the right name.

I think that the person and the bestuurseenheid can be in different graphs, enforcing them to be in the same one doesn't delete everything, see:
select * where { graph ?g { ?s ?p "Zwijndrecht-edit" }}

Also a note on syncs, I noticed that the wrong triple was is OP's landing zone. I then checked and found this weird name in OP QA. Might be worth updating it there (via the frontend)!

I don't have OP access on QA, only dev where it's fine. But note that the 'Zwijndrecht-edit' is in both verenigingen-loket QA and DEV

After double checking, it can't be changed via the frontend in OP, they have double labels in the backend in seems. Probably an error at some point. Anyways, that's a problem for an other app ;)

So should I close this PR or keep it?

Keep it, especially if you have that issue on multiple environment (for op it's only QA), but I still think you need to separate the graphs to remove everything!


Redo Option Deployment Type

The Redo Job functionality is very useful and works as expected, except that "Testing/Development" is the default Deployment Type even if the original job was run on "Production"

Can you test this please ? I've tested from my side and it seems to be working.

Confirmed to be working.


fix: toCalendar should use Calendar.MONTH instead MONDAY

Proposed changes
Issue Number: close #xxx

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

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.66 seconds
stream load tsv:          503 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.6 seconds inserted 10000000 Rows, about 349K ops/s
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230710134056_clickbench_pr_175718.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.79 seconds
stream load tsv:          446 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          25.9 seconds inserted 10000000 Rows, about 386K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230710072912_clickbench_pr_175715.html


I try running the program and get:

The program '[2548] RecursiveDelete.exe' has exited with code 1 (0x1).

I did not mean to close it previously.

Can you be more specific about what you are trying to do?
Obviously, you would be better off if RecursiveDelete did report why it failed, wouldn’t you?


Naming conflict with components

Hello,
An issue I have experience using this lib is naming conflicts between my project components and styled-icons. Example
import { Home } from 'styled-icons/material';
I already have a component called Home. It would be nice with styled-icons had unique names. To solve this I currently do import { Home as SiHome } from 'styled-icons/material'; not the best naming convention but it gets the job done. One strategy I have seen font-awesome use is
import FontAwesomeIcon from '@fortawesome/react-fontawesome';
import { faHome } from '@fortawesome/fontawesome-free-solid';

<FontAwesomeIcon icon={faHome} />

This ensures that there will almost never be a naming conflict. While this is a great strategy this would require an API change, and its a little more verbose than styled-icons. Maybe, it could be considered for a future version or some other solution.

Yeah, the decision to preserve the original icon names rather than prefix them was intentional, as then the names of the components are the names of the icons.  I've always found it a little annoying when using icons packs if the pack has some sort of custom naming scheme basically.
That said, it does create the issue of name conflicts, like where the icon names match the names of components you defined, or if you want to import the same icon from the regular pack and the solid pack, for instance.  But I wanted to avoid FaSolidHome and FaRegularHome, etc.
Two ideas for how to handle this:
First, you could do what you mentioned and alias the imports:
import {Home as HomeIcon} from 'styled-icons/material'

<HomeIcon />

Second, you can also potentially use ES modules imports to alias the whole pack:
import * as material from 'styled-icons/material'

<material.Home />

The only concern there is if you don't have your bundler configured correctly, you can accidentally bundle all the icons rather than just the ones you're using.  If everything's working as expected though, the * as name import should properly tree-shake down to just the icons you're using.  And then you don't have to alias icon names:
import * as regular from 'styled-icons/fa-regular'
import * as solid from 'styled-icons/fa-solid'

const HomeIcon = selected ? solid.Home : regular.Home

<HomeIcon />

So I use CRA and I never want to eject, not sure what the bundler config is in it.
I have been playing around with alternative solutions.
Options 1
import { material } from 'styled-icons';
type IconName = keyof typeof material;

export const MaterialIcons = ({name, ...props}: { name: IconName, size: number}) => {
	const Icon = material[name];
	if (Icon) {
		return (<Icon {...props} />);
	} else {
		return (Icon Not Found);
	}
};

Example usage:
<MaterialIcons name="Home" size={20}/> Home

Pros:

Icons in pack names remain the same.
As of TS v2.9.*, which is in vscode v1.24, we get IntelliSense for literal types
You can have a specific interface and component for each icon pack, eg. material icons or https://github.com/webkul/vivid supports a two-tone option font-awesome doesn't.

Cons:

Tree shaking unknown

Option 2
type IconName = keyof typeof material;

type StyledIconsProps = { type: 'material', name: IconName, size: number};

export class StyledIcons extends React.Component


get subtree roots to allow for spend-before-sync

Ohh.... 5bd083a breaks load_old_wallet_at_reorged_height, as adding that flag to the zcash config is incompatible with the old chain being loaded that didn't have that flag. Either that test needs special handling to not use the new flag, or we need to create a new chain for that test.

Ohh.... 5bd083a breaks load_old_wallet_at_reorged_height, as adding that flag to the zcash config is incompatible with the old chain being loaded that didn't have that flag. Either that test needs special handling to not use the new flag, or we need to create a new chain for that test.

ok i will take a look at fixing this. having zcash-local-net integrated would make this much easier!


Failed to register a ServiceWorker for scope, TypeError: Failed to register a ServiceWorker for scope

Issue and Steps to Reproduce

I got Uncaught runtime erros when running a simple test React with TSX template.
Failed to register a ServiceWorker for scope ('http://localhost:3000/') with script ('http://localhost:3000/OidcServiceWorker.js'): ServiceWorker script evaluation failed
TypeError: Failed to register a ServiceWorker for scope ('http://localhost:3000/') with script ('http://localhost:3000/OidcServiceWorker.js'): ServiceWorker script evaluation failed
Versions
The source code I written can be downloaded from Git hub:
https://github.com/tonyctsiu/oidctest.git
const configuration = {   client_id: "oidc-client",   redirect_uri: window.location.origin + "/authentication/callback",   silent_redirect_uri:     window.location.origin + "/authentication/silent-callback", // Optional activate silent-signin that use cookies between OIDC server and client javascript to restore the session   scope: "product.read product.write",   authority: "http://localhost:9001",   service_worker_relative_url: "/OidcServiceWorker.js",   service_worker_only: true, };
Screenshots

Expected
Actual
Additional Details

Installed packages:
{ "name": "testprogram", "version": "0.1.0", "private": true, "dependencies": {   "@axa-fr/react-oidc": "^6.19.2",   "@testing-library/jest-dom": "^5.16.5",   "@testing-library/react": "^13.4.0",   "@testing-library/user-event": "^13.5.0",   "@types/jest": "^27.5.2",   "@types/node": "^16.18.35",   "@types/react": "^18.2.10",   "@types/react-dom": "^18.2.4",   "react": "^18.2.0",   "react-dom": "^18.2.0",   "react-router-dom": "^6.12.1",   "react-scripts": "5.0.1",   "typescript": "^4.9.5",   "web-vitals": "^2.1.4" }, "scripts": {   "start": "react-scripts start",   "build": "react-scripts build",   "test": "react-scripts test",   "eject": "react-scripts eject" }, "eslintConfig": {   "extends": [     "react-app",     "react-app/jest"   ] }, "browserslist": {   "production": [     ">0.2%",     "not dead",     "not op_mini all"   ],   "development": [     "last 1 chrome version",     "last 1 firefox version",     "last 1 safari version"   ] } }

Hi @tonyctsiu , thank you very much for your issue.
It seems your TrustedDomains.js file is missing inside your public folder.
It is an issue from us. It should be created automaticaly during nom install.
Create and configure it and then it should work!

Thanks Guillaume. It works..


Increase range of threshold sigma parameter

The threshold sigma parameter in the segmentation reaches a max value of 999, but background intensity can be larger than this If one is using a 16bit image for example. The maximum value needs to be increased in order to accommodate these images and avoid segmenting background regions in the image.

We have two options here:

Increase the range
Make it proportional (which is the one that I'm inclined to).

Do you agree or do we want to keep to pixels?


Explorer's full path tooltip layout is wrong.

VSCode Version: 1.21.1
OS Version: Ubuntu 18.04 LTS

Steps to Reproduce:

Open explorer and unfold a folder.
Move cursor from folder's content to the folder name.
The tooltip appears but with wrong layout.

If I move the cursor to the folder's name again, then OK.

Does this issue occur when all extensions are disabled?: Yes

We are building exploration builds that use a much newer version of Electron (our UI framework). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux: Download
Windows: Download

/duplicate https://github.com/Microsoft/vscode/issues/23946


chore(qr): Move QR to profile

Moved QR code to user profile

Remove the QR code from the /dashboard/scan-in and honestly just remove that page

Just removed that page in latest commit


master: build output comes before pull output...?

Output of docker version:
$ docker version
Client:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   6e721f6
 Built:        Fri May 27 16:12:02 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   6e721f6
 Built:        Fri May 27 16:12:02 2016
 OS/Arch:      linux/amd64

Output of docker info:
$ docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 39
Server Version: 1.12.0-dev
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.6.0-fsociety
Operating System: Debian GNU/Linux stretch/sid
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.52 GiB
Name: debian
ID: LWLG:XJIB:M6QI:K4J2:JAIZ:6H4Q:E7FE:KZZU:VTSA:D2UH:Y7SO:YNMH
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 15
 Goroutines: 29
 System Time: 2016-05-27T09:59:31.363440285-07:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Linux obvs, debian, you know the dealio
Steps to reproduce the issue:

Build a dockerfile

Describe the results you received:
Expected pull output then build output.
Describe the results you expected:
Got build output then pull info. And I already had alpine locally :/
$ make run
docker build --rm --force-rm -t r.j3ss.co/contained .
Sending build context to Docker daemon 17.11 MB
Step 1 : FROM alpine
 ---> 13e1761bf172
Step 2 : MAINTAINER Jessica Frazelle<EMAIL_ADDRESS> ---> Using cache
 ---> 3a3611a0a666
Step 3 : ENV PATH /go/bin:/usr/local/go/bin:$PATH
 ---> Using cache
 ---> 8d32bc8c7523
Step 4 : ENV GOPATH /go
 ---> Using cache
 ---> feef1ccd128f
Step 5 : ENV GO15VENDOREXPERIMENT 1
 ---> Using cache
 ---> 2295970b7788
Step 6 : RUN apk update && apk add 	ca-certificates 	&& rm -rf /var/cache/apk/*
 ---> Using cache
 ---> 4a1705b913be
Step 7 : COPY *.go /go/src/github.com/jfrazelle/contained/
 ---> Using cache
 ---><PHONE_NUMBER>45
Step 8 : COPY vendor /go/src/github.com/jfrazelle/contained/vendor
 ---> Using cache
 ---> 97378d929ba9
Step 9 : RUN buildDeps=' 		go 		git 		gcc 		libc-dev 		libgcc 	' 	set -x 	&& apk update 	&& apk add $buildDeps 	&& cd /go/src/github.com/jfrazelle/contained 	&& go build -o /usr/bin/contained . 	&& apk del $buildDeps 	&& rm -rf /var/cache/apk/* 	&& rm -rf /go 	&& echo "Build complete."
 ---> Using cache
 ---> cd3ed0cf50b7
Step 10 : COPY static /usr/src/contained/
 ---> Using cache
 ---> f24c7e4a7043
Step 11 : WORKDIR /usr/src/contained
 ---> Using cache
 ---> 594ba36e6461
Step 12 : ENTRYPOINT contained
 ---> Using cache
 ---> 3d6a4b48eca7
Successfully built 3d6a4b48eca7
docker run --rm -it \
	--net container:contained-dind \
	r.j3ss.co/contained -d
latest: Pulling from library/alpine
d0ca440e8637: Pull complete
Digest: sha256:9dd95238d7f6ac0fabafd7b52e52d8a7c63a5e5b390d27e13cb5da8ddd2f0d98
Status: Downloaded newer image for alpine:latest
DEBU[0002] Server listening on 10000

Additional information you deem important (e.g. issue happens only occasionally):
I can look into it later, just don't really have time right now

Also this makes no sense because how can it pull a latest image and yet use the cache....

Could it be you had a "alpine:some-version" that matched alpine:latest? (Re: using cache)

yeah maybe but this is what my current docker images output looks like :/
jessie at debian in ~
$ docker images
REPOSITORY                TAG                                     IMAGE ID
           CREATED             SIZE
r.j3ss.co/contained       latest
 3d6a4b48eca7        16 hours ago        21.35 MB
r.j3ss.co/contained       dev
d02db3bed646        16 hours ago        655.2 MB
r.j3ss.co/docker          userns
 6be3e8fa53a7        16 hours ago        82.77 MB
mesosphere/dcos-docker    latest
<PHONE_NUMBER>7f        19 hours ago        612.7 MB
mesosphere/dcos-docker    base
 2bd3f6ccf8fc        19 hours ago        577.7 MB
mesosphere/dcos-docker    centos
 2bd3f6ccf8fc        19 hours ago        577.7 MB
mesosphere/dcos-docker    centos-7
 2bd3f6ccf8fc        19 hours ago        577.7 MB
mesosphere/dcos-genconf   b2f9559b654bf5f2bf-fb268d10a77b1dde5c
5a7dd57df2a0        20 hours ago        721.2 MB
node                      latest
 a6b9ffdcf522        2 days ago          651.4 MB
docker                    1.11.1-dind
283d58943c98        2 weeks ago         80.39 MB
alpine                    latest
 13e1761bf172        3 weeks ago         4.793 MB
centos                    7
d0e7f81ca65c        11 weeks ago        196.6 MB
centos                    <none>
 d0e7f81ca65c        11 weeks ago        196.6 MB

On Fri, May 27, 2016 at 10:09 AM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Could it be you had a "alpine:some-version" that matched alpine:latest?
(Re: using cache)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/23064#issuecomment-222201270,
or mute the thread
https://github.com/notifications/unsubscribe/ABYNbElW8BsBs6IT2mhj-t5ObvCrIby3ks5qFyVmgaJpZM4Ior3E
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

@tonistiigi could that (cache) be if all the layers were already present, from other images, but the actual "repo:tag" not?

I have had 1.12 do something odd when if I pull or run say ubuntu it tries to pull every tag of that that exists. I can't replicate it with an empty image store, but its kind of annoying. It is fine if I just pull :latest explicitly.

@justincormack huh, there was a bug like that but it should have been fixed… there is even an integration test for it.

@vdemeester when was it fixed? This was probably from a few days back but I can't quite remember which machine I saw it on to check. But if you know how to replicate it please check...

@jfrazelle I'm not sure how to reproduce though, on a clean docker daemon  :sweat:

yeah i have been trying to, this might just be one of those weird things
that hppens once and then disappears, we could blame it on a ghost in the
machine
On Fri, May 27, 2016 at 11:44 AM, Vincent Demeester <
<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle I'm not sure how to reproduce
though, on a clean docker daemon 😓
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/23064#issuecomment-222223418,
or mute the thread
https://github.com/notifications/unsubscribe/ABYNbCRZZ1AZnca6EdFgZx5aMBg4xAy7ks5qFzt7gaJpZM4Ior3E
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

figured i would see if anyone else saw it first before ignoring entirely
On Fri, May 27, 2016 at 11:45 AM, Jessica Frazelle<EMAIL_ADDRESS>wrote:

yeah i have been trying to, this might just be one of those weird things
that hppens once and then disappears, we could blame it on a ghost in the
machine
On Fri, May 27, 2016 at 11:44 AM, Vincent Demeester <
<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle I'm not sure how to reproduce
though, on a clean docker daemon 😓
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/23064#issuecomment-222223418,
or mute the thread
https://github.com/notifications/unsubscribe/ABYNbCRZZ1AZnca6EdFgZx5aMBg4xAy7ks5qFzt7gaJpZM4Ior3E
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu
http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3


[React][DatePicker] DatePicker content doesn't close onClick outside

Description
When properties lazyMount and unmountOnExit set to true, datePicker content doesn't close onClick outside.
There is this warn in the console

Link to Reproduction (or Detailed Explanation)
https://codesandbox.io/p/devbox/gifted-breeze-x9dmyz?layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522id%2522%253A%2522ROOT_LAYOUT%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522cltcmt0n80007356kohu48ixy%2522%252C%2522sizes%2522%253A%255B70%252C30%255D%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522EDITOR%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522id%2522%253A%2522cltcmt0n80002356kee06cla0%2522%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522SHELLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522id%2522%253A%2522cltcmt0n80004356kjronps73%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522DEVTOOLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522id%2522%253A%2522cltcmt0n80006356kyiorlnq9%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%252C%2522sizes%2522%253A%255B50%252C50%255D%257D%252C%2522tabbedPanels%2522%253A%257B%2522cltcmt0n80002356kee06cla0%2522%253A%257B%2522id%2522%253A%2522cltcmt0n80002356kee06cla0%2522%252C%2522tabs%2522%253A%255B%255D%257D%252C%2522cltcmt0n80006356kyiorlnq9%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522cltcmt0n80005356k7vkc4rck%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522TASK_PORT%2522%252C%2522taskId%2522%253A%2522dev%2522%252C%2522port%2522%253A5173%252C%2522path%2522%253A%2522%252F%2522%257D%255D%252C%2522id%2522%253A%2522cltcmt0n80006356kyiorlnq9%2522%252C%2522activeTabId%2522%253A%2522cltcmt0n80005356k7vkc4rck%2522%257D%252C%2522cltcmt0n80004356kjronps73%2522%253A%257B%2522id%2522%253A%2522cltcmt0n80004356kjronps73%2522%252C%2522tabs%2522%253A%255B%257B%2522type%2522%253A%2522TASK_LOG%2522%252C%2522taskId%2522%253A%2522dev%2522%252C%2522id%2522%253A%2522cltcn6loq00fv356kj4cuyxkl%2522%252C%2522mode%2522%253A%2522permanent%2522%257D%255D%252C%2522activeTabId%2522%253A%2522cltcn6loq00fv356kj4cuyxkl%2522%257D%257D%252C%2522showDevtools%2522%253Atrue%252C%2522showShells%2522%253Atrue%252C%2522showSidebar%2522%253Atrue%252C%2522sidebarPanelSize%2522%253A15%257D
Steps to Reproduce
1.Set props lazyMount, unmountOnExit to true.
2.Open date picker content with trigger
a warning appears in the console

3.Click outside the content block (content does not close)
Expected behavior -  when click outside the content block, he closes
Ark UI Version
2.2.2
Framework

[X] React
[ ] Solid
[ ] Vue

Browser
Chrome
Additional Information
No response

@Trufflesmld
Thanks for taking your time. The issue will be resolved with the next update https://github.com/chakra-ui/zag/commit/ffda06f1c30790da1331824f5b0ad6eb86c7dad3


[refactor] #2909: Hardcode ports for nextest

Signed-off-by: Ilia Churin<EMAIL_ADDRESS>

Description of the Change
For each test that is run by nextest in iroha_client, iroha_data_model and iroha_p2p, replace usage of prepare_for_nextest! macro with hardcoded ports.

Issue
Closes #2909.

Benefits
Nextest now doesn't fail on either of those packages and finishes successfully. Full manual control.

Possible Drawbacks
If any new tests are added, the programmer will have to keep track of ports already in use and maybe do some simple arithmetic. Also might have some debugging involved in case of failing to get it right at first. Also some code duplication introduced with parallel methods that just allow specifying a port.

Usage Examples or Tests
cargo nextest run -p iroha_client or any other of the mentioned crates

Alternate Designs
Making that unique_port crate work by making an inhouse solution with other primitives?..

IMO it will be inconvenient to add new tests, because you are not only had to look for all occupied ports in tests, but also add additional offsets (for api port, telemetry, ...).

Good. We have 77 which is at least 30 too many.
But more importantly, if you do need to add a new test, you could add the test with a single sleep statement. If any other test uses the same port, you'll see a collision. It will tell you which test is using that particular port.
Also you have git grep, which can be run in the tests dir, and see if that numerical pattern occurs anywhere else in the code.
Or better yet, to bring all the occurrences in a human readable format in a nice table.

Since we don't check if this ports occupied by other programs in system, couldn't we use some kind of static atomic counter AtomicU16 with step of 10 that will assign ports.
EDIT: problem is that test would run in different processes and counter is shared only between threads of single process.

If we could, then Aleś solution would have done the job.
But the idea with a global counter can be re-used. We can rely on the order of macro expansion to produce the counters via proc_macro.
Finally, making the tests not fail if the ports are occupied is also a good option.

But the idea with a global counter can be re-used. We can rely on the order of macro expansion to produce the counters via proc_macro.

I have tried to implement such approach, but seems like macro expands to the same value for different files.
const PORT_INCREMENT: u16 = 10;
static CURRENT_PORT: AtomicU16 = AtomicU16::new(20_000);

#[proc_macro]
pub fn unique_port(_: TokenStream) -> TokenStream {
    let port: u16 = CURRENT_PORT.fetch_add(PORT_INCREMENT, Ordering::SeqCst);
    quote!(#port).into()
}

Or what do you mean?

Does i understand correctly that we fallback to unique port if port is not provided manually?

Yes, I suppose that's the intended behaviour here. I could just make it use some predetermined port and throw out unique_port crate altogether, though.

I don't mind using unique_port as fallback, we can throw it out later.


Add Geofence to SDK

The SDK was missing the Geofence entity as well as one of the resource actions on the user.

Coverage decreased (-0.5%) to 95.362% when pulling 78a315932952d6d7d71db047a244253aa17e8cb9 on Instawork:master into 391e0fa0f034f7db34bcc61e23cd72f0bb2832f6 on hypertrack:master.

Coverage decreased (-0.5%) to 95.362% when pulling 78a315932952d6d7d71db047a244253aa17e8cb9 on Instawork:master into 391e0fa0f034f7db34bcc61e23cd72f0bb2832f6 on hypertrack:master.

Coverage decreased (-0.5%) to 95.362% when pulling 78a315932952d6d7d71db047a244253aa17e8cb9 on Instawork:master into 391e0fa0f034f7db34bcc61e23cd72f0bb2832f6 on hypertrack:master.

Coverage decreased (-0.5%) to 95.362% when pulling 78a315932952d6d7d71db047a244253aa17e8cb9 on Instawork:master into 391e0fa0f034f7db34bcc61e23cd72f0bb2832f6 on hypertrack:master.

Coverage decreased (-0.5%) to 95.362% when pulling 78a315932952d6d7d71db047a244253aa17e8cb9 on Instawork:master into 391e0fa0f034f7db34bcc61e23cd72f0bb2832f6 on hypertrack:master.


Dashboard and transactions sections are blank.

I have one successfully connected login to SaltEdge, it is shown in logins section, but there is nothing on the dashboard.

Any ideas how can I debug this?
Thanks,
Ivan

Hello.
Sorry, I didn't see your issue as I wasn't in the watching list by some reason :)
Once you have a login, you also have to have accounts in Settings -> Accounts section. Do you have some? Please make sure that you tick 'Show on Dashboard' checkbox so an account can be displayed on Dashboard(both desktop and mobile).
If everything is ok with accounts, then there might be an error with syncing transactions. I'm afraid that the only way to debug it so far is application logs. Did you deploy to Heroku? If so, you can try to reconnect your login with heroku logs -t --source=app command running in the console(or can see your logs on heroku.com as well). If you see an error you can post logs here(don't forget to remove your customer_id from them first).
Also, you can check Saltedge login page to see if there is a LAST FAIL MESSAGE field populated. Also please check if there are some transactions on Saltedge side.
Is your login interactive? If it's not you can try to restart your application by running heroku restart -a your-app-name. The thing is that if your login is not interactive, then a ExMoney background worker should pick up your login and run periodic job to sync accounts/transactions. Maybe by some reason it didn't work during first login connect.

/settings/accounts doesn't show any accounts imported from SaltEdge(SE). In SE  I can see all the data, including 2 accounts and many transactions.
However I skipped the section with adding scheduler because my heroku account is not verified. Do these workers relay on scheduler?
Thanks,
Ivan :)

No, all ExMoney workers with business logic are OTP GenServer workers, so they don't need external schedulers. That worker which should be runnning with a heroku's scheduler is for waking up an app from idling.
I'll try to start one of my logins from scratch and then hopefully will come up with some more ideas how to debug the issue.

Just tried to reconnect a login(for the first time ever) and saw that on reconnect SE sends customer_id field in the notify callback request as ID value from SE customer page, but usually, SE sends customer_id as CUSTOMER ID as shown here https://docs.saltedge.com/guides/callbacks.
ExMoney does not expect that, I will fix callbacks.

I also noticed that heroku branch is a bit behind master. Do you plan to sync master's features with heroku branch?

Yeah, that's a problem: I don't know how to handle heroku branch properly. Every time I sync heroku branch with master I do rebase and then push with --force. I could merge master in heroku branch all the time, but then it will become overloaded with merge commits really quickly.
Probably I need to merge heroku in master, because heroku probably should be the first option to deploy.
I just updated heroku branch and rebased it on master, so you will need to run git pull with --rebase option and then add --force when pushing to heroku.
I've added a field Saltedge ID to a user which represents customer's ID field, you will need to fill it in(I didn't come up with the way how to sync a user in ExMoney with a Customer on SE side yet). After that, you can try to reconnect your login and check the logs. Don't forget to run heroku run mix ecto.migrate after deployment and then heroku restart -a appname.

When you create a customer, you get his identifier in synchronous response, so you can just store that value somewhere. Or you can obtain it later calling GET | https://www.saltedge.com/api/v2/customers

Yeah, that's correct, I meant that according to ExMoney's workflow, a user should first create an account(a customer) in SE, so he can obtain a CUSTOMER ID. Then a user gets CUSTOMER ID from SE page and fills it in on Settings -> User Account page. Having CUSTOMER ID allows a user to create new logins using New link on Settings -> Saltedge Logins page. The New link goes to Saltedge Connect page. Without CUSTOMER ID, ExMoney cannot get a token, without a token a user cannot be redirected to Saltedge Connect.
As you can see in this workflow there is no point where ExMoney could sync a customer from SE since customer on SE side and a user on ExMoney side are created at different times.
The workaround I introduced tomorrow to make Login reconnect work is to provide ID field from SE side as well, so a user have to fill in CUSTOMER ID and ID fields on Settings -> User Account page.

I mean that you don't have to force the user to visit his SE profile to obtain the customer id. You can just add a button like create customer which will make create customer request and sync its ID automatically. After then there's no problem to send create token request with all the necessary attributes. It takes time to implement and not so important, but doable :)
P.S.
Deployed to heroku from your master, but had to clone config/prod.exc from heroku branch.
Connected one new login but accounts still didn't show up (but SE has all the data).
Also, deleting login from ex-money didn't delete the login from SE, had to delete it from SE profile manually. Maybe delete button should also send delete request to SE

It's more than clear to me that ExMoney should have an ability to visualize a process of adding/refreshing a login. I'll try to implement such feature during this weekend and will come to you.

If you need any additional information about SE integration or some tips about app workflows you can ask me directly via<EMAIL_ADDRESS>;)

Oh great, thank you!

I just merged my pull-request so now if you go to Settings -> Saltedge Logins and click on a login name you will see a history of login refresh/sync operations. I hope this can help you to debug your issue. Also, you can sync each login separately by clicking on a 'Sync' link.
The change is on master and heroku branches, after deployment you will need to run heroku run mix ecto.migrate and then heroru restart -a app_name.

I'm confused... Which branch should I deploy? Last time I deployed heroku branch, last few days I run master branch on heroku. Is there any reason to keep the heroku branch?

If you're deploying to Heroku you should use a heroku branch. There are some changes between heroku branch master branches:

additional worker to prevent a heroku dyno sleeping
additional script file to wake up a dyno
a proper settings in prod.exs


Accessing the Works page from Collections has a UI element missing

Descriptive summary
on the Repository Content - Works page of the dashboard, the page has All Works and Your Works tabs at the top of the page to help the user orient themselves to what works they are looking at in the table below. When accessing this page using the Add Works button on a Collections page, the tabs don't appear.
Rationale
This is a UI bug that doesn't appear when the Works page is accessed otherwise, and thus should be addressed for consistency and because it helps with user orientation on the page.
Expected behavior
From the Add Works button on a Collections page, the Works page should show the tab outlines at the top of the Works page around one of the two view options (All Works or Your Works).
Actual behavior
Neither All Works or Your Works is highlighted on the page.
Steps to reproduce the behavior

Go to a collection
Select Add Works button
Note that the highlight tabs are not highlighted on the Works page
For reference - select the Works page directly from the Dashboard and note that the Your Works tab is highlighted

this is what it looks like when coming from Add Works button on Collections page

this is what it looks like when coming to Works from the Dashboard - note the highlighted tab

I can't reproduce in Hyku. Will try again with Hyrax test app.

hmm. i just confirmed this in hyrax.

okie dokie, @vantuyls.

work page wierdsies.zip

@vantuyls Hyrax master or 1.x?

master


Script Improvement and Instruction for Already Created App

Hi,
Thanks for writing this fantastic script.

I have added some instruction for those who already created the app without buildpack multi .

It is not needed to download and build awscli. Currently it is failing on finding aws binary on /tmp after being installed. Also giving pip==1.4.1 requirement error as pip version is updated currently as 1.6.1 . So I have removed the aws local download portion and installed awscli via pip . Added this on the requirements.txt

Add a flexibility to use DATABASE_URL directly in DATABASE variable. DATABASE_NAME is scrapped from Heroku for the former case.

Thanks.

@ibrahim12 - We run our backups from a completely separate app from our database.  I think it's a bit simpler this way.  Separation of concerns.  Not only that but you are then running your backups for free since you have no dynos running on this other project.  If we agree this is a cleaner approach then it simplifies the setup as there are less branches in the instructions.


Enhancement: vkCmdBindDescriptorSets : validate if pipelineBindPoint matches layout targets

Hi,
i just slipped over a subtle error, passing accidentally VK_PIPELINE_BIND_POINT_COMPUTE as bind point for descriptors that where meant for VK_PIPELINE_BIND_POINT_GRAPHICS.
It should be possible to check pipelineBindPoint  against the targets of the supplied pipeline layout to report a use error.

We don't really know which bind point a pipeline layout (or descriptor set layout) is intended for-- it's possible to use the same across both graphics and compute.
How would this work-- are you suggesting that we look at the stage flags of each VkDescriptorSetLayoutBinding and determine whether which bind points the layout is /at all/ useful for?

How would this work-- are you suggesting that we look at the stage flags of each VkDescriptorSetLayoutBinding and determine whether which bind points the layout is /at all/ useful for?

Yes

This seems like a good candidate for the assistant layer -- any objections to adding it to that worklist?


Follow references in webhook validation of TaskRuns and PipelineRuns

Expected Behavior
When a user creates a PipelineRun or a TaskRun which is incorrect (e.g. missing parameters that a Task expects) they should find out immediately, i.e. the admission control webhook should fail.
Actual Behavior
With most types in k8s, an effort is made to ensure that the order of creation of resources that reference each other doesn't matter.
For example, if you create a pod that references a volume claim that doesn't exist, you can still create the pod, and the logic trying to realize the pod will continue to check if the volume comes into existence later.
The webhook validation has been built with that assumption, and does not provide any k8s client objects which can be used to follow references.
However PipelineRuns and TaskRuns are different: when they are created, this is b/c the user wants them to execute immediately. They should not wait for some future date when the objects they reference exist (e.g. if you create a TaskRun and the Task it references doesn't exist, it should fail immediately).
The current state is that we do this kind of validation in the reconciler, so the object will actually be created, but the status will be updated indicating the error.
Steps to Reproduce the Problem

Write a TaskRun that references a Task that doesn't exist
Create the TaskRun with kubectl <-- the command should succeed
Get the TaskRun with kubectl and see the error in the status

What we want is for (2) to fail and for the TaskRun to not get created at all.
Additional Info
It is important that the reconciler still do this same validation since it is possible that the admission webhook may not be running.

Is this solution acceptable?
https://github.com/tektoncd/triggers/pull/81

However PipelineRuns and TaskRuns are different: when they are created, this is b/c the user wants them to execute immediately. They should not wait for some future date when the objects they reference exist (e.g. if you create a TaskRun and the Task it references doesn't exist, it should fail immediately).

@bobcatfish I wonder if this assumption is "fully" true, there might be some case when we may want to wait "a bit" for the objects they reference to exists (I think it's highly limited to few fields, but I feel there is some use-cases for it)

An example is this issue https://github.com/tektoncd/pipeline/issues/1473 :angel:

Another example is #2237

@bobcatfish I wonder if this assumption is "fully" true, there might be some case when we may want to wait "a bit" for the objects they reference to exists (I think it's highly limited to few fields, but I feel there is some use-cases for it)

interesting! I think tho this would likely also cause the Run to fail in this case, is that right?

@bobcatfish I wonder if this assumption is "fully" true, there might be some case when we may want to wait "a bit" for the objects they reference to exists (I think it's highly limited to few fields, but I feel there is some use-cases for it)

interesting! I think tho this would likely also cause the Run to fail in this case, is that right?

On #1473 *Run fails indeed, but it's a race (the ServiceAccount is present at the time of the *Run creation, but the controller doesn't see it)


Use latest kube-dns

kube-dns got a rewrite in 1.3, and is required for features like federation to work properly. It's also lighter weight/simpler. Bootkube is deploying the old kube-dns, it should get upgraded (also while at it the file should be renamed to a -deployment suffix since its no longer an RC).

closed in https://github.com/kubernetes-incubator/bootkube/pull/126


Tables with None in an entire column fail with an IndexError

This repo hasn't seen much action since this project was released, but I ran into what appears to be a bug, so I'm reporting it anyway.
from markdown_table_generator import (
    Alignment,
    generate_markdown,
    table_from_string_list,
)

rows = [
    ['![golang](golang.svg)', '![kafka](kafka.svg)', '![kubernetes](kubernetes.svg)', '![postgresql](postgresql.svg)', None, None, None],
    ['golang', 'kafka', 'kubernetes', 'postgresql', None, None, None],
]

table = table_from_string_list(table_from_string_list(rows, Alignment.CENTER))

generate_markdown(table)  # Dies

The traceback looks like this (vi iPython):
IndexError                                Traceback (most recent call last)
Cell In[5], line 1
----> 1 generate_markdown(table_from_string_list(rows, Alignment.CENTER))

File ~/projects/project-name/.venv/lib/python3.11/site-packages/markdown_table_generator/markdown_table_generator.py:98, in generate_markdown(table)
     96     return ""
     97 columns_size = __compute_columns_size(table)
---> 98 header_row = __generate_row(table[0], columns_size)
     99 dash_row = __generate_dash_row(table[0], columns_size)
    100 markdown = header_row + "\n" + dash_row

File ~/projects/project-name/.venv/lib/python3.11/site-packages/markdown_table_generator/markdown_table_generator.py:230, in __generate_row(row, columns_size)
    228 string = "|"
    229 for column_index, cell in enumerate(row):
--> 230     column_size = columns_size[column_index]
    231     if cell is None:
    232         string += " " + __generate_string_with(" ", column_size) + " |"

IndexError: list index out of range

However, if you swap out the None values above with "", it all works just fine.  As the example in the README use None, I thought you might wanna know :-)

Oh it's an old project, thanks for using it.
Thanks for the report, I'll update the README ASAP!


Remove tfe provider from terraform-octk-tfc-workspace-set

Describe the Issue
It is a best practice to not place provider definitions in a terraform module. We want to move the provider generation to the terragrunt.hcl
Additional Context

this prevents removing the module and destroying resource with terragrunt

Acceptance Criteria

[ ] Prodiver is removed from the module
[ ] Provider is generated in the tfc-aws-automation.hcl
[ ] Run a terragrunt apply across all project sets across all environments

.
.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

https://github.com/bcgov-c/aws-ecf-terragrunt-configuration/pull/25
https://github.com/BCDevOps/terraform-octk-tfc-workspace-set/pull/4

https://github.com/bcgov-c/aws-ecf-terragrunt-configuration/pull/25
https://github.com/BCDevOps/terraform-octk-tfc-workspace-set/pull/4