Add logger and verbose mode

[ ] Add Python's logger for proper logging.
[ ] Convert all or most print statements to appropriate level (e.g. Info) logging statements
[ ] Add -v and --verbose arguments for verbose mode.
[ ] Only output info type messages in verbose mode

Please merge my PR to fix the first bullet point of your list.
thanks :)

Hello,
I will try to do this...
I just have one question. What does the last point means?
Does it means in verbose mode we need to output every messages including info type messages?
Or does it mean in verbose mode we must output info type messages only?
Sorry if the question seems stupid but I was not sure about this element.

The Verbose mode would display log messages up to Info level (i.e. not display any Debug level messages). More info in the official Python3 logging docs and here: https://docs.python.org/3/library/logging.html

Oh 🤭, I forgot there were a Debug Mode. Thank you for your answer.
I went to the second link, it seems it's an interressant website.
I will try to make a first pull request. Thank you for your help.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1964

Questions ?
Please refer to the Backport tool documentation


Decide on pipeline

I think the most prominent options for now are Dada2 and Qiime. If there will be an initial release Qiime 2 will also be interesting.

Since there is already the Alm Qiime pipeline we will concentrate on dada2 and friends for now.


Link error

with --import-builtin trying to build this program gets me undefined symbols:
Undefined symbols for architecture arm64:
  "_Pointers.945.Pointer.unsafe#925.let", referenced from:
      _Pointers.945.test#942 in Pointers.o
ld: symbol(s) not found for architecture arm64

public type Pointer<Pointee> {

  var base: Builtin.ptr

  memberwise init

  public property unsafe: Pointee {
    yield base as* (remote let Pointee)
  }

}

fun test(p: Pointer<Int>) {
  var x: Int = p.unsafe.copy()
}

public fun main() {}

The problem probably occurs during the depolymorphization pass, since removing the generic parameter from Pointer makes the link issue go away.


wait_for_everyone() and other features of Accelerate do not function without shared memory

System Info
- `Accelerate` version: 0.21.0
- Platform: Linux-5.15.0-76-generic-x86_64-with-glibc2.31
- Python version: 3.10.11
- Numpy version: 1.25.2
- PyTorch version (GPU?): 2.0.1+cu118 (True)
- PyTorch XPU available: False
- PyTorch NPU available: False
- System RAM: 393.40 GB
- GPU type: NVIDIA RTX A6000
- `Accelerate` default config:
        Not found

Information

[x] The official example scripts
[x] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[x] My own task or dataset (give details below)

Reproduction
The above system works, but an equivalent system and environment with the only difference being the kernel version, meant that Accelerate will hang.
I'm not skilled enough in this space to trace down what happens, but really the lack of shared memory in the 5.4 version kernel seems to bring this on.
Using simple multi gpu setup with 2 A6000s and Stable Diffusion 2.1.
Expected behavior
Accelerate should properly have the main_process_first() move on to the child threads.

I should add, it freezes as well with prepare() when you get rid of all the other state tracking/blocking decorators.

yes, unsolved.

Could you please provide the code leads to the hang?

https://github.com/bghira/SimpleTuner/blob/main/train_sdxl.py < this is where it occurs for SDXL
https://github.com/bghira/SimpleTuner/blob/main/train_sd21.py < this is the SD 2.x trainer that caused the problem
it's actually really frustrating. i found some other issues that caused the hang, where the dataset is improperly partitioned between processes - eg. the dataset ends up imbalanced with a few entries short on one process that caused it to move to the next epoch rather than do a backward pass. meanwhile, the other processes that had more (the "correct" amount of data) did not move to the next epoch.
it's hard to reproduce, even with the same codebase and kernel version. some of the 5.4 systems work correctly. but they are just, very slow. other times, it just waits forever - and then NCCL timeout.

This seems like a really tough issue to debug. Kernel version 5.4 are the GA kernel for Ubuntu 18.04 and 20.04 LTS for another 13 months before EOL, so it would be nice if this worked, but it's also relatively old at this point. Do you have a hardware setup that doesn't allow a newer kernel version to be used?

nope - and i would be okay with just a warning being emitted. is that good for you?

Do you mean a warning that checks for the Linux kernel version?

yes

I see. We could check platform.uname().release on startup and give a warning if the version is < 5.5. WDYT?

yeah i would have gone for <5.15 but <= 5.5 also works too. that (5.5) was a non-LTS kernel anyway. that said, i don't have access to 5.10 systems to test, either.

@bghira I do all my tests with Accelerate on 5.10 so I know that works :)

that covers all bases then. for my perspective, i was just thinking there were other issues in my code that caused this. i would comb through everything, and then ran it in debugger and found that it was all waiting on shared memory. upon further inspection, the Docker runtime complains at startup that the kernel lacks the proper shared memory config, and there's POSSIBLY a way to check /proc/config.gz for this info but i don't know what that is. a warning would at least alert the user that their kvers is likely to blame. thank you!

I've been going nuts with random NCCL timeouts for a long time and I just saw this issue. I'm on a university cluster with kernel 4.18. I reported this to the cluster administrators but seems very unlikely they will upgrade. Does anyone have any workaround or tips on how to avoid or minimize these issues?

(I'm the HPC cluster admin @miquelmarti mentioned).

but if I read this correctly

What the kernel devs do isn't at all relevant to what distros decide to take on (and what security fixes they backport; they backport a lot).  RHEL8 (4.18 kernel) is EOL in 2029 (even Ubuntu offers their extended support for 5+5 years; technically 14.04.6 isn't EOL yet ).
Even leaving aside what hardware vendor supports when building HPC systems (firmware, infiniband, drivers, cluster filesystem support etc), swapping out the OS means redeploying the entire cluster, rebuilding thousands of software packages, probably dropping support for the oldest versions (which might be in active use by many other researchers). This might happen once in the lifetime of a HPC cluster.
I'm curious about  this supposed bug in the kernel though, because

the lack of shared memory in the 5.4 version kernel

shared memory is absolutely not a new thing in 5.5. It's been around for.. well forever, and is of course used all the time by frameworks like NCCL, MPI/UCX/UCC all the time.
I suggested Miquel start by testing out testing some environment variables like disabling shm in NCCL just to see if the problem can be isolated.
And depending on what one might glean from that, look into debug files and/or profiling the application with Scalene and NVIDIA Nsight
Given the use of docker mentioned in the comment, and the fact that HPC schedulers like SLURM also uses cgroups for resource management (no HPC clusters use docker), I'm tempted to think there is a cgroups interplay here.  I'm really curious as to what the exact errors were here:

@bghira
upon further inspection, the Docker runtime complains at startup that the kernel lacks the proper shared memory config

if you want the Redhat backports to work for you, it'll have to be Redhat (or the vendor) that updates the kernel. those kernels are bad news. they've got too many poorly backported fixes, because redhat can't test every possible combination of software. I would not be surprised if zero pytorch loads run on those test boxes.
did you know Redhat doesn't support NVIDIA? that's something you have to get through nvidia-specific support entitlements. any issues between the Redhat kernel and NVIDIA, you're on your own.
as it is, we had to completely forego the Redhat patched kernel series because all the way up to 5.15 it is simply broken for more than one use case. the shared memory hangs are due to incorrectly backported fixes.
getting them to fix it wasn't something my team wanted to spend time on. instead, we switched the fleet to Ubuntu 22.

hey there, does this issue really find the root cause? we are actually getting this error all the time:Detected kernel version 4.15.0, which is below the recommended minimum of 5.5.0; this can cause the process to hang. It is recommended to upgrade the kernel to the minimum version or higher., but sometimes it wait for the train to be started. depending on the data loading. but no hang at all.

you really need to upgrade your kernel..


Add keyring-util

Fixes: https://github.com/bilelmoussaoui/oo7/issues/48

Regarding search and lookup, one could do get and list instead.

Looks good to me! I have one suggestion though and I'm not sure it's possible to implement. It would be great if keyring-util can handle a scenario like the following,
 ./target/debug/keyring-util store 'My password' key1 value1
Error: The collection 'default' doesn't exists

So, we need a new command to create a keyring or collection. What do you think @A6GibKm ?

I would check first what is the behaviour of secret-tool in this case. Collections are not widely used so maybe we should automatically create the default collection if it doesn't exists?

Looks good to me! I have one suggestion though and I'm not sure it's possible to implement. It would be great if keyring-util can handle a scenario like the following,
 ./target/debug/keyring-util store 'My password' key1 value1
Error: The collection 'default' doesn't exists

So, we need a new command to create a keyring or collection. What do you think @A6GibKm ?

I would check first what is the behaviour of secret-tool in this case. Collections are not widely used so maybe we should automatically create the default collection if it doesn't exists?

For the moment I will just create one if needed.

Looks good to me but still lacks CI bits :)

Could you please take care of this? I have yet to understand how github CI works.


Add link to legacy address page for checking unlocking graph

We've gotten reports from some users who seem confused as to whether they've unlocked all of the STX that should be unlocked by now. I've generally found it helpful to cross-check the graph we have on the legacy Explorer's address page to confirm whether the information shown on the new Explorer is correct.
Adding a link to the legacy address page with a note about how it can be used to cross-check the unlocking status might help clarify things for users who'd otherwise mis-calculate just how much they should have unlocked already:

ℹ Expecting different amounts here? View unlocking graph on the legacy Stacks Explorer to examine unlocking events by date

cc @GinaAbrams @ryanarndtcm

This would be a good interim help solution for sure. RE: Comment in Discord, I think we'll have even more luck showing this link in the wallet.

Could we add a version of the unlocking graph into the new explorer?

Yep, @GinaAbrams mind creating a separate issue for that request?

yep added a new one.

What's the URL of the legacy explorer?

https://explorer.legacy.blockstack.org/

After discussing with the team, it was decided to take these actions:

[ ] for unlocking addresses (or all if conditional not possible):

add link to read more / forum post with info about genesis data dump @muneeb-ali @GinaAbrams
Change copy from total balance to unlocked balance @hstove @markmhx

[ ] Remove available balance @hstove @markmhx
[ ] Hide current unlocked vs. locked component @hstove @markmhx
[ ] Open an issue for DevOps to redirect from the legacy to the new explorer @markmhx


refactor this

https://github.com/grahamwaters/mkyNetwork/blob/7bb88a0103df378f3b88b74787beffa742820a36/scripts/mkyBanker.js#L131

