Fannypack Roadmap

Feel free to build any uncompleted component below. If you would like to take on a component, please comment which component you would like to take (make sure nobody has mentioned it in the comments too!). Once you have commented, please raise an issue with the title 'Add <{Component}>', and I will label this as 'in-progress'.
Primitives
These will just be an export of Reakit's primitive components (we are including them for ease of development):

[x] <Box>
[x] <Block>
[x] <InlineBlock>
[x] <Flex>
[x] <InlineFlex>
[x] <Grid>

Layout

[x] <Columns>
[x] <Column>
[x] <Container>
[x] <Pane>
[ ] <Grid>

Typography

[x]

[x]
[x] <Heading>
[x] <Link>
[x] <List>
[x] <Paragraph>
[x] <Text>

Components

[ ] <Accordians>
[x] <Alert>
[x] <Avatar>
[x] <Breadcrumbs>
[x] <Button>
[x] <Callout>
[x] <CalloutOverlay>
[x] <Card>
[ ] <Carousel>
[x] <Dialog>
[x] <DialogModal>
[x] <Divider>
[x] <Icon>
[x] <Image>
[x] <Menu> (note: include example with Popover)
[ ] <Navbar>
[x] <Navigation>
[ ] <Pagination>
[x] <Spinner>
[x]

[x] <Tabs>
[x] <Tag>
[x] <Toast>
[ ] <Video>

Form

[x]
[x] <Checkbox>

[x] <CheckboxField>

[x] <Radio>

[x] <RadioGroup>
[x] <RadioGroupField>

[x] <Select>

[x] <SelectField>

[x] <SelectMenu>
[x] <Switch>

[x] <SwitchField>

[x] <Input>

[x] <InputField>

[x] <Textarea>

[x] <TextareaField>

[x] <Field>

Utilities

[ ] <Badge>
[x] <Backdrop> (from Reakit)
[x] <Group>
[x] <Hidden> (from Reakit)
[x] <Modal>
[x] <Overlay> (from Reakit)
[x] <Portal> (from Reakit)
[x] <Popover> (from Reakit)
[ ] <Sidebar> (from Reakit)
[ ] <Step> (from Reakit)
[x] <Tooltip> (from Reakit)

Extras

[x] <Timeline>
[x] <Rating>

Misc

[x] Ability to import on a per-component basis for consumers who don't support tree shaking (e.g. import Button from 'fannypack/Button'

@jxom i'm going to build Alert component

@jxom I'll pick up Textarea.

@jxom I will build Card

@jxom Yes, sorry for the delay.

I dibs Navbar

@jxom  I'll work on <Timeline>

is Accordians still up Up for grabs  ? I'd like to contribute on that @jxom

Accordians in progress!!


Allow batching of items when sent to LLM

Description
Can we modify convert_texts_to_vector in https://github.com/harmonydata/harmony/blob/main/src/harmony/matching/default_matcher.py to allow items to be batched when sent to the LLM?
Batch size should be variable
Rationale
If a user wants to harmonise 10,000 items, this will not fit in memory even in a high performance machine. Small laptops probably can only batch 20 items at a time. But the batching should be configurable as it will slow things down. Perhaps as a parameter.
People have reported that the website cannot cope with large harmonisations. E.g. below comment on Discord (23 Oct 2024)

@woodthom2 Hello. If this issue is still open, i would love to work on that and contribute to your project.

Hi @makrianast , please feel free to take this on! Thanks so much! Do you want to have a quick chat with me on Discord/Google Meet about it?

Just FYI the server that is running the Harmony web tool is 16 GB. I have not tested to find out at what size a request crashes the server but I am pretty certain that the critical number  is between 50 and 2000 questionnaire items! Of course we have to allow for different user machine specs

Hello @woodthom2 . Yes of course. My discord is: anastasiamakrii . Feel free to contact me there if you'd like!

Thanks!
On Fri, 1 Nov 2024, 17:49 makrianast, @.***> wrote:

Hello @woodthom2 https://github.com/woodthom2 . Yes of course. My
discord is: anastasiamakrii . Feel free to contact me there if you'd like!
—
Reply to this email directly, view it on GitHub
https://github.com/harmonydata/harmony/issues/56#issuecomment-2452316158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUBTVJO3H3YVFQCQY3UZXDZ6O5JPAVCNFSM6AAAAABQQRBEBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGMYTMMJVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Also related to https://github.com/harmonydata/harmony/issues/63


DigestBuilder should raise an exception when provided with invalid data

as it currently is, DigestBuilder can be fed with bogus data, but depending on what gets fed it will raise all sort of Exceptions, requiring the consumer of the API to capture all sort of exceptions.
Examples:
feeding it with a empty strings results in ArrayIndexOutOfBoundsException
while feeding with an short hash string results in StringIndexOutOfBoundsException
It would be great if a particular exception was raised.

I have verified that wrong inputs produce different java general exception.
I am going add an input check on builder method that produces an IllegalArgumentException when the hash is invalid.
What do you think @trixpan ?
new DigestBuilder().withHash("F42089EA34272885F0FB2D34E6911444C").build()

java.lang.StringIndexOutOfBoundsException: String index out of range: 40

new DigestBuilder().withHash("").build()
java.lang.ArrayIndexOutOfBoundsException: 0


error APPX1101: Payload contains two or more files with the same destination path 'AppEF.deps.json'.

Describe the bug
When building my app, I get this error:

Steps to reproduce the bug

Create a WinUI 3 app.
Add Microsoft.EntityFrameworkCore.Tools 6.0.5 from NuGet.
Build the app.

Expected behavior
No response
Screenshots
No response
NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 21H2 (19044, November 2021 Update)
IDE
Visual Studio 2022
Additional context
It looks like this error occurs while executing the script Microsoft.Build.Msix.Packaging.targets:

Moreover, the contents of these files are different:
.../bin/...

.../obj/...

Maybe that's why duplicates are not deleted ???

Dupe of #2237, #1856, et al.

Thanks for the tip. I read https://github.com/microsoft/WindowsAppSDK/issues/2237 and https://github.com/microsoft/WindowsAppSDK/issues/1856. Tried the methods suggested there. Unfortunately, in my case, they do not provide a solution to the problem. The error message APPX1101 is still issued.

I found a workaround for using EF Add-Migration and more in WinUI 3 in Desktop (Packaged) projects.
Workaround steps:

Workaround steps:

Create WinUI 3 in Desktop (Packaged) project

Workaround steps:

Create new Project AppEF.Model -> Class Library (WuinUI 3 in Desktop) . This project will be used to store the model description (DBContext). Add the necessary packages Microsoft.EntityFrameworkCore... into it. From the main AppEF project, add a reference to it. This is the main configuration for developing the necessary software. However, if you add a package Microsoft.EntityFrameworkCore.Tools to an AppEF project, the solution buid will fail.

