Problems with host and basePath

Hello,
I noticed some problems in the interpretation of the host and basePath parameters.
Suppose I have a gateway stage named mystage for the api api.example.com and a base path /v1.
A possible url could be: https://api.example.com/mystage/v1/myresource
To be able to generate correct documentation from the swagger file I should use this configurations:
host: "api.example.com"
basePath: "/mystage/v1"
But this arises a problem: when I use the importer it creates a "mystage" resource under root and when I deploy the api the final url becomes:
https://api.example.com/mystage/mystage/v1/myresource
which is wrong because of the double "mystage" resource.
The aws gateway exporter in the aws console resolves this problem by putting the stage name in the host parameter, like this:
host: "api.example.com/mystage"
basePath: "/v1"
but the problem with this configuration is that the host parameter written this way breaks the swagger 2.0 specifications (https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/2.0.md).
How could this be resolved? As a hint, if I recall correctly, version 1.2 of the importer did not have this problem but I could be wrong.
I hope I explained myself sufficiently,
Thanks,
Franco

Hi Franco,
Thanks for reporting. This is a known incompatibility between the exporter and importer. Currently the importer assumes the deployment stage is not a part of the API definition.
The API Gateway concept of Stage is not something that maps directly to the Swagger spec.
We're thinking of using the basePath field exclusively for the deployment stage for import and export, and enforcing that it can be only a single path element.
Any resource base path elements would need to be prepended in the individual paths.
Does this make sense? What would your preferred behavior be?

Hi, thanks for the answer. Sorry, I didn't know this was already known.
What do you think about adding an extension for the deployment stage? For example it could be stripped from the basePath to create resources.
For example something like:
host: api.example.com
basePath: /mystage/v1
x-aws-deployment-stage: /mystage
this would strip "/mystage" from the basePath and create resources starting from "/v1".
Generated documentation would be correct and to my knowledge will comply to swagger specification.
Thanks,
Franco

That wouldn't work as the generated documentation and tools built on the Swagger spec would be incorrect - the URL generated wouldn't include the stage, which is required to invoke an API.

Sorry, I don't follow you, to my knowledge the generated documentation would ignore the x- parameter  and the final url would be something like:
https://api.example.com/mystage/v1/my_resource
on both the documentation and the deployed api...
The x parameter it would be used just to create resources on the api gateway and create the correct url at deployment.
Franco

Sorry I didn't see that you had the stage in the basePath as well.
Yes I think it makes sense to include the stage name as the first element of basePath. I'm not sure if we need the extension at all in that case. We might want to have a flag in the importer to opt out of "use stage in base path" in case people don't want to associate stage information in their swagger file.
To summarize:

Export should export stage name in the base path, not in the host
Import should use the stage from the base path, or alternatively from an input parameter if "use stage in base path" is false.
The stage element of the base path should be excluded from the resource paths when creating resources

Sound good?

Related to https://github.com/awslabs/aws-apigateway-importer/issues/140

Sounds absolutely good, either extension or flag are good to me!
Thanks,
Franco

I've run into the same problem. I borrowed your code a while back to create a Gradle plugin -- currently used internally and not fully tested or supported so I haven't published it -- and was thinking about using the extension property as a solution. I think that is a more portable solution than the command line flags since the Swagger spec will be fully valid and the stage stripping, which is specific to API Gateway, would be documented as an x-aws-... extension in the spec itself.
I lean towards that method as well because it means other tools, such as my Gradle plugin, can leverage the same extensions as this command line tool to accomplish the upload in a consistent manner.

Swagger/OpenAPI import is now generally available in the API Gateway REST API, the AWS CLI and all AWS SDKs. You can also import and export Swagger definitions using the API Gateway console. This release addresses many of the open issues and feedback in this repository.
I would encourage you to migrate your workflow to the standard AWS tools. aws-apigateway-importer will receive minimal support from the API Gateway team going forward.
Any feedback or issues with the new importer should be directed to the official API Gateway forums.
Thanks,
Ryan


Updated various Docker items

Hey, I just made a Pull Request!
Updated various Docker items to make it easier to get a working POC/Demo if Backstage up and running. This includes the following changes:
Changes to @backstage/create-app

Updated to copy the examples folder in the Docker container
Updated app-config.production.yaml to include the locations config for the included examples

Changes to documentation

Updated Docker docs to copy examples folder in the Docker container for host and multi-stage builds
Updated Docker docs to include the app-config.production.yaml file when calling node to start up the app
Updated Docker docs to work for the new backend system when splitting out the frontend
Updated Catalog Configuration section on file locations to include a note on how to use this in a Docker container

:heavy_check_mark: Checklist

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

Hi @Rugvip, these are some of the items that came up during the Framework SIG last week - July 23rd. The would help those trying to get a POC/Demo up and running at their Organization easily by making sure the examples are included.
There's still a gap around using Guest auth but I think we've done a good job of documenting the need to install an auth provider. Obviously everything can always be improved but this is a step forward. 🚀


