Create more accurate CVE database with cve-add/cve-fix commits and rules

Signed-off-by: Yongkui Han<EMAIL_ADDRESS>

This commit adds new feature of creating more accurate CVE database, based on tagged cve-add/cve-fix commits and CVE checking rules.
changes to bomsh_hook2.py:

added --cve_check_dir option, which provides CVE checking rules file, and CVE checking will be performed for relevant source files during software build, and some extra metadata regarding CVEs are recorded in raw_logfile. This extra CVE metadata will be utilized later by the bomsh_search_cve.py script.
added --record_build_tool option, which records the gitoid of gcc/ld/rustc/go compiler/linker, its file_path and version info.
miscellaneous fixes.

changes to bomsh_create_bom.py:

extra CVE metadata handling to support CVE checking.
extra build_tool metadata handling.
miscellaneous fixes.

changes to bomsh_create_cve.py:

added --use_git_tags and --cveinfo_dir options, to support creating CVE DB using cve-add and cve-fix commits in a git repo.
added --source_tarball and --source_dir options, to support creating CVE extra DB for those blobs that do not exist in the baseline source tarball.
added --gen_extra_cvedb option, to support creating CVE extra DB for RPM git repo, which applies additional patches on top of the official source tarball. The baseline CVE DB from the git repo and the CVE-extra DB from the linux distro git repo, will cover all the blobs for the linux distro.
miscellaneous fixes.

changes to bomsh_search_cve.py:

support newly added metadata of cvehint results.
report a warning when there are any blobs in the gitBOM tree that are not covered by the CVE database.


dependencies problem

Hi there,
I've been attempting to install the stable-audio-tools package locally by cloning the repository, due to some pip installation dependency issues. However, in both cases, I've encountered a specific problem related to the pedalboard dependency version. The installation process is halted with the following error messages:
ERROR: Could not find a version that satisfies the requirement pedalboard==0.7.4 (from stable-audio-tools) (from versions: 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.8.9)
ERROR: No matching distribution found for pedalboard==0.7.4
It seems that stable-audio-tools requires pedalboard==0.7.4, but only newer versions of pedalboard are available.
I'm keen to hear if there's a workaround or if an update to accommodate newer pedalboard versions is possible.
Thank you in advance

I believe you need to be on python 3.8.12 @albedimaria. Just dealing with this issue myself.

thanks, it actually worked.


Changes to Donate to Charity Settings do not Save

Expected Behavior
Changes to the Donate to Charity sections of the Settings menu is saved.  Available Charities dropdown has available selections.
Actual Behavior
Changes to the Donate to Charity sections of the Settings menu are not saved.  The Available Charities dropdown has no selectable options.
How to Reproduce

Install Actifit for Android
Launch Actifit
Tap Settings
Tap Checkbox for Donate Rewards to Charity
Tap Save Settings
Tap Back button
Tap Settings

Test Environment

OS: Android 8.1.0
App: 0.3beta

Recording Of The Bug
https://youtu.be/OJsAlXDiLFg

@thewizardstudio it is normal that they do not save at the moment as the list is empty. Once filled the behaviour will change


Bug Article ID

The following error was found:
Error: Article ID cannot exceed 60 character(s).

Article name:

Doesn't matter the character length - still dumps

Hi @marketing720
I tried to replicate you issue, and it works like a charme.
What PHP version do you have? Can you put "My Blog Post Test" for the "Article Name field and try again?

Did you try again @marketing720?
What did you put for the "Article Name" field?

Hey @marketing720, since you didn't get back to me, I assume that this issue is now solved for you and can be closed. Just let me know if this isn't the case 😃


Mapping complex collection to flattened collection

It's be nice to have an example on how to map things like property of type Dictionary<string,Foo> into List with  internal mapping like Foo->Bar with defaults but Bar.ParentKey receives value from Key in KeyValuePair<string,Foo>.
I've tried few options but struggling to get it working. Although it looks like very simple scenario, default mappings from Foo to Bar are not being used or lost (or I'm doing something wrong).

+1

Hi, problem was Mapster 1.0 did not support Dictionary and struct like KeyValuePair. This should work in Mapster 2.0.


Dashboard & TabView bug

On the Dashboard the change section order have some bug going on like shifting some of the order will crash the app like shifting the order of the AC Helper+ and when hiding the section after relaunch of the app causes duplication and also unhide the section on it’s own. Below is a picture for reference.

For TabView is that everytime when you constantly go back and forth on certain tabs it will cause the wording of the title for the tab to be present and stacked up at the top. Below is a picture for reference.

iOS ver: 13.5 App ver: 1.6(052772020)

Yup @renaudjenny saw it too. Will fix :)

This bug is still not fixed in the latest release. Even after a clean install, the relaunch of the app still causes duplication and unhide sections. 😕

This bug is still not fixed in the latest release (1.6.2). Even after a clean install, the relaunch of the app still causes duplication and unhide sections. 😕

@dmndrz It'll be in 1.6.3 :) coming tomorrow.

I still have this bug in my environment.
Many rows are duplicated.

iOS ver: 13.5.1
App ver: 1.6.3
Do I need to uninstall the app and re-install?

@mimikun Yes sorry. If you have iCloud it'll restore your state on the launch. I'll try to add a cleanup methods to remove duplicates.

Thanks.
Looking forward to the update.


SliverAppBar navigates in an unexpected order when using VoiceOver

b/162037818 [See internal bug for a video]
Expected results:
Swiping to right
Navigation order: title -> Expanded title -> Text 0 to 3
Swiping to left
Navigation order: Text 3 to 0 -> Expanded title -> title
Actual results:
Swiping to right
Navigation order: title -> Expanded title -> Text 0 to 3
Swiping to left
Navigation order: Text 3 to 0 -> title
Code
import 'package:flutter/material.dart';

void main() {
  runApp(Demo());
}

class Demo extends StatelessWidget {
    @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: CustomScrollView(
          slivers: [
            SliverAppBar(
              pinned: true,
              expandedHeight: 200,
              title: const Text('Title'),
              flexibleSpace: FlexibleSpaceBar(
                background: Padding(
                  padding: EdgeInsets.only(top: 100),
                  child: Semantics(
                    header: true,
                    child: const Text('Expanded title'),
                  ),
                ),
              ),
            ),
            SliverList(
              delegate: SliverChildListDelegate(
                [
                  for (var i = 0; i < 50; i++)
                    Container(
                      height: 200,
                      child: Center(child: Text('Text $i')),
                    ),
                ],
              ),
            ),
          ],
        ),
      ),
    );
  }
}

@chunhtai

There are two problems:

the flex space bar will be removed from the rendering tree entirely when it is collapsed which means the semantics node will not exist when accessibility focus traverse back to the header. We should still include the render object of flex space bar even if it is collapsed.

the other problem is that the semantics focus may jump randomly after a scroll or layout change because we always give it a nil reference to post-accessibility-announcement api. I am not entirely sure how ios decide to focus next in this case, it seems to vary depends on the structure of the accessibility tree.

I will put up prs to fix these issues soon.


chore: update iconfiy version

Hi, iconify-json update some icon's set, could u pls update the version and release this pkg?

Hi, if you want, you can help me update all the dependencies and submit the lock file to git.

@hyoban Sure, I have updated all the deps.

Thanks! Can you commit the lock file update? Just run pnpm install locally then you can see it.

Seems the error from  pnpm version


Multinode run problem

Hi,
I'm using such tool on HPC machine, having 4 gpus per node. This is the launch command for 2 nodes and 4 gpu for each:
`
export LOGLEVEL=INFO
export NCCL_DEBUG=INFO
export NCCL_DEBUG_SUBSYS=COLL

export MASTER_PORT=$(expr 10000 + $(echo -n $SLURM_JOBID | tail -c 4))
export WORLD_SIZE=$(($SLURM_NNODES * $SLURM_NTASKS_PER_NODE))
echo "MASTER_PORT"=$MASTER_PORT
echo "WORLD_SIZE="$WORLD_SIZE

master_addr=$(scontrol show hostnames "$SLURM_JOB_NODELIST" | head -n 1)
export MASTER_ADDR=$(getent hosts $master_addr | awk '{ print $1 }')
echo "MASTER_ADDR="$MASTER_ADDR
python -m torch.distributed.launch --nproc_per_node=4 --nnodes=2 --use_env fasterrcnn-pytorch-training-pipeline/train.py --data ***/Deep_Learning/MIC_DL/mic_env_ai/tools/fiftyone_venv/conversions/for_detectron2/beni_culturali/beni_culturali_pvoc_stratified_negative_coords_translated/beni_culturali.yaml --epochs 1 --model fasterrcnn_resnet50_fpn --name beni_culturali_check --batch 1 --disable-wandb --workers 0
`

The code seems stuck and doing nothing. I'm doing something wrong?
`
  warnings.warn(
WARNING:torch.distributed.run:
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
INFO:torch.distributed.launcher.api:Starting elastic_operator with launch configs:
  entrypoint       : fasterrcnn-pytorch-training-pipeline/train.py
  min_nodes        : 2
  max_nodes        : 2
  nproc_per_node   : 4
  run_id           : none
  rdzv_backend     : static
  rdzv_endpoint    : <IP_ADDRESS>:29500
  rdzv_configs     : {'rank': 0, 'timeout': 900}
  max_restarts     : 0
  monitor_interval : 5
  log_dir          : None
  metrics_cfg      : {}

INFO:torch.distributed.elastic.agent.server.local_elastic_agent:log directory set to: /dev/shm/slurm_job.1745194/torchelastic_s78szpdv/none_e_rmw4ws
INFO:torch.distributed.elastic.agent.server.api:[default] starting workers for entrypoint: python
INFO:torch.distributed.elastic.agent.server.api:[default] Rendezvous'ing worker group

    agent_data = get_all(store, rank, key_prefix, world_size)
  File "****/Deep_Learning/MIC_DL/test_detectron_multinode/pytorch_1.12_cu11.6/lib/python3.10/site-packages/torch/distributed/elastic/utils/store.py", line 34, in get_all
    data = store.get(f"{prefix}{idx}")
RuntimeError: Socket Timeout

`