Workaround steps:

We start migration. We explicitly specify AppEF.Console (!!!) as the starup project.

As a result, the migration was successfully created. I will continue to check the compatibility of WinUI 3 and EF...
Maybe you had to immediately use template with Windows Application Packaging (WAP) project (???)

The workaround provided by @Ika59 works for Maui Native Mobile applications too. Thanks a lot!

MAUI is step by step releasing, yet this bug still hangs around.
Unbearable working conditions, I must say.

This is fixed in Windows App SDK 1.2 Preview 2, at which point the workaround may be removed

Hey @Scottj1s  I'm getting this when I set PublishTrimmed to "true". I get some trim analysis warnings -  one for WinRT.TypeExtensions, five for WinRT.Projections..cctor(); and one IL2104 for WinRT.Runtime.dll. And then error APPX1101.
I assume my code is not the problem because it warned me about the code to enable Mica, so I had to take that off.
If I set PublishTrimmed to "false" it builds normally, no problems.

@eduardobragaxz, yes the trim warnings are known and being investigated.  Are you seeing the APPX1101 with WinAppSDK 1.2 Preview 2?  And are you seeing it specifically with colliding deps.json files?  If so, please reopen this issue and provide a simple repro.  If you're seeing something else, please open a new issue.

@Scottj1s yes, WinAppSDK 1.2 Preview 2. Submitted the issue here.

This issue still existing on latest release of VS

I have this exact issue when I add Microsoft.EntityFrameworkCore.Design to the WinUI Application:

When I remove only this package, the build works as normal, but I can't generate migrations


Baubles

Implementation of Baubles API
This PR contains the following:

All the rings that are listed in the features are implemented.
Added The Lumberjack Ring and the Midas Touch Ring from the old version of WU.

TODO:

Config that sets the break speed when holding The Lumberjack ring. (Is set to 10f until the config is added)
Each ring as a tooltip describing what he does.

i. e. The Lumberjack contains a tooltip called "ring_tooltip.the_lumberjack_ring", which you will use to set what the ring does in the lang file.

Example: "ring_tooltip.the_lumberjack_ring": "Transforms everything in §mgold§r wood."

Give each item a unique texture.

No problem 👍


fix npm audit vulnerabilities

npm audit reports 38 vulnerabilities (1 low, 4 moderate, 24 high, 9 critical). these should be reviewed and addressed as appropriate

Update:
12 vulnerabilities found
Severity: 5 moderate | 2 high | 5 critical


fastapi error?

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[X ] I am running the latest code. Development is very rapid so there are no tagged versions as of now.
[ X] I carefully followed the README.md.
[ X] I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
[X ] I reviewed the Discussions, and have a new bug or useful enhancement to share.

Expected Behavior
Please provide a detailed written description of what you were trying to do, and what you expected llama-cpp-python to do.
uvicorn llama_cpp.server.app:app --reload
returns this error:
INFO:     Will watch for changes in these directories: ['/mnt/d/Dropbox/Developer-Tools/llama-cpp-python/examples/high_level_api']
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [601969] using WatchFiles
ERROR:    Error loading ASGI app. Attribute "app" not found in module "llama_cpp.server.app".
Current Behavior
Please provide a detailed written description of what llama-cpp-python did, instead.
Doesnt' work
Environment and Context
Please provide detailed information about your computer setup. This is important in case the issue is not reproducible except for under certain specific conditions.

Physical (or virtual) hardware you are using, e.g. for Linux:

$ lscpu
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      39 bits physical, 48 bits virtual
CPU(s):                             16
On-line CPU(s) list:                0-15
Thread(s) per core:                 2
Core(s) per socket:                 8
Socket(s):                          1
Vendor ID:                          GenuineIntel
CPU family:                         6
Model:                              141
Model name:                         11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
Stepping:                           1
CPU MHz:                            2303.999
BogoMIPS:                           4607.99
Virtualization:                     VT-x
Hypervisor vendor:                  Microsoft
Virtualization type:                full
L1d cache:                          384 KiB
L1i cache:                          256 KiB
L2 cache:                           10 MiB
L3 cache:                           24 MiB
Vulnerability Gather data sampling: Unknown: Dependent on hypervisor status
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Mitigation; Enhanced IBRS
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good
nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq vmx ssse3 fma cx16 pdcm
pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand
hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb stibp ibrs_enhanc
ed tpr_shadow vnmi ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invp
cid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx5
12bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx512vbmi umip avx512_vbmi2 gfni vaes
vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm a
vx512_vp2intersect flush_l1d arch_capabilities

Operating System, e.g. for Linux:

$ uname -a
Linux DESKTOP-UD5405F <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

SDK version, e.g. for Linux:

$ python3 --version
Python 3.8.10
$ make --version
GNU Make 4.2.1
$ g++ --version
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue. We are not sitting in front of your screen, so the more detail the better.

just run fastapi_server.py

Note: Many issues seem to be regarding functional or performance issues / differences with llama.cpp. In these cases we need to confirm that you're comparing against the version of llama.cpp that was built with your python package, and which parameters you're passing to the context.
Try the following:

git clone https://github.com/abetlen/llama-cpp-python
cd llama-cpp-python
rm -rf _skbuild/ # delete any old builds
python -m pip install .
cd ./vendor/llama.cpp
Follow llama.cpp's instructions to cmake llama.cpp
Run llama.cpp's ./main with the same arguments you previously passed to llama-cpp-python and see if you can reproduce the issue. If you can, log an issue with llama.cpp

Failure Logs
Please include any relevant log snippets or files. If it works under one configuration but not under another, please provide logs for both configurations and their corresponding outputs so it is easy to see where behavior changes.
Also, please try to avoid using screenshots if at all possible. Instead, copy/paste the console output and use Github's markdown to cleanly format your logs for easy readability.
Example environment info:
llama-cpp-python$ git log | head -1
commit 47b0aa6e957b93dbe2c29d53af16fbae2dd628f2

llama-cpp-python$ python3 --version
Python 3.10.10

llama-cpp-python$ pip list | egrep "uvicorn|fastapi|sse-starlette|numpy"
fastapi                  0.95.0
numpy                    1.24.3
sse-starlette            1.3.3
uvicorn                  0.21.1

llama-cpp-python/vendor/llama.cpp$ git log | head -3
commit 66874d4fbcc7866377246efbcee938e8cc9c7d76
Author: Kerfuffle<EMAIL_ADDRESS>Date:   Thu May 25 20:18:01 2023 -0600

Hey @silvacarl2 sorry about that, the command to run the server via uvicorn cli changed but I think I forgot to update it everywhere. I'll fix that.
You should be able to run the server viat uvicorn --reload --factory llama_cpp.server.app:create_app. You'll also need to set the MODEL environment variable to the path to the gguf file you plan to serve or set CONFIG_FILE if you plan to serve multiple models.

