Feature Request: Dark Mode

I couldn't find an easy way to change the background colors within Azimutt. I think the already existing color customization is great, but it would be nice to have further color customization within the platform. One common way is to implement a toggle switch for dark mode (example). A feature like this or a way to change the color layouts within the platform would be cool and would help make the platform more customizable.
Note: I am happy to make an attempt at implementing this, but am new to elm, so it would require some scrutiny.

Hi @proselotis
Thanks for reaching out!
Indeed personalization is still quite low on Azimutt but I still have some foundational features that are still missing (like undo/redo, realtime collaboration, better data exploration, better editor for SQL/AML, more in-depth db analysis...) so I don't think I can focus on this soon.
I think that task is not that hard thanks to the dark:* feature of Tailwind but having something that is qualitative everywhere looks like a very long task.
If you feel it you can try it and I can review your work but as Azimutt is still evolving a lot it could be challenging.
What do you think?


Error in handling the file

There was an error for me in opening the file. The directory was correct and the dataset is also the same. Could you take a look ?

safe_read_data <- function(file_path) {
tryCatch({
read.delim(file_path, sep = "\t")
}, error = function(e) {
cat("Error in reading file:", e$message, "\n")
return(NULL)
})
}
Try this @Koshijacok


Not for merge: Example of Person with Cars

@Rainer-Lang, please take a look!

Closing this, feel free to comment :)

@artem-zinnatullin This is really a great and very useful example. Thanks a lot.

Glad to help :)
вс, 20 сент. 2015 г. в 8:22, Rainer-Lang<EMAIL_ADDRESS>
@artem-zinnatullin https://github.com/artem-zinnatullin This is really
a great and very useful example. Thanks a lot.
—
Reply to this email directly or view it on GitHub
https://github.com/pushtorefresh/storio/pull/522#issuecomment-141749099.

--
@artem_zin


Add logging to provider app

OHSU is using a logging service.
Need to configure both apps to use this.

Sai has created proof of concept. Need to test with OSHU as soon as POC is available.

Sean is performing clean up on the branches.


Enable Integration tests

We have updated fixed and enabled integrations for Opensearch version >= 1.1.0. We plan on working on 1.0.x in accordance with this issue mentioned here: https://github.com/opensearch-project/project-website/issues/737

This is completed as part of #36 being merged


PHP doc to assist IDEs

So i have the code below on my preferred IDE/CE and I want to click on isAdmin() function so i can see how it is implemented.
if ($user->isAdmin()) return $model->approved();

So I have added "App\User" on the doc block when I click isAdmin it will go to App\User class.
Hopefully that was descriptive enough.

You need to rebase your branch.
I do not believe we should include this kind of changes only for the sake to help your IDE, your IDE needs to improve.
This change is wrong, you can not hardcode the user() method to be a qualified name like App\User because some people change their default App name so something elsee, others move the User model to maybe something like App\Models\User and others do not even use the User model as the main model to represent users.


NativePHP Implementation

👋🏻
So I've created a little app here. I don't think NativePHP is completely ready for prime time but could be close. They mention they're in alpha on their website.
However. I got some pretty decent progress in a few hours.
Key things:

Uses sqlite database
Will require scheduling to fetch RSS updates
Configurable via config/larajobs.php
Can be tested with artisan command php artisan larajobs:refresh-feed
Uses the laravel link which then redirects, just like the website.

You should be able to test it.
Just copy the example .env file, create an app key and set:
LARAJOBS_FEED_URL=https://larajobs.com/feed

and run:
pnpm (or your package manager of choice) dev

and (pay attention to the architecture and make sure it matches for you):
cp vendor/nativephp/php-bin/bin/mac/arm64/php vendor/nativephp/electron/resources/js/resources/php
php artisan native:serve --no-dependencies

Feel free to reach out with any questions. This wasn't hard but it wasn't straight forward, so if I forgot some step to get it to run, let me know.
Please see the README for way more information.
https://github.com/UserScape/larajobs-desktop/assets/5760821/5a5ece1c-b46c-4919-8699-dd258cb82bab

Thanks for leading the way @mdloop, the example of how to open the URLs in the browser was great!

No problem!


chore: jsonfmt timeseriesinsights

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Can one of the admins verify this patch?


Sync eng/common directory with azure-sdk-tools for PR 1560

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1560  See eng/common workflow

/check-enforcer evaluate

/check-enforcer reset

/check-enforcer evaluate


Remove black track

New versions of Kdenlive adds black video with no audio to the end of rendered video files. This is done for the files that are generated via script or command line, but not with the application.
Looking in the kdenlive or mlt (if using Generate Script option), you can see that the black track is being added.
By removing the "black_track" line from the above mentioned file, it will prevent this unnecessary addition to the rendered video files.

Line that shows up in file
<track producer="black_track"/>


local-ai: 2.17.1 -> 2.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/go-skynet/LocalAI/releases.
meta.description for local-ai is: OpenAI alternative to run local LLMs, image and audio generation
meta.homepage for local-ai is: https://localai.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.18.0 in filename of file in /nix/store/vywdsa655gfsa91bc5k9cycvspgvrpb0-local-ai-2.18.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

local-ai

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vywdsa655gfsa91bc5k9cycvspgvrpb0-local-ai-2.18.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A local-ai https://github.com/r-ryantm/nixpkgs/archive/226ca4f6265ac772a790e64041126c515ca1e057.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/226ca4f6265ac772a790e64041126c515ca1e057#local-ai

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vywdsa655gfsa91bc5k9cycvspgvrpb0-local-ai-2.18.0
ls -la /nix/store/vywdsa655gfsa91bc5k9cycvspgvrpb0-local-ai-2.18.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

local-ai

Maintainer pings
cc @onny @ck3d for testing.

The auto updater did not update the llama.cpp package. I will create a PR when #323331 is merged.


fix: Add correct representation of Value curves and remove name from cost and function data components

It does not make sense to have cost functions with names since we are not going to pull them individually. Instead, we inherit from InfraSysBaseModelWithIdentifers to only include UUID.

Codecov Report
Attention: Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 95.33%. Comparing base (9dc0e3e) to head (763162b).

Files with missing lines
Patch %
Lines

src/infrasys/value_curves.py
75.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
- Coverage   95.40%   95.33%   -0.07%
==========================================
  Files          33       33
  Lines        2719     2725       +6
==========================================
+ Hits         2594     2598       +4
- Misses        125      127       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fortify scanning

Need to scan the code.

I have raised the below request for gaining access to the Fortify SSC. It seems @Sizemore, Curtis W is OOO, is there some one can approve this request to procced on his behalf?
Sent an email waiting for the reply.

Chris has ran the fortify scans.


Add support for calling multiple agents on one service

Update agent/ directory to agents/
Move tests to their own repo
Create agents/models.py to consolidate model setup code
Create agents/agents.py with a dict of all included agents
Add agents/chatbot.py with a simple chatbot
Add a route /{agent_id}/invoke to invoke a specific agent
Add a route /{agent_id}/stream to stream results from a specific agent

@gbaian10 @antonioalegria I would love to get any feedback you might have on this PR when you get a chance!

Looks good


wip: dashboard access

SUMMARY

This is just a test, for now
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #153 (3f536c0) into master (343d3f8) will decrease coverage by 14.15%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #153       +/-   ##
===========================================
- Coverage   66.34%   52.18%   -14.16%
===========================================
  Files        1569     1569
  Lines       61686    61686
  Branches     6241     6241
===========================================
- Hits        40927    32193     -8734
- Misses      19161    27895     +8734
  Partials     1598     1598

Flag
Coverage Δ

hive
53.23% <ø> (ø)

mysql
?

postgres
?

presto
53.07% <ø> (ø)

python
53.52% <ø> (-29.07%)
:arrow_down:

sqlite
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/security/manager.py
64.76% <ø> (-27.21%)
:arrow_down:

superset/utils/dashboard_import_export.py
0.00% <0.00%> (-100.00%)
:arrow_down:

superset/dashboards/commands/importers/v0.py
14.79% <0.00%> (-75.15%)
:arrow_down:

superset/tasks/alerts/observer.py
27.77% <0.00%> (-72.23%)
:arrow_down:

superset/databases/commands/importers/v1/utils.py
27.77% <0.00%> (-72.23%)
:arrow_down:

superset/datasets/commands/create.py
30.18% <0.00%> (-69.82%)
:arrow_down:

superset/utils/pandas_postprocessing.py
16.45% <0.00%> (-69.36%)
:arrow_down:

superset/datasets/commands/importers/v0.py
24.82% <0.00%> (-68.80%)
:arrow_down:

superset/databases/commands/test_connection.py
31.42% <0.00%> (-68.58%)
:arrow_down:

superset/datasets/commands/update.py
25.88% <0.00%> (-68.24%)
:arrow_down:

... and 260 more

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 343d3f8...3f536c0. Read the comment docs.


Fix delete translation for Django 1.9+

