Developer Portal not available

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
The content of the the fastfile includes the following :
match(type:"appstore")
During builds it can take 2-3 attempts to complete the match operation through all App IDs as the following error appears at intermittent intervals.
[12:47:21]: Installing provisioning profile...
[12:47:22]: Installing provisioning profile...
[12:47:23]: An error occured while verifying your certificates and profiles with the Apple Developer Portal.
[12:47:23]: If you already have your certificates stored in git, you can run match in readonly mode
[12:47:23]: to just install the certificates and profiles without accessing the Dev Portal.
[12:47:23]: To do so, just pass readonly: true to your match call.
[12:47:23]: 🔒  Successfully encrypted certificates repo
Difficult to reproduce.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

[12:47:25]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
/usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/spaceship/lib/spaceship/client.rb:453:in `parse_response': [!]  (Spaceship::Client::UnexpectedResponse)

resultCode
503
userString
The Apple Developer website is undergoing maintenance. For details, visit developer.apple.com/system-status.
resultString
The Apple Developer website is undergoing maintenance. For details, visit developer.apple.com/system-status.
httpCode
503
userLocale
en_US

from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/spaceship/lib/spaceship/portal/portal_client.rb:464:in `provisioning_profiles'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/spaceship/lib/spaceship/portal/provisioning_profile.rb:263:in `all'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/spaceship_ensure.rb:54:in `profile_exists'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:142:in `fetch_provisioning_profile'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:40:in `block (2 levels) in run'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:39:in `loop'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:39:in `block in run'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:38:in `each'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/match/lib/match/runner.rb:38:in `run'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/actions/match.rb:8:in `run'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:243:in `block (2 levels) in execute_action'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:221:in `block in execute_action'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:217:in `chdir'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:217:in `execute_action'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:139:in `trigger_action_by_name'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
from Fastfile:62:in `block (2 levels) in parsing_binding'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/lane.rb:33:in `call'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/commands_generator.rb:105:in `block (2 levels) in run'
from /usr/local/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
from /usr/local/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/command.rb:153:in `run'
from /usr/local/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/runner.rb:446:in `run_active_command'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
from /usr/local/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/delegates.rb:15:in `run!'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/commands_generator.rb:302:in `run'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/fastlane/lib/fastlane/cli_tools_distributor.rb:63:in `take_off'
from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.15.0/bin/fastlane:15:in `<top (required)>'
from /usr/local/bin/fastlane:22:in `load'
from /usr/local/bin/fastlane:22:in `<main>'

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_AU.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.3.0"

default_platform :ios

ENV["XCODEPROJECT"] = "Solution.xcodeproj"
ENV["WORKSPACE"] = "Solution.xcworspace"

platform :ios do
  before_all do
    UI.message "Initialising lanes"
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  lane :inc_major do
    increment_version_number(bump_type: "major")
    increment_build_number(build_number: "0")
  end

  lane :inc_minor do
    increment_version_number(bump_type: "minor")
    increment_build_number(build_number: "0")
  end

  lane :inc_patch do
    increment_version_number(bump_type: "patch")
    increment_build_number(build_number: "0")
  end

  lane :certificates do
    match(type: "development", readonly: true)
    match(type: "appstore", readonly: true)
  end

  desc "Do a build for testing, no submission to testflight"
  lane :on_commit do |options|
    cocoapods
    #match(type: "appstore")
    gym(scheme: "V2 - Demo")
  end

  desc "Do a build for testing, no submission to testflight"
  lane :daily do |options|
    cocoapods
    #match(type: "appstore")
    increment_build_number
    gym(scheme: "V2 - Demo")
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do |options|
    cocoapods

    #match(type: "appstore") # more information: https://codesigning.guide
    increment_build_number
    gym(scheme: "V2 - Demo") # Build your app - more options available

    if options[:skip_submission]
      UI.message "Skipping submission, will only upload IPA"
      pilot(skip_submission: "true")
    else
      UI.message "Will submit and distribute IPA"
      pilot
    end

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    cocoapods

    # match(type: "appstore")
    # snapshot
    gym(scheme: "V2 - Demo") # Build your app - more options available
    deliver(force: true)
    # frameit
  end

  # You can define as many lanes as you want

  after_all do |lane|
    UI.message "Lane completed successfully"
    # This block is called, only if the executed lane was successful
    ENV['BUILD_VER'] = get_info_plist_value({key: "CFBundleShortVersionString", path: "Solution/Info.plist"})
    ENV['BUILD_ID']  = get_info_plist_value({key: "CFBundleVersion", path: "Solution/Info.plist"})
    slack(
        message: "Successfully built iOS application \"V2 - Demo\" Ver: #{ENV['BUILD_VER']}. Build: #{ENV['BUILD_ID']}."
    )

    if lane != :on_commit && lane != :certificates
        commit_version_bump(
            message: "Build Complete #{lane}. Ver: #{ENV['BUILD_VER']}. Build: #{ENV['BUILD_ID']}",
            force: true,
            xcodeproj: ENV["XCODEPROJECT"]
        )

        push_to_git_remote
    end
  end

  error do |lane, exception|
  slack(
      message: exception.message,
      success: false
  )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "com.secureone.v2.demo" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "B2NTP3ZB4X"  # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.15.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

i18n
0.8.0

json
1.8.6

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.55.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.4

faraday_middleware
<IP_ADDRESS>

io-console
0.4.6

openssl
2.0.2

generated on: 2017-02-14

Duplicate of https://github.com/fastlane/fastlane/issues/8208 and https://github.com/fastlane/fastlane/issues/8209, unfortunately that's out of our control when Apple's web services are not available.
You can always run match in readonly mode using match(readonly: true), this way it doesn't try to fetch the latest profiles from the Developer Portal.

Why does it fall over like that even when the services are available ? I mean it's not like the service is down for scheduled updates. It's just that the service cannot be connected to at intermittent intervals. I can run it again 5 seconds later and it would work.

@petersuwara It's out of our control that the Apple Developer Services are in maintenance mode, sorry.

@KrauseFx I really appreciate how you guys are very responsive. Great work.
It seems like a very strange and recent issue.
I can see that other are in a much more critical position than us. I have already setup the certificates on our build system so can comment these out for now until we get more clarity.

Sounds good, thanks 👍 Glad to hear you found a temporary solution until all servers are back up again


API Datetime values do not contain timezone

