Build errors with Carthage and Xcode 8

I ran into this issue initially with an existing project that had gone through the migration process to Swift 2.3, but I've also been able to reproduce it with a new "Single View Application" iOS project.
Carthage version: 0.18
Moya version: 7.0.2
Xcode version: 8.0 (8A218a)
After creating a new project, I add a Cartfile with the following contents:
github "Moya/Moya" ~> 7.0

Then:
$ carthage bootstrap --platform iOS
*** No Cartfile.resolved found, updating dependencies
*** Fetching Moya
*** Fetching RxSwift
*** Fetching Alamofire
*** Fetching Result
*** Checking out Alamofire at "3.5.0"
*** Checking out Result at "2.1.3"
*** Checking out ReactiveCocoa at "v4.2.2"
*** Checking out RxSwift at "2.6.0"
*** Checking out Moya at "7.0.2"
*** xcodebuild output can be found in /var/folders/d1/h0cf2xs12gv7w1wx5k41q7sc0000gp/T/carthage-xcodebuild.7jZFKG.log
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
*** Building scheme "Result-iOS" in Result.xcodeproj
*** Building scheme "ReactiveCocoa-iOS" in ReactiveCocoa.xcworkspace
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa.xcworkspace'.
*** Building scheme "RxBlocking-iOS" in Rx.xcworkspace
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
*** Building scheme "RxCocoa-iOS" in Rx.xcworkspace
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
*** Building scheme "RxSwift-iOS" in Rx.xcworkspace
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
*** Building scheme "RxTests-iOS" in Rx.xcworkspace
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
--- xcodebuild: WARNING: Unable to open project file '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.playground' in workspace '/Users/tim/tmp/MoyaTest/Carthage/Checkouts/RxSwift/Rx.xcworkspace'.
*** Building scheme "Moya iOS" in Moya.xcodeproj
** CLEAN FAILED **

The following build commands failed:
	Check dependencies
(1 failure)
** BUILD FAILED **

The following build commands failed:
	Check dependencies
