exploring tiledb's dataloaders

I ran into Tiledb's ML repo (https://github.com/TileDB-Inc/TileDB-ML/blob/master/tiledb/ml/readers/pytorch.py), which seems to implement a pytorch based dataloader. It looks like we can speed up our dataloaders without setting threads to 1.
Mostly exploration and then figuring out if we can adopt the same logic to our implementations.

Setting context to "spawn" will remove the need to setting threads to 1.

I'm going to refactor the dataloader to reduce the number of database accesses to one per mini-batch
I'm going to move to a sample based epoch rather than multi-set. I think it makes more sense.


Fixing issue 980 by changing default timestamp for start parameter in…

default timestamp for "start" parameter was set to 01/01/1950, so no data before that date was fetched. Set default value to 01/01/1900. This should fix https://github.com/ranaroussi/yfinance/issues/980
… base.py

Can you create another PR to merge into release/0.1. Currently we have two versions on the go.


Certain characters taking up more than one line in height

I've only noticed this for a single character type so far, and it's the mesh-like character that is used for progress bars
Here's what I mean

In the screenshot above the difference in height between the said mesh-like character and the box character is clearly visible, but the extending up on the line above is more clearly visible in this next one

It's not the biggest of bugs and it's not really that important nor does it need immediate attention, but it is something that is really bothering me and I thought I should point it out.

What character is this specifically? Can you find the unicode codepoint for it? (Or copy the output of that box and put it into a file and upload it?)

What character is this specifically? Can you find the unicode codepoint for it? (Or copy the output of that box and put it into a file and upload it?)

Yes, I have found the character in the character map, here is a screenshot to verify that it is in fact that one

And I have highlighted the Unicode value at the bottom


Performance profiling of the Graph

Related to problem in #41

on hotgym_full , garbage collection takes 49% time, can we reduce it?
with strokeBorderWidth(=0.1) the function Dygraph.stroke._drawSeries() rampages from about 10sec/graph to 280sec/graph!
highlightSeriesOpts also causing slowdown
large graph loading too slow -- what are the steps, are we using chunking for that? may need to revert to a lower MAX_FILE_SIZE

ad 4) I fugured with "hide all" option, the graph renders much faster. Could be show the loading screen, keep loading (if not streaming) and Show All when reached end of file?

I think that 60MB might be too large. That said, we can profile the different parts of the process.

Ok, we can try how reducing the size solves the issue.
Currently we resort to "Windowing" on large files, which is great for streaming data, but not ok if you want to work with the whole file, as in the hotgym_full.
What do you think about adding a toggle: Whole file (slow), Sliding window, Compressed, that would appear only if file>MAX_SIZE? Whole file & Windowing are implemented, Compressed would be idea of #43.

That might be the solution. This ties into my thoughts about a revamped UX, where we perhaps have a step after the file has been checked, to ask the user how they would like the file to be processed.


add unrar license and use

Description of changes
License is under the "UnRAR source" link on https://www.rarlab.com/rar_add.htm, not sure if it's better to link to the tarfile or to the webpage.

lib/licenses: add unrar
treewide: use unrar license where applicable

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

[x] Fits CONTRIBUTING.md.

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

Great, thanks!
BTW, here is the relevant part of the license (the only part that applies to and needs to be included in any derivative software):
   2. UnRAR source code may be used in any software to handle
      RAR archives without limitations free of charge, but cannot be
      used to develop RAR (WinRAR) compatible archiver and to
      re-create RAR compression algorithm, which is proprietary.
      Distribution of modified UnRAR source code in separate form
      or as a part of other software is permitted, provided that
      full text of this paragraph, starting from "UnRAR source code"
      words, is included in license, or in documentation if license
      is not available, and in source code comments of resulting package.

IANAL, but this doesn't read like it would interfere at all with Hydra.

There is currently no consensus to build redistributable non‐free packages on Hydra and I personally feel it would be a bit of a minefield; we already don’t do great at FOOS licence compliance and having Hydra implicitly agree to a bunch of dodgy EULAs would be very risky. Clause 6 is somewhat concerning; strictly‐enforced use restrictions are more fraught than simple “no derivatives” licences.

Also a bit OT for the PR, since the defaults for all of these packages are (naturally) to exclude the rar version (presumably not overridden at the top-level), and therefore the rar-less versions are what get built.

Yes. There are FOSS implementations of the RAR format, such as libarchive; they may not be quite as feature‐complete as the proprietary code, but I think helping upstreams migrate to using alternative implementations would a better approach to getting Hydra to build more tools with RAR support.

Hmm... well, IANAL but from what I understand of this license text... if we were to

take unrarsrc-7.0.9.tar.gz
delete everything from license.txt except paragraph 2
add a comment at the top of the file with a copy of paragraph 2
create a new archive of the result

then we, while complying with the original license, will have an archive containing UnRAR source code and relieve any recipients of said new archive from ever seeing or having to comply with paragraph 6.
I should point out that e.g. john does not include the original 6-paragraph license text at all, but only the second paragraph. Not sure what other software using this code does, but might be worth looking at this license as effectively consisting only of paragraph 2.

License texts themselves cannot be assumed to be licensed in the same way as the code itself; for example GPL3 is not GPL3 licensed but copyrighted.
I won't be taking on the legal responsibility of chopping up licenses.

Hi @eclairevoyant, have you given up on this? I was hoping to merge and was just waiting to hear back about the URL, since you had asked about where would be good to link to.

I plan to remove myself from nixpkgs and delete my gh fork; feel free to pick any of my closed PRs up as you wish.

