Enable sampling for Custom Performance Counters

If you are reporting bug/issue, please provide detailed Repro instructions.
Repro Steps

Create a PerformanceCollectorModule and initialize it with TelemetryConfiguration.Active.
2.
Add PerformanceCounters by PerformanceCollectorModule.Add(new PerformanceCounterCollectionRequest("\Processor(_Total)% Processor Time", "% Total Processor Time")) //Note: You can add any counter here.
3.
Run steps 1 and 2 in a loop or add the same counter request in step 2 multiple times
Actual Behavior
The counter reports to AI multiple times in a very short time (even once every ms depending upon the loop). Try ingestion sampling or adaptive sampling to control the data ingestion in App Insights. It does not work.
Expected Behavior
Perf counters or atleast custom perf counters should be subject to sampling.
Version Info
SDK Version : Microsoft.ApplicationInsights.AspNetCore (2.2.0-beta3)
.NET Version : net470
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) :
OS : Windows Azure
Hosting Info (IIS/Azure WebApps/ etc) : Service Fabric

Application Insights does not sample metrics and sessions telemetry types. Reduction in the precision can be highly undesirable for these telemetry types.  This is by design.
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-sampling

I think the intent of this issue is to raise the idea that we might be able to throttle perf counters that are ingested and stored, rather than ingested and used for transient UX elements such as Live Metrics Data. The issue arose for this customer when a lot of perf counter data started clobbering his quota over the course of a day.
The way I understand it is that perf counter data is necessary for Live Metrics Streams as often as possible (depending on the counter of course), but whittling down the actual ingested perf counter data stored would only have an effect on historic data - much the same that any throttling has on other telemetry.

The way I understand it is that perf counter data is necessary for Live Metrics Streams as often as possible (depending on the counter of course), but whittling down the actual ingested perf counter data stored would only have an effect on historic data - much the same that any throttling has on other telemetry.

Live metrics counters collected using alternative approach. Those counters are not sent to the paid backend

Understood, then perf counters could be filtered, no? Or would doing so affect both Live Metrics Streams as well as ingested+stored data?


WIP: [Release] Add Nightly Release workflow implementation

Description:
This pull request adds implementation for the Nightly Release workflow.
Workflow description
Workflow triggers:

On schedule;
Manual launch;

The aggregate-release-data stage:

Resolve the latest commit from the main branch, and set the commit_sha output;
Check version number in sources, parse and verify it;
Generate a new version based on the version in sources, and set version_number output;

Version generation example:

Version in sources
Generation strategy
Nightly release version

1.4.0a1
{ version }.dev{m/d/Y}+nightly
1.4.0a1.dev01042023+nightly

The release-github-pypi stage:

Pass data from the aggregate-release-data stage to release workflow and call it;

Work example:

https://github.com/dbt-labs/dbt-core-release-test/actions/runs/3840385988

Example of work
Workflow run: https://github.com/dbt-labs/dbt-core-release-test/actions/runs/3840385988
Workflow log:

The prep-release/test-run/1.4.0a1.dev01042023+nightly_3840385988 branch created
Changelog file created successfully
Version successfully bumped in codebase to 1.4.0a1.dev01042023+nightly
S3 build artifact path: s3://core-team-artifacts/dbt-labs/dbt-core-release-test/artifacts_testing/1.4.0a1.dev01042023+nightly/3d92787e32bb3351a754507caa6c7d01c7ded26a
Draft release: https://github.com/dbt-labs/dbt-core-release-test/releases/tag/untagged-119c0caba1b4aedf3f5a

Published packages:

https://test.pypi.org/project/dbt-tests-adapter/1.4.0a1.dev1042023/
https://test.pypi.org/project/dbt-core/1.4.0a1.dev1042023/
https://test.pypi.org/project/dbt-postgres/1.4.0a1.dev1042023/


Trigger scale run

Description
Trigger scale run
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

/retest

/test

/test gke-postgres-scale-tests


How can we know that the room call is ended from the Other end. I my case i am join but the one who initiate the call when he leave the call I still remains in the call and its not ended

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Hi @MrDanis,
Please use the Events documentation to track when a remote participant joins or leaves.
The latest releases for Android and iOS include this feature.
Thank you.

Hi @iaulakh,
Can you please tell me is there any way to accept a room call if my react-native app is in the background or in quite state as much as i read the documentation i didn't find any thing  related to that. Can you help me out in that

Hi @MrDanis,
For a customized experience, please use the azure-communication-calling SDK. You can get started with this QuickStart guide. Note that the azure-communication-ui-calling library provides only UI controls to initiate a call.


[Bug] making images consistent with image

Page link
No response
Description
The issue was with the images variable not having the same fields as image variable. We added two fields Reference and ReferenceWithTag to make both of them consistent.
Expected behavior
We need to document this issue
Slack discussion
No response

@1Shubham7, can you please send a PR for the documentation now that the code PR has been merged? This was included in 1.11.2 so can be written now.

sure @chipzoller


⚠ Bofrost.fr has degraded performance

In fc16a55, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1428 ms

Resolved: Bofrost.fr performance has improved in d49a6f0 after 7 minutes.


Error converting int64 to string in support-scheduler

https://github.com/edgexfoundry/edgex-go/blob/373c3ec415297c572841227f0503c779245cc382/internal/support/scheduler/schedule.go#L556
Error:
Scheduling with intervalaction-> method = "PUT" does not work while method = "GET" still works normally.
Fix:
req.Header.Set(ContentLengthKey, strconv.FormatInt(int64(len(params)), 10))

@weichou1229 could you please check whether this issue still happens in V2?

This issue is fixed in V2.
https://github.com/edgexfoundry/edgex-go/blob/ca82cc67a24dd3a646f9c54faca12af7640f6229/internal/pkg/utils/restaddress.go#L82

@jpwhitemn , we need to note this in the change log Bug Fixes section


Gradle Icon duplication issue.

Keeping icons in your project that is compiled by the dependencies is causing this issue, check out the answer too:
http://stackoverflow.com/questions/29965398/gradle-finished-with-non-zero-exit-value-1-ic-launcher-png-error-duplicate-fi

duplicates https://github.com/yahoo/android-range-seek-bar/issues/27

Correction: duplicates https://github.com/yahoo/android-range-seek-bar/issues/21
@Tukajo, if you grab the latest from https://github.com/anothem/android-range-seek-bar this issue is fixed. It will be going out on JCenter soon as well.


Create a template for our kick-off calls with STLTs and Senders

Problem statement
As the engagement team, we need a way to standardize some of our outreach effects to onboard STLTs and Senders effectively and rapidly. I'd like to initiate some standardization by creating templates/forms that we can use for all partners.
What you need to know
I've attached an example of the prep document that we used for BD Veritor. I would like to design a template similar to this to use for/on the kickoff calls.

BD Veritor Example

Acceptance criteria

[ ] Standardized template/form that we can use on all kick-off calls

To do

[ ] Determine what questions our engineers might need
[ ] User research info that would be beneficial
[ ] Determine what questions are common for kick-off calls

Connected tasks:

Create outreach email
Create intake form and email
-Create mail merge in Kickoff template to bring in information from the form
-Create notifications in smart sheets to update internal stake holders
-Create kickoff process document

Link to Template

@jakefishbein-navapbc how is this different from the SOP?


Add self signed cert