There are a few ways that you could refactor the Reg2Transaction class:
You could refactor the saveTransaction function to use a prepared statement with placeholders for the values being inserted. This would help to prevent SQL injection attacks, and would make the code more readable.

You could consider refactoring the saveTransaction function to use a Promise, which would allow you to use async/await syntax and make the code more readable.

You could consider refactoring the confirmAndSave function to use a Promise, which would allow you to use async/await syntax and make the code more readable.

You could consider refactoring the getWalletPubKey function to use a Promise, which would allow you to use async/await syntax and make the code more readable.

You could consider refactoring the calculateHash function to use a Promise, which would allow you to use async/await syntax and make the code more readable.

You could consider refactoring the Reg2Transaction class to use a more modern JavaScript syntax, such as class fields and arrow functions. This would make the code more concise and easier to read.

You could consider refactoring the Reg2Transaction class to use modern JavaScript features such as the spread operator, which would make the code more concise and easier to read.

You could consider refactoring the Reg2Transaction class to use modern JavaScript features such as destructuring, which would make the code more concise and easier to read.

You could consider refactoring the Reg2Transaction class to use modern JavaScript features such as template strings, which would make the code more concise and easier to read.

You could consider refactoring the Reg2Transaction class to use modern JavaScript features such as the for-of loop, which would make the code more concise and easier to read.


Issue 914

Issue
Fix : https://merative.atlassian.net/browse/MERATIVE-914
Test URLs

Before:

https://main--merative2--hlxsites.hlx.page/support/curam
https://main--merative2--hlxsites.hlx.page/support/micromedex

After:

https://Issue-914--merative2--hlxsites.hlx.page/support/curam
https://Issue-914--merative2--hlxsites.hlx.page/support/micromedex

Description
Issue link: https://merative-my.sharepoint.com/:w:/r/personal/abarcelona_merative_com/_layouts/15/Doc.aspx?sourcedoc={75611843-70d7-4e83-b416-b66141541e34}&action=view&wdAccPdf=0&wdparaid=633D6286
Curam product support: Issue C.
Micromedex product support: Issue C.
Note:
The  changes are generic and affects all the support pages where  "content-text-body" and "short-cards" blocks are used.

@Ajeet-Nellikeri
Only the spacing between the bullet points should be 8px.

CC: @keith-kaplan

@sachinmesh - Spacing between the bullet points to be 8px in Micromedex fixed


Error when trying to launch debugger

I shake my phone to open dev tools and I click on debug to open the debugger in firefox and then I have 2 errors:
TypeError: cannot use the given object as a weak map key index.delta:42125:11
Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
Impossible to find a solution on others issues.
react-native info:
System:
   OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
   CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
   Memory: 1.48 GB / 7.68 GB
   Shell: 5.0.3 - /bin/bash
  Binaries:
   Node: 10.15.2 - /usr/bin/node
   npm: 5.8.0 - /usr/bin/npm
  SDKs:
   Android SDK:
    API Levels: 23, 25, 28, 29
    Build Tools: 28.0.3, 29.0.2
    System Images: android-28 | Intel x86 Atom_64, android-29 | Intel x86 Atom_64
  npmPackages:
   react: 16.9.0 => 16.9.0
   react-native: 0.61.1 => 0.61.1
  npmGlobalPackages:
   react-native-cli: 2.0.1

Do you get it on an empty app?

no, it works well on an empry app.
After creating a new project and installing all tha packages one by one, it seems that is react-native-firebase that is the problem. I do not have any error, just crashing when turning on debugger...

I think you should post this under their repo then. Maybe try using Chrome instead of Firefox.


Clean.log

Is there a reason this wasn't done in #1776?

Separation of concern? I thought it would be right thing to make separate pull request for this.

Could you redo it on a fresh branch, then? I was reacting based on the "granular update" commit.

clean.log is separate branch. :)

Did you mean to include this commit in granular.update branch?

@ludbek No. I mean redo the changes against a branch taken from next rather than your local granular.update feature branch.

Basically, this:
git checkout next
git branch -d clean.log
git checkout -b clean.log
# redo `console.log` removals
git push -fu origin next


Add WayneWayner as genesis validator

Previous PRs:
https://github.com/anoma/namada-testnets/pull/84
https://github.com/anoma/namada-testnets/pull/352

Can someone please rerun the check? Looks like the issue were some non toml files of other folks which have been merged.

Seems like closing and opening the PR triggered Github to rerun checks :+1:


Splitting full site annotation in 4.image-and-segmentation-qc

This code block is giving me some trouble:
https://github.com/broadinstitute/pooled-cell-painting-profiling-recipe/blob/068c7eae79f56a50732fdf173902dc596c95ce3f/0.preprocess-sites/8.image-and-segmentation-qc.py#L202-L204
A couple notes:

Is the site_full always going to be coded in this way? i.e. Plate, then Well, then Site?
I've already encountered when site_full is not split by - (in a separate experiment, we delimit by underscore)

So, this is a very fragile way of handling this split. A couple of solutions:

We always output site_full with the same convention - this is still pretty fragile, since most scientists will forget the standard)
We somehow propagate plate, well, and site number information earlier and do not rely on this split at all. Is this info in the Image.csv file in a seprate metadata column already?

@ErinWeisbart - we should either resolve this or drop this before version 0.1

The way that we have our CellProfiler analysis pipeline currently set, the answer is yes, the output is always Plate_Well_Site (so site_full will always fit that split). It is possible one could change that part of the CellProfiler pipeline (there would be no reason for Beth or I to do so at this point).
In the Image.csv there are Metadata_Plate, Metadata_Well, and Metadata_Site columns so we can pull from those columns instead. It is not true that we don't use this split elsewhere - it is in 7.visualize-cell-summary.py as well.
We could move the Image Dataframe creation to 7.visualize-cell-summary, save it there and import that file into 8.image-and-segmentation-qc instead of recreating it? Is this something you'd like me to do?

We could move the Image Dataframe creation to 7.visualize-cell-summary, save it there and import that file into 8.image-and-segmentation-qc instead of recreating it? Is this something you'd like me to do?

This is great to know - given that I have built up some momentum, I will take care of this (I also have some example data that you sent). I think the best use of your time in this project now is reviewing the PRs and checking my logic. We are close to 0.1!

Having trouble finding which column to use in image.csv - maybe I am looking at the wrong file?
The only metadata columns I see in this file are:

Metadata_FileLocation
Metadata_Frame
Metadata_Series
Metadata_Site
Metadata_TopFolder

0
0
Site_1
CP074A_A1

Is this all the info I need? It still seems a bit dangerous to split off Metadata_TopFolder. I will keep digging and post what I find here.

We processed CP074A differently. So yes, it used TopFolder but CP151 and all future batches use Plate, Well, and Site.
I suggest you switch to using data from a plate of CP151 for building/testing v.1 as it is slightly different in many ways from the batches of CP074 and before.

cool - so the columns in image.csv will be Metadata_Plate, Metadata_Well, and Metadata_Site?


Add missing TemplateBindings to CalendarDatePicker

Hi @awxm,
somehow the SelectedDate does not update when the drop down opens. Do you have an idea, why this is the case? In Avalonias FluentTheme v1 it is working well.
Thank you and happy coding
Tim

Closes #68

@timunie Thanks for the PR! I've pushed a fix for the SelectedDate. It was working, but there was a style conflict which kept an element invisible.
I've also added a couple other style fixes I noticed while diagnosing the other issue: the popup is now centered under the main control, I've added an opaque background and added the overlay corner radius to the popup. Unrelated to the missing template bindings, but while I was in that code figured I'd fix it while it was fresh on my mind

Hi @amwx
thank you for your support. I'd have never figured this out. Now everything seems to work fine, so I marked this PR as ready
Have a great weekend & Happy coding
Tim


Svelte implementation of NFT

Before the hackathon would be great to have basic UI with Svelte or it could be done over the hackathon

[ ] minting
[ ] explorer
[ ] profile
[ ] item detail
[ ] collection detail
[ ] that's it, that's issue.

Continue to #2517


It's possible to get all the stories of a specific highlight?

Form

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Question
I know that it's possible to get all the stories of highlights, but, it is possible to get all the stories of a specific highlight?
Actually i'm getting the highlights by this way:
const tray = await ig.highlights.highlightsTray(userId);
const highlights = await ig.feed                 .reelsMedia({ userIds: tray.tray.map(x => x.id) })                 .items();
Thanks for reading.

You can just pass one specific id to the reelsMedia call:
const { tray: [ first ] } = await ig.highlights.highlightsTray(userId);
const items = await ig.feed.reelsMedia({ userIds: [first.id] }).items();


change: more machine refactors

Updates minecraft to 1.16.4
Large changes, mainly in networking and GUIs.

I configured the repos like that for speed - it makes it so that we only query the one repo for every dependency, rather than all of them (worst case).

I configured the repos like that for speed - it makes it so that we only query the one repo for every dependency, rather than all of them (worst case).


Update documentation in Mapper.kt

Fix input/output in the documentation, were written on the wrong parameter

Build failed as licenses are not being accepted, if the author would like to update the .travis.yml file it would be great


Model loading error

When I run bash run.sh for evaluation，there is a error happened：
Traceback (most recent call last):
File "./main.py", line 179, in
_main(args)
File "./main.py", line 68, in _main
net = _load_model(args)
File "./main.py", line 31, in _load_model
net = get_infer(args)
File "/remote_projects/cavaface/evaluation/infer/init.py", line 8, in get_infer
return CitrusPytorchInfer(args, dtype=dtype)
File "/remote_projects/cavaface/evaluation/infer/citrus_pytorch_infer.py", line 20, in init
super(CitrusPytorchInfer, self).init(args=args, dtype=dtype)
File "/remote_projects/cavaface/evaluation/infer/citrus_base_infer.py", line 260, in init
self._load_model()
File "/remote_projects/cavaface/evaluation/infer/citrus_pytorch_infer.py", line 37, in _load_model
tnet.model=torch.jit.load(spath[0], map_location=tnet.ctx)
File "/root/anaconda3/lib/python3.7/site-packages/torch/jit/init.py", line 221, in load
raise ValueError("The provided filename {} does not exist".format(f))
ValueError: The provided filename /workspace/results/lyb_results/IR_SE_100_Arcface/model_ep24_1.pth does not exist
Can you help me about that？

please set model path properly

please set model path properly

