I am working on a flutter project based on google_maps_flutter and the Geolocator plugin

The problem is that when I add the geolocator plugin to my project my project will not build when I run it. it presents a build error. But with the geolocator plugin, it builds and works just fine.
Any help will be much appreciated.
attached is a picture of the error message presented

Could you please add the output of flutter doctor?

@Awumboro I dont know if am the only one who didnt understand the error you said "The problem is that when I add the geolocator plugin to my project my project will not build when I run it. it presents a build error. But with the geolocator plugin, it builds and works just fine."
Which plugin works fine when you run the project?
However for the error, I think it comes with incompatible plugin versions with the gradle, you may sort to either downgrade or upgrade to match the dependencies. For android X incompatibilities check this documentation how to solve ithttps://flutter.dev/docs/development/packages-and-plugins/androidx-compatibility and If you want or need to avoid migrating to AndroidX, you’ll need to pin your plugin dependencies in your pubspec.yaml to the last major version from before they were migrated.
Or in you can set multidexenabled to true in your android/app/build.gradle file like below
` defaultConfig {
// TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
applicationId "yourappname"
minSdkVersion 16
targetSdkVersion 28
versionCode flutterVersionCode.toInteger()
versionName flutterVersionName
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
multiDexEnabled true
}`
then add a multi dex dependency, under dependencies, within the same file
dependency{  implementation 'com.android.support:multidex:1.0.3' }

I'm sorry the problem was not very clear.
The problem is that Google map flutter works fine on its on, geolocation
plug in works fine in its own. However, they don't work well together.
But I will try out your suggestions and see how it turns out.
Thanks for your help. I'll stay in touch
On Sep 25, 2019 4:02 PM, "Maureen Josephine"<EMAIL_ADDRESS>wrote:

@Awumboro https://github.com/Awumboro I dont know if am the only one
who didnt understand the error you said "The problem is that when I add the geolocator
plugin to my project my project will not build when I run it. it
presents a build error. But with the geolocator plugin, it builds and
works just fine."
Which plugin works fine when you run the project?
However for the error, I think it comes with incompatible plugin versions
with the gradle, you may sort to either downgrade or upgrade to match the
dependencies. For android X incompatibilities check this documentation how
to solve ithttps://flutter.dev/docs/development/packages-and-
plugins/androidx-compatibility http://url and If you want or need to
avoid migrating to AndroidX, you’ll need to pin your plugin dependencies in
your pubspec.yaml to the last major version from before they were migrated.
Or in you can set multidexenabled to true in your
android/app/build.gradle file like below
` defaultConfig {
// TODO: Specify your own unique Application ID (
https://developer.android.com/studio/build/application-id.html).
applicationId "yourappname"
minSdkVersion 16
targetSdkVersion 28
versionCode flutterVersionCode.toInteger()
versionName flutterVersionName
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
multiDexEnabled true
}`
then add a multi dex dependency, under dependencies, within the same file
dependency{ implementation 'com.android.support:multidex:1.0.3' }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/41064?email_source=notifications&email_token=ALJEVCH2VHKWZP47KINCGZLQLODSJA5CNFSM4IZEGOUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7SNTDA#issuecomment-535091596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALJEVCH6E3DAH3UTWPHZHI3QLODSJANCNFSM4IZEGOUA
.

Have you checked all the details on androidX in the readme of geolocator?
The best thing you can do is create a new project with the option androidX (do a flutter create - h to get the exact parameters) the copy all your Dart files and your pubspec into this new project

Hello @Awumboro !
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the issue, if you have any more information for us; we will reopen it right away!
Thank you for your contribution.
P.S. If anyone still experience the same problem, please file a new issue with the information required in the template.
All system setups can be slightly different so it’s always better to open new issues and reference related issues.


tf.while_loop allow to vary shapes by default

I tried everything with tf.while_loop. In nested loops I always get ValueError due to the shape.
I think the problem is with shape_invariants.
In my opinion, it's a bad feature that a developer should think about the initial shape of the loop variable. I think that to allow the shape to vary across iterations must be by deafult.
So one more parameter should be, for exmaple, shape_variation, that can be True or False. If shape_variation = False - we need to define shape_invariant. If shape_variation = True - shape has been allowed to vary across iterations, so shape_invariant doesn't need to be defined.
So in my opinion, it is necessary to correct this feature in the way I suggested

@vasilevskykv
Do you have any use case that requires the feature you are interested in? Please feel free to submit a PR if you have use cases that supports that feature.Thanks!

The case of every loop. The developer doesn't need to be concerned about the shape. It is impossible to make a correct nested loop because of the shape_invariant. Because the ValueError will be always:
ValueError: Input tensor 'while/while/Const:0' enters the loop with shape (), but has shape (3,) after one iteration. To allow the shape to vary across iterations, use the shape_invariants argument of tf.while_loop to specify a less-specific shape.

@vasilevskykv
Looks like duplicate of #45337. Can we close the issue here and track in #45337. Thanks!

The problem in 45337 didn't solve

The developer doesn't need to be concerned about the shape.

Yes, they do. Providing exact shapes yields optimized computation graphs, which is often critical in writing efficient operations, layers and models. Similarly, while shape_invariants allows to relax part of the loop variables' shapes, it also enables optimizing what can be (by partially or fully defining the shape of some of the variables). Having a coercive behavior as default can also be seen as a way to have developers offer some thoughts to what they are doing, and therefore push them towards writing better code - which is what they are supposed to do, in my humble opinion.
If you are truly annoyed about writing specs, you may try to write loops in a pythonic way and have Autograph take on part of the work.


fix: allow server to return conflict information

Seems the HandleError function hasn't been updated in a while and was stripping off the reason data from server. When it's a conflict it is allowed to be returned so the UI can display conflicts.
These differ from other situations in which the SDK needed to return session data + errors during replay. In this case the errors came from the server instead of SDK so it's more appropriate to keep the server as source of truth.

:tada: This PR is included in version 0.316.2 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update case-app to 2.0.5

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

Files still referring to the old version number
The following files still refer to the old version number (1.2.0).
You might want to review and update them manually.
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.alexarchambault", artifactId = "case-app" } ]

labels: library-update, semver-major, old-version-remains

Superseded by #54.


bump the build image to golang 1.18.2 in EC

This PR bumps the version of golang 1.18.2.

/retest


Project bootstrapping

[ ] add a templates directory with cookiecutter projects - https://cookiecutter.readthedocs.io/en/stable/advanced/directories.html
[ ] make a simple CLI so that pipx crawlee --template some-template-name project-dir/ works

[ ] the CLI should be just a simple wrapper around cookiecutter that always uses the current master (for fetching templates)
[ ] it could be beneficial to use inquirer
available templates should be

[ ] ??? simple playwright project
[ ] ??? simple beautifulsoup project

make a simple CLI so that pipx crawlee --template some-template-name project-dir/ works

Ideally it would be pipx crawlee create project-dir, --template arg should be optional, if not provided the inquirer should ask the user to pick one of the existing templates (same if the provided template is non-existent).

available templates should be

Let's start with those two, I would like to see "project templates" as we have in the JS version, so with a basic setup of scraper that dynamically goes though the crawlee.dev:
https://github.com/apify/crawlee/tree/master/packages/templates/templates/cheerio-ts
https://github.com/apify/crawlee/tree/master/packages/templates/templates/playwright-ts


Allow seeding the crawler with a list of URLs to crawl

I need to crawl a site multiple times to get updated content on a regular basis.
In order to save on bandwidth and avoid unnecessary work, I have customized the PageRequester class by deriving from it so that I can add an If-Modified-Since header to only request pages that have been modified since the last crawl. (I know I could have just  added a delegate for ShouldDownloadPageContent to make the decision, it's much cleaner to use HTTP headers to tell the server not to send the response if the page wasn't modified, than to let the server send the response but have the crawler ignore it).
The problem I'm having is that let's say the root page wasn't modified. In this case it's not going to be fetched and no links will ever be scheduled for crawling. This is going to stop the crawl immediately.
My request is to allow the crawler to be seeded with a list of URLs to crawl. In the first crawl session, I'm going to supply only the root Uri. In each subsequent crawl session I'm going to supply all URLs that have been crawled before for scheduling. This should allow the crawler to continue crawling those links even if any page containing those links isn't crawled due to not being modified.
When I looked I found that if I get access to the Scheduler object on the CrawlContext I can schedule those links. But the problem is that the CrawlContext is not available before starting the crawl; it's only passed when events/delegates are raised/invoked. I can certainly try to inherit from WebCrawler (or PoliteWebCrawler) and expose the context/scheduler or a method to seed the crawler with a list of URLs.
I guess my request is either:

Expose the CrawlContext on the IWebCrawler interface,
Expose the IScheduler interface through the IWebCrawler interface (doesn't feel right), or
Add an override to the IWebCrawler.Crawl() method that takes IEnumerable<Uri>

Hi khaledh, I am also trying to feed list of Uris to the crawler so that I can benefit from the scheduling feature. Could you illustrate how you scheduled the list of urls yourself in your derived crawler class? Thank you.


[$500] Android -Thread -Text entered offline in left thread renders in compose box online in thread

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

Version Number:  1.4.24-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:
Action Performed:

Open the app and log in
Open any chat, send a message and start a thread
Disable the internet connection
Leave the thread
Open the left thread
Enter text in the compose box
Return online and send the message
Send a new message and start a new thread
Leave the thread
Open the left thread

Expected Result:
The compose box is empty
Actual Result:
The text that was entered offline renders in the compose box in a new thread online
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/6e839dd9-d06f-4396-86d0-7cfa68ed36d3
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~015e48d0ca070c7254
Upwork Job ID:<PHONE_NUMBER>184891392
Last Price Increase: 2024-01-10

Proposal
Please re-state the problem that we are trying to solve in this issue.
The text entered on a left thread composer will be shown again when we open another left thread.
What is the root cause of that problem?
When we leave a thread and rejoin it, we are loading the report from the BE and while loading, we show a ReportActionCompose "placeholder".
https://github.com/Expensify/App/blob/823c5e2b896adebafafa3c5c93f4a3e418cb8603/src/pages/home/ReportScreen.js#L534-L547
Notice that we don't pass any report data to the placeholder composer. If the report is empty, the default value will be {reportID: '0'}
https://github.com/Expensify/App/blob/823c5e2b896adebafafa3c5c93f4a3e418cb8603/src/pages/home/report/ReportFooter.js#L55
And every time we type something, the message draft will be saved to the draft of '0'. So, when we join another left thread, we can see the previous draft that is saved on '0'.
What changes do you think we should make in order to solve the problem?

We should pass at minimum the reportID to the placeholder composer, so any draft will be saved to the reportID instead of '0'.
report={{reportID}}

// reportID here is from the route params

@sobitneupane proposal for you! ^

Actually, this has the same root cause as https://github.com/Expensify/App/issues/31705 and the solution proposed there is the same as above.

@bernhardoj thanks! I'll close for now and we'll reopen if we can still repro after https://github.com/Expensify/App/issues/31705 is fixed


Add tests

Add test vectors using different formats. Verify against good output from minimp3.
Add unit tests for specific algorithms.

Would fuzzing also be desireable?

Yep, fuzzing would be great. Currently this crate is unmaintained (I'll add a note to the README), but I'll accept PRs if someone wanted to improve it.


Erroneous highlight of HTML comment-out tags

Please include the language you are using, a screenshot, and copy/pastable example.

  1
  2

  5

On v0.0.28, HTML comment-out punctuation  is being detected as brackets and coloured as per the default "bracket-pair-colorizer-2.colors": ["Gold"...], configuration.
Disabling the extension resolved the syntax highlighting anomaly which helped confirm the issue was with Bracket Pair Colorizer 2 and not due to any other conflicting custom colours or extensions.
Please feel free to let me know if any more information is required. I've attached my VS Code/OS details summary below. Thanks for your time!
Click to view VS Code/OS details:
Version: 1.33.1 (user setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

I have excluded HTML from the addon, by adding
"bracket-pair-colorizer-2.excludedLanguages": ["html"]
into settings.json

Adding "bracket-pair-colorizer-2.excludedLanguages": ["html"], doesn't fix it for me, it actually exclude everything.
I've even tried a workaround using textMateRules to re-colour the comment tags to no avail


Invoices user filter

Conditionally render filters button when no filters
Added canListUsers authorization check
Added Invoices user filter

IOS build fixed


Error when using js_name with both getter and setter

Describe the Bug
It's not possible to rename both getter & setter with js_name=xxx
Steps to Reproduce
build: wasm-pack build
use wasm_bindgen::prelude::*;

#[wasm_bindgen]
pub struct MyStruct;

#[wasm_bindgen]
impl MyStruct {
	#[wasm_bindgen(getter)]
	#[wasm_bindgen(js_name = "myProp")]
    pub fn my_prop(&self) -> u32 {
        0
    }

    #[wasm_bindgen(setter)]
	#[wasm_bindgen(js_name = "myProp")]
    pub fn set_my_prop(&mut self, _value: u32) {}
}

Expected Behavior
I expect the property to be named myProp
Actual Behavior
I get this compile error:
error: symbol `mystruct_myProp` is already defined
 --> src\lib.rs:6:1
  |
6 | #[wasm_bindgen]
  | ^^^^^^^^^^^^^^^

error: aborting due to previous error

Changing the setter's name to set_myProp creates two properties:
    #[wasm_bindgen(setter)]
	#[wasm_bindgen(js_name = "set_myProp")]
    pub fn set_my_prop(&mut self, _value: u32) {}

A workaround is to rename the rust methods to myProp and set_myProp respectively.

You have to use the same attribute, like this:
#[wasm_bindgen]
impl MyStruct {
    #[wasm_bindgen(getter, js_name = "myProp")]
    pub fn my_prop(&self) -> u32 {
        0
    }

    #[wasm_bindgen(setter, js_name = "myProp")]
    pub fn set_my_prop(&mut self, _value: u32) {}
}

Did you try that code? I'm getting the exact same error message.

@0xd4d Hmm, odd, it did work when I tested it. It seems to work if you have a getter or setter, but not both. So that's definitely a bug with wasm-bindgen.

Seems to have been fixed by https://github.com/rustwasm/wasm-bindgen/pull/2074


softmax: Shapes are not in standard layout / SSD

ONNX file:
https://github.com/onnx/models/blob/master/vision/object_detection_segmentation/ssd/model/ssd-10.onnx
When parsed with cpp_parse_load_save application, the error is:
./parse_load_save /cgMIGraphX/AMDMIGraphX_v1/examples/cpp_parse_load_save//models/vision/object_detection_segmentation/ssd/model/ssd-10.onnx --parse onnx
Parsing ONNX File
MIGraphX Error: /cgMIGraphX/AMDMIGraphX/src/include/migraphx/check_shapes.hpp:136: standard: softmax: Shapes are not in standard layout
terminate called after throwing an instance of 'std::runtime_error'
  what():  Failed to call function
Aborted (core dumped)

The issue is fixed in PR #740

Fixed.


Quality of life "darc clone --depth 0" improvements

Add parallelism.
Reduce log noise.

The length right now exceeds my console scroll buffer size. 😋
Trim fat. We don't care about dependencies in --depth 0 mode, so Abandoning dependency and similar are clutter.
Perhaps log details to file, and by default send only enough to stdout to assure the user that a long-running process is happening and progressing.

Remove the "master copy" of the repo. Spawn worktrees from the bare git repo in .git instead.
Shorten commit hash length to make paths easier to read.

Some of this may be better to track in dotnet/arcade, but wanted to write them down.
I implemented some of this in https://github.com/dotnet/arcade-services/pull/1112, but they aren't easy to extract because that PR was basically an overhaul.
/cc @crummel

I think we should consider removing our dependency on darc and move to a build task maintained in dotnet/arcade for arcade-powered source-build.

Getting darc set up is complicated. There's an active dotnet/source-build bug where our infra tries to put it in a weird place: https://github.com/dotnet/source-build/issues/1711. With arcade-powered source-build, I expect more people to start running similar scenarios, and it would be great if this tooling was simply part of the Arcade SDK.
There's less need for code sharing. Since we only use --depth 0 now, we don't need to do any of the complex coherency parsing and analysis. I think we only share code for Version.Details.xml parsing and git clone/fetch/checkout commands now, and I'm not sure that's worth it.
It's (subjectively) easier for us to maintain code in dotnet/arcade than dotnet/arcade-services. dotnet/arcade-services doesn't branch for new product versions. (For good reason, but it raises the bar and back-compat needs for changes.) Also, this single darc command is the only thing source-build folks maintain in that repo, so we're not very familiar with it. (E.g. I'm not sure how to add new tests, and I hacked up my build to work with it last time because it has some specific VS workload requirements.)
It's (also subjectively) easier to test changes in dotnet/arcade. It builds easily on Linux, fits into the MSBuild nupkg ecosystem that I'm already familiar with, and can be accompanied by other changes in the Arcade SDK I need to do at the same time as my other testing.
darc currently is not built from source (https://github.com/dotnet/arcade/issues/629). This isn't strictly a problem for source-build, because we use it to create the source tarball rather than during the tarball build, but this is an ugly technicality IMO that isn't in the spirit of OSS. Changing to a task built in dotnet/arcade would also resolve that.

[Triage] darc clone is no longer used in source-build 6.0 +


Use consul-template for balancemembers

This patch adds a second type of resource for
adding balancemembers, namely: haproxy/balancemember_consul.
These balance members use consul-tempalte as a replacement for
exported resources and assume that both consul as well as
consul-template are installed on any systems using this
defined resource type.
Consul-template offers an alternative to exported resources
that allows for much more dynamic updates to configuration
based on the current state of a load balanced service (it
can allow nearly instantaneous updates of config when pool members
or added, removed, or start behaving badly)
Puppet configures the consul templates which rely on consul-template
to actually convert them into the real haproxy file on disk.

Hi @bodepd. Thanks for the contribution! However, could this be simpler as a new parameter in the balancemember resource to use consul? It looks like most of the resource is the same, with the difference being the template.

@bmjen I'm just going to go ahead and close. I wanted to contribute this since I thought it was generally useful, but I don't really have the test env set up to try to refactor atm.


Better querying of the evaluations results

Users should be able to query the evaluations results to answer questions like "get me all evaluations that have a score of 1 for the metric test i1-structrured metadata and a score of 0 for i1-license"
Either:

add functions to graphql, cf. https://dgraph.io/docs/graphql/schema/search/
Or load the whole DB in a triplestore for SPARQL querying

Done
query MyQuery {
  evaluations(filterTests: [
    {metric: "https://w3id.org/fair-enough/metrics/tests/f1-metadata-identifier-persistent", score: 1},
    {metric: "https://w3id.org/fair-enough/metrics/tests/f3-metadata-identifier-in-metadata", score: 1}
  ]) {
    subject
    results {
      metricTest
      score
    }
  }
}


[Vue warn]: Invalid prop: custom validator check failed for prop "color"

Environment

Operating System: Darwin
Node Version:     v20.10.0
Nuxt Version:     3.9.3
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      css, devtools, modules, ui, tailwindcss
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Version
3.9.3
Reproduction
https://stackblitz.com/edit/nuxt-ui-9fcppd?file=tailwind.config.ts
Description
I've been following the instructions to extend the theme and include more colors but I am getting a warning:
[Vue warn]: Invalid prop: custom validator check failed for prop "color"
What is the reason for this?

I already configured the colors and their corresponding shades in the tailwind.config.ts
I already included those colors to the safelist array in nuxt.config.ts

Additional context
You can see the error on the console

Logs
[Vue warn]: Invalid prop: custom validator check failed for prop "color"

You can fix this by defining your color with a dash: electric-blue.

ok solved, I think we must include this in the documentation

@benjamincanac I'm also getting this error when adding custom named colors with custom scales (1-12 instead of 50-950)
how can I overcome this?

You cannot change the shades naming unfortunately

yeah this is a shame
which is also why we're overwriting the UI styling for... every... single... component 😂
found a workaround for the error logs though 💪

Hey there,
I'm facing a very similar issue where i'm not quite sure if it's intended that way or not.
When using built-in colors like "zinc", "gray" it also throws that warning. I noticed it mainly in the grays, I'm not sure if other colors are missing as well, but I think that at least the gray variants should be included, right?

@wolfgang-hartl The zinc color is not available for components: https://ui.nuxt.com/components/progress#style

@wolfgang-hartl The zinc color is not available for components: https://ui.nuxt.com/components/progress#style

Oh yes, sorry that's what I ment. My suggestion was more about that it should be available in my opinion, creating a grayish secondary button for example would require to config another color which is already provided by tailwind, so it would be kind of duplication to configure another gray color.

This is not how @nuxt/ui is meant to be, you only choose one gray color from your app.config.ts among slate / gray (renamed to cool) / zinc / neutral / stone.

This is not how @nuxt/ui is meant to be, you only choose one gray color from your app.config.ts among slate / gray (renamed to cool) / zinc / neutral / stone.

Definitely true. But in that context, shouldn't then be at least the chosen gray color available in the color prop, Primar works there too though. Just needed the possibility to add my gray color tone to some components as well, that's why I'm asking for that.


Build wasn't ran before the last release of 2.2.0

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the bug has not already been reported

Fastify version
3.x
Plugin version
No response
Node.js version
18.x
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
using custom gentoo
Description
Updated to latest version than saw TS error complaining about no generic, but there is one in the root/index..ts.  I then realized root/dist/index.d.ts doesn't have the generic I added to root/index.ts.
Can look at adding a prepublish script to force build to be ran before every publish.
Steps to Reproduce
install as a package in another repo, then can see the index.d.ts in dist that the package.json points to does not match the index.ts file at the root of this repo.
Expected Behavior
No response

@RafaelGSS

Sorry for that. Fixed in v2.2.1.


Add Icon to ChequeWriter Project

Convert png to ico file
Add icon to ChequeWriter project

Check with @kevinboon3288  when startup this work item by requesting the project icon image

I have added the logo icon in this PR #43 : Logo
Basically in this work item, the icon that you added is iso file type and it is for the installer usage


AQL: STARTS WITH / ENDS WITH / CONTAINS operators

Skiplist indices can be exploited to make "startsWith" queries fast, but it requires some trickery:
FOR doc IN coll // {name: "John Deaux"}, {name: "Johnathan Rice"}
    // String.fromCharCode("n".charCodeAt(0)+1) == "o"
    FILTER doc.name >= "John" AND doc.name < "Joho"
    RETURN doc

Also see http://stackoverflow.com/questions/35587746/on-multiple-index-usage-in-arangodb
Unlike with full-text indexes, the proposed operators should work on whole strings, not individual words:
FOR doc IN coll
    FILTER doc.name STARTS WITH "Ric"
    RETURN doc // should not match "Johnathan Rice"!

Indices should be utilized as much as possible, which may require an additional index type or configuration to index strings with the characters reversed, to facilitate "endsWith" searches (also see #1795).
Instead of STARTS WITH and ENDS WITH, the operators could follow the style of CSS 3 selectors (which might be inspired by regex):

doc.name ^= "John" starts with
doc.name $= "aux" ends with
doc.name ~= "nathan" contains (avoids name clash with AQL string function CONTAINS())

The operators should also work without index on individual strings and obviate the need for STARTSWITH() etc. as proposed in #1045.

Im not sure if this is the right issue for this - however - i am running this, which is awful in terms of performance:
FOR question IN questions FILTER question.easyLookupName == @easyLookupName
					FOR v, e IN 1..1 OUTBOUND question._id with_options FILTER v.validated == true AND LIKE(v.displayValue, @companyName, true)
						SORT v.displayValue ASC
				LIMIT @queryStartNumber, @resultsPerQuery
				RETURN {id: v._id, text: v.displayValue}

which, at the time of writing, i belive the LIKE operator did not use an index. I would love to have a better like operator - doc.name ~= "nathan" would transform this query into something like the below, which not only ready better, but may be more performant?
FOR question IN questions FILTER question.easyLookupName == @easyLookupName
					FOR v, e IN 1..1 OUTBOUND question._id with_options FILTER v.validated == true AND v.displayValue ~= @companyName
						SORT v.displayValue ASC
				LIMIT @queryStartNumber, @resultsPerQuery
				RETURN {id: v._id, text: v.displayValue}

@iamacup: LIKE() is not an operator, but a function. It creates a regular expression internally and then tests against the given input. The regex engine is "isolated" if you will, it can only access the input string, the regex pattern and possibly some regex flags, but nothing like ArangoDB indexes.
I wouldn't say that it's awfully slow, but of course slower than an index lookup, because it runs against all given documents. If you can filter by other criteria, so that only a hand full of a documents remain, then it's perfectly fine to be used - a dozen calls to LIKE() shouldn't hurt. You shouldn't use it as sole filter criterion however, because it would do a full collection scan and evaluate the regex for every single document.
While skiplist indexes could be exploited to achieve fast starts with / ends with searches (wildcard on either end of the search pattern), it would require a completed different index type to enable fast contains searches, such as suffix tries / suffix arrays (very memory consuming, e.g. 4 times the size of the data they index). MySQL uses the Turbo Boyer-Moore algorithm as far as I know, which is essentially a full collection scan, but with a smart per-record evaluation, which skips a lot of unnecessary character-by-character comparisons. If exact matching isn't a requirement, one could also look into techniques that combine fuzzy string matching with compression to achieve good performance in combination with space efficiency (Lucene/Solr does this AFAIK).

It sounds like CONTAINS would be more difficult, but in the meantime it would be a huge win to have STARTS WITH and ENDS WITH, even if it's semantic sugar for the skiplist hackery... because it kinda stings that I have to jump through those kind of hoops to get something most other db's already have out of the box.

:+1:
This would be very useful, as this functions will use indexes I suppose.

Am I right in thinking that https://www.arangodb.com/docs/stable/aql/functions-string.html#starts_with will not use an index? At least in a query with 2 equality filters and one STARTS_WITH filter, the optimizer doesn't choose the compound index I set up with the 2 equality fields first and finally the STARTS_WITH field, but rather a different compound index that's similar, but the 3rd field is used in an UPDATE clause (where an index isn't needed...).

Correct, only https://www.arangodb.com/docs/stable/aql/functions-arangosearch.html#starts_with can utilize an index (inverted index/View)

Belated thanks for the answer... sorry about that.
To follow on, the ArangoSearch LIKE() function also says it uses an index [1], which implies that ArangoSearch has some sort of suffix tree or equivalent data structure implemented? Is that right?
Will LIKE() work with an inverted index?
Thanks again
[1] https://www.arangodb.com/docs/stable/aql/functions-arangosearch.html#like


Swap Active Job log subscriber safely

Issue #98
At the moment we unsubscribe whoever has subscribed to active_job notifications in the initialization process. Which leads to bugs and frustration. I either haven't seen the log subscriber once submitted the initial PR , or missed it somehow.
Description of changes
We have an opportunity to swap the log subscriber safely.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you for the pull request.


Clock

Clocking class for EasyPunchCard. Right now (10/10/24) it assumes an old database (there is no database right now) meaning it will HAVE to be updated to reflect the database.
fix #2

I updated Clock to represent the database. I fixed the errors with the SQLite queries, and I added start_time and working_status to all_users table (it was needed). I also make a test file that originally I wasn't going to keep, but it represented how the GUI would work really well so I kept it.


EAS build do not have error but ** ARCHIVE FAILED **  Exit status: 65

Build/Submit details page URL
No response
Summary
Migrating from Expo classic build to eas build but it always fails with
https://expo.dev/accounts/bustrackie/projects/trackie/builds/4d512645-00a3-440b-a83b-8369905ac762
** ARCHIVE FAILED **  Exit status: 65
Executing trackie » Bundle React Native code and images
Bundler cache is empty, rebuilding (this may take a minute)

› Executing trackie » [CP] Copy Pods Resources
› Executing trackie » [CP] Embed Pods Frameworks
› Executing trackie » [CP-User] [RNFB] Core Configuration
› Executing trackie » [CP-User] [RNFB] Crashlytics Configuration
› Executing trackie » [CP-User] [RNGoogleMobileAds] Configuration
› Signing   trackie » trackie.app
› Creating  trackie » trackie.app
Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'fmt' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'abseil' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-debug' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RCT-Folly' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-utils' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-Core' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-runtimescheduler' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'ReactCommon' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-NativeModulesApple' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-Codegen' from project 'Pods')

Run script build phase '[CP-User] Generate app.manifest for expo-updates' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXUpdates' from project 'Pods')

▸ ** ARCHIVE FAILED **
2023-11-17 18:12:23.074 xcodebuild[35581:45614] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
** ARCHIVE FAILED **
Exit status: 65
+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.213.0                 |
| sdk         | iPhoneOS16.4.sdk        |
+-------------+-------------------------+
Looks like fastlane ran into a build/archive error with your project
It's hard to tell what's causing the error, so we wrote some guides on how
to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
Before submitting an issue on GitHub, please follow the guide above and make
sure your project is set up correctly.
fastlane uses xcodebuild commands to generate your binary, you can see the
the full commands printed out in yellow in the above log.
Make sure to inspect the output above, as usually you'll find more error information there
[!] Error building the application - see the log above
Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.14.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 27, 29, 30, 31
Build Tools: 28.0.3, 29.0.2, 30.0.1, 30.0.3
System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmPackages:
babel-preset-expo: ^9.3.0 => 9.5.0
expo: ^49.0.6 => 49.0.18
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.72.6 => 0.72.6
npmGlobalPackages:
eas-cli: 5.8.0
expo-cli: 6.3.10
Expo Workflow: bare
npx expo-doctor

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check npm/ yarn versions
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
Error output
Xcode log google drive from EAS. The project works fine when make for "distribution": "internal",
https://drive.google.com/file/d/1qdz8fPfi0tG8yqna5TCXiSUoSCBNmVAA/view?usp=sharing
Last logs from fastlane
› Copying   ../../../Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Pods_trackie.framework/Headers/Pods-trackie-umbrella.h ➜ ../../../Users/expo/workingdir/build/ios/Pods/Target/ Support/ Files/Pods-trackie/Pods-trackie-umbrella.h
› Preparing Pods/Pods-trackie » Pods-trackie-Info.plist
› Compiling Pods/Pods-trackie » Pods-trackie-dummy.m
› Compiling Pods/Pods-trackie » Pods_trackie_vers.c
› Creating  Pods/Pods-trackie » Pods_trackie.framework
Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'trackie' from project 'trackie')

Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'trackie' from project 'trackie')

Run script build phase '[CP-User] [RNFB] Core Configuration' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'trackie' from project 'trackie')

Run script build phase '[CP-User] [RNFB] Crashlytics Configuration' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'trackie' from project 'trackie')