(1 failure)
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
/Users/tim/tmp/MoyaTest/Carthage/Checkouts/ReactiveCocoa/ReactiveCocoa/Swift/SignalProducer.swift:1945:69: warning: 'buffer' is deprecated: Use properties instead. 'buffer' will be removed in RAC 5.0
A shell task (/usr/bin/xcrun xcodebuild -project /Users/tim/tmp/MoyaTest/Carthage/Checkouts/Moya/Moya.xcodeproj -scheme "Moya iOS" -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** CLEAN FAILED **

The following build commands failed:
	Check dependencies
(1 failure)
** BUILD FAILED **

The following build commands failed:
	Check dependencies
(1 failure)

The end of the build log shows what I think is the root issue:
/usr/bin/xcrun xcodebuild -project /Users/tim/tmp/MoyaTest/Carthage/Checkouts/Moya/Moya.xcodeproj -scheme "Moya iOS" -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean buildBuild settings from command line:
    BITCODE_GENERATION_MODE = bitcode
    CARTHAGE = YES
    CODE_SIGN_IDENTITY =
    CODE_SIGNING_REQUIRED = NO
    ONLY_ACTIVE_ARCH = NO
    SDKROOT = iphoneos10.0

=== CLEAN TARGET Moya iOS OF PROJECT Moya WITH CONFIGURATION Release ===

Check dependencies
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

=== BUILD TARGET Moya iOS OF PROJECT Moya WITH CONFIGURATION Release ===

Check dependencies
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

Sorry you're running into this error, it's possible I made a mistake when releasing 7.0.2 for Swift 2.3. Could someone from @Moya/contributors who is familiar with Carthage take a look and see if 7.0.2, the latest release, works with Xcode 8/Swift 2.3?

No worries, I know you are all working hard on the recent Swift/Xcode changes.
If I had to guess, it looks like the migration changes to the Moya project file weren't included in the commit with the other Swift 2.3 updates #(2fc967f).

Ah, interesting! Would you be able to submit a PR against the release-7.0.1-take-two branch? Don't worry about it, though, I can take a crack tomorrow.

I've mostly got a PR together; just finishing up some testing. Expect to see it within a few hours.

Wonderful, thanks!

This is fixed with #636.


SQLMesh format converts SAFE_CAST to CAST

This is not semantically the same operation. The issue will need to be resolved in sqlglot I imagine but posting here because of its relevance in SQLMesh given the format CLI command.

@z3z1ma can you share the commands you used for this? i'm not seeing this behavior on sqlglot

q = parse_one("""
safe_cast(x as int64)
""", read="bigquery")

print(q.sql(dialect="bigquery", pretty=True))

I'll fix this


Design Engineer - Mobile - Responsiveness

Background
The purpose of this ticket is to update breakpoints and make the pages more responsive on mobile.
Scenario: Update breakpoints and enhance mobile responsiveness
Given I am a design engineer

[ ] When I am viewing Game Box on a mobile device
[ ] Then I update the breakpoints on all pages
[ ] And enhance responsiveness

completed in #84. moving to UAT


Creating custom drivers module in the zephyrproject-rtos/example-application

I'm developing custom application with the example-application, and now I want to create a new driver out-of-tree module called latching_relay with its own custom API. Next, I will create the driver for the latching relay part (some Panasonic one) that implements the latching_relay API. I've read about system drivers here but didn't find any useful information regarding creating custom driver model in the out-of-tree application.
I've copied the hello_world_module from the out_of_tree_driver sample from the Zephyr folder, successfully build it and flashed, and now I would like to move it to the drivers folder of the example application. When I move hello_world_module folder to the drivers folder and edit app/CMakeLists.txt file to append zephyr extra modules with the path ${CMAKE_CURRENT_SOURCE_DIR}/../drivers/hello_world_module, I get a fatal error saying No such file or directory #include <syscalls/hello_world_driver.h>. I have CONFIG_APPLICATION_DEFINED_SYSCALL flag enabled in the prj.conf.
Because my relay is driven by simply changing the states of two GPIO's, I could implement the relay driver as LED-GPIO one but I don't have good feeling doing so because my relay is not an LED.

Moved question to the discussions.


Cannot read properties of undefined (reading 'COSMIC_API_URL')

Hello,
I'm using Nuxt 3 (SSR) with Cosmic.JS and getting the following error:

Here is my plugin I created unter plugins/cosmic.ts:
import Cosmic from 'cosmicjs'

const api = Cosmic();
const bucket = api.bucket({
  slug: process.env.COSMIC_JS_BUCKET_SLUG,
  read_key: process.env.COSMIC_JS_READ_KEY,
});

export default defineNuxtPlugin(() => ({
  provide: {
    cosmic: bucket
  }
}));

Maybe it's necessary to check if "process.env" is existing?

Hey @AlexBa I'm not super familiar with Nuxt 3. Tagging @jazibsawar to see if he can offer advice. Thanks 🙌🏻

Hey @AlexBa I'm not really sure how NUXT is handling SSR. But apparently, process.env is undefined in SSR mode which shouldn't be in the Node environment.

@jazibsawar I tested a few things and found out that Nuxt 3 uses the same code for the frontend and backend (hydration and SSR). And process.env is not available with Vite in the frontend.
I guess that it's not possible to add your NPM library the "Nuxt 3 way" via plugins, BUT it's possible to create an API endpoint unter server/api, which is served always via Node in the backend. It's possible to call the backend in the frontend via "fetch".
Now it's working! :)

Great to hear @AlexBa I'll go ahead and close this issue.


make NewRTM configurable

adds dialer for managed RTM.
deprecates the RTMWithOptions method.

failure isn't understood, I suspect a timeout default causing it to hang.

Oh interesting. I missed this while creating #263. I think the switch to RTMOption is fine, but I'd argue that a websocket.Dialer is a better choice than a net.Dialer for changing how connections happen, because it has more websocket-specific stuff in it, in addition to a net.Dialer equivalent.

Of course, this leaks the gorilla websocket.Dialer type from the nlopes/slack package. I suppose once we move a few Go releases into the future, we could create an Alias.

@zellyn likely this PR won't be merged until I (or someone else!) gets a chance to look into the test failures.
I won't have time for the next few months probably due to other projects, work, and personal time. =/

@james-lawrence I'll incorporate these option-param changes into #263 and update it… any suggestions on other maintainers to ping?

I'll be able to review, just not investigate, but any one of the other maintainers can review as well.

@james-lawrence #269 is a combination of your PR and my old one, #263. The reason the tests were failing is that defaulting UseStart to false was hanging indefinitely. Here's the fix. I haven't figured out why yet, although I suspect it might be the test fake. ¯\_(ツ)_/¯


Write ECALL specification

risc zero's zkVM implements the RV32IM instruction set with several ecalls. These ecalls are specific to the RISC Zero zkVM and it's behavior (including failure cases) should be documented.

There are some comments on this topic in the docs here: https://dev.risczero.com/api/zkvm/developer-guide/zkvm-specification

This will be resolved by moving to the Linux ABI


Change booking to order

Closes #55.

Codecov Report

Merging #56 (ad8b8c7) into master (c5112e5) will decrease coverage by 0.55%.
The diff coverage is 36.36%.

@@             Coverage Diff              @@
##             master      #56      +/-   ##
============================================
- Coverage     67.16%   66.61%   -0.56%
- Complexity      398      399       +1
============================================
  Files            73       73
  Lines          1267     1279      +12
  Branches        117      122       +5
============================================
+ Hits            851      852       +1
- Misses          384      391       +7
- Partials         32       36       +4

Impacted Files
Coverage Δ

...2/btbb/logic/commands/client/AddClientCommand.java
100.00% <ø> (ø)

...tbb/logic/commands/client/DeleteClientCommand.java
86.66% <ø> (ø)

.../btbb/logic/commands/client/EditClientCommand.java
92.85% <ø> (ø)

.../btbb/logic/commands/client/FindClientCommand.java
100.00% <ø> (ø)

.../btbb/logic/commands/client/ListClientCommand.java
100.00% <ø> (ø)

...6_2/btbb/logic/commands/order/AddOrderCommand.java
0.00% <0.00%> (ø)

..._w16_2/btbb/logic/descriptors/OrderDescriptor.java
0.00% <0.00%> (ø)

...btbb/logic/parser/order/AddOrderCommandParser.java
0.00% <0.00%> (ø)

..._cs2103t_w16_2/btbb/model/util/SampleDataUtil.java
0.00% <0.00%> (ø)

...y2122s1_cs2103t_w16_2/btbb/model/ModelManager.java
80.70% <18.18%> (-1.45%)
:arrow_down:

... and 9 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 c5112e5...ad8b8c7. Read the comment docs.

Documentation was not really changed in this PR but it should be changed by the end of v1.2.


Couchbase Lite Exception -> Can't delete db file while other connections are open

Hi Triniwiz,
First of all ... as always thank you for all you've done for NS !
Then...
I'm trying to delete|destroy database content... So I'm calling myDB.destroyDatabase();
Strangely if myDB has already been opened and fulfilled with some data and then I want to destroy data, I get this exception.
--> CouchbaseLiteException{domain='CouchbaseLite', code=16, msg=Can't delete db file while other connections are open}
Then how can I close properly (or force to close) myDB before create new one ?
Or maybe I need to loop over my existing documents to delete them separately ?
Thanks in advance.
Lo.

I didn’t expose a close method but you can try myDB.android || .ios.close() <- which ever platform you’re on

Yep that seems to do the trick ;) Thanks.
Now I'm getting the database, do my stuffs and right after I close it. I'm not sure it's a performance issue...to close every time...but it seems to work.
But do you have an idea how to create index from your plugin ?
I have to manage about 3000 items and it not seems very fast when I do query all the items is about 3 sec...

I did not expose that feature but will add it in the next version also it would be v7 only another I can try enabling the multithreaded feature (currently begin a flag v7 only) then you even use the batch method 🙂

Aïe I'm not quite ready to upgrade to NS7 right now... I'm working on a big entreprise angular shared project...so it's a huge truck to move ;)
Thanks Osei.

Ah understood , you see I’m doing a massive clean up with all the plugins I maintain an the ones that got under-maintained ... I think everyone would love the next move 🙂

sure !

Finally... I will wait until your next plugin version, currently Couchbase is way too slow for my needs... Or maybe it's not the right tool. I don't know... I've simply compared its read performance with a simple string application storage done by child workers and that's really really more performant...From 3 sec to some milliseconds...Unbelievable, I've even added a timeout to let the time for some UI things to happen...More luck on next try. Cheers.


Formatting mangles multiline / doc comments

And incorrectly indents things that follow them.
Begin with
/*
 * foo
 * bar
 **/
baz

Insert an opening curly brace on a new line before the comment, and a closing one on a new line after the comment. The latter will trigger reformatting, and the result is:
{
    /*
 * foo
 * bar
 **/
baz;
}

Note how only the first line of the comment was indented, but not the following lines; and how baz was not indented, either.
[from codeplex: https://nodejstools.codeplex.com/workitem/1567]

Fixed in Es6 Intellisense Preview in NTVS 1.2 Alpha


Expression Level paging does not work

When searching expression levels, the next_page_token of the response is not set correctly.  Indeed, it always is set to empty, regardless of the query.  Therefore, the maximum number of pages returned is always 1.
The reason is expressionLevelsGenerator uses _objectListGenerator to iterate through the results it returns via rnaQuantification.getExpressionLevels.  Unfortunately, rnaQuantification.getExpressionLevels uses the pageSize to create a sql statement using a LIMIT query which only returns as many results as were requested for that particular page.  Therefore, when _objectListGenerator reaches the end of the returned results, it sees that there are no more objects to return on a future page, and does not set next_page_token.
I would not be surprised if this is a common problem affecting all search methods on objects which use a sqlite database as a backing store.  We will need a new interface in backend.py to deal with this kind of thing.

Fixed in #1332
There will likely be similar problems with other db-backed data types, so a refactor would probably be a good idea the next time this comes up.


[RFC] change strategy of defining LightGBM's dependencies

At present we assume that we are OK with all future versions of our dependencies by default. @henry0312 suggested to change that policy: https://github.com/microsoft/LightGBM/pull/2949#discussion_r401550141
Copying the discussion here

@henry0312
is this 'scikit-learn~=0.22,!=0.22.0'?

@StrikerRUS
Sorry, I can't find ~ in the setuptools docs. Can you please clarify what do you mean?

A version specifier is one of the operators <, >, <=, >=, == or !=, followed by a version identifier.
https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-dependencies

@henry0312
Version specifiers
https://www.python.org/dev/peps/pep-0440/#version-specifiers

@StrikerRUS
OK. I guess that this specifier is not compatible with setuptools as it is not listed there, is it?
Also, why do we need it? We are compatible with all (reasonable) versions except 0.22.0.

@henry0312

OK. I guess that this specifier is not compatible with setuptools as it is not listed there, is it?

I don't know the specific version but setuptools used in sklearn, numpy, scipy and pandas supports version specifier as least.

Also, why do we need it? We are compatible with all (reasonable) versions except 0.22.0.

Not enough.
As you know, many python packages follow Semantic Versioning, including scikit-learn.
If we specify scikit-learn!=0.22.0 and v1.0.0 of scikit-learn is released, LightGBM will allow users to use v1.0.0, which can lead to break backward compatibility.
Therefore, if we follow Semantic Versioning, we should specify libraries' version by Version specifiers.

@StrikerRUS

If we specify scikit-learn!=0.22.0 and v1.0.0 of scikit-learn is released, LightGBM will allow users to use v1.0.0,

I don't see any problems with it. Moreover, I believe that this should be an expected behavior.
Before now we have never blocked future versions of libraries, assuming that by default we are compatible with them. If it is not true, someone comes and posts an issue and we are investigating.
In case of prohibiting future releases it is highly likely that we'll forget to update those requirements or will do it with huge delay making user experience inconvenient.

@henry0312

Before now we have never blocked future versions of libraries, assuming that by default we are compatible with them.

When that is our policy, as you say, there is no problem and I'll approve this PR, though I don't think the policy is common in software engineering.
In other words, a new version which can breaks backward compatibility in terms of Semantic Versioning is released, we should check its compatibility and will add suuport of it in series.

@henry0312
In fact, if we specified Sphinx version, https://github.com/microsoft/LightGBM/commit/ce08242567e1e37e1f947038a78ac671c98ed18e#diff-e0c7b285f2f2d8028247b8cfd4dc76fcR1 were not needed, though that are just tests.
I think unless we follow the basic rules of software engineering, the quality of library won't increase so much even If we add more and more tests.
So I'll approve this when our support policy is clear.

@ekerazha
@henry0312 Actually it's pretty common in software engineering to allow for future versions of dependencies in libraries (while it's common to be more strict in end-user products). If a dependency follows Semantic Versioning (SemVer), you could put a restriction on major versions (e.g. scikit-learn<1.0), but I don't think sklearn is following SemVer. Unless you're ready to release a new version of LightGBM every time a new minor version or patch for a dependency is released, of course.

@StrikerRUS
@henry0312

though I don't think the policy is common in software engineering.

It's kind of debatable statements. And I don't think that this PR is a good place to discuss it. I think we should create a separate issue where we should at least get opinions of other maintainers before changing the current policy.

we should check its compatibility and will add suuport of it in series.

In ideal situation, yes!  But given that we are lacking human resources to do it in time, I suppose that it will be simply abandoned in the near future. Which will result in very old dependencies of LightGBM.

@StrikerRUS

Unless you're ready to release a new version of LightGBM every time a new minor version or patch for a dependency is released, of course.

Absolutely agree! It is definitely not our case when only 2-3 maintainers work actively at the same time.

@henry0312
@ekerazha @StrikerRUS I don't mean all of the future versions wont' be allowed, but only the future versions that can breaks backward compatibility (in other words, a release changes major version), which version specifiers (i.e. scikit-learn~=0.22,!=0.22.0 or scikit-learn>=0.22, == 0.*) realizes.
And is LightGBM an almost end-user products? I think so.

I don't think sklearn is following SemVer.

oh, really...? Actually, I'm not sure.

@ekerazha
@henry0312

And is LightGBM an almost end-user products? I think so.

LightGBM is a library, a travel website which uses LightGBM to recommend travels would be the end-user product.

oh, really...? Actually, I'm not sure.

scikit-learn had breaking API changes in minor versions, so it's not following SemVer.

@StrikerRUS
@henry0312 I guess 0.22 is a minor release, but it broke  backward compatibility.
Again, please let's move all our discussion to a separate issue where everyone will be able to comment. It's very hard to find it here and I want to merge this PR ASAP to enable the latest scikit-learn support.

ping @henry0312 @guolinke @chivee @jameslamb @Laurae2 @ekerazha

Thank you for your discussion.
I think we need to change the current policy only when scikit-learn (also including pandas, numpy and so on) follows Semantic Versioning.

I agree with @StrikerRUS that we should not block future versions of libraries.
Given a new version of scikit-learn:

(with blocking + LightGBM incompatible) --> users get error and open an issue asking us to support new version
(with blocking + LightGBM compatible) -->  users get error and open an issue asking us to support new version
(without blocking + LightGBM incompatible) --> users get error and open an issue asking us to support new version
(without blocking + LightGBM compatible) --> no errors and no issue

People are welcome to use conda, virtualenv, pipenv, Docker, or whatever else they want to peg versions of scikit-learn and  LightGBM  together. I feel we owe our users documentation on which versions are tested and thus expected to work together, but not a guarantee that LightGBM's setup.py will detect incompatibilities with newer versions of other libraries at installation time.

I mostly afraid (and to be honest, pretty sure) that we'll not be able to bump versions of dependencies in time due to lack of maintainers' hands. I believe that this will be more inconvenient for our users than suddenly (and I hope rarely) broken dependency. In addition it will allow us to know that some dependency is broken right after its release and do not wait when one come and create an issue.
As a workaround I guess we can try to use some tools for dependency versioning like https://dependabot.com/ or https://renovatebot.com/. I don't know whether any of them supports rules with <= or ~=, I only saw ==. It is field for the investigation. Auto-PRs look like the following (https://github.com/NewOrbit/load-image-react/pulls).


fix nav issues with q and escape

This resolves #379
I dont like the fix for escape, as it wouldn't save changes to the list
but in the logs, it would always come through a  rather than an escape, not sure why.
Although, thinking about it, is Esc more of a cancel action then a save action
Open to thoughts

updated

Wait, shouldn't we just replaces '<ESC>' with 'Esc' in rhl of escape mapping, because nvim_buf_set_keymap() replaces <ESC> with termcode, and the command just doesn't execute? I mean:
-         "<Cmd>lua require('harpoon.buffer').run_toggle_command('<ESC>')<CR>",
+         "<Cmd>lua require('harpoon.buffer').run_toggle_command('Esc')<CR>",

keycodes are replaced as usual.
https://github.com/neovim/neovim/blob/8bb5089974e14f043a0b0c17e4d38dbd0b9a9ab2/runtime/doc/api.txt#L1508

Sorry the other PR was a bit more comprehensive and was the way I wanted


blog: tags URL should be under blog prefix

https://dvc.org/tags/heartbeat -> https://dvc.org/blog/tags/heartbeat

[ ] Don't forget to update existing links
[ ] Check RSS (do we have it/need for tags?)

I ripgrepped for tag/ and changed everything that matches to blog/tag/, which should take care of existing content.
We currently don't use tag data for any feeds, and I'd say adding tags to feeds would warrant another issue entirely.


Fine grained parser using lexer state

Attempt to create Fine grained parser, using Lexer state.
closes: #23
Approach:
When the lexer sees ## Summary it activates the lexer which can only distinguish between Headline and non-headline.
Similarly when it sees ## Metadata it activates the lexer which can recognize <attr_key: attr_val> and Headline.

This is way out of sync now.


Differences between testvectors_v1 and testvectors

In https://github.com/C2SP/wycheproof/blob/master/doc/formats.md#test-vectors

The old test vectors are in the directory wycheproof/testvectors/, while the new test vectors are in wycheproof/testvectors_v1/.

Does it mean that the testvectors is a subset of testvectors_v1? Can we only use test cases from testvectors_v1?

testvectors_v1 contains the latest version of the test vectors. The main reason for making a new directory is that the format of the test vectors has slightly changed, so that it was possible to add more comments describing the tests. The new files contain the test vectors from the old directory as well as some new ones. Some file (e.g., dsa_test.json or ecdh_test.json) have been split into multiple files, since the original file became too large.
The JSON schemas do not appear to have been updated. They still describe the test vectors in the old testvectors/ directory.  However, there should not be any significant changes for the actual test vectors.
Also, if there are any issues/annoyances with the test vectors or their format, please point them out. I'm currently rewriting the whole project and it would be a good time to learn about problems. There are already some open issues about potential changes.


Update README with state of mockito

Hi,
Mockito has been supporting parallel tests, multiple servers and async since version 0.32. This PR updates the information in the README. I also aligned the table columns because :eyes:
Cheers,
Florin.

Thanks!


DNSSD backend based connection issue after successful discovery

Before you write the report
Read the REPORTING_ISSUES.md file in the main repository and prepare data mentioned there which looks relevant to you issue.
Describe the bug
In case the Service Name contain spaces, after the successful DNSSD backend based discovery, the DNSSD based connection to the printer fails.
To Reproduce
Steps to reproduce the behavior:

Configure a printer with spaces in the Service Name
Add the printer with CUPS WebUI to the system
After successful installation activate the Print Test Page function from CUPS WebUI (Printers/My Printer/Print Test Page)
Cannot connect to the printer, printing fails

Expected behavior
Based on the documentation of CUPS, the service name can contain spaces and after successful installation of such printer, CUPS can print test page.

CUPS documentation URL: http://localhost:631/help/network.html?TOPIC=Getting+Started&QUERY=
Example URI: dnssd://Foo%20Fighter-1969._pdl-datastream._tcp.local./

Screenshots
Not applicable
System Information:

OS and its version: Ubuntu 24.10
CUPS version: 2.4.10
Printer: EPSON L3150
Supported protocols by the printer: LPD, JetDirect, Bonjour, etc.
Printer driver is provided by vendor (Epson)

Additional context

After a lot of failed tries with DNSSD, I could configure CUPS to use LPD (lpd://) and/or JetDirect (socket://) directly, and the printer/printing is working.
After I removed the spaces from the Service Name field (in the printer administration webpage), I could also print the test page with DNSSD configuration.
When the Service Name contain spaces:

the avahi-browse -art command failed to resolve the services.
the generated URI is: dnssd://Epson%20printing%20services._pdl-datastream._tcp.local/

When the Service Name does not contain spaces:

the avahi-browse -art command successfully resolve the services.
the generated URI is: dnssd://epson._pdl-datastream._tcp.local/

I configured my printer long time ago and it was working well with all kind of non Linux devices. So, the long story short, I was happy to see that the installation process successfully recognized my printer with DNSSD, but right after the successful installation of driver, I could not use it (and the documentation of CUPS encouraged me to rule out the "spaces in the service name" as a root cause).

Maybe I just ran into the same issue. Never had printing issues before. After switching to LPD protocol I got it printing again.
System Information:

OS: Arch linux (6.6.59-1-lts)
CUPS version: 2.4.11
Printer: Brother HL-L8250CDN
Printer driver is provided by vendor and made available via AUR package

lpinfo -v
network beh
file cups-pdf:/
network socket
network https
network http
network ipps
network ipp
network lpd
network smb
network dnssd://Brother%20HL-L8250CDN%20series._pdl-datastream._tcp.local/?uuid=e32...
network ipp://Brother%20HL-L8250CDN%20series._ipp._tcp.local/
network lpd://BRN3005.../BINARY_P1

Please provide debug2 logs from CUPS when you try to print - we have to ensure we send the correct hostname to Avahi, otherwise if we do, it will be Avahi issue, not CUPS.
I cannot reproduce it in my env - test page prints fine:
Fedora 40
CUPS 2.4.11
Service Name: "HP Color LaserJet MFP M277dw"
Since it works for me here it looks like distro specific/environment specific as well, related to mDNS resolution.
But please attach .txt with debug2 logs, to be sure we do the right with on CUPS side.

The log files are attached.
horatius_access_log.txt
horatius_error_log.txt
Since logrotate deleted my previous logs, I reconfigured my printer to have spaces in the service name (and renamed it to "Horatius printing services") and also did the below steps to reproduce:

Printer reconfiguration, service name is "Horatius printing services" now, restart printer.
On CUPS interface "Find new printers" action that discovered the printer with the new name. The URI is: "dnssd://Horatius%20printing%20services._pdl-datastream._tcp.local/"
sudo cupsctl --debug-logging
systemctl restart cups around 11:15
On CUPS interface from Maintenance, "Print Test Page" around 11:17
The error message in CUPS interface:

Final error message:
processing since
Thu 07 Nov 2024 11:17:02 AM CET
"Unable to locate printer."

Please note that in the log files you might find "horatius" or "horatius-mDNS" references for my old printer configuration for DNSSD (without spaces in the service name) that is a working configuration for me. I did not deleted this printer configuration for this test, but might be confusing...

Thanks

Ok, I found the root cause and it is neither CUPS nor Avahi (or distro). It is the printer.
I ran several tests and once the test page was printed, so I ran the avahi-browse -art command and got back the successful name resolution for service name with spaces. But few minutes later it failed again...

So I restarted the printer and checked again with the avahi command and was successful.
Waited a minute and checked again, it was successful
Waited again minute or so and checked again, it was successful
Waited again minute or so and checked again and it failed!

The time difference was about 4 minutes. It seems that this printer shutdown (or crash?) its internal avahi service, because I could reproduce this behavior few more times.
Of course, the LPD and JetDirect printing method were working, so it is not the energy saving settings of the printer (which was set to 1 hour btw).
I am sorry for the troubles, but the mystery is solved in my case.

Either way it would be great if you could report this for Avahi for investigation - they could dig deeper and see whether they can something about it.


Drag&Drop

Make it possible to copy mods with drag & drop!
So far, files are completely moved from one folder to another. In other words, they are deleted from source folder.
This is GIF (click):

Yeah, I could add an option to control whether it will move the files or copy the files.


Scheduler prototype and test files.

The new files proto_schedule.py, proto_executor.py, and proto_log.csv work together to demonstrate how events might be scheduled using cron utilities and python-crontab.
-->
New Features
proto_executor has two methods which write to proto_log.csv.

Method1 is suitable for calls directly from crontab or terminal. It is the method called in the if main statement. When called, it writes a line to proto_log recording the time it was called, and its name.
Method2 is suitable for calling within Python itself. It behaves similarly to method1, and is only useful if debugging issues with writing to files.

proto_schedule has several methods which modify cron's crontab file. By doing so, it allows certain shell commands to be run at certain points in the future, possibly on a recurring basis. Additional details can be found in the description for each method. Currently, it only works for .py files in the same directory, but it should eventually extend to different directories and file types as well.
Breaking Changes
Some new code for getting username and file location means that configuration prior to runtime should not be necessary. However, some level of familiarity with cron may be useful for debugging things that break.
Dependency updates
Uses getpass, python-crontab, os, and datetime. Getpass and python-crontab seem to be new to the Poetry config.

@colinyaos , maybe we should close this PR in favour of https://github.com/uc-cdis/thor/pull/13
But please feel free to refactor my branch / PR if you want to augment the code comments and move some stuff around.
(cc: @haniya-ali , please share your thoughts and try to run the new unit tests on the Docker image with the full DEV dependencies)

Now superseded by aiocron, so the code here is redundant. Closing branch and PR.


verify that Status.Phase is set and works per design

From the doc:
status:
  phase: {"pending", "bound", "released", "failed"}  [5]
...
1. phases of bucket creation, mutually exclusive:
    - _pending_: the operator is processing the request
    - _bound_: the operator finished processing the request and linked the OBC and OB
    - _released_: the OB has been deleted, leaving the OBC unclaimed but unavailable.

fixed by #67


Deserialize private collection/dictionary causes MethodAccessException

I'm using MsgPack.CLI 0.6.8 targeting .NET Framework 4.6.1
I have a class contains a private List<int> Items property, deserialize it throws
An exception of type 'System.MethodAccessException' occurred in mscorlib.dll but was not handled in user code

Additional information: Attempt by method 'MsgPack.Serialization.EmittingSerializers.Generated.MyClassSerializer43.UnpackFromCore(MsgPack.Unpacker)' to access method 'MyClass.get_Items()' failed.

I tried to generate serializer assembly then decompile it, I found MsgPack generated deserializing code like this:
MyClass UnpackFromCore(Unpacker unpacker)
{
    // ....
    if (context.Items != null) // context.get_Items()
    {
        foreach (var item in unpackedList)
        {
            ((List<int>this._functionMyClass_get_Items.Invoke(context, null)).Add(item);
        }
    }
    else
    {
        this._functionMyClass_set_Items.Invoke(context, unpackedList);
    }
}

I think the problem is caused by the first access to Items directly called a NonPublic method MyClass.get_Items(). (PeVerify reported Method is not visible)
And the way adding item seems very inefficient.

Thank you and sorry, they are bugs.

This issue was fixed in 0.7.0-alpha3, so I've closed it.


on entity death, entity_type is invalid  (NPC)

EntityFightingEvents:
type: world
debug: false
events:
on entity death:
- debug log "<context.entity.entity_type>: <context.entity.name> died!"
- debug log "<context.entity> died!"
error is simple:
ERROR in script 'ENTITYFIGHTINGEVENTS'! Tag <context.entity.entity_type> is invalid!
This happens when an NPC dies.
Player is ok.
Monsters are ok.
Yes I could use on NPC death.  Unfortunately, if I am trying to catch and sort entity_type it errors.

I did use a workaround, where I use if <context.entity.is_player> and is_npc before any use of entity.entity_type..
My thoughts are that I shouldn't have to.. but anyway

possibly related.  Here is a paste of debug where it shows the ERROR]: Could not pass event EntityDeathEvent to Denizen v1.0.3-SNAPSHOT (build 401)
http://old.mcmonkey.org/paste/48907

OP Issue: Likely caused by Citizens setting NPCs to be removed from the world immediately on death event. Not sure about how to best workaround that. As an attempt that I believe should be fine though not completely ideal, I've modified the script event to run earlier (theoretically: before Citizens picks up the event and deletes the NPC). Might be more ideal to ensure Citizens does that deletion last always, rather than moving Denizen to be earlier.
Error message: That issue is present because I inexplicably trusted @BloodEko with something at one point, which was clearly a terrible idea to trust him and I don't know why I did that.
I fixed that as well.

Both seem to be working  fine.  Thanks!

Aight, the error goes on my cap, as I made changes for an improved damager tracker.
I haven't considered that the bukkit "Player" object can also ba an npc , which leads the error while converting to a dPlayer. Now it's dEntity instead which picks the right object itself.


Lottie fails to build on tvOS device builds

Steps to reproduce :scroll:

Clone this repro

Build for tvOS simulator - no error.

Build or tvOS device - build error.

Expected behavior :thinking:
App should build and deploy for a tvOS device build.
Actual behavior :bug:
Build is failing due to native linker errors for tvOS device builds.
Build FAILED.

MTOUCH : warning MT2107: It's not safe to remove the dynamic registrar, because Lottie.iOS references 'ObjCRuntime.BlockLiteral.SetupBlockUnsafe (System.Delegate, System.Delegate)'.
clang : error : linker command failed with exit code 1 (use -v to see invocation)
MTOUCH : error MT5216: Native linking failed for '/Users/ethand/Desktop/Lottie.tvOS.Sample/Lottie.tvOS.Sample/obj/iPhone/Debug/mtouch-cache/arm64/libLottie.iOS.dll.dylib'. Please file a bug report at http://bugzilla.xamarin.com
    1 Warning(s)
    2 Error(s)

Configuration :wrench:
Version: 2.5.4
Platform:

[ ] :iphone: iOS
[ ] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[x] :tv: tvOS
[ ] :monkey: Xamarin.Forms

This will be fixed in the next release.

Was this resolved?

@jd-alexander looks like it to me, the repro builds successfully now..


Error: NotSupportedException - MonoPInvokeCallback (il2cpp)

When I try to compile my script in "il2cpp", I get this error:
System.NotSupportedException: To marshal a managed method, please add an attribute named 'MonoPInvokeCallback' to the method definition. The method we're attempting to marshal is: NLua.MetaFunctions::CollectObject
  at KeraLua.Lua.LuaPushStdCallCFunction (System.IntPtr luaState, KeraLua.LuaNativeFunction fn) [0x00000] in <00000000000000000000000000000000>:0
  at NLua.ObjectTranslator.CreateBaseClassMetatable (KeraLua.LuaState luaState) [0x00000] in <00000000000000000000000000000000>:0
  at NLua.ObjectTranslator..ctor (NLua.Lua interpreter, KeraLua.LuaState luaState) [0x00000] in <00000000000000000000000000000000>:0
  at NLua.Lua.Init () [0x00000] in <00000000000000000000000000000000>:0
  at NLua.Lua..ctor () [0x00000] in <00000000000000000000000000000000>:0
  at InitAddons.InitLuaFile (System.IO.FileInfo fileInfo) [0x00000] in <00000000000000000000000000000000>:0
  at InitAddons.FindLuaOnDir (System.String dirPath) [0x00000] in <00000000000000000000000000000000>:0
  at InitAddons.FindAddons () [0x00000] in <00000000000000000000000000000000>:0
  at InitAddons.Awake () [0x00000] in <00000000000000000000000000000000>:0

How can it be solved? It appears when I try to create an object "Lua luaState = new Lua ();"
Code fragment (this procedure is called after two others which are called in "Awake"):
    private void InitLuaFile(FileInfo fileInfo)
    {
        string filePath = fileInfo.FullName;
        Lua luaState;
        try
        {
            /* ERROR LINE */
            luaState = new Lua();
        }
        catch(Exception ex)
        {
            uLog.LogError("Error create object  \"Lua\":\n" + ex);
            return;
        }

        luaState.LoadCLRPackage();

        string luaText = File.ReadAllText(filePath);

        Scene scene = SceneManager.GetActiveScene();
        luaState["UnitySceneName"] = scene.name;
        luaState["UnitySceneIndex"] = scene.buildIndex;

        luaState.DoString(luaText);

        luaFiles.Add(new LuaFile {
            state = luaState,
            path = filePath
        });

        int count = luaFiles.Count - 1;
        luaFunctionReplaceOrCreate("FixedUpdate", ref _fixed_update, luaFiles[count]);
        luaFunctionReplaceOrCreate("Update", ref _update, luaFiles[count]);
        luaFunctionReplaceOrCreate("LateUpdate", ref _late_update, luaFiles[count]);

        if (directoryWatcher.Find(x => x == fileInfo.DirectoryName) == null)
        {
            FileSystemWatcher watcher = new FileSystemWatcher(fileInfo.DirectoryName, "*.lua");
            watcher.NotifyFilter = NotifyFilters.LastWrite;
            watcher.Changed += ActionChangeLuaFile;
            watcher.EnableRaisingEvents = true;
        }
        else
            uLog.LogWarning("The folder is already listening!");
    }

I'm getting this error as well.

Did anyone have any luck getting this to work?


Import incident date and time from NIBRS file

The boston_nibrs_foia.csv.gz file has the incident date and time, but we aren't currently ingesting it. We should import the data, but only for incidents that don't already have date/time data; the NIBRS data has the date and hour, but not the minute, which is present in other data sources.

merged and live


Wipro Holmes Connector is not working as the payload validation fails

We are unable to connect with the Wipro Holmes Connector as the payload validation fails with the time stamp parameter as below
ValueError: time data '16.10.2019, 05:17:57' does not match format '%Y-%m-%d %H:%M:%S'
Wipro Holmes expects the time stamp to be in the format '%Y-%m-%d %H:%M:%S' but getting it as %d.%m.%Y, %H:%M:%S

Waiting for the development endpoint ...

Fixed with the latest changes in the connector.


Fix for "No handler registered for command"

No handler registered for command [AspenDigital\Resizer\Jobs…\ResizeFanout]" error.

@salamalejkum Thanks for your contribution, but this does not apply to Laravel 5.5 (OctoberCMS 420+). Illuminate\Contracts\Bus\SelfHandling no longer exists.


[ADD] Object list call function

Hey @altanmur I think a good way to implement this would be to allow filter parameter on /object/<string:model>/<string:function> to give users a freedom to filter records however they want not just by ids only. For instance someone might want to do something like /object/products.template/unpublish/?filter=[["quantity", "=", 0]]


ionic2: alert input maxlength ?

let alert = Alert.create({
	title: 'name',
	inputs: [
		{ name: 'name', value: '' }
	],
	...
})

maxlength
How to Set Up ?
Run ionic info from terminal/cmd prompt: (paste output below)
ionic2 Beta 6

Hello! Thanks for opening an issue with us! As this seems like more of a support question of how to implement certain functionality i will urge that you ask this question on our forum (forum.ionicframework.com). Thanks for using Ionic!


Is it angular 1.4 compatibile?

In bower it needs angular 1.2. Is it compatibile with 1.4?

Have not been tested, but, seems compatibile

It is - works great with me. Can You change bower file?

@piernik Check version v0.8.0


Aggregate Device Category reporting in Snowplow Analytics skewed

Background
Aggregate mobile reporting is highly skewed. There is a similar thread running for the device_type field (link to this thread available below). However, for Aggregate Device Category reporting, an accurate report is unavailable that produces basic reports with a dimension breakdown of deviceCategory (using a GA reference here, I think they have nailed this definition, sorry) that is, deviceCategory field values is either mobile OR tablet OR desktop
Available Snowplow Analytics fields:

platform This is user defined but limited to the following field values as per table Common parameters (platform and event independent)
device_type An example field value == computer

Question about device category related fields in SP:

Will platform table going to be finalised and enabled without it being user defined?
Will platform table values going to split Mobile/Tablet into  separate field values?

Current Hack/ Solution deployed
Required

GTM Macro using detect device type .js
IGLU Schema to store this value

Steps to replicate this client side:

Create GTM Macro as custom javascript called {{SPplatformCategory}} and insert the below js in the field.

function deviceType(){
if( navigator.userAgent.match(/Mobi/i) ) {
var windowWidth = window.screen.width < window.outerWidth ?
window.screen.width : window.outerWidth;
if(windowWidth < 500){
deviceType = 'mobile';
} else {
deviceType = 'tablet';
}
}
else if( navigator.userAgent.match(/iPad/i) ){
deviceType = 'tablet';
}
else if( navigator.userAgent.match(/Tablet/i) ){
deviceType = 'tablet';
}
else {
deviceType = 'desktop'
};
return deviceType;
}

To test just create a tag in GTM and push the above into the dataLayer with firing rule global onload

dataLayer.push({
    'simonrumble': 'pornstar',
    'event': '{{SPplatformCategory}}'
 });

Create GTM tag for Snowplow Analytics initialisation script with IGLU - async with firing rule of all pages {{url}} matches RegEx .*

<!-- Snowplow starts plowing -->
<script type = "text/javascript"> ;
    (function (p, l, o, w, i, n, g) {
        if (!p[i]) {
            p.GlobalSnowplowNamespace = p.GlobalSnowplowNamespace || [];
            p.GlobalSnowplowNamespace.push(i);
            p[i] = function () {
                (p[i].q = p[i].q || []).push(arguments)
            };
            p[i].q = p[i].q || [];
            n = l.createElement(o);
            g = l.getElementsByTagName(o)[0];
            n.async = 1;
            n.src = w;
            g.parentNode.insertBefore(n, g)
        }
    }(window, document, "script", "//XXXXXXXX.cloudfront.net/2.0.0/sp.js", "snowplow"));
    window.snowplow('newTracker', 'cf', 'XXXXXX.cloudfront.net', {
        appId: '{{MY_appId}}',
        platform: '{{SPplatformCategory}}' //would be great to have SPplatformCategory placed here!
    });
     // window.snowplow('setUserId', 'alex 123');
     // window.snowplow('setUserIdFromLocation', 'id');
     // window.snowplow('setUserIdFromCookie', '_sp_id.4209')
     // window.snowplow('setCustomUrl', '/overridden-url/');
    window.snowplow('enableActivityTracking', 10, 10);
    window.snowplow('enableLinkClickTracking');
       // window.snowplow('trackPageView', 'Async Test');
    window.snowplow('trackPageView', null);

// This is an example custom context using SPplatformCategory as a field
    window.snowplow('trackPageView', null); [{
    schema: 'iglu:com.au.narbehisawesome/user/jsonschema/1-0-0',
    data: {
        SPplatformCategory: 'mobile'
    }
}]);
</script>
<!-- Snowplow stops plowing -->

Thoughts on the client side approach?
Related issues:

#756

Just a plug for this: it'd be great to add a dvce_category field alongside the other dvce_* fields that's one of "desktop", "mobile", "tablet". We do this kind of query via GA all the time.

Superceded by new useragent enrichment.


Repeat - Delete Button -> Add a class for styling

Would be nice to have a classname to hook onto so the Delete button can be styled
Example custom styled:

Delete Button in this src code:
https://github.com/crossfield/gutenblock/blob/master/controls/src/repeat/index.js

 this.delete(index, onChange)}>Delete item

