jbuilder appears to buffer runtest output

I have a test which is hanging, however, I dont see any test output from jbuilder, which makes it difficult to track down the problem.
In fact, it doesn't even show that the test has started, so initially, I thought jbuilder itself was hanging.
Normally this wouldn't be an issue, as I can run the test by hand, but the test only fails on Travis in this case.

Yh, basically jbuilder captures the output of all sub-commands to avoid interleaving when multiple commands are executed in parallel and also to dump their output in the log file. It also print commands after they have finished by default to provide a better output.
I guess they could be an option to not capture the output.

Thanks - verbose will do the trick here, especially since the JOBS=1 on travis.

Ok. In any case this has already been requested so I think it's worth added. I added a --no-buffer option


i will love to do copywriting for you

I love your application and would want to contribute to it, I'm not a developer but I am good at copywriting. I would love to make a copywrite for your Readme and make a pull request for you to merge. Your response would be highly appreciated. Also I would like to request if we could communicate either here or via email, so I don't have to create issues. Thank you.

Hi.
I prefer to communicate here, in issues.
I'm not sure if I need this, and I don't know if I'll like it.
You may create a pull request for me to review but note that I do not guarantee that I'll accept it.
Thank you

I don't think I need this on this stage, considering that I am going to change some stuff, and that I will have to maintain this FAQ, I would prefer to not have such thing. Thank you.


Rename TrafficSplit API Type

What would you like to be added:
IMO the TrafficSplit API name does not properly reflect the intention of the API. The API should do more that "split" traffic. After traffic is split among multiple backends, the API should be able to manipulate the request, i.e. add/remove headers.
Why is this needed:
To support Istio, Knative and other use cases that perform request manipulation after a routing decision is made.
/assign @bowei
xref: https://github.com/kubernetes-sigs/service-apis/pull/57

@danehans I think this can be closed given the consensus around your approach here: https://github.com/kubernetes-sigs/service-apis/pull/57.

Closing due to https://github.com/kubernetes-sigs/service-apis/pull/57


Convert comparison to SQLModel to table and update claims

I had to correct the claim that sqlmodel hasn't seen a release in a while. Also I converted the comparison into a table, which seems to be the more concise and natural format. I thought about adding a tgn file as a way to easily update the table on tablesgenerator.com, but reverted the commit as the markdown itself should be editable enough and less files are always preferable imho.

Thank you @iron3oxide 🙏🏻


Update Documentation with Instillation Guidence

💡 Summary
For analysts, add additional instruction on how to install new releases.
Motivation and context
Limits the need to provide support to the analysts team.
Implementation notes

Update the README file with installation instructions.

Acceptance criteria
How do we know when this work is done?

[ ] README is updated

pip install -e . to refresh new code.


Fix #4869, oracledb correctly INSERTS Buffer

Related Issues and PRs

#4869

Change(s)

Fixes parameter function for Oracledb dialect to properly handle Blobs instead of replacing them with EMPTY_BLOB() in lib/dialects/oracledb/index.js.
Created new test file to verify new behavior in test/integration2/dialects/oracledb.spec.js.

Coverage decreased (-0.04%) to 92.24% when pulling 18b8d92f229038efc5227582841ef4bf8d4b70b7 on code-ape:issue-4869/fix-oracle-silent-empty-blob into e2516cd058df984410c113cafdd8808b3ca97cc7 on knex:master.

Hey @kibertoad and @OlivierCavadenti, hope your weeks are going well! Just wanted to drop a quick message in case this has slipped through your inbox. Would love to get this in this week if possible, as we need it for a production fix. Thank you both 🙏

@code-ape sorry for the late reply, I will check today. By the way, coverage decrease because it's count lines in test... strange

No worries, thanks so much @OlivierCavadenti 🙏


Body-parser conflicts if configured outside this library

The login handler accepts JSON and form-encoded posts.  We use the body-parser module to parse these.  When a social login is performed the posted object has nested properties:
{
  providerdData: {
    providerId: '',
    code: ''
  }
}

To read these types of bodies, we use the extended: true option of the body-parser library.
However, if the developer has configured the body-parser library outside of our library like this (meaning that this middleware function is place before our router):
app.use(bodyParser.urlencoded({ extended: false }));

The body will be parsed without the extended fields, and our login handler will fail and return "invalid username or password".  This is a nuance of the body-parser library, as it won't re-parse a body if it's already done so:
https://github.com/expressjs/body-parser/blob/master/lib/types/urlencoded.js#L80
The workaround is to tell the developer to ensure that the option is set to true.  But it would be nice to find a body parsing solution that isn't affected by edge cases that arise from configuration that is outside of this library

I've been looking through the code and it looks like you only use body-parser in your controllers and don't actually need to register it for the external app! Since you have full access to these I believe you can use body or raw-body (both recommended by the folks who maintain body-parser). If you did that, you could remove the dep on body-parser altogether which would close both this and #180.

Seems like this problem still exist, using the body parser, my login request gets stuck in pending.

@timothyej can you elaborate on how you're seeing this problem?  If you could show or link to sample code that would be great.

All I did was to add this line before adding the Stormpath middleware:
app.use(bodyParser.urlencoded({ extended: false }));

This should now be fixed in 2.3.7, closing.


Select head

Select the head for our transformer model. The problem of interest is one of classification, so we are interested in models which will take in a set of hidden states and output a classification.

Will also be part of predictive modeling


⚠ SceneTime has degraded performance

In ef1963e, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 8511 ms

Resolved: SceneTime performance has improved in efcb185.


Fix try import other files than json files

Hello,
I have fix but of getLocales, this try import other files than json files.
TODO: Implement deep json files explorer.
This fix the issue : #39
Thanks.

sorry, my mistake... this is draft PR.

@kazupon its ok, i end this tomorrow.

@kazupon You can merge that PR for make deep file explorer need more modification and many change.


JDK 8u342 for Windows lacks vcruntime140.dll

Please provide a brief summary of the bug
Version 8u342 of JDK 8 for Windows contains a file named vcrunt~1.dll instead of vcruntime140.dll in both the bin and jre/bin directories.
This prevents the JVM from starting on systems that lack the "Microsoft Visual C++ 2015-2022 Redistributable".
Please provide steps to reproduce where possible
On a system without the "Microsoft Visual C++ 2015-2022 Redistributable" run java.exe -version.
Since my dev system has a file named C:\Windows\System32\vcruntime140.dll I renamed it temporarily and set the Path environment variable to an empty string.
Expected Results
C:\Program Files\Eclipse Adoptium\jdk-8.0.342.7-hotspot\bin>java.exe -version
openjdk version "1.8.0_342"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_342-b07)
OpenJDK 64-Bit Server VM (Temurin)(build 25.342-b07, mixed mode)

Actual Results
C:\Program Files\Eclipse Adoptium\jdk-8.0.342.7-hotspot\bin>java.exe -version
Error: loading: C:\Program Files\Eclipse Adoptium\jdk-8.0.342.7-hotspot\jre\bin\msvcp140.dll
Error: loading: C:\Program Files\Eclipse Adoptium\jdk-8.0.342.7-hotspot\jre\bin\server\jvm.dll

What Java Version are you using?
openjdk version "1.8.0_342" OpenJDK Runtime Environment (Temurin)(build 1.8.0_342-b07) OpenJDK 64-Bit Server VM (Temurin)(build 25.342-b07, mixed mode)
What is your operating system and platform?
Windows 10 21H2
How did you install Java?
I used the MSI installer, but the ZIP file is also affected.
Did it work before?
Previous JDK 8 versions use an older MS VS runtime (version 12.0) and work correctly.

Did you test with other Java versions?
The upstream build uses an older MS VS runtime (version 10.0) and works correctly.

Other Adoptium releases using MS VS version 14.0 are not affected (latest JDK 11, 17, 18).

Relevant log output
No response

https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/2208/ respin

The latest build looks OK, thanks.


Added 2 new ConfigurationRepository implementations

A S3ConfigurationRepository that read configurations from an S3 object with optional background refresh
A ChainedConfigurationRepository that wraps multiple configuration repositories allowing fallback scenarios
Also refactored the base interface ConfigurationRepository to use Java's Optional deprecating the Guava Optional
This closes #14 and requires https://github.com/zalando/baigan-config/pull/12

:+1:


Cannot set a resource to a non-string value

Description
The documentation of the log data model at https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#field-resource states that the resource field is a map where the keys are of type string and the values of type any. However, trying to set a resource to a non-string value fails with error message
Failed to process entry        {"kind": "receiver", "name": "filelog/test_parsing", "operator_id": "$.regex_parser", "operator_type": "regex_parser", "error": {"description": "set parse_to: cannot set a resource to a non-string value"}, "action": "send", "entry": {"timestamp":"2022-02-11T11:45:52.559646658Z","body":null,"severity":0}}

I think this is due to type checking in https://github.com/open-telemetry/opentelemetry-log-collection/blob/89d49a3897633119bfe20628ff10f945d9741636/entry/resource_field.go#L44.
Setup

Ubuntu 20.04.2
otelcol version v0.43.0

Steps to reproduce
Create a file /tmp/test_parsing.log with following content:
<30>1 2022-02-11T09:09:14.936012+00:00 myhost.local systemd 1 - -  splunk-otel-collector.service: Succeeded.

Monitor the file using a filelog receiver and write data to a new file /tmp/otel_parsing.out as configured in the agent_config.yaml below. Check OTel Collector logs using journalctl -f -u splunk-otel-collector.
agent_config.yaml
extensions:
  health_check:
    endpoint: <IP_ADDRESS>:13133
  http_forwarder:
    ingress:
      endpoint: <IP_ADDRESS>:6060
    egress:
      endpoint: "${SPLUNK_API_URL}"
  smartagent:
    bundleDir: "${SPLUNK_BUNDLE_DIR}"
    collectd:
      configDir: "${SPLUNK_COLLECTD_DIR}"
  zpages:
  memory_ballast:
    size_mib: ${SPLUNK_BALLAST_SIZE_MIB}