Is this path a local path? Do I need to download the model in advance？Thanks.

please set model path properly

谢谢。我暂时登录不了google云盘，可以提供一下百度云或是其他的路径吗？

I got it, Thanks.


Add checking code

Coverage remained the same at 29.39% when pulling f297bc76ca38dc22d3fe10d3b5610a5b34b62f6a on qingweibinary:qingwei/fix_mobile into acc293cbf428939d2ca62338598afcb37518148f on binary-com:master.


Suport JSX (react) notation

The coffeelint's doc points to use coffee-react-transform, however it miss features and is deprecated. And, as the coffeelint's doc says, transformers may mess with the original source format.
Supporting JSX, coffeelint could test indentation of nested tags, line spliced tags, and more...

Vows test:
    topic:
        '''

            {value}

        '''

    'do not missunderstand JSX': (source) ->
        config = { spacing_after_comma: { level: 'error' } }
        errors = coffeelint.lint(source, config)
        console.log errors

Outputs:
[ { name: 'spacing_after_comma',
    level: 'error',
    message: 'a space is required after commas',
    description: 'This rule checks to make sure you have a space after commas.',
    lineNumber: 1,
    line: '
',
    rule: 'spacing_after_comma' },
  { name: 'spacing_after_comma',
    level: 'error',
    message: 'a space is required after commas',
    description: 'This rule checks to make sure you have a space after commas.',
    lineNumber: 1,
    line: '
',
    rule: 'spacing_after_comma' } ]

Why it matches spacing_after_comma in a JSX tag notation?


Add option to disable resource cache

We want an option to be able to turn off the resource cache for use in tests

Thank you all :)


chore(build): add workspace and public API controls to ensure compliance with project policies.

Two controls are implemented in this PR.

Public APIs are controlled with cargo-check-external-types (see #21).
Each crate in the workspace must complies with the following set of project policies.

Crate name starting with weaver_
Presence of a README.md file
Presence of a allowed-external-types.toml

Is it too early to enforce non breaking changes?
Overall looks good

Yes, it's too early. Once we have an approved Application Telemetry Schema (conceptually, components and resolved parts), then we should consider enforcing non-breaking changes.


Fix bug with calibratable parameters and add new parameters

Add calibratable parameters and fix bug with previous implementation.
For now, these parameters are working: maxsmc, satdk, slope, b, Klf, Kn, Cgw, expon, satpsi,wltsmc
These parameters did not pass the test and will be implemented in a second PR:    max_gw_storage,alpha_fc,refkdt, a_Xinanjiang_inflection_point_parameter,b_Xinanjiang_shape_parameter,x_Xinanjiang_shape_parameter, N_nash
Since this PR is already pretty large, I decided to send for review before adding the other parameters.
ngen updates the parameters (based on the realization file or calib config file) after the initialize function. However, many of the parameters are already used within the initialize. That cause a bug for few of the parameters in previous implementation.
I tested the implementation within ngen the following way:
Run 1: Run current version, with original configuration file
Run 2: Run the version in this PR, with original configuration file
Run 3: Run the version in this PR, with modified configuration file (change the param in the config file)
Run 4: Run the version in this PR, with original configuration file and modified realization file (change the param with ngen)
Modifications are okay if:

Results from Run 1 = Results from Run 2 - guarantee we did not change the results
Results from Run 3 = Results from Run 4 - guarantee the model parameters were correctly changed by ngen, and the CFE results are the same if the parameter was changed in the config file or through the realization file.

Additions
Modifications were made to the code to guarantee all parameters are correctly exposed. For example, the parameter alpha_fc and rfkdt were used within the initialization and not exposed to the CFE structures. I had to add them so I could modify them through calibration.
Also modify Set_value_at_indices to re-run some of the functions that are run within initialization (init_soil_reservoir)
Removals
Removed the parameters from the previous implementation that did not pass the test.
Testing
Described above.
Todos
Include the other parameters that did not pass the test.
Checklist

[ x] PR has an informative and human-readable title
[ x] Changes are limited to a single goal (no scope creep)
[ x] Code can be automatically merged (no conflicts)
[ x] Code follows project standards (link if applicable)
[ x] Passes all existing automated tests
[ x] Any change in functionality is tested
[ x] New functions are documented (with a description, list of inputs, and expected output)
[ x] Placeholder code is flagged / future todos are captured in comments
[ x] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ x] Reviewers requested with the Reviewers tool

This needs to be revisited before extensive calibration work continues.  @xfeng2021 @lcunha0118 @mattw-nws

@lcunha0118 Is your initial comment up to date?

For now, these parameters are working: maxsmc, satdk, slope, b, Klf, Kn, Cgw, expon, satpsi,wltsmc

These parameters did not pass the test and will be implemented in a second PR: max_gw_storage,alpha_fc,refkdt, a_Xinanjiang_inflection_point_parameter,b_Xinanjiang_shape_parameter,x_Xinanjiang_shape_parameter, N_nash
Since this PR is already pretty large, I decided to send for review before adding the other parameters.

@SnowHydrology After I put the PR description, I kept sending new commits. All parameters have been included. All parameters, with exception of the "Number of Nash reservoirs", have been fully tested.

Thanks @lcunha0118. That's what I was guessing, but I figured I should double-check before reviewing.

@xfeng2021 Tomorrow AM provided there aren't any major issues!

Can we get the merge conflict resolved?  I would like to carefully look through any potential variable side effecting that may go on between initialization and set_value, but until the conflict is resolved, that might be a foolish effort?

Can we get the merge conflict resolved? I would like to carefully look through any potential variable side effecting that may go on between initialization and set_value, but until the conflict is resolved, that might be a foolish effort?

Yes to the merge conflict, but I don't believe that will affect the undesired behavior of derived parameters. I.e., in our current configuration, you shouldn't run set_value on derived parameters or their constituent parts unless the derived parameter is calculated as a function of said parts beforehand. Such parameters cannot be varied randomly independent of one another.

Notes on the resolved merge conflict for future reference: I defaulted to the master for conflicts 1 & 3, which both involved enumerated entries (var_info[] and ptr_list[...]). The only change I made to the master code was to rename num_lateral_flow_nash_reservoirs to N_nash as in @lcunha0118's code. For conflict 2, I accepted the change from @lcunha0118.

@hellkite500  Agree with code re-use, but also did not want to change how the initialize was wrote by the code author. But a function would make sense.


Bug: No control over culture for string formatting

In my code, I have a SymbolicExpression Function, which when given specific values, the result is infinity.
As an example:
using Expr = MathNet.Symbolics.SymbolicExpression;

Expr Function(Expr symbol, Expr function)
{
  return function.Substitute(symbol, 2*symbol);
}

var x = Expr.Variable("x");
var result = Function(0, 1/x);

Console.WriteLine(result.ToString());

The expected result here is infinity, however, in console, this is displayed as "8".
See the following thread for more information.
Typically, in the general sense, you can use something like the following to remove the issue of these semantics:
var f = Function(0, 1/x);
var result = string.Format(CultureInfo.InvariantCulture, {0}, f);
Console.WriteLine(result);

This changes the output to "infinity", removing the issue.
However, MathNet.Symbolics seems to not allow this to happen, which I suspect is due to oversight deeper in the code. A resolution would potentially be:
var result = Function(0, 1/x);
Console.WriteLine(result.ToString(CultureInfo.InvariantCulture));

Symbolics is not relying on string.Format but instead intentionally and explicitly formats some special symbols with Unicode characters - not just for infinity, but also complex infinity and also pi. It can parse them accordingly as well, so this is a feature really.
Do I understand it correctly that the problem appears when using legacy raster fonts instead of true type fonts? According to the thread this seems to be the root problem (for some code pages), rather than the encoding by its own?


Atom error on first startup

Atom does not load correctly the first time I try to open it.
It seems to load correctly the second time I open it.

I'm using Windows 10 x64 and Atom version 0.146.0.

Atom version 0.146.0

That's a super old version of Atom. Do you see the same problem in the latest version, 1.0.7?

Oh I upgraded to the latest version and seems fixed now, thanks.


Build spec file not being overriden

So i added my configured amplify.yml to the root of my repo. But amplify isnt using that one

Hi @BCupen can you please open a new issue using the issue template so we can collect basic details to help us investigate:
https://github.com/aws-amplify/amplify-console/issues/new?assignees=&labels=&template=1.bug_report.yaml
Closing this one for now


change alignment check algo

Now we can use alignment values larger than required by the type 😊

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a6ee194) 93.33% compared to head (db40b2c) 93.33%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   93.33%   93.33%
=======================================
  Files           1        1
  Lines          30       30
  Branches        3        3
=======================================
  Hits           28       28
  Partials        2        2

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


fix: add ssh-agent socket support in programs.ssh.startAgent

Also add SSH_AUTH_SOCK SSH_AGENT_PID to the service. SSH_AUTH_SOCK is referenced for the socket location on ExecStart and ExecStartPre.
I'm a week-old nix user so a good set of eyes is appreciated.
Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/831

Will give it a try.

Is there any way to bring priority to this?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3978

@acid-bong @pbsds @SuperSandro2000 @sigprof

Please rewrite the git history to remove the merge commit, and fix the merge conflic

Does this actually work?
Apparently the upstream OpenSSH does not have any systemd support at all, and features like systemd service state notifications and socket activation support are added in distro-specific patches (e.g., see https://salsa.debian.org/ssh-team/openssh/-/tree/master/debian/patches, in particular systemd-readiness.patch and systemd-socket-activation.patch).  However, I don't see any patches like that in the Nixpkgs package for OpenSSH.
Also the systemd-socket-activation.patch mentioned above handles socket activation only for sshd and does not make any changes to ssh-agent.  There was an attempt to add socket activation to ssh-agent, but the patch was rejected by the OpenSSH upstream due to the libsystemd licensing.  Some other patches can be found in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068416, but they had not been accepted in Debian yet.
So it looks like adding the systemd socket activation support to the NixOS module for OpenSSH won't work until the corresponding code is added to the actual openssh package.


ConfigurationOptions is checked for equality when checking ConfigurationNode equality

It seems to me that there isn't a particular reason for this. If someone is checking for ConfigurationNode equality they're almost always intending to check when the values are equal and (to a lesser importance) if the keys are equal.
In my opinion, loader.load().equals(loader.load()) should be able to return true, and yet it doesn't. Given how ConfigurationOptions are created, equals may as well literally be a == check.

Yes, equality shouldn't account for options.
blood and I ran into this issue a few weeks ago, but I never got around to committing a fix. Feel free to PR :)