Fix #122 by registering the appropriate url path according to the django version

Current coverage is 85.66%

Merging #126 into master will increase coverage by +0.02% as of d1061d1

@@            master    #126   diff @@
======================================
  Files           39      39
  Stmts         2556    2560     +4
  Branches         0       0
  Methods          0       0
======================================
+ Hit           2189    2193     +4
  Partial          0       0
  Missed         367     367

Review entire Coverage Diff as of d1061d1

Powered by Codecov. Updated on successful CI builds.

Thanks!


laminar: 1.2 → 1.3

Description of changes
https://github.com/ohwgiles/laminar/releases/tag/1.3
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, 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/)
23.05 Release Notes (or backporting 22.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.

Both laminar and pkgsStatic.laminar builds find for me.

LGTM!


Setting to disable query wrapping

While I was implementing this into https://github.com/saelos/saelos, I noticed that the standard lucene query structure for Elastic search wasn't supported since this package wrapped the query sent to elastic search in *'s  for a wildcard search.
This PR adds the ability to disable wrapping the query with a wildcard while preserving current functionality.
This fixes #96
It should take precedence over and close #75

@ErickTamayo What are your thoughts for this?

I am very interested in seeing this PR being merged. Although it is relative simple to override the query by passing a callback as a second argument to Laravel Scout's search() method, I personally do not find any reason at all for the query to be wrapped in * as it gives you less control over search and does not allows for lucene syntax.


Changing the colors

I couldn't find a way to change the color of the background and the arrow, can you help me out with it?

Just found the answer in another issue that was closed earlier.


[near] cache getValidator and getCommission

📝 Description

Everytime a user go on their account they load all the Near nodes and the commissions for these nodes. We now add a cache on these function to only call these functions if the data is not in the cache

❓ Context

JIRA or GitHub link: https://ledgerhq.atlassian.net/browse/LIVE-10539

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[ ] npx changeset was attached.
[ ] Covered by automatic tests.

[ ] Impact of the changes:

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@lvndry Wrong JIRA ticket linked to this PR :eyes:

@lvndry Wrong JIRA ticket linked to this PR 👀


Create AtmelStudio.gitignore

Per PR #1614, creating a new PR that moves it into the community/ folder.
Added a new .gitignore for Atmel Studio.
https://www.microchip.com/mplab/avr-support/atmel-studio-7
Atmel Studio is for embedded development, so the build result files are mostly C.
It's built on top of an old version of Visual Studio, so they prefixed VS file extensions with at.
Keeping user settings out of the repo applies to everyone in my opinion.
It also used a similar build output directory structure as Visual Studio, hence the exclusion of Debug and Release directories.
This PR also introduces an Embedded directory in the community section.
I noticed a number of unmerged PRs for embedded development, like #2887, #2735, #2167, and #1239.
This introduces a place for the community to place embedded dev environment .gitignore files.

@rubberduck203 thanks!


Fix Panel to use /daemon

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: AliceNyan:x: HunterNyanAliceNyan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Binary file section ordering problem

As stated in the WebAssembly Spec:

Section ids do not always correspond to the order of sections in the encoding of a module.

From what I'm seeing in validation, the order is hardcoded, or am I wrong?
I propose a rewrite of it, where we dynamically figure out the type based on the type id extracted from the section.

Yes, the order is hardcoded on purpose.
I think the quoted statement from the WASM Spec may be misleading here.
It just states that section ids do not correspond to the order of sections. It does not make any statements about the order itself, which is defined in one of the next sections (see here).
The actual order of section ids is:
0, 1, 0, 2, 0, 3, 0, 4, 0, 5, 0, 6, 0, 7, 0, 8, 0, 9, 0, 12, 0, 10, 0, 11, 0

Note that the data count section (id=12) is out of order.


WGSL: Nullpointer dereference in WGSLSourceEmitter::emitStructFieldAttributes

Affected tests:

tests/autodiff/existential-1.slang
tests/autodiff/existential-2.slang
tests/autodiff/material/diff-bwd-falcor-material-system.slang
tests/autodiff/material2/diff-bwd-falcor-material-system.slang

This returnsl nullptr:
    IROffsetDecoration *const fieldOffsetDecoration =
        field->findDecoration<IROffsetDecoration>();

slang-test -bindir %BINDIR% -category full -api wgpu tests/autodiff/existential-1.slang

Here follows my summary of what's been discovered so far.
It seems that during struct legalization we create a new struct that inherits the 'size and alignment decoration', which is supposed to imply that the struct fields have got offsets calculated and added.
However, the new struct is created in such a way that the offsets did not get added, and so we crash during WGSL emission.
The fix will be to make sure we copy over the offsets for the fields that survive legalization.
(The legalization just removes fields that don't have any bearing on memory layout, so the offsets should still be valid.)

Currently testing the propsed fix in https://github.com/shader-slang/slang/pull/5525


Add devtools open on launch config to Cypress plugins

The old Cypress plugin location is deprecated as of Cypress v10.
Removals

Remove redundant default Cypress plugin directory.

Changes

Add workaround to display the devconsole on cypress launch.

How to test this PR

Any PR failures should have a screenshot that shows the dev console.

I have been unable to get this plugin to run without crashing Cypress, sadly. Follow https://github.com/cypress-io/cypress/issues/2024 for any developments.


Automigration does not appear to handle embedded gorm models

GORM Playground Link
https://go.dev/play/p/H0kaUoRuJeh
Description
Has-many relationships appear to require explicit definition of a foreign key when embedding gorm.Model. Per the link in the playground:
type Poll struct {
	gorm.Model
	Name     string
	Question string
	Choices  []Choice // `gorm:"foreignKey:ID"`
	Expires  time.Time
}

type Choice struct {
	gorm.Model
	Text  string
	Votes int
}
...
	if err := db.AutoMigrate(&model.Poll{}, &model.Choice{}); err != nil {
		panic(err)
	}

The code above fails to auto migrate with the following error:
[error] invalid field found for struct github.com/brakthehack/poll/app/model.Poll's field Choices: define a valid foreign key for relations or implement the Valuer/Scanner interface
The auto migration script should be able to guess that the FK for Poll.Choices should be the ID field of the Choice model. When the FK is explicitly added by removing the comments before the gorm tag, the code works successfully. The documentation also seems to suggest this should work in the first example by emitting the explicit foreignKey tag.
go version go1.19 linux/amd64

gorm.io/driver/postgres v1.3.8 // indirect
gorm.io/gorm v1.23.8 // indirect

https://gorm.io/docs/has_many.html#Declare

// User has many CreditCards, UserID is the foreign key

type Choice struct {
	gorm.Model
	Text  string
	Votes int
+ 	PollId uint
}


Need to update MPCs for VS2019

The MPCs listed in this page (e.g. 08860, 08862, and 08866) are for VS2017; VS2019 uses different MPCs:

Enterprise may be 09260 (I haven't confirmed it).
Professional is 09262 (I have confirmed it).
Test Professional could be 09266, but DDConfigCA.exe doesn't actually create that registry value so I am doubting this and haven't confirmed it.

In #3, what I mean is that when run elevated with no command-line params, DDConfigCA.exe from VS2019 GA creates the following registry keys under HKCR\Classes\Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA: 09260, 09262, 09263, 09264, 09265, 09271, 09275, 09276, 09277, 09278, 09279, 09280, and 0bcad. I would expect DDConfigCA.exe to create registry keys related to all supported MPCs, but I don't see 09266, so I don't know what the Test Professional MPC is.

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

ID: 11e2b93a-e89d-42ce-23d7-4cf85f47ba25
Version Independent ID: 4083c0d5-c871-ef24-d11c-b6ec1adbb571
Content: Automatically apply product keys - Visual Studio
Content Source: docs/install/automatically-apply-product-keys-when-deploying-visual-studio.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@grossag Thanks for letting us know; we have a PR in place to change the MPC values on the page. Meanwhile, you are correct in stating the following:
Visual Studio Enterprise | 09260
Visual Studio Professional | 09262
Thanks again for your feedback! We appreciate it.

Thanks @TerryGLee . Is there a MPC for Test Professional? Or is that going away?

@grossag Thanks for your feedback. We've updated the documentation with the correct codes. As to your question about Test Professional -- there isn't an MPC for that now, but here's some further information about our testing services:
Azure DevOps Services and Azure DevOps Server offer a web-based solution for manual testing that is included in the Visual Studio Test Professional subscription, known as Azure Test Plans. Azure Test Plans is a web-based manual testing solution, which works across all platforms and with all browsers. It provides experiences across Plan, Author, Execute and Track stages of Manual testing, for web-based and desktop apps.
In the past, we have also shipped a client based solution as Microsoft Test Manager (MTM). Microsoft Test Manager client is a desktop-based manual testing solution, which has traditionally been used by testers for their manual testing needs.  For more information on the support lifecycle of Microsoft Test Manager client and the benefits Azure Test Plans provides over MTM, read this topic: Guidance on Microsoft Test Manager usage.
Moving forward, the Microsoft Test Manager client will be deprecated and Visual Studio Test Professional subscription will continue to grant access to the web-based solution for test management that is known as Azure Test Plans.


[1.11.1] Docker bootstrap: Cannot start a container because of oci runtime error.

Output of docker version:
Docker version 1.11.1, build 5604cbe

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-253:0-394509-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 19.07 MB
 Data Space Total: 107.4 GB
 Data Space Available: 38.76 GB
 Metadata Space Used: 589.8 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.797 GiB
Name: localhost.localdomain
ID: E3X2:DQ6O:DVIO:2NPO:XFY7:6P65:SQG2:TXLM:EERQ:GFSO:NUWT:JF3S
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.): Vagrant centos/7 box
Steps to reproduce the issue:

Start docker as a bootstrap service in one console:

docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap --debug

Start container in second console:

docker -H unix:///var/run/docker-bootstrap.sock run -it --rm busybox sh

Describe the results you received:
Status: Downloaded newer image for busybox:latest
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: rootfs (\"/var/lib/docker-bootstrap/devicemapper/mnt/8c8cc49901da0ddbdd24298a7b294dc7a516a9c72d05055fd882964101f46897/rootfs\") does not exist".

 START
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032)
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032).  START
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init). END
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: unregisterDevice(17, 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init)
DEBU[0045] devmapper: DeleteDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init syncDelete=false) END
DEBU[0045] Closing buffered stdin pipe

