Adding purge whitelist options breaks Production Build

Version
@nuxtjs/tailwindcss:  1.4.1
nuxt:  2.11.0
Reproduction Link
None as Build fails, bug is in dev env.
Steps to reproduce
Add purge options as mentioned in the docs - https://tailwindcss.com/docs/controlling-file-size/#removing-unused-css
Example:
module.exports = {
  purge: {
    options: {
      whitelistPatterns: [/agile*/],
      whitelistPatternsChildren: [/agile*/]
    }
  },
  variants: {},
  plugins: []
}

What is Expected?
Skip the agile classes and add them in the css output in production build
What is actually happening?
Breaks the production build with the below error.
ERROR in ./.nuxt/components/nuxt-loading.vue?vue&type=style&index=0&lang=css& (./node_modules/css-loader/dist/cjs.js??ref--3-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--3-oneOf-1-2!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/string-replace-loader??ref--12!./.nuxt/components/nuxt-loading.vue?vue&type=style&index=0&lang=css&)
8:10:13 PM: Module build failed (from ./node_modules/postcss-loader/src/index.js):
8:10:13 PM: TypeError: Cannot read property 'filter' of undefined
8:10:13 PM:     at /opt/build/repo/node_modules/tailwindcss/node_modules/@fullhuman/postcss-purgecss/lib/postcss-purgecss.js:1:483
8:10:13 PM:     at LazyResult.run (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:295:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:208:26)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:14)
8:10:13 PM:     at /opt/build/repo/node_modules/postcss/lib/lazy-result.js:250:14
8:10:13 PM:     at new Promise (<anonymous>)
8:10:13 PM:     at LazyResult.async (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:246:23)
8:10:13 PM:     at LazyResult.then (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:127:17)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:212:17)
8:10:13 PM:     at LazyResult.asyncTick (/opt/build/repo/node_modules/postcss/lib/lazy-result.js:221:1

My guess is that you're missing the content property. Cannot read property 'filter' of undefined, undefined being the content property.
Adding content: [] should fix the problem, but then you wouldn't be purging anything. Could you try adding the following default config and see if it's working?
module.exports = {
  purge: {
   enabled: process.env.NODE_ENV === 'production',
    content: [
      'components/**/*.vue',
      'layouts/**/*.vue',
      'pages/**/*.vue',
      'plugins/**/*.js',
      'nuxt.config.js',
    ],
    options: {
      whitelistPatterns: [/agile*/],
      whitelistPatternsChildren: [/agile*/]
    }
  },
  variants: {},
  plugins: []
}

Well, the build is succeding now, but the whilelisting is now working.
I am still not getting classes for my vue-agile third party plugin and everything is still messed up.

a wild guess: try
whitelistPatterns: [/agile.*/]
(with a dot)
(and I don't think that you need whitelistPatternsChildren)

Tried, does not work.
Even the other nuxt-modules classes are now being removed. For Eg, nuxt-lazy load has stopped working since its classes are now being purged.

Damn this update is so worse than I had thought

Should I just downgrade to nuxt where it had the OG purgeCSS built in and prev TailwindCSS version.

ah sorry I meant whitelistPatterns: [/^agile.+*/].

Nope, does not work. I tried manually adding every single agile class in the whitelist array, it still didnt work.
I know its not vue-agile's issue because it works in dev server.
How it looks in dev server

Here is how it looks in production build

I even tried
purge: {
  enabled: false
}

The slider still wont work, this is very frustating, I used to work with tailwindcss and nuxt every single time in my work flow and never came across this issue.

Same issue here. Whitelisting not working at all...

Same issue here. Using purgecss-whitelister module and getting many errors of
Module build failed (from ./node_modules/postcss-loader/src/index.js):
SyntaxError: 'import' and 'export' may appear only with 'sourceType: module' (7:0)

The only option I currently see to fix this quickly is disabling purging in tailwind and using nuxt-purgecss plugin for purging

Please upgrade to Nuxt Tailwind v2 or v3 since we don't maintain anymore the v1 since Tailwind has an official way of purging the css now.

I'm hitting this as well with the tailwind cli. My purge options look like this:
    purge: {
        content: [
            '../../../../../../../vendor/hyva-themes/magento2-default-theme/**/*.phtml',
            '../../../../../../code/**/*.phtml',
            '../../**/*.phtml',
            '../../../**/*.phtml',
        ],
        options: {
            safelist: [
                // ... a lot of safelist classes
            ],
        },
    }

I don't use any regexes in the purge config.
Full error:
TypeError: Cannot read property 'filter' of undefined
    at web/tailwind/node_modules/tailwindcss/lib/jit/lib/resolveDefaultsAtRules.js:39:60
    at Array.map (<anonymous>)
    at Root.map (web/tailwind/node_modules/postcss-selector-parser/dist/selectors/container.js:347:23)
    at Processor.func (web/tailwind/node_modules/tailwindcss/lib/jit/lib/resolveDefaultsAtRules.js:38:20)
    at Processor._runSync (web/tailwind/node_modules/postcss-selector-parser/dist/processor.js:102:26)
    at Processor.transformSync (web/tailwind/node_modules/postcss-selector-parser/dist/processor.js:171:17)
    at extractElementSelector (web/tailwind/node_modules/tailwindcss/lib/jit/lib/resolveDefaultsAtRules.js:47:47)
    at web/tailwind/node_modules/tailwindcss/lib/jit/lib/resolveDefaultsAtRules.js:82:30
    at web/tailwind/node_modules/tailwindcss/lib/jit/processTailwindFeatures.js:64:50
    at Object.Once (web/tailwind/node_modules/tailwindcss/lib/cli.js:680:15)

Using tailwind 2.2.15, postcss 8.3.1. Happening with tailwindcss --postcss -i tailwind-source.css -o ../css/styles.css


Feature Request:  provide assert_logical_vector()

Feature Idea
While developing sdtm.oak we found it useful to have an assertion function for logical vectors, e.g. assert_logical_vector().
Relevant Input
No response
Relevant Output
No response
Reproducible Example/Pseudo Code
No response

@ramiromagno thanks for the suggest!  Am I to understand that you all developed something like this in sdtm.oak?  Care to share it with us?

Thanks @ramiromagno!  @pharmaverse/admiral what do you think?

Hmmm, I am a bit torn. If admiraldev were a package set up to provide generic checks, then absolutely yes.
But it's a package meant to support admiral, so I am hesitant to expand the scope in that direction. Moreover, we've had informal discussions about migrating admiraldev back into admiral. If that were to happen, then sdtm.oak would have to take on a bigger dependency to continue using these functions.
With a few open questions on this point, @ramiromagno do you think it may be best to add the function directly to your package for now? Something like this would work, or you could make a variant just for logical vectors
check_class <- function(x,
                        cls,
                        allow_empty = FALSE,
                        message =
                          ifelse(
                            allow_empty,
                            "The {.arg {arg_name}} argument must be class
                             {.cls {cls}} or empty, not {.obj_type_friendly {x}}.",
                            "The {.arg {arg_name}} argument must be class
                             {.cls {cls}}, not {.obj_type_friendly {x}}."
                          ),
                        arg_name = rlang::caller_arg(x),
                        class = "check_class",
                        call = parent.frame(),
                        envir = rlang::current_env()) {
  # if empty, skip test
  if (isTRUE(allow_empty) && rlang::is_empty(x)) {
    return(invisible(x))
  }

  if (!inherits(x, cls)) {
    cli::cli_abort(message, class = c(class, "standalone-checks"), call = call, .envir = envir)
  }
  invisible(x)
}

check_class(c(TRUE, FALSE), cls = "logical")
check_class(letters, cls = "logical")
#> Error:
#> ! The `letters` argument must be class <logical>, not a character
#>   vector.

Created on 2024-06-18 with reprex v2.1.0

Hi @bms63 and @ddsjoberg,
The function in question is already included in our package, sdtm.oak. In fact, the suggestion to raise this issue originated from another developer at sdtm.oak. Our team has been operating under the assumption that admiraldev serves as a foundational package for the CDASH -> SDTM -> ADaM continuum, and we have been leveraging it wherever possible to avoid duplicating efforts, particularly for fundamental assertions.
However, if the intent is for admiraldev to be a closer companion specifically to admiral, and other packages should minimize dependencies on it, we can adapt accordingly. For us at sdtm.oak, it should not be overly challenging to start integrating these functions directly into our package.

In principle we shouldn't have such general checks like assert_logical_scalar() in admiraldev because they are not admiral specific. However, I see no value in moving our general checks into a separate general package or removing the general checks from admiraldev and using other packages like checkmate. Thus I would leave it as it is.
@ramiromagno , if you don't want to implement assert_logical_vector() in your package (or remove it from your package), you could use checkmate::assert_logical().

Hi Stefan,
Thanks for the checkmate suggestion. Actually, the team decided to go with admiraldev instead of checkmate for these kind of assertions. But understanding now how you regard admiraldev as very closely related to admiral only we might start changing that.


closed: Failure on upgrade

Hello,
after apply recommendation of @remysa, I have same problem. See #47
acseo_typesense:
# Typesense host settings
typesense:
url: '%env(resolve:SEARCH_URL)%'
key: '%env(resolve:SEARCH_API_KEY)%'
# Collection settings
collections:
articles:                                     # Typesense collection name
entity: 'App\Entity\Article'              # Doctrine Entity class
fields:
id:                                # Entity attribute name
name: id                       # Typesense attribute name
type: primary                  # Attribute type
title:
name: title
type: string
content:
name: content
type: string
dateCreated:
name: date_created
type: datetime
facet: true
imageName:
name: image_name
type: string
default_sorting_field: date_created     # Default sorting field. Must be int32 or float

Please close this issue


Upgrade to RC2

We originally forked PDFBox 2 some time in September, in the middle of development. We just took whatever their latest master was, and then we complained about it being unstable. By now they've released two release candidates. This one is RC2. I hope that the API is now stable, and the code a bit more reliable.
The merge was a complete disaster because of the way you originally did the renaming. Git couldn't figure out that any of the files in the renamed directories go together. So I just did it over again, without renaming the directory. Instead, I renamed the package name from org.apache.pdfbox to org.allenai.pdfbox. It took IntelliJ a good 15 minutes of CPU time to do this, but it was almost completely automatic. I'm hoping that this will make the next merge clean. On the plus side, this means that the whole project builds properly (including at the root level). On the minus side, it means that this is not a drop-in replacement for the first version of pdfbox-ai2.
@rodneykinney, I don't mean to send all my reviews to you, but invariably you're the one who touched the code last, wherever I look. If you want to spread the load a bit better, let me know, and I'll find alternatives.

LGTM. Sounds like a much better way to create a different namespace than what I tried.

How did you originally publish this?

I just uploaded it manually to our nexus.

Dirk are you ok? Why you talking to yourself?

It was supposed to mean "Nevermind, I just did it this way. I don't need the answer anymore."
But I like your interpretation!
Are you following all the pull requests?

Ohh hahaha. That makes a lot more sense.
Apparently I'm watching everything in this repo. Guess I didn't notice before since this doesn't usually change much

I also just uploaded it manually.


[BUG] last transaction shows again after selecting vault in folder

Describe the bug
After doing a transaction and changing to a vault, which is located in a folder, triggers to show the old tx again and unable to open the vault.
To Reproduce
Steps to reproduce the behavior:

Do a tx
change to a vault which is located in a folder
See error

Expected behavior
Able to select vault without triggering old tx again

main branch

@realpaaao This PR should fix all the underlying vault selections within a folder bugs.
https://github.com/vultisig/vultisig-ios/pull/1497
If you get a chance, can you please verify??

it had been fixed in #1497

QA done.


Adapter with different results for cable connection

I have a 400 Mbit Down and 20 Mbit upload contract with cable supplier unitymedia.
Speed and a linux test get me different results. Please check or cant i use this adapter for cable connections ?
web-speedy:
Download: 68.035 Mbit/s
speedtest-cli under debian:
Download: 295.19 Mbit/s

Hi Seqway,
i'm also running a cable connection (Vodafone in Germany)
And i'm also having different results, but like you can see in the issue i've created (Multi-Connections), the reason in my case was comparing the adapter web-speedy which runs single connection tests with another test which runs multi-connection doesn't work.
Try to test single connection under debian with speedtest-cli and compare the results.
Sorry, if you're already running singe connection under debian, just wanted to point out a possible reason.. :)


Handle negative return from fork()

A negative return from fork() indicates an error forking, in which case no child process is created. If this happens, crash hard.
This is a very unlikely edge case, but I've had cases where fork fails because of ulimit rules and whatnot, so may as well handle this case.

Thanks! Sorry for the delay; I've been distracted lately.


refactor: replace toggle color for dark mode #29

Changes description

Findings:
On vitamin, toggle button switch from white to dark depending on the theme selected
Toggle button on iOS dark mode is still white (there is no color switch).
Proposal
In order to respect the platform as much as possible, I propose to replace the semantic coloring by a color base
Context

[x] Fix #29

Checklist

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on an iPhone device/simulator.
[x] If it includes design changes, please ask for a review with a core team designer.

Does this introduce a breaking change?

No

Screenshots

Yes 😅


Fix main contact info breaking pages

Jinja2 imports were unnecessary and breaking the page that the organism main contact info exists on.
Removals

jinja2 imports that were unnecessary and breaking the page

Testing

Go to a page with that organism.

Review

@richaagarwal
@kave

weird... I thought I ran into this and removed them earlier.  but :+1:


Update README.md

/joke

/joke

@PetarTodorovv: Why did the chicken get a penalty? For fowl play.

In response to this:

/joke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/bark

@PetarTodorovv:

In response to this:

/bark

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/meow

@PetarTodorovv:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test pre-submit-job

/test all


Feat/add external integrations

Added:

Docker integrations API
Doppler use

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FEATURE REQUEST] Better nvidia ShieldTV / AndroidTV support

Nice project!
I just sideload it to my (foster) nvidia ShieldTV pro 2015 device (the one with hdd in it) and it works.
But there are some points:

I can no longer used the double-press one home to see my other opened apps

I can not use the "menu + home" button option just because shield users normally (there is a brand new remote) does have this menu button on the physical remote

The listed apps are not all. Would be nice if a user can choose of all apps. Like system settings and so one. Could be useful. And did you know the app "Activity Launcher". See here https://apkcombo.com/de-de/activity-launcher/de.szalkowski.activitylauncher/
With this help to launch custom intent we could do a lot more, I think so. For example with this you can start your fav. netflix movie or show:
https://stackoverflow.com/questions/35556634/movie-deeplink-for-netflix-android-tv-app-com-netflix-ninja

Is there no chance on AndroidTV to ask o the device to grant the WRITE_SECURE_SETTINGS permission?

Did you ever think about to add more options. Like to give the user the chance to choose which buttons do what. For example I would love to use the mic-button on my remote for the custom-app. Then my home, back buttons have the shield-standard behavior.

THX for your nice app and your mentioned love to shieldtv users ;-)

