Unable to Create Sessions Using API after Update to 0.8.1

NetBox version
3.3.10
Describe the bug
We use the Python pynetbox library to create data in Netbox programatically.  After upgrading to Netbox 3.3.10 and BGP Plugin 0.8.1 we find we are unable to create BGP sessions any longer.  The error returned is
Related Field got invalid lookup: number
This is a snippit of the data we are using to feed pynetbox:
ipv4_bgp_session = get_or_create (
            netbox.plugins.bgp.session,
            get = {
                "q": _host["host_name"]+'-ip4'
            },
            create = {
                'peer_group': 1,
                'local_address': {'address': _host["unicast_v4_mgmt"]},
                'remote_address': {'address': _host["peering_ipv4_remote"]},
                'local_as': {'asn': _host["asn_ipv4_local"]},
                'remote_as': {'asn': _host["asn_ipv4_remote"]},
                'name': _host["host_name"]+'-ip4',
                'device': {'name': _host["host_name"]}
            }
        )

To Reproduce
Steps to reproduce the behavior:

Upgrade from an older versio of netbox BGP (prior to the ASN model)
Install Latest pynetbox
Attempt to create a BGP session

Expected behavior
BGP Session is created
Additional context
Prior to the migration to the ASN model the following code worked flawlessly
ipv4_bgp_session = get_or_create (
            netbox.plugins.bgp.session,
            get = {
                "q": _host["host_name"]+'-ip4'
            },
            create = {
                'peer_group': 1,
                'local_address': {'address': _host["unicast_v4_mgmt"]},
                'remote_address': {'address': _host["peering_ipv4_remote"]},
                'local_as': {'number': _host["asn_ipv4_local"]},
                'remote_as': {'number': _host["asn_ipv4_remote"]},
                'name': _host["host_name"]+'-ip4',
                'device': {'name': _host["host_name"]}
            }
        )

Are the ASNs you are passing in the script numbers or references to ASN objects in the Core Netbox Model?  After your upgrade to 0.8.1, only the latter will work.

Thanks for the reply.  The ASNs already exist in the ASN model, so I assumed I would be able to pass it the AS number, based on the response I was getting from a GET request to api/plugins/bgp/session/, if there's a different way I should be specifying existing AS numbers let me know.

Sorry, didn't look closely enough at the original code - the issue is simply that you are using 'number' to reference the ASN instead of 'asn'; try replacing 'number' with 'asn' in your lookup and you should be good.

Sorry, didn't look closely enough at the original code - the issue is simply that you are using 'number' to reference the ASN instead of 'asn'; try replacing 'number' with 'asn' in your lookup and you should be good.

Never mind this - didn't read the first code segment. How are you populating the references to the ASN objects?

Sorry, didn't look closely enough at the original code - the issue is simply that you are using 'number' to reference the ASN instead of 'asn'; try replacing 'number' with 'asn' in your lookup and you should be good.

Never mind this - didn't read the first code segment. How are you populating the references to the ASN objects?

The ASNs were originally populated using the 'Migrate' button in version 0.7.0 of the BGP Plugin.  Currently, the ASN object looks like this in the API:
...
{
            "id": 18,
            "url": "https://netbox.int.controld.com/api/ipam/asns/18/",
            "display": "AS64515",
            "asn": 64515,
            "rir": 12,
            "tenant": {
                "id": 2,
                "url": "https://netbox.int.controld.com/api/tenancy/tenants/2/",
                "display": "ControlD",
                "name": "ControlD",
                "slug": "controld"
            },
            "description": "",
            "site_count": 0,
            "provider_count": 0,
            "tags": [
                {
                    "id": 15,
                    "url": "https://netbox.int.controld.com/api/extras/tags/15/",
                    "display": "prd",
                    "name": "prd",
                    "slug": "prd",
                    "color": "4caf50"
                }
            ],
            "custom_fields": {},
            "created": "2023-01-04T21:59:05.855207Z",
            "last_updated": "2023-01-04T21:59:05.914261Z"
        },
        ...

Based on the error, it looks like it's trying to perform a lookup based on the 'number' key - is it possible that the 'number' key is referenced somewhere further downstream in the code?  If it's possible it would be nice to see more context (i.e., what ever is performing the 'create').  Also, have you tried just adding a session manually in the REPL?


[BUG] CV HUD Element not functional