I have noticed that when using Superset REST API returned results do not contain timezone information for attributes related to time.
Expected results
When i query api/v1/dashboard/1 the returned result contain changed_on with timezone information.
Actual results
 'result': {'changed_by': None,
            'changed_by_name': '',
            'changed_by_url': '',
            'changed_on': '2021-05-14T16:15:18.161551',
            'charts': ['Region Filter',

Screenshots
n/a
How to reproduce the bug

Checkout superset code
Run docker-compose -f docker-compose-non-dev.yml up -d
Run below code:

import requests

s = requests.Session()

token = s.post('http://localhost:8088/api/v1/security/login', json=dict(username='admin', password='admin', provider='db'))
token = token.json()['access_token']

print(s.get('http://localhost:8088/api/v1/dashboard/1', headers={'Authorization': f'Bearer {token}'}).json()['result']['changed_on'])

Notice value without timezone info

Environment
(please complete the following information):

superset version: latest master (74473e2ad1975150a6dc578d67aae05de5ba4b02)

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Unfortunately the timestamps are being stored without timezone, for this reason we suggest keeping the server in UTC and basing everything off of that assumption

thanks @nytai , uderstood


[Improvement][official website] pstree should be listed in the documentation as an application that must be installed

*For better global communication, please give priority to using English description, thx! *
Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.
Describe the question
If pstree does not exist on the DS installation machine, the kill operation to stop the process will fail, and the task will continue to run
--pstree 在ds安装机器不存在的话会导致停止进程的kill操作执行失败，任务会继续运行
What are the current deficiencies and the benefits of improvement
The mandatory software on the official website indicates the need for pstree, which can avoid many users stepping on the pit
--在官网的必装软件中提示需要pstree能够避免很多用户踩坑
Which version of DolphinScheduler:
-[all]
Describe alternatives you've considered
Specify the need for pstree in the mandatory software on the official website
--在官网的必装软件中写明需要pstree

I will bring a PR to the official website document

I will bring a PR to the official website document

I've already mentioned a pr

good job


Unable to compile JVM app with the new libraries 1.x.x

Hello!
It's great to see the new updates in PreCompose - thank you! 🙂
I'm trying to test the new updates, but when I try to run the desktop app I'm getting:
Error: LinkageError occurred while loading main class MainKt
        java.lang.UnsupportedClassVersionError: MainKt has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

I'm able to replicate this error in the sample project, by using the remote version of PreCompose, instead of the local one.
Briefly, on sample/desktop/build.gradle.kts file, I've changed the implementation to:
implementation("moe.tlaster:precompose:1.1.4")

I also tried the different versions that you've released starting with 1.0.0.
I tested different Java versions, from older to newer and the only thing that changed was the 55.0 number, which was continuously updated to the one that I was using.
Any idea, on what might be wrong?

I also face the same problem when using IntelliJ with JDK 17, it errors everywhere, but compile seems to be fine.
It seems that JDK 17 is just too early to use, back to JDK 11 is better.

Hi, can you try version 1.1.5, it should fix both of your issues.

Thank you! I'm testing with 1.2.1 and now I'm seeing:
e: Pre-release classes were found in dependencies. Remove them from the classpath, recompile with a release compiler or use '-Xskip-prerelease-check' to suppress errors

I needed to add to the root build.gradle.kts file:
subprojects {
    tasks.withType<KotlinCompile> {
        kotlinOptions {
            jvmTarget = "11"
            freeCompilerArgs += listOf("-Xskip-prerelease-check")
        }
    }
}

And I'm also using Kotlin 1.6.21.
Any idea on what might be causing this @Tlaster ?

I also have the same issue, but currently, I have no idea why, since PreCompose uses Kotlin 1.6.21, I don't know where these Pre-release classes come from.

Hi @Tlaster, that warning comes from the compose-jb. You're using 1.2.0 which is still a pre release version.
Reverting compose-jbto 1.1.1 will probably mitigate the issue, however, it will probably also be advisable revert kotlin to 1.6.10.

Hi @Tlaster, that warning comes from the compose-jb. You're using 1.2.0 which is still a pre release version.
Reverting compose-jb to 1.1.1 will probably mitigate the issue, however, it is probably also advisable to downgrade kotlin to 1.6.10.
Great work on the lib by the way 💪 .
Reverting compose-jb to 1.1.1 seems impossible since it was months ago and compose itself changes a lot. Better wait for a stable release of compose-jb 1.2.0

From what I was able to check, the lib doesn't seem to be using anything that depends from 1.2.0.
The iOS sample, on the other hand, does, since it's using the experimental.
You could have a "stable" release using compose 1.1.1 and kotlin 1.6.10, and exclude the iOS sample, and keep master using with the experimental version.
This way if anyone is interested this for their projects they could do so without having those annoying warnings.

From what I was able to check, the lib doesn't seem to be using anything that depends from 1.2.0.
The iOS sample, on the other hand, does, since it's using the experimental.
You could have a "stable" release using compose 1.1.1 and kotlin 1.6.10, and exclude the iOS sample, and keep master using with the experimental version.
This way if anyone is interested this for their projects they could do so without having those annoying warnings.

This is a good solution, but the version naming is quite difficult since PreCompose is now 1.2.3, which is using compose 1.2.0 and it's a stable version. If I have a release base on 1.1.1, what's the proper version name for this?

Why not keep moving forward. Like you said, the lib itself is stable, it's dependencies are the ones who are not. Basically you're downgrading them to fix a minor issue. So the next release would be 1.2.4.

What would i need to do to make my app work while we're waiting on compose-jb?

The latest version should work without any problem.
Closing as stale


Near real-time streaming (zero latency)

Hi @alfg,
First thanks for this repo :wink:
I try to setup near real-time streaming based on this repo and OBS but I see near 12 seconds of delay in VLC. Have you any suggestions to decrease this delay? I need a lower than 2-second delay for my stream. Is it possible with RTMP at all?

Hi @mnlbox,
This was discussed briefly on #34 by trying different configurations. I think the best we got was around 6 second delay. It might be difficult to obtain a near real-time (or under 2s) delay with HLS output. It could be a limitation on the source project, though: https://github.com/arut/nginx-rtmp-module.
I also saw this discussed on: https://github.com/video-dev/hls.js/issues/807
If you do figure this out, let us know. 😁

Hi @alfg,
Thanks for mention #34
I'm also OK with 6 second delay but it's now near 12 second. How we can reduce this to 6 second without fork this repo and change hls_fragment and hls_playlist_length?

Without forking, you can try mounting and overriding nginx.conf with your localized copy and configuration with those options.

Oh, thanks, and what values you recommend for these two variables?

Maybe try 2s and 6s first and go from there. You can also try removing some of the  variants to reduce encoding time.

Closing for now. Let us know if you find a solution. :)


backend: support shrink db

We want to be able to shrink backend so that people will be able to get back memory/disk space when they remove large number of keys from etcd and are not going to put that much later.
/cc @heyitsanthony @gyuho

lgtm after CI passes. Thanks.

lgtm but maybe call it Defrag instead of Shrink

@heyitsanthony Yea. I can change the name.


Model developers to tune architecture

With "Efficient Neural Architecture Search via Parameter Sharing"
Planned major changes
To better support architecture tuning with ENAS, I'm planning changes to Rafiki's current model training framework:
Replacing budget option MODEL_TRIAL_COUNT with TIME_HOURS
Context
Currently, when application developers create model training jobs, they pass a budget like { 'GPU_COUNT': 1, 'MODEL_TRIAL_COUNT': 20 }, with MODEL_TRIAL_COUNT deciding the no. of trials to conduct for each model template.
Change
Replace MODEL_TRIAL_COUNT option with TIME_HOURS option, which specifies how long the train job should run for. It is a soft time target. At the same time, I'll be reworking the Advisor component (which proposes trials' knobs) such that it is additionally in charge of deciding how many trials to run, when to stop each worker, when to stop the train job, given the budget e.g. GPU_COUNT and TIME_HOURS.
Reasons for change

