Increase test coverage for scale

As it stands, scale has a sub-100% test coverage. We got deducted marks on this so it would be best to ramp that number up.

From CodeCov:
https://app.codecov.io/github/UBC-MDS/VisuMorph/blob/main/src%2Fvisumorph%2Fscale.py

@shawnhu444 would you be able to take care of this issue before the deadline?


errors of loading gaokao datasets

[x] load_dataset("gaokao2019_np2","writing-grammar")

[x] load_dataset("gaokao2021_npb","writing-grammar")

The following two will be easier to fix when the above is done.

[x] Missing: "gaokao2019_np2","writing-grammar"
[x] Missing: "gaokao2021_npb","writing-grammar"

done with @yyy-Apple


high level deny overriding low level allow in doc.$determineAccessToAllPermissionsForResources()

eg.

deny permission on organization resource

allow permission on group resource

Should result in true for that permission checked against a user uid within the group, but returns false instead

additionally if there are conflicting denies + allows at the same parent level, the deny should win

fixed in 0.0.49

This solution causes major performance issues -- need to find another way :/

fixed in 0.0.52


[catch2] Don't install docs

Describe the pull request

What does your PR fix?
Disable installing docs

Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@FrankXie05 Why requires:author-response?

@Thomas1664 Could you please explain why want to turn off the option to download documents? :)

@Thomas1664 Could you please explain why want to turn off the option to download documents? :)

Our policy is to not install docs by default.
Copying docs takes time (not much here, though)

Thanks!


NameError: name 'mx' is not defined (python)

from skimage import io
import mxnet
test='C:/Users/Admin/Desktop/test.lst' # folder where must be my test.lst
DataSet='C:/Users/Admin/Downloads/mypic/' # folder with my pictures (20 pics

data_iter = mx.image.ImageIter(
... batch_size=4,
... data_shape=(3,816, 1232),
... label_width=4,
... path_imglist='test.lst',
... path_root='DataSet')
Traceback (most recent call last):
File "", line 1, in
NameError: name 'mx' is not defined

why mx is not defined, i loaded mxnet?

import mxnet as mx

yes, it works, but
i get error
Traceback (most recent call last):
File "", line 6, in
File "C:\Users\Admin\AppData\Local\Programs\Python\Python37-32\lib\site-packag
es\mxnet\image\image.py", line 1071, in init
with open(path_imglist) as fin:
FileNotFoundError: [Errno 2] No such file or directory: 'test.lst'

but this file there is ion my desktop

close since the issue is solved.


Fix tests on unix and make tests more reliable on all platforms

cc @moozzyk

Looks like this would increase the test run time a bit. Not sure if there's an alternative though.
:shipit:

:ship: :it:


Profile - Clicking the profile icon again causes the page to load endlessly

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch app
Tap Fab
Tap new chat
Tap user having custom profile picture
Tap on profile icon in header
Tap profile icon in profile page to open profile image page
Tap back button
Tap profile icon again to visit profile image page
Repeat step 2 - step 8 for different users having custom profile picture

Expected Result:
When user with custom picture, re-tap on profile icon to view profile image again, it should be displayed without any problem
Actual Result:
When user with custom picture, re-tap on profile icon to view profile image again, the profile image page keeps on loading infinitely
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/988f6152-0fd0-4333-8e92-728196da13ea
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Closing this as dupe.


CocoaPods could not find compatible versions for pod "Macaw": (~> 0.9.6)

Am i doing something wrong with my setup?
I also tried pod repo update.
remote-ios on  master [✘»!+?] took 1m32s
❯ pod install
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Macaw":
  In Podfile:
    Macaw (~> 0.9.6)

Specs satisfying the `Macaw (~> 0.9.6)` dependency were found, but they required a higher minimum deployment target.

Is it because Swift 5? I'll try earlier versions. Cheers. Currently using Swift 4.2:
# 8.0 Required for pods
platform :ios, '8.0'

target 'remote-ios' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for remote-ios
  pod 'RxSwift', '~> 4.0'
  # To fix keyboard problems
  pod 'IQKeyboardManagerSwift'
  # Material Design + nav drawer
  pod 'Material', '~> 3.1.0'
  # JSON obj mapping
  pod 'ObjectMapper', '~> 3.5'
  # SVG support for ios 8+
  pod 'Macaw', '~> 0.9.6'

  target 'remote-iosTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

remote-ios on  master [✘»!+?] took 4s
❯ pod deintegrate
Deintegrating `remote-ios.xcodeproj`
Deleted 1 'Check Pods Manifest.lock' build phases.
Deleted 1 'Embed Pods Frameworks' build phases.
- Pods_remote_ios.framework
- Pods-remote-ios.debug.xcconfig
- Pods-remote-ios.release.xcconfig
Deleted 1 'Check Pods Manifest.lock' build phases.
- Pods_remote_iosTests.framework
- Pods-remote-iosTests.debug.xcconfig
- Pods-remote-iosTests.release.xcconfig
Deleted 1 empty `Frameworks` groups from project.
Removing `Pods` directory.

Project has been deintegrated. No traces of CocoaPods left in project.
Note: The workspace referencing the Pods project still remains.

remote-ios on  master [✘»!+?]
❯ pod clean

remote-ios on  master [✘»!+?]
❯ pod install
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Macaw":
  In Podfile:
    Macaw (~> 0.9.6)

Specs satisfying the `Macaw (~> 0.9.6)` dependency were found, but they required a higher minimum deployment target.

remote-ios on  master [✘»!+?]
❯

Hmm. https://github.com/exyte/Macaw/blob/master/Macaw.podspec#L20
Looks like the readme needs update?


GridFS example

https://github.com/VeliovGroup/Meteor-Files/issues/114

Could you re-send PR to dev branch?

Sure, here it is: https://github.com/VeliovGroup/Meteor-Files/pull/116

Thank you, I'll close this one then


Tests fail

https://gist.github.com/PetrKryslUCSD/284fbe5235809039b8ad3581f0059f55

My first comment would be why are you testing GridapPETSc.jl, instead of GridapSolvers.jl?
Otherwise, the error seems to be related to MPI.

Where are you running your tests? Are you using custom binaries, or artifacts?
When using MPI you have to build your project, not only instantiate. Most weird errors go away after building, which is crucial to link all the binaries together.

You are right, I did start by testing GridapSolvers, but the errors below seemed to implicate GridapPETSc. I may be wrong, of course.
This is from the failed test of GridapSolvers:
https://gist.github.com/PetrKryslUCSD/3114a3e5e0a64adc2ba53f14a6c204ca

You are right, I did start by testing GridapSolvers, but the errors below seemed to implicate GridapPETSc. I may be wrong, of course.
This is from the test of
https://gist.github.com/PetrKryslUCSD/3114a3e5e0a64adc2ba53f14a6c204ca

It's an MPI issue, I think. The serial tests are running fine on both cases, but it fails to load the environment when doing the MPI tests.
Try building the packages first, then run the tests. Instantiating is not enough. I.e
using Pkg
Pkg.build()

I did what the README suggested. Activ/inst + build.

I think MPI.jl might have disabled some mpiexec flags we were using (namely --allow-run-as-root), I've pushed a couple changes to main.
Could you please try this:
using Pkg
Pkg.add(;name="GridapSolvers",rev="main");
Pkg.build()

then exit and re-start julia, which allows the links created by build to take effect. Once this is done, try testing it.
I just tested this on our linux cluster, and it seems to run.

Fantastic, all tests pass.

Great, I'll do a new minor release and modify our README to make all of this more clear.


Unable to receive calls in Homestead

First of all, love the name!
I'm unable to receive any messages using Ray from Homestead, I wish I had more details but unfortunately the welcome never disappears and no errors appear.
Returns string but nothing ever appears in the Ray client.
Route::get('test', function () {
    ray('Hello');

    return 'done!';
});

macOS Cataline Version 10.15.7
Laravel 7.30.1
Vagrant 2.2.14
Homestead 10.17.0
PHP 7.4.13

I have got this working on my Homestead installation (albeit with a modification to the package code). Make sure your host in your config file is set to <IP_ADDRESS>.
Due to an issue in the service provider, the host is not correctly applied to the request. I've submitted a pull request (#14) that fixes this.

I have got this working on my Homestead installation (albeit with a modification to the package code). Make sure your host in your config file is set to <IP_ADDRESS>.
Due to an issue in the service provider, the host is not correctly applied to the request. I've submitted a pull request (#14) that fixes this.

Thank you @bullenb!
I was trying to configure it to no avail, your PR seems to have fixed my issues.
Closing due to future PR fixing issue.

Thank you @bullenb!
I was trying to configure it to no avail, your PR seems to have fixed my issues.
Closing due to future PR fixing issue.


New version: CQLdriver v0.11.2

Registering package: CQLdriver
Repository: https://github.com/r3tex/CQLdriver.jl
Created by: @lukemerrick
Version: v0.11.2
Commit: f466a3a8ab16d08a7e09dcf042aa7973e6a6dde2
Git reference: HEAD
Description: A Julia package for interfacing with CQL compliant databases.