cc @crosbymichael

Seems to work on Ubuntu, but I can try reproducing on a CentOS host
docker -H unix:///var/run/docker-bootstrap.sock info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker-bootstrap/aufs
 Backing Filesystem: extfs
 Dirs: 2
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host
Kernel Version: 4.2.0-27-generic
Operating System: Ubuntu 15.10
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: ubuntu-2gb-ams3-01
ID: Y5HS:2JVU:MNOJ:Y7KE:RDFO:C7OJ:TZIS:77EA:LPFN:VBCV:YM6G:NCYQ
Docker Root Dir: /var/lib/docker-bootstrap
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 13
 Goroutines: 29
 System Time: 2016-05-12T08:39:38.213693283-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Same on CentOS 7.2
docker -H unix:///var/run/docker-bootstrap.sock info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-253:1-262181-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 19.07 MB
 Data Space Total: 107.4 GB
 Data Space Available: 40.63 GB
 Metadata Space Used: 589.8 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker-bootstrap/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker-bootstrap/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: centos-2gb-ams3-01
ID: VTDV:LIY6:YXSK:S5DE:4CMV:N6QK:MKTW:4XCW:57XB:KRR7:MSOE:LXHP
Docker Root Dir: /var/lib/docker-bootstrap
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 14
 Goroutines: 29
 System Time: 2016-05-12T09:09:36.849913681-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Are you running this in addition to another docker instance?

I made some research about this problem and it exists only on Vagrant with centos7 box.
I have very simple scenario:

create centos7 instance
install docker according to documentation: https://docs.docker.com/engine/installation/linux/centos/

Those steps are done in this project: https://github.com/zreigz/docker-vagrant
When vagrant provisioning is done then you should:

vagrant ssh to get to the VM
In VM

[vagrant@vagrantbox ~]$ sudo su
[root@vagrantbox vagrant]# docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap &

[root@vagrantbox vagrant]# docker -H unix:///var/run/docker-bootstrap.sock run -it --rm busybox sh

Then you see the error.
When I made downgrade to docker 1.10.3 then everything works fine

Can you update your docker.unit to match the https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.service unit-file? I see various settings missing (e.g. MountFlags=slave, Delegate=yes)

@thaJeztah I think the docker service looks similar. This is from Vagrant instance:
cat /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/docker daemon -H fd://
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes

[Install]
WantedBy=multi-user.target

I also tried with MountFlags=shared but without success
@justincormack  how can I check audit log?

I just made downgrade to:
Docker version 1.11.0, build 4dc5990 and works fine, so the problem appeared in 1.11.1
For 1.10.3 I also didn't notice any problems

@zreigz thanks! I saw the "template" in your repository, and thought that was used

@zreigz should be in /var/log/audit/audit.log

This is audit.log. I can not see any suspicious entries.
audit.log.zip

When execute systemctl stop docker and start docker-bootstrap daemon, it is success.
Both docker daemon  use same socket of docker-containerd.
It seems to be related to #22256.

OK I found solution. Similar problem is described here: https://github.com/kubernetes/kubernetes/issues/24654
I've added --exec-root=/var/lib/docker-bootstrap
and it looks like
docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap \
       --exec-root=/var/lib/docker-bootstrap

Problem fixed

