Launchable is killing test runs

Due to errors that launchable runs into, it ends up exiting with a non-zero status and killing a test run, despite assurances that adding Launchable to one's testing processes will not make one's test process more fragile.  Having Launchable kill a test run that would have otherwise run fine is adding fragility to our test runs.  I have complained about this multiple times in the past but this just seems to go on and on.  I cannot convince my team to continue to use Launchable if it's going to make our CI processes more fragile.
Here's the latest:
[2022-08-11T05:29:46.918Z] + launchable record build --name jenkins-daos-stack-daos-ci-daos-do-packer-ofed-images-PR-2-release-2.0-20 --source src=.
[2022-08-11T05:29:47.854Z] Exception in thread "main" java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must be called.
[2022-08-11T05:29:47.854Z] 	at org.eclipse.jgit.lib.BaseRepositoryBuilder.requireGitDirOrWorkTree(BaseRepositoryBuilder.java:636)
[2022-08-11T05:29:47.854Z] 	at org.eclipse.jgit.lib.BaseRepositoryBuilder.setup(BaseRepositoryBuilder.java:600)
[2022-08-11T05:29:47.854Z] 	at org.eclipse.jgit.lib.BaseRepositoryBuilder.build(BaseRepositoryBuilder.java:625)
[2022-08-11T05:29:47.854Z] 	at com.launchableinc.ingest.commits.CommitIngester.run(CommitIngester.java:133)
[2022-08-11T05:29:47.854Z] 	at com.launchableinc.ingest.commits.CommitIngester.main(CommitIngester.java:74)
[2022-08-11T05:29:47.854Z] Can't get commit history from `/data/jenkins/jenkins-1/ci_vm_wolf-106vm1-9/workspace/ker-ofed-images-PR-2-release-2.0`. Do you run command root of git-controlled directory? If not, please set a directory use by --source option.
f
[2022-08-11T05:29:47.854Z] fatal: Not a git repository (or any parent up to mount point /data)
[2022-08-11T05:29:47.854Z] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[2022-08-11T05:29:47.854Z] Can't get commit hash. Do you run command under git-controlled directory? If not, please set a directory use by --source option.
[2022-08-11T05:29:47.854Z] Command '['git', 'rev-parse', 'HEAD']' returned non-zero exit status 128.
[2022-08-11T05:29:47.854Z] Command '['java', '-jar', '/localhome/lcl_builder/.local/lib/python3.6/site-packages/launchable/jar/exe_deploy.jar', 'ingest:commit', '-endpoint', 'https://api.mercury.launchableinc.com/intake/', '-max-days', '30', '-scrub-pii', '/data/jenkins/jenkins-1/ci_vm_wolf-106vm1-9/workspace/ker-ofed-images-PR-2-release-2.0']' returned non-zero exit status 1.

Thank you for reporting the comment.
Yes, the cli shouldn't suspend the user pipeline especially cause of Launchable side problems.
However, the cli needs to notify the user when the user misses or fails to set up the cli. In short, the cli shouldn’t ignore all errors.
In this case, it seems to be that you set an incorrect directory.
If the cli couldn’t collect commit history, Launchable won’t predict the test selection. So, the cli needs to inform the users of this issue as an error.
Or, this pipeline has usually worked well, but it was sometimes stopped cause of the cli error, right?
If so sorry and we need to know the situation more deeply.

Right, it's a balance. Our priority is that the CLI should not return an error when the service is legitimately down. I recall you've been bitten by this, and I recognize and apologize that we've not done a great job here. I think we still have some improvements to make there, and if you're still seeing that, please let us know.
However, for the CLI to never raise an error, even in the case of misconfiguration, would present its own challenges, both for us and our customers.
This specific error doesn't look like a service issue. It looks like a configuration issue OR a CLI bug where a previously working configuration is on longer working (which would obviously be very bad!)
Do you know if the launchable invocation has changed or anything about the repository has changed? Thanks.


How are you guys compiling this library on Linux?

With what app?  VSCode?
I am trying and getting libudev.h No such file or directory.  I know i need to put directories to look for this stuff somewhere, but I am lost...   Please help?
Thank you.

I Apologize...  I didnt have libudev-dev installed..........

Yes, I use VS Code on Linux
I am glad you could make it work :)


Updated tests to unify strict/classic testing

Summary

Updated tests to unify strict/classic testing
Changes

Updated tests to unify strict/classic testing
Testing

Possible Regressions

Checklist

[X] Read the contributions page.
[X] Submitted the CLA form, if you are a first time contributor.
[X] The introduced changes are covered by unit and/or integration tests.

Notes

We said we would bee keeping the tests in the strict PR for now.


I want to use http to get rid of those error prompts, so annoying prompts

I want to use http to get rid of those error prompts, so annoying prompts

把这个提示去掉吧

Can remove this prompt

Just use http link instead of https or create a valid SSL certificate for your VsCode.
Or you can put nginx in front of everything.
Regards

Just use http link instead of https or create a valid SSL certificate for your VsCode.
Or you can put nginx in front of everything to deal with certificates.
Regards

How to solve the problem just using http

I'm sorry these are causing such a headache for you!
Unfortunately we don't have a way to remove the prompts.
--link is definitely your best option here. It'll handle everything.
If you can't use that, you could use --cert and code-server will
generate its own certificate. The browser will tell you it's insecure
and you'll have to click past it but it's still better than plain HTTP.


Develop

Codecov Report

Merging #2 (a1a5a4d) into main (77825c7) will decrease coverage by 0.76%.
The diff coverage is 6.66%.

@@           Coverage Diff            @@
##            main      #2      +/-   ##
========================================
- Coverage   3.70%   2.94%   -0.77%
========================================
  Files          4       5       +1
  Lines         27      34       +7
========================================
  Hits           1       1
- Misses        26      33       +7

Impacted Files
Coverage Δ

lssr/core.py
0.00% <0.00%> (ø)

lssr/util.py
0.00% <0.00%> (ø)

lssr/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 77825c7...a1a5a4d. Read the comment docs.


Create LICENSE

PR Goal

Implemented solution

Checkpoints

[ ] If relevant, manual tests have been done to ensure the stability of the whole application and that the involved feature works
[ ] Automated tests covering the feature or the fix, have been written, deemed irrelevant (give the reason), or an issue has been created to implement the test (give the link)
[ ] The PR or the original issue contains a short summary of the implemented solution.

@Skylsmoi @Haskaris could you review and merge this?


Server hot reload

It would be interesting if the server was restarted every time it was changed:

the config.toml
some minijinja template.
some static file.

There is this notify library for this purpose.
And there is this example and this discussion about restarting the axum server.

Solved in version 0.2.0


Cron: Update Mirrors cancelled: dial tcp {EXTERNAL IP ADRESS}:3306: connect: connection timed out

Description
The connection to the external database server often fails with a connection timed out message.
I have a MariaDB Galera Cluster with MaxScale. And In the MariaDB logs I can't seem to find the fault.
I read somewhere that the issue could be the max_allowed_packet which might be set too low. I set it to<PHONE_NUMBER> (1024 mebibytes), but no luck.
I have been trying to fix this for a while now, My System Notices are in total 938, with most of them being the connection time out message.
Gitea Version
1.20.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
built in
Operating System
Ubuntu 22.04.3 LTS
How are you running Gitea?
Docker rootless
Database
MySQL/MariaDB

Please paste your logs here.

@lunny
The logs

How many records on your action_runner table?

The are 9 records in the action_runner table

@lunny do you need any more information?

Looks like it's normal.
What's your database version?

@lunny the mariadb --version output:
mariadb from 11.0.3-MariaDB, client 15.2 for debian-linux-gnu (x86_64) using  EditLine wrapper

@lunny any luck on figuring this out?

I think these timeout messages are because it's too slow visiting from gitea to database? Maybe you can login to gitea container and have a test to visit the database.

I think this is a network problem or mysql side problem but not related with Gitea.

We close issues that need feedback from the author if there were no new comments for a month. :tea:


upgrading kurtosis after a downgrade requires a hidden, undocumented step

What's your CLI version?
0.75.7
Description & steps to reproduce
Workflow: I want to install an older version of Kurtosis, run some test/experiments, and then upgrade back to latest stable.
This is what I did:

brew uninstall<EMAIL_ADDRESS>from docs
brew install<EMAIL_ADDRESS>docs
Do my thing
brew update && brew upgrade kurtosis-tech/tap/kurtosis-cli from these docs
Get error:

derek@Dereks-MacBook-Pro ~ % brew update && brew upgrade kurtosis-tech/tap/kurtosis-cli
Already up-to-date.
Error: kurtosis-tech/tap/kurtosis-cli not installed

To fix, I have to uninstall 0.70.4 and then re-install Kurtosis as a net new install using this doc. This extra step is not documented.
Desired behavior
I should be able to simply run brew update && brew upgrade kurtosis-tech/tap/kurtosis-cli from any historical version of Kurtosis to upgrade to latest. The docs should include a note or tip that warns a user that they cannot upgrade to the latest stable release of Kurtosis from a previous version that they intentionally downgraded to. Something like: "to get the latest release, please make sure you uninstall the historical version and then perform a net new install of kurtosis"
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.

In terms of priority, I don't have data on how common people uninstall Kurtosis (cc: @h4ck3rk3y might know more about the metrics pipeline). However, I can imagine there are people who want to test against older versions of Kurtosis as part of a debugging workflow to pinpoint regressions in Kurtosis or in the packages users will author.


Configuration Reader

