text:
Refactor get-thin-edge_io.sh script to download the thin-edge.io zip package to install.

Is your refactoring request related to a problem? Please describe.
thin-edge.io is released as multiple different packages.i.e tedge, tedge_mapper, tedge_agent, plugin packages etc, for
for every supported platform (amd64, aarch64, armv7, armhf). This will be too many packages to download.
Also, there are naming conflicts for the same package for different platforms. For example, the tedge package for armv7 and armhf will be named as tedge_0.7.7_armhf.deb. Because of this restriction and the existing release scheme, only one package can be released. So, the installation script will download the same package for both platforms, and hence installation fails.
Describe the solution you'd like
So, the proposal is to use the zipped package per platform as is produced by the GitHub actions. This will help the installation script to download one zip package, unzip and install it on the device.
Describe alternatives you've considered

Additional context

As of now, we will create the tar packages of the Debian packages per architecture. The installation script will download, untar and install those Debian packages onto the device.

Looking on the planned packaging/hosting topics. We can close this as we will focus on way to install the packages via apt-get rather than downloading the packages manually. Also we are looking do publish some official docker images which will also remove the need to install the package on non-debian based linux operating systems.
Due to the current complexities of the maintenance scripts (e.g. the additional scripts/commands that need to be run before the service is usable), preparing a usable tar format is out of scope.

authors: PradeepKiruvale reubenmiller


text:
Config setting to disable auto-registration of entities

Is your feature improvement request related to a problem? Please describe.
When a customer wants to use explicit entity registration, while still using the default topic scheme (te/device/<device-id>/service/<service-id>), there is the possibility of the auto-registration logic conflicting with the explicit registration messages, resulting in the creation of entities with the wrong metadata.
Describe the solution you'd like
When a user has committed to use explicit registration, he should be able to completely disable the auto-registration mechanism using the following config setting:
[c8y.entity_store]
auto_register = false

The default value should be true.
Describe alternatives you've considered
Instead of a mapper specific setting, it could have been global tedge setting as well. But, since the auto-registration is currently handled differently by each mapper, it is better to keep it at a mapper level. In future, we can consider adding a global setting, which can be overridden at mapper level.
Additional context

QA has thoroughly checked the feature and here are the results:

[x] Test for ticket exists in the test suite.
tests/RobotFramework/tests/aws/aws_telemetry.robot
tests/RobotFramework/tests/cumulocity/registration/device_registration.robot
[x] QA has tested the function and it's functioning according description.
[x] Documentation existing
docs/src/references/mappers/c8y-mapper.md

source: gharchive/issue

authors: albinsuresh gligorisaev

license_type: permissive

license_source: github-api


text:
#958 unblocking tedge mapper start up

Proposed changes

unblocked tedge mapper startup. http_proxy was causing the mapper to remain in a while loop trying to fetch an internal device id from cumulocity. this has now been taken out of tedge mapper startup.
the struct in question, C8yEndPoint, now has an uninitialised version (C8yEndPointUninitialised) and the either crate is used to change the state from uninitialised to initialised.
the full proposal is covered here
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)

Paste Link to the issue

Closes to #958

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES

Further comments

I'm surprised that we are discarding the message when initialization fails, even though it is logged the event / software list request will not be triggered again.

Indeed, the fix proposed here unblocks the mapper - that can process local messages even if there is no cloud connections, but makes another issue more likely - if there is no cloud connections when the mapper start then the current software list is not sent to the cloud.

I believe that in this case we should either retry at least or queue the messages to be sent whenever we can initialize properly.

A retry would just push the issue a step further. A queue of messages to be sent would a better fix. If we focus on the issue that the current software list is not sent to the cloud when there is no cloud connections on start, I think we can find some not too complex workaround. But I'm afraid this workaround will break sooner or later.

It was pointed to me by Alex that we foresee this initialisation to happen almost immediately after the mapper starts, but it would not be a case as it will only be initialised when an event requiring HTTP will occur. I believe the right way to go about this is to have the init run as a task and be triggered at the start, but also we would need a caching for messages which cant be send while uninitialised.

Fixing the issue for all the events requiring HTTP requires much more that a queue of messages to be retried. We need to rethink the boundaries between the mapper and the HTTP proxy. Indeed, a method like C8YHttpProxy::send_event or  C8YHttpProxy::upload_log_binary is partial and focused on the HTTP part of the request. In the current code base, when these HTTP related methods return then the mapper needs to finalize the request addressing the MQTT part of the Cumulocity protocol. So, if we let this separation of work unchanged, not only one needs a queue of messages to be processed by the http proxy when the network will be up, one also needs a queue of messages to be further processed by the mapper.
I think the mistake is to cut the responsibilities between the mapper and the http proxy around the transport protocol while Cumulocity uses a mix of HTTP and MQTT.
In conclusion, I think that what to be done is a bit involved:

Reshape the HTTPProxy interface so a request like upload_log_binary is processed in its entirety (getting the JWT token from MQTT, uploading the content to cloud using HTTP, fetching the log event url and sending this url to the cloud via MQTT).
The mapper can then fully delegate these requests to the proxy without being blocked.

Closing this abandoned PR

source: gharchive/pull-request

authors: didier-wenzek initard


text:
Fix typo in mqtt.client.auth.key set error message

Proposed changes
There was a typo in tedge config set mqtt.client.auth.key which sneaked past the MQTT client authentication review.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
This highlights one more place where tedge_config could use some deduplication.

My apologies, seems I missed some of them. Will fix and resubmit.

I was under the impression that I changed mqtt.client.auth.key_file to mqtt.client.auth.key and mqtt.client.auth.cert_file to mqtt.client.auth.cert, but it I was mistaken, that's why I originally corrected it to mqtt.client.auth.key. Now there should only be cafile, cadir, certfile and keyfile, as it is in mosquitto.conf.


text:
App Stuck on Loading

Hello
I followed "https://thingsboard.io/docs/pe/mobile/getting-started/" to test the app on my android (using ThingsBoard Cloud). Everything worked fine on an emulator but when I run the app on my phone (Samsung Galaxy S10), It stuck on loading screen and can't do anything.

Hello @chatchai-bix,
I will close this issue since a significant amount of time has passed since your initial query. However, if the issue is still relevant, please feel free to reopen it and provide additional information, such as the mobile app console output.
Thanks!

authors: chatchai-bix ybeshkarov


text:
Create wallet ID constants file

Doesn't cover all cases, will incrementally replace uses of wallet IDs with these constants

PR-Codex overview
This PR updates wallet constants and types for Coinbase, Metamask, and other wallets. It aligns wallet IDs and connections with the defined constants.
Detailed summary

Updated wallet constants like COINBASE, METAMASK, and others.
Aligned wallet IDs and connections with the defined constants.
Updated wallet connection functions to use the new constants.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

I'm not really sure if it's useful to export a subset of wallet ids as constants. Could be more confusing than simply using the wallet id as string for library user

I'm not really sure if it's useful to export a subset of wallet ids as constants. Could be more confusing than simply using the wallet id as string for library user

The idea is mainly for internal use so we don't have the same manually typed string everywhere that could break with a typo. A user could theoretically import them but they shouldn't need to

I'm not really sure if it's useful to export a subset of wallet ids as constants. Could be more confusing than simply using the wallet id as string for library user

The idea is mainly for internal use so we don't have the same manually typed string everywhere that could break with a typo. A user could theoretically import them but they shouldn't need to

for internal use this makes sense to me, I don't think we should export them from the /exports at all (so they will not be publicly available, I don't think that is useful)

authors: MananTank gregfromstl jnsdls

repo: thirdweb-dev/js


text:
Add props for hiding send, receive and buy buttons on ConnectButton

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR enhances the ConnectButton component by adding props to hide "Send", "Receive", and "Buy" buttons in the details modal.
Detailed summary

Added props to hide "Send", "Receive", and "Buy" buttons in the ConnectButton component details modal
Updated ConnectButtonProps with new boolean props for hiding buttons
Modified Details.tsx to conditionally display buttons based on the new props

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4382  👈
main

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

Join @MananTank and the rest of your teammates on  Graphite


text:
feat: add ecosystem and sponsored transaction pages for in-app wallet

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
The focus of this PR is to enhance the in-app wallet feature by adding expanded navigation links, ecosystem connection, and sponsored transaction previews.
Detailed summary

Added expanded navigation links in the in-app wallet section
Implemented ecosystem connection functionality
Included sponsored transaction previews for in-app wallets

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4719  👈
main

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

Join @joaquim-verges and the rest of your teammates on  Graphite


text:
Firekeeper/prefabs

Vanilla version of Prefab_ConnectWallet

Adding Enums.cs at the SDK level might help bridge the gap between high level calls and inner classes

Added ShortenAddress to Utils, simplified the rest of the code.
Chain enum with custom values as chain ID will be great in the future once supported!

repo: thirdweb-dev/unity-sdk


text:
功能建议 - 自动添加逗号

每次插入关键词时都要手动插入逗号很不方便，尤其是连续插入多个关键词时。建议自动添加逗号（可参考https://github.com/lijialong1313/sdweb-easy-prompt-selector）

我搞错了，原来是Prompt-all-in-one的“Prompt格式”设置在自动去除末尾逗号。但是该设置并不会去除sdweb-easy-prompt-selector的逗号，造成我以为sd-webui-oldsix-prompt没有自动添加逗号功能。

repo: thisjam/sd-webui-oldsix-prompt

license: MIT


text:
Add more mappers

Maybe support more mappers

Remember to fix mapper 4


text:
Include Virtual Rides into Athlete Stats as tickable option

Tickable option from My Profile page or from SX option page

+1. Came here looking for this, but looks like it's already planned. Thanks!

authors: kevinlsw thomaschampagne

repo: thomaschampagne/stravistix

license: mit

license_source: bigquery


text:
Support RedisCache

Any directions / effort for support of redis cache?

Not really. Do you have sample code of such an integration? Unfortunately, I dont use Redis in any of my projects.

I might have a look at it once in the future. Thanks for the link about Distributed Caching.


text:
Turning off Auto Exposure

Using pi2 with latest raspbian (fresh install) and latest allsky (fresh install). Camera is ASI120. When I turn off auto exposure in AllSky the systems becomes unstable. Images begin to be taken as fast as possible. None are clear or usable. CPU maxes out.

I did a fresh instal on a Pi3 and have the same results with either an ASI224 or ASI120. They both start capturing as fast as they can when exposure is turned off. I turned it off in the GUI and through command line.

Can you post your settings here? What's your exposure value?

I tired various exposures. Since it was day time it was using auto automatically.
I did another fresh install on the PI 3. I ran things manually for a bit. Changing the settings.json, stopping and starting all sky each time from command. So far things seem good. I know things are working, but I'd like to re-image one more time and not do the manual testing before installing the GUI.
I'm also going to try again with the PI2 and see.
/Users/Travis/Desktop/Screen Shot 2019-12-27 at 4.11.12 PM.png

Yes day time uses auto-exposure. If you want to emulate night time, you can change your longitude temporarily.
Also, if you're NOT using the GUI, settings.json is located at /home/pi/allsky.
If you are using the GUI, the program uses settings.json located at /etc/raspap/. It gets updated when you save the settings using the GUI. However, you can update it manually as well using a text editor (with sudo).