New to me error...
An error occurred during a connection to <IP_ADDRESS>:8080. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG```


ReferenceError: Unknown plugin "transform-replace-object-assign" specified

Thanks for reporting an issue to us! We're glad you are using and invested in Enzyme.
Before submitting, please read over our commonly reported issues to prevent duplicates!
All common issues

common issues

Notoriously common issues

Webpack build issues
Cannot find module 'react-dom/lib/ReactTestUtils'
Query Selector fails
Testing third party libraries

If you haven't found any duplicated issues, please report it with your environment!
Current behavior
 FAIL  src/Comp/__test__/index.test.tsx
  ● Test suite failed to run

    ReferenceError: Unknown plugin "transform-replace-object-assign" specified in "/Users/~/xxx/node_modules/airbnb-prop-types/.babelrc" at 0, attempted to resolve relative to "/Users/~/xxx/node_modules/airbnb-prop-types"

      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
          at Array.map (<anonymous>)
      at Function.normalisePlugins (node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at OptionManager.init (node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
      at File.initOptions (node_modules/babel-core/lib/transformation/file/index.js:212:65)
      at new File (node_modules/babel-core/lib/transformation/file/index.js:135:24)
      at Pipeline.transform (node_modules/babel-core/lib/transformation/pipeline.js:46:16)

Expected behavior
Your environment
react-native
API

[ ] shallow
[ ] mount
[ ] render

Version

library
version

enzyme
"3.9.0"

react
"16.3.0"

react-dom
"16.3.1"

react-test-renderer
"16.8.6"

adapter (below)
"1.1.1"

Adapter

[x] enzyme-adapter-react-16
[ ] enzyme-adapter-react-16.3
[ ] enzyme-adapter-react-16.2
[ ] enzyme-adapter-react-16.1
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

<EMAIL_ADDRESS>  version "1.11.0"
  resolved "http://r.npm.sankuai.com/enzyme-adapter-utils/download/enzyme-adapter-utils-1.11.0.tgz#6ffff782b1b57dd46c72a845a91fc4103956a117"
  integrity sha1-b//3grG1fdRscqhFqR/EEDlWoRc=
  dependencies:
    airbnb-prop-types "^2.12.0"
    function.prototype.name "^1.1.0"
    object.assign "^4.1.0"
    object.fromentries "^2.0.0"
    prop-types "^15.7.2"
    semver "^5.6.0"

I think it's the mistake caused by the enzyme-adapter-utils upgrade.

This is a bug in the react native packager - it transpiles node_modules, which shouldn’t ever be done.
The temporary workaround until they fix this design flaw is to add a post install script to your app that deletes all .babelrc files in your node_modules dir.

Add resolutions in package.json:
  "resolutions": {
    "enzyme-adapter-utils": "1.10.1"
  },

It can also solve problems temporarily.

That doesn’t solve any problems though - all that does isn’t ensure you’ll be missing a ton of vital bug fixes and functionality.


cmd/compile: go1.21rc2: relocation R_X86_64_PC32 out of range error due to inliner changes

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

$ go version
go version go1.21rc2 linux/amd64

Does this issue reproduce with the latest release?
Builds successfully on go version go1.20.4 linux/amd64 and go1.19.x Fails on go1.21rc2
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH='amd64'
GOBIN='/home/user/go-code/bin'
GOCACHE='/home/user/.cache/go-build'
GOENV='/home/user/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/user/go-code/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/user/go-code'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/user/.cache/bazel/_bazel_rhang/b97476d719d716accead0f2d5b93104f/external/go_sdk_linux_amd64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/user/.cache/bazel/_bazel_rhang/b97476d719d716accead0f2d5b93104f/external/go_sdk_linux_amd64/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21rc2'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD=''
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2749149267=/tmp/go-build -gno-record-gcc-switches"

What did you do?
In testing our code against go1.21rc2 we found that a large go_binary target (we use Bazel) fails to build only on go1.21rc2.  git bisect points to this commit as the cause. The build time for this target also regresses significantly before the build exits compared to go1.20.4. Investigation details are posted in the last section of this ticket.
What did you expect to see?
Build pass. Program successfully builds.
What did you see instead?

external/go_sdk/pkg/tool/linux_amd64/link: running external/zig_sdk/tools/x86_64-linux-gnu.2.19/c++ failed: exit status 1
ld.lld: error: /tmp/go-link-3543165859/go.o:(function
some.internal.code._List_IncentiveOpsSupportData_Read: .text+0x38f310f0): relocation R_X86_64_PC32 out of range: -2147553908 is not in [-2147483648,<PHONE_NUMBER>]; references type:*
>>> referenced by go.go
>>> defined in /tmp/go-link-3543165859/go.o

// various forms of this error message are repeated until the end…

ld.lld: error: /tmp/go-link-3543165859/go.o:(function some.internal.code/base/xsync.(*TypedMap[go.shape.string,go.shape.*uint8]).Range.func1: .text+0x3b7ecbab): relocation R_X86_64_PC32 out of range: -2175929103 is not in [-2147483648,<PHONE_NUMBER>]; references type:*
>>> referenced by go.go
>>> defined in /tmp/go-link-3543165859/go.o

ld.lld: error: /tmp/go-link-3543165859/go.o:(function main.main: .text+0x3b7ed315): relocation R_X86_64_PC32 out of range: -2180777081 is not in [-2147483648,<PHONE_NUMBER>]; references type:*
>>> referenced by go.go
>>> defined in /tmp/go-link-3543165859/go.o

link: error running subcommand external/go_sdk/pkg/tool/linux_amd64/link: exit status 2

We're not able to post a reproducible program here since the code is internal but we have investigation notes that we hope the Go team will find helpful.
To narrow down what code patterns might cause issues in go1.21rc2, we searched for build artifacts that got significantly larger between go1.20 vs go1.21rc2 and found some.

(go1.20)
 % du -ch $GOPATH/bazel-bin/src/some.internal.code/go_default_library.a
576M
(go1.21)
% du -ch $GOPATH/bazel-bin/src/some.internal.code/go_default_library.a
709M

The generated packages are enormous but are built with generated code that follows a particular pattern that we believe does not interact well with go1.21rc2
The generated code makes extensive use of generics and anonymous function closures. Internally, we were able to rewrite the code generator to drop the use of generics and anonymous function closures and build the application successfully with go1.21rc2.
Unfortunately, we can’t share the exact code of the application but we can share the output of the code generator on a toy input before and after changes that allow the application to build on go1.21rc2.

}
// HandleFoo calls the generated generic function above with instantiated types.
func (h *fooHandler) HandleFoo(ctx context.Context, req *Request) (*Response, error) {
var res *ResponseV2
err := _cffFlowmagic_38_9(ctx,
_cffParamsmagic_39_3(req),
_cffResultsmagic_40_3(&res),
_cffConcurrencymagic_2515107422(8),
_cffWithEmittermagic_3224879298(cffemit.Metrics(h.scope)),
_cffWithEmittermagic_3224879298(cffemit.Logs(h.logger)),
_cffInstrumentFlowmagic_398550328("HandleFoo"),
_cffTaskmagic_13613616[func(req *RequestV2) (*GetManagerRequestV2, *ListUsersRequestV2)](
func(req *RequestV2) (*GetManagerRequestV2, *ListUsersRequestV2) {
return &GetManagerRequestV2{
LDAPGroup: req.LDAPGroup,
}, &ListUsersRequestV2{
LDAPGroup: req.LDAPGroup,
}
}),
// leaving out the rest HandleFoo ...
}
// the other _cff generated functions follow this form.
func _cffParamsmagic_39_3[t1 any](mmagic39_14 t1) func() t1 {
return func() t1 { return mmagic39_14 }
}
func _cffResultsmagic_40_3[t9 any](mmagic40_15 t9) func() t9 {
return func() t9 { return mmagic40_15 }
}

 Updated go1.21rc2 passing toy generator output
// This HandleFoo generated code is much simpler as it drops the use of generics and function closures to “pass through” values // in the scope of HandlerFoo to generated implementation functions defined at the bottom of the file.
// For context, the more complicated code generation scheme was created to avoid shifting line positions between source code
// and generated code to help with ends like Bazel-based code coverage and debugging in generated code.
func (h *fooHandler) HandleFoo(ctx context.Context, req *Request) (*Response, error) {
	var res *Response
	err := func() (err error) {
		/*line magic.go:37:18*/
		_37_18 := ctx
		/*line magic.go:38:14*/
		_38_14 := req
		/*line magic.go:39:15*/
		_39_15 := &res
		/*line magic.go:40:19*/
		_40_19 := 8
		/*line magic.go:41:19*/
		_41_19 := cffemit.Metrics(h.scope)
		/*line magic.go:42:19*/
		_42_19 := cffemit.Logs(h.logger)
		/*line magic.go:43:22*/
		_43_22 := "HandleFoo"
		/*line magic.go:46:4*/
		_46_4 := func(req *Request) (*GetManagerRequest, *ListUsersRequest) {
			return &GetManagerRequest{
					LDAPGroup: req.LDAPGroup,
				}, &ListUsersRequest{
					LDAPGroup: req.LDAPGroup,
				}
		}
                 // leaving out the rest of the implementation …
}

For the notable packages in the application, the symbol table dump is larger in go1.21c2 than in go1.20.

(go1.20)
$ go tool nm v1/go_default_library.a > /tmp/st1
$ du -ch /tmp/st1 (204M)

(go1.21rc2)
go tool nm v2/go_default_library.a > /tmp/st2
$ du -ch /tmp/st2 (240M)

Trying to understand what new symbols might be generated in go1.21rc2, we picked a specific function name (e.g. _cffFallbackWithcff_100088_4) and searched for all instances in the symbol table of the archive in go1.20 and go1.21rc2.

(go1.20)
2251c4d5 R some.internal.code..dict._cffFallbackWithcff_100088_4[*generated/example.code.User]
212faac4 r some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8_0].arginfo1<1>
212faac7 r some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8_0].argliveinfo<1>
18546595 T some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8_0].func1

(go1.21rc2)
99be885 T some.internal.code._cffFallbackWithcff_100088_4[*generated/example.code.User]
1db76b1d T some.internal.code._cffFallbackWithcff_100088_4[*generated/example.code.User]._cffFallbackWithcff_100088_4[go.shape.*uint8].func1
292dc4fa r some.internal.code._cffFallbackWithcff_100088_4[*generated/example.code.User].arginfo1<1>
292dc4fb r some.internal.code._cffFallbackWithcff_100088_4[*generated/example.code.User].argliveinfo<1>
299be7ff T some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8]
292dc4f5 r some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8].argi
nfo1<1>
292dc4f8 r some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8].argl
iveinfo<1>
1db76b18 T some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8].func1
2a7543c5 ? go:info.some.internal.code._cffFallbackWithcff_100088_4[go.shape.*uint8]$abstract
1d5260a4 T some.internal.code.(*userContextController).userContextRecentContactsValueOrderOrderBillingDataBillingDataEntityRef._cffFallbackWithcff_100088_4[go.shape.*uint8].func5
2a618793 R some.internal.code..dict._cffFallbackWithcff_100088_4[*generated/example.code.User]

Thanks for the report.
The specific CL that your bisection points to does increase the amount of inlining, so it is not too surprising that the code generated by the Go compiler is getting bigger, especially if you make heavy use of closures.
One thing that would be helpful here I think is if we had some understanding about just how much bigger your code is getting.    If you could link your program with some special flags (as below) and then capture the size of the intermediates (both with the old Go version and with 1.21rc2, that would be great. Here is an example on how to gather the data (this uses a build of "himom.go", but hopefully you can do something along these lines for your program):
$ cat script.sh
#!/bin/sh
set -x
set -e
rm -rf /tmp/xxx
mkdir /tmp/xxx
rm -f himom
go version
go build -ldflags="-linkmode=external -tmpdir=/tmp/xxx" himom.go
ls /tmp/xxx/go.o
size /tmp/xxx/go.o
$
$ // first build with 1.20
$ PATH=/ssd2/go1.20/bin:${PATH} sh script.sh
+ set -e
+ rm -rf /tmp/xxx
+ mkdir /tmp/xxx
+ rm -f himom
+ go version
go version go1.20.5 linux/amd64
+ go build '-ldflags=-linkmode=external -tmpdir=/tmp/xxx' himom.go
+ ls /tmp/xxx/go.o
/tmp/xxx/go.o
+ size /tmp/xxx/go.o
   text	   data	    bss	    dec	    hex	filename
1128573	  98096	 203032	1429701	 15d0c5	/tmp/xxx/go.o
$
$ // Then with 1.21rc2
$ PATH=/ssd2/go1.21/bin:${PATH} sh script.sh
+ set -e
+ rm -rf /tmp/xxx
+ mkdir /tmp/xxx
+ rm -f himom
+ go version
go version go1.21rc2 linux/amd64
+ go build '-ldflags=-linkmode=external -tmpdir=/tmp/xxx' himom.go
+ ls /tmp/xxx/go.o
/tmp/xxx/go.o
+ size /tmp/xxx/go.o
   text	   data	    bss	    dec	    hex	filename
1129686	  38416	 203824	1371926	 14ef16	/tmp/xxx/go.o
$

The "go.o" file is the output from the Go linker, prior to the point where it gets passed to the external linker.

Hey @thanm, thank you for taking a look.
I'm having a bit of trouble generating an archive or object file that's readable with the 'size' command. I first tried wrangling with our Bazel setup, but then moved on to a simpler go program and was still unsuccessful.
I created a simple go program
--- project/main.go ---
package main

import "my.experiment/project/other"

func main() {
    ohter.Fn()
}

--- project/other/other.go ---
packager other

func Fn() {}

$ cd project/other
$ go build -o outfile -ldflags="-linkmode=external -tmpdir=/tmp/xxx" ./other.go
$ ls
other.go  outfile
$  size outfile
size: __.PKGDEF: file format not recognized
size: go.o: file format not recognized
$  go tool pack x outfile
go.o  other.go  outfile  __.PKGDEF
% size go.o
size: go.o: file format not recognized
$ ls /tmp/xxx
ls: cannot access '/tmp/xxx': No such file or directory
However go tool objdump is able to succesfuly read project/other/outfile and project/other/_go_.o
I tried searching the docs in the go toolchain and the the closest thing I found was that go tool nm takes a -size option, but that seems to provide information per symbol. Is there an alternative command to run? I could try writing a go program to manually parse what size might give me? I hope i'm not missing anything.

The size program will work on an executable built from a main package.  It won't work on the object file created by compiling a non-main package.
If you follow @thanm 's script above you will get an object file in a temporary directory that size will work with.  Note that he is building a main package.

Thank you for the help!
With go1.20.5
 size /tmp/xxx/go.o
   text    data     bss     dec     hex filename
2130518528      27599283        2127160<PHONE_NUMBER>      80c2b8eb        /tmp/bliss-link-pre/go.o

With go1.21rc3
 % size /tmp/xxx/go.o
   text    data     bss     dec     hex filename
2429481255      27079443        2097744<PHONE_NUMBER>      928c268a        /tmp/bliss-link/go.o

A small note for anyone in the future who may encounter something similar with Bazel. I added the -tmpdir option to gc_linkopts attr of the go_binary rule.

Thanks for that.   Looks like your text size is up considerably, 15% or so,but more importantly you are working with a binary that it is already enormous and very close to being in the "danger zone" with respect to relocations (from text to data) not reaching.
I would suggest that you try to attack the problem from the angle of reducing the size of your generated code overall. In particular, in your generated code where you have functions that contain closures or return closures, e.g.
func _cffParamsmagic_39_3[t1 any](mmagic39_14 t1) func() t1 {

return func() t1 { return mmagic39_14 }

}

I would suggest changing your code generator to prefix these sorts of functions with "//go:noinline". This should (at least from what I can tell without being able to look at the complete source code) help restore the previous inliner behavior.
Hope this helps.

Thanks @thanm,
Understood, we just wanted to report this issue in the case there was an increase in size out of the bounds the Go team was expecting.

Circling back on this bug:  we don't have any plans to revert CL 492017, hence I think it makes sense to try to approach this problem via changes to your generated code. Closing this bug out, please reopen if needed. Thanks.


Ability to execute testinfra locally

I'm thinking about writing a testinfra ansible module.  This would allow tests to be written inside the playbook or tasks.   This is particularly useful when wanting to test something has happened but don't want to wait for the playbook to finish converging and verify at the end (such as the molecule workflow).
It looks as though the local driver could be leveraged.  I haven't done a lot of investigation yet, but is it possible?  Have you thought of this use case?

ping

Yes I think this could be possible and useful, all testinfra modules are available through a single object host that is returned by testinfra.get_host().
There is a similar attempt for salt (asserting with testinfra within the yaml sls file): https://github.com/saltstack/salt/blob/develop/salt/modules/testinframod.py
I guess the simplest way  is to have testinfra installed on target host since ansible modules are copied and executed on the target and use testinfra.get_host("local://").
For remote usage, maybe executing the module with local_action and use testinfra.get_host("ansible://$current_host?ansible_inventory=$current_inventory"),

Is there a documented python API vs CLI?


Remove transformer from DI

Avoid DI for AddSchemaDescriptionsTransformer as it seems to have a non-negligible performance penalty.

Before: https://github.com/martincostello/aspnetcore-openapi/pull/22#issuecomment-2273110771
After:

BenchmarkDotNet v0.14.0, Windows 11 (10.0.22621.3880/22H2/2022Update/SunValley2)
12th Gen Intel Core i7-1270P, 1 CPU, 16 logical and 12 physical cores
.NET SDK 9.0.100-preview.7.24406.8
  [Host]   : .NET 9.0.0 (<IP_ADDRESS>507), X64 RyuJIT AVX2
  ShortRun : .NET 9.0.0 (<IP_ADDRESS>507), X64 RyuJIT AVX2

Job=ShortRun  IterationCount=3  LaunchCount=1
WarmupCount=3

Method
Mean
Error
StdDev
Median
Gen0
Gen1
Gen2
Allocated

AspNetCore
18,696.7 μs
140,804.8 μs
7,717.99 μs
14,427.2 μs
609.3750
406.2500
156.2500
5290.23 KB

NSwag
373.4 μs
1,049.7 μs
57.54 μs
367.1 μs
2.9297
-
-
26.56 KB

Swashbuckle
11,594.9 μs
1,700.9 μs
93.23 μs
11,565.3 μs
156.2500
31.2500
-
1543.7 KB


Premium streaming endpoints can't be configured using all Azure CDN pricing tiers and providers

Hi,
it says in the article that Premium streaming endpoints can be configured using all Azure CDN pricing tiers and providers, but I tried and it doesn't seem like you can configure Standard Microsoft CDN.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3ee49eb7-e434-646b-483e-ffe1b9c5272c
Version Independent ID: ec9a1643-6612-364b-5f73-c7fcfa2d9691
Content: Stream content with CDN integration - Azure Media Services
Content Source: articles/media-services/latest/scale-streaming-cdn.md
Service: media-services
Sub-service: rest-v3
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

Thanks for bringing this to our attention @jkovacev . We are investigating and will get back to you.

This has been forwarded to Support.

Thanks for the update @IngridAtMicrosoft.
@jkovacev We will now proceed to close this thread since this issue is being addressed by Support.


JvmOverloads on GridKt._clickItem

Hi there :)
Could you add overloaded methods for GridKt._clickItem method with default values?
Getting a column in Java every time when I need to click a row item looks quite redundant.
Best regards

Thanks a lot :)

No problem :) Released as 1.1.6, please try it out

Great! :) It works fine.
Thanks for fast release.
czw., 9 maj 2019 o 12:52 Martin Vysny<EMAIL_ADDRESS>napisał(a):

No problem :) Released as 1.1.6, please try it out
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mvysny/karibu-testing/issues/22#issuecomment-490855340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABRBL3NQDN4LUIMEMKQNZ4LPUP65NANCNFSM4HLQ7D3Q
.


Extract and re-use element morphing logic

Follow-up to #1185
Related to #1192
The morph{Page,Frames,Elements} functions
Introduce a new src/core/morphing module to expose a centralized and
re-usable morphElements(currentElement, newElement) function to be
invoked across the various morphing contexts. Next, move the logic from
the MorphRenderer into a module-private IdomorphCallbacks class. The
IdomorphCallbacks class (like its MorphRenderer predecessor) wraps a
call to Idiomorph based on its own set of callbacks. The bulk of the
logic remains in the IdomorphCallbacks class, including checks for
[data-turbo-permanent]. To serve as a seam for integration, the class
retains a reference to a callback responsible for:

providing options for the Idiomorph
determining whether or not a node should be skipped while morphing

The MorphingPageRenderer skips <turbo-frame refresh="morph"> elements
so that it can override their rendering to use morphing. Similarly, the
MorphingFrameRenderer provides the morphStyle: "innerHTML" option to
morph its children.
Changes to the renderers
To integrate with the new module, first rename the MorphRenderer to
MorphingPageRenderer to set a new precedent that communicates the
level of the document the morphing is scoped to. With that change in
place, define the static MorphingPageRenderer.renderElement to mirror
the other existing renderer static functions (like
PageRenderer.renderElement, ErrorRenderer.renderElement, and
FrameRenderer.renderElement). This integrates with the changes
proposed in #1028.
Next, modify the rest of the MorphingPageRenderer to integrate with
its PageRenderer ancestor in a way that invokes the static
renderElement function. This involves overriding the
preservingPermanentElements(callback) method. In theory, morphing has
implications on the concept of "permanence". In practice, morphing has
the [data-turbo-permanent] attribute receive special treatment during
morphing.
Following the new precedent, introduce a new MorphingFrameRenderer
class to define the MorphingFrameRenderer.renderElement function that
invokes the morphElements function with newElement.children and
morphStyle: "innerHTML".
Changes to the StreamActions
The extraction of the morphElements function makes entirety of the
src/core/streams/actions/morph.js module redundant. This commit
removes that module and invokes morphElements directly within the
StreamActions.morph function.
Future possibilities
In the future, additional changes could be made to expose the morphing
capabilities as part of the window.Turbo interface.
For example, applications could experiment with supporting Page
Refresh-style morphing for pages with different URL pathnames by
overriding the rendering mechanism in turbo:before-render:
addEventListener("turbo:before-render", (event) => {
  const someCriteriaForMorphing = ...

  if (someCriteriaForMorphing) {
    event.detail.render = Turbo.morphPage
  }
})

addEventListener("turbo:before-frame-render", (event) => {
  const someCriteriaForMorphingAFrame = ...

  if (someCriteriaForMorphingAFrame) {
    event.detail.render = Turbo.morphFrames
  }
})

@seanpdoyle thanks for your work here 🙏. I'm reviewing this one before the week ends.


Making released action more automated

As title, it should let the released action be more automated.
The reference is available here.

Fixed via the following PRs:
#1322 and #1321.


Causes runelite to hang when switching the new runelite profiles

Recently runelite added a profile switcher. It does not do everything plugin presets does, and I value the plugin still.
However, when switching runelite profiles it will cause the client to hang for 1-3 minutes when the plugin is enabled.

Are you able describe some exact steps to reproduce this? I haven't had any issues with core profiles with plugin presets resently. Does the issue still arise if you uninstall the plugin?

The issue will go away when the plugin is disabled or uninstalled. As soon as it's enabled, swapping to another profile hangs the client.
If I make a brand new core profile, and change to the normal profile with the plugin, it will be fine. But changing from the profile with the plugin enabled, to a blank profile it will lock up.
Seems to be an issue with stopping the plugin on switch.

Anything on the logfile?
_But changing from the profile with the plugin enabled, to a blank profile it will lock up.
Seems to be an issue with stopping the plugin on switch._
Can you elaborate this more? What kind of presets and profiles you have? Are you logged into ReneLite account?

Had a hang on changing a profile that I couldn't figure out, Adam recommended profiling it. Figured out this was the culprit, and hopefully this is useful!

Hi Jademalo, I think that this might be caused by the plugin checking all of the config changes when switching profiles. I'll need to fix this once I have some time.

This is most likely fixed now in https://github.com/antero111/plugin-presets/commit/6e9370a9b1c6d4c6600d0f2cd59ae0cf1d57adb4. Profiles and the plugins config changed handler collapsed quite badly and caused the lag.


Support for SHA-256/512?

Are there any plans to add SHA-256/512 in addition to the "broken" SHA-1?

Hey @vguna I'm sorry to tell you it, but this project is going to deprecated :(


Docker image: missing GLIBC dependency.

Is there an existing issue for this?

[X] I have searched the existing issues

Description of the bug
The docker image is failing to run the program due to a missing GLIBC dependency.
Steps To Reproduce

Use the latest image
Run the program

Expected behavior
The program can execute without errors.
Screenshots / Logs
git-cliff: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by git-cliff)`
Software information
The official docker immage on gitlab runners.
Additional context
No response