May not be intuitive to the application developer to specify no. of trials while creating a train job ("how many trials should I put as budget? how long do I need to wait?"), especially if they're not supposed to be familiar with details like how model are trained and tuned. In contrast, TIME_HOURS is more straightforward.
Currently, different models & model tuning strategies would require different no. of trials to be effective. For example, the original ENAS tuning strategy requires maybe (301x150+10+1) trials for sufficient train-eval cycles.
In the future, it gives more flexibility for model tuning strategies at the Advisor component - for example, I'll be adding a new type of tuning strategy that takes all the models with no hyperparameters (e.g. model's knob config only consists of fixed values) and just conducts a single trial (since there's nothing to tune). It's also possible that a new tuning strategy can situationally conduct more/fewer trials based on feedback from workers.

Introducing PolicyKnob
Motivation
I have been integrating ENAS as a new model tuning strategy on Rafiki (e.g. at the Advisor component). If model templates want to do architecture tuning with ENAS, the model's training code needs to switch between different "modes":

During the ENAS architecture search phase, the model needs to alternate between "train my parameters for 1 epoch" and "don't train my parameters; just evaluate on the validation dataset"
At the end of the architecture search, the model needs to switch to training its parameters from scratch with a full-sized architecture stacked with more cells, and train for 310 epochs

Similarly, when you think about a standard hyperparameter tuning procedure, you might want the model to do early-stopping for the first e.g. 100 trials, then conduct a final trial for a full e.g. 300 epochs.
In both architecture tuning & hyperparameter tuning, the model needs to be configured by Rafiki somehow to switch between these "modes" on a trial-basis.
Change
We can model the configuration of a model template for different training "modes" with different model policies. For example, if a model is to engage in policy QUICK_TRAIN, it is to prematurely speed up its training step e.g. by either doing early-stopping or reducing the no. of epochs. The model communicates to Rafiki which policies it supports by adding PolicyKnob(policy_name) to its knob_config. On the other hand, Rafiki configures the activation of the model's policies on a trial-basis by realising the values of PolicyKnobs to either True (activated) or False (not activated).
For example, here is a example knob config of a model which supports the policy QUICK_TRAIN:

Whenever the model is to do early-stopping, Rafiki will pass quick_train=True as part of the model's knobs. Otherwise, the model defaults to full-length training.
Here is my current documentation for PolicyKnob:
'''
    Knob type representing whether a certain policy should be activated, as a boolean.
    E.g. the `QUICK_TRAIN` policy knob decides whether the model should stop model training early, or not.
    Offering the ability to activate different policies can optimize hyperparameter search for your model.
    Activation of all policies default to false.

    =====================       =====================
    **Policy**                  Description
    ---------------------       ---------------------
    ``SHARE_PARAMS``            Whether model supports parameter sharing
    ``QUICK_TRAIN``             Whether model should stop training early in `train()`, e.g. with use of early stopping or reduced no. of epochs
    ``SKIP_TRAIN``              Whether model should skip training its parameters
    ``QUICK_EVAL``              Whether model should stop evaluation early in `evaluate()`, e.g. by evaluating on only a subset of the validation dataset
    ``DOWNSCALE``               Whether a smaller version of the model should be constructed e.g. with fewer layers
    =====================       =====================

'''

@nudles I have added some details & reasoning on the major changes I'm going to make for architecture tuning. Let me know if you have any comments & advice on them!

In terms budget, can we let users to configure either hours or trials?
rename QUICK_TRAIN to EARLY_STOP?
when will DOWNSCALE be used?

Okay, I will keep MODEL_TRIAL_COUNT for backward compatibility as well.
Noted on the suggestion.
DOWNSCALE is used in architecture search for both NAS and ENAS. During the architecture search phase, the model constructed has fewer layers (e.g. 6 layers) to speed up the search, and its performance is somewhat a proxy of actual performance. On the other hand, at the final train phase, the final model trained from scratched is full-sized (e.g. 15 layers), which will be the one that is going to give the best performance.


Few checksums duplicated on databasechangelog, even using clear-schecksums results in duplication and validation errors on updating database

Search first

[X] I searched and no similar issues were found

Description
I started to receive checksum errors on same changesets even not changing them
I used clear-checksums and can uptate database, but sequentially using liquibase status the same not changed changesets fail on checksum validation
I then noted that that changesets were with the same MD5 on databasechangelog, even after clear-checksums + liquibase update over and over
Steps To Reproduce
I don't found a way to reproduce it, I just stucked on liquibase generating the same md5 to 4 changesets only.
Expected/Desired Behavior
Even if changing changets, after using clear-chechsums and update the error was gone
Liquibase Version
4.25.1
Database Vendor & Version
MySQL 5.7
Liquibase Integration
CLI
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
Windows 11
Additional Context
From log:
4 changesets check sum
changelogs/NormalizacoesIniciais.xml::000000019::marcio.monego was: 9:d41d8cd98f00b204e9800998ecf8427e but is now: 9:af7cbc3f01f74e15e79bb5f115733834
changelogs/NormalizacoesIniciais.xml::000000020::marcio.monego was: 9:d41d8cd98f00b204e9800998ecf8427e but is now: 9:7e4c3a0b1c0ee181564bacdc4dca687f
changelogs/NormalizacoesIniciais.xml::000000021::marcio.monego was: 9:d41d8cd98f00b204e9800998ecf8427e but is now: 9:7f0ae63086211a95fe731e8bd2252113
changelogs/NormalizacoesIniciais.xml::000000022::marcio.monego was: 9:d41d8cd98f00b204e9800998ecf8427e but is now: 9:0f99f5012de21d835ecdf20398eaaca8
The body of changesets:

			insert into itensservicos
			(Id_Orçamento, Hst, Deslocamento, Qtde_deslocamento, Valor_deslocamento)
			select Id_Orçamento, Hst, InstalacaoRede, Qtde_Inst, Valor_Inst
			from itensservicos
			where Qtde_Inst > 0;

Migrar pontos de rede

			insert into itensservicos
			(Id_Orçamento, Hst, Deslocamento, Qtde_deslocamento, Valor_deslocamento)
			select Id_Orçamento, Hst, Plantao, Qtde_Plantao, Valor_Plantao
			from itensservicos
			where Qtde_Plantao > 0;

Migrar plantões

			insert into itensservicos
			(Id_Orçamento, Hst, Deslocamento, Qtde_deslocamento, Valor_deslocamento)
			select Id_Orçamento, Hst, Estadia_Alim, Qtde_Estadia, Valor_Estadia
			from itensservicos
			where Qtde_Estadia > 0;

Migrar estadias

Migrar backups

			insert into itensservicos
			(Id_Orçamento, Hst, Deslocamento, Qtde_deslocamento, Valor_deslocamento)
			select Id_Orçamento, Hst, `BackUp`, Qtde_BackUp, Valor_BackUp
			from itensservicos
			where Qtde_BackUp > 0;

Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

Reviewing these changesets I saw that they are the only I had specified the DBMS with dbms attribute, all other changesets are without dbms attribute.
Hope it can help on identifying the issue.
As it's very boring clearing over and over the checksums I added the validCheckSum tag and it stopped the checksum error for now.

Hi @MarcioMonego, it looks like the changesets weren't copied correctly. Could you re-send them?
Thank you,
Tatiana

If you want the entire changesets i can pick them up, but with 4.26.0 the problem has gone!
The initial text i submitted has only the error showing that there are more than one changeset with exactly same checksum, even with sql change been different and changeset id also, as were not a duplicated changeset id validation.

I'm glad it was resolved with 4.26!
I'll be closing this issue, then. Feel free to reach out again if you come across this problem again.


[Bug] Message lost after forcefully stopping broker

Version
Formally reproduced the bug on Apache Pulsar 2.9.3 and 2.10.2. Based on my understanding of the code, it affects all active versions of Pulsar.
Minimal steps to reproduce

Start a Pulsar cluster (I had one in k8s).
Create a topic and subscription bin/pulsar-admin topics create-subscription -s abc test1
Produce a message to that topic bin/pulsar-client produce -m test test1
View internal stats to see broker state and zookeeper state bin/pulsar-admin topics stats-internal test1{
  "entriesAddedCounter" : 1,
  "numberOfEntries" : 1,
  "totalSize" : 54,
  "currentLedgerEntries" : 1,
  "currentLedgerSize" : 54,
  "lastLedgerCreatedTimestamp" : "2022-10-28T03:51:10.805Z",
  "waitingCursorsCount" : 0,
  "pendingAddEntriesCount" : 0,
  "lastConfirmedEntry" : "66:0",
  "state" : "LedgerOpened",
  "ledgers" : [ {
    "ledgerId" : 66,
    "entries" : 0,
    "size" : 0,
    "offloaded" : false,
    "underReplicated" : false
  } ],
  "cursors" : {
    "abc" : {
      "markDeletePosition" : "66:-1",
      "readPosition" : "66:0",
      "waitingReadOp" : false,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 0,
      "cursorLedger" : 67,
      "cursorLedgerLastEntry" : 1,
      "individuallyDeletedMessages" : "[]",
      "lastLedgerSwitchTimestamp" : "2022-10-28T03:51:10.815Z",
      "state" : "Open",
      "numberOfEntriesSinceFirstNotAckedMessage" : 1,
      "totalNonContiguousDeletedMessagesRange" : 0,
      "subscriptionHavePendingRead" : false,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    }
  },
  "schemaLedgers" : [ ],
  "compactedLedger" : {
    "ledgerId" : -1,
    "entries" : -1,
    "size" : -1,
    "offloaded" : false,
    "underReplicated" : false
  }
}

Kill the broker forcefully. This makes sure that it doesn't have a chance to persist the subscription state to zookeeper.
Restart the broker.
Get the internal stats for the topic: bin/pulsar-admin topics stats-internal test1{
  "entriesAddedCounter" : 0,
  "numberOfEntries" : 1,
  "totalSize" : 54,
  "currentLedgerEntries" : 0,
  "currentLedgerSize" : 0,
  "lastLedgerCreatedTimestamp" : "2022-10-28T03:54:27.951Z",
  "waitingCursorsCount" : 0,
  "pendingAddEntriesCount" : 0,
  "lastConfirmedEntry" : "66:0",
  "state" : "LedgerOpened",
  "ledgers" : [ {
    "ledgerId" : 66,
    "entries" : 1,
    "size" : 54,
    "offloaded" : false,
    "underReplicated" : false
  }, {
    "ledgerId" : 71,
    "entries" : 0,
    "size" : 0,
    "offloaded" : false,
    "underReplicated" : false
  } ],
  "cursors" : {
    "abc" : {
      "markDeletePosition" : "66:0",
      "readPosition" : "66:1",
      "waitingReadOp" : false,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 0,
      "cursorLedger" : 67,
      "cursorLedgerLastEntry" : 1,
      "individuallyDeletedMessages" : "[]",
      "lastLedgerSwitchTimestamp" : "2022-10-28T03:54:27.965Z",
      "state" : "NoLedger",
      "numberOfEntriesSinceFirstNotAckedMessage" : 1,
      "totalNonContiguousDeletedMessagesRange" : 0,
      "subscriptionHavePendingRead" : false,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    }
  },
  "schemaLedgers" : [ ],
  "compactedLedger" : {
    "ledgerId" : -1,
    "entries" : -1,
    "size" : -1,
    "offloaded" : false,
    "underReplicated" : false
  }
}

Get the stats again and see that the ledger for the single message in the backlog is now gone: bin/pulsar-admin topics stats-internal test1{
  "entriesAddedCounter" : 0,
  "numberOfEntries" : 0,
  "totalSize" : 0,
  "currentLedgerEntries" : 0,
  "currentLedgerSize" : 0,
  "lastLedgerCreatedTimestamp" : "2022-10-28T03:54:27.951Z",
  "waitingCursorsCount" : 0,
  "pendingAddEntriesCount" : 0,
  "lastConfirmedEntry" : "66:0",
  "state" : "LedgerOpened",
  "ledgers" : [ {
    "ledgerId" : 71,
    "entries" : 0,
    "size" : 0,
    "offloaded" : false,
    "underReplicated" : false
  } ],
  "cursors" : {
    "abc" : {
      "markDeletePosition" : "66:0",
      "readPosition" : "66:1",
      "waitingReadOp" : false,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 0,
      "cursorLedger" : 67,
      "cursorLedgerLastEntry" : 1,
      "individuallyDeletedMessages" : "[]",
      "lastLedgerSwitchTimestamp" : "2022-10-28T03:54:27.965Z",
      "state" : "NoLedger",
      "numberOfEntriesSinceFirstNotAckedMessage" : 1,
      "totalNonContiguousDeletedMessagesRange" : 0,
      "subscriptionHavePendingRead" : false,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    }
  },
  "schemaLedgers" : [ ],
  "compactedLedger" : {
    "ledgerId" : -1,
    "entries" : -1,
    "size" : -1,
    "offloaded" : false,
    "underReplicated" : false
  }
}

Note that if you run bin/pulsar-client consume -s abc test, you'll just wait forever.

What did you expect to see?
The mark delete position and the read position should not move forward from step 4 to step 7.
What did you see instead?
I lost a message.

I have a fix that I plan to submit soon.

@michaeljmarshall Have you reset the cursor during the test? Both PR #17668 and #18237 have mentioned the issue is related to resetting the cursor. But it looks like the steps don't require the reset cursor operation.


Deployed portfolio website

This is the  link to my deployed portfolio website;

https://lawrahkonwea.github.io/My-portfolio/

Hi @lawrahkonwea 😊,
STATUS: APPROVED! 🥇 💯

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit: 🚀
Congratulations! 🎉
Highlights
✅ Live demo work properly
✅ Project has met all the technical aspects you needed for this project. Keep rocking!
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


'Game' contract does not update balances

Gist 6dcd28d5149f505561ad6cc797b70f57
When Wallet 2 correctly guesses the answer, the Blockchain and Final Balance graphs show different results. Blockchain shows Tx, but Final Balance does not update correctly.

Also, should the 'Lock' action in the game have the 'Value' widget to choose the Currency in the same way the 'payToWallet' action does?
Currently it is simply 'getAda' and I think it should be consistent.

The wallet that makes a guess needs to run the startGame endpoint before the other wallet locks the funds (so that the guessing wallet knows to watch for new transaction outputs at the address). In your action sequence, the startGame action came last (and for wallet 1 instead of wallet 2). So when wallet 2 runs the guess endpoint, it submits an empty transaction because it does not know of any unspent transaction outputs at the game address, and then endpoint unlocks all known outputs. And empty transactions are OK on the mockchain, at least until we have a proper cost model.
So in a way this is the expected behaviour. But I'll change the guess endpoint to log a warning instead of submitting the empty transaction.

I think this would be easier to follow if we renamed:
lock -> offerPrize
startGame -> joinGame


Best strategy for low-latency, high-throuhgput serving in Multi-GPU setups

Hi all, I'm dealing with a scenario where I receive simultaneous requests for processing short audio clips (5-7 seconds) from multiple users, making both latency and throughput crucial.
In this context, which approach would be more effective?

Launching N containers, each with a WhisperModel instance configured for a single GPU.
Running a single container with one WhisperModel instance, but configured for N GPUs.

I'm leaning towards the first option because, when using multiple GPUs, the encoding results must be transferred to the CPU, not knowing which GPU will handle the next job. This transfer might introduce significant overhead, especially since I frequently need to infer short-length audio. Could this overhead be a concern in my scenario? (refer to code below)
def encode(self, features: np.ndarray) -> ctranslate2.StorageView:
        # When the model is running on multiple GPUs, the encoder output should be moved
        # to the CPU since we don't know which GPU will handle the next job.
        to_cpu = self.model.device == "cuda" and len(self.model.device_index) > 1

        features = np.expand_dims(features, 0)
        features = get_ctranslate2_storage(features)

P.S: Is it the same with decoding, where the results have to be moved to the CPU because we don't know which GPU will process the next task? I'm not familiar with C++, so it's challenging to understand. Can you tell me where the code specifies how tasks are distributed across multiple GPUs?
Any insights or suggestions are welcome.

@developer-cade Option 1 is better and simplest.
If I understand correctly, otherwise you state it the encode and decode is run in same GPU you don´t worry about that data overhead.
It is recommended to use two different GPUs (one for encoding and other for decoding) if your GPU memory can not handle the model end to end.
Each audio being 5 seconds and 60X acc. for a GPU such as 4080(24gb for reference), you can expect to transcribe about tens of audios each second per GPU.

Whisper is designed to decode long audio files. It processes audio in 30 second chunks. If your input chunks are less than 30 seconds, you'd better use other neural network architecture like Nvidia Conformer. You'll get same accuracy and 10X speedup. If you still want to use Whisper, your best solution would be to combine chunks into 30 seconds.

I believe that you are wrong, the audios get padded to 30 seconds, with VAD activation the padding is deleted.
Accuracy is more related to the speexh length and sentence length than with audio clip length. That is how the decoder works


Add gpt-4-1106-preview

The preview of the gpt-4 turbo is out:
https://help.openai.com/en/articles/8555510-gpt-4-turbo
It would be great to have support for this model!

This is definitely something we want to support. I don't have time this weekend, but I'm open to reviewing a PR

Merged! Thanks for your help @JosephTLyons


Images created by Jib occasionally causes 400 BAD REQUEST (BLOB_UPLOAD_INVALID) in Red Hat Quay

Environment:

Jib version: 1.6.1
Build tool: Maven 3.5.0
OS: Linux

Description of the issue:
Images created by Jib occasionally causes 400 Bad request in Red Hat Quay. It happens so rarely, it can hardly be categorized as reproducible, and if run again after failing then it works.
We have only seen this occur when running with -Djib.serialize=true
Expected behavior:
Upload success.
Steps to reproduce:

Get our project that uses Jib to upload to QUAY-REGISTRY
Run mvn compile jib:build

jib-maven-plugin Configuration:
<configuration>
    <to>
        <image>QUAY-REGISTRY/image-built-with-jib</image>
    </to>
</configuration>

Log output:
[2019-09-20T09:05:45.888Z] [ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.6.1:build (build_docker_image) on project app-backend: Tried to push BLOB for QUAY-REGISTRY/group/app with digest sha256:1eebb6432678ad971dfd2f732c51595050482f3d7aad8059ed5549f789cd273c but failed because: other: blob upload invalid | If this is a bug, please file an issue at https://github.com/GoogleContainerTools/jib/issues/new: 400 BAD REQUEST
[2019-09-20T09:05:45.888Z] [ERROR] {"errors":[{"code":"BLOB_UPLOAD_INVALID","detail":{},"message":"blob upload invalid"}]}
[2019-09-20T09:05:45.888Z] [ERROR] -> [Help 1]

Additional Information:
Please see https://github.com/GoogleContainerTools/jib/issues/1986, which is also an error with the Jib/Quay combo, and has the first mention of this error. We have not seen this error with the hello world app, but with another app we're developing this has now happened twice this week (out of maybe 100 runs) - so it's time to bring it up as an issue on its own.
@kurtismullins, can you please have a look at this one also?
When Quay says the blob upload is invalid, is it more likely that Jib created an invalid blob or that Quay incorrectly finds it to be invalid?

This is when pushing either 1) layer blobs (either base image layers or application layers); or 2) a container configuration JSON. Jib did attempt pushing a blob.
A blob push in Jib consists of three HTTP requests. It is unclear what was the actual endpoint without more details. It should be one of

