Surfacing of actual Termination Reason in Step Status

Current behaviour
Currently, Tekton only reports Completed and Error as Terminated Reasons in Step status after the Step terminates.
The status Error is also applied to the Steps if it "times out" or if the previous Step failed and caused this to be "skipped".
Likewise, the status Completed is applied to the Step if it actually "completed with exit code 0" or if the Step actually errored but the Task set onError: continue for that Step.
The table below summarizes it.

Termination Reason
Meaning

Completed
Finished successfully with exit code 0

Completed
Errored but ignored since onError was set to continue.

Error
Actually failed with a non-zero exit code.

Error
timed out (but only the logs indicate that it timed out)

Error
skipped because the previous Step failed.

This makes getting true visibility into the Steps challenging since the Termination reasons Completed and Error could mean different things.
Proposed behaviour
In order to get better visibility into what's happening in the underlying Steps, here is the proposed changes to the Termination Reason in the Step status.

Termination Reason
Meaning

Completed
Finished successfully with exit code 0

Continued
Errored but ignored since onError was set to continue.

Error
Actually failed with a non-zero exit code.

Timeout
timed out (but only the logs indicate that it timed out)

Skipped
skipped because the previous Step failed.

Cancelled
The step was stopped by user

/kind bug

/good-first-issue

Hi @chitrangpatel , Recently a Termination Reason Canceled has been added
https://github.com/tektoncd/pipeline/blob/a7d15ce59876405750154748e31312f3c63b17ab/pkg/entrypoint/entrypointer.go#L195-L201
Termination Reason: Canceled
Meaning: The step was stopped by user
Should this reason also be added to the table?

Yes, it should @chengjoey!

@shankarpentyala07 PTAL at the proposed changes to surface actual termination reason, thanks!

/assign @shankarpentyala07

Hey @shankarpentyala07! I just wanted to check if you are actively working in this issue. If not I would be happy to help with this. Thanks a lot! 😄

Hi @renzodavid9 ,Thanks for checking.
I am yet to start working , I would be happy to work together. Shall we have one meeting and discuss the changes. My email is<EMAIL_ADDRESS>, available any time apart from 9am-11am PST.

/unassign @shankarpentyala07

Hi @renzodavid9 - I have unassigned , please proceed.

/assign

Got it! Thanks @shankarpentyala07! I just assigned this


Bump buck to v2<IP_ADDRESS>

This should fix our current Android test failures.

Confirmed, BUCK issue fixed.


Response with HIGH

From DS18B20 Datasheet:
If the DS18B20 is powered by an external supply, the master can issue “read time slots” (see the
1-Wire Bus System section) after the Convert T command and the DS18B20 will respond by transmitting
0 while the temperature conversion is in progress and 1 when the conversion is done.
Please show me right way how on 1-wire line set HIGH level with you library?
digitalWrite(2,HIGH) - is it right way?

There is currently no publicly exposed function to send or receive a single bit, but that would indeed be an interesting functionality. There are internal functions to send/receive bits, that are used by bytes send/receive functions, so it's mostly an interface problem, the functionality is already implemented. I'll take a look to see how these functionalities can be exposed.
I wouldn't recommend to directly modify the pin output, because properly sending a bit is a little more involved (you have to wait for the master signal, then respond with the bit), but maybe that would work anyway. However, you never have to write a HIGH level, because the wire is at 5V by default (thanks to the pullup resistor). The simple fact of doing nothing is enough to send a 1 bit. In the case you want to write a 0 bit however, the bus must be pulled low, but you have to wait for the master signal to do it, otherwise you don't know when to release the bus, and if you never release the bus there won't be any further communication. Also, trying to directly write on the bus will necessarily interfere with the library that thinks it has exclusive control of it. The library would actually think it's the master misbehaving.

I think you get a lot of experience with the implementation of DS18B20 ))

I've added functions in the library to send individual bits (with the possibility to repeat the same bit until new order), and also to be notified of individual bits received (but that's not of use in the case of a DS18B20 implementation). To test everything, I've modified the sample sketch to implement a DS18B20, this should demonstrate how to use most features of the library with a concrete example.

Cool!!


Add optional title and desc elements to victory-label

For accessibility reason it would be nice to add <title> and <desc> tags to victory-label. This is helpful, for example, if the normal label text is truncated (for space reasons) and one wants to provide the full title in a browser tooltip.
This PR adds title and desc props to victory-label. They are optional and render their respective SVG tags only when provided. There is also an example added in the demo/ folder.

@sto3psl thanks for this work!


chore(avm)!: dont compress public bytecode

The bytecode now fits uncompressed (as expected) in the max public size (600kB, which we expect to lower to 30k or 100k)
Thanks Noir + Alvaro!

#8623  👈
master

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

Join @fcarreiro and the rest of your teammates on  Graphite

Merge activity

Sep 18, 10:30 AM EDT: @fcarreiro merged this pull request with Graphite.


ts-angular-jsonapi added to implementations section

Thanks! Would you mind moving this to the end? We usually add them in chronological order.

No problem! Now is on the end.
My intention was to keep the angular solutions together.
Regards!

Thanks @pablorsk!


Add projectId config option to GCS techdocs publisher

Fixes #13049
Hey, I just made a Pull Request!
Add projectId config option to GCP Cloud Storage techdocs publisher. This will allow users to override the project ID, instead of implicitly using the same one as found in a credentials bundle.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I haven't added a test for this because fromConfig is not yet undefined, and I can't see how you'd test this without breaking changes to the API (that would allow passing some kind of mockable StorageClientFactory to it).


cockpit: 312 -> 313

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cockpit is: Web-based graphical interface for servers
meta.homepage for cockpit is: https://cockpit-project.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 313 with grep in /nix/store/034pcyccb22n8z2pzh2c2jqq2hlq40rq-cockpit-313
found 313 in filename of file in /nix/store/034pcyccb22n8z2pzh2c2jqq2hlq40rq-cockpit-313

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cockpit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/034pcyccb22n8z2pzh2c2jqq2hlq40rq-cockpit-313 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cockpit https://github.com/r-ryantm/nixpkgs/archive/7de4580c91bcf551928676e37cedf28c068a60d0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7de4580c91bcf551928676e37cedf28c068a60d0#cockpit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/034pcyccb22n8z2pzh2c2jqq2hlq40rq-cockpit-313
ls -la /nix/store/034pcyccb22n8z2pzh2c2jqq2hlq40rq-cockpit-313/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

cockpit

Maintainer pings
cc @lucasew for testing.

Result of nixpkgs-review pr 296394 run on x86_64-linux 1

1 package built:

cockpit

Result of nixpkgs-review pr 296394 run on x86_64-linux 1

1 package built:

cockpit

@NixOS/nixpkgs-merge-bot merge


Installer ignores suggested default option for user choice (current or Flowforge) and bails when user hits enter

Current Behavior
Installer asks three questions during installation and the linux convention is that the uppercase option is default, and if the user submits empty input then that default option is used.
This doesn't work properly for the last question (and potentially others), the installer then bails and the user is left unaware how to proceed except to reinstall.
Expected Behavior
As expected with the capitol option being accepted as user default, and the option to use the Flowforge user is chosen when the user just hits enter with no other input.
Steps To Reproduce
On a pi 3A+ (512mb with 2/5ghz wifi), be patient as it appears to stall during npm but is just slow.
Run installer on fresh copy of raspberry pi OS 32bit headless.
Accept first question to install NodeJS, then expect following output (truncated):
Installing latest Node-RED as a stack
**************************************************************
installing stack node-red@latest
node-red@latest is currently<EMAIL_ADDRESS>installed stack<EMAIL_ADDRESS>**************************************************************
 Do you want to run FlowForge as a service?
**************************************************************
Y/n: y
**************************************************************
 Do you want to run FlowForge as the current user (pi)
 or create a flowforge user?
**************************************************************
Current/FlowForge (c/F):
**************************************************************
 Not C or F
**************************************************************
pi@rpi3a0001:/opt/flowforge $

Environment

FlowForge version: latest install instructions + zip

It's missing a block to set the default
https://github.com/flowforge/installer/blob/0d52cb8b3201d09561c3ed51d2755e114feea772/install.sh#L208-L213
should be:
      read -p "Current/FlowForge (c/F): " cf
      if [ -z "${cf}" ]; then
          cf=F
      fi
      if [[ "$cf" == "c" ]] || [[ "$cf" == "C" ]]; then

        FF_USER=`id -u -n`
        FF_GROUP=`id -g -n`

Fix should hopefully go out with the next release on Thursday


⚠ Bofrost.at has degraded performance

In 282c000, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1250 ms

Resolved: Bofrost.at performance has improved in 5818699 after 10 minutes.


✨ Add check ID

What kind of change does this PR introduce?
Enhancement to our structured results. Adds a static Check ID for all checks, along with updates to check validation process to make sure the ID is unique. Only impacts Json results.
I also ran fieldalignment on the files where I made changes to struct members.

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
Json output only has name for identifying the check
{
    "details": null,
    "score": 10,
    "reason": "no binaries found in the repo",
    "name": "Binary-Artifacts",
    "documentation": {
        "url": "https://github.com/ossf/scorecard/blob/main/docs/checks.md#binary-artifacts",
        "short": "Determines if the project has generated executable (binary) artifacts in the source repository."
    }
},

What is the new behavior (if this is a feature change)?**
Adding a uint as a unique ID allows users to filter/search for checks without string comparison.
{
    "id": 3,
    "details": null,
    "score": 10,
    "reason": "no binaries found in the repo",
    "name": "Binary-Artifacts",
    "documentation": {
        "url": "https://github.com/ossf/scorecard/blob/main/docs/checks.md#binary-artifacts",
        "short": "Determines if the project has generated executable (binary) artifacts in the source repository."
    }
},

Which issue(s) this PR fixes
Fixes #2577
Special notes for your reviewer
Does this PR introduce a user-facing change?
Add Check ID

I think this change represents an interesting challenge for the cron, as it's something we could technically go and backfill data for. Can we wait on this until after OSS NA?

No rush from me, will do a bit more cleanup and we can look at it after next week