@zreigz hm, I wonder if that should be --exec-root=/var/run/docker-bootstrap (not /var/lib..)
Perhaps this should be documented better, because it looks like we're not really documenting the --exec-root option. Would you be interested in contributing changes for that? Should probably go in this document; https://github.com/docker/docker/blob/master/docs/reference/commandline/dockerd.md
(and the associated man page; https://github.com/docker/docker/blob/master/man/dockerd.8.md)

Yes I think improved docs would help as it has changed quite a bit since containerd and there seem to be more people interested in running multiple dockers recently.

@thaJeztah Yes you are right. The --exec-root=/var/run/docker-bootstrap is better.
Sure I can improve documentation

Perhaps a section "running multiple daemons" or something similar (explaining the options to configure, and a warning that they should never share the same graph-dir 😇 )

@zreigz Hi! Are you ok closing this issue or do you think there's additional work to be done to fully resolve it? Thanks.

Yes I can close it


add json exported from sheets

This PR contains the converted data from Google Sheets as JSON

Closing this PR, i'll put a PR with camel case key names for the json.


[SPARK-20020][SPARKR] DataFrame checkpoint API

What changes were proposed in this pull request?
Add checkpoint, setCheckpointDir API to R
How was this patch tested?
unit tests, manual tests

Test build #74831 has started for PR 17351 at commit 87471cc.

Test build #74831 has finished for PR 17351 at commit 87471cc.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74831/
Test FAILed.

Test build #74832 has started for PR 17351 at commit 207922f.

Test build #74832 has finished for PR 17351 at commit 207922f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74832/
Test PASSed.

merged this to master ahead of the code freeze


Group screen mockup

Working through ideas related to what I think will be the trickiest aspects of this screen: We support comments on photos, photos that have been posted sometime in the past, but we want to surface those comments in the feed as new information (at the head of the feed).
There are two main situations I can imagine:

Photo is shared, the next item(s) in the feed are comments on that photo
Photo is shared, some other item is shared (let's say a message), then a(some) comment(s) on the previously shared photo.

Here's what I'm thinking for #1 so far:

In this case, the photo comments are appended onto the photo "card" and are presented as part of the shared photo's item.
For #2, we need to resurface some representation of the previously shared photo and display the newly added comments:

In this case, we display a thumbnail of the previously shared photo along with any new comments on the photo. Comments will be added to this "card" until there is a new feed item unrelated to the previously shared photo. If more comments come in later, we can repeat this photo comment card again in the feed.

Oh, in the photo comments card, there will be buttons to like and comment on the photo as well. I'm thinking they'll go right under the thumbnail.

The mechanics of simple chat items and photos are more simple. I guess there are some questions about how we want to support sharing/viewing multiple photos and how that impacts decisions about aspect ratio of images shared/viewed as a group.

One useful way to think about photo comments is kind of like "threads" in slack, where you can comment on a previous item, and optionally also display your comment at the head of the channel.

Love it. Will probably take some experimenting, but your slack analogy gives me confidence it could feel pretty natural. Only thought is for the "set" of photos... maybe the card is just the first one or maybe a collage or some kind. A tap could lead to a nice grid of them all where you can single tap each one, and then swipe though. Sounds more flex to me than the IG style of just swiping through them within the feed. Because, as you say, we'd have to consider aspect ratios if we did it like that (as they do)

One of the screens I put in AT was around the idea of seeing all the group's photos in a grid from the group info screen, "Group Photos" screen. This could help make the group space feel more photo-centric, as apposed to generic chat.

So like, maybe there's an "info" button in the upper-right corner of a group view. Tap that, and inside there's a row button to view all Photos or something... an enhancement for sure

and another row button to view all Members

Cool, thanks for your thoughts. That all sounds reasonable. Think I'll start with the simple feed of messages, photos, and photo comments, then we can enhance with photo grids and group info screen etc


wrong npm package name in readme > installation section

Readme.md contains an installation instruction that did not work for me.
I used npm install --save angularjs-currency-input-mask

Thank you @roduartefreitas ! I fixed the README.md with the correct command. Please let me know if you find any other issues during the installation.

Thank you @roduartefreitas ! I fixed the README.md with the correct command. Please let me know if you find any other issues during the installation.


Logstash Delete/trim Larger size logs

We are using SQS output, but unfortunately SQS allows only 256K size per messages/batch. Does logstash is providing any features to remove/trim larger size log messages, if it reaches beyond certain characters limits.

The plugin will now adjust the size of the batch to go around the 256k limits and yield log when it goes over.

Confirmed. You'll get an error message like follows in the logs:
[2017-01-10T21:29:15,575][WARN ][logstash.outputs.sqs     ] Message exceeds maximum length and will be dropped {:message_size=>264145}


Fix: Update asm to 9.3 to fix crash caused by LWJGL 3.3.1

Without this patch, Minecraft>=22w16a crashes as asm<9.3 doesn't support Java 19, and LWJGL 3.3.1 includes Java 19 classes.

Thanks!


make disclaimer bigger

We just had a guy in the Switchroot Discord thinking the builds were official

Okay, I'll try with bigger fonts or something
Even this repo says it's unofficial

I added a bigger disclaimer in my latest build s
You can check it herehttps://github.com/daviiid99/LineageOS-Switch-T210-UNOFFICIAL/releases


Renamed class 'StrCheck' to 'StrKey'

Seems that the class was changed from StrCheck to StrKey but the README.md was not updated to reflect that; I'm updating it now.

Thanks!


provide mongodb interface on top of 3bot

imagine we create a mongodb interface on top of 3bot
its little bit against our actor concept but would be fantastic tool for developers or 3 party tools to integrate.
following interesting project could be used
https://mockupdb.readthedocs.io/tutorial.html
its not trivial because there is a lot of functionality to implement and some like they query stuff will make it hard.
UI's like https://robomongo.org/ would be very cool though

https://mockupdb.readthedocs.io/tutorial.html


Support Lora Adapter generated from mistral-finetune

Feature request
Recent mistral models inlcuding mistral 7b v0.3 instruct have consolidated.safetensors which have different weights key names compared to what LoRAx expects. Also there are keys like lm_head, embed_tokens, layernorm and postattention_layernorm that vllm finds difficult to deal with.
Are you able to implement an update where a user who has generated a lora safetensors file from mistral-finetune can simply load this directly as a lora adapter into LoRAx and it just works instead of having to first try to map the weights to another weights key name convention as well as figuring out how to deal with unfamiliar keys such as layernorm and postattention_layernorm.
Motivation
Mistral-Finetune will become widely used so users who have generated lora safetensors from this should be able to simply plug and play their lora adapters into LoRAx.
Your contribution
I am happy to provide a lora safetensors if needed to help you understand the problem better.

Is an update available for this issue?


Feature request: Add grace period before message is marked as edited

This is something minor, that nevertheless bothers me whenever an app doesn't have it.
When I edit a message a very short time (eg less than 5s) after posting it, I would like for the small gray EDITED label not to appear. This is because I very often notice typos are bad choices of word immediately after posting a message. Having the message show up as "edited" makes me feel self-conscious, as I feel it communicates that I've changed the content of the message, which usually isn't the case in this situation.
For comparison, reddit has a similar feature, where a message won't show up as edited if the last edit time is less than 5min after post time. I think other forum/message apps have the same feature, but I'm not sure which.

I think other forum/message apps have the same feature, but I'm not sure which.

I just checked, and it seems Discourse has a grace period too.

@PoignardAzur this is an interesting idea; can you provide details on what Discourse uses as the grace period?
Since Zulip is more real-time than reddit or Discourse, I'd expect 5 minutes to be way too long for us (because there might already be a series of 5 messages responding to what you said with a missing "not", and then it'd be confusing as a reader to understand what happened).  I at least pretty often send a message with a typo, see someone reply s/foo/bar/, right? and then fix it all within 1 minute.
Another direction we could think about is having some concept of a "minor edit" that is treated differently.

I haven't tried to measure what Discourse does precisely; I assume the grace period is around a few minutes too, which is probably too long for instant chat.
You could have different grace periods depending on context; something like, "10 seconds by default", "1 minute if nobody has answered", etc. Though I also think the feature shouldn't be overly complicated, else it becomes unpredictable.


[Feature idea] Get the source artifact from GHA workflows

I've got workflows with Python projects where I build an sdist that gets tested, used for building wheels and is subsequently published to PyPI. So one of the first jobs produces it and shares as an artifact with other jobs. This tarball is the source of truth for any other packaging workflows.
Currently, packit.dev forces me to duplicate the sdist creation within it and so I ends up having a situation when there's now 2 sources of truth that may or may not be identical — you never now (but surely hope so!).
I want to propose supporting a mechanism that would allow Packit download that sdist from a GitHub Actions artifact instead of building its equivalent from a Git checkout. Or, alternatively (or additionally), Packit could support fetching SRPMs from GHA artifacts too.
How could this be implemented? Packit could listen for job success events and check if there's an artifact published matching whatever the maintainers would set in .packit.yml. Then, it'd auto-download it into the SRPM building env. Or, in case of SRPM, it'd just proceed with the testing jobs.
Instead of listening for the built-in GH events, Packit could alternatively provide an API end-point where GHA could send an HTTP request (with an artifact bundled) that would trigger Packit's processing workflows (this could be facilitated with a small GitHub Action that would also forward the env vars so Packit would "see" the context of the PR).
The current workaround, as I see it, could be polling GH API in a loop from the create-archive hook to see if an artifact appeared in the last workflow run, and downloading it there. But it seems suboptimal to me because (1) it's probably a waste of resources and (2) I think it wouldn't handle workflow re-runs well.
WDYT?

Sviato, you're not the only one who would benefit from this workflow.
The cockpit team went the most further and actually implemented it by polling the storage endpoint to collect the archive.
I agree that we should have an event-based mechanism instead in Packit that would allow connecting Packit and Github Actions together.

We can see that GitHub can send a webhook payload once a GHA run is completed: https://docs.github.com/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_run
we'd just need to react to that
we also need to check if we need more permissions to get those events

You may want to looks at workflow_job (allowing the users to specify which job to wait for rather than the whole workflow run) or check_suite (but that's more about GH Apps, not GHA).

Hi! During our triaging session last week, we, unfortunately, decided to drop this issue, as this functionality does not seem to affect many users and does not currently align with our priorities. If you feel this should be reconsidered/discussed again, please feel free to reopen!


Filter to feature gates tables

fixes #42102

The followings are done

[Default] and [Stage] lists are fixed
[Since] list will change dynamically based on [Default] and [Stage] selection.
Added reset button.

Since Feature gates tables are responsive table, based on the filter values the table column width will change automatically

Updated page preview: https://deploy-preview-42169--kubernetes-io-main-staging.netlify.app/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features

@sftim @tengqm
Please confirm the changes

The filtering functionality is fine. What I was expecting is something that can sort the table by a column.

it is difficult to do with the .md file .
The following steps to be implemented to do table column sort.

convert .md file to html
Need to include some jQuery datatable library to project and have rewrite table display value to certain datatable library format
eg: https://datatables.net/extensions/scroller/examples/styling/jqueryui.html

it is difficult to do with the .md file .
The following steps to be implemented to do table column sort.

convert .md file to html
Need to include some jQuery datatable library to project and have rewrite table display value to certain datatable library format
eg: https://datatables.net/extensions/scroller/examples/styling/jqueryui.html

@tamilselvan1102 To achieve this in a more organized and efficient manner, I recommend using Hugo shortcodes. These shortcodes allow you to insert dynamic content, such as scripts and CSS, into your Markdown files without cluttering the content or compromising maintainability.
For reference, you can check out draft PR https://github.com/kubernetes/website/pull/42412 i have quickly implemented. This PR should demonstrate how to implement the shortcode effectively. While it might not be the sole solution, it offers a valuable resource from which you can draw insights. Draft-PR-42412-Preview

Thank you @dipesh-rawat for guidance.
I think this is the solution @tengqm looking for.

Since other proposal has been accepted, closing this PR.
Thank you @dipesh-rawat


Override module function in a test after calling jest.mock()

Hi,
I have a react component that uses functions from a module to fetch data and I want to mock it, so I used the jest.mock in order to so and it worked. But I've reached a point in my test where I want to override one of the functions in the mock module and I can't find a way to achieve it.
For example:
moduleName.js
export const a = () => 1;
export const b = () => 2;

__mocks__/moduleName.js
export const a = () => 3;
export const b = () => 4;

moduleName.test.js

jest.mock('moduleName);

describe('Test block', () => {
    it('First test that uses the react component', () => {
        some code that with mount the component.
        here if the component will call the a function from the module it will receive the value 3(from the
        mock).
    })

    it('Second test the uses the react component', () => {
        here I want to override the a function to return the value 8 in the mock.
        But if I mount the component it will still call the a function and will receive the value 3.
    })
})

How can I achieve that? I tried jest.doMock but it doesnt override the jest.mock

just in case someone needs this in the future, you can use the second parameter in the jest.mock to do that.
https://jestjs.io/docs/en/jest-object#jestmockmodulename-factory-options


Json too large for GPT

Hi All!
I realize this should largely be about the actual 'crawling' of the sites - but given this was such a breeze with this tool I now find myself with the issue that the text that has been crawled far exceed the limits of what chatgpt can handle.
Does anyone have any recommendation on how to split the json files so as to evenly reach the limits as set by ChatGPT? I've tried both in GPT and in Assistants. In both cases, my json includes too much text

They said to use maxFileSize or maxTokens parameter to control the size of the json file. https://github.com/BuilderIO/gpt-crawler?tab=readme-ov-file#create-a-custom-gpt

Totally missed that part when doing the setup!

"if you get an error about the file being too large, you can try to split it into multiple files and upload them separately using the option maxFileSize in the config.ts file or also use tokenization to reduce the size of the file with the option maxTokens in the config.ts file"

Thanks for mentioning! I'll have another look on that.

What is the current limit of ChatGPT (size and number of files).
I need to do this on about 5,000 files of C# code.

What is the current limit of ChatGPT (size and number of files).
I need to do this on about 5,000 files of C# code.

Doesn't seem feasible!
What are those file upload size restrictions?

All files uploaded to a GPT or a ChatGPT conversation have a hard limit of 512MB per file.

All text text and document files uploaded to a GPT or to a ChatGPT conversation are capped at 2M tokens per files. This limitation does not apply to spreadsheets.

For images, there's a limit of 20MB per image.

Additionally, there are usage caps:

Each end-user is capped at 10GB.
Each organization is capped at 100GB.
Note: An error will be displayed if a user/org cap has been hit.

From： https://help.openai.com/en/articles/8555545-file-uploads-faq

hmm.. since limitation doesn't apply to spreadsheets. Can we just convert json to excel? would it be the same?

so what are your thoughts ?

Use RAG and langchain instead of ChatGPT or assistants.


Make the package compatible with Chime JS SDK version 2.6

Issue #:

The package was using an older version of JS SDK (v1.0)
Also it has been using components for the legacy screen share which is not supported in the Chime JS SDK version 2.x

Description of changes:

Upgraded package to use Chime JS SDK version 2.6
Added the components missing in the Chime JS SDK version 2.6 but are being used in the package
Refactored and updated the dependency versions

Testing
Manually

How did you test these changes?

By running npm run start and then turning on video.
Deploying a serverless demo and testing basic join operation across Firefox, Chrome and Safari and turning on the video in all the browsers at the same time.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Nice work! Please ensure that the demo works okay after a clean install.


Multiple small issues with Sensebox

Describe the bugs

If you add the WIFI actuator to your robot configuration, the program will compile, but it will not start on the sensebox. Using the sensemap, or connecting to a WiFi, is therefore impossible.
The BMP280 sensor outputs wrong data in 30% of the cases. The data are sometimes 5 times higher, sometimes 20% off the real values. You either get the right or the wrong data during one whole program execution. I was not able to identify a way to reproduce that behavior consistently. It is a bug though, because it does not occure at all, if you use the SenseBox-Blockly editor.
The OLED display is built visibly slower in the Open Roberta Lab, than if you build the same markup using the SenseBox-Blockly editor. For example, if you enter 8 lines of text, the text is show immedeately using the SenseBox-Blockly editor, but takes about 1.5 seconds to built using the Open Roberta Lab.
It is not possible to enter spaces in WIFI SSIDs, eventhough its an often found character nowadays. Some special characters, like the dollar sign ("$"), are also forbidden for the password for no obvious reason.

Additional context

An Sensebox EDU was used for testing
More information can be given by @VinArt

1, 2 and 4 should be now fixed with the hotfix, 3 will be tackled later, since it requires (most probably) the update of the resource container, so this will not be hotfixed.

Seems that this issue is already fixed and released, but never reviewed.
Will be done with the next release.


Merchant Add: Services

Please add to Services: "Ray Luechtefeld, PhD, Leadership & Team Coaching and Development" linked to https://clarity.fm/rayluechtefeld

I don't see anywhere on your page that says you accept Monero, would you
be able to add that? :)
+merchant

Added in #530
+in progress

I have added that I accept Monero.


Progress indicator for just update

Describe the bug
Not really a bug, but couldn't find the appropriate category for this. When using just update`, currently, there is no progress indicator, it just asks for the sudo password and waits until everything is done.
What did you expect to happen?
Can we get a a progress indicator for just update? It could just be in the form of running X, running Y rather than a percentage or a progress bar.
Output of rpm-ostree status
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-framework:39
                   Digest: sha256:a3703cb7b79f453406609416049e0e6d99bb5cda948dbf417af0a0f569837d66
                  Version: 39.20231129.0 (2023-11-29T18:04:31Z)
          LayeredPackages: gparted keychain neofetch pinentry-emacs pinentry-gtk pinentry-qt

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-framework:38
                   Digest: sha256:c3b221f773fe3c6ddc61f454b954f0d5b301288ee5a71d5bec0e623d60412dd2
                  Version: 38.20231128.0 (2023-11-29T18:05:26Z)
          LayeredPackages: gparted keychain neofetch pinentry-emacs pinentry-gtk pinentry-qt wl-clipboard
                   Pinned: yes

Extra information or context
No response

Maybe adding an echo with that snippet might be useful in the meantime?
Just for backstory for the people who might have not been around when we did this: we had to move to a service base approach to ensure the installation could be rebased to a signed image since we can't install a signed image directly at the moment.
We have a just update-ng which switches to bootc and assemble, maybe we should consider an alternative verb with the usual update commands with output in the terminal? IMO we still need to keep just update service based since rebasing to the signed image should be the most important thing.
Thoughts on this?

This is the script I have been using, does this make sense?
#!/usr/bin/env bash

if [ "$#" -ne 1 ] || [ "$1" = "help" ]; then
    echo "Usage: $0 <level>"
    echo "  <level>: Specify the verbosity level - 'full', 'minimal', or 'prompt'"
    echo "  Use 'full' to show full output of each command."
    echo "  Use 'minimal' to show minimal output and indicate success or failure."
    echo "  Use 'prompt' to prompt the user before running each command."
    exit 1
fi

level=$1

# Function to run commands with appropriate verbosity and approval check
update_command() {
    command=$1
    case "$level" in
        full)
            echo "Running $command..."
            $command
            echo "Completed $command"
            ;;
        minimal)
            echo "Running $command..."
            $command > /dev/null 2>&1
            if [ $? -eq 0 ]; then
                echo "Completed $command"
            else
                echo "Failed to complete $command"
                exit 1
            fi
            ;;
        prompt)
            printf "Do you want to run %s? [Y/n]: " "$command"
            read user_input
            user_input=${user_input:-Y}  # Default to Y if Enter is pressed
            if [ "$user_input" = "Y" ] || [ "$user_input" = "y" ]; then
                echo "Running $command..."
                $command
                echo "Completed $command"
            else
                echo "Skipped $command"
            fi
            ;;
        *)
            echo "Invalid level: $level. Please use 'full', 'minimal', 'prompt' or 'help' for usage."
            exit 1
            ;;
    esac
}

