Error "The field ... is not visible"

Hello,
I got these errors on Eclipse Oxygen.3a due fields are private:
Description	Resource	Path	Location	Type
The field Author.books is not visible	TestCriteriaFunction.java	/CriteriaStandardFunction/src/test/java/org/thoughts/on/java/model	line 45	Java Problem
The field Author.firstName is not visible	TestCriteriaConstructor.java	/CriteriaConstructor/src/test/java/org/thoughts/on/java/model	line 44	Java Problem
The field Author.firstName is not visible	TestCriteriaQuery.java	/CriteriaQuery/src/test/java/org/thoughts/on/java/model	line 53	Java Problem
The field Author.firstName is not visible	TestCriteriaTuples.java	/CriteriaTuples/src/test/java/org/thoughts/on/java/model	line 45	Java Problem
The field Author.id is not visible	TestCriteriaFunction.java	/CriteriaStandardFunction/src/test/java/org/thoughts/on/java/model	line 46	Java Problem
The field Author.lastName is not visible	TestCriteriaConstructor.java	/CriteriaConstructor/src/test/java/org/thoughts/on/java/model	line 44	Java Problem
The field Author.lastName is not visible	TestCriteriaQuery.java	/CriteriaQuery/src/test/java/org/thoughts/on/java/model	line 54	Java Problem
The field Author.lastName is not visible	TestCriteriaTuples.java	/CriteriaTuples/src/test/java/org/thoughts/on/java/model	line 46	Java Problem
The field Book.authors is not visible	TestCriteriaQuery.java	/CriteriaQuery/src/test/java/org/thoughts/on/java/model	line 47	Java Problem
The field Book.id is not visible	TestQueryPagination.java	/CriteriaQueryPagination/src/test/java/org/thoughts/on/java/model	line 45	Java Problem
The field Book.id is not visible	TestQueryPagination.java	/CriteriaQueryPagination/src/test/java/org/thoughts/on/java/model	line 70	Java Problem
The field Book.isbn is not visible	TestNaturalId.java	/HibernateNaturalId/src/test/java/org/thoughts/on/java/model	line 39	Java Problem
The field Book.price is not visible	TestCriteriaConstructor.java	/CriteriaCustomFunction/src/test/java/org/thoughts/on/java/model	line 48	Java Problem
The field Book.price is not visible	TestCriteriaUpdate.java	/CriteriaUpdate/src/test/java/org/thoughts/on/java/model	line 46	Java Problem
The field Book.price is not visible	TestCriteriaUpdate.java	/CriteriaUpdate/src/test/java/org/thoughts/on/java/model	line 46	Java Problem
The field Book.publishingDate is not visible	TestMetamodel.java	/JPAMetamodel/src/test/java/org/thoughts/on/java/model	line 44	Java Problem
The field Book.title is not visible	TestMetamodel.java	/JPAMetamodel/src/test/java/org/thoughts/on/java/model	line 44	Java Problem

These errors ocurred after I renamed "Author_" and "Book_" to "Author" and "Book".
"Author_" and "Book_" are jpa metamodel objects.


Pretraining Wav2Vec2 with 1 GPU faster than 8 GPU

Hi,
I'm pretraining Wav2Vec2 on the LibriSpeech train-other with 8 V100 GPU
Here is the command I used
fairseq-hydra-train task.data=data_manifest_librispeech  distributed_training.distributed_world_size=8 +optimization.update_freq='[8]' --config-dir fairseq/examples/wav2vec/config/pretraining/     --config-name wav2vec2_base_librispeech
It took 1 hour for each 200 num_updates, and for reaching 400k updates, it would take more than 80 days.
I estimated it should take around 10 days to complete 400k updates, am I right? Anybody facing the same issue?
for more info, when Im pretraining using only 1 GPU on just 1000 samples from LibriSpeech, it takes 30 seconds for 1 epoch. However, when I use 8 GPU, it takes ~70 second for 1 epoch.
Many thanks !!!

solved. for those who's facing the same issue:
https://github.com/facebookresearch/fairseq/issues/3342


[MNOE-155] Staff invite workflow

Same as #182 but merging in 3.2 branch

Closing as this is backporting #182 in the 3.2 branch which is no longer supported


Regressor architecture

Dear authors,
in your paper, you describe the regressor $g(\cdot): \mathbb{R}^{N} \rightarrow [-1, 1]$ architecture as composed of three fully connected layers (multi-layer perceptron). See the images below for reference.

However, in this repository, the regressor is implemented using convolutions with kernel size 1.
https://github.com/nhshin-mcl/MWR/blob/d070db454a6e7ae93426a9f220464f39f9187445/code/Network.py#L18-L27
https://github.com/nhshin-mcl/MWR/blob/d070db454a6e7ae93426a9f220464f39f9187445/code/Network.py#L48
Fully connected layers are usually implemented using a linear layer. Do you perform some slicing/viewing of the tensors, which makes the implementation equivalent to a linear layer? Or do you use convolutions here by mistake? Can you please elaborate on this?
Jakub

I suppose that the input of the Regressor is of shape [B, 1536, 1, 1], where B is the mini-batch size and the spatial dimensions are 1, 1. Is this correct?


Cloudbursting to other OpenNebula instance

Author Name: Carlos Martín (Carlos Martín)
Original Redmine Issue: 3406, https://dev.opennebula.org/issues/3406
Original Date: 2014-12-05

Requested during the OpenNebulaConf.
Just like we have cloudbursting drivers for ec2, develop a new set to interact with a remote ONE installation.

available in 5.8: http://docs.opennebula.org/5.8/advanced_components/cloud_bursting/oneg.html


controller-runtime use old version, need upgrade

Enhancement
sigs.k8s.io/controller-runtime => sigs.k8s.io/controller-runtime v0.10.3
controller-runtime API has changed

@shaofan-hs can we upgrade controller-runtime for all kusionstack/operating related projects?

since kusionstack/operating uses controller-runtime v0.10.3 to suit kubernetes 1.22, we won't upgrade controller-runtime directly. Alternatively, we created branch cr-v0.15.0+ & cr-v0.18.0+ for controller-runtime v0.15.0+ & v0.18.0+. BTW, multicluter options disabled temporarily in these 2 branches since kusionstack.io/kube-utils/multicluster adopted controller-runtime v0.10.3 too.


Updating list of contributors

Current coverage is 99.40% (diff: 100%)

Merging #254 into master will not change coverage

@@             master       #254   diff @@
==========================================
  Files            23         23
  Lines          1693       1693
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1683       1683
  Misses           10         10
  Partials          0          0

Powered by Codecov. Last update d5addce...bae0eb8


Avoid constant leader re-elections under heavy load

To avoid constant leader re-elections under heavy workload it's convenient to disable the TTL of the lease leader. This is a temporal patch that will set a high value to the TTL ONLY when using gRPC.
As a long term solution, we should add a flag to enable/disable the usage of TTL for the keys of the leases.
ping @teemow

Having a flag where you disable the TTL in a testing environment is definitely a better idea imo. But I need a little bit more information here to understand why the TTL isn't important within the grpc engine.
There is a lease in etcd that is removed after the TTL. So eg if the fleet leader isn't able to operate or has connectivity issues with etcd the lease is removed and a new leader with elected. Sounds like a good idea in a production setup. Is this still the case? If a leader is elected how do the other engines determine if the leader is still operating? Is it a timeout in a connection to the leader? Or is it a watch on the leader lease in etcd?
The time of the reconciliation loop has always been the bottleneck especially under heavy load. Most importantly if X units cannot be handled in time Y on a single machine it doesn't make sense to move the leadership since none of the machines will be able to handle this. How can we distinguish between reconciliation loop taking longer but operating and reconciliation loop being not operative any more? Eg each unit state that has been parsed could add time in the reconciliation loop. But this doesn't solve the problem with the local setup under heavy load. There the reconciliation loop is not only taking longer but also being slow.
In the end a flag is probably the simplest solution.

@teemow. I'd code the flag.

There is a lease in etcd that is removed after the TTL. So eg if the fleet leader isn't able to operate or has connectivity issues with etcd the lease is removed and a new leader with elected. Sounds like a good idea in a production setup. Is this still the case? If a leader is elected how do the other engines determine if the leader is still operating? Is it a timeout in a connection to the leader? Or is it a watch on the leader lease in etcd?

Is this still the case?

No if you use gRPC. A master change should be triggered only if the master isn't available. We now use etcd to only persist a key that tells us who is the current leader. In the old implementation, it was used to change the leader under supposed communication problems, or a leader too busy. With gRPC, the constant changes of a leader can cause undesired states cause the change has an impact in the agents. There isn't a hot-plug change from a leader to another as before.
Therefore, with gRPC, we should change the leader whenever it is not available or crashes.
Having the leaseTTL can cause period of deny of service due to frequent leader changes, e.g. when the leader is busy. The impact of this grows under heavy pressure on the gRPC leader or whenever etcd is slow.
Conclusion: Therefore, with gRPC, we should change the leader whenever it is not available or crashes.
If the leader crashes the other agents try to connect for a while. Otherwise any engine is elected as new leader, so consequently the agents are aware of this change and start to talk to the new leader. Yes, a watch.

There won't be much work on this direction so I will close this PR. Please open it if you feel like taking over.


Export RefImpl

What problem does this feature solve?
I would like to extend RefImpl to create a Ref which can hold more state.
Currently I would have to use customRef because I can't create a valid Ref object by myself without knowing RefSymbol, which is not exported either.
// Use the provided getters/setters
class MyRef<T> extends RefImpl<T>{
    get value(){
       //... do stuff
       return super.value;
    }
    //...
}

// Override the tracking
class MyRef2<T> extends RefImpl<T>{
    get value(){
       track(toRaw(this), "get" /* GET */, 'value');
       //... do stuff
       return this._value;
    }
    //...
}

What does the proposed API look like?
Just export the class and maybe look into setting properties as private or protected.

I just found out I can use track and trigger to get everything I need to create a custom reactive class.

For now, RefImpl is an implementation detail, and this implementation can change in future. In fact, refs weren't implemented as class instances until RC.7.
It seems like it's not being leaked to public API intentionally.

Closing since track and trigger solve the original problem

This is intentional. The only reason class being used internally is performance. It's not meant to be extended. Use customRef.