I have a good idea for this, will try to do it this week


[full-ci] More cache cleanup

This pr adds more cleanup to https://github.com/owncloud/ocis/pull/6019
/cc @wkloucek

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/21736/68/1
:boom: To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/21736/tracing/space-members-can-be-invited-with-an-expiration-date-alice-2023-4-25-09-08-49.zip

failing e2e tests unrelated: they cannot find the correct place to click on because of moon constellation and bad timing ... 😬


Redact Kubernetes token from messages sent to Sentry

We do not want the Kubernetes token to be printed out in the errors that are sent to Sentry.
https://trello.com/c/LfLkccvb/963-redact-kubernetes-token-in-service-token-cache

@tomas-stefano quite right! have added one


[yaml] Normalize JdbcIO

This PR normalizes JdbcIO to work with the YAML framework. Tested with BigQueryIO read/write and built-in YAML transforms.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @robertwb


Document versioning

As soon as we approach a stable v1 of our proto files, we should document our approach to versioning the APIs and the generated packages for node and java:

semantic and guarantees in a vX package
semantic of the GitHub tags used for releasing packages and tagging generated go code

https://cloud.google.com/apis/design/versioning

Example: https://github.com/stroeer/tapir/pull/272


Check Redis pool connection for error

I'm running into runtime error: invalid memory address or nil pointer dereference and I think it's because Enqueue doesn't check to see if the connection it receives from the Redis pool is of type errorConnection, for example here:
https://github.com/gocraft/work/blob/master/enqueue.go#L46
I can submit a PR to add this check.