receivers:
  filelog/test_parsing:
    include:
      - /tmp/test_parsing.log
    start_at: beginning
    include_file_name: false
    operators:
      - id: regex_parser
        type: regex_parser
        parse_from: $$body
        parse_to: $$resource['fields']
        regex: '^<(?P<priority>\d{1,3})>\d{1,2}\s(?P<timestamp>\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d+(?:[+-]\d{2}:\d{2}|Z))\s(?P<host>\S*)'

processors:
  batch:
  memory_limiter:
    check_interval: 2s
    limit_mib: ${SPLUNK_MEMORY_LIMIT_MIB}
  resourcedetection:

exporters:
  file/test_parsing:
    path: /tmp/otel_parsing.out

service:
  telemetry:
    logs:
      level: "debug"
  extensions: [health_check, http_forwarder, zpages, memory_ballast, smartagent]
  pipelines:
    logs:
      receivers:
        - filelog/test_parsing
      processors:
        - memory_limiter
        - batch
      exporters:
        - file/test_parsing

Seems to be addressed in https://github.com/open-telemetry/opentelemetry-log-collection/issues/190.


Updating Spectrum Tokens to 6.0.0-beta.18.9

Description
The build is breaking so I'm looking what components are having issues and what it will take to fix them.
If it's too much work I'll split it into issues.
To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[ ] This pull request is ready to merge.

Build fixed, some files were missing.


Feature/Create headless RCL

This change is

Testing locally since this repo isn't deployed on Netlify

Testing locally since this repo isn't deployed on Netlify

When testing locally it says Module not found: Can't resolve 'scripture-resources-rcl'
Did you publish<EMAIL_ADDRESS>

When testing locally it says Module not found: Can't resolve 'scripture-resources-rcl'
Did you publish<EMAIL_ADDRESS>

@mannycolon - see that version at https://www.npmjs.com/package/scripture-resources-rcl, but nevertheless I updated to the published version.

@mannycolon - see that version at https://www.npmjs.com/package/scripture-resources-rcl, but nevertheless I updated to the published version.

LGTM

LGTM


Correct email limit on Basic 100K

Description of the change: Changed email limit from 200,000 to 300,000 for Basic 100K
Reason for the change: Typo on the email limit for that plan
Link to original source: https://sendgrid.com/docs/ui/account-and-settings/billing/#limits-and-overage-rates

Closes #

Hello @katieporter,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


⚠ PrivateHD has degraded performance

In 22f4e80, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1628 ms

Resolved: PrivateHD performance has improved in 3fb3e40.


net/netip: Document of AddrFromSlice doesn't mention that passing IPv4 net.IP made with net.ParseIP to AddrFromSlice creates IPv4 mapped IPv6 netip.Addr

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

$ go version
go version go1.19 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/yutaro/.cache/go-build"
GOENV="/home/yutaro/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/yutaro/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/yutaro/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
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 -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2759925210=/tmp/go-build -gno-record-gcc-switches"

What did you do?
https://go.dev/play/p/Dnz95xrGio-
What did you expect to see?
isIPv4: true, string: <IP_ADDRESS>
isIPv4: true, string: <IP_ADDRESS>

What did you see instead?
isIPv4: true, string: <IP_ADDRESS>
isIPv4: false, string: ::ffff:<IP_ADDRESS>

The issue happens because net.IP holds an IPv4 address in the form of an IPv4 mapped IPv6 address if I understand correctly. Since AddrFromSlice is not aware of the net.IP and it only sees the length of the slice, so it is working as intended in that sense. However, the document of AddrFromSlice is a bit misleading.
Note that a net.IP can be passed directly as the []byte argument.

It can be read like we can use AddrFromSlice to convert net.IP to netip.Addr, but as mentioned in the https://github.com/golang/go/issues/37921, net.IP cannot distinguish IPv4 address and IPv4 mapped IPv6 address. Thus, users should always be aware of the address family of net.IP before calling AddrFromSlice and need to do net.IP.To4() when it is an IPv4 address. I think users should know this.

cc @ianlancetaylor @neild

CC @bradfitz @josharian

I believe this has been cleared?

i send a cl to add ipv4 check to netip.AddrFromSlice.
https://go-review.googlesource.com/c/go/+/443196
please feel free to review it

As the comments for net.IP say, 16-byte slices can still be IPv4 addresses. And IP.String() checks the version of ip and returns a different address string.
But AddrFromSlice only checks the length of the slice. So I think AddrFromSlice should check the ip version

// Note that in this documentation, referring to an
// IP address as an IPv4 address or an IPv6 address
// is a semantic property of the address, not just the
// length of the byte slice: a 16-byte slice can still
// be an IPv4 address.
type IP []byte

See also:

#53607
#53554

But AddrFromSlice only checks the length of the slice. So I think AddrFromSlice should check the ip version when the slice length is 16-byte.

In fact, AddrFromSlice over ParseIP or directly produces slightly different results.
The two objects compare successfully on a reflect.DeepEqual, but the .Is4 returns two different values.
This is confusing. If you really don't want to change it, at least please document it clearly.
func TestAddrFromSlice(t *testing.T) {

	addr1, _ := netip.AddrFromSlice(net.ParseIP("<IP_ADDRESS>"))

	if !addr1.Is4() { // this fails
		t.Logf("addr1 is not ipv4: %#v", addr1) // addr1 is not ipv4: netip.Addr{addr:netip.uint128{hi:0x0, lo:0xffffc0a80101}, z:(*intern.Value)(0x140000be018)}
		t.Fail()
	}

	addr2, _ := netip.AddrFromSlice([]byte{192, 168, 1, 1})
	if !addr2.Is4() {
		t.Logf("addr2 is not ipv4: %#v", addr2)
		t.Fail()
	}

	if !reflect.DeepEqual(addr1, addr2) {
		t.Logf("DeepEqual failed, addr1 %#v, addr2 %#v", addr1, addr2)
		t.Fail()
	}
}


update version to v0.37.0

update to cadvisor 0.37.0
use debian-slim to reduce image size
update readme.md

👍  +1

From what I can tell arm32v7/debian-slim doesn't exist.
https://hub.docker.com/r/arm32v7/debian-slim


Reading MESA edf file

There seems to be an issue with
https://github.com/cbrnr/sleepecg/blob/61b15a8d03089db8afddcad341c8857a6f630756/sleepecg/io/sleep_readers.py#L653
There is no channel name 'ECG' in latest MESA release, do not know if there was before or when it was changed.
a list of current channel names is as follows
['EKG',  'EOG-L',  'EOG-R',  'EMG',  'EEG1',  'EEG2',  'EEG3',  'Pres',  'Flow',  'Snore',  'Thor',  'Abdo',  'Leg',  'Therm',  'Pos',  'EKG_Off',  'EOG-L_Off',  'EOG-R_Off',  'EMG_Off',  'EEG1_Off',  'EEG2_Off',  'EEG3_Off',  'Pleth',  'OxStatus',  'SpO2',  'HR',  'DHR']

Could you provide a minimal reproducible example please? I tried the following snippet, which worked without errors:
from sleepecg import read_mesa, set_nsrr_token

set_nsrr_token("<INSERT_NSRR_TOKEN>")
mesa = read_mesa(records_pattern="0001*")
next(mesa)

`
from mne.io import read_raw_edf
rec = read_raw_edf("PATH/TO/file.edf", verbose=False)
ecg = rec.get_data("ECG").ravel()
`
ValueError: picks ('ECG') could not be interpreted as channel names (no channel "['ECG']"), channel types (no type "ECG"), or a generic type (just "all" or "data")

I do not use sleepecg's readers, the issue is located in an inner function that reads HR data from the edf files.
https://github.com/cbrnr/sleepecg/blob/61b15a8d03089db8afddcad341c8857a6f630756/sleepecg/io/sleep_readers.py#L480-L682
This might worked for previous versions of MESA, but it does not now.
The aim of this issue was to bring this misbehavior to your notice.


Support custom languages

Currently the list of supported generation languages is an enum in the CLI tool. This should be extensible so new languages can be added without having to update the CLI tool to add support for them.  This is especially useful since it is possible that the existing language generators are either insufficient, have bugs that need to be worked around or for adding support for a new language. There is an existing open issue asking for support for Crystal. In that issue it is recommended to create a custom generator but, again, that cannot be done without also modifying the CLI tool source code to add it to the enum.

Thanks for your interest in kiota and for reaching out.
We're ok with having languages in the enum for which the the generation implementation is not completed yet. This is how we've driven progress for all languages to date, and right now swift is a long way from being able to generate a working client for example.
The info command is here to provide the user with the maturity of each language implemented with their version of kiota.
Using an enum makes validation and code maintenance much easier over time.
I hope this answer provides better visibility on how kiota drives progress. Don't hesitate if you have further questions. We'll be more than happy to see pull requests for new languages support and we know it takes time to implement them fully.

Closing due to lack of activity


Add initial support for serializing physical plans with Substrait

Which issue does this PR close?

Part of https://github.com/apache/arrow-datafusion/issues/5173
Rationale for this change

I would like to be able to use Substrait with physical plans.
What changes are included in this PR?

Move existing consumer and producer into substrait::logical_plan namespace.
Create new consumer and producer in substrait::physical_plan namespace.
Implement very basic support for serializing ParquetExec (really, not enough to be actually useful, but gets the structure in place).

Are these changes tested?

New test added
Are there any user-facing changes?

No

@nseekhao @jdye64 @waynexia fyi


Work with PDF

It would be great if jetzt worked with PDFs. I don't know if that's possible from JS. But if it's not, we could at least documented a recommended way to convert PDF to text or HTML that works well with jetzt.
This is something I'm interested in researching.

Did anyone find a better alternative to work with PDFs by any chance?
I've been uploading them as ePub but it constantly turns out to be bad quality (rendering).


can't find 'ckpts/instructblip-vicuna-7b'

in demo.py
model_base = 'ckpts/instructblip-vicuna-7b'
sampler_model_base = 'ckpts/bert-base-uncased'
Are these two weight files downloaded from https://huggingface.co/Salesforce/instructblip-vicuna-7b and https://huggingface.co/google-bert/bert-base-uncased?

Yes,  I apologize for the lack of a proper introduction.


Unit test must exists in this repo to cover code coverage

In order to make sure our code is safer and bugs-free, we have to put unit test no matter what. @kelseyhightower please merge this PR

There is already 100% coverage.