Module Version: v0.6.4 (First seen in 0.6.0
Describe the bug
Clicking on the eyeball on the Token Hud does nothing.
To Reproduce
Steps to reproduce the behavior:

Enable CV HUD element
Click on the Eyeball
See error

Expected behavior
Expected a window to open up
Screenshots

Browser:
Electrum Local and Chrome Remote
Foundry Version: 9.269
Game System: DnD5e 1.6.1
Additional context
Roll#evaluate is becoming asynchronous. In the short term you may pass async=true or async=false to evaluation options to nominate your preferred behavior.

Is printed twice in the console upon clicking the element.

Should be fixed on 0.6.5 , ty i know about that warning for now i'm focused on fixing the bugs.

Fixed! Thank you.


fix(Makefile): use git sha for VERSION

mentioned for this repository in https://github.com/deis/minio/pull/9#discussion_r46206106

It looks like we're going to make this change across all of the repos.

:+1:


Fix RelayVM for 32-bit platforms

RelayVM runtime used platform dependent type size_t for code serialization and hashcode calculation.
As a result compiled models did not work on 32-bit platforms such as ARMv7.
Related Discussion: https://discuss.tvm.apache.org/t/relayvm-on-armv7-fails-cannot-find-function-in-module/9309

I checked all Save/Load methods.
size_t was used only for Constants (fixed)
After this fix we use the following types in each method:

Header - uint64_t, string
GlobalSection - string
ConstantSection - number of constants - uint64_t, NDArray (see below) and const_device_type - uint64_t (was size_t before).
PrimitiveOpNames - string
CodeSection:  number of functions - uint64_t, functions - string, instructions - uint64_t

During  NDArray serialization we write the following to the Stream:

cpu_ctx: DLContext - int device_type, int device_id (int is 4 bytes on 32 and 64 bit platforms. On some exotic platforms it can be 16 bytes)
dtype: DLDataType - uint8_t code, uint8_t bits, uint16_t lanes
int ndim (usually 4 bytes), int64_t* shape, data void* (data_byte_size calculation is platform independent = uint8_t bits * int64_t num_elems)

We should probably use int32_t instead of 'int' during the serialization (DLContext and ndim).
It is difficult to find such a device where int is 16 bits. Lets make this improvement in a separate PR with lower priority.


[RULE] -

Proposed rule name
smeltConcretePowderIntoStainedGlass

I feel like the name is too long, but I can't think of anything shorter that describes the rule enough atm.

Describe rule
This rule would allow the player to smelt a color of concrete powder into its corresponding stained glass color. For instance, if you were to smelt gray concrete powder, it would become gray stained glass.

I think the name length is good because it perfectly describes the rule from a glance i.e. when reading the list of rules in game.
The values would be true and false with the default value being false.
The rule description should be something like:
“Smelting concrete powder in a furnace will yield stained glass of the same color”.


Merged Measurements and Resets

What is the expected behavior?
Currently, the allowed behavior of gates, phases, and barriers is different than resets and measurements;
One can apply a gate/phase/barrier on a list of singular qubits or quantum registers but can only reset or measure a singular qubit or a single quantum register.
This is also apparent in the AST: List[Union[IndexedIdentifier, Identifier]] vs. Union[IndexedIdentifier, Identifier].
This feature request proposes that resets and measurements will also accept a list of qubits or quantum registers, as in:
measure q1, q7, myQubits;, reset q1, q7, myQubits;.
This will:

Make the quantum instructions specifications more consistent ("why changing phase for several singular qubits is allowed and resetting is not?", "why is it allowed to reset a quantum register of qubits simultaneously, but not several singular qubits?"), and
Allow to bulk together single-qubit resets/measurements and enable implementation-aware improvements (i.e., it might be faster to reset/measure the singular qubits together instead of sequentially).

I think the main inconsistency is that barrier is variadic, while reset isn't.  All the others are quite natural, to me at least:

gphase applies to zero qubits on its own, by it's more like a gate and can take modifiers like ctrl, which increase the number of operands
each individual gate has a fixed number of operands semantically, but the AST needs to represent that a grammatical "gate call" could have any number
reset, barrier and measure are all instructions, but look kind of like gate calls.  I don't think it's inconsistent for them to have fixed numbers of operands, and since they can't have modifiers attached, the reference AST can represent them in a fixed form.

Personally I'd have thought "implementation-aware improvements" like grouping measures should be handled by those specific implementations' compilers. The sequential measure statements should contain the same information and the spec allows reordering of instructions.  We have the barrier statement that means "don't re-order these instructions", so it's not 100% clear to me why we'd need a second explicit form for that.  That said, I'm very aware that it's easier for implementations if the intent is spelled out by the programmer.
Perhaps this is a course of action that keeps everyone happy:

remove the variadic nature of barrier and make it take exactly one argument
overload measure to also operate on registers (as opposed to single qubits), with an evaluated type of bit[n]
allow the "alias initialiser" syntax ({q[0], q[3], q[7]} and ++-concatenation) to be used in quantum-instruction contexts to create "alias literals" without being bound to a name.  The rules about needing to be a compile-time constant would be the same as let statements (currently they aren't spelled out, though).

I haven't thought through all the ramifications of that (it could be slightly confusing with regard to arrays, perhaps?), but something like it could be a way to enforce the idea of "quantum instructions all have a fixed number of operands, but broadcast over registers", which is good for consistency, while allowing more ad-hoc groupings of qubits and bits.
That would mean that instead of barrier q0, q1;, we'd have barrier {q0, q1}; and reset {q0, q1};, but then it'd go further.  The following operations are all logically already valid OpenQASM 3 statements:
qubit[10] q;
bit[10] c;

reset {q[0], q[7]};
barrier q[0:2] ++ q[4:6];
CX {q[5], q[3]}, {q[1], q[2]};

it's just that the user has to manually write
let _temp_0 = {q[0], q[7]};
let _temp_1 = q[0:2] ++ q[4:6];
let _temp_2 = {q[5], q[3]};
let _temp_3 = {q[1], q[2]};

reset _temp_0;
barrier _temp_1;
CX _temp_2, _temp_3;

The new syntax for I'm suggesting for these particular operations is just sugar that pushes this mechanical transformation onto the compilers rather than the programmers.
The new part of the steps I had above is the overload of measure to allow it to operate on registers instead of only bits, for example as
measure {q[6], q[8]} -> c[0:1];
{c[1], c[4]} = measure {q[4], q[9]};

This is a much more contentious point as the spec stands right now, because the type of alias expressions and the assignment semantics between them aren't currently defined.  That would need some careful consideration, but I think we could work together to make something consistent if it'll enhance OpenQASM 3's usability for real-world applications in the near term.


/experiments endpoint bugs from testing

Change the following endpoints to return the indicated responses:

GET /experiments/single/[id] => return 404 when no experiment is found; return 400 when [id] is not a valid UUID
GET /experiments/conditions/[id] => return 404 when no experiment is found; return 400 when [id] is not a valid UUID
GET /experiments/getGroupAssignmentStatus/[id] => return 404 when no experiment is found; return 400 when [id] is not a valid UUID
DELETE /experiments/[id] => return 404 when no experiment is found; return 400 when [id] is not a valid UUID

These changes resulted in the /init call returning a 404 called with a new user.

@bcb37 This issue is related to changes in experiment endpoints; the error you are getting is related to experimentUserService. This PR didn't make that change.

@bcb37 @Yagnik56 I will push a fix for this. It is due to a PR for this ticket. I will open this ticket and close this one.


Intuitive understanding of RPS

I thought the RPS is the area of the shaded parts of the ECDFs (see attached). The shaded area of the red curve looks to be larger than the shaded area of the blue curve, yet the RPS value of the red is lower than the blue (the black is observations and the two colours are two different forecasts). Does anyone have an intuitive (non-mathematical) explanation of what RPS actually is?

RPS is related to the shaded part of the ECDF, but it's actually the integral of the squared difference, not the integral of the absolute difference.
I don't know if the integral of the absolute difference is a proper scoring rule, but I suspect it is not.

Ah okay. So it's the sum of the vertical distances squared. That's why RPS for blue could be higher than for red, because the vertical distance for the blue are at times almost 100, but for red the max is ~60.

@oliverangelil Yes, exactly.


Update k8s-system-api-server.json

I added the ability to view the metrics for kubernetes clusters and server api nodes separately, as this adds more visibility

i can do the same for other dashboards

okay i will clouse the PR


Added default_home_dashboard_path

Description

Added the option to change the default home dashboard path.
Relevant issues/tickets

Relates to #578
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist

[ ] This change requires a documentation update
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added a test case that will be used to verify my changes
[ ] Verified independently on a cluster by reviewer

Verification steps

@Bobbins228 How do I use this, as the operator provisions the dashboards through the API I am unable to locate them in the container, therefore unable to use this to set a path for the home dashboard as I don't know the path.

@ninkaninus I am unsure to be honest. I don't remember how I tested these changes but perhaps someone in the grafana-operator channel on the Kubernetes Slack could help you?

@ninkaninus I'm trying to do the same. Did you find a solution ?

@clementnero We did not manage to do it, as we was waiting on some merges to bitnami's helm chart, we was only on version 3.8.X where the home dashboard provisioning was implemented after version 4.0.0.
Resources I found under the investigation.
https://github.com/bitnami/charts/pull/8059
https://github.com/bitnami/bitnami-docker-grafana/issues/17
https://github.com/grafana-operator/grafana-operator/issues/578
I hope to update and test my configuration within 1 month.


Logo not aligned

Is your feature request related to a problem? Please describe.
The issue is explained in the ss , i want to align this
Describe the solution you'd like
Nothing
Describe alternatives you've considered
No response
Additional context

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We have to change the logo buddy
If you have any suggestion then please reply

@amanjaiman1 I can work on the logo part, would that work?

Ohk go ahead


Dataset class

TODO: Create a custom pytorch dataset class to take fasta files
List of seqs -> tokenize to seqs of ints -> getitem returns a tensor of ints corresponding to one tokenized sequence

done


I can't purchase upgrades

When I click on an upgrade I can afford nothing happens.

What version of CC and what version of CM and are you sure you didn't run into the bug where the game thinks you are pressing shift or ctrl (fixed by pressing shift or ctrl again)?

That worked, Thanks:)

Welcome


Update id:potionmc server's name (PotionMC to IceLands)

I'm not sure if I can do this
If you need to create a new folder for a new server name, please let me know
Thank you for your review

I believe I have the authority to modify the content editing permissions of this server. Please refer to the Git records for specific details


To .NET 8

Does any one could update it to .NET 8  for Oqtane 5.0?
I can not get it !!
Thank you very much.

ATM we plan to wait for Oqtane 5.1 which will make some dramatic changes in the Theming.
After that we plan to upgrade.
Note that the current code does also run on Oqtane 5.0 (eg on https://blazor-cms.org) but we are aware that it's still very hard to get started, so we plan to simplify it in 5.1.


fix: add missing pull_request and repository params to getSlackMessageId

In index.js, getSlackMessageId was being used without any params passed in, which led to a Cannot read property owner of undefined error. This PR adds them in by using the action's context payload

@atrudeau-vitall sorry never saw this, but just pushed the same fix in 4.5.3


Experiment/video preview spike

A spike for video preview. Note: Don't really need a review on this PR, more just to get it in for my team to use as an example and for everyone in the project to have a look at. Having said that, feel free to comment.
This spike is its own package and you'll need to yarn and yarn start within the experiments/video-preview directory to view it. You'll also need to add a sample.mp4 file in the experiments/video-preview/assets directory
There is an annoying typescript linting error which I couldn't get rid of (still works despite it). If anyone can fix that I will be indebted for life.
This spikes makes uses of video streaming.
A custom video component (Replay) makes a request to the express streaming server for a range of bytes from the input video using the video timestamp. The video timestamp is updated when each cut of the input video ends.
A cut of the input video is created whenever the user makes an edit (actually multiple cuts). For example, if they delete a word then 2 cuts are produced on either side of the word. If they move a word then potentially 4 cuts are produced. When the user plays back the current state of the project, we jump around between these cuts and basically pretend the output video has already been created. :)
I estimate that for large files (eg: 1GB), the video preview component needs about 0.2 seconds to load (this could potentially be optimised after MVP). For smaller videos (eg: < 200MB), the video preview component needs about 0.05 - 0.1 seconds to load. Hence, the min clip/cut size/word duration will probably need to be around 0.1 seconds to be recognisable in the video preview.
Please have a look at these design docs to better understand the process:
Design docs diagrams
Design doc - potential methods
Design doc - video streaming
Thank you!

If anyone can fix that I will be indebted for life.

I accept cash credit and american express https://github.com/patrickbrett/mlvet/pull/43


create extensions header for optional features requiring more std includes or newer C++ features

As mentioned in https://github.com/onqtam/doctest/issues/121#issuecomment-388090275, https://github.com/onqtam/doctest/issues/321#issuecomment-566925092, https://github.com/onqtam/doctest/issues/319#issuecomment-566247618, https://github.com/onqtam/doctest/issues/192#issuecomment-471519301, https://github.com/onqtam/doctest/issues/248#issuecomment-505161791.

E.g. stuff from https://github.com/onqtam/doctest/blob/master/examples/all_features/stringification.cpp

@Trass3r Just wanted to let you know that I really appreciate the activity and will try to address most of it whenever I can, but August will be pretty busy...

as mentioned here we'll be adding a new doctest/extensions folder where extension headers will be named doctest_<whatever>.h and there will be a single extensions.md file with documentation for them for now (each header having it's own h1 heading with the ability to being linked to).


One to many augmentations and trivial_augment extension

🚀 🚀 Pull Request
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes
The PR adds two functionalities. Augmenter enables one to many augmentations. The other lets the user alter TrivialAugmentWide's augmentation space and use it with Augmenter.
aug = Augmenter()
include_transforms=["Rotate", "Identity", "ShearX", "ShearY", "TranslateX", "TranslateY"]
aug.add_step(["images"], [adjust_saturation(0.75), trivial_augment(include_transforms)])
loader = aug.augment(ds)   #returns a dataloader
Checklist:

[ ]  Add remaining arguments from hub.integrations.pytorch
[ ]  Add functionality to save dataset to Hub.
[ ]  Add tests
[ ]  Add necessary transforms like normalize and resize

Hey @neel2299 ! Was just wondering whether you think you'll have time to work on this or should be close it for now? Thanks!

Closing for now as it's stale.


Server error

Describe The Bug:

I got a server error in logs, before the update its all worked fine (i got fridge)
To Reproduce:

Expected behavior:

Logs:
[23/11/2021, 14:54:05] [LGThinQ] LG ThinQ internal server error, try again later.
[23/11/2021, 14:54:05] [LGThinQ]
Show the Homebridge logs here (make sure homebridge DEBUG mode is turned `on`), remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
NPM Version:
Operating System:

try restart bridge 1-2 times and see if it's worked again, this error because trouble on connection to LG server
you should turn on homebridge debug mode for more detail

try restart bridge 1-2 times and see if it's worked again, this error because trouble on connection to LG server you should turn on homebridge debug mode for more detail

restarted it several times, and in thinq app all works

try restart bridge 1-2 times and see if it's worked again, this error because trouble on connection to LG server you should turn on homebridge debug mode for more detail

restarted it several times, and in thinq app all works

please turn on homebridge debug mode, you will see more debug logging

[LGThinQ] NotConnectedError:
at /usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/request.ts:38:11
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Auth.getJSessionId (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/Auth.ts:139:30)
at API.refreshNewToken (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/API.ts:254:5)
at API.ready (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/API.ts:237:7)
at ThinQ.isReady (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/ThinQ.ts:292:5)

[LGThinQ] NotConnectedError: at /usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/request.ts:38:11 at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:95:5) at Auth.getJSessionId (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/Auth.ts:139:30) at API.refreshNewToken (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/API.ts:254:5) at API.ready (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/API.ts:237:7) at ThinQ.isReady (/usr/local/lib/node_modules/homebridge-lg-thinq/src/lib/ThinQ.ts:292:5)