Hey guys! Good timing, I'm in the middle of creating a new release :D
I think it is due to c28121c1aa427c3169df218a9803d838172f7c24 and should be fixed in 8bd0607e231e219f9b60eb4c7f0d8353ef4462e0 (bullseye contains libc6 according to these docs)
Thanks for reporting!

Oops, I guess I need to use bookworm instead, https://github.com/orhun/git-cliff/commit/36ad993d5956270c0df8c12d201068c1b4d7c580

Can you try again with latest?


Towards 0.2

Help needed.
This branch includes some changes that we have been discussing, mainly:

restructuring the code to make it simpler for devs
making --future the only option

Still pending are:

@cdondrup QTCBS family has not been restructured; I have provided the abstractmethods that need to be implemented; can you please restructure it? I will provide more details below.
@pet1330 Can you change the RCC relations according to PR #128 Sorry but it was not merged when I pulled master; shouldn't take long.

Some notes:

make function is replaced by make_world_qsr_trace. This is the main function that a dev should implement and has a lot of the previous overhead removed.
The overhead now is integrated in functions:
_process_qsrs_for
_process_qsr_parameters_from_request_parameters
_postprocess_world_qsr_trace
_init_qsrs_for_default
There are also new abstract classes:
QSR_Monadic_Abstractclass
QSR_Dyadic_Abstractclass
that also handle some of the common overhead.

