Crashes with IllegalArgumentException

The app randomly crashes. Here's the log:
07-29 18:25:31.490 E/AndroidRuntime(32608): java.lang.IllegalArgumentException: Service not registered: tr.edu.iyte.caffeine.CaffeineTileService$e@fa762f6
07-29 18:25:31.490 E/AndroidRuntime(32608): 	at tr.edu.iyte.caffeine.CaffeineTileService.onStopListening(Unknown Source:8)

I'm not sure how to reproduce it, it seems to be random (it even crashes sometimes when Caffeine is off).

Should be fixed

Nope, still giving the same error.

Unfortunately, I cannot pinpoint the issue without sophisticated error reporting libraries. I removed the proguard optimizations so exceptions should be a little more clear. Can you update the app and continue using it, so I can understand what the problem is? Thanks.

I haven't had a crash since the latest update (been about 26 minutes since I updated it, according to Google Play). So that may have fixed it. I'll leave the issue open for like a day to be sure, but it sounds like it may be solved.

It still hasn't crashed, so I'm guessing it's solved.


[SPARK-27893][SQL][PYTHON][FOLLOW-UP] Allow Scalar Pandas and Python UDFs can be tested with Scala test base

What changes were proposed in this pull request?
After this PR, we can test Pandas and Python UDF as below in Scala side:
import IntegratedUDFTestUtils._
val pandasTestUDF = TestScalarPandasUDF("udf")
spark.range(10).select(pandasTestUDF($"id")).show()

How was this patch tested?
Manually tested.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12031/
Test PASSed.

Test build #106814 has started for PR 24945 at commit 2e939f1.

cc @viirya, @dongjoon-hyun, @BryanCutler

Test build #106814 has finished for PR 24945 at commit 2e939f1.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 sealed trait TestUDF

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106814/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12060/
Test PASSed.

Test build #106843 has started for PR 24945 at commit 8fe2474.

Test build #106843 has finished for PR 24945 at commit 8fe2474.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106843/
Test PASSed.

Thank you @viirya. This is not invasive at all. Let me merge it.
Merged to master.

Late +1, very nice!


[Custom Cell] Having problems implementing custom class.

New issue checklist

[x] I have read all of the README, documentation, and FAQ.
[x] I have reviewed the contributing guidelines. Confirmation: ____
[x] I have searched existing issues and this is not a duplicate.

What happened?
I am trying to add a view below the avatar image. I have read the FAQ and the Documentation and done everything according to the instructions but it still doesn't seem to work. Can you please help me out?
I have created 3 custom classes, subclasses of the classes:

JSQMessagesCollectionViewCell
JSQMessagesCollectionViewCellIncoming
JSQMessagesCollectionViewCellOutgoing

ChatCell, sublcass of the JSQMessagesCollectionViewCell
@interface QChatCell : JSQMessagesCollectionViewCell

@end
@implementation QChatCell

@end

ChatCellIncoming, subclass of the ChatCell. I have created a xib file (QChatCellIncoming.xib) for this as well which is a copy of the JSQMessagesCollectionViewCellIncoming xib file:
@interface QChatCellIncoming : QChatCell

@end

@implementation QChatCellIncoming

- (void)awakeFromNib {
    [super awakeFromNib];
    [self.messageBubbleTopLabel setTextAlignment:NSTextAlignmentLeft];
    [self.cellBottomLabel setTextAlignment:NSTextAlignmentLeft];
}

+ (UINib *)nib {
    return [UINib nibWithNibName:@"QChatCellIncoming" bundle:nil];
}

+ (NSString *)cellReuseIdentifier {
    return @"QChatCellIncoming";
}
@end

ChatCellOutgoing, subclass of the ChatCell. I have created a xib file (QChatCellOutgoing.xib) for this as well which is a copy of the JSQMessagesCollectionViewCellOutgoing xib file:
@interface QChatCellOutgoing : QChatCell

@end

@implementation QChatCellOutgoing

- (void)awakeFromNib {
    [super awakeFromNib];
    [self.messageBubbleTopLabel setTextAlignment:NSTextAlignmentRight];
    [self.cellBottomLabel setTextAlignment:NSTextAlignmentRight];
}

+ (UINib *)nib {
    return [UINib nibWithNibName:@"QChatCellOutgoing" bundle:nil];
}

+ (NSString *)cellReuseIdentifier {
    return @"QChatCellOutgoing";
}
@end

In the Chat Controller Class in View Did Load I do this:
self.outgoingCellIdentifier = [QChatCellOutgoing cellReuseIdentifier];
self.outgoingMediaCellIdentifier = [QChatCellOutgoing mediaCellReuseIdentifier];

[self.collectionView registerNib:[QChatCellOutgoing nib] forCellWithReuseIdentifier:self.outgoingCellIdentifier];
[self.collectionView registerNib:[QChatCellOutgoing nib] forCellWithReuseIdentifier:self.outgoingMediaCellIdentifier];

self.incomingCellIdentifier = [QChatCellIncoming cellReuseIdentifier];
self.incomingMediaCellIdentifier = [QChatCellIncoming mediaCellReuseIdentifier];

[self.collectionView registerNib:[QChatCellIncoming nib] forCellWithReuseIdentifier:self.incomingCellIdentifier];
[self.collectionView registerNib:[QChatCellIncoming nib] forCellWithReuseIdentifier:self.

incomingMediaCellIdentifier];
And in the cellForItemAtIndexPath function Ive done this:
- (UICollectionViewCell *)collectionView:(JSQMessagesCollectionView *)collectionView cellForItemAtIndexPath:(NSIndexPath *)indexPath {
    JSQMessagesCollectionViewCell *cell;

    if ([self incoming:messages[indexPath.item]]) {
        cell = [collectionView dequeueReusableCellWithReuseIdentifier:self.incomingCellIdentifier forIndexPath:indexPath];
        [cell.textView setTextColor:COLOR_CHAT_INCOMING_TEXT];
        return cell;
    }
    else {
        cell = [collectionView dequeueReusableCellWithReuseIdentifier:self.outgoingCellIdentifier  forIndexPath:indexPath];
        [cell.textView setTextColor:COLOR_CHAT_OUTGOING_TEXT];
        return cell;
    }
}

When I go to the chat screen, the app crashes with the following error. It does the same for the avatarContainerView in the QChatCellIncomming xib. I checked the xib file I cant find "TtC5Q_Fix17QChatCellOutgoing" anywhere in the project and the avatarContainerView is correctly connected :
Unknown class _TtC5Q_Fix17QChatCellOutgoing in Interface Builder file.
*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<UICollectionViewCell 0x7f821cd42a80> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key avatarContainerView.'

Hey @OyaSaid
Just as a side note you probably do not need to do this subclass if you are not actually doing anything different
@interface QChatCell : JSQMessagesCollectionViewCell

@end
@implementation QChatCell

@end

you can just:
@interface QChatCellIncoming : JSQMessagesCollectionViewCell

The actual issue is probaby rooted in this

ChatCellIncoming, subclass of the ChatCell. I have created a xib file (QChatCellIncoming.xib) for this as well which is a copy of the JSQMessagesCollectionViewCellIncoming xib file:

By doing that ie (copying the file) You may have missed changing the Class. I have made this mistake many times before and the error message is quite misleading. 😤
So if you open up Xcode and open your  QChatCellIncoming.xib select the cell itself in the interface builder

Then look at the right panel IE(Utilities Panel) select the "identity Inspector" looks like this:

And Change your class from JSQMessagesCollectionViewCellIncoming

To your class name QChatCellIncoming Now your UI knows which code is backing it and doesn't get confused 😨.
Then clean and run and it should solve that issue.
Let me know if you have more issues 🖖🏽.

Hello MacMeDan,
The cells in the xibs are both QChatCellIncoming and QChatCellOutgoing accordingly.
Also, I know that at the moment there is nothing different. I was trying to get it to work first without any new things before adding my own view.
Thanks,
Oya

Ya @OyaSaid will do.
That no good that you still cannot get it running. Let us know if there is anymore information that narrows down where this may be located and maybe someone else has run into the same thing. 🖖🏽

@OyaSaid that error which you mentioned usually happens when you have a 'dangling' connection from one of your IBOutlets.
When I say dangling, I mean that with the previous class it was well connected, but when pasted, it usually maintains some sort of reference to the previous class when the new class doesn't have that connection/property.
Can you put your cells in the sample app and reproduce it?

Ahh yes I thought I had seen it before. If you open your connections inspector on the right tab you can see if you have any that are broken. here is a screen shot of mine. If the dot on the right is a dash. that means it is broken and should be deleted and reconnected to what you expect.

Hey ,
All the connections are intact. Here is a screenshot from the incoming cell. I tried reconnecting them just in case. It didn't fix the problem.

Also here is the Identity inspector

One thing I find weird is that the module is none in the interface builder and in the source code is set as

Did you also check the JSQMessagesCollectionViewIncomingCell.xib

also I have some time right now to look at your project if you want to push it to a branch on github.

I will make a sample project with only the chat and send you message. I would appreciate it  if you can check it out when you have the time.
Thanks

@MacMeDan  Here is the test project. It would be great if you can check it out.
Thanks
https://github.com/OyaSaid/ChatExampleJSQ

will do @OyaSaid

Alright @OyaSaid I think I have found it. So after pulling down your branch and getting the project setup I got the error you were seeing. Poking around everything was looking correct and looking at the error it was giving me it was saying that it could not find the CellIn inside of the interface builder file. So I went to the CellIn.xib and deleted the class and Typed CellIn Again into the Class field. Made sure that it autocompleted and hit enter. Ran the project and it works. You had it correctly it was actually just Xcode that could not find the reference.

So to fix just go to CellIn.xib
Select the Cell
Check the property inspector
Delete the Class
Retype the Class CellIn
Make sure it autocompletes
Hit Enter
Build and Run

I know it seems like you may have already done it and in fact you have the correct thing in that field. Xcode is just confused and not looking up the correct Class. Let me know if you need more help.
Here is a screen shot of it running on my phone.

Let me know if you get it to work and good luck☘. 🖖🏽👾
Also let me know if you have more questions.

Oh my god thanks. I get the same screen now as you. But one question. As you can see in the code I add avatars and everything. Before I tried the custom cells the avatars and text were showing but now as you can see it does not even if the connections are all there. Why is that happening? How can I fix that? I tried by disconnecting and reconnecting the controls but that didn't fix the problem.