awesome, thx, let me know when we can check it out.

AWESOEM THX!!!! CHECKING IT OUT!!!!!!!!!

JUST FYI THIS IS TOTALLY AWESOME.  WOW.

Haha happy to hear!


Make "Debug" output coloured

The output of the debug build with the fly_mission example is shown below. As you can see, the Info output is very clear (blue) but the Debug is white, and hence not so easy to differentiate from the app's output.
I think we can assume that, since we aren't making our debug output available, users will almost always output white.

I am not sure what colour would be best/we have already used. But see the ubuntu green/blue above are pretty easy to discern!

I like the green idea.


Removes KnownTableType, makes TableType sealed.

All tables are tables of records. Requiring lazy types to choose whether
they derive from TableType or RecordType is unnecessary confusion, and
instead, they should always derive from RecordType, calling ToTable if
needed as a table.

Pull Request Test Coverage Report for Build 317084

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.0007%) to 63.817%

Files with Coverage Reduction
New Missed Lines
%

/src/libraries/Microsoft.PowerFx.Core/Public/Types/TableType.cs
7
82.5%

Totals

Change from base Build 317078:
-0.0007%

Covered Lines:
24198

Relevant Lines:
37918

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Connectors.dll
:x: 4 Binary Compatibility issues for Microsoft.PowerFx.Core compared against version 0.2.2-preview.20220815-317077.

CannotSealType : Type 'Microsoft.PowerFx.Types.TableType' is actually (has the sealed modifier) sealed in the implementation but not sealed in the contract.
MembersMustExist : Member 'Microsoft.PowerFx.Types.TableType..ctor()' does not exist in the implementation but it does exist in the contract.
CannotMakeMemberNonVirtual : Member 'Microsoft.PowerFx.Types.TableType.Add(Microsoft.PowerFx.Types.NamedFormulaType)' is non-virtual in the implementation but is virtual in the contract.
CannotMakeMemberNonVirtual : Member 'Microsoft.PowerFx.Types.TableType.Visit(Microsoft.PowerFx.Types.ITypeVisitor)' is non-virtual in the implementation but is virtual in the contract.

:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.Interpreter.dll**
:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.LanguageServerProtocol.dll**
:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.Transport.Attributes.dll**

This should solve #550

:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Connectors.dll
:x: 4 Binary Compatibility issues for Microsoft.PowerFx.Core compared against version 0.2.2-preview.20220815-317110.

CannotSealType : Type 'Microsoft.PowerFx.Types.TableType' is actually (has the sealed modifier) sealed in the implementation but not sealed in the contract.
MembersMustExist : Member 'Microsoft.PowerFx.Types.TableType..ctor()' does not exist in the implementation but it does exist in the contract.
CannotMakeMemberNonVirtual : Member 'Microsoft.PowerFx.Types.TableType.Add(Microsoft.PowerFx.Types.NamedFormulaType)' is non-virtual in the implementation but is virtual in the contract.
CannotMakeMemberNonVirtual : Member 'Microsoft.PowerFx.Types.TableType.Visit(Microsoft.PowerFx.Types.ITypeVisitor)' is non-virtual in the implementation but is virtual in the contract.

:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.Interpreter.dll**
:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.LanguageServerProtocol.dll**
:heavy_check_mark: No Binary Compatibility issues for **Microsoft.PowerFx.Transport.Attributes.dll**


Trying to customize rule 'Contact K8S API Server From Container' causes other events not being logged

Describe the bug
While customizing Falco rules, I checked that when trying to customize 'Contact K8S API Server From Container', this was causing events like 'Write below etc' not be logged at all.
How to reproduce it
In a Falco installation close to the standard, I've set up the following custom_rules:
customRules:
  custom-rules.yaml: |-

    # For 'Create files below dev'

    - list: dev_creation_binaries
      append: true
      items: ["csi-provisioner", "csi-attacher", "csi-resizer"]

    # For 'Non sudo setuid'

    - macro: user_known_non_sudo_setuid_conditions
      condition: >
        ((k8s.ns.name = "nsa" and k8s.pod.name startswith "a1-") or
        (k8s.ns.name = "nsb" and k8s.pod.name startswith "b1-") or
        (k8s.ns.name = "nsc" and k8s.pod.name startswith "c1-") or
        (k8s.ns.name = "nsd" and k8s.pod.name startswith "d1-") or
        (k8s.ns.name = "nse" and k8s.pod.name startswith "e1-") or
        (k8s.ns.name = "nsf" and k8s.pod.name startswith "f1-"))

    # For 'Write below binary dir'

    - macro: user_known_write_below_binary_dir_activities
      condition: >
        (container.id = "host" and proc.pname in (docker_binaries))

    # For 'Write below etc'

    - macro: calico_writing_conf
      condition: >
        (k8s.pod.name startswith "calico-node" and container.image.repository in ("mcr.microsoft.com/oss/calico/node", "mcr.azk8s.cn/oss/calico/node"))

    - macro: user_known_write_below_etc_activities
      condition: >
        ((container.id = "host" and proc.pname in (docker_binaries)) or
         (proc.cmdline = "cp -TRv config/node-problem-detector/ /etc/node-problem-detector.d/") or
         ((proc.pcmdline startswith "bash /var/lib/waagent/Microsoft.AKS.Compute.AKS.Linux.AKSNode") and
          (fd.name startswith "/etc/node-problem-detector.d/")))

    # For 'Launch Privileged Container' and 'Launch Excessively Capable Container'

    - macro: user_privileged_containers
      condition: >
        (container.image.repository endswith "azurecr.io/docker.io/istio/proxyv2")

    # For 'DB program spawned process'

    - macro: user_known_db_spawned_processes
      condition: >
        (k8s.ns.name = "db" and k8s.pod.name startswith "db-")

    # For 'Run shell untrusted'

    - macro: user_shell_container_exclusions
      condition: >
        (k8s.ns.name = "db" and k8s.pod.name startswith "db-")

    # For 'Contact K8S API Server From Container' (Temporarily removed due to issues)