I don't think, that unit tests are really required. No code is bug safe. But nocode is bug safe.

Yeah, no code is widely portable to different platforms.  How can we account for all relevant states of execution?


A button to open download directory

Hi ziahamza
I think we need a button (one of the label showing download path) to open the download directory folder, don't you think?
Also, has the torrent list display been fixed? Thanks.

Does the torrent list display bug have an issue on github?
This should be possible and quite handy if the webserver already supports displaying directors of the download folder ... without it webui wont be able to display the folder of the download directory  I guess

Thanks for the reply.
Now I figured I can't find the torrent list function anymore. Is it removed?
I'll leave the directory fix to you, just a suggestion, and I actually have no idea what you are talking about...


why are nacos versions inconsistent?

<nacos.client.version>2.1.0</nacos.client.version>
<nacos.config.version>0.8.0</nacos.config.version>

Which version of springcloud alibaba is it? Dependency in which component? Please provide more information.

<nacos.client.version>2.1.0</nacos.client.version> <nacos.config.version>0.8.0</nacos.config.version>

Because, we don't use <nacos.config.version>0.8.0</nacos.config.version> actually and update it's version. we will delete relevant properties, dependency and code.

I deleted <nacos.config.version>0.8.0</nacos.config.version>.


Update New-SPSiteSubscriptionFeaturePack.md

Fixed example

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/New-SPSiteSubscriptionFeaturePack.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix newsletter subscribtion of an email address with symbols

Short Description and Why It's Useful
This PR solves the problem of the newsletter subscribe with an email containing symbols (like '+' for example). Since the email is sent as part of the URL request, now the chars are encoded.
Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

[ ] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[x] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

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

hey, thanks for pr, but email is not a part of URL. It's in body https://github.com/DivanteLtd/vue-storefront/blob/master/core/data-resolver/NewsletterService.ts#L25


okular: Add version 20.08.1-392

I told you to reopen the PR, not open a new one.
I do not see any test PRs in your repositories. Did you fix the issues?


[v1.28.0] Not able to inspect elements in WebView (android, emulator, API 33)

Describe the bug
I am not able to assert that some text is visible in an Android WebView when targeting API 33. The hierarchy does not contain any of the texts I expect, and Studio does not let me inspect any of the elements. (I also experience the same on my Pixel device running Android 14 preview) It works on emulator targeting API 32.
Slack thread discussing the issue: https://mobile-dev-inc.slack.com/archives/C041FU72T54/p1685687193237819
Cloud run that fails because of this: https://console.mobile.dev/uploads/290128bd-c337-499b-a1f9-a7aa6ef9109c?teamId=d654771a-0d9f-4d20-9c2a-c0dcd36c08b5&appId=69c4e90d-9edc-4c1f-82bd-03d096219a01&analysisId=36fe9c6b-eee0-4f15-a87d-a2894e9c8aab&checkIdx=0
To Reproduce
See the cloud run above to see the issue, but in short;

have an app that opens a webpage in a classic xml WebView
launch the app on an emulator targeting API 33.
run a flow or open Studio and try to do assertions in the webview.

Expected behavior
I want to be able to assert visibility of elements in a Android WebView.
Screenshots

Environment information (please complete the following information):

Maestro version: 1.28.0
Platform: Android, API 33
Framework: Native Android
Device model and OS version: Emulator (and possibly also device) targeting API 33 and above
Host Mac M1

One strange thing I notice: If I go back one step (still inside webview) and tap on the element that open this page again, then I am able to inspect the elements on the page! I guess that makes it clear that we can rule out any issues with the webpage being displayed.

@Dambakk can you please name the apk ? or you can share the application on which you are getting the error ?

Can you DM in the maestro slack? I can share it with you there :)

I have similar issue. I'm trying to interact with elements in webview but Maestro sees whole screen as an element. Do you have a detailes documentation about testing webview with Maestro?

Same here. Using Maestro studio and an Android apk when I open a webview, I can only do tapOn on the webview, I can't assert on any elements of the webview as Maestro Studio doesn't see them.

Still happens on 1.35.0

+1 it seems webview on android doesnt work for certain things, we would also need the webview to behave the same in android and ios

+1 I face this issue too, sometimes it detects the entire webview as a single component in android but sometimes, its able to view the hierarchy of the components inside webview.

Could this be related to leancodepl/patrol#244?
@bartekpacia I saw you are active in both Patrol and Maestro. And you (partly?) fixed the issue I linked in Patrol. Could there be a similar fix here? Or is it completely unrelated after all?
(I'm experiencing the same issue with a Flutter InAppWebView btw)

Could this be related to https://github.com/leancodepl/patrol/issues/244?

It's possible, but unfortunately people who reported this problem in this issue don't specify what technology their app is built in – so we're not sure if it's only Flutter.

@bartekpacia they mention Framework: Native Android in the initial report, so I guess it's not only flutter.
I'll give it a new try with the new Flutter release 3.24 and report back

No luck with 3.24

It is sill a problem on API 34, maestro 1.37.9. (Android Native)

Is someone able to provide an APK to test with? I'd love to work out what's going on here.

Is someone able to provide an APK to test with? I'd love to work out what's going on here.

I won't say that this problem applies to a specific APK, as in my tests I've noticed that the problem sporadically happens for the same APK and emulator/devices.

Sounds like a Studio bug then, if it's only reproducible intermittently?
Have you seen it affect real tests?


Inline vnode children

Decreases size. Further decrease with developit/microbundle#335.

Coverage remained the same at 100.0% when pulling 598e2403032614820e2859943cd94f25d4f1039e on inline-vnode-children into db040ac86b775b06a793277015dfd16b9d23d52c on master.

We can do this now or wait for my Fragments PR. Doesn't matter too much to me. Doing this was a to-do in my branch :)

@andrewiggins yeah, we didn't want to interfere with your indices based ceviche PR. You can do the call to merge here :)


repertory and files intellisense

it should be cool to have auto completion for repertory and files when you import or to do fread() fwrite().
Bye :)

What language are you using?


Fix #36074 Fixed syntax error on TestDatabases on latest laravel version 8.x

You're using a PHP version lower than 7.3

You're using a PHP version lower than 7.3


Missing type casting call for primary key

PHP Version: 8.0
Cycle ORM: 1.5.0
If you use the UUID as the primary key, then when fetching related records, the ORM crashes with an error:
[TypeError]
array_key_exists(): Argument #1 ($key) must be a valid offset type.

https://github.com/cycle/orm/blob/master/src/Parser/AbstractNode.php#L341
How to reproduce:

Follow this guide https://cycle-orm.dev/docs/advanced-column-wrappers
Follow this guide https://cycle-orm.dev/docs/advanced-uuid (but don't forget to replace Ramsey UUID with a typecasted object from p.1 in nextPrimaryKey).

Possible fix:
    protected function mountArray(string $container, string $key, $criteria, array &$data): void
    {
        $criteria = (string) $criteria; // fix

        if (!array_key_exists($criteria, $this->references[$key])) {
            throw new ParserException("Undefined reference `{$key}`.`{$criteria}`");
        }

        foreach ($this->references[$key][$criteria] as &$subset) {
            if (!in_array($data, $subset[$container], true)) {
                $subset[$container][] = &$data;
            }

            unset($subset);
            continue;
        }
    }

It is correct fix. Would you like to create a PR?

PR merged but still neet to add test case

Outdated


403 error systematically

trainline version: 0.1.2
Python version: Python 3.7.12
Operating System: Ubuntu 22.04

Description
import trainline
results = trainline.search(
departure_station="Toulouse",
arrival_station="Bordeaux",
from_date="15/05/2023 08:00",
to_date="15/05/2023 21:00")
print(results.csv())
What I Did

ConnectionError: Status code 403 for url https://www.trainline.eu/api/v5_1/search
{"url":"https://geo.captcha-delivery.com/captcha/?initialCid=AHrlqAAAAAMAlKNr1QJizNQAmE2fxQ==&cid=8xF~oUzPNL-oYo39IbiOCm6bsa07Cczk449-C5qcIlqEYLyQRKMnipNjrzunDh7j4fAy0_YdSq~qhEPSd0w73WxlGhLCy~qtybii6zkYYvkzpIUBELc3A9GvOjVIaOp&referer=HTTPS%3A%2F%2Fwww.trainline.eu%2Fapi%2Fv5_1%2Fsearch&hash=E1950F58FF4C3B67C237DE42A4D080&t=fe&s=35668&e=6418b8f16dabeec967beb95265b8b63962e2c4166ca4b41593d3e90c3995fb34"}

Hello,
The error is due to the anti-bot protection from Datatome.  which protects Trainline's APIs from scraping.

Is there any work-around this protection ?


.Net: Bug: VectorStoreOperationException using the SqliteVectorStore

Describe the bug
I'm having trouble using the new SqliteVectorStore included in the latest release.
I first attempted using the AddSqliteVectorStore(connectionString, options, serviceId) overload, but it creates a new SqliteConnection that it never opens and any subsequent operations on the vector store fail. I don't see any obvious way to open it after the fact.
https://github.com/microsoft/semantic-kernel/blob/01c288a4be3c5a2f9c99454aee1035294bc6cb17/dotnet/src/Connectors/Connectors.Memory.Sqlite/SqliteServiceCollectionExtensions.cs#L49-L69
I then registered an already open SqliteConnection that it could use and added the vector store using AddSqliteVectorStore(options, serviceId) overload instead. However, any operation on the vector store fails with a VectorStoreOperationException - SqliteException: SQLite Error 1: 'no such module: vec0'. It seems that it's using a SQLite module that is not included in the Microsoft.Data.Sqlite package.
Microsoft.Extensions.VectorData.VectorStoreOperationException
  HResult=0x80131500
  Message=Call to vector store failed.
  Source=Microsoft.SemanticKernel.Connectors.Sqlite
  StackTrace:
   at Microsoft.SemanticKernel.Connectors.Sqlite.SqliteVectorStoreRecordCollection`1.<RunOperationAsync>d__50`1.MoveNext()
   at ....

  This exception was originally thrown at this call stack:
    Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(int, SQLitePCL.sqlite3)
    Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
    Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(System.Data.CommandBehavior)
    Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
    Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery()
    System.Data.Common.DbCommand.ExecuteNonQueryAsync(System.Threading.CancellationToken)
    Microsoft.SemanticKernel.Connectors.Sqlite.SqliteVectorStoreRecordCollection<TRecord>.RunOperationAsync<T>(string, System.Func<System.Threading.Tasks.Task<T>>)