You probably just need to set the size of the avatar so the whole collection view knows how big they are. Let me take a look and see if there is an example, I know what it is in swift but ObjectiveC I have to look up 🙃.

So it looks like you just need to add something like this in your 'viewDidLoadof yourviewController`
    /**
     *  You can set custom avatar sizes
     */
    if (![NSUserDefaults incomingAvatarSetting]) {
        self.collectionView.collectionViewLayout.incomingAvatarViewSize = CGSizeZero;
    }

but don't use CGSizeZero


Sync to live

Docs Build status updates of commit 3fa2af8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/nuget-org/individual-accounts.md
:white_check_mark:Succeeded
View

docs/nuget-org/nuget-org-faq.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

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


Add cheap alternative to 'configuration' for checking only SDK version

Something like
inline fun fromSdk(version: Int, f: () -> Unit) {
    if (Build.VERSION.SDK_INT >= version) f()
}

inline fun ifSdk(version: Int, f: () -> Unit) { //whenSdk?
    if (Build.VERSION.SDK_INT == version) f()
}

Same behavior, what I can do with that, except use if (Build ....) ?

Any updates on this?


🍒[5.9][Executors] Clean up how we unwrap the local executor of distributed custom actor

Description: This removes a hacky workaround in how a "hop to" distributed actor is implemented.
Risk: Low, removes an internal underscored hack; The _ method could not have been used by any adopters yet.
Review by: @DougGregor @slavapestov
Testing: CI testing
Original PR: https://github.com/apple/swift/pull/64719

@swift-ci please test

@swift-ci please test


2.7.12 refresh metadata and instance failed

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.12
Operating System version: macOS
Java version: 8

Steps to reproduce this issue

dubbo-provider.xml

<dubbo:registry id="zkRegistry" protocol="zookeeper" address="<IP_ADDRESS>:2181">
        <dubbo:parameter key="registry-type" value="service"/>
</dubbo:registry>

<dubbo:metadata-report address="zookeeper://<IP_ADDRESS>:2181"/>

<dubbo:config-center address="zookeeper://<IP_ADDRESS>:2181"/>

start provider
print error log

2021-06-16 13:17:31,086 [Dubbo-framework-scheduler-thread-1] ERROR org.apache.dubbo.config.bootstrap.DubboBootstrap (DubboBootstrap.java:1172) -  [DUBBO] refresh metadata and instance failed, dubbo version: 2.7.12, current host: <IP_ADDRESS>
java.lang.NullPointerException
	at org.apache.dubbo.registry.client.metadata.ServiceInstanceMetadataUtils.calInstanceRevision(ServiceInstanceMetadataUtils.java:249)
	at org.apache.dubbo.registry.client.metadata.ServiceInstanceMetadataUtils.lambda$refreshMetadataAndInstance$6(ServiceInstanceMetadataUtils.java:272)
	at java.util.ArrayList.forEach(ArrayList.java:1259)
	at org.apache.dubbo.registry.client.metadata.ServiceInstanceMetadataUtils.refreshMetadataAndInstance(ServiceInstanceMetadataUtils.java:271)
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.lambda$registerServiceInstance$20(DubboBootstrap.java:1170)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

also 2.7.11  worked will, so i think this is a bug

I got the cause of the problem, in the org.apache.dubbo.registry.client.AbstractServiceDiscovery
2.7.11

2.7.12

ZookeeperServiceDiscovery depends on curator-x-discovery, but my project doesn't depends on, so doRegister cause exception, 2.7.12 exception first leads to null point exception

Please give your dependencies, it is generally recommended to directly rely on dubbo-registry-zookeeper.

Please give your dependencies, it is generally recommended to directly rely on dubbo-registry-zookeeper.

yes, add dubbo-registry-zookeeper works, but the error was confused, why not print class not found exception or log ?

Service Discovery model is no longer mantained in 2.7.x version, please upgrade to 3.0.x to using it.
If you found this issue still occurred in 3.0.x, please feel free to submit a new PR.

想使用dubbo这个RPC框架，但是参考官网中的测试用例和文档教程一直报错，各种报错，在排除了一堆后，还有一个始终无法解决的错误java.lang.NoClassDefFoundError: org/apache/curator/x/discovery/ServiceDiscoveryBuilder。看了你的评论后，加上了dubbo-registry-zookeeper依赖。终于正常运行了。非常感谢


Fix context menu positioning

Always get mouse position with get_global_mouse_position() because it takes fractional scaling into consideration.
Make menu appear to the right of the mouse like in other programs. (it would center on x axis before, the change is in Utils.gd)

Thanks!


1.6.1 Debian Package not work on Debian 11 Bullseye

postinst and postrm scripts contains trailing \r
greenbtc won't start due the error:
Error loading Python lib '/opt/greenbtc/resources/app.asar.unpacked/daemon/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /opt/greenbtc/resources/app.asar.unpacked/daemon/libpython3.10.so.1.0)

Please update to version 1.6.2

Please Install from deb files.Don't Install from source .

postinst and postrm scripts contains trailing \r greenbtc won't start due the error: Error loading Python lib '/opt/greenbtc/resources/app.asar.unpacked/daemon/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /opt/greenbtc/resources/app.asar.unpacked/daemon/libpython3.10.so.1.0)

Please update to version 1.6.3

The trailing \r problem persist also for 1.6.3


Webdriverio v8 errors resolving dependencies

Describe your question with as much detail as possible
noticed that the peer dependency is set to<EMAIL_ADDRESS>in the package.json
This means i am getting hard failures and  "ERESOLVE unable to resolve dependency tree" error when trying to install along side Webdriverio v8 (8.0.0-alpha.365).
If it's about a specific piece of code, try and include some of it to support your question.
As you can see the webdriverio versions included int eh main branch package.json are below the versions i am using
[ "dependencies": {
    "@cucumber/gherkin": "~22.0.0",
    "@wdio/logger": "~7.16.0",
    "@wdio/reporter": "~7.16.13",
    "fs-extra": "~10.0.0",
    "strip-ansi": "^6.0.1",
    "webdriverio": "~7.16.13"
  },
  "peerDependencies": {
    "@wdio/cucumber-framework": "7.x"
  },
  "devDependencies": {
    "@types/fs-extra": "^9.0.13",
    "@types/jest": "^27.4.0",
    "@types/long": "^4.0.1",
    "@types/node": "^15.14.9",
    "@typescript-eslint/eslint-plugin": "^4.33.0",
    "@typescript-eslint/eslint-plugin-tslint": "^4.33.0",
    "@typescript-eslint/parser": "^4.33.0",
    "@wdio/types": "^7.16.13",
    "babel-eslint": "^10.1.0",
    "babel-plugin-transform-function-bind": "^6.22.0",
    "coveralls": "^3.1.1",
    "cucumber-messages": "^8.0.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-import": "^2.25.4",
    "eslint-plugin-jsdoc": "^36.1.1",
    "eslint-plugin-prefer-arrow": "^1.2.3",
    "eslint-plugin-prettier": "^4.0.0",
    "eslint-plugin-tslint": "^3.1.0",
    "husky": "^7.0.4",
    "jest": "^27.4.7",
    "release-it": "^14.12.3",
    "rimraf": "^3.0.2",
    "ts-jest": "^27.1.3",
    "ts-node": "^10.4.0",
    "tslint": "^6.1.3",
    "typescript": "^4.5.4",
    "yargs": "^17.3.1"
  },]

Environment (please complete the following information):

Node.js version: v16.17.0
NPM version: 8.15.0
webdriver.io version: 8.0.0-alpha.365
@wdio/cucumber-framework version: 8.0.0-alpha.365
wdio-cucumberjs-json-reporter version: 4.4.3