initial POST to get the upload location (may or may not be cross-repo blob mount)
PATCH to write a blob to the upload location
PUT with a digest to conclude the push

We have never had a report of BLOB_UPLOAD_INVALID until now, although I won't rule out the possibility that something can go wrong with Jib.
For this kind of troubleshooting, I think the best approach is for Red Hat to check the server code to see under what conditions it can return the BLOB_UPLOAD_INVALID and cross-check that with the server error log.


Dark mode for toast

@eqan there is already dark mode support for the toast, it can be enabled via the Toaster component as follows:
<Toaster theme="dark" />

Like @JayWelsh mentioned, we have dark mode support alerady.

Yeah i found that recently


Fix express integration test

Coverage decreased (-0.002%) to 93.19% when pulling 88a4bb7034fe2dfdff3e23abca21f5932434ffc9 on fix-express-integration-test into bb28c43017915204a4ae41ee1d024668072d97e6 on master.


Color Loop actions require specified brightness for transition to function

It seems that activating or deactivating a Color Loop effect and smoothly transitioning the effect (from on -> off and vice-versa) only works when a brightness is specified within the triggering LightCommand. As an example:
// Method for setting multiple lights to a specified color effect at specified brightness (percentage or byte), and brightnessPercent overrides brightnessByte
public async Task SetLightsEffect(string[] LightIds, ColorEffect effect, double? brightnessPercent, TimeSpan transitionTime = default(TimeSpan), byte? brightnessByte = null,  bool forceLightsOn = true)
{
	LightCommand lc = new LightCommand();

	if (effect == ColorEffect.ColorLoop)
		lc.Effect = Effect.ColorLoop;
	else
		lc.Effect = Effect.None;

	lc.TransitionTime = transitionTime;
	byte? brightness = ProcessBrightness(brightnessPercent, brightnessByte);
	if (brightness != null)
		lc.Brightness = brightness;
	if (forceLightsOn == true)
	{
		if (AnyLightOff(LightIds) == true)
			lc.On = true;
	}
	await this.SendLightCommand(lc, LightIds);
}