Inner Exception 1:
SqliteException: SQLite Error 1: 'no such module: vec0'.

To Reproduce
Steps to reproduce the behavior:
HostApplicationBuilder builder = Host.CreateApplicationBuilder();
builder.Services.AddTransient(sp =>
{
    var conn = new SqliteConnection($"Data Source=test.db");
    conn.Open();
    return conn;
})
.AddSqliteVectorStore();

var host = builder.Build();

var store = host.Services.GetRequiredService<IVectorStore>();
var collection = store.GetCollection<string, TextChunk>("xxxx");
await collection.CreateCollectionIfNotExistsAsync();

internal class TextChunk
{
    [VectorStoreRecordKey]
    public required string Key { get; set; }

    [VectorStoreRecordData(IsFullTextSearchable = true)]
    public string? Text { get; set; }

    [VectorStoreRecordVector(Dimensions: 384, DistanceFunction.CosineDistance, IndexKind.Hnsw)]
    public ReadOnlyMemory<float>? Embedding { get; set; }
}

Expected behavior
No exceptions.
Platform

OS: Windows
IDE: Visual Studio
Language: C#
Source: Microsoft.SemanticKernel.Connectors.Sqlite - 1.24.1-preview

@f2bo Thanks for reporting this issue! At the moment, I'm working on documentation for Microsoft Learn portal with more information about SQLite connector and its setup. Meanwhile, I will share this information here:
SQLite doesn't support vector search natively, that's why SQLite extension should be loaded first. As for now, we are using the following vector search extension: https://github.com/asg017/sqlite-vec. In the future, if SQLite will support vector search natively, we will transition to that, otherwise we will continue to use this extension and maybe we could add support for other vector search extensions if there will be such requests.
In order to add it to your application, you can use following link and download install.sh file: https://github.com/asg017/sqlite-vec/releases/tag/v0.1.3. If you run this script, it will compile the extension and produce vec0.dll file. You need to take this file and put it in the same folder where your project that's using this connector is located (e.g. MyProject\bin\Debug\net8.0). After that, the extension should be loaded successfully and the functionality for vector search should work.
Thanks again!

@dmytrostruk Thank you for your reply.
Yes. I did look at the code and saw that it was using this extension. I understand that it will be necessary until SQLite supports vector search natively, but will the manual installation be required until then or is this just a temporary workaround? It's really not the best experience. Wouldn't it be possible to include the binary in the SQLite connector's package? Although, I suppose that it would mean having variants for each supported platform.
Other than the missing extension, there seems to be a second problem in that the connector never opens the SQLite connection. This can be seen with the following code that fails with InvalidOperationException: ExecuteNonQuery can only be called when the connection is open.
HostApplicationBuilder builder = Host.CreateApplicationBuilder();
builder.Services.AddSqliteVectorStore($"Data Source=test.db");
var host = builder.Build();

var store = host.Services.GetRequiredService<IVectorStore>();
var collection = store.GetCollection<string, TextChunk>("xxxx");
await collection.CreateCollectionIfNotExistsAsync();

Lastly, I noticed that the AddSqliteVectorStore overload that obtains its connection from the DI container does not load the sqlite-vec extension. Is that intentional and it is assumed that it will be already configured properly?
Thanks!

It's really not the best experience. Wouldn't it be possible to include the binary in the SQLite connector's package? Although, I suppose that it would mean having variants for each supported platform.

@f2bo Yes, the installation process is not the best one, but we will need to think how to support it better in terms of installation, since the vector extension is written in C. We will also need to handle versioning and so on. As for now, it's recommended to install it on your side in a way that works best for you.

there seems to be a second problem in that the connector never opens the SQLite connection

Thank you for reporting this, I've created a PR with a fix: https://github.com/microsoft/semantic-kernel/pull/9407

Lastly, I noticed that the AddSqliteVectorStore overload that obtains its connection from the DI container does not load the sqlite-vec extension. Is that intentional and it is assumed that it will be already configured properly?

Correct, this approach gives you more flexibility when exactly in your application runtime you want to open/close connection, load an extension etc. So, you manage it on your side, and we will just use it. Otherwise, if it's not provided, we will initialize an instance of SqliteConnection on our side, open a connection and load an extension for you. In PR I shared above, I also updated XML documentation with more details about this.
Thank you!

@dmytrostruk Thanks!
I was wondering if the requirement that the connection be already open could be removed and instead have the connector check its state and open it when necessary. Not a big deal but just one less thing that can go wrong when setting up the app.

I was wondering if the requirement that the connection be already open could be removed and instead have the connector check its state and open it when necessary. Not a big deal but just one less thing that can go wrong when setting up the app.

@f2bo In this case you could use a method overload that accepts a connection string, so the connection initialization and opening should be managed for you. I think we want to keep methods that pull SqliteConnection from DI container and just use it as is without any modifications on connection instance. This will allow users to configure their SqliteConnection in the way they want but still use DI to register VectorStore/Collection classes.

@dmytrostruk My point was that if the connection retrieved from the DI container is closed, and you use it as is, this is guaranteed to fail, which is clearly not what was intended. It seems unnecessary given that the connector can look at the state of the connection and if its closed, open it. I don't think that would break any expectations. Anyway, just wanted to make a suggestion. Feel free to close when the PR is ready.

My point was that if the connection retrieved from the DI container is closed, and you use it as is, this is guaranteed to fail, which is clearly not what was intended. It seems unnecessary given that the connector can look at the state of the connection and if it's closed, open it. I don't think that would break any expectations.

@f2bo I've added necessary logic to address this. Thanks for your feedback!

@dmytrostruk Good to hear! Thank you again.


Update Python versions with respect to May 3rd release

Thank you for the PR and the support of the project. I have verified your changes on the website and everything is correct.


Fix monitor by implementing abstractmethod can.Listener.stop

Between python-can release-4.2 and release-4.4.0, can.Listener.stop became an abstractmethod, which caused the cantools monitor command to fail with:
error: Can't instantiate abstract class Monitor with abstract method stop

See: https://github.com/cantools/cantools/issues/667
This implements a noop stop() method.

Fixed upstream. I removed the abstractmethod in 4.4.1


Query extract

Extract queries in a format readable by Navigator Optimizer

@hikoneru could you please do the following:

Squash the 2 commits into 1
Add some documentation describing the example
Hit the green "Merge pull request" button. You should have admin privileges on this repo. Please let me know if this is not the case.


Add GeForce RTX 3070

Closes https://github.com/nomadbsd/NomadBSD/issues/98
Confirmed to work in https://github.com/helloSystem/ISO/issues/359#issuecomment-1007518999

Thanks :)


Merge latest into master

Description
Merging the latest code base to master.
Overview of Changes

See above

Type of change
Please delete options that are not relevant.

[ ] Update

How Has This Been Tested?
All Tests and Build
Additional Notes
N/A

You did it @lopezton-anthem!
Thank you for signing the Anthem Opensource Software CLA.


Missing other headers on retry

I'm using rabbitmq available headers such as content-type or correlation_id but when tackles sends the message on the delayed queue, it does not proxy all the headers.
https://github.com/renderedtext/tackle/blob/master/lib/tackle/consumer/delay_queue.rb#L25

Hey guys, any news regarding this issue?


Update setting up IDE document

It's for this issue.
https://github.com/mxstbr/react-boilerplate/issues/721#issuecomment-232568348

Coverage remained the same at 98.248% when pulling df90098db8d9bae851179f2de4eb8ae787d969cf on chaintan17:update-doc into 0b0c61bbc7fd1fde27b5391ebc936ebc6b636462 on mxstbr:master.

Coverage remained the same at 98.248% when pulling df90098db8d9bae851179f2de4eb8ae787d969cf on chaintan17:update-doc into 0b0c61bbc7fd1fde27b5391ebc936ebc6b636462 on mxstbr:master.

Coverage remained the same at 98.248% when pulling e9fdd0cb9df695a634ea4ca69ce36fed9a16b726 on chaintan17:update-doc into 0b0c61bbc7fd1fde27b5391ebc936ebc6b636462 on mxstbr:master.

Let's move this the FAQ section instead of making it a new doc, and call it "Using this boilerplate with WebStorm" or something to that effect.
The explanations themselves are A+!

Coverage remained the same at 98.248% when pulling a29b24076ccedf6c6e5acb53ac868eba633761fe on chaintan17:update-doc into 9138c98dd81c95081d77b3b3154767be3aa327d3 on mxstbr:master.

please recheck :)

Coverage remained the same at 98.248% when pulling a29b24076ccedf6c6e5acb53ac868eba633761fe on chaintan17:update-doc into 9138c98dd81c95081d77b3b3154767be3aa327d3 on mxstbr:master.

Coverage remained the same at 98.248% when pulling 9140f8e155bd8352fcbc8f03957a4afa13ec46e8 on chaintan17:update-doc into 9138c98dd81c95081d77b3b3154767be3aa327d3 on mxstbr:master.

This is ace! Thanks so much @chaintan17, amazing work :tada:


wait body content still uncompleted

Hi,
I wrote a small example of my client.
Get content not ending and still waiting on the line: body.wait().unwrap()
It append less when the body is small, but every times when the body is around or upper 10000 bytes.
Do you have any idea ? Some bad usage in the example ?
Thanks,
Marc-Antoine
extern crate futures;
extern crate hyper;
extern crate hyper_tls;
extern crate tokio_core;

use futures::{Future, Stream, future};
use hyper::{Client, Error, Request, Method};
use hyper::header::ByteRangeSpec::FromTo;
use hyper::header::Range::Bytes;
use hyper_tls::HttpsConnector;
use tokio_core::reactor::Core;