PR that needs rejecting:

#136 as default behaviour of dyadic relations is to return all possible combinations (i.e. including mirrors) see also file combinations_and_permutations
#131
#128

Also I suggest blocking the remaining PRs till we get this sorted first.
Footnotes:

argd and argprod are bugged, working on it.
code far from cleaned up but can be done in parallel.
qsrs_for not fully tested but with the new way it is much easier to change and debug to what we finally decide.

Any questions shoot.
Many thanks.

Confirm you agree with PR rejections.

Ah yes and for examples see MOS or RCC2.

I have  few comments, sadly I cannot make inline comments, so please bare with me:

qsrlib the previous try and except should be faster than an if. The if is executed every time even though the default case will be that the qsr does exist. The except block is only executed when the exception occurs.

qsr_abstractclass

postprocess: why is this abstract. The normal implementation will always be:

def _postprocess_world_qsr_trace(self, world_qsr_trace, world_trace, world_trace_timestamps, req_params, qsr_params):
      return world_qsr_trace

why burden the dev with copying this? I only know of qtc that would currently need this being overridden.

handle_future: Just remove this. We want to get rid of deprecation, not include any more.
parameters: This could have a standard implementation:

def _process_qsr_parameters_from_request_parameters(self, req_params, **kwargs):
      try:
          qsr_params = req_params["dynamic_args"][self._unique_id]
      except KeyError:
          try:
              qsr_params = req_params["dynamic_args"]["for_all_qsrs"]
          except TypeError:
              pass
      except TypeError:
          pass
      return qsr_params

and just return the dictionary?!
Regarding rejection of QSRs:

#136 This returns all combinations as well but makes sure that they are only computed once. Do you do that as well? Couldn't find it on first glance.
#131 Is yours anyway, no opinion.
#128 should imho be merged now and then @yianni rebases his branch and makes the necessary adjustments

Regarding the blocking of PRs, that depends on who you want to do the work. The creator of the PR by giving your work precedence or yourself by merging the PRs now and then you making the necessary adjustments to resolve conflicts. Apart from sparing me some work, I also think that you know your changes the best and it would therefore make sense that you make them instead of us trying to find out what changed and then rebasing all our PRs.

BTW: Have you seen this: https://github.com/strands-project/lamor15/issues/1#issuecomment-133329040 ?

See below:

I have few comments, sadly I cannot make inline comments, so please bare with me:
qsrlib the previous try and except should be faster than an if. The if is executed every time even though the default case will be that the qsr does exist. The except block is only executed when the exception occurs.
This if hardly puts any overload, but that's fine, will take it off. The try/except makes debugging a pain... the error can be anything and different than the message. Might as well leave it unprotected.
qsr_abstractclass
postprocess: why is this abstract.
Agree. Non-abstract is fine.
handle_future: Just remove this. We want to get rid of deprecation, not include any more.
Code is being cleaned up, this is not used anywhere at the moment.

parameters: This could have a standard implementation:
def _process_qsr_parameters_from_request_parameters(self, req_params, **kwargs):
try:
qsr_params = req_params["dynamic_args"][self._unique_id]
except KeyError:
try:
qsr_params = req_params["dynamic_args"]["for_all_qsrs"]
except TypeError:
pass
except TypeError:
pass
return qsr_params
and just return the dictionary?!
Don't like this for many reasons, it does not allow pick-and-mix between the two namespaces, hence might as well force only the QSR namespace as the for_all_qsrs has no use then, creating some overhead for common attributes.

Regarding rejection of QSRs:
#136 This returns all combinations as well but makes sure that they are only computed once. Do you do that as well? Couldn't find it on first glance.
What do you mean? If it does so, then I am very much against it because this way forces that all data should be present. Such change needs to be clear and discussed beforehand.

#131 Is yours anyway, no opinion.
Still doesn't matter who makes the PR.

#128 should imho be merged now and then @yianni rebases his branch and makes the necessary adjustments
Can do that also.

Regarding the blocking of PRs, that depends on who you want to do the work. The creator of the PR by giving your work precedence or yourself by merging the PRs now and then you making the necessary adjustments to resolve conflicts. Apart from sparing me some work, I also think that you know your changes the best and it would therefore make sense that you make them instead of us trying to find out what changed and then rebasing all our PRs.

Don't mind either way.

I have few comments, sadly I cannot make inline comments, so please bare with me:

qsrlib the previous try and except should be faster than an if. The if is executed every time even though the default case will be that the qsr does exist. The except block is only executed when the exception occurs.

This if hardly puts any overload, but that's fine, will take it off. The try/except makes debugging a pain... the error can be anything and different than the message. Might as well leave it unprotected.

It only looks for a KeyError but I agree that the key error might also occur down the line. Fell free to change it if you like.

parameters: This could have a standard implementation:
def _process_qsr_parameters_from_request_parameters(self, req_params, **kwargs):
try:
qsr_params = req_params["dynamic_args"][self._unique_id]
except KeyError:
try:
qsr_params = req_params["dynamic_args"]["for_all_qsrs"]
except TypeError:
pass
except TypeError:
pass
return qsr_params
and just return the dictionary?!

Don't like this for many reasons, it does not allow pick-and-mix between the two namespaces, hence might as well force only the QSR namespace as the for_all_qsrs has no use then, creating some overhead for common attributes.

This should do the trick and take the global ones if there are no namespace ones
def _process_qsr_parameters_from_request_parameters(self, req_params, **kwargs):
    qsr_params = {}
    try:
        for k,v in req_params["dynamic_args"]["for_all_qsrs"]:
            qsr_params[k] = v
    except KeyError:
        pass
    try:
        for k,v in req_params["dynamic_args"][self._unique_id]:
            qsr_params[k] = v
    except KeyError:
        pass
    return qsr_params

#136 This returns all combinations as well but makes sure that they are only computed once. Do you do that as well? Couldn't find it on first glance.

What do you mean? If it does so, then I am very much against it because this way forces that all data should be present. Such change needs to be clear and discussed beforehand.

The argd previously created only QSRs for one object combination and excluded the inverse one. This resulted in o1,o2 having a argd value and o2,o1 not having one which is very non deterministic in nature. The PR just removes the check where inverse object combinations are discared and then calculates argd for o1,o2 and looks it up for o2,o1. I don't see a problem there as this is only used if no qsrs_for is given.

#131 Is yours anyway, no opinion.

Still doesn't matter who makes the PR. Feel free to comment.

I'm just not sure if the new branch resolves this issue a different a way so I relied on your judgment ;) Still I think that the inconsistent way of implementation used in #131 should never be merged but but I already said so in #114

Sceptical about the one below as allows the user to give its own names and break things. Anyway can also be changed later; as I am trying to get the core of the 0.2 out ASAP. Such improvements can be done later.

This should do the trick and take the global ones if there are no namespace ones

def _process_qsr_parameters_from_request_parameters(self, req_params, **kwargs):
    qsr_params = {}
    try:
        for k,v in req_params["dynamic_args"]["for_all_qsrs"]:
            qsr_params[k] = v
    except KeyError:
        pass
    try:
        for k,v in req_params["dynamic_args"][self._unique_id]:
            qsr_params[k] = v
    except KeyError:
        pass
    return qsr_params

@cdondrup OK, the latest commit on my towards-0.2 branch is missing the QTCS family to be brought up to speed. Can you have a look please? I will carry on with some other things in the meantime but I won't touch the QTCS* files to avoid conflicts. If you can do the same and stay out of the rest of the files other than the QTCS* it would be great :P.

Ah yes and ask me if you need something.... but in the end of the day all needed should be the make_world_qsr_trace and process_qsr_parameters... functions. Look MOS for example.

Will do but might not be able to before tomorrow.

That's fine. Thanks.

I'll leave a few suggestions here while which I came across while altering QTC:

Set req_params = req_params["dynamic_args"]
Set _for_all_qsrs = "for_all_qsrs" in abstract class so one can use req_params[self._for_all_qsrs] to get the global ones.
Check if the objects are available in both timestamps before running calculations:

if set(world_state_now.objects.keys()) != set(world_state_previous.objects.keys()):
               ret.add_empty_world_qsr_state(t)
               continue # Objects have to be present in both timestamps

custom_checks_qsrs_for still necessary? You state this in the code:

   def custom_checks_for_qsrs_for(self, qsrs_for, error_found):
       """Custom checks of the qsrs_for field

       :param qsrs_for: list of strings and/or tuples for which QSRs will be computed
       :param error_found: if an error was found in the qsrs_for that violates the QSR rules
       :return: qsrs_for, error_found
       """
       raise DeprecationWarning("No longer needed")