Yup, I did that. I changed the long in the settings when I was testing manually. After I installed the GUI I just changed it there.
I’ll update this after I do another image and retest the pi2.
Thank you!

Well, I can’t get the pi 2 to work. I had it up and got stretch configured, but won’t come back up after a boot.
The pi 3 is up and I can’t recreate the issues. It’s taking pics fine and not overrunning.
I’ll keep testing and monitor.

I have tried again with a  Pi 2 and 3. I believe I know what the issue was. The default night delay is '10' which equals 0.01 seconds. The day time delay is 5000 or 5 seconds. I believe the very short night delay was the issue.
May I suggest that the night delay default be changed to at least 5000 if not 10000.

The night delay should work fine with a value of 10 milliseconds as long as your exposure is long enough (a few seconds). Otherwise you will cycle really quickly between images and I don't think the RPi will enjoy that.

authors: thomasjacquin uzelessknowledge

repo: thomasjacquin/allsky


text:
Adds lots of time to startup.

The settings view says that this package adds 581ms to startup time. This is the biggest impact of any package that I have installed. It would be awesome if some optimization to start up time could happen :smile_cat:

Can confirm. Its still like this.

I've made some changes and performance improvements in 1.4.3, and I keep getting a steady 12ms activation time. The only exception is the first time Atom fires, and the activation time peaks at around 250ms. I'm thinking this has something to do with something being cached.
I'll continue to improve the activation time sporadically.

:+1 Seems a lot better now. Getting about 10ms load time after the first load.

Performance and startup time is vastly improved in the upcoming v2.0.0.

authors: fiws mythmon thomaslindstrom

repo: thomaslindstrom/color-picker


text:
🛑 UstFlix is down