With this custom rules, Falco seems to be working as expected, firing events like "Write below etc" when I force an event like this.
If I add the following for 'Contact K8S API Server From Container':
    - macro: k8s_containers
      condition: >
        ((k8s.ns.name = "ns1" and k8s.pod.name startswith "pod11-") or
         (k8s.ns.name = "ns2" and k8s.pod.name startswith "pod21-") or
         (k8s.ns.name = "ns3" and k8s.pod.name startswith "pod31-") or
         (k8s.ns.name = "ns3" and k8s.pod.name startswith "pod32-") or
         (k8s.ns.name = "ns4" and k8s.pod.name startswith "pod41-") or
         (k8s.ns.name = "ns5" and k8s.pod.name startswith "pod51-") or
         (k8s.ns.name = "ns6" and k8s.pod.name startswith "pod61-") or
         (k8s.ns.name = "ns7" and k8s.pod.name startswith "pod71-") or
         (k8s.ns.name = "ns8" and k8s.pod.name startswith "pod81-") or
         (k8s.ns.name = "ns9" and k8s.pod.name startswith "pod91-") or
         (k8s.ns.name = "ns10" and k8s.pod.name startswith "pod101-") or
         (k8s.ns.name = "ns11" and k8s.pod.name startswith "pod111-") or
         (k8s.ns.name = "ns12" and k8s.pod.name startswith "pod121-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod131-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod132-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod133-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod134-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod135-") or
         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod136-") or
         (k8s.ns.name = "ns14" and k8s.pod.name startswith "pod141-") or
         (k8s.ns.name = "ns15" and k8s.pod.name startswith "pod151-"))

(Tested lots of variants even leaving few lines, this is the kind of desired list)
this kind of alerts stop being logged, but also other alerts like 'Write below etc'
Expected behaviour
Only the 'Contact K8S API Server From Container' should not be logged
Environment

Falco version:
0.34.1
System info:

# falco --support | jq .system_info
Fri May  5 14:24:23 2023: Falco version: 0.34.1 (x86_64)
Fri May  5 14:24:23 2023: Falco initialized with configuration file: /etc/falco/falco.yaml
Fri May  5 14:24:23 2023: Loading plugin 'k8saudit' from file /usr/share/falco/plugins/libk8saudit.so
Fri May  5 14:24:23 2023: Loading plugin 'json' from file /usr/share/falco/plugins/libjson.so
Fri May  5 14:24:23 2023: Loading rules from file /etc/falco/falco_rules.yaml
Fri May  5 14:24:24 2023: Loading rules from file /etc/falco/rules.d/custom_rules.yaml
{
  "machine": "x86_64",
  "nodename": "falco-5h6vh",
  "release": "5.4.0-1103-azure",
  "sysname": "Linux",
  "version": "#109~18.04.1-Ubuntu SMP Wed Jan 25 20:53:00 UTC 2023"
}

Cloud provider or hardware configuration:
Azure and AWS
OS: Ubuntu
Kernel:
Linux falco-5h6vh 5.4.0-1103-azure #109~18.04.1-Ubuntu SMP Wed Jan 25 20:53:00 UTC 2023 x86_64 GNU/Linux
Installation method:
Generate manifests using helm template and custom values -> Apply

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

uhm that's interesting, we will take a look, thank you for reporting!

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

ei sorry for the late answer but I tried to reproduce it with the latest Falco version without success.
I used helm chart 3.8.7 and so Falco 0.36.2, this is how I modified the default vaules.yaml
diff --git a/charts/falco/values.yaml b/charts/falco/values.yaml
index b6467f4..34a595d 100644
--- a/charts/falco/values.yaml
+++ b/charts/falco/values.yaml
@@ -179,7 +179,7 @@ driver:
   # Always set it to false when using Falco with plugins.
   enabled: true
   # -- Tell Falco which driver to use. Available options: module (kernel driver), ebpf (eBPF probe), modern-bpf (modern eBPF probe).
-  kind: module
+  kind: modern-bpf
   # -- Configuration section for ebpf driver.
   ebpf:
     # -- Path where the eBPF probe is located. It comes handy when the probe have been installed in the nodes using tools other than the init
@@ -322,16 +322,80 @@ certs:

 # -- Third party rules enabled for Falco. More info on the dedicated section in README.md file.
 customRules:
-  {}
-  # Although Falco comes with a nice default rule set for detecting weird
-  # behavior in containers, our users are going to customize the run-time
-  # security rule sets or policies for the specific container images and
-  # applications they run. This feature can be handled in this section.
-  #
-  # Example:
-  #
-  # rules-traefik.yaml: |-
-  #   [ rule body ]
+  custom-rules.yaml: |-
+
+    # For 'Non sudo setuid'
+
+    - macro: user_known_non_sudo_setuid_conditions
+      condition: >
+        ((k8s.ns.name = "nsa" and k8s.pod.name startswith "a1-") or
+        (k8s.ns.name = "nsb" and k8s.pod.name startswith "b1-") or
+        (k8s.ns.name = "nsc" and k8s.pod.name startswith "c1-") or
+        (k8s.ns.name = "nsd" and k8s.pod.name startswith "d1-") or
+        (k8s.ns.name = "nse" and k8s.pod.name startswith "e1-") or
+        (k8s.ns.name = "nsf" and k8s.pod.name startswith "f1-"))
+
+    # For 'Write below binary dir'
+
+    - macro: user_known_write_below_binary_dir_activities
+      condition: >
+        (container.id = "host" and proc.pname in (docker_binaries))
+
+    # For 'Write below etc'
+
+    - macro: calico_writing_conf
+      condition: >
+        (k8s.pod.name startswith "calico-node" and container.image.repository in ("mcr.microsoft.com/oss/calico/node", "mcr.azk8s.cn/oss/calico/node"))
+
+    - macro: user_known_write_below_etc_activities
+      condition: >
+        ((container.id = "host" and proc.pname in (docker_binaries)) or
+         (proc.cmdline = "cp -TRv config/node-problem-detector/ /etc/node-problem-detector.d/") or
+         ((proc.pcmdline startswith "bash /var/lib/waagent/Microsoft.AKS.Compute.AKS.Linux.AKSNode") and
+          (fd.name startswith "/etc/node-problem-detector.d/")))
+
+    # For 'Launch Privileged Container' and 'Launch Excessively Capable Container'
+
+    - macro: user_privileged_containers
+      condition: >
+        (container.image.repository endswith "azurecr.io/docker.io/istio/proxyv2")
+
+    # For 'DB program spawned process'
+
+    - macro: user_known_db_spawned_processes
+      condition: >
+        (k8s.ns.name = "db" and k8s.pod.name startswith "db-")
+
+    # For 'Run shell untrusted'
+
+    - macro: user_shell_container_exclusions
+      condition: >
+        (k8s.ns.name = "db" and k8s.pod.name startswith "db-")
+
+    # For 'Contact K8S API Server From Container'
+    - macro: k8s_containers
+      condition: >
+        ((k8s.ns.name = "ns1" and k8s.pod.name startswith "pod11-") or
+         (k8s.ns.name = "ns2" and k8s.pod.name startswith "pod21-") or
+         (k8s.ns.name = "ns3" and k8s.pod.name startswith "pod31-") or
+         (k8s.ns.name = "ns3" and k8s.pod.name startswith "pod32-") or
+         (k8s.ns.name = "ns4" and k8s.pod.name startswith "pod41-") or
+         (k8s.ns.name = "ns5" and k8s.pod.name startswith "pod51-") or
+         (k8s.ns.name = "ns6" and k8s.pod.name startswith "pod61-") or
+         (k8s.ns.name = "ns7" and k8s.pod.name startswith "pod71-") or
+         (k8s.ns.name = "ns8" and k8s.pod.name startswith "pod81-") or
+         (k8s.ns.name = "ns9" and k8s.pod.name startswith "pod91-") or
+         (k8s.ns.name = "ns10" and k8s.pod.name startswith "pod101-") or
+         (k8s.ns.name = "ns11" and k8s.pod.name startswith "pod111-") or
+         (k8s.ns.name = "ns12" and k8s.pod.name startswith "pod121-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod131-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod132-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod133-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod134-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod135-") or
+         (k8s.ns.name = "ns13" and k8s.pod.name startswith "pod136-") or
+         (k8s.ns.name = "ns14" and k8s.pod.name startswith "pod141-") or
+         (k8s.ns.name = "ns15" and k8s.pod.name startswith "pod151-"))

 ########################
 # Falco integrations   #