This adds a basic configuration reader with tests. It is tested according to the merge order in #1.
It can be initialized more than once and even with other settings, however each project should only need to init it once, and pass along that final configuration.
I added the configuration to the hosts tasks.
It uses the new logging, but keeps the old console.log calls for reference for now.

Be sure to do a squash and merge, with the relevant comments left as it's has quite a lot of commits.

@Volzy Are you still alive, and want to review this? ;-)

Wow. Didn't see this before now. I'll review this today.

22 days ago :'(


Sort followers and following by time

Sorts followers and following so that who most recently followed you and who you most recently followed show up first

thanks for crushing this ser!!
will we have to run a backfill on existing events?

thanks for crushing this ser!!
will we have to run a backfill on existing events?

yup! we can join with the events table to backfill them

noiceee!


Add snmp_tile template to ddev create --type

What does this PR do?
Add snmp_tile template to ddev create, to be able to create a new snmp vendor tile by using
ddev create snmp_<vendor> --type snmp_tile

This will create a new integration folder with only a manifest.json and a README.md, properly configured.
Motivation
We are in the process of adding multiple vendor tiles based on snmp integration. To simplify the process, we are automating the repetitive task.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

@AlexandreYang I addressed your comments, can you give another round of review please?


$2,000 Bounty to add more support

Hey TSDav gang. I just raised a bounty of $2,000 to add more support for more CalDav services:
https://github.com/calcom/cal.com/issues/3457#issuecomment-1435999404

Sorry I didn't find time for adding more support for caldav, too much things happened in my life.
Glad I'm able to find time for open source work now again.

would you be interested if we take over the repo?


muted_users_ui: Convert module to TypeScript.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, after adding a bonus commit to fix a misleading variable name. Good to be on the lookout for this sort of thing as you work.


feat: path to a custom tsconfig

This adds a config field and a command line arg tsconfig for passing a path to a custom typescript configuration file. We don't do any typechecking, but we do pass it along to our build process so things like compilerOptions.paths get resolved correctly.

esbuild has its own machinery for finding then nearest tsconfig (which iiuc follows the same algo that typescript itself does) so I don't think we should do anything different here.


Database implementation

Addition #3

Closes data implementation using a simple txt "database" which stores IDs of blacklisted channels


pull request for e2e test at 01/13/2017 23:45:07

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


[feature] Support nesting in .config dotfolders

Is your feature request related to a problem? Please describe.
Ever-expanding dot clutter in the root of projects is a scourge. I appreciate that you've buried all of yours in a single .moon folder, but this could be improved slightly further.
Describe the solution you'd like
Allow for the .moon folder to be relocated to .config/moon instead. Renovate do something similar, except optionally allow their configurations to be buried within platform-specific .github or .gitlab directories.
Describe alternatives you've considered
n/a
Additional context
We're considering adopting Moon in our # and Þ repos. This would be appreciated.
If you support this, you can get added to the dot-config ecosystem list, as well: https://dot-config.github.io/ (although it is wildly incomplete)

While I'm a big fan of the .config folder approach, the .moon folder contains a lot of non-config files. Some examples are all build caches, VCS hooks integration, Docker stuff, and more.
Would feel a bit weird to nest all that under .config.

Hey @milesj, thanks for the response. How much of that stuff needs committing to Git? Presumably it is just the config parts? No opposition here to having the rest remain in a .moon folder, and/or having this available on a purely opt-in basis.

Fair enough. I'll look into it for a future release.

Awesome, thanks @milesj. This plus Renovate support would both help with entropy a lot (in our use case). :)


Add release/tag and dependencies version

Hi Mikael,
Congratulation on the great repository! I just wanted to make some suggestions; please, consider using Github tags or releases. It would make it easier to follow the latest updates/fixes of the tool. Also, it would be great to have specified the nitorch version that the unires uses to avoid having recent nitorch updates break any function from unires. Finally, it would be great to see the unires available at pypi to be easier to install and define it in the requirements. I would be more than happy to help with any of these suggestions; just let me know what you think. Cheers

Hi Mikael,
You could start by explicitly listing nitorch as a (github) dependency in your setup.py and pin it to a specific commit that you know works well with UniRes. Some pointers here: https://stackoverflow.com/questions/55146691
I would also add [all] at the end of the URL so that all optional dependencies to nitorch are installed (nibabel, etc).
Happy to help with this ;)

Hi @Warvito
Sorry this took ages, but I just pushed a branch that should sort out the dependency issue:
https://github.com/brudfors/UniRes/tree/fix-dependencies
Could you maybe try this, when you have the time, and let me know if it works for you?
I will then make a PR and merge it into main. Then I will create a release tag, as requested :)

Also @Warvito, if you are happy to help me get UniRes onto pypi, that would be great!

Hi @Warvito,
@balbasty managed to test the changes that I made to the setup.py and it all worked on the GPU. Therefore, I created a release tag:
https://github.com/brudfors/UniRes/releases/tag/v0.1
Hope it is helps :)


injecting locally causes error

i am using correct syntax (inject locally script) but it throws an error saying no path was specified.
heres the debug: http://mcmonkey.org/paste/23717

syntax change i was unaware of, never mind


Add optional timing output

To time how much just the formatting takes vs process startup.

Added in 0.4.3


Map - Identify stacked address

Stacked addresses can be seen on the map, but only because there are multiple address numbers and one point. From a functional perspective this is adequate, but would be more user friendly if it was easier to identify stacked addresses by looking at the map.

Also one for Ian Reese?

@billgeo - If he likes, However I suspect the solution would require a fair bit of coding to summarise the addresses within the stacks

It might be something that we wait until we've implemented primary/sub addressing so we can utilise the primary address as a label.

It is no longer possible to see stacked addresses on the map.

Fixed Please re test


Move tests (and upgrade elm-test)

content of the Tests.elm is as per #7 (I would have added this PR into that one, but I'm not enough of a github expert to know how to - if it is possible).  Main difference is that tests have been moved into a tests directory so the dependance on elm-test is removed from the top level elm-package file.
Also, not having used the HTML Runner that's not in there so the tests have to be run from the command line.  If you'd like me to add it back in, then let me know and I'll have a go (I should probably have a go with it).

I would have added this PR into that one, but I'm not enough of a github expert to know how to - if it is possible

Here's how you do that:

Go check out their fork
pull it into your fork
work on their branch in your fork

I'll merge this and publish, thanks!

brill - thanks - really appreciate the zippy turnaround.... came across this via @avh4's Lights Out ElmLive stream - which I can now go back to following along to - as tests are now running fine


Redirect super user to dashboard

Hello, I'm trying to redirect a superuser to dashboard after login instead of the home page can anyone help me?

As far as I can tell this is not a feature of Saleor today. Are you looking for advice on how you might go about adding the feature?

Yes, Im looking for advice on how I might go about adding this feature to saleor.

You'd need to monkey patch the LoginView used here: https://github.com/mirumee/saleor/blob/7fa04dbb3e79532124494323fdcbc54c41166425/saleor/account/views.py#L25
You need to override get_success_url to do your bidding. The original is https://github.com/django/django/blob/a906c9898284a9aecb5f48bdc534e9c1273864a6/django/contrib/auth/views.py#L63
There may be more to it than that but I don't think so.
Might be worth checking with mirumee that they would accept a PR as they may not be interested. Also worth considering that Storefront 2.0 is on the horizon... So perhaps wait and see how that pans out before doing anything.

You'll want to monkey patch LoginView used here: https://github.com/mirumee/saleor/blob/7fa04dbb3e79532124494323fdcbc54c41166425/saleor/account/views.py#L25
Probably by overriding get_success_url - original here:
https://github.com/django/django/blob/a906c9898284a9aecb5f48bdc534e9c1273864a6/django/contrib/auth/views.py#L63
Don't forget Storefront 2.0 is around the corner so unless critical to you it might be worth waiting to see what that looks like before attempting to customise. Also worth getting feedback from Mirumee as to whether they'll accept a PR as they may not be interested (which would be fine just need to include managing your customisation in your plans).


[Question/Feedback]: Request for Version Information in Terraform Resource Modules CSV for Automated Pipeline Integration

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
Hi,
I am currently working on automating the process of forking Terraform modules from the provided CSV into our internal Azure DevOps (ADO) repositories. My goal is to implement internal module library with a system that allows us to check for breaking changes and conduct unit testing before merging these modules into our main branch. This would enable us as platform team  to offer these modules internally to our app teams with greater confidence in their stability.
However, we have encountered a significant challenge in this process. The CSV file does not include version information for each module. Without versioning, it becomes extremely difficult for our pipeline to determine whether a module has changed and whether it should be re-forked and re-tested.
Request:
Could you please consider adding a version field to the CSV file? This would greatly enhance our ability to automate and streamline the process of module management, allowing us to track changes more effectively and ensure that we are always working with the most up-to-date versions of each module.
We believe this enhancement would not only benefit our team but also others who are integrating these modules into their CI/CD pipelines.
Thank you for considering this request.
Best Tomas

@tomaszurek, thank you for your patience!
@jaredfholgate, @jchancellor-ms, can you please take a look at this? Thanks!

In order to achieve this we would need to automate the generation of the CSV, which is currently manual. I think we can probably expose an API that reads the version directly from GitHub or Terraform registry rather than trying to add it to the CSV.
In the meantime, you can use this API call and page through the results to get what you need: https://registry.terraform.io/v1/modules/search?q=avm-&namespace=Azure

Here is some example PowerShell to create a CSV:
$resultsPerPage = 15
$url = "https://registry.terraform.io/v1/modules/search?q=avm-&namespace=Azure&limit=$resultsPerPage"

$results = @()
$result = Invoke-RestMethod -Uri $url

$results += $result.modules