Just wanted to make sure I wouldn't be wasting my time if I did. I'll hop right on it.


Wrong implementation of K1 rule

You're using naming convention to check both K1 and K2 at the same time, while K1 should be checked basing on if there's a dimension that has a primary key attribute set to yes

Hi!
This is by design. If you're interested in checking for the existence of primary_key: yes, I could add an example of doing this via custom rules.
However, these are the reasons I didn't do so in the default rules:

functionally, primary_key: yes just enables symmetric aggregates, which I usually suggest avoiding if possible
when there is more than one primary key column, the pk{n}_ naming convention and the primary_key:yes attribute would disagree about which dimensions are the primary key dimensions

@fabio-looker Can you give an example of how to check existence of primary_key?

Hi @jmak123 - to make this kind of rule easier to implement in the expression-based custom rule language, I am going to add a few helper functions for looping through objects - https://github.com/looker-open-source/look-at-me-sideways/issues/45
My hope is to get these added this week

@fabio-looker Thank you! Looking forward to it.

Hi @jmak123 - I sat down to do this today, and realized I had already done it long ago... oops! So I went ahead and made the example you requested as a testcase:
https://github.com/looker-open-source/look-at-me-sideways/blob/master/__tests__/dummy-projects/08-object-iteration-rules/manifest.lkml

Thanks so much @fabio-looker !
One thing though, the custom rule that iterates over dimensions seems to have problems outputting error to CLI.
I get
RangeError: Invalid array length
    at formatArray (util.js:696:18)
    at formatValue (util.js:578:18)
    at Object.inspect (util.js:293:10)
    at Console.dir (console.js:158:14)
    at module.exports (/usr/local/lib/node_modules/@looker/look-at-me-sideways/index.js:181:13)
    at <anonymous>

Hi @jmak123 - I sat down to do this today, and realized I had already done it long ago... oops! So I went ahead and made the example you requested as a testcase:
https://github.com/looker-open-source/look-at-me-sideways/blob/master/__tests__/dummy-projects/08-object-iteration-rules/manifest.lkml

@fabio-looker We're having an issue where this fails if there is a view (say an extends) with no dimensions. Is there a way to handle that in the current implementation?

Hi @jmak123 - I sat down to do this today, and realized I had already done it long ago... oops! So I went ahead and made the example you requested as a testcase:
https://github.com/looker-open-source/look-at-me-sideways/blob/master/__tests__/dummy-projects/08-object-iteration-rules/manifest.lkml

@fabio-looker We're having an issue where this fails if there is a view (say an extends) with no dimensions. Is there a way to handle that in the current implementation?

The LookML parser that LAMS uses does not currently resolve extensions/refinements before LAMS checks its rules, so in general anything that is done via extends is not recognized correctly. As of right now, using an exemption is the only solution. I will try to look for opportunities to work on extensions support in the parser in the future, as this will solve not only this, but a broad set of issues.

@ajbosco
The LookML parser that LAMS uses does not currently resolve extensions/refinements before LAMS checks its rules, so in general anything that is done via extends is not recognized correctly. As of right now, using an exemption is the only solution. I will try to look for opportunities to work on extensions support in the parser in the future, as this will solve not only this, but a broad set of issues.

Thanks that totally makes sense about extensions but what I'm trying to do is just get a rule that can iterate over Dimensions and won't throw a build error if none are present in a view.

Hi @ajbosco - I missed this reply earlier, sorry about that. You can always put in a conditional to guard against empty objects. I made an example here:
https://github.com/looker-open-source/look-at-me-sideways/blob/shortcircuit-example/__tests__/dummy-projects/10-shortcircuit-custom-rule/manifest.lkml


grammar fix

Simple grammar fix. Doesn't affect the content.

@all-contributors please add @LiamSwayne for code


Can't get print mode: custom to work with custom buttons

Describe the bug
When using the custom print button functionality I can't get the print mode: custom to work. It automatically print without letting me select an area. When I use the build in controls, everything is working as it should.
To Reproduce
L.control.browserPrint({
            position: 'bottomleft',
            closePopupsOnPrint: false,
            printModes: ["Portrait", "Landscape", "Auto", "Custom"],
            manualMode: false
        }).addTo(this.map);

And then the following in the custom button:
var modeToUse = L.control.browserPrint.mode.custom();
this.map.printControl.print(modeToUse);

Expected behavior
Should work as when using the build in controls.
Desktop (please complete the following information):

MAC OS
Chrome Version 81.0.4044.129 (Official Build) (64-bit)

Hello,
Thanks for noticing it. It was fixed in last version 1.0.5. Please take a look and let me know if any.
Regards,
Igor

Hi Igor,
I works👍 Thank you for the quick feedback!
Cheers,
Jens


CI for Node

node.js workflow

FAIL test/game.test.js
App
✕ Contains the compiled JavaScript (4 ms)
Game
Game
✕ Initializes with two players (3 ms)
  ✕ Starts the game with a random player

nextPlayer
  ✕ Sets the current player to be whoever it is not


General approach to converting this into a R3F component?

I'm trying to follow along with the code but there are extra modules unrelated to Three.js that I'm unsure if they can be dumped.
Is mocking this up in R3F doable? Perhaps build issues relating to JSX requiring a different setup?
Thoughts?
https://github.com/pmndrs/drei#html

What unrelated modules do you mean?

What unrelated modules do you mean?

Oops, Javascript.js is not a shim file it's a language syntax file for the text editor and Textor is the editor. Didn't quite get that for a second. And ConsoleTexture is the container basically.
And the actual shim file is for import maps which may not even apply given a build process with JSX.
Hmmm the code is actually pretty self explanatory.
A lot of it I can move into functions or hooks outside of the JSX render tree, and hopefully use setState for code content and updates.
I think it's doable. Might not need help. Just don't know if the editor can be fully encapsulated as an R3F drei module, but maybe.
If the world just gained a drop in  oh man.
Gonna try this.

What unrelated modules do you mean?

Oops, Javascript.js is not a shim file it's a language syntax file for the text editor and Textor is the editor. Didn't quite get that for a second. And ConsoleTexture is the container basically.
And the actual shim file is for import maps which may not even apply given a build process with JSX.
Hmmm the code is actually pretty self explanatory.
A lot of it I can move into functions or hooks outside of the JSX render tree, and hopefully use setState for code content and updates.
I think it's doable. Might not need help. Just don't know if the editor can be fully encapsulated as an R3F drei module, but maybe.
If the world just gained a drop in  oh man.
Gonna try this.
EDIT: it just occurred to me that that I may need two servers because authoring in R3F not straight Three.js in the editor will require a build process. Unless perhaps it can someone be done in the browsers entirely (not likely).

And it would need to be a remote session into VSCode so you can reach the terminal. Uh oh.

But then if it is VSCode for Web
https://code.visualstudio.com/docs/editor/vscode-web
How do you render on your side? Would need a tunnel to send updates to session container, but decompiled to raw Three.JS?
Some infinite loop / chicken and egg stuff here.
The entire thing needs to be able to be done in browser, build steps and all.
I think this enters WASM land.
Am I wrong?

Hmmm Babel directly in browser may work.
https://datacadamia.com/web/javascript/react/jsx_browser
Or Preact?
Hope may not be lost.
More research is needed.

OK wrote this up but getting a babel error.
Thoughts?
https://github.com/jeffscottward/R3F-VR-Client/blob/main/index.html
Inline Babel script:5 Uncaught ReferenceError: require is not defined
at :4:14

It works! Mostly...
I had to put imports on the window object to get around an ES6 import bug for babel/standalone.
I found a great  CDN tool for ESM modules because that was being quite a pain. https://esm.sh/
Fun fact: importmap is natively supported now. No more shims.
I filed a bug about the babel issue importing ES6 modules.
https://github.com/babel/babel/issues/15914
And here is the working-ish code
https://github.com/jeffscottward/R3F-VR-Client/blob/main/index.html

Nicely done!
Do you have a live link? 🤔

Nicely done! Do you have a live link? 🤔

Nope but it’s totally copy paste able, static HTML.
And sorry I misspoke, by “working” i mean just generally R3F with the window caveat.
I still need to do the whole conversion of this repo from THREE to R3F 😅. The ESM & Babel hill was climbed though.

imports working!
Babel present env was not needed.
now time to fork and convert the code to r3f.
closing this. will submit a branch PR for r3f, or perhaps a bool flag version for using r3f


Federated token subject claim is incorrect