If brightnessPercent or brightnessByte are both null the transitions are abrupt (seemingly TimeSpan.Zero), whereas if either has a value then the lc.Brightness parameter is populated in the command and the transition happens as specified.
I'm guessing this is a quirk of the Hue API itself, but I wanted to mention it just in case.

Yes, this is a Hue API quirk. You can check with a tool like Fiddler if all your specified properties are send in the json to the Hue bridge. If you specify a property and it's not in the json, it's a Q42.HueApi library bug, else it's probably the Hue bridge.


only delete node.dataset['command'] if defined

Deleting undefined properties raises an error in Safari
Docs suggest that deleting should raise in some cases in strict mode, but Safari is the only browser that seems to raise for this particular case. I can't actually tell if the documented case for raising should apply or not.
cf jupyter/jupyterlab#749

Wow. This is a safari bug. These properties are configurable properties, so they should not throw. Ugh.

We can use node.removeAttribute('data-command') instead of checking for presence.

My CV used to contain the phrase "intimate knowledge of browser idiosyncrasies"; it doesn't any more.

And if we're going to use removeAttribute might as well change the line above to be node.setAttribute('data-command', item.command) to be consistent.

Thanks for tracking this down!

Updated to use set/removeAttribute.

Thanks! Will merge once CI is finished.