# Run rpm-ostree update
update_command "rpm-ostree update"

# Run flatpak update
update_command "flatpak update -y"

# Run distrobox upgrade
update_command "distrobox upgrade -a"

In case the just script is a shell script, I can try and add this to the just update  script as the case for update-verbose.

@bobslept I understand the use of journalctl -fexu 'ublue-update.service' to see what is happening, but wouldn't it be better if it were self contained here rather than running another additional command?
I use this script personally in order to see what is being updated when I want to check if it is happening over slower connectioned when I am travelling or when I see a specific security update for the arch distrobox or flatpak.
Given my usage, I tend to have auto updates turned off and hence this method.

Sorry I think I don't understand it anymore. Recap

Question: Can we have more verbose output?
Anwser: Not in current setup, and we need that setup at this moment because if limitations in other places.
Proposal: Add just update-verbose that gives a variant with output. And for the just update inform users about journalctl

No need for scripts to reach that goal. If you already disable the ublue-update service, the just update should behave like we propose to do with just update-verbose. Doesn't it?

Apologies if I wasn't clear in my response, but this is what I was referring to.

Or did you want more verbose out in the case of a situation where you already did just disable-updates

Alright now I understand! Glad we sorted that part out :smile:
So i did a little bit of fiddling with you script to incorporate it into the just file, so people can try it out. Defaults to full if no argument is given.
# Update system, flatpaks, and containers all at once
update VERB_LEVEL="full":
    #!/usr/bin/env bash
    if systemctl is-enabled ublue-update.timer | grep -q enabled;
    then
      echo "Starting the ublue-update service"
      sudo systemctl start ublue-update.service
    else
      if [ {{ VERB_LEVEL }} = "help" ]; then
          echo "Usage: just update <level>"
          echo "  <level>: Specify the verbosity level - 'full', 'minimal', or 'prompt'"
          echo "  Use 'full' to show full output of each command."
          echo "  Use 'minimal' to show minimal output and indicate success or failure."
          echo "  Use 'prompt' to prompt the user before running each command."
          exit 0
      fi

      # Function to run commands with appropriate verbosity and approval check
      update_command() {
          command=$1
          case "{{ VERB_LEVEL }}" in
              full)
                  echo "Running $command..."
                  $command
                  echo "Completed $command"
                  ;;
              minimal)
                  echo "Running $command..."
                  $command > /dev/null 2>&1
                  if [ $? -eq 0 ]; then
                      echo "Completed $command"
                  else
                      echo "Failed to complete $command"
                      exit 1
                  fi
                  ;;
              prompt)
                  printf "Do you want to run %s? [Y/n]: " "$command"
                  read user_input
                  user_input=${user_input:-Y}  # Default to Y if Enter is pressed
                  if [ "$user_input" = "Y" ] || [ "$user_input" = "y" ]; then
                      echo "Running $command..."
                      $command
                      echo "Completed $command"
                  else
                      echo "Skipped $command"
                  fi
                  ;;
              *)
                  echo "Invalid level: {{ VERB_LEVEL }}. Please use 'full', 'minimal', 'prompt' or 'help' for usage."
                  exit 1
                  ;;
          esac
      }

      # Run rpm-ostree update
      update_command "rpm-ostree update"

      # Run flatpak update
      update_command "flatpak update -y"

      # Run distrobox upgrade
      update_command "distrobox upgrade -a"

    fi