Additional context
I noticed there was a previous issue (https://github.com/webdriverio-community/wdio-cucumberjs-json-reporter/issues/81) which is resolved but that specifically seems to be forcing a version of the framework that is causing the conflict as it it lower than 8.
Is it possible to tweak this in someway to enable me to successfully run an npm install and not get the dependency error?

The service needs to be tests in a v8 environment before we can release a version that includes v8 as compatible versions. If you like to help us with that please do. Thank you!

Can we upgrade the V8 dependency please -
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

@sankalpguptasymphony you are welcome to raise a PR 😉

@sankalpguptasymphony you are welcome to raise a PR 😉

I am not sure if I am not knowledgeable enough to do it but I'll give it a try once I am able to make Webdriverio 8 work for me.

I'm already working on it. I'm first updating all deps for V7 then will work on V8 support

I happened to have same issue. please help !

@PavanMudigonda
I'm already working on it in this PR, but all help is welcome

@wswebcreation / @christian-bromann - I am happy to be guinea pig on this if you have a version ready for testing on a running v8 set up

@Nemesischild would you be open to take @wswebcreation PR and bring it over the goal line?

Unable to deploy in Jenkin due to below error. Can you please help
While resolving<EMAIL_ADDRESS>[ERROR] npm ERR! Found<EMAIL_ADDRESS>[ERROR] npm ERR! node_modules/@wdio/cucumber-framework
[ERROR] npm ERR!   dev<EMAIL_ADDRESS>from the root project

it is because you are using the newest version webdriverio with old cucumber json reporting

@christian-bromann / @wswebcreation , I pulled the feat/support-v8 branch and made some changes. Also tested on my local WDIO v8 setup. Are you able to review this?

Any updates on how "CucumberJS JSON Reporter" compatible with with WDIO - v8?

I will release v5 with support for WebdriverIO v8. Please test it and let me know if any errors occur.

Sure, Thank you for the update. That will be very helpful.

@christian-bromann I tried upgrading to v5; however, after the upgrade while running the scripts I am getting below error
Failed launching test session: Error: Couldn't find plugin "cucumberjs-json" reporter, neither as wdio scoped package "@wdio/cucumberjs-json-reporter" nor as community package "wdio-cucumberjs-json-reporter". Please make sure you have it installed!
[0-0]     at initialisePlugin (file:///Users//<project_name>/node_modules/@wdio/utils/build/initialisePlugin.js:36:11)
[0-0]     at async BaseReporter._loadReporter (file:///Users//<project_name>/node_modules/@wdio/runner/build/reporter.js:178:30)
[0-0]     at async Promise.all (index 1)
[0-0]     at async BaseReporter.initReporters (file:///Users//<project_name>/node_modules/@wdio/runner/build/reporter.js:23:27)
[0-0]     at async Runner.run (file:///Users//<project_name>/node_modules/@wdio/runner/build/index.js:68:9)
[0-0] FAILED

@christian-bromann I tried upgrading to v5; however, after the upgrade while running the scripts I am getting below error
Failed launching test session: Error: Couldn't find plugin "cucumberjs-json" reporter, neither as wdio scoped package "@wdio/cucumberjs-json-reporter" nor as community package "wdio-cucumberjs-json-reporter". Please make sure you have it installed!
[0-0] at initialisePlugin (file:///Users//<project_name>/node_modules/@wdio/utils/build/initialisePlugin.js:36:11)
[0-0] at async BaseReporter._loadReporter (file:///Users//<project_name>/node_modules/@wdio/runner/build/reporter.js:178:30)
[0-0] at async Promise.all (index 1)
[0-0] at async BaseReporter.initReporters (file:///Users//<project_name>/node_modules/@wdio/runner/build/reporter.js:23:27)
[0-0] at async Runner.run (file:///Users//<project_name>/node_modules/@wdio/runner/build/index.js:68:9)
[0-0] FAILED

@christian-bromann Thanks for the upgrade.
I am getting below error while running it, this file is not present in node modules.
Error: Cannot find module '..\node_modules\wdio-cucumberjs-json-reporter\dist\reporter.js'. Please verify that the package.json has a valid "main" entry

I just pushed a patch with a fix and released it. Please let me know. Feel free to raise PRs with improvements at any time.


Fixes Get Demo button in header.

The Get a demo button is not doing anything, I cannot see any javascript attached to it. This adds the link to the Traefik Enterprise demo request form.

Close in favor of #51


Add Searx to Search Engines

Searx has many public instances, some run as Hidden Services.

https://github.com/CHEF-KOCH/ProjectX/commit/6ecf033f505a0aad7cf6e345393e1f7e6805c25f


Print the files that have been formatted successfully

This is a feature request/suggestion.
I would like ktlintFormat to print a list of files that has been successfully formatted similarly to how googleJavaFormat (Gradle task) does it. Example:
/home/odiferousmint/foo/bar.java: formatted successfully
/home/odiferousmint/foo/baz.java: formatted successfully

I tried to set verbose to true but that did not help.
If this is related to org.jlleitschuh.gradle.ktlint, then feel free to close the issue.

I submitted it here as well: https://github.com/JLLeitschuh/ktlint-gradle/issues/372 just in case.


Onboarding

[ ] Set up profile
[ ] Select relays
[ ] CTA to add space or browse spaces

This should be done using an external micro-app


How to collect and send gateway object including the IoT Device Objects resource

Question
Small question I guess; using the Leshan client, how can I make sure the IoT Device Objects resource (3) of the Gateway object (25) is present and filled?

I'm not sure I get the question.
Could you give me some context ? What are you trying to achieve ?

Yes exactly, with the leshan cliënt demo.

Ok you launch your leshan-client-demo than use command create 25, then you see the object but the resource 3 is empty ?
leshan-client-demo does really implement object 25.
When you call create 25, it will just create a dummy object with some random value depending of the type of the resource.
See : https://github.com/eclipse-leshan/leshan/wiki/Adding-new-objects#leshan-client-demo (this is documentation about v1.x but this is still mainly true for 2.x)
You can have a look at the DummyInstanceEnabler.
It seems for this multiresource corelink resource currently leshan demo doesn't provide any default resource ..
We can try to generate a random value for corelink resource if needed ? but keep in mind this is just a dummy object.

I was just wondering if it was possible to set it somehow. No need to do any code changes 😏
I think I can manipulate the payload server side to populatie the resource.

I think I can manipulate the payload server side to populate the resource.

I'm not sure what you have in mind but this is about sending a WRITE request from LWM2M server to Client. It seems this will not be possible because resource /25/?/3 is Read only.
See : https://github.com/OpenMobileAlliance/lwm2m-registry/blob/76aaf5becb46daf1acd859fb45ef50c005eb6da4/25.xml#L90-L99

No need to do any code changes

Currently we generate value for all type except coreLink resource, so it could make sense to me to change it.
There is also an option in client demo :
      -fb, --factory-bootstrap=<LwM2mPath=String>[,<LwM2mPath=String>...]
                             Can be used to initialize existing resource with
                               custom value.
                             LWM2M Text Content format encoding should be used
                               for resource value
                             E.g. to change Short Server ID :
                              -fb /0/0/10=1234,/1/0/0=1234

This allow to initialize client with custom value.
But for now this doesn't enable new object automatically maybe this could be modify to allow that :thinking:
Let me know if one of those changes could fit your need ?

No I needed to send the gateway object to my lwm2m server, not from the server to the client :-)
I already managed to manipulate the sample message from the demo client to my needs, so as far as I'm concerned this can be closed.

Note that Leshan doesn't really support the Gateway use case, so you could face some limitation at some point.

so as far as I'm concerned this can be closed.

Ok I will let this open as possible enhancement for client demo.
But I will not work on this now, as I understand you don't really need that improvement.


[Epic] Ghost and i18n

Project description: Ghost is currently pretty much UK-based English-language only, and has barely any features to account for timezones, locales, languages, alphabets, keyboard layouts or anything else that isn't UTC/English in either the admin or in themes. Even the USA folks luck out, sorry! All this is set to change with full support for multiple locales and languages across the admin and your blog posts. Throughout the Ghost GitHub, support for all of these sorts of features is referred to as i18n (internationalisation).

Currently, Ghost effectively doesn't work properly unless you're writing in English or something very similar. Throughout the application, from the ember admin, to the API and even down to themes there are things missing which make it hard to use Ghost if you aren't English speaking.
This issue is intended as a placeholder to keep track of all the different places where we know we need to add i18n support so that it becomes possible for anyone to publish content comfortably in their own language and locale.
i18n for Ghost falls into 2 broad categories
1. Publish content in your language/locale
We need to make it possible for anyone to create a blog and publish content which is 100% in their language. This includes extending theme helpers, adding support for non latin-standard chars in URLs and other files, and many other things.
2. Use Ghost in your language/locale
Much less important, it would be great for our users if they could have the admin UI appear in their language, with a tailored layout and specific fonts.
Features and Support
The following is a list of things we know we need to do / make possible / add support for:
Publishing

Level 1: blog language setting
Level 2: post language
customisable permalinks where english words are used
set <html lang="?">
add language output in JSON/LD
non-latin chars in slugs
non-latin chars in urls
non-latin chars when uploading files
non-latin chars handled by words and characters features of excerpt/content helpers
non-latin chars in generated heading id attributes
non-latin chars supported fully in editor
customisable permalinks for /tag/, /author/, and /page/ urls
locale dates in themes (moment.js language support)
different plural structures in the {{plurals}} helper
extensible rules for what constitutes paragraphs and words in the excerpt and content helpers
extensible rules for what constitutes paragraphs and words in the editor

Admin UI

translate the Admin UI
locale dates when entering published at date
register different fonts for use in the admin interface and specifically the editor
extend the admin interface with layout tweaks for different languages
install language packs which provide the translations and layout tweaks
non-latin chars handled by word count and counters on bio/description fields
ability to include extra character sets in admin via language packs

i18n and Apps
Not all features and support for other languages will exist in core. Different writing systems require very different layouts and as such it should be expected that if your language is significantly different to English, that an App may be required to make Ghost work for you.
The advantage of splitting functionality this way is that we don't have to design one UI that works for all languages and writing systems. Furthermore we don't have to bloat the core of Ghost with features that will only ever be used by one specific group. Language packs which add translations for the Ghost admin UI could also add layout tweaks, better fonts, and other modifications to make Ghost work just as well for other languages as it does for English.

The source code still references a related setting that is no longer used: forceI18n. Quoting @ErisDS: “we haven't  ever removed a setting before and it would require a bit of faffing around to check it doesn't have unintended sideeffects if you remove it”.
So the plan is to let it untouched for now, “and if you guys find a use for the setting, use it, else we'll look to remove it as part of project”.

Anyone & everyone following along with this should read and get involved with the proposals outlined here: https://github.com/TryGhost/Ghost/issues/5345

What is the current status on setting a post as a specific language/locale?

How far away are the i18n support for Ghost?

@aludvigsen The task is marked as stalled in the Trello roadmap.

:+1: Would love this :(

Don't know if this is an appropriate place for this, but I saw those, who were looking to solve the date language issue on posts. Go figure, this is the workaround:
open core/server/helpers/ghost_head.js and before module.exports = ghost_head; line add something like moment.locale('ru');

Not sure if this is included in "Level 2: post language" but I would like to be able to have multiple version of a single post in different languages, and Ghost would serve up the appropriate version depending on the user's locale (with the ability to override).

I'm agree with @Tyriar. This is the only functionality I missing since I've been on Ghost

Stopped using Ghost about a year ago due to only being able to use it for English-based sites. Still no progress? :(

@Nettsentrisk No progress since November 2012.

As a Ghost Kickstarter backer I can't help but feel a little left out not being able to use Ghost in production even once, because of the lack of localization.

I understand the replies here come from a place of frustration and a desire to see this implemented, however the comments here are achieving the opposite effect.
Anyone who comes to this issue with the intention of contributing will be put off by the negativity in the comments. This article does a great job of explaining what it feels like being a maintainer  on GitHub. It is extremely demotivating to put in tonnes of work only to have people rock up to GitHub to moan about all the things we haven't done or got wrong.
Moving forward:
This is an enormous issue, relating to 3 different concepts that people commonly mix up:

translating the admin UI
localising a theme
being able to publish content in multiple languages

We have said these aren't features the core team plan to build in the near future, instead looking for people from the community to lead the effort. We had a page on ghost.org dedicated to it for over a year, and we've had an #i18n channel in Slack for even longer.
If you want to see this implemented, then contribute something. Positivity, ideas and encouragement are all contributions. Rally together a group of people who could make this happen, use the tools we've provided and work with us to affect a change.
For now - I am going to close this issue. It serves only as a beacon of frustration for a feature set that does not exist, and that really belongs on ideas.ghost.org. If an individual or group wants to work on one of the 3 aspects of locatisation/internationalisation, we can raise a new issue to cover the spec of what they want to build, as happened with #5345.

Grav is an alternative to Ghost and has multi-language support. I think I will migrate to this solution. In terms of market share, Grav will catch-up Ghost at the end of 2017.


Update QueryEditor.js

No need for using useCallback here, since it's memoized by default
https://kentcdodds.com/blog/usememo-and-usecallback

At other places in this code base, you can see that I don't wrap handlers in a useCallback by default.
These specific cases that you've mentioned, are required. Without them, this component will get stuck in a render loop.


Fixed issue where server could not start after manually stopping it

Steps to reproduce:

Open csharp file foo.cs associated with multiple solution files
_ foo.cs
_ foo.sln
_ foo2.sln

Server will then be started (provided autostart flag is set to 1)

Stop server (:OmniSharpStopServer)

Try starting server again :OmniSharpStartServer

Observed result:
Prompt will be empty :
> sln:
Server is not started
Causes:
See https://github.com/OmniSharp/omnisharp-vim/blob/69a43ce9db692bc7d11fcac54df4c0c518c559c6/autoload/OmniSharp.vim#L476
It is checking variable g:OmniSharp_running_slns which is not cleared when server is stopped.
Solution:
Clear g:OmniSharp_running_slns when server is stopped.

Well, thanks!


I can hear players, but soooo low

Hi, i want to rise the voice chat volume because, when i talk by a radio i hear players, but soooooo low

Read the README.


Update cats-effect-laws to 2.4.0

Updates org.typelevel:cats-effect-laws from 2.3.3 to 2.4.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v2_4_0?sha=series/2.x

Documentation:

https://github.com/typelevel/cats-effect/blob/v2.4.0/scalafix/README.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect-laws" } ]

labels: test-library-update, semver-minor, scalafix-migrations

Closed in favor of #346


[Bug]: No error raised when the rootPath is wrong

Current Behavior
My Milvus is deployed by helm, so the default rootPath is by-dev.
But I refer to the following command, set the rootPath as instance name.

However, it does not raise any errors. It can not show any info when I type show collections(already create many collections).
This makes me confused: It does not work, but there is no error happened.the
Expected Behavior
Raise an error when the config is wrong.
Steps To Reproduce
No response
Environment
No response
Anything else?
No response

Good point. Currently Birdwatcher cannot detect rootPath was a valid one or not.
We could add a cheap check at least that whether rootPath prefix exists or not

Pr merged. Could you please check?
/assign @zhuwenxing
/unassign


Removed duplicate code in KylinMeta

Removed duplicate code in KylinMeta

Can one of the admins verify this patch?

Codecov Report

Merging #652 into master will increase coverage by 0.1%.
The diff coverage is 9.09%.

@@            Coverage Diff             @@
##             master    #652     +/-   ##
==========================================
+ Coverage      25.7%   25.8%   +0.1%
- Complexity     5976    6011     +35
==========================================
  Files          1382    1382
  Lines         82144   82147      +3
  Branches      11509   11511      +2
==========================================
+ Hits          21112   21198     +86
+ Misses        58985   58903     -82
+ Partials       2047    2046      -1

Impacted Files
Coverage Δ
Complexity Δ

...src/main/java/org/apache/kylin/jdbc/KylinMeta.java
53.84% <9.09%> (+3.84%)
15 <1> (+1)
:arrow_up:

...he/kylin/job/impl/threadpool/DefaultScheduler.java
74.41% <0%> (-2.33%)
12% <0%> (ø)

...eam/core/storage/columnar/DataSegmentFragment.java
57.37% <0%> (-1.64%)
17% <0%> (-1%)

...a/org/apache/kylin/common/util/HiveCmdBuilder.java
81.08% <0%> (-1.12%)
12% <0%> (ø)

...lin/dict/lookup/cache/RocksDBLookupTableCache.java
75.38% <0%> (-1.03%)
27% <0%> (ø)

...rg/apache/kylin/cube/inmemcubing/MemDiskStore.java
69.6% <0%> (-0.61%)
7% <0%> (ø)

...a/org/apache/kylin/source/hive/MRHiveDictUtil.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...apache/kylin/source/hive/CreateMrHiveDictStep.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...lin/source/hive/CreateFlatHiveTableByLivyStep.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...urce/hive/RedistributeFlatHiveTableByLivyStep.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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


Complete Testing and Acceptance Plans Section

Separate Issue for updating the repository and as such manually closing this.


WIP: Windows support

I thought I'd start looking into this a little bit and fixed some cross-env issues in npm scripts and also figured out why #290 happened. The backslashes in Windows get escaped away in webpack-plug/src/apply.js when building the script that's returned as a string.
I'm now able to run npm run example:dev without errors and localhost:8080 loads, unfortunately at localhost:8080/carte-blanche i'm getting a 404 and am a little stuck as to why that might be.
I see the basePath used in a few places and it should maybe always have a forward slash or at least sometimes (anything that's a URL obviously). Anyone have ideas as to the next steps?
npm run example:dev:iron also didn't work for me, but maybe that's related. In any case i'd say that's a battle for another day.

Woah, awesome @novascreen, will take a look shortly!

@mxstbr do you have windows machine to test it?

@mxstbr do you have windows machine to test it?

Sadly I realized today that my old Windows machine doesn't boot anymore. :cry: This looks good code-wise though!

could you use this?
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

@novascreen I'm very interested in this too, let me know if I can be of any help!

One small comment then we can merge this, cross-env is definitely the right way to go! Thanks!

@novascreen I've made some findings about the 404 problem.
It seems that the assets are emitted by carte-blanche using path.join to determine their destination path, which would be \path\to\file on windows instead of the expected path/to/file.
To fix this I tried to use path.posix in few points and this seems to fix the problem, now I can see carte-blanche's dashboard with a list of components on the left.
Anyway there are still 404, I guess that those come from the react-plugin instead, those calls fails: http://localhost:8082/variations/srccomponents/Header.js and thus I don't see my component rendered.

That's great news @ingro i'll check this out tonight (i'm 6h behind you guys), could you share your work as a patch or a branch in your own fork?
@mxstbr i'll move that function into utils and write a test tonight.
 So when you build that script as a string all that backslash does is escaping the next character (in the example R of Repos and r of react), and the end result is C:Reposreact-boilerplate. That's why I duplicated the backslashes.

I'm a little noob with github, I'll try with creating a new branch on a fork asap!

@novascreen that's the commit

Awesome, this is going to be good!

great, thanks @ingro

I'm still a little puzzled on how the list of components is generated and handed to the client, maybe @mxstbr could give us some insights on that part? I feel that the remaing problems lies there.

hey @ingro, i think i found all the places where we needed to enforce forward slashes
@mxstbr i also made sure that tests are passing on Windows. Let me know if you're ok with me adding that slash dependency and also changing some of your tests.
Is it normal that a variation takes 5+ seconds to load into the iframe?
That Travis CI build failure doesn't seem related to anything I did, does it?

Great work @novascreen , I'll check it out immediately!

I can confirm that now it works, although I too can report major slowness when creating and updating variations, but I don't know if they are related to windows.

I just fails due the flow linting which is fixed in this PR https://github.com/carteb/carte-blanche/pull/379

btw don't worry about it being slow on Windows. Running the development environment of carte blanche uses inline-source maps which leads to huge files that take a while to load

I had to fix a merge conflict and therefor opened another PR that I merged: https://github.com/carteb/carte-blanche/pull/381
Thx a lot @novascreen & @ingro - awesome work 👌


Enable buy and sell for decred and fix wallet bug on ios

Issue Number (if Applicable): Fixes #
Description

This PR fixes a bug where existing decred wallets are not found after the wallet app is restarted on ios.
This PR enables buy and sell onramp. Note: sell doesn't work rn (from my end) but there's a buy option for decred.

Builds on: #12
Pull Request - Checklist

[x] Initial Manual Tests Passed
[x] Double check modified code and verify it with the feature/task requirements
[x] Format code
[x] Look for code duplication
[x] Clear naming for variables and methods

Note: I've not been able to make onramper select decred as the default currency.

I don't think 44556dd is the right way to handle this bug.
I think we should just make the id a combination of txid:vout, so like "50a595cae0c57244d42a03725948c41041159ddc4f365171cb9fd8084a8ed04d:0", then they are all unique.

I think we should just make the key a combination of txid:vout, so like "50a595cae0c57244d42a03725948c41041159ddc4f365171cb9fd8084a8ed04d:0", then they are all unique.

Errm, okay. I'll try your suggestion. However, we still need to set output addresses, I think.

However, we still need to set output addresses, I think.

I could be wrong but I dont think we will. The problem was having different outputs using the same id. The values are already divided up by dcrwallet and we don't need to worry about adding them together. Really the map is not transactions but UTXO which is confusing but we should leave the name anyway imo.

Thanks this looks correct to me!
Two things I noticed, one is pending transactions are not being confirmed. Another is can you change the libwallet version in the android script as well?

one is pending transactions are not being confirmed.

They are replaced.

It seems the ui is not updating because the id is not the same as the map id. Can you not add vout to the transaction info and just make the id the txid:vout? You can make dcrdata work in lib/view_model/transaction_details_view_model.dart with return 'https://dcrdata.decred.org/tx/${txId.substring(0, 64)}';

Changes have been added to the upstream pr so closing.


ongoing test-e2e-linux and test-example-linux flakes

We are still seeing sporadic test flakes in the test-e2e-linux and test-example-linux jobs, e.g.:
https://github.com/projectcontour/contour-operator/actions/runs/1181920017
https://github.com/projectcontour/contour-operator/actions/runs/1180861979
https://github.com/projectcontour/contour-operator/actions/runs/1180638912
It'd be really nice to continue to try to get rid of these.

example tests seem a lot more stable since we moved them to go 🤞🏽

And seems like maybe that data race you fixed cleaned up the E2E's too

I'm going to close this out, things have been pretty stable for awhile now, nice work @sunjayBhatia!


Create a memory test to verify we don't keep using more memory

Given the work done on this PR here:
https://github.com/microsoft/vscode-python/pull/11835
We can potentially track memory inside our tests.
We could use this to write a test that verifies memory isn't growing over time.

Rich Chiodo

I had originally added code that would track memory usage and output statistics. I was thinking more of just outputting the statistics on every build and we could manually check the growth. Then you could determine which changes caused memory growth spikes. This is similar to how when we were all on the Visual Studio team (well okay not all of us, but Ian, Jim and I) did RPS tests. RPS tests also flagged an error if the growth was off by some percentage, but I think we can skip that part.
You'd track statistics say for each functional test run, or maybe vscode tests run (as those are more realistic)

Going to write a simple test that

Opens a notebook
Runs a cell
Asks for semantic tokens
Checks memory usage against last time. If more than double I'll fail the test. Not sure how noisy it will be yet, but will log the results as an artifact


Merge Develop into Master

This relies on https://github.com/O3Labs/ont-mobile/pull/12
Compiles and works in neovmUtils.
Implemented:

ontid
additional Ont RPC functions
Fix to neovm transaction building
ont account creation
address from public key

@apisit all this stuff is working. We're currently using it in the Ryu SDK in production with no problems.
This PR also enables bitcode in apps that use neo-utils which is pretty cool

Thanks @apisit


Feature to not exclude path even if parent was excluded, similar to what rsync does

Output of restic version
0.12.0
What should restic do differently? Which functionality do you think we should add?
From what I could see, restic doesn't have a feature similar to rsync's:
--include=PATTERN don't exclude files matching PATTERN
which ensures PATTERN will always be included even if the parent folder might have been excluded for example. Could this be added?
What are you trying to do? What problem would this solve?
This is very helpful if there's a directory containing many unneeded files (which must be excluded), and a single or a few files that need to be included.

Thanks, but this is already tracked in #233 so I'll close this one as a duplicate :)


Pod updates do not impact EndpointShardz

EndpointShards includes info from pods, but is not updated on pod change. For the most part ,this is ok... most of the fields are immutable anyways. However, labels can change. If a pod dynamically changes its labels, it is NOT seen in the EndpointShardz, which may impact DR subsetting
fyi @ramaraochavali @hzxuzhonghu

This is because we do not support label updates originally. Later I added labels update for proxy, this is to do that for endpoints.
I think it is a little similar as waypoint update

Is pod dynamic label update a common use case - I am not saying we should not fix this, but just asking

It can be updated by CI/CD, not very rare.

/not stale

not stale

cc @dddddai this issue is just  what you asked

This impacts ambient fairly severely. A pod can dynamically be added or removed from ambient, which requires us to switch the endpoint to enable or disable HBONE

I had a fix in https://github.com/istio/istio/pull/50323/files#diff-aad0a6de97a6c10ad212a2089a5b9f2abae57a8b2e5f6d0ee2c8761d1fec61ccR56, but I think its not quite right. The fix should not be scoped to ambient ideally.

There is not a very perfect way to do this imo. For a proxy, it constructs metata with its lables. This is really a static ones, but later a user can change that label. Now we donot support update the labels to proxy.  This will greatly increase pilot load even if do that for pure endpoints


OutOfMemory error on opening file via IsoFile

Constantly getting OutOfMemory error on any MP4 file written by Android device when opening file via IsoFile. Tested on MP4 files created by default camera apps Samsung S5 Android 6.0.1 and Nexus 6p Android 8.0.
new IsoFile("my.mp4");
File to test https://www.dropbox.com/s/3jdd5dii1in0o5u/mp4parser_isofile_outofmemory.mp4?dl=0
Using org.mp4parser:isoparser:1.9.31 on Android.
ISO Viewer app v2.0.2 also has this issue.
Caused by: java.lang.OutOfMemoryError: Failed to allocate a<PHONE_NUMBER> byte allocation with 4016136 free bytes and 508MB until OOM, max allowed footprint 8032272, growth limit 536870912
                                                                         at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:54)
                                                                         at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:49)
                                                                         at java.nio.ByteBuffer.allocate(ByteBuffer.java:261)
                                                                         at org.mp4parser.support.AbstractBox.parse(AbstractBox.java:96)
                                                                         at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:104)
                                                                         at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
                                                                         at org.mp4parser.boxes.iso14496.part12.MetaBox.parse(MetaBox.java:82)
                                                                         at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:104)
                                                                         at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
                                                                         at org.mp4parser.support.AbstractContainerBox.parse(AbstractContainerBox.java:75)
                                                                         at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:104)
                                                                         at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
                                                                         at org.mp4parser.IsoFile.<init>(IsoFile.java:57)
                                                                         at org.mp4parser.IsoFile.<init>(IsoFile.java:44)

Looks like this is the same issue https://github.com/sannies/mp4parser/issues/240

mp4parser is parsing the files according to ISO14496-12 spec. However, the file is formatted according to Quick Time File Format Specification. The key difference is that in ISO format, the 'meta' box contains two additional fields that precede the 'hdlr' box, namely,  8-bit version and  24-bit flag values. As the result, the data is shifted by 4 bytes.
The crash happens when the code tries to parse metadata ('meta') box. According to the ISO14496-12 format, the first metadata sub-box is the handler reference box ('hdlr'), which (as all boxes do) should start with 4-bytes representing the length. However, because of the 4-byte shift, the parser points to 'hldr' ASCII bytes (which equal to<PHONE_NUMBER>) and interprets them as length. That is the reason why you see: java.lang.OutOfMemoryError: Failed to allocate a<PHONE_NUMBER> byte.
The solution could be to determine the type of the metadata format and parse it accordingly.

TinyCam, thank you for the analysis. This problem has been frustrating me for a long time. I believe this https://github.com/sannies/mp4parser/issues/139 is the same problem. I wonder how I can tell which format. Perhaps I can get some time to work on this and submit a patch.

It should be possible to reset the ByteBuffer position back 4 bytes in MetaBox.parseVersionAndFlags() if the next 4 bytes represent 'hdlr' after reading the version and flags. For extra verification, the 9th to 12th bytes after 'hdlr' should contain 'mdta' (see Metadata Handler Atom].

I just ran in to this issue today. Is there anyway for us to merge in the pull request with the fix?

@YitianTonyXu can you please confirm if 1.9.37 - #288 fixed this issue?


Operator SDK doesn't processes items in workqueue simultaneously

I see that operator sdk is processing items in workqueue one after the other.
For example in the sample operator I am working on, the reconciler is taking 5 seconds to process the item in workqueue but items are being added to workqueue every 1 sec. So even though though the 3rd item is added at the end of 2 sec, it is not processed until first 2 items are processed which approx. takes 10 (5+5) sec to process.
So, I am looking for a way to see if operator SDK provides a way to process these items simultaneously as and when they are added.

@BaluDontu Check out the manager.Options field called MaxConcurrentReconciles. You can set this in your controller setup code.

If this doesn't solve it for you, let us know and we can re-open.


Updated ash from v0.37 to v0.38

I updated the ash and other dependencies to the latest version (Except Wayland-client and Wayland-protocol).
Added anyhow (version = "1.0") to fix some of the issues which normally would require writing a new code.
I just tried my best not to let any errors occur, but that doesn't mean the code is functioning properly.
As far as I tried, I don't seem to have faced an issue, but Please rewrite the code however you fit @maximbaz
Again Thanks for your help

Wait really sorry
Forgot about cargo.lock

I am sure you may be getting notifications every time I change something here. (Including my mistakes)
Again, I am really sorry for my mistake, but I have updated it successfully.
Please check the code at your leisure time.

Hello, @maximbaz
Just a quick question,
When keeping wlroots as a compositor, will it start detecting a white background and a black background immediately?
As soon as the program starts running,
Because after upgrading ash to v0.38
The program seems to work like before, except when I run it with wlroots, it won't show any error, but it doesn't seem to change anything when going from white to black background either.
I don't know whether I made a mistake where I forgot about considering the wlroots while changing the vulkan.rs code or something else occured.

Hello, I think it should react immediately, but to avoid any potential misconfiguration or setup issues, could you try with the main branch to see if vulkan+wlroots reacts there?

Hello @maximbaz,
Thank you for your immediate reply.
I just tested the Main branch as well as the one i updated ash to v0.38
And for some reason, both are now properly.
I have tried a couple of times, and it shows the same error thrown at me in the main branch luma.
My assumption is that i was running both the wluma (AUR) as well as the cargo run which seems to mess up with wlroots at that moment.

Sorry to ask but
I just saw https://github.com/maximbaz/wluma/pull/86#issuecomment-2320923641
and just curious,
was his/her code working?
If it is, I won't mind closing this pull request.
Since I made it not knowing someone else had already fixed the issue.

Unfortunately I'm in a position where I actually can't test vulkan part as my current hardware does not support vulkan 😭 So I don't know if it actually works. In the interest of getting something merged, I would suggest you continue the PR, especially as you have the ability to run it and verify that it works, and compare with the main branch. I think it's totally worth it to compare your ideas with how they done it in their patch, if nothing else then just in the interest of learning, but especially if you get stuck on something.

Unfortunately I'm in a position where I actually can't test vulkan part as my current hardware does not support vulkan 😭 So I don't know if it actually works. In the interest of getting something merged, I would suggest you continue the PR, especially as you have the ability to run it and verify that it works, and compare with the main branch. I think it's totally worth it to compare your ideas with how they done it in their patch, if nothing else then just in the interest of learning, but especially if you get stuck on something.

Yeah, Absolutely! 😀 I'm eager to see Wluma work on Hyprland, but more than that, I am happy that I am able to learn rust indirectly from doing it.

Let's also use ~1.0 as other deps do - by the way, love the idea of trying this crate out 👍
In a separate PR after this is merged, I would totally be open to considering replacing the std::Result with anyhow::Result, i.e. that all the functions get changed from Result<T, Box<dyn Error>> to anyhow's Result<T> - should make it a lot easier!

Phew! I initially thought You wouldn't like the idea (I assumed that using anyhow could have some other backlash in the Wluma program), so I spent days trying to do it one by one, but, in the end, I gave up and used it anyhow, but I'm glad you liked my idea ☺.

not that it is super important, but just reading the ash changelog, I think the devs intended you to replace ::builder() with ::default() and keep all the other code as is, i.e. in this case:
        let app_info = vk::ApplicationInfo::default()
            .application_name(&app_name)
            .application_version(WLUMA_VERSION)
            .engine_name(&app_name)
            .engine_version(WLUMA_VERSION)
            .api_version(VULKAN_VERSION);

I see, so it was intentionally done; I just found it somewhere as a reference to use default (read it in the changelogs as well), so I tried using it, and there were no errors being displayed, and it worked successfully. So I didn't question it. (I even asked ChatGPT for confirmation, but... well it failed.)

I think you might have lost one of the two extensions here, and from the patch you linked earlier today I think they found a more correct patch in this case:

Ah! My bad, its not that i forgot about this one but i couldnt find the updated version for KhrExternalMemoryCapabilitiesFn and i think i missinterpretted it and assumed that both are inside vkGetPhysicalDeviceProperties2 🫣.
But still Thank you for finding that error will fix it soon.

From the quick glance, I think I prefer the changes made to this file in #86 (comment) , except I like your solution to the error types, not to introduce a ton of .expect() calls. Would you like to try to converge your work and the work in #86 (comment) ?

Yeah, Sure! I will do that in a couple of days.

Also Just wanted some tip for you @maximbaz , How do you usually find which one is which after the dependency is updated.
For the past few days i have been struggling to figure out which one is which and what can be used for the replacement as such.
Since i was trying to update wlroots.rs, it became so messy to the point, i had to restart all over again today, just so i can make sense out of it 😵💫.

Could you explain a bit what you mean by which is which after the dependency is updated? With an example, perhaps? :upside_down_face:

Could you explain a bit what you mean by which is which after the dependency is updated? With an example, perhaps? 🙃

Like in wlroots.rs, EventQueue is still EventQueue (Small changes)
However, they removed Main in v0.30 for Wayland Client, And I have to figure out ways to make it work with proxy (Totally changed)
or
Display, which was used in v0.29.5; instead of that, I am now having to use Connection for v0.31 (Mediocre change)
Stuff like that is where I have to read the entire documentation to see if there is any difference. Takes a lot of time, and even if I read, sometimes I still don't get what I need to do next.

Ahh I see what you mean now... There is no easy answer, I would start from the changelogs or release notes if they are there, and fall back to normal documentation otherwise. Many dependencies follow semantic versioning scheme, where just by looking at the version change from e.g. 2.5.3 to 2.6.0 you'd know that no changes to the code are necessary and that 2.6.x only brings new features and doesn't break any existing ones, buut as you have already figured out with wayland libs, sadly not everything follows it.

Ahh, I see; thanks for your explanation. I actually didn't know properly about semantic versioning till now. (Probably because most don't follow it)

Hello @maximbaz, I have re-updated Vulkan.rs code
And I think everything properly has been re-written.
I don't think there should be any error here (I have become thorough with the Vulkan.rs code)
But could you still check once in case I missed something?

Let's revert to ok_or, potentially map_erroring it if needed.

Thank you for pointing out everything in detail. I will do just that now! 🔥

That comment seems useful even if I don't remember the defaults 😅 Lets keep it 🙏

Oh sorry!😅 Will change it back!

It's okay to keep it for now, but I suppose you want to undo this before final merge 😉

Yeah will do. 😀

Do you want to remove these commented parts, here and in a couple of other places, or you are experimenting with them?

Ah! Sorry, I forgot about that,
I was commenting out some of my code in case if while changing my code it breaks I can come back and revert it.

Hey @maximbaz , I have successfully made all the changes you asked to revert back.
Can you again reconfirm whether I missed something or made some mistake?

Okay I am back to Doubting myself,
Do you want me to send you a screen recording later? (Or should I send something like verbose logs of wluma while running)
To confirm it's working?

export RUST_LOG=trace
cargo run

Run it with wlroots.
Look for this log lines:
https://github.com/maximbaz/wluma/blob/7184d0adb78775369163b1b222db15baa0748b7d/src/predictor/controller.rs#L198
luma is the value of the screen retrieved from wlroots and processed via vulkan. If you move back and forth between a black and white windows, you should see luma value change. If this happens, we are good :)

Unfortunately, My wlroots still doesn't work 🥲.
Wluma only works when set to none in the compositor.
I ~assumed~ Hoped if i updated ash to v0.38 it may have an effect but it didn't, well i will continue to try later to update wayland-client and wayland-protocol.
Here is the screen recording i took to send.
https://github.com/user-attachments/assets/84d2bf20-ca77-4816-8f15-f726b4126839
https://github.com/user-attachments/assets/e615adff-0a77-4e2f-a328-b300fe4c094e
I used my study lamp to light up in front of my camera.
In case you are wondering, the brightness is at the top beside the clock.
And its changing based on light intensity so i think the code is working.
What do you think?

vulkan part is only involved when you use wlroots, so when you set capturer=none, you are also disabling the entire vulkan part, it doesn't get executed on your computer :wink:
At the same time I think the code change in this PR is very reasonable and I want to merge your very good progress, so that you can proceed with your awesome work from a fresh PR. Your contributions are very appreciated!
I'll ask a friend to test this in the coming days, plus I'm sure some people are running the latest code from main branch, so we will hear if this broke something.

Ohh, if you asked this before and I mislead you into thinking that vulkan might be a culprit, I am sorry! (and still grateful for your PR :grin: )

PS: Just realised I can at least moving forward eliminate vulkan.rs for not being the culprit on not working on my Hyprland

I still believe this comment https://github.com/maximbaz/wluma/issues/111#issuecomment-2266043457 to be true, hyprland has the "stable" version of that protocol and we still use the "unstable" one because of the old wayland-client dependency. As soon as we update wayland-client, the current code like use wayland_protocols::wlr::unstable::export_dmabuf... will become use wayland_protocols::wlr::stable::export_dmabuf (unstable -> stable) or something like this, and then it will work again on hyprland.


Form Duplication

This pull request introduces the ability to duplicate Forms.
The ability to register actions for Forms isn't yet available at the time of this PR. However, I've opened a PR on the Statamic side to make it possible: statamic/cms#5845.
Closes #38.

Note to self: this PR is pretty much ready to go, just waiting on the related Core PR to be merged.

Nice idea!


General Grievance: Watch Asham Tv

General Grievance requests the watch of the watch_keyword Asham Tv. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Asham Tv has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Add support for GCE list paging and filtering

GCE will return a maximum of 500 resources in a single list. This change
adds an iterator that allows filtering and/or paging of list results.

/cc @Kami - mind giving us your thoughts on this?

Will dig in ASAP.
On a related note - we already have an establish pattern for handling paginated collections which should probably also work here. See https://github.com/apache/libcloud/blob/trunk/libcloud/dns/drivers/zerigo.py#L149 for an example.

Ah, good point. Reminded me that the Google DNS driver also uses generators: https://github.com/apache/libcloud/blob/trunk/libcloud/dns/drivers/google.py

Ah, didn't see that. It looks like this would be the first time iterate_* is used in the compute driver.
It would be pretty easy to overlay the iterate_* functions on top of GCEList if my underlying approach is still sound. This would keep the filter functionality available in ex_list().
Alternatively we could establish a pattern for filter, too.

friendly ping and just checking in to make sure nothing is blocked on me.

@erjohnso can you please review this one and take it across the finish line?

@verb Sorry for the delay. I have quickly glanced over it and it looks good to me, but I haven't done any testing.

Sorry for the delay, @verb!  Thanks!!


Add runtime theme support for CV media upgrade dialogs

Jira issue:
https://glia.atlassian.net/browse/MOB-1991
Additional info:
Also updated a bit of code for all other dialogs as some of them missed font family in buttons and to overall make the code more consistent
Additionally, it seems that BaseConfigurableButton.setTheme(UiTheme) does not apply themes correctly. I marked it as deprecated and replaced it in Dialogs.kt.
Screenshots:

@gugalo Honestly, I don't have an answer right away.
Maybe @DavDo has any assumptions?

@DavDo I think there is no need to investigate at the moment
P.S: Just rebase this branch on the master to resolve merge conflicts and removed those comments.

!merge


Update Image CSP

Overview
Some of the example stories use images from the assets bucket, such as this one: https://ui.mydatahelps.org/?path=/docs/surveystep-celebrationstep--docs
They're showing up as broken links due to being blocked by the CSP. I added that site to the CSP, and also made a few typo/wording tweaks to the readme.
Security
REMINDER: All file contents are public.

[X] I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.

[X] Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
[X] There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.

[X] These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
Allowing images from our internal asset bucket does not introduce any new security risks.
Checklist
Testing

[ ] MyDataHelps iOS app
[ ] MyDataHelps Android app
[ ] MyDataHelps website

The above are n/a. Must be tested with the amplify deployment of the storybook site.
Documentation

[ ] I have added relevant Storybook updates to this PR as well.
[ ] If this feature requires a developer doc update, tag @CareEvolution/api-docs.

No documentation needed
Consider "Squash and merge" as needed to keep the commit history reasonable on main.
Reviewers
Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including:

Subject-matter experts
Style/editing reviewers
Others requested by the content owner

🚢


Update project to Swift 4.1 and make compatible with SPM 4.1

This change makes Marathon compatible with the Swift 4.1 toolchain, including the 4.1 version of SPM. The biggest change is the removal of the prefetching flag and fixing of some deprecation warnings.
Also includes a fix for the testEditingScriptWithXcodeOnMacOS test that was failing on master.

So much red 😝

WIP 😅 All tests are passing locally but need to figure out why they're not passing on CI (esp. Linux).

We're down to only two failures 😅 Getting close!

@johnsundell FWIW I just checked this branch out and it Works On My Machine™

@designatednerd Hehe that's good to know. The problem is (was?, hopefully!) on Linux. Hopefully it's fixed now 😅 I really need to get that Linux environment up and running so I can more easily debug these things.

FYI one of the dependencies 'releases' has some deprecations. Not sure if that might upset your CI build. It's a long shot
I run make on latest commit on this branch. Checkout 2d8f59b00b7d6fb3dd5e475713d4515e5a559b30
Output
///stuff
Resolving https://github.com/JohnSundell/Require.git at 2.0.1
swift build -c release -Xswiftc -static-stdlib
Compile Swift Module 'Require' (1 sources)
Compile Swift Module 'Unbox' (42 sources)
Compile Swift Module 'Wrap' (1 sources)
Compile Swift Module 'ShellOut' (1 sources)
Compile Swift Module 'Files' (1 sources)
Compile Swift Module 'Releases' (4 sources)
/Users/robertnash/Code/Marathon/.build/checkouts/Releases.git--3309408284261296015/Sources/Releases.swift:26:26: warning: 'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value
        return try lines.flatMap { line in
                         ^
/Users/robertnash/Code/Marathon/.build/checkouts/Releases.git--3309408284261296015/Sources/Releases.swift:26:26: note: use 'compactMap(_:)' instead
        return try lines.flatMap { line in
                         ^~~~~~~
                         compactMap
Compile Swift Module 'MarathonCore' (29 sources)
Compile Swift Module 'Marathon' (1 sources)
Linking ./.build/x86_64-apple-macosx10.10/release/Marathon
mkdir -p /usr/local/bin
mv .build/Release/Marathon .build/Release/marathon
install .build/Release/marathon /usr/local/bin
Roberts-iMac:Marathon robertnash$

OK @sunshinejr comes to the rescue and seems to have fixed the problem! 🚀 Let's see if we finally get it to turn green 😃

It's time to pop the 🍾! 😃 Thanks a lot to @sunshinejr for helping me finalize this 🙌


pragmatic_segmenter installing problem

gem install pragmatic_segmenter
Successfully installed pragmatic_segmenter-0.3.22
Parsing documentation for pragmatic_segmenter-0.3.22
Done installing documentation for pragmatic_segmenter after 0 seconds
1 gem installed
But it does not install:
sevilay@sevilay-linux:~$ apt-cache policy pragmatic_segmenter
N: Unable to locate package pragmatic_segmenter
Please anyone could tell me what is the problem?

Hi @sevilaybayatli, I'm responding to your comment here: https://github.com/diasks2/pragmatic_segmenter/pull/68#issuecomment-762462583
It seems like your system should have the gem installed properly. gem install is different from apt install, so instead of using apt-cache, use gem list to look for the package.
As for your code, if you re-run it now, I think you should have no error when you require pragmatic_segmenter in your code.

Hi @sevilaybayatli, I'm responding to your comment here: https://github.com/diasks2/pragmatic_segmenter/pull/68#issuecomment-762462583
It seems like your system should have the gem installed properly. gem install is different from apt install, so instead of using apt-cache, use gem list to look for the package.
As for your code, if you re-run it now, I think you should have no error when you require pragmatic_segmenter in your code.

Hi @alextsui05,
:~$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.8)
did_you_mean (1.0.0)
io-console (0.4.5)
json (1.8.3)
minitest (5.8.3)
net-telnet (0.1.1)
power_assert (0.2.6)
pragmatic (0.1.1)
pragmatic_segmenter (0.3.22, 0.3.18)
psych (2.0.17)
rake (10.4.2)
rdoc (4.2.1)
test-unit (3.1.5)
unicode (<IP_ADDRESS>)
It seems I have pragmatic-segmenter, I don't understand why  got that error then:(

Hi @alextsui05,
:~$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.8)
did_you_mean (1.0.0)
io-console (0.4.5)
json (1.8.3)
minitest (5.8.3)
net-telnet (0.1.1)
power_assert (0.2.6)
pragmatic (0.1.1)
pragmatic_segmenter (0.3.22, 0.3.18)
psych (2.0.17)
rake (10.4.2)
rdoc (4.2.1)
test-unit (3.1.5)
unicode (<IP_ADDRESS>)
It seems I have pragmatic-segmenter, I don't understand why  got that error then:(

Is this solved with the newest version: https://github.com/diasks2/pragmatic_segmenter/pull/68 ?

Yeah it solved.

Solved!


Aggregate is failing with certain db settings

In the current Query Builder instance in this package, the aggregate method doesn't remove things like order at least like the latest laravel version does to remove errors around full group by.
I can run the same query twice using this package enabled and without and the resulting queries look like:
With:
select count(*) as aggregate from "manufacturers" order by "id" desc

Without:
SELECT count(*) as aggregate FROM "manufacturers"

This causes the query to fail on servers where this option is enabled, whereas base installs of laravel, can function properly with this option.
For reference, https://github.com/laravel/framework/blob/master/src/Illuminate/Database/Query/Builder.php#L2421

Is this package still being maintained at all? I would think that a month's time would be enough to at least comment on things? The last change I suggested last time took close to 3 months (maybe more) to even have a response of some kind.

thanks for feedback :+1:
this method cannot be simply removed as original laravel's behavior works differently when we have subquery used in searchable

Shouldn't this be something that the Searchable package has then? If I'm not using it why should usage of something unrelated break?

It shouldn't break indeed. Can you provide a sample code to reproduce exactly the issue?

I don't recall specifically what the code was but based on the resulting query I had here:
Model::orderBy('id')->count()

This would work in laravel but not under this package.

I will give it a shot and make a fix where necessary! :clinking_glasses:


update JSON-Schema-Test-Suite; make ajv compatible with draft-04

The reason Ajv was failing the tests is that version 5.x requires explicitly adding draft-04 meta schema and making it default, otherwise it supports draft-06.
I am not sure why jsen and themis were throwing, they didn't throw for me.

@ebdrup I've added the condition that removes the section if there are no common errors. I still think it may be better to remove json-schema-validator-generator completely. What do you think?

I will merge and raise an issue with json-schema-validator-generator


BUG

Use "setTimestamp" function. Timestamp Data result was set in Realtime Database, but function return "false" and the error is "data type mismatch".

I use ESP8266 core 2.7.4 in Arduino IDE.
I installed "Firebase ESP8266 Client" version 3.0.1.
I use Firebase ESP8266 Client "timestamp" example in Arduino IDE.
I changed connection variables in example source code for my WiFi and Firebase Realtime Database.
Upload example to my NodeMCU 12-E ESP8266.
Open Serial Monitor in Arduino IDE.
I see the error in Serial Monitor below

I was checked data in my Realtime Database. Timestamp Data result was set in Realtime Database.

Below is part of example source code, that use "setTimestamp" but the result setTimestamp function is false and display error.

IDE and its version:

Arduino Version 1.8.13.

ESP8266 Arduino Core SDK version

2.7.4

This issue is now fixed. Please update the library to v3.0.2 (via GitHub download).


Implement integrate function/CLI command to simplify integrating offline-manager.js

This adds an integrate command as described in #25.
I haven't implemented the "add script automatically" part yet, I will do it in a follow-up.

Filed #47 for adding tests. Filed #48 for automatically adding the script tag.

Thanks, I'll update the patch shortly.


Fe/hacker page

Resolves #37 and #36 (Temporarily will just leave resume off admin pannel )

Lgtm


RawSouceWaveStream Minor Update

Added the capability for the RawSourceWaveStream to be initialized by a byte array.
Fixed position setter to prevent potential runtime playback corruption when seeking.

nice, although I'd usually do the block align by doing value - (value % waveFormat.BlockAlign). the decimals and rounding seems a little overkill to me

Ah, that would actually make a lot more sense (I was a little tired when I make the change first, and was just happy I got a result). Updated.

thanks


path normalization needed to avoid duplicated builds?

I tried to run cyan build on teal-language-server without having other teal-types definitions around. I got this output (will paste it in full here, but point to a specific thing below)
cyan build
    Error 5 type errors in src/rpc.tl
      ...    ./src/util.tl 2:29 no type information for required module: 'dkjson'
      ...    ./src/util.tl 73:19 cannot index a value of unknown type
      ...    src/rpc.tl 3:29 no type information for required module: 'dkjson'
      ...    src/rpc.tl 71:22 cannot index a value of unknown type
      ...    src/rpc.tl 83:21 cannot index a value of unknown type
     Info Type checked src/uri.tl
    Error 3 type errors in src/methods.tl
      ...    ./src/rpc.tl 3:29 no type information for required module: 'dkjson'
      ...    ./src/rpc.tl 71:22 cannot index a value of unknown type
      ...    ./src/rpc.tl 83:21 cannot index a value of unknown type
    Error 19 type errors in src/document.tl
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 5:33 no type information for required module: 'argparse'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 34:23 unknown type argparse.Command
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 55:34 unknown type argparse.Parser
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 57:27 cannot index something that is not a record: argparse.Parser (an unknown type)
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/init.tl 5:28 module not found: 'lfs'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/init.tl 18:24 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/init.tl 26:43 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/init.tl 124:11 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 112:15 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 170:15 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 176:15 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 182:15 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 194:30 assignment in declaration did not produce an initial value for variable 'err'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 194:48 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 196:27 in return value: got <unknown type>, expected string
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 209:18 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 381:27 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 383:27 cannot index a value of unknown type
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/log.tl 9:36 no type information for required module: 'inspect'
    Error 2 type errors in src/handlers.tl
      ...    src/handlers.tl 4:28 no type information for required module: 'lfs'
      ...    src/handlers.tl 30:20 cannot index a value of unknown type
    Error 2 type errors in src/init.tl
      ...    ./src/handlers.tl 4:28 no type information for required module: 'lfs'
      ...    ./src/handlers.tl 30:20 cannot index a value of unknown type

What caught my attention was that src/rpc.tl and src/handlers.tl were compiled twice (once as src/ and once as ./src), leading to the duplicated error messages

(btw, all these cannot index a value of unknown type will go away in the next version of Teal because now unresolved requires are invalid rather than unknown; as a curiosity, this is the output with the bidi-inference branch — it's shorter, but as expected the issue I described above still happens)
    Error 2 type errors in src/rpc.tl
      ...    ./src/util.tl 2:29 no type information for required module: 'dkjson'
      ...    src/rpc.tl 3:29 no type information for required module: 'dkjson'
     Info Type checked src/uri.tl
    Error 14 type errors in src/document.tl
      ...    ./src/rpc.tl 3:29 no type information for required module: 'dkjson'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 5:33 no type information for required module: 'argparse'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 34:23 unknown type argparse.Command
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 55:34 unknown type argparse.Parser
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/command.tl 57:27 cannot index something that is not a record: argparse.Parser (an unknown type)
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 161:55 invalid key 'include_dir' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 162:65 invalid key 'wdisable' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 163:61 invalid key 'werror' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 164:63 invalid key 'preload' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 166:26 invalid key 'gen_compat' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/config.tl 167:26 invalid key 'gen_target' in record 'args' of type command.Command.Args
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/init.tl 5:28 module not found: 'lfs'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/fs/path.tl 194:30 assignment in declaration did not produce an initial value for variable 'err'
      ...    /System/Aliens/LuaRocks/share/lua/5.4/cyan/log.tl 9:36 no type information for required module: 'inspect'
    Error 1 type error in src/handlers.tl
      ...    src/handlers.tl 4:28 no type information for required module: 'lfs'
     Info Type checked src/methods.tl
    Error 1 type error in src/init.tl
      ...    ./src/handlers.tl 4:28 no type information for required module: 'lfs'

Off the top of my head i want to say that this is due to tl using package.path and directly substituting filenames into something like ./?.lua, I guess the hotfix solution would be to manually add both paths to the env.loaded, but maybe a better solution would be to introduce something like tl.searchers? (analogous to package.searchers) to interact with how tl finds modules?

I tried this again to see if https://github.com/teal-language/tl/pull/538 fixed this by any chance, but with Cyan 0.10 I can't reproduce this, even with tl 0.13.2. So I guess this can be closed?


dev -> master

This change is

Reviewed 24 of 24 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Test

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

a discussion (no related file):
Wait for Gradle

a discussion (no related file):
Wait for Safewalk?

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

Reviewed 6 of 6 files at r4, 3 of 3 files at r5.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Reviewed 20 of 20 files at r6.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Reviewed 1 of 1 files at r7.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r8.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Call succeeds after expected revert

🐛 Script Bug Report
📝 Description
I encountered an issue where the .call() would succeed after expected revert.
Here is the part of code im referring to:
https://github.com/neotheprogramist/era-contracts/blob/983c4586b93eefa93c078a6a20fb7c424c526310/l1-contracts/test/foundry/unit/DeployProxy.t.sol#L197-L208
🔄 Reproduction Steps
Run tests on this branch:
https://github.com/neotheprogramist/era-contracts/tree/test/proxy-tests
To run tests use "yarn test:foundry --match-contract ProxyTest --ffi  -vvv".

It worked for me:


await supabase.auth.sign_up raises object NoneType can't be used in 'await' expression

Describe the bug
sign_up method from AsyncClient is raising the error  object NoneType can't be used in 'await' expression
To Reproduce
import os

import trio
from dotenv import load_dotenv

load_dotenv()

async def main():
    from supabase._async.client import AsyncClient, create_client

    DB_URL: str = os.getenv("DB_URL")
    ANON_KEY: str = os.getenv("ANON_KEY")

    supabase: AsyncClient = await create_client(DB_URL, ANON_KEY)  # works fine

    email: str =<EMAIL_ADDRESS>    password: str = "test123"

    user = await supabase.auth.sign_up({"email": email, "password": password})

trio.run(main)

Traceback (most recent call last):
  File "/user/sbtest/test.py", line 23, in <module>
    trio.run(main)
  File "/user/sbtest/.venv/lib/python3.11/site-packages/trio/_core/_run.py", line 2093, in run
    raise runner.main_task_outcome.error
  File "/user/sbtest/quick.py", line 20, in main
    user = await supabase.auth.sign_up({"email": email, "password": password})
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/user/sbtest/.venv/lib/python3.11/site-packages/gotrue/_async/gotrue_client.py", line 153, in sign_up
    await self._remove_session()
  File "/user/sbtest/.venv/lib/python3.11/site-packages/gotrue/_async/gotrue_client.py", line 653, in _remove_session
    await self._storage.remove_item(self._storage_key)
TypeError: object NoneType can't be used in 'await' expression

Expected behavior
Async sign up working
Desktop (please complete the following information):

Arch Linux
Python 3.11.6
Supabase 2.3.0

Additional context
Same issue on Android

Thanks for opening this issue and also the PR you opened too. We have merged in a fix and it has been released in version 2.3.2.

Closing this out as fix has been released.


Update go-mysql-server and prepare changelog for the next rc version

Signed-off-by: Antonio Navarro Perez<EMAIL_ADDRESS>

[x] I updated the documentation explaining the new behavior if any.
[x] I updated CHANGELOG.md file adding the new feature or bug fix.
[x] I updated go-mysql-server using make upgrade command if applicable.
[x] I added or updated examples if applicable.
[x] I checked that changes on schema are reflected into the documentation, if applicable.

@agarciamontoro because go modules use minimal version selection


[SPARK-43252][SQL] Rename the error class _LEGACY_ERROR_TEMP_2017 to UNRESOLVED_CUSTOM_CLASS

What changes were proposed in this pull request?
In the PR, I propose to assign the proper name UNRESOLVED_CUSTOM_CLASS to the legacy error class _LEGACY_ERROR_TEMP_2017 , and modify test suite to use checkError() which checks the error class name.
Why are the changes needed?
Proper name improves user experience with Spark.
Does this PR introduce any user-facing change?
Yes, the PR changes an user-facing error message.
How was this patch tested?
By running the modified test suites:
$ build/sbt "testOnly *ObjectExpressionsSuite"

@luizfna Could you address comments, please.

@MaxGekk I would like some calcifications regarding the discussions before to do it so

The title should be SPARK-43253 instead of SPARK-43252.


AFImageDownloader: Downloading multiple images fails when the tasks are cancelled and started again

When you start downloading multiple images simultaneously, then immediately cancel these downloads and then start them again, some downloads fail with cancelled status. This seems to be tied to the value of the "maximumActiveDownloads" property of AFImageDownloader, since the number of attempted downloads has to be greater than this value in order to make some of the downloads fail. Increasing this value also solves the issue.
The following is a failing unit test that can be added to AFImageDownloaderTests to demonstrate this issue:
- (void)testThatItCanDownloadAndCancelAndDownloadAgain {
    XCTestExpectation *expectation = [self expectationWithDescription:@"no download should fail"];
    __block NSUInteger successCounter = 0;

    NSArray *imageURLStrings = @[
                                 @"https://static.pexels.com/photos/1562/italian-landscape-mountains-nature.jpg",
                                 @"https://static.pexels.com/photos/397/italian-landscape-mountains-nature.jpg",
                                 @"https://static.pexels.com/photos/2698/dawn-landscape-mountains-nature.jpg",
                                 @"https://static.pexels.com/photos/2946/dawn-nature-sunset-trees.jpg",
                                 @"https://static.pexels.com/photos/5021/nature-sunset-person-woman.jpg"
                                 ];

    for (NSString *imageURLString in imageURLStrings) {
        AFImageDownloadReceipt *receipt = [self.downloader downloadImageForURLRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:imageURLString]] success:nil failure:nil];
        [self.downloader cancelTaskForImageDownloadReceipt:receipt];
    }

    for (NSString *imageURLString in imageURLStrings) {
        [self.downloader downloadImageForURLRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:imageURLString]] success:^(NSURLRequest * _Nonnull request, NSHTTPURLResponse * _Nullable response, UIImage * _Nonnull responseObject) {
            successCounter++;
            if (successCounter == [imageURLStrings count] - 1) {
                [expectation fulfill];
            }
        } failure:^(NSURLRequest * _Nonnull request, NSHTTPURLResponse * _Nullable response, NSError * _Nonnull error) {
            [expectation fulfill];
        }];
    }

    [self waitForExpectationsWithCommonTimeoutUsingHandler:nil];

    XCTAssertTrue(successCounter == [imageURLStrings count] - 1, @"all downloads should succeed");
}

Thanks for this reproducible case!
The bug appears to be with the cancelled task getting tied to the wrong response handler. I'm looking into it.

Check out #3325
Thanks again for the failing test case :beers:


set GOMIPS=softfloat but show error syntax error: unexpected word (expecting ")")

i use go version go1.17.1 linux/amd64
i have a device with cpu look like below:
cat /proc/cpuinfo
system type : 96848EG2F2V1_UX
processor : 0
cpu model : Broadcom BMIPS4350 V8.1
BogoMIPS : 598.01
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : no
hardware watchpoint : no
ASEs implemented :
shadow register sets : 1
kscratch registers : 0
core : 0
VCED exceptions : not available
VCEI exceptions : not available

processor : 1
cpu model : Broadcom BMIPS4350 V8.1
BogoMIPS : 606.20
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : no
hardware watchpoint : no
ASEs implemented :
shadow register sets : 1
kscratch registers : 0
core : 0
VCED exceptions : not available
VCEI exceptions : not available

i test it with the simple program：
package main

import "fmt"

func main() {
	fmt.Print("hello,world")
}

i build with GOOS=linux GOARCH=mips GOMIPS=softfloat CGO_ENABLED=0 go build  and get hello, but when i run ./hello in my device, it thell:line 1: syntax error: unexpected word (expecting ")")
also i build with GOOS=linux GOARCH=mipsle GOMIPS=softfloat CGO_ENABLED=0 go build  and get hello, but when i run ./hello in my device, it thell:
./hello: line 8:EL▒▒    ▒ !▒D▒▒$
▒f▒▒"▒▒▒▒5
"<tz▒<
d{▒۶▒d▒
       ▒▒D▒\+8▒< ▒B$4<7!$
% q ▒▒t0$*▒▒▒

▒=A
A▒0b▒h
8}= ▒b
$
 $
▒▒▒*@F!$: not found
./hello: line 9: syntax error: unexpected ")"

i test it again.
i build with GOOS=linux GOARCH=mips GOMIPS=softfloat CGO_ENABLED=0 go build -ldflags "-s -w" and get hello, but when i run ./hello in my device, it thell: line 1: syntax error: unexpected "("
also i build with GOOS=linux GOARCH=mipsle GOMIPS=softfloat CGO_ENABLED=0 go build  -ldflags "-s -w" and get hello, but when i run ./hello in my device, it thell: line 2: syntax error: unexpected "(" (expecting ")")

my device info:
uname -a:
Linux (none) 3.4.11-rt19 #1 SMP PREEMPT Fri Nov 20 00:26:52 CST 2020 mips GNU/Linux
cat /proc/version:
Linux version 3.4.11-rt19 (jenkins_wang@jenkins) (gcc version 4.6.2 (Buildroot 2011.11) ) #1 SMP PREEMPT Fri Nov 20 00:26:52 CST 2020

It appears your machine executes the binary as a shell script? This is weird. What is the output of file hello?
  You should use GOARCH=mips if it is big endian, GOARCH=mipsle if it is little endian.

the shell of my device is /bin/sh, is it a problem?


Add minimum polyfill to support "relative-time-element" in PaleMoon

Close #26525
Q&A:

Why not fully polyfill?

The full polyfill would be quite big because it needs different locale resources.

Why not use something like https://polyfill.io/v3/?

It needs to access external sites
Actually "polyfill.io" doesn't polyfill the incomplete Intl.NumberFormat because it considers there is already Intl.NumberFormat support .....

Chrome

PaleMoon (screenshot taken 22 seconds after the first one, ignore the time difference)

I see an issue with the plural rules

npm i @formatjs/intl-numberformat
add these
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
That fixes the plural rules (~300KB of JS)

PaleMoon (screenshot taken 22 seconds after the first one, ignore the time difference)
I see an issue with the plural rules
...
That fixes the plural rules (~300KB of JS)

I do not see it as an big issue because all other browsers all work fine and I believe PaleMoon will have full support soon. This change is a "minimal" change, I do not think we should make end users load more than 300KB JS code before the page-loading.