But in qsr_abstractclass line 114 we find this: qsrs_for_ret = self.custom_checks_for_qsrs_for(qsrs_for_ret)
OK, I'll open a PR to your branch @yianni
QTC now works for me.

I'll merge the PR and have a look later... Some things have changed since then.

Just saw it... have to rebase first, got conflicts.


add link to nomad-deploy

Hey there!
nomad-deploy is a little Python script I wrote for our CI/CD pipeline. It can take variables from different sources - os environment, yaml file or command line arguments - and render them into a Jinja2 template. Then it plans and executes the job on nomad.
There is a readme, some basic CLI documentation, as well as an executable python module that can be installed via Pip.
Cheers :)

@iakovmarkov very cool - thank you :)
Out of curiosity, why didn't https://github.com/jrasell/levant work for you ?

@jippi in the very beginning I've used Levant, but it was lacking in what it could do in terms of templating - defaults, conditions, importing template. Jinja2 has all this out of the box, with a familiar syntax.
I also remember having issues with the way Levant handled failing allocations, but I can't say what exactly was the problem. I just remember it didn't really work in our CI pipeline.


Intl support polyfill fails to load timezones on Android on 0.59.10

Intl polyfill has stopped working on 0.59.10, after upgrading we found our app was producing Invalid DateTime for all timezone related strings on Android.
Diving more deeply, the following code crashes:
Intl.DateTimeFormat("en-US", { timeZone: 'America/New_York' }).format()
and produces
RangeError: timeZone is not supported
Package.json includes:
"intl": "^1.2.5",

and Root.js has:
import 'intl';
import 'intl/locale-data/jsonp/en';
import 'intl/locale-data/jsonp/de';
import 'intl/locale-data/jsonp/fr';

React Native version:
info
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 834.63 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 11.12.0 - /usr/local/bin/node
Yarn: 1.16.0 - ~/.yarn/bin/yarn
npm: 6.10.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28
Build Tools: 22.0.1, 24.0.0, 27.0.3, 28.0.3, 29.0.0
System Images: android-24 | Android TV Intel x86 Atom, android-24 | Intel x86 Atom, android-24 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: ^0.59.10 => 0.59.10
npmGlobalPackages:
create-react-native-app: 0.0.6
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
Steps To Reproduce

install intl polyfill
add import 'intl' to your Root.js
call Intl.DateTimeFormat("en-US", { timeZone: 'America/New_York' }).format()

Describe what you expected to happen:
App should not crash on lookup of the timezone string.

Linked issue in Luxon: https://github.com/moment/luxon/issues/541

I can't upgrade to 0.60 due to a whole host of issues affecting dependent packages. I do need to upgrade to 0.59 though for the 64 bit support which is due next month.

Ay carumba.
🤦♂
https://github.com/andyearnshaw/Intl.js/blob/master/src/12.datetimeformat.js#L196
Was Intl support working before on android?

As it turns out intl polyfill and associated are totally uneeded.  I found buried in react-native-community (this wasn't listed in breaking issues!)
https://github.com/react-native-community/jsc-android-buildscripts#international-variant
I followed that guide and removed intl polyfill and all is well.

https://www.npmjs.com/package/date-time-format-timezone
this helped me

https://www.npmjs.com/package/date-time-format-timezone
this helped me

How did you import it into your app to make the Intl.DateTimeFormat method work for Android?


Permalink of a new widget page

I am using academic to create a website. But I want to add projects as a new page(widget_page) to be specific using instructions Here . But when I deploy it to github pages, the link to the page is of the format baseurl/baseurl/portfolio instead of baseurl/portfolio. On localserver it's just localhost/portfolio. For example in my case it become mnishant2.github.io/mnishant2.github.io/portfolio.
You can check Here .How to fix this

These issues are for bug reports and feature requests. For support, see https://github.com/gcushen/hugo-academic/blob/master/.github/support.md


reset bot in teams channel

Hello
is there a way to reset a bot from teams. I've tried removing the Teams channel and adding it back, but the bot won't respond to anything anymore. I kind of sitting with a mute bot in my Teams...

C# or Node.js ?

Node
On Feb 9, 2017 07:31, "Dan Marshall"<EMAIL_ADDRESS>wrote:

C# or Node.js ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/2213#issuecomment-278558915,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGKUIOdI_SVWX5UQRIMF5eP9xtcDWt5Hks5rarKdgaJpZM4L7bid
.

Have you tried this:
https://docs.botframework.com/en-us/technical-faq/#my-bot-is-stuck--how-can-i-reset-the-conversation

By stuck do you mean you're not receiving anything from Teams?  Have you tried running you code locally with ngrok to see if Teams is hitting it?
https://docs.botframework.com/en-us/node/builder/guides/core-concepts/#debugging-locally-using-ngrok

/deleteprofile did the trick thanks a lot
On Fri, Feb 10, 2017 at 4:30 PM, Richard Moe<EMAIL_ADDRESS>wrote:

By stuck do you mean you're not receiving anything from Teams? Have you
tried running you code locally with ngrok to see if Teams is hitting it?
https://docs.botframework.com/en-us/node/builder/guides/
core-concepts/#debugging-locally-using-ngrok
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/2213#issuecomment-278975135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGKUIJEo98LmKSLIMR29E1WUijOiRx1mks5rbIKZgaJpZM4L7bid
.


Adding ssh-config command

I suggested this on Slack and I was told it would be a good PR.
So far it's looking good, simple and working.
I am starting the PR for an early review and any guidelines/comments.
The only extra thing I'd like to do is to also add tunnel information to the ssh config. This could be simple-ish, like providing ports for the forward, or a bit more complex and attempt to parse the actual ~/.ssh/.config to make sure local ports are not being re-used. Not sure if it's worth actually doing that.

@pjcdawkins see an initial tunnel addition, I I can attempt to parse .ssh/config, thing is a good idea? thoughts on this?

Another option I am considering, instead of parsing .ssh/config.. is simply storing locally the previously used ports for each combination of alias.environment, so that new calls to ssh-config for the same alias.environment would yield the same ports all the time but new tunnels would get new port numbers.
I am thinking wether I should store ports for alias.environment or better project.environment so that the same port could be used with different alias. I think this is even better.

Well, I ended up working out the latter alternative as I think it's best. No need to parse anything out of a file that the cli uses. If there are other custom config that uses the same port, it'd be up for the user to tweak the others.
With this, the same por will be use for the same relationship until some key changes, in which case the port will change.
I actually think that loadCommandConfig and writeCommandConfig can be slightly reworked and put into CommandBase so that any  command could leverage from this option. Filename could simply be the command name.

If interested in that, I can provide either a wider PR on this one, or a separate one if this is accepted as is.

I should also note that having this in ssh allows for bash/shell completion, which is pretty useful.

Just bumping this one, been using it so far pretty nicely, so if possible to be accepted great, so I don't have to use my fork for when I need this.

@pjcdawkins just picking up on this, I rebased the commits and changed the writing of the configs into the already present config.yaml file.. relying entirely on CliConfig.
Let me know wha you think.

I'll look into the code changes.. the reason I went for making the ports used persistent is because I thought that once you get your ssh config and your tunnels setup, say with a sql client of the sort or whatever, you might want to always access the same database at that port. I also found myself branching a development environment and then maybe destroying it, to branch it again some time in the future, and I thought as a nice addition to always get the same ports for the same environment. And as I needed to at least store persistently the last used port, I thought of storing that as well.
I first did it on a per-command file, but found myself replicating a bit of the logic that was already there for storing/reading the config file, so that's why I switched to that, but a per command file would be OK as well, and I'd do it in CommandBase so that any command could use it.

Oops, closed it accidentally.

Hang on, I do think that the global config file is better than a per-command file, if it's decided that this info should be stored in a user-editable YAML file. I'm just not sure it's best placed there. Also, maybe it should be overridable from a command option.

In this particular command, maybe it's not that much of a big deal, I guess you could always output the same ports on the relationships and then edit it yourself manually in the ssh config, at least that makes it for a simpler addition and we can discuss/analyse the option of making the ports persistent on some other issue/PR? But sure, I'll hang and let me know what you think.

@pjcdawkins well, for what it's worth, I changed for storing a state json file per command. Kind of what tunnel does, which could be refactor into using this same logic. I attempted to remove all of that but for me it makes sense so that the ports are not repeated.
Also addressed your reviews.

Just rebased the code on top of the latest changes.

I guess this PR could use a rebase, not sure if you are happy with merge commits with all intermediate ones or prefer to squash some.

@hanoii when/if you have time could you write a short description as to how/when to use this?
BTW, I'm using the cache for the ports info, mainly because it's already a "service" and I didn't want to add to CommandBase. The disadvantages are that it can't be user-edited, and it would be flushed by platform cc. I'm not certain how bad that is.

@pjcdawkins i guess this is more a personal preference than anything else, but if it would be as temporary as a cache, you might be better off not caching it at all.
I rely on .ssh/config heavily, which means I configure shortcuts and tunnel information there rather than command line or even platform ssh or platform tunnel:open for that matter. It saves me time and keystrokes. I like to do something like ssh project.environment, and know that when logged in, I have all tunnels open. This can be used with scp as well. Then you are able to configure your local clients (mysql, redis, etc) and access them consistently. I'd say that's the use case.
I really never append it to .ssh/config, but rather copying and pasting. The reason that I wanted the ports to be always the same is because I configure, say mysql client, to access a specific port in localhost. If that port changes for whatever reason, I would have to change configuration. It's not a major thing and I don't think it will really be an issue. It's simply saving time when working with several projects and knowing each port you get from ssh-config would be unique within your workstation.

I see. It is cached permanently, unless you run platform clear-cache... still I guess that's not quite enough.

I like to do something like ssh project.environment, and know that when logged in, I have all tunnels open.

We could implement something like:
platform ssh --local-forward --local-port-start 30000

which would run
ssh -o 'LocalForward 30000 database.internal:3306' etc.


Add Support for [RFC 6750] Bearer Token Usage (a.k.a. Opaque Tokens)

Expected Behavior

Current Behavior

Context

@dfcoffin The purpose of the Bearer Token Usage RFC 6750 is to specify how a client can use a bearer token when requesting a protected resource. The 3 options are header, form parameter and query parameter. The bearer token can be either opaque or self-contained (JWT). This spec is specific to the client.
The Token Introspection RFC 7662, specifies how a protected resource can introspect an opaque access token to determine the claims associated with the opaque access token in order to make an authorization decision. The authorization server will grant an opaque access token to the client and then the client will call the resource server, which in turn will call the authorization server's introspection endpoint to return the claims associated with the access token and apply the authorization. So the bottom line is that #52 will deliver opaque token support.
Hope all this makes sense?

Does Release 0.0.1 support the generation of JWT and Opaque Tokens? If not what currently listed tasks will produce an opaque access token?


sst_importer: create a getter function for import path of an import file

Signed-off-by: CalvinNeo<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: ref #12849
What's Changed:

create a getter function for import path of an import file

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
None

/cc @BusyJay @tonyxuqqi

/hold

In https://github.com/tikv/tikv/pull/13061


Optionally instruct nginx to proxy assets from S3

This complements the change in the asset-manager nginx config.
The app sets the X-Accel-Redirect header to instruct nginx to proxy
the request for an asset to S3.
We're generating a presigned URL for the assets on S3 so that we can
avoid making them publicly accessible. The presigned URL is valid for 1
minute which should be enough time for nginx to use the URL to make the
request.

Thanks for the review, @floehopper.
I've just rebased on master and made some changes based on the updates in https://github.com/alphagov/govuk-puppet/pull/6280.
Can you review it again, please?


Enable readthedocs

Description of feature
Sphinx documentation should contain at least the API docs for the classes, and a tutorial.

Skipping since we'll merge it into pertpy


Add a link to David Snopek's video tutorial series about Godot and GiitLab CI

First of all, thanks so much for maintaining this project and always making sure that you have a new Docker image up when new Godot versions come out! It's wonderful that the community has this valuable resource available. :-)
I noticed that you put a link to Kyle Luce's video tutorial in the README.md, and I was wondering if you'd be willing to put a link to my video tutorial series as well?
The first part is up and it covers using this image for exporting to Windows, Linux, Windows and HTML5, and deploying to GitLab Pages. Future parts will cover deploying to Itch.io (and other places), more advanced exports (ex. Android) and using custom builds of Godot.
Anyway, thanks again for your work on this project! I'd love to chat sometime via email or Discord or whatever. :-)

Thanks for the tutorials! :)