@@ -410,7 +474,7 @@ falcoctl:
         # -- Do not resolve the depenencies for artifacts. By default is true, but for our use case we disable it.
         resolveDeps: false
         # -- List of artifacts to be installed by the falcoctl init container.
-        refs: [falco-rules:2]
+        refs: [falco-rules:2, falco-sandbox-rules:2, falco-incubating-rules:2]
         # -- Directory where the rulesfiles are saved. The path is relative to the container, which in this case is an emptyDir
         # mounted also by the Falco pod.
         rulesfilesDir: /rulesfiles
@@ -469,6 +533,8 @@ falco:
     - /etc/falco/falco_rules.yaml
     - /etc/falco/falco_rules.local.yaml
     - /etc/falco/rules.d
+    - /etc/falco/falco-sandbox_rules.yaml
+    - /etc/falco/falco-incubating_rules.yaml

   # [Experimental] `rule_matching`
   #

Let us know if you still face the issue

I will close this, feel free to reopen if this is still an issue


Understanding Power Platform Licensing for the Citizen Developer

Category

[ ] Content fix
[x] New article

Related issues:

mentioned in #13

What's in this Pull Request?
This is the initial article on Licensing from the Citizen Developer perspective. Changes are anticipated.
Guidance
The article should work as is.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: bigpix2000 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Docs Build status updates of commit 73c2162:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/powerplatformlicensingforcitizendeveloper.md
:warning:Warning
View
Details

Community/powerplatformlicensingforcitizendeveloper.md

Line 1: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1: [Warning] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 3: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 21: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 46: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 214: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 695e892:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/powerplatformlicensingforcitizendeveloper.md
:warning:Warning
View
Details

Community/powerplatformlicensingforcitizendeveloper.md

Line 1: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1: [Warning] Missing required attribute: 'title'. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@bigpix2000 - There's some required YAML we can add to the article. I can take care of that.