while ($result.meta.next_url) {
    $result = Invoke-RestMethod -Uri $result.meta.next_url
    $results += $result.modules
}

$results | Export-Csv -Path "C:\temp\microsoft-azure-avm-modules.csv" -NoTypeInformation

@tomaszurek, I can also echo what Jared summarized above. The intent behind our CSV's is to drive our module admittance (known as initial module triage process), therefore they're not meant to track version information. In the online version of the AVM module index (shown on the AVM website, here), we're however always dynamically reflecting the latest available module version for each module.
You can also see how this is done at the code level here.


Remove unnecessary  LogPrintf CreateNewBlock()

Remove unnecessary  LogPrintf CreateNewBlock() lines, that only fill up debug.log in normal operation.

Closing in favor of #171


defaultPath option for  showOpenDialog (file and directory fields)

It could be interesting to have the ability to specify  in fields "file" and "directory" a defaultPath to open the dialog window in it.
(this option exist on electron side in showOpenDialog but i've got no idea how to ?)

hi @dewiweb
Passing a defaultPath is indeed possible within electron. It's a property in the options parameter that you pass to the showOpenDialog.
IMO you should need a defaultPath, in the case when there is no default preference value set for that preference, and the user hasn't selected one yet.
In all other cases, I guess the defaultPath should be ignored, and the current value (the one set by the either the default preferences or by the user) should be used.
Would this implementation be in line with what you've had in mind?
Some possible caveats to test:

OS specific paths
Non existing paths
File paths should resolve to their parent folder

hi @pvrobays ,
Yes it seems to be right. My purpose is to open file dialog in the right folder when the dir preference is set by user.


Plane to body conversion

Encapsulate plane to body inverse projection in StarCam.plane2body() method.

Out of scope (for now).


Using MRAA with BeagleBone green

Hello, I'm new to development using a Beaglebone board, I would like to know if MRAA can be used with BeagleBone Green or only with Beaglebone Black.
Thanks in Advance.

I have been able to use it with BB Green and Black, both wired and wireless.
nJoy!

I have been able to use it with BB Green and Black, both wired and wireless.
nJoy!

Thanks for the reply @Chuckduey, I'll check the documentation and other informations to continue my project.

I have been able to use it with BB Green and Black, both wired and wireless.
nJoy!

Thanks for the reply @Chuckduey, I'll check the documentation and other informations to continue my project.
I have to prepare my eclipse IDE, in Ubuntu , to build a project for Beaglebone Green using MRAA, I am using arm-linux-gnueabihf as GCC, but I am unable to compile with MRAA.
This is my makefile:

I Keep getting this error: #error your machine is neither 32 bit or 64 bit ... it must be magical

I've changed the makefile now I keep getting this error. Let me explain this project: I have a project for LinkitSmart 7688, which uses MRAA, I've changed the GCC and some paths to build this project to BeagleBone Green, but now I'm getting this error.

It looks MRAA is not installed.
Type in mraa-gpio version on a console to the BeagleBone.  If you have a "command not found" then you will need to install MRAA Libs.  If the version is less than 2.0 I would uninstall and download the latest from Github.
Here are the directions for downloading and building the latest release.  Note the "apt install" usually has a very old version and may not have the latest bug fixes.
0. Load the packages do make the build **sudo apt install build-essential python-dev cmake automake libpcre3 libpcre3-dev byacc flex **

git clone https://github.com/eclipse/mraa.git
Descend into the mraa directory cd mraa
Create a build work area  mkdir build
Descend into that work area cd build
Run cmake cmake -D CMAKE_INSTALL_PREFIX=/usr ..
If cmake runs without error, run make
If this runs without errors you are ready to install. Run sudo make install
You may need to run sudo ldconfig or reboot before the linker works example gcc myfile.c -l mraa

After this you should be able to run the command mraa-gpio list and see all the pins that are controllable by MRAA on your system.
Good Luck
Chuck

It looks MRAA is not installed.
Type in mraa-gpio version on a console to the BeagleBone. If you have a "command not found" then you will need to install MRAA Libs. If the version is less than 2.0 I would uninstall and download the latest from Github.
Here are the directions for downloading and building the latest release. Note the "apt install" usually has a very old version and may not have the latest bug fixes.
0. Load the packages do make the build **sudo apt install build-essential python-dev cmake automake libpcre3 libpcre3-dev byacc flex **

git clone https://github.com/eclipse/mraa.git
Descend into the mraa directory cd mraa
Create a build work area  mkdir build
Descend into that work area cd build
Run cmake cmake -D CMAKE_INSTALL_PREFIX=/usr ..
If cmake runs without error, run make
If this runs without errors you are ready to install. Run sudo make install
You may need to run sudo ldconfig or reboot before the linker works example gcc myfile.c -l mraa

After this you should be able to run the command mraa-gpio list and see all the pins that are controllable by MRAA on your system.
Good Luck
Chuck

I Did the steps in my Beaglebone and in my VM (that I use to build the project).

Then, I added the /usr/lib and /usr/include to my makefile. Now I'm getting the following error

Did I missed something? Or there's another configuration that I have to do?
Thanks in advance

You are using a virtual box on an x86 platform. The BeagleBone is an ARM platform. I do not know how to make Eclipse on a VM act like a BeagleBone. You should be able to compile the program directly on the BeagleBone using GCC on that system. For the VM and Eclipse interface you will need to find a different resource that knows more about that.
Best regards
Chuck

Thanks Chuck. In fact, what I need is Cross-compile my code in eclipse (VM) for the BeagleBone, do you have in mind where I can get this kind of information?


feat: test on deangular feature branch

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

#65

this is only for testing, right?

this is only for testing, right?

Yes, only for test.


exclude placeholder bug in bug sweep and fix RHSA check

validate two types of bugs together, if not usejira the related bug list would be empty, so when checking ET type it can compute result together
elliott --assembly 4.10.28 --group=openshift-4.10 verify-attached-bugs --verify-flaws
2022-08-24 09:46:28,861 INFO Cloning config data from https://github.com/openshift/ocp-build-data.git
2022-08-24 09:46:30,627 INFO Using branch from group.yml: rhaos-4.10-rhel-8
2022-08-24 09:46:30,627 WARNING Constraining brew event to assembly basis for 4.10.28: 46763830
Retrieving bugs for advisory [100251, 100250, 100252, 100249]
Verify blocking bugs for 2112995 Passed
Verify blocking bugs for 2104454 Passed
Verify blocking bugs for 2100369 Passed
Verify blocking bugs for 2110963 Passed
Verify blocking bugs for 2115267 Passed
Verify blocking bugs for 2117369 Passed
Verify blocking bugs for 2114833 Passed
Verify blocking bugs for 2106794 Passed
Verify blocking bugs for 2112815 Passed
Verify blocking bugs for 2102386 Passed
Verify blocking bugs for 2108176 Passed
Verify blocking bugs for 2111335 Passed
Verify blocking bugs for 2117346 Passed
Verify blocking bugs for 2109518 Passed
Verify blocking bugs for 2116545 Passed
Verify blocking bugs for 2101412 Passed
Verify blocking bugs for 2116401 Passed
All bugs were verified. This check doesn't cover CVE flaw bugs.
All CVE flaw bugs were verified.

Is there a reason to make placeholder bug special? I think it is as normal as others. Unless there is a strong reason to treat the placeholder bug specially, I would not like this to be merged.

It try to solve the issue that if a placeholder bug from previous release still in VERIFIED when preparing release, prepare release will treat it as normal bug and will failed when attaching it because it already attached, and there is no jira field indicate the bug was already attached to ET


Output template to append filesize in GiB,MiB or KiB as shown in -F

Checklist

[X] I'm reporting a feature request
[X] I've verified that I'm running yt-dlp version 2021.12.01. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Basically a %(pretty_filesize)s output template field.
I know that %(filesize)s and %(approx_filesize)s exists.
But I want the value that shows up in -F to show up in my filenames. I know that size is less precise but it's way more human-readable.
I'd like
yt-dlp --get-filename --restrict-filenames -f 135 BaW_jenozKc -o "%(uploader)s-%(upload_date)s-%(title)s-%(id)s-%(pretty_filesize)s.%(ext)s"
to print
Philipp_Hagemeister-20121002-youtube-dl_test_video_a-BaW_jenozKc-849.41KiB.mp4
Or if I want -f 22 BaW_jenozKc then %(pretty_filesize)s should print its corresponding approx. filesize of ~1.82MiB as shown in -F making the output file Philipp_Hagemeister-20121002-youtube-dl_test_video_a-BaW_jenozKc-~1.82MiB.mp4
Thanks.

With https://github.com/yt-dlp/yt-dlp/commit/e0fd95737d1a3c4a2bfb470c5408a396c8545ca5, you can do %(filesize).2DiB

%(filesize).2DiB appears to give some sort of approximate size? Instead of the actual size as shown in -F?
Am I mistaken?
$ yt-dlp -F FJSI7QTAt_o | grep 3840x2160
313 webm  3840x2160   25 |    3.98GiB 8320k https | vp9         8320k video only              2160p, webm_dash

f313 is 3.98GiB. And the actual file size when downloaded is also 3.98GiB as shown in -F.
However, when I do
$ yt-dlp --print filename -f 313 FJSI7QTAt_o -o "%(filesize).2DiB"
4.28GiB

4.28GiB is way off the actual size of 3.98GiB.
It's not just f313. It's all formats.
The disparity is wider when the video filesize is larger so I've used f313 to illustrate.
But the %(filesize).2DiB for none of the formats match the correct size value as shown in -F.
Also for -f 22
yt-dlp --print filename -f 22 FJSI7QTAt_o -o "%(filesize).2DiB"
NoneiB

Instead of ~189.70MiB.

The D prefix uses 1000 based suffix. This is why the filesize was appearing different from what you expected. In https://github.com/yt-dlp/yt-dlp/commit/abbeeebc4c20bc5c690d96c83e91e89effd04b81, I have now added #D to use 1024 instead.
For -f22, the filesize is not known, only the filesize_approx is. If you want to use either, you can use filesize,filesize_approx as the key

Hey @pukkandan Thanks for the help but could you make it so that the decimals are not truncated?
yt-dlp --print filename -f 313 FJSI7QTAt_o -o "%(filesize)#DB"
3GiB

which is almost ~1GB away from the actual size of 3.98GiB
I'd very much like the output to be 3.98GiB as shown in -F.
Thanks!

It accepts the same format as float. So just do %(filesize)#.2DB


Error when using jsreport.binary.osx.ph2 on MacOS High Sierra

Hi there,
I have an ASP.NET Core 2 app using jsreport in a class library to create a pdf from some html. I've added both the jsreport.Local and jsreport.Binary.OsX.Ph2 packages. When I run it, an JsReportBinaryException is thrown. Interestingly when I run the exact same code in a console app, it sometimes works (first couple tries failed and then it started working). I also tried the same code ina  console app on Windows (jsreport.Binary package) with no issues.
The code in my library is as follows:
...
using jsreport.Local;
using jsreport.Types;

namespace MyProject.Repositories
{
    public class BookRepository : IBookRepository
    {
        ...

        private async Task CreatePdf()
        {
            try
            {
                var rs = new LocalReporting()
                    .UseBinary(jsreport.Binary.OSX.Ph2.JsReportBinary.GetBinary())
                    .AsUtility()
                    .Create();

                var report = await rs.RenderAsync(new RenderRequest
                {
                    Template = new Template
                    {
                        Recipe = Recipe.PhantomPdf,
                        Engine = Engine.None,
                        Content = "Hello"
                    }
                });

                using (var fs = File.Create("out.pdf"))
                {
                    report.Content.CopyTo(fs);
                }
            }
            catch (JsReportBinaryException ex)
            {
                var e = ex;
            }
        }

        ...
    }
}

Project file:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="jsreport.binary.osx.ph2" Version="1.10.0" />
    <PackageReference Include="jsreport.local" Version="1.1.2" />
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="2.0.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="2.0.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="2.0.2" />
    <PackageReference Include="WindowsAzure.Storage" Version="9.1.1" />
  </ItemGroup>
  <ItemGroup>
    ...
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.0" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" />
  </ItemGroup>
</Project>

Exception Message:
"Error rendering report: rendering has finished with errors:Error: An error occurred while trying to execute the command:    at onCriticalError ([eval]:36106:25)    at tryCatcher ([eval]:9718:23)    at Promise._settlePromiseFromHandler ([eval]:38241:31)    at Promise._settlePromise ([eval]:38298:18)    at Promise._settlePromise0 ([eval]:38343:10)    at Promise._settlePromises ([eval]:38418:18)    at Async._drainQueue ([eval]:4650:16)    at Async._drainQueues ([eval]:4660:10)    at Immediate.Async.drainQueues [as _onImmediate] ([eval]:4534:14)    at processImmediate [as _immediateCallback] (timers.js:396:17) {\"originalError\":{\"remoteStack\":\"Error: Command failed: /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/phantomjs.exe --ignore-ssl-errors=yes --web-security=false --ssl-protocol=any /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/standaloneScript.js /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/fab79ab0-6035-11e8-9796-059a117b593asettings.html\\n, Segmentation fault error: if you are using macOS Sierra with phantomjs < 2 remember that phantomjs < 2 does not work there and has bugs (https://github.com/ariya/phantomjs/issues/14558), try to upgrade to phantom 2 if using macOS Sierra\\n    at ChildProcess.exithandler (child_process.js:214:12)\\n    at emitTwo (events.js:87:13)\\n    at ChildProcess.emit (events.js:172:7)\\n    at maybeClose (internal/child_process.js:854:16)\\n    at Socket.<anonymous> (internal/child_process.js:330:11)\\n    at emitOne (events.js:77:13)\\n    at Socket.emit (events.js:169:7)\\n    at Pipe._onclose (net.js:487:12)\"}}(Original) Error: Error during rendering report: Command failed: /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/phantomjs.exe --ignore-ssl-errors=yes --web-security=false --ssl-protocol=any /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/standaloneScript.js /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/fab79ab0-6035-11e8-9796-059a117b593asettings.html, Segmentation fault error: if you are using macOS Sierra with phantomjs < 2 remember that phantomjs < 2 does not work there and has bugs (https://github.com/ariya/phantomjs/issues/14558), try to upgrade to phantom 2 if using macOS Sierra    at [eval]:39138:23    at ConcatStream.<anonymous> ([eval]:44860:43)    at emitNone (events.js:72:20)    at ConcatStream.emit (events.js:166:7)    at finishMaybe ([eval]:4229:14)    at afterWrite ([eval]:4115:3)    at nextTickCallbackWithManyArgs (node.js:486:18)    at process._tickCallback (node.js:384:17) {\"remoteStack\":\"Error: Command failed: /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/phantomjs.exe --ignore-ssl-errors=yes --web-security=false --ssl-protocol=any /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/compile/jsreport-1.9.2-ryBaRwiyG/standaloneScript.js /var/folders/_9/vkdjn0vn43l032b80b1q87r40000gp/T/jsreport/fab79ab0-6035-11e8-9796-059a117b593asettings.html\\n, Segmentation fault error: if you are using macOS Sierra with phantomjs < 2 remember that phantomjs < 2 does not work there and has bugs (https://github.com/ariya/phantomjs/issues/14558), try to upgrade to phantom 2 if using macOS Sierra\\n    at ChildProcess.exithandler (child_process.js:214:12)\\n    at emitTwo (events.js:87:13)\\n    at ChildProcess.emit (events.js:172:7)\\n    at maybeClose (internal/child_process.js:854:16)\\n    at Socket.<anonymous> (internal/child_process.js:330:11)\\n    at emitOne (events.js:77:13)\\n    at Socket.emit (events.js:169:7)\\n    at Pipe._onclose (net.js:487:12)\"}"

And the stack trace from the exception:
"   at jsreport.Local.Internal.LocalUtilityReportingService.<RenderAsync>d__10.MoveNext()\n--- End of stack trace from previous location where exception was thrown ---\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\n   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\n   at Admazing.Repositories.BookRepository.<CreatePdf>d__20.MoveNext() in /Data/GIT/verticalmotion_admazingbackend/source/Admazing.Repositories/BookRepository.cs:line 522"

Any thoughts would be appreciated.

Hmm, magically started working. Shrug. Closing.

How did it magically start working, because am using a mac with the same issue?

@huxaiphaer sorry, I wish I could tell you. I didn't change anything and it just started working. I don't really remember much else about the project.

Hey, I  managed to get it to work via this issue


Update index.js

Concatenated .addClass() calls.
Returns nodes directly instead of making variables.
Mobile responsive.

Looks good.

Just made a first-pass through this; it's looking good so far. I like that, as-per this PR, we'd be returning the jQuery collections directly, rather than declaring variables for them, and returning the variables.

Can you change @contributor to @contributors on lines 7, 22, and 42 of index.js?

Sure.

Thanks for the PR @darrylyeo. :shipit:


[feat] online store 2.0 structure

[x] Changed all template files from liquid to json files
[x] Added login page for stores without Multipass (Shopify Plus feature)
[x] Added giftcard template since it's not supported via the Storefront API
[ ] Update read.md file with the 2 new features above

closes #3

Hey @leeuwis ,
Thanks for your notification - looks good, I'll give this a go!

Closes #2


feat: add kubeadm provider

Signed-off-by: moweiwei<EMAIL_ADDRESS>
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Does this PR introduced a user-facing change?

Additional documentation, usage docs, etc.:

/lgtm

/lgtm
/approve


Template: status/500 - repo/branch_dropdown:12:82

Gitea version (or commit ref): 1.15.2 built with GNU Make 4.3, go1.16.7 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Git version: 2.30.2

Operating system: docker

Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x ] No