Since I don't have a ShieldTV, I won't be able to fix this – I'm sorry.


Encoder-Decoder (T5) support

Hey!
I needed  EncoderDecoder (T5) models support  for my research, but unfortunately neither TransformerLens, nor nnsight had support for them. So i coded this one)
This PR is mostly based on #276 and HuggingFace implementation of T5
Hope that it is enough to get started with encoder-decoder arhitectures, and merge into the lib. I will continue work on this.
Will be glad to receive any comments
:)
Loading example
from transformer_lens.HookedEncoderDecoder import  HookedEncoderDecoder

path = "results/t5_scratch_adamw_eos_3lay_8head_512d_2048dff_3e-4_400ep/"

#you can load  local custom model or official T5 weights from HF
path = "t5-small"

hooked_model = HookedEncoderDecoder.from_pretrained(model_name=path)

Description

added HookedEncoderDecoder class
added T5LayerNorm, T5Attention, T5Block
changed signature of AbstractAttention.forward
from pos to kv_pos in keys and values associated fields. This was needed for CrossAttention support
add model_state_dict loading from pretrained model
added support of loading models from local folders
See more in transformer_lens/loading_from_pretrained.py:669,1276,1437  Unsure about this one. I need this feature for my research purposes, don't know if this should go into release. (But i believe there's some people, who might find this useful too.

Fixes #258
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Very good! I will be reviewing this relatively quickly, but before I do that, can you do me a big favor, and add a demo, similar to the BERT demo you referenced in the other PR, so that the usage of this can be shown in detail for the future?

Thank you!
Feel free to point to any weak spots in the code, im totally okey with it and will fix them as soon as possible)
Added a simple demo of t5 on how to run it with cache, visualise attn patterns and topk token logits

Thanks for the great work! I will hopefully have time to to review the whole thing this week. I have a few bugs that I need to fix, and hopefully nothing comes up after that.

Alright, so now that 2.0 has been put up I have sometime to review this. There is quite a bit changing with standards for code submissions in this project, which mainly revolve around improvements to unit testing, and a couple changing standards. What you have done so far looks pretty good, but given the changing standards I am going to request a few things to make sure we are moving closer towards the new standards.
That being said, the first thing I would like to check is to make sure you replace any asserts outside of tests with an if block and the throwing of an error. This is one of those things that isn't an official requirement yet for the code, but it will be very soon, and anything new coming in should be in this new format.
The second thing that I am going to ask is that we improve the test coverage a bit. The test you added is good, but I want to get some unit tests in here to test different bits of functionality in isolation a bit more. The two new components should have a unit test setup for them with the same directory structure. (e.g. a test at tests/unit/test_t5_block.py. Then in that unit test we need to test the individual groups of logic in isolation. This means that it might be a good idea to separate something like the different operation groups found in your forward function into smaller functions, so that we can focus in on those operations to ensure that they are being applied correctly.
If you have any questions on what I mean with this, let me know. I am happy to help you with improving the test coverage. It's pretty late here, so I don't have time to do any specific examples of what I mean, but I can do that either tomorrow or Monday if you want to wait for me to demonstrate exactly what I mean.

Hi!
Thank you for the feedback!
Made a quick fix to ensure asserts are replaced with ifs and errors
understand the issue with coverage, i will try ti cut some time to fix it on this week
Could you be more specific in

separate something like the different operation groups found in your forward function into smaller functions

you mean in HookedEncoderDecoder.forward() or in T5Block?

Honestly, after really taking a full look at what you did, I think we are probably fine. What I was referring to when I made the comment about separating functionality in your forward function, I was referring to your forward function on the T5Block, but after really having time to dig into your code today, I think what you are doing is fine.
We are looking to find more ways to test blocks of functionality in isolation for the purpose of creating better unit tests. When it comes to doing that task on some of the classes you added, we may break it down a little bit more, so we can run tests to specific parts of your forward without touching the rest of it, but for the purpose of getting this into a release, I don't think there will be anything else requested of you.
I will mess with your demo to verify a few last minute things tomorrow, and hopefully I will get this closed out at the same time. Thank you very much for your contribution here. I will let you know if anything else comes up, but I wouldn't expect anything.


Change Blazor-Fluxor to just Fluxor

As the author notes on Blazor-Fluxor README

Blazor.Fluxor has now been migrated to Fluxor

Thanks!


enhance  shenyu-register-client module unit test, and add NacosClient…

…RegisterRepository close detail. add config and naming service to shutdown
// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ √] You have read the contribution guidelines.
[ √] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1471 (f3241d5) into master (b5891ac) will decrease coverage by 0.07%.
The diff coverage is 60.00%.

@@             Coverage Diff              @@
##             master    #1471      +/-   ##
============================================
- Coverage     63.40%   63.33%   -0.08%
  Complexity     2035     2035
============================================
  Files           407      407
  Lines          8797     8804       +7
  Branches        880      881       +1
============================================
- Hits           5578     5576       -2
- Misses         2800     2811      +11
+ Partials        419      417       -2

Impacted Files
Coverage Δ
Complexity Δ

...er/client/nacos/NacosClientRegisterRepository.java
66.03% <60.00%> (+1.45%)
6.00 <1.00> (+1.00)

...enyu/client/tars/TarsServiceBeanPostProcessor.java
23.17% <0.00%> (-6.10%)
5.00% <0.00%> (-1.00%)

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
10.00% <0.00%> (ø%)

...elimiter/handler/RateLimiterPluginDataHandler.java
69.23% <0.00%> (-1.54%)
14.00% <0.00%> (ø%)

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <0.00%> (-0.62%)
12.00% <0.00%> (ø%)

...nyu/sync/data/http/refresh/DataRefreshFactory.java
100.00% <0.00%> (ø)
5.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


Unable to run Rails when gem is installed

After successfully installing the gem (tokenizers (0.2.2-arm64-darwin)), I'm unable to open Rails console:
➜ rails console
[1]    8415 killed     rails console

When trying to install HEAD version, I get this error message:
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
…snip…
thread 'main' panicked at 'rustfmt is required to generate bindings. To install, run `rustup component add rustfmt`: Os { code: 2, kind: NotFound, message: "No such file or directory"
}', /Users/marc/.cargo/registry/src/github.com-1ecc6299db9ec823/rb-sys-build-0.9.56/src/bindings.rs:77:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
make: *** [target/release/libtokenizers.dylib] Error 101