Run script build phase '[CP-User] [RNGoogleMobileAds] Configuration' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'trackie' from project 'trackie')

› Executing [CP] Check Pods M
› Executing trackie » Start Packager on http://localhost:8081
› Executing trackie » [Expo] Configure project
› Copying   ios/trackie/GoogleService-Info.plist ➜ ./GoogleService-Info.plist
› Copying   ios/trackie/Supporting/Expo.plist ➜ ./Expo.plist
› Compiling trackie » SplashScreen.storyboard
› Preparing trackie » Info.plist
› Compiling trackie » trackie_vers.c
› Compiling trackie » main.m
› Compiling trackie » AppDelegate.mm
› Linking   trackie » trackie
⚠  ld: method '+moduleName' in category from /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/ExpoModulesCore/ExpoModulesCore.framework/ExpoModulesCore(ExpoBridgeModule-67835c281e72c2875d79b5cb283dbe2d.o) overrides method from class in /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/ExpoModulesCore/ExpoModulesCore.framework/ExpoModulesCore(ExpoBridgeModule-39dc610558659414887c85f7debe2801.o)
⚠  ld: method '+UIUserInterfaceStyle:' in category from /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/RNDateTimePicker/RNDateTimePicker.framework/RNDateTimePicker(RNDateTimePickerManager.o) overrides method from class in /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/React-Core/React.framework/React(RCTConvert.o)
⚠  ld: method '+UIStatusBarAnimation:' in category from /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/RNScreens/RNScreens.framework/RNScreens(RNSScreen.o) conflicts with same method from another category
⚠  ld: method '+UIDatePickerMode:' in category from /Users/expo/Library/Developer/Xcode/DerivedData/trackie-ftrkcgwbsgbzcmceiitmerqvziqt/Build/Intermediates.noindex/ArchiveIntermediates/trackie/BuildProductsPath/Release-iphoneos/react-native-date-picker/react_native_date_picker.framework/react_native_date_picker(RNDatePickerManager.o) conflicts with same method from another category
› Generating debug trackie » trackie.app.dSYM
› Executing trackie » Bundle React Native code and images
Bundler cache is empty, rebuilding (this may take a minute)