Thanks!  I tried putting it in but apparently I might have fat fingered it …
RR
From: Marc D Anderson<EMAIL_ADDRESS>Sent: Monday, March 16, 2020 12:28 PM
To: MicrosoftDocs/microsoft-365-community<EMAIL_ADDRESS>Cc: Ralph Rivas<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-community] Understanding Power Platform Licensing for the Citizen Developer (#119)
@bigpix2000https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbigpix2000&data=02|01||45d23e82d6704993687708d7c9cf6f25|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637199765061116446&sdata=Gu8ttkCyRwjgE20HR12Tv0RUiZnn1aHCDkgvryQneBI%3D&reserved=0 - There's some required YAML we can add to the article. I can take care of that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-community%2Fpull%2F119%23issuecomment-599665632&data=02|01||45d23e82d6704993687708d7c9cf6f25|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637199765061126454&sdata=ogK2%2F0BhdguMIQGWysmuedNgvMS%2FMc0Db7cFAuXDKSE%3D&reserved=0, or unsubscribehttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB2OOTWYSKTGK735NYPSUB3RHZOTJANCNFSM4LMOVMOA&data=02|01||45d23e82d6704993687708d7c9cf6f25|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637199765061126454&sdata=J7ZT3pvwwrhL86O1qxukLCZDr%2BhH%2FMd7Dvu%2BE6zOzz0%3D&reserved=0.


UI/UX Improvements Suggestion for Your Project

Hi @BamaCharanChhandogi,
I hope this message finds you well. I've been exploring your project and would love to contribute by enhancing its user interface for a more modern and engaging experience. Here are a few changes I believe would improve the look and usability of the page:

Left Sidebar: Shift the left bar to the extreme left for better structure and alignment.
Image Hover Effect: Add a hover effect to the image in the left bar, making it pop out when hovered.
Box Shadows: Introduce subtle box shadows to give the layout more depth and a cleaner visual hierarchy.
Font Styling: Update the font to improve readability and aesthetics, giving it a fresh, professional feel.
Button Hover Effects: Add smooth hover transitions on buttons to make them more interactive and user-friendly.

I'd love to help implement these changes to enhance the overall UI/UX. Please let me know if you'd like to move forward with this, and I'd be happy to collaborate!
Best regards,
Anisha Birla

👋 Thank you for raising an issue! We appreciate your effort in helping us improve. Our GitFinder team will review it shortly. Stay tuned!

What's the update on this @Anisha2123 .
Feel free to reach out to us if you have any queries or need help with anything. 🚀

Can You assign me this issue ?
@BamaCharanChhandogi

Yes Sir, I m working on it. Will update it soon @tmsagarofficial


Reaction Stoichiometry not reflected in output

In simulation, I used Dolomite that dissolves to give 1.45 Ca and 0.55 Mg per mole of dolomite, but in output the concentration of Ca and Mg are equal at time steps after few days. The stoichiometry in the display while running the model is correct.

I just now saw something in display. No kinetic reaction is being read. This is potentially the problem. But I don't think there is anything wrong in the input file. I will send you the input files and output.

You can directly attach your input files with the issues. That is much easier for me to match issues with input files.

I have attached them here.
konza_dol.zip
konza_dol_results.txt

@KayalvizhiSadayappan The issue is caused by the lack of newline character at the end of the file. I don't know how to fix this. Did you edit this file in Windows and then uploaded it?

I didn't edit in windows. After seeing your message, I tried it running
after pressing enter at the end of mineral reaction and saving the file. It
worked. Thanks!
On Tue, 2 Mar 2021 at 16:46, Yuning Shi<EMAIL_ADDRESS>wrote:

Closed #14 https://github.com/shiyuning/HBV-BioRT/issues/14 via 650e48a
https://github.com/shiyuning/HBV-BioRT/commit/650e48a7164dd7517cfd1cb7261c16e88a5cf722
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shiyuning/HBV-BioRT/issues/14#event-4398272808, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3QV6HBA2ST4N3MCGQNRTTTBVMEDANCNFSM4YPEKBOQ
.

I actually fixed this. You can try it by using your old input file.
What text editor did you use to generate the file? I want to look it up and see what is causing the problem.

I am using 'portal.aci.ics.psu.edu' to edit all files on the cluster. Not
sure what editor it is. I have attached pictures of chem file in the text
editor when it didn't work and when it worked. Maybe that will help?
On Tue, 2 Mar 2021 at 20:18, Yuning Shi<EMAIL_ADDRESS>wrote:

I actually fixed this. You can try it by using your old input file.
What text editor did you use to generate the file? I want to look it up
and see what is causing the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shiyuning/HBV-BioRT/issues/14#issuecomment-789350212,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3QV6EBN2Z6PWNB7SCC5JDTBWE7PANCNFSM4YPEKBOQ
.


Load branding based on domain

Based on #557 and #558, override default CSS variables with the brand colours based on the subdomain being used

 Branding

 Branding

 Branding

 Branding


[Allomancy] Metal Vial eating things it shouldn't

Issue description
When filling a metal vial with nuggets, if you place other blocks or items into the crafting grid it will consume them as well.
Steps to reproduce
Put metal vial into crafting grid with metal nugget (i.e tin)
Place other block into crafting grid
Craft the vial
Minecraft version
1.19.2 (Latest)
Forge version
43.3.5
Cosmere version
build 77
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response

Still happening in 1.20+


running Madness with QCengine

Description

This PR creates a new madness directory under programs.  The files are the first iterations to setting up madness in qcng.  It follows a very similar structure to that of nwchem.
Changelog description

This is the first iteration of setting up qcng to run madness calculations.
Status

[ ] Code base linted
[ ] Ready to go

please rebase to fix CI and conflict


STM32F4: Large I2C read/write access problem

On STM32F4, large (more than 256 bytes) read/write accesses fail when i try to communicate with an SE050 secure element from NXP.
Fix #43577 introduces a new mechanism which appears to not be implemented in I2C V1 devices like the STM32F4. Indeed I2C V1 devices seem to not implement LL_I2C_EnableReloadMode mechanism. Actually, in my opinion I2C V1 devices do not even require the use of any trick to send / receive data longer than 256 bytes.
On my side, i solved the problem by replacing the i2c_stm32_transaction() function by the following code:
static inline int
i2c_stm32_transaction(const struct device *dev,
		      struct i2c_msg msg, uint8_t *next_msg_flags,
		      uint16_t periph)
{
	int ret;
	if ((msg.flags & I2C_MSG_RW_MASK) == I2C_MSG_WRITE) {
		ret = stm32_i2c_msg_write(dev, &msg, next_msg_flags, periph);
	} else {
		ret = stm32_i2c_msg_read(dev, &msg, next_msg_flags, periph);
	}
	return ret;
}

@erwango, No problem, I will try to propose a PR shortly.

@erwango, Done


Move cloudlib client to nodeset model repo

Need to wait until both Marketplace and ProfileDesigner have consumed this branch.


Add devcontainer for GitHub Codespaces

Add devcontainer/features for use Codespaces

Install act - run github action locally
Features like black, flake8 , docker-in-docker
Usage:

act -W .github/workflows/quick-test.yml
black --check --skip-string-normalization .

Fixes #
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[x] New feature (It is strongly recommended to open an issue first)

We don't use black. Also, why docker-in-docker and act?
pylance, autopep8, isort, flake8, pytest would be usefull

act is useful if the developer wants to run the GitHub Actions locally without push the changes and depend on Docker for run the workflow
If the project wants i just add the basic requirement for development
pylance, autopep8, isort, flake8, pytest

Are you (or others) actually develop in codespaces? I've never seen it be used.
Now that we have hatch, would it make sense to let the user configure it themselves? you only have to install hatch and can use hatch test, hatch fmt, ...


Remove multiple question per page code

Multiple questions per page were never supported by Ruby Smart Answers. All this code was only there to support Smartdown's multiple questions per page functionality. Now that all flows have been converted to Ruby Smart Answers (i.e. single question per page), it's safe to remove this code.
Even if we decide we want to support multiple questions per page in the future, I think it's still worth doing this. Having made the changes in this PR, I'm sure we can simplify the code a lot further which would then make it easier to re-introduce multiple questions per page if it becomes desirable.
These changes should indirectly make it a bit easier to move towards directly rendering the landing page, question & outcome templates from the controller action.
I think there was already some unused CSS and this PR probably makes more CSS redundant. However, think that would be better tackled separately.
PS: Hopefully this PR isn't as bad as it looks for reviewing - I've tried to keep all the commits very small and focussed which is why there are so many of them.

Looks good to me.

I've rebased this against master and force-pushed in preparation for merging.


Build Templating

At a client site I've worked at, we've got a lot of builds that have basically the same YAML - but with very small/token changes to it. I'm considering sending in a PR that adds some features to simplify this workflow:

Ability to fetch the 'pipeline' content from another URL / git repository.
Ability to define environment variables that are common across all containers in a shared section.

The plan is that then these global environment variables are merged with the per-container environment (per-container taking precedence). For example a very typical docker flow
Example Drone YAML
environment:
  DOCKER_REPO: example-org/example-container

pipeline: https://github.com/steve-gray/drone-templates/docker

Example Template
pipeline:
  npm_tasks:
    image: node:latest
    commands:
      - npm install
      - npm test

  docker:
    image: plugins/docker
    repo: ${DOCKER_REPO}
    tags: latest

Considerations/extra requirements that spring to mind:

Signing including upstream content - I'm thinking that it's both not needed (if you control the upstream source, it's game over anyway), but also defeats the point (to force re-sign). Signing is going away anyway by the looks.

Repeatability of builds - Do we potentially need to capture the upstream template for repeatable builds? At a gut level I agree with this idea, but it complicates things. I'm thinking it's something can be rev 2.0 item?

Interesting idea!
I'd suggest to call the yaml key external_pipeline (so you can specify further jobs in the actual pipeline)
It might be useful to restrict the template to a specific branch + commit instead and print an info when a new commit is available in the specified branch.

Yeah, that'd probably make sense on the key name.
The specific branch/commit locking goes against the idea though: when I update the template, I don't want to have to update in the case I'm looking directly at over 150 repos. Right now I can cycle passwords using org secrets, but you can't change a non-secret setting or a build-matrix permutation list to add a new entry.

I think this relates to https://github.com/drone/drone/issues/1863

user wants a central or shared yaml file configuration that could apply to all, or a subset, of registered repositories.

user wants to automatically add default steps to all Yaml files

It is likely that we would implement this feature through yaml plugins as opposed to building this logic into drone, at least initially. This allows prototyping and gathering feedback without having to worry about impact to Drone core, with the ability to merge the feature in the future once it is fully flushed out.

@bradrydzewski Would it be fine to make this to a higher level, for example, request yaml from a remote server when the repo doesn't have an yaml in it (or some flag in the repo meta indicates this behavior)? We need this because we try not exposing this CI to end users.

I'm going to close this because it is not something we are going to add to drone core at this time. There is just too much complexity regarding how this will work with permissions and merging configuration / inheritance. I am also concerned that this complexity will create added support burden.
As mentioned above, I think plugins are the way to handle this. If there is an awesome plugin that proves my concerns are invalid and is a real benefit to the community, we can certainly revisit this in drone core.
Until then please follow https://github.com/drone/drone/issues/1863 for updates to our progress of making yaml configuration pluggable. Thanks!


Album Art

Thank you for making this, it's flippin' awesome while gaming.
Is the album art behavior hard-coded? I have foobar's Album Art setting to "Prefer Embedded" and the mini-player seems to only stick to "Prefer External" - album folders without images in them just show the neon green foobar logo in the miniplayer UI.

Just looked at the only other issue from a year ago and saw that album art was discussed. Maybe it's an issue with how the COM Automation plugin prioritizes Album Art.
I did find a temporary bodge of a workaround for one of the issues where it would pull whatever image Windows decided should be "Folder.jpg" for a folder filled with music that all has different album art...delete folder.jpg and stop Windows from re-creating it by changing the view settings for said folder.

Just looked at the only other issue from a year ago and saw that album art was discussed. Maybe it's an issue with how the COM Automation plugin prioritizes Album Art.
I did find a temporary bodge of a workaround for one of the issues where it would pull whatever image Windows decided should be "Folder.jpg" for a folder filled with music that all has different album art...delete folder.jpg and stop Windows from re-creating it by changing the view settings for said folder.

Hi,
It's not the COM automation plug-in, the album art is picked up by this software. It looks for common album art names like front.png first, if it fails to find anything it should check the file tags for album artwork, if this fails to find anything it'll show that foobar logo instead.
It sounds like in your case it's failing to find the embedded artwork at all?
I don't think there's an easy way for me to grab the preference from foobar but I could probably add a config option to prefer the embedded artwork.

Hi,
It's not the COM automation plug-in, the album art is picked up by this software. It looks for common album art names like front.png first, if it fails to find anything it should check the file tags for album artwork, if this fails to find anything it'll show that foobar logo instead.
It sounds like in your case it's failing to find the embedded artwork at all?
I don't think there's an easy way for me to grab the preference from foobar but I could probably add a config option to prefer the embedded artwork.

Wasn't expecting a response!
Yeah, in foobar's Advanced menu, under Display -> Album Art, I believe it defaults to "Prefer larger" but there are also options for "Prefer embedded" and "Prefer external."
Now that I know it's pulling album art on its own, that explains it. I don't expect it to grab foobar's preference if that's too difficult, but having it prioritize embedded album art would eliminate all of the problems where Windows has decided it ought to generate a "Folder.jpg" that's the wrong image (unavoidable with "Music" folders that have a mix of files in there).
I double checked the files where I saw the foobar logo, and the tags were messed up. Re-attaching the album art to those songs fixed it.
Only issue now is those mixed folders like I mentioned, a config option would be great. I tried to poke around in all of the files to see if it was something I could figure out and gave up.

Wasn't expecting a response!
Yeah, in foobar's Advanced menu, under Display -> Album Art, I believe it defaults to "Prefer larger" but there are also options for "Prefer embedded" and "Prefer external."
Now that I know it's pulling album art on its own, that explains it. I don't expect it to grab foobar's preference if that's too difficult, but having it prioritize embedded album art would eliminate all of the problems where Windows has decided it ought to generate a "Folder.jpg" that's the wrong image (unavoidable with "Music" folders that have a mix of files in there).
I double checked the files where I saw the foobar logo, and the tags were messed up. Re-attaching the album art to those songs fixed it.
Only issue now is those mixed folders like I mentioned, a config option would be great. I tried to poke around in all of the files to see if it was something I could figure out and gave up.

On a somewhat related note, the only files with embedded artwork that still don't display album art (wasn't all of them, kept clicking through my playlist) are FLAC or M4A files, either AAC or Apple Lossless. It can't see the same image that foobar shows present in the tags as "Front cover".

On a somewhat related note, the only files with embedded artwork that still don't display album art (wasn't all of them, kept clicking through my playlist) are FLAC or M4A files, either AAC or Apple Lossless. It can't see the same image that foobar shows present in the tags as "Front cover".