fn main() {
  println!("start to get data");

  let url = "https://nomalab-test-files-eu-west.s3.amazonaws.com/sting.mov.mxf?AWSAccessKeyId=AKIAJ2GT5XQ5PEHPZNAQ&Signature=Nk6GLF8%2FazK56wncCsdYfYVUCyc%3D&Expires=1510755848".to_string();
  let range = vec![FromTo(0, 6000)];

  let uri = url.parse().unwrap();

  let mut core = Core::new().unwrap();
  let client = Client::configure()
        .connector(HttpsConnector::new(1, &core.handle()).unwrap())
        .build(&core.handle());

  let mut req = Request::new(Method::Get, uri);
  req.headers_mut().set(Bytes(range));
  let work = client.request(req).and_then(|res| {
    Ok(res)
  });

  let response = core.run(work).unwrap();

  let body =
    response.body().fold(Vec::new(), |mut acc, chunk| {
      println!("LEN = {:?}", chunk.len());
      acc.extend_from_slice(&*chunk);
      future::ok::<_, Error>(acc)
    });

  println!("wait");
  let _body_data = body.wait().unwrap();
  println!("DONE");
}

The body is read only if the Core is running. You run it to get the response, but the body is still in transit. Then, waiting on the body while the core is not running will indeed never finish.


why do list_apps not support labels query parameters

Yeah, I'm wondering this as well.  The following should work.
Create a MarathonClient() instance pointing at your Marathon server(s):
>>> from marathon import MarathonClient
>>> c = MarathonClient('http://localhost:8080')

Then try calling some methods to list apps with the given label=value parameter:
>>> c.list_apps(label="somelabel%3dlabelvaluehere")

or
>>> c.list_apps(label="somelabel=labelvaluehere")


Change route gRPC API from imperative to declarative

Today we add/delete routes. However this will not work for plugins such as PTP which manipulate routes in non standard manner. So routes API should be performed one shot using update/set Routes.
For more details
https://github.com/containers/virtcontainers/issues/500

Initial implementation works on a route at a time.  Will address this next by updating routes in a single shot.  To avoid conflict, the first step of this update will be to clear out all pre-existing routes.  It is assumed that this UpdateRoutes call will be made after the interfaces (and their addresses) are setup.

Closed by https://github.com/kata-containers/agent/pull/148


New component macro: how do you use Self::Widgets inside watch!?

When I implement component manually, I can use Self::Widgets to refer to application widgets:
...
fn update_view(
        &self,
        widgets: &mut Self::Widgets, // widgets struct here
        input: &Sender<Self::Input>,
        output: &Sender<Self::Output>,
    ) {
        widgets.label.set_label(&format!("{:?}", widgets.gtk_box)); // allows us to do something like this
    }

But I don't see a way to use this struct in macro, when using watch! (or pre_view / post_view):
...
    set_child: gtk_box = Some(&gtk::Box) {
        append: label = &gtk::Label {
            set_label: watch!(&format!("{:?}", gtk_box)),
        },
    },

error[E0425]: cannot find value `gtk_box` in this scope
  --> src/main.rs:28:56
   |
28 |                     set_label: watch!(&format!("{:?}", gtk_box)),
   |                                                        ^^^^^^^ not found in this scope

Neither gtk_box, self.gtk_box or widgets.gtk_box are defined, so how do I use the struct here?
Tested the same thing in 0.4 version. Still impossible in watch!, but pre_view / post_view allow it.

I will try fixing watch!, yet pre_view and post_view should still work the same in 0.5... I will have a closer look this afternoon.

Okay, pre_view and post_view are now working for me. I might've made a mistake somewhere, sorry.

Should be fixed now on both stable and new-approach.

The above example now compiles and works correctly. Thanks for the fix.


Remove unnecessary escapes

I used the ESLint rule no-useless-escape to highlight unnecessary escapes in the Regex. You can also see this Stack Overflow answer for more details on characters that need to be escaped and those that do not need to be escaped when inside character classes.
I also noticed that the should still remove escaped markdown syntax test is not working correctly, because the string \# Heading in _italic_ is interpreted as # Heading in _italic_, and if you add double backslashes in the beginning (\\# Heading in _italic_) the test fails. You can see more details about using backslashes in strings here.
If you want me to add ESLint as a development dependency to the project, with the no-useless-escape rule as the only active rule, let me know.

bump. any interest in this one still?


Save file is created for Witchaven 1 & 2, but can't be accessed from in-game load menu

Game
Witchaven 1 & 2
Engine
BuildGDX
Linux Distribution
KDE neon User - 5.25 x86_64
Luxtorpeda Version
55
Bug description
When attempting to save a file in either Witchaven 1 or 2, the .sav file is created, and exists along with the .ini file, which is itself read correctly at startup. When saving, and then accessing the load screen, the save file is actually displayed in the same session as it was created, but any attempts to load from it fail. Subsequent sessions in Witchaven fail to have the save file display in the load menu at all. Absolute path for .sav, .ini, & .log = "/home/$USER/.local/share/Steam/steamapps/common/Witchaven/Enhanced/GAME/"
Steps To Reproduce

Create a save game
If in the same session, attempt to load save game
The save will fail to load
Upon exiting the game, after creating a save
Re-launch the game, and attempt to load the previously made save
The save file will fail to appear in the menu