Log gist:

2021/09/15 18:24:29 ...s/context/context.go:195:HTML() [E] Render failed: template: repo/branch_dropdown:12:82: executing "repo/branch_dropdown" at <.root.BranchName>: invalid value; expected string
2021/09/15 18:24:29 ...s/context/context.go:185:HTML() [D] Template: status/500

Description
I did an update of gitea to the latest version and every time I try to open a repo it gives me error 500

Are you using custom templates?

No
Il mer 15 set 2021, 18:58 Lauris BH @.***> ha scritto:

Are you using custom templates?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/17062#issuecomment-920200848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWNKSIB4KQPIISXJ4TMCXTUCDGEVANCNFSM5EC4GZ4A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

What version did you update from?

What version did you update from?
1.12

Does your app.ini set [repository] ROOT?
yes

however I solved it by recreating the container, thanks for the quick support


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.415
Run: https://github.com/slsa-framework/example-package/actions/runs/10988524544
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.415
Date: Mon Sep 23 06:07:32 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.416
Run: https://github.com/slsa-framework/example-package/actions/runs/11007942630
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.416
Date: Tue Sep 24 06:09:55 UTC 2024
Tests are passing now. Closing this issue.


Permissions

I'd like to push a branch to be able to create a PR. However,
remote: Permission to Kaldek/rat-ratgdo.git denied to CarlKnox.

Just want to PR an alternate proto board layout.