I am using<EMAIL_ADDRESS>in a GitHub workflow which is being triggered on Pull Request.
However the subject claim is not repo:Azure/Aks-Construction:pull_request as expected. It is using the name of the branch in the claim, eg. repo:Azure/AKS-Construction:ref:refs/heads/ml-windows
Run<EMAIL_ADDRESS>  with:
    client-id: ***
    tenant-id: ***
    subscription-id: ***
    enable-AzPSSession: true
    environment: azurecloud
    allow-no-subscriptions: false
    audience: api://AzureADTokenExchange
  env:
    AZCLIVERSION: [2](https://github.com/Azure/AKS-Construction/actions/runs/4047178860/jobs/6960888343#step:6:2).4[3](https://github.com/Azure/AKS-Construction/actions/runs/4047178860/jobs/6960888343#step:6:3).0
    ParamFilePath: .github/workflows_dep/AksDeploy-ByoVnet.parameters.json
    RESNAME: Byov
    DEPNAME: Dep22[9](https://github.com/Azure/AKS-Construction/actions/runs/4047178860/jobs/6960888343#step:6:9)2
    KVACCESS: IAM
Using OIDC authentication...
Federated token details:
 issuer - https://token.actions.githubusercontent.com/
 subject claim - repo:Azure/AKS-Construction:ref:refs/heads/ml-windows
/usr/bin/az cloud set -n azurecloud
Done setting cloud: "azurecloud"
Error: : AADSTS700[21](https://github.com/Azure/AKS-Construction/actions/runs/4047178860/jobs/6960888343#step:6:22): No matching federated identity record found for presented assertion. Assertion Issuer: 'https://token.actions.githubusercontent.com/'. Assertion Subject: 'repo:Azure/AKS-Construction:ref:refs/heads/ml-windows'. Assertion Audience: 'api://AzureADTokenExchange'. https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation

When i go to the Azure Portal and configure a new federated credential for the branch, it does work as expected - however i shouldn't have to do this. The pull_request claim should be used in preference to the branch name.
I have tried reproducing in a new branch, but it works as expected using the correct subject claim. However you can see from the workflow link that in this branch-workflow run it is using the wrong subject claim.
ref: https://github.com/Azure/AKS-Construction/actions/runs/4047178860/jobs/6960888343#step:6:23

Looks like the action workflow was being triggered through a PR and a PUSH trigger event.
Closing.


homepage now reflex correct component

moved calendar to dashboard

 As a User, I'd like to go to my respective homepage after I log in


[SITE] Try out WF without having to upload a font yourself

...without you needing to find and upload a font first.
For example, add a button saying "Try it with Recursive!" where a copy of Recursive is being downloaded/supplied to the site automagically.

Simple setup: https://github.com/Wakamai-Fondue/wakamai-fondue-site/pull/5


[FEA]: Support ControlMessage data types for inference stages

Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
Currently, all of our inference stages only support using the MultiMessage classes and their children. As we update the Morpheus stages to utilize ControlMessage, the inference stages need to be upgraded as well.
Describe your ideal solution
Ideally, the inference stages would support both MultiMessage and ControlMessage in a single class while we deprecate MultiMessage. However, ControlMessage objects have the additional task settings which area associated with each message. This would be very useful to allow adding an "inference" task to each message which controls properties about the inference on a message by message basis (for example, which model to use). It may make more sense to create the inference stage for ControlMessage as a new class to allow supporting using tasks.
Completion Criteria

[ ] Determine if the existing class should be updated or a new class should be added specifically for ControlMessage types
[ ] Update any batching and logits calculations to support ControlMessage
[ ] Add options to the class constructor to configure a fallback task if one is not attached to the message

[ ] If a message has the inference task attached, it should always default to using those settings for inference
[ ] If a message does not have an inference task, it should use the default task set on the inference stage
[ ] If a message does not have an inference task, and no default was supplied by the user, an error will be thrown

[ ] Update all inference testing to use both MultiMessage and ControlMessage
[ ] Update all documentation related to inference stages to reflect the new supported type
[ ] Compare performance between the two message types to ensure no performance degradation.

Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched the open feature requests and have found no duplicates for this feature request

Superceeded by #1802


Refactor packets

This is an attempt to clean up the packets! macro and packets in general.

[x] Rewrite packets!
[x] Remove Server and Client prefixes from packet names
[x] Look over all packets and fix any wrong types

Some details on what I've changed:

Packet types are namespaced by connection state (handshake/play/status/login) and direction (clientbound/serverbound).
Packets no longer implement Protocol, instead there is a new trait Packet whose decode method takes a packet length argument and decodes only the packet body.
A new type packet::PacketEnum can be used to exhaustively match packet types in the decoder.
A new function packet::read_packet decodes a packet from a reader and returns it wrapped inside a PacketEnum.
packet! has a new form for custom encode/decode implementations.

All of the above happens inside packets!. Additionally:

VarInt and VarLong are renamed to Var<i32> and Var<i64> respectively, without changing their implementations. This way we can easily move to more generic code (and things like Var<u32>) later if we want to.
I have implemented Protocol for State and Option<T> where T: Protocol, and used these types in packets.
I have added a macro proto_structs! for defining struct types used in the protocol and getting the Protocol impl for free. It's pretty much the same as the old packet!.

:+1: :tada:
Packets using Nbt can be enabled too.

:tada:

[ ] No write_packet
[ ] Compression
[ ] No need for Var other than i32 and i64
[ ] Enable packets using Nbt

No write_packet
Compression

I think this can wait for a later PR.

Need for Var<T> other than i32 and i64? Where? Why?

We might want to use Var<u32> and Var<u64> for packets where negative values make no sense. Clean types should be clean after all.

Enable packets using Nbt

Did I miss any? Afaict they're all enabled now, except for UpdateBlockentity (play, 0x35, clientbound) which requires custom encode/decode methods.

Compression can wait, requires read_packet and write_packet to hold state somewhere.
write_packet can't, it was already there. Wasn't it?

How are Var<u32> and Var<u64> encoded? -1 as varint is {0xFF, 0xFF, 0xFF, 0xFF, 0xF}

I forgot, Handshake and Status modules should be merged, they are the same thing, Ping is optional though.

Good point. We should add write_packet now, and move it to a connection manager later, along with read_packet.
The unsigned Var types are supposed to be encoded as signed (VarInt/VarLong). If an illegal value is encoded, it errors.
Since when are Handshaking and Status the same state? They can't be, since they both have a serverbound packet with id 0x00.

I forgot about the 0x00 id, it's in so many places... :disappointed: Nevermind.

Is it possible to not hardcode custom packets inside encode and decode blocks somehow? I've tested this new approach for PluginMessage and it works, but it's messy... It seems like coding with unknown variables.

I'm not sure what you're suggesting. Could you give an example?

@fenhl Could packet! macro write all of Packet for PluginMessage 0x3f but encode and decode methods and write those in some other file?

ExplosionOffset from Explosion (0x27) can be added to proto_structs!
ExplosionOffset { x: i8, y: i8, z: i8 }


Travis-ci boost dependency fix

Uses the generic download URL over a specific mirror seems to work.

Might want to try to switch to the current boost version, if you're at it. :)

That's ironic. I'm pretty sure that we locked in to a specific mirror because we were having problems with repeatedly landing on a bad mirror.

Using cached boost at /home/travis/boost_1_60_0

Travis uses the cache from the main (develop) if there isn't one for the individual branch, so I'm going to stop the build, clear the develop cache, and restart the build. That'll make it take longer, but is the only way to be sure it's working correctly.

@ximinez sound good.  I can trying fixing it to a new specific mirror if we find that works better.

@bachase It's already going. 😀

Yaaassss!

Current coverage is 65.11% (diff: 100%)

Merging #1909 into develop will decrease coverage by <.01%

@@            develop      #1909   diff @@
==========================================
  Files           686        686
  Lines         49033      49033
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          31931      31930     -1
- Misses        17102      17103     +1
  Partials          0          0

Powered by Codecov. Last update 47a919f...bd28a2e

👍  The commit message is too long, but I see it's been rephrased in #1912

Merged as cf60d4c30e31a4394deb98ab76836de76fb2693a


Feature Request: Add network address support for Postgresql

Hi, diesel developers.
I'm using diesel at work and need to handle network addresses for better functionalities of our product.
You know PostgreSQL supports network address types. CF PostgreSQL: Documentation: 9.6: Network Address Types.
Is it possible to support network address types on diesel? It doesn't seem MySQL and SQLite support it, so it will be a Pg only feature.
As it seems there aren't address range types neither in rust std nor crates.io, you may need to define enums such as:
use std::net::{Ipv4Addr,IpV6Addr}
enum Inet {
  Ipv4(Ipv4Addr, [u8; 4]),
  Ipv6(Ipvv6Addr, [u8; 16]),
}

MacAddress exits in crates.io CF https://docs.rs/eui48/0.1.0/eui48/struct.MacAddress.html .

Er.. subnetmask can be represented in u8, no need to have the same bits as addresses.

I think everything has been implemented now :)
Feel free to reopen if we missed something

No problem at all. Thank you.


from cmd prompt as administrator, after removing wsl; wsl --install and wsl.exe --install Invalid command line option: --install

Windows Build Number
Microsoft Windows [Version 10.0.19043.1083]
WSL Version

[ ] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
Visual Studio Code 1.57.1
wsl-install-fail.log
wsl-version-nil.log
wsl-status-nil.log
Repro Steps
I've been running ubuntu 20 but unable to run GUIs, although I thought gedit worked once. Certainly not nautilus.
I followed https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps to have GUIs working on my ubuntu distro. Have a recurring problem arising when trying to run  a GUI. This is one from nautilus attempt.
...cannot autolaunch D-Bus without X11 $DISPLAY
Unable to init server: Could not connect: Connection refused
(org.gnome.Nautilus:22): Gtk-WARNING **: 13:32:27.503: cannot open display:
I installed the intel graphics adaptor upgrade as recommended but it shoed no apparent change in the driver that I can read. I determined the problem was not having hyper-v. I bought a win 10 pro upgrade and installed without changing any of my WSL. Since having no more success, I reinstalled ubuntu twice I think. Once with unregistering and then installing from windows store .exe file. I later reinstalled from settings with app reset. Last, I've unregistered ubuntu again and removed wsl through windows apps.
"From "Apps & Features" (a.k.a. "Add or remove programs") in Windows, remove the "Windows Subsystem for Linux Update". I'm fairly certain this is the Linux kernel update. Probably reboot if you want to be sure it's fully gone before the next step.
From "Turn Windows Features on or off" in Windows, disable the "Virtual Machine Platform". This is the WSL2 Hyper-V support. Probably reboot if you want to be sure it's fully gone before the next step.
From "Turn Windows Features on or off", disable "Windows Subsystem for Linux."
https://superuser.com/questions/1619233/completely-rei
After reboot I've returned to https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps and attempted to run wsl --install or wsl.exe --install. Have no result.
Expected Behavior
I wasn't able to have wsl --install or wsl --update recognised before removing distro and wsl. And now I still don't. When I last ran the distro ubuntu, the drop down in windows terminal was showing ubuntu only and not ubunt 20.4 which it would have before. I don't know if that's relevant. Now I can even run gedit. I was sure I had that running before.
Have no inkling of seeing any GUI running from my distro. Feeling foolish now for buying a pro upgrade.
Actual Behavior
Expecting responses to the like of wsl --status from the cmd line as is instructed. Expect to have a working gedit but, was hoping more to be able to run the sqlite browser. I can't run so much as gedit now.
Diagnostic Logs
No response

You need Windows 10 Insider Preview build 21362+
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps#prerequisites

I’m running version 21H1. But I’ll try to upgrade if I can attain the correct link.
brian
@.***D77414.7B531790]
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Ben @.>
Sent: Thursday, 8 July 2021 3:51 PM
To: @.>
Cc: @.>; @.>
Subject: Re: [microsoft/WSL] from cmd prompt as administrator, after removing wsl; wsl --install and wsl.exe --install Invalid command line option: --install (#7160)
You need Windows 10 Insider Preview build 21362+
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps#prerequisites
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/WSL/issues/7160#issuecomment-876148840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFRB5D32J3LB6IC6F3JMMH3TWU4HVANCNFSM4776M2YA.

I can’t attain the build through insider program. The optional diagnostics option is grayed out and I believe I need that on in order to have access to the pre-releases.
Brian
@.***D77416.5B80CFF0]
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Ben @.>
Sent: Thursday, 8 July 2021 3:51 PM
To: @.>
Cc: @.>; @.>
Subject: Re: [microsoft/WSL] from cmd prompt as administrator, after removing wsl; wsl --install and wsl.exe --install Invalid command line option: --install (#7160)
You need Windows 10 Insider Preview build 21362+
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps#prerequisites
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/WSL/issues/7160#issuecomment-876148840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFRB5D32J3LB6IC6F3JMMH3TWU4HVANCNFSM4776M2YA.

Can anyone help with this? As I understand, I need to have the optional diagnostics data switch on. I can't access it. It's grayed out. I've tried to run settings as administrator through task scheduler but can't crack it. I am administrator in my normal login. But can't work out how to run this task as an administrator. I am trying to get the windows 11 build so that I can run GUIs on my WSL.


label slot not showing for FormGroup

Environment

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, colorMode, devtools, components, app, css, build, modules, runtimeConfig, devServer
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Version
2.8.1
Reproduction
https://stackblitz.com/edit/nuxt-ui-frhdyn?file=app.vue
Description
I tried to make use of the label as slot on the UFormGroup but it doesn't work. I even copied the snippet on the DOC. I still don't get any result
Additional context
No response
Logs
No response

This feature has been released in https://github.com/nuxt/ui/releases/tag/v2.9.0.


Pytorch reimplemention has something wrong!

Referring to your code, I reimplemented it using torch. but there are some problems. Can you help me take a look?

The problem is in the forward function of TransformerBlock.
    def forward(self, x):
        x = self.norm1(x)
        x = x + self.mulit_head_attention(x)
        x = self.norm2(x)
        # dump("attn_x_torch.pkl", self.ffn(x).detach().cpu().numpy())
        x = x + self.ffn(x)
        return x

The issue here is that you apply normalization to x and reassign that to x itself, meaning when you do x + mha(x) and x + ffn(x) both the x's have normalization applied to them when ONLY the one being fed to mha/ffn should be normalized. See:
def transformer_block(x, mlp, attn, ln_1, ln_2, n_head):
    x = x + mha(layer_norm(x, **ln_1), **attn, n_head=n_head)
    x = x + ffn(layer_norm(x, **ln_2), **mlp)
    return x

Notice, only that layer norm is only applied to the input of mha/ffn and not the residual connection.
So, the fix is simple:
    def forward(self, x):
        x_norm = self.norm1(x)
        x = x + self.mulit_head_attention(x_norm)
        x_norm = self.norm2(x)
        x = x + self.ffn(x_norm)
        return x

Thank you very much for your guidance. @jaymody


Synonyms not present in OWL

In the OWL version of UO, I am not finding synonyms. For example, kilogram has synonym kg on OLS. But this is not given in uo.owl.
cc @cmungall

I can confirm this:
$ curl -L -s http://purl.obolibrary.org/obo/uo.owl | grep kg
        <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">"A mass unit which is equal to one thousandth of a kilogram or 10^[-3] kg." [NIST:NIST]</rdfs:comment>
        <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">"A unit of concentration which expresses a concentration of a solution of 1 mole per kilogram of solvent (mol/kg)." [UOC:GVG]</rdfs:comment>
        <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">"A specific volume unit which is equal to a thousandth of a liter per kilogram or 10^[-3] l/kg." [NIST:NIST]</rdfs:comment>
        <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">"A specific volume unit which is equal to one millionth of a liter per kilogram or 10^[-6] l/kg." [NIST:NIST]</rdfs:comment>

no syns, just mentioned in comments
$ curl -L -s http://purl.obolibrary.org/obo/uo.obo | grep kg
synonym: "kg" EXACT []
def: "A mass unit which is equal to one thousandth of a kilogram or 10^[-3] kg." [NIST:NIST]
def: "A unit of concentration which expresses a concentration of a solution of 1 mole per kilogram of solvent (mol/kg)." [UOC:GVG]
synonym: "kg/m^[3]" EXACT []
synonym: "kg/m^[2]" EXACT []
synonym: "kg/mol" EXACT []
synonym: "kg.m/s" EXACT []
synonym: "m^[3]/kg" EXACT []
synonym: "kg/L" EXACT []
synonym: "kg/m" EXACT []
synonym: "l/kg" EXACT []
def: "A specific volume unit which is equal to a thousandth of a liter per kilogram or 10^[-3] l/kg." [NIST:NIST]
synonym: "ml/kg" EXACT []
def: "A specific volume unit which is equal to one millionth of a liter per kilogram or 10^[-6] l/kg." [NIST:NIST]
synonym: "ul/kg" EXACT []

@reality @leechuck is there something wrong with the release pipeline? I'm having a hard time with this repo figuring out which file is source (@kaiiam this may benefit from an odk revamp)

@cmungall my understanding from what @reality told me is that:

The current workflow is essentially: 1. edit unit.obo 2. run unitsconverter.groovy to generate the additional files.

If it's desired by the senior UO team, I'd be happy to try and do an ODK revamp of UO.

Hello,
I think we discussed this before -- yes, we would be happy with an ODK revamp :-)
Thanks,
Luke

Thanks Luke!
In the interim can we see if there is an easy fix to this particular issue? Does unitscnoverter wrap the owlapi? If so it is odd the synonyms don't show up in the owl - something else going on?

yes, we would be happy with an ODK revamp :-)