Unused import is not reported, when there is companion object with the same name

In AS:
reported:

Usage like: Log.e(TAG, "bla bla")
companion object takes precedence
   companion object {
        const val TAG = "MyTag"
    }

This issue can not be reproduced. I have tried with lots of olds version (back until 0.34.0) as well.


[PowerShell][Request] Allow for retry on certain failures

In AzureStack we have some operations on our operator side which can result in service migration.  During this migration the client might see an error which results in a broken connection.  For some operator operations we don't have a way to resume monitoring: update, repair node, etc.
We would like a way to provide customization so that if certain cmdlets see an exception it can wait some period of time and try again.  Currently, the C# SDK has hard coded a similar solution that allows them to handle specific error codes for older APIs.
Do you think it could be possible to expose a set of Funcs (Func<HttpResonseMessage, bool>) for each operations, POST, GET, DELETE, etc... where given a specific HttpResponseMessage it would return true when the client should retry, false when it should fail?

@fearthecowboy This is for specific cmdlets I believe.  Usually related cmdlets which might cause a service to migrate to another node which would cause a blip and the cmdlet to fail.  I don't think it would hurt to add it for an entire module though.  I will need to reach out to the team that asked for this, we had a re-org and I need to find out who owns this now.

Hopefully it's ok for all, if its not, I'm pretty sure I can give you another alternative that tweaks the pipeline on a per-cmdlet basis; the only downside is that you'd have to implement tiny partial class for each one.
It's also possible I could craft a directive you could use.
G

@fearthecowboy  I can't imagine anything bad can happen.  But, that is how bugs happen I guess lol.
Too bad we can provide a class that allows us to Inherit from your class where we can define a method that you call after you add all the default handlers i.e
public async System.Threading.Tasks.Task<System.Net.Http.HttpResponseMessage> FinalHandler( System.Net.Http.HttpRequestMessage requestMessage, Runtime.IEventListener listener, Runtime.ISendAsync next );

That's actually not too hard to implement -- generated cmdlets only inherit from  PSCmdlet -- we don't force a weird base class.
Would be a small directive to alter the inheritance on a subset of cmdlets so you could make a class inherit from PSCmdlet and the generated cmdlets could inherit from that.
I was thinking of that ; just want to see if a partial method in a child class can be fulfilled by a base class.

@fearthecowboy What would the tag thing entail?  Could we provide something in the spec itself?  Something like x-ms-failover-aware?


bug(cdk/overlay): Overlay not updating position on scroll

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
12.2.13
Description
When using a overlay with scroll strategy set RepositionScrollStrategy, position of a overlay is not updaring while scrolling.
Reproduction
Steps to reproduce:

This bug is present in official documentation, as example https://material.angular.io/cdk/overlay/examples

Expected Behavior
In previous version of documentation overlay is working as it should https://v12.material.angular.io/cdk/overlay/examples
Actual Behavior
https://material.angular.io/cdk/overlay/examples
Environment

Angular: 13.3.5
CDK/Material: 13.3.5
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

This is an issue with the docs, not the overlay. The scrollable container isn't registered as being a cdkScrollable so the overlay doesn't know that it's supposed to update.


Update config.yml

Update to 20230312 to include the fixes for flaky tests introduced by dynamo
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

@frank-wei any idea why the CI cant pull the new build?

The new Torch version may also need to be added to py/requirements.txt

The new Torch version may also need to be added to py/requirements.txt + tests/modules/requirements.txt. Also it seems that as of Mar 2, the versions on https://download.pytorch.org/whl/nightly/torch/ have switched to version 2.1.0, instead of 2.0.0.

yes, it looks like changed to 2.1 as  torch-2.1.0.dev20230314


add the library to my project

Sorry I'm starting to program on android and I don't know how to add the library to my project. The IDE says me that "compile" is obsolete when I add the dependency. I should use implementation but when I use it, it gives me this error:
ERROR: Failed to resolve: agency.tango
Affected Modules: app
these are my dependencies:
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:28.0.0'
implementation 'com.android.support.constraint:constraint-layout:1.1.3'
implementation 'agency.tango.android:material-intro-screen:{latest_release}'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
}
Sorry, I'm starting to program on Android and I do not know how to add the library to my project. The IDE says that "compile" is obsolete when I add dependency. I should use the implementation, but when I use it, I get this error:
ERROR: Error in resolving: agency.tango
Modules affected: application
These are my dependencies:
dependencies {
implementation fileTree (dir: 'libs', includes: ['* .jar'])
implementation 'com.android.support:appcompat-v7:28.0.0'
implementation 'com.android.support.constraint: design-restriction: 1.1.3'
** implementation 'agency.tango.android:material-intro-screen:{latest_release}'**
Implementation 'junit: junit: 4.12'
androidTestImplementation 'com.android.support.test: runner: 1.0.2'
androidTestImplementation 'com.android.support.test.espresso: espresso-core: 3.0.2'
}
Do I have to add something else?

ok I think was for {lates release}, I didn't see it sorry. But now I have problem with versions.

Does it work for android 8 or 9?

Yes


fix: translation de

Description
Small translation error corrected

Fixes # (issue)
Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made changes in the CHANGELOG.md file

:+1: Thank you so much for your contribution!


Upgrading home page

Here is an updated version. @GoRedbirds what do you think?

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Could you put this on codecademy?
On Fri, Mar 24, 2017 at 1:30 PM, Steven Copeland<EMAIL_ADDRESS>wrote:

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions
resolved, some commit checks failed.
Comments from Reviewable
https://reviewable.io:443/reviews/stevencopeland/stores/43
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/StevenCopeland/Stores/pull/43#issuecomment-289089864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYAvcZgXE-CoTMqvKFaBnBupmEFPHymbks5ro_3MgaJpZM4MojLe
.

Okay!

Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

begin_round_four.js, line 38 at r1 (raw file):
Previously, codacy-bot (Codacy Bot) wrote…
 Issue found: 'other' is not defined. (no-undef)

Done.

Comments from Reviewable

Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

begin_round_for_3_players.js, line 67 at r1 (raw file):
Previously, codacy-bot (Codacy Bot) wrote…
 Issue found: 'other' is not defined. (no-undef)

Done.

begin_round_number_two.js, line 69 at r1 (raw file):
Previously, codacy-bot (Codacy Bot) wrote…
 Issue found: 'other' is not defined. (no-undef)

Done.

JavaScript-Files/jQuery.js, line 4 at r1 (raw file):
Previously, codacy-bot (Codacy Bot) wrote…
 Issue found: The function hide can be unsafe (scanjs-rules/call_hide)

Done.

JavaScript-Files/jQuery.js, line 6 at r1 (raw file):
Previously, codacy-bot (Codacy Bot) wrote…
 Issue found: The function hide can be unsafe (scanjs-rules/call_hide)

Done.

Comments from Reviewable

Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

begin_round_four.js, line 38 at r1 (raw file):

one

Comments from Reviewable

Reviewed 1 of 6 files at r1.
Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

Comments from Reviewable

@GoRedbirds I am closing this and deleting this branch.


sudo is missing in the dockers .....

usually when we try to execute occ as root the suggestion is to run it with sudo

@tboerger

No sudo within docker containers, you are already root.

Anyway you don't need to execute occ as webserver user anymore, right? Yesterday I did an 'occ upgrade' within docker and that went flawlessly.

No sudo within docker containers, you are already root.

its not about getting root but switch the user to www-data.
while there are multiple ways of switching the user our suggestion in occ is to use sudo.
from an ux pov its bad to suggest sudo and not provide sudo ...

Somebody forgot to add the info about the occ wrapper to this readme: https://github.com/owncloud-docker/server/blob/master/README.md#commandline-commands

Anyway you don't need to execute occ as webserver user anymore, right?

you need to - e.g. when touching files it is necessary to do this as www-data

You don't need sudo for that, just execute occ from the path (without ./ in front of it)


Preserving gradients with copy()?

Does the copy() tensor method maintain a gradient back to the source tensor?
I have a tensor that I need to send to multiple Modules and used copy() to achieve the duplication. Might this cause issues with the gradient or is there a better way to do this?
Also, I intend to use trainable_variables() on my VarStore to loop through the parameters and compute a regularization loss. Might this be problematic and is there a better way to do this?

copy uses PyTorch copy_ operator behind the hood and from a quick experiment on the python side this seems to properly propagate the gradient through. Did you try it out in rust and that wasn't the case?
>>> t = torch.tensor([0.1], requires_grad=True)
>>> u = torch.tensor([0.])
>>> u.copy_(t + 1)
tensor([1.1000], grad_fn=<CopyBackwards>)
>>> u.backward()
>>> t.grad
tensor([1.])