Expected Behavior
The save is created, and is able to be loaded from; either from the same session, or any and all future game sessions, provided the save file hasn't been deleted.
Additional Context
Witchaven 2 behaves the exact same way, and the file paths are virtually the same.
Thank you to the devs, I appreciate your work! Everything else I've used so far via luxtorpeda has worked without issue. I don't know if I've provided enough information to help resolve this issue, but I'm willing to try again if necessary. :)
Relevant log output
BUILD engine by Ken Silverman (http://www.advsys.net/ken)
WitchavenGDX v1.16(BuildGdx v21.113) by [M210???] (http://m210.duke4.net)
Current date Jul 05, 2022 02:48:10
Running on Linux (version 5.13.0-52-generic)
	 with JRE version: 11.0.12

Initializing resource archives
Initializing Build 3D engine
Loading palettes
Loading gamma correction tables
Loading translucency table
Polymost renderer is initialized
AMD Radeon RX 580 Series (polaris10, LLVM 14.0.5, DRM 3.41, 5.13.0-52-generic) 4.6 (Compatibility Profile) Mesa 22.1.2 - kisak-mesa PPA
TextureCache uninited!
Found controller: "Microsoft X-Box 360 pad" [buttons: 17 axises: 6 povs: 1]
Found controller: "Corsair CORSAIR GLAIVE RGB PRO Gaming Mouse" [buttons: 32 axises: 0 povs: 0]
Initializing on-screen display system
Initializing fade effects
OpenAL Soft initialized
	with max voices: 32
	OpenAL version: 1.1 ALSOFT 1.15.1
ALC_EXT_EFX enabled.
AL_SOFT_Source_Resampler not supported!
Gervill initialized
Initializing def-scripts...
Found 124 files in whgdx.dat archive
Loading whgdx.dat...
Initializing autoload folder
Initializing cutscenes
TextureCache uninited!

I am able to replicate this. This appears to be an issue with the upstream engine as this is just using the built version from the BuildGDX project. I'm not sure as to a resolution as this time.

@vasdfj
I attempted to get some help from upstream and have done some stuff myself as well, to no avail. For now, I've removed BuildGDX as an engine, but will add it back if this gets resolved. In the meantime, Witchaven games are now supported by dosbox-staging. If  BuildGDX works again, I'll have both as engine choices for those games.


Bare domain forwarding not working

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
arn:aws:amplify:us-east-2:584873075600:apps/dq0x0kfy2jfdx
Region
No response
Step
Domain forwarding
Status
Not Working
Issue or question
When I go to www.mydomainname.com the website works. However, using the bare domain, mydomainname.com does not.
Even though, in my redirects I have:
[
    {
        "source": "https://mydomainname.com",
        "target": "https://www.mydomainname.com",
        "status": "302",
        "condition": null
    },
    {
        "source": "/<*>",
        "target": "/index.html",
        "status": "404-200",
        "condition": null
    },
    {
        "source": "</^[^.]+$|\\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>",
        "target": "/index.html",
        "status": "200",
        "condition": null
    }
]

So I am confused why it does not forward to the www. domain?
Error message
No response
Additional information
No response

Hi @gabrielstengel, thank you for raising this issue. I was able to repeat this behavior with my custom domain and amplify app. Marking this as a bug but we are currently investigating a workaround.

@gabrielstengel Which DNS provider are you using?


Prevent crash when objects move to invalid poses

🦟 Bug fix
Fixes https://github.com/gazebosim/gz-physics/issues/661
Summary
DART seems to compute invalid poses for certain objects (e.g. Capsule, Ellipse) with large accelerations. The computed poses end up with nan values resulting in a crash. This patch detects this condition and reassigns the poses to the last known poses and resets velocities to zero to prevent the crash.
Test it
gz sim -v4 rolling_shapes.sdf -z 1000000 -s -r

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@mergifyio backport gz-physics7


v1 Wallet apis wrong http methods

Hi guys,
WithdrawCrypto, WithdrawWire and Transfer methods seem to be using GET
http method although the respective endpoints are POST
I am willing to make a pr if you give me a go ahead.

@tonto
If you have a fix for this, please PR, I will put into 'review/qa' and if this works, will be eventually merged.
Also moving to the Icebox pipeline for now.
Thank you for your time.

@jvatianou cool.
One more thing, it would be nice if bitfinex.NewClient() had a http.Client as a parameter so one can test easily and more importantly set the timeouts. It's a very simple change, you would just use that clinet in your HTTPDo method instead of http.DefaultClient (which is a bad idea anyway).
Thanks


Machine Learning backend scripts are not running for HTML documents

Hi Team,
I added the machine learning backend succesfully and trained model for both NER and Text classification task (when I imported the CSV documents). But when I am adding the NER backend for HTML documents , I am facing issues -
Here is my Labelling configuration -

Here is the error I am facing -

I think its not working because of HyperTextlabels (which are not actually parsed by the backend) in labelling configuration. Please let me know how I can resolve this.
Thanks

Hi @pyturn
This error tells you that you have more than 1 tag in your labeling config.
If you want to use current labeling config as is you can just comment line:

assert len(self.parsed_label_config) == 1

and proceed with your predictions.


[Question] Understanding the road map of the solution

Describe the question
We have a few road map questions with regards to this solution.

Can we consider that this solution ready for a production grade deployment?

Currently, this solution is at 0.0.9.
Thus, is it recommended to use this solution in production grade deployments?

Will this solution be integrated into AKS based clusters in the future, by default?

Will this solution receive Azure technical support in the future?

The Azure official documentation recommends the use of this solution as a best practice.
But, as per this documentation this solution will not receive Azure technical support.
Having Azure technical support will be essential when moving forward with this solution in a production grade deployment.
Appreciate if you can provide us with an understanding of the above.
Suggested tags
question

@chirangaalwis Thank you for opening the issue.
We are working on the GA/Stable criteria in the community for the driver and the provider. This is the doc - https://docs.google.com/document/d/1ySjR_Zk93Kk7rel8ZIa4Spum-xArx3jRKPsFWTUKNr0/edit?usp=sharing
We have created Stable milestone for both the driver and provider and will be working on those issues for the next few months.

Will this solution be integrated into AKS based clusters in the future, by default?

There is a GitHub issue opened for AKS integration - https://github.com/Azure/AKS/issues/1876. You can follow the issue for updates.

Will this solution receive Azure technical support in the future?

After this solution is integrated with AKS, it will be supported by Azure technical support.
The project is currently open source and is only supported via GitHub issues - https://github.com/Azure/secrets-store-csi-driver-provider-azure#support. If you need assistance in addition to GitHub issues, you can also join the #csi-secrets-store channel on Kubernetes Slack, where other community members can also help.

Closing this issue now.
Please follow https://github.com/Azure/AKS/issues/1876 to track progress of AKS integration.


Providing different names for different pattern validations doesn't work with hookform/resolvers

Describe the bug
Providing a name on string.pattern() does not return an error key with the appropriate name provided.
To Reproduce
Steps to reproduce the behavior:

Create a validation like:

joi.string().pattern(Regex, 'name1').messages({    'string.pattern.name1': 'Name 1 error message' })
or
joi.string().pattern(Regex, { name: 'name1' }).messages({    'string.pattern.name1': 'Name 1 error message' })

Check that you get the default validation message and not the custom provided one.
I have debugged it with:

resolver: (data, context, options) => {
      console.log(data, context);
      console.log(joiResolver(joiSchema)(data, context, options));
      return joiResolver(joiSchema)(data, context, options);
}

and have confirmed the error key that is provided is always 'string.pattern.name', without the custom name provided.
I have been able to get the expected behavior while validating manually (not using the resolver).
Codesandbox link (Required)
https://codesandbox.io/s/musing-shaw-btb5ps?file=/src/App.tsx
Expected behavior
Expected to be able to give different messages for different patterns with 'string.pattern.nameProvided'.
Desktop (please complete the following information):

OS: Windows 11
Browser Chrome
Version 111.0.5563.147

Hi @mumispb thanks for the feedback. Can I see how you validate manually without the resolver?

Hi @jorisre I apologize, the manual validation way does not automatically provide errors with specific keys like 'string.pattern.fieldName1', 'string.pattern.fieldName2', etc. They way I did actually involved using the context provided by the manual validation, like:
const manualValidation = joiSchema.validate(values)

const { context } = manualValidation.error.details

That context provides me with the actual validation pattern name that was triggered, which I can use to search inside a separate array of possible errors. It seems I can do the same with the resolvers using the ref.name that is inside the errors object as in formState.errors[fieldName].ref.name, right?

This is not a problem since Joi doesn't provide the names you assign to Joi errors. Unfortunately, obtaining names from Joi validation is not possible, which can be seen as a limitation.


Fix nudging and nudge resizing

Closes #1317

Could you please make this operate in document space, not viewport space? So it should always nudge everything by 1px (or 10px if Shift is held) regardless of viewport zoom. Then you might encounter the issue described in #1317, which occurred upon switching from viewport to document space. I could also just edit that issue to describe the request to change to being relative to document space, and we proceed to merge this as-is for now (since having it at all is preferable to delaying until that can be fixed into its ideal form).

I decided it's a better use of your time @0HyperCube to merge this now so you can choose to make nudging operate in document space at a time of your choice instead of needing to do it now, or it can be left to the community to work on if you judge that you have bigger fish to fry compared to this quality-of-life improvement/papercut. So I updated #1317 to describe the improvement of switching it to document space (instead of its previous focus, which was a bug resulting from switching it to document space, as that's not as relevant yet). Feel free to tackle that now, or whenever, or leave it for the community— it's no longer critical path as a part of the document graph refactor tracking issue.


Allow optional OIDC values in Helm chart

Closes #3833

What changed?
Only the required OIDC values were able to be specified in the Helm Values. I added an optional map for optional values such as customScopes, which are required for certain OIDC providers

Why was this change made?
Improve Helm compatibility with OIDC providers such as GitLab or Azure

How was this change implemented?
Added an optional map of values, enabling future compatibility of extra values without requiring Helm changes

How did you validate the change?
Verify output of the Helm chart

Release notes
No

Documentation Changes
No

@bcorijn Thank you for your contribution this should be out in the next release.


Cannot start the fortigate exporter

For some reason I cannot use the binary:
Below is the output:
[root@netmonitor fortigate_exporter]# go build fortigate_exporter.go
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid pseudo-version: git fetch --unshallow -f origin in /root/go/pkg/mod/cache/vcs/dac3237ce23c7a321475df4e3bb8c7115ea5c093fdf9bc1798a57a9ef75ede77: exit status 128:
fatal: git fetch-pack: expected shallow list
What am I doing wrong?

Good day @amitkatti
Could you let me know the output of go version and uname -a?
Finally, can you try building the exporter using go build (without arguments)?

Good day sir, thanks!
[root@netmonitor fortigate_exporter]# go version
go version go1.15.5 linux/amd64
[root@netmonitor fortigate_exporter]# uname -a
Linux netmonitor 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
go build still gives me the same error:
[root@netmonitor fortigate_exporter]# go build
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid pseudo-version: git fetch --unshallow -f origin in /root/go/pkg/mod/cache/vcs/dac3237ce23c7a321475df4e3bb8c7115ea5c093fdf9bc1798a57a9ef75ede77: exit status 128:
fatal: git fetch-pack: expected shallow list

Very good, thanks!
If possible could you try with Golang 1.16 or newer? I believe we have some things that might require Go 1.16 if nothing else.

Alright, that worked just fine. Thank you!


QUESTION: TypeScript and CRA

Questions and description
Is there anything we need to know or configure when using TypeScript with CRA?
Tasks

[x] Task 1 : Research.
[x] Task 2 : If any actions required, research how to implement these in our app.

I tried to switch our app to typescript. CRA is already prepared for this, so there is not much to configure. But it requires to install many packages including the required types (e.g. for React Router, Jest, etc.). Plus, ESLint can be used for Typescript with 2 additional plugins @typescript-eslint/parser
and @typescript-eslint/eslint-plugin. After the required installations, the app and the tests run successfully. Thus, I am in favor of switching to TypeScript.


Add support for executing external scripts using @other_script.sql

As Flyway says, that is is compatible with all scripts which can be executed by SqlPlus ('Any Oracle sql script executed by Flyway, can be executed by SqlPlus [...]'), it would be nice to add support for executing other scripts within a script file like the following:
@other_script_1.fnc
@other_script_1.syn
@other_script_1.grt

Currently, Flyway interprets this as error:
ERROR: Error executing statement at line 1: @other_script_1.fnc
@other_script_1.syn
@other_script_1.grt

ERROR: Caused by: java.sql.SQLException: ORA-00900: invalid SQL statement

ERROR: Occured in oracle.jdbc.driver.DatabaseError.throwSqlException() at line 112

Is there a way to add support for this? Otherwise I'd have to change all existing scripts in order to be able to use Flyway.

+1 for finding a solution for this problem at some point. Loading the files from class path would work for my use case  and I'm not clear what transaction or error handling limitations this would involve.

+1 Using Flyway for DDL but still depend on SqlPlus for deploying procedures, functions from a single source of the truth in our git repo.
It'd be great if we could do it all with Flyway.

+1 Would be greate to have this feature. We organize our sources (packages, table definitions, etc.) in different subfolders with (of course) git. With git and specific branches we ensure not to deploy sources in the wrong version. Nowadays we use a kind of install manifest (e.g. 1_5_5.sql) to reference this files. Actually the same way like flyway does it but not automated.
Cheers
Adam L.

This has now been implemented.


Website Link in Readme is Incorrect

In the readme file you point to your official website, but the link is incorrect. I know that's not a part of the project itself, but for obvious reasons it’s still important.
You link to:
https://serenatadeamor.org/en
It redirects to:
https://serenata.aien/
It should redirect to:
https://serenata.ai/en/
I hope this helps.

@Irio – assigned that to you as you're the DNS guy, ok?

Solved. Thanks @markwyner ;)

It's my pleasure, friend.


Package building issue due to use of chown(8) on make install

The install target of the Makefile does not interact well with the FreeBSD package building system, because it is used for installing wifibox to a stage directory as a regular user who cannot use the chown(8) command to set the proper ownership for the directories.
/usr/sbin/chown 100:101 /wrkdirs/usr/ports/net/wifibox/work/stage/var/run/wifibox/appliance/lib/chrony /wrkdirs/usr/ports/net/wifibox/work/stage/var/run/wifibox/appliance/log/chrony
chown: /wrkdirs/usr/ports/net/wifibox/work/stage/var/run/wifibox/appliance/lib/chrony: Operation not permitted
chown: /wrkdirs/usr/ports/net/wifibox/work/stage/var/run/wifibox/appliance/log/chrony: Operation not permitted
*** Error code 1

A fix has been committed in 99b0f9adf2bf48ea29e58f18d62c0169bbbb1cce.


Changes for Ticket ESA2091

Related Jira Ticket https://hlth.atlassian.net/browse/ESA-2091 for documentation.
Before the March 1st deployment, everything was fine, afterwards, the Flow for Create SA request has had the default values for “Request type” (previously “new”) and create another request (previously “no”) default to have no default values, adding extra clicks in the workflow that were not present.
Adding these default values back into the flow to correct the issue. Cause is unknown, investigating the github shows that CGI made api upgrades in early February but nothing suggests actual code changes to explain the loss of those values.
Creating branch with pull request to remediate.
Total changes made:
Create SA Flow:
Request Type Screen, Request Type field, changed default value from blank to “New”
More requests screen: Radio selection for create additional request, changed default value from unselected to “no”. {!NoChoice} string.
Also added in some queue filter changes to remediate issues with the missing filters over-riding values in prod every deployment.