Outputs:
~ ❯ just -f update.just update help
Usage: just update <level>
  <level>: Specify the verbosity level - 'full', 'minimal', or 'prompt'
  Use 'full' to show full output of each command.
  Use 'minimal' to show minimal output and indicate success or failure.
  Use 'prompt' to prompt the user before running each command.

~ ❯ just -f update.just update
Running rpm-ostree update...
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:39
No upgrade available.
Completed rpm-ostree update
Running flatpak update -y...
Looking for updates…

Nothing to do.
Completed flatpak update -y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯ just -f update.just update minimal
Running rpm-ostree update...
Completed rpm-ostree update
Running flatpak update -y...
Completed flatpak update -y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯ just -f update.just update prompt
Do you want to run rpm-ostree update? [Y/n]: n
Skipped rpm-ostree update
Do you want to run flatpak update -y? [Y/n]: n
Skipped flatpak update -y
Do you want to run distrobox upgrade -a? [Y/n]: y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯

So this applies only to the just update where ublue-update is turned off. @castrojo what do you think about this?

This makes complete sense! Hope it gets included now :-)

This makes complete sense! Hope it gets included now :-)

Well if you want and able to make a PR, feel free to do! Not sure how comfortable you are with git?
 And after that create pull request! If it gets accepted it will end up in all images that incorporate just update!

Tried my first PR on this repo: https://github.com/ublue-os/config/pull/167, but it requires review I guess. Sorry, haven't ever used this before!

@bobslept Thank you for the encouragement :-)

Your PR has been merged!! :partying_face:

https://github.com/ublue-os/config/pull/167

It should be available for everyone when the next image rebuilds.
Congrats @bmp, awesome job!

@bobslept Thank you for all the help and encouragement :-)


Case insensitive key comparison

The key case sensitivity rule is rarely followed, this just makes it easier to find what you're looking for.

Accroding to specification keys are case sensitive. I prefer to follow the specs.
But we can add an option to make them case insensitive.
For example:
enum Key {
    CaseSensitive(String)
    CaseInsensitive(String)
}

impl From<String> for Key {...} // sensitive by default

...

fn item<K: Into<Key>>(key: K)

That would work too, but is it worth it?
https://wiki.hydrogenaud.io/index.php?title=APE_Tag_Item says:

APE Tags Item Key are case sensitive.
Nevertheless it is forbidden to use APE Tags Item Key which only differs in case.
And nevertheless Tag readers are recommended to be case insensitive.

I can't think of a situation where case sensitivity is really needed, it just adds a little extra unneeded complexity. For example, TagLib writes the artist key as "ARTIST" rather than "Artist", which I'm sure others have followed as a result.


SIL: Introduce lowered SILLayouts.

This gives us a concept we can eventually use to cache the lowered physical layout of fragile structs and classes, and more immediately, concretize the layout of closure boxes in a way that lets us represent the capture of generic environments and multiple captured values without compromising the "nominal" nature of box layouts. To start exercising the basic implementation, change the representation of SILBoxType to be in terms of a SILLayout, though avoid any immediate functionality change by preserving the single-boxed-type interface for now.

@swift-ci Please smoke test and merge


Platform independent compilation

I made a few changes to eliminate the need of a maven profile and asserting line endings...
Also enable windows buld
Lemme know what you think.


python312Packages.karton-core: 5.4.0 -> 5.5.0

Diff: https://github.com/CERT-Polska/karton/compare/refs/tags/v5.4.0...v5.5.0
Changelog: https://github.com/CERT-Polska/karton/releases/tag/v5.5.0
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 341459 at a94bdd91 run on aarch64-darwin 1

16 packages built successfully:

python311Packages.karton-asciimagic
python311Packages.karton-autoit-ripper
python311Packages.karton-classifier
python311Packages.karton-config-extractor
python311Packages.karton-core
python311Packages.karton-dashboard
python311Packages.karton-mwdb-reporter
python311Packages.karton-yaramatcher
python312Packages.karton-asciimagic
python312Packages.karton-autoit-ripper
python312Packages.karton-classifier
python312Packages.karton-config-extractor
python312Packages.karton-core
python312Packages.karton-dashboard
python312Packages.karton-mwdb-reporter
python312Packages.karton-yaramatcher


rc17 retention policy deletion kicks in too early

I have a retention policy of 7d:
      name  duration  replicaN default
0  default         0         1    True
1    short  168h0m0s         1   False

A few minutes after I push data to "short".amiigodev I see this in the logs:
[srvr] 2015/03/31 23:38:30 retention policy enforcement check commencing
[srvr] 2015/03/31 23:38:30 shard group 41, retention policy short, database amiigodev due for deletion
[srvr] 2015/03/31 23:48:31 retention policy enforcement check commencing

And if I query the data it is in fact gone.
I had a single point in the db that was in the future 2015-04-01, that point did not show up in any query (that I wanted to file an issue for it), and now only that point is returned

Can you please show us a sequence of curl commands that bring this out -- create a database, create an retention period, write the data in, query it to show that is there, wait until retention kicks in, and then query again. You can shorten the retention enforcement period by changing your config file. It defaults to 10 minutes, but you could make it 30 seconds.

@otoolep I think I found what happens. The date of the data I push is old (2014), when retention period enforcement kicks in it removes them all!
I was under the impression that the records get deleted not based on their timestamp but by when they are recorded, this makes the application of retention period limited to when system has up-to-date records and cannot be used with any historical data. IOW it will depend heavily on clock time.
I use the "short" retention policy for a temporary space to keep some information computed for some time, It would be teremendously helpful if this behavior could be selected (to delete records based on how long they have been in database and not their actual timestamp).

This is what I suspected was happening. Retention policy enforcement is based on event time, not reception (recording) time. This means if you stream data into the past, it may be deleted very quickly if you do not have retention policy covering the timeframe in question.
Right now this is how it works, so I am closing the issue, but I understand your request. You might like to open a ticket, describing exactly what you want.


clues: add fairy ring hint to cryptic clue

Added fairy ring hint to the medium cryptic clue with donovan the handyman. Regarding issue Fixes #15366 .

You can edit the PR body to Fixes #15366 and github will sync it.

You can edit the PR body to Fixes #15366 and github will sync it.

Thank you!


Remove usage of mapping types

Description
Remove usage of mapping types
Issues Resolved
#98
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1c28a08). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #119   +/-   ##
=======================================
  Coverage        ?   83.75%
  Complexity      ?      555
=======================================
  Files           ?       61
  Lines           ?     2050
  Branches        ?      146
=======================================
  Hits            ?     1717
  Misses          ?      227
  Partials        ?      106

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 1c28a08...54fdbe2. Read the comment docs.


[Doc] [Do-not-Merge] Add a parameter to forcefully close fenced topics

Modifications

To align with #8561, add a parameter for both broker and standalone pulsar to forcefully close fenced topics.
Remove a duplicate parameter from the list of standalone pulsar.

Note: This doc change will be applied to more historical versions (since 2.7.0) after the doc PR gets approval.

Preview

Documentation

[x] doc

Hi @massakam @codelipenghui @Anonymitaet, can you please review this PR? Thanks.
Please kindly note that this doc change will be applied to more historical versions (since 2.7.0) after the PR gets approval.

Thanks for your review and approval. I've applied the same changes to more historical versions since 2.7.0. PTAL.

Hi @massakam @codelipenghui @Anonymitaet, can you please review this PR? Thanks.
Please kindly note that this doc change will be applied to more historical versions (since 2.7.0) after the PR gets approval.

Ping @urfreespace we've merged this code PR, please do not forget to migrate changes, thanks


