Feature click listener triggers an info window for feature marker.

https://github.com/googlemaps/android-maps-utils/blob/master/library/src/com/google/maps/android/data/Layer.java#L118
I notice that the method setOnMarkerClickListener() returns true. This is probably why I get info window opened when feature is clicked. I would like to avoid this info window.

@uburoiubu When testing on the master branch using the MultiLayerDemoActivity, I don't see any info windows for KML or GeoJSON polylines or polygons. The marker info window appears if the title is set like this:
MarkerManager.Collection markerCollection = markerManager.newCollection();
markerCollection.addMarker(new MarkerOptions()
		.position(new LatLng( 51.150000, -0.150032))
		.title("My marker"));

...but if you don't set the title then no info windows appears:
MarkerManager.Collection markerCollection = markerManager.newCollection();
markerCollection.addMarker(new MarkerOptions()
		.position(new LatLng( 51.150000, -0.150032)));

Could you please check out the latest version of the library and re-open if you're still having issues?  Thanks!


On version 1.3.0 shadows of blocks on notifications is rendering weirdly.

On 1.2.4 it is normal

Nice catch! Fixed in 1.3.1!


Add Expire Timestamp and Related Information

This PR is definitely not ready to be merged; I just wanted to let you see where I was going to see if you have any issues, recommendations, etc. with my approach...and to ask for some specific help, hopefully just a second set of eyes that will quickly notice something amiss.
I already have things working well enough to use for my personal pet Rust project since my main KeePass db is still 3.1 format which is working as expected, illustrated in tests/entry_tests.rs; but, I have been stuck trying to figure out how to convert kdbx4 time nodes into something useful.  My new kdbx4_entry fn in tests/entry_tests.rs illustrates where I am stuck:
e.times.get_time("ExpiryTime") contains the raw XML character string for this node pulled from parse_xml_block.  (This is working fine for getting human readable results from kdbx3 files but not so with kdbx4 files.)
I tried converting this kdbx4 field from the Base64 encoded entry as follows; this code is currently in my new get_time() in db.rs:

Get vec of u8 digits representing the Base64 digits using base64::decode which is already being used elsewhere in the module.
Multiply out the vec digits to get a u64 (normal base 10 integer) representation of this value.

I had assumed this would give me the number of seconds elapsed since 0001-01-01 00:00 UTC as documented at the bottom of the KDBX 4 release page.  But, the number of seconds I am calculating is a couple of orders of magnitude smaller than the EpochConverter page says I should be seeing.
I did glance through the KeePassXC code to see how they are handling this; but, at first glance, it looks to me like they may just be handing off the conversion work to a QT library.  However, it is very possible I lost may way in that code; it has probably been 25 years since I wrote any C++.
If nothing jumps out at you, please don't feel like you have to spend a lot of time helping me with this.  I am actually hoping you will quickly see something that I have been staring at and missing, or completely misunderstanding, for the last few days.  If not, I can keep digging on my own.
Note:  My approach to handling ExpiryTime is a bit different than I had originally planned; but, I think this approach lays the groundwork for easily and consistently handling all time time fields from the KeePass XML.  If you are good with this approach (once it is actually working), I will do the same for all custom data fields; currently, I just have enough code in place to pull out the db_report_exclude flag that I need.

@sseemayer or anyone willing to help me out:
I am not sure if I am missing something fundamental or have just made an obvious mistake that I am just not seeing.
I have run the following code for all possible values of c.  The combinations that return Ok() produce one of the following values of d:
291529854
861071171194951
141427661638534
The EpochConverter site indicates I should be seeing something on the order of 6xxxxxxxxxx for the number of seconds after 0001-01-01, "/s4D2A4AAAA=" representing April 10, 2021 in the test_db_kdbx4_with_password_aes.kdbx file's XML.
use std::convert::TryFrom;

fn f(c: base64::Config) {
    match ::base64::decode_config("/s4D2A4AAAA=".as_bytes().to_vec(), c) {
        Ok(v) => {
            let mut d: u64 = 0;
            let b: u64 = 64;
            for (i, e) in v.iter().enumerate() {
                d += u64::pow(b, u32::try_from(i).unwrap())
                    * u64::try_from(*e).unwrap();
            }
            println!("d = {} for v = {:?} from c = {:?}", d, v, c)
        }
        z => println!("c = {:?} fails with {:?}", c, z)
    }
}

I think I have finally figured out how to get a u64 from the Base64 encoded integer; so, I am pulling this PR while I clean up my code and test.


feat: add news plugin

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: xiaohai-78:x: xiaoyuntaoxiaoyuntao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

done


By default run the PhEDEx emulator

test this please

test this please

@ericvaandering it seems this PR needs to be rebased

test this please

DBS failures are real including some others in DBS testing. Will have to fix these.

Test this please

test this please

Should work fine now, want to rewrite the history of these commits once it is, though.

I don't understand testListFileBlockLocation. It succeeds in my tests. Will investigate.

test this please

test this please

test this please

Ok @ticoann , this is good to merge. Still learning how mock works.

@amaltaro since you are the new sheriff in town, when do you plan to merge this? :-)

Since it does not affect cmsweb services, I'm merging it now. Thanks Eric!


Update to polkadot-0.9.16

Closes: #26

Verified this PR fixes all my issues!

https://github.com/paritytech/polkadot/pull/4320/files#diff-6dcbafad4c91afb2c91f5b01429549242a45a3bb0de721c830abd0a61421ae3aR1056


rm table wrapper div that breaks integration tests

For some reason, when the table is wrapped in a div, it will not be rendered by Cypress' browser until you explicitly set the correct height on that wrapper div.
Using a Fragment instead of a DOM node will also fix this issue.

@GeorgiSTodorov - it should be there now 👍


Add Illuminance type and device

Done

matter 0.3.2
Tested virtual "Dimmer" as a device which was connected with google home and had no problems.

(but dimer !== illuminance ...  :-) das wäre ein Brighness sensor

:-)
Illuminane is also working
tested with matter 0.3.2


Rethink FAQ

Given the new bundled macros #154 #155, a lot of the FAQ is looking pretty dated. It's also not from actually-asked questions, but anticipated ones. Maybe it's time to get rid of it. A few of them did end up getting asked in the chat room though. It was nice to be able to link to them. The old doc versions are still available though.
Given GitHub's Discussions feature, we probably don't need to keep this part in the Sphinx docs, although those do have the advantage (and disadvantage) of Sybil testing.
There are some valuable tips in there that aren't anywhere else. Those can maybe be converted to their own section or moved to the wiki.

Deleted FAQ in #158. I can still point to an older version of the docs if necessary, I just won't be maintaining it anymore. I'll probably look over it again in my next doc edit pass to see if anything should be moved.

I'm thinking of making a "cookbook" section in the docs with how-tos. That's what a lot of the old FAQ was.


create plan occurs without create

if you canx out of create plan, it remains
CAM version 1.1.1

Turns out this is not an easy problem to solve due to some details with the way that the migration k8s API works. This deserves more thought than simply deleting the plan.


TypeError: crypto.createHmac is not a function

I tried to use jsonwebtoken in Angular 2 get the EXCEPTION below
My Code
import * as jwt from 'jsonwebtoken';

ngOnInit() {
        var token = jwt.sign({ foo: 'bar' }, 'mySecretKey');
        var older_token = jwt.sign({ foo: 'bar', iat: Math.floor(Date.now() / 1000) - 30 }, 'mySecretKey')
    }