In 2e17e89, UstFlix ($USTFLIX_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UstFlix is back up in 9288412 after 24 minutes.

repo: thomhans/uptime


text:
Sqlite - Curious in an example adapter?

Hello all,
I'm making a sqlite adapter for a project. Would you guys be interested in using it as an example adapter? I can toss it in a pull request if you're interested. We chose sqlite because it's small, simple, easy, and good for random little projects, hopefully we can help out others.
Interested?

Yeah the more the merrier!

Closing awaiting a PR

I totally forgot about this sorry. I'll see if I can get something together.


text:
Timeouts when retreiving devices from brewpi-script

Apparently the bug that caused #95 is not limited to adding new devices to the controller. I ran into the same bug when attempting to connect to the controller as part of a new installation of Fermentrack. The "retry" code I wrote doesn't appear to be working as expected.
Need to fix this (or change the error message to prompt people to click the "reconnect" button

I thought we had this resolved, but per Mikmonken this is still an issue. Reopening.
Next step is probably going to be to refactor the device queries in brewpi-script to have it synchronously connect to the device and retrieve the device list rather than attempt to do it asynchronously.

seems to occur at around the 6th-7th attempt to connect a new device.

I think I have a solution coded up locally. Once I get somewhere I can test it, if it doesn't cause any issues I'll push it to production.
Basically, I'm making it so that brewpi-script treats the device info the same way it treats control constants/settings. Load them at script startup, and maintain a cache, refreshing the cache every time an update is triggered.
There isn't a way to (easily) make it read synchronously unfortunately without refactoring the entirety of brewpi-script.

authors: Mikmonken thorrak

repo: thorrak/fermentrack


text:
May I take over leap wallet on SDK?

Requested functionality area

[ ] Wallet
[ ] Chain
[ ] Provider
[ ] Other

Details
@ice-chillios
I am a Web3 full stack developer and want to contribute to SDK project.

@promisingdev425 sure, we had no plans in upcoming month to do so.
BTW. you could comment a main issue #379 😅

repo: thorswap/SwapKit


text:
Proper Linux support and testing (ish).

This commit adds a Dockerfile to quickly check that Curry and the generator compiles successfully.
Furthermore, it moves the curry generator into its own target, to support more recent changes to SPM that failed a build when any source files were present in the root of the directory.
Run docker build . to compile the package inside a Linux container.

After merging master, the generator is a non issue due to its implicit dependence on a Mac environment.

Oops, this closed because I deleted my spm branch. @swizzlr mind re-opening this against master and I'll get it merged?

authors: gfontenot swizzlr

repo: thoughtbot/Curry


text:
Issue rendering modal (SweetAlert) in CapybaraWebkit

We use SweetAlert2 (https://sweetalert2.github.io/) in our application. We recently updated to the latest version of SweetAlert (v7.12.11) and unfortunately all our SweetAlert tests are failing.
A relevant change in the upgrade is SweetAlert's move to Promise objects. We know Capybara-Webkit (or rather QT) doesn't support ES6 (and similarly Promise objects), so we've included a polyfill as per SweetAlert's docs (https://cdnjs.cloudflare.com/ajax/libs/core-js/2.4.1/core.js).
The Swal modal renders correctly if we use other Capybara drivers such as Selenium.
While debugging, I see that the Swal modal is indeed created and added to the DOM but the positioning is off and there might be an issue with the z-index. At the end of the day, capybara-webkit doesn't detect the ".swal2-modal" div, even though I can see the div by using page.evaluate_script.
I've created a sample application that demonstrates the issue: https://github.com/synth/swal-capybara-webkit-bug
The versions I'm on are as follows:

ruby 2.3.3p222
Rails 4.2.8
capybara (2.18.0)
capybara-webkit (1.15.0)
capybara-screenshot (1.0.18)
QT: 5.5.1
sweetalert2 v7.12.11

Any advice to tracking this down is appreciated!

Not only does capybara-webkit not support ES^, but it doesn't support a lot of modern CSS either (the last QtWebkit release was basically equivalent to a 6 year old version of Safari), so display issues are going to be common with anything that uses modern CSS.  In this case it would guess it's the use of flex box.

so display issues are going to be common with anything that uses modern CSS

:(
Where can we follow/contribute to here or annullens progress? I thought I remember there was a thread somewhere of people discussing alternatives/workarounds? I can't seem to find it now.
We've been loyal Capybara-webkit users for years, and would hate to abandon it. Thank you so much for all your work. Love live capybara-webkit!

Oh, think I was thinking of this: https://github.com/thoughtbot/capybara-webkit/issues/887

For anyone who might see this, we had success moving to Chrome headless (or selenium_chrome driver) as per this thread: https://github.com/teamcapybara/capybara/issues/1860#issuecomment-305347221
https://github.com/teamcapybara/capybara/blob/adaca2c9c49e403dff37e0405a3982ba4bb2f105/spec/selenium_spec_chrome.rb#L13-L20

@synth https://github.com/annulen/webkit/tree/qtwebkit-stable Is the repo for annulus qtwebkit.  First step is to get it building with a new Qt version and then try building/running specs of capybara-webkit to see what works and what's broken.  I've been meaning to do it for a while but just haven't had the time.

authors: synth twalpole

repo: thoughtbot/capybara-webkit


text:
Fix intermittent failure

Some of the other tests are running asynchronously and were causing
issues if they both used the same sequence name (in this case email).
Running the tests synchronously should fix the issue.
The tests are still plenty fast. Once Ecto supports concurrent tests, we may want to rethink the Sequence module so that it keeps sequences per process so others don't run into this issue with their tests. Fixes #44

:+1:

authors: jsteiner paulcsmith


text:
Update Bundler to v2.5.23

https://github.com/rubygems/rubygems/releases/tag/bundler-v2.5.23

Hi @smaboshe,  I tried testing this with Ruby 3.0.7, rails 6.1 and using bundler 2.3.25.
Everything passes with no problem. The only difference I can see is that the original 6.1.gemfile.lock resolved to FactoryBot 6.4.6, with the current version at 6.5.0.
Would re-bundling, or updating the 6.1.gemfile.lock pass the test?

authors: CodeMeister smaboshe


text:
Overriding a foreign key not working.

I've got a factory the uses a sequence to set the foreign key in a model like this:
factory :player do
  sequence(:team_id) do |n|
    teams = Team.all
    teams[n % teams.size].id
  end
end

If I try the override this attribute in a build command (not tried create or stub yet), it doesn't get overrided:
FactoryGirl.build(:player, team_id: 42)

Also the same code work if I set the team association directly instead of the foreign key.

@badu what version of factory girl are you running?
I just added this test to the codebase and it passes:

describe "overriding sequence values" do
  it "allows overriding a sequence value when setting overrides" do
    define_model("User", :name_id => :string)

    FactoryGirl.define do
      factory :user do
        sequence(:name_id) do |n|
          "John #{n}"
        end
      end
    end

    FactoryGirl.build(:user).name_id.should == "John 1"
    FactoryGirl.build(:user, :name_id => "overridden").name_id.should == "overridden"
  end
end

I'm running 2.3.1, I'll update my gems.

I don't think the test is right, the name_id attribute isn't a foreign key, I never had this issue with normal attributes.

factory girls doesn't check the database to see if it's a foreign key. It does, however, look at the attribute names and handle *_id a bit differently, which is why I wanted to verify it works with name_id.

I've tested it with 2.3.2 and the problem is gone.

authors: budu joshuaclayton


text:
Fix Locals need to be shallow cloned.

Resolves #20. prop_template prebuilds an array of options before handling it off to handle_collection to build. I recall this being somewhat related to faster collection rendering. Unfortunately, the trade off is that we have to be cognizant of how we mutate deeply nested options as those can be the same object. In this case, I missed a required clone on locals.

@kortirso this should fix the issue you're having. Would you like me to add you as co-author as I used your reproduction branch? If so, which email would you like me to use?
Let me know, i can push out a release same day.

hi, @jho406 this solution totally fixes everything, thank you

@kortirso this should fix the issue you're having. Would you like me to add you as co-author as I used your reproduction branch? If so, which email would you like me to use?
Let me know, i can push out a release same day.

I can make PR with test, so there will be some kind of history :)

https://github.com/thoughtbot/props_template/pull/24


text:
ACLs

In this storycard, we expect the behavior to be:
User ACLs:

properties of user:

threebot_id
email
pubkey
ipaddr

behavior of access:

Read
Write

Circle ACLs:

properties of user:

name
description
user_members (corresponds to users)
circle_members (correspondes to circles)

behavior of access:

Read
Write

This means that if a user has write access, but the circle is read-only, the user keeps the right access
if the circle gives right access, all its users have right access, even if the user itself has only read-only access. Thereby, getting write access.

Access Control List
An access-control list (ACL), with  BCDB, is a list of permissions attached to an object. An ACL specifies which users or circles are granted access to objects
User ACLs:

properties of user:

threebot_id
email
pubkey
ipaddr

behavior of access:

Read (r)
Write (w)

Circle ACLs (groups):

properties of user:

name
description
email
threebot_id
user_members (corresponds to users)
circle_members (correspondes to circles)

behavior of access:

Read
Write

example
bcdb = j.data.bcdb.get("test")

#create user
u = bcdb.user.new()
u.name = "kds_1"
u.email = "user1@me.com"
u.threebot_id = "user1.ibiza"
u.save()

#create circle
g = bcdb.circle.new()
g.name = "circle_1"
g.email = "circle1@me.com"
g.dm_id = "circle1.ibiza"
g.user_members = [1] # you can add all users need
g.save()

# create new model and will add our acl to this model
schema = """
    @url = despiegk.test5.acl
    name = ""
    an_id = 0
        """

model = bcdb.model_get_from_schema(schema)
a = model.new()

# that will add right to the circle and all users in the circle
a.acl.rights_set(userids=[], circleids=[1], rights="rw")

assert a.acl.rights_check(1, "r") is True
assert a.acl.rights_check(1, "rw") is True
assert a.acl.rights_check(1, "w") is True

run the test
j.data.bcdb.test(name="acl")

Ran the test :
JSX> j.data.bcdb.test("acls")
Go the following error:

My code is on the latest and this is a new installation.
3BOTDEVEL:3bot:jumpscaleX: git log -1
commit 2de63cfe6d9f79a45d80bd3eebc7e9367ea05e30 (HEAD -> development_jumpscale, origin/development_jumpscale)
Author: kristof de spiegeleer <>
Date:   Sun Jul 28 10:24:14 2019 +0200

    isntaller fix for root install

3BOTDEVEL:3bot:digitalmeX: git log -1
commit dc0feede4c2e389076e78019234c461a6ae17abe (HEAD -> development_jumpscale, origin/development_jumpscale)
Author: kristof de spiegeleer <>
Date:   Sat Jul 27 12:24:08 2019 +0200

    reformat?

@siddiquagig
please check you system or your old data you have
it works good ( i have last commit)

Working now, Tried on a new installation again.

3BOTDEVEL:test:jumpscaleX: git log -1
commit 95f10743d28bc5508036ad5bb263e9fe7a08271b (grafted, HEAD -> development_jumpscale, origin/development_jumpscale)
Author: kristof de spiegeleer <>
Date:   Sun Jul 28 15:52:34 2019 +0200

    Merge branch 'development_jumpscale' of github.com:threefoldtech/jumpscaleX into development_jumpscale

authors: BolaNasr rkhamis siddiquagig

repo: threefoldtech/jumpscaleX


text:
terraform  deployment responds with "account not found"

terraform version:

/opt/mytrunk/terraform/single_node$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding latest version of threefoldtech/grid...
- Installing threefoldtech/grid v0.1.15...
- Installed threefoldtech/grid v0.1.15 (self-signed, key ID 77AB02E5CA9698A3)

Created a "new" account in the polkadot interface in the browser

portal.test.grid.tf recognizes the account

when trying to deploy the single VM I input the mnemonic belonging to the account and I get this error message

~/opt/mytrunk/terraform/single_node$ terraform apply
provider.grid.mnemonics
  Enter a value: always borrow twenty negative call hundred ceiling leisure sunset enact feel frown

╷
│ Error: account not found
│
│   with provider["registry.terraform.io/threefoldtech/grid"],
│   on <input-prompt> line 1:
│   (source code not available)

There is not mention anymore in the example to connect to testnet - do I need to add a line specifying to deploy on testnet.
terraform {
  required_providers {
    grid = {
      source = "threefoldtech/grid"
    }
  }
}

provider "grid" {
}

Needed to create a new account by using the portal.  I figured out that we now use a new key pair type and that the "old" account is no longer valid

@weynandkuijpers I'm getting the same error: "account not found".  What do you mean by "create a new account using the portal"?   I have a new account created and funded on main net. I was able to deploy with it a full vm using the play.grid.tf.
I'm using "threefoldtech/grid v1.5.9"

Found the issue..  Terraform provider is using the wrong network (dev instead of main) and this gives the "account not found" error. See #364

authors: danielcwg weynandkuijpers

repo: threefoldtech/terraform-provider-grid


text:
refactor gridproxy tests

main things to consider while refactoring:

tests need to be somewhat less random, as at some times tests pass, and some other times they don't
use a mock db instead of a real db in tests. this would remove the db running on a container dependency from tests, and should make the tests more robust.
document how tests work since it's currently a bit vague.

was investigating using go-sqlmock, but concluded that this would  add to tests complexity, as it would validate executed sql statements. and since we're using an orm, it should not be our job to test the validity of generated sql statements.
so, i believe it's better to stick with the current approach for testing. maybe just refactor to make it more simple to update, and easier to figure where failures happen

[ ] use "github.com/google/go-cmp/cmp" to log differences between local and remote clients
[ ] remove validateResults and replace with reflect.DeepEquals
[ ] reorganize local client.
[ ] test each field of each filter separately.
[ ] refactor random filter generators
[ ] refactor satisfy fuctions (nodeSatisfies, farmSatisfies, ...) to return an error if a filter field is not handled
[ ] fix bugs in postgres

this issue is related to refactoring gridproxy end-to-end tests. more unit tests need to be added for individual components, but will open other issues for them separately.

Verified,
Tests were refactor and database updated.
Docs were added https://github.com/threefoldtech/tfgrid-sdk-go/blob/development/grid-proxy/docs/test.md.
Workflow is working and passing https://github.com/threefoldtech/tfgrid-sdk-go/actions/workflows/gridproxy-integrationtests.yml.

authors: A-Harby MarioBassem

repo: threefoldtech/tfgrid-sdk-go


text:
error dependencies. error in developing .

i tried download zip, clone, cli gatsby new with this repo link .
whenever i tried to gatsby develop, its all throw error like this . gladly use this starter really like it simplicity.
any help ?

run yarn OR npm install
then run yarn start OR npm run start
you can see in the package.json the start script already has gatsby develop and npm run clean, these commands are necessary to run the website in development. Also make sure your node version is 14 or above

run yarn OR npm install
then run yarn start OR npm run start
you can see in the package.json the start script already has gatsby develop and npm run clean, these commands are necessary to run the website in development. Also make sure your node version is 14 or above

it's already do. i think its not the case.

repo: thriveweb/yellowcake


text:
Include <thrust/detail/memory_wrapper.h>, not

Redo an earlier fix, which was somehow lost.  Fix #1236

Backported to staging branch, was already in perforce gpgpu/rel

authors: allisonvacanti dkolsen-pgi

repo: thrust/thrust


text:
关于预测的函数的理解

请问一下， 如果模型设置的是MS，预测的是OT， inverse = True;   pred_len = 30;
outputs = self.model(batch_x, batch_x_mark, dec_inp, batch_y_mark) ;这个函数是预测batch_x后面30个数据的OT值吗？还是预测的是什么呢？

是的

@bigdata0 谢谢您的回答

repo: thuml/iTransformer


text:
Attachment symbol shown when there is no attachment

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.715
Where did you get the app from?
Other
Android version
14
Device model
Pixel 5a
Steps to reproduce
Hello!
First, I love this app! To all contributors: Thank you so much for all the work done.
As for the issue:
It happens with some of my emails that k9 shows an attachment symbol in the subject line (for example in the inbox view where all the emails are listed) next to the time/date.
However, this email doesn't have an attachment. If I view the header, there's also no attachment listed. If I sort emails with attachments, then those emails are sorted too. As if they have an attachment, but they don't.
I couldn't find any bug report about it but please close my report if it is a duplicate.
Expected behavior
K9 should not show an attachment symbol when there is no attachment.
Actual behavior
K9 shows an attachment symbol when there is no attachment.
Logs
I'd rather not provide logs of my emails/k9 setup. But maybe it's not necessary to have logs here.

Please provide the source of such a message. Feel free to redact the contents. The important thing is the MIME structure.

Thanks. Apparently we display the attachment indicator when a message contains inline images.
Duplicate of #3405

authors: bypear cketti

repo: thunderbird/thunderbird-android


text:
Missing context2vec?

You might consider adding context2vec, which was one of the predecessors to ELMo and inspired much of the work on LM pre-training: https://www.aclweb.org/anthology/K16-1006.pdf

Thanks for your suggestion! We have updated the diagram and README.

repo: thunlp/PLMpapers


text:
🛑 Touhou Group is down

In 9c9a986, Touhou Group (https://touhou.group/) was down:

HTTP code: 403
Response time: 509 ms

Resolved: Touhou Group is back up in e646a60 after 12 minutes.

repo: thwiki/status


text:
config: add tiflash teams for owners config

Related to https://github.com/pingcap/community/pull/645
cc: @purelind @zhangyangyu

/merge

repo: ti-community-infra/configs


text:
pr: adjustments on the project documentation

notes about current deficits
more rules for contribution

related to: #1

Codecov Report

Merging #19 (922279e) into main (df3bf5e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #19   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            3         3
=========================================
  Hits             3         3

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

has been successfully reviewed by PR #10

authors: codecov-commenter rexut

repo: tiacsys/verylittlewire


text:
Mate problem with lone Q vs. K etc.

As promised in the closed issue with no more illegal moves:
Here Talento struggled with mate with a full Q up vs. a lone King.
[Event "Talento Test"]
[Site "RWBC-ESPRESSO Win11Pro Ryzen7 5700G 3.8Ghz 32GB"]
[Date "2024.11.28"]
[Round "151.1.2"]
[White "Monchester_10126-64"]
[Black "Talento_020-64"]
[Result "1/2-1/2"]
[ECO "A80"]
[GameDuration "00:01:15"]
[GameEndTime "2024-11-28T02:00:24.495 Mitteleuropäische Zeit"]
[GameStartTime "2024-11-28T01:59:08.634 Mitteleuropäische Zeit"]
[Opening "Dutch, 2.Bg5 variation"]
[PlyCount "246"]
[TimeControl "15+0.3"]

1. d4 {book} f5 {book}
2. Bg5 {book} c6 {book}
3. Nc3 {book} d5 {book}
4. Bf4 {-0.17/4 0.038} Nd7 {-0.63/4 0.92}
5. e3 {-0.34/4 0.037} Ngf6 {-0.68/4 0.91}
6. Bg5 {-0.77/4 0.057} Qa5 {-0.43/4 0.86}
7. Bxf6 {+0.48/4 0.061} Nxf6 {+0.06/5 0.83}
8. Qf3 {+2.54/5 2.60} b5 {+0.05/4 0.80}
9. Kd1 {+2.40/5 2.94} Be6 {+0.56/4 0.77}
10. Nce2 {+0.74/4 0.067} Ne4 {+0.86/4 0.75}
11. c3 {+2.48/5 1.73} O-O-O {+0.85/4 0.74}
12. Ke1 {+2.82/5 1.52} Qc7 {+0.61/4 0.71}
13. Nf4 {+3.77/5 1.63} Bf7 {+0.69/4 0.69}
14. Bd3 {+1.25/4 0.072} h5 {+0.20/4 0.67}
15. Qe2 {+1.40/4 0.084} Kb8 {+0.26/4 0.65}
16. Bxe4 {+2.14/4 0.079} dxe4 {+1.04/5 0.63}
17. Nfh3 {+2.37/4 0.069} Bc4 {+1.23/4 0.61}
18. Qd2 {+4.08/5 2.11} e5 {+1.36/4 0.60}
19. Qc2 {+4.02/5 1.89} exd4 {+1.88/5 0.59}
20. exd4 {+2.31/4 0.076} Be7 {+1.58/4 0.58}
21. a4 {+4.22/5 3.37} Bd3 {+1.67/4 0.56}
22. Qc1 {+2.40/4 0.079} bxa4 {+1.82/5 0.55}
23. Rxa4 {+2.31/4 0.074} Rhf8 {+1.46/4 0.54}
24. Qd1 {+2.74/4 0.083} h4 {+1.57/4 0.52}
25. Ra1 {+2.48/4 0.079} Qb7 {+1.90/3 0.52}
26. Qd2 {+2.48/4 0.085} Bd6 {+1.64/3 0.50}
27. f3 {+2.97/4 0.086} Rfe8 {+1.93/4 0.48}
28. f4 {+2.22/4 0.10} Bc4 {+2.03/3 0.48}
29. Ra5 {+2.51/4 0.073} Bd5 {+2.18/4 0.47}
30. Ra1 {+2.48/4 0.068} e3 {+2.50/4 0.46}
31. Qc2 {+2.54/4 0.077} Re4 {+2.33/4 0.45}
32. c4 {+2.08/4 0.087} Qb4+ {+3.28/4 0.44}
33. Qc3 {+2.97/5 0.45} Qxc3+ {+3.31/5 0.46}
34. bxc3 {+3.28/5 0.17} Bxc4 {+2.92/5 0.44}
35. d5 {+3.97/5 0.57} cxd5 {+4.33/5 0.42}
36. Nf3 {+3.11/5 0.42} Bxf4 {+3.61/5 0.43}
37. Nd4 {+8.22/5 0.93} Rde8 {+3.58/5 0.41}
38. Nxf5 {+1.22/4 0.038} Be5 {+3.74/5 0.40}
39. Rb1+ {+0.62/4 0.042} Kc7 {+4.43/5 0.40}
40. Rc1 {+0.45/4 0.050} g6 {+4.10/5 0.39}
41. Nd4 {+2.00/5 0.93} Bxd4 {+4.47/5 0.39}
42. cxd4 {+6.34/5 0.40} e2 {+4.53/5 0.40}
43. Ng5 {+6.48/5 0.33} Rxd4 {+4.54/5 0.38}
44. Nh7 {-0.31/5 0.37} Rf4 {+5.20/4 0.38}
45. Ng5 {-1.00/5 0.39} Rg4 {+5.02/4 0.37}
46. Nh3 {+5.65/5 0.44} Rxg2 {+4.92/5 0.37}
47. Nf4 {+5.54/5 0.23} Rg5 {+4.48/5 0.38}
48. Rc3 {+5.37/5 0.45} Re4 {+5.80/5 0.37}
49. Nh3 {+5.37/5 0.53} Rge5 {+5.84/5 0.36}
50. Nf2 {+5.42/5 0.28} Re3 {+5.79/5 0.35}
51. Rxc4+ {+5.42/5 0.29} dxc4 {+6.19/6 0.35}
52. Ng4 {-4.05/5 0.10} c3 {+6.28/5 0.35}
53. Nxe3 {-3.40/5 0.076} Rxe3 {+5.02/6 0.35}
54. Rg1 {-3.25/5 0.017} g5 {+5.78/5 0.35}
55. Rxg5 {-2.37/5 0.038} h3 {+5.61/5 0.35}
56. Ra5 {-2.25/5 0.067} Kd8 {+4.20/6 0.34}
57. Rxa7 {-1.68/5 0.043} c2 {+3.45/6 0.34}
58. Ra1 {-1.40/5 0.064} Rc3 {+3.25/6 0.33}
59. Rc1 {-0.80/5 0.065} Rc4 {+2.98/6 0.33}
60. Kxe2 {-0.40/5 0.035} Rc5 {+2.74/5 0.33}
61. Kd2 {-0.25/5 0.10} Rd5+ {+1.01/6 0.34}
62. Kxc2 {+0.14/5 0.027} Rc5+ {+1.26/5 0.33}
63. Kb1 {+0.17/5 0.046} Rxc1+ {+0.91/6 0.33}
64. Kxc1 {+0.28/5 0.002} Kc7 {+0.95/8 0.33}
65. Kc2 {+0.28/5 0.002} Kd6 {+1.00/7 0.32}
66. Kb3 {+0.25/5 0.004} Kd5 {+1.14/8 0.33}
67. Kc3 {+0.22/5 0.003} Ke4 {+1.44/8 0.32}
68. Kc4 {+0.31/5 0.003} Kf3 {+1.55/8 0.32}
69. Kc3 {-0.54/5 0.004} Kg2 {+2.80/8 0.32}
70. Kc4 {-0.60/5 0.002} Kxh2 {+9.75/8 0.32}
71. Kd3 {-0.65/5 0.002} Kg3 {+9.98/7 0.32}
72. Kc4 {-42.48/4 0.001} h2 {+10.20/7 0.32}
73. Kd5 {-42.51/3 0} h1=Q+ {+10.13/6 0.32}
74. Ke5 {-42.60/3 0} Qh5+ {+10.21/5 0.32}
75. Ke6 {-42.68/3 0} Qc5 {+10.25/5 0.32}
76. Kd7 {-42.74/3 0} Qd5+ {+10.27/5 0.33}
77. Kc7 {-42.57/1 0} Qe6 {+10.38/5 0.32}
78. Kd8 {-42.57/1 0} Qf7 {+10.50/6 0.33}
79. Kc8 {-42.60/1 0} Qe7 {+10.33/6 0.31}
80. Kb8 {-42.62/1 0} Qd7 {+10.80/6 0.31}
81. Ka8 {-42.65/1 0} Kf3 {+10.80/6 0.31}
82. Kb8 {-42.71/1 0} Kg4 {+10.82/6 0.32}
83. Ka8 {-42.74/1 0} Kg3 {+10.82/6 0.31}
84. Kb8 {-42.62/1 0} Qc6 {+11.09/5 0.31}
85. Ka7 {-42.62/1 0} Qb5 {+10.82/6 0.30}
86. Ka8 {-42.65/1 0} Qd7 {+10.82/6 0.30}
87. Kb8 {-42.62/1 0} Qc6 {+11.09/5 0.31}
88. Ka7 {-42.62/1 0} Qb5 {+10.80/6 0.31}
89. Ka8 {-42.65/1 0} Kf3 {+10.48/6 0.30}
90. Ka7 {-42.71/1 0} Ke2 {+10.80/6 0.30}
91. Ka8 {-42.74/1 0} Qd7 {+10.55/6 0.30}
92. Kb8 {-42.71/1 0} Qc6 {+10.80/5 0.31}
93. Ka7 {-42.71/1 0} Qb5 {+10.80/6 0.30}
94. Ka8 {-42.74/1 0} Qc6+ {+10.48/6 0.30}
95. Ka7 {-43.05/5 0.003} Ke3 {+10.80/6 0.31}
96. Kb8 {-42.80/1 0} Kf3 {+11.07/5 0.30}
97. Ka7 {-42.71/1 0} Ke2 {+10.80/6 0.30}
98. Kb8 {-42.71/1 0} Kf3 {+11.07/5 0.36}
99. Ka7 {-42.71/1 0} Qb5 {+10.80/6 0.30}
100. Ka8 {-42.74/1 0} Kg3 {+10.50/6 0.30}
101. Ka7 {-42.62/1 0} Qb4 {+10.80/6 0.30}
102. Ka8 {-42.94/5 0.003} Qb5 {+10.50/6 0.30}
103. Ka7 {-42.62/1 0} Qb4 {+10.80/6 0.30}
104. Ka8 {-42.94/5 0.003} Qe7 {+10.33/6 0.30}
105. Kb8 {-42.62/1 0} Qd7 {+10.63/5 0.30}
106. Ka8 {-42.65/1 0} Kf2 {+10.73/6 0.30}
107. Kb8 {-42.62/1 0} Qc6 {+11.00/5 0.33}
108. Ka7 {-42.62/1 0} Qb5 {+10.80/6 0.30}
109. Ka8 {-42.65/1 0} Qd7 {+10.73/6 0.30}
110. Kb8 {-42.62/1 0} Qc6 {+11.00/5 0.30}
111. Ka7 {-42.62/1 0} Qb5 {+10.80/6 0.30}
112. Ka8 {-42.65/1 0} Kf3 {+10.48/6 0.30}
113. Ka7 {-42.71/1 0} Qb3 {+10.80/6 0.30}
114. Ka8 {-43.02/5 0.002} Qf7 {+10.32/6 0.30}
115. Kb8 {-42.71/1 0} Qh7 {+10.62/5 0.31}
116. Kc8 {-42.94/5 0.003} Qe7 {+10.32/6 0.30}
117. Kb8 {-42.71/1 0} Qh7 {+10.62/5 0.31}
118. Kc8 {-42.94/5 0.003} Qe7 {+10.32/6 0.30}
119. Kb8 {-42.71/1 0} Qd7 {+10.62/5 0.30}
120. Ka8 {-42.74/1 0} Kf4 {+10.65/6 0.30}
121. Kb8 {-42.80/1 0} Qc6 {+10.92/5 0.30}
122. Ka7 {-42.80/1 0} Qb5 {+10.80/6 0.30}
123. Ka8 {-42.82/1 0} Qd7 {+10.65/6 0.30}
{Draw by fifty moves rule}
1/2-1/2

This game does not fit to the issue header, but it is from the same game collection.
With move 41. Bxe3?? it played the only non-winning move, actually a self mate in 5 afterwards.
As it reported move 41 with depth 6, I think it is a bit strange.
[Event "Talento Test"]
[Site "RWBC-ESPRESSO Win11Pro Ryzen7 5700G 3.8Ghz 32GB"]
[Date "2024.11.28"]
[Round "45.1.1"]
[White "Talento_020-64"]
[Black "Monchester_10126-64"]
[Result "0-1"]
[ECO "B40"]
[GameDuration "00:00:43"]
[GameEndTime "2024-11-28T01:21:26.081 Mitteleuropäische Zeit"]
[GameStartTime "2024-11-28T01:20:42.788 Mitteleuropäische Zeit"]
[Opening "Sicilian defense"]
[PlyCount "86"]
[TimeControl "15+0.3"]

1. e4 {book} c5 {book}
2. Nf3 {book} e6 {book}
3. g3 {book} d5 {book}
4. exd5 {+0.22/5 0.93} exd5 {-0.68/4 0.076}
5. Bg2 {-0.10/4 0.89} Qe7+ {-0.37/4 0.068}
6. Qe2 {-0.18/6 0.86} Qxe2+ {+9.25/5 1.14}
7. Kxe2 {-0.23/6 0.83} Bg4 {+2.11/5 1.02}
8. h3 {+0.20/5 0.81} Bxf3+ {+2.02/5 0.81}
9. Bxf3 {+0.73/5 0.78} Nf6 {+2.22/5 0.54}
10. Nc3 {+0.75/4 0.75} Nc6 {+2.22/5 0.72}
11. Bxd5 {+0.73/5 0.73} Nd4+ {+1.20/5 1.64}
12. Kd1 {+0.01/6 0.71} Rb8 {-0.45/4 0.060}
13. Bg2 {+0.33/4 0.69} b5 {+0.25/4 0.049}
14. Re1+ {+0.67/5 0.67} Kd7 {+1.57/5 0.25}
15. Ne2 {+0.72/4 0.65} Nxe2 {+0.45/4 0.065}
16. Kxe2 {+0.92/5 0.63} Bd6 {+1.51/5 1.03}
17. d3 {+0.83/4 0.62} Kc8 {+0.42/4 0.11}
18. Be3 {+0.93/4 0.60} Re8 {+7.91/5 1.86}
19. Rad1 {+1.00/4 0.58} Re7 {+0.17/4 0.076}
20. c3 {+1.13/4 0.57} b4 {+0.40/4 0.064}
21. cxb4 {+1.22/5 0.56} Rxb4 {+0.45/4 0.076}
22. b3 {+1.15/4 0.55} Bb8 {+0.20/4 0.083}
23. Kf1 {+1.31/4 0.53} Re5 {+0.05/4 0.085}
24. Kg1 {+1.41/4 0.52} Rb5 {+0.08/4 0.092}
25. f4 {+1.52/4 0.51} Rh5 {-0.05/4 0.070}
26. g4 {+1.69/4 0.50} Rh4 {+1.80/5 1.33}
27. Bf2 {+4.95/5 0.49} Rh6 {-0.91/5 1.39}
28. g5 {+3.83/5 0.48} Rg6 {-1.60/5 1.33}
29. gxf6 {+2.96/5 0.49} gxf6 {-6.77/5 0.62}
30. f5 {+4.12/5 0.46} Rg5 {-6.74/5 0.59}
31. h4 {+4.18/5 0.45} Rg8 {-7.00/5 0.61}
32. Re7 {+4.29/5 0.47} Ra5 {-1.20/5 0.85}
33. Rxf7 {+4.66/5 0.44} Rxa2 {-1.77/5 0.68}
34. Rxh7 {+4.56/5 0.43} Rb2 {-9.65/4 0.042}
35. Rc1 {+4.83/5 0.42} Kd8 {-1.94/5 0.90}
36. Rf7 {+4.84/5 0.42} Bf4 {-1.85/5 0.86}
37. Rf1 {+4.97/5 0.41} Kc8 {-10.00/4 0.033}
38. Rxf6 {+5.13/5 0.41} Kd8 {-10.40/4 0.042}
39. Rf7 {+5.56/5 0.40} a6 {-10.57/4 0.035}
40. f6 {+4.26/4 0.41} Be3 {-10.34/4 0.030}
41. Bxe3 {+5.21/6 0.39} Rgxg2+ {+M5/5 0.42}
42. Kh1 {-309.96/6 0.39} Rh2+ {+M3/3 0.43}
43. Kg1 {-309.98/7 0.38} Rbg2# {+M1/1 0.28}
{Black mates}
0-1

Both problems came from slow searching speed, in my commit a few seconds ago I made search be faster so it should at least solve the one it made that move where it got checkmated in 5, that only happened because it searched on depth 5, idk why it reported depth 6 but atleast while testing it always found that checkmate on depth 6 yet he went for that move with depth 5, with faster search that should be fixed because he will search greater depths, as for the other one he can't kind any checkmate on the searched depths and so it doesn't decide to move the King, both problems will be eventually fixed with a better evaluation and/or better search and I'm working on it.

authors: rwbc tiago-daniel

repo: tiago-daniel/Talento

license: Unlicense


text:
Question on fastapi on_event (shutdown) hooks for gunicorn-based set-up

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
@app.on_event('shutdown')
async def stop_sqs_clients():
    log.debug('*** Shutting down worker thread ***')
    asyncio.ensure_future(sqs_client.close())

Description
Greetings.

We are running fastapi with gunicorn workers inside docker container.
During startup we need to create an AWS sqs client to listen to a queue
During shutdown we want to be able to close this sqs client before doing a graceful exit
We have used gunicorn workers with a gunicorn_conf.py file
When container starts up we able to see gunicorn worker threads spawning off and each thread hosting a fastapi app, and able to hit the 'startup' event. Ex. -

@app.on_event('startup')
async def handle_start_up_sequence():
log.debug('Handling start up sequence')
asyncio.ensure_future(sqs_client.open())
We even printed the PID to ensure that gunicorn indeed spawned off multiple threads with fastapi instance in each.
However, when gunicorn master/parent thread sends a SIGABORT to worler threads (due to reaching timeout), we are unable to hit the on_event('shutdown') hook, thereby leaving dangling reference of an active SQS client in the worker thread, causing it to result a core dump.
We are looking for possible ways to utilize the shutdown event for gunicorn worker threads. Any leads/references/pointers/documentation would be appreciated.
Thanks in advance.
Operating System
Linux
Operating System Details
No response
FastAPI Version
0.58.1
Python Version
Python 3.9.13
Additional Context
gunicorn==20.0.4

https://github.com/encode/uvicorn/issues/1116

Thanks @Kludex for sharing this. So we still looking for a better and more elegant solution on this, right?

I wouldn't say that... 🤔 I think it's a gunicorn issue, but there hasn't been an explanation on gunicorn's side about it.
In any case, if you feel blocked, you can inherit UvicornWorker, and use https://github.com/encode/uvicorn/pull/1424/.
In any case, not a FastAPI issue.

@Kludex
I hear you. While going to UvicornWorker is a possibility but it is bit late in the game for our current scope of work.
Let me explore.

What do you mean late? If you use gunicorn, you are using that worker anyway...

I am talking about over-all testing and regression risks.

import threading

from uvicorn.workers import UvicornWorker

class CustomWorker(UvicornWorker):
    def _install_sigquit_handler(self, server: Server) -> None:
        """Workaround to install a SIGQUIT handler on workers.
        Ref.:
        - https://github.com/encode/uvicorn/issues/1116
        - https://github.com/benoitc/gunicorn/issues/2604
        """
        if threading.current_thread() is not threading.main_thread():
            # Signals can only be listened to from the main thread.
            return

        loop = asyncio.get_running_loop()
        loop.add_signal_handler(signal.SIGQUIT, self.handle_exit, signal.SIGQUIT, None)

    async def _serve(self) -> None:
        self.config.app = self.wsgi
        server = Server(config=self.config)
        self._install_sigquit_handler(server)
        await server.serve(sockets=self.sockets)
        if not server.started:
            sys.exit(Arbiter.WORKER_BOOT_ERROR)

Something like... I haven't tested.

authors: Kludex thegeekcentaur

repo: tiangolo/fastapi


text:
WSGIMiddleware is deprecated and will be removed in a future release

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from fastapi import FastAPI
from fastapi.middleware.wsgi import WSGIMiddleware
from flask import Flask, escape, request

flask_app = Flask(__name__)

@flask_app.route("/")
def flask_main():
    name = request.args.get("name", "World")
    return f"Hello, {escape(name)} from Flask!"

app = FastAPI()

@app.get("/v2")
def read_main():
    return {"message": "Hello World"}

app.mount("/v1", WSGIMiddleware(flask_app))

Description

fastapi.middleware.wsgi is inherited from Starlette
Starlette will remove starlette.middleware.wsgi in the future (See here)
fastapi.middleware.wsgi also has the deprecation and removal warning due to its import of  WSGIMiddleware (See here)
It is unclear if FastAPI will continue to support WSGIMiddleware from fastapi.middleware.wsgi or whether it too will be removed in the future

How to solve

Please clarify if fastapi.middleware.wsgi and / or WSGIMiddleware will continue to be supported or if it will be removed when Starlette removes it (which it will if no further action is taken)

Update docs to reflect an upcoming removal (if it will be removed)

Suppress deprecation warning from starlette.middleware.wsgi (if wsgi.WSGIMiddleware will not be removed from FastAPI)

[x] I commit to helping implement these changes.

Operating System
macOS
Operating System Details
No response
FastAPI Version
0.85.2
Python Version
Python 3.11.0
Additional Context
Thank you everyone for your hard work!

Opinion on https://github.com/abersheeran/a2wsgi? @tiangolo It's referenced in Starlette docs and is actively maintained

authors: TheJumpyWizard wolfskaempf


text:
🌐 Add Turkish translation for docs/tr/docs/how-to/general.md

🌐 Add Turkish translation for docs/tr/docs/how-to/general.md
Original File
Discussion: #9193

📝 Docs preview for commit d7103709b3a47843d95b6a459f57bee65a291a6e at: https://d99d2760.fastapitiangolo.pages.dev

📝 Docs preview for commit ca6dd224daa11a4d4b7cdeb79c61bae5983795dd at: https://6af2593e.fastapitiangolo.pages.dev

📝 Docs preview for commit 9de87ac638da3d805d5f28f442d7764d307787eb at: https://f09cd66b.fastapitiangolo.pages.dev

📝 Docs preview for commit eaef54ad7e32c3a943132087777ff99a7214a6c9 at: https://ac9678ba.fastapitiangolo.pages.dev

📝 Docs preview for commit 8f6d3061569c9cbba0b64399330d8fa8beb2a489 at: https://20f7e42f.fastapitiangolo.pages.dev

Great. Thanks @hasansezertasan :nerd_face:
And thanks for the help @OzgunCaglarArslan :100:

authors: alejsdev hasansezertasan tiangolo


text:
⬆ Upgrade Starlette from 0.19.1 to 0.20.4

Summary

Upgrade starlette from 0.19.1 to 0.20.4

0.20.2 includes a fix for regression on route paths with colons starlette#1675, I added a test case for custom method.

In order to bump starlette version, FastAPI has to drop support for Python 3.6.
Currently FastAPI supports python 3.6.

In order to bump starlette version, FastAPI has to drop support for Python 3.6.
Currently FastAPI supports python 3.6.

When do you expect to drop support for python 3.6?
It is said that "This is probably the last release (or one of the last releases) to support Python 3.6." in the latest release notes.

It's up to the maintainers of the project. I don't have an answer for when it'd be done🙂

Now https://github.com/tiangolo/fastapi/releases/tag/0.85.0 is released, I close this p-r.

Thanks for coming back to close the PR @SogoKato ! ☕

authors: SogoKato iudeen tiangolo


text:
[QUESTION] is there anything like @app.callback to do a after-command execution cleanup?

I use @app.callback to init my app.
I am wondering now if there is any common way to implement a post-execution-method/handler to finally cleanup some stuff which got initialised in the callback after the app executed the command?
Please let me know.

I haven't stumbled upon anything like that in Typer. Click recomends using Python's native context managers to do so:     https://click.palletsprojects.com/en/8.0.x/advanced/#managing-resources
There is an example of how to use it with click.Context, that however you cannot use, because it looks to me that it was introduced in click 8.0, where typer uses click 7.1, so you could use native with statement.

I found out that Typer class has an argument of result_callback.  It seems that is just used as a result_callback from Click.
https://click.palletsprojects.com/en/7.x/api/#click.MultiCommand
I am attaching a working example:
import typer

def result(executed_command_result):
    print("HELLO AFTER COMMAND")
    print("Function returned: ", executed_command_result)

app = typer.Typer(result_callback=result)

@app.callback()
def cb():
    print("HELLO BEFORE COMMAND")

@app.command()
def cmd():
    print("HELLO IN COMMAND")

    return 44

if __name__ == "__main__":
    app()

authors: Prutheus captainCapitalism

repo: tiangolo/typer


text:
防篡改校验失败，所有服务都不再上报数据了

[wgcloud-agent]2022/07/19 10:08:56 WgcloudAgent.go:429: 防篡改校验失败： 16
[wgcloud-agent]2022/07/19 10:09:09 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16
[wgcloud-agent]2022/07/19 10:13:11 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16
[wgcloud-agent]2022/07/19 10:14:11 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16

你好：
14、agent日志打印【防篡改校验失败】和【防篡改校验错误次数大于10次】的原因说明
这个问题注意几点：
(1) server和agent的主机系统时间差不能大于15个小时，若时间差不超过15小时的时候打印【防篡改校验错误】类似信息，忽略即可
(2) v3.3.5之前版本，server主机的9997端口（这是守护进程wgcloud-daemon-release的默认端口）要开放给agent主机，保证agent主机可以telnet通server的9997端口
v3.3.5或以后版本9997端口已经不需要开放给agent访问
(3) 若是v3.3.5或之后版本，查看server本机是否能正常访问http://localhost:9997获得返回值，如：2faa233a1400201bedc199fe1d8ab393，若server主机的localhost不能使用，可以在配置文件server/config/application.yml，将配置项daemonUrl: http://localhost:9997 中的localhost改成server主机ip
(4) wgcloud-server-release.jar不要修改
(5) server和agent要保持同一个版本
(6) server端的守护进程（wgcloud-daemon-release）不要关闭,特别是Windows注意不要关闭守护进程窗口。若是Linux，查看此进程是否存活（ps -ef | grep wgcloud）
还有一种可能是server部署在Windows，不小心左键点击守护进程的窗口，进入编辑模式了，右击恢复就好了
如果因为此原因的话，重启server（守护进程会随着server启动）后，1小时内所有agent会陆续恢复上线，也可以手动重启agent（立即上线）
(7) server如果运行在arm、龙芯等系统，需要将守护进程wgcloud-agent-release替换为对应的版本，点击下载【2】
(8) 如果server长时间没有运行，那么当server重新启动后，agent会在1小时内陆续自动恢复上线，不用重启agent
Good Luck
WGCLOUD

------------------ 原始邮件 ------------------
发件人:                                                                                "tianshiyeben/wgcloud"                                                                                @.>;
发送时间: 2022年7月19日(星期二) 晚上8:00
@.>;
@.***>;
主题: [tianshiyeben/wgcloud] 防篡改校验失败，所有服务都不再上报数据了 (Issue #49)
[wgcloud-agent]2022/07/19 10:08:56 WgcloudAgent.go:429: 防篡改校验失败： 16
[wgcloud-agent]2022/07/19 10:09:09 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16
[wgcloud-agent]2022/07/19 10:13:11 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16
[wgcloud-agent]2022/07/19 10:14:11 WgcloudAgent.go:287: 防篡改校验错误次数大于10次，不再上报数据： 16
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

authors: tianshiyeben uuflyer

repo: tianshiyeben/wgcloud


text:
建立文件夹出现异常，使用官方客户端能够建立

aliyunpan:test 开心杨99$ mkdir 301003-#网易cc- #小燃燃 竖屏收藏。 创建文件夹成功:  /test/301003-#网易cc-
建立的文件夹只有部分。301003-#网易cc-

后面确定了下具体原因，是因为文件名中带空格。
我使用的平台是windows11。

后面确定了下具体原因，是因为文件名中带空格。
我使用的平台是windows11。

加引号即可
$ mkdir "301003-#网易cc- #小燃燃 竖屏收藏"

authors: DolphinSh tickstep

repo: tickstep/aliyunpan


text:
feat: filter unregistered pubsiher_handle

Description

Fixed a problem in which the filter function did not work due to a change from the address at initialization during application execution. This problem occurs when using RCLCPP_INFO, etc.
Related links

Tier4 INTERNAL LINK
Notes for reviewers

Pre-review checklist for the PR author

[x] I've confirmed the contribution guidelines.
[x] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been properly tested.
[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 59.98%. Comparing base (75e1c3f) to head (c4dd143).
Report is 3 commits behind head on main.

Files
Patch %
Lines

CARET_trace/src/tracing_controller.cpp
0.00%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #277       +/-   ##
===========================================
+ Coverage   25.02%   59.98%   +34.96%
===========================================
  Files          58       28       -30
  Lines        3321     1877     -1444
  Branches     1085     1072       -13
===========================================
+ Hits          831     1126      +295
+ Misses       1756      535     -1221
+ Partials      734      216      -518

Flag
Coverage Δ

differential
59.98% <0.00%> (?)

total
?

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

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

authors: codecov-commenter ymski


text:
chore: add debug option to roi-detected-objects-fusion

PR Type

Improvement

add arg to debug roi-detected-objects-fusion
Related Links

Description

Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR: Required to pass before the merge.

:cry:


text:
add image gen script

This PR
This PR adds an image generation script to debug the actual device.

@obi-t4
コメントしました。
ご確認下さい!


text:
Feature/publish velocity wich covarivance

This is a pull request to make eagleye autoware.universe compliant.
・Eagleye requires GNSS Doppler velocity as input.
・The specification in Autoware(universe) requires that the velocity output from the GNSS driver be TwistWithCovarianceStamped.
https://github.com/autowarefoundation/autoware_msgs/tree/main/autoware_sensing_msgs#velocity
To output TwistWithCovarianceStamped, publish.pvtcartesian and publish.velocity in the yaml file must be set to true.
@taichiH @wep21 @hiro-ya-iv
I would like to merge this PR into a tier4 repository, who should I ask?

@wep21
ありがとうございます。汎用的な変更なのでupstreamにPRを出してみます。
このPRは閉じます。

ちなみにこのレポジトリをPublic archiveにはなさらないのでしょうか


text:
Beautify options not working for scss

I was trying to format .scss file according to custom settings specified from https://github.com/beautify-web/js-beautify
I tried with simple .css file, and it works.
Settings sample:
"beautify.options": {
        "css": {
            "newline-between-rules": true,
            "selector-separator-newline": true
        }
    }

Fixed in 2.0.3

repo: tierratelematics/code-beautifier


text:
LSM: Remove PostedGroove

Make Groove flexible enough so that the separate PostedGroove type is no longer needed.
See: https://github.com/tigerbeetledb/tigerbeetle/blob/85dc0a70fccc86294208d4e957901aa675059cf7/src/lsm/posted_groove.zig#L20
As part of this, the StateMachine's PostedGroove should be indexed by timestamp, not id (unless there is a reason for using id that I am missing).

Fixed by #966 :tada:

repo: tigerbeetle/tigerbeetle


text:
Fix up skeleton setup + Add Github action for tests

Summary

Fixes #2 and #3

This PR will fix the illegal byte sequence error that occurs when running the setup script and adds a skeleton github workflow file for running tests
Successful Github Action Workflow After Setup

Fantastic, thank you @tammytee!!

authors: mattstauffer tammytee

repo: tighten/php-package-skeleton


text:
Create SpamCardsSdk base repository

Create the basic flutter plugin for soamcards sdk.
Acceptance criteria

Example app running with user area service, presenter, controller, and model.


text:
In try_batch, we should use the latest apply's bucket_meta.

Description
Now in struct Apply, we have bucket_meta field. So we should adjust the try_bacth's code to use the latest bucket_meta (the original code have not handled with it which means we use the first apply's bucket_meta).

Please clarify the issue in the description.

Please clarify the issue in the description.

@SpadeA-Tang

Please clarify the issue in the description.

@SpadeA-Tang

Em.. The words in the description now are appended after the comments. I will list the original code.

/run-cherry-picker

repo: tikv/tikv


text:
CompactLog is too noisy under heavy write load

Feature Request
Is your feature request related to a problem? Please describe:
The CompactLog is too noisy under heavy write load.
Describe the feature you'd like:
We can reduce the related logs by enlarge compact step. At the same time we can add a last compacted time for each region. When the last compacted time is long enough we can dynamically
use a small compact step for this region. This can prevent the applied raft logs occupy too many disk space.

Seems duplicate of https://github.com/tikv/tikv/issues/3770


text:
codec improvement

What have you changed? (mandatory)
add some functions to component/codec. includes:

write_all_bytes for NumberEncoder
write and read compact-bytes and memory-comparable-bytes
add U64_SIZE, I64_SIZE, F64_SIZE constants to number, need to export this constants for replacing the old crate::util::codec::number::U64_SIZE
Error::Io is used when write read compact-bytes from file
util/codec/error has two more error, KeyNotFound is used in util/rocksdb_util/properties,  mabye we can introduce a new error type PropertyError; KeyLength is used in storage/types,  there is comments to suggest using assertion, which can get rid of this error type;

What are the type of the changes? (mandatory)
Improvement
How has this PR been tested? (mandatory)
unit test
Does this PR affect documentation (docs) update? (mandatory)
NO
Does this PR affect tidb-ansible update? (mandatory)
NO
Refer to a related PR or issue link (optional)
#4040

@breeswish  PTAL, thanks

@breeswish update some code with your suggestion , PTAL , thanks

/run-integration-tests

/run-integration-tests

@BusyJay @overvenus @brson Would you also like to take a look?

Thanks for pinging me @breeswish . I left a few comments. The one that concerns me is the function that returns the total vector length on error, instead of the encoded length. I it's correct, then I'd like a comment explaining why.
Nice work @niedhui.

/test

/test

@AndreMouche @siddontang PTAL at this PR. Thanks!

So I've syned with @brson about the trait issue (impl for File only), we think it's fine for now. If we want it to implement more types we can refine later. Please keep going :)

/run-integration-tests

/rebuild

authors: breeswish brson niedhui zhouqiang-cl


text:
importer: rewrite ts for download SST (#6225)

Cherry-pick of https://github.com/tikv/tikv/pull/6225

/run-all-tests


text:
youtube music installation problem

hello sir,
when i try to install youtube music from terminal some failed message occur.
please help to resolve it and install youtube music.

Hello @devangbairwa, thanks for reporting the issue. Could you try again and  record the exact time in UTC timezone? I'll look at the logs to see if there is any hint.

Closing in favor of #653.

authors: devangbairwa fenryxo

repo: tiliado/nuvolaruntime


text:
Grafana doesn't get any data (synology/docker)

I've installed the latest docker container vwsfriend and vwsfriend-grafana on my Synology NAS and configured vwsfriend like described in the wiki: https://github.com/tillsteinbach/VWsFriend/wiki/Install#install-on-synology-docker-native-synology-ui-no-docker-compose
I can now login to vwsfriend on my NAS on ip_adress:4000 and I get the Vehicle Status for my ID.3 without any problems.
After that I configured also vwsfriend-grafana, but after log in on ip_adress:3000 I get only some blank "no data" controls and a warning "You have to set the URL for the VWsFriend user interface correctly: Go to the user interface on port 4000 and select "Database" > ”Connection Settings"".
Back on the user interface from vwsfriend I can not find any Database settings. Only the status page, where I can pick my car and view the informations and status from the car.
Back on the Synology docker settings for vwsfriend-grafana I've checked the VWSFRIEND_HOSTNAME setting and it seems ok:

Is there anything I have to configure for Grafana?
Thank you!

Did you also Setup the postgres container?

I installed and set up the postgres container and configured the hosts IP in the docker settings for the grafana docker (DB_HOSTNAME). But for now, without any further access.
I've taken some screenshots from the container settings - maybe this helps.
Postgres Container Settings

VWsFriends Container Settings

VWsFriends-Grafana Container Settings

Web UI

WEB UI after clicking the two gears

Web UI after clicking on my car

Web UI Grafana with errors

Do you have the connection settings environment variable:
DATABASE_URL=postgresql://${DB_USER-admin}:${DB_PASSWORD-secret}@${DB_HOSTNAME-postgresdbbackend}:${DB_PORT-5432}/${DB_NAME-vwsfriend}
and
—with-database In the ADDITIONAL_PARAMETERS?

After adding the ADDITIONAL_PARAMETER and the string for DATABASE_URL:

the VWsFriends container doesn't start and the log throws this output:

I think it has to do with Synologys own Docker implementation (and editing) of the .env file with the Disk Station Manager.
Maybe I'm now going to cancel the installation with Synologys DSM and try it with docker compose on the console.

Ah yes I think the variables are only substituted in docker compose. So you have to replace the variables the real values. e.g. ${DB_USER-admin}  with the database password you configured in postgres.

The error looks like there is no connection at all possible to the database. It is sometimes a bit tricky to allow connections between the containers. Maybe you have to configure something in the UI for it to work?
Regarding the database. The database should exist if you put the Variable POSTGRES_DB=vwsfriend to the postgres container. It then creates it when starting the first time.

One last question: What is the difference between "Usable battery capacity (net)" and "Total battery capacity (gross)" in the vehicle parameters form?

Ah, I found it by myself.

Great that it works now!
If you would write a small manual for the DSM setup I would be very happy adding it to the wiki for other users.

I'll write a documentation for the installation with DSM and ssh (which also works fine with synology), when I find some time.

@escuco Did you find time to write the documentation? I'm stuck at the same problem.

authors: escuco piridium tillsteinbach

repo: tillsteinbach/VWsFriend


text:
Different Formats of Time Tags

Hello Mr. Steinbach,
I have observed the following behavior in the format of different time-tags:
Some have a   T   after the date part,
others have just a white-space there.
Example:
Last Upd from WeC    2023-02-01T23:30:01+01:00
Last Upd from Car    2023-02-01 22:07:24+01:00

Can you confirm this observation ?   Some reason behind ?
On my side I like to assign the value to a datetimetype in openhab, which does not work.
Thank you for your comment.
Best regards

hmmm, I have to check why this is wrong...

repo: tillsteinbach/WeConnect-mqtt


text:
S3 throw me a 204 No Content

I am facing issues since now 2 weeks, making progress piece after piece. I do not know If that is an issue or if I am the issue so sorry if I am disturbing and thanks for your great job!
I want to do direct upload to S3. I think my bucket is in a new region (eu-west-2) that only supports aws4 signing. So I followed step by step the aws documentation and rewrite the S3Direct model to change the StringToSign and the SigningKey to generate the signature and the policy.
The aws seems to work now, the preflight and the POST request

I still have my file name and it's type but nothing in my payload in terms of data:

I do nothing neither in my controller:
        getJSON('http://localhost:4200/api/v1/presign').then((response) => {
          return file.upload(response.url, {
            data: response.credentials
          });
        })

neither in my template which is a copy past of the one in the Readme (appart from a pair of ).
I had checked the plupload documentation but I didn't find anything relevant... If you can help me, I am stuck for so long on that ^^. One more time sorry for the disruption if the mistake comes from me!
Thanks

I have rewritten the upload method as follow:
        getJSON('http://localhost:4200/api/v1/presign').then(function (response) {
          /* file.upload(response.url, {
            data: response.credentials
          }); */
          var s3_signed = response.credentials
          var formData = new FormData(),
              xhr = new XMLHttpRequest();

          formData.append('name', filename);
          for (var key in s3_signed) {
            formData.append(key, s3_signed[key]);
          }
          formData.append('Content-type', "");
          formData.append('file', file);
          xhr.open('POST', response.url);
          xhr.send(formData);
        })

And now I have this strange thing instead of the file content: <(unknown mixin):ember672>

repo: tim-evans/ember-plupload


text:
Timber 1.1.4 breaks API compatibility

Expected behavior
Public API should not change on bugfix releases.
Actual behavior
Public API change causes Gantry to break: https://github.com/gantry/gantry5/issues/1542
Steps to reproduce behavior
Install Gantry and upgrade Timber from 1.1.3 to 1.1.4
What version of WordPress, PHP and Timber are you using?
WordPress 4.6, PHP 7, Timber 1.1.4, Gantry 5.3.4
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Upgraded to newest version by using manual update

One way to fix this would be to add a new function(s)/attribute which allows both \Twig_Loader_Filesystem and \Twig_Loader_Chain to be returned.

We have changed (and released) a change in Gantry 5.3.5 that creates a new \Twig_Loader_Filesystem class and includes it into the chain if the loader is a chain. This will mostly fix the issue for having a chain, though it would be better if there was a mechanism to get instance of \Twig_Loader_Filesystem so I wouldn't need to do that.
We use filesystem loader to add extra namespaces, which isn't supported by Timber.

@mahagr Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread

I've worked around the issue, it was API change which could be adjusted by moving from TImber plugin to Timber composer dependency and handling the issue with a new release.

authors: mahagr palmiak

repo: timber/timber


text:
Any roadmap for 2.* release?

Wondering if it's possible to get some visibility on the 2.* roadmap and release schedule. If it's still in the works.
If not anytime soon, it would be great to have a Timber update for Twig 3.* and other dependency updates.

I second that. I am also willing to spent some time as well to drive development forward but I don't know where to start at this moment. I would love to see a day organized where we rally some Timber users and contributors and iron out the release. We would need some guidance from the devs though. @jarednova , would you mind to give your thoughts on this?
And are there people interested in that?

I'd also be interested in having some visibility on the 2.* roadmap and I could also consider contributing to this project, if the development is still active

@jarednova Should I start a super-simple (6 page types) theme today with Timber v2?

@szepeviktor I've been using Timber v2 in production on several blogs for months now, everything seems good. If you're starting something new I would totally use v2 to avoid upgrade hassles, keeping in mind that some things might still change before the official release.

We just released a first beta for Timber 2.0: 2.0.0-beta.1 (release).
Unfortunately, we have no final release date yet and we don’t want to commit to one, because we all work on it in our free time. Thank you so much for understanding.
We made good progress in the last couple of weeks. If we can keep that momentum, I think you can expect a stable release soon.
For now, it would help us the most if you can test out the beta and report any bugs. Or if you feel like tackling known bugs for 2.0, there’s a 2.0 label in the issues. Feel free to work on any issues that have no assignees yet. I tagged some of the with the "Help wanted" and "Good first issue" labels, because I think they would be easy to tackle.
I’ll leave this issue open for now in case you have additional questions.

test out the beta and report any bugs

You can use PHPStan for that. It tells you a few dozen problems right away.

@szepeviktor Yep, working through the issues that PHPStan reports up to a certain level is also on our list. 👍

Start on Level 0, it is less frightening.

Hi everyone, the team is hard at work to make Timber 2.0 happen. We've just created an updated roadmap with open tickets, pull requests, etc. If you would like to help out on Timber, now is the perfect timing. See #2741
Closing this ticket in favor of the mentioned ticket above.

authors: Levdbas gchtr szepeviktor thdebay therealgilles xsynaptic


text:
fix trimLeadingZeros()

if there's nothing but zeroes in the version component it happens to strip
one too many for it should tolerate one leading zero if it also happens
to be a trailing one.

 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.

Sure. Was hoping you don't really care, especially for four-liner ;-) I hate paperwork.

Sorry to bother you again. Would you mind squashing the commits and rebasing them on the current master?
I will merge this in immediately after that, I promise! :slightly_smiling_face:

Like this?

Thanks for your contribution! :slightly_smiling_face:

You're welcome :)

authors: CLAassistant antekresic hacker

repo: timescale/promscale


text:
chore: release main

:robot: I have created a release beep boop
cli: 0.4.5
0.4.5 (2022-11-23)
Features

Flag to skip save note ids. (4449bd6)
Save noteIds after sync. (0fe5a4d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/timgreen/Anki.md/releases/tag/cli/v0.4.5 :sunflower:


text:
Automatically connect you Plex account to the container without SSH Port Forward or other tricks

Automatically connect you Plex account to the container without SSH Port Forward or other tricks.
Username and password are used to cat Plex.tv api to get an app token. Then add it to Preferences.xml and your Plex Media is Automatically linked to your account
ENV Variables to use :
PLEX_USERNAME
PLEX_PASSWORD
example :
docker run -d --name plex \
              -e PLEX_USERNAME=xcid  \
              -e PLEX_PASSWORD=password  \
              -h *your_host_name* \
              -v /*your_config_location*:/config \
              -v /*your_videos_location*:/data \
              -p 32400:32400  timhaak/plex

If you are using a different external port than 32400, you will have to user PLEX_EXTERNALPORT
docker run -d --name plex \
              -e PLEX_USERNAME=xcid  \
              -e PLEX_PASSWORD=password  \
              -e PLEX_EXTERNALPORT=33400  \
              -h *your_host_name* \
              -v /*your_config_location*:/config \
              -v /*your_videos_location*:/data \
              -p 33400:32400  timhaak/plex

All looks good. I've merged it.

@XciD could you also open a PR to update the readme with the new options?

authors: XciD thaJeztah timhaak

repo: timhaak/docker-plex


text:
Rename LyricAccessories to LyricAccessory

Properly reflect the object is a single accessory, not a collection of accessories.
[x] Unit tests pass locally
[x] ran python -m incremental.update aiolyric --patch
Let me know if this was an incorrect way to bump the version number.

Not sure what's going on with the failed checks here.  Looks like GitHub failed to pull my fork branch?

Not sure what's going on with the failed checks here. Looks like GitHub failed to pull my fork branch?

Not sure why it does that


text:
Suggestion: Some sort of Delay or non-switch for quick copy

I am loving this extension! However, one of the painpoints for me on follow mode is when I need to copy a single value from a small pane for use in a large pane. As I'm preparing to copy, the small pane ends up reflowing and changing the location of the item to copy, then again as I switch back.
Perhaps there could be a programmable delay, or some other UI option or feature to help solve this issue?

That sounds very reasonable. I'll include a configurable delay of the follow mode if I have some time.

http://i.imgur.com/Ndm20.jpg

I just published this feature as version 1.1.0 🎉
Sorry for taking so long, I was quite busy. You can find the delay in the configurations. 🙂

authors: benyanke timomeh

repo: timomeh/hey-pane


text:
HTTPS Server if TLS_CERT & TLS_KEY are specified

I run my local instance of nestrischamps on a computer that isn't my normal desktop, so in order to prevent the browser complaining about permission issues with either the webcam or serial port over HTTP, I bring the server up with a self signed certificate in HTTPS mode.    This change modifies server.js to bring up an HTTPS server if a cert file and key file are specified with environment variables.    This also modifies the playback link to be HTTPS.

Merged after adding a commit to lint!

Couple of notes on http vs. https:

You can develop locally with http with chrome provided in the chrome settings you mark localhost:5000 to be treated as a secure host in the chrome browser settings: chrome://flags/#unsafely-treat-insecure-origin-as-secure
Providing a local cert as this PR now supports works great, but the renderer may not load in OBS or SLOBS. It seems the browser sources do not like self-signed certificates 🤔
In "production" the https connectivity is handled by the load balancer, while the server always only handles http

authors: timotheeg zohassadar

repo: timotheeg/nestrischamps


text:
ContainsAny not working with slice index?

Take the example code from this issue, but replace Contains() with ContainsAny() for the two queries.
Output is:
[1]
0xc000087be0 (*string) cannot be compared with <nil> (<nil>)
[]

Doesn't look correct to me.

Fixed in master.  Thanks.

repo: timshannon/bolthold


text:
Help using  trackingallowedpids.ino

Hello, i'm trying using this sketch on ESP32S3
It compiles and uploads to baord, i can connect to racechrono under android, but i have the following message :
"  No PIDs are allowed."
I'd like to retreive gps and lap infos (no need of canbus)
Could someone explain how to do it please ?
Thanks

The device only does what RaceChrono tells it to do.
You need to set up a "vehicle profile" in RaceChrono and add custom data channels with their PIDs.

repo: timurrrr/arduino-RaceChrono


text:
If a cell edit fails, value should revert

Otherwise it's inaccurate. Ideally it'd show an indicator that it's failed instead.

Now that column types exist, this is more likely to occur so should be prioritised

repo: timwis/dataface


text:
feat: custom 404

Fix #22
Very basic custom 404 to at least provide to link to go back to the homepage.

@jamespohalloran I'm going to merge this to a new branch and refactor the styling.

authors: DirtyF spbyrne

repo: tinacms/tina-cloud-starter


text:
2635 - Document creating/updating success messaging

[x] remove redirect after updating a document
[x] add alert for successfully updating a document
[x] add alert for successfully creating a document

closes #2635

@jhuggett This looks perfect to me. For some reason I thought we also wanted to redirect to the new document in the admin when created as well. That would look like this
packages/tinacms/src/admin/pages/CollectionCreatePage.tsx
onSubmit: async (values) => {
        try {
          await createDocument(cms, collection, template, mutationInfo, values)
          cms.alerts.success(
            'Document Created!',
            30 * 1000 // 30 seconds
          )
+          navigate(`/collections/${collection.name}/${values?.filename || ''}`)
        } catch (error) {
          cms.alerts.error(
            `[${error.name}] CreateDocument failed: ${error.message}`,
            30 * 1000 // 30 seconds
          )
          console.error(error)
        }
      },

@jhuggett This looks perfect to me. For some reason I thought we also wanted to redirect to the new document in the admin when created as well. That would look like this packages/tinacms/src/admin/pages/CollectionCreatePage.tsx
onSubmit: async (values) => {
        try {
          await createDocument(cms, collection, template, mutationInfo, values)
          cms.alerts.success(
            'Document Created!',
            30 * 1000 // 30 seconds
          )
+          navigate(`/collections/${collection.name}/${values?.filename || ''}`)
        } catch (error) {
          cms.alerts.error(
            `[${error.name}] CreateDocument failed: ${error.message}`,
            30 * 1000 // 30 seconds
          )
          console.error(error)
        }
      },

Ill defer this to @Enigmatical

I think the plan was to tackle that later, but I may be misremembering

@jhuggett This looks perfect to me. For some reason I thought we also wanted to redirect to the new document in the admin when created as well. That would look like this packages/tinacms/src/admin/pages/CollectionCreatePage.tsx
onSubmit: async (values) => {
        try {
          await createDocument(cms, collection, template, mutationInfo, values)
          cms.alerts.success(
            'Document Created!',
            30 * 1000 // 30 seconds
          )
+          navigate(`/collections/${collection.name}/${values?.filename || ''}`)
        } catch (error) {
          cms.alerts.error(
            `[${error.name}] CreateDocument failed: ${error.message}`,
            30 * 1000 // 30 seconds
          )
          console.error(error)
        }
      },

Ill defer this to @Enigmatical

I think the plan was to tackle that later, but I may be misremembering

@jhuggett is correct here.  Handling the redirect when creating a new Document introduces some messy issues when creating Documents on TinaCloud (mainly, where do I redirect to when the Document doesn't exist yet?).  Commonly known as the "documentCreator Problem" - we decided yesterday to just continue doing what we're doing right now for create.

authors: Enigmatical jhuggett logan-anderson

repo: tinacms/tinacms


text:
add etna team members

Before submitting (must do checklist)

[ ] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Proposed Changes

Closing issues

Codecov Report

Merging #1267 (e662ac4) into master (fb5f6d4) will decrease coverage by 80.34%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master   #1267       +/-   ##
==========================================
- Coverage   87.98%   7.64%   -80.34%
==========================================
  Files         186     186
  Lines       10751   10747        -4
==========================================
- Hits         9459     822     -8637
- Misses       1292    9925     +8633

see 169 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: GrozniyToaster codecov-commenter

repo: tinkoff-ai/etna


text:
host extentions crashed

Type: Bug
host extentions crashed
Extension version: 0.0.7
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:50:47.800Z)
OS version: Linux x64 6.2.0-37-generic
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 4229)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
15.55GB (10.86GB free)

Process Argv
--unity-launch --crash-reporter-id f7448ebc-02b1-408f-8113-6821e27a36f6

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263cf:30880073
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
synctok:30869157
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixtcf:30871695
pythonregdiag2:30871582
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30885897
pythontbext0:30879054
dsvsc016cf:30886111
dsvsc017:30886112
dsvsc018cf:30886115
aa_t_chat:30882232

Extension host terminated unexpectedly 3 times within the last 5 minutes.

repo: tintinweb/vscode-solidity-language


text:
v1.0 Pools appear irretrievable

Minimum code to reproduce:
from tinyman.v1.client import TinymanClient
from algosdk.v2client.algod import AlgodClient

algod = AlgodClient('', 'https://api.algoexplorer.io', headers={'User-Agent': 'algosdk'})

# V1 client
client_v1 = TinymanClient(algod_client=algod, validator_app_id=350338509)
# V1.1 client
client_v2 = TinymanClient(algod_client=algod, validator_app_id=552635992)

# Get two assets
YLDY = client_v1.fetch_asset(226701642)
ALGO = client_v1.fetch_asset(0)

# Find pool (which definitely still exists)
# Actual target address is
# Y74RXNAUAZT2U5PD57Y22NVU6UPW5WNLRLHA763EE5IJSLSJXRAX6YY4OE
pool = client_v1.fetch_pool(YLDY, ALGO)
pool.address # FNWKQUJCBFEW3OIUFAV5WD5WF6YZ52DKCVVCVTW5G53TOY5RS4AX57SFXU

# Actual target address is
# KX6S647W6BEN6XHEJVMXK3UYLVNGT2Q6PHQSF5AA2JSSDFSOX7R4MESXRY
pool2 = client_v2.fetch_pool(YLDY, ALGO)
pool2.address # KX6S647W6BEN6XHEJVMXK3UYLVNGT2Q6PHQSF5AA2JSSDFSOX7R4MESXRY

I've issued a pull request that resolves this here:
https://github.com/tinymanorg/tinyman-py-sdk/pull/34/commits

I think SDK doesn't support the old version on purpose. Why do you want to use v1.0?
You can use the old version of the SDK for v1.0.
Ex. git+https://github.com/tinymanorg/tinyman-py-sdk.git@8eb969d741523aeb33325d2ad0ea33734176b84e
Doesn't it solve your needs?

I think SDK doesn't support the old version on purpose. Why do you want to use v1.0?
You can use the old version of the SDK for v1.0. Ex. git+https://github.com/tinymanorg/tinyman-py-sdk.git@8eb969d741523aeb33325d2ad0ea33734176b84e
Doesn't it solve your needs?

There are many reasons a user may want to get old pool addresses. Yes, dowloading an old version of the SDK would allow a user to retrieve old pool addresses correctly, at the expense of being able to retrieve current pool addresses correctly. The fact that the client functions allow you to pass a validator address tells you that this is not intended behavior.
My pull request resolves the issue. I'm not sure if the Tinyman team cares to merge the request, but if they do not, users should be able to download my pull request directly if they need pool addresses from both v1.0 and v1.1 contracts.

Thank you. As you suggested, users can use your PR.

authors: gokselcoban jmrMOONBOI

repo: tinymanorg/tinyman-py-sdk


text:
Using the local files with Webpack

I deploy the client of my Webapp using Webpack.
I would like to switch to the local files instead of the cloud so the app works without internet (only runs in the local network).
After adding the import for the base tinymce module it seems not to use the cloud anymore but the editor is not rendering anymore.
After looking at the errors in the browser console it seems like tiny tries to load additional files with a path like this: localhost:3000/js/<different plugins, themes etc>
The required files are not at this path therefore the editor does not load.
Tried adding the missing parts via imports, wich seems to work except for:
http://localhost:3000/js/langs/de.js
http://localhost:3000/js/plugins/emoticons/js/emojis.js
My import statements look like this:
import 'tinymce';
import 'tinymce/plugins/link';
import 'tinymce/icons/default';
import 'tinymce/themes/silver';
import 'tinymce/plugins/paste';
import 'tinymce/plugins/autolink';
import 'tinymce/plugins/emoticons';
import 'tinymce/plugins/codesample';
import '@tinymce/tinymce-webcomponent';

I don't know what imports to add to make it work.
The emoji one is not that important as i was thinking replacing it with a custom one.
But the language would be obviously really important.
UPDATE:
Seems like i got the language working by downloading the lang js file and adding it locally.
Removed the emoticons plugin and now it seems like the js files are ok.
The editor still does not show up seems like the same problem applies to the Stylesheet files.
The same workaround does not quite work for the Stylesheets, will try importing them via SASS und update again if it works.

Hi @akowi-sknobloch if you want to self-host I would recommend putting the tinymce folder in a public place and use the src property of the component to point to that path since that will be easier than importing each individual component of the editor

Thanks for the answer.
I have the package installed via npm.
Putting the static files in my Project would likely work.
But that way i cannot update/manage the version via npm and the git repository gets blown up.
Would really prefer to use it via the node_modules.
I have an idea to move the files from the node_modules into my assets output folder via a bit of Webpack magic.
Will try this later and write back if it works.

Ok the Webpack magic did the trick.
Using the copy-webpack-plugin i can copy the static files from the node_modules into my assets directory.
Just added this small snippet to my Webpack plugin config:
new CopyPlugin({
  patterns: [
    {
      from: 'node_modules/tinymce',
      to: path.resolve(__dirname, 'assets/tinymce'),
    },
    {
      from: 'tiny-mce-langs',
      to: path.resolve(__dirname, 'assets/tinymce/langs'),
    },
  ],
})

Set the src prop like @jscasca said and it works like a charm.
For the lang package I added the tiny-mce-langs folder to my projects root directory.
My server is configured to static serve everything in the assetsdirectory.

authors: akowi-sknobloch jscasca

repo: tinymce/tinymce-webcomponent


text:
Make sure to specify the windows home directory [skip ci]

This specify's the home directory for windows users more explicitly. This comes from feedback we got on the website.

@twang2218 do you mind taking a look at this?

LGTM. Thanks @amjith for merging it. 😄

*twitch* don't forget to delete the branch! [:

repo: tinytacoteam/zazu