add elgamal to community packages

adds snarkyjs-elgamal to community packages, as a first example package
part of https://github.com/o1-labs/proj-management/issues/36

@Trivo25 Is this published to NPM? I think we should publish it to NPM and link to NPM, so we encourage other developers to do the same when submitting their package for this list. Providing NPM links will make it quicker for other devs to consume and use these packages, and they can find the Github link on the NPM page

@Trivo25 Is this published to NPM? I think we should publish it to NPM and link to NPM, so we encourage other developers to do the same when submitting their package for this list. Providing NPM links will make it quicker for other devs to consume and use these packages, and they can find the Github link on the NPM page

yep agree! its published, changed the link.
Other than that, is this how we want community packages to be listed or do we want a different format/more information?
- [Package-Name](link-to-npm): A brief description


[Feature Request] BOSH not supported

Hi,
I'm enjoying ChatSecure on Android but I'm really missing one feature. Is it possible to implement BOSH Support for ChatSecure? Behind many company firewalls there is no way to connect to the default xmpp port, so it would be great to add an optional BOSH Server which runs on Port 80/443.
BOSH is specified by XEP-0124: http://xmpp.org/extensions/xep-0124.html
Thanks!

I use ChatSecure 14.2.0a on Android / CM 12.1.
Works well with my Prosody XMPP server -- until I inject a public VPN (PIA, HMA) into the mix.  I'm working (around) the WHY, but both seem to block/prevent XMPP traffic.
I suspect, but don't yet know, that that's due to port(range) blocking, not to packet inspection.
So, currently, to use ChatSecure's security I need to drop VPN's security :-/  Bit of a Catch22.
One way around it is to enable Prosody's BOSH server, where BOSH allows XMPP where only a unblocked HTTP(S) connection is available, front-ending it with an nginx proxy.
XMPP Technologies: BOSH
    https://xmpp.org/about-xmpp/technology-overview/bosh

Setting up a BOSH server
    https://prosody.im/doc/setting_up_bosh

With nginx's SNA support, the BOSH proxy could easily be added to an existing webserver-occupied IP.
For this to be useful, however, the Client needs to support BOSH as well.
Looking around, the closest I've found to bosh support for XMPP on Android is Smack (https://www.igniterealtime.org/projects/smack/).
Smack API runs native under Android, and provides bosh libs,
https://github.com/igniterealtime/Smack/tree/31c53f094c9a613821b9e101f9d7f9bfd775b4e1/smack-bosh/src/main/java/org/jivesoftware/smack/bosh
Afaict, ChatSecure does not.
Looking in ChatSecure sources, I do find,
grep -rlni bosh .
	./libs/asmack-android-7.jar

But don't see any docs, or setting, that are BOSH-specific/enabling.
I do see here above,
n8fr8 added this to the v15 AWESOME APP milestone on May 8

but don't find any flag/commit for it.
(1) Does ChatSecure -- in release or dev -- currently have BOSH client support?
(2) If not, can it be added?
Given CS's security focus, I'm guessing this is far more likely an issue that'd be dealt with here, sooner than elsewhere.

Up! I am currently doing testing for my secure messaging platform and I think ChatSecure fits the bill quite nicely. One of the requirements is BOSH support so it may be filtered through the security gateway and the reverse proxy for security scans. That being said, I would LOVE for the security offered in ChatSecure to include the flexibility offered in BOSH using TLS HTTPS connections. Surprisingly few (read that as 0) clients on Android support BOSH. Xabber appears to have dropped the BOSH feature request, which was put in back in 2013. If I am wrong, please let me know.

It is true that BOSH is becoming more useful, especially in an age where XMPP is seen as a non-standard protocol that can be often filtered since it is not on port 80 or 443. We are strongly considering it, though it would be as part of our work on next-generation version of ChatSecure called Zom... see https://github.com/zom and https://zom.im
I think the issue has been with the Smack XMPP library, in that historically BOSH support was not available on Android. I think that has changed, so we will take a look.

Very cool. Thank you for the quick reply. I will keep a close eye on Zom then for future updates and check out the interface/features on it.
Thanks again!


Documentation for Normalized Cache and Optimistic responses