My error has nothing to do with this actually, but would checking conn.Err() still be a good idea?

Glad to hear you worked it out.
Re: checking conn.Err() explicitly, I don't think it's necessary because Do will also return an error on the broken connection.

I did this to hopefully make this more helpful for others in the future:  adc78a0ed73aee9382cad6fa7e15235ee030357c


Issue #305

Improved dependencies section and corrected grammar.

YES

Thanks for the contribution ! do checkout other issues as well ^_^


I am connecting Scrcpy 2.7 using nodejs client, even I pass max-size arg as 1920 buffer retrieve as 26674 x 13876 any suggestions?

"using nodejs client"

What nodejs client?
It probably does not respect the protocol used by the server.

I have created nodejs program to get raw encoded buffer from Scrcpy.

OK, so there's a bug in your code. Read the protocol documentation carefully: https://github.com/Genymobile/scrcpy/blob/master/doc/develop.md#protocol

@AjitStudy I'm not a specialist here but I'm working on Scrcpy-server right now to replace the old minicap in my application. My max size is working just fine, are you passing max-size or max_size? The correct is max_size and it must be a multiple of 16, if I'm not mistaken.


Document how to use file-loader correctly for renderer webpack configs

Assets are not getting loaded after making the binary using "yarn make" on all platform (windows/Mac/Linux).  We are getting error "net::ERR_FILE_NOT_FOUND". Looks like Js files are pointing to the proper location as per the package.json configuration. but assets and source files are located in different location.
And we are seeing the same issue for component source which uses Lazy import statements
const Login = React.lazy(() => import('./screens/login'));