The best solution I found is to create a customRef<void> in the constructor and store the given track and trigger callbacks as instance properties, so I can use them whenever I want.
Storing the returned Ref<void> as a property gives me the ability to do watch(myinstance.ref).


Allow git ingester to work on Pull Requests as well

Summary
This is useful for writing simple rules that check out the git repo for
a pull request.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 55.353% (-0.006%) from 55.359%
when pulling c245322aab663b82d6bc66dfc388a7232d6bab17 on JAORMX:pr-git
into 4e29d370e71095969d589fd81a839d1ac80fb2dd on mindersec:main.


feat: introduce into_stream method

Backport 3a5c085

Codecov Report

Merging #14 (7cd8c18) into fdb-0.2.x (4a0b6c6) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           fdb-0.2.x      #14      +/-   ##
=============================================
+ Coverage      89.43%   89.44%   +0.01%
=============================================
  Files             17       17
  Lines           7655     7666      +11
=============================================
+ Hits            6846     6857      +11
  Misses           809      809

Impacted Files
Coverage Δ

fdb/src/range.rs
67.08% <100.00%> (+1.16%)
: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 4a0b6c6...7cd8c18. Read the comment docs.


Added additional responsive menu close logic

This commit adds JavaScript to close the responsive menu when a user clicks/taps outside of the open menu.

Is there a way to write the logic differently? I fear that if someone adds a section to the site using a  or some other sort of element then this feature won't work. Maybe something that if anything is clicked other than the menu itself?

How about now? This will grab all first level children inside body (because we don't need to worry about elements beyond that) and it will exclude the nav tag at the top. This way, if a user taps the white space in the nav, it wont close the menu but anything outside of the menu will close it.

Awesome. I like it. These are some great improvements to the default functionality of the Bootstrap mobile nav.
Thanks for the request and the revision!


database/sql: if there is a panic during Stmt execution, we cannot release resources

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

$ go version
go version go1.17.6 linux/amd64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/devalio/.cache/go-build"
GOENV="/home/devalio/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/devalio/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/devalio/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go-1.17"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go-1.17/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.6"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4248269622=/tmp/go-build -gno-record-gcc-switches"

What did you do?

	tx, err := db.BeginTx(ctx, nil)
	if err != nil {
		return err
	}
	defer tx.Commit()

	stmt, err := tx.Prepare(...)
	if err != nil {
		return err
	}
	defer stmt.Close()

	_, err = stmt.ExecContext(ctx, ...)  // the error occurs if there is a panic in the process
	if err != nil {
		return err
	}

This is the kind of algorithm that leads to a complete hang-up:

open the transaction
Prepare statement
Execute prepared statement
If there is a panic inside the execution - resources will not be fully released and closing the statement or transaction will cause the goroutine to hang

What did you expect to see?
I expect the pending functions to perform correctly and the goroutine to continue to panic
I do not expect the whole routine to hang up permanently
What did you see instead?
resources will not be fully released and closing the statement or transaction will cause the goroutine to hang

I know what's causing it and I'm dealing with it now

take a look at this code from database/sql
if the execution of the resultFromStatement function panics, then releaseConn will never be executed
func (s *Stmt) ExecContext(ctx context.Context, args ...interface{}) (Result, error) {
	s.closemu.RLock()
	defer s.closemu.RUnlock()

	var res Result
	strategy := cachedOrNewConn
	for i := 0; i < maxBadConnRetries+1; i++ {
		if i == maxBadConnRetries {
			strategy = alwaysNewConn
		}
		dc, releaseConn, ds, err := s.connStmt(ctx, strategy)
		if err != nil {
			if err == driver.ErrBadConn {
				continue
			}
			return nil, err
		}

		res, err = resultFromStatement(ctx, dc.ci, ds, args...)     // PANIC HERE!
		releaseConn(err)      // NEVER EXECUTED
		if err != driver.ErrBadConn {
			return res, err
		}
	}
	return nil, driver.ErrBadConn
}

This can happen if we implement a Valuer interface where panic occurs
I've seen libraries that use the reflect package inaccurately before and create a panic at this point

Yes, Valuer must not panic:
type Valuer interface {
	// Value returns a driver Value.
	// Value must not panic.
	Value() (Value, error)
}

To date I've not wanted to fix this.
I'll see if I can look at your CL to see how invasive this change is.

Yes, Valuer must not panic

it's not just about Valuer any panic in this thread will cause the gorutine to freeze
I recently sent a fix to this library: https://github.com/ClickHouse/clickhouse-go
it was panic that caused freezing and Valuer was not used there

Fair enough. I've heard you. I'll see what we can do.

I tried to reproduce in the test the call stack that leads to the error. To do this I had to implement a couple of driver interfaces. This shows that we are not protected against applications freezing if the driver that can panic when executing Exec or Query.
When goroutine is frozen, we can't complete the test, so I added a 15-second timeout
In any case, I corrected the tests today to make the problem I'm solving even clearer
https://golang.org/cl/382214


test-230414-4

this is a rubbish change to the dsp basicmath.h

The backport to v2.7-branch failed:
The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.7-branch v2.7-branch
# Navigate to the new working tree
cd .worktrees/backport-v2.7-branch
# Create a new branch
git switch --create backport-227-to-v2.7-branch
# Cherry-pick the merged commits of this pull request and resolve the conflicts
git cherry-pick -x d1eca25a03cb919c7b656734eed5ace35858030c
# Push it to GitHub
git push --set-upstream origin backport-227-to-v2.7-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.7-branch

Then, create a pull request where the base branch is v2.7-branch and the compare/head branch is backport-227-to-v2.7-branch.


Error while building

When I tried to build RustyBGP on fresh Linux installation with Docker, I got this:
# docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder cargo build --release
...
Compiling tonic-build v0.5.2
Compiling hyper v0.14.25
error[E0599]: no method named `send_replace` found for struct `Arc<tokio::sync::watch::Sender<Option>>` in the current scope
--> /home/rust/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.25/src/client/connect/mod.rs:225:17
|
225 |         self.tx.send_replace(Some(connected.clone()));
|                 ^^^^^^^^^^^^ method not found in `Arc<tokio::sync::watch::Sender<Option>>`
For more information about this error, try `rustc --explain E0599`.
error: could not compile `hyper` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed
Is there something wrong with my setup?
I have Docker version 20.10.21, build 20.10.21-0ubuntu1~22.04.2

Getting the same error with rust:1.68-bullseye docker image basis.

Thanks for the report, fixed.


Delay

I use the Reolink E1 Outdoor with the sub RTSP channel. The bitrate is 256kbit/s. When I run the stream on one device for a long time, there is a delay of up to 11 seconds. What is the reason for this?

This is known problems with some Reolink cameras.
Check go2rtc 1.3.0. If the problem still exists - it cannot be fixed with these cameras.
As I know - Reolink cameras has awful RTSP protocol support.


implements left outer join support to NL operation

@dobe pls review

used wrong branch to merge in, opened new PR https://github.com/crate/crate/pull/3940


How do I add additional features with BERT?[Question]

I want to use a pertained model with additional features for NER task. Lets say I have a sequence of pos tags I want to send in as feature to make prediction.

In Kashgari V1, we have a feature called stacked embedding and numeric embedding. Please try it out. This is not implemented on Kashgari V2 yet.
https://kashgari.readthedocs.io/en/v1.1.5/advance-use/handle-numeric-features.html

Thanks!


[BUG] from_pytest_fixture doesn't seem to work with parametrized fixtures

When using schemathesis.from_pytest_fixture(), if that fixture is parametrized with @pytest.fixture(params=...), pytest produces an error like this:
tests/integration/test_graphql_schema.py::test_graphql_schema FAILED                                                                                [100%]

============================================================================================== FAILURES ==============================================================================================
________________________________________________________________________________________ test_graphql_schema _________________________________________________________________________________________
'Function' object has no attribute 'callspec'

During handling of the above exception, another exception occurred:
The requested fixture has no parameter defined for test:
    tests/integration/test_graphql_schema.py::test_graphql_schema

Requested fixture 'graphql_schema_fixture' defined in:
tests/integration/test_graphql_schema.py:8

Requested here:
./venv/lib/python3.8/site-packages/schemathesis/lazy.py:189

To Reproduce
Here's an example of what the type of tests I'm trying to run:
import pytest
import schemathesis

API_VERSIONS = ["v1", "v2", "v3"]

@pytest.fixture(params=API_VERSIONS)
def graphql_schema_fixture(app):
    endpoint = f"/{request.param}/graphql"
    return schemathesis.graphql.from_wsgi(endpoint, app)

graphql_schema = schemathesis.from_pytest_fixture("graphql_schema_fixture")

@graphql_schema.parametrize()
def test_graphql_schema(case):
    response = case.call_wsgi()
    case.validate_response(response)

Expected behavior
When generating a schema object from a parametrized fixture, decorating a test function with that schema object would result in multiple iterations of the test function, for each schema produced by the parametrized fixture.
Environment (please complete the following information):

OS: Linux
Python version: 3.8.5
Schemathesis version: 3.6.0
Spec version: Open API 3.0.2
Pytest version: 6.2.3

Hi @dkbarn !
Thank you for a very detailed report, I will take a look at it in the next few days.

Fixed in 3.6.1

Thanks for quick fix! Confirmed that it's now working as expected in 3.6.1.


Added Loan_status_prediction.ipynb

Added loan_status_prediction.ipynb
Closes: #10

@SURYACODER please Create a folder with the loan prediction and add your file there!!

Create a new folder and add the file in that folder

Create a new PR


Understanding different times associated with simulation?

Hi, I've been following the examples in tutorial.ipynb, and I've noticed that there are various different, but important notions of time in a given simulation.
I'm most familiar with the mathematical timestep, dt, that is used to integrate Newton's laws of motions (a smaller timestep typically means a more accurate simulation). But then there is also 'clock time' (i.e., how long it takes for the computer to run the simulation). And rendering time... And simulation time.
Can anyone explain these subtle nuances in a concise clear way? I've looked at countless articles online, but the distinctions are not clear to me? I need to know as I'm struggling to understand how the example on Contacts in tutorial.ipynb presents a simulation that is "1/4x real time"? (This is the relevant code below):
# simulate and render
for i in range(n_frames):
  while data.time < i/120.0: #1/4x real time
    mujoco.mj_step(model, data)
  renderer.update_scene(data, "track", options)
  frame = renderer.render()
  frames.append(frame)

Regarding the specific question, video is played back at 30hz by default by the mediapy utility used in the tutorial. By rendering frames every 1/120 of a second, playback will be at 1/4x real time.
Any other specific questions?


Add video tests

Video tests

Checking that camera is available only in business-vm
Checking that video clip can be recorded, and some basic checks for video file is done

If I run Record Video With Camera test with camera lid on the test fails with message
'2073600 < (2073601-1)' should be true.
in the message field which means that all pixels of the captured image have same color. Could the fail message be more clear? For example: "Capturing video succeeded but real content was not detected. (Check the camera lid.)"
Also if the video file is empty the test fails with message
'0 > 0' should be true.
Could this also be more informative?


fix: If the latest barcode is removed from the carousel, it should be scannable again

If I scan a barcode, then remove it, it should be scannable again.
Presently, nothing happens.
Part of https://github.com/openfoodfacts/smooth-app/issues/2741

For tests failing, here is the story: https://github.com/openfoodfacts/smooth-app/issues/2747

Updated this PR tests working again

thanks @g123k
merging and deploying to internal


Form/Questionnaire View UI updates

Problem
Current Questionnaire view is the template, we want it to be our app designs.
Solution
Update the current UI view to display our designs

only UI for right now
take out any unnecessary information

@emmyxth + @BKrajancich
Additional context
No response
Code of Conduct

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

@jenlmoore is this supposed to be Onboarding Flow* updates? The Form/Questionnaire is in a decent state for this Thursday's deliverables (I think)

@BKrajancich Sorry! You're completely right, thanks for catching!


Cannot download available dataset

I am trying to run
kaggle datasets download -d madhab/jobposts
However it returns
404 - Not Found
I wonder why it so, because the dataset is available via the webpage https://www.kaggle.com/madhab/jobposts/
How can I download the dataset via API?

Found the bug, it's a server side issue with how we resolve the zip file name to the dataset.  Will have a fix out by Monday.
Sorry about that - thanks for the report!

Should be fixed in 1.4.4.  There was some wonkiness here though - please let me know if you continue to run into problems.

Hi,
I am using kaggle version : Kaggle API <IP_ADDRESS>
still getting not found issue for available dataset.
command : !kaggle competitions download -c tgs-salt-identification-challenge
result : 404 - Not Found

@manishprasadthapliyal have you accepted the competition's rules and are you able to download the dataset from the web UI?  Right now the error messages are not good around that (something to improve)

Kaggle won't allow to download Carvana and tag salt, and gave me 500 -internal server error, however it could download the zillow/zecon

Hey - i have a similar issue. I am using 1.5.2 and get an error 404 for everything (i have signed up to the Commercial Aviation Fatalities competition, and am able to download the files from the GUI (just want to avoid having to then shift them to AWS) Thanks!


CP-ITI-1100: Need a way to search creation date/time.

CP-ITI-1100: Need a way to find DocumentReference that hold attachments with a specified creation date/time. For the time during FHIR R4, we have guided the implementer to use the .date element to hold the created date/time. This solution requires careful duplication of the date value in both date and the attachment. This duplication enables use of the elements and query against date. The .date element in FHIR is defined as when the DocumentReference was created, which might be later than the document creation date/time. GF#19823 requested query parameter for the attachment created date/time for R5
R5 has a "creation" parameter that searches DocumentReference.content.attachment.creation
So this open-issue will be resolved by R5.

we could define a search parameter in the IG for this use in R4.

Add the Search Parameter


[Bug][Audit] SQL file executed error for ClickHouse in Audit

What happened
Execute the apache_inlong_audit_clickhouse.sql error:
5b142b25d12d :) SET NAMES utf8mb4;

Syntax error: failed at position 11 ('utf8mb4'):

SET NAMES utf8mb4;

Expected one of: token, Dot, Equals

5b142b25d12d :) SET FOREIGN_KEY_CHECKS = 0;