› Executing trackie » [CP] Copy Pods Resources
› Executing trackie » [CP] Embed Pods Frameworks
› Executing trackie » [CP-User] [RNFB] Core Configuration
› Executing trackie » [CP-User] [RNFB] Crashlytics Configuration
› Executing trackie » [CP-User] [RNGoogleMobileAds] Configuration
› Signing   trackie » trackie.app
› Creating  trackie » trackie.app
Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'fmt' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'abseil' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-debug' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RCT-Folly' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-Core' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-utils' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-runtimescheduler' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'ReactCommon' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-NativeModulesApple' from project 'Pods')

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-Codegen' from project 'Pods')

Run script build phase '[CP-User] Generate app.manifest for expo-updates' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXUpdates' from project 'Pods')

▸ ** ARCHIVE FAILED **
2023-11-18 17:46:46.771 xcodebuild[35146:44033] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
** ARCHIVE FAILED **
Exit status: 65
+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.213.0                 |
| sdk         | iPhoneOS16.4.sdk        |
+-------------+-------------------------+
Looks like fastlane ran into a build/archive error with your project
It's hard to tell what's causing the error, so we wrote some guides on how
to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
Before submitting an issue on GitHub, please follow the guide above and make
sure your project is set up correctly.
fastlane uses xcodebuild commands to generate your binary, you can see the
the full commands printed out in yellow in the above log.
Make sure to inspect the output above, as usually you'll find more error information there
[!] Error building the application - see the log above
Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
Reproducible demo or steps to reproduce from a blank project
Its a EAS Build issue when making it for app store, so not sure what code to provide here