Changes Unknown when pulling fca443a4a6ab3f79575068ec4e59430084c321fa on minrk:delete-only-if-defined into ** on phosphorjs:master**.

Thanks!


Colophon

per https://github.com/riboseinc/isodoc/issues/56#issuecomment-396111244

Implemented in isodoc. It includes the total page count, which is available in Word as a field.

Perfect. Thanks!


Dynamic template

Hi @tyomo4ka
Thank you for your app and work!
Would you be interested by a contribution to have dynamic schema and ui_schema?
The idea is to provide a choice field to the editor. He would choose one template when he creates the model. He then saves it. When he updates, the ReactJSONSchemaField present the form, based on the selected template.
It is somehow similar to https://github.com/The-Politico/django-foreignform
However they are a few things that I don' like in this app:

The form in render via the admin class. Therefore you can't have multiple react-jsonschema field per model (not an issue for me) and you can't have inlined model (this is an issue for me).

The template (schema + ui_schema) is saved in db, in a dedicated model. IMO this is unnecessary, as if you create a new jsonschema, you will probably need some code for the html template (or whatever you need to do with the data). Furthermore this is dangerous because one with the right permissions can very easily change the schemas in db, and destroy some data. At last, it is not versioned and any change requires a data migration to be deploy. Therefore I think that schema belongs to code rather than to db.

I have contributed a PR (update the more recent versions) and have opened an issue to offer to contribute some code to improve the first point (use a widget instead of the admin class to render).  I still have no response so I don't know if they are willing to accept contribution. I am fine with that (it takes to time to review and integrate contributions) but I'd rather not fork a project and contribute to an existing one.

So I prefer your approach of the problem, but I need to be able to let the editor choose which schema he wants for the field. I would make sure that we have some backward compatibility.
Cheers,
Damien

Hi there,
I had no news on the issue so I guess that my contribution is not of interest to the project (I am fine with that). For the record, I have developed the above-described modifications. Should you want to have a look you can find it here:  https://github.com/briefmnews/django-reactive
Please note that this is not backward compatible with your branch because I didn't it backward compatibility. But should you want to merge my code in your code I would be happy to provide a clean PR with backward compatibility.

Hi @cirotix!
I finally found some time to check your code.
Thanks again for offering a contribution to this library, but to be honest, I don't think it will be the best solution to implement this behavior in Django, as you need to save the form in order to update a part of it which is not very convenient for customers.
In my opinion, if you want behavior like this it is better to use one of field which is supported by RJSF. Check this one https://react-jsonschema-form.readthedocs.io/en/latest/dependencies/#dynamic
Of course, both solutions have pros and cons. I like yours because it's easier to understand for Django developers, but usability-wise it looses to the Dynamic fields offered by RJSF.

Hi @tyomo4ka
Too bad that you are not ok with our patch. I think that the one of can be an option for simple case but not really for what we are doing.
I think that the usability limitation that you are mentioning can be easily overcome in javascript, it should be quite trivial to change the form when the template is changed. Actually this is on our roadmap (but not high priority, this is why it is not done yet).
Furthermore, we have actually another improvement in our code that allows you to have several  react-jsonschema fields in one form, or several inlined form. This is not really possible with your code because the id of the field is not dynamic.
We have also other plans for this app, such as providing a route  to serve images saved in base64 in db as if they were files.
However I do understand that this is not your plan to integrate out changes. We will continue to maintain our fork and make the differences clear in the README. If we start to diverge too much we wlll maybe change the name to be able to publishe the app in Pypi (keeping the credit and license to your work of course).


Test against latest 3.0.x version (3.0.7)

Use latest 3.0.x version to run tests against.

Thanks for this :]


UI improvements

I love OmniDB and think the user experience could be improved with some UI changes. With an application like this that I easily spend several hours a day using, even the most minor changes can significantly improve how pleasant it is to work with the application and make it the most usable solution of any DB GUI.

Auto fit the width of columns in the Data view of query output. Only if the column is very wide (for example a huge JSON column) should it be cut off.

 So if you collapse some nodes causing it to need less width then it shrinks, and same when expanding some nodes it should expand to the width it needs
The table details window on the bottom left of the screen should be able to be closed in settings. For the kind of information I need when I'm in the GUI it isn't something I ever look at so it takes up useful screen real estate from the navigator window
Closing a tab shouldn't require a confirmation, at least this should be configurable in settings. We are used to closing tabs without confirmation in browsers, text editors, IDEs, and this should be no different. The only case is if you have unsaved changes then it should prompt if we'd like to save changes
A less intrusive close icon should be used, for example the way browsers do it where the close icon appears only when you mouse over the tab. Because right now I have many distracting bright red "X" icons all over the screen
Be able to customize the font used in the application. I have some nice system fonts that I use in my IDE and other applications and it would be good to be able to use the same one in this application, which is also nice when all applications I use have a consistent font
Don't make all text in the navigator on the left in a bold font, because when everything is bold then nothing stands out in the navigator window and it's harder on the eyes

Hi @rafaelthca ,
Please consider all great suggestsions from @rightaway when performing changes in OmniDB web interface.
Thanks and regards,
William


[ENHANCEMENT] Glossary terms

Glossary terms (#690):

Boolean
Currying
Object-oriented programming
Domain name
DNS

Description

Resolves #(issue number)
What does your PR belong to?

[ ] Website
[ ] Snippets
[x] General / Things regarding the repository (like CI Integration)
[ ] Tests

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking improvement of a snippet)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

Other than the contention point these all look good to me


Issue with webpack - Critical dependency: the request of a dependency is an expression

When doing server less webpack seeing the below errors,
external "fs" 42 bytes {0} [not cacheable]
[2] ./src/splunk.ts 2.13 kB {0} [built]
[3] external "zlib" 42 bytes {0} [not cacheable]
[4] ./src/splunklogger.ts 4.02 kB {0} [built]
[5] external "url" 42 bytes {0} [not cacheable]
[6] ./src 160 bytes {0} [built]
WARNING in ./src/splunklogger.ts
72:25-106 Critical dependency: the request of a dependency is an expression