I see that you have pass a --nnodes=2 argument. I am afraid that multi-node training is not supported at the moment.
It supports single node multi-GPU training.
Can you please start with a single node and 2 GPU training? That's what I have tested till date. I am trying to scale the code further but will take some time in doing so.

Ok, understood. The code is not multinode, but Multi-GPU yes. Why I don't see dist.all_reduce in training loop? Is somewhere?

You are right. There is a mistake. I have used SyncBatchNorm but forgot all_reduce. I will surely push the correct and updated code as soon as possible.

Hi, the all_reduce has been included in the reduce_dict function in utils.py. I hope this resolves the issue.
I am closing the issue for now. Please reopen if necessary.


Use as a steering wheel

since it has force feedback, itd be nice to use this for racing games as a racing wheel

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

ID: bf1d9b03-0aee-c779-b2b7-c0d354cf8b37
Version Independent ID: 7bbb638c-48df-75ab-49f4-82c7f6cb60cd
Content: Support the Surface Dial (and other wheel devices) in your Windows app - Windows apps
Content Source: hub/apps/design/input/radialcontroller-walkthrough.md
Product: uwp
Technology: design
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: kbridge

No issue reported.

Correct, it's a request.


Incorrect Padding

I generated a new Chef User (call him chefcleanup) and created a pen file for the user.  I then encrypted the pem file:
aws kms encrypt --key-id x-x-x-x-x --plaintext file://encrypted_pem.txt --region us-west-2 >> encrypted_pem.txt
copy the contents of encrypted_pem.txt to the lambda function and set everything up.
When I run the function I get an "Incorrect Padding" error.
Any thoughts as to why?
Jeff

Solved.  The instructions were not clear that the rest of the JSON in the CipherBlob needs to be stripped out when it's copied into "encrypted_text".  Changed that, all good.


It isn't possible to group by an empty _id

With the aggregation framework it is possible to group all documents from the result set,  by setting the _id field to an empty string.
{
    $group: {
        _id: "",
        num: { $sum: "$num"}
    }
}

This isn't possible with the aggregation commands from ReactiveMongo, because the most operators prefixes the field names with the dollar symbol($). It think these prefix operations should be deleted from all aggregation commands and operators. There is currently also an inconsistency with the prefixing of the field names. All group operators expect the AddToSet operators are prefixed. Why not AddToSet too?

Can be implemented with Group function.


Password Reset Page Password Field Form Size Style Issue

Description of bug
Provide a clear and concise description of the bug.
Steps to reproduce
List the precise steps to reproduce the bug:

Have a password reset link sent to your address from www.dnncommunity.org
Click on the link provided in the password reset email

Current behavior
The first password field is smaller than the second and not big enough for longer passwords to show characters being typed
Expected behavior
Both fields are big enough to type into and same size.
Screenshots

Additional context
Not sure the USERNAME field needs to be shown here.  It would be nicer if the form was centered in the page layout as well similar to login and registration.
Affected version

[ ] 10.00.00 alpha build
[ ] 09.10.02 release candidate
[ ] 09.10.01 latest supported release

Affected browser

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 11
[ ] Microsoft Edge (Classic)
[ ] Microsoft Edge Chromium

This needs to be handled on the theme for that site, please post in the forums there. Thanks.


Allow global patterns for local paths

Should be nice to allow global patterns for local and relative paths.
So we can change from:
[local]
.gitignore

[relative]
packages/benchmarks/.gitignore
packages/labs/.gitignore
packages/lit-element/.gitignore
packages/lit-html/.gitignore
packages/lit-ssr/.gitignore
packages/localize/.gitignore
packages/tests/.gitignore
packages/updating-element/.gitignore

To just:
[local]
.gitignore

[relative]
packages/**/.gitignore

@foray1010 do you have any plan to allow this? Thanks in advance!

@foray1010 do you have any plan to allow this? Thanks in advance!

work in progress, I guess I could finish it within this week

work in progress, I guess I could finish it within this week

🚢 3.1.0


fix(deps): upgrade to google-gax 1.x

Carrying on from #644, this upgrades to google-gax@1, making the suggestions provided by @alexander-fenster.
To Dos

[ ] Unit tests

I think that would be on the gax end. We can confirm we're passing the right options, but if gax says and tests that the options we pass work, then we should trust that per separation of concerns.

@stephenplusplus The changes look good to me. Some tests failed because the options object format has changed, this is expected I guess.
As for @JustinBeckwith's suggesting to check if grpc-gcp is actually used, I can suggest trying to sinon.spy the functions that is being passed in the config object (gcpChannelFactoryOverride and gcpCallInvocationTransformer ) and see if they are actually called. The problem here is that to make this test work, you'll need to mock a huge part of gRPC so it might make sense to do it in as a part of a system test and not the unit tests, so that we could just sinon.spy this two functions and just use the real service without a need to mock it.

I guess the question here is - what value does grpc-gcp provide.  Presumably it does something.

I will definitely test that we're passing the grpc-gcp things to the (eventual) GAX constructor. But speaking of if we're using grpc or not, I would just suggest checking that we pass it to GAX. GAX should have its own test that confirm it uses grpc when options.grpc is set.

@stephenplusplus I oppose that. It was my fault to let the original design pass through. Gax should know nothing about how the underlying transport works, and the best it can do is to pass any grpc.* options down to gRPC (whatever gRPC implementation is used), without doing an extra job trying to parse and understand these options.
I like thinking of Gax as of one more layer in the stack, that uses gRPC (using the common well-defined gRPC API so that any compatible gRPC implementation can be used) and that does not dig deep into how exactly that gRPC works. Gax has the default gRPC implementation to use (@grpc/grpc-js) but in the perfect world, it should not have any gRPC dependency at all, just accepting the whatever 🦆-typed gRPC that is passed to it.
In this picture, grpc-gcp is basically a property of the gRPC implementation to be used (you're kind of sending a mixture of grpc + grpc-gcp instead of just gRPC), so the only thing you can ask Gax is to pass down the corresponding options. To check that the gRPC (that client library supplied) actually calls the functions that the client library also supplied is something that client library can logically do, not the Gax.
(having that said, Gax does have a test that all grpc. options are actually passed down to gRPC - but it cannot check the semantics of these options because it should not know anything about that)

and the best it can do is to pass any grpc.* options down to gRPC (whatever gRPC implementation is used), without doing an extra job trying to parse and understand these options.

I don't think it should do an extra job, either. It should just make sure that the options are given to wherever they go.

To check that the gRPC (that client library supplied) actually calls the functions that the client library also supplied is something that client library can logically do, not the Gax.

Both this library and gax should follow the same system here-- we shouldn't have to double check that a dependency is doing what it says it does. We should trust the test suite of the dependency. nodejs-spanner trusts that the options we pass to gax are passed to grpc. And gax trusts that the options is passes to grpc are used properly by grpc.

The test that verifies that the options are passed down to gRPC is here: https://github.com/googleapis/gax-nodejs/blob/9e4d6ed7e444c3b4d64857d24a0ad0f51919bf17/test/grpc.ts#L171
They are really passed down there, I promise :)
But we do need a test that verifies that grpc-gcp actually works with Spanner. I do think it should be done in some system test for Spanner. At the very least, check that callback functions passed as parameters are called; even better is to check that something meaningful is going on (if not, why do we need this grpc-gcp at all :) )

@stephenplusplus anything blocking getting this over the finish line, would love to unblock it.

Sorry, I didn't mean to question the test quality of any library-- I never even checked. I was just trying to explain the separation of testing responsibility that made sense to me.

At the very least, check that callback functions passed as parameters are called; even better is to check that something meaningful is going on (if not, why do we need this grpc-gcp at all :) )

I actually don't know :) I'm still not clear why we need to double-check other libraries' behavioral guarantees. If grpc-gcp accepts these options, that should be proof that they are valid, and will be appropriately handled by grpc. Under that presumption, all that should be tested is that we pass these parameters, not that they are called (not our code that calls them? not our responsibility to test).

But we do need a test that verifies that grpc-gcp actually works with Spanner.

This can definitely negate my previous confidence-- what specifically needs to work, and why wouldn't it?

Hey @stephenplusplus,
So, here is how I see it. I totally get the point of having the library tests test the library functionality - that is how our unit tests work. In spanner, unit tests test spanner library up to the point where the request is taken care of by gax; in gax, they test gax features (e.g. if the parameters are passed down to gRPC).
We also have system tests that cover more than just this library's code: they test the functionality end to end: from sending a request to getting response, including all the stack of technologies under the hood (gax, gRPC, actual API implementation). The failure of a system test does not necessarily mean that the spanner library has a problem (the problem might as well be in gax, in gRPC, or in API server-side implementation), but it will likely mean that the end user will have a problem, and we just happen to be the ones who detect it.
So... back to grpc-gcp stuff. For now, we take some set of parameters and pass it to the client constructor. The client constructor knows to pass the same set of parameters to gax. Gax is tested and is believed to pass the same set of parameters to gRPC, which is believed to call the function being passed, that changes it behavior (in a way I have no idea about). That's why we have all this grpc-gcp: to change the gRPC behavior.
Now let me ask you: does the fact that we unit-test all the puzzle pieces individually means that grpc-gcp actually works for Spanner? Quite possibly, it might mean that the puzzle pieces perfectly stick together, but the resulting picture does not make any sense :)
That's why I'm suggesting to:

Understand what functionality grpc-gcp provides for end users;
Have a system test that verifies that adding grpc-gcp options and callback functions actually makes this functionality used by gRPC (at the very least, that the callback function that we pass is called).

I don't have any authority here on this library, just trying to be logical: we can't say we support grpc-gcp unless we actually checked that it works. Does this approach make sense for you @stephenplusplus? How about you folks @JustinBeckwith @bcoe?
Thanks!

TL;DR: I don't agree with this:

not our code that calls them? not our responsibility to test