fetch all archived threads (fixes #33)

Pull Request
Describe it here:
...
I have made sure all the things still work:

[ ] The index page and privacy policy page is still served
[ ] The sitemap isn't broken.
[ ] The guild listing ((example))[http://localhost:8084/592399417676529688] is still functioning
[ ] A guild's message listing ((example))[http://localhost:8084/592399417676529688/1015021717900513363] is still functioning.
The following post pages are still functioning:

[ ] Why the Slash Commands? Why aren't my images working? (very complete page that showcases most of the features)
[ ] Post your oshi!.. THE FORUM (the largest page that we serve at over 4,448 messages)
[ ] Any but not all of the posts in the test forum

[ ] Finally, it's curtious but not required to check if the website still renders correctly on an older browser. RetroZilla, based on Firefox 2.0, is the current standard If you do this feel free to provide a screenshot.

You didn't check the sitemap to be sure it works.
I've merged your change into #69, on which this does work.


[ace] Fix missing cpp files

Install all cpp files, we have a lot of source files with inline methods. At some point we should try to use the MPC prj_install support as alternative

What does your PR fix? Fixes #11707

The osg regression is fixing in #11645.

/azp run


optimizer: allow self-join without hash exchange

The distribution of StreamTableScan is UpstreamHashShard, where we're unknown of the distribution since different tables may use different consistent hash vnode mapping.
With #6098, we now have the table_id in the UpstreamHashShard. If we're doing a self-join, we can avoid the hash exchange before them and make the output UpstreamHashShard as well. cc @chenzl25
https://github.com/risingwavelabs/risingwave/blob/a9d668ccb0a42379c4c672f614b2f2691e91cf5d/src/frontend/src/optimizer/plan_node/logical_join.rs#L897-L918
dev=> explain create materialized view mv as select t1.v from t t1, t t2 where t1.v = t2.v;
                                                              QUERY PLAN
---------------------------------------------------------------------------------------------------------------------------------------
 StreamMaterialize { columns: [v, t._row_id(hidden), t._row_id#1(hidden), t.v(hidden)], pk_columns: [t._row_id, t._row_id#1, v, t.v] }
 └─StreamHashJoin { type: Inner, predicate: t.v = t.v }
   ├─StreamExchange { dist: HashShard(t.v) }
   | └─StreamTableScan { table: t, columns: [v, _row_id] }
   └─StreamExchange { dist: HashShard(t.v) }
     └─StreamTableScan { table: t, columns: [v, _row_id] }
(6 rows)

Same for batch join.

Yes. This optimization will cause a fragment contains more than one chain operator and we need to take care.

a fragment contains more than one chain operator and we need to take care

Yes. I believe there will some problems with the current MV on MV creation reporting since we're using the actor id. 😢

Resolved by #9320


Report Emails

Issue type
[x ] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version:
NetBox version:

Description
Would it be possible to setup some form of emailing of reports, or an indication that a report was run? This would be good so that management doesn't have to go into Netbox and parse out what they're looking for, and then run the report. I don't think the database would need to be touched unless you wanted to track emails sent.

There will likely be many things people want to do after running a report: sending an email, writing a log, calling a webhook, etc. These are all possible now by overriding the run() method, but it would be more convenient to add a post_run() method which report authors can more easily extend.
Related, here's an example showing how to send email in Django. The configured list of administrators is available at django.conf.settings.ADMINS.

Given there there is consensus that #81 will rely on Django signals, would it also be prudent is put in the effort here to fire signals on report completion?

@lampwins I'll defer the signals work until we have a chance to take a look at the whole project and go through adding signals everywhere they need to be, for both #81 and #1127.


Exposed UserManager methods wrapped by AspNetIdentityManagerService

Summary of the changes

Exposed UserManager methods GeneratePasswordResetTokenAsync, FindByEmailAsync and FindByNameAsync.

#28

Summary of the changes

Exposed UserManager method ResetPasswordAsync wrapped by AspNetIdentityManagerServer.
Added ResetPasswordAsync to IIdentityManagerService interface.

#28

Corrected commit comments.


Nep-Nep Connect: Chaos Chanpuru [PCSG00951]

App summary

App name: ねぷねぷ☆コネクト カオスチャンプル
App serial: PCSG00951
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3242
Commit hash: https://github.com/vita3k/vita3k/commit/32b607cb
CPU backend: Dynarmic
GPU backend: OpenGL

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game is intro
Screenshots:

Log
vita3k.log
Recommended labels

Intro

as of https://github.com/Vita3K/Vita3K/commit/1b0e65e66d17202b1ae9f155cfecea802dd58778, the game got a bit further and then showed me a connection error. after looking on Google, the service was shut down back on 2018.
Screenshot

Log
vita3k.log
Recommended labels
intro
connexion request

Infinite loading on vita3k version 3606.

as of Vita3K/Vita3K@1b0e65e, the game got a bit further and then showed me a connection error. after looking on Google, the service was shut down back on 2018.
Screenshot

Log
vita3k.log
Recommended labels
intro connexion request

Same error on the latest version of Vita3K.
The message in Japanese clearly says:
Failed to connect to the server.
Please check your signal status, and if the issue does not improve, the server may be congested. Please try again after some time.


Build fails on Apple Silicon: ld: library not found for -latomic

Please answer these questions before submitting your issue.

What did you do? If possible, provide a simple script for reproducing the error.

Compile openswoole 4.10.0 with php 7.2.x or 7.3.x on a Mac with an Apple Silicon (arm64) processor

What did you expect to see?

successful compile

What did you see instead?

ld: library not found for -latomic
clang: error: linker command failed with exit code 1 (use -v to see invocation)

What version of OpenSwoole are you using (show your php --ri openswoole)?

4.10.0

What is your machine environment used (show your uname -a & php -v & gcc -v) ?

macOS 11 on Apple Silicon (arm64)
php 7.2.34 or php 7.3.33
Problem does not occur with php 7.4.27 or later
Apple clang version 12.0.5 (clang-1<IP_ADDRESS>)
This was caused by 63d95ec9ea3d9e1de5d78cc705b8da04cfd42f7f. Reverting that fixes it.

Because PHP 7.2 & 7.3 are not supported by PHP team, we have removed the tests from OpenSwoole CI.
Reviewing if we still want to support 7.2/7.3, otherwise we will remove 7.2/7.3 versions from package.xml in the next release.

Closed by https://github.com/openswoole/swoole-src/pull/138


This adds a new setting to the S3Bucket called BypassGovernanceRetention, when set to true, the recursive delete of a bucket will set BypassGovernanceRentention to true when calling to S3, thus allowing the bypass of any governance enforcement.
Note: if you are using COMPLIANCE mode this will not work. aws-nuke will also currently fail if any objects are in compliance mode.

:tada: This issue has been resolved in version 3.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

If someone is looking at this and wants to use it on a yaml file, you need to put the following lines :
settings:
    S3Bucket:
        BypassGovernanceRetention: true

Thank you for implementing this :)


Part of Layers didn't display when the map was initialized but became normal when I resize the browser window?

[x] I'm reporting a bug, not asking for help
[x] I've looked at the documentation to make sure the behaviour is documented and expected
[x] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[ ] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet version I'm using: 1.0.2
Browser (with version) I'm using: chrome
OS/Platform (with version) I'm using: ubuntu16.04
step 1
step 2

What behaviour I'm expecting and which behaviour I'm seeing
It shows that the mao just display the layers normally around the top of the map view, like the pic shows below, which left the other part of the view blank.

The console didn't hint any bug info logs, and the situation can be fixed by I resize the window of chrome browser, exactly, any resize operation (excepts zoom and scale in the map) like open the console of chrome can help me get the other layers that didn't display normally at first.
I wonder if there is any potential rule in leaflet css or js can influence the layer's loading behavior?
The codes shows here (I just delete my accessToken and id here):
var baseLayer = L.tileLayer(
		'https://api.mapbox.com/styles/v1/{id}/{z}/{x}/{y}?access_token={accessToken}')

map = new L.map(id, {
		center: L.latLng(39.914,116.396),
		zoom: 12,
		layers: baseLayer
	  })

map.zoomControl.setPosition('topright');

Minimal example reproducing the issue

[x] this example is as simple as possible
[x] this example does not rely on any third party code

Using http://playground-leaflet.rhcloud.com/ or any other jsfiddle like site.

@hijiangtao this sounds very much like a resizing issue. If the map container div changes size after the map is initialized, Leaflet isn't automatically aware of this, and you will have to call map.invalidateSize() to notify Leaflet about the size change.
Leaflet will however notice window resize, and call invalidateSize for you.
So, can you check if invalidating the size fixes this problem for you? Otherwise, please create a playground example illustrating the issue - the code pasted above in itself clearly will not cause this problem, it's more or less the example on Leaflet's front page, and that does work.

Well then, I'm really sorry for that.
invalidateSize method didn't fix it, but this is definitely my problem. I usually put the stylesheets after <body> tag, which means the javascript file will initialize the map first and then change the size of my map container, the problem has been fixed by putting the stylesheets forward into the <header> tag, before the javascript code, thanks very much.
My silly code goes here: gist, the effect above screenshot goes here: playground

@perliedman  Really sorry about putting my bugs in a wrong place, I think it's time to close the silly issue and I will double check my codes and Leaflet documents next time, thanks very much.


[BUG] table.columns(), row with a foreign ref doesn't include table's row.

Describe the bug
A clear and concise description of what the bug is.
A failure is found at extract_table where as it seems not returning a row name of a foreign table reference.
To Reproduce
Steps to reproduce the behavior:

Open up python interpreter with sqlite_database installed.
Copy and execute this code

from sqlite_database import Database, text
from sqlite_database.query_builder import extract_table

db = Database(":memory:")
db.create_table("tbl", [
    text("row1"),
    text("row2").foreign("tbl/row1")
])
db.sql.commit()
table_sc = db.table("sqlite_master").select_one()["sql"]
columns = extract_table(table_sc)
row2 = columns[1]
print(row2.raw_source)

See error

Expected behavior
A clear and concise description of what you expected to happen.
The provided code should return "tbl/row1" not "tbl/"
Screenshots
If applicable, add screenshots to help explain your problem.
N/A.
Desktop (please complete the following information):

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

Kali Linux on Android using UserLAnd, running python 3.11
Ubuntu Linux 22.04 using python 3.11
Additional context
Add any other context about the problem here.
N/A

This is buggy bug. I'd say that i somewhat need a separate test case for query builder not gonna lie.

it was fixed in upstream


Set up authentication fails.

It would be nice to have env variables for authentication enabling, to set username/password, storage engine .. etc.
For guideline I have been using https://github.com/tutumcloud/mongodb/tree/master/2.6
Here is my dockerfile:
FROM mongo:2.6

RUN mongo admin --eval "db.createUser({user: 'myuser', pwd: 'mypass', roles:[{role:'dbOwner',db:'admin'}]});"

The build returns:
MongoDB shell version: 2.6.10
connecting to: admin
2015-08-01T00:59:42.877+0000 warning: Failed to connect to <IP_ADDRESS>:27017, reason: errno:111 Connection refused
2015-08-01T00:59:42.878+0000 Error: couldn't connect to server <IP_ADDRESS>:27017 (<IP_ADDRESS>), connection attempt failed at src/mongo/shell/mongo.js:146
exception: connect failed

Expected result - to build the image and set up new user.

I agree would great to have a variable i could set to enable auth.

Failed to connect to <IP_ADDRESS>:27017

You are getting this error because it takes a bit of time to start up mongo service. It seems people are using something like the following to avoid it:
Dockerfile:
FROM mongo:3.2.0
COPY setup.sh /setup.sh
RUN /setup.sh

setup.sh:
#!/bin/bash

mongod --dbpath /data/db &

RET=1
while [[ RET -ne 0 ]]; do
    echo "=> Waiting for confirmation of MongoDB service startup"
    sleep 5
    mongo admin --eval "help" >/dev/null 2>&1
    RET=$?
done

ADMINUSER=user
ADMINPASS=pass

echo "=> Creating an admin user in MongoDB"
mongo admin --eval "db.createUser({user: '$ADMINUSER', pwd: '$ADMINPASS', roles:[{role:'root',db:'admin'}]});"

mongod --dbpath /data/db --shutdown

However, after successfully building this image, and starting a container using this image I can't seem to be able to connect to the database. Anybody has idea why?

I also think it would be great to have a variable I could set to enable auth.

@xgdgsc, like https://github.com/docker-library/mongo/pull/145? (Still fixing bugs added by this, which is why it is not documented).

Closing old issue, fixed by #145. Feel free to comment if you feel this was closed in error.


extension nullable to check a box has no value or has a default value.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks for the interest in adding new APIs. All new public APIs have to go through the process documented here: https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md
Could you please start by opening issue in corefx?


Unicode Emoticons in Project Titles disable links to S3 files in Project Logs

Reported on the 0.45 Trello testing board
Steps

Go to a project you have admin access to that has a project name not containing unicode emoticons
Go to the project setting page and configure S3 for the project
On the Project overview page upload a file to the S3 folder
Refresh the page and look at the project logs
Confirm that you can see the filename that was just uploaded and that you can click on the link in the log
Go to the Title of the project on the project overview page
Click on the title to edit the name
In the text input field that appears, edit the project name to one that contains an unicode emoticon. Good examples are here http://unicodeemoticons.com/index.htm
Click the check mark to save the changes to the project title
Return now to the project log
Find the file that you recently uploaded to the S3 folder. Try to click on the filename

Expected
I would expect the Project title to have no effect on the project logs and links to S3 files within.
Actual
When the project title contains unicode emoticons the links to S3 files in the project logs are no longer available.

Rather a random edge case, eh? :smiling_imp: I'll tag w/Discuss

Closed


Scripts should be easier to upgrade using godot 3 to 4 upgrader

Godot-xr-tools uses numerous scripting approaches which don't work well with the godot 3 to 4 upgrader. These include:

Rename PlayerBody move_and_slide() function to move_body() as the name-collision confuses the upgrader
NodePath default argument values can no-longer be empty strings - instead replace with NodePath("")
GDScript 2 doesn't do as good a job with type-inference so prefer explicit types
Typed-exports don't work, so replace "export (SomeType) var x" with "export var x: SomeType"

Changes to aid in auto-conversion have been merged, and additionally the scripts have all been aligned between the 3.x and 4.x branches.


not working with pizigate (zigbee) on gpio

Hi
Since I installed a Pizigate on my RPi4 B+, the sensor.mitemp_bt didn't work
I tried to set up the BT controler with the hci_interface variable, without succes
HomeAssistant 0.110.4 on Rpi4 B+
Pizigate firmware 3.1c, on GPIO, using Port /dev/ttyS0
Bluetooth is NOT disable on the config.txt
RPi BT should be on /dev/ttyAMA0

What do you mean when you say that the component is not working? Is there any error recorded in the log?
I have no experience with PiZigate, but judging by its documentation, to work on RPi4B+ you do not need to turn off bluetooth, so everything should work. In what I was able to find out about this device, I did not find other reasons for bluetooth failure, except for potential problems in the field of electromagnetic compatibility (radio interference and other related problems associated with the physical proximity of both modules and antennas, for example).
You did not provide any information about the state of your system: you need to look at system logs, try to diagnose the status of the bluetooth subsystem using command-line utilities, enable debugging mode for the component and watch the HA log, that is, follow the usual diagnostic procedure.
Our FAQ also mentions problems in the operation of the RPi bluetooth subsystem associated with the presence of a connected SSD, for example - it is quite possible that you encountered a problem of the same nature. Please note that such problems do not lead to failure of the component, but affect the normal operation of the RPi bluetooth subsystem, on which the component relies.
In addition to the described, important information is how far your sensors are from the host and have you tried to place the sensors extremely close to the host before concluding that the component is not working?

I mean the component don't work anymore since I installed the Pizigate. And bluetooth is not turn off
I have a sensor very close to my RPi
On the system log :
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] update_ble called
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Discovering Bluetooth LE devices
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Time to analyze...
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Getting data from HCIdump thread
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Spawning HCIdump thread(s).
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] HCIdump thread: Init
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] HCIdump thread: Init finished
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Starting HCIdump thread for hci0
2020-05-31 18:53:38 DEBUG (Thread-10) [custom_components.mitemp_bt.sensor] HCIdump thread: Run
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] HCIdump threads count = 1
2020-05-31 18:53:38 ERROR (Thread-10) [custom_components.mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-05-31 18:53:38 DEBUG (SyncWorker_7) [custom_components.mitemp_bt.sensor] Finished. Parsed: 0 hci events, 0 xiaomi devices.

HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device

This is an operating system error, which means that the hci0 interface does not exist.
You must look for a problem at the operating system level.
What is the output of the hcitool dev command?

Or hciconfig command output.

I'm a noob HA user :( don't know how to use hcitool or hciconfig
new try : switched off the Rpi, unpluged the Pizigate, switch on.
-> mitemp_bt works fine

2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] update_ble called
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Discovering Bluetooth LE devices
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Time to analyze...
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Getting data from HCIdump thread
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] HCIdump thread: joining
2020-05-31 19:49:21 DEBUG (Thread-16) [custom_components.mitemp_bt.sensor] HCIdump thread: main event_loop stopped, finishing
2020-05-31 19:49:21 DEBUG (Thread-16) [custom_components.mitemp_bt.sensor] HCIdump thread: Run finished
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] HCIdump thread: joined
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Spawning HCIdump thread(s).
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] HCIdump thread: Init
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] HCIdump thread: Init finished
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Starting HCIdump thread for hci0
2020-05-31 19:49:21 DEBUG (Thread-17) [custom_components.mitemp_bt.sensor] HCIdump thread: Run
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] HCIdump threads count = 1
2020-05-31 19:49:21 DEBUG (Thread-17) [custom_components.mitemp_bt.sensor] HCIdump thread: Connection
2020-05-31 19:49:21 DEBUG (Thread-17) [custom_components.mitemp_bt.sensor] HCIdump thread: Connected
2020-05-31 19:49:21 DEBUG (Thread-17) [custom_components.mitemp_bt.sensor] HCIdump thread: start main event_loop
2020-05-31 19:49:21 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1105 hci events, 2 xiaomi devices.
2020-05-31 19:50:17 WARNING (MainThread) [zigate] No response after command 0x0010 (20)
2020-05-31 19:50:17 WARNING (MainThread) [zigate] Failed to retrieve zigate firmware version