E.g on Mac
Trying to load the png file from
/Contents/Resources/app/.webpack/renderer/main_window/33dbdd0177549353eeeb785d02c294af.png

But files are available in.
/Contents/Resources/app/.webpack/renderer/33dbdd0177549353eeeb785d02c294af.png

package.json
"plugins": [
        [
          "@electron-forge/plugin-webpack",
          {
            "mainConfig": "./webpack.main.config.js",
            "renderer": {
              "config": "./webpack.renderer.config.js",
              "entryPoints": [
                {
                  "html": "./src/index.html",
                  "js": "./src/app.tsx",
                  "name": "main_window"
                }
              ]
            }
          }
        ]
      ]

Sample Project https://github.com/jega-ms/electron-forge-react-typescript-webpack

File Listing

After landing on this issue and doing some of my own trial and error, I've come up with a solution that works both in dev and packaged, and combines various observations from this and linked issues.
Webpack setup
If you're using webpack5 (and you should be if you used the template), you no longer need file-loader or copy-webpack-plugin. Instead, you should rely on webpack's native asset management.
// webpack.rules.js
// Or in both your webpack.renderer.js and webpack.main.js if you keep them completely separate

module.exports = [
   // ... your other rules
   {
    // Note: I dont have `svg` here because I run my .svg through the `@svgr/webpack` loader,
    // but you can add it if you have no special requirements
    test: /\.(gif|icns|ico|jpg|png|otf|eot|woff|woff2|ttf)$/,
    type: 'asset/resource',
  },
]

Main process
Because Electron does magical things to an image based on the filename of the image, you should keep the original source file name in the output file name by configuring how webpack outputs asset names. Note that you can also do this for the renderer config if you prefer, but it's not a requirement since Chromium doesn't do anything magical based on the file name.
// `webpack.main.js`
module.exports = {
  entry: './src/main/index.ts',
  // ...other configs
  output: {
    // [file] is the key thing here. [query] and [fragment] are optional
    assetModuleFilename: '[file][query][fragment]',
  },
}

When using bundled files in the main process, make sure to resolve the bundled path:
// main/index.ts
import myImageFilePath from './path/to/file.png';
import trayImagePath from './path/to/trayImage.png';

// For example setting the dock icon
app.dock.setIcon(path.resolve(__dirname, myImageFilePath));

// Or setting the tray icon
const tray = new Tray(
    path.resolve(
      __dirname,
      trayImagePath,
    ),
  );

Renderer Processes
Because you can have many entrypoints, the webpack output of each entry point is nested under a renderer folder. By default, webpack outputs assets in the root output folder (which will be this same renderer folder). So your output file structure (inside of the .webpack folder) looks something like
> main
   - index.js
> renderer
   > entryPointOne
       - index.js
   > entryPointTwo
       - index.js
  - imageHash1.png
  - imageHash2.png

This means that in the outputted renderer/entryPointOne/index.js, we need to rewrite the image paths to one level above the index.js: ../. Note that this is essentially the same solve as the publicPath: '..' setting in file-loader from this related issue
// webpack.renderer.config.js
module.exports = {
  // ...other configs
  output: {
    publicPath: '../',
  },
}

Note that, like the main webpack config, you may change where webpack outputs its assets, but you still have to set the public path since it's outside of folder containing the index.js of each renderer entry point.
// webpack.renderer.config.js
module.exports = {
  // ...other configs
  output: {
    publicPath: '../myAssetFolder',
    // Note that here you are also keeping the original file name, but for the renderer you don't have to
    // and can simply rely on the default value of [hash][ext][query]
    assetModuleFilename: 'myAssetFolder/[file][query]',
  },
}

Here's a caveman solution, for my fellow Neanderthals.
Base64-encode the image.  Here's a handy tool for it:  https://github.com/veler/DevToys
Create a file like images.ts/images.js:
// TODO: Figure out how to use file-loader or Webpack Asset Modules later.  (If you're reading this two years later, congrats!  Your temporary solution became permanent.)
export const iconImage512x512Base64 = "data:image/png;base64,iVBORw0KGgoAAAA(etc. etc.)=";

Then in your TSX/JSX:
{/* Don't worry.  This is fine. */}
<img src={iconImage512x512Base64} />

I was able to to copy my assets into the development build with the help of copy-webpack-plugin.
Here's steps for my webpack forge .ts based project
To set up copy-webpack-plugin in your webpack.renderer.config.ts for copying assets to your app root folder, follow these steps:

Install copy-webpack-plugin
npm install copy-webpack-plugin --save-dev
yarn add copy-webpack-plugin --dev
Import copy-webpack-plugin in Your Webpack Configuration: At the top of your webpack.renderer.config.ts, add an import.
import CopyPlugin from 'copy-webpack-plugin';
Add CopyPlugin to your Plugins Array at webpack.plugins.ts. Adjust the from path according to where your assets are stored relative to the context of your webpack configuration.

//webpack.plugins.ts
import type IForkTsCheckerWebpackPlugin from 'fork-ts-checker-webpack-plugin';
import CopyPlugin from 'copy-webpack-plugin';

// eslint-disable-next-line @typescript-eslint/no-var-requires
const ForkTsCheckerWebpackPlugin: typeof IForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');

export const plugins = [
  new ForkTsCheckerWebpackPlugin({
    logger: 'webpack-infrastructure',
  }),
  new CopyPlugin({
    patterns: [
      { from: 'src/assets/', to: 'assets/' },
    ],
  }),
];

Content of my webpack config files:
//webpack.main.config.ts
import type { Configuration } from 'webpack';

import { rules } from './webpack.rules';
import { plugins } from './webpack.plugins';

export const mainConfig: Configuration = {
  entry: './src/index.ts',
  module: {
    rules,
  },
  plugins,
  resolve: {
    extensions: ['.js', '.ts', '.jsx', '.tsx', '.css', '.json'],
  },
  output: {
    assetModuleFilename: '[file][query][fragment]',
  },
};

//webpack.renderer.config.ts
import type { Configuration } from 'webpack';

import { rules } from './webpack.rules';
import { plugins } from './webpack.plugins';

rules.push({
  test: /\.css$/,
  use: [{ loader: 'style-loader' }, { loader: 'css-loader' }],
});

rules.push({
  test: /\.(png|jpe?g|gif|svg)$/i,
  use: [
    {
      loader: 'file-loader',
      // options: {
      //   name: 'assets/images/[name].[ext]',
      // },
    },
  ],
});

export const rendererConfig: Configuration = {
  module: {
    rules,
  },
  plugins,
  resolve: {
    extensions: ['.js', '.ts', '.jsx', '.tsx', '.css'],
  },
  output: {
    publicPath: '../',
  },
};

// webpack.rules.ts
import type { ModuleOptions } from 'webpack';

export const rules: Required<ModuleOptions>['rules'] = [
  // Add support for native node modules
  {
    // We're specifying native_modules in the test because the asset relocator loader generates a
    // "fake" .node file which is really a cjs file.
    test: /native_modules[/\\].+\.node$/,
    use: 'node-loader',
  },
  {
    test: /[/\\]node_modules[/\\].+\.(m?js|node)$/,
    parser: { amd: false },
    use: {
      loader: '@vercel/webpack-asset-relocator-loader',
      options: {
        outputAssetBase: 'native_modules',
      },
    },
  },
  {
    test: /\.tsx?$/,
    exclude: /(node_modules|\.webpack)/,
    use: {
      loader: 'ts-loader',
      options: {
        transpileOnly: true,
      },
    },
  },
  {
    test: /\.(gif|icns|ico|jpg|png|otf|eot|woff|woff2|ttf)$/,
    type: 'asset/resource',
  },
];

Hope this helps someone
related


Add support for odroid-m1

Everything's done except u-boot, which at this point is being built for a different board (evb_rk3568).
The m1 does come with u-boot and petitboot in an onboard SPI flash, so building a working u-boot isn't actually needed to get the board running.

thanks. I reviewing your changes and doing a test build.  Does this boot?

It does, yes. I've been booting daily from the NVME, via petitboot.
Booting from the EMMC should work using the embedded (but outdated) u-boot directly. I confess I haven't tested in a while, but can do it next week.

Sorry for the long delay, I just got around to test booting from the EMMC and it's broken.
It seems that the default UBOOT_ROOT from the *.bbclass is taking precedence over the machine defaults, which is wrong.
Since this PR is already merged (thanks!), I'll close it and create a new one for the fix. Sorry..

Turns out it was a simple fix, created a new PR.
I'm not allowed to close this as "merged", @akuster could you please do it? Thanks!

Opps sorry. Yeah I did it manually.
Thanks for adding the M1 support


Fixed ESP8266 issues

I updated all examples to reflect and the current API and how to use it correctly, especially certain examples which were faulty previously producing issues like #91, #92, #107, #93 and #89.
Additional thanks to the help of @abferguson, the compilation issues with the ESP8266 have been resolved (#99) and  should fix issues like #90.
Additionally I integrated the changes recommended in #89 which also fixes #101 and some tweaks of my one, so that the firmware actually retries to download instead of failing after one attempt. The changes have been tested thoroughly and are in the updated example and work with my ESP32.
Additionally while doing that I added support for not only MD5 hashes but support for MD2, MD4, SHA1, SHA224, SHA256, SHA384, SHA512 and RIPEMD160 with the newly created HashGenerator class.
Which makes it possible to now simply use the default SHA256 hash generated by ThingsBoard.
Furthermore the typo in sendAttributeJSON has been fixed so the data isn't send as Telemetry by mistake fixing #97.
Additionally the ThingsBoardHttp library has been improved to not only support Arduino but the ESP32/ESP8266 as well implementing the feature request in issue #60.
If the changes could be integrated, that would be highly appreciated @imbeacon.

Thanks a lot for the merge.
Would be highly appreciated if it were possible to release a new version 0.8.0 now that the changes have been merged

Thank you for participating in the project life, we will create a new release as soon as possible.


On boarding scene- Rewards cannot be claimed after closing the captcha modal

Explorer Alpha build versions:
0.27.0
Issue Description:
The rewards from Mat's quest and Tobor's quest cannot be claimed after closing the captcha modal. After closing the captcha you should be able to claim them by clicking on the character again if they weren't claimed before.
STR:

Open v0.27.0
Go to cryptonico.dcl.eth
Do the first time user experience and reach out to Mat
Finish Mat's quest and verify that a reward is given to you
Instead of accepting that reward , please click on the close button
Validate that you cannot open up the modal again when clicking on the character

Expected behaviour:
User should be able to click on the character and see the captcha modal again because the user did not receive the reward at all.
Current behaviour:
User does not receive the rewards from Tobor or Mat's quest
Evidence:
https://github.com/user-attachments/assets/9b396857-1372-4026-81c4-855fad3d76f2
https://github.com/user-attachments/assets/35088194-7ba8-4939-90c6-91213186df04
Additional Notes:
Windows 11 PRO
16 GB RAM
📂 Scene Repository
https://github.com/agustincarriso/dcl-sdk7-onboarding

@DafGreco is this 100% repro?


🐛 Bug: Invalid package attestation - 1.3.0

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Expected
Audit does not indicate invalid attestation
Actual
An npm audit indicates incorrect package attestation in version 1.3.0:
npm audit signatures
audited 1665 packages in 20s

1663 packages have verified registry signatures

14 packages have verified attestations

2 packages have invalid attestations:

<EMAIL_ADDRESS>(https://registry.npmjs.org/)
<EMAIL_ADDRESS>(https://registry.npmjs.org/)

Someone might have tampered with these packages since they were published on the registry!

Additional Info
node 20.11.0
npm 10.4.0

@shadaxv TBH it seems rather weird. The version 1.3.0 of ts-api-utils doesn't exist on GitHub (that's likely why it gets flagged by npm audit). Given the recent events around the XZ Utils backdoor, this looks rather suspicious to me and I would be careful!

🤷 yeah this was a confusing bit to look at. Since the issue hasn't happened again, I'd recommend going with a newer version of ts-api-utils to not get the warnings.

Oh, and this isn't the only package that had the same odd issue: https://github.com/nodemailer/nodemailer/issues/1634


Add pip install zenml[server] to relevant examples

Describe changes
This PR adds the server installation to examples that runs zenml up.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@dnth you can merge this i think!

Sure. Thanks for reviewing it Hamza!


Project is not dead

Just a heads up that this project is not dead, but focusing on it's core dependency https://github.com/Ghamza-Jd/jarust
Jarust is in active development so the API isn't stable yet which will make developing this sdk a bit trouble some, we're close to having a stable 1.0, after that we'll resume this one.
Also uniffi-rs released some nice features which will make this API of this sdk more robust

Resumed the work


Remove bundled viridis colormap

We currently bundle the viridis colormap with xarray:
https://github.com/pydata/xarray/blob/1c37d9ce526fecb9fdab2c82b3f46be06f55a128/xarray/plot/utils.py#L15-L26
https://github.com/pydata/xarray/blob/master/xarray/plot/default_colormap.csv
This is unnecessary these days and adds a small amount of packaging complexity. It's not unreasonable to expect at least matplotlib 1.5.x, which comes with viridis installed.

+1.  Do you want me to add this to my minimum versions update (#2204)?

@jhamman sure, that sounds great!

Done in be637d7.

closed via #2204


Add "export" to Props interface definition in all component index.d.ts files

Having standard Props interface defined as private makes it impossible to reuse the Props definition when creating your own custom version of the component.

Anybody helping with this?

Is anybody doing it? I'd like to slightly extend some components in my app and reusing existing props would be very convenient.
This sounds quite simple.


New user. Trouble with many things

Description of Problem or Question:
Problem N°1: When copying a scenario to use it with scenario editor all attempts crashes.
Problem N°2 Cant seem to find how to avoid getting a loop with first round mythos phase and starting all from beggingn upon returning to investigator phase.
Problem N°3 Cant find a way
Valkyrie Version
2.1.2

Hi

Problem N°1: When copying a scenario to use it with scenario editor all attempts crashes.

it's a known issue ( #936 ), will be fixed in next release

Problem N°2 Cant seem to find how to avoid getting a loop with first round mythos phase and starting all from beggingn upon returning to investigator phase.

The tutorial from @scrubbless is a good start for scenario creation.
You should have a look at it :
https://docs.google.com/document/d/1Gi5gTwKkw84Px0Lvk-bJ3Aml_vF3ZoljjB6a8FjWGt8

Problem N°3 Cant find a way

Please pick a madness card now ^^

:) great, many thanks
So problem n° 1 solved (get a clue token)
Problem N° 2 i guess i solved it too..the structure so far goes like....QUEST....EVENT TO SHOW UI PROLOG (IMAGE, TEXT AND CONTINUE BUTTOM THAT LINKS TO FIRST TILE, TOKENS, etc.
Already placed also first mythos...structure goes like this...rename Mitos round 1....insert dialog (will test 2 or suffer 1 horror facedown)....trigger mhytos....assign button: mythos flavour=0....insert .button none.
I am not sure how to add a second mythos without appearing in the same mythos phase
:(
still tinkering

well i cant seem to get it done..i am sharing an image of both mythos events so if anyone knows how to make them appear ordered will help a lot

I'll give this a better read tomorrow and respond.
For you insight, 'mythos' trigged events will always run. I think it's random in which order they are picked.
Personally I use one event and put the mythos trigger on it. The event is left empty and then chain i events from it, using a 'test' on each event to indocate if it is 'on' or 'off'.
This way you know your triggered mythos event will always run. But you are in control of what event it runs and in what order.
If you turn off normal mythos events your need to turn them back on at endround or start round. You can't do it during the mythos otherwise it'll trigger after your event finishes.

Many thanks benrq and scrubbles! Get a clue token each! {action} Can close the issue if you have the key item :)

Problem N°1: Solved exporte de zip file and manually located it in the MOM editor file
Problem N°2 Solved, finally used one event for each mythos phase.-
trigger: Mythos
Button: Continue
Test: #round==1  this order assign the mythos to round one...so if i put 2 it appears in round 2 and so on.

Happy to help  👍
Join us on Discord if you want to chat :)
https://discord.gg/yrVeSVt

Yeh, always happy to help :)


About the performance of BMSG-GAN

Hi, you published BBMSG-GAN. And In order to match the performance of ProGANs, you increased the size of the Discriminator (the one here in BMSG-GAN is technically half that of ProGAN) and use tricks like Batch Spoofing. So, do you mean that the performance of Pro-GANs is better than BMSG-GAN? But BBMSG-GAN is better than Pro-GANs? Of course, the number of parameters is bigger?

@Iceland-Leo
Sorry for the late reply. I have been lesser and lesser time these days.
Long story short: This repo doesn't use batch-spoofing and the effective discriminator is half of ProGAN's discriminator.
The BBMSG-GAN fixes that and the discriminator is comparable to ProGAN's discriminator. Please note that the Generator is still the same for both.
Btw, the capacity problem was also admitted by styleganv2. So, basically my conjecture was true :smile:
Hope this helps :+1:.
Cheers :beers:!
@akanimax

OK！Thank you so much

@akanimax Sorry, one more question. GAN is unstable. May I ask how to get the IS score in your article experient? Is it the average of some epoch results? Or simply choose the maximum IS score?


Prevent overflow in concatenate epochs

Reference issue
Fixes #5495.
What does this implement/fix?
In mne.concatenate_epochs(), when adding an offset to each iteration of epochs, don't update the offset with itself, as this leads to an overflow with large numbers of epochs.

if it's a bug fix, can you update the what's new file? https://github.com/mne-tools/mne-python/blob/master/doc/whats_new.rst

Thanks @ilogue


Support for Arm architectures

I have a kubernetes cluster running ElasticSearch 7.14 and would really like to use ElastAlert2 to monitor it. It should be as simple as adjusting your build pipeline to build for multi architectures:
docker buildx build --platform linux/amd64,linux/arm64 -t jertel/elastalert:2.3.1 . --push
This command will take quite a bit longer, so not desirable during development iterations, just release.
I cloned the repo and ran it myself, and it seems to work fine.

This is implemented for Docker Hub only. Currently the latest tag has amd64 and arm64. armv7 is always problematic due to rust/crypto/cffi broken deps so I've opted to leave it out. If there's demand I may also push multi-arch up to the GitHub CR, but for now arm64 is only available on Docker Hub.


Request for "Delete All Temp Files" Command for the plugin

Currently, the extension generates temporary files whenever a specific action is performed. However, there is no built-in option to delete all these temporary files at once.
I would like to suggest adding a new command to the command palette that allows users to delete all the generated temporary files in one go. This would greatly enhance the usability of the plugin and help keep the workspace clean as these tempfiles shows up in the file switcher.

I am willing to contribute to fixing this issue. Please let me know.

Thank you for your suggestion.
Implementing a feature to delete all created temporary files at once is impractical due to technical reasons. Users can set the tempfile.newFilePath configuration to any location, making an all-deletion command risky.
Instead, I recommend setting tempfile.newFilePath to a specific folder in your workspace, like {{wsdir}}/.tempfile/{{YYYY}}{{MM}}{{DD}}_{{HH}}{{mm}}{{ss}}{{SSS}}.md. This way, you can delete all temporary files by simply removing one folder.

This seems promising indeed. I'm going to test out this functionality and will provide feedback soon! 🙃

@wtetsu Yes the setting worked. Closing the issue :)