Include a link to the hosted documentation in the repository details

It's a little bit tricky to find the docs currently. I didn't realise there were any until I found them via google search. You can add a link to the repo details by clicking the gear (⚙) icon next to "about" on the LHS of the repo homepage

I'm not sure what you mean. The links to the docs is in the home page README.

yep I can see that but it's easy to miss. this would be a quick way to make it easier for newbies to find the docs
example here in the bazel repo: https://github.com/bazelbuild/bazel

Oh. That.  I never would have noticed it. I ignore most boiler-plate.  The about box is one I rarely look in.  I can see about getting one of the admins go do something.
It still sort of feels funny.  A link like that should be to the project rather than a specific part. The bazel.build link is to the overall project - not really the docs. You have to hunt the bazel project site to find the reference pages.


add outline to the number

I came to the github repo to request this, an outline would be great as I am having it on my map and visibility becomes low (Unless I change the color)

I think #30 solves this, closing.


Unable to use with react native

From what i can gather enumify has a dependency of babel-preset-es2015which kind of conflicts with react-native default presets and hence i am unable to use this with react-native currently.  More information can be found from here https://github.com/facebook/react-native/issues/5747#issuecomment-192356656. Currently i am forced to locally copy this code in my source code to use this library. Any help would be appreciated. Thanks

+1

Same. Thanks!

+1

+1

+1

+1

+1

+1


Emotes Menu

About the PR

Adds emote menu that can be bind to key (default is L) or opened from top menu bar.
Icons for emotes not implemented in this PR, I have no such skill

Why / Balance

Makes the use of emotions more accessible, understandable, consistent and comfortable.
Technical details

Uses EntityWhitelist for emote prototype whitelist and blacklist, to make emotes available only for certain entities (like borgs).
Localize all emote names and messages
Fix EntityWhitelist a requireAll check
Remove unused WaTail emote

Media

https://github.com/space-wizards/space-station-14/assets/14136326/bf51a81d-8f16-4394-bfc3-07513e8a2250

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Added emote panel (by default L)

This is amazing, my only complaint is using L as the keybind as it requires me to lift either my WASD hand or my mouse hand, thus limiting robustness

This is amazing, my only complaint is using L as the keybind as it requires me to lift either my WASD hand or my mouse hand, thus limiting robustness

I took Literally random button, so I open to suggestions

This is amazing, my only complaint is using L as the keybind as it requires me to lift either my WASD hand or my mouse hand, thus limiting robustness

I took Literally random button, so I open to suggestions

As long as you can change the bind, this is amazing for new players, and people who don't like typing

Massive upvote for this feature, we were just talking about it in the voice chat yesterday.

Would you consider adding #26594 to this feature?

they have, they show that they have in the video at the end

The march towards controller support continues ever onwards

Excellent work! This will make all sorts of emotes more accessible to players, as previously you had to learn from others or the code what emotes were what, but now it's all in one place and easily clickable.
I wonder if this could be made client configurable - then players could add their own emotes and categories to the wheel, similar to how emotes can be bound to keyboard with some config editing.

Its good, but needs more icons

Icons for emotes not implemented in this PR, I have no such skill

be the change you want to see

Test fails real.

changing the default key to Y as proposed


Flag profiles ready to expire eligible for an early renewal.

minor changes to help readabiity.

Coverage increased (+0.003%) to 92.956% when pulling edccf5940edaead8637e7f3289bb88c388fac3a9 on akatsoulas:curators-group-revouch into f67454d2d65088d501819b5c2703aaf180b6df23 on mozilla:master.

Tested it locally:

It doesn't allow you to renew membership for members
There is no way for curators to filter only pending renewals

@johngian pr updated. The membership of existing members can be renewed. As for the second comment, let's tackle it in another PR since it seems to me a bit out of scope.

Coverage decreased (-0.004%) to 92.949% when pulling 8ef4aa4321ad0d06919476e286966d11ce3af3c6 on akatsoulas:curators-group-revouch into f67454d2d65088d501819b5c2703aaf180b6df23 on mozilla:master.

@akatsoulas I pushed a patch here to allow filtering renewals please review and apply:
https://github.com/johngian/mozillians/commit/b3aedc03dbda57abab95365feda7da7cc612b54f

Coverage decreased (-0.01%) to 92.941% when pulling dd19538eaa7394d88afb11c2b23ee7859902eb4f on akatsoulas:curators-group-revouch into f67454d2d65088d501819b5c2703aaf180b6df23 on mozilla:master.


COB Transition Demo 1

COB transition work to be discussed on 2024-08-12 OBI dev call.

We never, ever remove a term that we've published. Please add OBI:0001720 to the obsolete template.

Sorry, that was a sloppy mistake on my part. I'm not sure how I missed that step. Fixed.

Everything seems to be working except:

COB_based_on which violated src/sparql/iri-violation.rq, see https://github.com/OBOFoundry/COB/issues/280
obi.obo conversion, because of a problem in COB:

OBO STRUCTURE ERROR Ontology does not conform to OBO structure rules:                                                                                multiple comment tags not allowed. in frame:Frame(CHEBI:33252 id( CHEBI:33252)name( atomic nucleus)comment( This is equivalent to CHEBI:33252)comment( Some people may be uncomfortable calling every proton an atomic nucleus)is_a( CHEBI:36342))


Consider project name under for RI (if any) and TCK

At the moment modules other than the API use a package name org.eclipse.configjsr. That seems legitimate (it is unlikely another Eclipse project uses that name), but most other Eclipse projects used as RI for JSRs did pick a "friendly" code-name, e.g. EclipseLink, Yasson, etc.
Could we also try to find such a code-name?

yep. interesting point. We can discuss to see which code-name is more appropriate.

The org.eclipse.configjsr mimics the way it's done in JBatch, CDI, BeanValidation, etc.
The TCK is not the implmentation, but otoh it is also not in the javax.config package of course.

Yes, we also did something similar with JSR 363 except RI and TCK there share the same package domain "tec.units". So far 363 also had no "friendly" RI code-name, but we did a survey for the next release and found one.

There needs to be a RI, but it may depend, if it was established/used at Eclipse or EE4J, Apache or somewhere else.

As long as the RI is Apache license, we will be fine. Maybe we can create a RI in Eclipse repo? Thoughts?

Let's discuss it today. @atsticks wanted to talk about it last week but he could not make it and other topics took more time. He said he plans to join today and as I have a headset I should also make it. I would rather avoid creating the RI directly in the JSR repo itself. TCK, that sounds possible there as it is tied to the spec, but the RI even if it is the official reference implementation better have a separate repo. JCache did, and all other JSRs I know or participate in. Other candidates could be those at Apache (Geronimo or Tamaya)

So what's the RI now, or will the JSR be abandoned at the JCP in which case there can be more than one "Compatible Implementation" of a Jakarta EE spec?


Added a note about installing to the correct directory on Windows

Wanted to put a quick note in the troubleshooting area about file permissions on the /Wind

Messed up a directory path. Fixing in a new PR


Menu item for copying app info to clipboard

See additional info here, and maybe there are more instances of this.
Idea is that there is a menu item that when clicked will copy application details such as the version, operating system, etc... that one could paste into an issue body or comment body instead of having to manually type it out.

Thinking about grabbing this one if that's okay. Just to clarify what the expectation is for this...
Adding a menu item (Copy: 'Copy Support Information' ?) on the 'Help' menu, that on click would write to clipboard the following:

OS Version
App Version
Shell (electron version)
Node Version
V8 Version
Architecture
Curl Version

As far as installation method listed in the referenced github issue, is that a requirement for this? If it is, not entirely sure where to start with that so if there are any ideas let me know otherwise I can get to researching!
Thanks


Add(Ahmed Rowaihi): react-native-i18n-storage

Thank you 🚀🚀🚀🚀🚀

@Mohd-PH check readme is not updating...

Yeah I'll do it manually and try to fix the github action asap
Thanks 😊

Hala @Alaboudi1
I've looked into the issue and tried to run the same workflow in my private clone of this repo
I believe it is a permission issue
We need the write permission for the contents scope in this organization settings
Only the admin can set the settings
Here how you can enable this permission:
https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-the-default-github_token-permissions
Looking forward for your input and thank you 🚀

@Mohd-PH I just gave you admin permission to debug this issue.

@Alaboudi1 everything works as it should now
Thank you
I think the previous documentation link was old and not accurate
I followed this blog post by github about permission and specified them in the workflow yaml file
GitHub Actions: Control permissions for GITHUB_TOKEN
Also fixed an issue where markdown fails to parse empty td tags

My pleasure 😄


Feature Request - agile predictions

Would you consider adding the ability to include Octopus Agile predictions? It would be especially useful to have predicted rates for a day or two in the future.
This data is already easy to get into Home Assistant, so I think it would just be a case of adding another config item to set the sensor.

FYI, the OE Greenness Forecast only gives a forecast for 23:00 to 06:00 each day.