next step : switched off the Rpi, replug the Pizigate, switch on.
EVERYTHING WORKS FINE !! :D
Don't know why ^^

hciconfig and hcitool are not directly related to the Home Assistant; these are Linux system-wide commands for diagnosing and working with bluetooth interfaces.
You need to learn how to work with the command line in Linux. Look for guides on the Internet or ask in the relevant thematic forums and chats.
Unable to reproduce your problem, I can not judge the reasons for what is happening.
Let's hope that the problem will not be repeated.


Export and import

I wanted to import my wish history to another device, something I had done before with no problem, but this time the pity wasn't accurate. It's still showing the correct date, obtained 4*/5* and pity in the excel file but when I import it, it just shows a bunch of 1s not the actual pity number in the file. As for 5s, it's weirdly low pity depending how many 4 came before.
And when I'm importing onto an already existing data it duplicates the cons of characters based on the pulls imported.
(I also tried to export from, and import to the same device too just to test it out but the pity numbers got lost this way too.)

Pleas open this: https://paimon.moe/settings?download=json then send the json and excel file


Initial implementation of issue 141

This is an initial implementation of issue #141 (add support for multi-license texts to license comparison logic).

Thanks @pmonks - Could you sign-off your commits - or you could also just add add a comment to this PR that you agree to the licensing section of the CONTRIBUTING.md file:  https://github.com/spdx/Spdx-Java-Library/blob/master/CONTRIBUTING.md#licensing
Also - one of the checks in the CI is complaining about a possible null pointer exception - on line https://github.com/spdx/Spdx-Java-Library/blob/180f4a5ac83614f30a7a11f4dd22251aa9c78f76/src/main/java/org/spdx/utility/compare/LicenseCompareHelper.java#L858
An easy fix would be to add a check at the beginning of the method - something like:
	public static boolean isStandardLicenseWithinText(String text, SpdxListedLicense license) {
               if (license == null || if text == null) {
                    return false;
                 }
		// Get match status
		boolean result = false;
		int startIndex = -1;

If you want to add that to the PR, that would be great.

@goneall I fixed the linter issue, and signed that final commit as well. I held off on rebasing all of my earlier commits to sign them, as I've been merging from master as you worked there in parallel, and didn't want to accidentally sign your interleaved commits (git makes this kind of thing way too difficult / error-prone, but I digress...).
Regardless, I assert here that all of my earlier commits were developed personally by me, and that they meet the requirements of CONTRIBUTING.md#licensing.

@goneall Note that the "1 new bug" detected by @sonatype-lift above is a false positive.  license cannot be null on line 863 because of the guard on line 858.

Thanks @pmonks  - I'll go ahead and merge this in.
BTW - I run into similar false positives on the linter from time to time.


[Question]What is the direct download URL for latest dra deb package that is not version dependent ?

Hi,
I came up with this URL to download the latest version of dra but it is version dependent : https://github.com/devmatteini/dra/releases/latest/download/dra_0.6.2-1_amd64.deb
Is there an URL to direct download URL for latest dra deb package that is not version dependent ?

Hi @sebma!
Every release asset have the version in the filename.
May I ask you what you are trying to do, so I can try to help you?
If you want to automate the first installation of dra, I currently use this bash script.
To download the Debian package, you can modify it like so:
TMP_DIR=$(mktemp --directory)
DRA_DEB="$TMP_DIR/dra.deb"

curl -s https://api.github.com/repos/devmatteini/dra/releases/latest \
| grep "browser_download_url.*amd64.deb" \
| cut -d : -f 2,3 \
| tr -d \" \
| wget -O "$DRA_DEB" -i -

sudo dpkg -i "$DRA_DEB"

If you have dra already installed, you can use dra itself to download and install the latest version:
sudo dra download -s "dra_{tag}-1_amd64.deb" -i devmatteini/dra

@devmatteini Thanks 😄

sudo dra download -s "dra_{tag}-1_amd64.deb" -i devmatteini/dra

What is the {tag} meaning in your last line ?

The {tag} is the placeholder part of the untagged asset that is generated by dra untag subcommand.
You can read how it works here: https://github.com/devmatteini/dra#selection
Hope this helps :smile:


Cortx 2.0.0 OVA slow download

I am able to download Cortx 1.0.4 from GitHub Release considerably much faster than Cortx 2.0.0 OVA (from cortx aws?).
Are there better mirrors or links for the new release?
Note: Slow download also means it's easier to fail from interruption.

Hi @mukul-seagate11 do you know if there is a faster way to download this?

Hi @mukul-seagate11 do you know if there is a faster way to download this?

@hseow-seagate, this is expected behavior based on latency where 1.0.4 image is been downloaded from GitHub cloud and 2.0.0 is being downloaded from AWS cloud

Mukul Malhotra commented in Jira Server:

@hseow-seagate, this is expected behavior based on latency where 1.0.4 image is been downloaded from GitHub cloud and 2.0.0 is being downloaded from AWS cloud

Mukul Malhotra commented in Jira Server:

Closing this issue as expected behavior due to latency

Mukul Malhotra commented in Jira Server:

Issue closed

Mukul Malhotra commented in Jira Server:

Closed in GitHub issue


Design tools unable create DbContext with custom constructor using the services provider

I've noticed that design time tools cannot instantiate a DbContext if the constructors doesn't follow a standard pattern (default constructor or with DbContextOptions derived parameter), even if the service provider is able to create the context.
The proposed change only replace:
Activator.CreateInstance(...);

with:
ActivatorUtilities.GetServiceOrCreateInstance(...);

which I think it will fallback to the previous behavior if the service provider is unable to create the context.
A test for checking this scenario has been added.

 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.:x: VladDragnea sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This will only help when your DbContext isn't registered as a service, but it has a constructor that takes services. Is that the case you're trying to fix?

Yes, but not only that. I could also happen when my DbContext is registered as a service, but not via AddDbContext. For example a context with a single constructor that takes a connection string, registered as a service with a factory. It will be provided by the service provider but not discoverable, because the code that looks for it actually looks for DbContextOptions.

@VladDragnea If you have a single constructor taking the connection string, then how will the context created using ActivatorUtilities get the correct connection string?

@ajcvickers the parameters, whichever they are, could be provided by the factory that is registered with the service provider. I've simulated this situation in the test case with a dummy connection string.


Feature/ch673/create external adapter for sportsdataio

Note: leaving out updates for npm dependencies until after initial review so viewing file changes is easier.
Added for CI

Not sure if this has changed but in the past CL said to keep API keys inside the endpoint files and out of config.ts so they dont get logged

README should be updated

@christianagnew
I'm taking point 1 has changed since then as I extended by adding one key/value pair where the other two were already there. I will say I didn't see any API keys in the many times I looked at logs while debugging.
As for 2, I added all the of the documentation around functionality I added.
I added documentation on curling so that 1) there's more examples out there to grab from and 2) because the test cases are still using the default.