Awesome thanks I'll try to get a PR going soon.

that should do it. the synonyms were simply not added to the ontology by the wrapper script. if you can confirm that this solves the problem for your use case, then I'll close the issue :-)


buildpack: init at 0.5.0

Motivation for this change
Add https://github.com/buildpack/pack
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

I've renamed it to buildpack, because pack was too generic, and this package is kinda niche

@GrahamcOfBorg build buildpack


Latest ajv-cli can't resolve refs on schemas using test script command

Maybe I'm doing something wrong with this, but the latest ajv-cli (and ajv itself) can't resolve refs in the schemas as they are.  This persists even after migrating from draft04 to draft06.  The command in test_examples.sh:
ajv compile -s "schemas/*/*.json" -r "schemas/*/*.json" --verbose

leads to the following results:
schema schemas/common/binary.json is valid
schema schemas/common/bundle.json is invalid
error: can't resolve reference identifier.json from id common/bundle.json
...
(many more errors on refs)

I've noticed in the python validator you're mutating the schema $refs at runtime so that they can actually resolve by adding "file://" to the front of the relative path.  Is this intended behavior?

Hi @thebleucheese, thanks for the report! It looks like some things have changed with draft06 that we'll need to fix (we would welcome a PR!).
However, as a temporary fix until that happens, you can use ajv-cli version 1.1.2 (the last version before draft06 support).

Thanks for the response.  I was confused about what was going on so I spoke in a chat with some AJV users about usage, and the author of the library determined there's a bug in one of the latest versions of a dependency.  He created a bug report here:
https://github.com/garycourt/uri-js/issues/31
I think that may resolve the reference resolution issue.
Additionally, he mentioned that the id's for the JSON schema weren't valid (likely even in the draft04 spec context).  Those ids will serve as a base path and should be absolute URI's.  I'm new to using JSON schema so I'm not confident in making a PR on this since I don't totally grok uri-references and all the other JSON schema particulars.
Potentially relevant info from the AJV documentation:

You don't have to host your schema files at the URIs that you use as schema $id. These URIs are only used to identify the schemas, and according to JSON Schema specification validators should not expect to be able to download the schemas from these URIs.
The actual location of the schema file in the file system is not used.

So what I did to load them is I do a recursive walk down the schemas dir, loading all the files into plain old js objects.  I manipulated the $id and $ref properties removing all the path information and changed the string contents to just the file name, which works when calling ajv->addSchema(), but my guess is that it still isn't proper, valid JSON schema.  From my limited understanding of the JSON schema spec so far, I think the long term solution is to change the $id params for most of the stix 2 schemas to a real absolute url... something like https://oasis-open.github.io/specs/stix2/schemas/sdos/attack-pattern.json