Re iterating on the trainable variables, this sounds perfectly fine, weight decay is already handled by most optimizers if that's what you're after but for another regularization loss that would probably be the way to go.


[FEATURE] : Adding animeted Pre Loader

Feature Description
The new feature is an animated preloader that would display while the website is loading its contents. The preloader would help enhance user experience by providing a smooth and visually appealing loading indicator before the main content of the site is fully rendered.
Use Case

Initial Load Times: Users might experience slight delays due to larger assets or slow networks. The preloader would fill this gap, making the waiting time feel more fluid and professional.
First-Time Users: First-time users of the site may have slower load times as assets like images and scripts are fetched for the first time. The preloader would reassure them that content is being loaded.

Benefits

Improved User Experience: Users won’t be left staring at a blank screen during loading times, which could otherwise lead to frustration or abandonment.
Enhanced Aesthetics: An animated preloader can add a professional touch, maintaining user engagement with an interesting visual instead of a plain loading bar.
Branding Opportunity: The preloader animation can incorporate elements of the website’s branding, such as its logo or color palette, helping to reinforce brand identity.

Add ScreenShots
Below one is sample video
https://github.com/user-attachments/assets/ab4e1fc8-54e5-4c2f-b58a-db67299b32af

@gauravsingh1281 Sir please assign this issue to me too

Can you assign me this issue?


Use new Console REST API for peer register and unregister

Now CC uses following REST API for peer register and unregister.
Because following REST API is deprecated.
/rest/v1/hub/unregister?sptoken=
/rest/v1/hub/register?sptoken=

We should use new Console REST API:
/rest/v1/bazaar/unregister?sptoken=
/rest/v1/bazaar/register?sptoken=

Successfully registered a peer
Fixed in master

Fixed in prod.


App Background Transparency

clearColor with alpha value to 0 (transparent) in settings.json is rendered obsolete due to the background: black; property being set at:

fixtures/dist/index.es5.html
fixtures/dist/index.es6.html

proposed fix in the following pull request #72

Thanks! Merged into dev-branch, will be published to master in a next release.


Add command line option to indicate whether sveltos-agent is running in the management or managed cluster

sveltos-agent must support being deployed:

in the managed cluster (this is current and should remain default behaviour)
in the management cluster

A new command line option is needed to tell sveltos-agent where it is deployed.
When running in the management cluster, should use the GetKubernetesRestConfig to get rest.Config to access managed cluster and use that one.
Sveltos-agent is already passed cluster info (namespace, name, cluster-type). Those info are required by GetKubernetesRestConfig.
Doing so require to grant sveltos-agent Secret read permission in the management cluster. Maybe another option would be to pass the Kubeconfig to access the managed cluster directly (as Classifier already has such permission).
When sveltos-agent is started in the management cluster, the run-mode option can only be set to "do-not-send-reports"
Meaning events and reports will be fetched by classifier (which is default behaviour).

Probably we could create a different YAML for what is needed to install sveltos-agent in the management cluster. This could end in the manifest directory. At build build time classifier can incorporate it (same as it does for current manifest today), and then use that one to deploy sveltos-agent in the management cluster.


Snake Game in JAVA

Describe the project you want to add with tech stack
Designing a typical Snake game with the help of java.awt and java.swing package.

Expected behavior
The game will keep incrementing the score as the snakes keeps on consuming the powerup and displays game over message when the snake strikes the boundaries or strikes itself.

Screenshots (optional)

@pranjay-poddar Request you to assign this issue to me under hactoberfest 2022

hey @pranjay-poddar, I want to contribute to this issue. can you please assign this to me?

Hey @pranjay-poddar , I would like to  contribute to this issue.

@pranjay-poddar wow bro..pathetic

@pranjay-poddar wow bro..pathetic

@flow6979 there's nothing pathetic, this issue is not opened by you and it is already assigned so someone else.


[path_provider] Breaking change in test mocks

Steps to Reproduce

Git clone https://github.com/flutter/plugins/tree/main/packages/path_provider/path_provider
run flutter test

Expected results: All tests pass
Actual results: All tests fails due
path_provider % flutter test
Running "flutter pub get" in path_provider...                      796ms
00:08 +0 -1: PathProvider full implementation getTemporaryDirectory [E]
  UnimplementedError: _instanceToken
  package:test_api                                                                      Fake.noSuchMethod
  package:plugin_platform_interface/plugin_platform_interface.dart 49:17                FakePathProviderPlatform._instanceToken
  package:plugin_platform_interface/plugin_platform_interface.dart 63:28                PlatformInterface.verify
  package:path_provider_platform_interface/path_provider_platform_interface.dart 35:23  PathProviderPlatform.instance=
  test/path_provider_test.dart 25:28                                                    main.<fn>.<fn>
  test/path_provider_test.dart 24:11                                                    main.<fn>.<fn>

Failure occurs only with path_provider_platform_interface release 2.0.2 (9 hours ago). Probably caused by https://github.com/flutter/plugins/pull/4643.
For reference https://pub.dev/packages/path_provider#usage-in-tests
Workaround
Lock path_provider_platform_interface to 2.0.1 in pubspec.yaml.

/cc @stuartmorgan

This has already been fixed (in plugin_platform_interface 2.1.1).


"Manoleasa", "Bold" and "Flondora" are listed in the drop-down menu

Description:
"Manoleasa", "Bold" and "Flondora" are is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Manoleasa" in the search bar.

Expected results
The location is listed in the drop-down menu as "Manoleasa, Botoșani (Manoleasa)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Bold" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bold, Botoșani (Manoleasa)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Flondora" in the search bar.

Expected results
The location is listed in the drop-down menu as "Flondora, Botoșani (Manoleasa)".