Yellow is the 3v3 signals, Though I question using a voltage divider for D7.
I added a header pin for D8 since I'm using homekit-ratgdo. Not using it yet, but it's there when I need it.
#define STATUS_OBST_PIN         D8  // output for obstruction status

Hi mate, anyone cane submit a Pull Request.  Did you fork the repository first?

Yep,
Tried to push before forking.
Tried PR after branching.
I can try again when I have more time, but thought you might take advantage of the photos in the meantime.

Yeah, generally it's Fork, Edit, Push.


remove space

Hey Garcia, I'm not considering your pull request because ngScrollable's UX is supposed to be compatible with native scrolling where spacebar scrolls down one page when not focusing on input fields.
As workaround you may turn off keyboard support with ng-scrollable="{useKeyboard:false}" if that's a option for you.


[PEX Sponge build 131] Default rank being wiped on restart

Hi there,
I am running into a rather annoying issue with PEX Build 131 where upon restarting the server the default rank is being reset. The other ranks are still all set up and nothing changes with them.
Here is a log but I am not sure if it will point to anything :/
Log for PEX 131.txt

Already responded to in your double post #2456 .

Well this is for build 131, which (as far as i can tell from the change logs) is prior to the update to API 5.0 and is for the correct versions that I am using on my server. So I am a little confused as to why your closing this issue unless your just no longer planning on supporting 1.8.9 versions at all???
My previous post was in regards to 132, which I had tried using hoping it may contain a fix. I hadn't realized at the time that it had upgraded to API 5.0.
In the meantime I am having to enter an extremely long list of commands manually to re-enter all the permissions every time I restart my server for updates.

Yeah, different issue

Try using https://minions.aoeu.xyz/zml/pex-api4.jar -- It's a build of PEX with the latest changes but for API 4.x

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


v1.13 backports 2023-04-28

[x] #24838 -- agent: Handle correctly state when CEP is present in multiple CESs (@alan-kut)
[x] #25117 -- cmd/cleanup: Fix cleanup of generic XDP programs (@pchaigno)
[x] #25025 -- test: Unquarantine host firewall + nodeport test (@pchaigno)

Skip the commit 743b4e7d16123cdeb7c923044f1d35f247ef8a19 as the bug is not present in 1.13

Once this PR is merged, you can update the PR labels via:
$ for pr in 24838 25117 25025; do contrib/backporting/set-labels.py $pr done 1.13; done

/test-backport-1.13

/test-1.24-5.4

/test-1.23-4.19

/test-1.24-4.19

@sayboras Lots of CI job restarts. Did you try and triage the failures?

Lots of CI job restarts. Did you try and triage the failures?

Yes, the below is in my note, I forgot copied and pasted here
Test Summary

test-1.24-5.4 failed due to github checkout issue.
test-1.23-4.19

first run failed due to Suite-k8s-1.23.K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L7 policy Tests NodePort with L7 Policy, which is related to https://github.com/cilium/cilium/issues/25096

test-1.24-4.19

first run failed due to K8sDatapathConfig Host firewall With native routing, which should be fixed in https://github.com/cilium/cilium/pull/25199


RBERT implementation

As per #1250, this PR describes an additional classification head for BERT for relationship classification tasks. This work is originally documented in this paper. In addition, the new head can be used with RoBERTa, producing a new SOTA as far as I know....
I have included a new example script and associated utils file that demonstrate how it can be used:
run_semeval.py, and updated the README.md in examples accordingly.
Note, contrary to what I said in the original issue, there is no need for new tokenisation classes - rather, strings simply need to be preprocessed with entity delimiting characters prior to tokenisation, and the input ID's of these characters passed to the classification head (see included example for details)

Codecov Report

Merging #1301 into master will increase coverage by 0.49%.
The diff coverage is 98.32%.

@@            Coverage Diff             @@
##           master    #1301      +/-   ##
==========================================
+ Coverage   80.77%   81.26%   +0.49%
==========================================
  Files          57       58       +1
  Lines        8092     8328     +236
==========================================
+ Hits         6536     6768     +232
- Misses       1556     1560       +4

Impacted Files
Coverage Δ

...ytorch_transformers/tests/modeling_roberta_test.py
86.91% <100%> (+7.91%)
:arrow_up:

pytorch_transformers/configuration_rbert.py
100% <100%> (ø)

pytorch_transformers/tests/modeling_bert_test.py
97.44% <100%> (+1.12%)
:arrow_up:

pytorch_transformers/modeling_roberta.py
69.32% <92.59%> (+4.36%)
:arrow_up:

pytorch_transformers/modeling_bert.py
89.03% <96%> (+0.7%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f995b9...bf2b5c3. Read the comment docs.

Ok, I went through the PR.
This is a very nice work @RichJackson!
One thing we should simplify though is to not have a separate configuration for RBERT and roberta. I will update a bit the configuration classes so we can safely add new parameters in them and have them initialized to defaults values when loading from pretrained config.
Let me do that now in this PR.

Actually I can't push on your PR so I'll create a new one to update that.


CI & cmake changes

Fully implement CI jobs for building under VS environment
Align the cmake test file with the VS generator.
NB: The ci change in this commit rely on my pr branch #256. I'm not sure whether should I make pr directly or just wait upstream to merged #256 then make this pr.

NB: The ci change in this commit rely on my pr branch #256. I'm not sure whether should I make pr directly or just wait upstream to merged #256 then make this pr.

I'm not quite sure what you mean: Does #263 add to & improve the changes in #256? If so, we could simply close #256 and only merge #263, right? I was holding back #256 because of your final comment "Not final solution".
Otherwise things LGTM with two single comments where I'd appreciate feedback to properly understand things. Also waiting for CI to complete. Thanks very much for this work!


Manifest warning

The "Illandril's Token Tooltips" module's manifest contained the following unknown keys: "manifestPlusVersion"

This property has value for other places that read manifest files. Until and unless the Manifest+ standard is updated to move this field into flags, or places that rely on this information stop using it and start only using standard fields, it will stay.


Better handling of untyped node module imports

Consider importing an untyped module, eg. exceljs:
import exceljs = require('exceljs');

This results in an error that the module exceljs is not found. There is at least two ways to fix this:

Setting allowJs: true and maxNodeModulesJsDepth: 1
Declare an ambient module in a separate file

I think it would be better if instead we update module resolution semantics such that when we find an appropriate package.json without a typings entry, we store it away. Then if module resolution fails (ie. we also can't find an @types/exceljs), we go back and import the untyped package.json as a JS import. Thoughts?
You might argue that this should only be allowed with --allowJs, but it might also make sense to just always use this behavior when using node resolution rules as you may still not want to allow JS in your own project while still allowing your dependencies to be authored in JS without typings.

Is there anyway we can solve this in a non npm specific manner? I like the concept but tying it to node_modules/import_name and node_modules/@types/import_name is not something I would like to see.

Also, please, please, please improve documentation on "ambient modules". I've read the section seven times now, I still have no idea what the ambient modules are, how to define them and where to put the specs so that they are picked up by TS. Espec
It would be awesome, if there was a small section "you want to import module X. you create a file X.d.ts here. Then you do this and that and this"

I followed a chain of four closed tickets to get here. Glad to see the issue was addressed. Could someone please point to docs for this feature? How do I use it? For my sake, and for everyone else who may end up here. :)

This is part of<EMAIL_ADDRESS>release, so for now you will need npm install typescript@next.
Now having an import like import foo from "Foo" the compiler will check if there is a package Foo, e.g. node_modules\Foo\index.js if one is available, even if it does not have a .d.ts file along with it, no error will be reported. the type of the imports will be any.
if you use --noImplicitAny, you would get these import flagged as implicit anys.
hope that helps.

That helps a lot, thank you. It seems like for now (v2.0.10) we can also use declare module "Foo";?

yes. that is Shorthand ambient module declarations

Now having an import like import foo from "Foo" the compiler will check if there is a package Foo, e.g. node_modules\Foo\index.js if one is available, even if it does not have a .d.ts file along with it, no error will be reported. the type of the imports will be any.

Does this mean that if you've got a node module  that doesn't use index.js but instead relies on a main field in package.json that this feature doesn't work?

@radicaled We check for that too.

Now having an import like import foo from "Foo" the compiler will check if there is a package Foo, e.g. node_modules\Foo\index.js if one is available, even if it does not have a .d.ts file along with it, no error will be reported. the type of the imports will be any.

And what about relatively referenced JS modules? import Blah from './blah.js';
In this case, Blah ends up as "type Blah" and TS tries its best to infer the shape of the exported object from blah.js, which in my case, was wrong (it only identified some of the properties on the object - others get errors of property key does not exist on value of type Blah).   Hence, Blah is NOT of type any!  I have to do (Blah as any).method() to get it to work.
I would think many would be hitting this issue mixing TS and JS.

Hi @lvpro, if the file does not come from node_modules it is presumed to be your own code, so TypeScript will infer types. As I see it you have 2 options:

Quick fix: disable all inference for that file by adding blah.d.ts containing:

declare const blah: any;
export default blah;

Add enough info for TS to infer the existence of those methods (if not the parameter/return types). You could add this to the constructor:

/** @type {Function} */
this.get = this.post = this.put = this.delete = undefined;

And you will now get these methods in autocomplete, although you won't get signature help.

Hi @andy-ms
I do not consider the 2nd suggestion a solution as it pollutes the original JS unnecessarily (other than to make typescript inference work).
Regarding the first solution, I tried that, but apparently ambient module declarations do not work for relative imports.  https://www.typescriptlang.org/docs/handbook/module-resolution.html

The first suggestion would go in its own file, not in a declare module.

Hi @andy-ms
I do not consider the 2nd suggestion a solution as it pollutes the original JS unnecessarily (other than to make typescript inference work).
Regarding the first solution, I tried that, but apparently ambient module declarations do not work for relative imports. https://www.typescriptlang.org/docs/handbook/module-resolution.html
From reading over the github issues related to this, it seems global imports (from node_modules) are inferred as any if no index.d.ts/@typings is found, but relative imports, as you stated, get inferred (in my case, improperly). Since it's a relative import, I'm unable to do an ambient module declaration ... or I'm just not getting the syntax right. Original code is in the stackoverflow link above.

Does quick fix 1 only work if blah.d.ts is in the same location as blah.js?  It does work, but my team may not want .d.ts files polluting their code directories (we're slowly using Typescript on new areas of the system, 95% of it is an ES6 codebase).

Does quick fix 1 only work if blah.d.ts is in the same location as blah.js?

If you import the module with its name (i.e. import d from "foo";) and not with a relative path (i.e. import d from "./foo";) then you can either 1. put the .d.ts next to the .js, 2. put it somewhere else, and add a path mapping, or 3. add it to a folder, e.g. ./types/foo/index.d.ts and add ./types  to your typeRoots in the tsconfig.json.
if it is a relative import, then you need to put the .d.ts next to the .js

So in instances where one imports relatively (this would be especially common in a create-react-app codebase), it seems these are the options;

Hope the TS compiler can infer your JS right
If it doesn't, you have these options:

(blah as any).method() on every use of the import
add a new variable to your .ts such as const blahAny: any = blah;
add a .d.ts to the same location as the .js, which may not be desirable or appreciated by the owners of that location.

I wish we could opt-in to having the same behavior as modules within node_modules, wherein if a typing is not found, the module could default to type any.  I saw someone suggest import blah: any from './blah.js', which would be clean and simple syntax specifying the programmer's intent.


Update dependencies

BREAKING CHANGE: Requires Node 10+

:tada: This PR is included in version 0.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[feat] bpv2 (update de by adding delta instead of set)

Description
Brief Description of the PR:
DE of tfra used to update embeddings / slots of embeddings by setting values, which introduces race condition problem among workers.
This PR solves this problem by updating MHTs of DE using the CuckooHashTable.Accum.
Type of change

[ ] Bug fix
[x] New Tutorial
[x] Updated or additional documentation
[ ] Additional Testing
[x] New Feature

Checklist:

[x] I've properly formatted my code according to the guidelines

[x] By running yapf
[x] By running clang-format

[ ] This PR addresses an already submitted issue for TensorFlow Recommenders-Addons
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

How Has This Been Tested?
If you're adding a bugfix or new feature please describe the tests that you ran to verify your changes:

see ./demo/bpv2/main.py
see ./tensorflow_recommenders_addons/dynamic_embedding/python/kernel_tests/dynamic_embedding_optimizer_test.py

Hi @nrailgun ,thank you for your excellent job, that 's really useful optimization.

LGTM


Remove .vscode dir

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 65.85%. Comparing base (eb50d20) to head (579cfb0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   65.85%   65.85%
=======================================
  Files          63       63
  Lines         984      984
  Branches       70       70
=======================================
  Hits          648      648
  Misses        295      295
  Partials       41       41

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


sink(ticdc): Add support for GBK charset

What problem does this PR solve?

Issue Number: ref #4806
What is changed and how it works?
To support GBK charset for MySQL sink, we do the following things:

Specifying the charset param with utf8mb4 in dsn (equals to set names utf8mb4) for MySQL connection. The reason is that we know the column value received from TiKV is always encoded in utf-8. So when we write those utf-8 column values to MySQL sink, we must ensure that the session-level variables character_set_client, character_set_connection are set to utf8mb4.
Using the string representation instead of byte array when parsing SQL events from KV events which have types such as CHAR, VARCHAR, TEXT, etc. Because if we use byte array for a column, the go-sql-driver will automatically set _binary for that column. Considering a table with a GBK charset column, the data written to that column is always in utf-8 other than GBK, which is not expected.

Check List
Tests

Unit test
Integration test

Release note
None

DDLs which containing GBK databases/tables/columns should also be considered.

@zhaoxinyu It would be nice if we could add some unit tests for the changes corresponding to the mouter.

@zhaoxinyu It would be nice if we could add some unit tests for the changes corresponding to the mouter.

OK, I will add later

/run-integration-test

Could you port TiDB GBK tests?

I will push forward PR https://github.com/pingcap/tiflow/pull/4695 for the TiDB GBK tests.

/run-dm-integration-test
/run-kafka-integration-test

/run-integration-test

/run-all-tests

Investigating a unit test failure of TiFlash. https://ci2.pingcap.net/blue/organizations/jenkins/cdc_ghpr_kafka_integration_test/detail/cdc_ghpr_kafka_integration_test/9772/pipeline/

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-verify

Codecov Report

Merging #4807 (5098856) into master (687e248) will decrease coverage by 0.2826%.
The diff coverage is 50.6357%.

Flag
Coverage Δ

cdc
61.0062% <54.0284%> (+0.4076%)
:arrow_up:

dm
51.7501% <49.0710%> (-0.7195%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4807        +/-   ##
================================================
- Coverage   56.1240%   55.8414%   -0.2827%
================================================
  Files           522        524         +2
  Lines         65325      66508      +1183
================================================
+ Hits          36663      37139       +476
- Misses        25094      25720       +626
- Partials       3568       3649        +81

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-integration-test

/run-leak-test

/run-dm-integration-test

/run-verify

/run-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

/run-all-tests

/merge

/run-verify

/run-leak-test

/run-verify

/run-verify

/run-verify


Add test debugging support

When cli.js executed by Node.js running in debug mode, child processes are also running in debug mode with different port.
It is possible to run cli.js in normal mode and debug only child processes using --debug option.
It is possible to specify debug port after --debug option.
Close #108.

Guys, what is required to merge this PR? Or do you have any other suggestions on how to debug qunit tests?


[staging-next] llvmPackages_8.llvm: fix build with gcc 10

Applies a patch from the gentoo bugtracker: https://bugs.gentoo.org/732094
Builds llvmPackages_8.llvm and dependee ccls, as reported broken in https://github.com/NixOS/nixpkgs/pull/89793#issuecomment-751768575
cc @MetaDark @FRidh
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thanks @r-burns! It looks like the patch is based on a change submitted upstream: https://reviews.llvm.org/file/data/tvo2b5dbskz6ybaz2zcn/PHID-FILE-lrja2af5rozq3grqej5g/file, but the upstream patch contains the whole context of the file, which is probably unnecessary.
I'm just waiting for the build to finish to verify the fix.

Thanks!


No object Radium.Config or Radium.config

From docs https://github.com/FormidableLabs/radium/tree/master/docs/api#configsetmatchmedia
Radium has no "Config" of "config" object in radium/dist bundle (i'm use webpack import).
Edit: commit with this feature will added 12 day ago. Maybe the time has come for new release?

Ah yes, that hasn't been released to npm yet. Docs are uptodate with
master. I can cut a release this weekend if I have time.
On Sat, Jun 20, 2015 at 7:17 AM MaxSvargal<EMAIL_ADDRESS>wrote:

From docs
https://github.com/FormidableLabs/radium/tree/master/docs/api#configsetmatchmedia
Radium has no "Config" of "config" object.
—
Reply to this email directly or view it on GitHub
https://github.com/FormidableLabs/radium/issues/220.


Embedding API request: config.errorFn

Embedders currently can set the writeFn for their VMs using a WrenConfiguration object.
I would like a similar process for wren runtime error output.
My particular use case is an in-browser wren editor with on-screen debugging, but I expect this feature could be useful for other types of applications.
I have a solution on my end that involves configuring emscripten, but this seems useful enough to merit a pull request.
I'm not really competent in C, but I think this could be achieved by having all the printfs here store to some string buffer, passing that to a config.errorFn.
I'll start there, and see where that takes me.

Yes, allowing the embedder to control all error output is definitely on my TODO list. I haven't yet because, as you note, you have to do some sort of string buffering to handle formatting and printf.

Wow, didn't notice that #265 was pretty much identical to this bug. I'll close and continue working on this over there.


Correct Category Page Footer Text Background

Pull Request Checklist
Issue - #1541

[x] I have added screenshots and videos to show before and after the working of my code.
[x] I have ensured that the screen size is set to 100% while making the video.
[x] I have synced the latest fork with my local repository and resolved any conflicts.
[x] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[x] I understand that if any the above conditions are not met , my PR will not be MERGED .

sync fork

hey @AnushkaChouhan25 there are a lot of changes done which are not even required , you have removed some routes from backend and also changed some code in backend folder completely irrelevant to your issue ,kindly check

Hey @ANSHIKA-26, I have doubts regarding this problem, Can you please help me?
This happened sometimes I made changes in only one file which was required but all other files also got added in which I did not make any changes, and this happens after committing,
all the files get pulled including the changes which I did not make.
And I use GitHub Desktop to contribute to the repo and face this same problem.

try syncing fork , then making a new PR

I always sync pr first then start work, and Not happened with all repos but yes with some other.

Hi @ANSHIKA-26, I made a new pr, Can you review it?


Support Do Not Track standard

https://consoledonottrack.com/

Is this a standard? Seems like it's been adopted by two relatively small projects, and that's it 👀


NAT Gateway support?

Is there a way to handle this? If not... can we get it? Not sure I'm the person to step up and build it, sadly.

@n8gard The latest version, Terraforming v0.10.0 has support of NAT Gateway. Please try it.


no module named '_bz2'

Hi, I was trying to running this bot, and then error appear... no module named '_bz2'

Can you print these two commands to ensure they are the proper versions?
ubuntu@ip-172-26-4-99:~$ python3.11 -V
Python 3.11.0
ubuntu@ip-172-26-4-99:~$ pip3.11 -V
pip 23.1.2 from /home/ubuntu/.local/lib/python3.11/site-packages/pip (python 3.11)

Also, are you using the main branch or are you testing the bot-multiexchange branch? If you have not already, check out the branch "bot-multiexchange" and follow the python3.11 installation instructions there and proceed using that branch if possible; it is recommended.

thanks for all, I am trying to use the bot-multiexchange branch, but now i have the next error,
Strategy.init() missing 1 required positional argument: 'manager'

Looking into this, saw it yesterday but got distracted. Which exchange & strategy are you trying to load? By the error you have pasted, it does seem as if I could have missed something in one of the many strategies.
Try running it like this if it was Bybit for example
python3.11 bot.py --exchange bybit --symbol ARBUSDT --strategy bybit_hedge_dynamic_full --config config_bybit_sub1.json
and for bitget
python3.11 bot.py --exchange bitget --symbol ARBUSDT_UMCBL --strategy bitget_hedge_dynamic --config config.json
and for huobi
python3.11 bot.py --exchange huobi --strategy huobi_hedge --amount 1 --symbol SUIUSDT --config config_huobi_main.json
Where config_bybit_sub1.json or however I have named mine, would just be your config file name in your configs folder which is located in the projects main directory.


[Feature] Read database password from Docker secret file

Hi there,
I plan to use Gitea in a production environment on a Docker Swarm cluster. I want to avoid having clear-text passwords in my docker-compose file.
An easy way to protect credentials with Docker Swarm is to use secrets. See https://docs.docker.com/engine/swarm/secrets/
Docker secrets are mounted as files in the container, so I can't use the environment variable DB_PASSWD.
A workaround used by images like MySQL or Postgres is to provide an environment variable storing the path of the secret, e.g. DB_PASSWD_FILE, then read that file. See section "Docker Secrets" on https://hub.docker.com/_/mysql for an example.
It would be nice to have the same for Gitea. This would only require an additional step during Gitea s6 setup, before setting default configuration variables.
if [ -n "$DB_PASSWD_FILE" ] && [ -r "$DB_PASSWD_FILE" ]; then
    DB_PASSWD=$(cat $DB_PASSWD_FILE)
fi

Here is a minimal docker-compose example where I used a custom image to add the above step.
version: '3.7'

services:
  git:
    image: custom-gitea
    environment:
      DB_TYPE: mysql
      DB_HOST: db:3306
      DB_NAME: gitea
      DB_USER: root
      DB_PASSWD_FILE: /run/secrets/db-password
      ROOT_URL: git:3000
      SSH_DOMAIN: git
      SSH_PORT: 22
    ports:
      - 3003:3000
    networks:
      - default
    secrets:
      - source: db-password
        target: /run/secrets/db-password
        mode: 0400

  db:
    image: mysql:5.7
    environment:
      MYSQL_ROOT_PASSWORD_FILE: /run/secrets/db-password
      MYSQL_DATABASE: gitea
    networks:
      - default
    secrets:
      - source: db-password
        target: /run/secrets/db-password
        mode: 0400

networks:
  default:
    driver: overlay

secrets:
  db-password:
    file: './db-password'

Steps :
# On a Docker Swarm cluster
echo 'mydatabasepassword' > db-password
docker stack deploy -c docker-compose.yml gitea-test

Gitea version (or commit ref): 1.10
Operating system: Docker
Database (use [x]):

[x] PostgreSQL
[x] MySQL
[x] MSSQL

Another way is to store password on envs.

Is there a way to have them hashed as environment variables ? I can't find anything about this in the documentation.
With Docker secrets, I avoid writing them in clear-text, which is a security concern.

If you create separate network for db and add only db and Gitea to it noone else will be able to connect to it so this way password complexity does not matter anymore

From the outside, Gitea being on an overlay network (which I'm already using) doesn't change a thing. It is easier to read an environment variable than a file. My point is also to not have sensitive values such as passwords in docker-compose.yml, especially if it is versioned.

I would like to see this feature implemented as well. +1

I too would like to see this, it is very important to easy infrastructure as code deployments. Databases like mariadb and postgres already support this (when setting the env variables, you just append _FILE to the end like DB_PASSWORD_FILE) and many other applications are adding in support as well (see the docker secrets section here).
It is now pretty standard practice to not include plain text passwords in the docker compose file or to inject them at runtime so this would be a great addition.

I agree that this is an important feature that is currently sorely missing!

I agree that this is an important feature that is currently sorely missing!

I solved this using a custom entrypoint script.

Copy the original entrypoint script with following adjustments (diff):

1c1
< #!/bin/sh
---
> #!/bin/bash
26a27,40
> ## Set environment variables by their respective secrets
> supportedSecrets=( "GITEA__database__PASSWD"
>                    "GITEA__mailer__PASSWD"
>                  )
> for secret in ${supportedSecrets[@]}; do
>     envFile="${secret}_FILE"
>     if [ $(printenv ${envFile}) ]; then envFileName=`printenv ${envFile}`; fi
>     if [[ ${!envFile} && -f "$envFileName" ]]; then
>         val=`cat $envFileName`
>         export "${secret}"="$val"
>         echo "${secret} environment variable was set by secret ${envFile}"
>     fi
> done
>

Mount that entrypoint in your docker-compose

volumes:
    ...
      - ./gitea/entrypoint:/usr/bin/entrypoint

You're done. Gitea now supports secrets for GITEA__database__PASSWD_FILE & GITEA__mailer__PASSWD_FILE. You can use them like this:
# docker-compose
secrets:
  gitea_db_password:
    file: $SECRETSDIR/gitea_db_password

services:
  gitea:
    image: gitea/gitea
    ...
    environment:
      GITEA__database__PASSWD_FILE: /run/secrets/gitea_db_password
    secrets:
      - gitea_db_password

@DennisGaida Thanks for the code, it works great.
One problem with adding secrets now is that the variable is added as a parameter in gitea's app.ini file:
PASSWD_FILE = /run/secrets/gitea_mariadb_password
This seems to be expected according to the documentation:
In addition to the environment variables above, any settings in app.ini can be set or overridden with an environment variable of the form: GITEA__SECTION_NAME__KEY_NAME.

Don't know if this will cause any issue in the future. Just a heads up for those who are trying to implement secrets in gitea.

Another way is to store password on envs.

This is the classic (read old) way of doing it, but passing sensitive data via environment variables is not a good idea (also read here).
I also believe @DennisGaida's suggestion can lead to problems: passing sensitive data via secrets and then exporting them to env vars gives other processes the ability to read them. We should use secrets as they are intended to.
That's why several images out there are being updated to support the _FILE version of sensitive env vars, +1 for the feature.

I also believe @DennisGaida's suggestion can lead to problems

Please don’t take my workaround as a suggestion - I would have created a PR if I thought it were a solution. I‘m working with what we have: secrets in environment variables.
secrets should be natively supported so this feature request is totally valid.

Here's one idea to add this feature. How about expanding environment-to-ini, such that it can read a configurable env (or ini) file. This could be a docker secret and won't need to be exposed as environment variables to any other process.
This is already a docker-specific utility intended to rewrite the app.ini, it would just add one more source of inputs.

Guys, this is important feature for prod using. How can we upvote it?

this is important not only for database. I want to use secret and for smtp too.

Duplicate of https://github.com/go-gitea/gitea/issues/19856
There is promising pull request https://github.com/go-gitea/gitea/pull/19857


pyproj/geopandas compatibility

fixes potential compatibility problem in forthcoming geopandas version: https://github.com/geopandas/geopandas/pull/1101#issuecomment-570727439

Coverage decreased (-0.06%) to 92.955% when pulling 8f84acc33b007b68911bb6452b1da339f72b04fd on pyproj into 71cd658df68391d24501d63c42a52712e18edcb7 on master.


Switch to using MonitorMechanism to get Mechanisms

This is built on PR #336, #337, #338
Only the last commit is from this PR.

I think these changes are reasonable. Not sure if you want to merge yet.

@fkautz #337, #338, #340 should be good to go :)

@fkautz Also #336
If you don't mind, I'd like to go PR by PR for the merge.  I strongly approve of our squash and merge policy... but just merging #340 is a bunch of things jumbled up together it might be nice to have a separate commits :)


chore(ci-cd): add the github release workflow

releases will be via the workflow
GH-71
Description
Added the release.yml file
also added the necessary screts and variables at repo level
Fixes #71
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

:tada: This PR is included in version 5.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix popup spawn in wrong position

I don't think this is an issue, it's more like a configurable property of the popup


Changes for Meteor 1.6.1

Up versions for compatibility

Hi, thanks for reporting.
I do not use meteor for long time.
Does there are some braking changes and I cant use just api.versionsFrom("METEOR@1.0.4");?
(Currently I have Easter holidays and can test > Wednesday )

<EMAIL_ADDRESS>has the effect of locking coffeescript version at 1.x, and Meteor 1.6.1 requires coffeescript 2+ (see https://blog.meteor.com/announcing-meteor-1-6-1-50aad71da4e6 for details)

Understood, I added reminder to myself to come back after holidays (Wednesday).


ModelBuilder.swift Compile error in Xcode 8.1

function transformableType
ValueTransformer.registerTransformerWithName(transform.name, transform: t, reverseTransform: r)
error:

Cannot convert value of type '(A?) -> Data?' to expected argument type '(_?) -> _?'

Xcode auto migrate feature will change NSData to Data by default.
I think we can still use NSData in swift 3.0.
So my workaround is the following ( use NSData instead of Data in ModelBuilder.swift)
public struct DataTransform<A> {     public let name: String     public let forward: (A) -> NSData?     public let reverse: (NSData?) -> A     public init(name: String, forward: @escaping (A) -> NSData?, reverse: @escaping (NSData?) -> A) {         self.name = name         self.forward = forward         self.reverse = reverse     } }
@floriankugler Will you guys update the core-data project to swift 3.0?

@kinwahlai Yes, we're currently working on updating the whole book for Swift 3/iOS 10. Should be done pretty soon.

We'll push an update in the next days.


Renew Tokens

Hi,
I'm new with using the quickbooks API. After 180 days the token has expired. How do I renew the quickbooks token?
Moses

client = QuickBooks(
    sandbox=True,
    consumer_key=QUICKBOOKS_CLIENT_KEY,
    consumer_secret=QUICKBOOKS_CLIENT_SECRET,
    access_token=access_token,
    access_token_secret=access_token_secret,
    company_id=realm_id,
    minorversion=4
)

client.reconnect_account()

Not sure why this wasn't in the readme, but I will add it.

Hey, just a note here: reconnecting the account doesn't work the best when the Quickbooks is run in the singleton mode. Had to call disable_global() after the token was reconnected (or restart the webserver)


Support other TLS/SSL certificates formats (currently only PEM)

https://github.com/maykinmedia/django-simple-certmanager/pull/40#discussion_r1703670347
It would be interesting to consider the other files formats for the certificates we upload. So far we have decided to only support PEM.

# Create custom error classes for better error handling
class Invalidx509CertificateError(Exception):
    pass

class InvalidPKCS12CertificateError(Exception):
    pass

class InvalidPKCS7CertificateError(Exception):
    pass

def load_certificate_file(
    cert_file: InMemoryUploadedFile, password: Optional[str] = None,
):
    if cert_file.content_type == "application/x-x509-ca-cert":
        # Verify if PEM or DER
        # Could be multiple certificates in one file
        try:
            certs = x509.load_pem_x509_certificates(cert_file.read())
        except ValueError:
            try:
                # DER method only accepts one certificate
                cert_file.seek(0)
                certs = x509.load_der_x509_certificate(
                    cert_file.read(), default_backend()
                )
            except ValueError:
                raise Invalidx509CertificateError()
    elif cert_file.content_type == "application/pkcs12":
        # Could be multiple certificates in one file
        # Password is required for PFX/P12
        try:
            certs = pkcs12.load_pkcs12(
                cert_file.read(), password.encode(), default_backend()
            )
        except ValueError:
            try:
                cert_file.seek(0)
                certs = pkcs12.load_key_and_certificates(
                    cert_file.read(), password.encode(), default_backend()
                )
            except ValueError:
                raise InvalidPKCS12CertificateError()
    elif cert_file.content_type == "application/x-pkcs7-certificates":
        # Verify if PEM or DER
        # Could be multiple certificates in one file
        try:
            certs = pkcs7.load_der_pkcs7_certificates(cert_file.read())
        except ValueError:
            try:
                cert_file.seek(0)
                certs = pkcs7.load_pem_pkcs7_certificates(cert_file.read())
            except ValueError:
                raise InvalidPKCS7CertificateError()
    elif cert_file.content_type == "application/x-java-keystore":
        # Password is required for JKS
        raise NotImplementedError()

    return certs


Add base changelog for 1.17.0

PR Summary
PSSA is getting close to the release and this is the preparation for it. The readme also gets tweaked
The date in this changelog is not final, we aim for it but do not promise anything.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] User facing documentation needed
[ ] NA Change is not breaking
[ ] NA Make sure you've added a new test if existing tests do not effectively test the code changed
[x] This PR is ready to merge and is not work in progress

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

Should this additional information not be quoted?

@LaurentDardenne It was already announced for 1.16 if you look at the changelog here
I will see if I can update the documentation on it to make its usage clearer.

should we have a different PR to change the versions in the various .csproj files?

@JamesWTruher Yes, I think so. This will make it also easier in future releases to see what needs to be changed/done.


RTL is not fully supported

I enabled rtl support : http://coreui.io/docs/getting-started/rtl-support/
Unfortunately it seems that rtl is not fully supported, please check out those pictures:

Am I missing something?

The solution was to attach dir="rtl" to the html tag and style="text-align: right;" to the body tag.


Clarification Required: Configuration

I am not sure of the point of this whole section. What you click on and what you see don't match, and there is no outcome in terms of the lab.
Configuration using ConfigMaps
The UI does not display the entire configMap as the steps suggest. All you get is the data

Secrets
The UI does not display the secret as per the steps elude.

Configuration using Environment Variables
The UI does not match the contents - and some of the environment variables are not even there. E.g. ENV_TOY_CONFIGMAP

Cc @okashi18


Update guide to fix menu item issue

Fixes #1195
This fixes the steps in the guide that shows how to add menu items to restaurant and order models.

Coverage remained the same at 96.5% when pulling 84c4345f6232d8436328f6a2a1f7071d6cabe692 on fix-in-depth-pmo-guide into 0b0f54687e403a9282574bbf75c79f5c4d62c43f on master.

Coverage remained the same at 96.5% when pulling 84c4345f6232d8436328f6a2a1f7071d6cabe692 on fix-in-depth-pmo-guide into 0b0f54687e403a9282574bbf75c79f5c4d62c43f on master.


DEBUG

Signed-off-by: Johannes Schindelin<EMAIL_ADDRESS>

This. Is. Not. Working.
I cannot seem to find any way to convince Actions to skip a workflow when the environment is protected and will not allow the workflow to be run.


At least one peer is required: (HTTP 400: error)

In testing the MPA email workflow I found that if I selected about 10 out of the 12 members of our group to request approval from, it would error out
At least one peer is required: (HTTP 400: error)

Selecting only a few members allowed the approval request to proceed

The number of approvers is currently limited to 10. That limit is arguably too low, and the error message is misleading too.
Thanks for flagging this.

We are using a group w/ 12 members, but should it allow the group itself to be displayed as a checkbox (as a single approver), perhaps in an expandable list?  If we had a group: principal which is used with 4 subgroups, that is our use-case, to choose which team to send to for approval instead of individuals.
Like:

[ ] engineering

[ ] team a

[ ] bob
[ ] alice

[ ] team b
...

I created a fix that introduces a new environment variable ACTIVATION_REQUEST_MAX_REVIEWERS. Using this variable, you can customize the maximum number of peers that users can select as reviewers. The default is still 10.

We are using a group w/ 12 members, but should it allow the group itself to be displayed as a checkbox (as a single approver), perhaps in an expandable list?

The application (or the Policy Analyzer API, to be precise) expands groups, so you should only see users in that list.
Changing the behavior to show groups might be tricky:

We could disable group expansion so that groups are shown just as they're listed in an IAM policy. But then users have no way of seeing whether the group actually contains any members, or whether it's a group with hundreds of members.
The fact that a group has access to a resource also doesn't necessarily mean that all members have access too, as some members might be subject to a deny policy.

Showing both, the group and its members might be an option. But it might be quite inefficient as the Policy Analyzer API can only return one of the two, so the app would need to make 2 calls.

Great, yes the expandable groups is not a must-have, as long as we can control the max reviewers that's great, thank you for the fix.
I received some feedback from our teams on the approval email, will submit those as new feature request issues.

Ok, thanks. I'll close this issue then and will await your additional feature request regarding the approval emails.


Add convenience asserts for handling errors

Handling errors should almost always use t.FailNow so provide convenience functions for Error, ErrorContains, and ErrorType from cmp.

LGTM 🤠


Support for earlier versions of python

Right now the SDK requires 3.6.2 or above. My concern is that many journalists may not be able to install newer versions of Python because of IT restrictions. Also I know that many were still on Python 2 as of a year or two ago, but that may not be the case. Not sure we need to support Python 2.

I think I'm going to close this as we wrote the SDK with some features like format strings that were introduced in 3.6. For farmshare you can download and copy the binary up. If people start complaining about requiring 3.6, we can see how to relax it. Closing for now


amazon2csv.py unable to generate output.csv with data extracting from Amazon

Hi author/ tducret,
I download all your files and attempted to run python setup.py install. Next, i  tried running amazon2csv.py followed your instruction steps found in https://github.com/tducret/amazon-scraper-python which says " You can also pass a search url (if you added complex filters for example), and save it to a file ".
However, on Windows command prompt windows session when i run this command   "  amazon2csv.py --url="https://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywords=python+scraping" > output.csv ", my output.csv file is generated however there's no data found inside the output.csv file.  Any advise what steps have i missed out which resulted to the output.csv file being empty (ie: no data extracting from url = https://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywords=python+scraping" ) ?
See below screenshot as a proof / reference

Hi @clementks
Sorry about that, but Amazon is definitely stronger than me. It's very hard to keep pace with their anti-scraping protections.
I'd really appreciate if somebody wanted to update the code though.

Hi tducret,
Thanks for your advice/response, in other words, u are implying that your amazon scraping program upon you upload to github, back then it works fine and able to export into csv file.
Pardon me as i'm not proficient in OO in Python, may i ask you if i were to perform web scrapping on another website (ie: https://www.walmart.com/), what product attributes does it need/require so that i can get your advice on what  to modify init.py, client.py etc ? I learnt a great deal on OO in Python from your program, which i would like to use it for my other project development. Hence, thanks a lot for your sharing by uploading into github