i'm facing same issue, Anything on this ?

I am facing the same error.
For me the error appears after I added these settings in app.json:
expo.ios.entitlements: { "com.apple.developer.family-controls": true }

Same issue for me... :(

I also encountered a similar 65 problem a few days ago.The following is my solution idea, which finally solved the problem. hope it help you.

Get detailed logs

export EAS_LOCAL_BUILD_SKIP_CLEANUP=1
eas build -p ios --local

After the build is completed, the cache directory will be output similar to: /var/folders/7d/lrm7kd194kbcvdx6zpl9zcmr0000gn/T/eas-build-local-nodejs/50c66fa9-dd56-4742-b18e-f7541d240807

Find the log file logs/app-app.log and find the following error

/var/folders/7d/lrm7kd194kbcvdx6zpl9zcmr0000gn/T/eas-build-local-nodejs/3abb902f-122c-490b-b6e3-d416d4e57ed2/build/ios/WKTV.xcodeproj: error: Provisioning profile "*[expo] com.xxxxxx. yyy AppStore 2024-01-18T17:02:50.071Z" doesn't include signing certificate "Apple Distribution: xxxxxx (xxxxxxx)". (in target 'xxxx' from project 'xxx')

Locate the certificate problem through the above problems, log in to expo.dev, find Account settings -> Credentials, and delete all certificates in Apple Distribution Certificates

Following the previous step, export the p12 file locally and upload it to Apple Distribution Certificates (I am not sure if this step is necessary, you can try it yourself)

Re-execute eas build -p ios --local

not worked fro me

This came up first in Google when I searched for it so I'll post a solution here:
EAS Build (local as well as in the cloud) was failing for me on IOS because Apple Developer had some updates and all of my provisioning profiles had become invalid. EAS should've notified me of this, but they didn't.
The solution:

Go into your Apple Developer account and check your Provisioning Profiles, as well as your other certificates etc, see if anything's invalid.
If they're invalid: Delete them within Apple Developer
Then run eas build again and say yes when it asks if it should generate new provisioning profiles

adding on to @jvgeee's comment, the best method for determining issues in --local builds, is to ensure the EAS_LOCAL_BUILD_SKIP_CLEANUP is set to =1
export EAS_LOCAL_BUILD_SKIP_CLEANUP=1

This will ensure your XCode logs are retained after the local build is complete. After that, command + click the link to the /var/folders/wn/<SOMETHING>/T/eas-build-local-nodejs/ directory to find the build output logs folder. This helped me determine where my error originated and what capability I needed to fix.
I think with that information, this issue thread could be resolved for many RN/Expo beginners (like me) who suffered from the same issue for hours before I finally realized that I was missing a lot of detail in the logs.
https://docs.expo.dev/build-reference/local-builds/#use-local-builds-for-debugging
Secondly, for the Expo team, I think the Apple entitlement / capability documentation could be updated to include attribute types. That would have helped me significantly. Instead of relying on those, I opened my project in XCode and added the required capabilities, looked in the ios/<PROJECT_NAME>/<PROJECT_NAME>.entitlements file to find out what XML data types were expected and translated those to JSON.
Hope this helps those who find this thread. 🙏

This came up first in Google when I searched for it so I'll post a solution here:
EAS Build (local as well as in the cloud) was failing for me on IOS because Apple Developer had some updates and all of my provisioning profiles had become invalid. EAS should've notified me of this, but they didn't.
The solution:

Go into your Apple Developer account and check your Provisioning Profiles, as well as your other certificates etc, see if anything's invalid.
If they're invalid: Delete them within Apple Developer
Then run eas build again and say yes when it asks if it should generate new provisioning profiles

This was my issue thanks.

I also encountered a similar 65 problem a few days ago.The following is my solution idea, which finally solved the problem. hope it help you.

Get detailed logs

export EAS_LOCAL_BUILD_SKIP_CLEANUP=1
eas build -p ios --local

After the build is completed, the cache directory will be output similar to: /var/folders/7d/lrm7kd194kbcvdx6zpl9zcmr0000gn/T/eas-build-local-nodejs/50c66fa9-dd56-4742-b18e-f7541d240807
Find the log file logs/app-app.log and find the following error

/var/folders/7d/lrm7kd194kbcvdx6zpl9zcmr0000gn/T/eas-build-local-nodejs/3abb902f-122c-490b-b6e3-d416d4e57ed2/build/ios/WKTV.xcodeproj: error: Provisioning profile "*[expo] com.xxxxxx. yyy AppStore 2024-01-18T17:02:50.071Z" doesn't include signing certificate "Apple Distribution: xxxxxx (xxxxxxx)". (in target 'xxxx' from project 'xxx')

Locate the certificate problem through the above problems, log in to expo.dev, find Account settings -> Credentials, and delete all certificates in Apple Distribution Certificates
Following the previous step, export the p12 file locally and upload it to Apple Distribution Certificates (I am not sure if this step is necessary, you can try it yourself)
Re-execute eas build -p ios --local

Error persists for me.


Native HDF5 backend

Instead of using the HDF5 library, create our own implementation to read HDF5 files.
This will allow a much faster access to the data (not need to work with dataspaces, vlen APIs, etc.)
The tricky part will be dealing with compressed data, but this should be similar to how we currently handle this with the CDF backend for zipped data.

Using partial array reads with the HDF5 backend currently imposes a penalty due to the use of H5Sselect_hyperslab(). This penalty can be considerable. There have been test cases where using a partial array read would actually be slower then just reading the full dataset (and then taking a slice from it in memory). Currently, a hyperslab selection may need to be much smaller than the overall size to actually see any performance gain.
An implementation of a native backend in CODA should also try to make sure that partial dataset reads will actually end up becoming faster than reading the full dataset (in most circumstances).


Overriding remote properties doesn't work

Describe the bug
According to documentation we should be able to override remote properties with local property sources, but it doesn't work.
Sample
Here's a demo project.

You missed the spring.cloud.config.overrideSystemProperties=false from the config/applications.properties

In my understanding of this statement: "and spring.cloud.config.overrideSystemProperties=false if only System properties and env vars should override the remote settings, but not the local config files" should make it even more restrictive, since only sys props and env vars values will override the remote values, those from local application.config will be ignored.
In my example I'm looking for using values from local application.config/yml

You are correct...I am facing the same issue and your example is a great starting point for me.
I have created a heap of tests, but I am also reading the documentation without having too many distractions around (working from home with new neighbours and their new baby screams all the time...sleeping now). It looks that the features that you are mentioning are from the previous version and that as of 3.1.0, these features no longer appear.
Initial finding is that PropertySourceBootstrapProperties has its properties set, however the properties are never read during boot. The only place that they are referenced is in PropertySourceBootstrapConfiguration, however this class is never initialised when I believe it should be. I don't know how to force it to be initialised, but it seems that the class is completely ignored.
I will update my finding as I discover the changes, but as it to say the new way is not documented well and part reading code and deciphering the documentation, I believe that the changes are problematic.

Long story short...add the following to the client application.properties...
spring.config.use-legacy-processing=true
Longer Story...
As you can probably gather from the name, this is the legacy way of handling overrides and there is a newer way to do so. However the new way, since spring boot 2.4, is a little more complicated and I am yet to get it working.
The documentation is not clear and there really needs a better example of how to achieve the same. Also I have tested this with profiles overriding and the results become less understandable and I am still trying to figure it out.
In the meantime, adding spring.config.use-legacy-processing=false should suffice, however it might be bebeficial for the author of the latest changes to make it easier for a newbie to get their head around local overrides in the new system.

Since SB 2.4, it is no longer possible to override external properties sources

Add the following to the client application.properties...
spring.config.use-legacy-processing=true
This works with 2.7 but will be removed with 3.0.0 (Next november). I've just checked against the 3.0.0-SNAPSHOT, indeed, it doesn't work anymore.

The Spring-Cloud documentation raises the spring.cloud.config.server.overrides property. But this is valid for global configuration. e.g. for all applications.
Server's main application.properties => spring.cloud.config.server.overrides.hello=Hello!
Client's application.properties => hello=Hi!
I can't see a way to override a property from a specific app configuration (client1.properties), like it used to be prior to SB 2.4.

I believe the way you order things in spring.config.import will specify the priority order (the last one will win).

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

@ryanjbaxter what can be ordered here? https://github.com/kis024/Spring-cloud-config-bug/blob/master/src/main/resources/application.properties
Please check the demo project linked in the first comment.

spring-boot-starter-parent => 2.7.9
spring-cloud-dependencies => 2021.0.6
Same behaviour.
spring-boot-starter-parent => 3.0.4
spring-cloud-dependencies => 2022.0.1
Same behaviour.
update demo project to latest versions.

For local overrides to work properly you need to use Bootstrap configuration.  If you add spring-cloud-starter-bootstrap to the classpath and then set spring.cloud.config.uri in bootstrap.properties and remove the spring.config.import property it should work as expected.

This is an issue report, not a Stack Overflow question.

I understand, but this is a limitation that is out of our control because Spring Boot is loading the properties when using spring.config.import.  This is why I am suggesting an alternate approach

The other option is to use a profile specific properties file in the client.  If you create application-overrides.properties and activate the overrides profile properties in that file will override what comes from the server.
Can you point to where in the docs it still references client side overrides?

That documentation is very old its from Version: Brixton.BUILD-SNAPSHOT.
I don't see any references to this in our current docs
https://docs.spring.io/spring-cloud/docs/current/reference/html/
https://docs.spring.io/spring-cloud/docs/2021.0.5/reference/html/

Those are environment variable and system properties not application properties

Old reference needs to be removed and issue closed.

Old reference needs to be removed

Can you be specific about which old references need to be removed?

I am happy to add some documentation around overriding properties in the local client app.
@christian-german I do not think you need to add spring.config.use-legacy-processing=true when using boot 2.7.x with spring-cloud-starter-bootstrap.  Also as a side not using spring-cloud-starter-bootstrap with Boot 3.0.x will also allow this to continue to work.

I was thinking of dropping the misleading page https://cloud.spring.io/spring-cloud-static/spring-cloud.html in favor of https://docs.spring.io/spring-cloud/docs/current/reference/html/

All of our documentation links point to https://docs.spring.io/spring-cloud/docs/current/reference/html/


Support extra tains per node, and merge with rke2_server_taint if set true

Description

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Small minor change not affecting the Ansible Role code (Github Actions Workflow, Documentation etc.)

How Has This Been Tested?
I have been rolling it out multiple times with rke2_server_taint set as false, true etc
And triede setting node_taints: -items for masters only, and for agents.

LGTM. @newbenji once you will have a minute, please just fix the task names and i will merge it. Thanks.

Was that better?

yes, thx.


File upload doesn't appear automatically

I found it hard to find documentation on this anywhere but seems to be due to browser changes in automatically opening a dialog from the code.
Calling .click() didn't just work, it has to be from a user interaction event, so refactored to make that part synchronous from the button click but weirdly this doesn't affect the anchor tag when downloading

fixed


[Request] VPM support

Hello everyone,
as you have probably heard, VRC will enforce use of the Creator Companion starting next year.
It comes with the ability to create project templates that can automatically pull packages and insert them into new projects as well as automatically update packages.
Custom repositories and packages are supported as well, but in order to take advantage of most of the advanced automation features, packages need to be provided in the VPM format. Tooling and documentation on creating a VPM package is provided here:
https://github.com/vrchat-community/template-package
Since I consider Pumkin to be one of the most essential tools for avatar creation and management, I would love for it to be available as a custom VPM repo to be able to keep it included in my projects and updated automatically.
Are there any plans on looking into that functionality?

Not at the moment, but I'll look into it eventually.
Been kinda busy with other stuff.

From: Andazeus @.>
Sent: Friday, November 18, 2022 11:25:08 AM
To: rurre/PumkinsAvatarTools @.>
Cc: Subscribed @.***>
Subject: [rurre/PumkinsAvatarTools] [Request] VPM support (Issue #73)
Hello everyone,
as you have probably heard, VRC will enforce use of the Creator Companion starting next year.
It comes with the ability to create project templates that can automatically pull packages and insert them into new projects as well as automatically update packages.
Custom repositories and packages are supported as well, but in order to take advantage of most of the advanced automation features, packages need to be provided in the VPM format. Tooling and documentation on creating a VPM package is provided here:
https://github.com/vrchat-community/template-package
Since I consider Pumkin to be one of the most essential tools for avatar creation and management, I would love for it to be available as a custom VPM repo to be able to keep it included in my projects and updated automatically.
Are there any plans on looking into that functionality?
—
Reply to this email directly, view it on GitHubhttps://github.com/rurre/PumkinsAvatarTools/issues/73, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD7RGWNIBJWSGXTHMRMS2MDWI5DPJANCNFSM6AAAAAASEI6FNQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

VPM support was added a while ago. I forgot to go through these.


Uppercase letters when using for-the-badge style

Issue
The for-the-badge style should use uppercase letters for the label and message.
What it currently does
The k is lowercase:

What it should do
The k should be capitalized:

Other styles should continue to use lowercase letters:

Please comment on the issue before making a pull request.
This issue is for first-timers only! Since this a simple issue to fix, I am offering this issue specifically to those who have submitted fewer than 4 pull requests

I'd like to give it a shot (:

@bofalke Awesome!
If you have any questions, don't hesitate to ask!

I cannot see the part where the query parameters are overwriting the default array. Maybe you can give me a small hint on this one? Or is this part of the issue here?

@bofalke In the get shields url function (in web/functions.php) there are calls to validateParam to check parameters like style. The number format changing currently happens at the end with the call to format response number. At that point, you can check the style parameter and capitalize it after formatting.

Ah i missed that the validateParam function was returning the values from the request if set. Thanks (:


Yandex Proxy

Make it regenerate from the most canonical link.
URL encode query, otherwise should be pretty straightforward

NVM, it has anti-bot mechanisms when you go through the general link


Provide inherited targets with each image

This can be built on the fly when GETing an image

:+1:
For the use case we are working out for the CYCLONE project with i2CAT, it would be very useful to have the inheritance of deployment scripts.

I've got this partially done in the json-persistence branch.  I'll show Lionel this afternoon.

@schaubl: Are you aware of the work done on the feature/json-persistance-and-serial branch? Can we schedule this issue for next iteration?

I didn't have time to show @schaubl last Friday.  But if you look at the ImageModule.java fill you'll find a transient 'targets' field, aimed at hosting on the fly constructed map of Target objects. The Target class includes the concept of inheritance.  I didn't have time to implement the filling of the targets field, but it would be similar to the parameters.
The idea of having a transient field, is that it gets serialised, but not persisted.  So we don't to store the inherited structure in the DB, since it can change depending on parenting changes.  Instead it is re-built every time the resource is retrieved (GET).  Also, not storing the structure also gives us much more freedom in the layout of the structure, without hibernate constraints.
Hope this helps.


Feat/proxy config

This PR adds configuration support to the proxy server.

Currently, the server is using values only from the input section.
FreeRDP's INI parser does not offer support for using keywords like TRUE, `FALSE, that's why we use 0 or 1. Maybe we'll add support later, if it will be needed.
Proxy context contains a pointer to rdpProxyServer which contains a pointer to the loaded configuration. That way, we can access the configuration from every callback of the library.

LGTM


Remove custom rendering of sql hints

Description
This PR introduces the following

Removes custom rendering of SQL hints (using ReactDom). Uses default element + custom CSS.
SQL Autocompletion hints disappear on mouse down
Fixes inconsistency in the style for SQL hint

PR fixes following issue(s)
Fixes #24072
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing
How Has This Been Tested?

[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test


Issue starting bot with puma daemonized

This is maybe not really an issue but I am not sure if there is a better place to ask this question. I am trying to start a bot (actually potentially several) from a Rails application in config.ru. It seems to work fine in development but when I use my production puma configuration something fails when I have daemonize set to true. I am curious if you have any idea why that might be the case.

Can you please provide some more information than "something fails"? Thanks.

Sorry, I was not necessarily sure whether this would even be worthy of your attention and I really appreciate your support. Here is a gist of the relevant code: https://gist.github.com/jonsgreen/5806f6c56a68fc71d9ed756f62dba131.
When I run with the daemonize I am able to just catch this trace in the puma.stderr.log:
/Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-essentials-0.20.5/lib/celluloid/internals/uuid.rb:21:in `synchronize': can't be called from trap context (ThreadError)
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-essentials-0.20.5/lib/celluloid/internals/uuid.rb:21:in `generate'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-0.17.3/lib/celluloid.rb:92:in `uuid'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-0.17.3/lib/celluloid/mailbox.rb:17:in `initialize'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-0.17.3/lib/celluloid.rb:87:in `new'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-0.17.3/lib/celluloid.rb:87:in `mailbox'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/celluloid-0.17.3/lib/celluloid/proxy/sync.rb:20:in `method_missing'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/slack-ruby-client-0.8.0/lib/slack/real_time/client.rb:68:in `started?'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/slack-ruby-client-0.8.0/lib/slack/real_time/client.rb:63:in `stop!'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/slack-ruby-bot-0.10.1/lib/slack-ruby-bot/server.rb:48:in `stop!'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/slack-ruby-bot-0.10.1/lib/slack-ruby-bot/server.rb:91:in `block (2 levels) in handle_signals'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.6.0/lib/puma/cluster.rb:448:in `select'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.6.0/lib/puma/cluster.rb:448:in `run'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.6.0/lib/puma/launcher.rb:172:in `run'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.6.0/lib/rack/handler/puma.rb:51:in `run'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/server.rb:296:in `start'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server.rb:79:in `start'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:90:in `block in server'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:85:in `tap'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:85:in `server'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
        from /Users/jonathangreenberg/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `<top (required)>'

As you can see I am probably not doing something all that conventional and perhaps with your deeper understanding of the code would be able to suggest a better approach to supporting starting and running multiple bots. I know you have the slack_ruby_bot_server gem somewhat for that purpose but it seemed to be more than what I needed and I was unsure of how to bend that one for my current needs. I actually really only need to be running one bot at this time so the critical piece is figuring out the best way to get one started with puma daemonized on production. Any suggestions will be greatly appreciated and thanks so much for all the work you do supporting and promoting slack bots in the ruby community and beyond!

The error I think explains what's going on, but might not explain what to do to fix it. The code probably looks like this:
trap("INT") { ... start the bot here ... }

Celluloid (or EventMachine) don't seem to like it. There seem to be a lot of google hits on this and none are proposing any solutions, so you need to take the bot initialization out of this.
Check out https://github.com/slack-ruby/slack-bot-on-rails and how it starts the bot from a thread. That should work.

If you look at the gist I believe I am starting my bot from a thread no? I got that approach from your code which is why I thought perhaps you might have a suggestion for how to do this differently. I will look into some of the similar errors people are having.

Just for posterity here...
It seems like just adding a 1 second sleep in between starting the bots and the rails app seems to have solved the problem. Go figure.

In case someone else stumbles upon this I was not able to figure out how to keep my bot clients from closing using puma with daemonizing. Something about calling Process.daemon(true) forced my bots to exit. I ended up moving starting them out of config.ru and instead used the daemons gem to manage starting and stopping my bot(s). I am sure there are many others ways to skin this cat.


Modify the POS endpoint to take a variable list of aircraft identifiers

Currently the API only allows requesting info on a single, or all aircraft.

Completed with 03b25f307e31cfebcb60d626e6d9588c7e1122da


azcopy update - better user experience expected

Which version of the AzCopy was used?
AzCopy 10.4.0
Which platform are you using? (ex: Windows, Mac, Linux)
Mac
What command did you run?
INFO: azcopy: A newer version 10.4.1 is available to download
No azcopy update command line, no link to download
What problem was encountered?
Counting the steps to update AzCopy

Google azcopy download (no link from the original info message)
Open https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10 (no explanation on the website, just download it)
Click on Mac version
Downloaded a file azcopy_darwin_10.4.1.zip (no installer, no documentation guidance from the microsoft.com website)
Go to Download subfolder azcopy binary present
Hmm, where I need to copy this file? Open a terminal, Check where it is which azcopy
Copy the file sudo mv ~/Downloads/azcopy_darwin_amd64_10.4.1/azcopy which azcopy``
Installed but not working as considered as malware

Open Finder
Go to /usr/local/bin
Click Control + context menu and click on Open

The competition is doing the same in one step gcloud components update (including the update of plenty of tools not gsutil only)
Comparative analysis
If you need to rank your tool for user experience what will be the result?
A suggestion provides a one-click update option azcopy update like the competition.
Have you found a mitigation/solution?
Example of scripts to do this for Windows, Linux
https://www.thomasmaurer.ch/2019/05/how-to-install-azcopy-for-azure-storage/

Thanks for the suggestion.
cc @zezha-msft for visibility the MacOS issues in the steps.

We were considering deploying azcopy using intune (so that we could use it in scripts to keep part of the local file system up to date). However to do the app needs to be notarized:-
https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-notarizing-your-macos-apps-to-prepare-for-macos/ba-p/808579
As far as I can tell azcopy 10.8 isn't notarized. I see little evidence of this being added to the 10.9 release.  This mean that teying to run azcopy would likely result in warning messages appearing to end users. This means it isn't yet a workable solution for us!

Thanks for reaching out @PaulG77. We appreciate the feedback.
We are aware of the problem and will try to tackle it soon, hopefully with the next release.

This has already been taken care of in the new AzCopy release 10.10.0. Please try to take a look and reopen  if the issue persists

I wanted to upgrade from version 10.10 to 10.12., but now the issue reoccurs with the error message: “azcopy” can’t be opened because Apple cannot check it for malicious software.


could this be used as a faster spherecast?

I'm wondering if this is faster than physx trigger enter or sphere cast.


Issue with sklearn

I am receiving the following error from running this basic code upon installing rs3
from rs3.seq import predict_seq
context_seqs = ['GACGAAAGCGACAACGCGTTCATCCGGGCA', 'AGAAAACACTAGCATCCCCACCCGCGGACT']
predict_seq(context_seqs, sequence_tracr='Hsu2013')

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/rs3/seq.py", line 53, in predict_seq
    seq_predictions = model.predict(featurized_sgrnas)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/lightgbm/sklearn.py", line 899, in predict
    predict_params = self._process_params(stage="predict")
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/lightgbm/sklearn.py", line 674, in _process_params
    if self._n_classes > 2:
       ^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'NoneType' and 'int'

I believe this might be associated with the fact that sklearn is now deprecated? I'm not completely sure, but any help would be greatly appreciated.

@nickschw2 I was having the same problem. It seems to stem from sklearn.py in lightgbm 4.3.0. I solved the problem by downgrading:
pip install lightgbm==3.3.5

I fixed the max version of lightgbm to 3.3.5 in the newest release so the model should work out of the box now. Thanks for pointing out this dependency issue @nickschw2 and thanks for the easy fix @ericmalekos


Need a way to ignore xmlns attribute

The xml I am parsing has the xmlns attribute in many locations. For example:
<sports xmlns="...">
    <basketball xmlns="...">data</basketball>
    <soccer xmlns="...">data</soccer>
</sports>

Is there a way to exclude an attribute? Or to just exclude the xmlns attribute wherever it may appear? I could always iterate over the entire object when I get it parsed and manually delete but it seems there should be a better way.
I tried the processors but they seem to only change a value or name, not remove one altogether.

I was able to solve this issue by returning undefined when attribute name was xmlns in the attrValueProcessors.

Thanks for the reply @moraleslevi.
If I understand you correctly, I would do something like this:
function filterOutAttributes(value, name) {
    if (name === "xmlns") {
        return undefined;
    }
}

const customParser = new xml2js.Parser({
    attrValueProcessors: [filterOutAttributes]
});

When I run that, I still see the xmlns object in the json object. It is just set to undefined. That is I guess better but still not what I'm looking for.

That is odd. I am doing essentially what you posted above, but I do not see the xmlns in the json output. Here is my full configuration:
function cleanOutput (value, name) {
  if (name === 'xmlns:xsi') {
    return undefined
  }

  // other custom manipulations

  return value
}

const Parser = new xml2js.Parser({
  normalizeTags: true,
  mergeAttrs: true,
  explicitRoot: false,
  explicitArray: false,
  attrValueProcessors: [cleanOutput],
  valueProcessors: [cleanOutput]
})

You aren't by chance using JSON.stringify to view the data are you? I know that will hide key/values where the value is undefined. I'll try to create a standalone xml example for this.

Ah yes, I am. The output is being sent to JSON.stringify to write json to the file system. That is probably where the discrepancy lies.


Overriding a task after a dependant task has been declared does not update the dependant task

What were you expecting to happen?
I expected that registering an override for a dependency task would update all dependants, as it used to under gulp 3
What actually happened?
I have a base set of tasks which a consuming project can import and a gulpfile.js which uses require-dir to pull in those tasks and then pull in local overrides from a local tasks folder; to illustrate:

first I require-dir on the gulp-tasks folder, which contains some task definitions in separate .js files
then I require-dir on the local-tasks folder (if available) and pull in any tasks there -- tasks there are purposely allowed to override base tasks by name, which works as expected for top-level tasks (and used to work for dependencies under gulp 3)

The idea is that for 90% of the time, there should be zero-conf to use gulp for building, testing, packing and potentially deploying .net projects.
It's worked fairly well for some time, and I've taken the leap to upgrade to gulp4, which is generally working quite well.
What I have noticed though, is that dependencies which are overridden in local tasks don't seem to make it to their dependants. An example illustrates, with gulp-tasks being the source of base tasks and local-tasks being locally-provided tasks:

gulp-tasks has a pack target which packs up any .nuspec files into nuget packages
local-tasks has a deploy task which depends on pack: once a nuget package has been created, it can be deployed to the nuget feed
local-tasks overrides the pack task because it has a different way of calculating the nuget package version: the base pack task simply uses the version specified in the nuspec file, where the override creates a version based on the date-time, Jenkins build number and SHA of the git commit for the package

What I'm seeing is that if I just run gulp pack, the override task is run -- so the original pack task was specified, then overridden from local-tasks. All good.
When I run gulp deploy, the original pack task is run, not the override, and I have to assume that what's happening under the covers (due to require-dir loading the local deploy before the local pack) is this:

pack from gulp-tasks is registered
deploy from local-tasks is registered, depending on a reference to the original pack task
 packfromlocal-tasksis registered, so becomes available as the top-levelpacktask, but _does not_ override the dependency for thedeploy` task

The result is that if I pack at top-level, I get the correct output for my package. If I deploy at the top-level, I get the incorrect version for my package because the override pack task is not run.
An example to reproduce the issue can be found here: https://github.com/fluffynuts/gulp-dependency-overrides

run npm run gulp pack to see the override is run
run npm run gulp deploy to see that the original pack is run instead

What version of gulp are you using?
package.json says: ^4.0.2
What versions of npm and node are you using?
npm --version -> 6.4.1
node --version -> v10.15.3

I took a look at your repo and I see you're using gulp.series('pack') to specify the dependency. The way gulp.series works is that it gets the task specified and creates a new function that is passed into the gulp.task method.
One way you could try solving this is by changing your code to something like this:
gulp.task('deploy', (...args) => gulp.series('pack')(...args), () => {
    console.log('deploy task called');
    return Promise.resolve();
});

I'm inlining the dependencies function here to show that the function you create is passed in as a dependency, then that uses gulp.series to create a function to call inside it.
To make this a little easier to use for other situations, you can create a function to help with creating those dependencies:
const dependencies = (...tasks) => {
  return (...args) => gulp.series(...tasks)(...args);
};

gulp.task('deploy', dependencies('pack'), () => {
  console.log('deploy task called');
  return Promise.resolve();
});

I hope this helps.
I'm going to close this issue since it's a support question and not a bug.

Thanks, that does indeed help (:


Update : Twitter Icon

Updated Twitter icon
Dark Theme

Light Theme

Maybe we might wanna change the file name to VTIconX.vue 👀

How about VTIconTwitterX.vue ?

How about VTIconTwitterX.vue?

Why? It is "X" isn't it? 👀

Looking good to me 👍
@yyx990803 @bencodezen @NataliaTepluhina
When do you think is a good timing to ally this change...? 🤔

@kiaking I think we can merge this for now. And then we can further publish it. And then people in the docs project can choose a proper time to apply it.
Let me will check the Netlify checks failure first.


Refactored step defs for automated testing

closes #78
Example
- And the response should contains:
-             | statusCode | 400                                                                                - |
-             | message    | ["name must be a string","name should not be empty","platform must be one of the following values: - YouTube, Twitch","platform must be a string","platform should not be empty","author should not be empty","startDate should - not be empty","startDate must be a Date instance","endDate must be a Date instance","endDate should not be empty"] |
-             | error      | "Bad Request"

+ And the response should contain:
+             | statusCode | 400           |
+             | error      | "Bad Request" |
+         And the response property "message" has items:
+             | name must be a string                                         |
+             | name should not be empty                                      |
+             | platform must be one of the following values: YouTube, Twitch |
+             | platform must be a string                                     |
+             | platform should not be empty                                  |
+             | author should not be empty                                    |
+             | startDate should not be empty                                 |
+             | startDate must be a Date instance                             |
+             | endDate must be a Date instance                               |
+             | endDate should not be empty                                   |

I really like that it gets more readable now! 😄

Awesome, thank you 👍


Replacing pip freeze.

Hey, great tool! Thanks!
Wanted to replace pip freeze and only save top level packages with pipdeptree. Tried to run pipdeptree -f and got a nice output after grepping it accordingly. Problem is, that one of the packages I want to control version of is not a top level package, well, it is (it's Django), I installed it separately, but because it has dependant packages it does not show as top level package for freezing purposes.
This is not a bug or a problem with pipdeptree itself, I just need to figure out how to avoid manually adding frozen version of django package to requirements file after each pipdeptree invocation. Tried to use -a but it would add many packages alongside django, which I am not interested in tracking.
Any ideas?
Thanks.

Hi, I missed this issue somehow, sorry about it. You might be able to achieve the above with following command,
pipdeptree --freeze | grep -Pi '^\w+|django' | sed 's/ //g'