Operators ">=" and "<=" are not working as expected

While working on Swayswap, I noticed that the operators above were not doing the right thing. I had to change

x >= y to x > y - 1
x <= y to x < y + 1

I will post an actual example later.

Ge and Le are implemented as !< and !>, but that should be equivalent with integers. I can fix this in a PR though now that Supertraits exist so >= and <= can be properly implemented unless you already a had a fix in mind?

@sezna have an open PR already here https://github.com/FuelLabs/sway/pull/1092


Implement lookups for witness generation.

This is partially implemented, but to a very limited degree:
The first element of the LHS has to be known and it looks this value up in the first element of the RHS and then matches all the other components.

@chriseth close?

@chriseth close?


bazel: 0.17.1 -> 0.18.0

Motivation for this change
Things done

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

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

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

@GrahamcOfBorg build bazel

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: bazel
Partial log (click to expand)
//examples/cpp:hello-success_test                                        PASSED in 0.1s
//examples/java-native/src/test/java/com/example/myproject:hello         PASSED in 0.3s

Executed 2 out of 2 tests: 2 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
INFO: Build completed successfully, 19 total actions
installing
post-installation fixup
patching script interpreter paths in /nix/store/hkdqpmqzigpjy4bmx0yd3xyvcrrq2gv2-bazel-0.18.0
/nix/store/hkdqpmqzigpjy4bmx0yd3xyvcrrq2gv2-bazel-0.18.0

Success on x86_64-linux (full log)
Attempted: bazel
Partial log (click to expand)
//examples/java-native/src/test/java/com/example/myproject:hello         PASSED in 0.4s

Executed 2 out of 2 tests: 2 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
INFO: Build completed successfully, 21 total actions
installing
post-installation fixup
patching script interpreter paths in /nix/store/nfmcvjngqsikj6pj5rr4qdd7vc7rpf2n-bazel-0.18.0
checking for references to /tmp/.bazel-1000 in /nix/store/nfmcvjngqsikj6pj5rr4qdd7vc7rpf2n-bazel-0.18.0...
/nix/store/nfmcvjngqsikj6pj5rr4qdd7vc7rpf2n-bazel-0.18.0

cc @mboes

LGTM


grafana, grafana-image-renderer: bump for CVE-2022-31176

Description of changes
https://grafana.com/blog/2022/08/30/security-release-new-versions-of-grafana-and-grafana-image-renderer-with-a-high-severity-security-fix-for-cve-2022-31176/
Update grafana to 9.1.2, grafana-image-renderer to 3.6.1.
grafana update done using the provided update script. For grafana-image-renderer I followed the instructions in default.nix.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Local testing seems fine, deploying to my personal infrastructure. If that works well, I'll merge :)


Selection outline on root element doesn't fit after change in properties panel

Reproduce:

create new diagram
change process id in the properties panel
click/hover over the start element

--> selection outline is four times bigger

add a pool
change process id
click in the upper left corner of the pool

--> selection outline is very small

Related to bpmn-io/diagram-js#149?

Fixed with https://github.com/bpmn-io/diagram-js/commit/90ca56f883dfa9b72feee782afbdcf5422899387


Cyclic jsdoc warnings

    /**
     * Updates app state by fetching new data from API server for latitude and longitude of new location.
     *
     * @param {number} lat Latitude
     * @param {number} lng Longitude
     *
     * @returns {undefined}
     */

Above code gives warning: Newline required after description, and Redundant return statement.
    /**
     * Updates app state by fetching new data from API server for latitude and longitude of new location.

     * @param {number} lat Latitude
     * @param {number} lng Longitude
     *
     * @returns {undefined}
     */

Jsdoc can't read after description here apparently because of missing *. What do Newline required mean here?
Also,
    /**
     * Updates app state by fetching new data from API server for latitude and longitude of new location.
     *
     * @param {number} lat Latitude
     * @param {number} lng Longitude
     *
     */

This code gives warning: Missing JSDoc @returns for function
The subjected function do not have a return statement. Adding a return {undefined} says redundant return, and removing it says return required.

My guess is that you have a local eslint thats extending canonical rules.

On Nov 19, 2015, at 18:57, Charanjit Singh<EMAIL_ADDRESS>wrote:
/**
 * Updates app state by fetching new data from API server for latitude and longitude of new location.
 *
 * @param {number} lat Latitude
 * @param {number} lng Longitude
 *
 * @returns {undefined}
 */

Above code gives warning: Newline required after description, and Redundant return statement.
/**
 * Updates app state by fetching new data from API server for latitude and longitude of new location.

 * @param {number} lat Latitude
 * @param {number} lng Longitude
 *
 * @returns {undefined}
 */

Jsdoc can't read after description here apparently because of missing *. What do Newline required mean here?
Also,
/**
 * Updates app state by fetching new data from API server for latitude and longitude of new location.
 *
 * @param {number} lat Latitude
 * @param {number} lng Longitude
 *
 */

This code gives warning: Missing JSDoc @returns for function
The subjected function do not have a return statement. Adding a return {undefined} says redundant return, and removing it says return required.
—
Reply to this email directly or view it on GitHub.

No I made sure to remove that this time. I dont' even have a global eslintrc

curiosity:~ gajus$ echo '/**
 * Updates app state by fetching new data from API server for latitude and longitude of new location.
 *
 * @param {number} lat Latitude
 * @param {number} lng Longitude
 * @returns {undefined}
 */
export default () => {
    return 'test';
};' | canonical --stdin --linter js --output-format json
{
    "messages": [],
    "errorCount": 0,
    "warningCount": 0
}