Fixed hasOrderByPrimaryKey evaluation

The $hasOrderByPrimaryKey was wrong, so order by ID was being added when it wasn't needed.
select * from `icons` order by `icons.id asc, icons.id DESC limit 40

With the fix;
select * from `icons` order by `icons.id` asc limit 40

The function also validates for raw queries.

A new inspection was created.

A new inspection was created.

The inspection completed: No new issues

The inspection completed: No new issues

A new inspection was created.

A new inspection was created.

@promatik Just tested your solution and works greate.
Pushed a small fix for an issue reported in gitter when using global scopes. The getQuery() method does not return the orders applied in global scopes, while toBase() does. https://laravel.com/api/8.x/Illuminate/Database/Eloquent/Builder.html#method_toBase
Let me know,
Pedro

@promatik Just tested your solution and works greate.
Pushed a small fix for an issue reported in gitter when using global scopes. The getQuery() method does not return the orders applied in global scopes, while toBase() does. https://laravel.com/api/8.x/Illuminate/Database/Eloquent/Builder.html#method_toBase
Let me know,
Pedro

The inspection completed: 3 new issues

The inspection completed: 3 new issues

@pxpm tested the toBase() and it's working as expected 👌
I'm going to move this to ready to merge.

@pxpm tested the toBase() and it's working as expected 👌
I'm going to move this to ready to merge.


Fix for #799

Adds t_start and related properties to ImageSequence;
Also renames "sampling_period" to "frame_duration", as I think this is more meaningful. As ImageSequence was added only recently, I decided against adding a deprecation period for this change.
Note that the important changes are in the first commit; the second commit is just formatting and editing of language.

Hello @apdavison! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/core/imagesequence.py:

Line 44:100: E501 line too long (100 > 99 characters)

In the file neo/test/coretest/test_imagesequence.py:

Line 45:9: E741 ambiguous variable name 'l'

Fixes for NixIO needed...

I think most of the issues with the failing tests are things that try to be general solutions to testing but fall on their face when things change in any meaningful way.  I'd like to make them more flexible and maintainable but I don't know when I'll have time.  I will at some point, though.

Ready for review...

This OK for me.


The login_check example curl does not work on Windows 10

The following (in the example code) does not work (it returns invalid JSON format).
curl -X POST -H "Content-Type: application/json" http://localhost:8000/api/login_check -d '{"username":"johndoe","password":"test"}'
When debugging the code (Windows 10, php bin/console server:run) i see, that i have to change the POST paramaters, to double quotes (else json_decode returns NULL, thus not logging in - using PHP 7.2)
The following works for me on Windows (Windows command prompt and PHPstorm console/GIT bash tested)
curl -X POST -H "Content-Type: application/json" http://localhost:8000/login_check -d "{\"username\":\"johndoe\",\"password\":\"test\"}"

(please disregard the different use of URI path (/api/login_check vs /login_check). I was simply playing around, look at the -d paramater :) Maybe it works just fine on linux/unix based systems. I only tested on Windows 10.

PR welcome to improve the doc in that regard.


Failed to build function with tekton

I am able to build sample functions https://github.com/OpenFunction/function-samples with the following command , google.go.functions-framework is detected correctly:
pack build --builder gcr.io/buildpacks/builder:v1 --env GOOGLE_FUNCTION_SIGNATURE_TYPE=http --env GOOGLE_FUNCTION_TARGET=HelloWorld benjaminhuo/sample-go-func:latest
v1: Pulling from buildpacks/builder
Digest: sha256:889d1cc172467dfb5560c69e5a24d8215804e0fb9ae36e2774f33bc2033ffb8c
Status: Image is up to date for gcr.io/buildpacks/builder:v1
v1: Pulling from buildpacks/gcp/run
Digest: sha256:35c7b9995b7b0ad398e504bc178e38b28626e1ce9052cfeabc8750fc313b4d36
Status: Image is up to date for gcr.io/buildpacks/gcp/run:v1
===> DETECTING
4 of 6 buildpacks participating
google.go.runtime             0.9.1
**google.go.functions-framework 0.9.3**
google.go.build               0.9.0
google.utils.label            0.0.1
===> ANALYZING
Previous image with name "benjaminhuo/sample-go-func:latest" not found
===> RESTORING
===> BUILDING
=== Go - Runtime<EMAIL_ADDRESS>===
Using runtime version from go.mod: 1.15
Installing Go v1.15
--------------------------------------------------------------------------------
Running "bash -c curl --fail --show-error --silent --location --retry 3 https://dl.google.com/go/go1.15.linux-amd64.tar.gz | tar xz --directory /layers/google.go.runtime/go --strip-components=1"
Done "bash -c curl --fail --show-error --silent --location --retry..."  (764.8063ms)
No framework version specified, using default
--------------------------------------------------------------------------------
Running "go get<EMAIL_ADDRESS>go: downloading github.com/GoogleCloudPlatform/functions-framework-go v1.2.0
Done "go get github.com/GoogleCloudPlatform/functions-framework-go..." (2.526341623s)
=== Go - Build<EMAIL_ADDRESS>===
--------------------------------------------------------------------------------
Running "go list -f {{if eq .Name \"main\"}}{{.Dir}}{{end}} ./..."
go: downloading github.com/cloudevents/sdk-go/v2 v2.2.0
go: downloading github.com/GoogleCloudPlatform/functions-framework-go v1.2.0
go: downloading cloud.google.com/go v0.63.0
go: downloading go.uber.org/zap v1.10.0
go: downloading go.opencensus.io v0.22.4
go: downloading github.com/google/uuid v1.1.1
go: downloading github.com/lightstep/tracecontext.go v0.0.0-20181129014701-1757c391b1ac
go: downloading go.uber.org/multierr v1.1.0
go: downloading go.uber.org/atomic v1.4.0
go: downloading github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e
/workspace
Done "go list -f {{if eq .Name \"main\"}}{{.Dir}}{{end}} ./..." (2.416441543s)
--------------------------------------------------------------------------------
Running "go build -o /layers/google.go.build/bin/main ./. (GOCACHE=/layers/google.go.build/gocache)"
Done "go build -o /layers/google.go.build/bin/main ./. (GOCACHE=/l..." (1.954832873s)
=== Utils - Label Image<EMAIL_ADDRESS>===
===> EXPORTING
Adding layer 'google.go.build:bin'
Adding 1/1 app layer(s)
Adding layer 'launcher'
Adding layer 'config'
Adding layer 'process-types'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
*** Images (a65b5fafa023):
      benjaminhuo/sample-go-func:latest
Adding cache layer 'google.go.runtime:go'
Successfully built image benjaminhuo/sample-go-func:latest

But when I use tekton to build the same function with gcr.io/buildpacks/builder:v1, google.go.functions-framework cannot be detected even after I add correct function environment to tekton tasks:
  stepTemplate:
    env:
      - name: CNB_PLATFORM_API
        value: "0.3"
      - name: GOOGLE_FUNCTION_SIGNATURE_TYPE
        value: "http"
      - name: GOOGLE_FUNCTION_TARGET
        value: "HelloWorld"

021/01/29 09:17:56 unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied
===> DETECTING
3 of 6 buildpacks participating
google.go.runtime  0.9.1
google.go.build    0.9.0
google.utils.label 0.0.1
===> ANALYZING
Restoring metadata for "google.go.build:bin" from app image
===> RESTORING
===> BUILDING
=== Go - Runtime<EMAIL_ADDRESS>===
Using runtime version from go.mod: 1.15
Installing Go v1.15
--------------------------------------------------------------------------------
Running "bash -c curl --fail --show-error --silent --location --retry 3 https://dl.google.com/go/go1.15.linux-amd64.tar.gz | tar xz --directory /layers/google.go.runtime/go --strip-components=1"
Done "bash -c curl --fail --show-error --silent --location --retry..." (49.726331998s)
=== Go - Build<EMAIL_ADDRESS>===
--------------------------------------------------------------------------------
Running "go list -f {{if eq .Name \"main\"}}{{.Dir}}{{end}} ./..."
Done "go list -f {{if eq .Name \"main\"}}{{.Dir}}{{end}} ./..." (95.171861ms)
--------------------------------------------------------------------------------
Running "go build -o /layers/google.go.build/bin/main . (GOCACHE=/layers/google.go.build/gocache)"
Done "go build -o /layers/google.go.build/bin/main . (GOCACHE=/lay..." (221.209006ms)
=== Utils - Label Image<EMAIL_ADDRESS>===
===> EXPORTING
Reusing layers from image 'index.docker.io/benjaminhuo/sample-go-func@sha256:cdef2bd124e6f8eeff2fcb4bfc63c189cf86bd04f322fbf51e5e91463ac71c30'
Adding layer 'google.go.build:bin'
Adding 1/1 app layer(s)
Reusing layer 'launcher'
Reusing layer 'config'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
*** Images (sha256:5d7e02be54eb0e88db49918b379de6637558a41397214f6e84d91e37ab0370ae):
      benjaminhuo/sample-go-func:latest
Adding cache layer 'google.go.runtime:go'

The tekton stuff is based on the CNB official website example  with some modification
---
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: git-clone
  labels:
    app.kubernetes.io/version: "0.2"
  annotations:
    tekton.dev/pipelines.minVersion: "0.12.1"
    tekton.dev/tags: git
    tekton.dev/displayName: "git clone"
spec:
  description: >-
    These Tasks are Git tasks to work with repositories used by other tasks
    in your Pipeline.

    The git-clone Task will clone a repo from the provided url into the
    output Workspace. By default the repo will be cloned into the root of
    your Workspace. You can clone into a subdirectory by setting this Task's
    subdirectory param.

  workspaces:
    - name: output
      description: The git repo will be cloned onto the volume backing this workspace
  params:
    - name: url
      description: git url to clone
      type: string
    - name: revision
      description: git revision to checkout (branch, tag, sha, ref…)
      type: string
      default: ""
    - name: refspec
      description: (optional) git refspec to fetch before checking out revision
      default: ""
    - name: submodules
      description: defines if the resource should initialize and fetch the submodules
      type: string
      default: "true"
    - name: depth
      description: performs a shallow clone where only the most recent commit(s) will be fetched
      type: string
      default: "1"
    - name: sslVerify
      description: defines if http.sslVerify should be set to true or false in the global git config
      type: string
      default: "true"
    - name: subdirectory
      description: subdirectory inside the "output" workspace to clone the git repo into
      type: string
      default: ""
    - name: deleteExisting
      description: clean out the contents of the repo's destination directory (if it already exists) before trying to clone the repo there
      type: string
      default: "true"
    - name: httpProxy
      description: git HTTP proxy server for non-SSL requests
      type: string
      default: ""
    - name: httpsProxy
      description: git HTTPS proxy server for SSL requests
      type: string
      default: ""
    - name: noProxy
      description: git no proxy - opt out of proxying HTTP/HTTPS requests
      type: string
      default: ""
    - name: verbose
      description: log the commands used during execution
      type: string
      default: "true"
    - name: gitInitImage
      description: the image used where the git-init binary is
      type: string
      default: "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:v0.18.1"
  results:
    - name: commit
      description: The precise commit SHA that was fetched by this Task
    - name: url
      description: The precise URL that was fetched by this Task
  steps:
    - name: clone
      image: $(params.gitInitImage)
      script: |
        #!/bin/sh
        set -eu -o pipefail

        if [[ "$(params.verbose)" == "true" ]] ; then
          set -x
        fi

        CHECKOUT_DIR="$(workspaces.output.path)/$(params.subdirectory)"

        cleandir() {
          # Delete any existing contents of the repo directory if it exists.
          #
          # We don't just "rm -rf $CHECKOUT_DIR" because $CHECKOUT_DIR might be "/"
          # or the root of a mounted volume.
          if [[ -d "$CHECKOUT_DIR" ]] ; then
            # Delete non-hidden files and directories
            rm -rf "$CHECKOUT_DIR"/*
            # Delete files and directories starting with . but excluding ..
            rm -rf "$CHECKOUT_DIR"/.[!.]*
            # Delete files and directories starting with .. plus any other character
            rm -rf "$CHECKOUT_DIR"/..?*
          fi
        }

        if [[ "$(params.deleteExisting)" == "true" ]] ; then
          cleandir
        fi

        test -z "$(params.httpProxy)" || export HTTP_PROXY=$(params.httpProxy)
        test -z "$(params.httpsProxy)" || export HTTPS_PROXY=$(params.httpsProxy)
        test -z "$(params.noProxy)" || export NO_PROXY=$(params.noProxy)

        /ko-app/git-init \
          -url "$(params.url)" \
          -revision "$(params.revision)" \
          -refspec "$(params.refspec)" \
          -path "$CHECKOUT_DIR" \
          -sslVerify="$(params.sslVerify)" \
          -submodules="$(params.submodules)" \
          -depth "$(params.depth)"
        cd "$CHECKOUT_DIR"
        RESULT_SHA="$(git rev-parse HEAD)"
        EXIT_CODE="$?"
        if [ "$EXIT_CODE" != 0 ] ; then
          exit $EXIT_CODE
        fi
        # ensure we don't add a trailing newline to the result
        echo -n "$RESULT_SHA" > $(results.commit.path)
        echo -n "$(params.url)" > $(results.url.path)
---
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: buildpacks
  labels:
    app.kubernetes.io/version: "0.1"
  annotations:
    tekton.dev/pipelines.minVersion: "0.12.1"
    tekton.dev/tags: image-build
    tekton.dev/deprecated: "true"
    tekton.dev/displayName: "buildpacks"
spec:
  description: >-
    The Buildpacks task builds source into a container image and pushes it to a registry,
    using Cloud Native Buildpacks.
    Cloud Native Buildpacks are pluggable, modular tools that transform application source code
    into OCI images. They replace Dockerfiles in the app development lifecycle, and allow for swift
    rebasing of images, and give modular control over images through the use of builders, among other
    benefits. This command uses a builder to construct the image, and pushes it to the registry provided.
  params:
    - name: BUILDER_IMAGE
      description: The image on which builds will run (must include lifecycle and compatible buildpacks).
    - name: CACHE
      description: The name of the persistent app cache volume.
      default: empty-dir
    - name: CACHE_IMAGE
      description: The name of the persistent app cache image.
      default: ""
    - name: PLATFORM_DIR
      description: The name of the platform directory.
      default: empty-dir
    - name: USER_ID
      description: The user ID of the builder image user.
      default: "1000"
    - name: GROUP_ID
      description: The group ID of the builder image user.
      default: "1000"
    - name: PROCESS_TYPE
      description: The default process type to set on the image.
      default: "web"
    - name: SOURCE_SUBPATH
      description: A subpath within the source input where the source to build is located.
      default: ""
    - name: SKIP_RESTORE
      description: Do not write layer metadata or restore cached layers
      default: "false"
    - name: RUN_IMAGE
      description: Reference to a run image to use
      default: ""

  resources:
    outputs:
      - name: image
        type: image

  workspaces:
    - name: source

  stepTemplate:
    env:
      - name: CNB_PLATFORM_API
        value: "0.3"
      - name: GOOGLE_FUNCTION_SIGNATURE_TYPE
        value: "http"
      - name: GOOGLE_FUNCTION_TARGET
        value: "HelloWorld"

  steps:
    - name: prepare
      image: docker.io/library/alpine:3.12@sha256:d7342993700f8cd7aba8496c2d0e57be0666e80b4c441925fc6f9361fa81d10e #tag: 3.12
      imagePullPolicy: Always
      command: ["/bin/sh"]
      args:
        - "-c"
        - |-
          chown -R "$(params.USER_ID):$(params.GROUP_ID)" "/tekton/home" &&
          chown -R "$(params.USER_ID):$(params.GROUP_ID)" "/layers" &&
          chown -R "$(params.USER_ID):$(params.GROUP_ID)" "/cache" &&
          chown -R "$(params.USER_ID):$(params.GROUP_ID)" "$(workspaces.source.path)"
      volumeMounts:
        - name: layers-dir
          mountPath: /layers
        - name: $(params.CACHE)
          mountPath: /cache
      securityContext:
        privileged: true

    - name: create
      image: $(params.BUILDER_IMAGE)
      imagePullPolicy: Always
      command: ["/cnb/lifecycle/creator"]
      args:
        - "-app=$(workspaces.source.path)/$(params.SOURCE_SUBPATH)"
        - "-cache-dir=/cache"
        - "-cache-image=$(params.CACHE_IMAGE)"
        - "-gid=$(params.GROUP_ID)"
        - "-layers=/layers"
        - "-platform=/platform"
        - "-process-type=$(params.PROCESS_TYPE)"
        - "-skip-restore=$(params.SKIP_RESTORE)"
        - "-previous-image=$(resources.outputs.image.url)"
        - "-run-image=$(params.RUN_IMAGE)"
        - "-uid=$(params.USER_ID)"
        - "$(resources.outputs.image.url)"
      volumeMounts:
        - name: layers-dir
          mountPath: /layers
        - name: $(params.CACHE)
          mountPath: /cache
        - name: $(params.PLATFORM_DIR)
          mountPath: /platform

  volumes:
    - name: empty-dir
      emptyDir: {}
    - name: layers-dir
      emptyDir: {}
---
apiVersion: v1
kind: Secret
metadata:
    name: basic-user-pass
    annotations:
        tekton.dev/docker-0: "https://index.docker.io/v1/"
type: kubernetes.io/basic-auth
stringData:
    username: xxx
    password: xxx
---
apiVersion: v1
kind: ServiceAccount
metadata:
    name: buildpacks-service-account
secrets:
    - name: basic-user-pass
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: buildpacks-source-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 500Mi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: buildpacks-cache-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 500Mi
---
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
  name: buildpacks-app-image
spec:
  type: image
  params:
    - name: url
      value: benjaminhuo/sample-go-func:latest #This defines the name of output image
---
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: buildpacks-test-pipeline
spec:
  workspaces:
  - name: shared-workspace
  resources:
  - name: build-image
    type: image
  tasks:
  - name: fetch-repository # This task fetches a repository from github, using the `git-clone` task we installed
    taskRef:
      name: git-clone
    workspaces:
    - name: output
      workspace: shared-workspace
    params:
    - name: url
      value: https://github.com/OpenFunction/function-samples.git
    - name: subdirectory
      value: ""
    - name: deleteExisting
      value: "true"
  - name: buildpacks # This task uses the buildpacks task to build the application
    taskRef:
      name: buildpacks
    runAfter:
    - fetch-repository
    workspaces:
    - name: source
      workspace: shared-workspace
    params:
    - name: SOURCE_SUBPATH
      value: 'hello-world-go' # This is the path within our samples repo we want to build
    - name: BUILDER_IMAGE
      value: 'gcr.io/buildpacks/builder:v1' # This is the builder we want the task to use
    - name: CACHE
      value: buildpacks-cache
    resources:
      outputs:
      - name: image
        resource: build-image
---
apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: buildpacks-test-pipeline-run
spec:
  serviceAccountName: buildpacks-service-account # Only needed if you set up authorization
  pipelineRef:
    name: buildpacks-test-pipeline
  workspaces:
  - name: shared-workspace
    persistentvolumeclaim:
      claimName: buildpacks-source-pvc
  resources:
  - name: build-image
    resourceRef:
      name: buildpacks-app-image
  podTemplate:
    volumes:
    - name: buildpacks-cache
      persistentVolumeClaim:
        claimName: buildpacks-cache-pvc

It seems like the env vars are not being passed correctly. You could try to set those via a project.toml file instead:
https://buildpacks.io/docs/reference/config/project-descriptor/

It seems like the env vars are not being passed correctly. You could try to set those via a project.toml file instead:
https://buildpacks.io/docs/reference/config/project-descriptor/

@jamesward It's a tekton setting issue, and it's fixed following the method described in https://github.com/buildpacks/tekton-integration/issues/4

@jamesward It's a tekton setting issue, and it's fixed following the method described in https://github.com/buildpacks/tekton-integration/issues/4

Solved by https://github.com/buildpacks/tekton-integration/issues/4


Switch to a MIPS-based calling convention

In general...

arguments are passed on the caller's stack frame
callee saves $fp, $ra
there are no return values

However, still lots of inconsistencies, HAX, and very hand-crafted
compilations atm.
Fixes many things, notably component hooks and bounds-tracking.
TODO: fix all the things, optimizations.

👏


Add TS lint rule to force declaring return type

It generally makes it easier to use and understand an API.

Done with #116


ambiguous use of operator '<'

What did you do?
let json = JSON(["name":"Jack", "age": 25])
print(json)
What did you expect to happen?
{
"name" : "Jack",
"age" : 25
}
What actually happened instead?
build/checkouts/SwiftyJSON/Source/SwiftyJSON/SwiftyJSON.swift:1215:51: error: ambiguous use of operator '<'
case (.number, .number): return lhs.rawNumber < rhs.rawNumber
Environment
List the software versions you're using:

SwiftyJSON: 4.3.0
Swift version 5.1 (swift-5.1.2-RELEASE)
Target: x86_64-unknown-linux-gnu

Please also mention which package manager you used and its version. Delete the
other package managers in this list:
Swift Package Manager - Swift 5.1.0 (331fa5cb)
Project that demonstrates the issue
Please link to a project we can download that reproduces the issue. Feel free
to delete this section if it's not relevant to the issue (eg - feature request).
The project should be short, self-contained, and correct example.

I am facing the same issue, but, actually, is this not duplicate of the #1038 ?
Cheers

it is


Safari  CSS transition

Version
2.2.6
Reproduction link
https://jsfiddle.net/uys1vofp/2/
Steps to reproduce
Given a transition name fade-overlay,
in safari, the <transition> component doesn't seem to work when position: absolute; is added to the .fade-overlay-enter, .fade-overlay-leave-to CSS rule.
What is expected?
Second image should smoothly fade in on top of the first image as the first image smoothly fades out.
What is actually happening?
Images switch with no transition.

Have you tried using a transition instead of -webkit-transition

You need to key your images: https://vuejs.org/v2/guide/transitions.html#Transitioning-Between-Elements

I revisited this and the strange behaviour happens because of safari on img elements with the absolute position added at the same time that the transitioning CSS property (opacity here). A workaround is applying the position: absolute in an other class
Here's the barebones bug https://jsfiddle.net/kvdqgwkv/1/

@yyx990803 sorry, I actually meant to add the key attribute. even with the key attribute, it doesn't work. please make sure to visit the second revision of the jsfiddle in safari.

@sunyang713 I think you should open the bug on Safari's or Webkit's bug tracker or web. You can use the fiddle I added

ah, okay. sorry I missed your earlier comment. I didn't realize this was actually a safari issue, not Vue. Thanks.


unsupported ruby version

govuk_puppet appears to be running an unsupported version of ruby here
https://github.com/alphagov/govuk-puppet/blob/master/.ruby-version

Thank you for raising this. We have an item on the roadmap to address this.


VAS Lightweight Ships Calculation Error

Some attributes for the lightweight ships are being calculated incorrectly. For example the activation time skill bonus is being applied twice, resulting in higher DPS than in reality.
This does happen because these attributes exists twice inside the static data. For example for the activation time:

id
attributeName
exampleMod
exampleChangeRange

4032
skillBonusDamageRateMod
/Skill/导弹打击概论/
/Laun/

40320
skillBonusDamageRateMod2
/Skill/导弹打击概论/
/LightShipLaun/

In this case, the 4032 and the 40320 attributes seem to have the exact same values. Also it seems like this is the only one get gets applied falsly, but there are more.

I have added a blacklist of those duplicated attributes. I don't know how/where the game filters out those attributes. But as they seem to be exactly the same as their "original" version, it does not really matter which one of them gets applied.
This is the current blacklist of attributes:


issues/48: exit with code 0 on success

Fixes: https://github.com/komuw/ote/issues/48

Codecov Report
Patch coverage: 33.33% and no project coverage change.

Comparison is base (d7ceddf) 68.84% compared to head (fc51b8d) 68.84%.

:exclamation: Current head fc51b8d differs from pull request most recent head 64f5350. Consider uploading reports for the commit 64f5350 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #51   +/-   ##
=======================================
  Coverage   68.84%   68.84%
=======================================
  Files           6        6
  Lines         504      504
=======================================
  Hits          347      347
  Misses        131      131
  Partials       26       26

Files Changed
Coverage Δ

ote.go
47.82% <0.00%> (ø)

modfile.go
76.04% <50.00%> (ø)

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


Added more meal types

closes #268
to be merged when UI work is done.

you are right

UI work has been merged. so I will merge this


incompatible with targets

NOTE: Before submitting an issue, please make sure to install the latest version of both the vscode extension and the R package. This can usually be achieved by running the command r.debugger.updateRPackage in vscode's command palette (F1).
Describe the bug
Can't debug code that uses the targets r package
To Reproduce

get an example project from the targets official website.
write an entrance script containing tar_make(target_name, callr_function = NULL)
no targets are run, different behaviour than run in a console.

Your R code
Your Launch config
If applicable, the launch config that causes the bug. E.g.:
        {
            "name": "R: tar_make",
            "debugMode": "file",
            "type": "R-Debugger",
            "request": "launch",
            "file": "tar_make.R",
            "workingDirectory": "${workspaceFolder}",
            "allowGlobalDebugging": false,
            "debuggedPackages": ["targets",],
            "commandLineArgs": [
                "--vanilla"
            ],
        }

Expected behavior

the target target_name should be run as it does when invoked by Rscript;
Breakpoints and browser() calls should enter me into the debug console.

Actual behavior
no targets are run as if no targets have been specified.
Desktop (please complete the following information):

OS: windows 10
R Version: 4.1
vscDebugger Version: 0.4.7
vscode-r-debugger Version: 0.4.7

Additional context
Add any other context about the problem here.

If I remove the callr_function = NULL (the targets official way of debugging code), the targets are run normally but no debugging functionality works.


Image marquee

Can I implement something similar to an infinite image marquee?
I tried infinite mode here but it gets weird because of the steps on each slide

Do you want to ask a question? Are you looking for support? Stack Overflow or Swiper Discussions is the best places for getting support

Please, don't use GitHub issues for questions


[Bug] Internal Error occur in GroupBy&Having sql

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Apache Doris 1.2.2 RELEASE
What's Wrong?
I'm trying to add Apache Doris support to SQLancer, this may be a logic bug found by @SQLancer.
You can reproduce this error from the following steps.

data prepare

CREATE DATABASE database0;
USE database0;
CREATE TABLE t0(c0 DECIMALV3(8,2) NOT NULL) UNIQUE KEY(c0) DISTRIBUTED BY HASH (c0) PROPERTIES ("replication_num" = "1");
INSERT INTO t0 (c0) VALUES (0.44777220487594604);
INSERT INTO t0 (c0) VALUES (0.154103085398674);
INSERT INTO t0 (c0) VALUES (0.1650441288948059);
INSERT INTO t0 (c0) VALUES (0.34528547525405884);
INSERT INTO t0 (c0) VALUES (0.1154308021068573);
INSERT INTO t0 (c0) VALUES (0.15414485335350037);

select t0.c0 from t0 group by t0.c0;
The result of this SQL is as follows, which is correct

select t0.c0 from t0 group by t0.c0 having t0.c0 is not null;
But if we add having in sql, an internal error occurs

What You Expected?
SQL select t0.c0 from t0 group by t0.c0 having t0.c0 is not null; should not throw error, and return correct results.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

This bug has been fixed in the new version, please try using an updated version. In the updated version, you can solve this conflict just by adding enable_decimal_conversion = true into the FE configuration file.


Full C# API??

Hello,
So... i just found this page while checking Zed github randomly...
This is true, a full C# API for the zed cam??? Streaming, detection, etc... without C++??
Please tell me is true..., did you have date for release ???? Is this stable actually??
That very awesome guys, thank you !!!!!!

Hi,
This is a wrapper around C++ API. Therefore it calls inside the C++ functions but all your code will be in C#.
It contains all the functions of the ZED SDK 3.1.
This is stable and the first version. Just clone this repository.

Did you have any idea about a date for streaming Function ?

It's already available :
On Sender , use EnableStreaming() function
On Reciever, use initParameters.ipStream and initParameters.portStream

That great thanks.
I can run the Hello ZED sample, that ok.
But i already have a big, big project in C# WPF, did you know a way to add directly a zed.dll into my project reference and just use the DLL like i do usually (GPIO card, joystick, etc..) without cmake, who creating project with ZERO_CHECK, ALL_BUILD etc... ??

Thank you, Can i receive stream from c++ sender to C# receiver? I try but that doesnt work, but receiver work in c++.


fix: use shortname for member children linked style

This PR addresses https://github.com/machow/quartodoc/issues/150 by shortening the names shown for interlinks when using children: linked.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.60%. Comparing base (4739a4e) to head (a98bf47).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #366      +/-   ##
==========================================
+ Coverage   88.46%   88.60%   +0.13%
==========================================
  Files          37       37
  Lines        2931     2931
==========================================
+ Hits         2593     2597       +4
+ Misses        338      334       -4

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


Extra spacing between PIN input labels and fields

Description of problem
There is extra unnecessary spacing between labels and fields for PIN inputs.
Expected behavior
There is no extra space unless it is taken up by an error message when error messages are configured to be above inputs.
Steps to reproduce
Navigate to Change PIN screen
Screenshots and/or log output

Environment

[x] Occurs on Android
[x] Occurs on iOS

Build #:
Android Device Model:
iOS Device Model:
Workaround
Severity

[ ] High
[ ] Medium
[x] Low

Spacing appears fixed (verified on IOS and Android)


🐛 An unknown camera error occured.

What were you trying to do?
An unknown camera error occured.
Reproduceable Code
An unknown camera error occured.

What happened instead?
An unknown camera error occured.
Relevant log output
2023-01-28 14:21:42.888  1292-2082  System.err                                           W  java.lang.NullPointerException
2023-01-28 14:21:42.889  1292-2082  System.err                                           W  	at com.mrousavy.camera.utils.CameraCharacteristicsUtilsKt.getDeviceTypes(CameraCharacteristicsUtils.kt:30)
2023-01-28 14:21:42.889  1292-2082  System.err                                            W  	at com.mrousavy.camera.CameraViewModule$getAvailableCameraDevices$1.invokeSuspend(CameraViewModule.kt:184)
2023-01-28 14:21:42.889  1292-2082  System.err                                            W  	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
2023-01-28 14:21:42.889  1292-2082  System.err                                            W  	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
2023-01-28 14:21:42.889  1292-2082  System.err                                           W  	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
2023-01-28 14:21:42.889  1292-2082  System.err                                           W  	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
2023-01-28 14:21:42.889  1292-2082  System.err                                           W  	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
2023-01-28 14:21:42.889  1292-2082  System.err                                           W  	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
2023-01-28 14:21:43.094  1292-4059  unknown:Re...gWebSocket com.mrs                              W  Couldn't connect to "ws://localhost:8081/message?device=rk3399-Android10%20-%2010%20-%20API%2029&app=com.mrs&clientid=DevSupportManagerImpl", will silently retry
2023-01-28 14:21:43.408  1292-1656  ReactNativeJS                                        I  FaceIdentification Component | Camera permission status: authorized

2023-01-28 14:21:44.902  1292-1656  ReactNativeJS                                     W  Possible Unhandled Promise Rejection (id: 24):
                                                                                unknown/unknown: [unknown/unknown] An unknown camera error occured.
                                                                                [unknown/unknown]: [unknown/unknown] An unknown camera error occured.

### Device

Android 10

### VisionCamera Version

2.13.0

### Additional information

- [ ] I am using Expo
- [X] I have read the [Troubleshooting Guide](https://mrousavy.github.io/react-native-vision-camera/docs/guides/troubleshooting)
- [X] I agree to follow this project's [Code of Conduct](https://github.com/mrousavy/react-native-vision-camera/blob/main/CODE_OF_CONDUCT.md)
- [X] I searched for [similar issues in this repository](https://github.com/mrousavy/react-native-vision-camera/issues) and found none.

I'll try something: https://github.com/mrousavy/react-native-vision-camera/pull/1467

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!


Optimize memory usage on Arduino

The project is reaching the limits of available RAM on the Wio Terminal. Memory needs to be highly optimized.
See the following resources: https://www.forward.com.au/pfod/ArduinoProgramming/ArduinoStrings/index.html#minmem
https://docs.arduino.cc/learn/programming/memory-guide/#sram-memory-optimization

created branch 29-memory to address this issue

mentioned in commit 63657d3a74397a8366a42c6770c0956cb22e9ae9

Dynamically allocated memory is freed
All string literals use F() / are stored in flash memory
String is used sparingly

mentioned in commit a84e5052f487d82ad4e845c5f70e0c1cecd55887

mentioned in commit 543ebae662f4c54b530351835aa65513e7651502

mentioned in commit 117ae549982cea84b130316238fed3d333224722

mentioned in commit 502c6584f080f86b287146618867f2a96914275a

In GitLab by @alexkval on May 14, 2024, 23:15
mentioned in commit 4eeb7ebe50a75b31d28c9106a578036419eb35b1

created branch 29-optimize-memory-usage-on-arduino to address this issue