We are the last Google-supported layer of the stack before the actual customer, so we might as well need to test everything :)  You folks might have a different opinion here, I'm OK with that.

I agree with both of us :) Thanks for the time to explain your position. The way we used to think of it was, unit tests test library code and system tests test our docs and examples (not 1:1, but in general, does the lib do what we say it does).
We should get specific on what grpc-gcp does and figure out if we think it's at risk for failing with Spanner. Does anyone know what it is? The README isn't very informative.

@WeiranFang for the rescue!

I might miss some of the content, so please correct me if I'm wrong. By reading this thread, it seems like grpc-gcp has been moved out of gax because it's not compatible with grpc-js, and the spanner library would need to pass both the grpc-native-core and grpc-gcp as options into gax. Is that right?
If that's the case, are we planning to move it back to gax once grpc-gcp is compatible with grpc-js? FYI we will start working on this to resolve the incompatibility issue in Q3.
To answer some of the questions:

Understand what functionality grpc-gcp provides for end users

grpc-gcp is a grpc extension that supports GCP specific features that are not supported (or may never be) in grpc itself. And those features are normally service specific (i.e. spanner and bigtable may have different requirements). So this library acts as an extension point to carry both the underlying features and API/Service specific configurations when using grpc clients.
Currently one of its major features is to support grpc channel management/pooling. This is to solve the GFE max 100 concurrent streams on TCP connection.

Have a system test that verifies that adding grpc-gcp options and callback functions actually makes this functionality used by gRPC (at the very least, that the callback function that we pass is called).

Not sure if it helps but the library has an integration test to test the channel pool functionality for spanner stub.
Let me know if there's any other questions.

Thanks @WeiranFang! As for moving it back to gax, we can discuss it later when the support for grpc-js is implemented. To be fair, I like the idea of passing grpc-gcp options all the way down without having any code in gax looks cleaner from the architectural point of view for me. But let's get back to this discussion later when grpc-gcp supports grpc-js. Until that time, it just cannot be a part of gax because of the extra dependency (grpc) it pulls.

Just referencing to the original issue #622

Pinging for another review. I have added the tests to confirm we are passing through the correct things from grpc-gcp.


Build warnings from cython