Note the linter we use currently is fieldalignment

Went back and reset the structs and ran fieldalignment on them.

@ashearin we are planning to merge this at the same time that we flip the switch on maintainer annotations, since both require a schema change to the BigQuery data. So going to do both at the same time.

/scdiff generate License,Vulnerabilities,Code-Review,Dangerous-Workflow,SAST,Pinned-Dependencies,Branch-Protection,Signed-Releases,Maintained,Token-Permissions,CII-Best-Practices,Packaging,Binary-Artifacts,Dependency-Update-Tool,Security-Policy,Fuzzing


As a customer I want to export my consumption and production data so that I can create custom visualizations in Excel and/or drill into details

Lukket grundet forældelse


Question: Multiple instance resource

@dbaba san,
According to OMA spec, there are multiple instance resources.
For example, in SmartObject "Connectivity Monitoring", resource "Ip Address" is Multiple Instance.
It means, I need to send values as /4/0/4**/0** =
How can I do this using node-red-contrib-lwm2m ?
1. Define Object
I need to define this object in Objects of Client Out node. How?
i didn't find example in https://github.com/CANDY-LINE/node-red-contrib-lwm2m#management-object-json-format
But there is

MULTIPLE_RESOURCE ... Resource Array
Is this multiple resource instance?

Well, I was thinking about this format -> but this doesn't work
{
    "4": {
        "0": {
            "4": {
                "0": {
                    "type": "STRING",
                    "acl": "R",
                    "value": ""
                }
            }
        }
    },

1. Send data using Inject node
I was thinking about using this format - is it correct way to send measurements for resource instance?

Regards,
Andrey

Thank you for spotting the missing description regarding MULTIPLE_RESOURCE.
For the first question, here is how to define MULTIPLE_RESOURCE type value in JSON format:
(will update README.md)

MULTIPLE_RESOURCE
The type is a collection having Resource Instance ID and Resource value pairs.
{
    "type": "MULTIPLE_RESOURCE",
    "value": {
        "100": 999,
        "101": true,
        "999": {
            "type": "FLOAT",
            "value": 987654.321
        }
    }
}

If the Resource Instance ID starts with "0" and its following IDs are 1,2,3... (increases by 1), you can provide a JSON Array like this.
{
    "type": "MULTIPLE_RESOURCE",
    "value": [
        123,
        false,
        {
            "type": "FLOAT",
            "value": 1234.567
        }
    ]
}

This is equivalent to:
{
    "type": "MULTIPLE_RESOURCE",
    "value": {
        "0": 123,
        "1": false,
        "2": {
            "type": "FLOAT",
            "value": 1234.567
        }
    }
}

And in terms of the second one, you cannot provide the string value in Payload as you showed.
Instead, you need to use JSON format in Payload.

Payload (choose JSON rather than az(string) in the typed input area) could be like this:

{
  "0": "<IP_ADDRESS>"
}

or
["<IP_ADDRESS>"]

Topic should be always:

/4/0/4

The Resource Instance ID (0) cannot be included in URI at all.

@dbaba san, thank you!
I tested:
Part 1  - it is correct,
Part 2 - only "array"format works correctly:
["<IP_ADDRESS>"]
This format returns "lwm2m error" in debug window
{   "0": "<IP_ADDRESS>" }

@djDuff My fault! Found the issue and will fix it soon. Thanks!

How do I send measurements for a multiple ressource definition?
Lets say I have /6/0 (location object) with ressource /0 (latitude) and /1 (longitude).
msg.topic /6/0 and
payload { "0" : 46.123 , "1": 9.345} dos not work.


User permission data not loading

Description
I recently set up LuckPerms bungee, now when players log-in they receive this error message in chat. I haven't noticed anything breaking at all, it seems like everything is working 100% which is frustrating me as I can't locate the issue.
I've tried removing Geyser/Floodgate & my Bungeeguard/AntiBot on my proxy without any change, the issue still persists.
error message on login:
https://imgur.com/a/9P5saHu
Console error on the proxy:
https://www.toptal.com/developers/hastebin/zuzixacepo.sql
Reproduction Steps
Setup LuckPerms on my Bungee network correctly, I have no issues anywhere apart from this annoying message. Everyone, including lp staff, in the Discord support chat are clueless.
Expected Behaviour
I didn't expect to get this error message
Server Details
Purpur 1.19 #1679
LuckPerms Version
v.5.4.30
Logs and Configs
https://www.toptal.com/developers/hastebin/zuzixacepo.sql
Extra Details
No response

have you installed a plugin on proxy or waterfall

have you installed a plugin on proxy or waterfall

I've got The bungee LP on my proxy and the standalone LP on my seperate servers

have you installed a plugin on proxy or waterfall

here are the plugins installed on my bungee server: https://imgur.com/a/YuZEINr


Add support for spaces (and other specials) in keys

Currently, page url generation (slugification) is just toLowerCase. In https://github.com/yannbertrand/macos-defaults/pull/146 I add some defaults that contain keys with spaces, which currently breaks.
This pulls in slugify to add support, and shell escapes keys in examples.

I'm not sure what happened to the schema test - I haven't changed either the schema file or the defaults yaml files here.

LGTM

Thanks!


Update Wrist-Mk2 model – Physical components

We're required to update the Simscape model of wrist-mk2 by exporting the latest mechanics from CREO.
cc @ale-git @salvi-mattia @valegagge @fiorisi @mfussi66 @Nicogene

Ok, I think that there is no real need to link the private repo - a picture from there will do the job.  Since I'm documenting here the model updating task I've to put here a note about the RoM that hasn't been yet analyzed since the analysis was made for 90 deg angle, and it has to be taken into account in the control logic.

Remark: now the motor enumeration is as follows. Anyway, since the mechanism can be mounted in different ways, we must remember to check the real order.

Hi @ale-git
Does this mean that the order is different from the current one identifying M0, M1, and M2?
(I don't seem to find the relative picture – maybe @mfussi66 can remember where it is)

@pattacini I checked with the mechanical assembly. For Mk2.0 it was like this:

To, me it would seem natural to do the same for Mk2.1.

But it is just my two cents 🪙 🪙 .

Thanks @Lawproto 👍🏻

To me, it would seem natural to do the same for Mk2.1.

Yep, right, unless @ale-git has some constraints to deal with.
Just let's bear in mind that even a small think like changing the name convention may have impacts in many places.

@pattacini don't worry :) I assumed this order from the rest positions 0-120-240, but we can set any order we want by adding an offset. This reminds me that, since we'll have different versions of the wrist, the arm offsets mus be made configurable.

Hi @Lawproto , the CAD exported the vertical axis of rotation of the three pulleys pointing down as in the figure, so that the positive rotation is clockwise when looking from above. I reverted them in the simscape model in order to have CCW positive rotation as in the real joint but, if the CAD allows it, it would be better to have the three axis pointing up in order to be aligned to the robot control logic. I don't know if it is possible to impose a direction btw, since I remember that when we export urdf models the direction is random.

I don't know if it is possible to impose a direction btw, since I remember that when we export urdf models the direction is random.

cc @mfussi66 @Nicogene

I don't know if it is possible to impose a direction btw, since I remember that when we export urdf models the direction is random.

It is kinda random (Creo has its own internal logic), but for generating the URDF it can be reversed by setting the csys in the reverseRotationAxis tag. So it's just a matter of exporting the first time, and checking if it's the desired direction. Otherwise, reverse it and export again.

The Creo CAD model used to generate the SimScape model is ic_021_g_134_mech.asm.

I don't know if it is possible to impose a direction btw, since I remember that when we export urdf models the direction is random.

It is kinda random (Creo has its own internal logic), but for generating the URDF it can be reversed by setting the csys in the reverseRotationAxis tag. So it's just a matter of exporting the first time, and checking if it's the desired direction. Otherwise, reverse it and export again.

Yes, there is a further step in generating URDFs from the SimScape model where we can configure the script to invert joint directions when required, but we stop at the previous step when importing the model in Simulink.

I've updated the model with the new wrist Mk 2.1, and made the wrist_decoupler configurable at runtime. Now all the geometric parameters are accepted as input by the 'wrist_decoupler' subsystem.
They are:

arm angle offsets
platform angle offsets
arm bending
right/left wrist

This is the schema of the Simulink controller that makes use of the wrist_decoupler in the Simscape digital twin of the wrist.

Here the PR
https://github.com/robotology/icub-firmware-models/pull/56

I've updated the motion control library in icub-firmware, then I realized that this task wasn't scheduled yet.
https://github.com/ale-git/icub-firmware/commit/0847b2ab36cd3a4d5cab6f634c1952bbac672ab7


goToDefinition broken for functions returned from expressions

The following example from @kasperpaulen loses the definition of fn:
/** @tsplus type Foo */
export interface Foo {}

export function identity<S, P extends [...unknown[]], A>(fn: (self: S, ...rest: P) => A): (self: S, ...rest: P) => A {
  return fn;
}

/**
 * Docs
 *
 * @tsplus fluent Foo fn
 */
export const fn = identity((self: Foo) => self);

function bar(foo: Foo) {
  foo.fn(); // go to declaration and docs lookup don't work
}

I think I found another example that doesn't work yet with the latest tsplus, when I make Foo generic in T:
/** @tsplus type Foo */
export interface Foo<T> {}

export function identity<S, P extends [...unknown[]], A>(fn: (self: S, ...rest: P) => A): (self: S, ...rest: P) => A {
  return fn;
}

/**
 * Docs
 *
 * @tsplus fluent Foo fn
 */
export const fn = identity(function <T>(self: Foo<T>) {});

function bar(foo: Foo<number>) {
  foo.fn(); // go to declaration and docs lookup don't work
}


This may not be a bug, or if is, may not be directly attributable to powertoys

Microsoft PowerToys version
0.53.3
Running as admin

[X] Yes

Area(s) with issue?
Settings
Steps to reproduce
N.A.
✔ Expected Behavior
Not have this report appearing on my desktop!
Thank-you.
❌ Actual Behavior
The report keeps appearing after being deleted!
Other Software
No response

whoops, forgot to attach my desktop screenshot...

This is a result from "report a bug" in the sys-tray menu. Did you click that?

Go to %ProgramFiles%\PowerToys\Tools
Run BugReportTool.exe {a path where bug report should be generated}. Make sure the passed path contains only ASCII characters(try Latin letters)
Check if a bug report is generated in the passed folder

Please do these steps in the terminal and see if you can get a report.
And what is your desktop path?
/needinfo

PS C:\Program Files\PowerToys\Tools> ./PowerToys.BugReportTool.exe C:\Users\jedla\OneDrive\Desktop
PS C:\Program Files\PowerToys\Tools>

eventually corrected itself a few days back, not sure what exactly I did or what happened prior to that (didn't notice till sometime later), it just stopped constantly reappearing on the desktop.


RuntimeError: expected scalar type Half but found Float

Traceback (most recent call last):
File "main/train.py", line 226, in
train(dataset, parser)
File "main/train.py", line 132, in train
out2, out3, out4, out5, pose = net(image)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/home/senlinren/LR/ICON-main/main/model/icon/icon.py", line 221, in forward
x1 = self.dfa1(x1)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/home/senlinren/LR/ICON-main/main/model/icon/modules.py", line 134, in forward
p3 = self.atrConv(f)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/container.py", line 204, in forward
input = module(input)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/anaconda3/envs/u2/lib/python3.7/site-packages/torch/nn/modules/activation.py", line 1240, in forward
return F.prelu(input, self.weight)
RuntimeError: expected scalar type Half but found Float

Check your apex version and https://github.com/mczhuge/ICON/blob/main/main/train.py#121.
But please notice, it may influence the performance.

Hi, @Lrr57 . Have you solved this issue?

@Ayews Actually, I often met this problem in "Pytorch+Apex" based project. Yes, you can double check the environment:
[Python 3.5](https://www.python.org/)
[Pytorch 1.3](http://pytorch.org/)
[OpenCV 4.0](https://opencv.org/)
[Numpy 1.15](https://numpy.org/)
[TensorboardX](https://github.com/lanpa/tensorboardX)
[Apex](https://github.com/NVIDIA/apex)

@mczhuge Oops... I can't find pytorch1.3 on its website, and deploying a related CUDA environment is also a problem, I guess pytorch1.3 cant support CUDA 11.3? I also wonder if you install the apex with cuda/cpp extensions or not? Thanks for your help in providing this information.
I think it is normal for pytorch+apex to have problems because apex installation does not depend on a strict environment, any python version, pytorch vision, CUDA vision can install it, so whether it works or not is unknown to some extent.
but I succeeded in running ICON with several changes:

The error above seemed to be caused by the incompatibility between the current apex and prelu, I replaced prelu with relu;

When I fixed pre error, I met this new error:
Traceback (most recent call last): File "main.py", line 68, in <module>  fit([60],model,lr,train_dl,method) File "/root/workspace/train.py", line 142, in fit  loss = train_one_epoch(epoch,epochs[st],model,train_dl) File "/root/workspace/train.py", line 96, in train_one_epoch  out2, out3, out4, out5, pose = model(images)             File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl  return forward_call(*input, **kwargs) File "/root/workspace/icon.py", line 215, in forward  x2  = self.ice1(in1=x2, in2=x1, in3=x3) File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl  return forward_call(*input, **kwargs) File "/root/workspace/Models/icon/modules.py", line 173, in forward  x = F.relu(self.bn_cross(self.conv_cross(x))) #[B, C, H, W] File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl  return forward_call(*input, **kwargs) File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 457, in forward  return self._conv_forward(input, self.weight, self.bias) File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 453, in _conv_forward  return F.conv2d(input, weight, bias, self.stride, File "/root/miniconda3/lib/python3.8/site-packages/apex-0.1-py3.8-linux-x86_64.egg/apex/amp/wrap.py", line 21, in wrapper  args[i] = utils.cached_cast(cast_fn, args[i], handle.cache) File "/root/miniconda3/lib/python3.8/site-packages/apex-0.1-py3.8-linux-x86_64.egg/apex/amp/utils.py", line 97, in cached_cast  if cached_x.grad_fn.next_functions[1][0].variable is not x: IndexError: tuple index out of range
I read this source code from utils and found this is an inspection measure, I just remark it with '''.
`def cached_cast(cast_fn, x, cache):
if is_nested(x):
return type(x)([cached_cast(y) for y in x])
if x in cache:
cached_x = cache[x]
'''
if x.requires_grad and cached_x.requires_grad:
# Make sure x is actually cached_x's autograd parent.
if cached_x.grad_fn.next_functions[1][0].variable is not x:
raise RuntimeError("x and cache[x] both require grad, but x is not "
"cache[x]'s parent.  This is likely an error.")
'''
# During eval, it's possible to end up caching casted weights with
# requires_grad=False.  On the next training iter, if cached_x is found
# and reused from the cache, it will not actually have x as its parent.
# Therefore, we choose to invalidate the cache (and force refreshing the cast)
# if x.requires_grad and cached_x.requires_grad do not match.
#
# During eval (i.e. running under with torch.no_grad()) the invalidation
# check would cause the cached value to be dropped every time, because
# cached_x would always be created with requires_grad=False, while x would
# still have requires_grad=True.  This would render the cache effectively
# useless during eval.  Therefore, if we are running under the no_grad()
# context manager (torch.is_grad_enabled=False) we elide the invalidation
# check, and use the cached value even though its requires_grad flag doesn't
# match.  During eval, we don't care that there's no autograd-graph
# connection between x and cached_x.
if torch.is_grad_enabled() and x.requires_grad != cached_x.requires_grad:
del cache[x]
else:
return cached_x
casted_x = cast_fn(x)
cache[x] = casted_x
return casted_x
`
Anyway, the training code started running. I'm looking forward to its results

@Ayews I think the most important thing is to check your CUDA, CUDNN, torch, Apex version. If they match, I think there is no problem. You could try SWIN/PVT encoder first.

ched_cast(cast_fn, x, cache):
if is_nested(x):
return type(x)([cached_cast(y) for y in x])
if x in cache:
cached_x = cache[x]
'''
if x.requires_grad and cached_x.requires_grad: # Make sure x is actually cached_x's autograd parent. if cached_x.grad_fn.next_functions[1][0].variable is not x: raise RuntimeError("x and cache[x] both require grad, but x is not " "cache[x]'s parent. This is likely an error.")
'''
During eval, it's possible to end up caching casted weights with
requires_grad=False. On the next training iter, if cached_x is found
and reused from the cache, it will not actually have x as its parent.
Therefore, we choose to invalidate the cache (and force refreshing the cast)
if x.requires_grad and cached_x.requires_grad do not match.

During eval (i.e. running under with torch.no_grad()) the invalidation
check would cause the cached value to be dropped every time, because
cached_x would always be created with requires_grad=False, while x would
still have requires_grad=True. This would render the cache effectively
useless during eval. Therefore, if we are running under the no_grad()
context manager (torch.is_grad_enabled=False) we elide the invalidation
check, and use the cached value even though its requires_grad flag doesn't
match. During eval, we don't care that there's no autograd-graph
connection between x and cached_x.
if torch.is_grad_enabled() and x.requires_grad != cached_x.requires_grad:
del cache[x]
else:
return cached_x
casted_x = cast_fn(x)
cache[x] = casted_x

There is a quick method to solve the first problem, that change the 'O1' to 'O2' in https://github.com/mczhuge/ICON/blob/main/main/train.py#121.
But as I mentioned, it would inflect the performance. So I am now trying to solve this issue.

@Ayews  There is a quick method to solve the first problem, that change the 'O1' to 'O2' in https://github.com/mczhuge/ICON/blob/main/main/train.py#121.
But as I mentioned, it would inflect the performance. So I am now trying to solve this issue.

@mczhuge I also met this problem.Is it repaired now? Thanks.

@zqy1
Hi, could you re-build your environment following:   https://github.com/mczhuge/ICON/tree/main/util
And if there is still a problem, please let me know.
My wechat: tjpxiaoming if you need more help

As suggested by yuqiuyuqiu.
Use the PyTorch version <= 1.10.1


The redirect_uri parameter is not valid

Receiving this error in Auth0 log after following your guide. Any suggestions?
The redirect_uri parameter is not valid: "zendoks.app.mobile%3A%2F%2Fzendoks.auth0.com%2Fcordova%2Fzendoks.app.mobile%2Fcallback" If url looks fine, check that you are not including non printable chars

Do we have a timeline for when the updated quick start will be published for Ionic 3?

@ankit-ilogix @gabedeko I don't have a confirmed publish date yet, only that it should be ready in the next few weeks. I can, however, point you to the sample repo that implements Ionic 3 with auth0-cordova--but with the caveat that it's not finalized. It does work as-is, but the sample may change again before the QS is published, so use it at your own risk! https://github.com/kmaida/auth0-ionic3-samples

Thanks! I'll be anticipating it being published.

Thank you so much @kmaida


Won't start

Trying to start it from TTY results in the error below.
Minimum issue requirements
Search the issue tracker first, as it's very possible your question has been asked and answered
Please provide, at minimum:

Way Cooler version (obtained via way-cooler --version

Way Cooler 0.8.0
Way Cooler IPC version 1

rc file

alias reboot = 'sudo reboot'
alias poweroff = 'sudo poweroff'
alias brightness = 'ion /home/a/scripts/brightness.ion '

alias ls = 'exa -lm --color=auto '
alias l = 'exa -alm --color=auto '
alias la = 'exa -alm --color=auto '
alias lc = 'exa -al --color=always '
alias lac = 'exa -alm --color=always '
alias ld = 'exa -d .* -m --color=auto '
alias ldc = 'exa -d .* -m --color=always '

alias grep = 'rg '
alias find = 'fd '
alias cat = 'bat '
alias c = 'bat '
alias sysupdate = 'ion ~/scripts/update.ion'
alias sysinstall = 'sudo xbps-install -Sv'
alias sysuninstall = 'sudo xbps-remove -Rv'
alias profile = 'micro ~/.profile'
alias notes = 'micro /data/documents/void.txt'
alias hist_dedupe = 'awk '!x[$0]++' ~/.local/share/ion/history > ~/.local/share/ion/history.tmp && mv ~/.local/share/ion/history.tmp ~/.local/share/ion/history'
alias gclone = 'git clone'
alias gpull = 'git pull'
alias gpush = 'git push'
cd ~/

export XKB_DEFAULT_LAYOUT = "gb" # used by way-cooler/wayland
export XDG_RUNTIME_DIR = "/tmp/${UID}-runtime-dir" # used by way-cooler/wayland
if not test -d "${XDG_RUNTIME_DIR}"
	mkdir "${XDG_RUNTIME_DIR}"
	chmod 0700 "${XDG_RUNTIME_DIR}"
end
#export XDG_VTNR = 2 # tty used by way-cooler/wayland
export PATH = "$HOME/bin:$PATH"
export EDITOR = "/usr/bin/micro"
export PAGER = "/usr/bin/less"
export CC = "/usr/bin/clang" # used by cargo
export CXX = "/usr/bin/clang++" # used by cargo

### from rustup, delete this and the following line after uninstall
export PATH = "$HOME/.cargo/bin:$PATH"

Debug log

You can obtain a debug log like so: way-cooler 2> log.txt
If the error is a result of a segfault, please also include a backtrace or a coredump.
Launching way-cooler...
 INFO [way_cooler] src/main.rs:215 Logger initialized, setting wlc handlers.
 INFO [way_cooler] src/main.rs:220 HOME: /home/a
 INFO [way_cooler] src/main.rs:220 USER: a
 INFO [way_cooler] src/main.rs:220 SHELL: /home/a/.cargo/bin/ion
 INFO [way_cooler] src/main.rs:220 TERM: linux
 INFO [way_cooler] src/main.rs:220 PATH: /home/a/.cargo/bin:/home/a/bin:/usr/local/bin:/bin:/usr/bin
 INFO [way_cooler] src/main.rs:220 MAIL: /var/spool/mail/a
 INFO [way_cooler] src/main.rs:220 LOGNAME: a
 INFO [way_cooler] src/main.rs:220 HOST: a
 INFO [way_cooler] src/main.rs:220 PWD: /home/a
 INFO [way_cooler] src/main.rs:220 OLDPWD: /home/a
 INFO [way_cooler] src/main.rs:220 XKB_DEFAULT_LAYOUT: gb
 INFO [way_cooler] src/main.rs:220 XDG_RUNTIME_DIR: /tmp/1000-runtime-dir
 INFO [way_cooler] src/main.rs:220 EDITOR: /usr/bin/micro
 INFO [way_cooler] src/main.rs:220 PAGER: /usr/bin/less
 INFO [way_cooler] src/main.rs:220 CC: /usr/bin/clang
 INFO [way_cooler] src/main.rs:220 CXX: /usr/bin/clang++
 INFO [way_cooler] src/main.rs:220 RUST_BACKTRACE: 1
gbm: failed to open any driver (search paths /usr/lib/xorg/modules/drivers)
gbm: Last dlopen error: /usr/lib/xorg/modules/drivers/radeonsi_dri.so: cannot open shared object file: No such file or directory
failed to load driver: radeonsi
 INFO [wayland] src/wayland/mod.rs:7 Initializing wayland protocols
 INFO [wayland::gamma_control] src/wayland/gamma_control.rs:233 Initializing gamma control manager
 INFO [wayland::desktop_shell] src/wayland/desktop_shell.rs:170 Initializing desktop shell
 TRACE [callbacks] src/callbacks.rs:193 Registered wlc callbacks
 INFO [way_cooler] src/main.rs:271 Running wlc...
 INFO [way_cooler] src/main.rs:65 wlc: libinput: resume
thread '<unnamed>' panicked at 'Unable to create dbus session: D-Bus error: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (org.freedesktop.DBus.Error.NotSupported)', src/libcore/result.rs:906:4
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 1366x768@60000 *
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 1366x768@40000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 1280x720@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 1152x768@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 1024x768@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 800x600@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 848x480@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 720x480@60000
 INFO [way_cooler] src/main.rs:65 wlc: MODE: (0) 640x480@60000
 WARN [way_cooler] src/main.rs:66 wlc: Connector 1 is not connected or has no modes
 INFO [way_cooler] src/main.rs:65 wlc: eDP-1 Chose mode (0) 1366x768
 TRACE [callbacks] src/callbacks.rs:37 output_resolution: WlcOutput { handle: 1, name: "eDP-1", views: [] } from  Size { w: 0, h: 0 } to Size { w: 1366, h: 768 }
 WARN [layout::actions::layout] src/layout/actions/layout.rs:521 LayoutTree {
    tree: InnerTree {
        graph: StableGraph {
            Ty: "Directed",
            node_count: 1,
            edge_count: 0,
            node weights: {
                0: Root(
                    Uuid("003bba02-99f0-42b8-8bff-62fd020f9e86")
                )
            },
            edge weights: {},
            free_node: NodeIndex(4294967295),
            free_edge: EdgeIndex(4294967295)
        },
        id_map: {},
        view_map: {},
        root: NodeIndex(0),
        active_path: "0"
    },
    active_container: None
} did not have a parent of type Output, doing nothing!
 TRACE [callbacks] src/callbacks.rs:18 output_created: WlcOutput { handle: 1, name: "eDP-1", views: [] }: eDP-1
 TRACE [layout::core::tree] src/layout/core/tree.rs:453 Adding new output with WlcOutput { handle: 1, name: "eDP-1", views: [] }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(0)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(1) for Output { handle: WlcOutput { handle: 1, name: "eDP-1", views: [] }, background: None, bar: None, id: Uuid("705b27e2-b671-45d7-9d08-863966bd0ed3") }
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:43 Adding workspace Workspace { name: "1", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1366, h: 768 } }, fullscreen_c: [], id: Uuid("e6b0ae89-3275-4a4d-bfa2-34c09e4793f0") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(1)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(2) for Workspace { name: "1", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1366, h: 768 } }, fullscreen_c: [], id: Uuid("e6b0ae89-3275-4a4d-bfa2-34c09e4793f0") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(2)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(3) for Container { layout: Horizontal, floating: false, fullscreen: false, output_handle: WlcOutput { handle: 1, name: "eDP-1", views: [] }, apparent_geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1366, h: 768 } }, geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1366, h: 768 } }, id: Uuid("ef01e75d-656f-43f7-a54d-4df457ca1c76"), borders: None }
 DEBUG [layout::commands] src/layout/commands.rs:416 Layout.SwitchWorkspace("1")
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:78 Switching to workspace 1
 WARN [way_cooler] src/main.rs:66 wlc: Arguments are inconsistent
 WARN [way_cooler] src/main.rs:66 wlc: Could not initialize any context
 INFO [way_cooler] src/main.rs:65 wlc: Released drm surface (0x7f6aba473160)
 INFO [way_cooler] src/main.rs:65 wlc: Removed bsurface from output (1)
 TRACE [callbacks] src/callbacks.rs:30 output_focus: WlcOutput { handle: 1, name: "eDP-1", views: [] } focus=true
 INFO [way_cooler] src/main.rs:65 wlc: Added output (1)
 INFO [way_cooler] src/main.rs:65 wlc: become active
 INFO [way_cooler] src/main.rs:65 wlc: Cleanup wlc
 INFO [callbacks] src/callbacks.rs:140 Preparing compositor!
 INFO [lua::thread] src/lua/thread.rs:210 Running lua on_init()
 INFO [lua::thread] src/lua/thread.rs:122 Initializing lua...
 INFO [lua::thread] src/lua/thread.rs:127 Loading way-cooler libraries...
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:22 Registering Rust libraries...
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:46 Executing Lua init...
 ERROR [awesome] src/awesome/mod.rs:94 xcb: Could not connect to xwayland instance. Is it running?
 ERROR [awesome] src/awesome/mod.rs:95 ClosedParseErr
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:55 Lua register_libraries complete
 TRACE [lua::init_path] src/lua/init_path.rs:65 Looking for init file at ~/.config/way-cooler/init.lua
 WARN [lua::init_path] src/lua/init_path.rs:70 No init file found in ~/.config, will default to /etc as a last resort.
 WARN [lua::init_path] src/lua/init_path.rs:81 way-cooler was unable to find an init file. Using our default, pre-compiled init.lua.
 WARN [lua::init_path] src/lua/init_path.rs:83 Our default init.lua is available on GitHub, it is included with the source.
 WARN [lua::init_path] src/lua/init_path.rs:85 You may place it in ~/.config/way-cooler/init.lua, or a similar folder if you use $XDG_CONFIG_HOME, or /etc/way-cooler.
 WARN [lua::init_path] src/lua/init_path.rs:87 You may also use the environment variable $WAY_COOLER_INIT_FILE to point directly to the file of your choice.
 WARN [lua::thread] src/lua/thread.rs:173 Defaulting to pre-compiled init.lua
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("d")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("Return")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("l")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("h")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("l")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("Left")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("Right")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("Up")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("Down")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("Left")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("Right")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("Up")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("Down")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("h")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("v")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("e")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("s")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("w")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("f")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("q")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("space")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("space")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("r")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("1")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("1")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("2")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("2")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("3")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("3")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("4")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("4")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("5")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("5")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("6")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("6")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("7")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("7")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("8")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("8")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_ALT, Some("9")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("9")) for Event: KeyEvent::Command, passthrough: false
 INFO [lua::thread] src/lua/thread.rs:186 Entering main loop...
 DEBUG [layout::commands] src/layout/commands.rs:640 Layout.focus("ef01e75d-656f-43f7-a54d-4df457ca1c76")
 DEBUG [layout::commands] src/layout/commands.rs:590 Layout.Focus("ef01e75d-656f-43f7-a54d-4df457ca1c76")
 INFO [layout::core::tree] src/layout/core/tree.rs:231 Active container was 3, is now 3
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_ALT, Some("Escape")) for Event: KeyEvent::Command, passthrough: false
 INFO [way_cooler] src/main.rs:65 wlc: Closing Xwayland
 INFO [way_cooler] src/main.rs:65 wlc: Closed drm
 TRACE [lua::thread] src/lua/thread.rs:226 Lua: awaiting request
 TRACE [lua::thread] src/lua/thread.rs:238 Handling a request
 TRACE [lua::thread] src/lua/thread.rs:399 Updating programs:String(LuaRef(12)) = String(
    "lemonbar"
)
 TRACE [lua::thread] src/lua/thread.rs:399 Updating mouse:String(LuaRef(8)) = Boolean(
    false
)
stack backtrace:
 TRACE [lua::thread] src/lua/thread.rs:226 Lua: awaiting request
 TRACE [lua::thread] src/lua/thread.rs:238 Handling a request
 TRACE [lua::thread] src/lua/thread.rs:285 Received request to execute way_cooler.on_init()
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: start_thread
 ERROR [way_cooler] src/main.rs:67 wlc: Failed to activate vt7 for restoration
 ERROR [way_cooler] src/main.rs:67 wlc: Failed to switch back to vt1
sh: 1: wc-bg: not found

Bonus information
If you provide this information as well, I can respond to your request much faster:

Is the issue reproducible on Sway?

We share the same backend, so if it's not a Way Cooler specific issue it might affect them too
I haven't installed Sway.

Is the issue reproducible on Awesome?

It may not be a bug, it could be a feature.
I haven't installed Awesome.

What distro do you run?
Void Linux
How did you install Way Cooler?

E.g: build from source? Package manager? Found on a disk by the side of the road?
Basically with xbps-install -S way-cooler.

Awesome specific questions
If the bug report is an issue with the Awesome API, please mention the appropriate method/object from the Awesome Lua API and describe how it is not working as intended.

Ah no worries.
I don't actually think I have a Way Cooler Rc file (which one is it supposed to be again? I couldn't find any documentation or man pages about it unfortunately). But yeah, I think it's definitely a good idea to clarify which file is required in the issue template.
I've since installed the X11 window manager bspwm and sway (not sure if it uses wlc, but sway --version indicates that it's sway version  (2018-04-18, branch "")). I've found out that both way-cooler and sway are unable to be launched from the TTY (way-cooler crashes with the message above, and sway freezes the screen), but both can be launched from bspwm. Maybe this is related/the same issue as #351?


Consistent Gray Color Families for Template Metadata

Bug Description
There's one usage of "grey" in the template metadata. We should name this "gray" for consistency.
(to follow, an array so that both spellings get search results)
Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

So actually "grey" showed up for search results for morten in bug bash because the tags for the tech template include "grey".

Closing in favor of converting to an array for both grey and gray as color families.

Pascal thinks this is a p0 so reopening and updating the tag 🤝


Beginner tutorials: Machine learning Interfaces with PL

Title:
Machine learning Interfaces with PL. ADR in review. This is under progress.

@AroosaIjaz Please wait until ADR is finalized before making a PR here


Expand the Tasks whenever it is hover over on the Holiday

Can we expand the  Tasks whenever it is hover over on the Holiday Periods?

What do you mean by expand tasks?

please follow the contribution guidelines, be more descriptive and also add screenshot (if any)


save pods in olm namespace

Type of change

Enhancement

Description

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[x] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=olm ocp4

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:


[BUG] Couple of cases of infinite recursion

Describe the bug
Methods getFloatVectorValues(String field) and getByteVectorValues(String field) in TranslogLeafReader class
Related component
Indexing
To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

https://github.com/opensearch-project/OpenSearch/blob/6152afeef3ceb3fe4f18f6be2d55ac60256bc2db/server/src/main/java/org/opensearch/index/engine/TranslogLeafReader.java#L266-L274
Introduced in https://github.com/opensearch-project/OpenSearch/pull/6078 but the diff shows something similar prior to that:
https://github.com/opensearch-project/OpenSearch/blob/c557f2717ad45627cacd88e8243893dd84a56623/server/src/main/java/org/opensearch/index/engine/TranslogLeafReader.java#L257-L260
That was introduced in https://github.com/opensearch-project/OpenSearch/pull/1109
It's not clear what it should be.  @nknize any idea?

I would at least raise a not implemented exception here to begin with, I imagine all tests will pass, this code is obviously not executed.


Environment variables for UID/GID no longer valid in Documentation

Hi,
I just noticed during my latest pull that the environment variables for running the Emby server under a specific UID/GID are no longer APP_UID/APP_GID, but seem to be UID/GID now (which works as designed as s6-applyuidgid is being called with the -U parameter). Documentation seems to be wrong on this or the change to /etc/services.d/emby-server/run was not intentional.
Interestingly enough my /etc/services.d/emby-server/run is completely different from what I can see in this repo - is this actually the place for the official Emby docker image or am I too dumb/blind to find the relevant run file?
Thanks!

This repo has nothing to do with the deployment or development of the Emby
container. The container is now using the .netcore binaries. If you have
questions regarding the development of the container it is best to post
your questions or issues on the Emby forums. I no longer donate any
considerable amount of time to this project. My apologies for not being
clear enough with my previous response. Best of luck.
On Jan 31, 2018 4:17 PM, "Gordon Schulz"<EMAIL_ADDRESS>wrote:

It is not ... in regards to what point?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MediaBrowser/Emby.Build/issues/69#issuecomment-362103689,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiQzXcAGO9cxJIvLDsi470KyzotXL-Xks5tQPSRgaJpZM4R0sXJ
.

Ah, I see, thanks for clarification. Since the official image (I suppose emby/emby-server is still the official one?) on Docker Hub still links to this repository it is kind of misleading. Do you have any pointers on where the official image is being built/supported nowadays?

Emby forums is the best source for all and any relevant info.
On Feb 1, 2018 7:08 AM, "Gordon Schulz"<EMAIL_ADDRESS>wrote:

Ah, I see, thanks for clarification. Since the official image (I suppose
emby/emby-server is still the official one?) on Docker Hub still links to
this repository it is kind of misleading. Do you have any pointers on where
the official image is being built/supported nowadays?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MediaBrowser/Emby.Build/issues/69#issuecomment-362276116,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiQzdVf5hL1H8e4nWRIdoTGjZTRclncks5tQcVjgaJpZM4R0sXJ
.

Our docker setup guide also lists everything that is supported:
https://docs.docker.com/installation/#installation


chore: fixed cypress tests execution

SUMMARY

I found that someone has changed password for cypress -> instead "admin" it should be "general". Fixed.
In native filters test file it was one additional step which was not needed.
for cypress run it should be feature flag enabled - > I modified config file for cypress tests

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #61 (a516936) into dashboard-native-filters (1b9eb9b) will decrease coverage by 0.38%.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##           dashboard-native-filters      #61      +/-   ##
============================================================
- Coverage                     63.63%   63.24%   -0.39%
============================================================
  Files                           958      466     -492
  Lines                         46331    28688   -17643
  Branches                       4503        0    -4503
============================================================
- Hits                          29483    18145   -11338
+ Misses                        16664    10543    -6121
+ Partials                        184        0     -184

Flag
Coverage Δ

javascript
?

python
63.24% <ø> (-0.96%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.62%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/presto.py
69.95% <0.00%> (-12.45%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
83.80% <0.00%> (-5.27%)
:arrow_down:

... and 513 more

Continue to review full report at Codecov.

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

This test 'should update the title' seems to fail because of application error (does not come with cypress tests.
@rusackas
Cannot read property 'filter_configuration' of null The error may be correlated with this previous error: TypeError: Cannot read property 'filter_configuration' of null     at Object.eval [as current] (webpack-internal:///./src/dashboard/components/nativeFilters/state.ts:49:112)     at Subscription.checkForUpdates [as onStateChange] (webpack-internal:///./node_modules/react-redux/es/hooks/useSelector.js:56:47)     at Subscription.handleChangeWrapper (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:100:12)     at eval (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:26:20)     at batchedUpdates$1 (webpack-internal:///./node_modules/@hot-loader/react-dom/cjs/react-dom.development.js:21888:12)     at Object.notify (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:22:7)     at Subscription.notifyNestedSubs (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:95:20)     at Subscription.checkForUpdates [as onStateChange] (webpack-internal:///./node_modules/react-redux/es/components/connectAdvanced.js:90:9)     at Subscription.handleChangeWrapper (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:100:12)     at eval (webpack-internal:///./node_modules/react-redux/es/utils/Subscription.js:26:20)


[util] Add new "Zusi 3" exe filename

Hopefully the regex is correct. It works for ZusiSim.64.exe (which is the executable launched by steam), but I'm not sure how to launch the legacy 32 bit "ZusiSim.exe" in steam, so I have not tested if that still works correctly.
Commit message:
In addition to the legacy "ZusiSim.exe" executable, the recent 3.5 release added a 64-bit "ZusiSim.64.exe" executable. This is now the default executable when launching the game in Steam. The game is unplayable without this option, so update the regex for Zusi 3.
Fixes #3250.

Updated commit message to add "Fixes #3250.".
Also, I have now verified that the regex still works for the 32-bit exe filename "ZusiSim.exe" after updating 32 bit dxvk dlls in the compatdata wine prefix (launching it from the command line using Proton's wine executable and the compatdata wine prefix simply works as expected, I thought there would be some DRM/Steam issues).

That's a great question!
I've never used these editors and don't really know how to use them (they seem complicated), but giving them a very superficial test:

ZusiFtdEditor.64.exe: This one appears broken with dxvk, with and without "noExplicitFrontBuffer". Instead of the cab view image, there is just a gray area with the cab view flickering for ~1 frame when clicking the gray area. This is not an issue when using wine d3d9 apparently.
Zusi3DEditor.64.exe: I haven't noticed any obvious issues when not using the config.
ZusiFzgEditor.64.exe, ZusiDateiverwaltung.exe: It seems like these don't use D3D
ZusiGleisplanEditor.exe: Not sure how to launch this one (it attempts to launch using my wine-mono installation, even though it should probably use MS dotnet from the game's Proton wineprefix instead)

Thanks for the extra testing. I have asked besentv if he has any input on the last exe.

Edit: Would you be able to make a issue for the ZusiFtdEditor.64.exe problem?

Sure, I'll try to find out what is going on, and then open an issue (if I can't find an existing issue for this problem).
Thanks for the review :-)


Error during the installation with Composer under Laravel 5.7.1

Describe the bug
Error during the installation with Composer under Laravel 5.7.1.
The installation doesn't work but it's probably because I'm testing a lot of stuff on my "test" site.
To Reproduce
C:\Christophe\test>composer require binarytorch/larecipe
Using version ^1.0 for binarytorch/larecipe
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install binarytorch/larecipe v1.0.1
- Conclusion: don't install binarytorch/larecipe v1.0.0
- Conclusion: remove symfony/dom-crawler v3.4.15
- Installation request for binarytorch/larecipe ^1.0 -> satisfiable by binarytorch/larecipe[1.0.x-dev, v1.0.0, v1.0.1].
- Conclusion: don't install symfony/dom-crawler v3.4.15
- binarytorch/larecipe 1.0.x-dev requires symfony/dom-crawler ^4.1 -> satisfiable by symfony/dom-crawler[4.1.x-dev, 4.2.x-dev, v4.1.0, v4.1.0-BETA1, v4.1.0-BETA2, v4.1.0-BETA3, v4.1.1, v4.1.2, v4.1.3, v4.1.4].
- Can only install one of: symfony/dom-crawler[4.1.x-dev, v3.4.15].
- Can only install one of: symfony/dom-crawler[4.2.x-dev, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.0, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.0-BETA1, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.0-BETA2, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.0-BETA3, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.1, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.2, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.3, v3.4.15].
- Can only install one of: symfony/dom-crawler[v4.1.4, v3.4.15].
- Installation request for symfony/dom-crawler (locked at v3.4.15) -> satisfiable by symfony/dom-crawler[v3.4.15].
Installation failed, reverting ./composer.json to its original content.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop:

Windows 10 64bits

More info: installation is OK on a new installation (Laravel new larecipe) but still not on my test site even after a composer update (and thus with Laravel 5.7.2)

Hi @cavo789
Thank you for addressing the issue. However, I went through the installation process with one of my current projects which has more than 200 tests and it seems to work just fine.
Could you please share your project's dependencies here?

Hi Saleem,
I've just tried again on Laravel 5.7.3 and it's OK (I've first make a composer update).
I was under 5.7.1; perhaps something wrong with that version of Laravel since 5.7.2 was there very fast and now 5..7.3.
This issue can, for me, be closed.
Thanks and have a nice day.

Happy to hear that 🤠 have a nice day to you too.


x/tools/gopls: go vet: Printf incorrect type check in generic method

Type in printf function for floating-point verb is specified correctly, but go vet shows this as an error
gopls version
gopls v0.8.1
Editor and settings
vscode 1.65.2
"gopls": {
       "ui.diagnostic.staticcheck": true,
       "ui.completion.usePlaceholders": true,
       "ui.diagnostic.analyses": {
           // "fieldalignment": true,
           "nilness": true,
           "shadow": true,
           "unusedparams": true,
           "unusedwrite": true
       },
       "ui.diagnostic.annotations": {
           "bounds": true,
           "escape": true,
           "inline": true,
           "nil": true
       },
   },

What did you see?

Your float64 is not what you think it is: https://go.dev/doc/faq#types_in_method_declaration


fix(message-parser): mentions and emojis inside bold, italic and strikethrough

Proposed changes (including videos or screenshots)

Mentions and emojis are not parsed when they are inside bold, italic or strikethrough
After:
mentions.webm
Channel Mentions

Emojis
Unicode Emoji.webm

Emoticons

Issue(s)

https://github.com/RocketChat/Rocket.Chat/issues/27838
https://github.com/RocketChat/Rocket.Chat/issues/27839
https://github.com/RocketChat/Rocket.Chat/issues/28843
Further comments

Modifications:

Added tests for these cases and added Emoji | UserMention | ChannelMention to Bold, Italic, Strike definitions
Modified grammar.pegjs to support emojis and mentions. I added Whitespace, UserMention, ChannelMention, Emoji, Emoticon Rules.

For testing in Rocket.Chat application, modify gazzodown package  (e.g. Rocket.Chat/packages/gazzodown/src/elements/BoldSpan.tsx)
// . . .
// add imports for mentions and emojis
import EmojiElement from '../emoji/EmojiElement';
import ChannelMentionElement from '../mentions/ChannelMentionElement';
import UserMentionElement from '../mentions/UserMentionElement';

// Modify type to include emojis and mention
type BoldSpanProps = {
	children: ( MessageParser.Emoji | MessageParser.ChannelMention | MessageParser.UserMention | MessageParser.Link | MessageParser.MarkupExcluding<MessageParser.Bold>
        )[];
};

const BoldSpan = ({ children }: BoldSpanProps): ReactElement => (
	<strong>
		{children.map((block, index) => {
			switch (block.type) {
                                // . . .
				// add cases to support mentions and emojis
                                case 'MENTION_USER':
					return <UserMentionElement key={index} mention={block.value.value} />;

				case 'MENTION_CHANNEL':
					return <ChannelMentionElement key={index} mention={block.value.value} />;

				case 'EMOJI':
					return <EmojiElement key={index} {...block} />;

				default:
					return null;
			}
		})}
	</strong>
);

export default BoldSpan;

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

@tassoevan. I'm a bit unsure about marking my pr as "Ready for review" because some of the tests are failing. Can you please advise me on what I should do in this situation?

Hi @jayesh-jain252 thanks a lot for your contribution 🚀
I'm taking a look here, and the tasks that are failing it's important to fix, we had to avoid generating Emphasis elements with only whitespace inside.
I'll try to figure out here, but just as a note, we need to fix those

For Instant Testing:
Copy this grammar code from here: https://gist.github.com/jayesh-jain252/522356f9f375ccbd0ab60136080d5fbd
Paste this code at Peggyjs Online version - https://peggyjs.org/online.html
Problem (taking example for bold text):
As I modified the code and added the Whitespace rule to support UserMention/ChannelMention in Bold
Example: For input * *
We should get

We are getting

So for user inputs with only blank spaces, our grammar should not treat them as emphasis but as plain text.
I tried modifying AnyBold Rule to address this issue, but that resulted in more tests failing. If there's a way we could solve this issue do let me know.
You can modify the grammar at Peggy online for testing

For this grammar I took the top part of the code from rocketchat-pegjs-benchmark by hugocostadev and rest from current message-parse grammar.

For Instant Testing: Copy this grammar code from here: https://gist.github.com/jayesh-jain252/522356f9f375ccbd0ab60136080d5fbd Paste this code at Peggyjs Online version - https://peggyjs.org/online.html
Problem (taking example for bold text): As I modified the code and added the Whitespace rule to support UserMention/ChannelMention in Bold
Example: For input * * We should get

@hugocostadev Could you point me to any resources or give me a hint on how to approach the solution? Thanks in advance!

For Instant Testing: Copy this grammar code from here: https://gist.github.com/jayesh-jain252/522356f9f375ccbd0ab60136080d5fbd Paste this code at Peggyjs Online version - https://peggyjs.org/online.html
Problem (taking example for bold text): As I modified the code and added the Whitespace rule to support UserMention/ChannelMention in Bold
Example: For input * * We should get

@hugocostadev ,The Whitespace rule I added is responsible for these test cases to fail, but for supporting user/channel mentions I added it. Would love to hear your thoughts and suggestions on this. 😊

@hugocostadev now all the tests are passing. I've added an EmphasisWithWhitespace rule to the code. This rule checks for inputs that are of type * *,  ** **,  _ _.
Could you please review my changes and let me know if you have any feedback?

Awesome @jayesh-jain252 everything is working now, thanks a lot for your effort!

@jayesh-jain252 can you open a PR in Rocket.Chat making the changes in the Gazzodown ?

Thanks for the approval @hugocostadev 🚀. Opened the PR with changes in the gazzodown package https://github.com/RocketChat/Rocket.Chat/pull/29391


Fix setup.py

Before, biggraphite would not install without -e.

This change is

Previously, unbrice (Brice Arnould) wrote…
> #### Fix setup\.py
>
> Before, biggraphite would not install without -e.
>
>
>

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Coverage remained the same at 77.113% when pulling 0c153851bf1fbb74058e4f86cc5970101dd33d01 on unbrice:master into c7e466050f02a4310194a018fcf841a8322b941e on criteo:master.

Coverage remained the same at 77.113% when pulling 0c153851bf1fbb74058e4f86cc5970101dd33d01 on unbrice:master into c7e466050f02a4310194a018fcf841a8322b941e on criteo:master.

Previously, coveralls wrote…
>
> [![Coverage Status](https://coveralls.io/builds/6329107/badge)](https://coveralls.io/builds/6329107)
>
> Coverage remained the same at 77.113% when pulling **0c153851bf1fbb74058e4f86cc5970101dd33d01 on unbrice:master** into **c7e466050f02a4310194a018fcf841a8322b941e on criteo:master**.
>

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


Dragging container with draggable object throws error

If you click and drag on the containing div a javascript error is thrown.
drag-coordinator.js:53 Uncaught TypeError: Cannot read property 'target' of null
Easily replicated on the demos. Just click and drag on the white space between the boxes: http://mharris717.github.io/ember-drag-drop/sort

Thanks for the bug report, should be a pretty easy bug to address.

Fixed in release 0.3.3


Theme Switch Button Steps (for future reference)

There isn't a direct order you need to go in for this, although I started with finding the way I wanted to create the button and the keywords I wanted to use. I started with trying to create the theme switch as one function, but that didn't work overall.
The method I used had two different sass files, connecting to two different JS files which the function controlled in the SettingsControl file. I created a dark-mode.scss, and a light-mode.scss file.
This is the code used for the dark-mode.scss, as a reference:

.dark-mode {
    background-color: black;

    a {
        color: rgb(75, 186, 255);
    }

    a:hover {
        color: #7a7976;
    }
    .site-title, .site-title:visited, .site-nav, .page-link {
        color: #FFFFFF;
    }

    .site-nav {
        background-color: #000000;
        border-color: #FFFFFF;
    }

    * {
        scrollbar-color: #FFFFFF;
    }

    pre, code {
        // BVas a lighter colour to better highlight short code words
        border-color: #FFFFFF;
        background-color:#000000 ;
    }

    .page-description {
        color: #FFFFFF
    }

    .post-meta {
        color: #FFFFFF;
    }

    .post-content p, .post-content li {
        color: #FFFFFF;
    }

    .btn {
        background-color: #000000;
        color: #FFFFFF;
        border-color: #FFFFFF;
    }

    .btn:hover {
        background-color: #7a7976;
    }

    table th{
        background-color: #000000;
        border-color: #FFFFFF;
        color: #FFFFFF;
    }

    table td{
        background-color: #000000;
        border-color: #FFFFFF;
        color: #FFFFFF;
    }

    .flash {
        color: #5e5d5b;
        filter: brightness(80%);
    }

    .post-list > li > div {
        box-shadow: none;
        background-color: #FFFFFF;
        border: none;
    }

    li .post-meta-description {
        color: #FFFFFF;
    }

    .search-result-preview{
        color: #FFFFFF;
    }

    .search-result-highlight {
        color:yellow !important;
        font-weight:bold !important;
    }

    .search-results-list-item .search-result-title {
        color: cornflowerblue !important;
    }

    .button#startGame {
        color:#FFFFFF;
        background-color: #000000;
    }

    .leaderboard-button {
        color:#FFFFFF;
        background-color: #000000;
    }

    .input.userID {
        background: #000000;
    }

    .table.levels {
        background-color: #000000;
    }

    .sidebar {
        color:#000000;
        background-color: #FFFFFF;
    }
    .p {
        color: #FFFFFF;
    }

    .submenu {
        color: #FFFFFF;
        background-color: #000000
    }

    .menu-icon {
        color: #000000;
    }

    .div {
        color:#000000;
        background-color:#FFFFFF;
    }
    .container canvas {
        /* Reset styles for canvases within .container */
        background: none;
        /* Add any other styles you want to reset */
    }
}

for the light mode, all that needs to be done is switch the hex code properties to the opposite colors. There is an invert filter that also exists, but I'm not sure if that will work as well--I'm listing what ended up working for me.
I stored the two files in custom-styles.scss, preferably in order of how I want the files to switch.
// Guide: https://github.com/jekyll/minima/blob/master/README.md
@import "minima/dark-mode";
@import "minima/light-mode";

Now that the sass is created, and it is checked that they both work, we can create 2 functions that remove and add the light and dark mode. (Again, this is not the easiest way, but the function does work.)
lightMode.js:
// lightMode.js
export function enableLightMode() {
    // Code to enable light mode
    document.body.classList.remove('dark-mode');
    document.body.classList.add('light-mode');
}

darkMode.js:
// darkMode.js
export function enableDarkMode() {
    // Code to enable dark mode
    document.body.classList.add('dark-mode');
    document.body.classList.remove('light-mode');
}

those files will be used with the function that we created in SettingsControl.js. Import the two files into SettingsControl.js so the code knows what files you're referring to when you use it within the code with an if, else statement.
import { enableLightMode } from './lightMode.js';
import { enableDarkMode } from './darkMode.js';

I'm not directly sure if this event-listener affects the function, but I replicated one of the previous parts of the code to create this function. It seems to just be storing it in Local Storage, so I did not mess with that part.
 window.addEventListener("isTheme", (e)=>{
            // Update the isInverted value when an invert event is fired
            this[this.keys.isTheme] = e.detail.isTheme();
            // Update the isInverted value in the game environment
            GameEnv.isTheme = this[this.keys.isTheme];
            // Save the isInverted value to local storage
            this.save(this.keys.isTheme);
        });

the code is all in a certain order, so I made sure to insert the code into the correct parts of the file.
The next part of the code, is the function and the code that will create the checkbox. Here, you can name the checkbox with inner html, then connect the event-listener function to change the theme.
 get isThemeInput() {
        const div = document.createElement("div");
        div.innerHTML = "Theme Change:"; // label

        const islightMode = document.createElement("input");  // get user defined lightmode boolean
        islightMode.type = "checkbox";
        islightMode.checked = GameEnv.lightMode; // GameEnv contains latest is lightMode state
        islightMode.addEventListener('change', () => {
            if (islightMode.checked) {
                enableLightMode();
            } else {
                enableDarkMode();
            }
        });

        // Append elements to the DOM or wherever appropriate
        div.appendChild(islightMode);
        return div
        // Append div to your settings container
        // For example:
        // document.getElementById('settingsContainer').appendChild(div);
    }

I placed this code after the "isInverted" input.
now, towards the end of the document we need to duplicate some of the code to construct the HTML input, along with event update:
  // Get/Construct HTML input and event update for theme change
        var themeChangeControl = settingsControl.isThemeInput;
        document.getElementById("sidebar").append(themeChangeControl);

This code helped me construct everything, although I ran into frequent problems, so I'll list my solutions below:

The game/website uses multiple sass files. If you don't indicate the two different classes for light and dark mode it will not be used on the website. in PlatformerStyles.scss, some of the parts of code will use keywords that were previously contained in the main dark-mode.scss file. Change that keyword to a similar color, or the color that works best for that element.

b/c of this issue, I thought that I would have to wrap the entire sass file/s in main, but I just needed to create separate classes for each of them.

make sure that the sass does not also overwrite the sass within the game. I added this code to both sass files to exclude the objects within the game:

.container canvas {
    /* Reset styles for canvases within .container */
    background: none;
    /* Add any other styles you want to reset */
}

Problems I currently have:

the website starts on light mode, which I indicated I didn't want to happen. I'm not sure why it does that so I'll look into it;
you have to click the button twice for it to actually indicate the change, which doesn't make a lot of sense , so I wanna fix that as well.
adding the function into lightmode
finish replicating the code for the invert function

This code structure is pretty unique, so the process for a light/dark-mode in other websites may be similar, but I don't believe it is as complicated as it was here. I think I learned a lot more about sass code and problems with things I'm trying to do, so I'm glad I was able to learn a lot more. When I would research to see how I can create the function, I think that this code structure was so specific, that not many websites really taught me how to specifically do it how I had to do it inside of this code.
I actually had to reset the code the first time I finalized the theme switch, because with commit issues and stuff breaking it was too risky to commit my changes in. I think its more polished after starting over clean.

Fixing Issues on Function:
We needed the website to start on light mode, so I worked with Trevor in order to revise the code, this is what I changed it to:
'''js
get isThemeInput() {
const localstorage = window.localStorage
const lightmodekey = "islightMode"
const div = document.createElement("div");
div.innerHTML = "Theme Change:"; // label
GameEnv.isLightMode = localstorage.getItem(lightmodekey).toLowerCase() === "true"
    const islightMode = document.createElement("input");  // get user defined lightmode boolean
    islightMode.type = "checkbox";
    if (GameEnv.isLightMode) {
        enableLightMode();
        islightMode.checked = true;
    } else {
        enableDarkMode();
        islightMode.checked = false;
    }
    islightMode.addEventListener('change', () => {
        if (islightMode.checked) {
            enableLightMode();
            GameEnv.isLightMode = true;
            localstorage.setItem(lightmodekey, GameEnv.isLightMode)
        } else {
            enableDarkMode();
            GameEnv.isLightMode = false;
            localstorage.setItem(lightmodekey, GameEnv.isLightMode)
        }
    console.log(GameEnv.isLightMode)
    });

    // Append elements to the DOM or wherever appropriate
    div.appendChild(islightMode);
    return div
    // Append div to your settings container
    // For example:
    // document.getElementById('settingsContainer').appendChild(div);
}

within this code, we saved it to local storage, and changed the code from a string to boolean so that it actually inputs into local storage. We defined localstorage, and lightmodekey so that it can be stored as true or false.


Use DeployTarget in publish command

remove DeployTarget fields and logic from Target struct

Fixes #769 🎉

this is still happening! in a different pr. #966


Demo favicon

Add a favicon to the demo website:

Not sure if there is an official logo for the project but I created it based on this:
https://twitter.com/denisvoituron/status/1720377475882954986

I really like this but before we can merge, could you make the light version to have:

The  F filled transparently (like the rest of the inside of the Blazor 'flame')
or
have the rest of the inside of the Blazor flame be filled with white like the inside of the F

I think option 2 is better wrt the dark version. The having it all transparent would make the F kind of fade away I believe.
It is indeed our 'official' logo. There is also a png version available in the repository here. Maybe easier to work from that one.

Option 1: As expected, transparency does not look good on dark.

Option 2: Filled with white (= the change I made).

For the Dark theme, I think a white icon would be better. We lose the colors, but it's probably better. No ?
Also for Accessibility rules.

This is what you get in dark mode with the new Blazor Web App template:

so a sort of white outline around it. Can we try that?

I can do a .svg icon which is black on light mode and white on dark mode:

I prefer the solution proposed by Vincent 😊 Or only black/white for the Dark mode, but in colors for Light mode.
I've a SVG file with the colored icon. I can give you that this evening.

I like a purple variant better

Version with white outline:

Lgtm!

I replaced favicon.ico it FluentUI.Demo.Server\wwwroot when I tested locally but it seems the deployed website is FluentUI.Demo.Client\wwwroot.
The preview site https://black-pebble-0dc79cb03.3.azurestaticapps.net/ does not have the favicon.
Can you please make the change?

I just pushed the changes to replace the favicon everywhere 15 minutes ago :).
It is changed now:


Spinner animation has gone all massive

This is on Chrome 98 on Linux. Haven't had time to explore any further.

Seen on Chrome on Mac in the #measures section of the Prescribing across the NHS in England page when the charts are loading.
A possible solution would be to specify a max width in the loading-wrapper CSS:
https://github.com/ebmdatalab/openprescribing/blob/510e8c07e841cd42284c109774d1730b6463f376/openprescribing/media/css/dashboard.less#L47-L54
For example:

    max-width: 300px;  /* or a more appropriate max width */
    margin: 0 auto;    /* and centre the spinner */

@sebbacon


ParseError

Hi there. my backend running on http://localhost:1337/ but when I try to run the frontend I receive an error:
$ gridsome develop
Gridsome v0.7.21

Initializing plugins...
Load sources - 0s
ServerParseError: Unexpected token M in JSON at position 0
    at JSON.parse (<anonymous>)
    at D:\frontend\node_modules\apollo-link-http-common\lib\index.js:35:25
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Thanks for reporting this issue. The problem is that the GraphQL plugin wasn't added by the template. I have now updated the template accordingly.
There are 2 ways you can now fix this:

Install the GraphQL plugin from the marketplace on your Strapi admin dashboard
Delete your backend folder, and rerun the command to create the backend with the template


[docs] Log4j configuration needs to be better documented

We currently don't have much documentation around how to configure Log4j debugging for Pulsar, and the log4j docs are confusing. For example, I'm trying to enable DEBUG logging for Pulsar, but we're having trouble getting debug statements to show up in our rolling log. The Pulsar docs don't provide sufficient explanation around how to do this.

For example, the following Log4j file doesn't emit debug statements for permits from ConsumerImpl, Consumer, or PersistentDispatcherMultipleConsumers
log4j2.yaml.txt

I tried hard-coding "debug" in place of "${sys:pulsar.log.level}" in this part of the file:
Root:
      level: debug
      additivity: true
      AppenderRef:
        - ref: "${sys:pulsar.log.appender}"
          level: "${sys:pulsar.log.level}"
        - ref: Prometheus
          level: info

but the only classes that appear to be emitting debug-level information are bookkeeper classes.

I was able to get debug statements after hard coding "debug" in place of "${sys:pulsar.log.level}" in this part of the log4j2.yaml file:
Root:
      level: debug
      additivity: true
      AppenderRef:
        - ref: "${sys:pulsar.log.appender}"
          level: "${sys:pulsar.log.level}"
        - ref: Prometheus
          level: info

However, I haven't been able to get debug logging on the functions.

The issue had no activity for 30 days, mark with Stale label.


api-key header no longer supported

the uses the api-key header for authentication - but support for passing the api-key via the header has been continued.
any chance this can be updated?

This has been fixed. Thank you for reporting the problem and submitting a pull request!


Good

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution or feature you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
https://github.com/microsoft/azuredatastudio

@https://github.com/microsoft/azuredatastudio/pulls


Enable timers in webapp

Stop player timer
Shut down timer
Fade volume timer is prepared, but requires some additional work in core
[Not in scope] Idle timer

Very nice!


pageserver: N*2 runtime on relation drops in transaction aborts

via https://neondb.slack.com/archives/C07SY45GCLV/p1729627172113989?thread_ts=1729623078.360529&cid=C07SY45GCLV
In ingest_xact_record we do this:
        for xnode in &parsed.xnodes {
            for forknum in MAIN_FORKNUM..=INIT_FORKNUM {
                let rel = RelTag {
                    forknum,
                    spcnode: xnode.spcnode,
                    dbnode: xnode.dbnode,
                    relnode: xnode.relnode,
                };
                if modification
                    .tline
                    .get_rel_exists(rel, Version::Modified(modification), ctx)
                    .await?
                {
                    self.put_rel_drop(modification, rel, ctx).await?;
                }

put_rel_drop has O(N) cost because it rewrites the full map of relations. Then we call it N times.  Oops.
We never saw this before, until someone was doing a transaction that created ~83,000 relations and then sent us a ~1MB sized abort WAL record.

Candidate reproducer:
stas=# \timing
Timing is on.
stas=# begin;
BEGIN
Time: 3,340 ms
stas=*# DO
$$
DECLARE
    i INT;
    table_name TEXT;
BEGIN
    FOR i IN 1..100000 LOOP
        table_name := 'table_' || i;
        EXECUTE 'CREATE TABLE IF NOT EXISTS ' || table_name || ' (id SERIAL PRIMARY KEY, data TEXT)';
    END LOOP;
END
$$;
DO
Time: 111406,850 ms (01:51,407)
stas=*# commit;
COMMIT
Time: 809,877 ms
stas=# begin;
BEGIN
Time: 0,276 ms
stas=*# DO
$$
DECLARE
    i INT;
    table_name TEXT;
BEGIN
    FOR i IN 1..100000 LOOP
        table_name := 'table_' || i;
        EXECUTE 'TRUNCATE ' || table_name ;
    END LOOP;
END
$$;
DO
Time: 81238,192 ms (01:21,238)
stas=*# abort;
ROLLBACK
Time: 38396,160 ms (00:38,396)


[BEAM-9383] Staging Dataflow artifacts from environment

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @robertwb, @chamikaramj

Retest this please

@chamikaramj PTAL and rerun the tests.

Retest this please

Retest this please

Run Java PreCommit

Run Python PreCommit

Run Java PreCommit

Run Python PreCommit

@chamikaramj @robertwb : PTAL. Thanks!

Retest this please

Run Python PreCommit

@robertwb Thanks for your comments! PTAL.

@ihji Just thinking about timing, were we hoping to get this into 2.22?

Yes, I think we need this. Heejong, can you make the jar a blocker for beam 2.22 ?

Retest this please

Retest this please

Retest this please

Heejong, can you please resolve conflicts and push an update to rerun tests ?

Rebased and fixed conflict. Please rerun the test.

Retest this please

Retest this please

Run Java PreCommit

Run Java PreCommit


chore: align JSDoc usage

Align used & generated doc blocks
Check if we are able to lint them automatically

[ ] Allow selection of tags
[ ] Ban plain function & array type usage
[ ] Prefer lowercase primitives i.e number instead of Number

We currently don't have the full configuration enabled. There are some things we need to look at before we can go all in on linted JSDoc. We need to help fixing jsdoctypeparser/jsdoctypeparser#131 for things like typeof import and { foo: boolean }[] support.  And hopefully get some perf improvements in. Either by generating more efficiently, or by measuring and sending some patches to the upstream libraries.  With JSDoc linting enabled, a big project goes from about 40 seconds to a full 4 minutes with --fix enabled.
Keeping this issue open for now, prioritized after some query builder improvements and more docs.


Support building for Android with NDK.

Treat Android as Linux.
Signed-off-by: Joel Cao<EMAIL_ADDRESS>

Build status:

Linux
Windows


No handler & target matching

Hi,
I have setup the graphite-api + cyanite  + grafana.
It seems to run fine and I can get the metrics.
I see 2 issues:
1)
I do get 'No handlers could be found for logger "flask.app"' error when I try to query with the target containing a value list...i.e. {p1,p2}.*
wget -qO- "http://xxxx/render?target={srv1,srv2}.cpuload.avg1&from=-5min&until=now&format=json&maxDataPoints=960"

when I run below query...I get results for 2 metrics srv1.cpuload.avg1 & srv1.cpuload.avg15
my expectation is only to get the data for srv1.cpuload.avg1
wget -qO- "http://xxxx/render?target=srv1.cpuload.avg1&from=-5min&until=now&format=json&maxDataPoints=960"
thanks for your help

CentOS or RHEL?  I have seen issues on CentOS6 here with a zope-interface package getting in the way of things before.

This problem is most likely fixed in cyanite itself. The issue where a query for "srv1.cpuload.avg1" also returns "srv1.cpuload.avg15" is cause by cyanite's index, which has changed recently. Closing, feel free to reopen if the problem persists with cyanite master.


#378 - mounted state

Closes #378
Adds a wrapper for useState that checks if component is mounted first. Good to use for setting state within async return. Implemented in every case except 2 where the setter could not be refactored to accept a single state it required using the function param version (log modal and queue modal alerts)
All pages should continue to work normally and no infinite loops introduced. Tests still pass.

Found an infinite loop (I'm guessing) when trying to access the "say_day" command:

Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

Retested after the latest updates and everything I tried seems to work as expected now.


Remove Skype for Business Server 2019 from all the 'Applies To" sub-header/section.

The Persistent Chat role isn’t applicable for Skype for Business Server 2019 as it has deprecated. However, the articles still shows the several Persistent chat related cmdlets are applicable to Skype for Business Server 2019. This is incorrect, and the users will fall into confusion. Hence, I would suggest removing Skype for Business Server 2019 from the “Applies to” section or Add the Note within the articles saying as below.
Note : The Persistent chat in Skype for Business Server 2019 is deprecated and running this cmdlet will be applicable only to Lync Server 2013 / Skype for Business Server 2015 Persistent chat in the co-existence environment.

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

ID: 1e95b509-86cb-0436-134d-d60050af5c62
Version Independent ID: 58fb91a2-caed-9253-40c7-620c2e79434d
Content: Get-CsPersistentChatRoom (skype)
Content Source: skype/skype-ps/skype/Get-CsPersistentChatRoom.md
Service: skypeforbusiness-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

@NeeranjanShettar  This is a duplicate of issue https://github.com/MicrosoftDocs/office-docs-powershell/issues/1920. I am closing this issue as a duplicate.


go/oasis-test-runner: Refactor code to refer to scenario(s) consistently

go/oasis-test-runner/cmd: Rename --test flag to --scenario flag (-s for short version) for consistency.
go/oasis-test-runner/env:

Rename TestInstanceInfo type to ScenarioInstanceInfo and its Test field to Scenario field for consistency.
Rename Env's TestInfo() and WriteTestInfo() methods to ScenarioInfo() and WriteScenarioInfo() for consistency.

go/oasis-node/cmd/common/metrics: Use "scenario" metrics label instead of "test" for consistency.

Also fix: https://github.com/oasisprotocol/oasis-core/blob/0466b12b6c3ab9a395bcc748006d442869737242/.buildkite/scripts/daily_txsource.sh#L9

Also fix:
https://github.com/oasisprotocol/oasis-core/blob/0466b12b6c3ab9a395bcc748006d442869737242/.buildkite/scripts/daily_txsource.sh#L9

Done.


Only do gateway attachments when we are actually creating

Hi @jmahowald, thanks for the PR. It LGTM, but I'll check this branch out, test it and then merge it. Please allow me some time for this.

I've tested with vpn_create_connection = true and vpn_create_connection = false and got the expected results in both cases.

Thank you guys for the PR and review!
v1.4.0 has been released