"webpack": "^3.10.0",
"serverless-webpack": "^2.2.3",

Please use issue template. Servless webpack is not official part of webpack, better create issue in their repo, thanks


Switch to Environment Files

https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@chancancode I don't have merge access :)


ERROR Failed to download on some posts

I get the following error on some media files when downloading:
2022-08-26 14:42:30.3401 ERROR Failed to download https://c10.patreonusercontent.com/4/patreon-media/p/post/63692522/710deacb70e940d999bf2f6032e1e2f0/eyJhIjoxLCJwIjoxfQ%3D%3D/1.png?token-time=1661644800&token-hash=xxxxxxxxxxxxxxxxxxxxxxxxxx: Error while downloading https://c10.patreonusercontent.com/4/patreon-media/p/post/63692522/710deacb70e940d999bf2f6032e1e2f0/eyJhIjoxLCJwIjoxfQ%3D%3D/1.png?token-time=1661644800&token-hash=xxxxxxxxxxxxxxxxxxxxxxxxxx: [63692522] Unable to retrieve file id for https://c10.patreonusercontent.com/4/patreon-media/p/post/63692522/710deacb70e940d999bf2f6032e1e2f0/eyJhIjoxLCJwIjoxfQ%3D%3D/1.png?token-time=1661644800&token-hash=xxxxxxxxxxxxxxxxxxxxxxxxxx, contact developer!
I redacted the token-hash because I'm not sure if this is better to keep private but the 3 token-hash are the same.
26 out of 311 media files failed to download with the same message

I find this happens if the file names are the same on the server.  In this example, I'm guessing that each file is 1.png and the downloader had issues because 1.png has already been saved for that gallery.  The fallback method for naming files doesn't work, so maybe we need an additional option for force download files even if they exist with a -1 or something in the file name.

This is just an issue with the regex expression used to match the url, will be fixed in the future version.

Should be fixed in <IP_ADDRESS>


Naming rules - merged namespaces

Currently we are reporting diagnostics if a namespace does not follow stylecop naming conventions even if the namespace is also defined in metadata. Do we want to make an exception in these cases?

I don't think we need to do that. It seems like an appropriate place to use a source suppression.


Fix dependabot warnings

Description
Update high severity vulnerabilities in dependencies flagged by Dependabot

This PR has:

[x] been self-reviewed.

Removed Security label since this only affects dev dependencies

Removed Security label since this only affects dev dependencies


No exception on dispose

Prevents an exception from being thrown when the slave is stopped. This improves performance and avoids a spurious interruption when debugging with break-on-exception-thrown enabled.

425608e duplicates #2

Yes, the try-catch is still required, since the object may get disposed between the lines
socket = Server.Server.EndAccept(ar);

and
Server.Server.BeginAccept(AcceptCompleted, slave);

Ok. Could you delete 425608e from this banch, replace tabs with 4 spaces in your changes and I'll merge this PR

Done

Done. Note that I deleted 425608e as a public history rewrite (which I understand is acceptable for short-lived feature branches like this).


Disabled ARMC6, enabled MTB_RAK811

Disabled ARMC6 compiler
Added MTB_RAK811 configuration
Imported execute() command from library

Don't we support armc6 as an official compiler target in Mbed OS? Why are we disabling it?

@janjongboom If you want questions/issues to get better visibility (aka require maintainers to route them to the appropriate people), please open a GH issue.
As for the question, somewhat. As of right now, only ARMv8 targets support ARMc6, because they aren't supported in ARMv7.


"const" -> "var" to support es5

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG
Please add a description of your change here, it will be automatically prepended to the CHANGELOG.md file.

Coverage remained the same at 98.784% when pulling 02f3ac9e5ffc3b706ac6089f9e215e2a8ff13d9a on nchen63:patch-1 into 95f890ed15ac503246bd3a96e542259f6f7fd9d3 on ciena-blueplanet:master.

@sandersky can you merge this? It's blocking for me. The es6 import seems ok because webpack handles that


[Task] - ActExp#2 Put this experiment behind a feature flag.

Create a new release flag for this feature and keep it:

turned off - production
turned on - release

Fixed with: https://github.com/appsmithorg/appsmith/pull/29020


Firefox stays inhibited after closing

After playing a video in firefox (and closing it) the lock screen still doesn't execute. It looks like two idle inhibitors are being started, one with owner 1.123 which is firefox and one with owner 1.39 which appears when the video starts but doesn't disappear when closed. Not sure if this is an issue with firefox.
Logs:
[LOG] ScreenSaver inhibit: true dbus message from firefox (owner: :1.123) with content video-playing
[LOG] Inhibit locks: 1
[LOG] Cookie 1337 sent
[LOG] ScreenSaver inhibit: true dbus message from  (owner: :1.39) with content video-playing
[LOG] Inhibit locks: 2
[LOG] Cookie 1338 sent
[LOG] App with owner :1.123 disconnected
[LOG] Inhibit locks: 1

Config (timeouts modified for testing):
general {
    ignore_dbus_inhibit = false
}

general {
    lock_cmd = pidof hyprlock || hyprlock       # avoid starting multiple hyprlock instances.
    before_sleep_cmd = loginctl lock-session
    after_sleep_cmd = hyprctl dispatch dpms on
}

listener {
    timeout = 10
    on-timeout = brightnessctl -s set 1
    on-resume = brightnessctl -r
}

# Screenlock
listener {
    # HYPRLOCK TIMEOUT
    timeout = 30
    # HYPRLOCK ONTIMEOUT
    on-timeout = loginctl lock-session
}

# dpms
listener {
    # DPMS TIMEOUT
    timeout = 35
    # DPMS ONTIMEOUT
    on-timeout = hyprctl dispatch dpms off
    # DPMS ONRESUME
    on-resume = hyprctl dispatch dpms on
}

# Suspend
listener {
    # SUSPEND TIMEOUT
    timeout = 600
    #SUSPEND ONTIMEOUT
    on-timeout = systemctl suspend
}

update hyprilde


explanation about android studio

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Hi @aviral2004, thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


feat: add test sessions url [sc-14214]

I hereby confirm that I followed the code guidelines found at engineering guidelines
Affected Components

[x] CLI
[ ] Create CLI
[ ] Test
[ ] Docs
[ ] Examples
[ ] Other

Notes for the Reviewer

add test-sessions URL to test --record command.

Resolves #[sc-14214]

New Dependency Submission

@nahuelon could you merge it to the test sessions PR from Chris?


Missing regex function in queryvariable builder in golang

it is available on grafana UI v10.2.0 but it is not available to set through code https://github.com/grafana/grafana-foundation-sdk/blame/c194c2c51b5a7f5ac9f865d838411567bb2890d5/go/dashboard/queryvariable_builder_gen.go#L135
I dont understand because i can see the datamodel defined https://github.com/grafana/kind-registry/blob/4798cfda9258a1bde10217a615cddaf8cbe3547e/grafana/v10.2.x/core/dashboard/dashboard.cue#L210
how come it does not show up on on the queryvariable_builder_gen file? 🤔

Hey!
Thanks for opening this issue. This option was excluded by mistake, I opened a PR on our codegen tool to fix that. A fix should land in this repository soon :)


Do you have met with "FailedMount" Errror?