I'm not sure reason for this error, something I got error like this because my network got trouble, but when I restarted it after 5-10 minute, it's worked again
at the time you reported it, I tried also and see connection to LG server is slower than normal, maybe that is problem

i used to connect with apple ID and used token,
now i open a new account with LG account and its the same :(
what else can i do?

now reinstall the plugin and its stuck on this screen

the wheel is spinning non stop

please re-check network from homebridge device, look like your network (from device running homebridge) is too slow while connecting to LG server

thanks!


⚠ Cioos National CKAN has degraded performance

In f7aac01, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 5034 ms

Resolved: Cioos National CKAN performance has improved in 58632b4 after 7 minutes.


cmd/go: get ignores GOARCH environment variable

What version of Go are you using (go version)?

$ go version
go version go1.13.4 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
$ go env

GO111MODULE=""
GOARCH="386"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=".exe"
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="windows"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
GO386="sse2"
AR="ar"
CC="i686-w64-mingw32-gcc"
CXX="i686-w64-mingw32-g++"
CGO_ENABLED="1"
GOMOD="/usr/src/myapp/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-m32 -mthreads -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build660781913=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I want to cross compile a program to GOOS=windows and GOARCH=386. These variables have already been set in the environment (see above). However, I want to install some tools (code generators) before actually (cross) compiling.
Since the HostOS and HostARCH differ, I inline GOOSand GOARCH before the actual go get:
$ GOOS=linux GOARCH=amd64 go get github.com/gogo/protobuf/protoc-gen-gofast

What did you expect to see?
I expect that by specifying GOOS and GOARCH inline with the go get command, that the program (in this case protoc-gen-gofast) is compiled for linux amd64.
What did you see instead?
The inline GOARCH environment variable is ingnored. Instead a binary is produced for linux_386.

@dh1tw I believe that when you are specifying GOARCH, go get will install the compiled binary to a subdirectory of $GOPATH/bin. In this case, I believe it would be named $GOPATH/bin/linux_amd64/protoc-gen-gofast.
For example, on my amd64 linux install, if I specify a GOARCH of 386:
$ GOARCH=386 go get github.com/gogo/protobuf/protoc-gen-gofast
$ file $GOPATH/bin/linux_386/protoc-gen-gofast
go/1.13.3/bin/linux_386/protoc-gen-gofast: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, Go BuildID=RPEyDh1sv4tnwvNOxSHp/EehTLUa5pI1qu2yMin51/sLznK566rlSWYqmCDwTM/IgTIQ-IUDCYV5GkUCGRU, not stripped

Can you check $GOPATH/bin/ for me and see if that is the case?

Hi @toothrot,
The problem is actually easy to reproduce. For example, let's use a clean golang container:
$ docker run -it golang:1.13-buster /bin/bash

Within the container, we execute:
$ export GOARCH=386
$ GOOS=linux GOOARCH=amd64 go get github.com/gogo/protobuf/protoc-gen-gofast
$ ls -al /go/bin
linux_386
$ ls -al /go/bin/linux_386
protoc-gen-gofast
$ file /go/bin/linux_386/protoc-gen-gofast
/go/bin/linux_386/protoc-gen-gofast: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, Go BuildID=WMKXHIKIYum37lDtIAnS/TsmmTc2G8ppJZvlNqQea/RbWhcsXqhRnKMWQcf3DW/UXNXxoQYDBTuNAoKMvWp, not stripped

Despite explicitly specifying GOARCH=amd64 inline with the go get command, the GOARCH gets ignored and a binary for 386 gets generated (which was set as an environment variable earlier).
Same problem happens with go build.

@dh1tw In your example here, GOARCH is mistakenly spelled as GOOARCH. Can you verify that is not the issue?

Indeed, misspelling GOARCH was the problem. Embarrassing... I thought those kinds of things wouldn't happen to me anymore 😅


Sorry for the noise.


Fix withdraw expired nonce retry issue

Fixes #2797
Short description
This was caused by a race where the sending node would emit withdraw.failure as soon as the WithdrawExpired was sent, which did shutdown the node on SP, without waiting for the partner to send the Processed for it (which clears the Withdraw it in both sides). Therefore, when the nodes were restarted, the sending side started retrying this message, but the receiver had already handled it with a nonce change and would reject new retries.
The fix involves both ensuring the sender side waits for the respective Processed before failing the withdraw attempt, as well as allowing the receiver to handle older messages and send the respective Processed for it, even if it was already handled locally.
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

I've tested this PR manually on top of master with PC at hub.raiden.eth and tried several success and unsuccessful cases of withdraw, without being able to get the clients out of sync. WithdrawExpireds were sent and accepted properly, with and without WithdrawConfirmations having been mined (it's quite easy to test with how congested Goerli is currently), so I'm quite confident withdraw edge cases are solid now.


npm audit fixes, babel upgraded

Happy to help!

Please pull master