SET FOREIGN_KEY_CHECKS = 0

Query id: a79b41c4-f65e-44cf-a76d-bd49de02c293

0 rows in set. Elapsed: 0.001 sec.

Received exception from server (version 22.1.3):
Code: 115. DB::Exception: Received from localhost:9000. DB::Exception: Unknown setting FOREIGN_KEY_CHECKS. (UNKNOWN_SETTING)

5b142b25d12d :) SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

Syntax error: failed at position 16 ('"NO_AUTO_VALUE_ON_ZERO"'):

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

Expected one of: TRUE, FALSE, literal, NULL, number, Bool, true, false, string literal

5b142b25d12d :) SET time_zone = "+00:00";

Syntax error: failed at position 17 ('"+00:00"'):

SET time_zone = "+00:00";

Expected one of: TRUE, FALSE, literal, NULL, number, Bool, true, false, string literal

What you expected to happen
Can execute successfully.
How to reproduce
Just execute the apache_inlong_audit_clickhouse.sql.
Environment
No response
InLong version
master
InLong Component
InLong Audit
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

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

I want to fix this issue.


Change line cursor behaviour to be more intuitive

In discussions following the recent UX testing, it was decided to make the following changes to the behaviour of the line cursor:

[ ] The cursor should not visit stacks nodes.
[ ] The cursor should skip value connections (input/output) if there is a connected block.
[ ] The cursor should be able to visit all fields, including whole-block fields on simple reporter blocks.
[ ] When navigating between top-level stacks (or rather the constituent blocks thereof, as we will no longer visit the stack nodes), it should be possible to visit all top-level stack, and they should be visited in the same sorted order that is used for code generation.

The following change was discussed but the result of discussions seems to be in dispute (@cpcallen believes it was generally agreed, but @rachel-fenichel thinks it was not):

[ ] The cursor should skip stack connections (next/previous) if there is a connected block.

Additionally, I (@cpcallen) propose that the workspace cursor behaviour be modified to bring it in line with proposed changes to the block movement mechanism in #TBD, principally:

[ ] The cursor should not visit the workspace (i.e. arbitrary xy coordinates), unless a modifier key (probably shift) was held down in conjunction with one of the arrow keys, in which case it will move to the nearest workspace gridpoint location in the specified direction (within a ±45° arc).
[ ] When the cursor is on the workspace, and an arrow key is pressed, the cursor should move to the nearest block in the given direction (within a ±45° arc).

Revised above description to allow the cursor to visit connections that do not have a connected block.  That's kind of necessary if we want to make it reasonably easy to place new blocks using the marker workflow (see #102).


catalog backend: deduplicate locations

Currently, you are permitted to add duplicate locations. Make it so that if you add a duplicate, you just get back the preexisting one in your response.

taking this one


Update to Kubernetes v1.27

Update to Kubernetes v1.27
Update vulnerable dependencies

:+1:

:+1:

:+1:

merged and released as https://github.com/szuecs/kube-static-egress-controller/releases/tag/v0.2.14


meli: alpha-0.6.2 -> alpha-0.7.1

Motivation for this change
Upgrade to alpha-0.7.1 thus fixing build error seen in #139171.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 139191 at 085705dc run on aarch64-linux 1

1 package failed to build:

meli

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


notification_icon support