when i make the deployment of comfyui.
"MountVolume.SetUp failed for volume "comfyui-inputs-pv" : rpc error: code = Internal desc = Could not mount "comfyui-inputs-xxxxxxxxxx-us-east-1" at "/var/lib/kubelet/pods/xxxxxxxxxx/volumes/kubernetes.io~csi/comfyui-inputs-pv/mount": Could not check if "/var/lib/kubelet/pods/xxxxxxxxxx/volumes/kubernetes.io~csi/comfyui-inputs-pv/mount" is a mount point: stat /var/lib/kubelet/pods/xxxxxxxxxx/volumes/kubernetes.io~csi/comfyui-inputs-pv/mount: no such file or directory, Failed to read /host/proc/mounts: open /host/proc/mounts: invalid argument"

mentioned in the README https://github.com/aws-samples/comfyui-on-eks?tab=readme-ov-file#55-deploy-comfyui-deployment-and-service
please refer to the issue https://github.com/awslabs/mountpoint-s3-csi-driver/issues/174
mountpoint-s3-csi-driver will fix it in the next release.

really thanks


Externalizing all parameters through .env file

@wmnnd the idea behind this PR is that you don't need to tweak the script file to configure anything such as domains, emails, etc. Just create a .env file and add the required variables and the script will pick it up - for both LetsEncrypt and Nginx. If you don't provide the env file, it functions as before with defaults. Readme docs have also been updated.

@wmnnd Is there any plan to merge this. BTW, thanks for your good work.

Thanks, this is a great improvement! Why it isn't merged so long time?

Good job!

what's up? merge this


Does this package working in 5.6 version ?

Hi.
I want to ask if this package working in laravel 5.6 ?
Thank you in advanced.

I switched to Laravel 5.6 and it seems to run without errors. :)

Yes it does work. I am using it in my Laravel 5.6 project.

@ amrokhudair  What error show you.

@anis-bedhiafi
Did you run : php artisan entrust:migration ?
I had a error:
ReflectionException  : Method Zizaco\Entrust\MigrationCommand::handle() does not exist
So I think entrust is not ready all for Laravel 5.6.
I fixed it by add the following code in class Zizaco\Entrust\MigrationCommand.
and then, it work well
public function handle()
{
$this->fire();
}

@terrywamg I had alot of problems with this package. I don't recommend it. Here is why:
https://laravel-news.com/two-best-roles-permissions-packages
https://github.com/spatie/laravel-permission
https://github.com/JosephSilber/bouncer
I am using laravel-permission with v5.6. It is an awesome package. You should give it a try.

@anis-bedhiafi That article is pretty outdated, for example Bouncer allows syncing for roles and abilities, where in the article that was the main benefit of going with Spatie.

Does Laravel 5.6 use the auto-load features for this package or does the app.php file still need manually updated for the provider and alias?

@gbryant200 it is actually called auto discovery. Starting from v5.5 Laravel will lookup the provider for you. To answer your question, just require the package with composer. Laravel will do the rest.

I have troubles when using the instruction:
Entrust::routeNeedsRole('admin/advanced*', 'owner', Redirect::to('/home'));
InvalidArgumentException:
Attribute [filter] does not exist.
Cause:

Route filters have been deprecated in preference of middleware and was removed entirely with the release of Laravel 5.2 in December 2015

In laravel 5.5 withRole method not working? Is supported withRole method for v5.5 laravel?

@anis-bedhiafi i try laravel-permission it gave me model_id error and any help

@MaherSakka  did you already solved it? I have the same problem too..


Lack of document about consistency.

Page
https://www.alluxio.io/blog/4-different-ways-to-write-to-alluxio/
Summary
A main different between HDFS and S3 is consistency, this blog mentioned it, but details are lack. I hope in the summary table, there could be a column Consistency just like Write Speed and Fault Tolerance.
What I especially want to know is, what consistency Alluxio gives when under storage is S3, and Write Type is one of MUST_CACHE,THROUGH,CACHE_THROUGH,ASYNC_THROUGH, and what will happen when a worker crashes.

Hi @Renkai. These are good questions to be asking. Generally, Alluxio holds a consistent view of all metadata as long as every operation goes through Alluxio.
If you are writing with MUST_CACHE, CACHE_THROUGH or ASYNC_THROUGH the data will be consistent with the metadata as long as the data isn't erased in Alluxio and that the data isn't modified in the underlying storage system through some other means.
Writing with THROUGH, Alluxio's metadata about the file will be consistent with what is written, but when reading, the data may not be able to be retrieved and is dependent upon the UFS consistency guarantees.
However, if you introduce modifications to your underlying UFS without using Alluxio, then things get somewhat murkier. Metadata consistency is going to be determined by how often Alluxio is configured to sync metadata with a UFS via the property alluxio.user.file.metadata.sync.interval. This can be set to something like 1min, 5min, 12h, etc. And so that interval will determine how consistent the master's view of a part of the namespace is.
Do note that that is a client-side property, so you can force a metadata update by setting alluxio.user.file.metadata.sync.interval=0 (There will be a performance penalty).
Workers crashing do not mean much other than possibly imposing a slight performance hit depending on the data it stored. Since the data is expected to be stored in another underlying system (S3, HDFS, etc) the worker will lose its cached data, but the expectation is that the data is still available. A client will simply look to the next available worker to retrieve the data. If there are no workers with the data, it will pick a worker close to the client and stream the data from the worker, which streams the data from the UFS.
I hope these explanation helps answer your questions.

Hi @ZacBlanco , I still have a question that what will happen if I writing with ASYNC_THROUGH and worker crashes after it tell client write success and before it write files to underlying storage.

Sure thing I can clarify that part.
If you are writing with ASYNC_THROUGH and the worker crashes before you persist the data, then you will incur a data loss. However, we do provide a feature we call "durable writes" which will split the write among 1 or more workers simultaneously during the write. This prevents data loss in the case of one or more machines. You can enable durable writes by setting the property  alluxio.user.file.replication.durable. By default it is one, but if you want to ensure the availability of data in the case of a node loss, you may increase this to 2, 3, or more to produce replicas synchronously during the write.

Sure thing I can clarify that part.
If you are writing with ASYNC_THROUGH and the worker crashes before you persist the data, then you will incur a data loss. However, we do provide a feature we call "durable writes" which will split the write among 1 or more workers simultaneously during the write. This prevents data loss in the case of one or more machines. You can enable durable writes by setting the property  alluxio.user.file.replication.durable. By default it is one, but if you want to ensure the availability of data in the case of a node loss, you may increase this to 2, 3, or more to produce replicas synchronously during the write.

Would "durable writes"  lead multi writes same data to UFS ?

No, the data will only be written to the UFS once

@Renkai we have most of our documentation at docs.alluxio.io. I think this information is valuable if it is not already included there. Where do you think is the most intuitive place for this information to live there?

@ZacBlanco I think Apache Flink have a good document hierarchy, especially there are two segments called concepts and internals, they are very useful for experienced engineers to have a quick understand for a new system.

@Renkai  a section on data consistency has been added to Architecture page in documentation. https://github.com/Alluxio/alluxio/blob/bc5929e4fd22d4fc2041c7e372ec30f19906ff84/docs/en/overview/Architecture.md