source
ERROR
EXCEPTION: Uncaught (in promise): Error: Error in :0:0 caused by: crypto.createHmac is not a function
TypeError: crypto.createHmac is not a function
    at Object.sign (webpack-internal:///../../../../jwa/index.js:34:23)
    at Object.jwsSign [as sign] (webpack-internal:///../../../../jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (webpack-internal:///../../../../jsonwebtoken/sign.js:186:16)
    at CheckIMEIStatusComponent.ngOnInit (webpack-internal:///../../../../../src/app/components/check-imei-status/check-imei-status.component.ts:26:25)
    at Wrapper_CheckIMEIStatusComponent.ngDoCheck (/ComponentsModule/CheckIMEIStatusComponent/wrapper.ngfactory.js:22:53)
    at CompiledTemplate.proxyViewClass.View_CheckIMEIStatusComponent_Host0.detectChangesInternal (/ComponentsModule/CheckIMEIStatusComponent/host.ngfactory.js:28:38)
    at CompiledTemplate.proxyViewClass.AppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:438:14)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:633:44)
    at ViewRef_.detectChanges (webpack-internal:///../../../core/src/linker/view_ref.js:175:20)
    at RouterOutlet.activate (webpack-internal:///../../../router/src/directives/router_outlet.js:160:42)
    at ActivateRoutes.placeComponentIntoOutlet (webpack-internal:///../../../router/src/router.js:1359:16)
    at ActivateRoutes.activateRoutes (webpack-internal:///../../../router/src/router.js:1326:26)
    at eval (webpack-internal:///../../../router/src/router.js:1262:58)
    at Array.forEach (<anonymous>)
    at ActivateRoutes.activateChildRoutes (webpack-internal:///../../../router/src/router.js:1262:29)
ErrorHandler.handleError @ error_handler.js:54
next @ application_ref.js:348
schedulerFn @ async.js:93
SafeSubscriber.__tryOrUnsub @ Subscriber.js:234
SafeSubscriber.next @ Subscriber.js:183
Subscriber._next @ Subscriber.js:125
Subscriber.next @ Subscriber.js:89
Subject.next @ Subject.js:55
EventEmitter.emit @ async.js:79
NgZone.triggerError @ ng_zone.js:333
onHandleError @ ng_zone.js:294
ZoneDelegate.handleError @ zone.js:233
Zone.runGuarded @ zone.js:129
_loop_1 @ zone.js:416
drainMicroTaskQueue @ zone.js:425
Promise resolved (async)
scheduleQueueDrain @ zone.js:378
scheduleMicroTask @ zone.js:386
ZoneDelegate.scheduleTask @ zone.js:245
Zone.scheduleMicroTask @ zone.js:165
scheduleResolveOrReject @ zone.js:507
resolvePromise @ zone.js:470
(anonymous) @ zone.js:449
webpackJsonpCallback @ inline.bundle.js:22
(anonymous) @ components.module.chunk.js:1
error_handler.js:59 ORIGINAL STACKTRACE:
ErrorHandler.handleError @ error_handler.js:59
next @ application_ref.js:348
schedulerFn @ async.js:93
SafeSubscriber.__tryOrUnsub @ Subscriber.js:234
SafeSubscriber.next @ Subscriber.js:183
Subscriber._next @ Subscriber.js:125
Subscriber.next @ Subscriber.js:89
Subject.next @ Subject.js:55
EventEmitter.emit @ async.js:79
NgZone.triggerError @ ng_zone.js:333
onHandleError @ ng_zone.js:294
ZoneDelegate.handleError @ zone.js:233
Zone.runGuarded @ zone.js:129
_loop_1 @ zone.js:416
drainMicroTaskQueue @ zone.js:425
Promise resolved (async)
scheduleQueueDrain @ zone.js:378
scheduleMicroTask @ zone.js:386
ZoneDelegate.scheduleTask @ zone.js:245
Zone.scheduleMicroTask @ zone.js:165
scheduleResolveOrReject @ zone.js:507
resolvePromise @ zone.js:470
(anonymous) @ zone.js:449
webpackJsonpCallback @ inline.bundle.js:22
(anonymous) @ components.module.chunk.js:1
error_handler.js:60 Error: Uncaught (in promise): Error: Error in :0:0 caused by: crypto.createHmac is not a function
TypeError: crypto.createHmac is not a function
    at Object.sign (webpack-internal:///../../../../jwa/index.js:34:23)
    at Object.jwsSign [as sign] (webpack-internal:///../../../../jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (webpack-internal:///../../../../jsonwebtoken/sign.js:186:16)
    at CheckIMEIStatusComponent.ngOnInit (webpack-internal:///../../../../../src/app/components/check-imei-status/check-imei-status.component.ts:26:25)
    at Wrapper_CheckIMEIStatusComponent.ngDoCheck (/ComponentsModule/CheckIMEIStatusComponent/wrapper.ngfactory.js:22:53)
    at CompiledTemplate.proxyViewClass.View_CheckIMEIStatusComponent_Host0.detectChangesInternal (/ComponentsModule/CheckIMEIStatusComponent/host.ngfactory.js:28:38)
    at CompiledTemplate.proxyViewClass.AppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:438:14)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:633:44)
    at ViewRef_.detectChanges (webpack-internal:///../../../core/src/linker/view_ref.js:175:20)
    at RouterOutlet.activate (webpack-internal:///../../../router/src/directives/router_outlet.js:160:42)
    at ActivateRoutes.placeComponentIntoOutlet (webpack-internal:///../../../router/src/router.js:1359:16)
    at ActivateRoutes.activateRoutes (webpack-internal:///../../../router/src/router.js:1326:26)
    at eval (webpack-internal:///../../../router/src/router.js:1262:58)
    at Array.forEach (<anonymous>)
    at ActivateRoutes.activateChildRoutes (webpack-internal:///../../../router/src/router.js:1262:29)
    at resolvePromise (webpack-internal:///../../../../zone.js/dist/zone.js:475:31) [angular]
    at resolvePromise (webpack-internal:///../../../../zone.js/dist/zone.js:460:17) [angular]
    at eval (webpack-internal:///../../../../zone.js/dist/zone.js:509:17) [angular]
    at Object.onInvokeTask (webpack-internal:///../../../core/src/zone/ng_zone.js:266:37) [angular]
    at ZoneDelegate.invokeTask (webpack-internal:///../../../../zone.js/dist/zone.js:261:40) [angular]
    at Zone.runTask (webpack-internal:///../../../../zone.js/dist/zone.js:151:47) [<root> => angular]
    at drainMicroTaskQueue (webpack-internal:///../../../../zone.js/dist/zone.js:405:35) [<root>]
    at <anonymous> [<root>]
ErrorHandler.handleError @ error_handler.js:60
next @ application_ref.js:348
schedulerFn @ async.js:93
SafeSubscriber.__tryOrUnsub @ Subscriber.js:234
SafeSubscriber.next @ Subscriber.js:183
Subscriber._next @ Subscriber.js:125
Subscriber.next @ Subscriber.js:89
Subject.next @ Subject.js:55
EventEmitter.emit @ async.js:79
NgZone.triggerError @ ng_zone.js:333
onHandleError @ ng_zone.js:294
ZoneDelegate.handleError @ zone.js:233
Zone.runGuarded @ zone.js:129
_loop_1 @ zone.js:416
drainMicroTaskQueue @ zone.js:425
Promise resolved (async)
scheduleQueueDrain @ zone.js:378
scheduleMicroTask @ zone.js:386
ZoneDelegate.scheduleTask @ zone.js:245
Zone.scheduleMicroTask @ zone.js:165
scheduleResolveOrReject @ zone.js:507
resolvePromise @ zone.js:470
(anonymous) @ zone.js:449
webpackJsonpCallback @ inline.bundle.js:22
(anonymous) @ components.module.chunk.js:1
zone.js:392 Unhandled Promise rejection: Error in :0:0 caused by: crypto.createHmac is not a function ; Zone: angular ; Task: Promise.then ; Value: ViewWrappedError {_nativeError: Error: Error in :0:0 caused by: crypto.createHmac is not a function
    at ViewWrappedError.BaseErro…, originalError: TypeError: crypto.createHmac is not a function
    at Object.sign (webpack-internal:///../../../../j…, context: DebugContext} TypeError: crypto.createHmac is not a function
    at Object.sign (webpack-internal:///../../../../jwa/index.js:34:23)
    at Object.jwsSign [as sign] (webpack-internal:///../../../../jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (webpack-internal:///../../../../jsonwebtoken/sign.js:186:16)
    at CheckIMEIStatusComponent.ngOnInit (webpack-internal:///../../../../../src/app/components/check-imei-status/check-imei-status.component.ts:26:25)
    at Wrapper_CheckIMEIStatusComponent.ngDoCheck (/ComponentsModule/CheckIMEIStatusComponent/wrapper.ngfactory.js:22:53)
    at CompiledTemplate.proxyViewClass.View_CheckIMEIStatusComponent_Host0.detectChangesInternal (/ComponentsModule/CheckIMEIStatusComponent/host.ngfactory.js:28:38)
    at CompiledTemplate.proxyViewClass.AppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:438:14)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:633:44)
    at ViewRef_.detectChanges (webpack-internal:///../../../core/src/linker/view_ref.js:175:20)
    at RouterOutlet.activate (webpack-internal:///../../../router/src/directives/router_outlet.js:160:42)
    at ActivateRoutes.placeComponentIntoOutlet (webpack-internal:///../../../router/src/router.js:1359:16)
    at ActivateRoutes.activateRoutes (webpack-internal:///../../../router/src/router.js:1326:26)
    at eval (webpack-internal:///../../../router/src/router.js:1262:58)
    at Array.forEach (<anonymous>)
    at ActivateRoutes.activateChildRoutes (webpack-internal:///../../../router/src/router.js:1262:29)
consoleError @ zone.js:392
_loop_1 @ zone.js:421
drainMicroTaskQueue @ zone.js:425
Promise resolved (async)
scheduleQueueDrain @ zone.js:378
scheduleMicroTask @ zone.js:386
ZoneDelegate.scheduleTask @ zone.js:245
Zone.scheduleMicroTask @ zone.js:165
scheduleResolveOrReject @ zone.js:507
resolvePromise @ zone.js:470
(anonymous) @ zone.js:449
webpackJsonpCallback @ inline.bundle.js:22
(anonymous) @ components.module.chunk.js:1
zone.js:394 Error: Uncaught (in promise): Error: Error in :0:0 caused by: crypto.createHmac is not a function
TypeError: crypto.createHmac is not a function
    at Object.sign (webpack-internal:///../../../../jwa/index.js:34:23)
    at Object.jwsSign [as sign] (webpack-internal:///../../../../jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (webpack-internal:///../../../../jsonwebtoken/sign.js:186:16)
    at CheckIMEIStatusComponent.ngOnInit (webpack-internal:///../../../../../src/app/components/check-imei-status/check-imei-status.component.ts:26:25)
    at Wrapper_CheckIMEIStatusComponent.ngDoCheck (/ComponentsModule/CheckIMEIStatusComponent/wrapper.ngfactory.js:22:53)
    at CompiledTemplate.proxyViewClass.View_CheckIMEIStatusComponent_Host0.detectChangesInternal (/ComponentsModule/CheckIMEIStatusComponent/host.ngfactory.js:28:38)
    at CompiledTemplate.proxyViewClass.AppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:438:14)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:633:44)
    at ViewRef_.detectChanges (webpack-internal:///../../../core/src/linker/view_ref.js:175:20)
    at RouterOutlet.activate (webpack-internal:///../../../router/src/directives/router_outlet.js:160:42)
    at ActivateRoutes.placeComponentIntoOutlet (webpack-internal:///../../../router/src/router.js:1359:16)
    at ActivateRoutes.activateRoutes (webpack-internal:///../../../router/src/router.js:1326:26)
    at eval (webpack-internal:///../../../router/src/router.js:1262:58)
    at Array.forEach (<anonymous>)
    at ActivateRoutes.activateChildRoutes (webpack-internal:///../../../router/src/router.js:1262:29)
    at Object.sign (webpack-internal:///../../../../jwa/index.js:34:23)
    at Object.jwsSign [as sign] (webpack-internal:///../../../../jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (webpack-internal:///../../../../jsonwebtoken/sign.js:186:16)
    at CheckIMEIStatusComponent.ngOnInit (webpack-internal:///../../../../../src/app/components/check-imei-status/check-imei-status.component.ts:26:25)
    at Wrapper_CheckIMEIStatusComponent.ngDoCheck (/ComponentsModule/CheckIMEIStatusComponent/wrapper.ngfactory.js:22:53)
    at CompiledTemplate.proxyViewClass.View_CheckIMEIStatusComponent_Host0.detectChangesInternal (/ComponentsModule/CheckIMEIStatusComponent/host.ngfactory.js:28:38)
    at CompiledTemplate.proxyViewClass.AppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:438:14)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (webpack-internal:///../../../core/src/linker/view.js:633:44)
    at ViewRef_.detectChanges (webpack-internal:///../../../core/src/linker/view_ref.js:175:20)
    at RouterOutlet.activate (webpack-internal:///../../../router/src/directives/router_outlet.js:160:42)
    at ActivateRoutes.placeComponentIntoOutlet (webpack-internal:///../../../router/src/router.js:1359:16)
    at ActivateRoutes.activateRoutes (webpack-internal:///../../../router/src/router.js:1326:26)
    at eval (webpack-internal:///../../../router/src/router.js:1262:58)
    at Array.forEach (<anonymous>)
    at ActivateRoutes.activateChildRoutes (webpack-internal:///../../../router/src/router.js:1262:29)
    at resolvePromise (webpack-internal:///../../../../zone.js/dist/zone.js:475:31) [angular]
    at resolvePromise (webpack-internal:///../../../../zone.js/dist/zone.js:460:17) [angular]
    at eval (webpack-internal:///../../../../zone.js/dist/zone.js:509:17) [angular]
    at Object.onInvokeTask (webpack-internal:///../../../core/src/zone/ng_zone.js:266:37) [angular]
    at ZoneDelegate.invokeTask (webpack-internal:///../../../../zone.js/dist/zone.js:261:40) [angular]
    at Zone.runTask (webpack-internal:///../../../../zone.js/dist/zone.js:151:47) [<root> => angular]
    at drainMicroTaskQueue (webpack-internal:///../../../../zone.js/dist/zone.js:405:35) [<root>]
    at <anonymous> [<root>]

Angular version
Angular CLI: 1.6.1
Node: 6.12.0
OS: linux x64
Angular: 2.4.9
... common, compiler, compiler-cli, core, forms, http
... platform-browser, platform-browser-dynamic, upgrade

@angular/cli: 1.6.1
@angular/router: 3.4.9
@angular/tsc-wrapped: 0.5.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.1
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.2.1
webpack: 3.10.0

This library is not for the browser, and its dependent libraries require the crypto library that's built into node. You will probably need a different library that does not have that dependency.

@joovel thanks for the reply.


refactor: Extract common functionality for APIs

Common patterns for resource IDs.
Function for building StatusRuntimeExceptions with ErrorInfo.

This change is

Split out from #1932


ucrop url not found

Codes are fine, no any errors shown but when I click on run button this errors were found on log and stopped running further.

Summary

8: Task failed with an exception.

What went wrong:
Execution failed for task ':app:mergeDebugNativeLibs'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.github.yalantis:ucrop:2.2.6-native.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
- https://repo.maven.apache.org/maven2/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
- https://jcenter.bintray.com/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
Required by:
project :app
Could not find com.github.dhaval2404:imagepicker:2.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/github/dhaval2404/imagepicker/2.1/imagepicker-2.1.pom
- https://repo.maven.apache.org/maven2/com/github/dhaval2404/imagepicker/2.1/imagepicker-2.1.pom
- https://jcenter.bintray.com/com/github/dhaval2404/imagepicker/2.1/imagepicker-2.1.pom
Required by:
project :app
Could not find com.github.yalantis:ucrop:2.2.6-native.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
- https://repo.maven.apache.org/maven2/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
- https://jcenter.bintray.com/com/github/yalantis/ucrop/2.2.6-native/ucrop-2.2.6-native.pom
Required by:
project :app > com.github.dhaval2404:imagepicker-support:1.7.1

Code to reproduce

Used in MainActivity on onCreate Method.
fab.setOnClickListener(new View.OnClickListener() {
           @Override
           public void onClick(View view) {
               ImagePicker.with(MainActivity.this)
                       .createIntent();
           }
       });

If I exclude Companion then it shows error with with() method.  (Cannot resolve method)
Android version

minSdk 21
targetSdk 31
Impacted devices

Installation method

implementation 'com.github.dhaval2404:imagepicker:2.1'
implementation 'com.github.dhaval2404:imagepicker-support:1.7.1'
SDK version

compileSdk 31
Other information

Gradle 7.0.2
buildscript {
    repositories {
        google()
        mavenCentral()
        maven { url "https://jitpack.io" }
    }
  dependencies {
        classpath "com.android.tools.build:gradle:7.0.1"
 }
}
task clean(type: Delete) {
    delete rootProject.buildDir
}

This is my gradle.build  Project file

Hey @vtxmg
Kindy try by adding UCrop dependency manually
allprojects {
   repositories {
      jcenter()
      maven { url "https://jitpack.io" }
   }
}

implementation 'com.github.yalantis:ucrop:2.2.6' - lightweight general solution
implementation 'com.github.yalantis:ucrop:2.2.6-native'  - get the power of the native code to preserve image quality (+ about 1.5 MB to an apk size)

@hitesh-dhamshaniya  I tried implementation given by you still not working.
allprojects {
   repositories {
      jcenter()
      maven { url "https://jitpack.io" }
   }
}

I tried to paste this code in my build.gradle  Project  but shows other errors. Do I need to include this code in other way. I used this codes:
buildscript {
    repositories {
        google()
        mavenCentral()
        maven { url "https://jitpack.io" }
    }
  dependencies {
        classpath "com.android.tools.build:gradle:7.0.1"
 }
}
task clean(type: Delete) {
    delete rootProject.buildDir
}

@Dhaval2404 I did everything you have said and I got this error now
Duplicate class com.github.dhaval2404.imagepicker.BuildConfig found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePicker found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePicker$Builder found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePicker$Builder$showImageProviderDialog$1 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePicker$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePickerActivity found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePickerActivity$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePickerActivity$WhenMappings found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.ImagePickerFileProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.constant.ImageProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.listener.ResultListener found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.BaseProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CameraProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CameraProvider$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CompressionProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CompressionProvider$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CompressionProvider$startCompressionWorker$1 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CropProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.CropProvider$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.GalleryProvider found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.provider.GalleryProvider$Companion found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.DialogHelper found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.DialogHelper$showChooseAppDialog$1 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.DialogHelper$showChooseAppDialog$2 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.DialogHelper$showChooseAppDialog$dialog$1 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.DialogHelper$showChooseAppDialog$dialog$2 found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.FileUriUtils found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.FileUtil found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.ImageUtil found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.ImageUtil$WhenMappings found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.IntentUtils found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)
Duplicate class com.github.dhaval2404.imagepicker.util.PermissionUtil found in modules jetified-imagepicker-2.1-runtime (com.github.dhaval2404:imagepicker:2.1) and jetified-imagepicker-support-1.7.1-runtime (com.github.dhaval2404:imagepicker-support:1.7.1)

Go to the documentation to learn how to Fix dependency resolution errors.

You only need this one
implementation 'com.github.dhaval2404:imagepicker:2.1'
Remove this if you have added in gradle:
implementation 'com.github.dhaval2404:imagepicker-support:1.7.1'
Both library has same class files thats why you're getting duplicate class error. Support lib should be used when your project is not compatible with android X.

@Dhaval2404 Thank you so much it is working now. :)

save my day.

I still get the error "cannot resolve method 'with' in 'ImagePicker' "
Help please

@khadija-kaimous
Kindly check build configuration as discussed above. or provide your build.gradle configuration to understand the issue.

Cannot resolve method 'with' in 'ImagePicker' I remove the dependencies even checked each and every thing  implementation 'androidx.appcompat:appcompat:1.4.2'
implementation 'com.google.android.material:material:1.6.1'
implementation 'androidx.constraintlayout:constraintlayout:2.1.4'
implementation 'com.google.android.gms:play-services-cast-framework:21.0.1'
testImplementation 'junit:junit:4.13.2'
androidTestImplementation 'androidx.test.ext:junit:1.1.3'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'
implementation 'com.github.dhaval2404:imagepicker:2.1'
}
package com.example.imagepicker;
import androidx.appcompat.app.AppCompatActivity;
import android.os.Bundle;
import android.view.View;
import android.widget.ImageView;
import com.google.android.gms.cast.framework.media.ImagePicker;
import com.google.android.material.floatingactionbutton.FloatingActionButton;
public class MainActivity extends AppCompatActivity {
ImageView cover;
FloatingActionButton fab;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    cover = findViewById(R.id.cover_Img);
    fab=findViewById(R.id.floatingActionButton);
   fab.setOnClickListener(new View.OnClickListener() {
       @Override
       public void onClick(View view) {
           ImagePicker.with (MainActivity.this)
                   .crop()	    			//Crop image(Optional), Check Customization for more option
                   .compress(1024)			//Final image size will be less than 1 MB(Optional)
                   .maxResultSize(1080, 1080)	//Final image resolution will be less than 1080 x 1080(Optional)
                   .start();
       }
   });
}

}pluginManagement {
repositories {
gradlePluginPortal()
google()
mavenCentral()
}
}
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
jcenter()
maven { url "https://jitpack.io" }
}
}
rootProject.name = "Image picker"
include ':app'
here is my all work

I still get the error "cannot resolve method 'with' in 'ImagePicker' " Help please

same problem with me please help

Add this -> implementation 'com.github.Dhaval2404:ImagePicker:v2.1'
Add jitpack.io to setting. gradle
then sync your project
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
jcenter() // Warning: this repository is going to shut down soon
maven { url "https://jitpack.io/" }
}
}
this is working


The Database Gets Paused

          The supabase project has been paused for a while because there was no traffic within at least 1 week. Would you be posting your wallet address @Steveantor ?

Originally posted by @0xcodercrane in https://github.com/ubiquity/bounty-bot/issues/207#issuecomment-1486132606
If supabase gets paused due to inactivities it's a critical issue as the bot relies on it.

Would you be posting a proposal how we could handle this case?

I think this is a non issue because Supabase pauses due to inactivity. Assuming the bot is used, the instance should not be paused.


  So in my CreateFooter.chtml
@Html.Action("GetStatus", "VisitCounter", new { Address = "PV-Home -> Index" },true)
But things in my footer gets messed up. some part of footer which is right after this line of code, repeats before whole footer!! If i change it to this line
@Html.Action("GetStatus", "VisitCounter", new { Address = "PV-Home -> Index" })
Nothing gets messed up but the visit status data wo'nt be fresh anymore.
In Home controller , CreateFooter has dounut attribute
In VisitCounter controller , GetStatus has'nt dounut attribute
Please kindly help me.

Can you provide me a simple MVC demonstrating the issue ?

ok here is one example
if you take a good look, in footer we should have two lines of "some other information about copyrights" but in second page load which is when the page is cached, we have 4 lines.
https://drive.google.com/file/d/0B3YNJ8ZQzEClY3pmekxMeUVnN28/view?usp=sharing

And I found out the second child action gets called just once! which should display fresh data everytime but it won't.
Thanks

Are you doing any of this in an actionfilter?
If so, I had a similar problem and discovered it's because the actionfilter was being called twice, if it is on an action which calls a child action. You can avoid that by checking filterContext.IsChildAction.

Thanks man,
But no I'm not. If you download the sample project you'll see.

@mahdi87gh From your description it sounds like what I posted is correct. You need to somehow check for IsChildAction, and return if that is the case, else you will get two calls to the child action. See here.

Dear @migig As I mentioned before, I'm not getting two calls at all, and I'm not using any action filter. You can see it for yourself in the sample project.
Thanks anyway

@mahdi87gh You implied in your post that you are getting two calls, because you said that the markup is repeated.
If it is repeated then you are getting two calls into the same child action. Maybe put a breakpoint in there and double check (or rephrase that sentence).

@migig I did that (putting breakpoints on every action) before and NO I'm not getting two calls!!! and markup is repeated that's why I posted here!

That's weird...

@mahdi87gh See this

@migig Thanks
I did what i had to. I put database driven markup inside CreateFooter action and other markup to _layout.chtml

Cool :sunglasses:


auto generated side bar missing markdown files

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
When a folder contains a markdown file with the same name as the folder, the markdown file doesn't appear in the sidebar. This worked on previous versions.
Steps to reproduce
Sandbox link: https://codesandbox.io/s/vibrant-boyd-e34iti?file=/docs/same/same.md

Create a folder named X in docs
create a file named X.md in folder X

Expected behavior
X appears in the sidebar
Actual behavior
X is missing from the side bar
Your environment

Docusaurus version used: 2.0.0 beta-15

Reproducible demo
https://codesandbox.io/s/vibrant-boyd-e34iti?file=/docs/same/same.md
Self-service

[ ] I'd be willing to fix this bug myself.

Hi, this is a duplicate of #6301 and fixed in #6495.


Expose Eigen's Direct and Iterative Sparse System Solvers

See the [eigen] pull request for a comment about efficiency.
I added a dependency on Core for access to the Option module. If you would prefer to remove that and use pattern matching or a home-spun Option.map, that is also fine.
I also exposed eigen's rows() and cols() for convenience and as a defensive measure when setting the .m and .n properties of the solution matrices.
I did find one bug in the transpose() function, the dimensions were not being set correctly.

I agree with @tachukao, it is great to expose these functions but we should minimize the dependencies. If we want to avoid rewriting the mapping function, I’d rather add stdcompat as backward compatibility dependency and use Option.map from the new Stdlib exposed through it

For what concerns error reporting, that would be also very welcome but i think could be postponed! We can expose it in eigen in a separate PR and then add it here at that stage

I close this since there hasn't been any progress ... reopen if necessary.


[build-script] Enable new parser validation by default

Widen the parser validation coverage.
This encourages the developers to implement the new grammar in SwiftParser in addition to the old C++ parser.
In case  there's an unavoidable reason not to implement in SwiftParser, disable the validation for each test case by passing a frontend option '-disable-experimental-parser-round-trip'. But please file an issue and add FIXME like:
// FIXME: Remove '-disable-experimental-parser-round-trip' (rdar://xxx).

@swift-ci Please smoke test

preset=asan
@swift-ci Please test with preset macOS platform

@swift-ci Please smoke test


fix: radar chart issues

Description
Fixes some sizing issues with radar charts.

looks like the package-lock thing breaks npm ci in CI

looks like the package-lock thing breaks npm ci in CI

Yep seems like. I think it somewhat broke docker for me though maybe worth testing some more at some point.


[Bug][Android] TabView in RTL with Entries in content, changes tab when entry is focused

Description
I have a need to have form based items in multiple tabs, and each tab has controls like Entry, Picker, Editor & button.
When the app is switched to RTL language (arabic), and the focus on the Entry forces the tabview to different (left-most) tab
Steps to Reproduce

Create multiple tab with entries.

Add support in Android RTL.

Change the app or page to RTL flow direction.

Choose the right most tab and click on the entry.

The tab forcefully switches to the left most tab.

Expected Behavior
TabView should remain in the same tab and entry should be focused.
Actual Behavior:
Tabview switches to the left most tab.
Sample App: Use the getting started tab view from the XCT sample
XamarinCommunityToolkit-main.zip

I have the same problem with TabView when supporting RTL.

Any update on this regards ?

Any update here please ?

same issue here

Ok apparently for me it was a design issue in the XAML file. i had a ScrollView with Horizontal options that causes the issue. when i removed the ScrollView, the tabs are working fine now and the content are working fine also.

Any update on this bug please ?

Was anyone able to solve the issue ?

i found a workaround to resolve it and it is wired :
https://stackoverflow.com/questions/67384011/xamarin-community-toolkit-tabview-switching-tabs-when-tapping-on-entry


[CI] Run specs in random order by default

Running specs in random order is better than the default lexical ordering. But it's currently not the default behaviour and thus rarely used because it needs opt-in (#12540).
This patch opts into random order execution in CI and the Makefile in general.

Specs are currently failing due to side effects between examples. This is fixed in #12539. These side effects have been discovered through random order execution. So this already shows the benefits =)


[0.18] Fix KafkaBinding conversion

Proposed Changes

Cherrypick https://github.com/knative/eventing-contrib/pull/1651 into 0.18 branch
No fuzzing tests like KafkaSource. Created https://github.com/knative-sandbox/eventing-kafka/issues/145 for that

Release Note

- 🐛 Fix bug
Fix KafkaBinding conversion

Docs

/lgtm


ACM-5513: Update go to v1.20

Related Issue:  ACM-5513
Description of changes

Update go to v1.20

/cherry-pick release-2.6

/cherry-pick release-2.6

/hold

/unhold


Merge master branch to prTesting1_202009131925 branch

Docs Build status updates of commit aa7ce23:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit aa7ce23:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestCon1.md
:warning:Warning

Details

split/updateTestCon1.md

Line 0: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 1: [Suggestion-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning around July 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Recommendation: Add a Burn event in a similar way to the Mint.

Description
There is a mint event on the mint function, but there isn't on the burn function.
https://github.com/Steemhunt/dixel-v2-contract/blob/657250a219bbf63e27b970336045d48640151b6f/contracts/DixelClubV2NFT.sol#L42
https://github.com/Steemhunt/dixel-v2-contract/blob/657250a219bbf63e27b970336045d48640151b6f/contracts/DixelClubV2NFT.sol#L115-L127
https://github.com/Steemhunt/dixel-v2-contract/blob/657250a219bbf63e27b970336045d48640151b6f/contracts/DixelClubV2NFT.sol#L108-L113
Impact
The operator could not track the on-chain events easilty.
Recommendation
Add a Burn event and emit it as same as the mint function for better handling on the off-chain side.

cc/ @jinmo

Fair enough.
I didn't implement Burn event because we don't really track burn event anymore on V2, but some creator might need that.
They can still track it using Transfer event, but to make it consistent with Mint event, I will add it.
Thanks for your suggestion!


Assertion failing in behave test scenario @issue_680 tag

Observed below error messages in recent travis builds. This issue is inconsistent but most of the times build is failing with below scenario. This could be another timeout issue as assertion value of "a" is taking from the initial invoke value.
Scenario:
@issue_680
Scenario Outline: chaincode example02 with 4 peers and 1 membersrvc, issue #680 (State transfer) -- @1.3 Consensus Options
Below are Error messages:
Assertion Failed: For attribute OK, expected (20), instead found (130)
http://chunk.io/f/8b49ada17f5247e08b7d11da327a4d02
Exception: Max time exceeded waiting for transactions with current response map = {'bddtests_vp0_1': 404, 'bddtests_vp1_1': 0, 'bddtests_vp2_1': 0}
http://chunk.io/f/c1b62c91018342f2bf394444938d914a
Container Log Files:
bddtests_vp0_1_chaincode_example02_with_4_peers_and_1_membersrvc,issue#680_(State_transfer)-.1.3_Consensus_Options.log
http://chunk.io/f/598ffb3c661e4f2a99f29fd858828b5c
bddtests_vp1_1_chaincode_example02_with_4_peers_and_1_membersrvc,issue#680_(State_transfer)--1.3_Consensus_Options.log
http://chunk.io/f/055afebd4099421fa41bbc15c8b739aa
bddtests_vp2_1_chaincode_example02_with_4_peers_and_1_membersrvc,issue#680(State_transfer)--1.3_Consensus_Options.log
http://chunk.io/f/1f123a79dce040e486bb55bacce7e85e
bddtests_vp3_1_chaincode_example02_with_4_peers_and_1_membersrvc,issue#680(State_transfer)_--_1.3_Consensus_Options.log
http://chunk.io/f/220baf46073e426ab685277a4d1c9415

I saw this "expected 20 found 130" error while looking at #1331 .
From looking at both sets of logs,  vp3 had not finished state transfer before the query came in thus the incorrect query return. I added a wait before issueing the final query in the test and have not been able to reproduce.
@jyellick @simon thoughts ?

@tuand27613 Like many other Travis failure's we've seen, it seems likely that this is the timeout issue as you described.  I would have to check logs to confirm, but if tweaking the timeout up seems to solve it, then I'd be in favor of pulling it.

logs from behave run in my Vagrant setup
1358.zip

+1 on not having 680 as part of the travis run .
Perhaps we can tweak the travis behave call to skip this test ? Developers can still have it run when they do their manual unit tests

@tuand27613 I actually wasn't proposing deleting the test, I meant "pulling (as in a PR) a timeout fix".  State transfer is one of the more complex test scenarios, but I think it's important it be tested, especially as new developers want to submit code changes which might break it in subtle ways.

I put in a PR to add the extra wait.
My issue is how to deal with the many false positives out of travis ? Maybe we should have developers attach output of a full unit tests/behave tests/sdk tests run while travis runs a smaller regression bucket.
At least until we can bend behave to our will :-)


Option to "hide" the tab bar

Some use cases demand temporarily hiding the tab bar

PR is welcome would be nice with an animation of some kind

checkout #19


Small white line above title bar

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
There appears to be a small white line above the title bar as seen in the screenshot below. This is especially irritating when in mojave dark mode and using a dark atom theme.
Atom on top of screen:

Atom placed anywhere on screen:

Steps to Reproduce

none

Expected behavior: No white line, so the dark atom colour will go seamlessly into the status bar.
Actual behavior: There's a white line above atom which prevents this.
Reproduces how often: 100%
Versions
atom: 1.30.0
Mac: MacBook Air 13"
MacOS: Mojave 10.14 Dark Mode
Additional Information
I think there is none.

Thanks for the report!  I poked around in the Electron repository and found https://github.com/electron/electron/issues/13164, so seems like an Electron issue.


Update to latest apispec

Several versions behind now, and it's causing conflicts.

I have found apispec-chalice to be very useful, but the deeper I get into it I'm finding it difficult to use because it's hard to find the right documentation for older versions of apispec.

@bugeats you are absolutely right, apispec-chalice does need to be updated to be compatible with the newer versions of apispec. Unfortunately, I do not have the capacity to do this at the moment. Would you be interested in submitting a PR? If not, I'll get to it as soon as I can.

Any update on this?


[Info | Request] Anpylar Material

Not sure if this falls into info or feature request: are there any plans about porting Material Design to Anpylar like material2 for Angular?

AnPyLar offers just the framework, not the kits (like material2 or bootstrap)
That would be a separate project.


Can't Seem to find the documentation

Says it is well documented, but I can't find it anywhere. A good shove in the right direction will be most helpful.

Found it; I just had to switch branches to see the link. Maybe adding it to the readme would be helpful.
Link for anyone who needs it: Click Here


Unable to set OpenGL force_introspection setting

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 86be75dd97b5633b8c0aa6bdcb3346fa871a8480 dirty (events: bring back accidentally nuked preConfigReload).
Date: Tue Feb 20 04:24:15 2024
Tag: v0.35.0-59-g86be75dd

flags: (if any)

System Information:
System name: Linux
Node name: archlinux
Release: 6.7.6-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000

GPU information:
2d:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:
  split-monitor-workspaces by Duckonaut ver 1.1.0

Bug or Regression?
Bug
Description
When i try to set
opengl {     force_introspection=0 }
in my hyprland config file, I get the following error: config option opengl:force_introspection does not exist.
I would like to try changing it, to see if i can get my performance in games to be a bit better, but I'm unable to test this setting right now. Enabling tearing and the nvidia anti flicker setting seem to improve the stuttering of games I've been running into, so I was hoping that force_introspection set to 0 (instead of the default 2) might make it even better.
How to reproduce
Go into your hyprland.conf file and add
opengl {     force_introspection=0 }
Crash reports, logs, images, videos
No response

for the love of god please make sure you're on latest before opening issues about config options from the -git wiki being missing

for the love of god please make sure you're on latest before opening issues about config options from the -git wiki being missing

Sorry about that, thought i was on latest, seems i was wrong though, next time I'll double check


New version: Beeper.Beeper version 3.102.10

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @SpecterShell,
I couldn't find a download link in the PackageUrl, and instead found "Join the waitlist" links. Has this package been officially released yet?

Hi @SpecterShell,
I couldn't find a download link in the PackageUrl, and instead found "Join the waitlist" links. Has this package been officially released yet?

https://www.beeper.com/download which is at the bottom of the PublisherUrl. I have updated the PackageUrl accordingly.
The InstallerUrl is from https://download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in <INSTALLDIR>\resources\app-update.yaml

@stephengillie

Thanks for updating the PackageUrl.

The InstallerUrl  is from https://download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in <INSTALLDIR>\resources\app-update.yaml

The upgrade location for this application can be found in a YAML file of a previous version? I'm guessing this application has an upgrade check, and this is where the application records the upgrade's location. This sort of data isn't easy to record in the PackageUrl, to navigate between them.

Thanks for updating the PackageUrl.

The InstallerUrl  is from download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in <INSTALLDIR>\resources\app-update.yaml

The upgrade location for this application can be found in a YAML file of a previous version? I'm guessing this application has an upgrade check, and this is where the application records the upgrade's location. This sort of data isn't easy to record in the PackageUrl, to navigate between them.

Yeah, the same file can also be found in the installer from the PackageUrl, and is usually consistent across the versions.
Many other (electron-based) packages are using the same methodology for upgrading, including Anydo.Anydo, JetBrains.Space and LukiLabs.Craft.

Verify:


Add server side function wkt("polygon") to allow subsetting by WKT polygon

Add new server side function like:  &wkt("a string with the WKT polygon")  ERDDAP could handle this by converting the polygon into lat and lon constraints, getting that data subset, then properly subsetting to the polygon, then return the results to the user. Thanks to Matthew Biddle.

Rather than just add a wkt(polygon feature, it may be much better to add support for the features of the new
OGC EDR API . That could be relatively easy given that ERDDAP is already set up to do all the background work (getting data from data sources).

That API seems to provide a good framework for single-url requests that includes WKT. The details specified in the API look very nice to me but I will be happy to get data for a given WKT regardless of the implementation.

The need for this functionality keeps coming up in my communities. Utilities are being developed to provide this functionality client-side by combining results from several ERDDAP calls.
What can I do to help move this forward? I am setting up an ERDDAP dev environment now in case I can help contribute some code.

I'm just one guy and I'm maxed out. If you want to speed this up:
a) You can add a server-side function to do it. (It won't be easy because it would be the first server-side function for griddap. There is analogous code for server-side functions in tabledap. Maybe the first step is to add this function to tabledap.)  Sorry, for now, I can't offer much help. I'm maxed out.
b) You can add it by adding support for (some of) the EDR API to ERDDAP.
c) You may be able to fund (a) or (b). We have another programmer capable of this, but currently by contract only.  Talk to<EMAIL_ADDRESS>about funding issues.

Hi, afaik the scenario that makes sense is retrieving coverage of the given polygon that is diagonal to the box like Adriatic sea or vessel route corridor. The user does not draw polygon manually then.
Ad URL limit options I can see are POST instead of GET and URL of the polygon in parameter rather than inline and additional external query assuming it's allowed.


Composing Multiple HOCs - property types ignored/lost

Using flow-bin 0.69.0.
This is related to  https://github.com/facebook/flow/issues/6057.
We use -
react-i18next  - https://github.com/flowtype/flow-typed/tree/master/definitions/npm/react-i18next_v7.x.x/flow_v0.64.x-
react-redux - https://github.com/flowtype/flow-typed/tree/master/definitions/npm/react-redux_v5.x.x/flow_v0.62.0-
library definitions in our product.   We have many usages like the following -
export default translate()(connect(mapStateToProps, mapDispatchToProps)(MyComponent));
where we are composing multiple HOCs.  As the above github flow issue describes, the property types for MyComponent are not checked (no errors reported when they should be).
Is there any way to type the translate and connect HOCs so that errors are properly reported?  The issue report notes that returning Class<React.Component<...>> instead of React.ComponentType might work.  Unfortunately I am not an expert in type annotations and library definitions are Greek to me.  Is there any suggestion on how to fix this issue?

What kinds of errors are you trying to properly report? connect should work fine, so if usages of the output of translate()(...) is not typing correctly I'd suspect react-i18next to be the culprit.

In my example above, MyComponent had flow properties defined such as -
myRequiredProperty: boolean,
myPropertyOfSpecificType?: string

and I used the component like this -
<MyComponent myPropertyOfSpecificType={4}/>
I would expect flow to report that myRequiredProperty was not specified and that myPropertyOfSpecificType is of the wrong type.  It doesn't report these errors when both composing multiple HOCs (translate + connect).
If the export is -
export default translate()(MyComponent);
or
export default connect(mapStateToProps, mapDispatchToProps)(MyComponent);
the errors are reported correctly.  A single HOC works.  Composing multiple HOCs does not.
I will point out the flow issue that I linked to in my original report - https://github.com/facebook/flow/issues/6057.  In that report 2 people note that composing multiple HOCs appears to "lose" property types.
The reporter of that issue indicates that if the type definitions of the HOCs return Class<React.Component<...>> instead of React.ComponentType that this seems to work.  The comment by @vetvicka also reproduces this error by using an HOC defined using the pattern documented in the Flow documentation at https://flow.org/en/docs/react/hoc/#toc-supporting-defaultprops-with-react-elementconfig.
I tried modifying the translate and connect libdefs locally to return Class<ReactComponent<...>> but that resulted in other Flow errors.
So if this issue and https://github.com/facebook/flow/issues/6057 are related it seems that it is not a react-i18next libdef issue but a more generic issue since both translate (react-i18next) and connect (react-redux) use the same React.ComponentType / ElementConfig pattern.


Need your help, sir. How should I specify the download path?

As the title shows, I use this code: hatitrust-downloader mdp.39015073487137 1 10 --name my-book
I don’t know the specific location of the downloaded file on my computer. Can I let this code specify the path and download the book to the path I specify? Please help me, am a newbie.

Hey, it will always default to storing the files in the same place as you run the command from. There is no support to specify a different download location at this point.
However, you can change the directory where you run it from. For example, create a new folder for a book, open the terminal to run from that folder and run the tool from there. That way, the files will be written to that new folder.
I would be happy to accept a contributing PR which adds a new parameter to control the download path to, but it will require knowledge of Python to make that reality.

Hey, it will always default to storing the files in the same place as you run the command from.嘿，它始终默认将文件存储在您运行命令的同一位置。
There are two ways you can control the directory where the file is stored:有两种方法可以控制存储文件的目录：

Change the directory where you run it from. For example, create a new folder for a book, open the terminal to run from that folder and run the tool from there. That way, the files will be written to that new folder.更改运行它的目录。例如，为一本书创建一个新文件夹，打开终端以从该文件夹运行，然后从那里运行该工具。这样，文件将被写入该新文件夹。
Use the --name parameter with a path-prefix. Whether to use / or \  in the path to denote folders is operating system dependend, so I can't get you a generally working example. But for Linux / Mac something like hathitrust-downloader mdp.39015073487137 1 10 --name my-book-dir/my-book.将 --name 参数与路径前缀一起使用。在路径中使用 / 或 \ 来表示文件夹取决于操作系统，因此我无法为您提供一个通常有效的示例。但对于 Linux / Mac，类似于 hathitrust-downloader mdp.39015073487137 1 10 --name my-book-dir/my-book .

Thank you so much for your answer and help! I finally figured it out! Thank you for your contribution, you are really a genius! Awesome!

Hey, it will always default to storing the files in the same place as you run the command from.
There are two ways you can control the directory where the file is stored:

Change the directory where you run it from. For example, create a new folder for a book, open the terminal to run from that folder and run the tool from there. That way, the files will be written to that new folder.
Use the --name parameter with a path-prefix. Whether to use / or \  in the path to denote folders is operating system dependend, so I can't get you a generally working example. But for Linux / Mac something like hathitrust-downloader mdp.39015073487137 1 10 --name my-book-dir/my-book.

After experimentation, I found that in Windows, only the first method can be used to specify the specific path for book downloads, that is: in the specified folder, hold down the shift key, right-click to open PowerShell, and enter "hathitrust-downloader mdp.39015073487137 1 10 --name my-book".


Improvement/add go doc

Closes #19

Looks great! I'll try to create a static web-based documentation page using godoc later.


Raw Data vs Parsed Data

Use lowercase variables for raw data and CamelCase for parsed data.
Example:
flags: 0x1f
Flags: {
hops: 3,
remaining: 2,
etc....
}

I believe this is corrected


All events captured by the logging integration are grouped together

Platform
Flutter Mobile
Obfuscation
Disabled
Debug Info
Enabled
Doctor
[!] Flutter (Channel stable, 3.7.1, on macOS 13.1 22C65 darwin-x64, locale en-GB)
• Flutter version 3.7.1 on channel stable at /Users/barabas/source/flutter
! Warning: dart on your path resolves to /usr/local/Cellar/dart/2.19.3/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/barabas/source/flutter. Consider adding /Users/barabas/source/flutter/bin
to the front of your path.
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 7048ed95a5 (3 months ago), 2023-02-01 09:07:31 -0800
• Engine revision 800594f1f4
• Dart version 2.19.1
• DevTools version 2.20.1
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
• Android SDK at /Users/barabas/Library/Android/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 14C18
• CocoaPods version 1.11.3
[!] Android Studio (version 2022.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
✗ Unable to find bundled Java version.
• Try updating or re-installing Android Studio.
[✓] VS Code (version 1.74.3)
• VS Code at /Users/barabas/Downloads/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (2 available)
• iPhone XR (mobile) • 00008020-001E2C881A33002E • ios        • iOS 15.6.1 19G82
• macOS (desktop)    • macos                     • darwin-x64 • macOS 13.1 22C65 darwin-x64
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 3 categories.
Version
6.22.0
Steps to Reproduce
Enable the logging integration and write a severe log. Do not provide an error or stacktrace parameter to the logger.
Expected Result
The event generated by the log includes a stack trace, filename and line number information of where the log was written from.
Every time the log runs, a new event is added to the same group in the web UI.
Every time a different line logs an event a new group is created for that log.
Actual Result
The generated event has a filename and stacktrace of <asynchronous suspension>. All of the severe logs in the project are grouped under this stack trace in the web UI using the default grouping.

I expected every instance of a severe log to be grouped with other events generated by the same line. I tried to set up a custom group, but the best I seem to be able to do is to completely prevent grouping using the following line:
stack.abs_path:"<asynchronous suspension>" -> nostack, {{ message }}
Are you willing to submit a PR?
Yes

I've found a workaround by setting recordStackTraceAtLevel to match the recordStackTraceAtLevel. Now all severe logs have a backtrace, either through the logging library providing the current stacktrace, or the user provided one through the function parameter.
This solution works for me. I'll keep the issue open so that it can be added to the documentation.

@maBarabas thank you for raising this.
I see, if no stackTrace is provided, the SDK gets the Stacktrace.current automatically, and due to the nature of async/await stuff, they could look like this "asynchronous suspension".
Another option is setting a beforeSend callback and removing all the threads values, then the event will be grouped by the message field and not stack trace anymore.
Using Stacktrace.current automatically also has its benefits so changing this behavior is not desirable.
I'm not sure we can do something here, if you found a workaround, can we close this?

If the SDK uses Stacktrace.current, and it returns a meaninless stack trace like a single frame of <asynchronous suspension>, would it make sense to submit the event without a stacktrace instead? That would then fall back to grouping by message which is more desirable I think. This can be done inside the SDK without any user configuration, and prevents the bug where unrelated events are grouped together because of the low quality stack trace.
If the stacktrace is meaningful, the event can be submitted with the stacktrace as usual and nothing changes.
I think this would be a good change, since it resolves the bad grouping when using the default configuration. If you don't want to implement it, you can close the issue, as I'm happy with the workaround.

@maBarabas that makes sense, if its a single frame and has that label, we could strip it out, this should be possible on the server as well with stack trace rules, let me check which ones make more sense.


Add check for daq-reader processing threads

What is the problem / what does the code in this PR do
Check that redax / dispatcher is not writing wrong threads to wrong runs.
Can you briefly describe how it works?
Each of the readers is registered, let's check that we don't get reader_6 for non NV data, etc.
This is of course very sloppy and we shouldn't do need this for a long period of time

"Sloppy" is a word to describe this. We're passing through separately the keys and values of daq_config.processing_threads, and not using them in a combined and coherent way.

@darrylmasson I wasn't anticipating that we'd keep this implemented for long, you want me to change it?

"Sloppy" is a word to describe this. We're passing through separately the keys and values of daq_config.processing_threads, and not using them in a combined and coherent way.

@darrylmasson I wasn't anticipating that we'd keep this implemented for long, you want me to change it?

We have two options: a quick and dirty implementation, or something that makes fuller use of the information we can access. Do we want DAQReader to always just take whatever files are present, or do we think it's reasonable to actually check that it's seeing the files it should? We had a similar problem much earlier when redax wasn't correctly allocating processing threads, and this is quite similar.

We have two options: a quick and dirty implementation, or something that makes fuller use of the information we can access. Do we want DAQReader to always just take whatever files are present, or do we think it's reasonable to actually check that it's seeing the files it should? We had a similar problem much earlier when redax wasn't correctly allocating processing threads, and this is quite similar.

We have two options: a quick and dirty implementation, or something that makes fuller use of the information we can access. Do we want DAQReader to always just take whatever files are present, or do we think it's reasonable to actually check that it's seeing the files it should? We had a similar problem much earlier when redax wasn't correctly allocating processing threads

Okay, based on your phrasing, I think you imply the latter. Thanks for the feedback. To implement the latter:

Indeed just use the dict instead of keys and values separately;
use a counter to see that the number in each chunk is le the #processing threads from the rundoc (last few chunks don't need to have all threads per se).

We have two options: a quick and dirty implementation, or something that makes fuller use of the information we can access. Do we want DAQReader to always just take whatever files are present, or do we think it's reasonable to actually check that it's seeing the files it should? We had a similar problem much earlier when redax wasn't correctly allocating processing threads

Okay, based on your phrasing, I think you imply the latter. Thanks for the feedback. To implement the latter:

Indeed just use the dict instead of keys and values separately;
use a counter to see that the number in each chunk is le the #processing threads from the rundoc (last few chunks don't need to have all threads per se).

Thanks @darrylmasson, well spotted mistakes. Just tried it on two runs in non production mode. One processed all right the other gave:
/live_data/xenonnt/012118/THE_END. Got reader6_reader_0
Are you happy with this behavior with the counting of threads or would you argue for smarter checks?

Thanks @darrylmasson, well spotted mistakes. Just tried it on two runs in non production mode. One processed all right the other gave:
/live_data/xenonnt/012118/THE_END. Got reader6_reader_0
Are you happy with this behavior with the counting of threads or would you argue for smarter checks?


Grammar with error before first EOL causes bad error report

xxx// Grammar showing bug 1 -- error before first EOL
ironmeta BuggyParser<char, bool> : Matcher<char, bool>
{
}

Just confirming this goes deeper. The function MatchState.GetLine gets badly confused if called for an error before the first EOL, and returns the wrong source code line. It seems to because the Position array is empty. Adding a zero position at the beginning might make it all work.


Can't edit github project without master branch

Describe the bug:
When connecting a project to an existing GitHub repo without a master branch, the error: Could not resolve reference "refs/heads/master" appears and the project seems to load forever.
Link to the blitz that caused the error
https://stackblitz.com/edit/github-ctd7ra
Steps to reproduce:

Open project linked to a GitHub repo without a master master branch

Expected behavior:
Should load the default branch, or load the different branches and give the option to switch
Version of webcontainer:
Hash: 70a1ff62a0f0131ac0df3c30faf487fef744ac90
Screenshots:

Desktop (please complete the following information):
Browser name  = Chrome
Full version  = 91.0.4472.124
Major version = 91
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 85395530,
  "usedJSHeapSize": 67277294,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Looks like a duplicate of #195

Duplicate of #195 alright


Reenable preferences, active friends, etc

Addresses https://github.com/rsms/fb-mac-messenger/issues/308, which is the base cause for https://github.com/rsms/fb-mac-messenger/issues/313, https://github.com/rsms/fb-mac-messenger/issues/309, and https://github.com/rsms/fb-mac-messenger/issues/305 as well.
So, here is what's changed on Facebook's side:

The left-side header is no longer its own React component
The gear menu itself is no longer its own React component

This means we can't easily grab the settings gear any more and we can't rely on calling methods directly on it. So here's what I did:

I grab the header and gear button as regular DOM elements rather than React components
I use CSS to hide the gear and back buttons since we can't rely on proxying componentDidMount any more, given that we don't have a component
Digging through the messenger.com source, it looks like they switch sidebar views with require('MessengerActions').changeMasterView(require('MessengerView').MASTER.RECENT) and similar calls, so I use that
Logging out and opening preferences are slightly more complicated since they require passing a React component argument into methods to attach the modal window onto a view, which is a little sketchy to try to replicate. Since preferences and logout are the first and last menu items respectively, it seems relatively safe to try to click on those through the menu DOM.

Interesting side note about that: there still are methods attached to the menu that we could try to call directly, but they have names like component.$MessengerSettingsMenu1() (where, weirdly, they count from 1 to 11 but skip 6 and 10), so I figured these are not the sorts of methods we should rely on
Also, when going to the active friends menu and then returning to the inbox, Messenger leaves the old menu ul hidden in the DOM. If you open the menu, it creates a new one. If you go back and forth, it keeps adding more menus. So, when doing a DOM query to find the preferences and logout buttons, I do a querySelectorAll and grab the last one in order to make sure I get the most recent menu that has actual event listeners on it.

I also took the opportunity to add active friends list and inbox links into the View menu.
Let me know if there's anything in here that feels too sketchy or needs to be cleaned up!

Works good for me! Thank you, this has been driving me crazy!

pinging @rsms
I work on messenger.com and use this wrapper. Because of the way assets are bundled you can't target class names easily. Things like the gear broke like five times now. Unfortunately we can't take into consideration every wrapper out there, sorry about that.
However. would it be easier for you if we exposed e.g. two or three never-changing classNames on relevant DOM elements? While we're at it, what other functionality do you need? For instance, cmd-f is also broken now.

@davepagurek Great work! 😃  One small issue though: showActiveFriends doesn't work while in "Message Requests" view. You'll have to change view to "master.recent" before switching to 'master.people', i.e.
showActiveFriends: function() {
  require('MessengerActions').changeMasterView(require('MessengerView').MASTER.RECENT);
  require('MessengerActions').changeMasterView(require('MessengerView').MASTER.PEOPLE);
},

Plus, how about key shortcuts? E.g. option+cmd+{1, 2, 3} for Inbox, Requests, and Active Friends respectively?
@chenglou Thank you for coming forward, it's greatly appreciated! The best way would probably be to expose an API that would perform most common interactions that these wrappers do like showing and hiding settings window, hiding the cog icon, focusing search field, changing views (new message, requests, active friends, inbox), etc.
While that solution puts most of the maintenance burden on FB/Messenger.com team it is the least likely to accidentally break wrapper apps.
On my experimental branch I open Messenger settings with:
require('MessengerActions').showDialog(
  require('MessengerSettingsDialog.react'),
  { viewer: require('CurrentUser').getID() }
);

A wrapper-friendly API could simplify that particular action to, for example:
require('WrapperAPI').showDialog('settings');

I assume that if Facebook was eventually release its own desktop app it would probably use similar API to encapsulate all binding points between app shell and react app.

Update: added keyboard shortcuts and fixed a small CSS thing that broke with the settings gear when you hover over a conversation in small screen mode, plus the showActiveFriends fix from @CvX.

Nice work. Thanks!

Shipped in version 0.1.12


method intelliSense is wrong in Parallel.For action

Environment:
版本: 1.88.1 (system setup)
提交: e170252f762678dec6ca2cc69aba1570769a5d39
日期: 2024-04-10T17:41:02.734Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
C# Dev Kit: v1.4.29

input new Dictionary,but   intelliSense is Parallel.For  method,like this:

code like this
 Parallel.For(0, 200, async (index) =>
  {
      new Dictionary()
  });

The starred suggestions are provided by the 'IntelliCode for C# Dev Kit' extension, which promotes certain items in the list based on what you likely might pick.  It isn't guaranteed to pick exactly what you want every time, but it should pick reasonable things.
In this case, promoting index inside the list doesn't seem unreasonable to me (the variable is in scope).
If you're consistently seeing strange suggestions, file an issue on the intellicode side here - https://github.com/MicrosoftDocs/intellicode/issues


Crash when Model.created is missing

Description
When I request models with openAI.models(), sometimes if the response is not containing the created property, serialization throws an exception.
com.aallam.openai.api.exception.OpenAIHttpException: Illegal input: Field 'created' is required for type with serial name 'com.aallam.openai.api.model.Model', but it was missing at path: $.data[0]

Steps to Reproduce

Set baseUrl to https://api.endpoints.anyscale.com/v1/.
Call openAI.models().
Exception is thrown.

Additional Info
Giving created a default value and/or making it nullable can solve the problem. Also some providers are not including owned_by as well, so giving it a default value would help in these cases.

This issue is duplicated and Pull request related to this problem has been approved (https://github.com/aallam/openai-kotlin/pull/332)
Commit available here: https://github.com/aallam/openai-kotlin/pull/332/commits/338b8f0d8aeaf920a009493afa15a1633a3d891c
Previous issue available here: https://github.com/aallam/openai-kotlin/issues/331
As a temporary solution you can use bare http request and decode JSON response.


teach me plz

What an amazing problem/solution set!
Could you teach me some, ziwen?

When are you going to die?

what an inspiring work，love from China！

I think so.


Add docs on gateway node connection limits

Fixes DOC-2582
Summary of changes:

Add an include file that describes the new
server.max_connections_per_gateway cluster setting, and the error
code that results if the max connections are exceeded

Reference the include from various related places in the documentation that
mention connection pools, admission control, etc.  Specifically, the
following pages:

Admission Control

Connection Pooling

CREATE DATABASE (specifically the CONNECTION LIMIT syntax)

Known Limitations (where memory monitoring is mentioned
w.r.t. simultaneous client connections)

Recommended Production Settings (where connection pools are
referenced)

UI SQL Dashboard (where the number of connections is mentioned)

Bonus: Added an anchor link to a good definition of 'gateway node' in
the SQL Layer page of the architecture docs, and link to it from the
include where we mention the gateway node.

This change is


Suppress qiskit algorithm globals deprecation messages

Summary
The algorithm_globals function here in Qiskit Algorithms delegates its behavior to the equivalent logic in Qiskit as part of the migration support from algorithms in Qiskit that were migrated here. Since that time the function in Qiskit has been deprecated and deprecation messages added to alert the user to the migration. When this logic here was initially done those deprecation messages were not present, but since that time the way the logic is here causes users to see these deprecation messages which they should not. These messages also flooded the combined deprecation output from CI here. This PR suppresses these around the points of usage here so the messages are no longer raised.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 15 (93.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 90.578%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_algorithms/utils/algorithm_globals.py
14
15
93.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
6470

Relevant Lines:
7143

💛  - Coveralls


0.5.1 Release notes

Adds summary and any needed polish to 0.5.1 release notes

[x] Update changelog

Codecov Report

Merging #426 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #426   +/-   ##
=======================================
  Coverage   50.89%   50.89%
=======================================
  Files          33       33
  Lines        9292     9292
=======================================
  Hits         4729     4729
  Misses       4563     4563

Continue to review full report at Codecov.

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


Close process gracefully

Listen for os.interrupts so that defer file.close() calls can be executed

Looks clean!


NLog MDLC + NDLC when NLog ver. 4.6 is ready

NLog 4.6 includes better handling of non-string-objects: NLog/NLog#2857

Thanks for PR @snakefoot ! I see nlog 4.6 is not shipped yet. This is safe to ship before 4.6 is out?

@snakefoot Can you contact me privately (see my profile for email)? I would like some help maintaining this library and I feel I am doing a disservice to you and the lib's users at this point. Simple reason is time. Am @randompunter on twitter too if you want to DM there.

Yes the reflection logic will ensure the new logic will only activate when running with NLog 4.6
There might be a catch22 when having multiple libraries that are using LibLog and only some are using 5.0.3.Then use of OpenMdc will behave different during transition phase of upgrading all libraries. But MDLC is the "future".
I'm already fully booked with NLog so not ready for an extra child :)
Sent from my Sony Xperia
---- Damian Hickey wrote ----
Thanks for PR @snakefoothttps://github.com/snakefoot ! I see nlog 4.6 is not shipped yet. This is safe to ship before 4.6 is out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/damianh/LibLog/pull/181#issuecomment-436913385, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK-fnBr2MhHHnp3PgXhI4fNuVeIflXvhks5us-v9gaJpZM4WdLEs.

Should one also update the pp-file? Looks like I have forgotten it. Will fix it tonight. Unless you do it
Sent from my Sony Xperia
---- Damian Hickey wrote ----
Thanks for PR @snakefoothttps://github.com/snakefoot ! I see nlog 4.6 is not shipped yet. This is safe to ship before 4.6 is out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/damianh/LibLog/pull/181#issuecomment-436913385, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK-fnBr2MhHHnp3PgXhI4fNuVeIflXvhks5us-v9gaJpZM4WdLEs.

@damianh Created #188


Add support for modules

Because fery few other compilers did that. Also, this requires changes on the sourcemapping format and the name handling and resolution.

Because fery few other compilers did that.

yes, so we need to make a kinds of "macro" like C's #include or "bundler" like webpack

I (very) often need this with mlogjs !
Why not just include a file (at the parser level) ?
import 'module.js';
This would just read the concatenate module.js to the rest of the file (the compiler should even not know that a module was imported).
(I'm not an expert at all in javascript)

Why not just include a file (at the parser level) ?

Because mlogjs doesn't actually do the parsing by itself, it uses babel to parse the code and then traverses the AST (Abstract Syntax Tree) that babel generated.
The are a few things that are in the way of implementing modules:

Implementing a module resolution algorithm (needs the path of the input file and needs to give the compiler access to the file system, instead of just giving it to the CLI)
Implementing import views (see this stackoverflow answer)
Updating the sourcemaps feature to handle multiple files
Make all of it compatible with the web environment so that it works on the online editor

And while module support is within my priorities, I find it more important to implement the optimizer first, as that will eliminate many bugs in the current implementation and possibly make handling modules more straightforward in some aspects.


improvement(linter/oxc): using facades for barrel detections.

closes #3069
It is similar to this, I've dialed back some package resolving to make it more general, We might want to invest in creating a package resolver(let me know if we already have the infrastructure for it and I've missed it).

#3215  👈
main

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

Join @rzvxa and the rest of your teammates on  Graphite

Now I understand what this is doing once it's written in Rust 😅


Dev

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: bathams sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Does deck.gl support a floating polygonLayer?

Does deck.gl support a floating polygonLayer?

do you mean like this - https://github.com/uber/deck.gl/issues/2435#issuecomment-441831996 ?


[11.x] Update trait and interfaces directory

Using the commands php artisan make:interface [InterfaceName] and php artisan make:trait [TraitName], the desired interface and trait are created within the app directory.
Even if the names of the interface and trait are identical, the second command won't execute and will return an error '[Interface/Trait] already exists'.

With this pull request, the organization of these two items within the app directory is improved, allowing for faster development and access to the files.

These should be flexible in design as they are not framework-specific.

@Noorani-MM This can be worked around by prefixing the command line argument to include the desired directory.
php artisan make:interface Contracts/Example

php artisan make:trait Traits/Example

I agree with @ahinkle that a framework agnostic approach is better in this case because the commands create plain old PHP structures and not framework specific ones like make:job or make:cast for example. Developers have different preferences for how they prefer to structure domain-specific code, which usually takes the form of plain old PHP structures.

I fully agree with @ahinkle; it shouldn't be restricted to App\Traits or App\Interfaces.

Tests fail here

I was going to open an issue, but with @grahamsutton explanation, I think it is okay as it is then.


Fix formSelect component's default option

When adding using the default-option directive you would need to have added a length property with a truthy value to successfully add the default option. This change fixes that by making sure there is a default option with a text and value property.

thanks :)


Karpenter default provisioner selection

version 0.7.2
I have either miss-understood the documentation or there is an issue with the way the default provisioner is implemented.
Expected behaviour:
I create a Provisioner named default and a Provisioner named burstable.
when a pod is created it is provisioned using the default Provisioner .

apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
name: default
labels:
app.kubernetes.io/name: default
app.kubernetes.io/component: karpenter
spec:
requirements:
- key: node.kubernetes.io/instance-type
operator: In
values:
- m6i.large
- m6i.xlarge
- m6i.2xlarge
- c6i.large
- c6i.xlarge
- c6i.2xlarge
- r6i.large
- r6i.xlarge
- r6i.2xlarge
- key: kubernetes.io/arch
operator: In
values:
- amd64
- key: karpenter.sh/capacity-type
operator: In
values:
- on-demand
limits:
resources:
cpu: 100
provider:
amiFamily: Bottlerocket
subnetSelector:
kubernetes.io/cluster/mycluster: ""
securityGroupSelector:
kubernetes.io/cluster/mycluster: ""
ttlSecondsAfterEmpty: 300
ttlSecondsUntilExpired: 1209600 # = 14 days

apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
name: burstable
labels:
app.kubernetes.io/name: burstable
app.kubernetes.io/component: karpenter
spec:
requirements:
- key: node.kubernetes.io/instance-type
operator: In
values:
- t3.micro
- t3.small
- t3.medium
- t3.large
- t3.xlarge
- t3.2xlarge
- key: kubernetes.io/arch
operator: In
values:
- amd64
- key: karpenter.sh/capacity-type
operator: In
values:
- on-demand
limits:
resources:
cpu: 100
provider:
amiFamily: Bottlerocket
subnetSelector:
kubernetes.io/cluster/mycluster: ""
securityGroupSelector:
kubernetes.io/cluster/mycluster: ""
ttlSecondsAfterEmpty: 300
ttlSecondsUntilExpired: 1209600 # = 14 days

Observed behaviour:
When a pod is created it is provisioned by the burstable provisioner.
Thanks

Hey @jsmith97
Just to clarify, the Provisioner spec with name "default" is just an arbitrary name and not treated any differently when compared to other provisioners.  So, when Pod requirements and constraints match more than one Provisioner spec, Karpenter will sort them alphabetically and choose the first one.  In this case, it would be "burstable" per your

Thanks for the clarification Jim thought I must have miss-understood the docs.
Regards
Ben Smith

On 24 Mar 2022, at 16:04, Jim DeWaard @.***> wrote:

Hey @jsmith97
Just to clarify, the Provisioner spec with name "default" is just an arbitrary name and not treated any differently when compared to other provisioners. So, when Pod requirements and constraints match more than one Provisioner spec, Karpenter will sort them alphabetically and choose the first one. In this case, it would be "burstable" per your
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Ha, sorry I accidentally hit the "comment" button before I was ready.  Hopefully this comment makes more sense ^ ^.


Instagram issues

Tried to pull instagram posts from user 'cristiano', soccer player, but is giving some errors regarding the access token, isnt possible to get posts without being the own user from instagram account?

From what I can remember, Instagram only allows you to grab posts from the account that you have an access token to. Do you have access to the Cristiano account to create an access token?