This needs to be manually merged because versions 0.11.0 and 0.11.1 were released on GitHub but never registered here (and they wouldn't pass auto-merging).


things as simple objects

The aim is to simplify the API used by client developers still further by using getters and setters for synchronous updates to object properties, and by treating actions as object methods that return promises. The client platform should validate data and thrown an exception if the app tries to pass a value that is invalid in respect to the thing description. Asynchronous errors are reported via events, e.g. loss of connection or an error reported by the server, but note that actions are asynchronous and the app should deal with errors through the promise returned when invoking an action. We need to agree on a means to separate the system events from the events declared in thing descriptions. One idea is by event name, but another idea would be to an API for subscribing to system events, e.g. to set onerror handlers. The error pattern is common place for node and for the browser DOM.

One complication is how to get the model given a thing. One idea is to reserve part of the name space for object properties, e.g. all properties whose name starts with "@", this thing["@model"] would provide the model for the thing. My plan is to layer all this on top of the platform abstraction API, e.g. a setter for a thing's property would first validate value against the thing description, then call the thing's platform's write method which returns a promise. If the promise is rejected, this would be used to notify a system event.
How many events need to be defined?

errors for property read and write - in most cases, client-side data validation should avoid these errors
unexpected loss of connectivity and restoration of connectivity
invalid bearer token, e.g. where a previously valid token has expired or been revoked
updates to metadata and to the declarations for properties, actions and events


Custom fields in to user_profile table

Hi!
How i can add custom fields to user_profile table (for example, type, role, age etc.)?
Which approach is more correct?
Additional migration?

Please use Gitter to ask questions. Github issues are for reporting issues (!).


team drive

hi,
nice repo
one problem
how to add my gmail so it shows my team drives in bot?

Hello
You need to add exactly the same sa in the bot and as member of the destination shared drive else it won't work.
You the chat : t.me/msgsuitechat to get help.

I am also facing he same issue


Fixed typos and spacing on PDF creation

To test:

Start app and fill out form. Generate a PDF.
On generated PDF, confirm that spelling errors and spacing issues have been corrected.

Also note that I removed the instruction page containing placeholder text from the beginning of the document and the blank page at the end of the document. These can be re-added if they are necessary for the client's needs.

@MrErin This is great! Thanks!


Updated JSON files

The new GenerateDoc.py script was run on all the JSON files with
XML documentation from ITK v4.11.  This changed 182 of the 281
JSON files in SimpleITK.

Topic was updated and has been merged into master:
https://github.com/SimpleITK/SimpleITK/commit/b67e04234e0088623f72edee1be3d6785bad03b7


align 64bit counters in 32bit system

close #2698

Codecov Report

Merging #2703 (4c46ef3) into main (cdccfe8) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2703      +/-   ##
==========================================
+ Coverage   59.58%   59.59%   +0.01%
==========================================
  Files         138      138
  Lines       23626    23627       +1
==========================================
+ Hits        14077    14080       +3
+ Misses       7716     7715       -1
+ Partials     1833     1832       -1

Impacted Files
Coverage Δ

pkg/meta/base.go
67.01% <100.00%> (+0.04%)
:arrow_up:

pkg/meta/tkv_mem.go
86.61% <0.00%> (-0.71%)
:arrow_down:

pkg/meta/sql.go
63.95% <0.00%> (ø)

pkg/chunk/disk_cache.go
78.20% <0.00%> (ø)

pkg/chunk/utils_unix.go
91.66% <0.00%> (+25.00%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How to see who the Admins are? (and make a change)

hello team -

i'm wondering if there is a way to see who the admins are on the back end
i would also like to change my admin email from gmail to my city email

thank you in advance @jszwedko @jafowler49 !

Hi @jeanwalshie
You can see the current admins here: https://adoptadrain.sfwater.org/admin/user?model_name=user&utf8=✓&f[admin][41771][v]=true&query=
If you navigate to a user, you can check the "Admin" box for that user:

Hope this helps!

(I also updated your user's email to the @sfwater.org address -- you'll need to use this one when logging in now)

Scratch that, I see there is already a user with that address. Instead, made the other user an admin.

got it, so do a filter for admin = true.
great, i'll close this. thanks @jszwedko!


output download messages / progress

helping the user to recognize/handle issues, see discussion in #24

ping @jeanp413 for review

Any comment on this @jeanp413?

How does the output log looks after this change? don't think it would be nice if it's polluted with progress lines output

In my test this led to 2 additional lines after all the script that is dumped before execution.
One line showed the download information, the other a progress bar. Is that different on your side?

I did some test and I think we can use --no-verbose for wget and --show-error --silent for curl, sounds good? otherwise I see it prints lots of this lines
 30700K .......... .......... .......... .......... .......... 64%  548M 0s
 30750K .......... .......... .......... .......... .......... 64%  490M 0s
 30800K .......... .......... .......... .......... .......... 64%  368M 0s
 30850K .......... .......... .......... .......... .......... 64%  378M 0s
 30900K .......... .......... .......... .......... .......... 64%  378M 0s
 30950K .......... .......... .......... .......... .......... 65%  526M 0s
 31000K .......... .......... .......... .......... .......... 65%  606M 0s
 31050K .......... .......... .......... .......... .......... 65%  614M 0s
 31100K .......... .......... .......... .......... .......... 65%  516M 0s
 31150K .......... .......... .......... .......... .......... 65%  522M 0s

That's already better than what we currently have (quite), please take that for now, leaving this issue open - I want to check when the printing is updated (likely a TERM setting) and if we can use that - multiple lines are definitely bad.


Revert veldrid update

Reverts https://github.com/ppy/veldrid/pull/32
Reverts https://github.com/ppy/veldrid/pull/31

This reverts commit 02626fd633a21e68cdae78c528b58a06b281ceae.

OP is confusing, I'm pretty sure it should say that it's reverting https://github.com/ppy/veldrid/pull/30 and https://github.com/ppy/veldrid/pull/31? (it currently says it's reverting https://github.com/ppy/veldrid/pull/32, which is a revert, so :exploding_head:)
Other than that, looks good in theory. Someone with a Mac should probably confirm in practice, though.

Yeah, misread the PR title. Fixed now.


Next

Related Issues

closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (if There Are Any)

Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

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

Upgrade Notes and Changelog

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

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

[ ] I read and followed contribution rules

Pull Request Test Coverage Report for Build 410271053

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+12.5%) to 99.31%

Totals

Change from base Build 406035937:
12.5%

Covered Lines:
119

Relevant Lines:
120

💛  - Coveralls


add PostgreSQL driver

add PostgreSQL driver as a dependency, so it will be bundled into Docker image...
as proposed in #254

@nitram509 thank you for your contribution 🎉 I'll review your PR soon 👀

@saig0 can you please release 2.1.1 (not just a snapshot)? 2.1.0 doesn't work with PSQL driver.

@danshapir yes :sweat_smile: I'll build a release in the next few days :building_construction:

@danshapir a new version 2.2.0 is released :tada:

Hi, can you please add Mysql Support, driver not found since 2.1.0 version
Thanks

Hi, can you please add Mysql Support, driver not found since 2.1.0 version

There is no MySQL support until now. Please create a new issue for it.
Feel free to contribute by submitting a PR similar to this one :rocket:


Filters are missing

Hello, I'm trying to use the ImGuiTextFilter class from your C bindings (which are great otherwise!) and couldn't find anything related to the use of text filters, especially the Draw and PassFilter methods.

yea the filters are not yet wrapped for c yet. but it is easy to copy the code inside those methods and use it with cimgui. Filters are just for convenience. Feel free to extend cimgui with Filters via a PR

I'll probably have a very big PR for you in a few days, I basically already upgraded cimgui to the latest 1.46WIP and added almost every missing calls, I just need to wrap the internal API as well and I'll send it your way.

I just updated to imgui 1.45 and tagged that (https://github.com/Extrawurst/cimgui/releases/tag/v1.45) so we are good to go to a WIP version now. please rebase your changes to go from there.

@ddude any news here ?


Provide access to metadata

The current introspection api does not provide access to metadata annotations on declarations today. You can configure macros themselves by passing info to the constructor, but you can't see any other metadata or macros.
This likely would mean we want to expose some sort of equivalent to the DartObject api for these, which is a larger undertaking.

cc @davidmorgan

Note, that until the declaration phase ends we cannot resolve metadata, because at any point a new declaration could be added, and so change the resolution.
import 'package:my/macro.dart' show myAnnotation, myMacro;

@myMacro
class A {
  @myAnnotation
  int foo;
}

If myMacro adds a new static const field to A, then @myAnnotation will be resolved to it.
import 'package:my/macro.dart' show myAnnotation, myMacro;

@myMacro
class A {
  static const myAnnotation = 0;
  @myAnnotation
  int foo;
}

Also it metadata class or any args come from the current library cycle then we can't construct it at all 🤔

So one idea here is we could place some restrictions on metadata annotations:

Macros aren't allowed to introduce declarations that would shadow identifiers used in metadata

Possibly, this would be a good generalized restriction to reduce confusion?

Classes used as metadata must be defined in a separate module (similar to macros)
Classes used as arguments to metadata must also be defined in a separate module

With those restrictions, I think we should be able to provide access to metadata from any phase.

We probably cannot disallow using local declaration for all metadata.
But it would be reasonable for annotations that are macro references.
Probably mostly such configuration will be primitives - String and int, or some objects declared in macro libraries.
Running all phases seems reasonable, in the analyzer we usually process library cycles fully one by one.

It is likely a reasonable restriction that macros can only access metadata for types reachable by the macro definition itself. Possibly with an api like Iterable<Annotation> annotationsOfType<T>() on the Declaration class. We would have to not allow passing type variables to that api I think, which gets a bit funky, but is probably doable.


Improve Repository Structure and Organization

I propose restructuring the WordWise repository to improve code organization, maintainability, and developer onboarding. Below are the key enhancements:

Restructure Folder Hierarchy:

Create dedicated folders for src (source code), tests (unit tests), docs (documentation), and data (example datasets).

Improve Documentation:

Include architecture.md in the docs/ folder for better understanding of the project.
Code Organization:

These changes will make the repository more professional, readable, and contributor-friendly. Let me know your thoughts!

Hi @ANSHIKA-26,
I request you to please add the level 1 label to this issue.

@ANSHIKA-26


TransitioningContentControl does not transition on content change

Hello, I'd like to propose an important improvement for TransitioningContentControl:
Actual:
TransitioningContentControl does not transition with cool animation when Content dependency property changes.
Expected:
TransitioningContentControl should also transition with cool animation when content changes (specifically when change is invoked by DataBinding mechanism)
Remarks:
Right now the cool animation of transition is started only when visibility of the TransitioningContentControl changes. I think it should also play transitrion animation when content is changed. This is very desirable behavior for extension of ContentControl.
Please see https://mahapps.com/docs/controls/transitioningcontentcontrol for example.
Also the fix seems very simple, just invoke StartTransition() in TransitioningContentControl.cs when content changes.
Thanks

This would be very useful. In fact, when I started using this control for the first time I thought It wasn't working because this was the behavior I was expecting.

Thanks @NaBian for the work! Amazing!


Discord Redirect

The previous site had a redirect from https://thecodingtrain.com/discord to a permanent discord invite. What's the best way to add this back into this site? @fdoflorenzano feel free to let us know if there is a specific way you prefer we implement this!
I'm also trying to remember what other redirects we might have had? I guess we'll discover them as they come up!

I'm not sure which is the best way of doing this in Gatsby. It looks like it can be added in the build process, but I would have to test it out with Netlify.

There's also an option to use configure Netlify's redirects in netlify.toml or _redirects to handle redirecting pages. Although, the Gatsby approach would be hosting agnostic and would work locally unlike the Netlify approach.
Documentation for the Netlify redirects approach:

https://prince.dev/netlify-redirects
https://docs.netlify.com/routing/redirects/

I've used the Netlify approach for my site React Robins for the "Discord" and "Submit a Talk" links: https://github.com/React-Robins/website/blob/13f53379e0a17e990f6619af03529d24ec9bf362/static/_redirects.


Check routes

Would it be possible to check route classes and methods?
See https://github.com/slevomat/coding-standard/issues/412

@szepeviktor Sure! Thanks for the proposal. Great idea!

Maybe my code cloud be used
https://github.com/szepeviktor/debian-server-tools/blob/master/webserver/laravel/Commands/RouteCheckCommand.php#L55-L105

No plans at this time to implement this myself. Fell free to pull request this feature.


Some generic error messages

In messages.ts, I'd suggest to improve the generic Unexpected token:
MissingFromClause: 'Unexpected token',
NoAsAfterImportNamespace: 'Unexpected token',
InvalidModuleSpecifier: 'Unexpected token',
IllegalImportDeclaration: 'Unexpected token',
llegalExportDeclaration: 'Unexpected token',

I had created a PR but had not created the issue first.

c.f. https://github.com/jquery/esprima/issues/1547 for implementation details

The messages were left generic because back then V8/Node.js did not have ES6 support. Let's check what V8/Node.js shows when encountering such an error and adopt the same error message.

A good reference: https://chromium.googlesource.com/v8/v8/+/master/src/messages.h.

Let's just fold this one into #1214.


Triple transmission supports message compression

What is the purpose of the change
Support payload compression in the triple protocol
Brief changelog
Triple transmission supports message compression
Verifying this change
Yes

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

plz fix ut

the server always put all encodings in header https://github.com/grpc/grpc-java/blob/3b237339c7b0b5e60b6331cac9e23650e97b1e8c/core/src/main/java/io/grpc/internal/ServerCallImpl.java#sendHeadersInternal

plz fix ut
you might builld it again because some wrong codes were merged into 3.0 but they are fixed by now.

the server always put all encodings in header

yes, we did like that

the server always put all encodings in header https://github.com/grpc/grpc-java/blob/3b237339c7b0b5e60b6331cac9e23650e97b1e8c/core/src/main/java/io/grpc/internal/ServerCallImpl.java#sendHeadersInternal

yes，it is what we did > org.apache.dubbo.rpc.protocol.tri.AbstractServerStream#createRequestMeta

Codecov Report

Merging #8817 (4e6f58c) into 3.0 (1702fa0) will decrease coverage by 0.13%.
The diff coverage is 70.52%.

@@             Coverage Diff              @@
##                3.0    #8817      +/-   ##
============================================
- Coverage     63.74%   63.61%   -0.14%
  Complexity      313      313
============================================
  Files          1169     1171       +2
  Lines         49210    49255      +45
  Branches       7360     7338      -22
============================================
- Hits          31370    31333      -37
- Misses        14412    14478      +66
- Partials       3428     3444      +16

Impacted Files
Coverage Δ

...apache/dubbo/rpc/protocol/tri/GrpcDataDecoder.java
48.57% <33.33%> (+0.18%)
:arrow_up:

...pc/protocol/tri/TripleHttp2FrameServerHandler.java
42.63% <54.54%> (+1.11%)
:arrow_up:

.../apache/dubbo/rpc/protocol/tri/GzipCompressor.java
60.86% <60.86%> (ø)

.../org/apache/dubbo/rpc/protocol/tri/TripleUtil.java
42.85% <62.50%> (+0.98%)
:arrow_up:

...protocol/tri/TripleHttp2ClientResponseHandler.java
46.00% <63.63%> (+4.97%)
:arrow_up:

.../apache/dubbo/rpc/protocol/tri/AbstractStream.java
47.50% <83.33%> (+1.39%)
:arrow_up:

...e/dubbo/rpc/protocol/tri/AbstractClientStream.java
66.66% <100.00%> (+1.73%)
:arrow_up:

...e/dubbo/rpc/protocol/tri/AbstractServerStream.java
56.31% <100.00%> (+2.22%)
:arrow_up:

...ubbo/rpc/protocol/tri/ClientTransportObserver.java
80.00% <100.00%> (ø)

...che/dubbo/rpc/protocol/tri/IdentityCompressor.java
100.00% <100.00%> (ø)

... and 54 more

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 1702fa0...4e6f58c. Read the comment docs.

For streams, we should also support full stream compression.

For streams, we should also support full stream compression.

it will support in the another pr

How to activate compression


improve filter system of schedule page

Short description of what this resolves:
Fix bugs in the filter system of schedule page. Also, add track and room filter for calendar mode.
Changes proposed in this pull request:

Add track and room filter for calendar mode in schedule page.

Display "no results" message after applying track or room filter, if there are no matching results.
Before change ( Message is not shown, even there are no matching results )

After change

While applying search filter in calendar mode, it will filter data for all dates (As in track mode).
Before change ( It is filtering only current date sessions, No change in other dates )

After change

Fix "no results" message activity.

While applying clear filter.
Before change ("no results" message is shown even after removing filter)

After change

While switching between dates.
Before change ( "no results" is shown because current date has no matching results, but it remains for other dates too )

After change

Fixes #1822.
Deployment link: https://adityahirapara.github.io/eventSiteWebApp/schedule.html

@AdityaHirapara Okay, is the deployment link updated, because it is not working in the deployment.

It is working for me, @geekyd

@AdityaHirapara Great work when you are showing no result found message the star for bookmark is coming down which is not looking good , you can display the no result found message in the box in which clear filter is written and display it in red.

@AdityaHirapara Thank you! :)

A bit late perhaps, but I suggest the "No matching results found" results could appear in the results area, instead of resizing the input box.


Updated to SkiaSharp 3.0.0-nightly.13

What does the pull request do?
Update to SkiaSharp 3.0
WriteableBitmapImpl isn't drawing images, so we can't pass SKSamplingOptions - need to figure out what to do about it.
What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Closing this PR temporarily due to inactivity. Please ping me if this needs to be reopened.


Decouple lock information provision from the lock itself, disable DNS…

… lookup by default, add it as an optional information provider.
The DNS lookup adds significant delays (up to 5 seconds) in some environments, and is not necessary by default in my opinion.

Merged, thanks!


output-management-v1: send complete head state on enable change

Send all head data when an output gets enabled since data can change while the head is disabled and the changed data in this case not sent.
I noticed that issue with sway and Disman on the repeated hot-plug of an external display with a position different to (0,0). The position event was only received the first time. Afterwards the position event was not received anymore. This also happened when Disman was restarted but the sway session continued.

The freebsd build failed, but I don't think it's because of this change here. Can I restart the build somehow?

I just hit the same this weekend and this fixes it.


Replaced by PR #7382

[approve ci autest]

Sigh, although the Au tests pass, this code crashes when I test it with h2load.

Closing this, as I now understand why the linked list head pointer tagging is necessary ( https://en.wikipedia.org/wiki/ABA_problem ).  This code could still use some cleanup, but unlikely to significantly improve performance.

See https://github.com/apache/trafficserver/pull/7382


Non-supported target handling

https://forum.defold.com/t/android-builds-with-native-extensions-fail-def-3026/14326/10

The actual compile error was from the fact that defos doesn’t support android yet, so you get a linker error. Perhaps @Pkeod could add a null-implementation for it? E.g. adding the C++ symbols, but not registering a defos Lua module, so the user can check for it?

Cool! I’ll make a PR tomorrow/tonight.


Add test for seeds file

As we continue to integrate in our models, we'll want to use the seeds file more and more; we should add a straightforward end to end test (either in CI or in the test suite) that throws a flag if anything's busted, just to be on the safe side.
Maybe a rake task similar to the one @Kevin-Wei  wrote for factory girl?

I think we're unlikely to ever actually do this. I'm closing.


Update home & build

Update repo for:

the move from prisae to the emsig-org;
the build from distutils to meson (thanks @jokva).

This doesn't not work currently on many fronts.

I pushed a patch which fixes a part of that issue by simply removing the fftlog/ dir, just doing src/ directly.

With these patches I see the same test failure in the CI job as I do locally. I figure you're more familiar with the API and can work on that for a bit.

Thanks, much appreciated! That is also the one I had locally. If I remember right, wsave is a "working array" in Fortran that stores all sort of things, which was not needed in the Python version, respectively constructed internally and the user did not have to bother about it. I'll have to dig in to try and remember, will do that over the holidays.

The current error is
E       TypeError: _fftlog.fhti() missing required argument 'wsave' (pos 7)

Something must have changed in f2py, but I cannot figure out what right now. Nothing changed in the signature file (although I tried adding hide to the intent(out), but with the same error).


FileNotFoundError: [Errno 2] No such file or directory: 'sam_vit_h_4b8939.pth'   run error

I am trying to do a Fill any thing and get an execution error like this Please help me with a solution.
Traceback (most recent call last):
File "fill_anything.py", line 79, in
masks, _, _ = predict_masks_with_sam(
File "/home/haga/Inpaint-Anything/sam_segment.py", line 23, in predict_masks_with_sam
sam = sam_model_registrymodel_type
File "/home/haga/Inpaint-Anything/segment_anything/segment_anything/build_sam.py", line 15, in build_sam_vit_h
return _build_sam(
File "/home/haga/Inpaint-Anything/segment_anything/segment_anything/build_sam.py", line 104, in _build_sam
with open(checkpoint, "rb") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'sam_vit_h_4b8939.pth'

Hi，it seems that model checkpoint of sam does not exist.
You can first download the model checkpoints provided in segment_anything (e.g. sam_vit_h_4b8939.pth. And then change the args --sam_ckpt to the checkpoint path.


test: add integration test

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

Added Integration test.

Integration test is failing due to api is not enabled.

@googlebot I consent

Closing for obsolete.


Handle SIGTERM on the API

Which Issue(s) this Pull Request Resolves

Related to #521 and #556
Release Note

The KubeArchive API now gracefully shuts down if the process receives a TERM or INTERRUPT signal (SIGTERM or SIGINT respectively).

Notes for Reviewers

Handling here the API, as the sink is not migrated to Gin yet (#556)
SIGINT is not emitted by Kubernetes, but its the interrupt signal so I think is just normal that we handle it as well.
To test delete the API pod. In the logs you should see the different messages.

I've tested this and I saw in the api deployment logs the "Shutting down server" message :) @rh-hemartin I have an small suggestion about the comments that you added, should those follow the style guide as well? for example this phrase: We do not accept bodies yet, because we are read-only, so we set a

I don't think we need to follow the style guide. They are documentation, but the documentation style guide is intended for user facing documentation at least.


Some small improvements

This PR adds:

Simple README file
Add highlighting of the non GSM7 characters: this is really useful to quickly identify which characters cause the message to be change encoding
Add legend at the bottom of the page (mainly to explain the non GSM-7 highlighting)

@smendes while working on the npm package, I thought about some small improvements to the tool. The non GSM7 highlight is a feature that can be really useful for users to understand how to keep the message to the least amount of segments

@smendes while working on the npm package, I thought about some small improvements to the tool. The non GSM7 highlight is a feature that can be really useful for users to understand how to keep the message to the least amount of segments

That's how those changes look like:

That's how those changes look like:

@smendes I added the GitHub corner to the page so people can access this repo. Let me know what you think


How to uninstall Black Screen?

You should be able to do brew uninstall black-screen

Didn't work for me. If you installed black-screen using cask, then you should uninstall it using cask, otherwise you'll probably be shown a No such keg: .../black-screen. So you must uninstall it this way:
brew cask uninstall black-screen


Roll Flutter from e3471f08d1d3 to 957494d9f029 (41 revisions)

Roll Flutter from e3471f08d1d3 to 957494d9f029 (41 revisions)
https://github.com/flutter/flutter/compare/e3471f08d1d3...957494d9f029
2023-02-13<EMAIL_ADDRESS>Marks Linux_android flavors_test to be unflaky (flutter/flutter#120299)
2023-02-13<EMAIL_ADDRESS>fb8840578 Roll Dart SDK from 1caf3a9ad101 to f80c5db8736a (1 revision) (flutter/engine#39588) (flutter/flutter#120606)
2023-02-13<EMAIL_ADDRESS>60c8532d6 Roll Fuchsia Mac SDK from NZAnfCkpbswhYplty... to 6hbPQq6ED0PkuQiKM... (flutter/engine#39587) (flutter/flutter#120602)
2023-02-13<EMAIL_ADDRESS>Roll Plugins from 02571ec0dd36 to f3bc6f1eb0c2 (2 revisions) (flutter/flutter#120601)
2023-02-13<EMAIL_ADDRESS>ede2a0a3c Roll Skia from c6f1de2239fb to d85501fa487d (1 revision) (flutter/engine#39585) (flutter/flutter#120593)
2023-02-13<EMAIL_ADDRESS>1695b7bbc Bump github/codeql-action from 2.1.39 to 2.2.4 (flutter/engine#39584) (flutter/flutter#120588)
2023-02-13<EMAIL_ADDRESS>fix a Slider theme update bug (flutter/flutter#120432)
2023-02-13<EMAIL_ADDRESS>4107a7b71 Roll Skia from 615965d545f4 to c6f1de2239fb (1 revision) (flutter/engine#39581) (flutter/flutter#120580)
2023-02-13<EMAIL_ADDRESS>1eef041d4 [Impeller] Source the pipeline color attachment pixel format from RenderPass textures (flutter/engine#39556) (flutter/flutter#120576)
2023-02-13<EMAIL_ADDRESS>Roll Flutter Engine from b7e80ad6ef51 to 1ff345ce5f63 (2 revisions) (flutter/flutter#120574)
2023-02-12<EMAIL_ADDRESS>b7e80ad6e Roll Fuchsia Mac SDK from y35kWL0rP5Nd06lTg... to KpTOXssqVhPv2OBZi... (flutter/engine#39574) (flutter/flutter#120559)
2023-02-12<EMAIL_ADDRESS>0aa4fcbd2 Roll Skia from ec87ec6fd34f to 615965d545f4 (1 revision) (flutter/engine#39573) (flutter/flutter#120558)
2023-02-12<EMAIL_ADDRESS>9a19d7eea Roll Fuchsia Linux SDK from arbaBzyUE2ok1bGl5... to 8fdyKaKQqTPpjcp-L... (flutter/engine#39572) (flutter/flutter#120554)
2023-02-12<EMAIL_ADDRESS>fe56a45b4 Roll Dart SDK from c4255cea566a to 1caf3a9ad101 (1 revision) (flutter/engine#39571) (flutter/flutter#120552)
2023-02-12<EMAIL_ADDRESS>Roll Flutter Engine from 2cba062f9f4c to 05d81c0f2ebe (2 revisions) (flutter/flutter#120547)
2023-02-12<EMAIL_ADDRESS>Roll Flutter Engine from d8e01097e66b to 2cba062f9f4c (2 revisions) (flutter/flutter#120538)
2023-02-11<EMAIL_ADDRESS>Revert "Fix BottomAppBar & BottomSheet M3 shadow (#119819)" (flutter/flutter#120492)
2023-02-11<EMAIL_ADDRESS>d8e01097e Roll Fuchsia Mac SDK from 6nMZjuYXTcnD_VZQI... to FxFPRn_9rSWWAWFw0... (flutter/engine#39562) (flutter/flutter#120519)
2023-02-11<EMAIL_ADDRESS>761891200 Roll Dart SDK from 1d26a1d57edf to b1836aacc08a (1 revision) (flutter/engine#39561) (flutter/flutter#120513)
2023-02-11<EMAIL_ADDRESS>5efb42971 Roll Fuchsia Linux SDK from 482Njb1v72P7fNyj4... to MVMTNxWJaWdwPWstz... (flutter/engine#39559) (flutter/flutter#120512)
2023-02-11<EMAIL_ADDRESS>Roll Flutter Engine from c3dc68e0e263 to 363355af5158 (2 revisions) (flutter/flutter#120511)
2023-02-11<EMAIL_ADDRESS>c3dc68e0e Roll Skia from 70a3a194ec98 to 6c3097e6f833 (1 revision) (flutter/engine#39555) (flutter/flutter#120508)
2023-02-11<EMAIL_ADDRESS>8baee2164 Roll Skia from 5230650dc096 to 70a3a194ec98 (2 revisions) (flutter/engine#39554) (flutter/flutter#120507)
2023-02-11<EMAIL_ADDRESS>Roll Flutter Engine from f737dc868a3e to 3ac3338489d2 (2 revisions) (flutter/flutter#120505)
2023-02-11<EMAIL_ADDRESS>f737dc868 [macOS] Add XCode marks for TextInputPlugin (flutter/engine#39550) (flutter/flutter#120501)
2023-02-11<EMAIL_ADDRESS>Roll Flutter Engine from 6660300ea34f to 5e3ff1e5c9b3 (4 revisions) (flutter/flutter#120495)
2023-02-10<EMAIL_ADDRESS>roll packages (flutter/flutter#120493)
2023-02-10<EMAIL_ADDRESS>Roll Flutter Engine from 4104eb5cbc40 to 6660300ea34f (6 revisions) (flutter/flutter#120487)
2023-02-10<EMAIL_ADDRESS>Revert "Revert "[web] Move JS content to its own .js files (#117691)" (#120275)" (flutter/flutter#120363)
2023-02-10<EMAIL_ADDRESS>[conductor] Remove CiYaml model (flutter/flutter#120458)
2023-02-10<EMAIL_ADDRESS>Roll Flutter Engine from add9e11edb66 to 4104eb5cbc40 (14 revisions) (flutter/flutter#120470)
2023-02-10<EMAIL_ADDRESS>Remove deprecated SystemChrome.setEnabledSystemUIOverlays (flutter/flutter#119576)
2023-02-10<EMAIL_ADDRESS>[conductor] Tag engine versions (flutter/flutter#120419)
2023-02-10<EMAIL_ADDRESS>Delete Chrome temp cache after closing (flutter/flutter#119062)
2023-02-10<EMAIL_ADDRESS>Fix classes that shouldn't be extended/instantiated/mixedin (flutter/flutter#120409)
2023-02-10<EMAIL_ADDRESS>Roll Plugins from 73986f4cc857 to 02571ec0dd36 (3 revisions) (flutter/flutter#120443)
2023-02-10<EMAIL_ADDRESS>add9e11ed Fix position of BackdropFilter above PlatformView (flutter/engine#39244) (flutter/flutter#120415)
2023-02-10<EMAIL_ADDRESS>Fix lerping for NavigationRailThemeData icon themes (flutter/flutter#120066)
2023-02-10<EMAIL_ADDRESS>Use String.codeUnitAt instead of String.codeUnits[] in ParagraphBoundary (flutter/flutter#120234)
2023-02-10<EMAIL_ADDRESS>post submit only (flutter/flutter#120411)
2023-02-10<EMAIL_ADDRESS>Roll Flutter Engine from 9a40a384997d to e1d0032029e4 (6 revisions) (flutter/flutter#120414)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins
Please CC camillesimon@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
...

Commit queue failed; closing this roll.


ol.interaction.Select layers param

Hello,
When adding a selection like this:
this.selectHover_ = new ol.interaction.Select({
    layers: [this.openLayersOverlay_],
    condition: ol.events.condition.pointerMove,
});

the selectHover_ hightlights all the features from all the layers.
For using only the this.openLayersOverlay_ features I have to do this:
this.selectHover_ = new ol.interaction.Select({
    layers: [this.openLayersOverlay_],
    condition: ol.events.condition.pointerMove,
    filter: function(feature, layer){
        if(layer === this_.openLayersOverlay_)
            return true;
        else
            return false;
    }
});

Is it normal ? the "layers" param is working ?

Duplicate of #4631.


Using popover component in Tooltip

Tooltip component should use our Popover for its content.

Completed with #483


Feature Request: MAC ADDRESS

Hi, please, i know that might not be easy, but could you try to add MAC address specification / protocol for stb emu codes player (stalker player) ?

This would be awesome as there isn't any app that does it on PC.

You have SFvip-player for pc

I have found https://github.com/tweakunwanted/OpenXC-Main/blob/master/wwwdir/portal.php
It's harder for me to understand than xtream api.
let say portal is
http://example.com/c and mac is 00:1A:79:1E:7F:50
mac needs to be url encoded
type can be stb, itv, vod, etc. and depending on the type different actions are allowed so for example in the browser this works
http://example.com/c/portal.php?type=stb&action=get_profile&mac=00%3A1A%3A79%3A1E%3A7F%3A50
http://example.com/c/portal.php?type=itv&action=get_all_channels&mac=00%3A1A%3A79%3A1E%3A7F%3A50
etc.
http://example.com/c/portal.php?type=itv&action=create_link&mac=00%3A1A%3A79%3A1E%3A7F%3A50
gives me
{"js":{"id":"","cmd":"ffmpeg http://example.com/play/live.php?mac=00:1A:79:1E:7F:50&stream=&extension=ts&play_token=zZ2vx3RiOH"},"streamer_id":0,"link_id":0,"load":0,"error":""}
I tried
http://example.com/play/live.php?mac=00%3A1A%3A79%3A1E%3A7F%3A50&stream=2838&extension=ts&play_token=zZ2vx3RiOH
but it didn't work I'm doing something wrong but I don't why
with xtream it was very easy you get the streamid from http://example.com/player_api.php?username=user&password=pass&action=get_live_streams and then you can build the stream url
http://example.com/live/user/pass/streamid.ts which will work directly in VLC

        if(validateDate($valid)==true){

            $url = $portal.$loader."?type=itv&action=create_link&cmd=".$cmd."&series=&forced_storage=0&disable_ad=0&download=0&force_ch_link_check=0&JsHttpRequest=1-xml&mac=".$mac;

            $url = str_replace(' ', '%20', $url);

            $curl = curl_init($url);
            curl_setopt($curl, CURLOPT_URL, $url);
            curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
            curl_setopt($curl, CURLOPT_USERAGENT, $agent);
            curl_setopt($curl, CURLOPT_HTTPHEADER, array(
                'Content-Type: application/json;charset=UTF-8',
                $authorization,
                $cookie
            ));

            $resp = curl_exec($curl);

            $jsonData = json_decode($resp, true);

            //$jsonData = strstr($jsonData, '{');
            //$jsonData = strstr($jsonData, '}', true);

            curl_close($curl);

            /*
            print "
";
            print_r($jsonData);
            print "
";
            */

            if(!empty($jsonData)) {

                //test4: experimental EPG WORKING
                /*
                $url2 = $portal."portal.php?type=itv&action=get_short_epg&ch_id=".$id."&size=10&JsHttpRequest=1-xml";
                $curlX = curl_init($url2);
                curl_setopt($curlX, CURLOPT_URL, $url2);
                curl_setopt($curlX, CURLOPT_RETURNTRANSFER, true);
                curl_setopt($curlX, CURLOPT_USERAGENT, $agent);
                curl_setopt($curlX, CURLOPT_HTTPHEADER, array(
                    'Content-Type: application/json;charset=UTF-8',
                    $authorization,
                    $cookie
                ));

                $resp2 = curl_exec($curlX);
                $jsonData2 = json_decode($resp2, true);
                curl_close($curlX);
                */
                /*
                print "
";
                print_r($jsonData2);
                print "
";
                */
                //test4: experimental EPG END

                $ff = str_replace($jsonData['js']['id'],$id,$jsonData['js']['cmd']);

                //$ff = str_replace('ffmpeg ','',$jsonData['js']['cmd']);

                $ff = str_replace('ffmpeg ','',$ff);

                $pieces = explode("&", $ff);

                //print_r($pieces[1]);

                if(array_search("stream=",$pieces)!=NULL) {
                    if ((stripos($ff, "stream=") !==false)) {
                        //stream=
                        $ff = str_replace('stream=','stream='.$id,$ff);
                    }
                }
                /*
                header("Content-Type: video/vnd.mpegurl");
                header("Content-Disposition: attachment;filename=hvp-playlist.m3u");
                header("Pragma: no-cache");
                header("Expires: 0");
                */

                header("Content-Type: video/vnd.mpegurl");
                header("Pragma: public"); // required
                //header("Content-Type: audio/x-mpegurl");
                header("Content-Disposition: attachment; filename=itv-".time().".m3u");
                //WITH EPC: echo "#EXTM3U url-tvg=\"".$url2."\" \r\n#EXTINF:0,".$name."\r\n#EXTVLCOPT:network-caching=9000\r\n".$ff."\r\n";
                echo "#EXTM3U\r\n#EXTINF:0,".$name."\r\n#EXTVLCOPT:network-caching=9000\r\n#EXTVLCOPT:http-user-agent=".$agent."\r\n".$ff;

            } else {
                echo "error-5";
                echo "

<<  Go Back

";
            }

        }

Hi,
Using it for more than one year now.
I can decode all portals and generate the "VLC" link
I watch channels of the world, movies, series, netflix, amazon, diney+, apple TV and others.
I made all the web app a year ago.
If you want i can give you access for a limited time so you can test it.
Have a nice day.

Hey guys, it took me a while to implement stb/stalker portal support but now it's available in version 0.15. I would close that one, if something is missing there please open a new issue.


Refund API is not working

I created using Refund API but it is not working.
Am I some wrong?
refund_c = ShopifyAPI::Refund.calculate(
                    {
                        :shipping => {
                            :full_refund => true
                        },
                        :refund_line_items => [
                            {
                                :line_item_id => line_item_id,
                                :quantity => 1,
                                :restock_type => "no_restock"
                            }
                        ],
                    },
                    :params => {
                        :order_id => order_id
                    }
                )

                refund = ShopifyAPI::Refund.new(
                    :order_id => order_id,
                    :user_id => old_order.customer.id,
                    :notify => true,
                    :restock => false,
                    :note => reason,
                    :shipping => { :full_refund => true },
                    :refund_line_items => [
                        {
                            :line_item_id => params[:line_item_id],
                            :quantity => 1
                        }
                    ],
                    :transactions => refund_c.transactions
                )
                refund.save

@nwtn Could you please help me?

Hi @Yu-coding. Can you provide some more information?

What are you trying to do?
What response are you expecting?
What response (including errors or response codes) are you getting?

@nwtn Thanks for reaching me.
I am getting this issue.
Failed. Response code = 422. Response message = Unprocessable Entity.
def calculateRefund(order_id, line_items)
        refund = ShopifyAPI::Refund.calculate(
            {
                :shipping => { :full_refund => true },
                :refund_line_items => line_items
            },
            :params => {
                :order_id => order_id
            }
        )
        refund
    end

Without looking at our logs for the actual request, it looks like you are not passing an array of line_items to be refunded as the value of refund_line_items. If that's not the case, can you provide the X-Request-Id response header value of your request so I can look in the logs?

I have fixed this issue using Transaction with kind = refund.
Thank you guys.


Shrinkwrap all the deps to lock them down to known working versions

Updates can be handled with greenkeeper. Shrinkwrap will ensure that the exact working deps can be preserved in the history of the project. This makes it much easier to do git bisect to find regressions, and we can always have a cloneable and reproducable repo.
Sometimes when a fuzzy version specification in packages.json matches a newer version of a dep, it can break things in unexpected ways. With shrinkwrapping, we can easily opt-in and manage those upgrades with the PRs from Greenkeeper instead.

Build broken due to https://github.com/zeit/hyperterm/pull/533

SGTM!

@rauchg hah, you not a shrinkwrap fan?

I guess you've got the non-dev deps pinned

Greenkeeper doesn't actually support this, I thought it did, but they're working on it https://github.com/greenkeeperio/greenkeeper/issues/96

@MrRio: Should we close this and revisit when Greenkeeper release support for shrinkwrapping?

@ekmartin Yes! 😊


Prop editor input improvements

there are actually three things in this pr. (I can separate them if desired)
Shortcuts for spin_slider
the spin slider had an exp(), speed dependant, behaviour (which was hard to control)
now it is easy to control it's behaviour by shortcuts (ctrl = int steps, shift = factor 0.1)

Also the step per int is now always consistent (6 pixels per int) and slow enough to actually make small steps.
also pressing control during spinning rounds the value to the next int immediately.
There is an issue on OS X, that control click is changed to right click... This prohibits you from holding control and than start to drag (with int steps), instead you first have to drag, and than (when the mouse button is hold down) press ctrl. It works fine but if someone has a better solution would be great.
Better tab control
this was hard to implement there might be an easier solution (took me a long time to figure out what signals I should use) so any help/feedback is desired.

tab now also enters the text and you go to the next input AND activated the value_input (the modal popup with the textfield) (as seen in the gif, before you had to: enter, down arrow, enter, text input, enter....)
enter closes the modal value_input
esc closes the modal value_input
click outside the input, closes the modal value_input

fixed showing grabber
The grabber was still shown when editing the number with the value_input.
which looked buggy
Deprecated (commit removed)
Removed the grey highlighting on the left of the inspector
Since the one on the items themselves is more than enough Imo. (looks better I think, it's just an aesthetic thing)
Can be seen in the gifs too.
@djrm you told me I should not add sneaky changes (which you are right!) I made it a separate commit. so we can easily remove it.

@toger5 im currently working on the Inspector visual design, and i already removed the section highlighting, so..... i don't think it is necessary.

@djrm than it would even lead to merge conflicts. ;)
so I remove that commit. Thank you!!

@djrm super curious about how you handle the sub-resource editor. Will it become easier to see?

@toger5 my current proposal is something like this (colors are not final), it makes subresource section very easy to see, and reduces the margin needed, so you can easily have up to 10 (maybe less) i would say depth levels without having a tiny sub inspector.

Tab support is very nice!

can this get merged before there are any conflicts?

@akien-mga rebased


KeyValueStore server example for async bidirectional streams

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

One or more commits are not associated with a GitHub user. The email used in the Git commit must match a verified email address in a GitHub user profile. For more information, please see https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

Regards,
CLA GitHub bot

Done

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @MansoorMohsin isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @MansoorMohsin isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot


[#1221] improvement(common): Add the method checkValue for the ConfigEntry

What changes were proposed in this pull request?
Now, ConfigEntry lacks the ability of check config options. So we add the support of this feature referring to Spark.
Why are the changes needed?
Fix: #1221
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add new ut.

Probably be better to add the checkValue to all the configurations that can be checked, not only the string configurations.

Probably be better to add the checkValue to all the configurations that can be checked, not only the string configurations.

Added.

Probably be better to add the checkValue to all the configurations that can be checked, not only the string configurations.

OK, I will try to add more checks.

Added.


Add support for Doctrine\ORM\QueryBuilder

Can you add support for Doctrine\ORM\QueryBuilder  pagination?
To paginate Doctrine\ORM\Query objects we have to build entity repositories that returns Query objects instead of the usual results.
I guess that it could be simple, since you can get a Query from a QueryBuilder.

yes, I will, thanks for bringing that up

implemented in commit

TY bro


Adjust need-storage-modify to exlcude cnf.*.tar from being overwritten

Hi @oksuzian,
You have proposed changes to files in these packages:

CampaignConfig

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for 828cd3e5197004bd94f0a8f900fc11a2aa772d4e: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 828cd3e5197004bd94f0a8f900fc11a2aa772d4e.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 828cd3e5197004bd94f0a8f900fc11a2aa772d4e at da644954093255d9a7a431c6d0058e5a6ec90800

build (prof)
:white_check_mark:
Log file. Build time: 04 min 12 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 828cd3e5197004bd94f0a8f900fc11a2aa772d4e after being merged into the base branch at da644954093255d9a7a431c6d0058e5a6ec90800.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

I tried it, and it works as expected.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ray Culbertson @.>
Sent: Monday, October 7, 2024 9:11:30 PM
To: Mu2e/Production @.>
Cc: oksuzian @.>; Mention @.>
Subject: Re: [Mu2e/Production] Adjust need-storage-modify to exlcude cnf.*.tar from being overwritten (PR #345)
@rlcee approved this pull request.
This should work, as far as I know, but just to note, I have not tried this exact syntax myself.
—
Reply to this email directly, view it on GitHubhttps://github.com/Mu2e/Production/pull/345#pullrequestreview-2353228775, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALVJESQXYS6CUA56P2MZUSLZ2M5NFAVCNFSM6AAAAABNI4LBWKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGNJTGIZDQNZXGU.
You are receiving this because you were mentioned.Message ID: @.***>

No need to rerun the CI since it has no coverage of this change.  Merging now.


blackslach not showing in page

Issue in ./help/c-experiences/c-manage-content/passing-profile-attributes-to-the-html-offer.md
In this sentence:

When using dynamic attributes in a Recommendations design, you must insert a backslash (‘’) before the dollar sign (‘$’) in order for the dynamic value to render properly

The backslash doesn't show in the ('') where it should be.

Thanks. I had to escape the backslash in our new system.
https://experienceleague.adobe.com/docs/target/using/experiences/offers/passing-profile-attributes-to-the-html-offer.html?lang=en#experiences

Thanks. I had to escape the backslash in our new system.
https://experienceleague.adobe.com/docs/target/using/experiences/offers/passing-profile-attributes-to-the-html-offer.html?lang=en#experiences


Refs #6763 Feature/xtypes dds

[x] Migrate method signatures to use xtypes::DynamicData instead of soss::Message.
[x] Implement conversion methods between xtypes::DynamicData and eprosima::fastrtps::types::DynamicData.
[x] Uncomment and fix implementation of SOSS-DDS methods.
[x] Easy FastRPTS installation and install documentation
[ ] https://github.com/osrf/soss/pull/20 merged

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Build status:

Linux

Closing this, since the reworking from SOSS to Integration Service is now near to be completed. feature/xtypes-dds branch will be transferred to main, and then the code migration from soss to eprosima::is in the namespaces, as well as using Fast-DDS 2.X.X new API will be done in a separate pull request.


fix(readme): fix broken link

Signed-off-by: Dmitry<EMAIL_ADDRESS>https://github.com/accordproject/techdocs/issues/80#issuecomment-544871864

Travis errors are not from this change, merging.


Added basic asset module structure

Coverage remained the same at 94.146% when pulling 1b62fc8dfcc2140e040597dfdff0511a93fdc045 on asset-management into d23764c889b5521131aa13874b793a1fcd6d778d on master.

Coverage remained the same at 94.146% when pulling 1b62fc8dfcc2140e040597dfdff0511a93fdc045 on asset-management into d23764c889b5521131aa13874b793a1fcd6d778d on master.

Coverage remained the same at 94.146% when pulling 91012642df17650757c04baecfa4add66b781414 on asset-management into 443df4905b106b8833604fdb7770aa57eb4a727b on master.

Coverage remained the same at 94.146% when pulling 91012642df17650757c04baecfa4add66b781414 on asset-management into 443df4905b106b8833604fdb7770aa57eb4a727b on master.

Coverage remained the same at 94.146% when pulling 91012642df17650757c04baecfa4add66b781414 on asset-management into 443df4905b106b8833604fdb7770aa57eb4a727b on master.

Coverage decreased (-3.4%) to 90.701% when pulling e8b18e3984f811b6e2afd3941794f0bc7c3fba02 on asset-management into 443df4905b106b8833604fdb7770aa57eb4a727b on master.

Coverage decreased (-3.4%) to 90.701% when pulling a59cdd1dee5819dde964daecc1d1e4f0fc5bdf04 on asset-management into 443df4905b106b8833604fdb7770aa57eb4a727b on master.


fix: invalid id for cts, mts, cjs, mjs files

Will revert the manual version bump and then merge this. Workflows should take care of publishing and making release notes


Refactoring + Text outside the frame

Refactoring and remove redundant parts between data_generators.py and test_frcnn.py :
normalize_img (Zero-center by mean pixel) and get_new_img_size(Get the resized shape, keeping the same ratio).

Change the predicted class text location if this text is outside (above or below)

Thanks for the pr! Looks good, and they seem like useful changes. I'm quite busy right now, I'll try and merge this soon, hopefully in the next few days

Great ! Will try to add more changes soon

When I run the test_frcnn.py to detect some pictures, I got no one rectangle in these pictures. It means it detect nothing. but I don't know where is wrong.Can you give me some advice to solve this problem?? Thank you !!!

Same for me, I ran 60 epochs but still test didn't even detect an object


Make +evil:copy-this-file autoload interactively

:cp was not autoloaded correctly beforehand. I just changed +evil:copy-this-file's autoload
signature it so it would match +evil:move-this-file, with which I had no issue - and it works!

Good catch. Thanks!


JMTE workshop at the EarthCube meeting

As per our conversation from the last two meetings, here are some plans and to-dos for the upcoming Jupyter Meets the Earth workshop. My memory might be wrong so please correct me if you see anything strange here!
Plans

Google doc link for tentative agenda and timeline
Workshop length is 1.5 hours
Use live, online presentation as well as 3 breakout Zoom rooms to address a large size of the audience
Update the Github pages for more self-guided resources and future references.

To-dos

[x] Finalize the main topic(s) for the entire workshop
[x] Finalize the number of sessions and their topic
Create content

[x] Opening remark: The Jupyter landscape. & Illustrate with real research and education use cases. (@fperez and Edom)
[x] Using Jupyter in a research project: toy workflow presentation (@whyjz and #59)
[x] Breakout sessions A: Exploratory analysis: JLab, Widgets, IPython, RetroLab (@fperez )
[x] Breakout sessions B: Cloud native workflows at scale: JHub, Dask, Intake, RTC (@consideRatio, notes, slides)
[x] Breakout sessions C: Sharing, publishing, repro: nbviewer, JBook, Binder, GitHub (@whyjz )

[x] Make Google Form survey (@fperez; also @lrennels will help conduct the survey at the workshop)
[x] Make https://hydro.jupytearth.org and https://workflow.jupytearth.org point to @whyjz and @EMscience's GitHub pages (@consideRatio)

[x] @whyjz visit the settings, set a custom domain workflow.jupytearth.org, and then after a while when you can press the Force HTTPS checkbox.
[x] @EMscience visit the settings, set a custom domain workflow.jupytearth.org, and then after a while when you can press the Force HTTPS checkbox.

Please feel free to add anything you come up with at any time!

As we successfully hosted the JMTE workshop at the EarthCube meeting, I am closing this issue now but will follow up on the remaining tasks (e.g. #61) in a separate thread or two.


[Feature Request] Allow the folder attribute to be any const identifier

It seems that the folder attribute for the RustEmbed derive macro can only be a string literal. I have a need to use this directory string elsewhere as well, so it would be great if I could specify the folder attribute using a const identifier (or even any const expression) so I can define it in a single place.

The value needs to be used during the proc macro execution, which doesn't have access to the rest of your program. Proc macros receive the input as tokens, so we can't resolve the value of a variable, even if it's const.

Thinking a little more on this, it might work if include_bytes supports it, but I don't think it does.

Yeah, I definitely see that now, I've written some proc macros myself and had not taken into account how they actually work. In particular, I imagine that a const value could be used in the debug case where the directory is searched at runtime since presumably the macro produces code in the host program that does this and thus would have access to a const identifier. However, in the release case I see that this would not be possible since the directory is read at compile time instead.
I did a quick test and verified that you are correct in that neither include_bytes nor include_str work with const identifiers, and explicitly say that they require a string literal.
I tried another approach described in a reddit post I just made here, but it also didn’t work. I’ll also note that the env macro approach does work for include_bytes and include_str. If you’re as stumped as I am, we’ll see if anyone in my reddit post has any ideas for workarounds.

You can actually include whatever you want in attributes, it's just that right now the library expects a string. Whatever you write there will still just be unevaluated tokens to the macro though. The proc macro does read some metadata about the file (ex. hash, last modified time), so it does want the real path during its execution, but besides that it would technically be possible to accept an expression that resolves at compile time (ex. env macro) to a string that include_bytes would accept.

Yeah, based on my experience, I assumed that the proc macro itself is specifically looking for a string literal. I'm guessing that the syntax tree for the attribute could just be the macro expression, which does exist in syn for example. However, unless there's a a way inside the proc macro to actually evaluate the env macro I don't think it's possible to do this. It sounds like maybe this is just not possible.
Although, given that include_bytes does the same kind of things at compile time, it must be possible unless it's using some special black magic. I might look into how this is accomplished.

If you use the interpolate-folder-path feature you can use environment variables in the folder string, but that doesn't help much since now you'd need to set an env variable in addition to the const.

Yeah the interpolate-folder-path feature totally solved this for me. Maybe I should have completely read the docs before submitting and issue here!


Implementation of length penalty using logits processors

This implementation is simpler than changing the sampler code and less invasive in the core vllm code.

Closing this one because I didn't sign-off all commits. This is fixed in #14


onSwipeDown() didn't work for iOS     enableimagezoom false dint work for iOS

This is how i am using enableimagezoom

are we bona fix this issue any time soon i have ship this to client already and i found this error

Thanks it did work yesterday I figure it out but thanks again...
Get Outlook for Androidhttps://aka.ms/ghei36

From: 黄子毅<EMAIL_ADDRESS>Sent: Wednesday, August 8, 2018 7:19:51 AM
To: ascoders/react-native-image-viewer
Cc: Asfand; Author
Subject: Re: [ascoders/react-native-image-viewer] onSwipeDown() didn't work for iOS enableimagezoom false dint work for iOS (#219)
set enableSwipeDown=true, and onSwipeDown could work.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/ascoders/react-native-image-viewer/issues/219#issuecomment-411261873, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVeiz_9Ru10A9lZUSWMeWvlGNjsmvtJGks5uOkrHgaJpZM4Vymf9.


Test suite missing in PyPI tarball

The 17.0.0 tarball uploaded to PyPI doesn't have the tests directory, and it is therefore impossible to test the release. This is important for distro packaging. Could you please fix the MANIFEST.in to include tests?

As I understand it, Gentoo has multiple methods for generating a new package, including pulling tarballs from GitHub. As such, it doesn't seem entirely necessary to clutter the installable source package with the tests. Things on PyPI are meant to be pip installable. While some maintainers may choose to include tests, the tests are useless to anyone using the python packaging tooling.

@sigmavirus24  standard is download package from pypi..And including tests in sdist helps also for other distributions.
PIP isn't installable but distribute. Install is only one part of workflow

@mimi1vx It's not just an argument against doing this for Gentoo. The Python packaging guide has two kinds of archives:

source archive
source distribution (a.k.a, sdist)

An archive, as the name suggests, is the appropriate channel for tests from which one can generate an installable artefact. A distribution is an installable artefact. Just because others have been bullied and confused into including tests in an sdist doesn't mean it should actually continue.
That aside, turns out packagers only run the tests when convenient, regardless of whether they're present. I've had packages be shipped with broken patches because the packager didn't actually run the tests that I included at their behest. The same has been happening with other packages I'm aware of.
In short, packagers are overworked and no matter how much I try to help, educate, or guide, it makes little difference in the quality of distro-provided package versions of the software I've seen apart from me directly becoming involved (which I don't have time for).

While I agree with Ian, I don't have the energy for this recurring fight so I've just added everything and it will be part of the next release.


Investigate why fileHashes.lock sometimes stays locked on Windows

fileHashes.lock is sometimes still locked after a build finished.
Occurrence on CI:

https://builds.gradle.org/viewLog.html?buildId=2165815
https://builds.gradle.org/viewLog.html?buildId=2210377

Possible related commit:
https://github.com/gradle/gradle/commit/b0c142972089b382b22f99ef452c742d35df5603
Expected Behavior

It should always be possible to delete/modify fileHashes.lock after a build finished

Current Behavior

fileHashes.lock sometimes stays locked on Windows

Once this is fixed, remove @LeaksFileHandle / @Ignore from

[x] checkDefaultGradleUserHome- https://github.com/gradle/gradle/blob/e80e77278a02a9b8d38d3bdfe8e9026461f09a82/subprojects/integ-test/src/integTest/groovy/org/gradle/integtests/CommandLineIntegrationTest.groovy#L132-L132 (fixed by https://github.com/gradle/gradle/pull/1326)
[x] systemPropGradleUserHomeHasPrecedenceOverEnvVariable - https://github.com/gradle/gradle/blob/e80e77278a02a9b8d38d3bdfe8e9026461f09a82/subprojects/integ-test/src/integTest/groovy/org/gradle/integtests/CommandLineIntegrationTest.groovy#L195-L195 (fixed by https://github.com/gradle/gradle/pull/1326)
[ ] generates events for downloading artifacts - https://github.com/gradle/gradle/blob/5116753a4279a5b76a17ea8e4681838ac63ef9b4/subprojects/tooling-api/src/integTest/groovy/org/gradle/integtests/tooling/r35/BuildProgressCrossVersionSpec.groovy#L95-L95

This is intended behaviour. A process will keep this cache open until some other process requires the lock.
If these tests are failing because they happen to be using a test specific Gradle user home that they later delete, they should inform the test fixtures about this, which can in turn tell DefaultGradleUserHomeScopeServiceRegistry to eagerly close the cache.

I should clarify: "intended behaviour" doesn't necessarily mean "good behaviour". We might rethink how this works, or not.

I've tried to get rid of the @LeakFileHandle annotation here for another tapi test but without anyluck. I've tried manually passing the system property org.gradle.internal.reuse.user.home.services to the build manually but that didn't solve the problem. My latest try is here reusing requireIsolatedToolingApi: https://builds.gradle.org/viewLog.html?buildId=2328588&tab=buildResultsDiv&buildTypeId=Gradle_Branches_CommitPhase_WindowsCommit_WindowsCommitJava17_2WindowsCommitJava

@jjohannes Can you help out @breskeby so we can get this issue into the done state?

What @adammurdoch described earlier goes into the right direction I think. This is an issue with the tooling API test fixtures when running isolated daemons. In that case, we force kill the daemon at the end of the test (or do not stop it at all). Still we attempt to delete the daemon base dir, as it is inside the test folder. This leads to situations where the daemon might still hold file handles (or the handles did not get released yet because of the force kill).
I think the solution here, and probably to other file handle leaking tooling API tests, is to improve the test fixtures ToolingApi and ToolingApiSpecification in a way that they properly stop the isolated daemon and wait for it to be stopped during cleanup. Before the test directory is cleaned.
Note that there are several flags and fields in ToolingApi which influence whether a separte daemon base dir is used or not. This could use some simplification as well.
I am opening a separate issue for this on our CI health board and closing this one. I am also removing the bug tag, as this was only about test fixture issue.

Ran into this one...is there a link you can provide to the bug you mentioned opening on the CI health board. Any workaround or resolution other than reboot my machine so I can release this lock?

This is referring to Gradle's test infrastructure, not Gradle in general.
If you're running into this, you can try stopping daemons (gradle --stop).

Yes, I'm aware. I'm doing plugin developement testing for plugins used at my company. I execute tests using the Gradle Runner on Gradle versions from 2.6 - 3.5. I'm invoking the Gradle Runner with arguments that isolate the test into a temporary directory under my buildDir, something like build/acceptance-tests/...
Everything is fine when the tests are passing, but I just started adding 3.5 testing and have some test failures. Now, the fileHashes.lock is locked by the System process and then I start getting failures when I run the 'clean' task because it cannot delete the temporary directories used by my tests under the buildDir.
It sounds like this problem but perhaps I'm seeing a different similar bug?

@eric-isakson This sounds like a similar, but different issue to me. Maybe the GradleRunner is starting a daemon process and does not shut it down in case of failure in your case.
If this is still an issue for you, could you create a separate bug issue with an example that allows us to reproduce the problem? Thanks!

According to Microsoft documentation you should the gradle daemon
`
stop the Gradle daemon to ensure no files are left open (impacting the save cache operation later)
./gradlew --stop

`
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops


Fixed required SpatiaLite version in docs.

Can you say when it changed so we know how far to backport the correction?

See bc0aba7786978ec312809eae5ecb3d751608b5b7. It looks like it should be backported to 1.8.
I just noticed that 2.3 is also mentioned here https://github.com/django/django/blob/master/docs/ref/contrib/gis/install/spatialite.txt#L126.

Merged in 1a10ae45b102bd6dab15ef0bd95cda91635916ad, thanks.
Created https://code.djangoproject.com/ticket/25633#ticket for the outdated KyngChaos installation instructions. I'll mail the geodjango mailing to try to get feedback on that unless it's something you're knowledgeable about?

Nope, I have no idea what (who?) this KyngChaos is.


overlayfs does not support rename operations

https://github.com/containers/build/blob/master/examples/mongodb/build-mongodb.sh
Importing MongoDB's GPG keys fail because rename operations are not supported by overlayfs.
Beginning build with an empty ACI
Setting name of ACI to example.com/mongodb
Adding dependency "quay.io/sameersbn/ubuntu"
Running: [apt-key adv --keyserver keyserver.ubuntu.com --recv 7F0CEB10]
Downloading quay.io/sameersbn/ubuntu: [========================] 69.5 MB/69.5 MB
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.dFBktScdB2 --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 7F0CEB10
gpg: requesting key 7F0CEB10 from hkp server keyserver.ubuntu.com
gpg: renaming `/etc/apt/trusted.gpg' to `/etc/apt/trusted.gpg~' failed: Invalid argument
gpg: error writing keyring `/etc/apt/trusted.gpg': file rename error
gpg: key 7F0CEB10: public key "[User ID not found]" imported
gpg: error reading `[stream]': file rename error
gpg: Total number processed: 0
gpg:               imported: 1  (RSA: 1)
run: non-zero exit code: 2
Ending the build

A potential solution to this would be to run acbuild squash on the container before doing any rename operations, but that command hasn't been implemented (#18) yet.

Alternatively, Ubuntu could be declared not as a dependency but as the starting image, when doing acbuild begin.

What kernel version do you have?

uname -a
Linux node1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Can you repro on 4.7 or later?

Success on kernel 4.10, closing...

Odd that this was not mentioned in the documentation though.

It definitely should be, I'm going to reopen this as a reminder to myself to add that the next time I'm sparing some cycles for acbuild.


Facebook previews on user page don't play video

If you go to a user's page with a Facebook video post on it we only show the preview with no way to play it. Fix this.

@cguess I can't replicate this. When I go to a user's page, of any kind platform (including Facebook), I'm able to play the video.
We are using the native <video> tag and its native controls, which are hidden after a moment of inactivity. But you can click the video area to start playing, or hover (on desktop) to reveal controls.
Can you verify that this issue exists, and maybe we can screenshare about it if so?

Talking w/@cguess, this was meant to be about preview images not videos, thus a dup of #258.


Implement gRPC API for Social Media Sharing Customization

Fixes #809
Current Behavior
Description
Final PR for implementing gRPC API for Social Media Sharing Customization, will be followed by PR for implementing GraphQL API for Social Media Sharing Customization. gRPC API helps fetch OpenGraph Tags and Twitter Tags while GraphQL API will help update OpenGraph Tags and Twitter Tags

Hi @kapillamba4 , thank you so much for working this PR! I left few comments.


Switch to self-hosted Renovate in GHA

This change moves the Renovate bot from the hosted version to be running as a scheduled job in GHA.
This will allow us to run any post-upgrade command in our set up environment and allow us to use our tooling to update versions we use in variables that generate code or documentation like the Helm chart.
It does come with a downside that any actions with the bot (eg. asking for a rebase) does come with a delay as the bot runs every two hours (like on the tetragon repo).
Fixes: https://github.com/cilium/cilium/issues/25457

/test

This will be very nice improvement


Cypress tests search

Description
Added Cypress-test to test if the search works as intended with the listComponent

Related Issue(s)

closes #{issue number}

Verification

Manual testing

[ ] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added
[ ] Cypress E2E test(s) have been added
[ ] No automatic tests are needed here
[ ] I want someone to help me make some tests

User documentation @ altinn-studio-docs

[ ] Has been updated

[ ] No changes/updates needed

Changes/additions to component properties

[ ] Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
[ ] No changes made

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[ ] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board

Hei! Prøver du å merge på nytt igjen fra vår main, slik at vi får sjekket om cypress-testene er OK? :blush: Akkurat nå feiler de nok etter forrige PR, men det fikset jeg i #846

Hei! Prøver du å merge på nytt igjen fra vår main, slik at vi får sjekket om cypress-testene er OK? 😊 Akkurat nå feiler de nok etter forrige PR, men det fikset jeg i #846

Glemte å si at det ligger en PR i frontend-test for å få Cypress testen med søk til å funke: https://dev.altinn.studio/repos/ttd/frontend-test/pulls/16/files :)


Feature Request: Wireless Crafting Terminal

I don't know if you've seen the wireless crafting terminal for AE2 on 1.7.10, but it would be nice if we could craft/auto-craft on the go. I am usually always on the go and it's a bit of a nuisance to have to go all the way back to the terminal to craft something. Also, how about an upgrade for the wireless extenders to allow for cross-dimensional access? I believe the cross-dimensional upgrade would solve the need for multiple extenders.

If you are at the point where you have wireless, get autocrafting set up for the stuff you need on the go. Having a crafting grid in the wireless grid is way too OP.

Cross-dimensional access is OP as well

Ok. It was just a suggestion.


terminate called after throwing an instance of 'cv::Exception'

Thank u for your excellent work!
i got a error as following
terminate called after throwing an instance of 'cv::Exception'
what():  OpenCV(4.2.0) /home/opencv-4.2.0/modules/core/src/matrix_expressions.cpp:23: error: (-5:Bad argument) Matrix operand is an empty matrix. in function 'checkOperandsExist'
Aborted (core dumped)
Training progress:   8%|__                    | 2460/30000 [06:05<1:23:21,  5.51it/s, Loss=0.2444826$
so i want to know what is the version of opencv about your environments
thanks~ :)

For the opencv-python, our version is <IP_ADDRESS>. For the opencv for C++ in Propagation module, our version is 4.2.0. Hope this help you.

For the opencv-python, our version is <IP_ADDRESS>. For the opencv for C++ in Propagation module, our version is 4.2.0. Hope this help you.

Thanks for your reply :)

Thanks @kcheng1021 :)


Lots of TypeScript compilation errors when running webpack server

Checking this repo out, but I am having some issues with it. Any ideas? (I just cloned the repo and did a yarn install.) Could be #12 but I'm unsure...
$ npm run-script start

><EMAIL_ADDRESS>start /Volumes/extra/git/3rd-party/react-hot-ts
> webpack-dev-server

Project is running at http://localhost:8080/
webpack output is served from /

[at-loader] Using<EMAIL_ADDRESS>from typescript and "tsconfig.json" from /Volumes/extra/git/3rd-party/react-hot-ts/tsconfig.json.

[at-loader] Checking started in a separate process...

[at-loader] Checking finished with 174 errors
Hash: e68bb4bcf4aada26f5a8
Version: webpack 2.7.0
Time: 3813ms
        Asset       Size  Chunks                    Chunk Names
    bundle.js     1.3 MB       0  [emitted]  [big]  main
bundle.js.map    1.51 MB       0  [emitted]         main
   index.html  341 bytes          [emitted]
chunk    {0} bundle.js, bundle.js.map (main) 1.18 MB [entry] [rendered]
 [./node_modules/react-hot-loader/lib/patch.js] ./~/react-hot-loader/lib/patch.js 209 bytes {0} [built]
 [./node_modules/react-hot-loader/patch.js] ./~/react-hot-loader/patch.js 40 bytes {0} [built]
 [./node_modules/react/react.js] ./~/react/react.js 56 bytes {0} [built]
 [./node_modules/strip-ansi/index.js] ./~/strip-ansi/index.js 161 bytes {0} [built]
 [./node_modules/url/url.js] ./~/url/url.js 23.3 kB {0} [built]
 [./node_modules/webpack-dev-server/client/index.js?http:/localhost:8080] (webpack)-dev-server/client?http://localhost:8080 7.95 kB {0} [built]
 [./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.73 kB {0} [built]
 [./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.05 kB {0} [built]
    [0] multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server react-hot-loader/patch ./src/index.tsx 64 bytes {0} [built]
 [./node_modules/webpack/hot ^\.\/log$] (webpack)/hot nonrecursive ^\.\/log$ 160 bytes {0} [built]
 [./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.57 kB {0} [built]
 [./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 77 bytes {0} [built]
 [./node_modules/webpack/hot/log-apply-result.js] (webpack)/hot/log-apply-result.js 1.02 kB {0} [built]
 [./src/App.tsx] ./src/App.tsx 2.56 kB {0} [built]
 [./src/index.tsx] ./src/index.tsx 1.65 kB {0} [built]
     + 362 hidden modules

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3542:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'a' must be of type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>', but here has type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3543:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'abbr' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3544:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'address' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3545:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'area' must be of type 'DetailedHTMLProps<AreaHTMLAttributes<HTMLAreaElement>, HTMLAreaElement>', but here has type 'DetailedHTMLProps<AreaHTMLAttributes<HTMLAreaElement>, HTMLAreaElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3546:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'article' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3547:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'aside' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3548:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'audio' must be of type 'DetailedHTMLProps<AudioHTMLAttributes<HTMLAudioElement>, HTMLAudioElement>', but here has type 'DetailedHTMLProps<AudioHTMLAttributes<HTMLAudioElement>, HTMLAudioElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3549:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'b' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3550:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'base' must be of type 'DetailedHTMLProps<BaseHTMLAttributes<HTMLBaseElement>, HTMLBaseElement>', but here has type 'DetailedHTMLProps<BaseHTMLAttributes<HTMLBaseElement>, HTMLBaseElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3551:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'bdi' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3552:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'bdo' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3553:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'big' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3554:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'blockquote' must be of type 'DetailedHTMLProps<BlockquoteHTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<BlockquoteHTMLAttributes<HTMLElement>, HTMLElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3555:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'body' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLBodyElement>, HTMLBodyElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLBodyElement>, HTMLBodyElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3556:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'br' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLBRElement>, HTMLBRElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLBRElement>, HTMLBRElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3557:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'button' must be of type 'DetailedHTMLProps<ButtonHTMLAttributes<HTMLButtonElement>, HTMLButtonElement>', but here has type 'DetailedHTMLProps<ButtonHTMLAttributes<HTMLButtonElement>, HTMLButtonElement>'.

ERROR in [at-loader] ./node_modules/@types/react-hot-loader/node_modules/@types/react/index.d.ts:3558:13
    TS2403: Subsequent variable declarations must have the same type.  Variable 'canvas' must be of type 'DetailedHTMLProps<CanvasHTMLAttributes<HTMLCanvasElement>, HTMLCanvasElement>', but here has type 'DetailedHTMLProps<CanvasHTMLAttributes<HTMLCanvasElement>, HTMLCanvasElement>'.

[...more similar errors]

Looks like @types/react has been updated and broke something again...
Pull Requests welcome!

Pull Requests welcome!

Sure. Where should the debugging start, is it a matter of incompatible dependencies or what do you think?

It is definitely incompatible @types dependencies 👎 .
I would first check package.json, see if there are any more worthwhile updates (react, react-hot-loader, etc). After all up-to-date, check for errors again.
Look for GitHub issues which demonstrate any errors. I often find a comment like "Hey! Version X of dependency Y does not work with version A of dependency B! Downgrade dependency Y to version Z to fix! 💥 🎆 ". 🙄
In some cases, it may be a TypeScript update itself and we need to update dependencies and potentially make changes in our code, too.