These command line additions are already saving me time. : )

The error was that the function I was documenting was a class function (foo() { }), and it could not recognise that syntax. Changing it to foo = () => {} solves the problem.
I am closing this issue since turns out that it don't really belong to canonical. Not sure where it belongs.


Deleted my account but still received emails!

Hello, I need help deleting my account completely.
Description
I signed up using my github account (AbeTavarez) last year. I deleted my account but I’m still getting all emails notifications.
Expected Behavior
I need to stop all notifications coming from your app asap, I’m missing important emails because of the amount of emails send a day.
Current Behavior
Currently is sending dozens of emails per day.
Is this the best way to solve this issue?
Please help!

Looking at this now

I don't see a user with your github username in the database. Are you still getting emails? Can you send me the email address you're getting them delivered to? If you don't want to post it here you can find my email address in my github profile.

I got one other report at around the same time. I'm wondering what you see when you click the "delete" link. I'm thinking maybe sendgrid had a short outage for their URL service.

Hey thank for looking into this.
My email is<EMAIL_ADDRESS>

When I clicked on the delete link it just confirmed that I wanted to delete the account and it logged me out.

Think you're out of the DB, let me know if you're still getting emails.


Update log level of skipped files message

Hello.
I suggest changing log level of "skipped" files because in production use we don't want to know about skipped files.
We will delete, and we need to know what will be deleted. Not what will be skipped.

The second reason.
When we use wal-g retain job, we have very big log files with a lot of messages like:
INFO: 2019/12/06 16:43:49.108388   skipped: wal_005/000000010000127700000071.lz4
INFO: 2019/12/06 16:43:49.108395   skipped: wal_005/000000010000127700000072.lz4
INFO: 2019/12/06 16:43:49.108406   skipped: wal_005/000000010000127700000073.lz4
INFO: 2019/12/06 16:43:49.108413   skipped: wal_005/000000010000127700000074.lz4
INFO: 2019/12/06 16:43:49.108424   skipped: wal_005/000000010000127700000075.lz4
INFO: 2019/12/06 16:43:49.108432   skipped: wal_005/000000010000127700000076.lz4
INFO: 2019/12/06 16:43:49.108443   skipped: wal_005/000000010000127700000077.lz4
INFO: 2019/12/06 16:43:49.108462   skipped: wal_005/000000010000127700000078.lz4
INFO: 2019/12/06 16:43:49.108473   skipped: wal_005/000000010000127700000079.lz4
INFO: 2019/12/06 16:43:49.108482   skipped: wal_005/00000001000012770000007A.lz4
INFO: 2019/12/06 16:43:49.108493   skipped: wal_005/00000001000012770000007B.lz4
INFO: 2019/12/06 16:43:49.108500   skipped: wal_005/00000001000012770000007C.lz4
INFO: 2019/12/06 16:43:49.108511   skipped: wal_005/00000001000012770000007D.lz4
INFO: 2019/12/06 16:43:49.108518   skipped: wal_005/00000001000012770000007E.lz4
INFO: 2019/12/06 16:43:49.108529   skipped: wal_005/00000001000012770000007F.lz4
INFO: 2019/12/06 16:43:49.108536   skipped: wal_005/000000010000127700000080.lz4
INFO: 2019/12/06 16:43:49.108547   skipped: wal_005/000000010000127700000081.lz4
INFO: 2019/12/06 16:43:49.108555   skipped: wal_005/000000010000127700000082.lz4
INFO: 2019/12/06 16:43:49.108565   skipped: wal_005/000000010000127700000083.lz4
INFO: 2019/12/06 16:43:49.108573   skipped: wal_005/000000010000127700000084.lz4
INFO: 2019/12/06 16:43:49.108583   skipped: wal_005/000000010000127700000085.lz4
INFO: 2019/12/06 16:43:49.108590   skipped: wal_005/000000010000127700000086.lz4
INFO: 2019/12/06 16:43:49.108603   skipped: wal_005/000000010000127700000087.lz4
INFO: 2019/12/06 16:43:49.108610   skipped: wal_005/000000010000127700000088.lz4
INFO: 2019/12/06 16:43:49.108621   skipped: wal_005/000000010000127700000089.lz4
INFO: 2019/12/06 16:43:49.108628   skipped: wal_005/00000001000012770000008A.lz4
INFO: 2019/12/06 16:43:49.108639   skipped: wal_005/00000001000012770000008B.lz4
INFO: 2019/12/06 16:43:49.108646   skipped: wal_005/00000001000012770000008C.lz4
INFO: 2019/12/06 16:43:49.108657   skipped: wal_005/00000001000012770000008D.lz4
INFO: 2019/12/06 16:43:49.108664   skipped: wal_005/00000001000012770000008E.lz4
INFO: 2019/12/06 16:43:49.108675   skipped: wal_005/00000001000012770000008F.lz4
INFO: 2019/12/06 16:43:49.108682   skipped: wal_005/000000010000127700000090.lz4
INFO: 2019/12/06 16:43:49.108693   skipped: wal_005/000000010000127700000091.lz4
INFO: 2019/12/06 16:43:49.108700   skipped: wal_005/000000010000127700000092.lz4
INFO: 2019/12/06 16:43:49.108711   skipped: wal_005/000000010000127700000093.lz4
INFO: 2019/12/06 16:43:49.108719   skipped: wal_005/000000010000127700000094.lz4
INFO: 2019/12/06 16:43:49.108730   skipped: wal_005/000000010000127700000095.lz4
INFO: 2019/12/06 16:43:49.108737   skipped: wal_005/000000010000127700000096.lz4
INFO: 2019/12/06 16:43:49.108748   skipped: wal_005/000000010000127700000097.lz4
INFO: 2019/12/06 16:43:49.108755   skipped: wal_005/000000010000127700000098.lz4
INFO: 2019/12/06 16:43:49.108766   skipped: wal_005/000000010000127700000099.lz4
INFO: 2019/12/06 16:43:49.108774   skipped: wal_005/00000001000012770000009A.lz4
INFO: 2019/12/06 16:43:49.108784   skipped: wal_005/00000001000012770000009B.lz4
INFO: 2019/12/06 16:43:49.108792   skipped: wal_005/00000001000012770000009C.lz4
INFO: 2019/12/06 16:43:49.108802   skipped: wal_005/00000001000012770000009D.lz4
INFO: 2019/12/06 16:43:49.108809   skipped: wal_005/00000001000012770000009E.lz4
INFO: 2019/12/06 16:43:49.108820   skipped: wal_005/00000001000012770000009F.lz4
INFO: 2019/12/06 16:43:49.108827   skipped: wal_005/0000000100001277000000A0.lz4
INFO: 2019/12/06 16:43:49.108840   skipped: wal_005/0000000100001277000000A1.lz4
INFO: 2019/12/06 16:43:49.108847   skipped: wal_005/0000000100001277000000A2.lz4
INFO: 2019/12/06 16:43:49.108858   skipped: wal_005/0000000100001277000000A3.lz4

I think it's good for debug on dev environment, but not in production use.


Modified code to use a sqlite DB instead of csv

Modified app.py to use an sqlite DB instead of using the CSV to allow for larger databases and reliability.

Changed the styling to use tailwind css to allow for easier styling and responsiveness. Added a quantity system to the DB to allow for tracking, and organization. Quantities can be quickly updated through the added add and subtract buttons on the item card.

This is some really cool work thank you for taking the time, I only have one note. I would prefer the Add item form to drop down instead of over laying.

I will fix it after I’m done work today.

Honestly I love everything you've done it is beautiful, cannot thank you enough for volunteering your time.

When editing an item, if you hit cancel on every prompt it will display everything as null. After some finicking with it (without refreshing) I tried to delete the null item and it locked the database requiring me to restart it.

@Callsign-Carrot yeah I'm kind of aware of this issue, it happens on the CSV version as well. There's a couple things I can do, option one I ignore it, option two I fix it, option three I get rid of the cancel button, 🤣🤣

@nikpcenicni I hope you don't mind I took the liberty of making the changes myself, I tested everything it should work fine. But if you notice anything wrong let me know


Get CI to check if demo artwork renders successfully

We want CI to guard against breaking the renderability of the demo artwork.
@TrueDoctor how easy is this?

We should be able to just add a unit test for this right?

Yes, that was what I meant by CI (unit tests checked by CI).

In that case pretty easy

Feel free to add a test for this when you get a little spare time then! It would be valuable in the short-term to help us avoid mistakes. It just needs to ensure the actual graph renders real output.

https://github.com/GraphiteEditor/Graphite/blob/444929adbfa090f1b20fbf4c6f3a832bb4a826cd/editor/src/dispatcher.rs#L463-L471


Use a valid example for the testAssemblyVer2 property

The existing sample is not valid and won't work.  Multiple users have
wasted time with a bad example.
This addresses #1580

@jimmylewis : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@jimmylewis Do you have any thread going with Andy on this? What are the updates here.

Fixed in another PR


DoorBird D301A

Is the D301A not compatible? Adapter ist not able to connect.

COMPATIBLE DEVICES

Device
Hardware version
Firmware version

DoorBird Video Door Station D10x
1.00 and above
000099 and above

DoorBird Video Door Station D20x
1.00 and above
000099 and above

DoorBird Video Door Station D21x
1.00 and above
000108 and above

BirdGuard B10x
1.00 and above
000099 and above

DoorBird Video Door Station D11x
1.00 and above
000130 and above


Get sheet in Excel/OpenOffice by name

Is there a way to get a sheet by name rather than number?

@mcarans
Hi. Not in current tabulator version. But I suppose it's possible to implement.

This is important because getting sheets by number is brittle if there are lots of sheets because you cannot be sure that the number will be fixed (eg. doc owner could copy sheet data to another sheet and rename sheets accordingly)


Reconcile tasks when recovering from failure

After recovering from failure, reconcile the TaskStatus of non-terminal tasks.
Notes:
Ben Mahler's Reconciliation document, recommends an algorithm to be used by frameworks for reconciliation.

We should upgrade the Mesos dep to 0.21.1 to get improved reconciliation semantics.
BenM's official doc is now at http://mesos.apache.org/documentation/latest/reconciliation/


pipeline support

Also added replaceWith support

Though looks like Travis failed the build

Yeah - I need to finish off FLE before the build will be green