approved


UI plugins refactoring. org.jkiss.dbeaver.ext.exasol

Refactoring for this plugin:
org.jkiss.dbeaver.ext.exasol
Separate ui-part to new *.ui plugin

Tools import table/export table- checked (only old bugs exist)
Session manager "force application"- checked
Lock Manager - skipped
New schema creation - verified
Constraint creation- checked
Foreign keys creation- checked (only old bugs exist)
Schema functions creation- checked (only old bugs exist)
Connection page- checked


Removed 'Analyze this data in BigQuery' button from visualization tools

Before

After

Thanks for doing this! Could you wait on submitting this for now? I think the usage dashboard I was looking at earlier wasn't updated/out-of-date, so want to double check with Prem

Thanks for doing this! Could you wait on submitting this for now? I think the usage dashboard I was looking at earlier wasn't updated/out-of-date, so want to double check with Prem

Just checked with Prem and looks like we're good to disable for now, thanks!

Thanks for doing this! Could you wait on submitting this for now? I think the usage dashboard I was looking at earlier wasn't updated/out-of-date, so want to double check with Prem

Just checked with Prem and looks like we're good to disable for now, thanks!

Sounds good-thanks Natalie!


Support relative path for aether repository

Currently i have a project using a repo generated by ceylon-gradle-plugin, and i would like to have it not hardcoded to my configuration as remote=aether:/Users/DiegoCoronel/Documents/workspace/discovery/build/maven-settings.xml

Nice! I think I also need to make it possible to use relative paths in the Gradle plugin... will do before Ceylon 1.2.3 is released.

@davidfestal I tried to use relative path in my config/.ceylon like: remote=aether:build/maven-settings.xml for my project discovery and eclipse doesnt recognize, does it need something to be done in eclipse side?

I wouldn't be surprised this is because in Eclipse it will take the path relative to whatever is Eclipse's working directory and the the project's.

@DiegoCoronel : please open an issue in ceylon-ide-eclipse.


fix(JSDoc): client & server tags should be optional

LGTM!

I aim to release a new version this weekend when I can get the cspell issues sorted out.


Bank organizer plugin

Hi Runelite Devs,
First of all thanks for the amazing client!
I'm really having problems organizing my bank. Im just a bit of a messy person.
But as my bank grows it's getting more inconvenient.
I'm not sure what the possibilities are but maybe a sort bank option?
That sorts on specific filters, like maybe herbs, gems, armour, weapons or just sort by value.
Just thought about this and thought why not suggest it, I could not find another issue about it, Im not that familiar with github so sorry if there actually is one, if so could you link me?
Kind regards,
Sander

We cant really "sort" actual bank if that is what you mean. You can use tag tabs

We cant really "sort" actual bank if that is what you mean. You can use tag tabs

Aha, yeah bank tanks require you to tag every item tho right? so that is still alot of work. If you didn't do it from the start. I was hoping the client could somehow check what item it is and maybe give the item a bank tag automatically(like herb or armour or something) and then you would be able to filter/sort.
Again just an idea, I'm not really experienced in programming so I have no idea if I am asking for something impossible. However if it's not possible I would be interested in hearing why.
Kind regards

As @sanderb93 said, sorting bank requires a lot of manual labor. I would actually suggest supporting the idea that the bank tags were a shareable commodity.
Lets say you've got a potentially common tab for "teleportation", where all runes and items offering teleports are listed. It would make sense to have this kind of tag template available and enable means to import this template of tab. Furthermore, lets say that you are interested in my custom tab, whatever it is. It would be great if I could share the tab to you and you could take it into use via import mechanism. What are your thoughts?
~piksu

We have this rolling on the discord server under #bank-tags. The gear setup also has an extensive list of import strings.

We added sharing for bank tags and also we have bank tags and so I don't think this feature request is valid anymore, as it do not provides any benefits over existing implementation, so closing


Crystal fails to compile on macos

Steps To Reproduce
Steps to reproduce the behavior:
nix-shell -p crystal2nix --run crystal2nix on macos 21E230
Expected behavior
As described in docs
Additional context
error: builder for '/nix/store/krfiihb7c99wk0f5ykq1xzh825yfxpym-crystal-1.0.0.drv' failed with exit code 2;
       last 10 log lines:
       > .......ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ....ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ....ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ..ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ..................ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ....ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ..ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ....ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > .........ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
       > ....make: *** [Makefile:93: compiler_spec] Illegal instruction: 4
       For full logs, run 'nix log /nix/store/krfiihb7c99wk0f5ykq1xzh825yfxpym-crystal-1.0.0.drv'.
error: 1 dependencies of derivation '/nix/store/9z8aar3sab6ghrb7gjy02zlrmvfnrcsq-crystal-1.1.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/psf0s9m5gvgczlgnc75c8sh24avxdm75-crystal-1.2.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/f0m0llnr3am1ip33x2dqdc9a9wyg7wr3-shards-0.16.0.drv' failed to build

.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
...ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
..ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
............ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
..ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'
.ld: warning: directory not found for option '-L/nix/store/naqxf0zirwx3jcb9j3lkyzanx4my0h90-crystal-1.0.0-lib/crystal'

Metadata
these 2 paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
  /nix/store/3iqq82lf6alaiyb8k2xqyxh4dvj3dc1l-DarwinTools-1
  /nix/store/51jc5ig0hz78vfq7p51f7c61fp6bqavl-nix-info
copying path '/nix/store/3iqq82lf6alaiyb8k2xqyxh4dvj3dc1l-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/51jc5ig0hz78vfq7p51f7c61fp6bqavl-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-darwin"`
 - host os: `Darwin 21.4.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.7.0`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Installed with sh <(curl -L https://nixos.org/nix/install) and sudo

The issue isn't crystal2nix but crystal itself on mac - it's fine on linux. We absolutely need to get this fixed for 22.05.

@peterhoeg oh I see, thanks

I've managed to dig up a mac and I'm having no issues here with nixpkgs-21.11-darwin:
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-darwin"`
 - host os: `Darwin 17.7.0, macOS 10.13.6`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.5.0pre20211206_d1aaa7e`
 - channels(peter): `"darwin"`
 - channels(root): `"darwin, nixpkgs-21.11pre336782.0a58eebd8ec"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

However with nixpkgs-unstable crystal it is indeed broken. Let me see what I can dig out.

@peterhoeg Maybe its still working due old macos version?

My bisect isn't quite done, but it looks like the issue was the Nixpkgs-wide LLVM 11 upgrade or one of the commits immediately before/after it. Which is strange, because we already pin LLVM 10!
  inherit (callPackages ../development/compilers/crystal {
    llvmPackages = if stdenv.system == "aarch64-darwin" then llvmPackages_11 else llvmPackages_10;
  })
    crystal_1_0
    crystal_1_1
    crystal_1_2
    crystal;

I'd like to remind the people here that branch-off is scheduled for tomorrow and depending on how good the staging builds progress, we will branch off rather soon.

Interestingly, crystal (and kakoune-cr which I needed this for) builds and runs for me successfully on macOS 13.0.1, aarch64-darwin, nixpkgs 872fceeed60ae6b7766cc0a4cd5bf5901b9098ec. It does still print these warnings and a lot of "object file was built for newer macOS version (13.0) than being linked (11.0)", though.
However crystal2nix still fails to build with the same error as the one for crystal above, and I also failed to build the x86_64 version of kakoune-cr (failed in crystal-1.0.0 like above) through pkgsx86_64Darwin. Since it looks like only crystal-1.2 is supported on aarch64 and it builds fine there, I assume that only older versions (or at least only 1.0.0) are broken. Would it be possible to build it the same on x86_64-darwin as for aarch64-darwin that at least the broken flag can be removed for the main package?

Interestingly, crystal (and kakoune-cr which I needed this for) builds and runs for me successfully on macOS 13.0.1, aarch64-darwin, nixpkgs 872fcee. It does still print these warnings and a lot of "object file was built for newer macOS version (13.0) than being linked (11.0)", though.
However crystal2nix still fails to build with the same error as the one for crystal above, and I also failed to build the x86_64 version of kakoune-cr (failed in crystal-1.0.0 like above) through pkgsx86_64Darwin. Since it looks like only crystal-1.2 is supported on aarch64 and it builds fine there, I assume that only older versions (or at least only 1.0.0) are broken. Would it be possible to build it the same on x86_64-darwin as for aarch64-darwin that at least the broken flag can be removed for the main package?

Feel free to make a PR.

Alright, I'm going to see if I can also make 1.2 compile on x86_64 like it does on aarch64 first, though.

Well, trying to use the precompiled 1.2.0 to build 1.2.2 on x86_64 gives me a linker error, looks like that's not that simple. I'm just going to make a PR that removes the broken flag for aarch64-darwin in a bit.

Closing this since all the packaged Crystal versions now build for x86_64-darwin as of right now, and the version that failed to build here, 1.0.0, is gone. (please reopen if there's still an issue)


Use as static row of buttons

I'd like to just show the row of share buttons, rather than having to click the "Share" button to reveal it. Having a config option to do this would be great.

@brandones surprisingly enough, this is actually against our original intention of the share-button. we were tired of the spattered share buttons one all of these sites and wanted to see if we could make a little cleaner and more concise solution to the sharing problem.
that said, we don't deny that there are use-cases out there to display the buttons on their own. while we may not prioritize this feature with a config option right now, you may realize you can probably still accomplish this effect. by using the share.open() function in the public api you could reveal the network buttons and then use CSS to remove the "share" button itself.

Hack for those interested:
JS:
var share = new Share("#share-button", {
  ui: {
     flyout: 'middle middle'
  }
});
    share.open();

CSS:
div.social {
    margin-left: -80px !important;
}

much appreciated @brandones. I'm sure others will find this helpful


UAE Pass production is not working on iOS

HI @Faisalkc4u,
We are trying to integrate UAE Pass in Android and iOS. In Android sandbox and production both are working but in iOS only sandbox is working but Production is not working and we already added configuration for iOS in .plist file.
So, kindly Can you refer some solution or document that may be missed to add our iOS configuration file.
Note: Please find the attached file for reference.
Waiting for your kind response.
Thanks

I think you missed some steps on  info.plist.
Please add your return app schema there.
@jamaljaba I don’t really recommend using this method.
There is an issue we encountered while submitting to the UAE pass team, They need the dialog for loading in fullscreen. Which is an issue from the flutter side with SDK. And we couldn't solve it.


[Question] Exposing builder pattern and issue with lifetime

Hi,
I have in Rust a builder pattern:
struct MyBuilder<'a> {
  // multiple fields , some with lifetime
}

impl<'a> MyBuilder<'a> {
  pub fn new() -> Self {
    MyBuilder {
       // all fields to None
    }
  }

  pub fn param1(self, param1: TypeOfParam1) -> Self {
     // ...
  }

  pub fn param2(self, param2: &'a TypeOfParam2) -> Self {
    // ...
  }

  pub fn build(self) -> BuiltType {}
}

I tried exposing this to C++ like this:
#[cxx::bridge]
mod ffi {
    extern "Rust" {
        type MyBuilder;

        unsafe fn new_builder<'a>() -> Box<MyBuilder<'a>>;

        unsafe fn param1<'a>(
            builder: Box<MyBuilder<'a>>,
            param1: &CxxString,
        ) -> Result<Box<MyBuilder<'a>>>;

        unsafe fn param2<'a>(
            builder: Box<MyBuilder<'a>>,
            param2: &'a CxxVector<u8>,
        ) -> Result<Box<MyBuilder<'a>>>;

        unsafe fn build<'a>(
            builder: Box<MyBuilder<'a>>,
        ) -> Result<Vec<u8>>;
    }
}