dunno how to fix bundle step :(

Fixed. thank you for help


Postscripts not working - entry is not defined

log ID: 3GR9BD8M-euc
I cannot get postscripts to work in Zotero version 5.0.96, BBT version 6.2.10 (other versions not tested). Export -> Postscript is set to the example from here:
if (Translator.BetterBibTeX && item.itemType === 'webpage') {
    if (item.accessDate) {
      entry.add({ name: 'note', value: "(accessed " + item.accessDate.replace(/\s*T?\d+:\d+:\d+.*/, '') + ")" });
    }
    if (item.url) {
      entry.add({ name: 'howpublished', bibtex: "{\\url{" + entry.enc_verbatim({value: item.url}) + "}}" });
    }
  }

I get the following error in the Zotero console:
Reference.postscript failed: <Error: ReferenceError: entry is not defined in resource://zotero-better-bibtex/Better%20BibTeX.js line 74155 > Function line undefined anonymous/result<@resource://zotero-better-bibtex/Better%20BibTeX.js line 74155 > Function:10:7 anonymous@resource://zotero-better-bibtex/Better%20BibTeX.js line 74155 > Function:7:20 complete@resource://zotero-better-bibtex/Better%20BibTeX.js:74546:17 doExport@resource://zotero-better-bibtex/Better%20BibTeX.js:75319:7 Zotero__workerContext</ctx.onmessage@resource://zotero-better-bibtex/worker/zotero.js?version=<IP_ADDRESS>&platform=win&translator=Better%20BibTeX&output=[...]bibtex.bib&localeDateOrder=dmy&debugEnabled=true&worker=15:46631:11 >
Any reference to entry causes this problem. Reading and outputting item works fine.

I need a log generated by right-clicking an item and sending it from the popup menu; it will have -refs in the ID. If the problem happens with any item (and I expect it will), any item will do.

log ID: 237HUNMH-refs-euc
While trying to reproduce the issue, I was able to nail it down to a single bibliography entry causing this error. I have attached a .rdf file, just in case.
problematic entry.zip
In any case, the issue appears to be fixed with the test build you provided. Thank you very much!

thank you, a new build is running for release


Update chart dependencies before installing

This addresses #1278, for the "alpha" series (i.e., not for #1382). It simply calls helm dep build in the chart directory, when installing or upgrading a release.
Note that it bakes in a repositories.yaml file (which specifies the repo URLs, and is necessary for the helm commands to function). This file specifies only the conventional "stable" repo. We will need to figure out how to allow other repos to be specified; it is not quite good enough to mount your own file, since it lives in a directory helm wants to write to (and the mount would mean it's read-only).

I need to make sure this can cover a couple of scenarios aside from the bare basics:
Can you set it up to use a repo other than stable?
This will probably mean mounting a repositories.yaml file; but,

those tend to have local paths in them
.. and possibly refer to certificates which would also need to be present
.. and, Helm really wants this file to be in the same directory as where it's downloading charts, but if you're mounting it from a volume, it'll be read-only

How do you provide credentials for the repo?
Credentials get put in the repositories.yaml file; so again, if you want to supply credentials, you'd have to mount that file from a secret, with the problems as above.

I've pushed the image quay.io/squaremo/helm-operator:pr-1450 for anyone who wants to try this out.


Organise

System information

OS: Win7
TypeScript Hero version: 0.11.0
VSCode version: 1.8.0

Description
When editing a TSX file, organise imports command removes the React import which is required for JSX to work.
Steps to reproduce

Edit a TypeScript file containing some react code using JSX tags
Run organise imports command

Code no longer compiles due to lack of import.

I too have a disappearing import statement, in my project when using that feature. I have an app.ts file at the root of the project which exports a default variable called app. Most of my files have a line as such:
import app from '../app';

and when I use the Organize feature, that one line disappears each time...

It would be nice if you could specify a pattern for organization.
Personally, I like node specific modules first, followed by a line feed, and then all local application imports.

Organize imports removes ListViewModel import for some reason.
I guess it's related to default exports/imports
//... other imports
import ListViewModel from './ListViewModel';

export default class ListView extends BaseView<ListViewModel> {}

Got the same issue. When i use ctrl+alt+o some used imports are always removed.
import ConfigService from "../modules/ConfigService";
Configservice exports default class.

+1

import Variables from "~/services/variables";
...
req.checkBody('password')
.notEmpty()
.isLength({ min: Variables.registration.password.minLength })
and after organize it remove always

this happens with default imports on reducers...


moving diagnostic updater for other robot

I'd like to use diagnostic updater for pepper robot ,could you move/copy this to naoqi_bridge or pepper_robot repository? Or if you tell me the direction, I can create pull request.
https://github.com/ros-naoqi/nao_robot/blob/master/nao_apps/nodes/nao_diagnostic_updater.py

right now, we have one in the C++ bridge (that you can dl as the ros-indigo-naoqi-rosbridge package) and this Python one should simply be removed. I guess we will not move it: let's simply move the C++ bridge in naoqi_bridge and we'll have everything we need this way.

Thanks, I tried but have segfaults, what's wrong with this?
+ /opt/ros/indigo/lib/naoqi_rosbridge/alrosbridge_bin --qi-url <IP_ADDRESS> <IP_ADDRESS>
going to add: /opt/ros/indigo
[W] 3513 qi.path.sdklayout: No Application was created, trying to deduce paths
[I] 3513 qimessaging.session: Session listener created on tcp://<IP_ADDRESS>:0
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://<IP_ADDRESS>:35074
using ip address: <IP_ADDRESS>
found a catkin prefix /opt/ros/indigo/share/naoqi_rosbridge/share/boot_config.json
load boot config from /opt/ros/indigo/share/naoqi_rosbridge/share/boot_config.json
found robot variable juliette
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
no camera information found for camera_source 3 and res: 0
found robot variable juliette
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
found a catkin URDF /opt/ros/indigo/share/naoqi_rosbridge/share/urdf/pepper_robot.urdf
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
found robot variable juliette
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
Audio Extractor: Start
registered subscriber:	teleop
registered subscriber:	moveto
nodehandle reset

You may pass a wrong formatted qi-url argument (tcp:// and port :9559 are missing)
Sorry for the inconvenience, I've seen it's not correctly documented. Will fix that asap.
could you please re-run with this command:
/opt/ros/indigo/lib/naoqi_rosbridge/alrosbridge_bin --qi-url=tcp://<IP_ADDRESS>:9559 <IP_ADDRESS>

thanks, finally I can start alrosbridge_bin program and see following topics
BTW, what is the goal of alrosbridge? replace all python ros drivers? if so
should we rename alrosbridge prefix for backward compatibility of pepper_robot package and
fix https://github.com/ros-naoqi/pepper_robot/blob/master/pepper_bringup/launch/pepper.launch t ouse alrosbridge?
$ rostopic  list
/alrosbridge/audio
/alrosbridge/camera/depth/camera_info
/alrosbridge/camera/depth/image_raw
/alrosbridge/camera/depth/image_raw/compressed
/alrosbridge/camera/depth/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/depth/image_raw/compressed/parameter_updates
/alrosbridge/camera/front/camera_info
/alrosbridge/camera/front/image_raw
/alrosbridge/camera/front/image_raw/compressed
/alrosbridge/camera/front/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/front/image_raw/compressed/parameter_updates
/alrosbridge/camera/ir/camera_info
/alrosbridge/camera/ir/image_raw
/alrosbridge/camera/ir/image_raw/compressed
/alrosbridge/camera/ir/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/ir/image_raw/compressed/parameter_updates
/alrosbridge/imu_base
/alrosbridge/imu_torso
/alrosbridge/info
/alrosbridge/laser
/alrosbridge/sonar/back
/alrosbridge/sonar/front
/cmd_vel
/diagnostics_agg
/joint_states
/move_base_simple/goal
/rosout
/rosout_agg
/tf

I guess all that is obsolete now that the naoqi_driver is much more stable.

@k-okada did you fix the exception message ? I get the same message when launching naoqi_driver ...


Hard-coded DNS servers in udhcpc busybox script

Can you explain the intent behind this change a bit more please?  For example, what issue did you experience, how does this fix it, and how can it be reproduced?

Sorry, this was opened here instead of the forked repository by mistake.
The issue lies with the udhcpc startup script. It replaces the contents of /etc/resolv.conf if a custom DNS server is provided with a single NS entry.


[SPARK-46455][CORE][SQL][SS][CONNECT][PYTHON] Remove redundant type conversion

What changes were proposed in this pull request?
This pr aims to clean up redundant type conversion in Spark production code.
Why are the changes needed?
Code clean up.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

Thanks @dongjoon-hyun and @ShreyeshArangath


[SPARK-16656][SQL][BRANCH-1.6] Try to make CreateTableAsSelectSuite more stable

What changes were proposed in this pull request?
This PR backports #14289 to branch 1.6
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62593/testReport/junit/org.apache.spark.sql.sources/CreateTableAsSelectSuite/create_a_table__drop_it_and_create_another_one_with_the_same_name/ shows that create a table, drop it and create another one with the same name failed. But other runs were good. Seems it is a flaky test. This PR tries to make this test more stable.

Test build #63853 has started for PR 14668 at commit 59b65b5.

Test build #63853 has finished for PR 14668 at commit 59b65b5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63853/
Test PASSed.

Test build #63866 has started for PR 14668 at commit adde06e.

Test build #63866 has finished for PR 14668 at commit adde06e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63866/
Test PASSed.

I am merging this to branch 1.6.

I have merged this PR to branch 1.6. Closing it.


Show number of unread messages in room list

Preliminary investigation the sliding sync query parameter is {"room":{"timeline":{"unread_thread_notifications":true,"limit":20},"state":{"lazy_load_members":true}}}

That'd be great to have!


Split ModelCheckpoint filepath into dirpath and filename

🚀 Feature
Previous discussions:
https://github.com/PyTorchLightning/pytorch-lightning/pull/3163#issuecomment-683539565
https://github.com/PyTorchLightning/pytorch-lightning/pull/3163#issuecomment-695854769
https://github.com/PyTorchLightning/pytorch-lightning/issues/3001
Idea:
Keep backwards compatibility by having filepath (old parameter) and dirpath, filename (new parameters)
- if filepath is set: old logic, show deprecated warning.
- if dirpath and filename are set: new logic.
- if filepath, dirpath, and filename are set: raise MisconfigurationException

cc @Borda @awaelchli @ananthsub @rohitgr7 @ydcjeff

I have been suggesting this for a long time. 😅

I know, @Borda just asked me to create a new issue to discuss.

I have been suggesting this for a long time. 😅

but it was not properly resolved, right? do you remember the issue/PR?

I like it, I vote for this :) We have plenty of tests for the filepath arg (I think thanks to @carmocca?), so the guarantee for back compatibility is there.

but it was not properly resolved, right? do you remember the issue/PR?

There was this PR #2584 but was slightly different

Should we have these parameters now in ModelCheckpoint since 1.x is released?

Yes, I think it would be useful.


Update ServiceConfig.java

增加注视
What is the purpose of the change
XXXXX
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Thank for your pr. Can you comment in English?

Thanks, please comment use English.


[WIP]Parallel execution benchmark test

[x] Parallel benchmark and group test cases.
[x] TaskQueue and TaskQueueManager test cases
[x] Handler event format and cases check

:white_check_mark: Build AElf <IP_ADDRESS>1 completed (commit https://github.com/AElfProject/AElf/commit/8e829bff7d by @EricBlack)

:x: Build AElf <IP_ADDRESS>5 failed (commit https://github.com/AElfProject/AElf/commit/ca123cf56c by @EricBlack)

:x: Build AElf <IP_ADDRESS>7 failed (commit https://github.com/AElfProject/AElf/commit/c2fcd65a5f by @EricBlack)

:x: Build AElf <IP_ADDRESS>1 failed (commit https://github.com/AElfProject/AElf/commit/3387f81ef3 by @EricBlack)

:x: Build AElf <IP_ADDRESS>3 failed (commit https://github.com/AElfProject/AElf/commit/4c1766a564 by @EricBlack)

:x: Build AElf <IP_ADDRESS>5 failed (commit https://github.com/AElfProject/AElf/commit/d1f9e8977c by @EricBlack)

:x: Build AElf <IP_ADDRESS>8 failed (commit https://github.com/AElfProject/AElf/commit/c31407b683 by @EricBlack)

:x: Build AElf <IP_ADDRESS>9 failed (commit https://github.com/AElfProject/AElf/commit/3d14d7ae3b by @EricBlack)

:x: Build AElf <IP_ADDRESS>3 failed (commit https://github.com/AElfProject/AElf/commit/6b168aaf41 by @EricBlack)

:x: Build AElf <IP_ADDRESS>9 failed (commit https://github.com/AElfProject/AElf/commit/ed43592409 by @EricBlack)

:x: Build AElf <IP_ADDRESS>36 failed (commit https://github.com/AElfProject/AElf/commit/61d51b9112 by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>49 completed (commit https://github.com/AElfProject/AElf/commit/ec499e8606 by @EricBlack)

What is AElf.Kernel.Parallel.MultiToken.Tests and what's being tested in it? Is it a unit test?

This project is created for contract parallel unit test, currently only include transaction group tests.

:x: Build AElf <IP_ADDRESS>65 failed (commit https://github.com/AElfProject/AElf/commit/b7ad7e52af by @EricBlack)

Close this PR and create new #1844


[Server] added asr engine

PR types
New features
PR changes
Models
Describe
added asr engine

@KPatr1ck review下


GUI: Enhancements to improve tutorials

Going through the tutorials has revealed some modifications that would make using the GUI much smoother for users:

[ ] Add global smoothing and scaling option (temporarily set default smoothing to zero (right now these are set manually for every new plot you make)
[x] Allow setting min/max freq on PSD
[ ] Disable spectrogram specific parameters when other plots are selected
[x] Add E/I synaptic gains button (already implemented in #885)
[ ] Add ability to set simulation data to None so that you can just load in and plot a data file

For discussion

[ ] Disable simulation data in Data to compare box, you can plot multiple simulations by hitting the Add plot button multiple times

See #914 for proposed PSD fix

[] add observer to monitor change in tstop in Simulation tab to ensure simulation length can be correctly specified for rhythmic, poisson, and tonic external drives

#918


⚠ Work In Progress : Digital Signatures ✍

This is a Work in Progress PR for Implementation of Digital Signatures into gofpdf. This PR is created to let know people that this future is currently being worked upon.
This PR soon will address issue no #115.
The implementation is majorly inspired and ported from TCPDF Example.
If you are interested in contributing to this PR, please create PR against my fork here (https://github.com/itsbalamurali/gofpdf/).
Looking for Contributors.
Thanks,
Balamurali Pandranki.

Thank you, @itsbalamurali

@itsbalamurali -- let's re-open this when everything is working.

We are also looking for same solution in our project. Any help wanted ? @itsbalamurali

We are also looking for same solution in our project. Any update ? Any help wanted ? @itsbalamurali @jung-kurt


Update context-info-transact-sql.md

Text revisions to tighten and optimize the reading flow of the material.

@fbsolo : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

Thanks @fbsolo for your clarity pass. #sign-off

@fbsolo : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.


Omit "--save" flag if npm version >= 5.0.0

As of npm 5.0.0, installed modules are added as a dependency by default, so the --save option is no longer needed.

Thanks @Suyash-Purwar

No problem

@all-contributors please add @Suyash-Purwar for bug

@all-contributors please add @Suyash-Purwar for bug


fix wrong function call

Proposed changes:

...

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[x] reformat files using black (please check Readme for instructions)

👍 Thanks!


Follow path attribute on inline mod blocks

Following on from #332 and #327, it looks like there is at least one more case to handle for mods:
https://doc.rust-lang.org/reference/items/modules.html#the-path-attribute
#[path = "thread_files"]
mod thread {
    // Load the `local_data` module from `thread_files/tls.rs` relative to
    // this source file's directory.
    #[path = "tls.rs"]
    mod local_data;
}

In visit.rs DiscoveryVisitor as well as remembering the names of modules we're inside we also need to remember their path, and then use this when finding the file to read.
https://github.com/sourcefrog/cargo-mutants/blob/3259d7765dc057d0a4402fb8de066ef4b863a707/src/visit.rs#L137-L142

@danjl1100 no obligation, but if you want to take this one let me know.

Thanks for the followup mention.
I plan on taking a look at implementing this, but likely wouldn't be until next weekend.

My initial thoughts, any guiding feedback welcome:

Thinking to use the same testdata/nested_mod test case, and add all the examples listed in the rust reference you linked.  Possibly add more levels of nesting too, so it's fairly exhaustive.
Introduce a new struct (ModNamespace?) to contain the name and optional path for each module in the mod_namespace_stack: Vec<ModNamespace>

On further look, only the path to the module (not the module name identifiers) are used on the second step.  I am thinking an extra struct is not needed, the separation from namespace_stack (all rust identifiers) means that mod_namespace_stack can contain just the filesystem names for the modules (without carrying around name as well).

Using the same test case but with some addition modules containing #[path] attributes sounds good.
Even though it's not really a security boundary we should check that paths don't contain .. or /.

Though it may be helpful to add a struct FilesystemName(String) newtype wrapper to ensure we're acknowledging it's a path and not an identifier?

Yes, the Vec<Vec<String>> feels a bit loose. Though, on the other hand, maybe it should just be a Utf8PathBuf which is basically like a FilesystemName(String): a stack holding the relative directory we'll search, and then the visitor can accumulate the paths of actual modules we need to later find. Then we need to translate a/b/c to either a/b/c.rs or a/b/c/mod.rs unless we had a specific path for c, but there's already some code like that.
Regarding the "not found" message:

Maybe that should be upgraded to an error rather than warning, and cause a non-zero exit.
Maybe the more useful thing there would be to remember and report not just the mod name but the source file/line/col of the mod statement.

Also, I think this bug is some additional evidence for the refactor considered in #329 of separating walking mods from generating mutants, but that might be large so I'd rather do it myself. It shouldn't block or conflict with this.


Apply the Immediate property to "text" components

Use the oninput attribute to apply the Immediate and ImmediateDelay properties.
These properties are only used with these components:

FluentNumberField
FluentTextField
FluentSearch
FluentTextArea

Example
<FluentTextField @bind-Value="value1" Immediate="true" ImmediateDelay="500" />

You entered: @value1

Hi. Yes that could be a good idea. I will add that in my backlog 😊

Thank you so much for considering it. 😊

Hi. Yes that could be a good idea. I will add that in my backlog 😊

Hi @dvoituron by any chance do you have an expected time for this?

Add the ImmediateDelay to FluentAutoComplete? This will be helpful before raising the event OnOptionsSearch when user is still typing.

Hi. Yes that could be a good idea. I will add that in my backlog 😊

Hi @dvoituron by any chance do you have an expected time for this?

Add the ImmediateDelay to FluentAutoComplete? This will be helpful before raising the event OnOptionsSearch when user is still typing.

Hi.
Yes, it's always in our task list. But we'd like to include this component with the same management as the other List components and add this ImmediateDelay feature to it. It's a bit more complex than I initially imagined, so it'll take a bit longer...
But we won't forget you :-)

Hi. Yes that could be a good idea. I will add that in my backlog 😊

Hi @dvoituron by any chance do you have an expected time for this?

Add the ImmediateDelay to FluentAutoComplete? This will be helpful before raising the event OnOptionsSearch when user is still typing.

Hi. Yes, it's always in our task list. But we'd like to include this component with the same management as the other List components and add this ImmediateDelay feature to it. It's a bit more complex than I initially imagined, so it'll take a bit longer... But we won't forget you :-)

Alright, that's a good one! 😊 May I know is there any way I can keep track of this update? I would like to get inform as we have a production issue due to this. User type something in the AutoComplete and it will immediately search from DB (async task). While users are typing fast, the call to DB (take some time) making the AutoComplete control to behave weird (text removing by itself).
Don't get me wrong, I am not pushing, just wish that I could track this so I could update my project once it is done. 😊
Once again, many thanks for your hard work.

We will tag you in this discussion when that will be done (in addition of the Release notes)


FunctionK instance for Rerunnable ~> Future

So tiny as to be arguably pointless but I've found I needed it more
than once.

Codecov Report

Merging #240 into master will increase coverage by 0.51%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #240      +/-   ##
==========================================
+ Coverage   91.30%   91.82%   +0.51%
==========================================
  Files           9        9
  Lines         161      159       -2
  Branches        3        3
==========================================
- Hits          147      146       -1
+ Misses         14       13       -1

Impacted Files
Coverage Δ

...il/src/main/scala/io/catbird/util/Rerunnable.scala
90.24% <100.00%> (ø)

...o/catbird/util/effect/RerunnableContextShift.scala
81.81% <0.00%> (+4.89%)
:arrow_up:

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 504edd2...300bbce. Read the comment docs.

Looks good to me.
I have no idea what the naming convention for FunctionK instances is. I feel like toFutureK would be clearer, so I'll let @travisbrown merge this one :)

I like toFuture, especially given that in normal usage it's not clear that there's a FunctionK involved at all.


Template Parse error

Hi @Cordobo ! I'm trying to add library to my project. I've installed it and then imported to module where my component lives but I still have template parse errors like this
compiler.js:2430 Uncaught Error: Template parse errors:
Can't bind to 'qrdata' since it isn't a known property of 'qrcode'.
Angular version: 7.2.15

Hi @ovesyan19 ,
can you provide a stripped down sample repo to reproduce the error?

@Cordobo yeah, I've put saple code in Stackblitz to check if it's working and no problems with that, but I'm pretty curious what can be wrong in mine if it's only importing of module to set it up. unfortunately I cant provide repo. if you can suggest cases which can cause this behavior, I will be very thankful

@Cordobo I've found what caused this issue. I've imported qrcode module only in one module where my Testcomponent lives, but few other components inherit from Testcomponent, so I just add to their module qrcode too and now it's working. maybe it will be helpful for someone

Thanks for your feedback!


testing: B.Run

go version: go1.6.2 linux/386
Sorry, if this is not relevant, but I can not find answer to this issue:
In documentation the testing pakage has function B.Run(...)
https://golang.org/pkg/testing/#B.Run
But compiler gives me error, that it is undefined.
Am I missing something? why it is in doc and not implemented?

Introduced in Go 1.7. https://golang.org/doc/go1.7#testing

@bradfitz thank you. sorry for inconvenience and a dumb question.


Flutter traces include information from before trace started?

cd flutter/examples/material_gallery
flutter run

open observatory
click 'timeline'
click 'start recording'
click 'stop recording'
click 'refresh'

Notice how the trace includes a bunch of events from before you clicked 'start recording'.  All the interesting bits of your trace (including the dart code and flutter engine, etc.) are at the far right of the timeline.   This is particularly true if you've left the app running for a while.
@johnmccutchan @chinmaygarde

It can also end up with traces after you stopped tracing?  Presumably they're still in the ringbuffer and we're dumping the whole ring buffer and not just the range we actually traced?

Observatory's timeline view is a hybrid view of the timeline and the cpu profiler. The CPU profiler is always running, so the blue bars you see before and after the trace are actually CPU samples-- this can be observed by selecting some of them and looking at the inspector panel at the bottom.

This seems confusing.  I explicitly started/stopped and then am confused that I see stuff outside of when I started/stopped.


OWNERS: remove Aleksa Sarai

I haven't contributed to this project in quite a while, and so I think
it's no longer correct to catagorise me as a maintainer of the project.
So long and thanks for all the fish.
Signed-off-by: Aleksa Sarai<EMAIL_ADDRESS>

/ok-to-test

Thanks for your work @cyphar :)

/lgtm


docs: Change saved/configured chain variable name

Description:
Variable name was openai_poem but it didn't pass in the "prompt": "poem" config, so the examples were showing a joke being returned from a variable called *_poem.
We could have gone one of two ways:

Updating the config line and the output line, or
Updating the variable name

The latter seemed simpler, so that's what I went with. But I'd be glad to re-do this PR if you prefer the former.
Thanks for everything, y'all.  My b


Replace double quotes to identifier

🚧  Draft yet

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

792 of 794 (99.75%)  changed or added relevant lines in 72 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 98.418%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/src/data/interval/mod.rs
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
39566

Relevant Lines:
40202

💛  - Coveralls


Admin user can't login after reboot

Hi,
I've correctly installed caravel on my laptop following the tutorial on
Caravel installation and initialization
During the installation I created a user admin with password admin and I can log in at localhost:8088.
Just rebooting the pc and restarting the application with
caravel runserver -d
and the user admin can't log in more.
I have to perform all the steps of installation to login again.
I've try this almost 4 time with the same behaviour; am I missing something?
Thanks in advance.
Regards

I think your SQLite database is in the /tmp folder. In the tutorial you linked you can see that the caravel_config.py file given as an example sets the SQLALCHEMY_DATABASE_URI = 'sqlite:////tmp/caravel.db'. Set it to a file that is not in /tmp. Also make sure the caravel_config.py file is in your python path.

Hi  IljaKroonen,
thanks for your answer.
I've not used the caravel_config.py file in my installation, I suppose that the default position of the SQLite database is /tmp folder too.
I'll try to specify a different location in that field.
Regards

I am facing the same issue. Could you solve it? I tried changing the caravel.db location from /tmp to somewhere else as well, but with no luck. If I have caravel.db inside /tmp and if the config file it pointing to that file, I don't see an issue why it should not work. And why was it working when I first installed it and stopped working after the reboot.

I could solve the issue by changing the location of caravel.db and changing config.py's SQLALCHEMY_DATABASE_URI to point to my new caravel.db location. When browsing the sqlite database, I could see that there was no user there. So I used "fabmanager create-admin --app caravel" again to create admin user. I was able to successfully log in after that, however dashboard and slices would not load as the tables were not present there. So I ran "caravel db upgrade" again and everything is running as expected after that.

Updating caravel_config.py, adding it to python path, and running caravel db upgrade addressed this issue for me.
I then got 404's on `http://localhost:8088/tablemodelview/show/1
Clearing cookies for localhost fixed this per #462, it is a FlaskApp issue and cookie clearing is a workaround.

Probably you are on Azure. Instance clean /tmp after restart. I have replaced sqlite with mysql backend for storing internal Caravel data.
Create /usr/local/etc/caravel_config.py:
ROW_LIMIT = 50000 CARAVEL_WORKERS = 16 CARAVEL_WEBSERVER_ADDRESS = '<IP_ADDRESS>' CARAVEL_WEBSERVER_PORT = 8088 CARAVEL_WEBSERVER_TIMEOUT = 60 CUSTOM_SECURITY_MANAGER = None SECRET_KEY = '\2\1changethis\1\2\e\y\y\h' SQLALCHEMY_DATABASE_URI = 'mysql://root:changethis@localhost/caravel' AUTH_USER_REGISTRATION = False CACHE_CONFIG = {'CACHE_TYPE': 'RedisCache'}
Then export PYTHONPATH:
export PYTHONPATH=/usr/local/etc
Then run all setup steps again.


Unable to build app for Android SDK 31 or 32.

Bug Report
It is not possible to build the application for android platform sdk 31 and 32 after adding the plugin.
Platform and Version: Android Sdk 31 and 32
cordova info Printout

Task :app:compileDebugKotlin FAILED
w: Runtime JAR files in the classpath should have the same version. These files were found in the classpath:
C:///.gradle/caches/transforms-3/385d3cef332eae6d8c833ca4a22c5d7f/transformed/jetified-kotlin-stdlib-jdk8-1.3.72.jar (version 1.3)
C:///.gradle/caches/transforms-3/37c16254af6de93c45d2587b8dfcd992/transformed/jetified-kotlin-stdlib-jdk7-1.5.20.jar (version 1.5)
C:///.gradle/caches/transforms-3/efb587c616850f9dc0cda8853a96db77/transformed/jetified-kotlin-stdlib-1.6.21.jar (version 1.6)
C:///.gradle/caches/transforms-3/b6f68fc904e7a7217e6038f3031dcf3a/transformed/jetified-kotlin-stdlib-common-1.6.21.jar (version 1.6)
w: Some runtime JAR files in the classpath have an incompatible version. Consider removing them from the classpath
e: C:***\platforms\android\app\src\main\java\com\adobe\phonegap\push\PushPlugin.kt: (466, 57): Unresolved reference: token
e: C:***\platforms\android\app\src\main\java\com\adobe\phonegap\push\PushPlugin.kt: (619, 57): Unresolved reference: deleteToken

Same (or very similar) issue for me. It's very bizarre -- I've been quite happily building my app every few minutes, then bang... build fails. I've not added or removed any plugins, just changed some app JS.
> Task :app:compileDebugKotlin FAILED
w: Runtime JAR files in the classpath should have the same version. These files were found in the classpath:
    C:/Users/m.beard/.gradle/caches/transforms-3/cc5cc74c45c7cc5e76733fe8278ba926/transformed/jetified-kotlin-stdlib-jdk7-1.5.20.jar (version 1.5)
    C:/Users/m.beard/.gradle/caches/transforms-3/adaf9cac4b199e0779758b8aae901bb4/transformed/jetified-kotlin-stdlib-1.7.10.jar (version 1.7)
    C:/Users/m.beard/.gradle/caches/transforms-3/eda4e3aecc1ddb0771d71f6ab843e15d/transformed/jetified-kotlin-stdlib-common-1.7.10.jar (version 1.7)
w: Some runtime JAR files in the classpath have an incompatible version. Consider removing them from the classpath
e: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors
e: C:/Users/m.beard/.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation/1.5.0/857678d6b4ca7b28571ef7935c668bdb57e15027/annotation-1.5.0.jar!/META-INF/annotation.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.

I've not posted the entiore error log as it goes on and on, but the key seems to be:
Class 'kotlin.somehting' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.

Removing the plugin fixes the issue, but that's not really an option.

Same here.
Yesterday everything was working fine.

I don't remember exactly what I did to fix this problem, because I had several problems trying to get my app to work for sdk 32. But I believe that reinstalling all my plugins in the most current version and installing jdk 11, one of these two things solved it. Maybe you should start by trying to install JDK 11.

And of course, make sure you are running the most current version of cordova and cordova-android.

Thanks, but none of that explains how the app will build without problems, but then fail a few minutes later. I'm already on JDK11. Also, the latest cordova-android is 11.0.0, which is not a trivial update to 10.1.2.

preziotte - You made my day, after I lost two other days for looking for a solution.
BTW it is f...g crazy when one day cordova stops compiling app without any warning.

@preziotte thanks. I coud have sworn I'd already tried that, but it does indeed work. Maybe it was after I'd removed annd re-added the plugin and platform a few times.

I think I was able to fix this by adding the following to my config:
<preference name="GradlePluginKotlinEnabled" value="true" />
<preference name="GradlePluginKotlinVersion" value="1.7.10" />

My build succeeds at least. No idea why this just started happening. Everything was fine a day or two ago.

Ah I thought i was going crazy! My builds were working fine 2 weeks ago, changed nothing & wasn't working today :(.
Spent all day looking for a fix until I came across @preziotte's solution. Fixed it for me! Thank you!

@matscav what's capacitor?

Me either had the same problem. Trying to fix it, I deleted ~/.gradle/caches, then deleted entire ~/.gradle. Nothing helped: my assembly chain creates the cordova project from scratch each build; I have the recent Java SDK.
Indeed, my build chain worked two weeks ago, and now it's broken without any changes from my side. Nevertheless, the solution of @preziotte (thank you, mate !) worked to me. I'm curious what happened...
The output of my build toolchain is the following (after clean launch) :
Task :app:compileDebugKotlin FAILED
w: Runtime JAR files in the classpath should have the same version. These files were found in the classpath:
/Users/xxx/.gradle/caches/transforms-3/37c16254af6de93c45d2587b8dfcd992/transformed/jetified-kotlin-stdlib-jdk7-1.5.20.jar (version 1.5)
/Users/xxx/.gradle/caches/transforms-3/16f0fa7a8f147bbbdd08181b1d0ed2ab/transformed/jetified-kotlin-stdlib-1.7.10.jar (version 1.7)
/Users/xxx/.gradle/caches/transforms-3/727d189c560aae87eb38bbb136e543d5/transformed/jetified-kotlin-stdlib-common-1.7.10.jar (version 1.7)
w: Some runtime JAR files in the classpath have an incompatible version. Consider removing them from the classpath
e: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors
e: /Users/xxx/.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation/1.5.0/857678d6b4ca7b28571ef7935c668bdb57e15027/annotation-1.5.0.jar!/META-INF/annotation.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/xxx/.gradle/caches/transforms-3/16f0fa7a8f147bbbdd08181b1d0ed2ab/transformed/jetified-kotlin-stdlib-1.7.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/xxx/.gradle/caches/transforms-3/727d189c560aae87eb38bbb136e543d5/transformed/jetified-kotlin-stdlib-common-1.7.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/xxx/work/prescrire/guide/cordova/platforms/android/app/src/main/java/com/adobe/phonegap/push/BackgroundActionButtonHandler.kt: (14, 2): Class 'kotlin.Suppress' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/alex/.gradle/caches/transforms-3/16f0fa7a8f147bbbdd08181b1d0ed2ab/transformed/jetified-kotlin-stdlib-1.7.10.jar!/kotlin/Suppress.class
e: /Users/xxx/work/prescrire/guide/cordova/platforms/android/app/src/main/java/com/adobe/phonegap/push/BackgroundActionButtonHandler.kt: (31, 25): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.

ref: #224

@matscav what's capacitor?

https://capacitorjs.com/

I had the same error appear on me out of nowhere and I literally spent almost 2 days trying to figure it out. I even switched to MacOS for building thinking it's a Windows issue but it was exactly the same. Everything worked and suddenly stopped.
My app builds now after adding the preference, however on MacOS I encountered the problem somewhere else, but thankfully it doesn't cause the build to fail:
e: /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.7.10/d2abf9e77736acc4450dc4a3f707fa2c10f5099d/kotlin-stdlib-1.7.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.4.0.
e: /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.7.10/1ef73fee66f45d52c67e2aca12fd945dbe0659bf/kotlin-stdlib-jdk7-1.7.10.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.4.0.
e: /Users/user/.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation/1.5.0/857678d6b4ca7b28571ef7935c668bdb57e15027/annotation-1.5.0.jar!/META-INF/annotation.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.4.0.
e: /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-android-extensions-runtime/1.7.10/6cf8c7aec5501d2892bc4392f0a109f68eb86da/kotlin-android-extensions-runtime-1.7.10.jar!/META-INF/kotlin-android-extensions-runtime.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.4.0.
e: /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.7.10/bac80c520d0a9e3f3673bc2658c6ed02ef45a76a/kotlin-stdlib-common-1.7.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.4.0.

@veodko : i might be this problem #224

@veodko : it might be this problem #224

I have already tried the modified version of the plugin, as well as adding the Kotlin version preference to cordova.
This error is thrown from task:lintVitalRelease and does not affect the build, I guess it's not a crucial task but I'm still a little concerned.
It complains about version 1.4.0 here so it's something that uses an even older version than the rest of  Cordova.
This whole problem kinda looks like something just started ignoring older Kotlin versions and builds with 1.7.1 anyway. It's weird because during the cordova build I could see that kotlin compiler for 1.5.20 was being  downloaded.
I  thought that using the modified plugin & removing the preference would fix it (if the plugin was only one at fault) but it's still there.

Just a bump for "capacitor". I maintain bunch of hybrid apps. About 50% on capacitor and 50% are still on cordova. The capacitor ones are a dream to maintain with zero issues, whereas every time I make a change on a cordova app, hours are wasted on issues just like this.

Just a bump for "capacitor". I maintain bunch of hybrid apps. About 50% on capacitor and 50% are still on cordova. The capacitor ones are a dream to maintain with zero issues, whereas every time I make a change on a cordova app, hours are wasted on issues just like this.

It's true, cordova is a total mess with every single plugin not being maintained by anyone for 2-4 years and even if people try to maintain them by making PRs, no one accepts them so we end up with 10 forks of the same plugin. I'm only  still using this garbage technology because of a large app written using cordova and meteorjs. There is no time to move this to anything newer, it would require a full rewrite to some other framework.

I think I was able to fix this by adding the following to my config:
<preference name="GradlePluginKotlinEnabled" value="true" />
<preference name="GradlePluginKotlinVersion" value="1.7.10" />

My build succeeds at least. No idea why this just started happening. Everything was fine a day or two ago.

I am upgrading an old project from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>The build did not succeed in my project after this change. however,  error regarding JAR Files disappeared.

@preziotte thanks for your suggestion as above.
I've applied your suggestion but it does not fix the build yet.
Given, I am using
Node - v18.15.0, NPM-v9.5.0, cordova-v11, cordova-android-v11, gulp-v3.9, android-sdk-build-tools-v32.0.0,
Please suggest:
> Task :app:compileReleaseKotlin
e: /path-to-my-app/platforms/android/app/src/main/java/com/adobe/phonegap/push/PushPlugin.kt: (466, 57): Unresolved reference: token
e: /path-to-my-app/platforms/android/app/src/main/java/com/adobe/phonegap/push/PushPlugin.kt: (619, 57): Unresolved reference: deleteToken

Just a bump for "capacitor". I maintain bunch of hybrid apps. About 50% on capacitor and 50% are still on cordova. The capacitor ones are a dream to maintain with zero issues, whereas every time I make a change on a cordova app, hours are wasted on issues just like this.

It's true, cordova is a total mess with every single plugin not being maintained by anyone for 2-4 years and even if people try to maintain them by making PRs, no one accepts them so we end up with 10 forks of the same plugin. I'm only still using this garbage technology because of a large app written using cordova and meteorjs. There is no time to move this to anything newer, it would require a full rewrite to some other framework.

Thats why we should keep the community alive, and going, so we dont have to spend huge amount of time for rewrite.... Selfishly atleast keep the community going until our retirement lol

Just a bump for "capacitor". I maintain bunch of hybrid apps. About 50% on capacitor and 50% are still on cordova. The capacitor ones are a dream to maintain with zero issues, whereas every time I make a change on a cordova app, hours are wasted on issues just like this.

Want to maintain one more?  We are looking to outsource the maintenance of our Cordova app.

It's true, cordova is a total mess with every single plugin not being maintained by anyone for 2-4 years and even if people try to maintain them by making PRs, no one accepts them so we end up with 10 forks of the same plugin.

Thats why we should keep the community alive

@clarklight, that's exactly what the person before you said - people TRY to keep the community alive, but more and more companies are stopping with hybrid apps exactly because they're messy and the Cordova maintainers can't even keep a push plugin alive. This isn't even an official plugin, and unofficial plugins tend to do exactly this: get ghosted and fall out of maintenance. And then, people completely unrelated start showing up with issues and try to jerry-rig solutions (I even have my own fork of this, trying to fix #94), until someone more knowledgeable tries to steer the ship back to its course. Sadly, it's very rare for a new captain to show up, or the old one to wake up.
Bottom-line: the community is alive, but without captains to take control of the ships, we'll slowly drown. So we better jump ship before it's too late - and I feel it is, since there are years this essential plugin is taking dust around here...

@preziotte thanks for your suggestion as above. I've applied your suggestion but it does not fix the build yet.
Given, I am using Node - v18.15.0, NPM-v9.5.0, cordova-v11, cordova-android-v11, gulp-v3.9, android-sdk-build-tools-v32.0.0,
Please suggest:
> Task :app:compileReleaseKotlin
e: /path-to-my-app/platforms/android/app/src/main/java/com/adobe/phonegap/push/PushPlugin.kt: (466, 57): Unresolved reference: token
e: /path-to-my-app/platforms/android/app/src/main/java/com/adobe/phonegap/push/PushPlugin.kt: (619, 57): Unresolved reference: deleteToken

Make sure you do not only upgrade the push plugin to the latest version 4.0.0-dev.0 but either first uninstall the plugin with:
cordova plugin remove @havesource/cordova-plugin-push

and then reinstall with:
cordova plugin add @havesource/cordova-plugin-push@dev

Or manually update the versions under cordova.plugins in package.json to the following:
"@havesource/cordova-plugin-push": {
    "ANDROIDX_CORE_VERSION": "1.6.+",
    "FCM_VERSION": "23.+",
    "IOS_FIREBASE_MESSAGING_VERSION": "~> 8.1.1"
}

Finally, you also need to make sure the POST_NOTIFICATIONS permission is present in config.xml:
<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>

Until #238 has been fixed you can use cordova-plugin-android-permissions to check for and request permissions.

This issue should have been resolved with the latest released version 4.0.0. It has Kotlin version 1.7.21 set.
Please reinstall the plugin and try again.


Not supporting Laravel-DataTables-oracle [9.0]

Summary of problem or feature request
Can't install laravel-datatables-fractal because it's require yajra/laravel-datatables-oracle: 8.*
and not supporting yajra/laravel-datatables-oracle: 9.*
when trying to install this package plugin
with composer require yajra/laravel-datatables-fractal
composer shows  error:

yajra/laravel-datatables-fractal v1.3.0 requires yajra/laravel-datatables-oracle 8.*

Operating System : Ubuntu 16.04
PHP Version : 7.2
Laravel Version : 5.9
Laravel-Datatables Version : 9.0

+1 👍for this :-)

Any updates on this? This is blocking my update process...


Storybook 4 not compatible with react 15

Bug
Expected: Min version of react is set to react >= 15.0.0 , but real minimal version of react set by @emotion/core which need react >= 16.3.0
Using react 15 produce error on loading storybook

Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/react 4.0.0-alpha.21
react 15

Screenshots / Screencast / Code Snippets (Optional)
// @storybook/core/package.json
"dependencies": {
    "@emotion/core": "0.13.0",
},
"peerDependencies": {
    "react": ">=15.0.0",
    "react-dom": ">=15.0.0"
},

// @emotion/core/package.json
"peerDependencies": {
    "react": ">=16.3.0"
},

It's frustrating, since I can not use the react 15 and webpack 4 in my application if it use storybook

Hey @Sujimoshi thanks for the issue.
We want to help you as much as wel can. I hope you understand we're doing the best we can to stay backwards compatible AND allow users to use the latest and greatest AND have a nice experience doing it ourselves.
Right now this is these thoughts on the matter:
We're moving forward with React 16 compatibility only for the moment. We didn't want to exclude React 15, it just happened with us ourselves updating to the modern tools/libs.
This may sounds strange, but React is the only lib that has this problem because of how we're using webpack & set up the package dependencies. We want to change this.
Mid term, we want to split the manager & preview more and this would allow you to run any version of react, and us to run our own.
Short term there are a couple of options:

Keep using the alpha.20
Upgrade to React 16
Find some compatibility lib
Assist us with achieving the above faster. I'd be super happy to have a chat about it in detail.
Assist us in bringing back compatibility using some other method

I understand this is not exactly the news you were hoping to get, Let's help each other!

Isn't alpha.20 have the same dependencies?

Isn't alpha.20 have the same dependencies?

I am not familiar with storybook source code, but why not just remove react from peerDeps, and allow storybook webpack bundle two versions of react

I am in the process of updating a React 15 application to use Webpack 4 and Babel 7. An upgrade to React 16 is in the horizon, but our app is quite large, and will take quite a long time.
Of the options that @ndelangen posted above, I chose to pin the version of Storybook.
Just a note that I needed to pin to version 4.0.0-alpha.18 to get things to work.

@Sujimoshi how does your .storybook/webpack.config.js look? There's a chance we could find out how to make it work with<EMAIL_ADDRESS>

Just a note that I needed to pin to version 4.0.0-alpha.18 to get things to work.
Thank for you reply, my project is huge, so i can't just update to react 16. But pin to 4.0.0-alpha.18 make sense.

@Sujimoshi how does your .storybook/webpack.config.js look? There's a chance we could find out how to make it work with<EMAIL_ADDRESS>
I'm in no hurry to switch to webpack 4. I just would like to solve the problem with backward compatibility, and help Storybook. Anyway here is my webpack 4 config:
const path = require('path')
const OneToOnePlugin = require('webpack-one-to-one-plugin')

module.exports = (unused, args) => {
  const env = args.mode || 'production'
  const isProd = env === 'production'

  const config = {}
  config.module = { rules: [] }
  config.plugins = []

  config.mode = isProd ? 'production' : 'development'

  config.entry = path.resolve(__dirname, 'src/index.js')

  // config.devtool = 'cheap-module-source-map'

  config.context = path.resolve(__dirname, 'src')

  config.output = {
    path: path.resolve(__dirname, 'dist'),
    filename: 'index.js',
    library: 'cond-component-datepickers',
    libraryTarget: 'umd',
  }

  if (isProd) config.plugins.push(new OneToOnePlugin())

  config.module.rules.push({
    test: /\.js$/,
    exclude: /(node_modules|bower_components)/,
    use: {
      loader: 'babel-loader',
    },
  })

  config.module.rules.push({
    test: /\.css$/,
    use: [
      { loader: 'style-loader' },
      { loader: 'css-loader' },
    ],
  })

  config.module.rules.push({
    test: /\.scss$/,
    use: [
      { loader: 'style-loader' },
      { loader: 'css-loader' },
      { loader: 'sass-loader' }],
  })

  config.module.rules.push({
    test: /\.(png|svg|jpg|gif)$/,
    use: [
      'file-loader',
    ],
  })

  config.module.rules.push({
    test: /\.(woff|woff2|eot|ttf|otf)$/,
    use: [
      'file-loader',
    ],
  })

  return config
}

I just managed to launch Storybook 4 with webpack 4 and react 15. As I mentioned above, I just set react and react-dom 16.4.1 as forward dependencies of Storybook/core, Storybook/react and Storybook/ui. So after the launch, there were two versions of the react inside the bundle. React 15 for my project, and React 16 for storybook components. And it works

Why react is listed as peerDependency, if Storybook generally use react for its ui. I'm surprised that this problem did not arise before

I just set react and react-dom 16.4.1 as forward dependencies of Storybook/core, Storybook/react and Storybook/ui. So after the start-storybook, there were two versions of the react inside the bundle, React 15 for my project, and React 16 for storybook components. And it works

Can you please help me understand what you mean with this?
I'm unfamiliar with "forward dependencies".

Direct dependency (just dependencies in package.json), sorry for my english

No problem, I think I understand now.
I guess if we set react & react-dom as regular dependencies with 16 or higher, this will fix this issue too.
Is what you're saying..?

Yeah that sounds like something we could do, to preserve React <16 compatibility!
@Hypnosphi is our peerDependency master, do you see any issues with this?
The version of react Storybook needs, is whatever emotion 10 needs.

Exactly

@Sujimoshi you have no plugins, so there are good chances that your setup will work with Storybook 3.4 and webpack 4 as is

We use React & React DOM in preview iframe as well: https://github.com/storybooks/storybook/blob/master/app/react/src/client/preview/render.js

@norbert We use React & React DOM in preview iframe as well: https://github.com/storybooks/storybook/blob/master/app/react/src/client/preview/render.js

Is this a problem?

We can actually use resolve.alias to enforce our version. But this means that components that use some APIs removed in 16 (like React.PropTypes) will break. Which can in turn be fixed by user-provided resolve.alias in custom webpack config =)

Not the best solution, as for me

@Sujimoshi you have no plugins, so there are good chances that your setup will work with Storybook 3.4 and webpack 4 as is

Not an option, I have other configurations that require plug-ins

I have other configurations that require plug-ins

those will require some duplication between webpack.config.js and .storybook/webpack.config.js

Is this a problem?

That means that we can render your components (created with React 15) using React DOM 16, which can become a problem in some cases

What if pass specific version of ReactDOM as option to storybook

I'd say that resolve.alias is such an option =)

As long as we keep the react in the iframe compatible with react15 we're good on react15 compatibility, IF we make sure iframe and manager can have a separate versions of react.
I think it's natural for there to be 2 versions of react there, otherwise react-users are locked to use the same version of react as we are.

I thinlk we can just prebuild manager and bundle our react 16 into dist

addons.js makes it a bit tricky but still possible

IF we make sure iframe and manager can have a separate versions of react.

A good question is, how do we do that. Does webpack allow different require.resolve for different entry points? Or we need two separate webpack builds?

Is I know webpack doesn't have such option.

And we probably can't use emotion in info addon unless we do #1501

@Hypnosphi docs-view will solve this. I'd say we're not doing #1501 and we'll assist people migrating to docs-view instead. (which will not have the react in preview)

As I know webpack doesn't have such option. So you need two configs

Working that that exactly, will not make it into 4.0.0
But we'll likely introduce this in some 4.x.y

Released a first version of compatibility in 4.1.0-alpha.4: https://github.com/storybooks/storybook/releases/tag/v4.1.0-alpha.4
Still needs more testing and documentation.

cc @ranyitz @Sujimoshi @caitlin615 @arkadiusm @Buggytheclown @stereodenis
If you'd like to test out the alpha on your projects and let us know if it works for you, that would be really awesome! Just try out @storybook/react@next which should get you the latest alpha.
@ndelangen is there anything else they need to do or will it work out of the box?

We changed so the preview and manager can use different versions.
With the last next release, using any version of react should just work.

@Frankcarvajal it's released as alpha in @storybook/react@next. Please check it out! We expect to do a stable release in the next few weeks.

@shilman - I've tried the new version on our project wix-style-react but building the storybook failsas Webpack fails to bundle the manager and hits undefined (no error checking on build-static.js).
Trying to log the webpack errors shows it couldn't resolve react from react-dom
You can check out the PR branch that was created https://github.com/wix/wix-style-react/pull/2494 and our discussion.

Thanks @shlomitc!
@shilman I've found the bug with the resolution of react/react-dom.
TL;DR The manager gets the user version of react and react-dom instead of the version specified in @storybook/react. The issue explained in details in this comment.

The next "next" release should fix this.

@shilman Do we close this, as it's fixed now in "next"?

Yep, closing!

I keep getting errors with the latest alpha build (v4.1.0-alpha.11) when trying to run build-stroybook
ERR! Module not found: Error: Can't resolve 'react/lib/ReactCurrentOwner' in '/Users/shlomitc/WebstormProjects/wsr-storybook-new/node_modules/react-dom/lib'
(node:73176) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): ModuleNotFoundError: Module not found: Error: Can't resolve 'react/lib/ReactCurrentOwner' in '/Users/shlomitc/WebstormProjects/wsr-storybook-new/node_modules/react-dom/lib'
(node:73176) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


Paginate problem

I downloaded the theme and run "jekyll serve". I got this error. Can you help me? Thanks.
C:\Users\HonouR\Desktop\jekyll-uno-bozuk\jekyll-uno-master>jekyll serve
Configuration file: C:/Users/HonouR/Desktop/jekyll-uno-bozuk/jekyll-uno-master/_
config.yml
       Deprecation: You appear to have pagination turned on, but you haven't inc
luded the `jekyll-paginate` gem. Ensure you have `gems: [jekyll-paginate]` in yo
ur configuration file.
            Source: C:/Users/HonouR/Desktop/jekyll-uno-bozuk/jekyll-uno-master
       Destination: _site
 Incremental build: disabled. Enable with --incremental
      Generating...
  Dependency Error: Yikes! It looks like you don't have pygments or one of its d
ependencies installed. In order to use Jekyll as currently configured, you'll ne
ed to install this gem. The full error message from Ruby is: 'cannot load such f
ile -- pygments' If you run into trouble, you can find helpful resources at http
://jekyllrb.com/help/!
  Liquid Exception: pygments in C:/Users/HonouR/Desktop/jekyll-uno-bozuk/jekyll-
uno-master/_posts/2016-01-08-welcome-to-jekyll.markdown
             ERROR: YOUR SITE COULD NOT BE BUILT:
                    ------------------------------------
                    pygments

Like the error mentioned, jekyll-paginate was missing from the config. I have fixed and updated the project.


Suggested fixes for issues #64 and #67

Note, this does set the default of having a square hinton diagram equal to False, but since we're bounding to the data size, I think that's okay.  Since the axes are now left in their default state, if someone wants to disable the x-ticks and y-ticks, they can do so by grabbing the current axis and turning off the ticks, e.g.,
bplt.pyplot.xticks([])
bplt.pyplot.yticks([])

Thanks a lot, this is great! :+1:

For your information, I made just some minor changes to the suggested fixes in https://github.com/bayespy/bayespy/commit/399892695ac76252ab9e465c257fd944cd1afb28 and https://github.com/bayespy/bayespy/commit/7d424d994258c4523eb86a2913a1e899f706dd9d. I also added you to the list of contributors. Thanks for this!

I'm not entirely sure about the way I changed that Hinton plot. Matplotlib is a bit dark magic sometimes. Anyway, I wanted the axes to be tight around the Hinton diagram and not show any ticks but still support axis labels. By trial-and-error I ended up in the final version..


DNS: server can't find management1: NXDOMAIN

After a fresh deployment of management1 and login1:
[root@login1 ~]# nslookup management1
;; Got recursion not available from <IP_ADDRESS>, trying next server
;; Got recursion not available from <IP_ADDRESS>, trying next server
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

** server can't find management1: NXDOMAIN

No problem when specifying the DNS:
[root@login1 ~]# nslookup management1 <IP_ADDRESS>
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Name:   management1.tumulus.local
Address: <IP_ADDRESS>

My resolv.conf:
[root@login1 ~]# cat /etc/resolv.conf
#### Blue Banquise file ####
## Ansible managed: modified on 2020-05-28 22:47:28 by root on management1

search tumulus.local
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

https://kb.isc.org/docs/aa-00269

Interesting. Would need to define ACL then.
Don't use internal DNS on lab cluster, so never faced this.

I found some time to look at this. It seems to be related to nslookup behavior which defaults to recurse. The dns_server role disable recursion in named.conf, thus the ;; Got recursion not available from <IP_ADDRESS>, trying next server seems legit. Because there is another nameserver in my /etc/resolv.conf (I use a copy of the example inventory which defines external_dns.dns_client), nslookup moves to the next server. Because the last nameserver is external, it does not know management1 (obviously).
Correct nslookup command:
[root@login1 ~]# nslookup -norecurse management1
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Name:   management1.tumulus.local
Address: <IP_ADDRESS>

It is still weird because nslookup(1) states:

[no]recurse
Tell the name server to query other servers if it does not have the information.

The nameserver <IP_ADDRESS> has the information since it is able to provide the correct answer when disabling recurse, so it should not try to query other servers?!? Anyway, I believe this is an issue with nslookup, not with BlueBanquise.
Otherwise, use dig:
[root@login1 ~]# dig +short +search management1
<IP_ADDRESS>


Fix non-fixed types serialization

@slowli PR is ready for review. Can you please check it again.

Coverage increased (+0.7%) to 90.203% when pulling fc01b00c2e61a90f3378108b4311fddbcbdc2384 on boguslavsky:fix-types-serialization into a9034fdbf8b4ce89ea48d4201d1b2bf6a05fba6d on exonum:master.