Hey @marckohlbrugge, thanks for the report. Looks like this is a similar issue to Polars Ruby (https://github.com/ankane/polars-ruby/issues/2).
Are there any crash reports in the Console? https://support.apple.com/guide/console/reports-cnsl664be99a/mac

I've shared a crash log with you privately via Twitter DM.
Looks like it might be a code signing issue?
Here's a summary of the log:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               ruby [38389]
Path:                  /Users/USER/*/ruby
Identifier:            ruby
Version:               ???
Code Type:             ARM-64 (Native)
Parent Process:        zsh [21260]
Responsible:           iTerm2 [618]
User ID:               501

Date/Time:             2023-01-22 10:57:50.6255 +0700
OS Version:            macOS 13.1 (22C65)
Report Version:        12
Anonymous UUID:        [removed]

Sleep/Wake UUID:       [removed]

Time Awake Since Boot: 130000 seconds
Time Since Wake:       2259 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Codes:       UNKNOWN_0x32 at 0x000000010381c000
Exception Codes:       0x0000000000000032, 0x000000010381c000

Termination Reason:    Namespace CODESIGNING, Code 2 Invalid Page

Not sure if this is the correct way to verify a code signature, but it does say invalid signature
codesign --verify /Users/marc/.asdf/installs/ruby/3.0.3/lib/ruby/gems/3.0.0/gems/tokenizers-0.2.2-arm64-darwin/lib/tokenizers/3.0/tokenizers.bundle
/Users/marc/.asdf/installs/ruby/3.0.3/lib/ruby/gems/3.0.0/gems/tokenizers-0.2.2-arm64-darwin/lib/tokenizers/3.0/tokenizers.bundle: invalid signature (code or signature have been modified)
In architecture: arm64

Manually replacing the signature allowed me to use tokenizers! Of course it's not a proper solution, but it does confirm it's a code signing issue.
sudo codesign -f -s - /Users/marc/.asdf/installs/ruby/3.0.3/lib/ruby/gems/3.0.0/gems/tokenizers-0.2.2-arm64-darwin/lib/tokenizers/3.0/tokenizers.bundle
Password:
/Users/marc/.asdf/installs/ruby/3.0.3/lib/ruby/gems/3.0.0/gems/tokenizers-0.2.2-arm64-darwin/lib/tokenizers/3.0/tokenizers.bundle: replacing existing signature

@ankane It's possible you've signed it which a key that works fine on your machine, because you're the developer. If you have a hard time figuring debugging the issue I recommend booting up a virtual machine where you're not logged in with your developer account.

Awesome, thanks @marckohlbrugge! I think it's probably due to stripping symbols and debuginfo, so either need to disable that or re-sign afterwards. Will fix and try to get a release out tomorrow.

New version is out with a valid signature. Thanks again!


Calamares Installer: uploaded log pastes are truncated

Describe the bug
Logs pasted to https://termbin.com are incomplete, most probably because besaid paste service has a certain size limit.
Errors usually happen in the end, so the pasted log is useless as it does not contain the relevant bits.
Steps To Reproduce
Steps to reproduce the behavior:

boot https://channels.nixos.org/nixos-22.11/latest-nixos-gnome-aarch64-linux.iso
run into any failure during install
agree to paste the install log to the web
get a link to it, e.g. https://termbin.com/m946k

Last three lines from that link to illustrate:
  /nix/store/ri0f2k1aqp46ddf6x10cbf2xrvzq0y0a-ed-1.18
  /nix/store/ri6x31kpn0giiifx4i9vwbaly0ajw88j-cryptsetup-2.5.0
  /nix/sto

Expected behavior
Pasted logs should be complete.

The actual error is now lost, at least to anyone who does not know how to manually recover logs from the live installer system.
Clicking on "OK" immediately closes the graphical installer.


Got Trainer error: typing.Optional requires a single type.

When running the notebook code for training the unet (part 3), I got this error:
TypeError: typing.Optional requires a single type. Got <module 'torch.optim.lr_scheduler' from 'C:\Users\AppData\Local\Programs\Python\Python3.

Looking into it. My first guess would be the Python version, which one are you using @unimusic?

Hi, sorry for the delay. I am using Python 3.10.6.

Hi, try to use Python 3.8 or 3.9. Let me know if this resolves the issue. @unimusic

I decided to remove the optional and default from that line, so I just have lr_scheduler: torch.optim.lr_scheduler, now. It works for my purposes. Thanks!


Better readability for text used over image

Describe the bug
Having difficulty reading white text used over the background image on mobile screens and medium screens.
Expected behavior
Bring more readability to the text used over background image on smaller screens
Screenshots

Additional context
I'd could make the background image a bit darker using linear gradient for only mobile and medium screens as the readability is fine for larger screens. Doing so will imporve the readbility drasticaly.
I would like to work on this

@akshitagupta15june hey new contributor here. Can I make it responsive enough for all screens with screen contrast ?

thanks for this issue i am planning to change background image


Improving live timing readability

There is a main issue currently: the players list gets squeezed vertically because of the cars' names getting word wrapped, and therefore becomes very difficult to read even on wider screens, especially when the cars' names are very long.
Perhaps being able to choose which columns to display / hide might be a workaround? (maybe also separate car skin name and car name in different columns could be a good idea)
Here is an example of what I mean

We could look into hiding columns, although we are considering removing the skin name from the car entry completely as it isn't really useful in the context of the live map.

We could look into hiding columns, although we are considering removing the skin name from the car entry completely as it isn't really useful in the context of the live map.

That makes sense, telling the name of the skin doesn't really tell  anything. A full skin preview would make sense, but that would just make the whole list even more difficult to read, so yeah


bump(github.com/fsouza/go-dockerclient):42d06e2b125654477366c320dcea99107a86e9c2

@csrwng @jhadvig ptal.

going to do the bump here instead:
https://github.com/openshift/source-to-image/pull/263


Kyuubi Cassandra Integration enhancement

1. Describe the feature
ANSI SQL 92 standard queries can not run directly on Cassandra hence Kyuubi can run the queries and get the result.
2. Motivation
Recent years Cassandra is much popular as data storage and most BI tools need a Cassandra adaptor. Kyuubi can solve the problem.
3. Describe the solution

packaging kyuubi Spark Cassandra open-source driver part of the library.

provide the necessary configuration to Kubbi config file or hive JDBC url

documentation for Kyuubi  cassandra integration

4. Additional context
Small java or scala sample code to run a query to retrieve data from cassandra,

thank you @kmsantanu. Are we going to add a friendly user guide to introduce how to integrate Kyuubi with Cassandra using https://github.com/datastax/spark-cassandra-connector?
Also cc @pan3793


PROD-550: Credit Cost Per Question Deck Form Admin

Description
Add new select input in Deck form to allocate credits to each questions - Credit Flow (Featured flag)

What are the steps to test that this code is working?
Create a new deck or edit existing deck, you will see Credit Cost property at second last in the form

Screen shots or recordings for UI changes
NA

Tests are failing due to migration


jMAVSim HITL Navigation Failure

Describe the bug
I am trying to run a HITL simulation using jMAVSim following these instructions: https://dev.px4.io/en/simulation/hitl.html. I am running the master PX4 firmware. Whenever I try to takeoff, the shell says "Takeoff detected" and then it says "CRTICIAL NAVIGATION FAILURE - CHECK SENSOR CALIBR". Then it goes completely unstable and moves uncontrollably with the Pixhawk flashing purple light.
Expected behavior
I expected the drone to takeoff and hold in position.
Log File
Log file: https://logs.px4.io/plot_app?log=db2a6cfd-84ef-4971-87d3-dc897e542431
These are the messages I see:
MSG: ARMED by arm/disarm component command
MSG: [logger] file: /fs/microsd/log/2018-06-19/17_31_4
MSG: Takeoff detected
MSG: MANUAL CONTROL LOST (at t=139348ms)
MSG: MANUAL CONTROL REGAINED after 666ms
MSG: CRITICAL NAVIGATION FAILURE - CHECK SENSOR CALIBR
MSG: Failsafe enabled: no local position
MSG: Failsafe mode enabled
Drone:

Describe the type of drone:
DJI Flame Wheel F450Quadrotor x (4011)

Additional context
SITL simulation is working fine for me, but only having this trouble with HITL.

Sometimes the navigation doesn't fail, but it says "Takeoff detected" and "Landing detected" as I move the throttle stick, but nothing happens in the GUI.
According to this flight log: https://logs.px4.io/plot_app?log=86679494-993a-410d-aca1-b1f8eb9cf326
It seems as though it is getting the throttle RC input, but it is not changing the z velocity or local z position.

Can you please configure the HITL multicopter configuration instead? That will likely resolve your issue.

I just tried that, and it has the same issue (getting a throttle input but no change in the z position and no movement in the jMAVSim)
Log: https://logs.px4.io/plot_app?log=832a6e3f-f057-4172-ab60-79ca36708934

I just tried AirSim (https://dev.px4.io/en/simulation/airsim.html), and it has the same issue (says takeoff/landing detected, but nothing happens in the simulator). This means that it definitely isn't a problem with the simulator, but something wrong with the firmware I would suspect. Any ideas? Could someone try HITL and see if it's working for them?

@bkueng Could Nico try this and report back?

Just for some more info, HITL works on my Pixhawk using v1.4.4 firmware (I just picked some old version to see if maybe there was something wrong with my hardware), but it doesn't work with v1.8. I will try to find the newest version where HITL works.

Yes, HITL also work on v1.7.0 stable release.

@bkueng Could Nico try this and report back?

@nicovanduijn ^

I've been trying to reproduce, but couldn't so far. When setting COM_RC_IN_MODE to Joystick/No RC Checks it arms and takes off just fine on my machine. I'm looking for an RC now to see if I can reproduce

@mrehan3 It works just fine for me with a PixRacer and a Taranis.

What hardware are you using? (Flight controller, RC)
Can you once again confirm that you are
a) Running PX4 v1.8 (seems fine from the log you uploaded though)
b) Have chosen the HIL Quadcopter X in Airframe (reboot to apply setting)
c) Have unchecked all AutoConnect boxes except for UDP under the General tab of the settings menu
in QGC
d) Have set NAV_DLL_ACT to "Disabled"
e) Have set COM_RC_IN_MODE to "RC Transmitter" if you are indeed using a remote as described
f) Have your remote properly bound to the receiver and calibrated with QGC

If all of those are as we expect, my guess is as good as yours... It works on my machine

@nicovanduijn
It still doesn't work for me on v1.8 :(

The hardware I am using is the 3DR Pixhawk 1 and the FS-TH9X RC.

a) Reloaded PX4 v1.8 again (log and QGroundControl confirm that it's running v1.8)
b) Definitely chose HIL Quadcopter X (confirmed in log and QGroundControl)
c) Unchecked everything except UDP
d) NAV_DLL_ACT is disabled
e) COM_RC_IN_MODE is set to "RC Transmitter"
f) RC is correctly bound and callibrated (can see throttle and other stuff moving in QGroundControl)
Here are some more logs:
On v1.7 (it works here): https://logs.px4.io/plot_app?log=7960fcec-40d0-429b-8f80-cc48eed67642
On v1.8 (does not work here, just says takeoff/landing detected): https://logs.px4.io/plot_app?log=b53ec207-f810-4c1f-aba7-97b39bb7448a

@nicovanduijn
I am using pixhawk 1 by Radiolink and followed all the steps you mentioned. I am still facing the same issue.
Another question :
When i uploaded the V1.7 .px4 using QGC, i am still using the latest repository of firmware that i have cloned to use jMAVSim HITL command.
Is that okay ??
Thanks

@sivateja619 I used the latest repository to run the jMAVSim command and it worked fine for me when v1.7 was flashed onto the pixhawk (through QGC)

@sivateja619 I'm not sure how backwards compatibility is. To be on the safe side, just do a
git checkout tags/v1.7.0 && git submodule update --init --recursive.
@mrehan3 I found a pixhawk 1 laying around somewhere and was indeed able to reproduce what you described. Haven't had time to get to the bottom of it yet. Seems that HITL and v1.8 on the pixhawk 1 doesn't work

@nicovanduijn I was able to downgrade to V1.7 but, while testing HITL, can see the quad flipping by itself and shooting up an error "check sensor calibr". Also, i tried with  COM_RC_IN_MODE to Joystick/No RC Checks.
Arming/disarming, selecting flight modes is all good. But, the flight itself is an issue.
SITL is working fine.
Is it a problem with my hardware (pixhawk 1 by Radiolink) ?

Hi, I'm having a similar issue: trying HIL on pixhawk FMUv2 and I get zero output on hil actuator controls even though everything else seems OK. I traced this (I think) to pwm_out_sim not being present on the firmware, which I guess is responsible for outputting the actuator controls. See the error about the command not found. It seems that this command is not built for FMUv2, is this intentional?

nsh> INFO  [logger] Start file log
INFO  [logger] Opened log file: /fs/microsd/log/2018-07-10/21_52_44.ulg
INFO  [commander] Takeoff detected
INFO  [commander] Landing detected
WARN  [load_mon] init low on stack! (268 bytes left)
WARN  [load_mon] init low on stack! (268 bytes left)
WARN  [load_mon] init low on stack! (268 bytes left)
WARN  [load_mon] init low on stack! (268 bytes left)
INFO  [logger] closed logfile, bytes written: 213472
WARN  [platforms__common] Reboot NOW.
WARN  [dri�
FMUv2 ver 0x8 : Rev 0 V2
[boot] Fault Log info File No 4 Length 3177 flags:0x01 state:1
[boot] Fault Log is Armed
sercon: Registering CDC/ACM serial driver
sercon: Successfully registered the CDC/ACM serial driver
HW arch: PX4FMU_V2
HW type: V2
HW version: 0x00090008
HW revision: 0x00000000
FW git-hash: 96443b3cf3e3adaec8b2ebb6c83a19a92d40a13f
FW version: Release 1.8.0 (17301759)
OS: NuttX
OS version: Release 7.22.0 (118882559)
OS git-hash: 63775322bf25adb406594f8e610122fe0cef2f7a
Build datetime: Jun 19 2018 06:36:49
Build uri: BUILD_URI
Toolchain: GNU GCC, 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
MFGUID:<PHONE_NUMBER>34511100380033
MCU: STM32F42x, rev. 1

WARNING   WARNING   WARNING!
Revision 1 has a silicon errata:
This device can only utilize a maximum of 1MB flash safely!
https://pixhawk.org/help/errata

UID: 380033:30345111:37383933
[hardfault_log] Fault Log is Armed
INFO  [tune_control] Publishing standard tune 1
INFO  [param] selected parameter default file /fs/mtd_params
rgbled on I2C bus 2 at 0x55 (bus: 100 KHz, max: 100 KHz)
nsh: rgbled_pwm: command not found
INFO  [dataman] In flight restart, data manager file '/fs/microsd/dataman' size is 350216 bytes
INFO  [load_mon] stack check enabled
ERROR [param] Parameter UAVCAN_ENABLE not found
nsh: pwm_out_sim: command not found
INFO  [tune_control] Start playback...
WARN  [load_mon] init low on stack! (268 bytes left)
INFO  [tune_control] Playback finished.
ERROR [px4io] RECOVERING FROM FMU IN-AIR RESTART
WARN  [commander] Failsafe enabled: no RC
WARN  [load_mon] init low on stack! (268 bytes left)
px4io re-sending arm cmd
INFO  [px4io] default PWM output device
INFO  [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B
INFO  [mavlink] mode: Onboard, data rate: 80000 B/s on /dev/ttyS2 @ 921600B
ERROR [param] Parameter UAVCAN_ENABLE not found
px4flow [159:100]
WARN  [px4flow] scanning I2C buses for device..
INFO  [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
ERROR [mavlink] offboard mission init failed (-1)
INFO  [init] Mixer: /etc/mixers/quad_x.main.mix on /dev/pwm_output0
INFO  [init] Mixer: /etc/mixers/pass.aux.mix appended to /dev/pwm_output0
INFO  [logger] logger started (mode=all)

Confirmed my suspcicion, see discussion here: https://github.com/PX4/Firmware/commit/22acb1dab1483fcbf618a8836864750ff8596b8f#r28613651
Could be re-enable this by default? Or is flash size limiting? Maybe there's another not so critical module that can be disabled instead, loosing HITL ability is pretty bad IMHO.

I believe @bkueng made this change to limit the flash space usage. You may not be able to fit the firmware into memory on the older hardware, but give it a shot

I finally recompiled with the module enabled and indeed this was the reason for zero outputs. Anyways, the outputs were really erratic. They would appear to react to actuator targets but oscilate between minimum and maximum very aggressively. For now I will not continue with HIL as it seems there are still some problems.


Enhance CI settings (avoid the need tomanually add new apps)

Right now, from the list of #24, I'm just addressing the minimize need for manual maintenance (all new modules are included by default in Coveralls and Code Climate), which IMHO was the most important thing.
I still can go further with:

Using some defaults for some settings and minimize the usage of the web panel for env vars;
If so, I'd probably use dj-database-url;
And surely investigate what is causing timeout in Travis, i.e. #21

Any thoughts?

Coverage decreased (-0.7%) to 95.865% when pulling 7f440e148ce2f56fa4fd47d44372b4c73f3943f1 on cuducos:ci-settings into e3e2fa39e73cdc492ad0ff5323ec68f16ad4b424 on dirtycoder:next.

@dirtycoder I'm gonna push a new commit that will fail on Travis CI until we update the environment variables needed.
You can delete all of them except OPBEAT_DISABLE_SEND, and add DATABASE_URL=postgres://postgres@localhost/pets, ok?
When you have only these vars, can you restart the build at Travis?

Coverage decreased (-0.7%) to 95.865% when pulling fd44d25c973d24f867c856ad7db69b4a9522f039 on cuducos:ci-settings into e3e2fa39e73cdc492ad0ff5323ec68f16ad4b424 on dirtycoder:next.

Reading the code I just spotted an error I introduced some time ago, here.
Csv() expects a string, so the correct value would be an empty string '', but I have another idea.
For the SECRET_KEY and the DATABASE_URL I'd prefer to not have a default value, as it's an important configuration I'd want it to be a complete "show stopper" if not properly configured, instead of letting the user run the project with a wrong setting.
Running with the default could lead to bad results like the file system being erased, in case of sqlite and Heroku, or creating a security problem running with the known secret_dummy_key value for SECRET_KEY.

Reading the code I just spotted an error I introduced some time ago, here.
Csv() expects a string, so the correct value would be an empty string ''.
For the SECRET_KEY and the DATABASE_URL I'd prefer to not have a default value, as it's an important configuration I'd want it to be a complete "show stopper" if not properly configured, instead of letting the user run the project with a wrong setting.
Running with the default could lead to bad results like the file system being erased, in case of sqlite and Heroku, or creating a security problem running with the known secret_dummy_key value for SECRET_KEY.

Great ideas, man!
I basically addressed all the issues you raised in the scattered commits above. Does it look better?

Coverage decreased (-0.7%) to 95.865% when pulling ff5858d1772dd092344c895468e336a7e2dbf6b9 on cuducos:ci-settings into e3e2fa39e73cdc492ad0ff5323ec68f16ad4b424 on dirtycoder:next.

@cuducos sorry for the slow pace of review, a lot of things to do.
Anyway, everything looks great now, thanks!
I think we are good to go here, could you rebase this in a single commit? :)
The last build timed out, don't know if you can get the information needed to investigate the problem from the log.
But here is an idea, I think you could configure your own repo on Travis CI and then ask them to enable de debug there, so you could connect to the build machine.

I think we are good to go here, could you rebase this in a single commit? :)

Great news, then!
I still have to investigate the timeout thing (not only this one, but #21 too) before rebasing and considering it a ready to merge PR hahaha…

As #21 is the issue that really deals with the timeout, I'm ok to merging this one, if the tests passes when a timeout don't occur.
I think the current PR deals with the issues raised in #24, but with the rebase and a new commit push, the tests will run again and a new timeout could not occur.
Thank you very much.
I'll leave this up to you to decide what to do. :)

Already running tests on my fork, allow me a few days of exploration, if I figure out anything we fix here. Otherwise we keep #21 alive and merge this PR, ok? I'll come back with some news soon!

Ok, thanks! :)
Great!

I got in touch with Travis support and in fact the containers, Selenium and PhantomJS aren't best friends. There is an approach of retries that seem to be working in other projects, but I don't have time to implement this on Pets that quickly.
So it's up to you: feel free to merge this and leave #21 for another PR (let me know and I paste this reference there), or keep this PR open until one of us are able to try to implement this workaround.

@cuducos hey man thx for you time!
I'll merge this PR an close the related issue once the Travis builds are green. :tada:
I'll leave the #21 open for now, I was thinking about it and probably I'll migrate to Firefox + xvfb in the CI server as it feels less "hacky" and people writing test code don't need to have an extra care using functions that are not standard.

Coverage decreased (-0.7%) to 95.865% when pulling 715caf885f13445ac91681724d14ccaf2efdc69d on cuducos:ci-settings into 3cbdf625d4535f32150df3182b0e4c12ac96fde1 on dirtycoder:next.

Coverage decreased (-0.7%) to 95.865% when pulling 679c76973adce52dfe686a7b448b9f5d28e593fb on cuducos:ci-settings into 3cbdf625d4535f32150df3182b0e4c12ac96fde1 on dirtycoder:next.


new style for clay-starter sample article

added style, css to clay starter sample-article.html

fallow https://app.zeplin.io/project/5c6f153327f5b4405c6ce26c/screen/5c6f155c6d6dc440975b3bda
for design.

Also needs a rebase


New version detection - error

When I download latest version 1.4.12 and start it, I got immediatelly a message, that there is a new version 1.4.9 available, what is wrong.

The latest is 1.4.12.
This bug works also vice versa. If I install 1.4.9, there is a message that this is latest version.

Same issue with 1.4.10 and 1.4.11, all are linking to 1.4.9.

The problem is located here: CheckForNewVersionAbstract#done() line 68 if (current.compareTo(running) > 0) the version Strings are compared with the default String#compareTo() therefore 9 > 10. The solution would be to parse the three parts of the version String into numbers and compare the integers.

I think the problem is the not responding URL:
http://otroslogviewer.appspot.com/services/currentVersion?runningVersion=1.4.13&java.version=1.8.0_322&os.name=Linux&vm.vendor=Amazon.com+Inc.&uuid=1187f187-ec57-4072-873f-1dec947c79b3
The server Response:
Error: Server Error
The server encountered an error and could not complete your request.

Please try again in 30 seconds.

I think it must be rewritten. See #534

Fixed with #602


nixos-rebuild: Add missing passed-through options to man page and completion

Description of changes
This is syncing the man page and bash completion with the options. This fixes #16770.
In addition it adds the repl command to the bash completion.
I'm also adding myself to CODEOWNERS to ensure the bash completion doesn't drift again.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Github says there is an error in CODEOWNERS related to jonringer being listed there, but being an "unkown owner"
I didn't know if that would impact merging this change, but thought I'd mention it

The same errors are in master: https://github.com/NixOS/nixpkgs/blob/master/.github/CODEOWNERS
Though since the ban is temporary, not an issue.


Is this project abandoned?

Is this project abandoned?
I tried looking for the demo site for Jingo 1.x and it appeared to be down, but stumbled upon reference to this next version. Is this still being worked on?
There appears to only be one other Node.js based wiki engine, and with 44 open PRs, it's development appears stalled. Seems like the community may benefit from options in the space?

@broxen thanks for asking! I am trying to restart development in this project, at least to bring it to a stable version 1. I hope by the end of the year to have it ready 👍🏻

(development in Jingo 1 is definitely stopped since the codebase is really old)


Start working on pipeline parallelism

Addresses #105

This seems to pass some preliminary tests, was able to load gpt-j-6.7B and things ran just fine. I'll probably test more thoroughly later, but would also appreciate input on design!

I tested loading gpt-j-6b on 7 GPUs and things were fine (was able to generate text and it seemed sensible). I'll try OPT-66-B and let you know how that goes.
One thing that makes me a bit sad is that the current implementation enforces that the number of devices be divisible by the number of transformer blocks - idk if I have an elegant way of making this a not strict requirement and still somehow having a nice balance of layers on each device.
I was also considering keeping the token and position embeddings, final layer norm, and unembed all on the same gpu (probably the rank 0 one) and then splitting the layers across the remaining GPUs. This would be cleaner in a few ways since inputs and outputs would all be on the same device. Lmk what you think of that.
I also like adding mixed precision, I'll try working that in.

Hi @anshradh - nice work on this! The simple approach is great.
A few additional comments:

Please can you remove the unrelated code changes (e.g. formatting changes) so that the final PR is easier to review? We can add extra linting/formatting to the whole codebase (and this would be great) but it would be better to do this separately.
The if n_devices == 1 ... else ... logic isn’t needed and makes testing hard. The code can be written such that it works for any number of devices (including 1) without these if/else statements. In fact it looks like it mostly works if you just delete the  if n_devices = 1 blocks.
Can you also split this logic out into it's own util function/method. This can be tested with pytest for the various use cases (including just one device). We're trying to add tests to the codebase going forwards (I've just recently merged in a CD pipeline to help with this).

Thanks @alan-cooney!
Made the suggested changes - I think I'm a little uncertain if the refactor into a util method was in the form that you were looking for. If not, happy to make further changes. I can also write tests once this looks good!

Thanks @anshradh - there still appear to be lots of formatting changes (see https://github.com/neelnanda-io/TransformerLens/pull/125/files ) - are you able to remove these?

Argh sorry about that! My editor's saveOnFormat was a bit trigger happy, even after being disabled ... My bad for also not doublechecking that all of the formatting changes were reverted properly. Things look ok now?

Argh sorry about that! My editor's saveOnFormat was a bit trigger happy, even after being disabled ... My bad for also not doublechecking that all of the formatting changes were reverted properly. Things look ok now?

No worries - thanks for doing that! I think this may also represent a wider thing that we should have some linting config committed to keep editors happy.

I think I'm a little confused about the testing strategy we want here, given that the tests need to run on a CPU-only machine. Would you mind explaining a little further/suggesting some tests that you might write for this? I can obviously test the utility function on various inputs, but I'm not sure I see an avenue for something closer to an integration test involving loading and running a forward pass on a full model.

I think testing the utility function alone (esp if it includes this extra logic) should get us to a high degree of confidence, so pragmatically this may be enough.
I think we should also have an integration test mocking out torch.to(device), but I'm not sure exactly how to do this with PyTorch. Happy to pull that out as a later task therefore. As long as we have good unit test coverage + manual tests with multiple GPUs, I think it should be enough for now.

Curious what the state of this PR is?

Ah, sorry about this - been busy with REMIX and interviews. I think I should definitely be able to wrap this up by end of the month (probably shouldn't be much more than a few hours of work), though someone should feel free to finish it off if they'd like to. I think the only remaining thing is to implement tests, though as Alan and I discussed above, I think this is slightly nontrivial, though not super complicated.

No rush! Just wanted to check it wasn't blocked on me lol
On Fri, 20 Jan 2023, 4:33 am Ansh Radhakrishnan, @.***>
wrote:

Ah, sorry about this - been busy with REMIX and interviews. I think I
should definitely be able to wrap this up by end of the month (probably
shouldn't be much more than a few hours of work), though someone should
feel free to finish it off if they'd like to. I think the only remaining
thing is to implement tests, though as Alan and I discussed above, I think
this is slightly nontrivial, though not super complicated.
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/125#issuecomment-1397911971,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKIH55AFQ6FTKAK4I2DWTIIQPANCNFSM6AAAAAATITHWXI
.
You are receiving this because your review was requested.Message ID:
@.***>

Also happy to pairs code on writing the tests next week if you want

Tasks to do (discussion between me and @rusheb )

[ ] test the utility function on various inputs
[ ] Work out if it's possible to have an integration test mocking out torch.to(device)
[ ] either way, write a manual test script which can be be run semi-regularly on a machine with multiple GPUs (something closer to an integration test involving loading and running a forward pass on a full model such as GPT2)

I can try to get this over the line!
@jbloomAus are you happy to give me write access so I can push to @anshradh's branch?
If not, I can clone the branch onto my fork and raise a new PR.
Let me know!

@rusheb, I don't think this is possible without @anshradh's help, I'll ask them.

I think you'd just have to add @rusheb as a collaborator?

I've pinged @neelnanda-io about this since I don't have the ability to do that :)

Hi, I got a last-minute invitation to an ML bootcamp which I will be working on full time for the next 2 weeks. If this PR is still open when I return then I can pick it back up then!

I spent a bunch of time trying to "mock" GPUs for testing yesterday to make testing of the multi-GPU code more frequent. That turned out to be hard, and there weren't any apparent solutions online. I will probably spin up some GPUs and write bespoke test scripts that we can run before releases.

Alrighty so an update:

I attempted "Work out if it's possible to have an integration test mocking out torch.to(device)" which was HARD. No clear answers online such as on the pytorch forums. I gave it several hours and discovered some limitations of GPT4/maybe just python. It's hard to mock a complex type signature like the method .to in pytorch because it sometimes gets passed a tensor and sometime just a device. I couldn't always retrieve the original tensor making it hard to mock the output.
test the utility function on various inputs I assume this is test_get_device_for_block_index which I have written a test for. I don't think there's a huge amount of complexity to test. Maybe raising an error if the inputs are wrong is something we should add/test but I'm not super concerned by it.
I've written a test for n_devices varying which only activates if the computer has 4 gpu devices. This test checks the following:

The code runs for 1 <= n_devices <= 4.
The logits/activation cache matches for 1 <= n_devices <= 4.
The devices are assigned a roughly equal proportion of layers in the model.

I think these tests are likely sufficient. We can run them pretty easily before releases and people working with multiple GPUs can also run them after they install the package.
@alan-cooney @neelnanda-io I think it should be fine to merge this PR. I'll wait a day or two in case you want to comment/suggest modifications to the tests but otherwise will merge soon :)

I attempted "Work out if it's possible to have an integration test
mocking out torch.to(device)" which was HARD. No clear answers online such
as on the pytorch forums. I gave it several hours and discovered some
limitations of GPT4/maybe just python. It's hard to mock a complex type
signature like the method .to in pytorch because it sometimes gets passed a
tensor and sometime just a device. I couldn't always retrieve the original
tensor making it hard to mock the output.

Dumb question - why can't you mock it out with a function that checks
whether the input is a string, device or tensor, and deals with it
differently accordingly?
But yeah, looks decent.
My one concern is that, as is, there's not a way to have a cache keep
tensors on device, or have a hook layer know what device it's on (I
think?). IMO this is a fairly important feature to add to run_with_cache,
if it's not too big a headache, because communicating large tensors between
devices can be a major performance overhead. I would implement it by giving
each HookPoint a self.device parameter, and having run_with_cache use
that unless overridden.
On Sun, 9 Apr 2023 at 02:32, Joseph Bloom @.***> wrote:

Alrighty so an update:

I attempted "Work out if it's possible to have an integration test
mocking out torch.to(device)" which was HARD. No clear answers online
such as on the pytorch forums. I gave it several hours and discovered some
limitations of GPT4/maybe just python. It's hard to mock a complex type
signature like the method .to in pytorch because it sometimes gets
passed a tensor and sometime just a device. I couldn't always retrieve the
original tensor making it hard to mock the output.
test the utility function on various inputs I assume this is
test_get_device_for_block_index which I have written a test for. I
don't think there's a huge amount of complexity to test. Maybe raising an
error if the inputs are wrong is something we should add/test but I'm not
super concerned by it.
I've written a test for n_devices varying which only activates if
the computer has 4 gpu devices. This test checks the following:

The code runs for 1 <= n_devices <= 4.
The logits/activation cache matches for 1 <= n_devices <= 4.
The devices are assigned a roughly equal proportion of layers in the
model.

I think these tests are likely sufficient. We can run them pretty easily
before releases and people working with multiple GPUs can also run them
after they install the package.
@alan-cooney https://github.com/alan-cooney @neelnanda-io
https://github.com/neelnanda-io I think it should be fine to merge this
PR. I'll wait a day or two in case you want to comment/suggest
modifications to the tests but otherwise will merge soon :)
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/125#issuecomment-1501015195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKMMHVQZEE4SKCKCKOLXAIGT5ANCNFSM6AAAAAATITHWXI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Dumb question - why can't you mock it out with a function that checks
whether the input is a string, device or tensor, and deals with it
differently accordingly?

You can try this, but if you are only handed a string and need to return the tensor, that tensor will need to be in scope for you to return it. The "self" object is the mock function, so you can't return that. I thought this sounded solvable and proceeded to read the mocking docs, and I didn't find the solution. If someone knows how to ensure a mocked method on a class has the original class (being mocked in scope), then we could return it (aka, return the tensor still on the CPU as if it had been moved), however without it I think we're stuck.

My one concern is that, as is, there's not a way to have a cache keep
tensors on device, or have a hook layer know what device it's on (I
think?). IMO this is a fairly important feature to add to run_with_cache,
if it's not too big a headache, because communicating large tensors between
devices can be a major performance overhead. I would implement it by giving
each HookPoint a self.device parameter, and having run_with_cache use
that unless overridden.

This seems reasonable to me, and possibly quite doable. Might it be reasonable to merge this and make an issue for that one? Reasons to go that way include:

Having this is better than nothing for now.
We can direct people toward that card if they have complaints about the overhead.
It sounds like a great first issue to give someone.

Sorry for the delay! Yes this seems fine to merge as is with that as a
follow-up PR
On Sun, 9 Apr 2023 at 23:48, Joseph Bloom @.***> wrote:

Dumb question - why can't you mock it out with a function that checks
whether the input is a string, device or tensor, and deals with it
differently accordingly?
You can try this, but if you are only handed a string and need to return
the tensor, that tensor will need to be in scope for you to return it. The
"self" object is the mock function, so you can't return that. I thought
this sounded solvable and proceeded to read the mocking docs, and I didn't
find the solution. If someone knows how to ensure a mocked method on a
class has the original class (being mocked in scope), then we could return
it (aka, return the tensor still on the CPU as if it had been moved),
however without it I think we're stuck.
My one concern is that, as is, there's not a way to have a cache keep
tensors on device, or have a hook layer know what device it's on (I
think?). IMO this is a fairly important feature to add to run_with_cache,
if it's not too big a headache, because communicating large tensors between
devices can be a major performance overhead. I would implement it by giving
each HookPoint a self.device parameter, and having run_with_cache use
that unless overridden.
This seems reasonable to me, and possibly quite doable. Might it be
reasonable to merge this and make an issue for that one? Reasons to go that
way include:

Having this is better than nothing for now.
We can direct people toward that card if they have complaints about
the overhead.
It sounds like a great first issue to give someone.

—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/125#issuecomment-1501229926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKNKRK2OSAGSNTSMTM3XAM4E7ANCNFSM6AAAAAATITHWXI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks Neel. I'll merge this. I've updated both the original issue and created a new proposal for the cache-device-awareness which when completed may enable us to close the original issue. https://github.com/neelnanda-io/TransformerLens/issues/246


Moving kassava from jcenter to another repository

Hey there, I just started using kassava in a project, but I want to continue to use it. Sadly bintray and jcenter are shutting down in February 2022. So it would bbe nice if you could move it to another repository.
The Article: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
Thank you so much 😄

Sadly, this library is not available from maven central.  jcenter shutdown years ago.

I've left the company/project, but there were plans to move this and the JPA spec DSL libraries to central. I don't think it ever eventuated....


Spellcheck README

Just some small corrections in the readme. Otherwhise a very nice project.

In my opinion, 2023.9.1 is a more relevant branch.


support for xcode 8 beta 5 with swift3

@wangshengjia
I created this PR just for you to take a look. Two things to mention:

For test dependency (Quick, Nimble), i pointed to my fork to get it compiled. But i didn't fix syntax in test target
There are exceptions raised when i push twitter and details page demo.
from this function lg_setupCustomStyle which i haven't looked into.

Thanks and can't wait to get this more mature to use it. Keep up.

Thanks a lot for the PR. 👍
I'll look into the details a little bit later.

@wangshengjia I just updated unit test. All tests passed successfully except ConvertibleSpec which is caused by .numberOfLines(10) in ConvertibleSpec.swift. which also triggers compiler error. Please take a look.

@JackieQi Thanks a lot for your help, this is really cool. I've tested with Xcode 8 beta 6, it works like a charm. 👍 💯
We'll merge it once it's all stable. Furthermore, we also need to refactor/break some APIs to make them adapt better the Swift 3 best practices.
ps: By the way, just for the information (no big deal at all), the commit 38e1d13 is just too huge for review, tones of code changed by Xcode and by Cocoapods in one single commit. Usually we prefer to separate commits into small units with the unique purpose. It makes code review a lot easier :)

@wangshengjia Sorry about that. I realized it. I was just trying to get it done.  So the demos still crashed because of lg_setupCustomStyle function not called in UIView extension which i am not sure why.

@JackieQi There is nothing to apologize ;-)
I'll take care of this issue a little bit later when I got time, thanks a lot.

👍


Preserve trailing slash in URL path in runtime

Given a path like "/api/tasks/" the runtime uses path.Join to join the
base path to it which strips any trailing slash. If the path previously
ended with a trailing slash ("/"), it is reinstated after adding the
base path prefix because the behaviour of the server's path handling
cannot be guaranteed.
Fixes #289
Signed-off-by: Jonathan Ingram<EMAIL_ADDRESS>

lgtm

Thanks a lot for this btw

You're welcome @casualjim it's the least I can do! You're the one that created the great lib :) Still hitting some curve balls to get it working for our API, but hoping we will get there.


Verify that Read the Docs is building after master -> main

Spotted on https://github.com/dask/dask-cloudprovider/issues/244#issuecomment-795310925. Read The Docs was still building latest from the master branch and builds were failing. It was configured to build from the default branch, but had cached the value master somewhere. Manually pointing it to  main in the RtD control panel fixed things.

Just checking in here, @martindurant is RTD pointing to main? Looking at the RTD builds there have been some recent builds, but I wanted to double check

Yes, it points to main. THyew!


[TypeCheck] Remove all calls to 'rename' from the PIR type checker

This removes all calls to rename (1 of them) from the PIR type checker.

Nikos is vacationing, hence the review responsibility is yours @michaelpj.
@bezirg check this PR once you're back (not before!).


Add cnegf package

Part of https://github.com/stdlib-js/todo/issues/1454
Description

What is the purpose of this pull request?

This pull request:

Adds cnegf package
[x] JS package
[x] C implementation
[x] Native addon
[x] Tests, examples, readme, etc

Related Issues

Does this pull request have any related issues?

This pull request:

is part of https://github.com/stdlib-js/todo/issues/1454

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

I will! Thanks a lot!


Output of 'list-connected-devices' is unusable

I setup a simple 'get connected devices' and made sure I had a device actually connected, and all i get back is a [object,object] text. Tried to decode with json block but no avail. I expect a json string listing out all the stuff thats connected.

#Solution
uknonwn, please advise. I expect the output here to be usable, but its not.

This is the fault of the debug node. If you want to view the response as json you have to use the Json node before debugging.

Also don't forget that the devices will be under msg.payload.data.

You can also set the debug node to show msg.payload.data and you can inspect the array in the debug tab.

ah, good to know, thanks!


Parse floats in the range [0,1)

Currently, the parser things 0.5 is a string.

@jlawton Awesome—thanks! Could you add an test to the MTFYAMLSerializationSpec to test this case?


[Add] New Button

Details
I want to add new (linkedin) button to this amazing collection of buttons
Screenshots
https://github.com/Spyware007/Animating-Buttons/assets/127978268/cb791afe-370d-432a-aaba-be4c76a1d959
Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[ ] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

Please check #1346


Abort not working using Upload.http method

var upload = Upload.http(config).then(function (resp) {
...
}
$scope.cancel = function(){
upload.abort();
};
Can you pls give the solution?

Edit:
Tested in Mac Chrome Browser

Since Upload.http()  sends all the content inside the request body abort may not work.

You can try `Upload.upload(...).xhr(function(xhr) {xhr})

version: 10.1.14
Upload.upload(...).xhr(function(xhr) {
$scope.xhr = xhr; // this line was not triggered
});

we are uploading file as binary. can you provide an abort solution for Upload.http?

Actually abort is working on the demo page for http. Follow the demo page code, calling abort should abort the request.

If you still have problem create a jsfiddle with steps to reproduce.


Link to libm when necessary

I have a system where isnan is a macro redirecting to __isnan(), which is only defined in libm.

Coverage decreased (-0.6%) to 95.561% when pulling abb80dc5ca05d19eb524b1e09c31e2d024b565d4 on RedDwarf69:isnan_libm into a740f15c17ef7956b1493d8d1f800896c1e60bad on akheron:master.

Would it be enough in your system to use -ljansson -lm?

Yes, that would work.
But if you don't want the patch because it adds complexity for a corner case I will probably just carry the patch locally instead of adding the "fake" direct libm dependency to everything using jansson.

Well, at least it would need to be ported to autoconf also

I am doing as paid work and realistically I am not going to do it for autotools any time soon.
There is really a need, though? With or without an autotools fix this fixes something for people using CMake.
It's not like they generate the same stuff anyway:

The CMake build generates a janssonConfig.cmake file to use by other cmake projects
The autotools build generates a libtool file to use by other autotools projects

Autoconf is all but dead (https://lists.gnu.org/archive/html/autoconf/2021-01/msg00049.html), requiring fixing the autotools build system when fixing the cmake build system is only going to stop people from providing cmake fixes.

I am doing as paid work and realistically I am not going to do it for autotools any time soon.
There is really a need, though? With or without an autotools fix this fixes something for people using CMake.
It's not like they generate the same stuff anyway:

The CMake build generates a janssonConfig.cmake file to use by other cmake projects
The autotools build generates a libtool file to use by other autotools projects

Autoconf is all but dead (https://lists.gnu.org/archive/html/autoconf/2021-01/msg00049.html), requiring fixing the autotools build system when fixing the cmake build system is only going to stop people from providing cmake fixes.


Enable warning for the clippy::question_mark lint

Objective

Enable the warn level for the clippy::question_mark lint. It seems rather uncontroversial and general good practice to me.

Solution

Enable the lint.
Use the question mark/ok adapter to simplify some Option/Result returns. I can revert that and keep only the changes highlighted by the lint if preferable.
Fix some trailing whitespace.

There are two other question mark related lints that could be added alongside this one, which currently do not trigger anywhere in the codebase (unless we want to go with always one lint per PR):

needless_question_mark
needless_return_with_question_mark

One lint per PR is nice: it lets us evaluate the impact and discuss them seperately.

@mockersf do you still want to mark this PR as controversial?


Use GH actions for build/release - image-build-crictl

https://github.com/rancher/image-build-crictl/pull/25


GitHub events - display the profile pic of author

This PR will add display the avatar of the person who authored that event.

Resolves #3  & #17

Thank you !


reorganize docs to improve usability

Reorganize the documentation as per the following google doc:
https://docs.google.com/document/d/1bperGgkCQqHxVVutbiZYM7Cwqk9gMo7fv4nChGpgBfI/edit?ts=594aeb47#

woot!


Android: No Dragging, Item Jumps to Top (RN 0.61.5)

See video:

Repro

npx react-native init XXX --template react-native-template-typescript
Install peer dependencies
Replace content of App.tsx with example code from readme
Run on Android

Package: Dependencies
"dependencies": {
"react": "16.9.0",
"react-native": "0.61.5",
"react-native-draggable-flatlist": "^2.0.10",
"react-native-gesture-handler": "^1.5.2",
"react-native-reanimated": "^1.4.0"
},

Same issue

Have you followed the extra setup instructions for rngh in MainActivity? It's not 100% autolinked... https://software-mansion.github.io/react-native-gesture-handler/docs/getting-started.html

Same issue here

I had the same issue, but following guide on proper installing react-native-gesture-handler mentioned by computerjazz solved this for me. https://software-mansion.github.io/react-native-gesture-handler/docs/getting-started.html

@chriszwickerocteris did you try the above solution? Can we close this?

Indeed, that solves it, thanks - and sorry, hadn't had the time to review before!
I would suggest documenting this in the installation steps section of the README, though. In times of autolinking, I may not be the only one not checking peer dependencies' docs.

I can also confirm it does not work as expected inside a Modal

Hey guys, I've found the solution to getting it to work in side a modal. Just wrap the Component you want to use as the modal inside gestureHandlerRootHOC.
Example:
import {gestureHandlerRootHOC} from 'react-native-gesture-handler';

const MyModalComponent = (props) => {
    return (<View> .... </View>)
}

export default gestureHandlerRootHOC(MyModalComponent)

This got it working like a charm for me. :)


Feature Request: [Pipeline Caching] Please add control options to run "Post-job: Cache" even if a previous task has failed.

Required Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: Pipeline Caching
Issue Description
I encountered a case where I wanted to cache a specified folder, regardless of the success or failure of the pipeline.
The pnpm package manager caches library packages in the ".pnpm-store" folder.
Often it fails to download packages, but this does not cause any inconsistencies in the cache folder.
Cache tasks don't work when the pipeline fails, so there are no fewer packages to download when you run the pipeline again.
That's why I want to configure the Cache task to work even if the pipeline fails.

I'm also trying to enable pipeline caching for pnpm at the moment as well, do you happen to have a yaml example you're working with?

@AndrewCraswell
I am currently trying to use the following yaml.
- script: 'npm install -g pnpm'
  displayName: 'install pnpm'

- script: 'pnpm config set store-dir $(Agent.TempDirectory)/.pnpm-store'
  displayName: 'set store dir'

- task: Cache@2
  displayName: Cache
  inputs:
    key: '""'
    path: '$(Agent.TempDirectory)/.pnpm-store'
  continueOnError: true
  condition: always()

- script: 'pnpm install --frozen-lockfile'
  displayName: 'pnpm install'

- script: 'pnpm build'
  displayName: 'pnpm build'

- task: ArchiveFiles@2
  displayName: 'Archive dist'
  inputs:
    rootFolderOrFile: dist
    includeRootFolder: false

- task: PublishBuildArtifacts@1
  displayName: 'Publish Artifact: drop'

It would be great to have this implemented.


RTSP demo application disconnecting after some time

Hi team,
I have setup two RTSP cameras on my network and I have followed the RTSP demo application (https://github.com/aws-samples/amazon-kinesis-video-streams-demos/tree/master/producer-cpp/docker-rtsp) that uses docker desktop on Windows to send  both streams to Amazon Kinesis Video. I was successfully able to see each video feed on amazon console for each stream. However after I left the sample to run for some time. After some time the process shuts down and the stream is stopped. I can see some warnings before the error "Error received from element source: Could not read from resource." is thrown. Seems the first warning that is thrown is " curlCompleteSync(): curl perform failed for url https://xxxxxxxxxxxxxx.us-west-2.amazonaws.com/putMedia with result Failure when receiving data from the peer: OpenSSL SSL_read: Connection reset by peer, errno 104". I have seen some suggestions on threads on this site which suggested to turn down the camera stream "Frame Size", "Max Bit Rate", "Target Quality" and finally "Intra Frame Period". When I was running at ("Frame Size" =  "1920 1080") sometimes it would stop stream after about 20-30 mins. But since I have turned it down to ("Frame Size" =  "640 360", "Target Quality" = "Medium",  "Max Bit Rate" = "1 MBps" and   "Intra Frame Period" = "1s")  and it actually ran for about 2.5 hours before shutting down with the same issue. I have blacked out all the keys and credentials and  attached two screen shots to this message. They contain all the warnings and the error that is thrown before the process is shut down. We plan to use architecture for a client and we will be adding many more cameras to the network.
Can you please guide me to what can be causing this issue and ways to improve this so the process does not shut down. Also please let me know if you need anything else.
Thanks for your time

@MushMal Any help would be appreciated

@disa6302 @MushMal Any help would be appreciated

Hello, I hope you are very well. Could you fix the error? Where did you set the variables you name? I'm trying to stream from RTSP but it disconnects after a couple of seconds

I don't see anything actionable in the picture of the log - seems that you might have an issue with the connection being dropped from your RTSP upstream. I would recommend removing kvs from the equation and debugging your RTSP stream in the vm you are using and check what's causing the connection drop.

rtspsrc sends an EOS when it stops receiving data from the rtsp source (e.g. internet disruption), which we see in the logs:
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
../gst/rtsp/gstrtspsrc.c(5819): gst_rtspsrc_loop_udp (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
The server closed the connection.
[INFO ] [19-09-2023 16:53:43:561.222 GMT] EOS Event received in sink for demo-stream

You will need to restart the application when this happens, to have rtspsrc try to connect to the camera again. Once the EOS is sent, the session finishes. The session needs to be re-initialized from the beginning.
Some suggestions for doing this may be to use a use a while true loop, or looking into a using systems and service manager such as systemd to restart the application for you.


PV2-3203 - .NET 6 upgrade

Note: this PR is a combined effort between this branch, main PV2 and another dev branch: https://github.com/SkillsFundingAgency/das-payments-v2-requiredpayments/tree/PV2-3203_net6_upgrade_using_DL-Spike_dependencies
This PR contains a different Git history to that of the current main branch. The intention with this PR is to overwrite the current main branch as this PR contains new commits from PV2 that haven't been migrated over yet.
Test evidence attached to ticket: https://skillsfundingagency.atlassian.net/browse/PV2-3203
The following are the new .NET 6 related commits which require review. All subsequent commits exist either in the PV2 app or the current main branch, and have been cherry picked over to this branch.

PR superseded by https://github.com/SkillsFundingAgency/das-payments-v2-requiredpayments/pull/7


foxglove_bridge: 0.2.0-3 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository foxglove_bridge to 0.2.0-3:

upstream repository: https://github.com/foxglove/ros-foxglove-bridge.git
release repository: https://github.com/ros2-gbp/foxglove_bridge-release.git
distro file: galactic/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.1.0-2

foxglove_bridge
* Add support for client channels (#66 <https://github.com/foxglove/ros-foxglove-bridge/issues/66>)
* Add smoke tests (#72 <https://github.com/foxglove/ros-foxglove-bridge/issues/72>)
* Update package maintainers (#70 <https://github.com/foxglove/ros-foxglove-bridge/issues/70>)
* [ROS2]: Fix messages not being received anymore after unsubscribing a topic (#92 <https://github.com/foxglove/ros-foxglove-bridge/issues/92>)
* [ROS2]: Refactor node as a component (#63 <https://github.com/foxglove/ros-foxglove-bridge/issues/63>)
* [ROS2]: Fix message definition loading for .msg or .idl files not located in msg/ (#95 <https://github.com/foxglove/ros-foxglove-bridge/issues/95>)
* [ROS1]: Mirror ROS 2 node behavior when /clock` topic is present (#99 <https://github.com/foxglove/ros-foxglove-bridge/issues/99>)
* [ROS1]: Fix topic discovery function not being called frequently at startup (#68 <https://github.com/foxglove/ros-foxglove-bridge/issues/68>)
* Contributors: Hans-Joachim Krauch, Jacob Bandes-Storch, John Hurliman

Thanks for redoing these. major bumps of bloom (0.10 -> 0.11) usually include significant changes for support of additional ROS distributions or overall improvements to the release templates.


pipewire: 0.3.35 -> 0.3.36

The timing of this new release... :laughing:
Motivation for this change
https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.36
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Looks like the root-level meson.build did not get updated with the new version upstream so everything still reports 0.3.35. Paths still point to the 0.3.36 package and everything seems to work fine.

The version should not really bother us much.

Backport failed because it depends on #137533


App router redirectUrl for hash based router

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[x] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

Currently, useRouter.queryParams returns the params the router parses. The hash and virtual routers only parse the params within the URL fragment, so any params appended to the normal URL by the user are ignored.
Before the change:

Path routing
A SignIn component mounted at https://example.com/sign-in?redirect_to=/protected will correctly redirect to /protected
Hash routing with hash param
A SignIn component mounted at https://example.com/sign-in#/?redirect_to=/protected will correctly redirect to /protected
Hash routing with normal param
A SignIn component mounted at https://example.com/sign-in?redirect_to=/protected will ignore the redirect_to hash param

Before the change:
1 + 2 remain the same
2. Hash routing with normal param
A SignIn component mounted at https://example.com/sign-in?redirect_to=/protected will read the normal param and redirect to /protected
If both hash and normal params exists, the hash params will have priority - no breaking changes here.
Regarding the nextjs change: concatenating pathname and searchParams resulted in broken URLs like:
http://localhost/sign-inredirectTo=/protected - notice the missing ?.
Since no changes are needed, we can simply reexport the components as well.

Closes #997

We decided to revert the extractAuthProp change for now, and instead prompt the users to switch to path-based routing.

@nikosdouvlis Did we notice any issues with the change in extractAuthProp?


Selected for radio or select

Is there anyway to set a selected radio or select input?
If not, could it be a new feat?

The inputValue option can be used to set the initial value, or are you talking in terms of setting it afterwards via an API?

Duplicate of https://github.com/limonte/sweetalert2/issues/207

@samturrell inputValue works for input select/radio type?


flutter pub run crashes with CreateProcessW failed 193

Hi Flutter team.
I'm facing a problem with the flutter CLI tool, especially only when running the flutter pub run <something> command.
Steps to Reproduce

I don't know if this is a real steps to reproduce, but this is typically what I have done:

Use the beta channel of flutter: flutter channel beta
Create an app and add plugins which comes with build systems (like json_serializable)
Run the build system (in my case, I am trying flutter pub run build_runner build and flutter packages pub run build_runner build)

The firsts times I have supposed that is a problem with build_runner, but any other flutter pub run <executable> crashes with the same error: CreateProcessW failed 193
Logs

This is the output of the error:
CreateProcessW failed 193
%1 is not a valid Win32 application.

  Command: D:\Dev_Tools\flutter\bin\cache\dart-sdk\bin\dart --packages=file:///D:/Aliens_Group/Isintu/isintu-chat-app/.packages --snapshot=.\.dart_tool/pub\bin\build_runner\build_runner.dart.snapshot.dart2 file:///D:/Dev_Tools/flutter/.pub-cache/hosted/pub.dartlang.org/build_runner-1.7.2/bin/build_runner.dart
CreateProcessW failed 193
%1 is not a valid Win32 application.

  Command: D:\Dev_Tools\flutter\bin\cache\dart-sdk\bin\dart --packages=file:///D:/Aliens_Group/Isintu/isintu-chat-app/.packages --snapshot=.\.dart_tool/pub\bin\build_runner\graph_inspector.dart.snapshot.dart2 file:///D:/Dev_Tools/flutter/.pub-cache/hosted/pub.dartlang.org/build_runner-1.7.2/bin/graph_inspector.dart
CreateProcessW failed 193
%1 is not a valid Win32 application.

  Command: D:\Dev_Tools\flutter\bin\cache\dart-sdk\bin\dart --packages=file:///D:/Aliens_Group/Isintu/isintu-chat-app/.packages --snapshot=.\.dart_tool/pub\bin\flutter_launcher_icons\main.dart.snapshot.dart2 file:///D:/Dev_Tools/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_launcher_icons-0.7.4/bin/main.dart
CreateProcessW failed 193
%1 is not a valid Win32 application.

  Command: D:\Dev_Tools\flutter\bin\cache\dart-sdk\bin\dart --packages=file:///D:/Aliens_Group/Isintu/isintu-chat-app/.packages --snapshot=.\.dart_tool/pub\bin\test\test.dart.snapshot.dart2 file:///D:/Dev_Tools/flutter/.pub-cache/hosted/pub.dartlang.org/test-1.9.4/bin/test.dart
pub finished with exit code 1

This is the output of flutter doctor -v
[√] Flutter (Channel beta, v1.12.13+hotfix.6, on Microsoft Windows [Version 10.0.18363.535], locale en-US)
    • Flutter version 1.12.13+hotfix.6 at D:\Dev_Tools\flutter
    • Framework revision 18cd7a3601 (4 weeks ago), 2019-12-11 06:35:39 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at D:\Dev_Tools\android_sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = D:\Dev_Tools\android_sdk
    • Java binary at: C:\Users\axlna\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\191.6010548\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Users\axlna\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\191.6010548
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.41.1)
    • VS Code at C:\Users\axlna\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.7.1

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Thanks by advance for any help.

@jonahwilliams do we support build_runner yet?

Hi @dnfield, I think yes because I  already have successfully executed this command times ago, with an older version of Flutter on a Linux machine. But when I have migrated to Windows with the latest beta version of Flutter, every flutter pub run command is crashing, not only when trying to run build_runner.

The tool shouldn't need to do any support here since we're just forwarding arguments to pub. I wonder if this is actually an issue in pub?

Hi @dnfield @jonahwilliams @jmagman there is a workaround to solve this ? I'm unable to build my app since I have not generated required files.


[BUG] Add backport label PR is failing on branches other than main

What is the bug?
add_backport_label.yml on the 1.x branch is invalid.

Error: .github#L1
Invalid type for on

Correct syntax is on main branch:
name: Add Backport Label
on:
  pull_request_target:
    branches: main
    types: opened

The 1.x branch is incorrect. It should either match main (probably preferred to avoid future merge conflicts), or not exist at all, so that it gets ignored:
on:
  branches: main
  pull_request:
    types: opened

How can one reproduce the bug?

Create a pull request to the 1.x branch, which happens when a PR is merged on main to generate the backport PR
Push to the 1.x branch, which happens when a backport PR is merged

What is the expected behavior?
The action doesn't run at all.
Do you have any screenshots?

Fixed in #553


fix: handle missing daemon errors

@pfrazee this seems to solve your issue, want to try it out?

Yeah that solved it! Thanks

thanks!


Improve module evaluation by not requiring shim scripts in order to access namespace objects.

Thanks to https://github.com/Microsoft/ChakraCore/pull/4707, it's now possible to programmatically get at namespace objects.
This allows the functionality in
https://github.com/BaristaLabs/BaristaCore/blob/master/src/BaristaLabs.BaristaCore.Common/BaristaContext.cs#L456
and
https://github.com/BaristaLabs/BaristaCore/blob/master/src/BaristaLabs.BaristaCore.Common/BaristaModuleRecord.cs#L260
to no longer rely on a 'shim' script in order to get at the variables exported by modules. This should improve execution speed, remove pollution of the global namespace, reduce the possibility of down-stream side effects, and allow the export of non-default values as well.

The upstream changes should be incorporated in ChakraCore 1.9.x

This functionality is now partially implemented thanks to the upstream changes in ChakraCore 1.10.x.
The relevant sections of BaristaModuleRecord.cs still parse script, however, as 1) It doesn't appear to be able to set variables in namespaces 2) attempting to eval getnamespace during module loading breaks the runtime and throws an exception.


hlog lacks examples and unit tests

Is your feature request related to a problem? Please describe.
I see a lack of samples and unit tests for the use of hlog
Describe the solution you'd like
add examples and unit tests

Thanks for reporting! Are you interested in submitting a pr to solve it?
It's OK if it is not so, I'll put it into TODOs.

Thanks for reporting! Are you interested in submitting a pr to solve it? It's OK if it is not so, I'll put it into TODOs.

I'd like to try

@L2ncE  We should also improve the logging documentation to let users know that we support zap log.

https://www.cloudwego.io/zh/docs/hertz/tutorials/basic-feature/log/

@L2ncE We should also improve the logging documentation to let users know that we support zap log.

https://www.cloudwego.io/zh/docs/hertz/tutorials/basic-feature/log/

got it


Set javahome default to allow puppet compile test.

https://github.com/puppet-community/puppet-confluence/issues/43

This includes a change from #45 as well as additional changes, but the
commit message only mentions the change from #45.
--
Rob Nelson
<EMAIL_ADDRESS>

Hello:
What is the status of this PR?


From input prog args, group together the training_params, eval_params, plotting_params, file_params, and data_params

I have worked so far on the UI for training which groups together the training_params and data_params. At present, I've only included the training params when training a new model from scratch, so I need to add the additional params for re-training a model.

Task completed.