But had issue with param2 because of the lifetime.
So I went for:
#[cxx::bridge]
mod ffi {
    extern "Rust" {
        type MyBuilder;

        unsafe fn new_builder<'a>() -> Box<MyBuilder<'a>>;

        unsafe fn param1<'a>(
            builder: Box<MyBuilder<'a>>,
            param1: &CxxString,
        ) -> Result<Box<MyBuilder<'a>>>;

        unsafe fn build<'a>(
            builder: Box<MyBuilder<'a>>,
            param2: &Vec<u8>,
        ) -> Result<Vec<u8>>;
    }
}

This work because I'm lucky and only have one param that have a lifetime bound.
The other thing that is bothering me is passing the Box around, I need to create a new Box on each param call as by builder function are fn param(self) -> Self.
Which force C++ to call std::move(builder) on each param call as well (but I'm not sure this is avoidable).
Am I right doing so, or am I missing a cleaner solution?

Regarding lifetimes, I was not able to reproduce whatever error you would have seen. I would likely need you to provide a compilable repro (which I can ideally just clone from git and run cargo check) in order to be helpful. Here is what I wrote, which is exactly what you gave with only the missing type definitions and function bodies filled in: https://gist.github.com/rust-play/67ecc156b1e7a2892a11cf7255869228.
As for the boxing and std::move -- this is just a reflection that C++ has no good equivalent to Rust self-by-value method calls. My recommendation would be to wrap your original self-by-value builder into a self-by-reference builder, and expose only the self-by-reference one to C++. That API would become straightforward ordinary method calls in C++. Also only a single Box needs to be made.
Something like:
use std::mem;

type MyBuilderRs<'a> = self::MyBuilder<'a>;

#[cxx::bridge]
mod ffi {
    struct MyBuilder<'a> {
        rs: Box<MyBuilderRs<'a>>,
    }

    extern "Rust" {
        type MyBuilderRs<'a>;

        unsafe fn new_builder<'a>() -> MyBuilder<'a>;

        unsafe fn param1<'b, 'a>(
            self: &'b mut MyBuilder<'a>,
            param1: &CxxString,
        ) -> Result<&'b mut MyBuilder<'a>>;

        unsafe fn param2<'b, 'a>(
            self: &'b mut MyBuilder<'a>,
            param2: &'a CxxVector<u8>,
        ) -> Result<&'b mut MyBuilder<'a>>;

        unsafe fn build(self: &mut MyBuilder) -> Result<Vec<u8>>;
    }
}

impl<'a> Default for MyBuilder<'a> {
    fn default() -> Self {
        MyBuilder::new()
    }
}

fn new_builder<'a>() -> ffi::MyBuilder<'a> {
    let rs = Box::new(MyBuilder::new());
    ffi::MyBuilder { rs }
}

impl<'a> ffi::MyBuilder<'a> {
    fn param1(&mut self, param1: &CxxString) -> Result<&mut Self> {
        *self.rs = mem::take(self.rs.as_mut()).param1(param1);
        Ok(self)
    }

    fn param2(&mut self, param2: &'a CxxVector<u8>) -> Result<&mut Self> {
        *self.rs = mem::take(self.rs.as_mut()).param2(param2);
        Ok(self)
    }

    fn build(&mut self) -> Result<Vec<u8>> {
        Ok(mem::take(self.rs.as_mut()).build())
    }
}

Full compilable version: https://gist.github.com/rust-play/b38f01c8e63ab29aef3451f4606bac87
(Make sure you are using at least cxx 1.0.39 and cxx-build 1.0.39 for this, since the most recent releases have some fixes related to the use of explicit lifetime annotations.)

What is that:
type MyBuilderRs<'a> = self::MyBuilder<'a>;

I'm discovering something new in Rust here :D

(I was off last week hence the late answer):
Re the lifetime issue: It's because I need to transform the Vec<u8> into a type that doesn't belongs to me and don't have anything to construct it with a tie to a lifetime (https://docs.rs/picky/6.2.0/picky/key/struct.PrivateKey.html) So I guess until we got that, I can't get out of this lifetime issue (I think, or maybe there's another Rust pattern that I don't know of)


Print object diff in ValidateUpdate webhook call

Knowing what is changing in each resource update helps troubleshooting why a resource keeps reconciling.

abandoning in favor of #503


Masonry

[ x] I have followed (at least) the PR section of the contributing guide.

Add Masonry Component

fixes: https://github.com/mui-org/material-ui/issues/17000
TODO:

create better documentation
Create unit testing (I'm not familiar with Chai, so I would appreciate someone with more knowledge in this topic)

when
https://github.com/mui-org/material-ui/issues/23885 is done
we should either add examples on how the parent component can use the hook to send the current columns count
or use it inside of the component and allow a new param similar to:
https://next.material-ui.com/system/basics/#responsive-values

closing due, wrong title


Design change suggestions

Per Chris' request, I am including my design suggestions to better align with the brand guidelines.

Please use this logo (.svg) (.png) instead.
Also, try and use colors from the color palette. So perhaps:
Left column has background #DADFE1 or #BBD7D8 with text color #282728. Highlighted and active menu links in #9B0000.
In the content area, normal white #ffffff is good, otherwise #f7f7f7. Text color #282728.
Text fonts should be Montserrat for headings and Atkinson Hyperlegible for body.

Thanks, @navin2uw! Would anyone from @UW-Madison-DataScience/nexus-developers be willing to tackle these changes? I'm trying to get Nexus ready for launch by the ML Marathon kickoff date (7/25). The earlier the better!

@navin2uw what about the dark mode color scheme?

For the logo, are we sure we want to lose the tagline? What we're using right now is a transparent version of the secondary with the tagline.

Indeed, the look of the primary logo on a red background looks a bit clunky with the light sidebar theming:

I can think of 3 alternatives:

Make the sidebar background red. In that case we will need to think about a contrasting color choice for the sidebar elements and active links in the sidebar.
Use the secondary logo and make the sidebar background white.
Use a transparent version of the secondary logo (this is currently missing from our brand files)

Thanks for tinkering with this, @sverchkov. I agree that version looks clunky. I think option #3 might be best. The concern with the tagline was that it doesn't contrast well when viewed in the dark theme, and it's a little small to read in general. @navin2uw when you have a sec, could you upload the illustrator/indesign file you used for the logo to Google drive? I can export the transparent version from there.
We might might to explore adjusting the color for the dark theme just slightly so it contrasts better with the logo red.

Ohhh I must have overlooked making transparent versions for those. So, @qualiaMachine, I designed the logo in Canva; if you follow the instructions under the Badges section in my offboarding document, you can also access all the versions. You might have to activate the free trial. Otherwise, I would just run the current version in our files through a transparency maker online, or in Illustrator, if that's easier.


No config flow

The docs say I should get a configuration flow but I get this instead

I've mistakenly thought that HACS shows the README file from the current released but instead it shows the one in the master branch. Yesterday #8 landed on master, introducing config flows and a new README but this will be available just after we release Lightener v2.
I've reverted the README change with 785bf48 and I'll reintroduce it once v2 is released.

Thanks for the quick response


Clear from duplication response/types.go

To fix one error in the Primary key in User, I had to dig into a pile of lines.
It will be necessary to correct this.

here a lot of work.


prepare_table does SDK handle this? If so migrate to it

          @visch @sebastianswms this is great!

One thought when I saw this though was that I worked on similar improvements in the SDK (re: https://github.com/meltano/sdk/pull/1779), not sure if its exactly the same or not. Maybe you've already done this recently but you might want to compare what youre doing in the overridden methods here to make sure its not already done in the SDK for you. Its been a while since this target was created and the SDK has come a long way. Overridden methods wont get to take advantage of ongoing improvements so removing them if theyre no longer needed could be a beneficial.
Originally posted by @pnadolny13 in https://github.com/MeltanoLabs/target-postgres/issues/228#issuecomment-1836236297

I gave it a couple hours and wasn't able to get a reasonable implementation with the SDK's new prepare_table(). Many of the methods in target-postgres are overridden and have different expectations for input parameters than what is found in the SDK, meaning that it would take a lot to "unwind" the current target-postgres implementation (not as simple as just removing the prepare_table() override).
Based just on comparing the two codebases visually, I expect that the SDK does not address the same problems as #228. Following the path of execution, it's still O([number of columns]) db queries to prepare a table. Caching would speed things up after the initial run, but it would still fundamentally requires a large number of queries to set up.

Thanks for looking!