We can also use raw.githubusercontent.com URLs to link to the exact files (even though this isn't strictly required). @clenk what do you think?

We had some talk about hosting the schemas in https://github.com/oasis-open/cti-documentation/ but I think using raw.githubusercontent.com URLs would be better as it would remove the need to sync updates between repos.
The jsonschema python library we're using in https://github.com/oasis-open/cti-stix-validator doesn't yet have a stable version supporting draft 6, but when it does (soon) we'll update the schemas to draft 6 and fix the IDs.

The schemas have now been updated to JSON Schema draft-07, and the $ids and $refs should be fixed now. Please open another issue if the latest changes are still a problem for you. Thanks!


⚠ Presupuesta.me has degraded performance

In 3646b88, Presupuesta.me (https://staging.presupuesta.me/up) experienced degraded performance:

HTTP code: 500
Response time: 1426 ms

Resolved: Presupuesta.me performance has improved in dd65074 after 10 minutes.


feat(#697): Rremove Redundant Methods

In this PR I succesfully removed many outdated and redundant methods from xmir package.
Closes: #697.
History:

feat(#697): removed unused XmlInstruction#toNode method
feat(#697): remove redundant code
feat(#697): add more javadocs

PR-Codex overview
This PR adds and updates methods and constructors in various classes related to XML representation and bytecode handling.
Detailed summary

Added a name method in BytecodeMethod
Renamed parameter in XmlAnnotationProperty constructor
Updated method call in XmlMethodTest
Removed empty comment in XmlDefaultValue
Updated comments in XmlField
Removed writeTo method in XmlBytecodeEntry
Updated comments in XmlBytecodeEntry
Updated comments in XmlAttribute
Updated comments and examples in HexString
Updated props method in XmlAnnotation
Removed writeTo method in XmlLabel
Updated constructor parameter name in XmlClassProperties
Removed writeTo method in XmlTryCatchEntry
Updated constructor parameter name in XmlAttributes
Updated bytecode method in XmlHandler
Updated XmlOperand constructor
Updated XmlProgram constructors
Removed writeTo method in XmlInstruction

The following files were skipped due to too many changes: src/main/java/org/eolang/jeo/representation/xmir/XmlInstruction.java, src/main/java/org/eolang/jeo/representation/xmir/XmlMaxs.java, src/main/java/org/eolang/jeo/representation/xmir/XmlFrame.java, src/main/java/org/eolang/jeo/representation/xmir/XmlMethod.java, src/main/java/org/eolang/jeo/representation/xmir/XmlNode.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@volodya-lombrozo Thanks for your contribution! Here's the breakdown of your +4 points: +4 base, -8 for 464 hits-of-code (≥200), -16 for no code review, -16 for no reviewer comments, +40 adjustment. While the high volume affected your score, we appreciate your effort. For future submissions, consider smaller, review-friendly contributions to maximize your points. Your balance is now +120. Keep up the good work! 🚀


Replaced MustGetLogger with more idiomatic GetLogger.

Also, +1 to renaming GetLogger to NewLogger.

Sorry, I don't agree. Why would this be more idiomatic?

Panics aren't great.  They're very noisy and hard to recover from.  A returned error value is nicer to deal with.  Nearly ever method in the golang stdlib uses error values for error handling.  Here's a stackoverflow question that goes into more detail: http://stackoverflow.com/questions/21265464/golang-idiomatic-error-handling

I also don't agree.  Full explanation would be needed for me to consider supporting this change.

On Nov 24, 2015, at 4:39 PM, Örjan Persson<EMAIL_ADDRESS>wrote:
Sorry, I don't agree. Why would this be more idiomatic?
—
Reply to this email directly or view it on GitHub.

I have never even observed this go logging panic getting triggered IRL, so why is this worth everyone's time?   Has it caused you significant trouble?

On Nov 24, 2015, at 5:05 PM, Xavi<EMAIL_ADDRESS>wrote:
Panics aren't great. They're very noisy and hard to recover from. A returned error value is nicer to deal with. Nearly ever method in the golang stdlib uses error values for error handling. Here's a stackoverflow question that goes into more detail: http://stackoverflow.com/questions/21265464/golang-idiomatic-error-handling
—
Reply to this email directly or view it on GitHub.

@xavi OK. I might have been a bit trigger happy.
Yes, I agree with you. I even see that I have a TODO about calling it NewLogger. However, since I don't feel like breaking backwards compatibility right now it will stay as is.
For the formatter, both versions are available there; use the NewStringFormatter if you want but in the example I believe it doesn't hurt to use the Must variant. If you however can change the format string from a configuration file or similar, I agree that you should use the NewStringFormatter.
The New vs. Must pattern is taken from the regexp package in this case.

Yeah, the lack of semvar or similar mechanism makes golang a troublesome language...  An alternative is to make NewLogger an alias for GetLogger and deprecate GetLogger.


Remove debugger

removed all debuggers from the repository.
removed warnings for Vuetify components in VSCode.

the version of some package upgrade

Removed all package.json changes.


*: add fail over scheduler

now checker couldn't found abnormal region immediately. and there are some priorities for scheduling the fail store regions.

There is a new way to select region(s). Please merge master and update your code.

how about the effect when the store is failed?

close by low priority and inactive.


Protractor tests fail on PhantomJs, but work on Chrome and Firefox

Hi everybody. Protractor tests fails on PhantomJs, but passed successfully on Chrome and Firefox. Did anybody had same error, and how to fix it

Hi there!
Since it involves usage and debugging (and you haven't used the issue template to indicate otherwise), your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks and good luck!


A little late, but gets all functionality in place

🥴  Gets all the needed in place!

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


As PO I want SnackChats to be stored temporarily in firebase storage at an obscure public URL

AC:

When a user sends a SnackChat, the image is uploaded to firebase storage as opposed to slack
Images are stored at a URL that cannot be easily guessed
Images are only retained temporarily (1 hour?)
Messages sent do not appear to come from the user who generated the slack token
Slackbot's username and icon are consistent with the honesty.store brand

All AC have been met by the snackchat branch except for only storing images temporarily. Some things to consider:

While slack does cache the image for a little while after sending the message it does eventually request it again after only a few minutes at which point, if it no longer exists, the image disappears (see screenshot below)
Images are located at URLs generated using cryptographically secure random file names (20 random bytes) to obscure them
The image itself is only returned when specifying ?alt=media at the end of the URL, otherwise only a JSON summary is returned
Firebase storage comes with 5 GB of space for free and the generated images are ~300 kB so we can store plenty of them simultaneously
Running cron jobs on firebase is a little awkward and would require setting up several new services on our App Engine account
It would be relatively simple to set up an endpoint that is periodically called by https://cron-jobs.org but this relies on an external resource


Fix error caused by incorrect rank assumption in tf.image.flip_left_right

This PR tries to address the issue raised in #40580 where an error
was thrown out when tf.image.flip_left_right process a tensor of unknown
rank.
The reason was that tf.image.flip_left_right assumes rank == 3 in case
of unknown rank.
This PR adjust to use array_ops.rank(image) to obtain the true rank
when unknown rank is present.
This PR fixes #40580.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Thanks @mihaimaruseac for the review. The PR has been updated and  next(iter(dataset)) has been converted to get_single_element(dataset.take(1)). This should resolve the graph mode failure I think. Please take a look and let me know if the issue still exists.

Tests are still failing :(
This is tensorflow/python:image_ops_test:FlipTransposeRotateTest.testFlipImageUnknownShape
Traceback (most recent call last):
  File ".../tensorflow/python/client/session.py", line 1365, in _do_call
    return fn(*args)
  File ".../tensorflow/python/client/session.py", line 1350, in _run_fn
    target_list, run_metadata)
  File ".../tensorflow/python/client/session.py", line 1443, in _call_tf_sessionrun
    run_metadata)
google3.third_party.tensorflow.python.framework.errors_impl.InvalidArgumentError: TypeError: `generator` yielded an element that could not be converted to the expected type. The expected type was int32, but the yielded element was Tensor("Const:0", shape=(1, 2, 2, 3), dtype=int32).
Traceback (most recent call last):

  File ".../tensorflow/python/data/ops/dataset_ops.py", line 843, in generator_py_func
    ret, dtype=dtype.as_numpy_dtype))

  File ".../tensorflow/python/ops/script_ops.py", line 205, in _convert
    result = np.asarray(value, dtype=dtype, order="C")

  File ".../numpy/core/numeric.py", line 538, in asarray
    return array(a, dtype, copy=False, order=order)

TypeError: __array__() takes 1 positional argument but 2 were given

Thanks @mihaimaruseac for the help. The failure very much looks like related to shape is not passed in generator. I have added additional parameter to from_generator. Think this might solve the internal test issue.
I have updated the PR. Please take a look and see if the issue still exist.

Hmm, I am seeing the same error

Let's try to resync copybara import to make sure all changes are in.

Yes, same error with the latest commit included :(

@yongtang, @mihaimaruseac Any update on this PR? Please. Thanks!

@gbaned I will take a look, sorry for the late reply.

@yongtang  Any update on this PR? Please. Thanks!

@mihaimaruseac The PR has been updated by switch from usage of tf.constant to np.array inside the generator. This will avoid calling extra layer conversion between tf and numpy. I think this might resolve the issue. Can you give it a try? Sorry for the extra inconvenience.


Building LXC Images

LXC (LinuX Containers) have been a first class citizen in the Linux Kernel since quite a while now and they are getting ever increasing attention as a light weight and quick alternative for OS level containerization instead of e.g. VServer and others.
Can we integrate some support for LXC into Veewee?
This would make the veewee/vagrant combination even more invaluable for simple deploys in my opinion for System Admins.

+1

This feature would be nice!

as I am only doorkeeper here - anyone interested in taking a shoot at implementing it?

https://github.com/fgrehm/vagrant-lxc


Fix Travis build

Allow retrieving a pre-built cmake package with wget via HTTPS without
checking certs.

unverified https is still better than plain http


obs-studio: Update to version 30.2.2

What type of Apps related PR is this? (check all applicable)

[ ] ✨ Add Manifest
[ ] ♻ Refactor
[x] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 🚩 Other

Description
Update the checkver configuration and update to the latest version
Related Tickets & Documents
None
[optional] What gif/emoji best describes this PR or how it makes you feel?
:pencil2: :alien: :wrench:
Did you verify the followings
Add/Modify a description in the manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Check URLs?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update to the latest version?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update Hashes?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Format the json manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Did you identify extra steps
Notes in the manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Application Dependencies?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Application Suggestions?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Pre-installation steps to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Post-installation steps to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

File persistence to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

All changes look good.
Wait for review from human collaborators.
obs-studio

[x] Description
[x] License
[x] Hashes
[x] Checkver
[x] Autoupdate
[x] Autoupdate Hash Extraction


Onboard Trino Users to Fybrik

We created a sample Fybrik Trino module. To onboard Fybrik users we should actively reach out to Trino users via

[ ]  Slack channels

[ ] Git discussions

[ ] Write blog

[ ]  Identify active Trino gurus and reach out to them


Add an image representation service Example

add an image representation service with general serving.

Model: Resnet50 based on Imagenet dataset
write a publishable tutorial for the serving part given a trained model with paddle.

https://github.com/PaddlePaddle/Serving/tree/develop/python/examples/imagenet


Add Streamz Hello World to Readme for easy searching

Subject says it all @taureandyernv :)

resolved in https://github.com/rapidsai/notebooks-extended/pull/112


Remove SwinjectStoryboard

Remove SwinjectStoryboard related files. They have been ported to SwinjectStorbyoard repo.

The ported SwinjectStoryboard is here:
https://github.com/Swinject/SwinjectStoryboard/tree/19ee86ad9688e1f0091bf16f3a6bc6e2c0833972

The ported PropertyLoader is here:
https://github.com/Swinject/SwinjectPropertyLoader/pull/1


Building doest work %100

I've had the cannot GET/ error and found out what caused it. If you build the software it builds the server but doesn't build the full client side so the index.html are not created. Might want to fix that ;)

Wait for #267 to be merged. Should fix it.


Release branch linux driver doesn't build on RockyLinux 9.3

When building the linux driver from the "release" branch on RL 9.3, we get this:

[100%] Building Linux driver
linux distro: rocky
linux distro flags: -DDISTRO_TYPE=rocky -DDISTRO_IS_RHEL_LIKE=1 -DDISTRO_MAJ_VERSION=9 -DDISTRO_MIN_VERSION=3 -DDISTRO_KERNEL_PKG_MAJ=362 -DDISTRO_KERNEL_PKG_MIN=8 -DDISTRO_KERNEL_PKG_PNT=1
lib: lib
/root/Downloads/aja17/libajantv2-release/driver/linux/ntv2driver.c: In function ‘aja_ntv2_module_init’:
/root/Downloads/aja17/libajantv2-release/driver/linux/ntv2driver.c:2991:32: error: assignment to ‘int (*)(const struct device *, struct kobj_uevent_env )’ from incompatible pointer type ‘int ()(struct device *, struct kobj_uevent_env *)’ [-Werror=incompatible-pointer-types]
2991 |         ntv2_class->dev_uevent = aja_ntv2_dev_uevent;

I see there is a fix for this (file driver/linux/buildenv.h) in the 17_0 and main branches (which compile properly).

Hi, as we're having the same issue, can we expect the ntv2_17_0 to be merged to release branch soon? I'm just wondering if we should wait or modify our workflow to cherry-pick the respective commits.

QA tells me that a 17.0.1 release is slated for February. I don’t have a specific date yet.
You can wait for the official release to be tagged, use the ntv2_17_0 branch in its current pre-release state, or cherry-pick the changes you need. Note that AJA only provides support for officially tagged releases.

@janbrothanek Have you verified that this is fixed for you if you use the latest ntv2_17_0 branch?

@paulh-aja yes, I can confirm it's fixed. Thank you.

Thanks for confirming @janbrothanek.
Closing...


Method of identifying symbol at Marker is inadequate for symbols with constructs

If you interact with the script of a script identifier, you don't get the correct highlighting or tooltip behaviour.

There is NO point in tuning the editor behaviour before you have automated tests. NONE. It's either good enough to experiment or too broken to use, but the fine details can't be expected to remain in working condition without tests. Testing ties into logging- you could make a macro system to capture actions and write a script to invoke them again.


[WHLSL] Verify the parser uses the same grammar as the language

Migrated from https://bugs.webkit.org/show_bug.cgi?id=188517:
At 2018-08-13T15:50:45Z<EMAIL_ADDRESS>wrote:
The current hand-written recursive-descent parser is relatively slow and is the main bottleneck of the prepare function. The parser should be rewritten using a tool that produces more efficient code, such as https://github.com/antlr/antlr4.

At 2018-08-27T22:21:28Z<EMAIL_ADDRESS>wrote:
*** Bug 189014 has been marked as a duplicate of this bug. ***

At 2018-08-27T22:22:11Z<EMAIL_ADDRESS>wrote:
It takes 2.5 hours to compile the standard library. 95% of the time is spent parsing.

At 2018-08-28T22:55:01Z<EMAIL_ADDRESS>wrote:
One way to do this is by using a parser generator. Another way of doing this is with testing. Another way is via inspection.

At 2018-09-13T01:51:31Z<EMAIL_ADDRESS>wrote:
rdar://problem/44403020


CSS still overriding styles in webapplications

.main-container rule of https://github.com/USGS-R/repgen/blob/master/inst/extdata/styles.css is overriding a bootstrap rule in the AQCU applicatoin.
Can you namespace this class? eg: .repgen-main-container

@thongsav-usgs I must not have committed that. I thought I fixed it locally, and will check on that.


Settings view

Added Account settings controller and view

See email re this (ex Controllers folder)

updated the folder

All that needs to be is done is run the code and be sure the functions in the Account Controller work. To test just go to url/account/testfunction.

Also a lot of functionality is commented out due to hard coded data but the pages should return something at all times, just look at the return values of each function.

Testing all Account Controllers/Views on settingsView branch:
Testing all [HttpGet]

[x] /account/ yields account/index
[x] /account/login
[x] /account/register
[x] /account/RequestResetPassword
[x] /account/ResetPassword

We were able to step into the [HttpPost] methods using Fiddler by specifying:
Content-Type: application/x-www-form-urlencoded, and adding to the Request body.
Since there is no functionality with user data I just ensured the views worked and did not test the logic.
*Note we may need to specify urlencoded for unit tests in the future
[InlineData("application/x-www-form-urlencoded")]
:shipit:


Support for multiple ComponentVersions and Rollback

this is related to the following issue: https://github.com/open-component-model/ocm-controller/issues/159
ocm-controller should support rollback to previously known working version.
assuming following scenario flow:

we specify initial ComponentVersion e.g.

version:
    semver: v1.0.0

This will trigger OCM-controller to pull specified version v1.0.0 from OCI registry and create local copy for further deployment

we bump the ComponentVersion e.g.

version:
    semver: v1.0.1

This will trigger OCM-controller to pull the new version v1.0.1 from OCI registry and create local copy for further deployment
if the option prune: from https://github.com/open-component-model/ocm-controller/issues/159 is not active, we should have two versions of componentdescriptor CR in cluster
componentdescriptor.delivery.ocm.software/github.com-acme-podinfo-v1.0.0-10999154105985767822
   20d
componentdescriptor.delivery.ocm.software/github.com-acme-podinfo-v1.0.1-11333791066380101757

This is desired in some circumstances. therefore we should also define a parameter defining how may version we should keep; perhaps keepNumberOfComponentVersion: 2

NOW let say we identified there is a problem with new version and we want to downgrade the ComponentVersion to previously known working version e.g.

version:
    semver: v1.0.0

This should  trigger OCM-controller to:

check if the vision does not exists locally,
or pull old  version v1.0.0 from OCI registry

then version specified in  ComponentVersion should be use by deployer/operator to deploy application.

The reverting to a previous version should work with https://github.com/open-component-model/ocm-controller/pull/163.
Are you saying that it did not work?
Prune is mostly passed over to Flux. ComponentDescriptors are only used to gather version and resource information. Keeping them doesn't add too much value into the flow as they are dynamically recreated anyways once a version is reconciled. What benefit would be keeping the descriptors if the component version is removed/updated/reverted? Nothing accesses that information anymore.

Okay, so after a long discussion and some time in this area, we decided this is not a good idea. After installing a version, trying to return to a previous version is error-prone. Many unknown factors are involved with a version install, such as migrations, third-party component changes, state changes, persistent volume changes, secrets, component access, validations, etc...
Rolling these back is near impossible without messing something up badly. The mindset we will adopt is an always-go-forward mindset. If a version is compromised, either delete it and install a previous version or bump it to a fix. Anything else leaves the cluster in an unknown state which is not desirable.
We will turn off the current functionality of the ability to specify a lower version than is currently installed. It won't error, but it will ignore that version.

Roll-backs are also an attack vector that needs to be considered, especially in the context of a project such as OCM which is concerned with automated delivery.

This is desired in some circumstances. therefore we should also define a parameter defining how may version we should keep; perhaps keepNumberOfComponentVersion: 2

We could keep several versions in cache like suggested. The use could then revert manually by changing the semver.

We could keep several versions in cache like suggested.

We don't cache resources that point to these, like Kube objects. And we don't cache anything applied to the cluster that potentially modified like service accounts, secrets, etc. We don't keep a catalogue either, that's flux, I guess. In-fact without a resource like a snapshot no-one know where anything is. :D So once the objects are deleted, the storage is useless. ( We should even probably clean it up periodically ).
Further, and more importantly... our cache is a throwaway. It's not persistent storage in any way. Meaning it could be restarted, deleted, updated, whatever. It has two purposes. Provide ease on external repositories. Like having to fetch something constantly from the outside especially if it's big. And an integration point with Flux. Storing a version there is no guarantee that the actual thing is there.


Http Pipeline

I don't see az_mut_span const * const => az_mut_span * const, other than that, LGTM.

@gilbertw , Please fix this


Support svelte.config.cjs file naming

When trying to run unit tests with SvelteKit, svelte-jester throws Could not find svelte.config.js.
It would be great to have SvelteKit support!

It looks like Cosmiconfig v7 handles .cjs files. I don't think that is the only change necessary, but it would probably remove the No loader specified for extension ".cjs" error that I'm getting when I try this transform config: transform: { "^.+\\.svelte$": ["svelte-jester", { preprocess: "./svelte.config.cjs" }] }

Actually, I just tried it and { preprocess: "./svelte.config.cjs" } totally works if svelte-jester uses Cosmiconfig v7! The type of change is here, but it's literally just updating the dependency version.
The other question is what should { preprocess: true } do -- should it look for "svelte.config.cjs" if "svelte.config.js" doesn't exist? And the same for { rootMode: "upward" } -- should it also search for "svelte.config.cjs" as well as "svelte.config.js"?

Hey @forrestjacobs thanks for looking into all this! If you can throw a PR my way for this I'm happy to pull it in and release ASAP. The answer to both questions is yes, it should look for both svelte.config.js and svelte.config.cjs.

@mihar-22 sure thing! Just opened one.

Released in 1.4.0 thanks to @forrestjacobs! Thanks!


SARAALERT-1212: Dashboard Jurisdiction "Scope" Bugfix

Description
Jira Ticket: SARAALERT-1212
Before, we had a bug where, whenever the jurisdiction was changed in the patient index interface, the scope would be changed to "all" even if it had been "exact match" beforehand. This updates the javascript to change the scope to its set value whenever the page is updated, and modifies the demo.rake to cover the test case that produced the error so we catch these in the future.
(Bugfix) How to Replicate
Bug report here:
https://teams.microsoft.com/l/file/F25865B2-C3D6-40CF-AF62-FD8FEB1033C5?tenantId=c620dc48-1d50-4952-8b39-df4d54d74d82&fileType=pptx&objectUrl=https%3A%2F%2Fmitre.sharepoint.com%2Fsites%2FCoVDT%2FShared Documents%2FGeneral%2FProduct Owner Materials%2FTesting%2FBug Reports%2FEnroller Scope<EMAIL_ADDRESS>(Bugfix) Solution
See above: I updated the javascript to change which field is selected to the original value when the options are refreshed.
Important Changes
app/views/patients/_patients.html.erb: the change to update the field.
config/sara/jurisdictions.yml and lib/tasks/demo.rake: changes to our demo code to also create a state without child counties when producing demo and test data, which was the case that first uncovered this bug.
Testing
This fix was tested on the following browsers (submitter must check all those that apply):

[x] Chrome
[x] Firefox
[ ] Safari
[ ] IE11

Please describe the tests needed to verify your changes. Provide instructions for reproducing these tests. List any relevant details for your test configuration.

this branch needs a rebase