Oh, no. I am sorry to see you go. :(

It's ok, I had a good run and learnt a lot.
It was great working with you and many others :smile:

@emilazy #341115


Add tests and description about usage of go 1.16 embed feature.

Nothing changed in a code. Just added new test/testdata and updated README.
TBD: DiscoverSQLMigrationsFromFilesystem and all under the hood may be refactored from http.FileSystem to fs.FS but it will break backwards compatibility.

:+1: Thanks

I don’t think that would work well, especially on Windows, because DiscoverSQLMigrationsFromFilesystem for some reason converts dir to absolute path using filepath.Abs.


pipe stdin to vmd

e.g. be able to do this:
cat README.md | vmd

Doesn't make vmd a pager yet, but does allow for more unixy actions. Also maybe detect if in TTY to pipe to stdout. Not sure what the added value would be over something like cat, but playing ball with cli tools is a good thing imo.
vmd README.md | grep -C 3 foo > file.md

maybe you could use something like get-stdin

@akileez Oh, that's really useful. Thanks for sharing!

my pleasure.

There's also read-file-stdin and write-file-stdout, which work incredibly well.

read-file-stdin looks like it's worth considering. The source is only couple lines plus a dependency. It takes a file and falls back to stdin if it doesn't exist. It's more like "read-file-or-stdin".  So we wouldn't have to do ifs and all that. The module does it for us. Good find!

:+1:
Would enable the following coolness:
npm view browserify readme | vmd

pushed in 1.7.0 :+1:

:dancers:

🙌🔥🍉


Migrations bug for upgrade from 1.2 to 1.3

Gitea version (or commit ref): 1.3.1+1-g8a19c6b9
Operating system: Ubuntu 16.04
Database (use [x]):

[x] PostgreSQL

Can you reproduce the bug at https://try.gitea.io:

[x] Not relevant

Description
I think I have discovered a serious migrations bug when upgrading from version 1.2.3 to version 1.3.1 today. It seems that several migrations were backported to the 1.2 branch out of order. Our Gitea installation had a database version of 42 before the upgrade and was upgraded to version 49. However, due to the ordering of the migrations, three of them were applied twice and three were not applied at all.
I becomes clearer if looking at the diff of models/migrations/migrations.go from the 1.2 to the 1.3 branch:
@@ -126,12 +126,26 @@ var migrations = []Migration{
        NewMigration("unescape user full names", unescapeUserFullNames),
        // v38 -> v39
        NewMigration("remove commits and settings unit types", removeCommitsUnitType),
-       // v43 -> v44
-       NewMigration("fix protected branch can push value to false", fixProtectedBranchCanPushValue),
+       // v39 -> v40
+       NewMigration("adds time tracking and stopwatches", addTimetracking),
+       // v40 -> v41
+       NewMigration("migrate protected branch struct", migrateProtectedBranchStruct),
+       // v41 -> v42
+       NewMigration("add default value to user prohibit_login", addDefaultValueToUserProhibitLogin),
        // v42 -> v43
        NewMigration("add tags to releases and sync existing repositories", releaseAddColumnIsTagAndSyncTags),
+       // v43 -> v44
+       NewMigration("fix protected branch can push value to false", fixProtectedBranchCanPushValue),
        // v44 -> v45
        NewMigration("remove duplicate unit types", removeDuplicateUnitTypes),
+       // v45 -> v46
+       NewMigration("remove index column from repo_unit table", removeIndexColumnFromRepoUnitTable),
+       // v46 -> v47
+       NewMigration("remove organization watch repositories", removeOrganizationWatchRepo),
+       // v47 -> v48
+       NewMigration("add deleted branches", addDeletedBranch),
+       // v48 -> v49
+       NewMigration("add repo indexer status", addRepoIndexerStatus),
 }

 // Migrate database to current version

As can be seen, v43, v42 and v44 were applied (in that order) in the 1.2 branch (but with database versions of 40, 41 and 42). v39, v40 and v41 were then added before the existing migrations in the 1.3 branch. This led to v39, v40 and v41 being skipped, while v42, v43 and v44 have been applied a second time:
2017/12/11 16:13:30 [I] Migration: add tags to releases and sync existing repositories
2017/12/11 16:13:30 [I] Migration: fix protected branch can push value to false
2017/12/11 16:13:31 [I] Migration: remove duplicate unit types
2017/12/11 16:13:31 [I] Migration: remove index column from repo_unit table
2017/12/11 16:13:31 [I] Migration: remove organization watch repositories
2017/12/11 16:13:31 [I] Migration: add deleted branches
2017/12/11 16:13:31 [I] Migration: add repo indexer status

Fixed by #3157


Updates to Wkly Module Metrics

Hello @KELSEYDOWLING7 , we are finally bringing the module metrics report back up in priority for revisions. Eventually, we would like to fold this report into the Operations Report instead of being run separately. For now, please work on this outside of the Operations Report and outside of the automation until we finalize all of the metrics needed. Once finalized, we will then work on where each metric should go in the Operations report.
We made several comments in the file attached below. We would like to consolidate and get rid of several of the metrics and also requested changes to current metrics as well as new. Some of the metrics we will also need to discuss before finalizing (e.g. there's a metric that we need the distribution reran so we can decide what categories would make sense to convert it to a categorical table). Can you please take a look and let us know if you have any questions? Once we get closer to a final version, we will re-evaluate which metrics should also be updated to be stratified by site FYI.
We know you have several higher priorities right now, so we understand you may not be able to get started on this right away which is fine.
Comments below:
CCC_Weekly_Module_Metrics_12_11_2023_AMRComments_Updated01242024.pdf

@robertsamm  Hi, thanks I'll get started on these. One general question though. Is it possible to keep this as a separate report? The Operations report already can take up to an hour to run depending on the machine/issues/testing/ect. We were really hoping to reduce its size, which is where we got into the specifics of what csv outputs were or were not being used. I'd very much like these tables to not be added to that report, as it would only increase how long it already takes to run/test the Operations report.

@robertsamm Here's the updated report from the notes I could see. please let me know if anything is missing or misinterpreted.
CCC-Weekly-Module-Metrics_RMD.pdf
For table 2, if stratification of recruitment status is removed there are therefore only 2 columns, so I'm not sure if row percentages would make sense. Each row would be 100%. For now I kept them as the percentage of participants within each Module as it was before (so each section will have the 3 not started, started, and submitted rows add up to 100).
For table 7 in the currently existing report, we do have a Github issue for that (https://github.com/episphere/questionnaire/issues/220) but no current ETA on making a fix.

Hi Kelsey,
This is getting much closer. I've attached with feedback.
CCC-Weekly-Module-Metrics_MJB.pdf
After you address this, we'll take a look and see what else we need.
Thanks

Hi @KELSEYDOWLING7 We think looks really good. A couple of small changes and then this should be good to move to prod.

Delete Figure 1 and Figures 2.1-2.4. They aren't revealing much that is useful and we're finding them pretty hard to consume.
Table 6 change units to minutes to better align with the other information in the report
Table 2- is it possible to put Not Started, Started, Submitted in columns and have BOH, MRE, SAS, LAW in rows to make it easier to follow?
One table to add to the beginning of the report, please make it Table 1. Completion of Baseline Survey by Site. Please make the format the same as Table 13 from the Weekly Operations report but it should just reflect Baseline Survey, not blood collection.

Then we'll give it one last glance before you post it to Connect_ALL.

Actually one more thing, sorry! @KELSEYDOWLING7 please add to Table 4 a row at the bottom for 'All Modules' meaning time from verification to the time they completed the last of the four modules they submitted, regardless of which one was last. And please change Table 4 to days instead of hours.

Good morning, @brotzmanmj  Just about done. The only question I have is should that Table 4 only look at Active participants, or at all participants? I realized I had it set to active only

Good question @KELSEYDOWLING7  Let's include all participants

@brotzmanmj  Thank you! Please let me know if anything else should be changed. I assumed the new table one should just be essentially all completed or not all completed, and that row percentages would make the most sense.
CCC-Weekly-Module-Metrics_RMD.pdf

@KELSEYDOWLING7 just one thing, the new table looks great, can you change in the title from '...Baseline Surveys...' to '...Initial Survey...' for consistency? The format looks perfect.

And I think this change still needs to be made: @KELSEYDOWLING7 please add to Table 4 a row at the bottom for 'All Modules' meaning time from verification to the time they completed the last of the four modules they submitted, regardless of which one was last. And please change Table 4 to days instead of hours.

@brotzmanmj  Sorry! The old table 4/new table5 was being incorrectly masked so it's here now. And yes, that consistency update has also been made.
CCC-Weekly-Module-Metrics_RMD.pdf
If this is good to go I'll post it to the Connect_ALL folder manually for the next two Mondays, since it's a bit late for us to get that into next week's automation, and during the next automation meeting on 3/15 Jake can add this in

Hi @KELSEYDOWLING7 new Table 5 and Table 7 don't have the 'N' column. Can you please add that?
Fine to do it manually for the next two Mondays.

@brotzmanmj  Thank you for pointing that out. Please see the updated report. If this looks good, I can upload it to Connect_ALL. Do you have an existing folder it should go in or should one be created?
CCC-Weekly-Module-Metrics_RMD.pdf

Hi @KELSEYDOWLING7 Thanks for adding that.
In the footnote of Table 9 there are a couple of typos, can you fix those?
And on Table 10 can you put row percents instead of column percents? I think they will be much more informative.
And then it can go on Box in this new folder I just created here for Connect Weekly Survey Status Metrics: https://nih.app.box.com/folder/251929835507

CCC-Weekly-Module-Metrics_RMD.pdf
If this looks good I'll upload there now

Look good, thanks! Ready to upload


Hitting Return in duplicator creates a new item

I'm not sure whether this is desired behaviour or not, but it is different from previous versions so thought I'd mention it.
When adding fields to a section, if I hit return when an input inside the duplicator has focus, a new item is added to the duplicator. In previous versions hitting return would submit the form. This is a regression in my opinion, since it was easy to make a small change, hit return, and have the form submit. One now must tab or scroll down to the submit button.

The add item button now is a real button - this certainly causes the misbehaviour. Not sure how to solve this.

Actually yes this is definitely a bug. If the section name field has focus and I hit enter then the duplicator adds an item! So it doesn't matter whether the duplicator controls have focus or not.

Fixed by adding type="button" to the Add Item <button>. If the explicit type is missing, it seems that Chrome (and others perhaps) will assume it is submit. If you set it to button then the default action for the form will be the first input of type submit (Save Changes).


Add .gitmessage to allow for consistent commit messages

Description

Add a .gitmessage file to the root directory of sir-lancebot to have the same message come up for running the command line git commit command. There are templates that exist and can be modified to match the communities needs. Users will have to configure their .gitconfig (or this can be pushed as well) to use the .gitmessage as the template for their commit messages. The command line command to configure this is:
From the root of sir-lancebot:
git config --local commit.template ./.gitmessage
Users may need to change the relative path to the .gitmessage
Reasoning

This will give the chance for user's commit messages to be more uniform. It is not a guarantee.
Proposed Implementation

Create .gitmessage file and allow users to configure their own .gitconfig
Create .gitmessage file and update .gitconfig with adding these lines:

...
[commit]
  template = ~/.gitmessage
...

Additional Details

Example .gitmessage.txt:
# 50 characters                                 #
# Subject
# (If implemented this commit will ___)

# 72 characters                                                       #
# Problem
# Problem, Task, Reason for Commit
# Solution
# Solution or List of Changes
# Note
# Special instructions, testing steps, rake, etc

# Issue #

View from command line commit:

Would you like to implement this yourself?

[X] I'd like to implement this feature myself
[X] Anyone can implement this feature

That's an interesting idea, I'm not a fan of the structure of the proposed template, but if we have a good one to use, sure, why not. I do like the mention of length limits and what should each paragraph be though.


Feature/#57 max call stack after removing

This fix looks strange to me because I don't know why you add the patternSet after we removed them but this will fix #57 and pass the tests. I found a different issue which is reproducible with and without these changes. If you run npm run bench the bloomrun benchmark will run into a memory leak are you aware of that?
><EMAIL_ADDRESS>bench E:\Repositorys\bloomrun
> node benchmarks/bench2.js

patrun#add x 749,526 ops/sec ±0.83% (90 runs sampled)

<--- Last few GCs --->

[8628:000001E2755DF3C0]    17708 ms: Mark-sweep 1257.3 (1314.0) -> 1256.5 (1282.2) MB, 3720.9 / 0.0 ms  last resort
[8628:000001E2755DF3C0]    21439 ms: Mark-sweep 1256.5 (1282.2) -> 1256.4 (1282.2) MB, 3730.7 / 0.0 ms  last resort

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000003820D629891 <JS Object>
    2: add [E:\Repositorys\bloomrun\bloomrun.js:~27] [pc=000000CE3CFB55F3](this=000001EAF56DC8F1 <a Bloomrun with map 0000027ABE4DF271>,pattern=0000031FBB9C5E61 <an Object with map 0000027ABE4EC109>,payload=00000059FE7F8441 <String[12]: test pattern>)
    3: fn [E:\Repositorys\bloomrun\benchmarks\bench2.js:~13] [pc=000000CE3CFBBCD4](this=000001EAF56EC6A9 <a Benchmark with map 0000027ABE49AE59...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Looks like a memory leak in node > 4  because in node 4 it works.

Closed due to https://github.com/mcollina/bloomrun/pull/60


[OpenCL] Enable OpenCL for GPU tasks

Enable OpenCL support for GPU tests.

This PR enables OpenCL test in CI. For that:

Added USE_OPENCL flag in the build gpu script
Added adreno target in the CI target
Moved relay opencl texture tests in different location to support run them independently. This is necessary due to not all relay tests supports OpenCL CI configuration
Now opencl texture tests working in fp32.

@echuraev I found better solutions to exclude tests, now they are excluded in CI scripts. Please check

@tvm-bot rerun

@tvm-bot rerun

@tvm-bot rerun

cc @masahi @junrushao, it needs a merge trigger!


Sometimes Fails when Ctrl+R is used

NotITG has a quick reset feature that quickly restarts the current song. Under some conditions, the mirin template doesn't play mods properly when that feature is triggered. https://clips.twitch.tv/EntertainingSucculentNigiriPeanutButterJellyTime-Kc8kMCneStSdJBIk
Twitch

I cannot reproduce this issue

Party time, we have deleted screen ready


Add german translation de.json

German translation

No please add de.json😉

No problem, but re-add en.json to your PR.
You deleted it.
You can probably do this command to revert your change:
git checkout custom_components/gardena_smart_system/translations/en.json

And push back your changes ;)

i have closed this one and reopend with https://github.com/py-smart-gardena/hass-gardena-smart-system/pull/8


Cloudflare Pages directs bug reports to location that doesn't exist

Expected Behavior
The Pages known issues page should direct people to a place that actually exists for filing bug reports.
Known Issues
Actual Behavior
The documentation says to post bug reports in the #pages-help channel on discord. This channel either does not exist or is not visible to new members.
Section that requires update
Provide a link to the page that needs an update and be specific about which section requires the update.
Additional information
I discovered this issue while attempting to file a bug report for Pages. If anyone could provide me with the correct place to file a bug report, that would be appreciated.

The discord channel was updated yesterday. It's now named #pages-general
There is a whole Pages category now where you can find the channel most relevant to you.

And that is the correct place for filing bug reports?


feat: support "use" in GRPC requests

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This PR:

supports "use catalog and schema" (behaved like the "use" in MySQL) in GRPC requests
refactor the codes, instead of using the DEFAULT_CATALOG_NAME and DEFAULT_SCHEMA_name consts everywhere, try to use the catalog and schema in query context
use a seperate schema for each sqlness test case

act as tests for this feature, since sqlness is using GRPC to request the database
table names are made short and concise again

make Meta use memory kvstore instead of etcd when running sqlness test for distribute mode
prepare for implementing "use" in distribute mode (tracked in #670 )

Checklist

[ ]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@MichaelScofield There are some conflicts.

@killme2008 resolved, PTAL


Implement Proxmox as supported cloud provider

Since we abandoned Proxmox support, i'm closing this issue.


(python3) upgrade to version 3.5.2 does not work

Here is the debug-log:
PS C:\Users\USERNAME> choco upgrade python3 -debug -y
Chocolatey v0.10.3
Chocolatey is running on Windows v 10.0.14393.0
Command line: "C:\ProgramData\chocolatey\choco.exe" upgrade python3 -debug -y
Received arguments: upgrade python3 -debug -y
The source 'https://chocolatey.org/api/v2/' evaluated to a 'normal' source type

NOTE: Hiding sensitive configuration data! Please double and triple
 check to be sure no sensitive data is shown, especially if copying
 output to a gist for review.
Configuration: CommandName='upgrade'|
CacheLocation='C:\Users\USERNAME\AppData\Local\Temp\chocolatey'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|WebRequestTimeoutSeconds='30'|
Sources='https://chocolatey.org/api/v2/'|SourceType='normal'|
Debug='True'|Verbose='False'|Force='False'|Noop='False'|
HelpRequested='False'|RegularOutput='True'|QuietOutput='False'|
PromptForConfirmation='False'|AcceptLicense='True'|
AllowUnofficialBuild='False'|Input='python3'|AllVersions='False'|
SkipPackageInstallProvider='False'|PackageNames='python3'|
Prerelease='False'|ForceX86='False'|OverrideArguments='False'|
NotSilent='False'|ApplyPackageParametersToDependencies='False'|
ApplyInstallArgumentsToDependencies='False'|IgnoreDependencies='False'|
AllowMultipleVersions='False'|AllowDowngrade='False'|
ForceDependencies='False'|Information.PlatformType='Windows'|
Information.PlatformVersion='10.0.14393.0'|
Information.PlatformName='Windows'|
Information.ChocolateyVersion='<IP_ADDRESS>'|
Information.ChocolateyProductVersion='0.10.3'|
Information.FullName='choco, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=79d02ea9cad655eb'|

Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|
Information.IsLicensedVersion='False'|Information.LicenseType='Foss'|
Features.AutoUninstaller='True'|Features.ChecksumFiles='True'|
Features.AllowEmptyChecksums='False'|
Features.AllowEmptyChecksumsSecure='True'|
Features.FailOnAutoUninstaller='False'|
Features.FailOnStandardError='False'|Features.UsePowerShellHost='True'|
Features.LogEnvironmentValues='False'|Features.VirusCheck='False'|
Features.FailOnInvalidOrMissingLicense='False'|
Features.IgnoreInvalidOptionsSwitches='True'|
Features.UsePackageExitCodes='True'|
Features.UseFipsCompliantChecksums='False'|
Features.ScriptsCheckLastExitCode='False'|
ListCommand.LocalOnly='False'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
ListCommand.Exact='False'|ListCommand.ByIdOnly='False'|
ListCommand.IdStartsWith='False'|ListCommand.OrderByPopularity='False'|
ListCommand.ApprovedOnly='False'|
ListCommand.DownloadCacheAvailable='False'|
ListCommand.NotBroken='False'|UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
NewCommand.AutomaticPackage='False'|
NewCommand.UseOriginalTemplate='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|FeatureCommand.Command='unknown'|
ConfigCommand.Command='unknown'|PinCommand.Command='unknown'|
_ Chocolatey:ChocolateyUpgradeCommand - Normal Run Mode _
Upgrading the following packages:
python3
By upgrading you accept licenses for the packages.

You have python3 v<IP_ADDRESS>61002 installed. Version 3.5.2 is available based on your source(s).
Backing up existing python3 prior to operation.
Capturing package files in 'C:\ProgramData\chocolatey\lib\python3'
python3 not upgraded. An error occurred during installation:
 Updating 'python3 <IP_ADDRESS>61002' to 'python3 3.5.2' failed. Unable to find a version of 'python' that is compatible with 'python3 3.5.2'.
python3 package files upgrade completed. Performing other installation steps.
The upgrade of python3 was NOT successful.
python3 not upgraded. An error occurred during installation:
 Updating 'python3 <IP_ADDRESS>61002' to 'python3 3.5.2' failed. Unable to find a version of 'python' that is compatible with 'python3 3.5.2'.
Attempting rollback

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - python3 (exited 1) - python3 not upgraded. An error occurred during installation:
 Updating 'python3 <IP_ADDRESS>61002' to 'python3 3.5.2' failed. Unable to find a version of 'python' that is compatible with 'python3 3.5.2'.
Exiting with 1

There is another example of this here:
https://chocolatey.org/packages/notepadplusplus#comment-2967581229
@ferventcoder any thoughts on what is going on here?

And another message here:
https://chocolatey.org/packages/mongodb.install#comment-2967592319

Maybe the following upgrade log could also be helpful: python3.zip

Getting the same error when I did a clean install of python

@Dmaisano404 , try cinst python3 until we fix the problem.

@gep13 the notepadplusplus issue and the comment directly below it are why we use exact version dependencies. If I install notepadplusplus 7.0, I expect it to get notepadplusplus.install 7.0 (or perhaps 7.0.0.pkgfixversion). It's really hard to mess up the exact version dependencies and that is why it is preferred over the version ranges - however it is almost never prudent to use minimum version for the meta/.install/.portable packages.
cc @AdmiringWorm @flcdrg @majkinetor

Here's the issue with MongoDB upgrade - https://chocolatey.org/packages/mongodb (note 3.2.9).

If we release python with the proper version, this is fixed :+1:

.@ferventcoder if you use exact version 7.1, wouldn't that prevent installation of dependency with version 7.1.0.pkgfixversion which I believe is the issue regarding the notepadplusplus package?

@AdmiringWorm the issue regarding notepadplusplus is that someone missed they needed to update both notepladplusplus.install and notepadplusplus.
The problem is that you can not just do minimum dependencies when it comes to these kinds of packages.
So the dependency for notepadplusplus should be either:

"notepadplusplus v7.1" - <dependency id="notepadplusplus.install" version="[7.1, 7.2)" />
OR "notepadplusplus v7.1.0.pkgfixversion" - <dependency id="notepadplusplus.install" version=[7.1.0.pkgfixversion]" />

But never: "notepadplusplus v7.1" - <dependency id="notepadplusplus.install" version="7.1" />, because @flcdrg's comment - it will install 7.1 of notepladplusplus, but notepadplusplus.install v8.0 when it comes out - but I wanted 7.1. Also never "notepadplusplus v7.1" - <dependency id="notepadplusplus.install" />,
The exact version dependency easily translates to EVERY package in this format no matter what the versioning scheme. The version range is very subjective based on how the software is versioned, so that same major.minor strategy would not also apply to python:

"python v3.5.2" - <dependency id="python3" version="[3.5.2, 3.5.3)" />
OR "python v3.5.2.pkgfixversion" - <dependency id="python3" version=[3.5.2.pkgfixversion]" />

You can easily start to see why we recommend the exact version dependency. It's not subjective at all, and you get exactly the same version of the meta and the actual, which is what is desired.

The problem here is not the exact version dependency, it's that some packages were missed getting updated in addition to the other packages.

@ferventcoder
thank you for clarifying as well giving such a detailed answer, I can see why you guys recommend the exact version. I don't necessarily agree with it though, but that is just because I'm used to something entirely different on the linux distros I'm using.
May I perhaps suggest, adding the recommendation of exact versioning when it comes to meta packages to Create a chocolatey package documentation?
I remember trying to find out about what was recommended (and why) or not regarding meta packages,
when I was talking to gep and majkinetor on the au channel yesterday.

@AdmiringWorm the issue regarding notepadplusplus is that someone missed they needed to update both notepladplusplus.install and notepadplusplus.

No, that is not the issue. There is NO SOMEONE in this case. Package is virtual and all 3 packages should  get updated in the same AU run. However, one of those packages failed. So your system is good until everything works as expected, but fails with any outliers. And this is the reason the system is bad, its not flexibile.
Contrary, if you specify minimum version:

First time you install something you MAY finish with older version.
Next time you cup virtual package is irrelevant and dependent pacakge will update.

Also, the problem with this approach is that you need to update ALL dependent packages so you are forcing the other pakcage which doesn't need update to be updated.
So, virtual package should be changed along with dependent (or vice-versa) but should use minimum version and that will allow that dependent pacakges can use choco fix notation.

So, to recap, the system where you always update the virtual package with minimum version is better as it allows independant fixes on depndant packages and doesn't suffer from any shortcomings mentioned above.

So, to recap, the system where you always update the virtual package with minimum version is better as it allows independant fixes on dependent packages and doesn't suffer from any shortcomings mentioned above.

@majkinetor Here's the problem. Let's use python as an example.
Say there was python and python.install. Say python v2.7.2 took a minimum version dependency on python.install 2.7.2 (<dependency id="python.install" version="2.7.2" />. Now imagine that there is also Python v3.5.2 packages available. Now when I as a user call choco install python --version 2.7.2, what version of Python will I actually have installed at the end of that?

what version of Python will I actually have installed at the end of that?

To answer my own question, you will have Python 3.5.2 installed on the system at the end of that. It doesn't take a rocket scientist to see how that is completely incorrect. I specified 2.7.2 and got 3.5.2. That is easily thousands of times more wrong than forgetting to update the meta/virtual package, which is just a temporary set back and easily correctable, even if it is less flexible.

the system where you always update the virtual package with minimum version

I'm going to harp on your terminology as it is paramount to the discussion. There are only the two options I specified - exact version dependency or version range dependency. Can we agree that minimum version (e.g. "notepadplusplus v7.1" - <dependency id="notepadplusplus.install" version="7.1" />) is completely incorrect?
Unless you've built a system flexible enough to be able to handle [7.1, 7.2) (notepad++, but later it may be [7.1.0, 7.1.1), etc (following the older versioning scheme - image below)  and [3.5.2, 3.5.3), there really is no discussion on which option you should use. Until you've shown you completely understand how it works and the implications of all scenarios, it is better to not request that it change either.
It must be flexible enough to deal with changing minds about versioning schemes in the same software as well:

Maybe exact version dependencies are a bit inflexible, but they've worked for 5 years and when the small issues that happen every once in awhile are worked out, they will continue to work for the forseeable future.
The one way you could specify the version range dependency is to always specify 3 segments on the right side (the lower than) side unless all four segments were used, then you are back to exact version range dependencies. Then you also suffer the issue of when the software changes the versioning scheme. If it happens the consequences could be more drastic than exact version dependencies.
The only way I see a change is when we introduce package versions. As in notepadplusplus.7.1.p1.nupkg and notepadplusplus.7.1.p2.nupkg (or something like that). This is something we've been talking about and thinking about how to best introduce for nearly five years. Then we won't need package fix version notation, and an exact version dependency would allow for package fixes, which means (you guessed it), the framework automatically allows folks to continue doing what we've been telling them for years with exact version dependencies and it automatically corrects nicely.

Maybe exact version dependencies are a bit inflexible, but they've worked for 5 years and when the small issues that happen every once in awhile are worked out, they will continue to work for the forseeable future.
The one way you could specify the version range dependency is to always specify 3 segments on the right side (the lower than) side unless all four segments were used, then you are back to exact version range dependencies. Then you also suffer the issue of when the software changes the versioning scheme. If it happens the consequences could be more drastic than exact version dependencies.
The only way I see a change is when we introduce package versions. As in notepadplusplus.7.1.p1.nupkg, notepadplusplus.7.1.p2.nupkg, etc (or something like that). This is something we've been talking about and thinking about how to best introduce for nearly five years. Then we won't need package fix version notation, and an exact version dependency would allow for package fixes, which means (you guessed it), the framework automatically allows folks to continue doing what we've been telling them for years with exact version dependencies and it automatically corrects nicely.

The only way I see a change is when we introduce package versions

That would be semantically most correct.

Unless you've built a system flexible enough to be able to handle [7.1, 7.2)

Yeah, I have
function global:au_SearchReplace {
  $vmin = [version]$Latest.Version    #7.1.2
  $vmax = [version]::new($vmin.Major, $vmin.Minor+1)   #7.2
  $dep = "[{0},{1})" -f $vmin, $vmax   # [7.1.2, 7.2)
  $dep = "[{0}, {1})" -f $Latest.Version, ([version]$Latest.Version
  @{
        "$($Latest.PackageName).nuspec" = @{
            "(\<dependency .+?`"$($Latest.PackageName).install`" version=)`"([^`"]+)`"" = "`$1`"$dep`""
        }
    }
 }

Why wouldn't I use above code as general solution and tweak it for special cases. It would work in the case of python and allow for fixes.

It's not correct - if 7.1.2 is released, how would you handle it? Please reread ALL that I wrote first.

Above case is for 7.1.2 release. Give examples when it goes wrong pls.

But I could equaly use build part of the [version]. It would still allow for fix.

The above should not also upgrade to 7.1.3, but it will if that version is released. In other words, what you are suggesting will be incorrect if/when a 7.1.3 release materializes. You still haven't fully grokked what I wrote above.

The one way you could specify the version range dependency is to always specify 3 segments on the right side (the lower than) side unless all four segments were used, then you are back to exact version range dependencies.

That is [7.1.2, <IP_ADDRESS>). I change my earlier statement, the right side would be all four version segments, not three.
You must be thinking about all different scenarios and the implications of them. A very thoughtful foresight must be used if you are going to suggest an alternative. Unfortunately I'm still not seeing that you've thought through that.
I would strongly suggest you stick with exact version dependencies for now.

OK, I pushed an AU virtual python package.
Here is the test:
master~> $au_NoPlugins = $true; .\update_all.ps1 python* -ForcedPackages 'python python3'
FORCED PACKAGES: python python3
Updating 3 automatic packages at 2016-10-29 10:33:24
Push is disabled
   python is updated to <IP_ADDRESS>61029
   python2 has no updates
   python3 is updated to <IP_ADDRESS>61029

So if we do git commit -m '[AU python python3]' --allow-empty at this moment  it should fix this problem.
If anybody has complains let me know
@gep13 @AdmiringWorm @ferventcoder

@majkinetor sounds good to me! 😄

Now, with exact versioning desynchronisation of packages makes them unusable (for either side) which requires effort from maintainers to keep them in sync. Above code for example will probably one day get out of sync as python3 package may fail even if python doesn't (this make happen due to network problems, auto checksum problems etc.)
I was thinking about adding to AU atomic operations on virtual package and its packages:
This is the python:update.ps1
# . $PSScriptRoot\..\python3\update.ps1   <- I DO THIS NOW

function global:au_SearchReplace {
   @{
        "$($Latest.PackageName).nuspec" = @{
            "(\<dependency .+? version=)`"([^`"]+)`"" = "`$1`"$($Latest.Version)`""
        }
    }
}

update -ChecksumFor none -WithDependency    #  <- SHOULD I DO THIS?

So in this  WithDependency scenario AU will look into nuspec deps for python, take the first one, try to run its updater and then update itself only when dependent package updated successfully. Then AU will push both packages or none if any of them failed. Push could still fail on any of them but this still significantlly reduces the probability of failure as it will happen in almost the same moment of time.
This feature would actually be used almost exclusively for virtual packages.
Now, this is only idea and we should probably talk about it if desync starts to happen with above method that separatelly updates and pushes them.

Pushed
Name	Updated	Pushed	RemoteVersion	NuspecVersion
python	True 🔸	True	<IP_ADDRESS>61029	3.5.2
python3	True 🔸	True	<IP_ADDRESS>61029	3.5.2


Move integration jobs to update_containers role

Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/1884
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

Based on my testing https://review.rdoproject.org/zuul/build/e1a38dc6c7e94a26856e535cccd948d4 with https://review.rdoproject.org/r/c/testproject/+/53513 with Depends-on https://github.com/openstack-k8s-operators/ci-framework/pull/1893 and https://github.com/openstack-k8s-operators/ci-framework/pull/1884
https://logserver.rdoproject.org/13/53513/5/check/periodic-podified-multinode-edpm-deployment-antelope-ocp-crc-cs9/e1a38dc/job-output.txt
set_openstack_containers task is skipped
2024-06-19 03:26:46.902922 | controller | TASK [Update OpenStack Services containers Env name=set_openstack_containers] ***
2024-06-19 03:26:46.902931 | controller | Wednesday 19 June 2024  03:26:46 -0400 (0:03:46.823)       0:10:38.604 ********
2024-06-19 03:26:46.902941 | controller | skipping: [localhost]

update_containers task
2024-06-19 03:27:29.069518 | controller | TASK [Update Openstack containers or BM CSV or Ansibleee CSV to update proper image name=update_containers] ***
2024-06-19 03:27:29.069527 | controller | Wednesday 19 June 2024  03:27:29 -0400 (0:00:00.027)       0:11:20.750 ********
2024-06-19 03:27:29.069538 | controller |
2024-06-19 03:27:29.696261 | controller | TASK [update_containers : Destination directory exists state=directory, recurse=True, path={{ cifmw_update_containers_dest_path | dirname }}] ***
2024-06-19 03:27:29.696304 | controller | Wednesday 19 June 2024  03:27:29 -0400 (0:00:00.037)       0:11:20.788 ********
2024-06-19 03:27:29.696317 | controller | ok: [localhost]
2024-06-19 03:27:30.077967 | controller |
2024-06-19 03:27:30.077999 | controller | TASK [update_containers : Generate update containers yaml file src=update_containers.j2, dest={{ cifmw_update_containers_dest_path }}] ***
2024-06-19 03:27:30.078008 | controller | Wednesday 19 June 2024  03:27:29 -0400 (0:00:00.626)       0:11:21.415 ********
2024-06-19 03:27:30.078019 | controller | changed: [localhost]
2024-06-19 03:27:30.651767 | controller |
2024-06-19 03:27:30.651802 | controller | TASK [update_containers : Update the containers _raw_params=oc apply -f {{ cifmw_update_containers_dest_path }}] ***
2024-06-19 03:27:30.651811 | controller | Wednesday 19 June 2024  03:27:30 -0400 (0:00:00.381)       0:11:21.796 ********
2024-06-19 03:27:30.651822 | controller | changed: [localhost]

and correct containers in use.
https://logserver.rdoproject.org/13/53513/5/check/periodic-podified-multinode-edpm-deployment-antelope-ocp-crc-cs9/e1a38dc/controller/ci-framework-data/logs/openstack-k8s-operators-openstack-must-gather/namespaces/openstack/pods/barbican-worker-worker-7f8bccc74d-vz67l-describe
Image:         quay.rdoproject.org/podified-antelope-centos9/openstack-barbican-worker:4e9e53a3c419c62adc46f89756c4e6f6
    Image ID:      quay.rdoproject.org/podified-antelope-centos9/openstack-barbican-worker@sha256:28282ff2a13ebc14a97f70bc5f695c5f5ac760ea98bb4013e571739238c311f3

openstack version cr file: https://logserver.rdoproject.org/13/53513/5/check/periodic-podified-multinode-edpm-deployment-antelope-ocp-crc-cs9/e1a38dc/controller/ci-framework-data/logs/openstack-k8s-operators-openstack-must-gather/namespaces/openstack/crs/openstackversions.core.openstack.org/openstack-galera-network-isolation.yaml

/lgtm

/approve


Select all inside HTML tags

Example:

Link1

Link2

Is it possible to configure the plugin to act in the following way?:

when the caret is on Link1, expanding goes in the following way:
Link1 > a > li > both li (ul inner) > ul (including ul tags)
when the caret is between the ul and li tags (for example:
|
, the selection is expanded to the ul content, that being the 2 li elements.

The reason is that i often need to add another container for some elements, and I can do this easily in ST3's Expand Region in combination with emmet.

Yes, that would be very nice to have!

Please add another stop for html attribute (rel="stylesheet"):
<link rel="stylesheet" type="text/css" href="assets/css/style.css">

+1

1

+1

+1

+1

+1

+1

Please try it!
emmet package is required.
~/.atom/config.cson
'.text.html':
  'expand-region':
    commands: [
      {
        command: 'editor:select-word'
        recursive: false
      }
      {
        command: 'emmet:balance-outward'
        recursive: true
      }
      {
        command: 'expand-region:select-inside-single-quotes'
        recursive: false
      }
      {
        command: 'expand-region:select-around-single-quotes'
        recursive: false
      }
      {
        command: 'expand-region:select-inside-double-quotes'
        recursive: false
      }
      {
        command: 'expand-region:select-around-double-quotes'
        recursive: false
      }
      {
        command: 'expand-region:select-inside-angle-brackets'
        recursive: false
      }
      {
        command: 'expand-region:select-around-angle-brackets'
        recursive: false
      }
    ]


Video extends DisplayObject

I'm getting these errors in javascript, when clicking on videos:
Uncaught TypeError: target.get_tabEnabled is not a function(…)
I guess the solution would be to have Video extend InteractiveObject, at least for:
#if js

Video behaves similar to Bitmap, if we are looking for a hit test, it's supposed to help trigger the hit test (you hit an object!) but the target should be the parent interactive object (usually a sprite). I copied code from Bitmap and the error went away for me :smile:

Thanks


[Error - Specific YouTube Video, Letterbox issue?] Format either not reporting right or not downloading right

Video in question: https://www.youtube.com/watch?v=rI9tpK9S28g
When running
youtube-dl -F https://www.youtube.com/watch?v=rI9tpK9S28g
It shows the "best" option as -f 22 720p.
When trying to download that format with
youtube-dl -f 22 https://www.youtube.com/watch?v=rI9tpK9S28g
I end up with a 1280x542 file.  I'm not sure if this is just improper reporting of the resolutions from YouTube, because there is actually a 1080p option in the YouTube player, but it doesn't show up as an option in youtube-dl.
The video is letterboxed on YouTube but not when it is downloaded with the above command so I'm not sure if that has anything to do with it.
Thanks for any insights!

These resolutions are reported by YouTube.
1080p does show up in youtube-dl:
248          webm       1920x814   DASH video 2226k , vp9, 24fps, video only, 12.77MiB
137          mp4        1920x814   DASH video 3621k , avc1.640028, 24fps, video only, 23.36MiB

To download best available quality you don't need to specify any format. You must have ffmpeg/avconv installed though.

I know I don't need to specify, and I do have ffmpeg installed.  If you try to download that video the letterboxing goes away.  Is this something I can work around somehow?

When running
youtube-dl -F https://www.youtube.com/watch?v=rI9tpK9S28g
It shows the "best" option as -f 22 720p.

When trying to download that format with
youtube-dl -f 22 https://www.youtube.com/watch?v=rI9tpK9S28g
I end up with a 1280x542 file.
it will be fixed in the next version:
python2 __main__.py -F https://www.youtube.com/watch?v=rI9tpK9S28g
[youtube] rI9tpK9S28g: Downloading webpage
[youtube] rI9tpK9S28g: Downloading video info webpage
[youtube] rI9tpK9S28g: Extracting video information
WARNING: video doesn't have subtitles
[youtube] rI9tpK9S28g: Downloading MPD manifest
[info] Available formats for rI9tpK9S28g:
format code  extension  resolution note
249          webm       audio only DASH audio   51k , opus @ 50k, 464.68KiB
250          webm       audio only DASH audio   68k , opus @ 70k, 589.49KiB
171          webm       audio only DASH audio  124k , vorbis@128k (44100Hz), 1.10MiB
140          m4a        audio only DASH audio  128k , m4a_dash container, mp4a.40.2@128k (44100Hz), 1.16MiB
251          webm       audio only DASH audio  139k , opus @160k, 1.15MiB
278          webm       256x108    DASH video   78k , webm container, vp9, 12fps, video only, 636.87KiB
160          mp4        256x108    DASH video  110k , avc1.42c00c, 12fps, video only, 997.13KiB
242          webm       426x180    DASH video  226k , vp9, 24fps, video only, 1.36MiB
133          mp4        426x180    DASH video  247k , avc1.4d400d, 24fps, video only, 2.19MiB
243          webm       640x272    DASH video  410k , vp9, 24fps, video only, 2.31MiB
134          mp4        640x272    DASH video  571k , avc1.4d4015, 24fps, video only, 2.99MiB
244          webm       854x362    DASH video  722k , vp9, 24fps, video only, 3.79MiB
135          mp4        854x362    DASH video 1101k , avc1.4d401e, 24fps, video only, 6.15MiB
247          webm       1280x542   DASH video 1275k , vp9, 24fps, video only, 6.88MiB
136          mp4        1280x542   DASH video 1961k , avc1.4d401f, 24fps, video only, 11.91MiB
248          webm       1920x814   DASH video 2226k , vp9, 24fps, video only, 12.77MiB
137          mp4        1920x814   DASH video 3621k , avc1.640028, 24fps, video only, 23.36MiB
36           3gp        320x136    small , mp4v.20.3,  mp4a.40.2
17           3gp        176x144    small , mp4v.20.3,  mp4a.40.2@ 24k
5            flv        426x180    small , h263, mp3  @ 64k
18           mp4        640x272    medium , avc1.42001E,  mp4a.40.2@ 96k
43           webm       640x360    medium , vp8.0,  vorbis@128k
22           mp4        1280x542   hd720 , avc1.64001F,  mp4a.40.2@192k (best)

Letterboxing is most likely implemented by means of the YouTube player. If none of the formats provides a letterboxed video there is no way do so then.

it will be fixed in the next version

By fixed it seems you are referring to the reporting of the resolution?

If none of the formats provides a letterboxed video there is no way do so then.

Understood - perhaps I can do this with ffmpeg post-download, I'll look into that.
Thank you both!

By fixed it seems you are referring to the reporting of the resolution?

yes


Ghoul Retainer

text: Ammo cards are not playable on Guns when used by Ghoul Retainer
link: https://www.vekn.net/forum/rules-questions/80412-can-ghoul-retainer-use-ammo#107745

Duplicate #675


Scrape failed to capture video from Facebook post

Hello MediaVault,
We archived this Facebook post containing a deepfake video. But we found that the archived file didn't include the video. Would you mind helping us to figure it out?
Here is the original link: https://www.facebook.com/100089812680688/videos/2360570097610510/
Thank you.
Artika - Cek Fakta Tempo, Indonesia
<EMAIL_ADDRESS>==
Erica verified issue on 11/22
Same result for this link:
https://www.facebook.com/100089812680688/videos/2360570097610510/
No video saved:
https://mvau.lt/media/1e09596a-c2e7-4ebf-991b-355845160a26

Another example:
Dear Erica and team,
We found that this case also happened to similar links. Here the archive link doesn't show the video too.
https://mvau.lt/media/131d337a-5bfc-4ea9-a8c2-2f4cf1746821
Please let me know how to solve this. Thank you so much.
//Art

Similar issue reported by AFP:
Stephanie YOUSSEF<EMAIL_ADDRESS>We also faced another issue with Facebook reels, vault is archiving the captions but not the videos themselves. (screenshot and link below)
Vault link: https://mvau.lt/media/b388211a-8a7b-4c85-b17c-9822ced76ec1


Create mybac.txt

This adds Botswana Accountancy College mybac.ac.bw students email domain to the repository

@the-mastermind Could you please provide us with:

the university official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students.

Good day Philip
xxxxx-xxx<EMAIL_ADDRESS>is the email format for Botswana Accountancy College students, staff’s email address format is xxxxxxxx<EMAIL_ADDRESS>and the staff email domain has already been added, we are therefore trying to add students emails.
Students can only use this email when they are still studying, after their final year students’ domain user account get disabled together with the email.
The URL for the official website of the college is www.bac.ac.bwhttp://www.bac.ac.bw/
School of Computing and information Systems offers several four year degree courses in which students are taught programming and database administration
This is a link to one of our four year degree - Computer Systems Engineering in which we have partnered with University of Sunderland, UK.
http://www.bac.ac.bw/bsc-hons-computer-systems-engineering
This is a link to another of our four year degree - Mobile Technologies
http://www.bac.ac.bw/bsc-hons-mobile-technologies
To verify that mybac.ac.bw domain is owned by bac.ac.bw please visit https://www.whois.net and enter www.mybac.ac.bwhttp://www.mybac.ac.bw, the registrant name and email are the same for both bac.ac.bw and mybac.ac.bw, Please don’t hesitate to contact the gentleman in the given contact numbers to verify the information above, he is the college network administrator.
Regards
Sylvester Mokgwe
School of Computing and Information Systems
Botswana Accountancy College
Private Bag 00319
Gaborone Botswana
Tel: (+267)3953062  Ext: 1626
Email: sylvesterm<EMAIL_ADDRESS>From my Mac Book Pro i7
On 15 Mar 2017, at 1:53 PM, Philip Torchinsky <notifications<EMAIL_ADDRESS>wrote:
@the-mastermindhttps://github.com/the-mastermind Could you please provide us with:

the university official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/2834#issuecomment-286719969, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADCzhpXMoOEEk78nhvbt2AnQKBbwRAMWks5rl9EqgaJpZM4McjTh.

Good day Philip
You can also find information explaining to students on how to access their mybac.ac.bw email in Botswana Accountancy College website at this page http://www.bac.ac.bw/ict-services
Regards
Sylvester Mokgwe
School of Computing and Information Systems
Botswana Accountancy College
Private Bag 00319
Gaborone Botswana
Tel: (+267)3953062  Ext: 1626
Email: sylvesterm<EMAIL_ADDRESS>From my Mac Book Pro i7
On 16 Mar 2017, at 8:41 PM, Sylvester Mokgwe <sylvesterm<EMAIL_ADDRESS>wrote:
Good day Philip
xxxxx-xxx<EMAIL_ADDRESS>is the email format for Botswana Accountancy College students, staff’s email address format is xxxxxxxx<EMAIL_ADDRESS>and the staff email domain has already been added, we are therefore trying to add students emails.
Students can only use this email when they are still studying, after their final year students’ domain user account get disabled together with the email.
The URL for the official website of the college is www.bac.ac.bwhttp://www.bac.ac.bw/
School of Computing and information Systems offers several four year degree courses in which students are taught programming and database administration
This is a link to one of our four year degree - Computer Systems Engineering in which we have partnered with University of Sunderland, UK.
http://www.bac.ac.bw/bsc-hons-computer-systems-engineering
This is a link to another of our four year degree - Mobile Technologies
http://www.bac.ac.bw/bsc-hons-mobile-technologies
To verify that mybac.ac.bw domain is owned by bac.ac.bw please visit https://www.whois.nethttps://www.whois.net/ and enter www.mybac.ac.bwhttp://www.mybac.ac.bw/, the registrant name and email are the same for both bac.ac.bw and mybac.ac.bw, Please don’t hesitate to contact the gentleman in the given contact numbers to verify the information above, he is the college network administrator.
Regards
Sylvester Mokgwe
School of Computing and Information Systems
Botswana Accountancy College
Private Bag 00319
Gaborone Botswana
Tel: (+267)3953062  Ext: 1626
Email: sylvesterm<EMAIL_ADDRESS>From my Mac Book Pro i7
On 15 Mar 2017, at 1:53 PM, Philip Torchinsky <notifications<EMAIL_ADDRESS>wrote:
@the-mastermindhttps://github.com/the-mastermind Could you please provide us with:

the university official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/2834#issuecomment-286719969, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADCzhpXMoOEEk78nhvbt2AnQKBbwRAMWks5rl9EqgaJpZM4McjTh.

@the-mastermind Thank you very much for the detailed clarification! Pull request is now merged.

Much appreciated Phillip
Regards
Sylvester Mokgwe
School of Computing and Information Systems
Botswana Accountancy College
Private Bag 00319
Gaborone Botswana
Tel: (+267)3953062  Ext: 1626
Email: sylvesterm<EMAIL_ADDRESS>From my Mac Book Pro i7
On 17 Mar 2017, at 5:17 PM, Philip Torchinsky <notifications<EMAIL_ADDRESS>wrote:
@the-mastermindhttps://github.com/the-mastermind Thank you very much for the detailed clarification! Pull request is now merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/2834#issuecomment-287382751, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADCzhoWTkKoLDc0q2D2oRyEtyi3yrcIEks5rmqPygaJpZM4McjTh.


Override the default highlight style on a per-note basis using a note's frontmatter (properties)

This feature was implemented in commit 3c5f47c.


🗺 Vehicle spawns

Some of the vehicle's spawn inside mapping in sfpd vehicle's spawn location need to be fixed.

With mapping removed, all vehicle spawn points were reset.


[FLINK-8139][table] Check for proper equals() and hashCode() when reg…

https://issues.apache.org/jira/browse/FLINK-8139
Check for proper equals() and hashCode() when registering a table.
Contribution Checklist
Verifying this change
flink-table unit tests passed.

Hi @Aegeaner, thanks for the pull request.
I had a brief look at it and noticed a few things:

Please fill out the PR template (see #5063 as an example)
Please add unit tests that validate that the checks you added are working correctly.
Please update the equals() and hashCode() methods of Row as mentioned in the JIRA issue.

Thank you, Fabian

Hi @fhueske , thanks for review.
I will updateequals()and hashcode() methods of Row, but I also noticed that in JoinOperator and KeySelector, they used RowComparator to compare row elements.
For the unit test, I noticed in TypeInformationTestBase there is a testHashcodeAndEquals method already, I will complete this test to add test case with type info without implementing its own hashcode  and equals method.

@fhueske I found TypeInformation class has abstract equals() and hashcode()  override methods defined, so any type info must implement these methods. So is reflection check necessary?

@Aegeaner equals and hashCode in TypeInformation are meant for comparing type information and not instances of values with this type. The RowComparator internally uses hashCode and equals of the objects as well.

@twalthr But when registering a table/TableSource, we only got a TableSchema, which is an array of TypeInformation ? How should I check the instances of values?

Hmm, I agree with @twalthr. Adding these checks when a DataSet/DataStream is imported would prevent valid queries (e.g., those that to simple transformations). I would not add a config switch to disable the global checks. Adding the checks to the operators that require properly implemented equals() and hashCode() methods sounds like a better approach.
We should also add to the documentation that all objects that are processed by the Table API / SQL should have equals and hashCode properly implemented.


Use of unstable rust syntax (let...else)

description
When building on NixOs  cargo throw many errors like:
error[E0658]: `let...else` statements are unstable

From what I saw, all of the let ... else are used in a form:
let Some(val) = option else { return Err(atspi_error); };

proposed solution.
Prefer to use a stable syntax which in the case of Option translation is probably better and not more verbose.
The let ... else syntax is provided for cases you expect one variant of an enum and do something else or return a default value. But preferably for enums with more than two variants.
Moreover, if it's the only reason we need unstable rust channel, it's better to use the stable syntax:
let val = option.ok_or(atspi_error)?;

Other solutions
add the #![feature(let_else)] in the top lib.rs file.
Anyway as explained above, it's better to avoid using this unstable feature if it's the only case where it's needed and if it's the only unstable feature we need.
Environment.
NixOS 22.11
rustc 1.64.0

We always use the latest stable Rust, which is currently 1.67.1. This syntax landed in Rust 1.65.
We will update our minimum rust version in Cargo.toml to reflect this.

Ok, I thought it was not already stabilized.
The 1.65 is probably a good MSRV. I was not expecting NixOS stick on that old version of rust.

Anyway I personaly prefer the ok_or syntax for options ;) but it's only personal feeling

In the end it may be a matter of taste but maybe I can convince you ( a little bit ).
In our example we use it to see whether this is the event we seek, otherwise continue to the next event in stream:
	while let Some(Ok(ev)) = events.next().await {
		let Ok(change)  = StateChangedEvent::try_from(ev) else { continue };

		if change.kind() == "focused" && change.enabled() == 1 {
			let Some(bus_name) = change.inner().sender()? else { continue };
			println!("Accessible belonging to {bus_name}  focused!");
		}
	}

Here it is unambiguous what the pattern, the assignment and the control flow is in case do not match the Ok(change) pattern - all in one go.
That being said, I will also keep an eye open for instances where ok_or would be more suitable alternative, however I doubt we will lose let-else completely.
Thanks !


Fastify and Mongodb - JS choice

Thanks for your pull-request!
Several comments :

The project should follow the JavaScript Standard Style.

There will be only TypeScript templates.

I'm adding the js template, because this project I think it should be wider. I'll add the ts version early.

Waiting forward for your TypeScript version! 👍

Avoid hard-coded value, I see you use environments variable that's cool but seems like you don't for the database url : 'mongodb://localhost:27017/simple-shop-api.

If you use dotenv you should commit  .env.example file so we can see what environments variables need to be set, also you should commit the .gitignore file for this specific README.md.

Avoid unecessary comment like theses one :

// Here you can use middleware(s)
//password
//username

You should respect the Model, routes, controller pattern, I don't know what is handlers.js.
Avoid using npm deprecated package like boom.

Looking forward for your improvments, thank you again.

Thanks, I'll work on the rest of features.


Support hpxrx

This PR adds the following things which have proven to be useful while implementing HPXrx:

Allow for executables which are compiled by including hpx_main.hpp to add configuration customizations
Adding names to schedulers to support debugging
Adding scheduler_specific_ptr
Renaming generic_thread_pool_executor  to current_executor

This PR also includes the changes to the resource manager contributed by @nidhimj22 during her GSoC work (those are needed for HPXrx).

@sithhell All of your comments have been addressed.

Thanks!


pri doesn't complete to println!

I'm rather new to Rust, so not sure if this is an actual issue with racer, but from my limited experience I'd expect the result of
RUST_SRC_PATH=~/.multirust/toolchains/stable/src ./racer complete pri

to include stuff like println!. Instead, I'm getting no results at all. For completeness, the example in de docs works correctly:
RUST_SRC_PATH=~/.multirust/toolchains/stable/src ./racer complete std::io::B
MATCH BufReader,33,11,/home/erwin/.multirust/toolchains/stable/src/libstd/io/buffered.rs,Struct,pub struct BufReader<R> {
MATCH BufWriter,179,11,/home/erwin/.multirust/toolchains/stable/src/libstd/io/buffered.rs,Struct,pub struct BufWriter<W: Write> {
MATCH BufStream,442,11,/home/erwin/.multirust/toolchains/stable/src/libstd/io/buffered.rs,Struct,pub struct BufStream<S: Write> {
MATCH BufRead,516,10,/home/erwin/.multirust/toolchains/stable/src/libstd/io/mod.rs,Trait,pub trait BufRead: Read {
MATCH Broadcast,628,11,/home/erwin/.multirust/toolchains/stable/src/libstd/io/mod.rs,Struct,pub struct Broadcast<T, U> {
MATCH Bytes,746,11,/home/erwin/.multirust/toolchains/stable/src/libstd/io/mod.rs,Struct,pub struct Bytes<R> {

I've searched through the issues and this seems related to #45, but that was marked as solved.

Hi @ErwinJunge, I'm afraid Racer doesn't support completion of macros yet, sorry.

Then why to close the issue? Isn't it better to leave it open and label as an enhancement? I'm interested in Rust but without a proper completion it's a pain to write anything complex enough. I'd rather look into suggestions than search the documentation and sources (which is the last resort for me).


Create environment manager in dpdkinfra and move current interface code there

Instead of a Environment Mngr I implemented a portmngr and pipemngr.


🐞 - The tuiDropdownMinHeight property in the tui-hosted-dropdown component does not work.

Playground Link
https://stackblitz.com/edit/angular-jawb27?file=src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.less
Description
The 'tuiDropdownMinHeight' property has no effect on the minimum height of the 'tui-hosted-dropdown' component.
Angular version
12.2.13
Taiga UI version
3.25.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

tuiDropdownMinHeight is not about minimum height of the dropdown like CSS min-height. It means the minimum size down to which dropdown will shrink as it approaches the edge of the screen before it jumps to the other side. Say you have a select and a dropdown of 500px and you set [tuiDropdownMinHeight]="200". You scroll page up and now dropdown hits the bottom of the screen. It would start to shrink and scrollbar will appear. Once its height is below 200px it would jump up and be shown above the select at its full height of 500px again. If you just want to make sure your dropdown has at least X px in height — wrap your content with some DIV and set its min-height with CSS.

tuiDropdownMinHeight is not about minimum height of the dropdown like CSS min-height. It means the minimum size down to which dropdown will shrink as it approaches the edge of the screen before it jumps to the other side. Say you have a select and a dropdown of 500px and you set [tuiDropdownMinHeight]="200". You scroll page up and now dropdown hits the bottom of the screen. It would start to shrink and scrollbar will appear. Once its height is below 200px it would jump up and be shown above the select at its full height of 500px again. If you just want to make sure your dropdown has at least X px in height — wrap your content with some DIV and set its min-height with CSS.

I wrapped the dropdown content and set min-height, but the dropdown still has its own max-height.
Example: https://stackblitz.com/edit/angular-jawb27-uxvvd6?file=src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.less


[Locale Modale]: Web Components - VO - Focus trapping not working in mobile

Description
Focus trapping is not working for the locale modal in mobile.
One thing to try is to change the sentinel nodes to button elements instead of anchor elements as done in: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/8074. This would have to be done in the carbon-web-components modal component as locale modal is extending that.
https://user-images.githubusercontent.com/54281166/150870389-0e73f33a-66dc-4045-9021-2c20f3c6b98e.mov
Component(s) impacted
Locale Modal
Browser
Safari
Carbon for IBM.com version
1.30.0-rc.1
Severity
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Application/website
https://www.ibm.com/standards/carbon/web-components/?path=/story/components-locale-modal--default
Package
@carbon/ibmdotcom-web-components
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

@annawen1 is this ticket needed for the same sprint as #8086?

@andy-blum nope, this ticket is being treated separately! This one isn't going into this upcoming release so we can schedule this in for the next sprint.

Additional accessibility concerns regarding the locale modal:
DDSRegionItem components are rendering links instead of buttons

- This is semantically wrong as clicking this item _does something_ rather than _goes somewhere_.
- This has the unfortunate side effect in iOS voiceover of also never getting focused when VO reads the text, leading to disabled options getting read out but not being clickable. Rendering these as buttons would allow us to use the native `disabled` attribute on the button, preventing VO from ever reading it
The focus trap doesn't navigate the same forwards as it does backwards

Cycling the elements forwards and backwards should include all items, currently cycling forwards does not include the close button, which could lead visually imparied users to assume there is no close button.
This is coming from the way we're collecting all focusable elements and always putting elements in the shadowRoot behind lightDOM children
DDSLocaleSearch has some problems of its own

On ios, the first focused item is the first item in the list. Cycling focus forward may lead users to think they have to navigate the entire list to get down to the bottom of the list. Ideally, the item getting focus would be the modal, allowing users to navigate forward through the close button, title, and search bar before getting to the list
The search updates the list as users type, but that isn't communicated to the screen reader. As a user types in their search term, VO reads back the individual letter and if a pause is detected, will announce the entire word(s). But we should also communicate to users that the list of items has changed and how many options are there now with an aria-live="polite" region.

@andy-blum Since you already looked into this issue. Do you want to grab this one?


agda-mode supresses implicit markdown support from vscode

When the agda-mode extension is enabled, syntax highlighting and the "Open Preview" option (Ctrl+Shift+V) stop working for .lagda.md files.

Which Markdown extension are you using? 👀

I'm not using any Markdown extension.
This is how VS Code behaves when agda-mode is disabled:

It has syntax highlighting and the "Open Preview" option for .lagda.md files.
And this is how it behaves when agda-mode is enabled:

The syntax highlighting stops working and "Open Preview" option is not available anymore.


234 feature change readme install instructions

Description

[ ] updated requirements to be used directly in PyCharm or conda
[ ] updated Readme
[ ] Note: approximate package requirements (~=) are not recognized by Conda
[ ] Note for Readme: one may need to manually specify the CUDA_HOME variable for native (to the package folder .../cudatoolkit_* containing /bin/nvcc)

closes #234
Checklist

[x] This pull request is associated to an issue
[x] This PR contains a description
[ ] Add someone else as reviewer and wait for approval before merging.

my best bet for installation:
git clone https://github.com/lettucecfd/lettuce.git lettuce
cd lettuce
conda create -n lettuce
conda activate lettuce
conda install --yes --file requirements.txt
python setup.py develop
lettuce convergence
pytest tests

for now:
git clone https://github.com/lettucecfd/lettuce.git lettucetest
cd lettucetest
git fetch origin
git checkout 234-feature-change-readme-install-instructions
conda create -n lettucetest
conda activate lettucetest
conda install --yes --file requirements.txt
python setup.py develop
lettuce convergence
pytest tests

@McBs

[ ] do we need exact restricitons for packaging, click and setuptools?
[ ] can you check if the instructions above or, ideally, in the new readme work for you?

@McBs
* [x]  do we need exact restricitons for `packaging`, `click` and `setuptools`?

* [x]  can you check if the instructions above or, ideally, in the new readme work for you?

Hi @PhiSpel
the instructions work on my workstation :-)


ActiveSupport to_datetime for DateTime conversion

Fixes #1162.
This pull introduces/changes:

ActiveAttr used to_datetime for DateTime conversion; changing to strptime broke conversion of string values from form inputs. Going back to to_datetime fixes this.

Pings:
@cheerfulstoic
@subvertallchris

This is great! I'll merge and do a patch release when I have a few minutes unless Brian gets to it sooner.

:+1: nice! just ran into this issue too

Awesome, thanks!  Released as 7.0.1


feat: create scanner template sample

Sample template for custom scanner.

This code should compile, but doesn't. Eraser is pinned at v0.5.0, but v0.5.0 doesn't have the pkg/scanners/template package

yup we need to wait until v1.1.0, I'll update the module when that is released


support for text alignment in legend box; + support for colored legend box (face and edge)

I wrote some lines for supporting the proper alignment in the legend box (Since the default value is centered...). And a bit for coloured boxes

Apparently untested. :) The PR contains syntax errors.

Hmm. Not this very version.
My code is from mid-december and I was quite sure that it is working. But I see also the syntax error. Sorry.

So now it's been tested :)

This PR changes the appearance of one test output, but it looks okay comparing with the original matplotlib output. Can you update the phash in the legends test to fdfc810e97810e2b?

Sure. But not before monday.
Good to know this travis ci stuff.
I guess it's likely that legends2.py changes its hash too

Updated. Unfortunately now there are some code style suggestions. Should I fix that?

Don't worry about it, the styles will fix themselves later on.


use crawlera error

http://proxy.crawlera.com:8010?noconnect (user:

@ichenfujun , can you provide more information on the error?

INFO:Using crawlera at http://proxy.crawlera.com:8010?noconnect (user: fe84844...)     only this line
my settings.py:
DOWNLOADER_MIDDLEWARES = {
'scrapy_crawlera.CrawleraMiddleware': 300,
}
50 CRAWLERA_ENABLED = True
51 CRAWLERA_APIKEY = 'fe8484409712441f84442c14cbcdc3f9'

@ichenfujun , what kind of error are you having? is it a python error? or some error code from Crawlera?
It may be more suited for Crawlera support, not scrapy-crawlera middleware.
Feel free to reopen the issue with more details.


Added migration create command for creating empty migration classes

Fixes https://github.com/propelorm/Propel2/issues/832
For semantic reasons, I chose to implement it as a separate command instead of an "--empty" command to migration:diff.

Note: The travis builds are failing because of other reasons than this PR. Actually, accepting https://github.com/propelorm/Propel2/pull/1056 results in green travis builds again.

Very cool, thanks! We should also add this to PropelBundle: https://github.com/propelorm/PropelBundle/issues/372


Code Review: Add support for slices in SketchAPI (#16184)

Fix #150
Fix BohemianCoding/Sketch#16184

Warnings

:warning:

Source/dom/WrappedObject.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/SharedStyle.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/BorderOptions.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Color.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Gradient.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Selection.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Style.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/utils.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/wrapNativeObject.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/ui/UI.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/Page.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Library.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/StyledLayer.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/models/ImageData.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Document.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Flow.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Flow.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Document.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/ImageData.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/SymbolMaster.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/Library.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/SymbolInstance.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/models/SharedStyle.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/StyledLayer.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/BorderOptions.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/Page.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Color.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/Image.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Gradient.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/HotSpot.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/GradientStop.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/layers/Group.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/dom/style/Style.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/enums.js changed, but not its tests. That's OK as long as you're refactoring.

:warning:

Source/ui/UI.js changed, but not its doc. That's OK as long as you're refactoring.

:warning:

Source/dom/style/GradientStop.js changed, but not its tests. That's OK as long as you're refactoring.

  Generated by :no_entry_sign: dangerJS


[Bug]: Collection.delete() is typed to return none but returns a list of uuids

What happened?
Collection.delete() is typed to return none but returns a list of uuids
We should align the behavior to the type signature.
Versions
Chroma v0.3.22
Relevant log output
None

Solved in #360


Add a auto-reply for people that ask for help/if someone knows xyz

I see a lot of people join the server and go to #python-general and not #how-to-get-help and instead of just asking the question they ask people if they are familiar with xyz module or can anyone help me?
I propose we add a auto-reply to redirect the person to either ask the question directly or to read the #how-to-get-help. (ghost ping them inside #how-to-get-help) then delete there original message on general and the bot message.

It was mentioned in #community-meta that it seems very difficult to detect these cases. Also, other suggestions involving deleting people's messages have been rejected since it's quite confusing and means the person will lose their message content.

Closing as I don't think this is feasible or something we really want.


Add a tooltip to explain what marking a preset as "runnable" does

It may be confusing at first, so this helps clarify what "runnable" presets are for.

Thanks!

Cherry-picked for 3.1.2.


allow to configure client plaintext connection

hello! thanks for very useful argo extention!
Please consider following change:
allow to configure client plaintext connection, when applicationset-progressive-sync is running in the same cluster with argocd this will allow to use argocd svc as address ARGOCD_SERVER_ADDR=argocd-server:80

Hey @riuvshyn, thanks for the contribution. I will fix the build process in the next couple of days so we will see all green on this PR and then we can merge it.

Hey @riuvshyn , once https://github.com/Skyscanner/applicationset-progressive-sync/pull/149 it's merged you should be able to:

rebase
bump the helm chart to fix the chart test failing

and then we can merge this


Update appimage runtime to the static runtime to remove libfuse2 dependency

Hello, I've noticed that the appimages being made with nix-appimage still use the old dynamic runtime that has a libfuse2 dependency.
The appimage folks actually now have the static runtime here: https://github.com/AppImage/type2-runtime/releases
All the runtimes in the pre-releases are the static runtime, while the runtimes in the last stable release only the ones marked fuse3 are static.
Those runtimes don't have libfuse2 dependency and work on musl systems as well, they are also being used as the default runtime in go-appimage and appimagetool

Ah nice, that seems much more maintained than the one currently in use. It also seems like I can upgrade the AppImageCrafters runtime to use libfuse3 by making squashfuse use fuse3 instead of fuse.
Can you explain what the benefit of using fuse3 over libfuse2 is?

Can you explain what the benefit of using fuse3 over libfuse2 is?

libfuse2 is an EOL library, it is no longer pre-installed in distros.

Also see:

https://github.com/NixOS/nixpkgs/pull/340410

Thanks for fixing the issue.

Also see:
* [squashfuse: Use fuse3 instead of fuse NixOS/nixpkgs#340410](https://github.com/NixOS/nixpkgs/pull/340410)

squashfsfuse in this case would be used to make the squashfs image right? In that case I don't think it is a big deal if you use fuse or fuse3 to make it but I'm not very sure. As far as I know what matters is the runtime itself and not how the squashfs image is made.
You might want to consider using appimagetool to creates the squashfs image, since it supports multiple multiple arguments like the PR you have open is doing, example.
Although it might not work on nix.

squashfuse is the library that both runtimes use to mount the bundled data when you run the appimage, you're probably thinking of squashfsTools.

I use nix-appimage to run my nix packaged applications (nixvim, etc.) on compute cluster on which I don't have root access. I was not able to run my appimages on some servers, where fuse3 is not installed and had to change the runtime to use fuse2. I am not very familiar with appimages or what would be the right way to address this issue, I just want to make you aware that this might be a problem for some users / use-cases.

Hi, do you have this issue with the appimages of cemu, zen-browser, duckstation and pcsx2? Those use the static runtime as well and only need a fusermount or fusermount3 binary on the system.

Those work for me. At least they launch before they complain about missing libGLX.so.

Those work for me. At least they launch before they complain about missing libGLX.so.

Can you try extracting the nix appimages that have the issue --appimage-extract and then using either go-appimage or appimagetool turn the squashfs-root directory back into an appimage so that it gets the static runtime again.
Let me know if that works, if it does then it is likely an issue with how the squashfs image is made.

Maybe I should have postet this before, but the error message I get is:
fuse: failed to exec fusermount3: No such file or directory

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory

I am not quite sure how to turn the extracted squashfs-root back into an appimage. appimge-tools complains about missing a desktop file. I really have no experience with appimages and just wanted to make you aware of the issue.
My current workaround is to simply revert the runtime back to fuse2 (https://github.com/Jonas-Finkler/nix-appimage).

There's no need to revert to using libfuse2, if you install the fusermount3 binary, everything should work.
You can compile it yourself or download a static binary if you don't have necessary privileges.
https://bin.ajam.dev/x86_64_Linux/Baseutils/fuse3/
[+] https://github.com/Azathothas/Toolpacks/blob/main/.github/scripts/x86_64_Linux/bins/fuse3.sh
https://bin.ajam.dev/aarch64_arm64_Linux/Baseutils/fuse3/
[+] https://github.com/Azathothas/Toolpacks/blob/main/.github/scripts/aarch64_Linux/bins/fuse3.sh
As to how to turn squashfs-root back into an appimage, here's a few examples:
https://github.com/Azathothas/Toolpacks/blob/main/.github/scripts/x86_64_Linux/bins/mpv.sh
https://github.com/Azathothas/Toolpacks/blob/main/.github/scripts/x86_64_Linux/bins/ladybird.sh
https://github.com/Azathothas/Toolpacks/blob/main/.github/scripts/x86_64_Linux/bins/nicotine-plus.sh

@Jonas-Finkler you can also try some of the appimages that @Azathothas makes, which actually get extracted and made again with appimagetool.
They work without fusermount3.

You can download it here: https://bin.ajam.dev/x86_64_Linux/
(search for mpv.AppImage).