For Android I have a followed this guide (https://developer.android.com/studio/write/create-app-icons#create-notification) for generating a notification_icon.
In my case it generate the following assets:

However, running
npx @capacitor/assets generate --iconBackgroundColor '#eeeeee' \
  --iconBackgroundColorDark '#222222' --splashBackgroundColor '#eeeeee' \
  --splashBackgroundColorDark '#111111'

will remove all of the generated notification_icon icons.
Is it possible that we can preserve the notification_icon icons?

oeps, its Friday... It was my own fault.  Case closed!


Roll engine 5646e86a6f44..06377b10763b (9 commits)

https://github.com/flutter/engine/compare/5646e86a6f44...06377b10763b
git log 5646e86a6f44..06377b10763b --no-merges --oneline
06377b107 Document not passing empty-strings into Locale (flutter/engine#6818)
bdd5640f3 Roll src/third_party/skia 1c3f17fffa79..c7a34cae21d2 (2 commits) (flutter/engine#6821)
a5bc33546 Revert "Roll Dart version to f9ebf2129732fd2b606286fdf58e500384b8a0bc (#6812)" (flutter/engine#6820)
961930688 Roll src/third_party/skia 95af4726bf91..1c3f17fffa79 (1 commits) (flutter/engine#6819)
4dbdf94aa Ensure that the EGL rendering context is bound to the GPU thread in Rasterizer::MakeRasterSnapshot (flutter/engine#6816)
799ce8742 fix log (flutter/engine#6817)
3e4c8cca7 Roll src/third_party/skia ef4709b7850d..95af4726bf91 (22 commits) (flutter/engine#6815)
2584816d7 Roll Dart version to f9ebf2129732fd2b606286fdf58e500384b8a0bc (flutter/engine#6812)
9669aeb95 Roll src/third_party/skia 06a477c3300d..ef4709b7850d (31 commits) (flutter/engine#6811)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6223948184289280

Commit queue failed; closing this roll.


Feature request: add ability to query pages structure

Feature request
Is your feature request related to a problem? Please describe.
Given a /pages folder. I'd like to be able to be able to

build an overview page that lists and links to the other pages without having to define them statically
build navigation components, like a sidebar, that is dynamically populated with whatever is in my project
build sitemaps automatically based on the pages I have in my project
build rss feed based on the pages I have in my project

Describe the solution you'd like
a way to query the project structure at runtime. And a way to add metadata to the result from within the individual pages. For instance: there could be an endpoint like
// GET /_next/structure?filter=/posts/*&fields=path,meta.title
{
  "pages": [
    { "path": "/posts/some-post", "meta": { "title": "This is some post" } },
    { "path": "/posts/some-other-post", "meta": { "title": "This is some other post" } }
  ]
}

for the project
// /posts/some-post.mdx
export const meta = {
  title: This is some post
}

# This is some post

// /posts/some-other-post.jsx
export const meta = {
  title: This is some other post
}

export default function Page () {
  return
This is some other post

}

Or it could be a graphql endpoint that allows for querying a bunch of project and structure related data at runtime.
getInitialProps can then fetch this endpoint so the page can use it to build its UI, like:
export default class extends React.Component {
  static async getInitialProps ({ req }) {
    return (await fetch(basePath(req) + '/_next/structure')).json();
  }

  render () {
    return (

        {this.props.pages.map(({ path, meta }) => (
          <Link href={path}>{meta.title}</Link>
        ))}

    );
  }
}

It could also be used to fetch serverside to generate a sitemap on the fly.
Having it like this allows me to add/remove/change any page while the navigation of my site gets updated automatically.
Describe alternatives you've considered
I started by trying to generate a json file in the /static folder with this information at build time. But there's a few challenges with this:

in order to retrieve the meta object, the components need to be compiled and imported with the next configuration of the project. So in order to dothis, one will need to recreate the webpack configuration already in next
one would also need to recreate the way next discovers and defines what are pages and their path. (index.js resolution etc...)

The problems lie mainly in generating the data. a static file would be less powerful than a graphql, but still useful.
Additional context
I think it's also related to point 3. of this ticket https://github.com/mdx-js/mdx/issues/126

I am not sure if this helps but you could use babel-macros to gather the information you‘ll need at build time.
Here is an example of babel-macros and next.js: https://github.com/zeit/next.js/tree/canary/examples/with-babel-macros
Just use node-glob and babel-register to detect pages and extract the infos you need.


3.0.5 rc master->slave replication does not work

I have started localhost:6379 and localhost:6380 as a slave.
On the start the slave node read some f keys from the master and not sync anymore.
Then I run 2.8 as a slave of the same mater. It works perfectly.
Is that issue  or I need to configure anything additionally for 3.0.5 rc?

Hi @win32nipuh,
can you please provide the configuration files and the log files to help identify the problem?
Thank you.

There are 2 log files from 2.8 slave and 3.0.5 slave and config files for master and 3.0.5 slave
salve_log.txt
slave_log_2_8.txt

redis_pwd_master.conf.txt
redis_pwd_slave.conf.txt

@win32nipuh
it looks like a bug in the 3.0.5 when the password is required, I'll investigate further and I'll let you know.
Thank you.

ok, thnx.
Btw, probably it can help.
I have a SQLCLR procedure which connects to Redis (with password) and writes some data.
I use master->slave replication
It works with 2.8 ok.
Now I am testing it with 3.0.5 rc master->3.0.5 slave.
I have detected that sometimes connection can be broken by server

Thank you, will test.

@win32nipuh
the RC2 release is available with e fix for this issue.
Feel free to reopen the issue if needed.
Thank you.

Hi,
In my environment it works:
master->slave->slave
Thank you.

@win32nipuh
thank you for the feedback :)


suggestion for new feature

Description
Find a better name to detect mobile?  desktop?
What do you expect
It's better to detect mobile? desktop? with the Browser::Base subclass, on the upper layer, just return matched class result
Software:

Rails version: [Add rails version here]
Browser gem version: [Add browser gem version here]

Example
module Browser
  class Some < Base
    def mobile?
      true
    end

    def desktop?
      false
    end

    def match?
      ua.match?(/some/)
    end
  end
end

Browser.new('some ua').mobile? #=> true
Browser.new('some ua').desktop? #=> false

Report
Just a suggestion? hope you like it.

On previous versions of this gem, there were too many methods on Browser instance; hence the extraction to specific objects like platform and device.
I think we can maybe have a new file that adds some aliases to methods like mobile? to Browser class? Then the developer can, optionally, load it with something like require "browser/alias".
Again, I'm not sure I'd like to add more methods to the main class.

Yes, I think it's a good idea


Add progression process to draw callback

Currently the draw callback recieves both the context and the time since the start of the recording. However, in a recording of a fixed amount of frames, I would like to know how fare I am through the animation relative. Maybe an additionargument t that returns the progress between 0 and 1. Alternativly a way to query that.

Fixed in 3f890c0cb8bb386434581d48ebf34b98eb2b3719


Change Event::PostCb from std::function to absl::AnyInvocable

Commit Message: Change Event::PostCb from std::function to absl::AnyInvocable
Additional Description: The intent here is to match the type to the expected behavior (post-callbacks are called once, so being once-only invocable is valid), which makes it so the lambda can capture move-only types, such that horrors like this become unnecessary. (See change to cache_filter.cc in this PR for example cleanup.)
This also removes the potential memory leak, wherein if a lambda of that form (capturing a bare pointer) is never called, the pointer doesn't ever get re-wrapped in a smart pointer and therefore leaks. Using AnyInvocable allows us to capture the smart pointer, so it gets destroyed when the lambda is destroyed, whether called or not.
It turns out there are many many instances of PostCb being abused as shorthand for "a callback" rather than "a callback for posts" as its name suggests, and also many instances of actual post callbacks not being typed as PostCb, so this PR doubles as a cleanup of all that.
There are also a number of move-semantics-related changes, mostly in mocks, required to make this change possible.
Risk Level: ??? - should be effectively a no-op cleanup, but it touches a lot.
Testing: covered by existing tests due to being effectively a no-op cleanup.
Docs Changes: n/a, though I may make a small followon update to the async http filter guidance I just wrote.
Release Notes: added
Platform Specific Features: n/a

/retest

/retest

Seems like having many auto-assigned reviewers is counterproductive; assigning mattklein123 because it's a sweeping low-level change, I don't know who else is well suited to look at that kind of thing.

Argh. There was me thinking "well this inline editor was convenient for fixing a merge conflict, I can use it to fix this new yaml formatting requirement too", but then editing inline not for the merge conflict didn't include the DCO-required signature, so now I had to do a forced push to resolve that instead, so it made things worse not better.

/retest


SEO component isn't working

Error:

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of SEO.

Change the returned JSX to just <></> and the site will load. I'm not sure yet what it is.

The new version of react-helmet was the problem. Downgrading to v5 fixed it.


[release-ocm-2.10] MGMT-18313: Replace golang base image as it is based on Centos Linux 7

/cc @adriengentil @eifrach @pastequo

/uncc @oourfali

/lgtm


⚠ AGEG website (prod) has degraded performance

In 2f8979c, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 9042 ms

Resolved: AGEG website (prod) performance has improved in 3d40ed6.


Use of ly_verb_dbg and LY_LOG_DBG_GROUP without conditioning on NDEBUG

Hi
in the main.c of netopeer2-server the LY_LOG_DBG_GROUP flags are used without any conditioning on NDEBUG.
in libyang.h file the functions ly_verb_dbg and the enum type LY_LOG_DBG_GROUP are defined only if the symbol NDEBUG is not declared
#ifndef NDEBUG
/**

@typedef LY_LOG_DBG_GROUP
@brief Selected displayed debug message groups.
*/
typedef enum {
LY_LDGDICT = 0x01,  /< Dictionary additions and deletions. */
LY_LDGYANG = 0x02,  /< YANG parser messages. */
LY_LDGYIN = 0x04,   /< YIN parser messages. */
LY_LDGXPATH = 0x08, /< XPath parsing end evaluation. */
LY_LDGDIFF = 0x10   /*< Diff processing and creation. /
} LY_LOG_DBG_GROUP;
/
@brief Enable specific debugging messages (independent of log level).
@param[in] dbg_groups Bitfield of #LY_LOG_DBG_GROUP - enabled debug message groups.
*/
void ly_verb_dbg(int dbg_groups);
#endif

Hi,
should be fine now.
Regards,
Michal

Hi Michal
thanks a lot for your support?
I have noticed that you fixed the problem in the 'notifications' branch.
I'm using the 'devel' branch.
Do you advise to use the 'notifications' branch instead of the 'devel'
or has I to port the fix on the devel by myself?
regards
fabio
On 07/03/2017 08:55, michalvasko wrote:

Hi,
should be fine now.
Regards,
Michal
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CESNET/Netopeer2/issues/108#issuecomment-284648236,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFpJnZMQqjehaKZutRXZPhNMHs3u82aBks5rjQ1wgaJpZM4MSZSp.

Hi,
of course, sorry, my bad.
Michal

Thanks
fabio
On 07/03/2017 09:18, michalvasko wrote:

Hi,
of course, sorry, my bad.
Michal
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CESNET/Netopeer2/issues/108#issuecomment-284652641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFpJnYvFpkI5nD3CN-DZhLLI5_aiYNuRks5rjRLIgaJpZM4MSZSp.


🐛 PaneItemExpander is expanding when adding a pane into NavigationView

Describe the bug
When adding a pane into the NavigationView with a setState(), if a PaneItemExpander is open in the footerItems, it will close. When we remove a pane, the PaneItemExpander will open by itself if it was closed.
To Reproduce

I have made a reproducible project right here : https://github.com/AlexisL61/PaneItemExpander_bugreport
After starting the project with flutter run, press the filter icon on the bottom left part of the screen for opening it
Then press the + button in the bottom left part of the screen
The filter will close by itself
If you press the + button again, the filter will open by itself

Expected behavior
The PaneItemExpander should not open or close when adding or removing a pane
Additional context
Tested on Windows only for now?

Hmmm, interesting.
The pane item expanders work by index. They are saved to the page storage with their assigned index, so when their index changes, their state is likely to be lost :/

I see.
If I can be of any assistance on this issue, tell me


"Snap to Grid" isn't saved

I had saved my graph file with setting that grid snapping is enable, and today I opened the same file but I found the setting is disappeared.

thank you for this ticket,
the issue will be fixed for 0.5.2.


[Bug report] CI: trino-connector:test FAILED on Cron Integration Test 20240820

Version
main branch
Describe what's wrong
> Task :integration-test:test
Current project version: 0.7.0-incubating-SNAPSHOT
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.hadoop.security.authentication.util.KerberosUtil (file:/root/.gradle/caches/modules-2/files-2.1/org.apache.hadoop/hadoop-auth/2.10.2/29ab697d6b925ed3a52b782554d59e3312c94572/hadoop-auth-2.10.2.jar) to method sun.security.krb5.Config.getInstance()
WARNING: Please consider reporting this to the maintainers of org.apache.hadoop.security.authentication.util.KerberosUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

> Task :trino-connector:test FAILED

:trino-connector:test failure marker
  Error: Execution failed for task ':trino-connector:test':
      org.gradle.api.internal.exceptions.MarkedVerificationException: There were failing tests. See the report at: file:///actions-runner/_work/gravitino-test/gravitino-test/gravitino/build/reports/index.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.2/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
129 actionable tasks: 72 executed, 57 up-to-date
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':trino-connector:test'.
> There were failing tests. See the report at: file:///actions-runner/_work/gravitino-test/gravitino-test/gravitino/build/reports/index.html

* Try:
> Run with --scan to get full insights.

BUILD FAILED in 14m 8s

Error message and/or stacktrace
N/A
How to reproduce
Cron Github Action:
https://github.com/datastrato/gravitino-test/actions/runs/10477629581/job/29019254226
Additional context
No response

@diqiu50 Would you like to help trouble shooting this issue on cron CI ?


suggestion: add a "new page" command

It would be really useful to have a command to generate a post with a standardised filename and boilerplate frontmatter.
For example,
astropaper new post
which would create a file called contents/YYYY-MM-DD- with all the frontmatter fields provided, date and slug fields automatically pre-filled.

Thanks for this.
I'll try to implement command line blog post generation in the future releases.

@rwillmer
I've opened a PR for this feature. You can check it out and give feedback/suggestion if you want. You can also try it out in feat/cli-generate-post branch.

PR works fine. I need to tweak it slightly; for my purposes I always use filenames YYYY-MM-DD- so I'd ask for the slug first and then default the filename to that format. But that might well not suit everyone, so I can just tweak that locally if you prefer your format.
Thanks for doing this so fast.

Helo @rwillmer
Sorry for my late reply. What I'm thinking right now is that in the future I might make a NodeJS CLI for AstroPaper to generate posts, tags and other stuff.
So, at the moment, I'll leave my PR #14 without merging to the main branch. For those who want to generate blog posts via command line like you, they can clone feat/cli-generate-post branch.  I'll keep that branch in sync with my main branch so it will be update to date and has CLI post generation feature.
For now, I'll close this one. If you still have some issues, you can reopen this anytime. Thanks.


server: fix tests on linux

By the way, is it intentional that issues cannot be opened on this repository?

By the way, is it intentional that issues cannot be opened on this repository?

No, definitely not. Fixing that now.


Implement --unstable-presymbolicate

Adds --unstable-presymbolicate, which will output  .syms.json file alongside the regular profile output. If that file is present when the server is fired up (based on the profile name, i.e. foo.json -> foo.syms.json), it is parsed and the data is added to be used when symbolicating. If a library has presymbolicated info (by debugid), only that info is used. There's no attempt to fall back to on-disk etc.
This allows a capture to be entirely self-contained, so that no symbol servers or on-disk data are needed for looking at the profile, which is very useful for running in CI or other locations where publishing the debuginfo isn't necessarily useful otherwise.

Ok, implemented proper address/symbol info and properly implemented frames. Should have addressed all the review feedback here. I didn't make the GlobalLibIndex -> UsedLibraryHandle change, that can be a future thing


New options page to add domain regexes to a whitelist

I really appreciate this project and look forward to a new version that I can use on more websites more flexibly. I attempted to modify a few lines of code as below:

Refactor the options page by React, and support users to edit their own domain lists on which Codeium is allowed to complete code. The default list is the following 11 regular expressions, extracted from script.ts

https:\/\/colab.research\.google\.com\/.*
https:\/\/(.*\.)?stackblitz\.com\/.*
https:\/\/(.*\.)?deepnote\.com\/.*
https:\/\/(.*\.)?(databricks\.com|azuredatabricks\.net)\/.*
https:\/\/(.*\.)?quadratichq\.com\/.*
https?:\/\/(.*\.)?jsfiddle\.net(\/.*)?
https:\/\/(.*\.)?codepen\.io(\/.*)?
https:\/\/(.*\.)?codeshare\.io(\/.*)?
https:\/\/console\.paperspace\.com\/.*\/notebook\/.*
https?:\/\/www\.codewars\.com(\/.*)?
https:\/\/(.*\.)?github\.com(\/.*)?

Test the feature on some web pages with the online editor, e.g., leetcode.com, codepod.io, and some web apps I deployed on local env with URL starting by localhost. It works when I write a correct regex for them. And also in reverse, removing some default regexes above can disable the code completion of Codeium on those websites.
Though it extends the application scenarios for Codeium further, it may not work on many websites even if they apply Monaco or CodeMirror as their online editors (for example, online vs code/github.dev, codesandbox). The rules are too rough to support them well for now.

Though it extends the application scenarios for Codeium further, it may not work on many websites even if they apply Monaco or CodeMirror as their online editors (for example, online vs code/github.dev, codesandbox). The rules are too rough to support them well for now.

We have an internal issue tracking github.dev -- this would require a modification of our vscode extension to support the web environment.
I've previously looked at CodeSandbox. I think it doesn't work for a similar reason as described in https://github.com/Exafunction/codeium-chrome/issues/4#issuecomment-1519231767

@pqn
Thank you so much for reviewing this PR and valuable suggestions. I pushed some new commits to complete:

Change the font of domain inputs to "monospace"
Validate the domain inputs, add toast notification on success/error when clicking on the save button
Fix the duplicated injection issue

Can you take a look and give more feedback?

@pqn Thanks for your comment. I updated the code as you suggested. Now, the new UI looks like:

I'm uncertain whether it should be "allow list" or "allowed list" (since I'm not a native English speaker...)

Looks like the rebase or merge had some issue and the commits are showing up in the PR history.

Update: add the reset button and remove the exit button.

Thanks! 🎉


Google Login Error in Flutter mobile app

Bug report
Google Login Error in Flutter mobile app
I have tried to log in using google ..signIn(provider: Provider.google), but it doesn't help at all. Webview pop-up doesn't appear even you can get the URL in print() method.
To Reproduce
Steps to reproduce the behavior:

Setup google login as per your documentation
Add button action in the app to login (I tried on physical device and simulator)
No pop-up to show available accounts
If you try to print URL from Result, it shows a URL like this https://[YOUR_APP_ID].supabase.co/auth/v1/authorize?provider=google

Expected behavior
The user should be able to view available google accounts and select.
Screenshots
No screenshot because nothing available on the page but I can share code snippets.

System information

OS: macOS, Android device. Android Simulator
Version of supabase-Flutter: supabase: ^0.0.1-dev.22

I am getting same problem. Anyone can share the flutter example, please.

Hi @muhammadmateen027 @nomanmurtaza786
supabase-dart package just returns the authorize url for third party providers. You will need to manually trigger the browser tab to open this url.
you can take a look at the code example here

@muhammadmateen027 we release supabase_flutter to help with deeplink authentication on mobile. Give it a try and let me know if you are still facing the problem with Google login https://pub.dev/packages/supabase_flutter

@phamhieu I was trying to implement google authentication. As per the documentation, we require a google client id and a client secret. But after following those steps I am just getting a client id (no client secret, I have got a JSON file though but it too does not have anything sort of secrets). Seems like google client secrets have been deprecated for native applications. Can you suggest anything on how to proceed from here on now?

@Sahil-kachhap It appears that you have selected Android application in your case, but at the moment, you need to create a OAuth 2.0 Client IDs for web application even for native apps using Flutter. Don't worry, you will be able to sign users in form your iOS and Android apps even if you create a web application OAuth 2.0 Client ID. If you choose web application, it will give you all the necessary information including client secret!


percentage estimate calculation isn't correct in the tutorial text

The percentage estimate isn't correct in the text:
"
For example, if you have a workload that has high activity during 9am – 6pm weekday business hours, then the percentage of time at peak is: 45 hours at peak / 730 hours / month = ~6%.
"
It should be closer to ~27% not ~6% as:
(45hpw * 52wpy / 12mpy) / ( 24hpd * 7dpw * 52wpy / 12mpy) = 195 / 728 = 0.267

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

ID: 49712e97-ef9c-4198-9559-824628b54614
Version Independent ID: 59d9ae9b-e3f4-90cf-49cb-78027002fd34
Content: Estimate costs using the Azure Cosmos DB capacity planner - API for NoSQL
Content Source: articles/cosmos-db/nosql/estimate-ru-with-capacity-planner.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @deborahc
Microsoft Alias: dech

Hi @stockers,
Thanks for sharing this feedback. We will look into this and action as appropriate.

Hi @deborahc,
Could you please look into the feedback shared here and update as appropriate. Thanks!

Hi @deborahc,
Could you please look into the feedback shared here and update as appropriate. Thanks!


Broken link due to an extra Character "]" in the URL

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

@rl-msft - thanks for the catch!


Fixes #172

Make the interal value of BtpMessagetype into a short instead of an int.
Signed-off-by: sappenin<EMAIL_ADDRESS>

Codecov Report

Merging #173 into master will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #173   +/-   ##
=========================================
  Coverage     72.46%   72.46%
  Complexity      284      284
=========================================
  Files            78       78
  Lines          1264     1264
  Branches        132      132
=========================================
  Hits            916      916
  Misses          289      289
  Partials         59       59

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/org/interledger/btp/BtpMessageType.java
100% <100%> (ø)
8 <2> (ø)
:arrow_down:

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 a35a9ec...bddf50b. Read the comment docs.


Add a visual indicator four boundary nodes

Currently, there is no visual cue to suggest that a node is a boundary or a floating node. Possible visual cues include:
Rectangle around the node
A small filled dot in the corner
etc
Probably a rectangle around the node would be easiest to implement

Added a rectangle around boundary nodes


add an expectAll feature

🚀 Feature Proposal
As a developper I want my test to be able to fail on multiple expects so that I can debug/test faster
Example
It would work like the assertAll in Junit5
assertAll("Should` return address of Oracle's headquarter",
    () -> assertEquals("Redwood Shores", address.getCity()),
    () -> assertEquals("Oracle Parkway", address.getStreet()),
    () -> assertEquals("500", address.getNumber())
);

instead of :
expect(true).toBe(false); // test runner report only this line as a failure
expect(true).toBe(false);

I suggest :
expectAll(
   () => expect(true).toBe(false), // test runner report this line as a failure
   () => expect(true).toBe(false) // test runner report this line as a failure
)

Jest is awesome and with this QOL improvement it would enhance developpers productivity even more

Hi!
I think that this is an interesting idea! I wonder if this could be also done as a third party library to begin with?
For example import expectAll from 'expect-all', or one would add it as a global in one the setup files. Similar to how jest-extended works

That's a good idea, didn't thought about jest-extended ! I'll post an issue there to see what happens

Got it. I’ll close this in the mean time, we can reopen it if needed.

@rogeliog
I feel this is a legit feature request for jest !
Not so much for this jest-extended library, which aims to support matchers,
while this is more a core jest assertion bubbling modification request.
Having used this effectively and extensively in Junit5 - assertAll,
it is really a better user experience to not have to fix one error at a time! 😅
API REQ: expectAll

Asserts that all supplied executables do not throw an (Assertion) Error

If any of the supplied executable throws an AssertionError,
all remaining executables should still be executed,
and all failures can be aggregated and reported in a MultipleFailuresError

Else if an executable throws an exception that is not an AssertionError,
execution should halt immediately,
and the exception should be re-thrown as is but masked as an UncheckedException

Bonus:
If Jest does this Error collection more smoother by default for all AssertionErrors within the it block (with some js magic, without an explicitAll assertions),
that would also be Awesome!! 😃

I agree with @ufo2mstar @rogeliog  the jest-extended is centered around matchers, I believe it's better to implement it here.
I can try to implement it if you don't mind

@RomainBitard that'd be great if you get this working! :D
We have the same as an open issue here: https://github.com/jest-community/jest-extended/issues/272

for the moment both issues are closed but if I manage to get some time I would gladly try and implement it


Fix shouldNot typeCheck syntax for Scala 3

Fixes #2007

@bvenners I hope this can make 3.2.9

Tnx @griggt for the fix! @SethTisue We'll look into it pronto.

@bvenners The changes looks great to me, and I tested it with Scala 3.0.0-RC3 also, too bad we missed this for 3.2.8, do you mind to merge the following first:
https://github.com/scalatest/scalatest/pull/2009
so that we can create release tag for 3.2.8 and continue to merge this as part of 3.2.9?
Thanks.

@cheeseng will do. Tnx for reviewing!

I'm going to merge this, though shouldNotTypeCheck is not differentiating between a type and a syntax error:
scala> "val a: Int dude! = 1" shouldNot typeCheck
val res14: org.scalatest.Succeeded.type = Succeeded

Same is true for assertTypeError:
scala> assertTypeError("val a: Int fred = 42")
val res5: org.scalatest.Succeeded.type = Succeeded

In Scala 2, for example we get:
scala> assertTypeError("val a: Int fred = 42")
org.scalatest.exceptions.TestFailedException: Expected a type error, but got the following parse error: "identifier expected but '=' found.", for code: val a: Int fred = 42
  ... 35 elided

The compiler classifies the first example as a type error rather than a parser error:
scala 3.0.0-RC3> scala.compiletime.testing.typeCheckErrors("val a: Int dude! = 1")
val res0: List[scala.compiletime.testing.Error] = List(Error(<error Not found: type dude> does not take type parameters,val a: Int dude! = 1,11,Typer), Error(Not found: type dude,val a: Int dude! = 1,11,Typer))

which seems be the case in Scala 2 as well:
scala 2.13.5> "val a: Int dude! = 1" shouldNot typeCheck
val res3: org.scalatest.Succeeded.type = Succeeded

https://scastie.scala-lang.org/R1x2YhdURlimVhv5a5jR9A

The second example is correctly identified as a parse error by the shouldNot typeCheck implementation in this PR:
scala 3.0.0-RC3> "val a: Int fred = 42" shouldNot typeCheck
org.scalatest.exceptions.TestFailedException: Expected a type error, but got the following parse error: "an identifier expected, but '=' found", for code: val a: Int fred = 42
  ... 38 elided

However I notice that assertTypeError (I was unaware of this function) has a separate implementation that was not updated by this PR.
I'd be happy to open a new PR to fix that as well.

@griggt A PR would be awesome. I now remember sometimes I thought something should be a parse error but it was classified as a type error, though I think I checked each of those in Scala 2. Anyway, a PR would be very helpful. Tnx!


importing aws route53 records is painfully slow

this dominates the runtime of our periodic imports -- any reason it takes so long? It seems a cli53 export -> transformation would be orders of magnitude faster.

Our algorithm is as follows:

Fetch a list of hosted zones
For each hosted zone fetch a list of fetch a list of zone's records
Reimport each resources separately by Terraform AWS provider plugin

That last step might take significant amount of time and might be the cause of your problems. In the meantime, we also send requests to fetch resource schema from the plugin for each detected resource (it takes quite a lot of CPU cycles). That's I think is the only performance improvement that we can make since:

Terraform import functionality doesn't allow batching
We want to make use of the plugin to format Terraform resources correctly

@sergeylanzman I think general improvements to terraformer is everything that can be done, without changing the core assumptions on how we interact with Terraform plugins.
AWS Route 53 has limitation on the number of how many calls can be made to the service and it is 5 per second. After that, it'll throttle requests (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html#limits-api-requests-route-53).
On my account, I can import ~240 AWS Route 53 resources in around 2 minutes, which makes on average 2 reqs per second. That sounds good enough for me not to initiate request throttling and I think that number might higher close to US East coast (am placed in SE Asia) due to lower latencies. The import time is same as terraform plan command.

Thanks! @meshuga


Comment out torch installation since it is failed, and torch is already installed in colab.

this is to fix the installation from colab

ERROR: Could not find a version that satisfies the requirement torch==2.1.2+${DEVICE} (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0)
ERROR: No matching distribution found for torch==2.1.2+${DEVICE}

Merging now, but feel free to let me know your feedback and will follow up.


I need help!

I'm sorry for bothering you again my friend, I tried to modify it several times but it doesn't work, you changed node modules and always got an error, the script you gave me (https://pastebin.com/raw/emnA4viQ) doesn't seem to work compatible with node modules, can you zip the whole project together with suitable node modules for this script https://pastebin.com/raw/emnA4viQ
I have tried with some previous node modules that you have published, but I always get a different error!
Thank you for everything you have helped me!!!

if it breaks i don't open issue again here please it not related to my script now
heres the zip file after extract it in it's directory use npm i https://www.mediafire.com/file/9upikkzvlrjdaaf/final.zip/file


(#76) Cleanup and fix weird dev module behaviour

Description Of Changes

Renamed module.psm1 to module.ps1
Changed the dot-sourcing in the dev-time ChocoCCM.psm1 to load it from the new name

Motivation and Context
Previously importing the module from src/ChocoCCM.psd1 or src/ChocoCCM.psm1 would open a notepad window. This seems to be because dot-sourcing PSM1 files is not permitted and it simply invokes the file. Instead, just rename the module.psm1 to module.ps1 so it can be dot- sourced.
Testing

Import the dev-time module with Import-Module ./src/ChocoCCM.psd1
No Notepad window should be created

Change Types Made

[x] Bug fix (non-breaking change)
[ ] Feature / Enhancement (non-breaking change)
[ ] Breaking change (fix or feature that could cause existing functionality to change)
[ ] PowerShell code changes.

Related Issue

Fixes #76
Change Checklist

[ ] Requires a change to the documentation
[ ] Documentation has been updated
[ ] Tests to cover my changes, have been added
[x] All new and existing tests passed.
[ ] PowerShell v2 compatibility checked.

@vexx32 thanks for getting this fixed up!


Fix for WFCORE-1829, added CLI reload support

--start-mode for reload command.
--admin-only has been deprecated. No more proposed by completion but still usable.
Added unit test and updated help.
Follows up on #1841
https://issues.jboss.org/browse/WFCORE-1829

Core - Full Integration Build 3878 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3079, ignored: 93; compilation error: Compiler (new) Build time: 00:31:58

Full integration - Windows Build 2321 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3062, ignored: 94; compilation error: Compiler (new) Build time: 00:59:46

Core - Full Integration Build 3879 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3079, ignored: 93; compilation error: Compiler Build time: 00:32:31

Core - Full Integration Build 3880 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3079, ignored: 93; compilation error: Compiler Build time: 00:41:46

Full integration - Windows Build 2322 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3062, ignored: 94; compilation error: Compiler Build time: 00:50:34

Core - Full Integration Build 3882 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Exit code 1 Build time: 00:00:05

Core - Full Integration Build 3883 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Exit code 1 Build time: 00:00:03

Core - Full Integration Build 3884 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Exit code 1 Build time: 00:00:03

Core - Full Integration Build 3885 outcome was FAILURE using a merge of f1127305c30084c602928126f8a2a9fc518d1528
Summary: Tests passed: 3569, ignored: 115; unexpected error: java.lang.RuntimeException: Failed to create context for build runner: Error creating bean with name 'jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor#0' defined in URL [j... Build time: 01:07:01


Add pagination to valid versions improver

We are having the same problem that we had with the default improver, the volume of advisories is too high and it eats up a lot of RAM, by paginating the advisories we will be able to save a lot of RAM.

Trivial change merging this


HDDS-11484. Add check for javadoc correctness

What changes were proposed in this pull request?
This PR fixes all the javadoc warnings that appeared previously and adds a new job to the ci.yml file that is responsible for Javadoc validation.
What is the link to the Apache JIRA
https://issues.apache.org/jira/projects/HDDS/issues/HDDS-11484
How was this patch tested?
Patch was tested via build-branch workflow on the fork.

Thanks @Daniilchik for updating the patch, the change LGTM.  However, there are lots of conflicts, can you please merge master into your branch?

All merge conflicts resolved. I also suggest closing HDDS-11488, as all Javadoc warnings have been fixed.

Thanks @Daniilchik for fixing all the javadoc warnings and iterating on this patch.


Deploy package to www.npmjs.com

I would be nice if you could upload your package to www.npmjs.com.
Unfortunately the name is already taken (there is another package with the same name).

Seems we need to rewrite package.json. Any name suggestion?

Maybe angular-datetime-input ?

I tried updating package.json: https://github.com/eight04/angular-datetime/commit/e5c2f2faf5ade1b046952ab1df530448d3d7b182
I'm not sure how to make it become a valid node module. To add var angular = require("angular") at top of the dist file?

https://www.npmjs.com/package/angular
It says that we can use require('angular'), but I always get ReferenceError: window is not defined. Maybe it is OK to just mark "dist/datetime.js" as main file.

Fixed in 3.1.1. Please reopen this issue if I have done something wrong.


Can I expand one row to Level2 but not another

In my data source there are 2 columns. I drag them both to left panel as row fields. Say Level1 and Level2 aee headers of these 2 columns.
In Level1...items are A, B, C. etc
Level 2 are details. Eg product details...how to set the code so if items is A, H and C then preload its Level2 is expanded ...other are collapsed and Level2 is not expanded by default?
Thanks

There is no way to collapse anything unfortunately.


udev rule doc error

Hi, according to the README:
SUBSYSTEM=="usb", ATTRS{idVendor}=="289D", ATTRS{idProduct}=="XXXX", MODE="0666", GROUP="users"
However, at least on Raspbian (Debian Jessie), I had to use:
SUBSYSTEM=="usb", ATTRS{idVendor}=="289d", ATTRS{idProduct}=="XXXX", MODE="0666", GROUP="users"
(Lower case 'd' in 289d)
This had me stumped for a while!

Is very likely to be a typo. Will modify it

Done


[Bug]: Compilation failure due to missing bazel platforms support

Describe the issue
bazel is migrating to use the new "platforms" to support multi architectures: https://bazel.build/concepts/platforms
As more and more people start to use the new bazel and the platforms rules, we will see more compilation errors such as:
https://github.com/abseil/abseil-cpp/issues/1210
https://github.com/abseil/abseil-cpp/issues/1227
Can abseil update to support that?
Steps to reproduce the problem
Use bazel "platforms" to cross compile for non-x86 target, you will see the errors.
What version of Abseil are you using?
latest as of Nov 19, 2023.
What operating system and version are you using?
Host Debian 12 am64, target arm64.
What compiler and version are you using?
gcc cross compiler.
What build system are you using?
bazel 6.4.0
Additional context
No response

Steps to reproduce the problem
Use bazel "platforms" to cross compile for non-x86 target, you will see the errors.

I don't doubt that something doesn't work. Can you give us an example command?

See my steps in https://github.com/aspect-build/gcc-toolchain/issues/155

To reproduce, use the cross compiler from aspect-build gcc-toolchain which uses the new bazel platforms.
git clone https://github.com/abseil/abseil-cpp.git
cd abseil-cpp/
cat >> WORKSPACE << EOF

# aspect-build
http_archive(
    name = "aspect_gcc_toolchain",
    sha256 = "3341394b1376fb96a87ac3ca01c582f7f18e7dc5e16e8cf40880a31dd7ac0e1e",
    strip_prefix = "gcc-toolchain-0.4.2",
    url = "https://github.com/aspect-build/gcc-toolchain/archive/refs/tags/0.4.2.tar.gz",
)

load("@aspect_gcc_toolchain//toolchain:defs.bzl", "gcc_register_toolchain", "ARCHS")

gcc_register_toolchain(
    name = "gcc_toolchain_aarch64",
    sysroot_variant = "aarch64",
    target_arch = ARCHS.aarch64,
)

gcc_register_toolchain(
    name = "gcc_toolchain_x86_64",
    sysroot_variant = "x86_64",
    target_arch = ARCHS.x86_64,
)
EOF

bazel build //absl/random --incompatible_enable_cc_toolchain_resolution --platforms=@aspect_gcc_toolchain//platforms:aarch64_linux --cxxopt=-std=c++17 --host_cxxopt=-std=c++17

You should see the errors because the cpu type was not properly selected.

+1 for this, the problem is in absl/copts/configure_copts.bzl
# ABSL_RANDOM_RANDEN_COPTS blaze copts flags which are required by each
# environment to build an accelerated RandenHwAes library.
ABSL_RANDOM_RANDEN_COPTS = select({
    # APPLE
    ":cpu_darwin_x86_64": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_darwin": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_x64_windows_msvc": ABSL_RANDOM_HWAES_MSVC_X64_FLAGS,
    ":cpu_x64_windows": ABSL_RANDOM_HWAES_MSVC_X64_FLAGS,
    ":cpu_k8": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_ppc": ["-mcrypto"],
    ":cpu_aarch64": ABSL_RANDOM_HWAES_ARM64_FLAGS,

    # Supported by default or unsupported.
    "//conditions:default": [],
})

if using platforms this should be written:
select({
    "@platforms//cpu:k8": ABSL_RANDOM_HWAES_X64_FLAGS,
    "@platforms//cpu:ppc": ["-mcrypto"],
    "@platforms//cpu:aarch64": ABSL_RANDOM_HWAES_ARM64_FLAGS,
    # blabla...

    # Supported by default or unsupported.
    "//conditions:default": [],
})

See https://bazel.build/concepts/platforms#select

+1 for this, the problem is in absl/copts/configure_copts.bzl
# ABSL_RANDOM_RANDEN_COPTS blaze copts flags which are required by each
# environment to build an accelerated RandenHwAes library.
ABSL_RANDOM_RANDEN_COPTS = select({
    # APPLE
    ":cpu_darwin_x86_64": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_darwin": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_x64_windows_msvc": ABSL_RANDOM_HWAES_MSVC_X64_FLAGS,
    ":cpu_x64_windows": ABSL_RANDOM_HWAES_MSVC_X64_FLAGS,
    ":cpu_k8": ABSL_RANDOM_HWAES_X64_FLAGS,
    ":cpu_ppc": ["-mcrypto"],
    ":cpu_aarch64": ABSL_RANDOM_HWAES_ARM64_FLAGS,

    # Supported by default or unsupported.
    "//conditions:default": [],
})

if using platforms this should be written:
select({
    "@platforms//cpu:k8": ABSL_RANDOM_HWAES_X64_FLAGS,
    "@platforms//cpu:ppc": ["-mcrypto"],
    "@platforms//cpu:aarch64": ABSL_RANDOM_HWAES_ARM64_FLAGS,
    # blabla...

    # Supported by default or unsupported.
    "//conditions:default": [],
})

The proposed solution doesn't support MSVC. It makes the assumption that all compilers for that CPU support the GCC-style flags.

The correct solution is to use the settings in this file rather than platforms:
https://github.com/bazelbuild/rules_cc/blob/main/cc/compiler/BUILD

The correct solution is to use the settings in this file instead of OS settings (plus @platforms//cpu constraints if necessary): https://github.com/bazelbuild/rules_cc/blob/main/cc/compiler/BUILD

Yes, that is part of the solution. How do I get the cross product of platform and cpu?

Yes, that is part of the solution. How do I get the cross product of compiler and cpu?

One option would be to use skylib's selects.config_setting_group to define selectable targets for each combination in the cross product.

Yeah, nobody can build absl-cpp with a recent Bazel without this. And nobody could for quite a while. Is this thing even alive?


patch/dependencies-1.0.4

Release 1.0.4

Codecov Report

Merging #32 (b2e9c27) into master (0abee85) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #32   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          157       157
=========================================
  Hits           157       157

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 0abee85...b2e9c27. Read the comment docs.


chore: update to Nx v18

For now I'm holding off this update until there is more clearance on https://github.com/nrwl/nx/issues/21791


Facelift of README

I needed to install apiary-client locally and I realized the README is so terrible and unhelpful that I couldn't prevent myself to initiate a change.
Note: https://github.com/apiaryio/apiary-client/issues/78 should be resolved before merging this.

Issue: output of apiary help is following:
$ apiary help
Commands:
  apiary fetch --api-name=API_NAME    # Fetch apiary.apib from API_NAME.apiary.io
  apiary help [COMMAND]               # Describe available commands or one specific command
  apiary preview                      # Show API documentation in default browser
  apiary publish --api-name=API_NAME  # Publish apiary.apib on docs.API_NAME.apiary.io
  apiary version                      # Show version

That's very far from the version in the original README:
$ apiary help

Usage: apiary command [options]
Try 'apiary help' for more information.

Currently available apiary commands are:

  preview                                     Show API documentation in default browser
  preview --browser [chrome|safari|firefox]   Show API documentation in specified browser
  preview --output [FILE]                     Write generated HTML into specified file
  preview --path [PATH]                       Specify path to blueprint file
  preview --api_host [HOST]                   Specify apiary host
  preview --server                            Start standalone web server on port 8080
  preview --server --port [PORT]              Start standalone web server on specified port
  publish --api-name [API_NAME]               Publish apiary.apib on docs.API_NAME.apiary.io
  publish --api-name [API_NAME] \
          --message [COMMIT_MESSAGE]          Publish with custom commit message
  fetch   --api-name [API_NAME]               Fetch apiary.apib from API_NAME.apiary.io
          --output [FILE]                     Write apiary.apib into specified file
  help                                        Show this help
  version                                     Show version

I see there's even already a dedicated issue for that from @Almad: https://github.com/apiaryio/apiary-client/issues/78

:+1:

I have made #96, which I believe encompasses and obsoletes this PR.


Fixes for conv_asm perf config validity check.

Remove k-split comparison with output size.
Update IsValidValue so that it is stateless, allows IsValidPerformanceConfig to be called without state.

@junliume Can we merge this ?


Replace Mockery with Phony

The expect-run-verify model of testing does not mirror how code is
actually developed. A mock-run-verify approach allows faster prototyping
and reflects how code is actually executed.
Phony has additional features, such as order verification.
https://github.com/eloquent/phony#inception

Coverage remained the same at 100.0% when pulling eff6d8978d574bf1602b57ca9f8f59c7993ff7d3 on feature/replace-mockery-with-phony into 04a26129e3241ef6bc276ba56f327e15923a1ac9 on 2.x.

@ramsey any objections to this change?

Coverage remained the same at 100.0% when pulling 22c3cb78834fd508e2270592d8fd1afa78ecb724 on feature/replace-mockery-with-phony into 0958ebdf0f862a65a68ffb9e3cb61e8898e5caf9 on 2.x.

Coverage remained the same at 100.0% when pulling 2aa6980783e81a0ea191196e65673ed88295f404 on feature/replace-mockery-with-phony into 0958ebdf0f862a65a68ffb9e3cb61e8898e5caf9 on 2.x.

@shadowhand No objections. Looks good.

Coverage remained the same at 100.0% when pulling 1c581783a098d93458e4890499879bae60cc07e6 on feature/replace-mockery-with-phony into 0958ebdf0f862a65a68ffb9e3cb61e8898e5caf9 on 2.x.

Coverage remained the same at 100.0% when pulling 1c581783a098d93458e4890499879bae60cc07e6 on feature/replace-mockery-with-phony into 0958ebdf0f862a65a68ffb9e3cb61e8898e5caf9 on 2.x.

Coverage remained the same at 100.0% when pulling 1c581783a098d93458e4890499879bae60cc07e6 on feature/replace-mockery-with-phony into 0958ebdf0f862a65a68ffb9e3cb61e8898e5caf9 on 2.x.


Error reported after running $ballerina init

Description:
I just installed Ballerina and was following the steps in the "Quick Tour".  I ran ballerina init and got an error.
Steps to reproduce:
run ballerina init
Affected Versions:
latest install version
OS, DB, other environment details and versions:
MacOS
ballerina-internal.log

Do you have permission to write to the directory you’re trying to initialize the project in?

I created a new directory and tried again and this time it succeeded. Thanks.
David Taylor
07548 019759

On 26 Jul 2019, at 03:53, Pubudu Fernando<EMAIL_ADDRESS>wrote:
Do you have permission to write to the directory you’re trying to initialize the project in?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Glad it worked. But if this indeed was a permission issue, then that shouldn't have crashed the runtime. It should've just simply said permission denied or something.

From ballerina 1.0 we will be removing init command. Please use new command to create a new directory.
Refer https://v1-0-0-alpha.ballerina.io/learn/quick-tour/ for more details.
You can download the alpha from
https://ballerina.io/downloads/
Will keep this open till we check if this issue handle in other commands.

Closing this since the issue is no longer relevant with 1.2.x and SL versions.


Android publication issues

Having jvm and android in the same project is complicated and presents some difficulties when publishing. More testing needs to be done, but it seems like publishing jvm only first, then rebuilding and publishing android only is not ideal in resolving the issues that come from production (or lack there of) of jvm JavaDocs needed for MavenCentral.
Might be that the following procedure is needed:

Build with -PKMP_TARGETS=JVM and publish jvm only
Build with -PKMP_TARGETS=ANDROID and publish android only

This will require linking those android source set containing modules that will be published with the jvm only modules that are in the staging repo which were just published, instead of the project modules.

Downgrading the Gradle Maven Publish plugin fixed the issue. See https://github.com/05nelsonm/kotlin-components/pull/62


Remove ignored file

This file was removed in #265 but it's back... do you need to remove it locally or something @vitorpamplona?
git rm --cached .idea/misc.xml

hum... my bad... probably a merge conflict with that older pr I had going for a while


Add traditional vs simplified chinese language options in publish

probably remove zh
Add Hant / Hans, and use text from Languages section for traditional vs simplified, or something like "Chinese (Simplified), Chinese (Traditional)".

https://github.com/lbryio/types/issues/44

中文（正體） = Chinese (Traditional)
中文（简体） = Chinese (Simplified)


Suggestion For Dark Armor

Description:
I have switftness upgrade on my dark steel leg piece, this causes it to drain 10x faster than other pieces so
if all pieces of the same level of empowered they could share power between tools? for more constistent recharge scedule and the possibilty to use armor as batpack for your tools?

Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-<IP_ADDRESS>_beta
EnderCore: 1.10.2-<IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>9

Your most recent log file where the issue was present:
[pastebin/gist/etc link here]

Why "of the same"? They could just share the expenses towards equal charge percentage. (So that no single item discharge before any other item.)

i was thinking maybe game balance it would make upgrading all of the armor and tools to a high level maybe less apealing

im not sure about it, it is just a suggestion after all and its up to the modder anyway

Thank you for your suggestion. It has been added to our list or possible enhancement.
This ticket will be closed because we want the list of open tickets to reflect known issues.


Update bookinfo.md

Spelling correction "folloiwng" to "following"

Certainly, @ldemailly!

From: Laurent Demailly<EMAIL_ADDRESS>Sent: Monday, January 1, 2018 3:48:03 PM
To: istio/istio.github.io
Cc: Lee Calcote; Author
Subject: Re: [istio/istio.github.io] Update bookinfo.md (#824)
@ldemailly approved this pull request.
thx for the fix !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/istio/istio.github.io/pull/824#pullrequestreview-86070035, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHOFEAHh5n786qDbohVUM0uM0lDlvLoSks5tGVKSgaJpZM4RQLXn.


Fixes dead aux channels introduce in oneshot

@sanderux
Sorry for the delay I has cascading HW issue to be able to get to a point to test. Would you be able to test this commit.
@LorenzMeier, @kd0aij
Please see if this makes sense
Returned the fmu mixer code to where it updated the HW once
it has a mixer. But  only signals a up_pwm_update() for
onshots on actual control update.
Before this change the hw outpuse were not updated.

Fixes https://github.com/PX4/Firmware/issues/6911


Update README.md

Existing Sample Changes
Description
Single file execution for FPGA on Intel Devcloud for oneAPI

These instructions are already appearing in the FPGA top level readme:
https://github.com/oneapi-src/oneAPI-samples/tree/master/DirectProgramming/C%2B%2BSYCL_FPGA#build-and-run-the-samples-on-intel-devcloud-optional

Hi, the instructions are more generic on reference for FPGA. User's need to activate oneAPI environment on Devcloud before execution and that is missing in README.

Okay Thanks, contributed as it shall be helpful for user's to have dedicated instructions for oneAPI devcloud.

We used to have these instructions but decided to remove them as:

having long readmes with instructions for all different environments was obfuscating the actual simple build commands
devcloud has its own documentation, which change with time
we can't document all possible environments

I hope this clarifies :)


Why disable formatters in vim

I just tried Reporters under vim, but I find it do not work. Then I discover the cause after I search the issues.

Disable custom formatters when running under vim
#166 opened on Jul 7 by aripollak

However when I overwrite the choose_reporters method(as below), it actually works. The output of minitest is actually formatted and colorized.
require 'minitest/autorun'
require 'minitest/reporters'

module Minitest
  module Reporters
    def self.choose_reporters(console_reporters, env)
      if env["TM_PID"]
        [RubyMateReporter.new]
      elsif env["RM_INFO"] || env["TEAMCITY_VERSION"]
        [RubyMineReporter.new]
      else
        Array(console_reporters)
      end
    end
  end
end

Minitest::Reporters.use! Minitest::Reporters::SpecReporter.new

class FlowTest < Minitest::Test
  def test_1
    assert_equal 4, 1+2
  end

  def test_2
    assert_equal 4, 4
  end
end

So, why Reporters is disabled under vim??

I think this is the question for @aripollak (I'm not using vim)

I think I explained it pretty well in the original PR?

Vim's quickfix list does not support color codes and only recognizes errors from the default Minitest output formatter.

If you use, say, vim-rails to make :Rake run unit tests, you should be able to use the quickfix list to quickly jump to the line with the errors. But minitest-reporters changes the formatting and makes vim not be able to recognize the filenames & line numbers.

I think the explanation is complete.  If it is not I'd suggest to discuss this in the gitter channel I've created.

Sorry for my unconsidered question. Surely, quickfix is a better choise to trace errors in vim despite the uncolorized output.

@os97673 Would you be open to contributions to make this configurable? Since for example, I do use vim, but not outputting anything to Quickfix since that is showing messed up output.
So I'm running the tests in a TTY enabled env, but also via VIM (so the ENV['VIM'] is set)

@jvanbaarsen am I correctly understand that VIM env.var. is set even when you run the tests in a TTY-enabled env?

@os97673 Yes, I run my test via a test runner, and under the hood they just do: !clear && bin/rake TESTFILE. But this still does not have any formatting. (I assume when you do a ! command, this gets run outside of the context of vim?

I assume when you do a ! command, this gets run outside of the context of vim?

I do not know (since I do not use vim for development :(
Could you please print value of ENV['VIM'] from your tests so we would be sure that we know the cause of the problem.  If it is I will be happy to get PR and discuss it (will need to invite @aripollak to the discussion)

@os97673 The output is:
"/usr/local/Cellar/macvim/7.4-79/MacVim.app/Contents/Resources/vim"

So, I'm waiting for the PR ;)

:+1:

@os97673 What do you think would be the best course of action? Add an option named ignore_vim? And if that is set to true, we always use the formatter, even when ENV["VIM"] is set?

@os97673 I figured out another way we can do this, without having to change the behaviour of the gem. Since all the arguments @aripollak is presenting are valid. I now setup the minitestreporter as follow:
Minitest::Reporters.use! [Minitest::Reporters::DefaultReporter.new(reporter_options)], ENV.delete("VIM")

This will enforce that the ENV['VIM'] is not present, and thus always uses the reporter :-)

I'm not sure that this is exactly what you wanted originally, but if you are ok with this then I'm ok too ;)

@os97673 Not exactly, but I don't think having an option in there for a specific editor is also terrible :-) So I'll take my loses and roll with this :-) Thanks for this awesome project!

you are welcome


Update norm estimate in each iteration

This improves the precision of the recurrences for the first iterations.

Coverage decreased (-0.5%) to 84.581% when pulling 451526af9ab4c1cb0725781b256a37811b0ae5f8 on anj/normupdate into 4d71e91980c57dad16478b5d4b906b97affc79e5 on master.


Support for NX-8SE?

Just a newbie question, but would you expect this plugin to also work with the NetworX NX-8SE alarm system? Or is it specific to your NX-595E?

From what I gather, NX-8SE is the Dutch version of NX-8E. All the prior NetworX (NX) series boards (namely, NX-4, NX-6 and NX-8 and their derivatives) support the NX-595E, and from what I know they don't support out-of-the-box IP connectivity. NGX (xGen) boards have native IP support, however, but the plugin does not support those, as I don't have a device on hand for testing, sadly.
Does your NX-8SE really have native IP support, or maybe you have an xGen model installed?

Hi Spyros, thanks for your reply. Yesterday I finally had a chance to dig in. I created a new 'homebridge' user via the web interface of the alarm and configured the plugin. I guess I do have native IP support. Everything worked out of the box, truly amazing work!

The alarm has 3 states for off, home and away
All the sensors are in HomeKit
Even the doorbell chime is there as a separate switch

I'm a happy man!
The only thing that was a bit unreliable was setting the alarm to "Home". When switched, it did arm the alarm, but in HomeKit is moved to "Away". From the alarm's web UI I could see it was in fact on "Home". It's hard for you to test of course without the device, but can you help me fix this?

Could you please try to restart the homebridge server? Sometimes after the initial setup the alarm state gets stuck when changing, which is resolved with a simple restart done just once.
Also, bear in mind that while the alarm is arming the plug-in reports the alarm as "away", because the interface provides no way to discern between arming for away and arming from home. After the arm countdown period has passed, it should report the proper status.
Please check this and report back to me so we can figure this out :)

You're right, it does switch to Home after the cool-down period. Takes a bit longer than expected, but that's good to know. I thought I'd be 10 seconds, but it's about a minute or so. Either way, I'm a happy camper. Looking forward to using the plugin. If I run into anything, I know where to ask. Thanks again!

No worries, glad you could take advantage of the plug-in ✌🏻