feat: Update “download datasets” copy URL (#5589)

Reason for Change

#5589
https://github.com/chanzuckerberg/single-cell-data-portal/issues/5586

Changes

Modified download datasets copy URL.
Modified download datasets copy caption text as per mocks to include a link to the schema and Discover API.
Schema URL is updated to https://github.com/chanzuckerberg/single-cell-curation/blob/main/schema/3.1.0/schema.md as per slack thread.

My cursory assessment is that the FE is still calling this endpoint which (still) generates a presigned url.

My cursory assessment is that the FE is still calling this endpoint which (still) generates a presigned url.
Copying from #5589:

Currently, a request is sent to create and retrieve a pre-signed URL. The generated pre-signed URL is no longer required; the URL is to be assembled by the frontend from the dataset version ID.

Hi @danieljhegeman, we changed the approach on how the permanent URL should be generated but it looks like I didn't update the "need" section of the corresponding ticket. I have just made that update.
The update to call the new endpoint is here.
The existing POST endpoint will be cleaned up in this ticket.

The update to call the new endpoint is here.

This is not a new endpoint, as you allude to in a subsequent comment. It is the same endpoint, just a different method, right?

Hi @danieljhegeman, we changed the approach on how the permanent URL should be generated but it looks like I didn't update the "need" section of the corresponding ticket. I have just made that update.

Can you say a bit more about this?

The update to call the new endpoint is here.

This is not a new endpoint, as you allude to in a subsequent comment. It is the same endpoint, just a different method, right?

Ah, I see! Yes, we added a GET method to /datasets/datasetId/asset/assetId in this PR, specifically here.
The existing POST method (e.g. here) will be removed with Remove Data Portal pre-signed asset URL capability once this PR lands.

Can you say a bit more about this?

Originally the approach was to generate the link to the permanent URL on the FE and deprecate the existing POST method. During our weekly call on September 13, (@frano-m and) I raised the issue that we need to display a file size in the download modal which is currently provided to the FE via the soon-to-be-deprecated POST endpoint. @ebezzi suggested we create a new GET method to return both the permanent URL (as we could then re-use the logic used by the curator API) and the file size.
@danieljhegeman, let me know if this isn't clear or if you have any more q's!

The update to call the new endpoint is here.

This is not a new endpoint, as you allude to in a subsequent comment. It is the same endpoint, just a different method, right?

Ah, I see! Yes, we added a GET method to /datasets/datasetId/asset/assetId in this PR, specifically here.
The existing POST method (e.g. here) will be removed with Remove Data Portal pre-signed asset URL capability once this PR lands.

Can you say a bit more about this?

Originally the approach was to generate the link to the permanent URL on the FE and deprecate the existing POST method. During our weekly call on September 13, (@frano-m and) I raised the issue that we need to display a file size in the download modal which is currently provided to the FE via the soon-to-be-deprecated POST endpoint. @ebezzi suggested we create a new GET method to return both the permanent URL (as we could then re-use the logic used by the curator API) and the file size.
@danieljhegeman, let me know if this isn't clear or if you have any more q's!

Thanks @MillenniumFalconMechanic . I think this work just came in / is coming in more piecemeal than I might've expected, but all the same in terms of the end goal. Thanks for confirming!


what batch_size do you use for neural models

Hi, I wonder what batch_size do you use for each neural model? It is really hard to reproduce results in Table 3 without knowing this parameter...

Hi @ShellingFord221
We did not tune learning rate or batch size specifically, please use the default setting in the args (lr=1.0 and using decay, batch size=64)
We tuned the dropout for each task and model. Please try the following settings and let me know if you have further questions.
KBP BiGRU: input_dropout 0.5, intra_dropout 0.1, output_dropout 0.6
KBP BiLSTM: input_dropout 0.5, intra_dropout 0.2, output_dropout 0.8
KBP PA-LSTM: input_dropout 0.5, intra_dropout 0.1, output_dropout 0.5
KBP PCNN: dropout 0.2
KBP CNN: dropout 0.3
NYT BiGRU: input_dropour 0.5, intra_dropout 0.3, output_dropout 0.5
NYT BiLSTM: input_dropout 0.4, intra_dropout 0.3, output_dropout 0.7
NYT PA-LSTM: input_dropout 0.5, intra_dropout 0.3, output_dropout 0.7
NYT PCNN: dropout 0.2
NYT CNN: dropout 0.2
TACRED BiGRU: input_dropout 0.6, intra_dropout 0.1, output_dropout 0.6
TACRED BiLSTM: input_dropout 0.7, intra_dropout 0.1, output_dropout 0.7
TACRED PA-LSTM: input_dropout 0.7, intra_dropout 0.3, output_dropout 0.6
TACRED PCNN: dropout 0.4
TACRED CNN: dropout 0.3
cc: @Milozms

Hi, I tried parameters recommended above. Here are the results of CNN_KBP:
Original 27.35±1.42
Max-thres 31.20±2.04
Entropy-thres 32.18±2.39
BA-Set 28.97±0.75
It seems that the results of Original and BA-Set are a little bit worse than the results reported in Table 3. Here is my command:
python Neural/train.py --model cnn --data_dir data/neural/KBP --hidden 230 --lr 1.0 --in_drop 0.3 --info cnn_kbp --repeat 5
Thanks!

I also tried PCNN_KBP with dropout 0.2:
Original 27.92±1.10
Max-thres 31.28±2.10
Entropy-thres 32.74±3.28
BA-Set 30.26±1.10
Similarly, Original and BA-Set are a little bit worse than the results reported in Table 3.

Hi @ShellingFord221
Could you please try adding --lower in the command for cnn/pcnn models?

Hi, I try the following command, and here is what I get:
python Neural/train.py --model cnn --data_dir data/neural/KBP --hidden 230 --lower --lr 1.0 --in_drop 0.3 --info cnn_kbp --repeat 5
Original 26.25±2.08
Max-thres 30.16±3.21
Entropy-thres 31.71±3.49
BA-Set 29.64±3.38
It seems that Original is getting worse ... Here are all my parameters:
Namespace(attn_dim=200, batch_size=64, bias=True, bidirectional=True, cpu=False, cuda=True, data_dir='data/neural/KBP', emb_dim=300, fix_bias=False, hidden=230, in_drop=0.3, info='cnn_kbp', intra_drop=0.1, lower=True, lr=1.0, lr_decay=0.9, mask_with_type=True, max_grad_norm=5.0, model='cnn', ner_dim=30, num_epoch=30, num_layers=2, out_drop=0.6, pos_dim=30, position_dim=30, repeat=5, save_dir='./dumped_models', seed=7698, state_drop=0.5, vocab_dir='data/neural/vocab', vocab_size=33826, window_size=3)
Thank you so much!!

Hi @ShellingFord221
Please try --lr_decay 0.1, this should solve the problem, and I should have made 0.1 the default value in the code.
python Neural/train.py --model cnn --data_dir data/neural/KBP --hidden 230 --lr 1.0 --lr_decay 0.1 --dropout 0.3 --info cnn_kbp --repeat 5 --lower
python Neural/train.py --model pcnn --data_dir data/neural/KBP --hidden 230 --lr 1.0 --lr_decay 0.1 --dropout 0.2 --info pcnn_kbp --repeat 5 --lower

Thanks for bringing up this issue!

Hi, I tried all the recommended parameters, PCNN, Bi-GRU, and Bi-LSTM all achieve the desired performance. However, set_bias method of CNN seems underperform the original model on KBP:
original: 30.48
set_bias: 0.2817
fix_bias: 0.3519
Also, when I tried to train pa_lstm on NYT, there is an error:

I can successfully train pa_lstm on KBP, but I don't know why the error rises on NYT.
Thanks!


Default JSON payloads to {} when JSON is selected

When creating a new action that doesn't require a payload, for example a get or an example, the UI is still expecting a {} in the payload or you can not add the action but the user doesn't get any information about the mandatory field

Can you please describe how you implemented this task? I can not find an explicit commit.


Merge nzst::* and zsty::* into fat::*?

Motivating example:
let u32 = ABox::new_in(42_u32, Malloc);
let zst = ABox::new_in((),     Malloc);

It would be nice if the former compiled while the latter didn't.  This cannot be particularly well accomplished by separating nzst::* from zsty::*.  For another example, these should both compile:
let u32 = ABox::new_in(42_u32, DangleZst(Malloc));
let zst = ABox::new_in((),     DangleZst(Malloc));

TODO

[x] Widen thin to accept usize
[x] Reimpl everything in terms of zsty
[x] Drop nzst
[x] Rename nzst -> fat
[x] ABox ZST support assertions

c781389 ABox: ZST checks


ld: library not found for -lPods

ld: library not found for -lPods
clang: error: linker command failed with exit code 1 (use -v to see invocation)
It should not include any third party stuff in compiler if you don't have the code.

Do you open the project with .xcworkspace?

hi jamztang,
i am also facing same kind of error.I just opened my project wit workspace.


the api not work

When I try to use my self-hosted One-Time Secret API on the GLPI plugin, I get these errors:
[11/Apr/2024:15:24:05 +0200] "GET /img/favicon.png HTTP/1.1" 200 189 0.0036
2024-04-11 15:25:14 +0200 Invalid request: Invalid HTTP format, parsing fails.
/var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/request.rb:86:in execute' /var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/request.rb:86:in parse'
/var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/connection.rb:39:in receive_data' /var/lib/gems/3.0.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:195:in run_machine'
/var/lib/gems/3.0.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:195:in run' /var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/backends/base.rb:75:in start'
/var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/server.rb:162:in start' /var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/controllers/controller.rb:87:in start'
/var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/runner.rb:203:in run_command' /var/lib/gems/3.0.0/gems/thin-1.8.2/lib/thin/runner.rb:159:in run!'
/var/lib/gems/3.0.0/gems/thin-1.8.2/bin/thin:6:in <top (required)>' /usr/local/bin/thin:25:in load'
/usr/local/bin/thin:25:in `'
Can someone help me ?

Yes, I’ll take a look.

Thank you! I host my GLPI on the same machine as One Time Secret, yet when I use the API from the One Time Secret site, it works. However, ultimately, I would like to have both locally.
For One Time Secret, I left the configuration at default

Thank you! I host my GLPI on the same machine as One Time Secret, yet when I use the API from the One Time Secret site, it works. However, ultimately, I would like to have both locally.

Nice, yeah that sounds like great setup.
Do you have a web server / proxy running on that machine as well? Something like Nginx, Caddy, HAProxy etc.

I have nothing else except for One Time Secret and GLPI on this VM.

Kk, I got it sorted out. The issue you're having is related to SSL/HTTPS.
The Onetime Secret ruby app doesn't handle SSL itself. So when making a request for https://myexampledomain.com/ (or https://myexampledomain.com:3000), that's how you get the error you're seeing.
2024-04-11 08:23:05 -0700 Invalid request: Invalid HTTP format, parsing fails.
	/Users/d/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/thin-1.8.2/lib/thin/request.rb:86:in `execute'
  ...

Running a reverse proxy
The solution is to use a reverse proxy to handle the SSL termination. This is a common pattern in web applications. The reverse proxy is responsible for handling the SSL connection and then forwarding the request to the application server (in this case, the Onetime Secret app).
Thin supports SSL itself so that's one option (see this gist). An easier option is to use Caddy as a reverse proxy. Here's a simple Caddyfile that you can use to get started:
##
# Caddy 2 Configuration - One time secret
#
# Usage:
#
#   $ caddy run --config Caddyfile
#

https://myexampledomain.com {
   reverse_proxy localhost:3000
   log {
       output stdout
   }
   header X-Content-Type-Options nosniff
   header X-Frame-Options SAMEORIGIN
   header Referrer-Policy no-referrer-when-downgrade
}

Most importantly, Caddy automatically handles all of the SSL details for you (including generating the certificates). You can run Caddy as a service or in a container.
Installing Caddy
The official instructions are great and should have details for whichever kind of system you run:
https://caddyserver.com/docs/install.
Or in a nutshell, manually installing goes like this:
# Download and install Caddy
curl -o caddy.tar.gz "https://caddyserver.com/api/download?os=linux&arch=amd64&idempotency=1234567890123"
tar xvf caddy.tar.gz
sudo mv caddy /usr/local/bin/

# Save your Caddyfile configuration to a file
cat << EOF > Caddyfile
https://myexampledomain.com {
    reverse_proxy localhost:3000
    log {
        output stdout
    }
    header X-Content-Type-Options nosniff
    header X-Frame-Options SAMEORIGIN
    header Referrer-Policy no-referrer-when-downgrade
}
EOF

# Run Caddy with your configuration
caddy run --config Caddyfile --adapter caddyfile

With that, you'll be able to access your Onetime Secret app over HTTPS at https://myexampledomain.com (or whatever domain you're using).

Hey @delano
will it be possible to have a flag to ignore SSL/HTTPS verification for dev testing?
I tried to modify this:
ONETIMESECRET_SSL="true" to ONETIMESECRET_SSL="false" in the .env file and I got:
ERROR: for app  'ContainerConfig'
Traceback (most recent call last):
  File "/usr/bin/docker-compose", line 33, in <module>
    sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts', 'docker-compose')())
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 81, in main
    command_func()
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 203, in perform_command
    handler(command, command_options)
  File "/usr/lib/python3/dist-packages/compose/metrics/decorator.py", line 18, in wrapper
    result = fn(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 1186, in up
    to_attach = up(False)
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 1166, in up
    return self.project.up(
  File "/usr/lib/python3/dist-packages/compose/project.py", line 697, in up
    results, errors = parallel.parallel_execute(
  File "/usr/lib/python3/dist-packages/compose/parallel.py", line 108, in parallel_execute
    raise error_to_reraise
  File "/usr/lib/python3/dist-packages/compose/parallel.py", line 206, in producer
    result = func(obj)
  File "/usr/lib/python3/dist-packages/compose/project.py", line 679, in do
    return service.execute_convergence_plan(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 579, in execute_convergence_plan
    return self._execute_convergence_recreate(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 499, in _execute_convergence_recreate
    containers, errors = parallel_execute(
  File "/usr/lib/python3/dist-packages/compose/parallel.py", line 108, in parallel_execute
    raise error_to_reraise
  File "/usr/lib/python3/dist-packages/compose/parallel.py", line 206, in producer
    result = func(obj)
  File "/usr/lib/python3/dist-packages/compose/service.py", line 494, in recreate
    return self.recreate_container(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 612, in recreate_container
    new_container = self.create_container(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 330, in create_container
    container_options = self._get_container_create_options(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 921, in _get_container_create_options
    container_options, override_options = self._build_container_volume_options(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 960, in _build_container_volume_options
    binds, affinity = merge_volume_bindings(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 1548, in merge_volume_bindings
    old_volumes, old_mounts = get_container_data_volumes(
  File "/usr/lib/python3/dist-packages/compose/service.py", line 1579, in get_container_data_volumes
    container.image_config['ContainerConfig'].get('Volumes') or {}
KeyError: 'ContainerConfig'

You're on the right track. ONETIMESECRET_SSL and ONETIMESECRET_HOST are the environment variables you need to set. e.g. the equivalent settings in the etc/config file:
:site:
  :host: localhost:3000
  :ssl: false

The error KeyError: 'ContainerConfig' is coming from the docker python library and possibly to do with its own docker compose configuration.