The Agile Predict site, here, has a nice API, and it's easy to get that into HA:
https://prices.fly.dev/
This seems to stretch for a week - and is not official, but seems to be a good guide to what the prices could be.

You could try this ... https://github.com/elyobelyob/octopus-energy-greenness-forecast-card ...
I didn't want to mention it myself, but it's what I use ...

or this:

type: custom:apexcharts-card
experimental:
  color_threshold: true
header:
  show: true
  title: Greenness Forecast
graph_span: 7d
span:
  start: hour
apex_config:
  chart:
    height: 135
  stroke:
    width: 4
  xaxis:
    labels:
      format: ddd
series:
  - entity: sensor.octopus_energy_a_xxxxxxxx_greenness_forecast_current_index
    name: Forecast
    show:
      in_header: false
      legend_value: false
    color_threshold:
      - value: 0
        color: red
      - value: 40
        color: orange
      - value: 80
        color: green
    data_generator: |
      return entity.attributes.forecast.slice(0, 7).map((entry) => {
      return [new Date(entry.start), entry.greenness_score];
        });type: ''

Not sure where I got this from so can't give credit unfortunately.

Thanks so much for the help. I like Apex charts, and use it to show price predictions from Agile Predict.  However, I really like the octopus-energy-rates-card view - e.g. the colour-coded table with prices.   I'd love it if there was the ability to add data for several days ahead --- e.g. just extending the chart beyond 11pm tomorrow.
I have the data for this - it comes from the Agile Predict API - but I think to add this there just needs to be another option in octopus-energy-rates-card;  e.g. you could have an "agileEntity" property which would work in a similar way to "futureEntity" but just further into the future.


React.createClass is deprecated and will be removed in version 16

As the warning says when using this library:
Warning: MathJaxNode: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.

when this pull is sorted out (https://github.com/SamyPesse/react-mathjax/pull/8) this issue can be closed

Fixed in 1.0.0


[build.sh] Print out undocumented RealmSwift declarations

Doubt this change caused the performance regressions. Merging.


Slim Framework issues

Just tested against Slim Framework using:
php composer.phar create-project slim/slim-skeleton [my-app-name]
cd [my-app-name]
Create the .phan and config.php inside by changing /vendor/symfony/console to just /vendor (using the example configuration).
go back to the [my-app-name]
run php phan.phar (using the latest phar)
And the result is:
src/routes.php:4 PhanUndeclaredVariable Variable $app is undeclared
src/routes.php:6 PhanUndeclaredVariable Variable $this is undeclared
It is not detecting that $app was defined on global scope in index.php.
$this, inside the get method closure is supposedly to be a container, but isn't picked up either as such.
Adding /** @var $app \Slim\App */ doesn't sort it.
Are those false positives due to edge cases of php syntax?
@akrabat @silentworks @slimphp

First, it should be /** \Slim\App $app */ there. The type comes first.
Also, global scope is tricky because order matters. Try putting your index.php first in your file list.
I don't understand what you mean by $this being a container. Can you provide a short code snippet?

@rlerdorf,
For this code:
$app = new \Slim\App();
$app->get('/', function ($request, $response) {
    dump($this->get('settings'));
});
$app->run();

Slim has bound the closure to its DI container, so $this is an instance of \Slim\Container.

Ah, ok. Phan has no support for Closure::bind (http://php.net/manual/en/closure.bind.php) at this point.
I've created a separate ticket for that issue: https://github.com/etsy/phan/issues/309.

If we can confirm that the global issue was fixed by updating the file order, I'll close this ticket and try to get to #309.


System aarch64-darwin is not supported

I would like to set up a Nix Purescript project on an M1 Mac, but purs-nix does not support aarch64-darwin; is there a strong reason for this?

Duplicate


Add catalog-info.yaml config file

This pull request adds a Backstage entity metadata file to this repository so that the component can be added to the VMware Tanzu Application Platform software catalog.
After this pull request is merged, the component will become available.
For more information, read an overview of the Backstage software catalog.

Allowed for TAP to integrate with this app


fix: disable logging for prod, create .easybsb directory for prod

closes #204

create directory if not exists allready solved with users, changed name to .easybsb now.


[Autocomplete] The selected option is not displayed for asynchronous list of options

Hello,

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

I was trying to use the Autocomplete component and I ran into the following issue:
I have an asynchronous call to the server that is supposed to bring the list of options while I design the Autocomplete component into the page. Since the call to the server takes longer than the render of the component, the selected option won't be displayed even after the options list was populated.
Current Behavior 😯
My list of options is empty for the moment. I render the Autocomplete component. The selected option is not displayed(obviously). The server call finishes and the options list is now populated. The selected option is still not being displayed(the problem). However, if I open the Autocomplete and loose focus somewhere in the page, the selected option is displayed correctly.
Expected Behavior 🤔
My list of options is empty for the moment. I render the Autocomplete component. The selected option is not displayed(obviously). The server call finishes and the options list is now populated. The selected option is now being displayed.
Steps to Reproduce 🕹
Here is the reproduction of the situation explained above: https://codesandbox.io/s/material-ui-issue-forked-bh727?file=/src/Demo.js I have simulated the asynchronous call by waiting for 3 seconds before populating the list of options.
Steps:
1.Open the Code Sand Box provided above
2.Wait for 3 seconds
3.Observe that the selected option is not being displayed

4.Open the Autocomplete and observe the selected option is highlighted

5.Click anywhere in the page and the selected option is now being displayed correctly

Context 🔦
I am trying to render the React components while fetching the data.
Notes

I have noticed that this behavior is not present if I did not used the callback functions instead of arrow functions but this is not desirable considering the performance costs.
Also, the behavior is not present if the value(the state) is firstly initialized with a different value than the selected option. You can see the difference by changing this line of code from line 24:
 const [state, setState] = useState(1);             into this:             const [state, setState] = useState(2);
Please open the Console to see the logged info that helped me to debug.
Thhank you very much!

Duplicate of #19173

@andra-sava The linked issue is up for grab. If you want to work on the proposed solution, feel free too :)


PWA on mobile

Hi, I have been looking at ways to view PWA's on a device during development, but haven't been successful. Is there any way to view your app on a mobile device during development?

Hi!
Thanks for the feedback. I've rewritten the codelab from scratch and recommend using Glitch, it'll make it much easier to test on mobile and desktop as you're going. The code has been updated, I'm just waiting for the guide to go live. In the meantime, I've deployed the codelab at https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/.
If you find any issues with the new codelab, please let us know!
Thanks!


Three-mesh-ui multiple versions error

In branch ui_filiz, I'm using one of the three-mesh-ui versions; however, it is giving an multiple versions error in the console

I tried making a change on ui_filiz where I moved all our jsdelivr stuff to skypack.
Unfortunately, XRControllerModelFactory (used in controllers.mjs to generate the controller meshes in VR) does not seem to be available on skypack.
Leaving this one library on jsdelivr works, but it displays a warning that multiple versions of THREE.js are being imported (since XRControllerModelFactory pulls in its own).
Is there a good alternative that will let us work with both Three-Mesh-UI AND XRControllerModelFactory, where both see/use the same underlying THREE.js version?
Maybe we need to give up on using CDNs and just build our dependencies into a file that lives on our own server. It's the final week, so hopefully our dependencies are stable enough now that we know what to include?

sorry @DMGregory just looking at this now. I assume building our own dependencies would make for a lot of extra work down the line wrt updates etc. will return to this in a sec


Bump service version from 3.26.0 to 3.27.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 31.553%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
12549

Relevant Lines:
14239

💛  - Coveralls


feat: added validate-palindrome.java

Why:
Closes #34
What's being changed:

Added programme to validate palindrome in java

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

I added myself to the contributors in the README.

Thanks for your contribution, it will be merged soon.


Update commands.js

After var awayName = user.name + ' - Ⓐⓦⓐⓨ';, you forgot your break; line :s

I was testing you. Keeping you on your toes.


Readiness/Liveness probes for srping boot should be aware of server.servlet-path property

Generated probes for spring boot application need to check the server.servlet-path property.
There are cases, where mvc path is moved from / to a custom location.
Example: https://docs.spring.io/spring-boot/docs/current/reference/html/howto-actuator.html#howto-use-actuator-with-jersey
For those cases, it would be really nice if f-m-p could read the configuration and adapt the path to the health endpoint.

agreed, we should pick up this configuration option from spring-boot.


Misinterpretation of HTML tags in plain text

Hey @thetarnav  thank you very much for a great module.
Just a bug that I noticed. Seems that if the streaming text has a html tag even outside of code block, streaming-markdown converts it to html. See attached screenshot.

the parser doesn’t parse html elements, so I think it’s up to the renderer
if the renderer is using innerHtml to render the text, the elements will just get rendered
Also since this is supposed to be a optimistic parser, html elements will get rendered, even if only the opening element is present, when supported.
Can you share more details about the markdown content so there is no misunderstanding and what renderer are you using?