NBD if you can't change it, now that I know how it's working, I can just add a proper "folder.jpg" to those with missing art. It's something I was working on automating anyways so that my library looks neater in Explorer and so that I don't have Windows' dinky little 200x200 automatically generated ones muddling things up too.
I'm just happy to be able to control foobar in full screen games without having to fiddle with multimedia keys and different "Fn" layer mappings on different keyboards.

NBD if you can't change it, now that I know how it's working, I can just add a proper "folder.jpg" to those with missing art. It's something I was working on automating anyways so that my library looks neater in Explorer and so that I don't have Windows' dinky little 200x200 automatically generated ones muddling things up too.
I'm just happy to be able to control foobar in full screen games without having to fiddle with multimedia keys and different "Fn" layer mappings on different keyboards.

What I think I'll do is default to the embedded artwork and add an option to override it (larger/external). I'll take a look at FLAC/M4A embedded artwork while I'm in there too, not sure what the situation might be there.
It'll be a couple days before I have time to work on this as I don't have a Windows machine ready to go right now.
Thanks for bringing it up with a detailed report.

What I think I'll do is default to the embedded artwork and add an option to override it (larger/external). I'll take a look at FLAC/M4A embedded artwork while I'm in there too, not sure what the situation might be there.
It'll be a couple days before I have time to work on this as I don't have a Windows machine ready to go right now.
Thanks for bringing it up with a detailed report.

No problem, take your time. Thank you for taking the time to make this, I couldn't find any other foobar miniplayers that stayed on top of full screen applications. Only other option would've been a klutzy custom layout for foobar that I would have to switch back and forth between while toggling foobar's "Always On Top" setting.

No problem, take your time. Thank you for taking the time to make this, I couldn't find any other foobar miniplayers that stayed on top of full screen applications. Only other option would've been a klutzy custom layout for foobar that I would have to switch back and forth between while toggling foobar's "Always On Top" setting.

Oh, and one WMA file as well lol. It's weird, removing "folder.jpg" from my big "mixed" folder did get all of the MP3s in there to start showing their embedded art correctly.

