Making back button work on initial page

I have a paginated and filterable list of entries that I'm tracking the history of via {% do craft.app.response.headers.add('HX-Push', '?page=' ~ page ~ '&' ~ categoriesString) %}
It works just fine, except if the back button is clicked to go back to the first page that was rendered (when {% if sprig.isRequest %} is false). The page doesn't re-render via Sprig because htmx doesn't have history for that page. So the page is what the browser saw last and that often has a popup filtering form expanded.
If I add {'s-trigger': 'load'} to my Sprig component and only render when {% if sprig.isRequest %} is true like in the docs for Dynamic Content it works well, except I can't figure out a way to pass in the initial URL parameters only if the back button was used to load the first page (whether or not that URL has URL parameters).
I also tried adding '{'id': 'grid'}' to my Sprig component and running document.getElementById('grid').dispatchEvent(new Event('refresh')); on page load. This works for the first use of the back button to the initial page.
I just need htmx to know the state of the initial page load and have it loaded into to the browser's history. How can I accomplish this?

It works just fine, except if the back button is clicked to go back to the first page that was rendered (when {% if sprig.isRequest %} is false). The page doesn't re-render via Sprig because htmx doesn't have history for that page. So the page is what the browser saw last and that often has a popup filtering form expanded.

This sounds like native browser behaviour, not sure it can be changed.

I just need htmx to know the state of the initial page load and have it loaded into to the browser's history. How can I accomplish this?

Seeing as though this is a htmx specific question, I'd suggest asking in the htmx github issues.


Testfairy action fails randomly in jenkins

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I'm getting random failures on Testfairy action (possibly timeout) that started last month. The error I'm getting back from logs is:

undefined method `key?' for "":String

I just update fastlane to the latest version and now failures are 90%. can anyone point this error to any open issue or is this by any chance regression issue?
Complete output when running fastlane, including the stack trace and command used

[14:06:02]: Cruising back to lane 'ios build_and_release' 🚘
[14:06:02]: ----------------------------------------
[14:06:02]: --- Step: Switch to ios release lane ---
[14:06:02]: ----------------------------------------
[14:06:02]: Cruising over to lane 'ios release' 🚖
[14:06:02]: -----------------------
[14:06:02]: --- Step: testfairy ---
[14:06:02]: -----------------------
[14:06:02]: Starting with ipa upload to TestFairy...
+------------------------------------+---------------------------------------------------------------------------------------------------+
|                                                              Lane Context                                                              |
+------------------------------------+---------------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                                                |
| PLATFORM_NAME                      | ios                                                                                |
| LANE_NAME                          | ios ci                                                                                |
| VERSION_NUMBER                     | 4.0.0-qa                                                                                |
| SIGH_PROFILE_TYPE                  | ad-hoc                                                                                |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"*********"}          |
| BUILD_NUMBER                       | 1868                                                                                |
| IPA_OUTPUT_PATH                    | /Users/ *********/build/workspace/******************_QA.ipa                                       |
| DSYM_OUTPUT_PATH                   | /Users/ *********/build/workspace/******************_QA.app.dSYM.zip                              |
| XCODEBUILD_ARCHIVE                 | /Users/ *********/Library/Developer/Xcode/Archives/2018-01-30/**_QA 2018-01-30 14.02.01.xcarchive |
| TESTFAIRY_BUILD_URL                | https://app.testfairy.com/projects/*********/builds/***************                               |
+------------------------------------+---------------------------------------------------------------------------------------------------+
[14:06:47]: undefined method `key?' for "":String
+------+----------------------------------------------+-------------+
|                         fastlane summary                          |
+------+----------------------------------------------+-------------+
| Step | Action                                       | Time (in s) |
+------+----------------------------------------------+-------------+
| 1    | Verifying fastlane version                   | 0           |
| 2    | default_platform                             | 0           |
| 3    | Switch to ios build_and_release lane         | 0           |
| 4    | get_version_number                           | 1           |
| 5    | Switch to ios download_signing_identity lane | 0           |
| 6    | match                                        | 13          |
| 7    | match                                        | 7           |
| 8    | Switch to ios build lane                     | 0           |
| 9    | increment_version_number                     | 1           |
| 10   | increment_build_number                       | 1           |
| 11   | gym                                          | 272         |
| 12   | Switch to ios release lane                   | 0           |
| 13   | testfairy                                    | 40          |
| 14   | Switch to ios build lane                     | 0           |
| 15   | increment_version_number                     | 1           |
| 16   | increment_build_number                       | 1           |
| 17   | gym                                          | 184         |
| 18   | Switch to ios release lane                   | 0           |
| 19   | testfairy                                    | 43          |
| 20   | Switch to ios build lane                     | 0           |
| 21   | increment_version_number                     | 1           |
| 22   | increment_build_number                       | 1           |
| 23   | gym                                          | 243         |
| 24   | Switch to ios release lane                   | 0           |
| 💥   | testfairy                                    | 43          |
+------+----------------------------------------------+-------------+
[14:06:47]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡  [!] undefined method `fetch' for #String:0x007fb9844e32d0 (NoMethodError)
https://github.com/fastlane/fastlane/issues/10967 [open] 3 💬
2 weeks ago
➡  Type Checking error: got 'Fixnum' for attribute 'fileEncoding' and undefined method `each' for nil:NilClass
https://github.com/fastlane/fastlane/issues/11016 [open] 2 💬
2 weeks ago
➡  Scan completion issue: undefined method `username=' for Slack::Notifier
https://github.com/fastlane/fastlane/issues/11590 [closed] 6 💬
2 weeks ago
and 46 more at: https://github.com/fastlane/fastlane/search?q=undefined method `key?' for "":String&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
/Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/actions/testfairy.rb:110:in parse_response': [!] undefined method key?' for "":String (NoMethodError)
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/actions/testfairy.rb:97:in run' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:253:in block (2 levels) in execute_action'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:231:in block in execute_action'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:227:in chdir' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:227:in execute_action'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:148:in trigger_action_by_name' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/fast_file.rb:148:in method_missing'
from Fastfile:165:in block (2 levels) in parsing_binding' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/lane.rb:33:in call'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:201:in try_switch_to_lane' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:156:in trigger_action_by_name'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/fast_file.rb:148:in method_missing' 	from Fastfile:93:in block (3 levels) in parsing_binding'
from Fastfile:91:in each' 	from Fastfile:91:in block (2 levels) in parsing_binding'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:201:in try_switch_to_lane'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:156:in trigger_action_by_name' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/fast_file.rb:148:in method_missing'
from Fastfile:80:in block (2 levels) in parsing_binding' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/lane.rb:33:in call'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in call' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in run'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in run_active_command' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in run!'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in run!' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/commands_generator.rb:337:in run'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/commands_generator.rb:42:in start' 	from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/fastlane/lib/fastlane/cli_tools_distributor.rb:98:in take_off'
from /Users/ *********/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.79.0/bin/fastlane:20:in <top (required)>' 	from /Users/ *********/.rbenv/versions/2.4.0/bin/fastlane:22:in load'
from /Users/ *********/.rbenv/versions/2.4.0/bin/fastlane:22:in `'
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.4.0

Bundler?
false

Git
git version 2.14.3 (Apple Git-98)

Installation Source
~/.rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.6 (16G1114)

Ruby Lib Dir
~/.rbenv/versions/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2k  26 Jan 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
require_relative 'support/system'
require_relative 'support/provisioning_profiles'

# This is the minimum version number required.
fastlane_version '2.10.0'
default_platform :ios

platform :ios do
    desc 'Run CI sequence'
    lane :ci do |options|
        puts options
        build_and_release(options)
    end

    desc 'Distribute the app to TestFairy'
    lane :build_and_release do |options|
        release_notes = options[:release_notes] || raise('Error: Must specify release notes')
        build_number = options[:build_number] || ENV['BUILD_NUMBER'] || raise('No build number specified')
        version_number = get_version_number

        download_signing_identity

        ['Production', 'Demo', 'QA', 'Development'].each do |environment|
            build(build_number: build_number, environment: environment, version_number: version_number)
            release(build_number: build_number, environment: environment, release_notes: release_notes)
        end

        build_production_testflight(version_number: version_number, build_number: build_number)
    end

    desc 'Build production for testflight'
    lane :build_production_testflight do |options|
        version_number = options[:version_number] || raise('No version number specified')
        build_number = options[:build_number] || raise('No build number specified')
        increment_version_number(version_number: version_number)
        increment_build_number(build_number: build_number)

        match(type: 'appstore', readonly: true)

        productionIpaFile = " *********_Production.ipa"
        gym(scheme: "Production", clean: true, output_name: productionIpaFile)

        productionBuildDir = "/Users/*********/build/production/#{build_number}"
        Dir.mkdir(productionBuildDir)
        puts "Our directory is #{Dir.pwd}"
        FileUtils.mv("../#{productionIpaFile}", productionBuildDir)
    end

    #####################
    ### Private Lanes ###
    #####################

    private_lane :download_signing_identity do
        ProvisioningProfiles.delete_local

        match(type: 'development', readonly: true)
        match(type: 'adhoc', readonly: true)
    end

    private_lane :build do |options|
        version_number = options[:version_number]
        build_number = options[:build_number]
        environment = options[:environment]

        updated_version_number = version_number + '-' + environment.downcase
        increment_version_number(version_number: updated_version_number)
        increment_build_number(build_number: build_number)

        gym(scheme: "#{environment}",
            clean: true,
            output_name: " *********_#{environment}.ipa",
            include_bitcode: false,
            export_options: {
                compileBitcode: false,
                uploadSymbols: true,
                uploadBitcode: false
            })
    end

    private_lane :release do |options|
        build_number = options[:build_number]
        environment = options[:environment]
        release_notes = options[:release_notes]

        distribution_group = "*********-#{environment.downcase}"
        testfairy_comment = "Environment: #{environment}\nBuild: #{build_number}\nDistribution Group: #{distribution_group}\nRelease Notes:\n#{release_notes}"
        testfairy(api_key: '*********', comment: testfairy_comment, testers_groups: [distribution_group], notify: 'on')
    end
end

`./fastlane/Appfile`
app_identifier "*********" # The bundle identifier of your app
apple_id "*********" # Your Apple email address
team_id "*********"  # 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.79.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
2.3.2

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

commander-fastlane
4.4.5

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

gh_inspector
1.0.3

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

declarative-option
0.1.0

representable
3.0.4

mime-types-data
3.2016.0521

mime-types
3.1

httpclient
2.8.3

google-api-client
0.13.6

openssl
2.0.2

highline
1.7.10

io-console
0.4.6

excon
0.60.0

CFPropertyList
2.3.6

mini_portile2
2.1.0

nokogiri
<IP_ADDRESS>

plist
3.4.0

faraday
0.14.0

faraday_middleware
0.12.2

unf
0.1.4

domain_name
0.5.20170404

os
0.9.6

googleauth
0.6.2

signet
0.8.1

fastimage
2.1.1

json
2.1.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.5.4

bundler
1.16.1

terminal-table
1.8.0

unicode-display_width
1.3.0

generated on: 2018-01-30

Any update on this issue, I added verbose flag to the runner and it is timeout error but the build goes out. Is there any global timeout parameter we can change and fix this?

It looks like it's an issue with testfairy - can you run testfairy directly without fastlane with no issues/

@KrauseFx
Yes, I tried it multiple times and it looks working individually. You are right it looks like Testfairy issue and somehow they delay, but we may be able to set the timeout on this action (down to Faraday) to be able to prevent this failure.

If you want to, feel free to submit a PR for this, however unfortunately we can't invest time in working around bugs of a third party library

I'm working with one of Testfairy's support agent to figure out why is this happening first. If it's something we can control in action level sure I will make a PR.

Awesome, thanks 👍

@farshadtx Heyyyy 👋 Were you able to figure this out with Testfairy's support?

@joshdholtz Yes, they said it was a bug on their end and fixed it. I haven't had that failure for about a month.


ASGARDEX shows 404 error for Cosmos wallet using Keystore

Expected Behavior
200 OK
Current Behavior
404 Not Found
Steps to Reproduce

Open ASGARDEX,
load a Keystore wallet

Possible Solution
Load balance/healthcheck RPC servers using cosmos.directory

https://cosmos.directory/cosmoshub/nodes

this URL is a proxy URL that will do healthchecking for us https://rpc.cosmos.directory/cosmoshub

Fixed by https://github.com/thorchain/asgardex-electron/pull/2375
Unfortunately https://rpc.cosmos.directory/cosmoshub does not work for xchain-cosmos. It does need a single lcd url (not a list of different endpoints).


Marathon timeout of KillTasks

Hello,
We have seen this message when trying to issue a DELETE to the /v2/apps endpoint.
{"message":"Ask timed out on [Actor[akka://marathon/user/MarathonScheduler#2035436870]] after [5000 ms]. Sender[null] sent message of type \"mesosphere.marathon.MarathonSchedulerActor$KillTasks\"."}
To my knowledge this timeout is not configurable. I'm also not able to find specific info in the logs during this occurrence. Any suggestions/comments?

@jolexa
Which version of Marathon do you run?
Under which circumstances do you see this?
Can you add a more complete log?

Version: 1.3.0 (non-DCOS)
Issuing a DELETE to the /v2/apps endpoint. curl -X DELETE localhost:8080/v2/apps/<app id>/tasks/<task id>
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: akka.pattern.AskTimeoutException: Ask timed out on [Actor[akka://marathon/user/MarathonScheduler#-882593002]] after [5000 ms]. Sender[null] sent message of type "mesosphere.marathon.MarathonSchedulerActor$KillTasks".
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:331)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:282)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:286)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:238)
Nov 28 07:10:13 ip-10-224-118-91 marathon[13884]: #011at java.lang.Thread.run(Thread.java:745)

@jolexa : did you get some input about this ? We may encounter the same issue on one cluster.

We experienced this issue as well. I suggest following steps:

Upgrade to 1.3.10 it contains performance optimizations.
Increases metrics timeout. Metrics collected every 10s consumems 10% of CPU.
Disable events callbacks or switch to filtered SSE. Parsing events consumes CPU and deployment events could be pretty big.
Avoid multiple deployments at once, better to squash them in one request.
If you are using HTTP health checks please consider moving to command because they are done on host by Mesos.
Increases timeouts.

@janisz Many thanks for your feedbacks. Do you remember how did you solve the issue at first ?Before doing these short-terms

We still experience this issues. Maybe not exactly on kill action. Marathon still returns 500 with timeout error but we reduced this number. We started with increasing timeouts, not all are documented some of them are marked as INTERNAL TUNING PARAMETER.

OK, in our case it was a side effect of activating features through an isolator which apparently blocked the TASK_FINISHED or TASK_KILLED events from being received by the master, triggering contentions and so on.
Rollbacking those features just resolved the issue, even with hundredth of apps, some of them failing every time etc.
I guess that your environment is heavily loaded :)

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2106. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


[Issue]: WG (openApiV2): Some PUT/POST methods throw "Request body is invalid or missing" error

Description
Some PUT/POST methods throw "Request body is invalid or missing" error, e.g. CreateUser.
We found that these requests sent to the backend have "Content-type: application/xml". (Content-type should be "application/json")
In our specification file, we have "requestBody" like this:
requestBody:
    content:
        application/xml:
            schema:
              $ref: '#/components/schemas/UserSignUp'
        application/json:
            schema:
              $ref: '#/components/schemas/UserSignUp'

There is a workaround to fix it:
It seems that the first content is used. If we remove "application/xml" or we put "application/json" before "application/xml", this issue will be gone.
Reproduction
In description
@wundergraph/sdk: 0.174.0

The fix has been merged, but not released yet.

Released in upstream closing this issue now


Move Word Count Indicator

The location of the word count indicator not only looks bad, but it is definitely not where I would expect it. Usually in the case of reading indicators it's on the top area. Or potentially move it to the left side where there is usually no scroll bar, or on the inside of the viewport or even on the bottom of the screen. It really isn't that noticeable where it is, and I think moving it to the top like the standard or the bottom of the viewport would be the best spot for it.

This is where its been for years without any problem or complaint, and its where it will stay.


Cleanup fails when cache buster is enabled

BlessCSS version:
$ blessc -v
blessc 3.0.3 (CSS Post-Processor) [JavaScript]

Cleanup works (no cache buster):
$ blessc --no-cache-buster big.css target.css
blessc: Source CSS file contained 10,503 selectors. 3 CSS files created.
$ ls target*
target-blessed1.css target-blessed2.css target.css
$ blessc --no-cache-buster small.css target.css
blessc: Source CSS file contained 4,464 selectors. 2 CSS files created. Additional CSS file no longer needed. 1 additional file removed.
$ ls target*
target-blessed1.css target.css

Cleanup fails:
$ blessc big.css target.css
blessc: Source CSS file contained 10,503 selectors. 3 CSS files created.
$ ls target*
target-blessed1.css target-blessed2.css target.css
$ blessc small.css target.css
blessc: Source CSS file contained 4,464 selectors. 2 CSS files created.
$ ls target*
target-blessed1.css target-blessed2.css target.css
$ grep @import target.css
@import url('target-blessed1.css?z=1451559387818');

I don't need the cache buster. I just noticed this bug while I was debugging another problem. See https://github.com/BlessCSS/gulp-bless/issues/20 for details.

I don't need the cache buster. I just noticed this bug while I was debugging another problem. See https://github.com/BlessCSS/gulp-bless/issues/20 for details.


[11.x] Add ability to configure SQLite busy_timeout, journal_mode, and synchronous pragmas

This PR adds optional busy_timeout, journal_mode, and synchronous configuration options to allow setting the corresponding pragmas on SQLite database connections. Together, these three configuration options can improve SQLite's performance enormously.
Background
This SQLite configuration:
PRAGMA busy_timeout = 5000;
PRAGMA journal_mode = WAL;
PRAGMA synchronous = NORMAL;

is becoming the widely recommended default for modern apps because it is orders of magnitude faster than the default setup and far less prone to SQLITE_BUSY errors.

journal_mode configures how transactions are implemented. The default setting, DELETE, uses a rollback journal. Since SQLite 3.7 a WAL mode is available that uses a write ahead log, which is significantly faster and allows concurrent database reads and writes in more scenarios.
busy_timeout configures how long SQLite will wait when a table is locked before returning a SQLITE_BUSY error. The default is 0, which means any attempted concurrent writes will fail immediately. Setting it to a positive integer will make SQLite wait that many milliseconds if the database is locked, which in most cases means that operations will complete with a negligible delay instead of erroring.
synchronous configures how often SQLite flushes the contents of the database to the disk. The default, FULL, writes data to disk more or less immediately when it changes. The NORMAL mode syncs data when necessary but less often, and in combination with WAL mode is much faster, fully consistent, and highly durable. NORMAL is SQLite's recommended setting when used with WAL mode.

Rails and Django both currently support some or all of this functionality. They both have a timeout configuration option, Rails 7.1 defaults to WAL mode and NORMAL, and Django 5.1 (releasing in August) is going to add configuration fields for setting transaction modes and other custom pragmas:

https://guides.rubyonrails.org/configuring.html#configuring-an-sqlite3-database
https://github.com/rails/rails/blob/cacf96ecd053f0a3d64c7bf478dac63f98e6aa6d/activerecord/lib/active_record/connection_adapters/sqlite3_adapter.rb#L81
https://docs.djangoproject.com/en/5.0/ref/databases/#database-is-locked-errors
https://docs.djangoproject.com/en/dev/ref/databases/#setting-pragma-options

More info:

https://www.sqlite.org/wal.html
https://www.sqlite.org/pragma.html#pragma_busy_timeout
https://www.sqlite.org/pragma.html#pragma_journal_mode
https://www.sqlite.org/pragma.html#pragma_synchronous
https://kerkour.com/sqlite-for-servers
https://fractaledmind.github.io/2024/04/15/sqlite-on-rails-the-how-and-why-of-optimal-performance/
https://www.bigbinary.com/blog/rails-7-1-comes-with-an-optimized-default-sqlite3-adapter-connection-configuration
https://gcollazo.com/optimal-sqlite-settings-for-django/

Implementation
I based this on the existing code for setting the foreign_keys pragma, it works exactly the same way except that the new options accept custom values instead of just being on or off.
busy_timeout and synchronous are per-connection settings and have to be set every time Laravel connects to a SQLite database (like the existing foreign_keys pragma), so it makes sense to store them in the config like foreign_keys. journal_mode is a persistent setting and technically only has to be set once, but the implementation is much simpler and more consistent if we just set it on every connection too.
The new configuration options all default to null so that existing apps will be completely unaffected by this change.
Alternatives
How I'm currently doing this:
// in AppServiceProvider.php

public function boot(): void
{
    Event::listen(function (ConnectionEstablished $event) {
        if ($event->connection instanceof SQLiteConnection) {
            $event->connection->statement(<<<SQL
                PRAGMA busy_timeout = 5000;
                PRAGMA journal_mode = WAL;
                PRAGMA synchronous = NORMAL;
                SQL);
        }
    });
}

Future Scope
I'm going to work on a PR for immediate transactions too, which also combine really well with these settings but will have to be implemented differently.

Excuse my ignorance, but aren't we supposed to set journal_mode once for the database file rather than configuring it on every connection?

Excuse my ignorance, but aren't we supposed to set journal_mode once for the database file rather than configuring it on every connection? Doesn't SQLite persist it?

Yeah good question, I addressed that in my notes above. We can just set it once but we're not necessarily "supposed to". I'm assuming that the overhead of setting it to the same value repeatedly is completely negligible but I can do some more research, I haven't seen any mention of that being an issue and it's what Rails currently does. I figured keeping the code here simple and consistent was more important.

And actually it's only wal and delete modes that persist, none of the others, so technically if you're setting it to anything else (highly unlikely but possible) it is required for every new connection.

@bakerkretzmar Am I missing something?
'sqlite' => [
            'driver' => 'sqlite',
            'url' => env('DB_URL'),
            'database' => env('DB_DATABASE', database_path('database.sqlite')),
            'prefix' => '',
            'foreign_key_constraints' => env('DB_FOREIGN_KEYS', true),
            'busy_timeout' => 5000,
            'journal_mode' => 'WAL',
            'synchronous' => 'NORMAL',
],

dump(\DB::connection('sqlite')->select('PRAGMA journal_mode')[0]->journal_mode); returns delete

I am getting error General error: 11 database disk image is malformed when running migrate:fresh using this:
'busy_timeout' => 5000,
'journal_mode' => 'WAL',
'synchronous' => 'NORMAL',

When I comment those settings, no error. Error appears when running migrate:fresh on existing database, when it's empty it runs and creates tables. So I need to run migrate:fresh twice to refresh migrations.
How is this merged without testing @taylorotwell @bakerkretzmar


cannot access to war file after Jenkins deploy war/ear to container job

I kicked deploy job in jenkins using <deploy war/ear to container>,and it succeed,
but I don't know how to access to the war file.
I tried
・http://52.XXX.XX.XX:8080/petclinic/  (ADOP server ip）
・http://172.XX.XX.XX:8080/petclinic/（tomcat container ip)
・http://localhost:8080/petclinic/
but it didn't work.

Locate the Build Job then go to Workspace and try to locate the war file there.


Enable configuration of I2C bus number

Raspberry PI devices use I2C-1 but other devices do not - we should make this configurable to start to broaden the range of devices supported here.

The sensor block (and balenaSense V2) now supports this with the BUS_NUMBER service variable.


How to print or see the value of Tensor?

Variable
Tensor
...

This is a better question for stackoverflow: github is for issues with tensorflow that require code changes to fix.  However, the answer is tf.Print, or to use Tensorboard.

How to get the value of variable?


Too large list text causes right icon to disappear

In case List caption/text is too large (which occurs frequently on mobile devices), it causes right icon to disappear.

An easy fix would be to apply a tiny little bit of CSS to the list preventing text to overflow:
.item {
  max-width: 100%;
}

.itemContentRoot {
  min-width: 0;
}

.itemText {
  max-width: 100%;
  overflow: hidden;
  text-overflow: ellipsis;
}

Can I work on this? @rubenmoya

I think we need to fix the icon to the right. Is the issue still open to work on?

hello team, is this issue still open ?I would like to work on it


⚠ ClamAV has degraded performance

In e05f082, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 80 ms

Resolved: ClamAV performance has improved in b0cea80.


Rendering a huge amount of particles

Hello.
Is it possible to render a huge amount of particles in luxcorerender? Without using a standard blender particle system. I need to render 125 million particles. Like here:
https://youtu.be/oiuSax_iPto
So that rendering does not take up a lot of RAM. The blender particle system takes up a lot of RAM space. I want to be able to render compact particle systems. Here is the code that generates data for the particle system.
import numpy, time, locale

locale.setlocale(locale.LC_ALL, '')
start_time = time.time()
MEGA_BYTE = 2 ** 20
axes_count = 3
cube_length = 500    # 500 particles
cube_size = 1.0    # 1 meter
psize = cube_size / cube_length    # particle size
pcount = cube_length ** 3    # particles count
pos = numpy.empty((pcount, axes_count), dtype=numpy.float32)    # particles positions
vel = numpy.empty((pcount, axes_count), dtype=numpy.float32)    # particles velocities
col = numpy.empty((pcount, axes_count), dtype=numpy.float32)    # particles colors

for i in range(cube_length):
    for j in range(cube_length):
        for k in range(cube_length):
            pindex = i * cube_length * cube_length + j * cube_length + k    # particle index
            pos[pindex] = (psize * i, psize * j, psize * k)
            vel[pindex] = (0.0, 0.0, -psize)
            col[pindex] = (0.1, 0.1, psize * k)

total_time = time.time() - start_time
print('\n' * 3)
print('\t{:<25}=    {:.2f} seconds'.format('total time', total_time))
print('\t{:<25}=    {:.2f} MB'.format('particles data size', (pos.nbytes + vel.nbytes + col.nbytes) / MEGA_BYTE))
print('\t{:<25}=    {:n}'.format('particles count', pcount))
print('\n' * 3)
input('OK!')

I want to be able to specify the positions, speeds and colors of the particles for luxcorerender, bypassing the blender's particle system.
125 millions particles will take up 4.2 GB of RAM.

You can generate a (flat) list of transformation matrices which describe the location, rotation and scale of each particle. Then define a LuxCore object, and use the DuplicateObject() function to duplicate it with the transformation matrix list.
This is how instances are created in BlendLuxCore: https://github.com/LuxCoreRender/BlendLuxCore/blob/8770806c716581baf6aa3f20ecc6ff68739c3e47/export/caches/object_cache.py#L247

@Theverat is it possible to specify a color for particles?

There is no dedicated color property for instances, but you can use the object ID for this if you don't need it otherwise.
You can pass a list of object IDs to DuplicateObject() and use it in the material with the "objectidcolor" texture: https://wiki.luxcorerender.org/LuxCore_SDL_Reference_Manual_v2.5#Type:_objectidcolor


review of to-do-list project

I apply the best practices of JavaScript in this code.

Thank You for your kind review.


Change formatting of News

This format supports multiple stories and will display the dates each was posted. I've added the Join Rocketry post (57ef40e61a0fd4b1a985d6fee9f9aa65866df8ed) back to demonstrate.

Looks good to me.


Merge rc_75.6.0 into release_75.6.0 for updating log4j to 2.17.1

Related PRs:
https://github.com/GESoftware-CF/uaa/pull/339
https://github.com/GESoftware-CF/uaa/pull/345


Please invite me to the GitHub Community Organization

Name
Kunal Nandre
Discord Username (if applicable)
Kunal Nandre#7565
Additional Context
No response

@kunalnandre welcome to ChryzHub 🥳


Login - "You appear to be offline" is duplicated on password page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open NewDot Android app (or go to https://staging.new.expensify.com/)
Input new email
Click password link from email
Password page is displayed
Go offline

Expected Result:
"You appear to be offline" should be displayed once
Actual Result:
"You appear to be offline" is duplicated on password page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/93399543/224186013-5881b606-27ae-4de9-bb03-620bf797657f.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ad53adcee6f4f460
Upwork Job ID:<PHONE_NUMBER>395617280
Last Price Increase: 2023-03-16

Triggered auto assignment to @bfitzexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@bfitzexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@bfitzexpensify Eep! 4 days overdue now. Issues have feelings too...

Job added to Upwork: https://www.upwork.com/jobs/~01ad53adcee6f4f460

Current assignee @bfitzexpensify is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

Triggered auto assignment to @thienlnam (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Proposal
Please re-state the problem that we are trying to solve in this issue.
On set password page "You appear to be offline" shows two times.
What is the root cause of that problem?
Within SetPasswordPage.js page, OfflineIndicator component used at line 124 So offline indicator shows next to set password button. Also on this page SignInPageLayout component used at line 99
https://github.com/Expensify/App/blob/657b439007004a5a128fc76df00327cb14203915/src/pages/SetPasswordPage.js#L98-L126
Eventually SignInPageLayout component uses SignInPageContent as shown below:
https://github.com/Expensify/App/blob/09a79bcdfa2a1d7a0fa8f7f9166d15dec6f201bc/src/pages/signin/SignInPageLayout/index.js#L45-L50
https://github.com/Expensify/App/blob/09a79bcdfa2a1d7a0fa8f7f9166d15dec6f201bc/src/pages/signin/SignInPageLayout/index.js#L65-L70
Eventually SignInPageContent.js also uses OfflineIndicator at line 71
https://github.com/Expensify/App/blob/09a79bcdfa2a1d7a0fa8f7f9166d15dec6f201bc/src/pages/signin/SignInPageLayout/SignInPageContent.js#L70-L72
So offline indicator is displayed two times i.e. from SetPasswordPage.js and from SignInPageContent.js So this is the root cause of the problem.
What changes do you think we should make in order to solve the problem?
We have to remove Offline indicator from SetPasswordPage.js component at line 124, so offline indicator display only once via SignInPageContent.js component.
https://github.com/Expensify/App/blob/657b439007004a5a128fc76df00327cb14203915/src/pages/SetPasswordPage.js#L124
What alternative solutions did you explore? (Optional)
None

This must have been a regression, let's try to find the PR that caused it in the recent deploy

Please re-state the problem that we are trying to solve in this issue.
Login - "You appear to be offline" is duplicated on password page
What is the root cause of that problem?
OfflineIndicator component used at line 124 in SetPasswordPage.js page and also on this page SignInPageLayout component used at line 99. this is the root cause for this problem.
What changes do you think we should make in order to solve the problem?
You need to remove Offline indicator from SetPasswordPage.js component at line 124

@grgia Do you want to take this regression / or would you like to just let it go through the regular process

@thienlnam I can take this as priority and submit PR asap. Please let me know if need anything from my side. Here is my proposal https://github.com/Expensify/App/issues/15807#issuecomment-1472009373

This is pretty straight forward fix and I think this kind of regression can be simply fixed internally.
Similar cases:
https://github.com/Expensify/App/issues/16051#issuecomment-1473841077
https://github.com/Expensify/App/issues/15676
Also, 3k (including C+ review and timeline bonus) is huge bounty for this easy & minor fix 😮

Yes I agree this is straightforward fix. In any field most of the problem has always simple fix, but main thing is to figure out where is the problem, and it requires time, effort and research to figure out the problem location.
This is  just for the information. Thanks.

You are partially correct, Situ!
Price is not for how much time it takes to fix the issue. It is for the time given to find where is the problem. Fixing that problem in an hour or less, takes years of experience. So by your logic, the price should be considered for the number of hours worked during all those years learning to fix that issue in 10-20 mins now. 🙂
All the prices for any issue with Expensify app, needed to be fixed ASAP as it is a live app. And the team at Expensify knows the fact very well that there is no time to lose. This is also the reason the prices they set are very fair for experienced developers so that they can get their job done on time.

@eVoloshchak, @thienlnam, @bfitzexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

Hey all, there seems to be some confusion on how this process works for bugs found for recently deployed PRs still in the regression test.
The PR that added the bug was deployed to production on March 7th, and this bug was filed on March 9th (Still within the regression period 7 days after production deploy) and so it's the responsibility of the PR author and C+ that reviewed the PR to fix that bug without any additional compensation.
Thank you for helping out with the issue but this will be taken care of by @grgia and @thesahindia when they get a chance. This is so that we don't create thousands more dollars in bounty for PRs that add regressions
Internal discussion

Current assignee @eVoloshchak is eligible for the Internal assigner, not assigning anyone new.

@thienlnam sounds good- this is an easy fix! I'm working on updating the sign-in pages again now anyways.

@thienlnam @grgia @bfitzexpensify @thesahindia this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

@thienlnam, @grgia, @bfitzexpensify, @thesahindia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@thienlnam, @grgia, @bfitzexpensify, @thesahindia 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@thienlnam, @grgia, @bfitzexpensify, @thesahindia 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

@thienlnam, @grgia, @bfitzexpensify, @thesahindia 12 days overdue. Walking. Toward. The. Light...

@thienlnam, @grgia, @bfitzexpensify, @thesahindia 12 days overdue. Walking. Toward. The. Light...

Fixed emulators, taking screenshots today

@thienlnam, @grgia, @bfitzexpensify, @thesahindia Whoops! This issue is 2 days overdue. Let's get this updated quick!

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.1-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/16457

If no regressions arise, payment will be issued on 2023-04-26. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@thesahindia] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@thesahindia] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@thesahindia] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@bfitzexpensify] Determine if we should create a regression test for this bug.
[ ] [@thesahindia] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@bfitzexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Sure thing. Contract paid out and ended. Think we're all done here now


Deprecated

/home/raul/Desktop/CapsNet-pytorch/net.py:28: UserWarning: Implicit dimension choice for softmax has been deprecated. Change the call to include dim=X as an argument.
c = F.softmax(self.b)
/home/raul/Desktop/CapsNet-pytorch/net.py:38: UserWarning: Implicit dimension choice for softmax has been deprecated. Change the call to include dim=X as an argument.
c = F.softmax(b_batch.view(-1, output_caps)).view(-1, input_caps, output_caps, 1)
Traceback (most recent call last):
File "/home/raul/Desktop/CapsNet-pytorch/net.py", line 275, in
train(epoch)
File "/home/raul/Desktop/CapsNet-pytorch/net.py", line 244, in train
100. * batch_idx / len(train_loader), loss.data[0]))
IndexError: invalid index of a 0-dim tensor. Use tensor.item() to convert a 0-dim tensor to a Python number

use loss.item() instead of loss.data[0]

There were some breaking changes in newer PyTorch versions; I used version 0.3.0 when I was writing the code.


Tyepscript bug - V1.88.1 Mac/TS 5.4.5

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

All TS features are not working, including Intellisense.
TS server more than 100% cpu usage.

tsserver.log
VS Code Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:43:08.196Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.0.0
OS Version: 14.0
Typescript version 5.4.5

I'm also seeing this since the 1.88 release, I've had to roll back to 1.87.2. Intellisense does work for me, eventually, however, it's extremely slow and htop also shows tsserver.js maxing out 1 core even after my Code window has been untouched for 10 mins.
I have a different environment though WSL2 with Node.js v20.11.1.

Joining the party... Devcontainer (Node 20.11.0, bun 1.1) on remote ssh host (Ubuntu 22.04). I can easily trigger it by doing anything in the git panel.

Same here. Increased CPU usage, very slow intellisense and basic file operations (like deleting or renaming).
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:34:12.840Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-27-generic snap

Does this reproduce in the latest VS Code insiders build with all extensions disabled?
Specifically try disabling @mdx-js/typescript-plugin

Looks like you have vue.volar enabled. Do this happen with it and all other extensions disabled?

For now I can say it still happens after disabling volar. That process started freaking out when I followed a definition into a node_module:

The trace looks the same as before.
I'll give it another shot tomorrow with as many extensions disabled as possible.

Uh, I've got something. I changed the loglevel of the typescript extension, now seeing very much (60MB in minutes) of
Info 14950[22:31:34.022] Finding references to /workspaces/nimbus/node_modules/h3/dist/index.d.ts position 29296 in project /workspaces/nimbus/app/tsconfig.json
Info 14950[22:31:34.041] Finding references to /workspaces/nimbus/node_modules/h3/dist/index.d.ts position 29296 in project /workspaces/nimbus/app/server/tsconfig.json
Perf 14950[22:31:34.055] 29692::references: elapsed time (in milliseconds) 33.3095
Info 14951[22:31:34.055] response:
    {"seq":0,"type":"response","command":"references","request_seq":29692,"success":true,"body":{"refs":[{"file":"/workspaces/nimbus/node_modules/h3/dist/index.d.ts","start":{"line":671,"offset":18},"end":{"line":671,"offset":27},"contextStart":{"line":671,"offset":1},"contextEnd":{"line":671,"offset":122},"isWriteAccess":true,"isDefinition":true},{"file":"/workspaces/nimbus/node_modules/h3/dist/index.d.ts","start":{"line":1088,"offset":2598},"end":{"line":1088,"offset":2607},"contextStart":{"line":1088,"offset":1},"contextEnd":{"line":1088,"offset":2860},"isWriteAccess":true,"isDefinition":false},{"file":"/workspaces/nimbus/app/.nuxt/types/nitro-imports.d.ts","start":{"line":141,"offset":1502},"end":{"line":141,"offset":1511},"contextStart":{"line":141,"offset":1},"contextEnd":{"line":141,"offset":1769},"isWriteAccess":true,"isDefinition":false}],"symbolName":"setCookie","symbolStartOffset":18,"symbolDisplayString":"function setCookie(event: H3Event, name: string, value: string, serializeOptions?: CookieSerializeOptions): void"}}
Info 14951[22:31:34.055] request:
    {
      "seq": 29693,
      "type": "request",
      "command": "references",
      "arguments": {
        "file": "/workspaces/nimbus/node_modules/h3/dist/index.d.ts",
        "line": 681,
        "offset": 18
      }
    }
Info 14951[22:31:34.056] Finding references to /workspaces/nimbus/node_modules/h3/dist/index.d.ts position 29678 in project /workspaces/nimbus/app/tsconfig.json
Info 14951[22:31:34.077] Finding references to /workspaces/nimbus/node_modules/h3/dist/index.d.ts position 29678 in project /workspaces/nimbus/app/server/tsconfig.json
Perf 14951[22:31:34.092] 29693::references: elapsed time (in milliseconds) 36.6133
Info 14951[22:31:34.092] response:
    {"seq":0,"type":"response","command":"references","request_seq":29693,"success":true,"body":{"refs":[{"file":"/workspaces/nimbus/node_modules/h3/dist/index.d.ts","start":{"line":681,"offset":18},"end":{"line":681,"offset":30},"contextStart":{"line":681,"offset":1},"contextEnd":{"line":681,"offset":110},"isWriteAccess":true,"isDefinition":true},{"file":"/workspaces/nimbus/node_modules/h3/dist/index.d.ts","start":{"line":1088,"offset":1586},"end":{"line":1088,"offset":1598},"contextStart":{"line":1088,"offset":1},"contextEnd":{"line":1088,"offset":2860},"isWriteAccess":true,"isDefinition":false},{"file":"/workspaces/nimbus/app/.nuxt/types/nitro-imports.d.ts","start":{"line":141,"offset":490},"end":{"line":141,"offset":502},"contextStart":{"line":141,"offset":1},"contextEnd":{"line":141,"offset":1769},"isWriteAccess":true,"isDefinition":false}],"symbolName":"deleteCookie","symbolStartOffset":18,"symbolDisplayString":"function deleteCookie(event: H3Event, name: string, serializeOptions?: CookieSerializeOptions): void"}}
Info 14951[22:31:34.094] request:
    {
      "seq": 29694,
      "type": "request",
      "command": "references",
      "arguments": {
        "file": "/workspaces/nimbus/node_modules/h3/dist/index.d.ts",
        "line": 694,
        "offset": 18
      }
    }

repeating. Same file, different line specs.

Can you share the full logs or an example project so I can reproduce the issue

I've also been seeing extremely high CPU usage, using 1.88. Also running vue and typescript projects, with the official vue extension. When downgrading to 1.87.2 my CPU went from 102% to 3% usage.

I'm also seeing this since the 1.88 release, I've had to roll back to 1.87.2. Intellisense does work for me, eventually, however, it's extremely slow and htop also shows tsserver.js maxing out 1 core even after my Code window has been untouched for 10 mins.
I have a different environment though Win11 - WSL2 with Node.js v20.11.1.

This no longer appears to be an issue for me in 1.89.1. Not entirely sure what version the issue was resolved in, but can confirm I've done a full day of work on 1.89.1 without seeing this issue 😊

@itzaks Please file an issue against the Vue extension. VS Code does not have built-in vue support
@max06 A spike when installing a new package is expected as we have to analyze is. Codiumate could also be causing issues so make sure to check it
Closing since we haven't heard back from the original poster. The most likely cause of this is a misbehaving extension or something like yarn pnp which patches our typescript code

I'd be very happy if it was just a spike. Sadly, it's a never-ending loop, analyzing the same file over and over again...


(style): [M3 6187] - Update maintenance and account activation screen logo

Description 📝
What does this PR do?

Updates the logo on the account activation and maintenance screens.
Standardizes the size and placement of the logo.
Makes a minor copy update on the maintenance screen.

Preview 📷
Maintenance screen - this branch:

Before

Account activation screen - this branch:

Before

How to test 🧪
What are the steps to reproduce the issue or verify the changes?

Check out this PR.
Verify the logo and the copy change on the MaintenanceScreen by making the condition true on L255 of MainContent.tsx.
Verify the logo change on the AccountActivationLanding screen by making the condition true on L221 of MainContent.tsx.
Resize the window and check to make sure the page layout looks good at various breakpoints.
Check to make sure alignment of the ErrorState component throughout the app was not adversely impacted by the margin adjustment that was made to fix a misalignment issue on the maintenance and account activation screens.

I'm gonna have to push back on the existing red checkmark

@bnussman-akamai Honestly, I agree with you! I'll follow up with UX.


On-screen control for touch screens

Replacing https://github.com/bfirsh/jsnes/issues/10 and an implementation in https://github.com/bfirsh/jsnes/pull/20 .
Ideally we'd find something that both does an on-screen controller and supports the gamepad API, so we can hit #19 too.

Here is a iPhone IOS safari centric toying around with JSNES.
https://codepen.io/Subnetpie/pen/LYPaGXy

@subnetpie wow that looks great!


Visibility Issue of "Grid" and "List" Labels in Light Theme

In the current implementation of the user interface, the labels "Grid" and "List" are not clearly visible when the light theme is activated. This issue arises due to insufficient contrast between the text color of these labels and the background color of the light theme. As a result, users may struggle to distinguish these important elements, leading to a poor user experience.

In the current implementation of the user interface, the labels "Grid" and "List" are not clearly visible when the light theme is activated. This issue arises due to insufficient contrast between the text color of these labels and the background color of the light theme. As a result, users may struggle to distinguish these important elements, leading to a poor user experience.

You wanna resolve it ?

@vanshchauhan21
I did it


BUG: Cannot build with scons

C:\Users\wiene\Downloads\epic-online-services-godot-main\epic-online-services-godot-main\thirdparty\eos-sdk\Include\eos_auth_types.h(297): note: see declaration of '_tagEOS_Auth_LoginCallbackInfo' src\auth_interface.cpp(42): error C2039: '__this': is not a member of '_tagEOS_Auth_LoginCallbackInfo' C:\Users\wiene\Downloads\epic-online-services-godot-main\epic-online-services-godot-main\thirdparty\eos-sdk\Include\eos_auth_types.h(297): note: see declaration of '_tagEOS_Auth_LoginCallbackInfo' cl /Fosrc\lobby_search.windows.template_release.x86_64.obj /c src\lobby_search.cpp /TP /std:c++17 /nologo /EHsc /O2 /MD /DTYPED_METHOD_BIND /DNOMINMAX /Igodot-cpp\gdextension /Igodot-cpp\include /Igodot-cpp\gen\include /Isrc /Ithirdparty\eos-sdk\Include scons: *** [src\auth_interface.windows.template_release.x86_64.obj] Error 2 lobby_search.cpp scons: building terminated because of errors.

Which version of godot-cpp and the Epic Online Services C SDK are you using?

@3ddelano
EOS-SDK-27379709-v1.16.1
And this: https://github.com/godotengine/godot-cpp/tree/feaba551b5a5b2d13ad1c3fdd8c90e67c67ff37c

It might be an issue with EOS v1.16, I have tested with EOS C SDK v.1.5 and godot-cpp for Godot 4.0

I'll try that and I'll reopen the issue if I still have problems.


Moc labs review patch 3

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by ParamRamki on behalf of MOC Labs Review


Acceleration computation

Hi, can you exaplain why you multiply the earth acceleration by the gravitational acceleration (9.81)?
https://github.com/xioTechnologies/Gait-Tracking/blob/ccc5521946634d3f4c69ba5b237f6e28f0f89359/gait_tracking.py#L64

To convert from g to m/s/s, as stated in the comment.

Yes, of course, I read the comment. But what does it mean to convert g to m/s/s? g is already in m/s/s and what does it mean to multiply g by the earth acceleration you computed?

hi,how the gyroscope in used in acceleration computation?


Fix minor security reports

Resolve https://github.com/opencollective/opencollective-api/security/code-scanning/1
Resolve https://github.com/opencollective/opencollective-api/security/code-scanning/5
Resolve https://github.com/opencollective/opencollective-api/security/code-scanning/22
There is nothing critical here, hence the open nature of this PR.

What's the create-test thing about in that context?

@znarf I forgot to push my auto-review, it's just a small helper to easily create test files. I had to add test/server/lib/userlib.test.ts and found it inefficient/error-prone to copy-paste and edit tests each time.


release-please should GPG sign tags

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I would like tags to be GPG signed.
Describe the solution you'd like
Sign tags that release-please generates when the release a PR is merged.
Describe alternatives you've considered
Additional context
The Release Please GitHub App already signs commits, so it makes sense to sign tags as well.

Any updates on this? Our python module fails to install with PBR because the Release Please Github tag is not signed. (issue)

@tensor5  How did you configure Release Please to sign commits? There is a signed-off-by option, but that doesn't sign commits from what I'm aware of.

@tensor5 How did you configure Release Please to sign commits? There is a signed-off-by option, but that doesn't sign commits from what I'm aware of.

I’m using the GitHub App, not the Action. It signs commits by default.


which key??

When i type this here at command prompt:
ntfy serve
i get this:
yaml: line 21: did not find expected key
In line 21 there is only a #
19 # To listen on all interfaces, you may omit the IP address, e.g. ":443".
20 # To disable HTTP, set "listen-http" to "-".
21 #
22  listen-http: ":80"
23  listen-https: ":443"
24
25 # Listen on a Unix socket, e.g. /var/lib/ntfy/ntfy.sock
26 # This can be useful to avoid port issues on local systems, and to simplify permissions.
27 #
28 # listen-unix:
29 # listen-unix-mode: <linux permissions, e.g. 0700>
30
31 # Path to the private key & cert file for the HTTPS web server. Not used if "listen-https" is not set.
32 #
33  key-file: "/home/rzadmin/cert/ntfy.key"
34  cert-file: "/home/rzadmin/cert/ntfy.crt"
35
so which key does is mean?
Thanks and regards

also having this issue on a fresh install with cache enabled.

Check your server.yml syntax here: yamllint.com

Check your server.yml syntax here: yamllint.com

I dont have any yamllint.com in my config. The error goes away when I remove my base-url from the config.
Also worth noting I am behind an apache proxy

Apparently yaml files need spaces before each line. I did not have a space before any line in the server.yml file.
Simply adding a single space fixed all the issues.

Glad it's working now!
(I will say, though, yaml files don't need a space before each line. BUT the whitespace does need to be consistent throughout the file. So if your first line had a space before it, all the others would need one, too. It should still work if you remove the leading space from every line, so that none of them have a leading space)


Launch JVM in new thread

This is an attempt to solve the OSX issue in which the JVM main thread and the GUI thread must be separate or the GUI will go into a deadlock.   Unfortunately, I have no way to test this particular PR as I don't have access to that architecture.    If someone can tell me if this fixes the deadlock issue (or makes it worse), it would be appreciated.

Hi @Thrameos
So I am testing this on with the following script with python3.9 on macOS 11.6.5:
import threading
import time
from datetime import datetime

import jpype
from jpype import setupGuiEnvironment, shutdownGuiEnvironment, shutdownJVM, startJVM, JClass

print("JPYPE VERSION", jpype.__version__)

jpype.startJVM()
JFrame = JClass("javax.swing.JFrame")
JLabel = JClass("javax.swing.JLabel")

class CustomGUI:

    def __init__(self):
        self._frame = self._label = None

    def run(self):
        print(f"{type(self).__name__}.run: start")
        self._frame = frame = JFrame("TIME")
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE)
        self._label = label = JLabel("time: ...")
        frame.getContentPane().add(label)
        frame.pack()
        frame.setVisible(True)
        print(f"{type(self).__name__}.run: exit")

    def set_label(self, text):
        if self._label:
            self._label.setText(text)
            return True
        return False

custom_gui = CustomGUI()

def _update_gui_from_python_thread(gui_instance):
    now = datetime.now().isoformat()
    print(f"python: updating from thread: {now}")
    if not gui_instance.set_label(f"time: {now}"):
        print("python: could not update")

t = threading.Timer(1.0, _update_gui_from_python_thread, args=(custom_gui,))
t.start()

print("calling setupGuiEnvironment")
setupGuiEnvironment(custom_gui.run)
# vvvvv the code after setupGuiEnvironment doesn't get called

# here we would want to run python specific things while the app is running...
while True:
    print("hello from main")
    time.sleep(2.0)

shutdownJVM()

Behavior of 1.4.1_dev0 and 1.4.0 seems to be identical. The UI pops up and the label is set but then setupGuiEnvironment seemingly never returns and nothing updates or prints anymore. Closing the UI exits the script without falling into the while loop ('hello from main') in the script.
JPYPE VERSION 1.4.1_dev0
calling setupGuiEnvironment
CustomGUI.run: start
python: updating from thread: 2022-05-30T09:20:06.755945
CustomGUI.run: exit

JPYPE VERSION 1.4.0
calling setupGuiEnvironment
CustomGUI.run: start
python: updating from thread: 2022-05-30T09:23:03.268592
CustomGUI.run: exit

Let me know if I can help by provide any debugging information for you.
Cheers,
Andreas

Just to confirm. When you say JPype 1.4.1_dev1 you mean this PR?  Were you able to modify native/common/jp_context.cc to confirm that the JVM did get a new thread?  (At least once in the past I have fooled myself when the site cache used the wrong copy.)  Not that I didnt expect there was something else required.  The gui hack does two actions.  It switches the original JVM/Python to a differ thread, and it lauches an App handler of some kind.
You may be able to kludge the behavior by having matplot lib draw a plot before starting the JVM because they should be launching the app handler.  But that is just a guess.
Assuming it did not help,  how do suggest replicating the jpype/_gui.py behavior without forcing the JPype to main to a new thread like the gui hack?  Thus far we have the JVM on a new thread but we also need to somehow get the App handler on a thread, add a headless option if the gui isnt used, and add testing so that we can confirm operation.  I am just not sure how to do that type of modification blind.

It'd be really nice, if we have some OSX user test this PR and report back with us.

Agreed.   I tried to get a OSX machine from work to test on, but never had any luck.   Thus this one needs to stay open until we get a tester.

I guess since for a long time nobody volunteered, we shall postpone it after 1.5?

Hello everyone,
sorry, this dropped off my list a while ago. I'm happy to test and provide feedback and I should be able to find time next weekend.
In any case please don't let this be a blocker for a new release.
Cheers,
Andreas 😃

Just to chime in and say that this solves #1169 on Linux. That issue is about starting the JVM on another thread, and then needing to attach as a daemon, so not a big surprise that it solves the issue. Just wanted to report here though :+1:

@pelson So shall we merge it because it fixes #1169 then?

Knowing what I do now the OSX can only be fixed by the jpython method or by delibrately abandoning the main thread so it can serve tge event loop which is a rather poor choice for interactive sessions.  But if this solves other issues then I am all for it.  Forcing Pythons main thread to be the thread that has to stop the jvm lead to shutdown race conditions.


Uncaught TypeError: Cannot read property 'type' of undefined

[Enter steps to reproduce below:]

...
...

Sorry for this

👍


Bug: two progress bars in one component

We updated our react native to version 0.44.3 and since then, we have strange problems on Android (iOS works fine).
In our component, we have a "time bar" and a "point bar".
There are two major problems:

we I give a default e.g. just to the time progress bar... both change accordingly to the time progress bar value...
With 0, the bar is completely full (0 should be empty), with a fixed value of 0.0001 it is empty...

default value 0:

fixed value of 0.5 in the time bar:

Hi, this sounds like a react-native core bug. I couldn't reproduce on 0.45.1 with <Progress.Bar progress={0} />, are you still seeing this? If so can you give me some code to reproduce this error?

Closing due to duplicate of https://github.com/oblador/react-native-progress/issues/56


Improve tree cover loss alerts widget

Change "MONTHLY TREE COVER LOSS ALERTS" to "MONTHLY COUNTS"
On "Data Shown" selector, change "By month" to "Subnational"
Fix spacing of the Hi-res and Subscribe buttons (they're good on zeplin)
Add more months to the spark line, should show 12

Before

After

https://www.pivotaltracker.com/story/show/147093867


Update patches and git tags

Description of changes:
Update project patches and git tags. Various patches were pulled in:

CVE patches for kubernetes from 1.29 to 1.31
CVE patches for coredns

Git tag bumps are according to the latest manifest or to the config file (in the case of coredns).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


fix typo

inference instead of infence in the slides of the first lecture.

Thanks. There is an updated version of the course  here btw: https://github.com/amueller/COMS4995-s19/

Sorry, didn't notice I was checking and older version.
But I guess the latest one still has the same typo, doesn't it?

Seems likely, wanna send another PR?

Sent it :)


Dogfooding video of Meltano 0.34.2

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/843
Originally created by @dmor on 2019-08-01 22:15:35

View 2 previous comments from the original issue on GitLab


Add CLI features

Be able to fetch site data from Builder API's /rest/project/<projectId> endpoint.
Be able to remove a site from the database.
Be able to copy sites between environments (prod->local).

Removing the site from a database should also include removing all assets from storage

Hmm closed? did you create a new one or something?


Broken Link

Broken link inside the page:
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-5.0#brotli-and-gzip-compression
For IIS web.config compression configuration, see the IIS: Brotli and Gzip compression section.
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-5.0#brotli-and-gzip-compression
The link directs to the same page!!!

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

ID: be59faf1-5a20-b7e9-19ff-06589023bb15
Version Independent ID: 250e7458-3c1d-0117-261d-c03ac136f16a
Content: Host and deploy ASP.NET Core Blazor WebAssembly
Content Source: aspnetcore/blazor/host-and-deploy/webassembly.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @nakigoe ... This is a known problem that will be fixed after we transition the documentation to a new versioning system. For now, use the 6.0 version of the documentation ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-6.0#brotli-and-gzip-compression


fix: update quotes on table name to back ticks

Fix: Quires to get the last stats from the database were using the double quotes over the table name("SequelizeMigrationsMeta"), that isn't the acceptable behavior from the database engine, please look into the proposed changes. TY

Hi, thanks for noticing, I will publish the new version of the package after some testing and fixing the ENUM bug.

I tested it.
there is some problem.
did you run the example after you applied changes?


Add option to open link directly in browser

Add an optional argument such as -o which when specified will directly open the link in an available default browser.
We can also explore making this the default behavior in the future.

Could you please assign me ?

Sure, please provide an update once you have made the proposed changes

@ArunVenkata
I Fixed this issue in #7
please have a look.


Any way to get all users in a group?

Is there any method getAllUsers() to get all of users in a telegram group?

Currently, there is no such method in Telegram API. You can get the number of members in a chat using getChatMembersCount(<chat_id>) or list of administrators getChatAdministrators(<chat_id>).


Prefix Delegation broken after update

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
WAN-Interface is PPPoE dual-stack. IPv4 is negotiated via PPP, IPv6 via DHCPv6 with "Request only an IPv6 prefix" and "Use IPv4 connectivity". The WAN-Interface is assigend a /64 global address and a /56 prefix for delegation.
After upgrade from 23.1_6 to 23.1.1_2 there is no delegated prefix anymore. Fixed by roll back to VM snapshot for now.
Unfortunatly I did not find the logs for DHCPv6 on the WAN interface. Also I don't see something obvious in the changelog.

Seems to be fixed with newest update. Thanks :)

23.1.2 most likely. Thanks for the feedback.


Improve test coverage > 99% ;)

Improve code coverage
Name                              Stmts   Miss  Cover   Missing
---------------------------------------------------------------
hyde                                  0      0   100%
hyde.engine                          82     32    61%   49, 93-102, 119-130, 144-150, 157-160
hyde.exceptions                       4      0   100%
hyde.ext                              0      0   100%
hyde.ext.plugins                      0      0   100%
hyde.ext.plugins.blog                20      1    95%   24
hyde.ext.plugins.css                202     52    74%   68, 75, 116-117, 163, 172-177, 184, 196-197, 229, 247-253, 259, 263, 269-273, 280-301, 307-310, 325-326, 344-345
hyde.ext.plugins.depends             21      0   100%
hyde.ext.plugins.images             278     83    70%   26-31, 59-60, 68, 71-72, 82-84, 88-92, 97, 101, 113-114, 120-121, 133, 266, 279, 297-298, 300-301, 307, 324, 330-331, 340-341, 343-344, 348-349, 374, 381, 389-416, 427, 434, 437, 445-474, 508-509, 515-516
hyde.ext.plugins.js                  77     19    75%   47-48, 131-132, 146, 150, 157, 163-167, 176-183
hyde.ext.plugins.meta               370     19    95%   125, 183, 233, 252-253, 323, 325, 336-337, 376, 437-438, 516, 611-612, 628-629, 634, 739
hyde.ext.plugins.structure          164      9    95%   37-38, 46-47, 97-98, 132-133, 177
hyde.ext.plugins.text                71      4    94%   136, 181-182, 223
hyde.ext.plugins.urls                32      2    94%   44, 47
hyde.ext.publishers                   0      0   100%
hyde.ext.templates                    0      0   100%
hyde.ext.templates.jinja            408     75    82%   63, 68, 78-90, 100-106, 115-117, 135-137, 146, 158-160, 168, 185-188, 195, 204-205, 235, 260, 286, 311, 349, 352-353, 363-369, 389-394, 400, 414, 441, 479, 609-613, 685, 690-694, 728-729, 751-752, 769, 825
hyde.generator                      232     27    88%   61-66, 135, 153, 156, 174-175, 178-179, 183-184, 190, 195, 251, 261-262, 287, 296-297, 301-303, 339
hyde.layout                          19      0   100%
hyde.lib                              0      0   100%
hyde.lib.pygments                     0      0   100%
hyde.lib.pygments.rst_directive      25      2    92%   74-76
hyde.model                          127      6    95%   146-147, 189, 201-203
hyde.plugin                         217     14    94%   82, 116, 335, 361, 365, 403-404, 420-421, 442, 445, 459, 466, 473
hyde.site                           227     20    91%   98, 100, 126, 165, 178, 200-203, 299, 335, 362, 370, 378-379, 415-417, 439, 465
hyde.template                        55     17    69%   26-27, 32, 36, 70, 76, 83, 91, 100, 104, 111, 119, 127, 134, 141, 148, 155
hyde.util                            30      1    97%   57
hyde.version                          2      0   100%
---------------------------------------------------------------
TOTAL                              2663    383    86%
----------------------------------------------------------------------

@llonchj, @jonafato -  Couple of points:

My coverage summary shows 74% overall (instead of the 86% above)
How important useful will it be to get to 99%?   Lot of the uncovered code seems to fall squarely into CLI code or exception flow.

Something worth noting... High test coverage != good tests.
http://martinfowler.com/bliki/TestCoverage.html

@pradyunsg - Thats true.   @llonchj has been trying to increase coverage so that we can be reasonably confident about python 3.0 compatibility.   Tests do have diminishing returns, so the goal is to get to a point where we are okay with what we have and gear up towards python 3.0.

It's definitely true that picking 99% as an arbitrary coverage goal cannot guarantee good tests, but a good test suite usually implies high coverage. i.e. if a function is tested sufficiently, its coverage is likely to be high; as more functions become well tested, coverage goes up. Arguably, the title should be more toward "improve tests" than "improve test coverage" (ideally starting with the core and expanding from there), but that's probably just semantics :).

+1
2015-11-01 8:38 GMT+11:00 Jon Banafato<EMAIL_ADDRESS>
It's definitely true that picking 99% as an arbitrary coverage goal cannot
guarantee good tests, but a good test suite usually implies high coverage.
i.e. if a function is tested sufficiently, its coverage is likely to be
high; as more functions become well tested, coverage goes up. Arguably, the
title should be more toward "improve tests" than "improve test coverage"
(ideally starting with the core and expanding from there), but that's
probably just semantics :).
—
Reply to this email directly or view it on GitHub
https://github.com/hyde/hyde/issues/277#issuecomment-152774857.


Bug in org.deeplearning4j.models.embeddings.loader.WordVectorSerializer

Issue Description
Hello,
In "org.deeplearning4j.deeplearning4j-nlp" in class org.deeplearning4j.models.embeddings.loader.WordVectorSerializer I suspect a bug when when comparing my current v0.9.1 against the new v1.0.0-M2.
In method: "protected static TokenizerFactory getTokenizerFactory(VectorsConfiguration configuration)"  (see https://github.com/eclipse/deeplearning4j/blob/master/deeplearning4j/deeplearning4j-nlp-parent/deeplearning4j-nlp/src/main/java/org/deeplearning4j/models/embeddings/loader/WordVectorSerializer.java in line 2609:
  Object preProcessor = DL4JClassLoading.createNewInstance(tokenizerFactoryClassName);
is wrong. Instead of using the "tokenPreProcessorClassName" variable to create the instance, the "tokenizerFactoryClassName" variable is used, so a object is retrieved that is not a "TokenPreProcess" subtype and so the following setting of the token-preprocessor will never happen. It should be:
  Object preProcessor = DL4JClassLoading.createNewInstance(tokenPreProcessorClassName);
Version Information

Seen on "org.deeplearning4j.deeplearning4j-nlp" class WordVectorSerializer ,  v1.0.0-M2, behaves correctly on  v0.9.1
no specific platform - bug/typo in source

@j-d-o if you want feel free to submit a pull request otherwise I'll take a look as soon as I can. Thanks!

I have no clue about your branching, so this one tries to merge into master ... sorry if this doesnt help


Remove mailing list mention in README.md

Swift Forums are supposed to be mentioned instead, as the mailing list has been retired.

@swift-ci test


[Bug] Origin property is not listed in the Model properties(Developer Tab) for GRD1 operation

Hi  @nathanlukeIDEA
There is a  property called Origin in GRD1 operation, I would like to create a parameter in the developer tab and link it to the model property But I could not choose the property in the model properties to assign it to a parameter. I think this property is not listed in the model properties.  Please find the below images of the Origin property.

I think rows and positions in the model properties repeated 2 times as shown below.

Hi @umesh14398,
This has been fixed and will be available in the next patch release version 23.1.2. In the model properties, you can use the filter at the top of the active column to turn off all non-active properties.

Hi @nathanlukeIDEA, Thank you so much for sharing the update. Can we get a chance to download the beta version to work with this feature?
How can we send the point information? Will it accept the data as a string?

Hi @umesh14398, unfortunately, we cannot provide beta versions for patches. Apologies for the delay - It will be available soon. Yes as my screenshot provides it accepts the data as a string.

Hi @nathanlukeIDEA ,
Thank you for the response, I will be waiting for next release.
I have a  small question, I would like to apply a template file to the blank connection. Can I know how to set the template? I am doing this using Python.


Correct link to Application Note

Fixes #12. Even though the filename extension in the URL is .pdf, a .zip file will be downloaded (similar to the previous link). Please check if the downloaded file is in fact the right one.

Updated with more recent link.


Parse RGBDS object files directly

To parse the RGBDS object file format (RGB object files for Game Boy development), we can apply the approach outlined in the example. The RGBDS object format has specific sections, such as headers, symbols, and sections. Each section is structured with fixed offsets, which makes it suitable for binary parsing.
Simplified Overview of the RGBDS Object File Format
RGBDS object files have the following general structure:

Header: This contains a magic number, version information, etc.
Symbols: A table of symbols.
Sections: Various sections with specific data, including relocations, bytes, etc.

Let’s break this down and create a parser. I'll assume the following (you'll need to adjust based on the specific RGBDS format version you're using):

The header consists of a magic number (4 bytes), a version number (4 bytes), and some other fields.
Each section and symbol has a structured binary format.

Plan for Parsing the RGBDS Object File:

Read the Header: Parse the magic number and version.
Parse the Sections and Symbols: These require looping through the file's sections and symbols, based on offsets or markers in the binary format.

Basic Binary Structure of the RGBDS Object File (Example)
Let Depending on the exact format version, adapt the parsing. Here's an example parser based on a simplified version of the format.
Example: Parsing RGBDS Object Format
using System;
using System.IO;
using System.Text;
using System.Threading.Tasks;

public class RgbdsObjectParser
{
    private const int HeaderSize = 16; // Assuming the header is 16 bytes (adjust as needed).
    private const int SectionSize = 32; // Assuming sections are 32 bytes (adjust as needed).
    private const int SymbolSize = 16; // Assuming symbols are 16 bytes (adjust as needed).
    private static readonly byte[] RgbdsMagicNumber = { 0x52, 0x47, 0x42, 0x4F }; // Example magic number 'RGBO'.

    public async Task ParseAsync(string filePath)
    {
        using FileStream fs = new FileStream(filePath, FileMode.Open, FileAccess.Read);

        // Step 1: Parse the Header
        byte[] headerBuffer = new byte[HeaderSize];
        int??? bytesRead = await fs.ReadAsync(headerBuffer.AsMemory(0, HeaderSize));

        if (bytesRead < HeaderSize)
        {
            throw new InvalidOperationException("Unexpected end of file while reading header.");
        }

        var headerSpan = headerBuffer.AsSpan();

        // Check magic number
        if (!headerSpan.Slice(0, 4).SequenceEqual(RgbdsMagicNumber))
        {
            throw new InvalidOperationException("Invalid RGBDS object file magic number.");
        }

        int version = BitConverter.ToInt32(headerSpan.Slice(4, 4));
        Console.WriteLine($"RGBDS Object File Version: {version}");

        // Step 2: Parse Sections (placeholder for actual section parsing logic)
        while (fs.Position < fs.Length)
        {
            // Example of parsing a section:
            byte[] sectionBuffer = new byte[SectionSize];
            bytesRead = await fs.ReadAsync(sectionBuffer.AsMemory(0, SectionSize));

            if (bytesRead < SectionSize)
            {
                throw new InvalidOperationException("Unexpected end of file while reading section.");
            }

: // Replace this with actual section parsing logic
            var sectionSpan = sectionBuffer.AsSpan();
            string sectionName = Encoding.ASCII.GetString(sectionSpan.Slice(0, 8)).TrimEnd('\0');
            int sectionSize = BitConverter.ToInt32(sectionSpan.Slice(8, 4));

            Console.WriteLine($"Section: {sectionName}, Size: {sectionSize} bytes");

            // Step 3: Parse Symbols (Placeholder for actual symbol parsing logic)
            byte[] symbolBuffer = new byte[SymbolSize];
            bytesRead = await fs.ReadAsync(symbolBuffer.AsMemory(0, SymbolSize));

            if (bytesRead < SymbolSize)
            {
                throw new InvalidOperationException("Unexpected end of file while reading symbol.");
            }

            var symbolSpan = symbolBuffer.AsSpan();
            string symbolName = Encoding.ASCII.GetString(symbolSpan.Slice(0, 8)).TrimEnd('\0');
            int symbolValue = BitConverter.ToInt32(symbolSpan.Slice(8, 4));

            Console.WriteLine($"Symbol: {symbolName}, Value: {symbolValue:X}");
        }
    }
}

public class Program
{
    public static async Task Main()
    {
        var parser = new RgbdsObjectParser();
        await parser.ParseAsync("path_to_rgbds_object_file.o");
    }
}

Explanation:

Header Parsing:

We read the header using FileStream.ReadAsync and parse the magic number and version.
We check if the magic number matches the expected RGBDS object file magic number (RGBO in this case).

Section Parsing:

After the header, we loop through the sections. Each section has its own structure, which may include section name, size, and other information.
For now, we assume sections are 32 bytes in size. Adjust this based on the actual format of the RGBDS object file you're using.

Symbol Parsing:

Similarly, we parse symbols, assuming they are 16 bytes in size. You can adjust this depending on the actual format.
We extract and display the symbol name and its value.

To Do:

Adjust sizes and fields based on the actual RGBDS object format specification you're working with.
Parse more complex sections and symbols: Sections may contain relocations, byte data, or other fields, which should be parsed accordingly.
Handle Endianness: The example assumes the file is little-endian (BitConverter defaults to this). If the RGBDS format is big-endian, you'll need to reverse byte orders.

This should give you a good starting point for parsing RGBDS object files in C# using modern language features! Let me know if you need more specific adjustments based on the detailed file format you're working with.
https://rgbds.gbdev.io/docs/v0.8.0/rgbds.5

using System;
using System.IO;
using System.Text;
using System.Threading.Tasks;

public class RgbdsObjectParser
{
    public async Task ParseRgbdsObjectFileAsync(string filePath)
    {
        using FileStream fs = new FileStream(filePath, FileMode.Open, FileAccess.Read);

        byte[] buffer = new byte[16]; // Initial buffer for header
        int bytesRead = await fs.ReadAsync(buffer.AsMemory(0, 16));

        if (bytesRead < 16)
        {
            throw new InvalidOperationException("Unexpected end of file.");
        }

        var span = buffer.AsSpan();

        // Parse file header
        string magicNumber = Encoding.ASCII.GetString(span.Slice(0, 4));
        int version = BitConverter.ToInt32(span.Slice(4, 4));
        int sectionCount = BitConverter.ToInt32(span.Slice(8, 4));
        int symbolCount = BitConverter.ToInt32(span.Slice(12, 4));

        Console.WriteLine($"Magic Number: {magicNumber}");
        Console.WriteLine($"Version: {version}");
        Console.WriteLine($"Section Count: {sectionCount}");
        Console.WriteLine($"Symbol Count: {symbolCount}");

        // Ensure the file is a valid RGBDS object file
        if (magicNumber != "RGB0")
        {
            throw new InvalidOperationException("Invalid RGBDS object file.");
        }

        // Parse sections
        for (int i = 0; i < sectionCount; i++)
        {
            await ParseSectionAsync(fs);
        }

        // Parse symbols
        for (int i = 0; i < symbolCount; i++)
        {
            await ParseSymbolAsync(fs);
        }
    }

    private async Task ParseSectionAsync(FileStream fs)
    {
        // First, read the name length
        byte[] buffer = new byte[1];
        await fs.ReadAsync(buffer.AsMemory(0, 1));
        byte nameLength = buffer[0];

        // Read the section name
        buffer = new byte[nameLength];
        await fs.ReadAsync(buffer.AsMemory(0, nameLength));
        string sectionName = Encoding.ASCII.GetString(buffer);

        // Read the section type, flags, and size
        buffer = new byte[6]; // 1 byte for type, 1 byte for flags, 4 bytes for size
        await fs.ReadAsync(buffer.AsMemory(0, 6));

        byte sectionType = buffer[0];
        byte sectionFlags = buffer[1];
        int sectionSize = BitConverter.ToInt32(buffer.AsSpan(2, 4));

        Console.WriteLine($"Section Name: {sectionName}");
        Console.WriteLine($"Section Type: {sectionType}");
        Console.WriteLine($"Section Flags: {sectionFlags}");
        Console.WriteLine($"Section Size: {sectionSize}");

        // Optionally, read the section data (skip for now)
        fs.Seek(sectionSize, SeekOrigin.Current); // Skip section data for now
    }

    private async Task ParseSymbolAsync(FileStream fs)
    {
        // First, read the name length
        byte[] buffer = new byte[1];
        await fs.ReadAsync(buffer.AsMemory(0, 1));
        byte nameLength = buffer[0];

        // Read the symbol name
        buffer = new byte[nameLength];
        await fs.ReadAsync(buffer.AsMemory(0, nameLength));
        string symbolName = Encoding.ASCII.GetString(buffer);

        // Read the symbol type, flags, and value
        buffer = new byte[6]; // 1 byte for type, 1 byte for flags, 4 bytes for value
        await fs.ReadAsync(buffer.AsMemory(0, 6));

        byte symbolType = buffer[0];
        byte symbolFlags = buffer[1];
        int symbolValue = BitConverter.ToInt32(buffer.AsSpan(2, 4));

        Console.WriteLine($"Symbol Name: {symbolName}");
        Console.WriteLine($"Symbol Type: {symbolType}");
        Console.WriteLine($"Symbol Flags: {symbolFlags}");
        Console.WriteLine($"Symbol Value: {symbolValue}");
    }
}

public class Program
{
    public static async Task Main()
    {
        var parser = new RgbdsObjectParser();
        await parser.ParseRgbdsObjectFileAsync("example.o");
    }
}


new GO term

Would it be possible to create a new term: response to interleukin-33?
PMID:29686383
Thank you
Rossana

Hi @rozaru
Thanks for the suggestion. Why not use the more precise term 'GO:0038172 interleukin-33-mediated signaling pathway' ?

Thanks Pascale! I should have searched with 'interleukin-33' alone. I will use the term you suggested.


Update instructions page (readme.md)

The Readme only has instructions for running using make and seems a little bit outdated.
There is no reference to the JS version at all. I would like to propose adding a mention to the JS version.  I would also like to propose suggesting that one can test out the JS version easily with RawGit. Also, I would add the instruction you wrote on the JS version itself: "If you are opening this file locally (file://), Chrome will give you errors. Try using php -S localhost:8000 or similar for a quick web server."

Thank you, updated

@fulldecent Please Fix the link for the JS version.
On rawgit.com:
"Use a specific tag or commit hash in the URL (not a branch). Files are cached permanently based on the URL. Query strings are ignored. I have provided the proper urls in a comment. Please see my comment on the commit.


sap.mTokenizer + sap.m.MultiInput performance when pasting big number of values

Hi,
I described the issue here:
https://github.com/SAP/openui5/issues/1802
In this PR I see how can fix the performance rerendering problem while pasting big number of values in the multiinput control.

 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.Petr Plenkov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update robots.txt internal template

It's actually wrong syntax to just have a catch-all user agent without allow or disallow rule. Google proposes to have an Allow to allow access to everything. While this is (as of now) working it's false and might stop working at some point. So let's have it properly done :)

 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.

The file you edited is autogenerated. The source lives in a txt file in the templates folder. When you edit one of those you need to run mage generate.

updated


Installation fails with "No matching distribution found for google-fhir-core~=0.8"

I am using https://colab.sandbox.google.com/ with these lines:
!git clone https://github.com/google/fhir-py.git
!cd fhir-py; ./install_all.sh
This is my output:
Processing ./google-fhir-core
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Preparing metadata (setup.py) ... error
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Processing ./google-fhir-r4
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Preparing metadata (setup.py) ... error
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Processing ./google-fhir-views
Preparing metadata (setup.py) ... done
Collecting absl-py~=0.10.0
Using cached absl_py-0.10.0-py3-none-any.whl (127 kB)
ERROR: Could not find a version that satisfies the requirement google-fhir-core~=0.8 (from google-fhir-views[bigquery,r4]) (from versions: none)
ERROR: No matching distribution found for google-fhir-core~=0.8

Hi, sorry for the slow response. We now have this up on PyPI, so you can install via pip by:
pip install google-fhir-views[r4,bigquery]

Hope that helps.


Raise topUpAmount Value

Right now the example code for Topup an identity’s balance results in an error:
Something went wrong:
 [StateTransitionBroadcastError: Asset lock transaction 7d3496d9835cd8885e56fb7fda0021ea60bf7ca3e902b5fd604d1298fceabce2 output 0 only has 1000 credits left out of 1000 initial credits on the asset lock but needs 50000 credits to start processing] {
  code: 10530,
  cause: IdentityAssetLockTransactionOutPointNotEnoughBalanceError {
    __wbg_ptr: 3280960
  }
}

Raising the value of topUpAmount above 50000 as mentioned in the error fixes the issue.
Here's a quick repro of the error if you want to validate the fix.

Preview build: https://dash-docs-platform--53.org.readthedocs.build/en/53/

I recall a comment (either in official docs or on @ajcwebdev's notes) that said the the 1,000 number was "duffs). If so that should have given enough credits to do a lot of txs, but I think we only got 1,000 credits.  Need to look into that.

Thanks for the contribution @ajcwebdev! The SDK method indicates it should be duffs, that may be a typo too. I'm going to merge the fix so at least the example is functional.