Building cython extensions from source generates a wall of warnings
[7/8] Compiling C object scipy/linalg/_matfuncs_expm.cpython-310-x86_64-linux-gnu.so.p/meson-generated__matfuncs_expm.c.o
scipy/linalg/_matfuncs_expm.cpython-310-x86_64-linux-gnu.so.p/_matfuncs_expm.c: In function '__Pyx_Import':
scipy/linalg/_matfuncs_expm.cpython-310-x86_64-linux-gnu.so.p/_matfuncs_expm.c:48372:21: warning: the comparison will always evaluate as 'true' for the pointer operand in '(char *)"scipy.linalg._matfuncs_expm" + 5' must not be NULL [-Waddress]
48372 |             if ((1) && (strchr(__Pyx_MODULE_NAME, '.'))) {
      |                     ^~
[8/8] Linking target scipy/linalg/_matfuncs_expm.cpython-310-x86_64-linux-gnu.so
Build OK

This is for a recent cython:
$ cython --version
Cython version 3.0.2

Maybe @da-woods or @matusvalo could weight in on these?

But definitely file a Cython bug. The C compiler version you're using is probably the most relevant information. And we can see if it can be fixed

Thanks @da-woods , filed  https://github.com/cython/cython/issues/5663

The fix for the warning in the issue description will be present in Cython 3.0.3. Together with other gh-19170 we should be down to a reasonable number of warnings - I'm aiming to get it back down to zero in the near future.

Looks to me like this was closed by gh-19714 - there may be a few warnings from Cython still there so feel free to reopen for those if so, but the wall is gone (it's hard for me to tell as I have a lot of warnings still, see gh-19734 and gh-19736

Yes indeed, this is fixed.


Notifications sent to clients only

Some (most) notifications are being sent to the server. That shouldn't happen. RemoteExec with -2 for the targets.

Fixed it.


Cannot find module 'Adonis/Addons/MongoritoModel'?

I have a error when run web, it show error:Cannot find module 'Adonis/Addons/MongoritoModel'.
I search "MongoritoModel" in project but not found.
Help me, please! Thanks!

Hi @tanobi92
I recomend the use of Lucid-Mongo for now.
I'm working with many projects using Laravel and React these days, and I cannot invest time to give maintenance on this package right now.
But fell free to fix issues or improve it and make a pull request.
I will merge and publish the package as soon as possible(about 24h max)


replace instead of updating incident records

We do a lot of checking right now to match incoming records to records in the database, and some information is being lost in the process. Instead, we should replace all records of an incident when we get new information about it.
This should happen after #124

We should do this by comparing an 'updated' date, so that any record that's older than X hours will be replaced, otherwise will be added.


start update process automatically

@ninewise the update process of Unipept can be triggered by following the UniProt RSS feed. On the same page, also see alternative FTP servers for downloads from Europe (servers in UK or Switzerland).
Original issue by @pdawyndt on Tue Apr 07 2015 at 12:56.

This might be worth reconsidering. These are the step I now take:

stop the mysql database on adler (because we need the memory)
start the make file
wait
copy the generated files to a separate dir on adler, to sherlock and to mycroft
start the mysql database on adler
drop unipept on adler and unipept2 on sherlock and mycroft
recreate all tables on all servers
run load.sh && index.sh on all servers
run loadProteomes.sh on adler
delete the cache dir on adler
manually check the results on adler
bump the unipept version number
swap the databases on sherlock and mycroft
deploy a new release on sherlock and mycroft
run loadProteomes.sh on sherlock
delete the cache dir on sherlock

Original comment by @bmesuere on Mon Feb 01 2016 at 14:44.


Application freezes sometimes

Bonjour Emmanuel,
Dans le cadre d'un projet, j'ai dû intégrer Matomo afin de faire du tracking basique.
J'utilise la version 3.2.0 du ngx-matomo/router (donc la dernière version).
Depuis la mise en place du module, sur certaines actions, j'ai un freeze complet de mon application. Je dois fermer l'onglet et en ouvrir un nouveau. Ce problème est reproduit sur plusieurs navigateurs (FF, Chrome) et par plusieurs personnes sur plusieurs environnements.
C'est un problème qui arrive pendant une navigation (changement de page), à chaque fois depuis les mêmes pages, vers n'importe laquelle.
Lorsque je passe le paramètre "disabled" à true dans le MatomoConfiguration, je n'ai plus de problème (mais plus de tracking non plus). Dès que je le réactive, le problème apparait.
Avez-vous des retours quant à ce problème?
Merci d'avance

Bonjour @VincentFraboulet123

sur certaines actions

Lesquelles ? Dans quel contexte ? Arrivez-vous à identifier l'instruction qui provoque le blocage ?
Pouvez-vous svp reproduire le problème sur un environnement minimal (type Stackblitz) afin d'identifier l'origine

Hello there !
I'm a coworker of @VincentFraboulet123 and I have been investigating this issue for the past day or so.
I am sad to report that I haven't been able to identify the root cause of this issue :/
However, I did find something that fixes it.
I was playing around with a smaller version of your matomo-router.service.ts and identified that it was the call to this.tracker.trackPageView() that was causing the freezes.
And I figured out that it was probably conflicting somehow with something within the angular internals (digest cycle or maybe change detection ? I'm not sure how to investigate that ...). And with that in mind, I tried running the function outside angular and asynchronically :
this.router.events
      .pipe(
        // Take only NavigationEnd events
        filter(isNavigationEnd),
        distinctUntilKeyChanged('urlAfterRedirects')
      .subscribe((event) => {
        this.ngZone.runOutsideAngular((event) => setTimeout(() => {
            this.tracker.trackPageView(this.titleService.getTitle())
        }, 0))});

That ended up fixing the issue for us !
While looking around for clues i stumbled upon a few other people having the same kind of issues (here or here) so I don't think the issue lies in your package but within matomo itself.
With all that said. For now we'll fork the repo in order to include this fix and i will submit a PR for you to review if you'd want to integrate it (and maybe another not linked to this issue :D).

I'll try that !

So !
Can confirm the patch fixes it !
I'll be working on that PR and will make sure it's an opt-in (this is a great idea i agree !)

Great! Don't hesitate to open a PR even if it's work in progress, so we can discuss about it

:tada: This issue has been resolved in version 4.0.1 :tada:
The release is available on:

v4.0.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.2.1 :tada:
The release is available on:

v3.2.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.6.1 :tada:
The release is available on:

v2.6.1
GitHub release

Your semantic-release bot :package::rocket:

I had the same issue as the author, the run outside angular zone saved me. So thank you ;)

:tada: This issue has been resolved in version 4.0.1 :tada:
The release is available on:

v4.0.1
GitHub release

Your semantic-release bot :package::rocket:


[OpenImageIO] build failure

Operating system
Windows
Compiler
No response
Steps to reproduce the behavior
while installing xstudio dependencies using cmake gui, with visual studio 2019

Failure logs
Package<EMAIL_ADDRESS>Host Environment

Host: x64-windows
Compiler: MSVC 19.29.30151.0
vcpkg-tool version: 2023-12-12-1c9ec1978a6b0c2b39c9e9554a96e3e275f7556e
vcpkg-scripts version: 9fd83fa98 2023-12-28 (20 hours ago)

To Reproduce
vcpkg install
Failure logs
-- Downloading https://github.com/OpenImageIO/oiio/archive/v<IP_ADDRESS>.tar.gz -> OpenImageIO-oiio-v<IP_ADDRESS>.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Disabling metrics because vcpkg.disable-metrics exists
[DEBUG] Trying to load bundleconfig from d:\xstudio-windows\xstudio-windows\build\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: d:\xstudio-windows\xstudio-windows\build\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://github.com/OpenImageIO/oiio/archive/v<IP_ADDRESS>.tar.gz
[DEBUG] Trying to hash d:\xstudio-windows\xstudio-windows\build\vcpkg\downloads\OpenImageIO-oiio-v<IP_ADDRESS>.tar.gz.16372.part
[DEBUG] d:\xstudio-windows\xstudio-windows\build\vcpkg\downloads\OpenImageIO-oiio-v<IP_ADDRESS>.tar.gz.16372.part has hash 5e7710676eb2bd97fa8d30ac3f9fab0bf95e4c71389f41694290b423712b64944b15135d3929cfb72744c6d5ff0ad3a85d3c1d280a439637639ef42ff10203b7
error: Failed to download from mirror set
error: File does not have the expected hash:
url: https://github.com/OpenImageIO/oiio/archive/v<IP_ADDRESS>.tar.gz
File: d:\xstudio-windows\xstudio-windows\build\vcpkg\downloads\OpenImageIO-oiio-v<IP_ADDRESS>.tar.gz.16372.part
Expected hash: e8b232bb3c1bb66cc6c4f023dcf6e29633a1aee64c49a2860c2157c0885960c40114ee3988d4f132e6e55670b8b1e01b5b4cd4462651ae047a89d22de527581c
Actual hash: 5e7710676eb2bd97fa8d30ac3f9fab0bf95e4c71389f41694290b423712b64944b15135d3929cfb72744c6d5ff0ad3a85d3c1d280a439637639ef42ff10203b7
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(1048):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 6us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 293us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 6.5 s (6469982us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

      Failed to download file with error: 1
      If you are using a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
         set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
         The value set by your proxy might be wrong, or have same `https://` prefix issue.

      3. Your proxy's remote server is out of service.

      If you've tried directly download the link, and believe this is not a temporary
      download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
      to report this upstream download server failure.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
  buildtrees/versioning_/versions/openimageio/7c06030b088b87143ff7a85c23af606bbd967496/portfile.cmake:1 (vcpkg_from_github)
  scripts/ports.cmake:170 (include)

Additional context
vcpkg.json
{
  "name": "xstudio",
  "version": "1.0.0",
  "dependencies": [
    "stduuid",
    "reproc",
    "nlohmann-json",
    "glew",
    "freetype",
    "pybind11",
    "spdlog",
    "fmt",
    "caf",
    "opencolorio",
    "openimageio"
  ],
  "builtin-baseline": "dafef74af53669ef1cc9015f55e0ce809ead62aa",
  "overrides": [
    {
      "name": "caf",
      "version": "0.18.5"
    },
    {
      "name": "opencolorio",
      "version": "2.1.1#2"
    },
    {
      "name": "fmt",
      "version": "8.0.1"
    }
  ]
}

Additional context
hash error while downloading

There have been patches since that version to deal with the release of some new versions as well as the move to a different organization.

commit accd79817981f1ce00c6a4164aecf2b2ac699823
commit 7e10d7ce8e4059973ec3771461157567e45f6d3e
commit d5b03c125afee1d9cef38f4cfa77e229400fb48a
commit 0ae3ed5f1c96694467596e63f72caaa16fe5ec01

This seems to work with a fairly current version ...
(It is worth noting that there's version 2.5.x when only 2.4.x is currently packaged...)

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


OKC SQL meetup address is incorrect

As reported in an email to Techlahoma from Kimberly Collins.
"Is the Techlahoma Google calendar kept up to date?  I was looking up the address for the OKC SQL meetup and found that it still shows the group as meeting at Dell.  I looked into it more and found that it's wrong here too:  http://us.techlahoma.org/groups
I'm also not sure whether anyone monitors the email address listed on that page (info@okcsql.org)."
Please update the following:

[ ] Google calendar
[ ] Techlahoma user group page

The user groups list now lives in the techlahoma_lander project.
https://github.com/techlahoma/techlahoma_lander/tree/master/data

I removed the address from the recurring event on Techlahoma's google calendar and added http://www.okcsql.org/ to the event description.


Re-enable DiscoveryDNS

It isn't acceptable for us to release a provider that lacks live tests.
Also, the mock tests aren't invoking the custom SSL logic. This means we are further flying blind. MockDiscoveryDNSServer needs to use ssl to ensure the plumbing works.

@wnagele I can help with the mock part and questions on the live tests. We shouldn't release DiscoveryDNS until live tests are in and you or someone else runs them successfully.

I'll look into this. Currently swamped with other work - can't commit to a date just yet.

Ping me privately with credentials if you'd like a hand on the live testing!

@MisterK will be working on this. I just can't find the time at the moment.

cool. @MisterK welcome!

fyi https://github.com/Netflix/denominator/pull/298 adds live tests. they still need to be run, though

@adriancole Hi!
Just wanted to know if you already had a timeline in mind. I would rather work on this at the end of the month, if possible. Would this be fine by you?

Once https://github.com/Netflix/denominator/pull/309 is in, this issue is limited to getting live tests plumbed and passing.
Waiting is fine, but I might unhook discoverydns from the 4.4 release in that case. We shouldn't hold the release hostage as everything else will be ready in 2 weeks. We could always re-add it back in 4.5.

FYI, if anyone can give me discoverydns account credentials, I can at least try to get this into the 4.4 release. else, it will have to bump as I can only do the release this weekend.

bumping to 4.5 via #317

Hi, folks. I'd love to see this addressed, but please note that if I don't have credentials by the time we release 4.5, I will be deleting this provider completely. There's too much unnecessary burden here, and nagging displaced my time that I can use to help the project.
https://groups.google.com/forum/#!topic/denominator-dev/s5jefvKRJNA

@adriancole For the credentials, @wnagele will provide them for you shortly, to test on our test environment.
Thanks!

I can't wait!

I have been able to successfully run most of the Live Tests myself today. I fixed a few problems along the way. I'll send a pull request ASAP (hopefully tomorrow).

Note: re-enabling this is dependent on a process by which contributors can easily test.
Right now, testing requires contributors have a static IP, which is a tall order, and not accessible.
I've asked discoveryDNS to make easy testing a priority. We need this to be accessible via a dynamic IP before adding. Ex. via a bastion, a test endpoint, or a UI that allows self-service whitelisting.
If we can't get a process that makes contributors' life easy, we'll have to ask discoverydns to host their own provider.

@adriancole I had a chat with @wnagele and he explained to me that we might want to externalize the discoveryDNS provider instead, into its own project, to use it as an external "plugin" (that way we can manage the testing and the credentials ourselves).
So I gave it a try.
For the Java code usage, it works very well, I just added the denominator-core and the new separate denominator-discoverydns provider as dependencies to a test client project, and I was then able to use the provider as expected.
However, for the CLI, I wasn't able to use the separate provider. I tried to modify the "denominator-cli-4.4.2-fat.jar" script to use the folder containing the denominator-discoverydns.jar file, but it still only lists the providers included in the fat jar itself. I'm guessing the "executable fat-jar hack" might be the cause of this, but I'm not sure.
Could you please advise if you have a workaround, or if you could add a more flexible way to add custom providers at CLI run-time?
Thanks in advance.

Glad to hear things are working out.
So, the easiest way to make the cli work with a third-party provider is to
either set the classpath to the following.

Meta-inf/services directory with your provider listed
Exisiting cli jar
Your jar

Or make a build file that repackages the cli. It would probably be pretty
simple, two deps: your jar and the existing fat jar. If you use maven, the
"really-executable-jar" plugin should do the trick. Otherwise it would
involve a little gradle work which I could help with in your repo
Lemme know how you would like to proceed.

Actually, just placing the provider jar first in the classpath should work
(as it contains the meta-inf)

I finally made it working.
The problem is that the "really-executable-jar" script uses the "-jar" option, so it ignores the "-cp" option, and you have to use the "Class-Path" manifest entry instead.
So I added it temporarily in the cli project's manifest, and it worked.
The problem is that this manifest entry does not support wildcards, so you cannot add random plugins jars at run-time.
So it leaves me with two options:

either re-package the fat jar as you mentioned, but that's not really what I wanted, as I think it would be preferable to let end-users just use the standard Denominator jar, just adding Discovery on top, as an optional provider.
The other possibility would be to ask you to modify the denominator.Providers class, so that is provides its own ClassLoader when calling ServiceLoader.load(Provider.class), so that it could also point to a predefined "plugins" or "providers" directory, where the optional provider jars could just be dropped in.

What do you think?
Other than that, I'll now make a pull request to remove everything DiscoveryDNS-related from the denominator project. And then I'll create our own denominator-discoverydns Github project.

Let's keep this limited to the bash header in the cli. At most extreme, we could introduce an ENV variable which controls where third party providers can be found.
Ex. here's how to make it look for the providers directory.
-    shortcutFile << 'exec java -jar $0 "$@"' + "\n"
+    shortcutFile << 'exec java -cp providers/*:$0 denominator.cli.Denominator "$@"' + "\n"

I tested this out by unhooking discoverydns, and adding it to the providers directory.
Can you find a solution that is limited to this? I would prefer that, as it seems least change necessary.

OK I quickly tested your solution and it works for me.
Are you going to push that change to the cli? An hard-coded "providers" directory or an ENV variable is fine by me, as I would think that the description on how to extend Denominator through third party providers should probably end up in the Denominator Wiki, so that end-users know how to handle those third party providers. What do you think?
Another quick question: our new project needs to access some of your test infrastructure classes (TestGraph, Live, etc.), from both the denominator-core and the denominator-model projects, as I wouldn't like to duplicate this useful test setup. Would you be keen on making those classes an accessible Gradle dependency?

All sounds good. Yeah sounds like we would publish test jars. Shouldn't be
too hard. I will open an issue around third party provider development to
track this stuff. Thanks for collaborating on this!
-A

I've created the denominator-discoverydns external project.
I'll fix all the remaining problems in the next few days.
Thanks for your help!


A couple of kani fixes

PR does two things because a recent upgrade of kani broke our setup. I'm not sure why it just showed up.
We fix the verification for amount types which recently broke because of MAX_MONEY changes and then we add a verification function to internals because build fails and one fix is to just add something.

Patch 1: units: Assumes correct values
Patch 2: units: Removes a stale check now that MAX_MONEY is being used for MAX
Patch 3: Add verification to internals::ArrayVec.

This code will break again if/when we enforce the invariant in from_sat as per #3730

Ouch, 2nd merge queue related problem on master this week. And the lint PR is likely going to be the 3rd. Maybe all the merge queue talk was more warranted than I thought.

I'm not sure what is going on now, I can run cargo kani in units and also in repo root.

This PR fixes the kani check in units for me too, but I do get an error in internals.  The same error as here "error: Failed to detect Kani functions"
If I add a kani function in internals everything passes.  But I don't know why it complains when there is none.

Can you post the command you run to get the error please (and from what directory).

I just ran cargo kani from internals/, but I also get the same error if I run it in the repo root.  It runs fine in units/.
Maybe due to a kani update? I only just installed it then (V 0.57.0)

It looks like it's an issue with kani V0.57.0. If I revert back to 0.56.0 I don't get the error.

Oh that explains it, good debugging bro.

Holy moly, I have v0.17.0 installed.

Just thought I should clarify my ACK that this PR is fine and fixes the described kani failure.  The conclusion above is that there is an issue with kani causing the current CI fail.

I added a kani verification to internals::ArrayVec. Clears the error we were experiencing and adds some value by verifying no out of bounds in ArrayVec.

Nice! Will ACK and merge this so we can get CI moving.
But we should separately change Amount::to_signed to no longer return a Result.

Added to #3787


Revising blog links

bluemix.net links are deprecated and no longer updated
updated to new cloud.ibm.com link style
also the product name is IBM Cloud Kubernetes Service, not Armada
follow on to PR #12792

Checked the updates on: https://deploy-preview-12796--kubernetes-io-master-staging.netlify.com/blog/2017/07/how-watson-health-cloud-deploys/ and the updates on: https://deploy-preview-12796--kubernetes-io-master-staging.netlify.com/blog/2018/05/04/announcing-kubeflow-0.1/
/lgtm

/approve


[release-1.13] Include TLS resources in release test setup

Cherry-pick of #3636

Closed as wrong target branch


Ready for Python 3

I've done all I know how to do with getting the code working in both Python 2 and Python 3. I can't quite figure out how to run the tests completely successfully, but the code is working for me in an application in both Python 2.7 and Python 3.3.
I'm willing to do more for this to get accepted. I'm so glad to see kstateome doing something about this repo. Thanks.

Thanks for the contribution!
I'm out of the office until Tuesday but I will take a look at this as soon as I get back.

@chadgh So I'd really like to get some tests up and running through travis before I merge this (and any other commits as well).  My plan is to have some sort of tests running by the end of next week and then hopefully get this merged in.
Thanks again for your contribution.

Sounds good. Let me know if there is anything I need to change as you do the testing.
Thanks again.

@chadgh thanks for contributing.  There are some (very small) tests ran by Travis that have been merged to develop.  Could you update this branch with develop and push so that tests are ran?

I hope I did that correctly. I've never used Travis before. Commit 8aa5383 failed so I fixed the issue and committed those changes.
Assuming this build passes the tests, is the plan to merge these changes in? I noticed that Travis wasn't going to test anything against Python 3.X. Will that be added later?

Yes.  I'd like to merge these in.  Since this is the first build with Python 3 support could you do the following:
on this line https://github.com/kstateome/django-cas/blob/develop/.travis.yml#L4
add
- "3.3"
- "3.4"

This way Travis will go ahead and check Python 3.

Thank you, I'll do a final review of this tomorrow.

Sweet! Thanks so much for maintaining this project.


ImportError: cannot import name 'State' from 'dash_extensions.enrich'

An ImportError occurs when trying to import dash_extentions.enrich.State. This occurs when running the examples such as callback_serverside_output.py. Brief version info below:
dash                  1.20.0
dash-bootstrap-components 0.12.2
dash-core-components      1.16.0
dash-daq                  0.5.0
dash-extensions           0.0.56
dash-html-components      1.1.3
dash-interactive-graphviz 0.3.0
dash-renderer             1.9.1
dash-table                4.11.3
I've just rolled back to dash-extensions==0.0.55 and no problems there. Happy to provide more details as required.

Ah great stuff. Other than this it is working very nicely for me, so thanks for all your work!


Fetch submodule info on run instead of compile

Fixes #7
Code changes aren't too complicated; some of the changed lines are just formatting by rustfmt. Many of these can be ignored when viewing the PR diff with the "ignore whitespace" feature.
Happy Hacktoberfest!

Hey Thanks a lot for the contribution! We'll be checking the PR soon and letting you know!


Windows 10: possible problems with combinations of nw.js, node and node-usb to obtain working noble

This is a placeholder to document possible problems with combinations of nw.js node versions to obtain working noble rather than hijack other issues
At the present time, I am unable to build an nw.js application from source to obtain a working noble.
This comment gets edited as I document the issue, with possible re-open if I find something interesting
https://github.com/tessel/node-usb/issues/162#issuecomment-280881267

Reopened as https://github.com/tessel/node-usb/issues/162#issuecomment-280881267 is now changing to WIP with this title so as not to hijack the electron based issue.
I will be working on usb for the next couple of days and come back with a current status as time goes by.
Current status is I cannot get back to 👍 from last time I wrote with the current master.
Probably because I have not written down all the steps that I did last time or something I have overseen.
I edit this comment as time goes by to keep noise level down but indicate there is a perceived problem.

Next step:

a non nw.js test setup for node and node-usb with noble.

"I'll be back"

Closing this issue for now; feel free to re-open with additional details (though I can't guarantee I can help with nw.js).


[zh]translate Restrict a Container's Syscalls with seccomp

close https://github.com/kubernetes/website/issues/31869

/approve

Please notice that:

Renamed in EN: en/docs/tutorials/clusters/seccomp.md → en/docs/tutorials/security/seccomp.md
ZH version exists: https://kubernetes.io/zh/docs/tutorials/clusters/seccomp/

Please notice that:

Moved in EN: en/docs/tutorials/clusters/seccomp.md → en/docs/tutorials/security/seccomp.md
ZH version exists: https://kubernetes.io/zh/docs/tutorials/clusters/seccomp/

thanks, already fix the pr content

/lgtm


(preinstall) add freya to 'supported' distros

Simply to add freya to the recognised Linux distros in the preinstall script. Freya (i.e. Elementary OS 0.3) is based on Ubuntu 14.04 and the script completes successfully.

Thanks Rory.
(Ignoring the Appveyor CI network failures as this change does not affect Windows.)

@lovell :+1:


[turbopack] Unable to get the configuration of PostCSS from package.json

What version of Next.js are you using Turbopack in?
13.4.4
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
According to the document of postcss-load-config, PostCSS supports configuring it using the postcss field in package.json or a configuration file.
However, the postcss field in package.json is not working when I using PostCSS with Turbopack.

Then, I tried to create a .postcssrc.json and copied the same configuration into it, everything is in line with expectations.

Expected Behavior
Use postcss in package.json to configure PostCSS, which should get the same results as using a configuration file.
To Reproduce

Create a project that uses Next.js and PostCSS, for example: Next.js + Tailwind CSS Example
Removed postcss.config.js to prevent it from interfering with experiments
Configure Post CSS using postcss in package.json:"postcss": {
  "plugins": [
    "tailwindcss",
    "autoprefixer"
  ]
}

Run Next.js with Turbopack:pnpm next dev --turbo

Reproduction Repo
https://github.com/mogeko/movisea
PACK-2499

Closing as Turbopack as moved homes


Collective no logo placeholder

https://monosnap.com/file/xGsjI9Ei4T6971bNw07i0m6p0wzu1B

Looks good. Can you pls rebase on top of master and fix conflicts, so we can merge today?

@asood123 done :+1:


Also use cache dir as temporary directory, solving cross-disk copy errors

Prevent the following error from occurring: panic: failed to fetch targets: rename /tmp/klone-1469327034/modules/boilerplate /home/username/.cache/klone/47952611b91a53de34be5ba9fba781: invalid cross-device link

/approve


Bug Issues That resolves gee pull stash and apply

Still need to add another cmd. gee remove -- which will remove any repos from the gee.toml file. In addition to a gee cleanup which will cleanup any stale branches


Gene Ontology annotations for RNAs

Per convo with Chris Mungall, there is abundant GO annotations for lots of human RNAs. We can help set up an ingest for these if this is of interest (and you are not already ingesting them)

Hi Justin! Thanks for reaching out, this would be very interesting! I will send an email to you and Chris to schedule a meeting😃


Should we introduce the label property to align with other components?

If we decide to introduce the label property we should define what will have a priority and probably throw a warning if both ways to set a label are used.

Might be a nice convenience API. Light DOM content should take priority over the attribute, IMO. A warning is probably in order, yes.

Yeah, checkbox should be aligned with other components and have the label property, in 90% developers don't need anything but a plain string for checkbox labels.

A use case for us is that we ask our customer to accept terms and conditions in a form. We need both label and text.

If the customer submits the form without clicking the checkbox, we want to set an error message to the field.

I’m not sure, but this also sounds like a potential use case for https://github.com/vaadin/vaadin-core/issues/150 (a generic “field wrapper” element).
It might even be that <vaadin-form-item> could/should handle that role.
For exapmle:
<vaadin-form-item label="Terms and conditions" required error-message="You need to agree in order to continue">
  <vaadin-checkbox>Yes, I agree</vaadin-checkbox>
</vaadin-form-item>

It might even be that  could/should handle that role.

Forcing users to use a wrapper component might be not a good idea.
Also, since we already have required and error-message for form components like vaadin-text-field, in order to be consistent we shouldn't remove (and therefore produce a breaking change) those properties, but instead add them to vaadin-checkbox.

I’m just thinking this would make it easier to share the common functionality, for things like radio-group and checkbox-group.
But if you want to implement it separately for each element and have separate grouping wrappers, that’s fine by me. Maybe checkbox and radio-button should have label, required and invalid as part of their API, just for convenience 🤷♂
And I wasn’t suggesting that we should remove any current functionality from existing elements. Though, <vaadin-text-field> might want to use this common “field wrapper” element internally, though, to reduce duplicate implementation and reduce the possibility of inconsistencies.

@brp-oskar, btw, what would you expect to happen when a user clicks the ”Terms and conditions” label in your case? I’m expecting it to focus the checkbox, but not actually toggle it.

I think a wrapper could be useful when creating own webcomponents (we combine two date pickers for a date range field, it would be useful to be able to add a label, required and invalid state for the combined field). Also for a phone number field (combined country picker and text field).
How would the flow component be implemented with the wrapper? We need to be able to use the Binder with the wrapper and the actual checkbox. The Binder should bind to both the wrapper (label, required, error message) and the checkbox (value, invalid).
@jouni, I think only a focus is the best. A radio button group with a wrapper should only get focus, no select or click.

How would the flow component be implemented with the wrapper? We need to be able to use the Binder with the wrapper and the actual checkbox. The Binder should bind to both the wrapper (label, required, error message) and the checkbox (value, invalid).

I don’t have experience or good knowledge of Binder, but I would assume you can create a Flow component that exposes the contained components and their API so that you can access the value and invalid properties (in addition to the wrapper components properties). @Legioth can probably add more details.

A value input component (aka HasValue or Field) is most easily integrated with Flow it if supports required and readonly properties on the root element. Alternatively, the component integrator can also map the Java methods to any other DOM level action. Otherwise, those features will be no-ops from a UX point of view, but still enforced on the Java side.


Add BitBucket post_receive_webhook rule for autodeployment of commits

BitBucket
Status

pack extension, complete

Description

Add rules/post_receive_webhook.yaml which calls packs.deploy that was added in PR#????
Add emacs editor saves to .gitignore
Document new rule in README.md.

Checklist (tick everything that applies)

[X] Metadata: pack.yaml, icon, structure (required for new packs)
[X] Version bump (required for changed packs)
[ ] Code linting (required, can be done after the PR checks)
[ ] Tests (not required but really recommended)

Thanks for the contribution.

Great, thanks.
I will go ahead and merge it into master.


About RMS parameter computation and PSD curve analysis

In contact.engineering, I find two problems.
First, in RMS parameter computation, I find RMS height and slope can be computed but RMS curvature is missing. Plus, I also suggest scan size and pixel size of the profiles can be also listed in the window where computed RMS parameters of all profiles are presented. This helps copying data of both size of profile and RMS parameter.
Second, in PSD curve analysis, I find the output PSD curves have no data when frequency equals zero. In ideal case, it should be zero at q=0. I think the gap between the first point and q=0 cannot be ignored because Cq values in this region are greater than Cq at higher frequency. In other words, this gap also has some contribution to overall PSD. For example, when computing RMS height of a profile by integrating PSD curves, without considering q=0, RMS height equals 0.7 unit, while RMS height equals 0.8 or close to 0.9 unit if q=0 is involved.

Hey Rick, I guess I are referring to the web app (https://github.com/ContactEngineering/TopoBank).
Concerning the missing RMS curvature, where did you look? For example, the "Roughness Parameters" analysis function
result shows such a value:

Or do you mean in case of line scan? Here the values are still missing in the "Roughness Parameters" results, but you can find them if you press "open" for the "Curvature Distribution" results:

But yes, probably we should also add that for line scans to "Roughness Parameters".
@pastewka , @AntoineSIMTEK could help with the second point?

Regarding the second point, the PSD at q=0 has no meaning. It depends on the mean value of the topography, which is zero in the webapp since the average value is always subtracted. (In that sense it is correct that the value should be zero, but I wouldn't display this.)

For the first point, I refer to line scan. In roughness parameter function, curvature is missing. However, in curvature distribution function, I did not find specific value option. But I see your web app has this option. Is there anything wrong with my side? Plus, the screenshot also indicates it fails to analyze curvature distribution of some of my profiles but I did not understand the reasons.
For the second point, I understand it. I care this point because my analysis involves integrating PSD curves from Cq at q=0 to Cq at q=max. The gap between q=0 and first none zero q influences the final computed results.
Thank you very much for the help.

@Rick224339, did you press the "Open" button? Currently, the "RMS curvature" values for line scans are only there.
I agree we should add that to "Roughness parameters". I've added an issue for that in the repo of the web app: https://github.com/ContactEngineering/TopoBank/issues/660
Because of the reason for failure. Could you post an example for the reason or share your data with me inside the web app?

See 'Open' button. Sorry for not noticing that. Now I can check RMS curvature in this place.
The errors are (two examples):

Traceback (most recent call last):
File "/app/topobank/taskapp/tasks.py", line 127, in perform_analysis
result = analysis.function.eval(subject, **kwargs)
File "/app/topobank/analysis/models.py", line 288, in eval
return self.get_implementation(subject_type).eval(subject, **kwargs)
File "/app/topobank/analysis/models.py", line 340, in eval
return pyfunc(subject, **kwargs)
File "/app/topobank/analysis/functions.py", line 308, in curvature_distribution
rms_curv = topography.rms_curvature_from_area() if topography.dim == 2 else topography.rms_curvature_from_profile()
File "/opt/conda/lib/python3.7/site-packages/SurfaceTopography/HeightContainer.py", line 85, in getattr
', '.join(self._functions.keys())))
AttributeError: Unkown attribute 'rms_curvature_from_profile' and no analysis or pipeline function of this name registered (class DetrendedUniformTopography). Available functions: mean, min, max, scale, detrend, transpose, translate, to_matrix, to_netcdf, to_nonuniform, make_fft, bandwidth, derivative, fourier_derivative, domain_decompose, plot, fill_undefined_data, mirror_stitch, interpolate_bicubic, interpolate_fourier, window, filter, shortcut, longcut, autocorrelation_from_profile, autocorrelation_from_area, power_spectrum_from_profile, power_spectrum_from_area, rms_height_from_profile, rms_height_from_area, rms_gradient, rms_slope_from_profile, rms_laplacian, rms_curvature_from_area, checkerboard_detrend, variable_bandwidth, scale_dependent_curvature_1D, scale_dependent_curvature_2D, scale_dependent_slope_1D, scale_dependent_slope_2D
Analysis failed for subject 100k_sample1_FIXEDv2p1.asc. Traceback:
Traceback (most recent call last):
File "/app/topobank/taskapp/tasks.py", line 127, in perform_analysis
result = analysis.function.eval(subject, **kwargs)
File "/app/topobank/analysis/models.py", line 288, in eval
return self.get_implementation(subject_type).eval(subject, **kwargs)
File "/app/topobank/analysis/models.py", line 340, in eval
return pyfunc(subject, **kwargs)
File "/app/topobank/analysis/functions.py", line 308, in curvature_distribution
rms_curv = topography.rms_curvature_from_area() if topography.dim == 2 else topography.rms_curvature_from_profile()
File "/opt/conda/lib/python3.7/site-packages/SurfaceTopography/HeightContainer.py", line 85, in getattr
', '.join(self._functions.keys())))
AttributeError: Unkown attribute 'rms_curvature_from_profile' and no analysis or pipeline function of this name registered (class DetrendedUniformTopography). Available functions: mean, min, max, scale, detrend, transpose, translate, to_matrix, to_netcdf, to_nonuniform, make_fft, bandwidth, derivative, fourier_derivative, domain_decompose, plot, fill_undefined_data, mirror_stitch, interpolate_bicubic, interpolate_fourier, window, filter, shortcut, longcut, autocorrelation_from_profile, autocorrelation_from_area, power_spectrum_from_profile, power_spectrum_from_area, rms_height_from_profile, rms_height_from_area, rms_gradient, rms_slope_from_profile, rms_laplacian, rms_curvature_from_area, checkerboard_detrend, variable_bandwidth, scale_dependent_curvature_1D, scale_dependent_curvature_2D, scale_dependent_slope_1D, scale_dependent_slope_2D

Thanks! This seems to be a bug in case of uniform line scans. Are those failures related to uniform line scans exclusively?
I've opened other issues for this:

For underlying package: https://github.com/ContactEngineering/SurfaceTopography/issues/95
For the web app:  https://github.com/ContactEngineering/TopoBank/issues/663

It seems this bug exists in both uniform and non uniform cases. For more examples, please see ceramic quarry 1 quarry 2 labeled by floor shoe project which are published surface recently by me. It has 36 profiles in total but in curvature distribution function, it fails to analyze 26 profiles of all.
Thanks for the help.

I also appreciate it if RMS curvature can be listed in roughness parameter function for line scans. Plus, if scan size and pixel size are also listed in the same window with these parameters, this will be helpful and convenient to check the scale dependence of RMS parameters.

Hi @Rick224339 - note that there is a scale dependent slope plot now in the web app. We will also add a scale-dependent curvature plot in the next release. This will probably help you with the things you are trying to look at.
I agree that scan size and pixel size should also be displayed in this table, as those rms parameters don't make sense by themselves.

@pastewka , I would retrieve scan size and pixel size by topo.physical_sizes and topo.pixel_size, correct?

That's correct... Although I am not sure whether NonuniformLineScan has pixel_size. There is a bandwidth function that should exist for all containers and yields the same information.

Regarding the additional values in the table, I've opened a new issue in Topobank: https://github.com/ContactEngineering/TopoBank/issues/677
Regarding the original issue here, this should be solved by using release 0.94.0 of SurfaceTopography in the web app.
This is planned for the next release: https://github.com/ContactEngineering/TopoBank/milestone/29
Closing this.


Memory issue

I tried with this image https://38.media.tumblr.com/a123606e52db443841a6bb982d93febe/tumblr_n7a40sXB7P1r2geqjo1_r1_500.gif
the memory keep increasing, though memory is released when I dismiss viewcontroller.

It seems that we have met the same problem.

me too.🙂 2.9M gif,but memory is 107M. Why?

any solution for the above problem?


Update the README to use recent package details and usage examples, as well as the outdated Asciinema demo.

Updated READMEs, asciinema demo is good enough for now...


Calendar

If you have ever lost track of which day of the week is today or the number of days in that particular month, you should build a calendar yourself. The Calendar is written in the C programming language, and this Calendar assists you in determining the date and day you require. We can implement it using simple if-else logic and switch-case statements. The display() function is used to display the calendar and it can be modified accordingly. It also has some additional functions. The GitHub link of the calendar has been provided below.

Can i work upon this issue ??


bump tokio and actix and mysql

note: based on #56 ... Merge whichever first, but this PR currently has target branch of the former.

Sorry, I didn't realize I was merging in the wrong order, can you clean up the conflicts?

Shoehorned feature-guard of mysql into this PR. Reason: the mysql feature is used by me in private projects and shouldn't block PRs in normal circumstances. In this case, it's the mysql_common crate that doesn't build with crate2nix, but builds fine with cargo. I'll look into that out-of-band. (#59)


Add ecosystem test for homeassistant

Extends #2942 with another repository.
This one might be too big it takes 5 minutes haha — but it's faster than Windows still!

Home assistant uses a custom index, no build and a musl based python 3.12 for their deploys, i think we need to replicate this if we want to use it as a test


Some work toward fixing ARM builds.

Add some docker debugging.
Re-enable ARM PR builds.

@dotnet-bot test ci please


Neal friendly

Checkout this branch -- if it works then pull it into EDGAR -- if not then leave a review with necessary changes suggested

Build on what Kamil did.
'process_nflx.py' missing the module import step. Fixed.
Adding a folder containing a .py class to determine if a file has annotation.
In the main folder of EDGAR, there is a .py file that can loops through the filed downloaded and produce an array that tells whether a file has annotation (based on the tags in tag_list.txt).


like sending funds to another account Help!!!!!

Hi, could you tell me how I can send funds to another account through your api?

@kenyi019 you need to import the paper wallet back into a software or online wallet.

lack of negative feedback to last suggestion -> bug closed


Advanced command(s) for generating or dumping a config.json

This is handy for our testing and debugging, and also can serve as a reference for what fields we support in the config file.

Amazing @mrmr1993 thanks for opening this issue!

Fixed in #8648.


Browserstack GitHub actions

Re-instates Browserstack workflow. Unsurprisingly this fails on a credentials error as the browser stack keys will need updating in the secrets.

I can't approve this as I raised it but so happy with this. I'd check two things with @luke-hill before we hit merge:

Happy sticking with the latest versions for now (my preference) or should we pin to the same versions that are in the Jenkinsfile
Do the build names in the BrowserStack UI look OK?

1 - yeah I prefer the latest I think but will merge and check in with Luke when he's back tomorrow
2 - yup I peeped and they and both the build and sessions names are 🆗

There's a few things I want to change from this. But given this is just running alongside things for now it can stay as is (As this will run everything twice, once for Jenkins once for GHA I believe).
Do we have a follow-up ticket to remove the Jenkinsfile? If so we can add the required changes there. Some of the changes I'll want to get done soon as they break some existing features we kinda relied on.


Added ArcSight as a SIEM option

@ilantz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


fix event writer implementation and add flush

Signed-off-by: dellThejas<EMAIL_ADDRESS>Change log description
Added flush for event writer
Updated implementation of Event Writer
Purpose of the change
#340
What the code does
Flush implementation added to event writer similar to Byte writer
Also, event writer will not be return the receiver anymore. This implementation helps setup the flush, and makes the write operation easier to implement for users.
How to verify it
ran existing tests

Codecov Report

Merging #341 (b9c0e2a) into master (792b81d) will decrease coverage by 8.92%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #341      +/-   ##
==========================================
- Coverage   75.09%   66.17%   -8.93%
==========================================
  Files          47       25      -22
  Lines       11633     6066    -5567
==========================================
- Hits         8736     4014    -4722
+ Misses       2897     2052     -845

Impacted Files
Coverage Δ

wire_protocol/src/mock_connection.rs
17.34% <0.00%> (-57.21%)
:arrow_down:

retry/src/retry_async.rs
39.28% <0.00%> (-55.31%)
:arrow_down:

retry/src/retry_result.rs
35.71% <0.00%> (-50.01%)
:arrow_down:

retry/src/retry_policy.rs
61.53% <0.00%> (-38.47%)
:arrow_down:

controller-client/src/mock_controller.rs
7.24% <0.00%> (-32.51%)
:arrow_down:

shared/src/lib.rs
48.29% <0.00%> (-32.10%)
:arrow_down:

wire_protocol/src/connection_factory.rs
59.31% <0.00%> (-17.67%)
:arrow_down:

wire_protocol/src/error.rs
15.38% <0.00%> (-15.39%)
:arrow_down:

wire_protocol/src/connection.rs
0.00% <0.00%> (-13.16%)
:arrow_down:

connection_pool/src/connection_pool.rs
85.08% <0.00%> (-3.81%)
:arrow_down:

... and 29 more


Conversion between euler and quats doesn't seem stable

While creating a pygfx Controller I noticed the following:
Moving from euler to quats and back is not stable.
Here's an example:
In [11]: la.quat_to_euler(la.quat_from_euler(np.array([math.pi/2, math.pi/180,0])))
Out[11]: array([1.57079633e+00, 1.73472348e-18, 1.74532925e-02])

Almost as if the last two items of the array are reversed.

In code:
import math
import numpy as np
import pylinalg as la

la.quat_to_euler(la.quat_from_euler(np.array([math.pi/2,math.pi/180,0])))

Looked at scipy, and that one works:
import numpy as np
import pylinalg as la

from scipy.spatial.transform import Rotation

quat = np.array([0.70707986, 0.00617059, 0.00617059, 0.70707986])

la.quat_to_euler(quat)
Rotation.from_quat(quat).as_euler("XYZ")

Would you mind opening a pull request with a unit test that demonstrates the failure?

Done: https://github.com/pygfx/pylinalg/pull/87
It seems the issue has to do with the order. The default uppercase "XYZ" has a different result than lowercase "xyz".

https://github.com/pygfx/pylinalg/blob/92a83a223d4580c4438d54c78d23387f781f3faa/pylinalg/quaternion.py#L296
Using uppercase letters apparently makes that axis extrensic. I don't really understand what that means.

The three rotations can either be in a global frame of reference (extrinsic) or in a
body centred frame of reference (intrinsic), which is attached to, and moves with, the object under rotation

https://docs.scipy.org/doc/scipy/reference/generated/scipy.spatial.transform.Rotation.from_euler.html
My 2cts:

Document the behavior
give quat_to_euler also an order
have quat_to_euler and quat_from_euler use the same default order.

If you want to take a shot at it, you're more than welcome. We're shorthanded at the moment.

Thanks for the offer. Am very busy, but who knows.


Use android logging in PullServerHandler

should fix #42

thx. i also pushed this into the play store just now. let's see if that fixed the issue.


Upgrade to Quarkus CXF 3.9.0

@aldettinger if this PR passes as is, then I think there is no need to stop the CQ 3.9.0 release train. QCXF 3.8.1 (that we currently use in CQ) and 3.9.0 are quite similar.

@ppalaga Let see how it goes, the release is not working anyway. So there might be an opportunity integrate this if I need to restart from scratch.

@aldettinger passed


Cloud Storage API: Setting storage.Object.ContentType does not actually control the ContentType

kellegous on 24 Mar 2014 at 12:30:
What steps will reproduce the problem?
1. Run the given example.
2. Use gsutil (or curl) to examine the reported Content-Type of the object
3. Cry

What is the expected output? What do you see instead?
I would expect the object to have the ContentType I specified. Instead,
text/plain is used as the Content-Type.

What version of the product are you using? On what operating system?
46967f157fd4008b48fe78dcbc97ab67006a5658

Please provide any additional information below.
There are a number of issues here. First is that storage.Object purports to
have a ContentType field that seems to be completely disregarded by the Cloud
Storage API. The second issue is that, by default, googleapi.go tries to
DetectContentType on the io.Reader you provide ... unless you read the source
and see that the Reader can be pimped as a ContentTyper. This is kind of a "Not
cool, bro." kind of API. This is especially true in that I did not expect the
API to use uploadType=multipart even when I was uploading a simple object, so I
had no reason to consider that my stream would need to be typed apart form my
object.

ianrose14 on 26 Aug 2014 at 3:51:
Hi<EMAIL_ADDRESS>
We have had similar problems and in talking to enterprise support we got the
following suggestion.  Haven't quite had time to try it yet but hopefully it
will work:

Having Go library accept media content type will require few changes and a new
release, which might not suit your transition timelines. MediaType in Object
struct is not writable so we will need to introduce a new field to inject this
value to the Http request.

Here is a workaround that we think should work in the meantime. Please keep a
check on library upgrades to make sure this doesn't break in future.

a.) Create a wrapper over io.Reader object:

type StorageMedia struct {
io.Reader
Ctype string
}

And define a method.

// Returns Media Type.
func (sm StorageMedia) ContentType() string {
return sm.Ctype
}

b.) Now to upload an object, create a reader of type StorageMedia:

reader := StorageMedia{content, "text/css"}

And pass it to call upload service:

storage.NewObjectsService(service).Insert(bucket, &storage.Object{Name:
object}).Media(reader).Do()

Successfully auto-migrated from code.google.com:
https://code.google.com/p/google-api-go-client/issues/detail?id=55

Using the ContentTyper should solve this problem.
Closing, but feel free to reopen if you can't get it to work and post your simple test case that demonstrates the problem.


New page: Board Policies

We'd like to add a new page about Board Policies, with a list of policies linking to the PDF of each in our library/archive, and its date of adoption. Initially I thought these links could be on the About page, but there are approximately 70 ... so, is it possible to create a new page for this?
I can send a mock-up of design, and spreadsheet with links/dates.

@shrayshray - we can create a new page for this. The mock-up, as always, would be very helpful!

@reginafcompton below is a a mock-up, and I'll post the spreadsheet of links soon!

@reginafcompton @hancush would it be possible for Omar and I to have access to edit/update this page once it's set up?

@shrayshray - we need a little time to discuss options. Can we get back to you by early next week?

Of course!
From: Regina Compton<EMAIL_ADDRESS>Sent: Thursday, March 15, 2018 13:12
To: datamade/la-metro-councilmatic
Cc: Ray, Shelly; Mention
Subject: Re: [datamade/la-metro-councilmatic] New page: Board Policies (#265)
@shrayshrayhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshrayshray&data=01|01|rays%40metro.net|d2241fd247c34a9c118e08d58ab1124d|ab57129bdbfd4cacaa77fc74c40364af|0&sdata=iyhXNpgpBETxIXUWZC2kWALFkgKvmhuROX6BoKLCues%3D&reserved=0 - we need a little time to discuss options. Can we get back to you by early next week?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdatamade%2Fla-metro-councilmatic%2Fissues%2F265%23issuecomment-373507729&data=01|01|rays%40metro.net|d2241fd247c34a9c118e08d58ab1124d|ab57129bdbfd4cacaa77fc74c40364af|0&sdata=dvV0q4CNw%2BVwijhwYU0WpNZxEhOwD2auk7Uzr5gCbI8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAaw49Oa7h2LjztB9ycDkl_2tKRfAM-Eeks5tesspgaJpZM4Sjb_c&data=01|01|rays%40metro.net|d2241fd247c34a9c118e08d58ab1124d|ab57129bdbfd4cacaa77fc74c40364af|0&sdata=tOyk%2FRacF1G10HkI4tJDKbMaM7Ai42cT5kbxauS6x74%3D&reserved=0.

@shrayshray - we talked about implementation options, and we see two ways forward:
(1) DataMade creates a new page and periodically makes content changes, whenever requested by Metro.
(2) DataMade adds a Content Management System to Councilmatic - it would allow Metro admins to edit text on any of the static views (e.g.,  the new board-policy page and the about page).
The first option is very lightweight, but does not give Metro much freedom, i.e., only DataMade can make editorial changes.
The second option would require considerable time to implement (around 40 hours), but it will offer Metro greater autonomy.
We can put together a more precise estimate for the second option, if it sounds like something you'd like to consider. It could be an additional scope or we could use maintenance hours for it. Let us know!

(Notes for development)
Relevant links for building a CMS:
https://github.com/datamade/openness-project-nmid/blob/e6fd35e56cfd17f84b6a1fcbe046893ea463180e/pages/models.py#L7
https://github.com/datamade/openness-project-nmid/blob/e6fd35e56cfd17f84b6a1fcbe046893ea463180e/pages/admin.py#L9
https://github.com/datamade/openness-project-nmid/blob/e6fd35e56cfd17f84b6a1fcbe046893ea463180e/camp_fin/base_views.py#L524
https://github.com/datamade/openness-project-nmid/blob/master/camp_fin/views.py#L46

The Board Policies page is on hold for the moment, but we'd still like to move forward with developing option 2: a CMS for Metro admins to edit static text on the Councilmatic site, such as the About page, and Board Bios and Titles (see #336).
Does the estimate of 40 hours to develop still seem accurate?
And does it seem reasonable to set this as a December milestone?


Correction for raw affiliation Building Blocks for Future Electronics Laboratory

Correction needed for raw affiliation Building Blocks for Future Electronics Laboratory
raw_affiliation_name: Building Blocks for Future Electronics Laboratory
new_rors: 02sh10804;01w108f05
previous_rors: 02sh10804
works_examples: W3093917816
contact: 8348972c11384288ffed2d30c2df9a92:1733882d98f7fc388b2c7fc1ab @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Adding Username and Pass via login() function

Created a handler which obtains csrf token, then allows login by setting cookies and headers.
We should probably review how this is done since it's not very clean.
fixes: demisto/etc#19401

@amshamah419 looks good. Note my 2 commits (env var support and changelog).


Rename tract-details.js and sortable-table.js and update their documentation

Renames tract-details.js  to plots.js and renames sortable-table.js to table.js. This PR also updates the docstrings of all functions in these two files for auto-documentation with sphinx-js.

LGTM. Merging.


Analysis of tiny flag

I have included the mention that the tank speed, shot speed and jump height do not change, since it might not be as intuitive. Seeing a tank twice as small, it is nice to know that all other factors are not made weaker.

Agreed with all and patch pushed; thanks for the feedback, @allejo!


Redundant require('@vue/devtools-api') in the CJS prod build

Version
4.1.3
Reproduction link
unpkg.com
Steps to reproduce
Cmd + F, search for require('@vue/devtools-api') on the page
What is expected?
The require statement should be tree-shaken away from the bundle, because non of its exports are used in the prod bundle of vue-router, and the package is of sideEffects: false:
https://github.com/vuejs/devtools/blob/ba54bb770a829429226a630dd5dbedcf596f27ef/packages/api/package.json#L9
What is actually happening?
It remains in the CJS prod bundle

Originally reported at https://github.com/vuejs/devtools/issues/1932
As my comment on the issue, it's not a big issue as most users would use the esm-bundler version, which could be correctly tree-shaken.
But this issue still indicates that something might be wrong in vue-router's rollup config.

It's funny, we were just talking about this with the Nuxt team yesterday for pinia: https://github.com/vuejs/pinia/pull/1561
It does seem like a bug in rollup (or maybe intentional for perf reasons) but we did find a way to remove it so I will just apply the same change


State-Driven Dynamic CSS: v-bind don't work inside media queries

Version
3.2.2
Reproduction link
https://sfc.vuejs.org/
Steps to reproduce
v-bind after max-width and min-width inside media queries do not provide any data
What is expected?
Expected to see red font with screen width less than 700px
What is actually happening?
We get this css code after compiling:
@media only screen and (max-width: v-bind(width)) {
div[data-v-f13b4d11] {
color: red;
}
}

@harmyderoman
your repro link is broken.

@harmyderoman
your repro link is broken.

fixed

You can't use CSS vars in media query declarations and since Vue relies on them, this is not possible.


Update artemis-jms-client-all to 2.30.0

About this PR
📦 Updates org.apache.activemq:artemis-jms-client-all from 2.19.1 to 2.30.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #411.


Add napari.yaml to first plugin file layout

Description
Reading through the first plugin tutorial it seemed like napari.yaml was missing from the initial file setup stage.
Type of change

Improved docs
References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Thanks,
This wasn't an oversight... but I did struggle a bit with whether to include it there.  If we change this here I think we also might want to modify the text below that instructs the user to create the empty manifest file. (Since now it would have already happened)

Add a napari.yaml manifest¶
Create an empty plugin manifest file at napari_hello/napari.yaml We will use this file to tell napari:

I think I'm with @dstansby here and I would add it manually at the beginning in that touch as it is nice to see the full set of critical files that we will need. It primes you that a few steps later something will be coming that relates to this napari.yaml thing that you created.
I would make it below something like

Add a napari.yaml manifest¶
If you have not already done so, create an empty plugin manifest file at napari_hello/napari.yaml

I would make it below something like
Add a napari.yaml manifest¶
If you have not already done so, create an empty plugin manifest file at napari_hello/napari.yaml

works for me too!  just don't want it have it come off like we're creating a new file in both sections

👍 I updated the line below as suggested


Keras dev

Hi @pgleeson.
I am currently working on updating the readme while trying to work on creating a convolution example that works. I want to test that the batch normalization and dropout nodes currently work well, so I might update the Keras model on the MNIST data to include those layers.
I opened this draft pull request so that the changes I make can be tracked. You can merge these changes at any time.
Thank you.

@Onoyiza I'll just merge in the latest version of the readme and check it through. Feel free to update with more info if you like


difflicious and diffx

Hi,
I tried reaching you out on twitter but the tweet must've got lost among others. I always thought that the way you designed difflicious internals is superior to what I did in diffix, but up until that moment I was able to implement everything I needed in diffx.
Recent bug issue(https://github.com/softwaremill/diffx/issues/418) pointed out some flaws in the diffx that cannot be fully fixed without major rewrite of internals. Of course, I could make that rewrite but that would mean doing basically the same thing what you did in difflicious. I don't really see a point in fixing diffx that way, when there is already a better version of it implemented :) While implementing diffx and later maintaining it was a great journey for me, I think that objectively the best I can do now is to deprecate it and redirect users to your library. However, there are some users of diffx out there and I would like to do it right, and provide a smooth transition for them.
First, I would like to make sure that you are planning to maintain difflicious and you have a capacity to do that. These days my capacity is fairly limited by other projects but I will be happy to help if you need any help.
Second, I am considering writing a scalafix rule to ease the migration. I guess rewriting imports and class names would cover most of the cases. Do you think it is a good idea?
Third, difflicious doesn't support automatic derivation. I understand reasoning behind that decision. I never use auto derivation in my own projects. Still, there are some people that do, and it is a nice feature especially when prototyping/ trying out new things. Would you consider adding it? (maybe it could be done as a separate module?)

Hi @ghostbuster91 thanks for the kind words. Yeah I did not receive any message from you on Twitter..definitely had similar things happen before 🤔

I do plan to maintain this lib and still got some big improvements I'm hoping to implement, but time is limited these days and whatever I have I try to push Doobie a little bit closer to 1.0. Help will be much appreciated and I'm more than happy to add you as a maintainer :)
I think the lack of auto-derviation will be a blocker for a useful scalafix rule. Happy to make auto-derivation available under a separate import (like Circe) as I have wished for it a few times while debugging legacy tests using classic assertions ;)

Understood and thank you. I won't have much time before December but after that I can try contributing the auto-derivation. It seems that we have some vague plan of moving forward. So to sum up:

add the auto-derivation to difflicious
put diffx into maintenance mode
scalafix rule for migration from diffx
test the migration and see if there is still anything missing that should be added to difflicious
final deprecation of diffix and redirection of users to difflicious

Let me know if you think that something is missing or should be done in different order.

Yep sounds good to me thanks!