Oh, and one WMA file as well lol. It's weird, removing "folder.jpg" from my big "mixed" folder did get all of the MP3s in there to start showing their embedded art correctly.

Hi, sorry, I had some delays getting around to this issue.
I've just uploaded a release (0.1.0) that should address the issues you mentioned. It has some extra bits I wanted to add too, there's a full changelog on the release page. I've only done minimal testing on my own machine so please let me know if you have any issues with the release.
I managed to get FLAC album artwork loading. I didn't readily find any M4A/WMA files with attached artwork in my collection so there is probably still an issue there. If you could provide some sample files I'll have a go at getting them working too.
Thanks

Appears to be fixed, at least on the first problem FLAC file I ran across!

Lucked into an M4A file that isn't working:

https://www104.zippyshare.com/v/w3gESWQH/file.html
Had to give the config.ini a quick and dirty edit. I've got a 1280x800 screen and it was drawing it somewhere outside it by default.

Thanks, I've updated the position value in the release. I'm getting a 403 (forbidden) error from link, could you upload it to a different host?

Strange, never had that issue with Zippyshare before.
mega.nz

That one's working, I'll try to get an updated release out tomorrow

Hi, there's a release up with M4A support now. Please let me know if there's any issues with it.


Update SDK Version in dist folder after versioning happens [ALT-367]

Purpose
https://contentful.atlassian.net/browse/ALT-367
This issue was happening because the sdkVersion.ts file was being updated in a prepare script, which happens before the build. This is before the new version of the SDK is known, so the old version was being compiled into the dist folder.
We don't know what the new version will be until later in the CI/CD pipeline, when lerna publish runs. However, the code that gets published already has the out-of-date version in it.
Approach
Added a postversion script to the sdk package that runs a js script that searches through the compiled dist folder for any SDK_VERSION assignments and replaces the old version number with the new one.
This script runs after lerna versions the packages, but before publish.
Also fixes ALT-790 by adding the exact flag to the publish command on prod builds, which ensures the deps referenced from the monorepo use the exact versions.

Hey @elylucas, I checked in the colorfulful-coin-eb project, node_modules/experiences-sdk-react/package.json have the latest version. But in sdkVersion.ts -> SDK_VERSION is not updated. Instead of injecting the version using process.env.npm_package_version. How about we do this
src/sdkVersion.ts
import { version } from '../package.json'

export const SDK_VERSION = version;

This will get us the latest version from package.json which lerna has updated itself before publishing. e.g commit like this
What are your thoughts?

Sorry we tried this approach but it didn't work either.
Hey @elylucas, I checked in the colorfulful-coin-eb project, node_modules/experiences-sdk-react/package.json having the latest version. But in sdkVersion.ts -> SDK_VERSION is not updated. Instead of injecting the version using process.env.npm_package_version. How about we do this
src/sdkVersion.ts
import { version } from '../package.json'

export const SDK_VERSION = version;

This will get us the latest version from package.json which lerna has updated itself before publishing. e.g commit like this

Thanks Anwar. I've updated the PR with a solution, and tested it well through a pipeline and it appears to work well. I used the postversion lifecycle script you mentioned and that provided a bit cleaner solution than breaking a part the lerna version and publish scripts.


soil profile (Aida's work) and evaluation metrics

Addition of two new soil profiles (Aida's work) and activation of evaluation period command.

soil profile (Aida's work) and evaluation metrics

@Zeitsperre Seems to be a problem with the netcdf build. No objection pulling 3.7 from the suite if that simplifies things.

I believe it's this issue here: https://github.com/Unidata/netcdf4-python/issues/1179. The wheel is bad on PyPI. I can add the fix for it in here at some point.

@huard Python3.7 is rapidly approaching end of life, so let's do that and see if the issue stems from there. I'm going to drop it in another PR.


Issue/1888 remove depracated option variable iso5

Description
add a changelog deprecation note stating the deprecation of Jinja's is defined for nullable attributes
closes #1888
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso5 in ab3ac0184a17d4c47c973541090b76ca6d0a6dca


OpenAI models not working with truthfulqa_* tasks

After following the instructions from the README, when I run the command to evaluate either a completion or a chat model, I get the following issues.
1. openai-completions with gpt-3.5-turbo-instruct:
lm_eval --model openai-completions \
    --model_args model=gpt-3.5-turbo-instruct \
    --tasks truthfulqa_de_mc1

Causing:
openai.BadRequestError: Error code: 400 - {'error': {'message': "Setting 'echo' and 'logprobs' at the same time is not supported for this model.", 'type': 'invalid_request_error', 'param': 'echo', 'code': 'invalid_parameter_combination'}}

2. openai-chat-completions with gpt-3.5-turbo:
lm_eval --model openai--chat-completions \
    --model_args model=gpt-3.5-turbo \
    --tasks truthfulqa_de_mc1

Causing:
NotImplementedError: No support for logits.

Maybe I'm misunderstanding here something, but I would think that the logits should not be relevant for the multiple choice versions from truthfulqa.

For openai-completions, if we remove the echo parameter from the request:
response = oa_completion(
                client=self.client,
                model=self.model,
                prompt=inps,
                max_tokens=None,
                temperature=0.0,
                logprobs=10,
                seed=self.seed,
            )

and then remove the filtering of the echoed original prompt:
def get_result(response, ctxlen: int) -> Tuple[float, bool]:
    """Process results from OpenAI API response.

    :param response: dict
        OpenAI API Response
    :param ctxlen: int
        Length of context (so we can slice them away and only keep the predictions)
    :return:
        continuation_logprobs: np.array
            Log probabilities of continuation tokens
        is_greedy: bool
            whether argmax matches given continuation exactly
    """
    is_greedy = True
    logprobs = response.logprobs.token_logprobs
    continuation_logprobs = sum(logprobs)

    for i in range(len(response.logprobs.token_logprobs)):
        token = response.logprobs.token_logprobs[i]
        top_tokens = response.logprobs.top_logprobs[i]
        top_token = max(top_tokens.keys(), key=lambda x: top_tokens[x])
        if top_token != token:
            is_greedy = False
            break

    return continuation_logprobs, is_greedy

We have a working version for one of the prediction types again.

Should it be merged?

Thanks @djstrong for addressing this!

@haileyschoelkopf Unfortunately, it does not work. Log probs can be returned only for generated tokens. Current implementation calls for every answer questions: answer_i with max_gen_tokens=0.
My understanding of current openai API is that openai models can not be tested with loglikelihood tasks. At most, we can ask for completion for question:  and hope that in 5 top completions is an answer.

It should help :)


DSMN add result stats to network table

To make sure the information (metabolites not in database, metabolites not connectable, metabolites connected) is stored in the session

Updated the results panel to work for Wikidata, and mapped entries alike.