Hi,
I was just reading around normalized cache and optimistic responses.
After some digging, I saw that @sav007 created/merged a few features concerning this (last one being, #618).
Is there some documentation or best practice example on how to use these features? Im a little lost and all the apollo android docs seem broken atm.
Generally, I would like to be able to put my mutation results in the cache and reload dependent queries. How can this be implemented?
Any tips?
Thanks!

As this project is run by volunteers, we do not have proper documentation. We do have fantastic test coverage! Take a look at the tests to see if you CA find a good example.

@digitalbuddha Thanks, that actually helps a lot! Im assuming the tests can be used as guidance for the beste practices? One more thing I did not discover in the tests: What is the recommended way to refetch the dependent queries? Should I use a watcher or the refetch mechanism? Thanks a lot!

I would use the refetchQueries mechanism which will allow you to say which queries to refetch when the mutation happens.  Enjoy!


fix: don't render json response if url contains /api/

🔗 Linked issue
https://github.com/nuxt/nuxt/issues/19093
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Although a helpful idea, I think this is too broad a net for rendering an API response. Even routes starting with /api might still benefit from an HTML response if requested from a browser.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Isn't that a breaking change? With Nuxt requests to server/api endpoint now return html instead of the expected json.

~> see https://github.com/unjs/nitro/pull/969

Thank you for the background, I see :+1:  Intuitively I'd expect "root" /api routes to keep the previous json behavior, not matter how they're accessed.
I have an endpoint that either returns a specific content type (text/calendar) or throws a createError. I'd expect json for errors, even when calling that endpoint by manual input into the browser's address bar.
I don't want to rename the endpoint to *.json as it can return a different mime type. I also don't want to set the Content-Type header manually before errors. I'm not sure if the cors-related fix will solve that question, but I'll try later :raised_hands:
Is there something I should do instead? Maybe I don't see the obvious way to do it now.

I understand what you mean, though equally I would not expect users to access an /api/ endpoint directly in the browser and receive JSON (but only in the event of an error).
Would you open an issue to discuss adding a .startsWith() test? We might also consider allowing handlers to indicate their preference somehow, or something else.
cc: @pi0 who may have a better idea.

Reverting in https://github.com/unjs/nitro/pull/971 for now.

I've created https://github.com/unjs/nitro/discussions/978 as a place where a discussion can continue.


Cater for OSGi Environments

Following on from a comment made by Emily Jiang in PR #32 about an issue from the Config API project, will this not need a similar setInstance(SPIFactory spiFactory) method for this to work in an OSGi environment?

Probably yes, but I am not experienced with OSGI runtimes. Would you like to provide a PR for this?

Resolved with #46


[4.0.0] Custom SSL certificates

Able to add custom SSL certificates to Traefik.

Yes please

Check this out #1483 could be added as featurer request there…

Hello, I just noticed this issue and would like to see it implemented. Is there any workaround available right now?

When is this coming, I want to use Cloudflare origin SSL certificates on each of my services?

I thought this is already implemented through: https://coolify.io/docs/knowledge-base/traefik/custom-ssl-certs

Yeah, it’s now implemented, could be closed

No this is for adding SSL certs via the UI not trough ssh and folders.

No this is for adding SSL certs via the UI not trough ssh and folders.

Oh I see! Yes this would be fantastic. I could sign up with any provider like namecheap and download the key/certs and upload it through the Coolify UI you're saying? That would be amazing.


Spans from Sidekiq workers are missing after upgrading to v1.2.1

Description of the bug
After upgrading only the opentelemetry-sdk gem from v1.2.0 to v1.2.1, I started seeing a lot of "Calling finish on an ended Span." warnings from Sidekiq. I also found that I am only receiving a single span (the parent) for all of my Sidekiq workers. After reverting the SDK back down to v1.2.0 these problems went away.
The only thing that looks to have changed in 1.2.1 was https://github.com/open-telemetry/opentelemetry-ruby/pull/1412.

Share details about your runtime
Operating system details: macOS 13.4.1 (22F82)
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.2.2"
RUBY_DESCRIPTION: "ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]"

Here are is a simple example. You will need to have redis running locally and available on the default port.
Gemfile
# frozen_string_literal: true

source 'https://rubygems.org'

gem 'opentelemetry-api'
gem 'opentelemetry-common'
gem 'opentelemetry-instrumentation-base'
gem 'opentelemetry-instrumentation-sidekiq'
gem 'opentelemetry-sdk'

gem 'sidekiq'

Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    concurrent-ruby (1.2.2)
    connection_pool (2.4.1)
    opentelemetry-api (1.2.0)
    opentelemetry-common (0.19.7)
      opentelemetry-api (~> 1.0)
    opentelemetry-instrumentation-base (0.22.1)
      opentelemetry-api (~> 1.0)
      opentelemetry-registry (~> 0.1)
    opentelemetry-instrumentation-sidekiq (0.24.1)
      opentelemetry-api (~> 1.0)
      opentelemetry-common (~> 0.19.3)
      opentelemetry-instrumentation-base (~> 0.22.1)
    opentelemetry-registry (0.3.0)
      opentelemetry-api (~> 1.1)
    opentelemetry-sdk (1.2.1)
      opentelemetry-api (~> 1.1)
      opentelemetry-common (~> 0.19.3)
      opentelemetry-registry (~> 0.2)
      opentelemetry-semantic_conventions
    opentelemetry-semantic_conventions (1.10.0)
      opentelemetry-api (~> 1.0)
    rack (3.0.8)
    redis-client (0.14.1)
      connection_pool
    sidekiq (7.1.2)
      concurrent-ruby (< 2)
      connection_pool (>= 2.3.0)
      rack (>= 2.2.4)
      redis-client (>= 0.14.0)

PLATFORMS
  arm64-darwin-22

DEPENDENCIES
  opentelemetry-api
  opentelemetry-common
  opentelemetry-instrumentation-base
  opentelemetry-instrumentation-sidekiq
  opentelemetry-sdk
  sidekiq

BUNDLED WITH
   2.4.10

sidekiq_example.rb
# frozen_string_literal: true

require "rubygems"
require "bundler/setup"

Bundler.require

# Export traces to console by default
ENV["OTEL_TRACES_EXPORTER"] ||= "console"

OpenTelemetry::SDK.configure do |c|
  c.use "OpenTelemetry::Instrumentation::Sidekiq"
end

# A basic Sidekiq job worker example
class SimpleJob
  include Sidekiq::Worker

  def perform
    OpenTelemetry.tracer_provider.tracer("sidekiq_example", "0.0.1").in_span("foo") do
      puts "Workin'"
    end
  end
end

if ARGV[0] == "client"
  SimpleJob.perform_async
end

1. Queue the job
❯ ruby sidekiq_example.rb client

Output
I, [2023-07-18T16:03:06.400647 #9479]  INFO -- : Instrumentation: OpenTelemetry::Instrumentation::Sidekiq was successfully installed with the following options {:span_naming=>:queue, :propagation_style=>:link, :trace_launcher_heartbeat=>false, :trace_poller_enqueue=>false, :trace_poller_wait=>false, :trace_processor_process_one=>false, :peer_service=>nil}
2023-07-18T20:03:06.400Z pid=9479 tid=70b INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>nil}
#<struct OpenTelemetry::SDK::Trace::SpanData
 name="default send",
 kind=:producer,
 status=#<OpenTelemetry::Trace::Status:0x000000010565d5f0 @code=1, @description="">,
 parent_span_id="\x00\x00\x00\x00\x00\x00\x00\x00",
 total_recorded_attributes=5,
 total_recorded_events=1,
 total_recorded_links=0,
 start_timestamp=1689710586400870000,
 end_timestamp=1689710586400903000,
 attributes=
  {"messaging.system"=>"sidekiq",
   "messaging.sidekiq.job_class"=>"SimpleJob",
   "messaging.message_id"=>"c1634515acddda2474fb13bd",
   "messaging.destination"=>"default",
   "messaging.destination_kind"=>"queue"},
 links=nil,
 events=[#<struct OpenTelemetry::SDK::Trace::Event name="created_at", attributes={}, timestamp=1689710586400817871>],
 resource=
  #<OpenTelemetry::SDK::Resources::Resource:0x0000000105753ec8
   @attributes=
    {"service.name"=>"unknown_service",
     "process.pid"=>9479,
     "process.command"=>"sidekiq_example.rb",
     "process.runtime.name"=>"ruby",
     "process.runtime.version"=>"3.2.2",
     "process.runtime.description"=>"ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]",
     "telemetry.sdk.name"=>"opentelemetry",
     "telemetry.sdk.language"=>"ruby",
     "telemetry.sdk.version"=>"1.2.1"}>,
 instrumentation_scope=#<struct OpenTelemetry::SDK::InstrumentationScope name="OpenTelemetry::Instrumentation::Sidekiq", version="0.24.1">,
 span_id="\xACg+\x84\xBF\x06\xD7H",
 trace_id="`uV4l\xFB\x8B\x04\x04=R\x03\x9C+(U",
 trace_flags=#<OpenTelemetry::Trace::TraceFlags:0x00000001054f9970 @flags=1>,
 tracestate=#<OpenTelemetry::Trace::Tracestate:0x00000001054f0cd0 @hash={}>>

2. Run the sidekiq server
bundle exec sidekiq -r ./sidekiq_example.rb

Output
I, [2023-07-18T16:04:24.659634 #9874]  INFO -- : Instrumentation: OpenTelemetry::Instrumentation::Sidekiq was successfully installed with the following options {:span_naming=>:queue, :propagation_style=>:link, :trace_launcher_heartbeat=>false, :trace_poller_enqueue=>false, :trace_poller_wait=>false, :trace_processor_process_one=>false, :peer_service=>nil}

               m,
               `$b
          .ss,  $$:         .,d$
          `$$P,d$P'    .,md$P"'
           ,$$$$$b/md$$$P^'
         .d$$$$$$/$$$P'
         $$^' `"/$$$'       ____  _     _      _    _
         $:    ',$$:       / ___|(_) __| | ___| | _(_) __ _
         `b     :$$        \___ \| |/ _` |/ _ \ |/ / |/ _` |
                $$:         ___) | | (_| |  __/   <| | (_| |
                $$         |____/|_|\__,_|\___|_|\_\_|\__, |
              .d$$                                       |_|

2023-07-18T20:04:24.659Z pid=9874 tid=97q INFO: Running in ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]
2023-07-18T20:04:24.659Z pid=9874 tid=97q INFO: See LICENSE and the LGPL-3.0 for licensing details.
2023-07-18T20:04:24.659Z pid=9874 tid=97q INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
2023-07-18T20:04:24.659Z pid=9874 tid=97q INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>nil}
2023-07-18T20:04:24.665Z pid=9874 tid=97q INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>5, :pool_name=>"default", :url=>nil}
2023-07-18T20:04:24.665Z pid=9874 tid=97q INFO: Starting processing, hit Ctrl-C to stop
2023-07-18T20:04:24.671Z pid=9874 tid=966 class=SimpleJob jid=c1634515acddda2474fb13bd INFO: start
Workin'
#<struct OpenTelemetry::SDK::Trace::SpanData
 name="default process",
 kind=:consumer,
 status=#<OpenTelemetry::Trace::Status:0x0000000103945c10 @code=1, @description="">,
 parent_span_id="\x00\x00\x00\x00\x00\x00\x00\x00",
 total_recorded_attributes=6,
 total_recorded_events=2,
 total_recorded_links=1,
 start_timestamp=1689710664671493000,
 end_timestamp=1689710664671540000,
 attributes=
  {"messaging.system"=>"sidekiq",
   "messaging.sidekiq.job_class"=>"SimpleJob",
   "messaging.message_id"=>"c1634515acddda2474fb13bd",
   "messaging.destination"=>"default",
   "messaging.destination_kind"=>"queue",
   "messaging.operation"=>"process"},
 links=
  [#<OpenTelemetry::Trace::Link:0x00000001036328e8
    @attributes={},
    @span_context=
     #<OpenTelemetry::Trace::SpanContext:0x000000010355c310
      @remote=true,
      @span_id="\xACg+\x84\xBF\x06\xD7H",
      @trace_flags=#<OpenTelemetry::Trace::TraceFlags:0x0000000103633590 @flags=1>,
      @trace_id="`uV4l\xFB\x8B\x04\x04=R\x03\x9C+(U",
      @tracestate=#<OpenTelemetry::Trace::Tracestate:0x000000010326b070 @hash={}>>>],
 events=
  [#<struct OpenTelemetry::SDK::Trace::Event name="created_at", attributes={}, timestamp=1689710586400817871>,
   #<struct OpenTelemetry::SDK::Trace::Event name="enqueued_at", attributes={}, timestamp=1689710586403222084>],
 resource=
  #<OpenTelemetry::SDK::Resources::Resource:0x0000000103656bd0
   @attributes=
    {"service.name"=>"unknown_service",
     "process.pid"=>9874,
     "process.command"=>"/Users/jdeff/.asdf/installs/ruby/3.2.2/bin/sidekiq",
     "process.runtime.name"=>"ruby",
     "process.runtime.version"=>"3.2.2",
     "process.runtime.description"=>"ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]",
     "telemetry.sdk.name"=>"opentelemetry",
     "telemetry.sdk.language"=>"ruby",
     "telemetry.sdk.version"=>"1.2.1"}>,
 instrumentation_scope=#<struct OpenTelemetry::SDK::InstrumentationScope name="OpenTelemetry::Instrumentation::Sidekiq", version="0.24.1">,
 span_id="d\x0E\xCC\xC1\x10\xB3\x84\x90",
 trace_id="b2\b\xA0\xCC\xF8\xC9\x93%\xDA\xBA\xEA\x803\x04p",
 trace_flags=#<OpenTelemetry::Trace::TraceFlags:0x00000001032ca890 @flags=1>,
 tracestate=#<OpenTelemetry::Trace::Tracestate:0x000000010326b070 @hash={}>>
W, [2023-07-18T16:04:24.678488 #9874]  WARN -- : Calling finish on an ended Span.
2023-07-18T20:04:24.678Z pid=9874 tid=966 class=SimpleJob jid=c1634515acddda2474fb13bd elapsed=0.008 INFO: done

We have a similar issue opened in the instrumentation repo: https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/544
Would you mind sharing your comments there instead?


Temporary disable ForbiddenCallLikeRule as cause error on getrector.com/demo

it cause error on server

will check directly on server.

The fix https://github.com/rectorphp/getrector-com/pull/2458


Replay fails to load

Describe the bug
Any replay on the beatmap Zettai Tokken Shuchou Shimasu! Hoshi Syoko Solo Remix loads endlessly. Tested only on the "Koume's Extra" and "Karia's Extra" difficulties.
Expected behavior
The replay should finish loading.
Desktop

OS: Windows 10 Pro
Version: 2004 (build 19041.329)

Additional context
This bug was bugging me a bit (haha), so I decided to investigate a little. The developer console reports some 404 Not Found errors on requests made to the internal API of Rewind when attempting to load the replay. The requests seem to contain a trailing space character (%20) at the end of the directory name of the beatmap.
To mitigate this issue, I used Fiddler to redirect the requests to an address without the trailing space, although it cannot be done for the background image request as it seems to be handled internally by the API itself (which returns a 500 Internal Server Error, presumably for the same reason as the other errors).
A quick and dirty fix could be to trim the string before appending it to the URL, but I wonder why this doesn't happen on the other beatmaps.
Extra
Although this bug seems to present itself with any replay I tested so far, I have attached one in case it is necessary:
Ratchy - Syoko Hoshi (CV Satsumi Matsuda) - Zettai Tokken Shuchou Shimasu! Hoshi Syoko Solo Remix [Koume's Extra] (2022-02-27) Osu.zip

Same bug happens on this beatmap as well: https://osu.ppy.sh/beatmapsets/914865#osu/1929268


[ThemeManager] Problems while defining Colors

Hi,
Like you said to me, I created another issue.
For now, I just found a bug using the PaletteHelper : the Flyout (even with theme "Accent") is White or Dark. Here is a sample project : http://www.mediafire.com/download/6mfzie0arh7o4s2/MaterialTemplateProject.zip
Have a nice day,
Clément.

Cool.  Just got MahApps dialogs working with the help of MahApps guys, so will come to this soon.

Great ! I forgot to try dialogs :/

I'm sorry but I got another bug in my other Project with Dragablz... When I set a theme like here :

and then when I pull the tab to create another window, it reset the theme :

Don't be sorry, you are helping me sort the bugs! :smile:

Of course ^^
So as I said in my "EDIT", the bug don't really come from you, it's because my UserControl is reloaded :/

@furiousbuilder do we still have an issue here?


Build failed for iOS Simulator

When building for any iOS simulator on an M1 Mac, the following error occurs:
Could not find module 'TPInAppReceipt' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator, at: /Users/wizfinger/Library/Developer/Xcode/DerivedData/appname-bkfhgmponcvrxfawozdvxtgsikwn/Build/Products/Debug-iphonesimulator/TPInAppReceipt.swiftmodule
(TPInAppReceipt_Objc has the same result).
Build for device works correctly.
What can I do to fix this?

@Wizfinger Unfortunately, I don't have m1 mac, but based on error it seems you are running x86_64 simulator (maybe rosetta is turned on). It compiles for arm64-apple which is m1, but you are asking for x86_64

Thanks I’ll have a look here: https://stackoverflow.com/questions/56957632/could-not-find-module-for-target-x86-64-apple-ios-simulator
looks like it can be fixed by adding some settings in the podspec or the swift package manager.

While experimenting, I have found more details:
TPInAppReceipt-Objc.o, building for iOS Simulator-x86_64 but attempting to link with file built for unknown-arm64
TPInAppReceipt.o, building for iOS Simulator-x86_64 but attempting to link with file built for unknown-arm64
ASN1Swift.o, building for iOS Simulator-x86_64 but attempting to link with file built for unknown-arm64

As per this answer, support for arm64 Simulator slices on M1 Macs should be added in order to allow building for the Simulator.

@Wizfinger I'm sorry for the delay, I've been traveling for the last two weeks and will be able to check it out in a week. If you know how to fix it — feel free to make a PR. Thank you.


feat: increment relay's limits for basic/extended/privileged users

Description:

Currently, the local node's relay is using default values for spending plans.
Related issue(s):
Fixes #854
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 62.96%. Comparing base (ec0edf9) to head (864af9f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #855   +/-   ##
=======================================
  Coverage   62.96%   62.96%
=======================================
  Files          30       30
  Lines        1234     1234
  Branches      149      149
=======================================
  Hits          777      777
  Misses        436      436
  Partials       21       21

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


Add link titles for all links in the class reference

This makes them display in a nicer way in the editor help. (The title will display instead of the full URL.)
Note: Technically cherry-pickable to the 3.2 branch, but probably not worth doing so in practice due to the effort required.

Seems you used some regex to write them? I went through all titles, they are all good.

I wrote them by hand based on the page titles (with occasional modifications when relevant).

You've got to use sed for things like these!  In any case it's looking good.

You've got to use sed for things like these!

Well, as always, this chart applies :stuck_out_tongue:

Yes, it's all good.

Needs a rebase.

Thanks!


Nginx-le logs growing out of hand.

Access log has grown to 12 gb.
We need to roll the logs.
What should our retention policy be.
Disable letsencrypt log rotation
soft link those files to /dev/stdout in container
ln -s /dev/stdout access.log
ln -s /dev/stdout error.log
ln -s /dev/stdout letsencrypt.log
May be a option in nginx - set access log to stdout.
Could we have the dart code call logrotate - call it every hour.
threshold is date or size (100MB max)

gzip each file.
keep a fortnight of each file.
access.log -

done.


Minimal Implementation Walk Through

@bitskri3g  I like the goal of Kinetic which is to have a general baseline and a site specific overlay/pillar.  I will be glad to help build a blog/tutorial/etc on a Minimal Implementation that can be posted as part of the readme or a link to include in the readme.   I think that will help provide a quick start guide for easy adoption.  Let me know your thoughts and how I can help.

@kpeeples yes that's the goal.  I need to port more code from the old vta piece for it to be viable.  Give me a few more weeks.

@kpeeples We're almost at the point where we can apply a 1.0 tag.  Since you don't know the new codebase, I'm curious to see how well you're able to navigate it.  Some stuff should look familiar, some stuff not.  If you want to continue with README.md and see what you can glean from the source, by all means.
Our environment-specific pillar for prod is at https://git.cybbh.space/vta/kinetic-pillar.


Fix compiler warnings and clippy lints

@aldanor This fixes the latest CI failures

Thanks @mulimoen, as always :)
// I'm back next week after a few month long vacation trip and I'm keen on jumping back on train so we can release the big version and move on forward, e.g. with docs etc.


webmin 2.102 website post links to older usermin

at http://webmin.com on the changelog tab is the announcement/details on August 24 for webmin 2.102 and usermin 2.002
first, the Suggest Changes button does not work.
but secondly, and more important, that post links to the older usermin 2.001 release  😄

Thanks for the heads up! All fixed!


Grammar issues

Major grammar issues:
"Avoid recommendations mention things that are generally not a good idea, but breaking the rule sometimes makes sense:
❌ AVOID NuGet package references that demand an exact version.
And finally, Do not recommendations indicate something you should almost never do:"

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

ID: f519bf56-3618-bfba-3921-cacea56e810a
Version Independent ID: 9786b989-bce5-13ae-1e24-e88d7cadb7d3
Content: Package authoring best practices
Content Source: docs/create-packages/Package-authoring-best-practices.md
Service: nuget
GitHub Login: @nkolev92
Microsoft Alias: nikolev

Looking at it, I don't think there's a grammatical error necessarily, but there's definitely some ambiguity.

Avoid recommendations mention things that are generally not a good idea, but breaking the rule sometimes makes sense

In this case, Avoid recommendations is the object.
Similar thing applies to the other sentence as well.
Maybe there's a way to rewrite it to reduce the ambiguity though.


Overview of Current Scrapers

Looking solely at Sentry errors over the last three days- these are the only courts that have active issues.
Oklahoma appears to be an issue still.  Something about a captcha protections + HTML is causing weirdness

[x] Okla
[x] OklaCivApp
[x] OklaCrimApp
[x] OklaAG

Mississippi still blocks our scrapers but maybe we can resolve this soon.

[ ] Miss
[ ] MissAppCt

And another check of these courts is needed.

[ ] juriscraper.opinions.united_states.federal_appellate.ca10
[ ] juriscraper.opinions.united_states.administrative_agency.bva

Oklahoma should be resolved.

Whoo boy.

Currently we are selenium free
FYI

Pardon me? Like, we can remove it from our infrastructure?

Correct.  we no longer use selenium to scrape any website.  Do we want to keep it just in case we come across something?  idk.

Well...it's pretty easy to scale these down and save some memory, so I'm going to do that. If things go sideways, we'll know pretty quickly, I think.

BVA should get its own issue and Mississippi has its own.  So im going to close this for now.
We are going to start generating new issues when the new person starts going thru the system.


urgent: together.ai  api key incompatible with new code base updates

To reproduce the error, download the repo today and try to use together.ai as the llm. it will not work. this is due to recent changes made to the code. prior there was a loophole to use the openai key in the yaml as the api key (as together ai is meant to work).
like it goes ... open ai : 'together api key'  but that doesnt work now.
I tried 100 ways. not a developer so I cant edit the main code successfully besides the variables. it seems like a structural issue a small change maybe.
Original error message:
[INFO] Speech To Text - Whisper using GPU: True
Traceback (most recent call last):
File "C:\Users\transcribeUpdated\app\transcribe\main.py", line 125, in
main()
File "C:\Users\transcribeUpdated\app\transcribe\main.py", line 68, in main
ui_components = ui.create_ui_components(root, config=config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\transcribeUpdated\app\transcribe\ui.py", line 494, in create_ui_components
if not utilities.is_api_key_valid(api_key=api_key, base_url=base_url):
^^^^^^^
UnboundLocalError: cannot access local variable 'api_key' where it is not associated with a value

create a section in override.yaml file as follows
Together:
  api_key: 'API_KEY'

create a section in override.yaml file as follows
Together:
  api_key: 'API_KEY'

Ok I put the api as together.ai but still get this same error
File "C:\Users\transcribeUpdated\app\transcribe\main.py", line 125, in <module>     main()   File "C:\Users\transcribeUpdated\app\transcribe\main.py", line 68, in main        ui_components = ui.create_ui_components(root, config=config)                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\transcribeUpdated\app\transcribe\ui.py", line 494, in create_ui_components     if not utilities.is_api_key_valid(api_key=api_key, base_url=base_url):                                               ^^^^^^^ UnboundLocalError: cannot access local variable 'api_key' where it is not associated with a value

Transcribe configuration is very flexible. There are several ways to achieve the desired behavior of using Together AI.
They way described in the previous comment is accurate
OpenAI:
  api_key: 'API_KEY'
  base_url: 'https://api.together.xyz/v1'
  ai_model: ' together model '

The underlying issue is that Together AI does not support the way we use to validate the API key. This was a recent change.
I believe the issue has been fixed in https://github.com/vivekuppal/transcribe/pull/185 and your way of doing it should continue to work after that PR is merged.

ok thanks for the validation of the issue. Thank you!

Issue should be resolved now

Resolved by new updates nice work thanks. sorry I couldn't fix it myself.

Seems like this repo is serving some purpose to some extent.
There are multiple ways to contribute to the repo. Could write code, write something good about it, star the repo, make a video about useful use cases people like it for.


Powershell will force close on any error

Brief description of your issue
Powershell will close when it encounters an error preventing you from seeing what error was created
Steps to reproduce
run any winget app that fails and powershell will close
Expected behavior
powershell should stay open to see the error msg.
Actual behavior
powershell force closes
Environment
[winget --info]
Windows Package Manager v1.0.11451
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19042.985
Package: Microsoft.DesktopAppInstaller v1.11.11451.0

Any other software?

Are you executing this in Windows Terminal or a CMD session?
If you run this via [Windows]+[r] the command completes and the session is closed.

I was using Terminal, seems after windows update 21h1 it no longer happens.

I'll mark this as Area-External to keep it open for a while and see if this resolves the issue for others.

We've published the v1.1 release candidate and updated our troubleshooting guide.


[Documentation] Add AppGateServer Docs

Summary
Human Summary
This PR:

Introduces a first pass at the documentation for the appgateserver

AI Summary

Summary generated by Reviewpad on 23 Nov 23 19:32 UTC
This pull request includes changes to multiple files.

The file relay_fixtures_test.go has changes to the variables marshaledMinableRelaysHex and marshaledUnminableRelaysHex. These variables have been updated with new values.

The file server.go has changes to the function recordLocalToScalar. The error messages returned by this function have been formatted to provide more information about the types involved.

A new file server.md has been added to the package. It serves as comprehensive documentation for the AppGateServer component, covering various aspects of its usage and functionality.

The file synchronous.go in the pkg/relayer/proxy package has changes to the serveHTTP function. The changes involve using the relayRequest.Meta.SessionHeader on the relayResponse session header, along with an added log statement for debugging purposes.

The file diff also shows changes to the dependency versions in a separate file.

If you need further assistance, please let me know.

Issue

Fixes (in part) 159

Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[x] Code health or cleanup
[x] Documentation
[ ] Other (specify)

Testing

[x] Run all unit tests: make go_develop_and_test
[x] Verify Localnet manually: See the instructions [here](TODO: add link to instructions)

Sanity Checklist

[x] I have tested my changes using the available tooling
[x] I have performed a self-review of my own code
[x] I have commented my code, updated documentation and left TODOs throughout the codebase

@h5law Going to review this tomorrow. Thanks for the patience!

@h5law Does this need any updates?
Do you mind synching this with main after #252 is merged in and I'll re-review?

@h5law Are we going to pick this PR up again?

@Olshansk @red-0ne I will close this PR and create a new document as lots has changed since I originally made it.


Implement test for db_setup.py and encrypt_key.py

Related to #7
Add tests for db_setup.py and encrypt_key.py using pytest.

Add requirements files

Add requirements.txt for runtime dependencies.
Add requirements-dev.txt for development dependencies, including pytest.

Add tests for db_setup.py

Create tests/test_db_setup.py with test cases for validate_config and convert_config_to_db functions.
Handle temporary directories and environment variables in tests.
Cover edge cases for convert_config_to_db, including empty config, missing keys, unsupported authentication types, and invalid encrypted keys.
Encrypt real-api-keys before writing out to config file.

Add tests for encrypt_key.py

Create tests/test_encrypt_key.py with test cases for get_secret_key, encrypt_key, and decrypt_key functions.
Handle temporary directories and environment variables in tests.
Test encryption and decryption with different secret keys and default secret file path.

For more details, open the Copilot Workspace session.

requirements.txt と requirements-dev.txt からバージョン指定を外してください


singular and plural helpers are being registered the old way

it appears that the util for selecting how the helpers are registered is not working properly for me
https://github.com/stefanpenner/ember-inflector/blob/master/addon/lib/utils/make-helper.js
I am getting the deprecated version of the helper makeBoundHelper
Though I cant seem to find what version of the inflector i am running?
I am on ember 1.13.7, ember-data 1.13.8, and ember-cli 1.13.8

bump to ember-data 1.13.9 will fix it

k thanks! i suppose we can close this then :false-alarm:


Added xWinsSetting resource - Fixes #302

Pull Request (PR) description
This PR adds the xWinsSetting resource for configuring global WINS settings. It specifically allows enabling of LMHOSTS lookups and enabling/disabling of DNS resolution using WINS.
This Pull Request (PR) fixes the following issues:

Fixes #302
Relates to #199 but does not fully complete it (another resource xWinsServer is required).

Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[x] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[x] Examples appropriately updated?
[x] New/changed code adheres to Style Guidelines?
[x] Unit and (optional) Integration tests created/updated where possible?

@johlju - would you mind reviewing when you get a chance? I based this around the code you pasted in #199. I'll plan to implement a WINS server resource at some point, but to be honest it is a low priority (I'm a little bit surprised anyone is still using WINS at all :wink:).

This change is

Codecov Report

Merging #304 into dev will decrease coverage by <1%.
The diff coverage is 93%.

@@         Coverage Diff         @@
##            dev   #304   +/-   ##
===================================
- Coverage    98%    97%   -1%
===================================
  Files        25     26    +1
  Lines      1805   1848   +43
===================================
+ Hits       1769   1809   +40
- Misses       36     39    +3

@PlagueHO Awesome! I will review this tonight. WINS is a legacy we are trying to move away from... wish it could go less slowly though 😄 The script in issue #199 was used to move away from it on new deployments.

Looking good! Mostly non-blocking nitpicks.

Reviewed 10 of 10 files at r1.
Review status: all files reviewed at latest revision, 9 unresolved discussions.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/MSFT_xWINSSetting.schema.mof, line 5 at r1 (raw file):

EnableLMHOSTS

I think we need to use pascal case on this (EnableLmHosts), even if that might look uglier. :smile:  Throughout.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/MSFT_xWINSSetting.schema.mof, line 6 at r1 (raw file):

EnableDNS

I think we need to use pascal case on this (EnableDns), even if that might look uglier. :smile:  Throughout.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/en-US/MSFT_xWINSSetting.strings.psd1, line 8 at r1 (raw file):

An error result of

Does this return an error code? Using 'result' sounds to me that we get something (a result) that we expect. Not sure, but wouldn't An error code of, or Error code '{0'} was returned..., sound better?

Tests/Integration/MSFT_xWinsSetting.Integration.Tests.ps1, line 88 at r1 (raw file):

$configData

Nitpick, non-blocking: $configurationData. Throughout.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 117 at r1 (raw file):

                It 'Should call the expected mocks' {
                    Assert-MockCalled -CommandName Get-ItemProperty -Exactly -Times 2

Non-blocking: You could add the ParameterFilter scriptblock on the mock to a variable, then you can reuse it on the Assert-MockCalled to verify that it actually calls the mock once for each filter.
$getItemProperty_EnableDns_ParameterFilter = {
    $Path -eq 'HKLM:\SYSTEM\CurrentControlSet\Services\NetBT\Parameters' -and $Name -eq 'EnableDNS'
}

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 128 at r1 (raw file):

            Context 'Set EnableLMHosts to enabled and EnableDNS to enabled' {
                Mock -CommandName Invoke-CimMethod -MockWith { @{ ReturnValue = 0 } }

Hash table braces should be on separate row. Throughout. Non-blocking since I don't know if this is the way it's made for the rest of the module.
Maybe:
Mock -CommandName Invoke-CimMethod -MockWith {
    @{
         ReturnValue = 0
    }
}

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 137 at r1 (raw file):

                It 'Should call expected Mocks' {
                    Assert-MockCalled -commandName Invoke-CimMethod -Exactly -Times 1

Non-blocking:  There could be a -ParameterFilter on the Assert-MockCalled that verifies that the mock was called with the right values.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 137 at r1 (raw file):

-commandName

-CommandName - upper 'C'. Throughout.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 151 at r1 (raw file):

                It 'Should call expected Mocks' {
                    Assert-MockCalled -commandName Invoke-CimMethod -Exactly -Times 1

Non-blocking:  There could be a -ParameterFilter on the Assert-MockCalled that verifies that the mock was called with the right values.

Comments from Reviewable

All done! Great catches all round. I hoped WINS was going away - but I know the reality of large enterprise :grin: So I might still end up implementing an xWinsServerAddress resource using CIM. Just so I can say it's done and forever forget it :grin:

Review status: 4 of 10 files reviewed at latest revision, 9 unresolved discussions.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/MSFT_xWINSSetting.schema.mof, line 5 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

EnableLMHOSTS

I think we need to use pascal case on this (EnableLmHosts), even if that might look uglier. :smile:  Throughout.

Done. Although I left the ones the Registry Key names to match the case as they appear in the Registry as I felt this was appropriate.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/MSFT_xWINSSetting.schema.mof, line 6 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

EnableDNS

I think we need to use pascal case on this (EnableDns), even if that might look uglier. :smile:  Throughout.

Done. Although I left the ones the Registry Key names to match the case as they appear in the Registry as I felt this was appropriate.

Modules/xNetworking/DSCResources/MSFT_xWinsSetting/en-US/MSFT_xWINSSetting.strings.psd1, line 8 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

An error result of

Does this return an error code? Using 'result' sounds to me that we get something (a result) that we expect. Not sure, but wouldn't An error code of, or Error code '{0'} was returned..., sound better?

Good call - done.

Tests/Integration/MSFT_xWinsSetting.Integration.Tests.ps1, line 88 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

$configData

Nitpick, non-blocking: $configurationData. Throughout.

Done.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 117 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Non-blocking: You could add the ParameterFilter scriptblock on the mock to a variable, then you can reuse it on the Assert-MockCalled to verify that it actually calls the mock once for each filter.
$getItemProperty_EnableDns_ParameterFilter = {
    $Path -eq 'HKLM:\SYSTEM\CurrentControlSet\Services\NetBT\Parameters' -and $Name -eq 'EnableDNS'
}

Done.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 128 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Hash table braces should be on separate row. Throughout. Non-blocking since I don't know if this is the way it's made for the rest of the module.
Maybe:
Mock -CommandName Invoke-CimMethod -MockWith {
    @{
         ReturnValue = 0
    }
}

Doh! Good catch - I also cleaned up the other mocks a bit.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 137 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Non-blocking:  There could be a -ParameterFilter on the Assert-MockCalled that verifies that the mock was called with the right values.

Done.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 137 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

-commandName

-CommandName - upper 'C'. Throughout.

Done.

Tests/Unit/MSFT_xWinsSetting.Tests.ps1, line 151 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Non-blocking:  There could be a -ParameterFilter on the Assert-MockCalled that verifies that the mock was called with the right values.

Done.

Comments from Reviewable

Haha. Yes, it would be good to have that xWinsServerAddress resource, at least as long as there is a Windows Server version that support WINS and are in extended support :smile: So probably throughout this decade :)

Reviewed 6 of 6 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Thanks @johlju


Web engine leaks SemanticsHandle when running integration test

The Web Engine is causing a SemanticsHandle leak when an integration test generates semantics information. This leak went previously undetected because our leak detection logic contained a bug that's getting fixed in https://github.com/flutter/flutter/pull/121571.
Here's what's causing the leak:
An integration test calls SemanticsBinding.ensureSemantics and holds on to the returned semantics handle (it is properly disposed at the end of the test). This will cause the framework to generate a semantics tree, which at the end of the frame gets send to the engine via FlutterView.updateSemantics and ends up here in the web engine:
https://github.com/flutter/engine/blob/0f4acf3be29203de0f71f65574e400b5e9f77858/lib/web_ui/lib/src/engine/semantics/semantics.dart#L1787
The web engine now thinks that because it received a semantics tree it should turn around and tell the framework to turn on semantics. This happens indirectly by setting this semanticsEnabled setter to true:
https://github.com/flutter/engine/blob/0f4acf3be29203de0f71f65574e400b5e9f77858/lib/web_ui/lib/src/engine/semantics/semantics.dart#LL1799C9-L1799C25
At the end of that setter, the framework is informed that the engine is interested in semantics updates:
https://github.com/flutter/engine/blob/0f4acf3be29203de0f71f65574e400b5e9f77858/lib/web_ui/lib/src/engine/semantics/semantics.dart#L1608
This causes a SemanticsHandle to be created, which represents the engine's interest in semantics updates. This SemanticsHandle is never disposed, causing the SemanticsHandler leak detection to fail. Also, the fact that one test turned on semantics now leaks into the next test. The only proper way of disposing this SemanticsHandle is for the engine to give up its interest in receiving semantics update. In an integration test there isn't really a way to do this, though.
Overall, the engine should only tell the framework to turn on semantics when it itself has an interest in it. Not because somebody else (e.g. a test) expressed their interest and caused semantics updates to be generated. AFAIK, all other embedders behave this way.
The web engine already contains special logic for regular unit tests to avoid this problem. Maybe this needs to be extended to cover integration tests as well?
https://github.com/flutter/engine/blob/0f4acf3be29203de0f71f65574e400b5e9f77858/lib/web_ui/lib/src/engine/semantics/semantics.dart#L1789

The following g3 target shows the issue:
//mobile/flutter/samples/hello_flutter/app:integration_tests_screendiff_test_testing_web

Added an exemption and TODO for web integration tests to the leak detector:
https://github.com/flutter/flutter/blob/6de42a70f1a9986d21bfab72fe3d7ebae4842774/packages/flutter_test/lib/src/widget_tester.dart#L1047-L1048
We should revise that exemption and TODO when this issue gets fixed.

Make sense. We should split the enabling logic into two parts:

Enabling the web engine semantics system: this simply bootstrap semantics in the engine and processes updates, if any, coming from the framework. It should be unopinionated about whether the framework-side semantics is enabled or not.
Enabling the framework semantics system: this part would listen to either the framework or the a11y placeholder events, then enable the web engine semantics system, and, if the event came from the placeholder, notify the framework that semantics was enabled.

This would break the cycle, since the web engine semantics no longer sends any notifications back to the framework.

Another usecase is inability to programmatically disable semantics in web once enabled.
Reproduction code:
  @override
  void initState() {
    semanticsTest();
    super.initState();
  }

  Future<void> semanticsTest() async {
    print(SemanticsBinding.instance.semanticsEnabled); // 'false'

    final handle = SemanticsBinding.instance.ensureSemantics();

    print(SemanticsBinding.instance.semanticsEnabled); // 'true'
    print(SemanticsBinding.instance.debugOutstandingSemanticsHandles); // '1'

    await Future.delayed(const Duration(seconds: 5));

    print(SemanticsBinding.instance.debugOutstandingSemanticsHandles); // prints '2', which is incorrect

    handle.dispose();
    // expect semantics to be disabled after handle disposal

    print(SemanticsBinding.instance.debugOutstandingSemanticsHandles); // prints '1' (should be 0)
    print(SemanticsBinding.instance.semanticsEnabled); // prints 'true', should be 'false'
  }


React 17 support

--legacy-peer-deps seems to be fine for now..
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-netlify-forms
npm ERR<EMAIL_ADDRESS>from the root project

Thanks for reporting this issue!
I extended the version range to allow React 17 as peer dependency.
It's now part of v1.3.2


Fix uploading activity as a text.

Unfortunately gave up writing a test. BTW, how do you launch them?

The tests are a bit tricky, because you have to create your own test.ini that has a strave API token.  And  unfortunately some of the "sample data" that I was using for tests (which was from examples in Strava API) is no longer accessible.  Short of mocking out the Strava side, I'm not sure how to handle the fact that the data in Strava is not especially stable.  (And of course mocking out the Strava API really reduces effectiveness of the test.)

Thanks for fix!


Unable to get any stats

The changes regarding TLS 1.2 seems to have broken lookups altogether for .Net Core.
I have tried on .Net Core 2.0 as well as .Net Core 2.1 and I get the same exception.
If it helps, I'm running Windows 10 and Visual Studio 2017 Community.

I'm on Win10 as well, I was having problems without it though, it seems support for TLS12 is all over the shop and right now I'm between a rock and a hard place with it.
The tests are all running on framework 4.6.2, and are running fine there.
I'm not up to speed on NetCore the only thing I could really find on the issue was this

I ran an analysis on PlayOverwatch and it does seem to support TLS 1.1 as an alternative to 1.2
If you happen to have a local copy you could try this out for me and see if you get on with it, I don't have netcore set up on my machine in any capacity right now.
HttpProfileClient.cs in OverwatchAPI/Core/WebClient/
switching line 17 from this...
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls11;

to just this
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11;

Good news!
I changed line 17 like you asked and everything seems to work just fine.
I'm able to get player data using TLS 1.1 with both .Net Core 2.0 and 2.1.

Fix is implemented and will be up with the next release.


USSD public line update message receiver flow

two new states to be added to the public line that calls for change to the flow

@gsvr please review

@NicolaasDieBaas Done for now.

@gsvr Second-pass please.  There might be a more elegant way of displaying state 16

:+1:


add ka-GE locale.

ka-GE locale, if needed of course.

Thank you very much for the PR!
Could you please address one comment? Thank you!

I'm sorry, I don't quite get what you meant by 'address one comment'. If it's github specific stuff, I'm kinda new here (but account is old).


pin cairo dependencies and corelib checks

Fixes #304
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #337 (5e15a49) into main (113be0b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #337   +/-   ##
=======================================
  Coverage   72.43%   72.43%
=======================================
  Files         117      117
  Lines       20590    20590
=======================================
  Hits        14915    14915
  Misses       5675     5675

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature Request: Add support for Cloud Run

@54m
Would it be possible to add support for Cloud Run environment variables ?
https://cloud.google.com/run/docs/container-contract#env-vars

@tg-kozaki
waiting for your contribution

@54m
Cloud you grant permission to write(push) ?

@tg-kozaki
invited you to the organization(gcp-kit). plz check it.

or fork & pr

Thank you. I created PR. plz review this in your free time.
https://github.com/gcp-kit/gcpen/pull/2


NavigateAway modal shows up on state change even though form doesn't change

When moving from one state to another state without change in form, the navigate away popup is shown.  How to avoid the same ?

hmmm it must think it's dirty for some reason. are you loading data in/setting values after the form is initialized? if you don't want to worry about that you can just disable the feature entirely... thoughts?

Hmm, i just realized that in one of the form we have only filter criteria and on apply of any of those filter(s) it is setting $changed to true. This is causing the navigate away modal pop's up.
So can we disable navigate away for a specific  form ?

Yup:
https://github.com/AngularAgility/AngularAgility/blob/b283ee6a296d7fc6b76539d2e7b7ee2787c1a37c/demo/app/formExtensions/advanced.html#L62
Feel free to do some PRs to add more docs as you find things. That is one lacking thing with this library unfortunately...

Below code doesn't work
div ng-form="xyz" on-navigate-away-strategy="none">
Am i missing something here ?

Not sure, try giving the debugger a whirl:
https://github.com/AngularAgility/AngularAgility/blob/2bed4475891ba7ff0e3e57ed026db7f41de5c6e9/src/formExtensions/directives/ngForm.js#L90


Aperture and slits

Simulations needs aperture and slits to restrain the beam and suppress unrealistic beam trajectories.

(clean)[https://ops.aps.anl.gov/manuals/elegant_latest/elegantsu126.html#x137-13600010.16]
could be used to do this

the better solution found in the forum: https://ops.aps.anl.gov/manuals/elegant_latest/elegantsu112.html#x123-12200010.2


port1.0: Implement use_xcode option

To my understanding, MacPorts runs fine using only the Command Line Tools and this has been a problem for quite some time. In this PR, as part of the GSOC program, I have implemented several changes as the first step in providing a smooth experience of using MacPorts without Xcode:

In addition to the port 1.0 PortGroup, maintainers can declare Xcode dependency using a new Portfile option use_xcode
Unless ports declare Xcode dependency:

Default ‘DEVELOPER_DIR’ to point Command Line Tools. Thus, shim Xcode binaries such as /usr/bin/clang and /usr/bin/gcc will point to Command Line Tools instead of Xcode. This will ensure all Xcode-independent ports have reproducible builds
Installing/building with trace mode will hide the Xcode installation, so MacPorts can fail builds for ports that actually need Xcode but are not declared as such. This will help maintainers identify Xcode dependency.

Error out in the fetch phase when users try to install Xcode-dependent ports without installing Xcode (if $xcodeversion eq "none")

Relevant:

https://trac.macports.org/ticket/35045
https://trac.macports.org/ticket/58016
Prior discussion in https://github.com/satraul/macports-base/pull/11

Thank you.

This looks good to me as well.
As expected, this change does not seem to have any affect on the compiler behavior for OS < 10.9.

Okay, I've rebased and cleaned the commit history


kvm kitchen test has an error

I downloded kvm from supermarket. Then I did kitchen converge and I saw this error:
================================================================================
       Recipe Compile Error
       ================================================================================

       Chef::Exceptions::RecipeNotFound
       --------------------------------
       could not find recipe disable for cookbook ntp

       Cookbook Trace:
       ---------------
         /tmp/kitchen/cache/cookbooks/kvm/recipes/guest.rb:26:in `from_file'
         /tmp/kitchen/cache/cookbooks/kvm/recipes/default.rb:21:in `from_file'
         /tmp/kitchen/cache/cookbooks/gtd_buildhost/recipes/default.rb:12:in `from_file'

       Relevant File Content:
       ----------------------
       /tmp/kitchen/cache/cookbooks/kvm/recipes/guest.rb:

        19:  #
        20:
        21:  ## Use kvm-clock
        22:  # http://s19n.net/articles/2011/kvm_clock.html
        23:  # Disabling NTP is recommended when using kvm-clock
        24:  if node['os'] == 'linux' && node['kernel']['release'] >= '2.6.27'
        25:    node.override['ntp']['ntpdate']['disable'] = false
        26>>   include_recipe 'ntp::disable'
        27:    include_recipe 'ntp::ntpdate'
        28:  else
        29:    include_recipe 'ntp'
        30:  end
        31:

       System Info:
       ------------
       chef_version=13.0.118
       platform=centos
       platform_version=7.3.1611
       ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
       program_name=chef-client worker: ppid=12076;start=20:02:27;
       executable=/opt/chef/bin/chef-client

       Running handlers:
       [2017-05-10T20:02:30+00:00] ERROR: Running exception handlers
       [2017-05-10T20:02:30+00:00] ERROR: Running exception handlers
       Running handlers complete
       [2017-05-10T20:02:30+00:00] ERROR: Exception handlers complete
       [2017-05-10T20:02:30+00:00] ERROR: Exception handlers complete
       Chef Client failed. 0 resources updated in 03 seconds
       [2017-05-10T20:02:30+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       [2017-05-10T20:02:30+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       [2017-05-10T20:02:30+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
       [2017-05-10T20:02:30+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
       [2017-05-10T20:02:30+00:00] ERROR: could not find recipe disable for cookbook ntp
       [2017-05-10T20:02:30+00:00] ERROR: could not find recipe disable for cookbook ntp
       [2017-05-10T20:02:30+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
       [2017-05-10T20:02:30+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>>     Converge failed on instance <default-rhel7>.  Please see .kitchen/logs/default-rhel7.log for more details
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuratio

Based on my investigation, it is only realed to ntp cookbook and kvm. But I cant understand what is a problem. Also, I used my custom box which I created woth packer and libvirt provider.
I installed the last version of Chef-DK for Ubuntu 16.04 which is chefdk_1.3.43-1
chef-client: 12.19.36
berks -v: 5.6.4
Test kitchen -v: 1.16.0

ntp::disable was removed 4 yrs ago.
The kvm owner needs to update their cookbook

@shortdudey123 so I have to delete that recipe?

@aidda Yes that should be removed from the KVM cookbook

@shortdudey123 OMG I was searching for this issue about two hours! thanks a lot!
I did it, and now it`s fine


Change name to the vote result

This is a reminder to future self to change the name in the draft (title, text, buttons!, links!) once we have settled on a final name choice.

Fixed on 6e7e3d3.


crashed on startup with  EGL_NOT_INITIALIZED (0x12289):

Regression?
No
System Info and Version
 System/Version info
                  -`                    cong@kuku
                  .o+`                   ---------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Kernel: 6.9.6-arch1-1-cong
               `+oooooo:                 Uptime: 6 hours, 26 mins
               -+oooooo+:                Packages: 1887 (pacman), 52 (nix-default), 18 (flatpak)
             `/:-:++oooo+:               Shell: zsh 5.9
            `/++++/+++++++:              Resolution: 3840x2160
           `/++++++++++++++:             DE: GNOME 46.3.1
          `/+++ooooooooooooo/`           WM: Mutter
         ./ooosssso++osssssso+`          WM Theme: Adwaita
        .oossssso-````/ossssss+`         Theme: adw-gtk3-dark [GTK2/3]
       -osssssso.      :ssssssso.        Icons: Adwaita [GTK2/3]
      :osssssss/        osssso+++.       Terminal: tmux
     /ossssssss/        +ssssooo/-       CPU: AMD Ryzen 7 1700X (16) @ 3.400GHz
   `/ossssso+/:-        -:/+osssso+-     GPU: NVIDIA GeForce GTX 1070 Ti
  `+sso+:-`                 `.-/+oso:    Memory: 7037MiB / 56175MiB
 `++:.                           `-/+/

❯ lsmod |grep nvi
nvidia_drm            122880  9
nvidia_modeset       1617920  19 nvidia_drm
nvidia_uvm           6680576  0
nvidia              61005824  278 nvidia_uvm,nvidia_modeset
video                  77824  2 asus_wmi,nvidia_modeset

~ via 🐍 v3.12.4
❯ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y

Description
start hyprland in tty and it crash
How to reproduce
start hyprland in tty and it crash
Crash reports, logs, images, videos
--------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Calm down, it was a misinput! MISINPUT!

Hyprland received signal 6(ABRT)
Version: 5dd2c27b631f16e49a2c6e6cbbefba9fa50bf543
Tag: v0.41.2-164-g5dd2c27b
Date: Sun Aug 4 20:19:37 2024
Flags:

System info:
	System name: Linux
	Node name: kuku
	Release: 6.9.6-arch1-1-cong
	Version: #1 SMP PREEMPT_DYNAMIC Wed, 26 Jun 2024 12:08:30 +0000

GPU:
	06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller])

os-release:
	NAME="Arch Linux"
	PRETTY_NAME="Arch Linux"
	ID=arch
	BUILD_ID=rolling
	ANSI_COLOR="38;2;23;147;209"
	HOME_URL="https://archlinux.org/"
	DOCUMENTATION_URL="https://wiki.archlinux.org/"
	SUPPORT_URL="https://bbs.archlinux.org/"
	BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
	PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
	LOGO=archlinux-logo
Backtrace:
	# | Hyprland(_Z12getBacktracev+0x46) [0x62a041383e96]
		getBacktrace()
		/usr/src/debug/hyprland-git/Hyprland/build/../src/helpers/MiscFunctions.cpp:791
	#1 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0xabf) [0x62a04130ce4f]
		CrashReporter::createAndSaveCrash(int)
		/usr/include/c++/14.2.1/bits/basic_string.h:632
	#2 | Hyprland(_Z25handleUnrecoverableSignali+0x5c) [0x62a0412a104c]
		handleUnrecoverableSignal(int)
		/usr/src/debug/hyprland-git/Hyprland/build/../src/Compositor.cpp:73
	#3 | /usr/lib/libc.so.6(+0x3d1d0) [0x7c6c2144c1d0]
		??
		??:0
	#4 | /usr/lib/libc.so.6(+0x963f4) [0x7c6c214a53f4]
		??
		??:0
	#5 | /usr/lib/libc.so.6(gsignal+0x20) [0x7c6c2144c120]
		??
		??:0
	#6 | Hyprland(_ZN15CHyprOpenGLImpl7initEGLEb+0x17c) [0x62a041531e5c]
		CHyprOpenGLImpl::initEGL(bool)
		/usr/src/debug/hyprland-git/Hyprland/build/../src/render/OpenGL.cpp:114 (discriminator 1)
	#7 | Hyprland(_ZN15CHyprOpenGLImplC1Ev+0xb28) [0x62a04153b9f8]
		CHyprOpenGLImpl::CHyprOpenGLImpl()
		/usr/src/debug/hyprland-git/Hyprland/build/../src/render/OpenGL.cpp:305
	#8 | Hyprland(_ZN11CCompositor12initManagersE18eManagersInitStage+0xc41) [0x62a0412a8dd1]
		CCompositor::initManagers(eManagersInitStage)
		/usr/include/c++/14.2.1/bits/unique_ptr.h:202 (discriminator 1)
	#9 | Hyprland(_ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi+0xbfc) [0x62a0412a2bfc]
		CCompositor::initServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int)
		/usr/src/debug/hyprland-git/Hyprland/build/../src/Compositor.cpp:311
	#1 | Hyprland(main+0xbca) [0x62a04123a6ba]
		main
		/usr/include/c++/14.2.1/bits/basic_string.h:809
	#11 | /usr/lib/libc.so.6(+0x25e08) [0x7c6c21434e08]
		??
		??:0
	#12 | /usr/lib/libc.so.6(__libc_start_main+0x8c) [0x7c6c21434ecc]
		??
		??:0
	#13 | Hyprland(_start+0x25) [0x62a041268485]
		_start
		??:?

Log tail:
[LOG] [AQ] drm: Ignoring connector 85 because it has no CRTC
[LOG] [AQ] drm: Scanning connector id 89
[LOG] [AQ] drm: Initializing connector id 89
[LOG] [AQ] drm: Connector gets name DP-3
[ERR] [AQ] drm: getCurrentCRTC: No CRTC 0
[LOG] [AQ] drm: Ignoring connector 89 because it has no CRTC
[LOG] [AQ] drm: Rechecking CRTCs
[LOG] [AQ] drm: connector DVI-D-1, has crtc -1, will be rechecked
[LOG] [AQ] drm: Skipping connector HDMI-A-1, has crtc 41 and is connected
[LOG] [AQ] drm: connector DP-1, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-2, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-3, has crtc -1, will be rechecked
[LOG] [AQ] drm: slot 0 crtc 41 taken by HDMI-A-1, skipping
[LOG] [AQ] drm: slot 1 crtc 51 unassigned
[LOG] [AQ] drm: slot 2 crtc 61 unassigned
[LOG] [AQ] drm: slot 3 crtc 71 unassigned
[LOG] [AQ] drm: Connector DVI-D-1 is not connected
[LOG] [AQ] drm: Connector DP-1 is not connected
[LOG] [AQ] drm: Connector DP-2 is not connected
[LOG] [AQ] drm: Connector DP-3 is not connected
[LOG] [AQ] drm: rescanning after realloc
[LOG] [AQ] drm: Scanning connectors for /dev/dri/card0
[LOG] [AQ] drm: Scanning connector id 76
[LOG] [AQ] drm: Connector id 76 already initialized
[LOG] [AQ] drm: Ignoring connector 76 because it has no CRTC
[LOG] [AQ] drm: Scanning connector id 78
[LOG] [AQ] drm: Connector id 78 already initialized
[LOG] [AQ] drm: Connector 78 connection state: 1
[LOG] [AQ] drm: Scanning connector id 81
[LOG] [AQ] drm: Connector id 81 already initialized
[LOG] [AQ] drm: Ignoring connector 81 because it has no CRTC
[LOG] [AQ] drm: Scanning connector id 85
[LOG] [AQ] drm: Connector id 85 already initialized
[LOG] [AQ] drm: Ignoring connector 85 because it has no CRTC
[LOG] [AQ] drm: Scanning connector id 89
[LOG] [AQ] drm: Connector id 89 already initialized
[LOG] [AQ] drm: Ignoring connector 89 because it has no CRTC
[LOG] [AQ] drm: gpu /dev/dri/card0 becomes primary drm
[LOG] [AQ] Starting the Aquamarine backend!
[LOG] [AQ] Starting the Wayland backend!
[ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
[ERR] [AQ] Requested backend (wayland) could not start, enabling fallbacks
[ERR] [AQ] Implementation wayland failed, erasing.
[LOG] [AQ] Created a GBM allocator with drm fd 30
[LOG] [AQ] drm: Connectors size2 5
[LOG] [AQ] Created a GBM allocator with drm fd 31
[ERR] [AQ] CDRMRenderer: fail, eglInitialize failed
[ERR] [AQ] drm: onReady: no renderer for gl formats
[LOG] [AQ] drm: onReady: connector 76
[LOG] [AQ] drm: onReady: connector 78
[LOG] [AQ] drm: onReady: connector 78 has output name HDMI-A-1
[LOG] [AQ] Swapchain: Clearing
[LOG] New aquamarine output with name HDMI-A-1
[LOG] [AQ] drm: onReady: connector 81
[LOG] [AQ] drm: onReady: connector 85
[LOG] [AQ] drm: onReady: connector 89
[LOG] Running on DRMFD: 29
[LOG] wl_display_add_socket for wayland-1 succeeded with 0
[LOG] Creating the CHyprOpenGLImpl!
[LOG] Supported EGL extensions: (16) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_explicit_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
[LOG] eglDeviceFromDRMFD: Using device /dev/dri/card0
[ERR] [EGL] Command eglInitialize errored out with EGL_NOT_INITIALIZED (0x12289): DRI2: failed to create screen
[ERR] [EGL] Command eglInitialize errored out with EGL_NOT_INITIALIZED (0x12289): DRI2: failed to create screen
[ERR] [EGL] Command eglInitialize errored out with EGL_NOT_INITIALIZED (0x12289): DRI2: failed to create screen
[ERR] [EGL] Command eglInitialize errored out with EGL_NOT_INITIALIZED (0x12289): eglInitialize
[CRITICAL]
==========================================================================================
ASSERTION FAILED!

EGL: failed to initialize a platform display

at: line 112 in OpenGL.cpp

this is a problem with your gpu driver

I'm having the same problem when reverting from the nvidia propretary driver to the nouveau, but I didn't find a fix yet. Any help pls?


Plugin Validation Mode

SHIELD plugins now have a new mode to support, validate, which is
repsonsible for reading a SHIELD endpoint and verifying that the
required parameters are present.  Plugins may opt to perform whatever
validations they see fit, including basic presence checks to more
in-depth value assertions (i.e. S3's signature_version must be either 2
or 4).
Each compiled plugin can now be told to run the validate subcommand
which will trigger this new behavior, print (hopefully helpful)
information to the screen, and exit 0 if the endpoint is valid.
All built-in plugins have been updated to perform the necessary checks,
based on existing logic.

Here's a few sample runs from the S3 plugin, which demonstrates the most complicated of validations (sadly, color doesn't translate, but you get the idea)
Complete failure:
$ ./s3 validate -e '{}'
✗ s3_host              No 's3_host' key specified in the endpoint json
✗ access_key_id        No 'access_key_id' key specified in the endpoint json
✗ secret_access_key    No 'secret_access_key' key specified in the endpoint json
✗ bucket               No 'bucket' key specified in the endpoint json
✗ prefix               No 'prefix' key specified in the endpoint json
✓ signature_version    4
✗ skip_ssl_validation  No 'skip_ssl_validation' key specified in the endpoint json
s3: invalid configuration

Mostly working, just got a bad signature_version:
$ ./s3 validate -e '{"s3_host":"s3.amazonaws.com","access_key_id":"AKI123","secret_access_key":"shhhhh","prefix":"core-","bucket":"backups","skip_ssl_validation":false,"signature_version":"3"}'
✓ s3_host              s3.amazonaws.com
✓ access_key_id        AKI123
✓ secret_access_key    shhhhh
✓ bucket               backups
✓ prefix               core-
✗ signature_version    Unexpected signature version '3' found (expecting '2' or '4')
✓ skip_ssl_validation  no, SSL WILL be validated
s3: invalid configuration

Third time's a charm:
$ ./s3 validate -e '{"s3_host":"s3.amazonaws.com","access_key_id":"AKI123","secret_access_key":"shhhhh","prefix":"core-","bucket":"backups","skip_ssl_validation":false}'
✓ s3_host              s3.amazonaws.com
✓ access_key_id        AKI123
✓ secret_access_key    shhhhh
✓ bucket               backups
✓ prefix               core-
✓ signature_version    4
✓ skip_ssl_validation  no, SSL WILL be validated


Epic: Negotiation Card UI Improvements

This epic covers work on refactoring MLTE negotiation card for multiple improvements.

#403

#453
#454

#458
#459

Fixed by #448


Feature/company-employees/groups

Please update Describe label as we documented in ISSUE-TEMPLATE.md.


Add an option to stop proxy and handle response manually

Describe the feature you'd love to see
We are working with a "proxy and cache" feature, in which we'd like to proxy a request the first time it appears and cache the response, after then we immediately respond from cache and not to proxy it to target server
After some investigation we find no solution to stop request proxy by a custom function, even though we can handle response in onProxyRes, the proxy requests are always sent
We expect to see an onBeforeProxy(req, res, next) option to determine whether to forward to proxy or handle it manually
If this is acceptable, I'd like to create a PR for this
Additional context (optional)
No response

Hi,
If you are working with express; middlewares can be chained in express.
In your case you can add a custom caching middleware in front of the proxy middleware to implement the behaviour you just described.
IMHO. This way you can keep middlewares simple and compose the behaviour you want for your application.

Thanks for explanation, I'm doing exactly what you suggested by restrict our webpack's proxy config to a very limited set.
It's my mistake to thinking webpack's proxy config parsing as a part of http-proxy-middleware, it seems I should handle this in webpack or somewhere else.

Think you could look at setting up your own middlewares and configure your own proxy+caching functionality.
https://webpack.js.org/configuration/dev-server/#devserversetupmiddlewares


feat(headless): allow algorithm choice for Range Facets (equiprobable vs even distribution)

https://coveord.atlassian.net/browse/KIT-571

I made the updateRangeFacetRangeAlgorithm available for both numeric and date facets but I am unsure if this was needed/required.

Have you tested the full loop to see if it works? Once it's an option is can be added to the atomic range facets 🙂

for rangeAlgorithm: 'even':

for rangeAlgorithm: 'equiprobable':

You can delete the readmes to resolve conflicts, we removed them recently on "master"

One thing that is missing is a good explanation of what even vs equiprobable means, so user can take an informed decision. Pinging @dlutzCoveo for this one!


Bump Steelseries Engine to v3.6.4

Pretty straightforward.

Thank you for the contribution. It was merged directly as 968265d9214f000dcb1c81c6591cf53963a467fc to keep commit history cleaner. Your contribution is still credited to you.


2.0.1-development crash report

I'm using 2.0.1-development for linux x64.  I'm having an issue w/ periodic crashes of PhantomJS.  I was going to convert to a stack trace, but  there's not 2.0 "symbols" file here: https://bitbucket.org/ariya/phantomjs/downloads
I've attached the dump here (GitHub won't allow me to attache the .dmp alone): http://ge.tt/6WrZe8J2/v/0
I'm seriously at a loss here.. I'm not seeing any memory spikes or CPU spikes on the box.  Is there a way to see error logs for PhantomJS?  Does it maintain a log?

I'm seeing TONS of crash reports being added here w/ very little feedback.
Is anyone maintaining this project anymore?

If you use your own version (compiled from the source), you have to compile it with debug info to get debug symbols.

Arg.. I did try to compile my own, but ran into so many headaches, I ended up just using one that someone else had compiled.  Really wish the binaries for Linux would get finalized..

@RavenHursT said:

I'm seeing TONS of crash reports being added here w/ very little feedback. Is anyone maintaining this project anymore?

We do have a bit of a manpower problem right now.  And most crash reports turn out to be bugs in Qt and Webkit, which we can't do anything about directly.  And we need to rewrite the crash reporting instructions to make it clear that a crash dump isn't enough for us to go on -- we also need some way of making the crash happen for ourselves.
The good news is, we are actively working on keeping up with Qt and Webkit upstream releases, and every one of those fixes a bunch of the crasher bugs :-)

Thank you @zackw for the feedback.
Is there any possibility that 2.x linux binaries (as well as debug versions) might be available soon?  I'm having crashes every week w/ this thing, and I can't give any debug info because doing a proper build is so complicated at this point...


Incorrect at_row length for multi-channel image such as CV_8UC3?

Hi thanks for the lib! For example I have an image of CV_8UC3 type, and of size 500x400. Then mat.at_row::<u8>(0) seems to return a slice of type u8 and length 400. However, since it has 3 channels, it seems that we should return a slice of 400x3 = 1200.

Oh I see: should use Vec3.


publicDir value of '.' or '' copies the entire project root into dist on build

Phew, what a bug

For context, I accidentally changed publicDir to '.' and '' thinking I was changing what is actually build.assetsDir. Not sure if this is something vite let's happen, or if it's caused by Cayo. I kind of want to prevent it, if it is a Vite issue.


Removed mentions of documentup website

Since documentup website is no longer available, I have removed all mentions of it in README.md and RELEASE.md
Current documentation is generated using npm run gendocs to pull annotated comments and append in README.md.
npm test and npm run lint passed.
Let me know if you have any questions.

This was also discussed in issue 1049: https://github.com/shelljs/shelljs/issues/1049

Codecov Report

Merging #1056 (672ea34) into master (d0a4516) will decrease coverage by 0.82%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1056      +/-   ##
==========================================
- Coverage   97.14%   96.32%   -0.83%
==========================================
  Files          35       35
  Lines        1332     1332
==========================================
- Hits         1294     1283      -11
- Misses         38       49      +11

Impacted Files
Coverage Δ

src/which.js
80.00% <0.00%> (-15.00%)
:arrow_down:

src/cmd.js
94.11% <0.00%> (-5.89%)
:arrow_down:

src/find.js
95.45% <0.00%> (-4.55%)
:arrow_down:

src/ln.js
96.87% <0.00%> (-3.13%)
:arrow_down:

src/ls.js
97.67% <0.00%> (-2.33%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks for approving my pull request!
It seems that merging is blocked due to the requirement for all signed commits. Do I need to rebase and resign my commits to merge this pull request?
Thanks :)

Ah, my apologies. I was just waiting for the unit tests to pass but forgot to come back to this. All looks good!


Cache issue/timing issue with CompatibilityAccessManager when calling configure immediately after configuring the normal Purchases SDK.

In sandbox mode, everything works as expected, but in production, it seems that ‘CompatibilityAccessManager’ cannot convert old users without reopening the app. So my guess is that
‘func isActive(entitlement: String, result: @escaping ((Bool, Purchases.PurchaserInfo?) -> Void))’
works only after some delay or 2nd time in production.
I configure entitlements on ‘appDidFinishLaunch’ to grand access with this method:
‘func configure(entitlements: [BackwardsCompatibilityEntitlement], completion: ((Purchases.PurchaserInfo?) -> Void)? = nil)’.
Also, I set ‘PurchasesDelegate’ to catch updates and configure UI.

Can you confirm you're only checking for entitlements via CompatibilityAccessManager:
CompatibilityAccessManager.shared.isActive(entitlement: "entitlement") { (isActive, purchaserInfo) in
  // isActive is true if the user has access via RevenueCat or with registered build versions
}

And not via the default Purchases SDK property?
PurchaserInfo.entitlements["entitlement"].isActive

CompatibilityAccessManager is a local, client side check and doesn't change anything on RevenueCat's side, so you can't use the default properties on PurchaserInfo. In your case, it's likely only working after the cache expires or after the app is relaunched. In which case, you might have the versions registered incorrectly.
If indeed this is a timing issue, a workaround would be to manually call Purchases.shared.syncPurchases or .restoreTransactions at another time in your app's lifecycle, when we know that Purchases has been configured and PurchaserInfo has already been returned.
You can see the exact logic for when CompatibilityAccessManager tries to sync a missing receipt here, that you can replicate in your own flow: https://github.com/codykerns/PurchasesHelper/blob/master/Sources/PurchasesHelper/CompatibilityAccessManager.swift#L50
Since CompatibilityAccessManager requires a receipt to be synced with RevenueCat in order to work (since we rely on the originalApplicationVersion in PurchaserInfo), we just need to try and get that user's receipt synced ASAP. If it's not working from the configure method, try and get purchases synced as soon as possible.
Worst case scenario, you should communicate to your users in your paywall that if they are a previously paid user they need to restore purchases, and provide a button that calls restoreTransactions.

I just published v0.2.0, which adds additional features including a new check for originalPurchaseDate, improves the ReadMe for clarity, as well as improves the logging of CompatibilityAccessManager. Take a look at the new version and see if things are a bit more clear for how to implement this package.
Closing this for now, feel free to re-open if you're still have issues.


Improvement: Make audio description selectable on the details screen

🎩 What is the problem?
Currently, the content/description displayed in the details screen is not selectable, therefore the user can't copy relevant information like links.
:tophat: How was this resolved?
Implementing SelectionContainer and wrapping it by creating a new composable: SelectableEmphasisText

Thanks, @soyjimmysaenz!!
It works like a charm!


Feature/restub snapshot

Description
Add test and then check for re-stubbing workflow with frozen versions
Issue
https://github.com/dockstore/dockstore/issues/4717
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future

thought: may be a little aggressive: maybe only if the snapshot has been DOIed or ORCIDed?


Calligraphy does not work with NavigationView

I tried to change it using Calligraphy configs but didn't work
CalligraphyConfig.initDefault(new CalligraphyConfig.Builder()
                            .setDefaultFontPath("fonts/Roboto-RobotoRegular.ttf")
                           .setFontAttrId(R.attr.fontPath)
                            .build());
Also, I tried to get the menu from the NavigationView navigationView.getMenu() and use CalligraphyTypefaceSpan to set the title with no luck!
Is there anyway to achieve that?
Thanks in advance

I think the NavigationView isn't a textview. and doesn't inflate it's children.
Need to nudge Goog to make there support lib stuff use the LayoutInflater.

I like this library a lot. And it works great. But can't get the right fonts in the NavigationView either.
I made a small app, to show that it isn't working. Items in a NavigationView are inflated and CalligraphyContextWrapper is used, but somehow the font isn't changed.

https://github.com/ajdevries/android-navigation

@chrisjenx any clue what is happening here?
I'm getting the fontPath value res/drawable/list_selected_background.xml in https://github.com/chrisjenx/Calligraphy/blob/master/calligraphy/src/main/java/uk/co/chrisjenx/calligraphy/CalligraphyFactory.java#L192
When the NavigationMenuPresenter is inflating his Views

Guessing there could be a resource conflict, never seen this before. :/
On Tue, 29 Mar 2016, 19:06 Albert-Jan de Vries<EMAIL_ADDRESS>wrote:

I like this library a lot. And it works great. But can't get the right
fonts in the NavigationView either.
I made a small app, to show that it isn't working. Items in a
NavigationView are inflated and CalligraphyContextWrapper is used, but
somehow the font isn't changed.

https://github.com/ajdevries/android-navigation

@chrisjenx https://github.com/chrisjenx any clue what is happening here?
I'm getting the fontPath value res/drawable/list_selected_background.xml
in
https://github.com/chrisjenx/Calligraphy/blob/master/calligraphy/src/main/java/uk/co/chrisjenx/calligraphy/CalligraphyFactory.java#L192
When the NavigationMenuPresenter is inflating his Views
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/chrisjenx/Calligraphy/issues/258#issuecomment-203030491

It would be great if you have a solution for this... Need this one for the project I'm working on. If I can help please let me know. A work around is also an option.
Debugging it many times today with my larger Android project, and isolated it to this small project.

OK thanks for isolating, that helps. Have you tried the snapshot?
Thanks
On Tue, 29 Mar 2016, 19:33 Albert-Jan de Vries<EMAIL_ADDRESS>wrote:

It would be great if you have a solution for this... Need this one for the
project I'm working on. If I can help please let me know. A work around is
also an option.
Debugging it many times today with my larger Android project, and isolated
it to this small project.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/chrisjenx/Calligraphy/issues/258#issuecomment-203040660

Yes. You can see it in the build file. https://github.com/ajdevries/android-navigation/blob/master/app/build.gradle#L26

I have custom font with calligraphy working a-ok with <android.support.design.widget.NavigationView /> I wonder if there's an issue with<EMAIL_ADDRESS>I am not using that, instead app:itemTextColor="@color/textColorBright". I've found with other android.support.design views the TextAppearance screws thiings up.

Okay... And can you tell me how you changed the type face in the NavigationView?

@ajdevries  Sorry i wasn't clear. By using the default config.
init CalligraphyConfig in Application object
CalligraphyConfig.initDefault(new CalligraphyConfig.Builder()
                .setDefaultFontPath(getString(R.string.font_path_regular))
                .setFontAttrId(R.attr.fontPath)
                .build());

And attaching base context in activity
 @Override
    protected void attachBaseContext(Context newBase) {
        super.attachBaseContext(CalligraphyContextWrapper.wrap(newBase));
    }

Hmm, yeah. Maybe that is an solution, but for my current project difficult, because I'm using different fonts. When there is time I'll have a look what is happening here.

Hi @chrisjenx its CheckedTextView, and inflated from xml file. There is no workarounds in the code.

This is my workaround for now;
public class TypefaceSpan extends MetricAffectingSpan {
  private final Typeface typeface;

  public TypefaceSpan(Typeface typeface) {
    this.typeface = typeface;
  }

  private static void apply(Paint paint, Typeface typeface) {
    paint.setTypeface(typeface);
  }

  @Override
  public void updateDrawState(TextPaint textPaint) {
    apply(textPaint, typeface);
  }

  @Override
  public void updateMeasureState(TextPaint textPaint) {
    apply(textPaint, typeface);
  }
}

private void changeFont() {
	Menu menu = navigationView.getMenu();
	Typeface typeface = Typeface.createFromAsset(activity.getAssets(), "fonts/customFont.ttf");

	for (int i = 0; i < menu.size(); i++) {
		MenuItem menuItem = menu.getItem(i);

			if (menuItem != null) {
			SpannableString spannableString = new SpannableString(menuItem.getTitle());
			spannableString.setSpan(new TypefaceSpan(typeface), 0, spannableString.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);

			menuItem.setTitle(spannableString);
		}
	}
}

You know there is already a typeface span in Calligraphy?
On Wed, 30 Mar 2016, 22:50 Hisham Ghatasheh<EMAIL_ADDRESS>wrote:

This is my workaround for now;
public class TypefaceSpan extends MetricAffectingSpan {
private final Typeface typeface;
public TypefaceSpan(Typeface typeface) {
this.typeface = typeface;
}
private static void apply(Paint paint, Typeface typeface) {
paint.setTypeface(typeface);
}
@Override
public void updateDrawState(TextPaint textPaint) {
apply(textPaint, typeface);
}
@Override
public void updateMeasureState(TextPaint textPaint) {
apply(textPaint, typeface);
}
}
private void changeFont() {
Menu menu = navigationView.getMenu();
Typeface typeface = Typeface.createFromAsset(activity.getAssets(), "fonts/customFont.ttf");
for (int i = 0; i < menu.size(); i++) {
    MenuItem menuItem = menu.getItem(i);

        if (menuItem != null) {
        SpannableString spannableString = new SpannableString(menuItem.getTitle());
        spannableString.setSpan(new TypefaceSpan(typeface), 0, spannableString.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);

        menuItem.setTitle(spannableString);
    }
}

}
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/chrisjenx/Calligraphy/issues/258#issuecomment-203650352

Extending the NavigationView and wrapping it's context on the constructor, I've managed to change the font only on the menu itens that DON'T have a image.

On RED, the wrong font, on GREEN, the right one
here's the menu.xml:
<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android">
    <item
        android:id="@+id/nav_account"
        android:icon="@drawable/ic_navigationdrawer_account"
        android:title="Account" />
    <item android:title="HARDWARE">
        <menu>
            <item
                android:id="@+id/nav_connect"
                android:icon="@drawable/ic_navigationdrawer_connect_hardware"
                android:title="Connect Hardware" />
            <item
                android:id="@+id/nav_calibrate"
                android:icon="@drawable/ic_navigationdrawer_calibrate_beta_monitor"
                android:title="Calibrate Beta Monitor" />
        </menu>
    </item>
</menu>

Manage to get it working with the changeFont method posted by @ghatasheh, but I've used the CalligraphyTypefaceSpan instead of the custom TypefaceSpan. But it's a workarround

Thanks for this; it has been taxing me all day.  I used the Calligraphy Typeface Span also.  I iterate through the drawer menu items and send them to this method below.  (Sorry, haven't worked out how to indent code in these forums yet)
   private void applyFontToMenuItem(MenuItem mi) {         Typeface font = Typeface.createFromAsset(getAssets(), "fonts/TeXGyreAdventor-Bold.ttf");         SpannableString fontableTitle = new SpannableString(mi.getTitle());         fontableTitle.setSpan(new CalligraphyTypefaceSpan(font), 0, fontableTitle.length(), Spannable.SPAN_INCLUSIVE_INCLUSIVE);         mi.setTitle(fontableTitle);     }

as said bay @scottyab after use the<EMAIL_ADDRESS>the font went do default android value. I tried the SpannableString but didn't work. Any workaround?

Scotty also put a work around on here. Does that not work?
On Mon, 17 Oct 2016, 08:28 jzeferino<EMAIL_ADDRESS>wrote:

as said bay @scottyab https://github.com/scottyab after use the
<EMAIL_ADDRESS>the font went do
default android value. I tried the SpannableString but didn't work. Any
workaround?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrisjenx/Calligraphy/issues/258#issuecomment-254223272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHRsfoXfTquOpTUnmh7CpkFDLj0WdZDks5q04X4gaJpZM4Hs1yG
.

@chrisjenx what @scottyab said is that when using the<EMAIL_ADDRESS>the font DON'T use the calligraphy font. It uses the default. In my case I need to use the app:itemTextAppearance.

I ended-up hacking the drawer menu to force the font when the DrawerStateChanged:
See the font here:
https://gist.github.com/jzeferino/797c5e6b72c666b6f87969f6146a2a6e


perf: avoid unnecessary buffer copy

The pending array is emptied every iteration so just pass the file chunk directly into the rabin chunker instead.

Fixes #35


More strict moderation on issues page

Hello,
Flutter github issues are a mix of general questions about how to do X, bug reports, idea suggestions, etc. If you follow the Flutter issues, you'll get more than 100 notifications per day.
Many issues are just questions that would be more appropriate for a support focused platform like StackOverflow. Redirecting general questions there would encourage community involvement, improve discoverability and bring some peace to current issues. It would keep the latter focused on bugs, ideas and development.
So what do you think about being more strict about those issues, and encourage to post on stackoverflow (+ close issue)? Or is the general support intended to be done here as well?

I prefer that there is a strict separation.    Real issues/feature suggestions here.    Support StackOverflow, Gitter, google groups, etc

Fastlane uses a bot https://github.com/fastlane/issue-bot
Maybe we can auto-tag some of the how-to questions.

Surprised there's an actual API for creating questions on stackoverflow https://api.stackexchange.com/docs/create-question

As a general rule we consider bugs of the form "How do I..." to be documentation bugs (as in, our documentation needs work if it didn't answer the question). While Stack Overflow is important, our project should not be dependent on it to be usable.

We have a clearly defined triage process now. https://github.com/flutter/flutter/wiki/Triage


fix: Fix omission of change to change ValidatorSet to VoterSet

Description

Corresponding to the omission of change from the validator set to the voter set during version upgrade work.
This commit change was not reflected.
https://github.com/line/ostracon/commit/25fe25c5a5f92f734b8236007916b065c7bb8494

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(search): add indexing for developer news

Hi @scissorsneedfoodtoo,
Great start, I am just going to dump my thoughts here from an architectural perspective. We can pair on this. I have gone ahead and created a separate branch for this to land later on master.
Here are few key considerations:

[ ] We really do not need the scraping, we should just use the Ghost Content API to get whatever we need to create the indexes.
[ ] We also would want to run the script in the build phase or after the build phase in the CI/CD pipeline.
[ ] Finally we would want to make this multilingual for supporting languages.


Docs changes for SAM, Channels Last, Noop, Selective Backdrop

Fixes #407

Seems to be failing linting


Text edits for algo change

Should let this accumulate corrections before merging.
Planned for displayed text, etc. Nothing that affects function.

The text editing itself has fallen hopelessly behind, and equihash-as-is probably isn't in our future.
Closing.