Document user list + message search fixup

Current: https://zulip.com/help/search-for-messages

Updated

User list (new page)

Sidebar:

There may be follow-ups, but I wanted to get the basic page up and move on to other tasks for now. We should also make a page for the left sidebar.


STATIC_ASSERT no longer defined when CONFIG_NEWLIB_LIBC is enabled

Describe the bug
When you include CONFIG_NEWLIB_LIBC in your proj.conf file, the static_assert macro stops working.   It seems like the static_assert function isn't supported in newlib.
When I try building the application it uses assert.h from the zephyr library  <..>\ncs\zephyr\lib\libc\minimal\include\assert.h
When I build with newlib it pulls assert.h from my toolchain directoy instead <...>gnuarmemb\arm-none-eabi\include\assert.h
As I understand it, enabling CONFIG_NEWLIB_LIBC swaps out a smaller, minimal, set of C libraries in Zephyr for a larger set.  So it seems like static_assert isn't defined in the new set.
To Reproduce
Easiest way to reproduce the error is to use the event manager example from Nordic's nRF repository here: https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/event_manager
The example will build with no issues.
Now add CONFIG_NEWLIG_LIBC=y to the proj.cof file and rebuild.
The build will fail stating that static_assert is undefined.
Impact
Unable to use the Event Manager with Zephyr.
Environment (please complete the following information):

OS: Windows
Toolchain GNU Arm ebedded - q2 2018

I'm using the nRF9160 development kit from Nordic along with the Nordic edition of SEGGER Embedded Studio V4.18.

@andrewboie can you help here?

This is a duplicate of #11754.  See also this recent fw-nrfconnect-nrf commit.
That static_assert should never have been added to <assert.h> is a different issue which I'll follow up on.


Prometheus Instrumentation

We want to start building out robust metrics in FireFly for better operations. As a start, we need to create a metrics endpoint that Prometheus can scrape. This should be pretty easy with the HTTP handler built into the Prometheus Go library: https://github.com/prometheus/client_golang.
As a basic demonstration of the new metrics capabilities, we could just add a simple counter for the number of API calls that have been made to the node. Any time an API endpoint is called, it would simply increment a counter.
As a demo of this functionality, it would be great to see the metrics being reported in Prometheus itself. This could simply be a local instance of Prometheus scraping logs from FireFly nodes running locally, set up by the CLI. The FireFly CLI does not need to set up Prometheus.

Re-reading this issue now that #321 is merged, and I think https://github.com/hyperledger/firefly-cli/issues/121 will address some of this but we will still need to add some custom metrics for FF to finish the vision of this issue.
@nguyer would you rather re-open this issue or creating a new issue for the custom metrics?


implements in Fragment

Hi, it is really an awesome animated context menu!!
Thanks!!
But is it possible to implements OnMenuItemClickListener / OnMenuItemLongClickListener in Fragment?

I wonder why it does not work

Fixed in new 1.0.5 version. Commit: https://github.com/Yalantis/Context-Menu.Android/commit/dc4c4f9a09e7c9aca51aae789f726eeab7db59d8
You can find changelog in the readme: https://github.com/Yalantis/Context-Menu.Android/blob/master/README.md


ci: fix version check CI job

Part of the job checks out the pull request (this isn't done automatically because this runs with pull_request_target which checks out the base by default).
That step was using merge_commit_sha which is not correct (this still checks out the base).  The fix instead checks out head.sha which is correct.
It is not possible to get a merge_commit_sha  (there is a request for this here) but head.sha should be good enough for our purposes.

@wjones127 thanks for the title fix :)


client API/impl check in

@chavdar , @ibuenros
please review it when you have time.

LGTM

@tuGithub This is complete, right?

@vasanthrajamani Please assign and priortize

https://issues.apache.org/jira/browse/GOBBLIN-146
Please update your PR title with following prefix: [GOBBLIN-146]


No fallback font or included web font for Raleway

Expected behavior
The header font should be Raleway, or at least a sans-serif font.
Actual behavior
The header font was a generic serif font, and did not match the rest of the page at all.
Steps to reproduce the behavior

Open https://elementary.io/ on a system without Raleway (such as Windows)
Observer the level one headers like "Meet Our Apps"

System information

Operating system: Windows 7 x86_64
Operating system version: 7 x86_64
Browser: Google Chrome 52
Browser version: 52
Enabled Browser Extensions: Ublock Origin, Reddit New Comments Highlighter, Pomodoro Timer

We recently pushed a change to the server where we host the web font instead of using Google fonts. The style sheet is not updated yet due to cloud flare cache. Should be fixed soon hopefully

If you clear your cache you should see expected behavior now. Can you please confirm?

Yep, works now :)


OOM when loading new resources

Describe the bug
When I load new mapping or tlscontext to my ambassador, cpu and ram usage goes to top, and mostly gets OOM at process.

To Reproduce
My configuration is Ambassador API Gateway not Edge Stack
Loaded mappings: 137
Loaded tlscontext: 41
Module loaded:
    config:
      enable_http10: true
      envoy_log_type: json
      idle_timeout_ms: 40000
      regex_max_size: 543
      retry_policy:
        num_retries: 2
        retry_on: 5xx
      server_name: cloud-dev-lb
      use_remote_address: true
      xff_num_trusted_hops: 2

Pod Limit:

cpu: 2
ram: 3gb

Expected behavior
Apply mappings shoould not couse ram and cpu peak and OOM.
Versions

Ambassador: 1.1
Kubernetes 1.15.6

Old ambassador v0.75 with many more mappings with multiple mappings change has no pick:

It'seams that problem is the tlsscontext, when loaded 41 context envoy validation takes more thatn 5 sec and ram has get up. without it runs smoothly....


[Community] Official maintainers

It's been almost 5 months since we (@nuxtlabs) made this module open-source that was initially meant to power https://volta.net and https://nuxt.studio. Since then, it became popular way beyond my expectations, got 1.8k+ stars and it even got the honor to become an official Nuxt module under @nuxt/ui.
I would like to thank everyone who supported the module and especially those who contributed to make this module what it is today.
As such, I'd like to give visibility to the people that work on this module on a day to day basis by making them official maintainers.
If you're interested, please DM me on Twitter: https://twitter.com/benjamincanac

Here someone interested! But I am not able to DM you on Twitter

Sorry about that! This should be possible now.


Error thrown when collectCoverage:true

Hi, I'm having a bit of trouble using babel-jest with the new coverage feature in jest, on a React component written in ES6/JSX with an ES6 testfile.
I'm not sure if this issue belongs here, with babel, with the Jest repo (or even istanbul?). Looks like a similar issue has been discussed here.
I suspect it is something to do with the way istanbul maps line numbers between actual and instrumented files - possibly the JSX transformation is interfering.
I've made a crude gist that reproduces the issue, with this outcome:
$ npm test

Using Jest CLI v0.4.0
 PASS  __tests__/component.test.js (2.108s)
1 test passed (1 total)
Run time: 2.451s
-------------------------------------------|-----------|-----------|-----------|-----------|
File                                       |   % Stmts |% Branches |   % Funcs |   % Lines |
-------------------------------------------|-----------|-----------|-----------|-----------|
   babel-jest-coverage/                    |       100 |       100 |       100 |       100 |
      component.jsx                        |       100 |       100 |       100 |       100 |
   babel-jest-coverage/node_modules/react/ |       100 |       100 |       100 |       100 |
      addons.js                            |       100 |       100 |       100 |       100 |
-------------------------------------------|-----------|-----------|-----------|-----------|
All files                                  |       100 |       100 |       100 |       100 |
-------------------------------------------|-----------|-----------|-----------|-----------|

Failed with unexpected error.

/home/decoy/dev-local/babel-jest-coverage/node_modules/jest-cli/src/jest.js:179
      throw error;
            ^
TypeError: Cannot set property 'covered' of undefined

Yeah, looks very similar if not the same to gotwarlost/istanbul#94. Looks like Istanbul is being passed the transformed source and when it's trying to match up the line numbers it's throwing a tantrum because the input it was given doesn't match the original source as it's been transformed.

@sebmck thanks for taking a look. Do you think this is an issue that should be solved in babel-jest, istanbul or jest-cli?
For anyone after a quick workaround, an alternative is to make a preprocessor file that uses react-tools like so:
package.json
"jest": {
    "scriptPreprocessor": "./preprocessor.js",
    ...
},
"dependencies": {
    "react-tools": "*",
    ...
}
...

preprocessor.js
var ReactTools = require('react-tools');
module.exports = {
  process: function(src) {
    return ReactTools.transform(src, { harmony: true });
  }
};

I'm not sure, seems like it would be in jest-cli, I'm not sure if there's a way to fix it in babel-jest as it's unrelated.

Ok, I'll close this and have a poke around in jest-cli.

Great, thanks!

@craigdallimore Did you ever find a fix for this? I just ran into the exact same issue.

@hotzenklotz no, not yet. I haven't raised an issue at the jest-cli repo either, let me know if you do.

@hotzenklotz @craigdallimore I just ran into this issue as well. Wondering what if anything I can do to help fix it.
The issue can reproduced by following these precise steps:
git clone https://github.com/jehoshua02/react-scaffold.git
cd react-scaffold
npm install
npm test -- --coverage

And I get this output:
~/projects/jehoshua02/react-scaffold 🚀  babel_jest
$ npm test -- --coverage

><EMAIL_ADDRESS>test /Users/employee/projects/jehoshua02/react-scaffold
> jest --coverage

Using Jest CLI v0.4.0
 PASS  __tests__/sum-test.js (0.682s)
 PASS  __tests__/Hello.js (1.048s)
2 tests passed (2 total)
Run time: 1.971s
-----------------------|-----------|-----------|-----------|-----------|
File                   |   % Stmts |% Branches |   % Funcs |   % Lines |
-----------------------|-----------|-----------|-----------|-----------|
   app/components/     |       100 |       100 |       100 |       100 |
      Hello.js         |       100 |       100 |       100 |       100 |
   app/util/           |       100 |       100 |       100 |       100 |
      sum.js           |       100 |       100 |       100 |       100 |
   node_modules/react/ |       100 |       100 |       100 |       100 |
      addons.js        |       100 |       100 |       100 |       100 |
-----------------------|-----------|-----------|-----------|-----------|
All files              |       100 |       100 |       100 |       100 |
-----------------------|-----------|-----------|-----------|-----------|

Failed with unexpected error.

/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/src/jest.js:179
      throw error;
            ^
TypeError: Cannot set property 'covered' of undefined
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:175:66
  at Array.forEach (native)
  at annotateLines (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:173:28)
  at HtmlReport.Report.mix.writeDetailPage (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:406:9)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:472:26
  at SyncFileWriter.extend.writeFile (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/util/file-writer.js:57:9)
  at FileWriter.extend.writeFile (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/util/file-writer.js:147:23)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:471:24
  at Array.forEach (native)
  at HtmlReport.Report.mix.writeFiles (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:465:23)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:467:22
  at Array.forEach (native)
  at HtmlReport.Report.mix.writeFiles (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:465:23)
  at HtmlReport.Report.mix.writeReport (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/html.js:549:14)
  at LcovReport.Report.mix.writeReport (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/report/lcov.js:55:19)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/reporter.js:93:20
  at Array.forEach (native)
  at Object.Reporter.write (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/istanbul/lib/reporter.js:87:30)
  at DefaultTestReporter.IstanbulTestReporter.onRunComplete (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/src/IstanbulTestReporter.js:33:14)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/src/TestRunner.js:453:40
  at _fulfilled (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/q/q.js:798:54)
  at self.promiseDispatch.done (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/q/q.js:827:30)
  at Promise.promise.promiseDispatch (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/q/q.js:760:13)
  at /Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/q/q.js:574:44
  at flush (/Users/employee/projects/jehoshua02/react-scaffold/node_modules/jest-cli/node_modules/q/q.js:108:17)
  at process._tickCallback (node.js:442:13)

npm ERR! Test failed.  See above for more details.

It outputs coverage to the console beautifully and that's really all I want. I wonder if I can disable whatever else is going on?

:+1:


refactor(types,shared): Assign telemetry property to main Clerk interface

Description
Unblocks SDK-1672
Assigns telemetry property to main Clerk instance to access it within React hooks from shared package, like so:
const clerk = useClerkInstanceContext();
clerk.telemetry?.record(eventMethodCalled('useOrganization'));

Checklist

[X] npm test runs as expected.
[X] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[X] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

@LauraBeatris With this change, this piece of code can be updated as well

@LauraBeatris With this change, this piece of code can be updated as well

@panteliselef I've just removed the assertion & ts-ignore comment. I'd prefer to remove the entire hook tho, but don't have a strong opinion on this.
It seems that it was only added to override the telemetry type, and the actual benefit is that you don't have to call useClerk() and access it every time.


Support stream-based NJsonSchema construction

When checking what #1466 was all about, saw that data was always read into memory (to string) and then deserialized. This crashed the .NET file reading API. Created overloads for FromJsonAsync to load from stream (FromFileAsync now uses it when non-netstandard1.0). Stream-based handling is much more efficient.
Now I'm able to get the proper error message at least:
var jsonFilePath = @"C:\temp\all-cards-20211216101126.json";
var schema = await JsonSchema.FromFileAsync(jsonFilePath);

Unhandled exception. Newtonsoft.Json.JsonSerializationException: Cannot populate JSON array onto type 'NJsonSchema.JsonSchema'. Path '', line 1, position 1.
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
   at Newtonsoft.Json.Serialization.JsonSerializerProxy.PopulateInternal(JsonReader reader, Object target)
   at Newtonsoft.Json.JsonSerializer.Populate(JsonReader reader, Object target)
   at NJsonSchema.ExtensionDataDeserializationConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\Work\NJsonSchema\src\NJsonSchema\JsonExtensionObject.cs:line 38
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonSerializer.Deserialize[T](JsonReader reader)
   at NJsonSchema.Infrastructure.JsonSchemaSerialization.FromJson[T](Stream stream, IContractResolver contractResolver) in C:\Work\NJsonSchema\src\NJsonSchema\Infrastructure\JsonSchemaSerialization.cs:line 198
   at NJsonSchema.Infrastructure.JsonSchemaSerialization.<>c__DisplayClass15_0`1.<FromJsonAsync>b__0() in C:\Work\NJsonSchema\src\NJsonSchema\Infrastructure\JsonSchemaSerialization.cs:line 120
   at NJsonSchema.Infrastructure.JsonSchemaSerialization.FromJsonWithLoaderAsync[T](Func`1 loader, SchemaType schemaType, String documentPath, Func`2 referenceResolverFactory, IContractResolver contractResolver, CancellationToken cancellationToken) in C:\Work\NJsonSchema\src\NJsonSchema\Infrastructure\JsonSchemaSerialization.cs:line 138
   at NJsonSchema.Demo.Program.Main(String[] args) in C:\Work\NJsonSchema\src\NJsonSchema.Demo\Program.cs:line 25
   at NJsonSchema.Demo.Program.<Main>(String[] args)

Also added couple try-finally where seemed appropriate and removed unnecessary awaits when task was fine to return as-is.

ltgm.

ltgm. Does this actually solve the issue? Seems to be a JSON Schema file with 1.5gb => having this in memory of course takes much more than the JSON file size... Ok on further inspection this is not really a JSON Schema but an actual JSON file...

Yep it was wrong data from the get-go, but good example how much more performant stream-based loading can be when it's possible.


interrupted DB download

Hi :)
I have been trying to wget the database but the download got interrupted for the second time around 4GB
wget https://www.dropbox.com/sh/3ktsdqlcph6x95r/AACGSj0sxYV6IeUQuGAFPtk8a/database_V1.tar.gz
message being:
Connecting to uc74b03ffd8d9bdab8f13928a165.dl.dropboxusercontent.com (uc74b03ffd8d9bdab8f13928a165.dl.dropboxusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length:<PHONE_NUMBER>3 (22G),<PHONE_NUMBER>7 (19G) remaining [application/octet-stream]
Saving to: 'database_V1.tar.gz'

database_V1.tar.gz           21%[+++++==>                                 ]   4.84G   483KB/s    in 60m 6s

2022-08-12 00:26:11 (467 KB/s) - Connection closed at byte<PHONE_NUMBER>. Retrying.

--2022-08-12 00:26:14--  (try: 4)  https://uc74b03ffd8d9bdab8f13928a165.dl.dropboxusercontent.com/cd/0/inline2/BqwvXeC5sUWGCnrYlQPmCyJIRYo9IJT_JFomtKJD1bc-mjnrPLGVahksRHg4SS0h5IWzF_6gjBRaid2_vOsCHMxMHKSvsHgz1D55bxZzN6GNzIOejsJgOrKcJr1vIgCP9_DqMzxGiD18TywZC9TdO27gEWxUXzORj7J8hVCr7MR5cOYPhFYQX9WPux0pR1LGjXRDLJOt_M7hZaWnlf4pGFOH93OTHepBc05Z_xKmJZNMA6ZLBCN1gbFyqGhl3im0q-HBWmlZDnCeTx9JVbCO3MfMwdK4X4xqy3w2KxTk6mywGcraZ8Qw785XeSPQFf44Z7VnT9iZGYPFxHnq2wHTUoIqjGWJ0r411m-0v5R3iSv20wGt_SG0-dvL_UFAsw9Jko_1hPNxxsmPYKeRKudcKX4ZKJuhEoIOXb1PSCFzAVXFhA/file
Connecting to uc74b03ffd8d9bdab8f13928a165.dl.dropboxusercontent.com (uc74b03ffd8d9bdab8f13928a165.dl.dropboxusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-08-12 00:26:16 ERROR 404: Not Found.

Dany

Hi Dany,
Thank you for your interest in Phanta!
We will investigate this next week and update you.

Hi Dany,
I'm not sure what went wrong, but tested it again and there seem to be no problem with the link.
Can you please check with you system admin if you have some limit to 4GB?
Are you able to download the test set?
( wget https://www.dropbox.com/s/o65ibd288ozfb5w/test_dataset.tar.gz )
Yishay

Hi :)
tried several times but it stops downloading. I did succesfully downloaded the test dataset.
It now stopped at 5.6GB:
database_V1.tar.gz           15%[+++==>                                      ]   3.49G   593KB/s    in 60m 4s

2022-08-17 23:23:02 (565 KB/s) - Connection closed at byte<PHONE_NUMBER>. Retrying.

--2022-08-17 23:23:04--  (try: 3)  https://ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com/cd/0/inline2/BrI72B2vC7Ga3XGgwV4bKrLlW4zh6LAL_77TwayzbTDBqVjbnmVHBQPiXOo4yfvbup-BqAvYSOIU7LRzMwYsF1wjojaKMLtfQhLn8cAIQt3gmsArV2RCM5KmWd9-5KwwpLL-PSU6-VRp4ZcCifT6zW26Vr9TCmT4pzmdtfscDFFJiDs13Zky4nSFmNQM_bE6p0VOuospRfuSzEmlKoij5jXxEUjEXVZ82VCPBR1TL63xArbLNUd7JxDbeEU_NzwGUjGWhovWgjtYb0z6f56b-fjOi6a8FGGJoRIgjQs_VGwf5wqiA8ONlfWB457liNRMIhsk15itVAb7p5WZB1Bh84qjE2INqk3BkNnVTiBbf2v2e_R_XBU-h2ZrjP3dctPOLLudTlwzh3Z74O7kDNMp1HnUlzdOVPyz8ljB_6_idDkuBg/file
Connecting to ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com (ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length:<PHONE_NUMBER>3 (22G),<PHONE_NUMBER>7 (19G) remaining [application/octet-stream]
Saving to: 'database_V1.tar.gz'

database_V1.tar.gz           24%[++++++===>                                  ]   5.43G   589KB/s    in 60m 5s

2022-08-18 00:23:14 (565 KB/s) - Connection closed at byte<PHONE_NUMBER>. Retrying.

--2022-08-18 00:23:17--  (try: 4)  https://ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com/cd/0/inline2/BrI72B2vC7Ga3XGgwV4bKrLlW4zh6LAL_77TwayzbTDBqVjbnmVHBQPiXOo4yfvbup-BqAvYSOIU7LRzMwYsF1wjojaKMLtfQhLn8cAIQt3gmsArV2RCM5KmWd9-5KwwpLL-PSU6-VRp4ZcCifT6zW26Vr9TCmT4pzmdtfscDFFJiDs13Zky4nSFmNQM_bE6p0VOuospRfuSzEmlKoij5jXxEUjEXVZ82VCPBR1TL63xArbLNUd7JxDbeEU_NzwGUjGWhovWgjtYb0z6f56b-fjOi6a8FGGJoRIgjQs_VGwf5wqiA8ONlfWB457liNRMIhsk15itVAb7p5WZB1Bh84qjE2INqk3BkNnVTiBbf2v2e_R_XBU-h2ZrjP3dctPOLLudTlwzh3Z74O7kDNMp1HnUlzdOVPyz8ljB_6_idDkuBg/file
Connecting to ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com (ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length:<PHONE_NUMBER>3 (22G),<PHONE_NUMBER>9 (17G) remaining [application/octet-stream]
Saving to: 'database_V1.tar.gz'

database_V1.tar.gz           25%[++++++++++>                                 ]   5.62G   592KB/s    in 5m 59s

2022-08-18 00:29:19 (559 KB/s) - Connection closed at byte<PHONE_NUMBER>. Retrying.

--2022-08-18 00:29:23--  (try: 5)  https://ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com/cd/0/inline2/BrI72B2vC7Ga3XGgwV4bKrLlW4zh6LAL_77TwayzbTDBqVjbnmVHBQPiXOo4yfvbup-BqAvYSOIU7LRzMwYsF1wjojaKMLtfQhLn8cAIQt3gmsArV2RCM5KmWd9-5KwwpLL-PSU6-VRp4ZcCifT6zW26Vr9TCmT4pzmdtfscDFFJiDs13Zky4nSFmNQM_bE6p0VOuospRfuSzEmlKoij5jXxEUjEXVZ82VCPBR1TL63xArbLNUd7JxDbeEU_NzwGUjGWhovWgjtYb0z6f56b-fjOi6a8FGGJoRIgjQs_VGwf5wqiA8ONlfWB457liNRMIhsk15itVAb7p5WZB1Bh84qjE2INqk3BkNnVTiBbf2v2e_R_XBU-h2ZrjP3dctPOLLudTlwzh3Z74O7kDNMp1HnUlzdOVPyz8ljB_6_idDkuBg/file
Connecting to ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com (ucc1ebd4577b99175ac373980db1.dl.dropboxusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-08-18 00:29:24 ERROR 404: Not Found.

I checked with the HPC admin and we don't have wget size limits.
Dany

Hi Dany,
Thanks for the update and good to hear you are able to download the test set!
We are wondering whether it may be a problem of connectivity speed.
Looks like you may be try to resume the partial download using the instructions here -
https://ostechnix.com/how-to-resume-partially-downloaded-file-using-wget/
Hope that this works for you!

It was a very slow upload, but it succeeded. Thank you.

Great! Glad to hear.


This just fixes some of my issues ;)

like #164 also tell me if you have any problems with these changes.

Oh and I am sorry for all the extra white space as I was printing most of the stuff to see how it all works :)

Thanks, this looks really good!
The only big issue I have is with the x is $Value ? a() : b() pattern you have here and here. This pattern is kind of a trap since adding it will often seem to fix an issue without actually fixing it, and 95% of the time it's not the right way to fix the root cause of the problem. If you want to open issues for the problems you were trying to fix I can help narrow down the underlying problem.
Also, if you wouldn't mind please run dart format . in the root directory to format all of the source code.
Finally, it looks like you started trying to implement support for extensions here, but if they don't work yet please remove this code for now.

I knew the is $Value check was bad.
Will open an issue so you help me fix the problem.
Also the Wrappers I added are auto generated so, it can help to implement most of the stdlib like that.
Lemme make this a draft I'll do the changes tomorrow.


Add the condition data table to the tool interface

Similar to the Outcome Data Explorer table, there should be one for the condition variables. Filters should be implemented similarly too for year, period, etc.

Closed in #14


System running issue. Potential dir problem.

System running issue
this is a continued thread from a previous problem on workspace_dir. I tried changing the format according to *stratte89* (LLM_API_KEY="OpenAI API Key"
LLM_MODEL="openai model name"
WORKSPACE_DIR="./workspace") but it still returned an error.
Setup and configuration
Current version:

commit 4882cb6a66e856106930f0ce5c5849cbe135e09f (HEAD -> main, origin/main, origin/HEAD)
Author: Robert Brennan<EMAIL_ADDRESS>Date:   Sat Mar 30 14:11:58 2024 -0400

    Update README.md (#403)

My config.toml and environment vars (be sure to redact API keys):
LLM_API_KEY="myopen ai api key"
LLM_MODEL="gpt-3.5-turbo"
WORKSPACE_DIR="./workspace"="https://localhost:3001/"

My model and agent (you can see these settings in the UI):

Model: "gpt-3.5-turbo"
Agent: OpenAI

Commands I ran to install and run OpenDevin
**Back End
_PS C:\Users\max\opendevin> set LLM_API_KEY="i_inserted_my_api_key"
PS C:\Users\max\opendevin> set WORKSPACE_DIR="https://localhost:3001/"
PS C:\Users\max\opendevin> set LLM_MODEL="gpt-3.5-turbo"
PS C:\Users\max\opendevin> python -m pipenv install -v
Installing dependencies from Pipfile.lock (5563c0)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
PS C:\Users\max\opendevin> python -m pipenv shell
Launching subshell in virtual environment...
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\max\OpenDevin> uvicorn opendevin.server.listen:app --port 3000
INFO: Started server process [28312]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)_
Error! Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.') Failed to stop container: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.') Error creating controller.
Additional Context: this is a continued thread from a previous problem

Previous issue for context: https://github.com/OpenDevin/OpenDevin/issues/663

Do you have docker running? see also: https://github.com/OpenDevin/OpenDevin/issues/155

@TUTULEMAN thank you for the details. If docker isn't running on your machine, you need to start it.
Also, the commit from  March 30th means your repo is outdated by now, there've been some fixes meanwhile.

@enyst how can I get the system back to date? Also, thank you @foragerr I should have turned it on.

In the project directory, git pull.
Then run as the readme says: make build.

what if I had run it and this is what it said:
make : The term 'make' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At line:1 char:1

make build

  + CategoryInfo          : ObjectNotFound: (make:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

@TUTULEMAN you need to run on WSL, not on Windows itself. Please see the README for more info

i did

If you don't have make on the system, you can install it. What Linux distribution have you chosen in WSL? Please run the project there, in that distribution.
Your initial post shows c:\ paths, which shouldn't happen in the Linux subsystem. I think it will be something like /mnt/c/other/directories

Looks like this is a windows issue from the logs. Make sure you're running in WSL, and if you're still having trouble feel free to open an new issue


🔧 [Refactor] Fix up Frontend for Presentation

:zap: Refactor ticket

This is the TODO-List for next week Thursday. It is based on https://stage1.gradido.net/vue/

[x] @BerndHueckstaedt might require some text changes. Those changes get delivered to you by him.
[x] Remember me or also Passwort merken: check if this feature has functionality - if so finish implementation and have correct behaviour. If there is no implementation remove the checkbox & text and related code

[x] There is no error produced to the user if the login fails. Only the console shows a success: false
[x] Forgot Password - Check if functionality is implemented and what could be implemented with the current backend. Make a followup issue for issues regarding this.

[x] Rename English Imprint into Legal Notice
[x] Correct link to gradido.net legal notice
[x] Correct link to gradido.net privacy policy
[x] Remove License Link

[x] On Register: The Form-Error-Messages are not translated if set to german
[x] On Register: Privacy Policy not linked correctly

[x] EMail for register contains incorrect URL with double slash @einhornimmond

[x] Followup Issue how we can/have to adjust the EMail for the new Frontend, since the link goes to the old frontend @einhornimmond
[x] Menu Logout has different background by default. better have a proper hover effect?

[x] Edit Profil Button seems to have an incorrect color

[x] Button colors are all over the place - define a consistent style

[x] Profil contains data we cannot change like position, workplace, location, note etc. Remove this for now @ogerly . Please define what we can save in the backend currently @einhornimmond

[x] Profil transaction count and other statistics is incorrect

[x] Profil show more button does nothing

[x] Menu translations are inconsistent

[x] Activities have dummy data

[x]  Transactions are not shown correctly since we call localhost and not use the .env variables correctly

[X] Remove Bitte trage jede Arbeit einzeln ein text
[X] Remove placeholder {Name der Community}
[x] Hide activities since we cannot save them (must be easy to enable again)

[ ] Form field evaluation Errors are not displayed consistently

[x] Different fonts & margins in send gradido form

[ ] No Error Feedback when trying to send gradido and it does not work
[ ] Cancel on Send Gradido form does not close the send window.

Motive

We want to make a Video of the new Frontend and deploy the whole thing to staging and later on to live.

We will do the next test on Tuesday <3

with api_password_reset #82 link in email verification email is set in login-server config

fixed // it was only a / to much in login-server config

closing this, most things seem to be done and a followup issue exists #87


To Staging: Change to cloud-hosted-guide-containerize

Updated by github actions, triggered by the guide-containerize repo.

@jakub-pomykala would you help me to resolve the test conversion failure?


docs: Fix some typos

Fix some typos in docs.
Signed-off-by: Liao Pingfang<EMAIL_ADDRESS>

Can one of the admins verify this patch?


[WIP] update dependencies

Depends: https://github.com/crypto-browserify/ripemd160/pull/14 https://github.com/crypto-browserify/sha.js/pull/36
Ref: https://github.com/crypto-browserify/createHash/issues/11 https://github.com/crypto-browserify/createHash/issues/12

md5.js extracted to crypto-browserify/md5.js
ripemd160 updated for supporting streams in own repository
sha.js updated for using hash-base instead cipher-base

utACK 58e06c1,  obviously blocked on sha.js updating etc

is this still current?

sha.js still not uses hash-base, so still WIP

Close in favour of https://github.com/crypto-browserify/createHash/pull/19


Add sasl and enif mutexes

Per the cyrus-sasl documentation, in order to have some assurance of thread safety, sasl mutex callbacks must be provided. In addition, we should also wrap sasl calls in an enif mutex to be on the safe side.

Small update, while we absolutely should be using cyrus-sasl mutex callbacks (and using mutex as additional guards around cyrus-sasl calls), this is not the issue I ran into. It is still a bit elusive, however I upon re-visiting the code I found a few issues, one of which we knew about already :

The one issue that was known is that sharing a sasl context across a process can (and will) result in a segfault, while this the library is not intended to be used this way, we should guard against it. The main guard in a patch I will send up is what zlib in otp does, specifically it checks that calling process is the same as the calling process that created the resource originally. In addition, mutexes will be added around cyrus-sasl calls (though that's mainly to guard against problems with a small bit of global state in cyrus-sasl).

We are copying the principal pointer to the callback structure, since the principal is usually going to be < 32 bytes, it could dissapear on us, this would definitely cause an issue if cyrus-sasl tries to access the user name/id on the context. Going forward (with a patch I'm working on and testing) we'll simply copy arguments into unsigned char pointers and pass those and free when appropriate.

In running the nif in the erlang debug emulator, it was observed that cyrus-sasl may mutate a challenge binary we pass on to it in mech step. If this is so, it could corrupt the heap, and result in undefined behaviour, I do believe. So, we'll just copy it into an unsigned char pointer and pass that in, freeing after the call.

Hi @starbelly, Thanks for finding all these problems and that you are working on fixes. As far as I know we have not heard of problems with crashes but this does not mean they have not happened. Let me know when you have a PR ready and I will review it.

Hi @starbelly, Thanks for finding all these problems and that you are working on fixes. As far as I know we have not heard of problems with crashes but this does not mean they have not happened. Let me know when you have a PR ready and I will review it.

I will get a PR in a minute. We'll have to go over what we think is needed and what is pure defensiveness and what we see as not helping anything, I chose pure defensiveness in battling this one, since making a reproducer is extremely difficult, though I'm still looking into that using rr.


deep-learning-v1 keras/tf student here, are the videos mostly the same?

I took it a long time ago and we used Keras and TF but I want to learn Pytorch now.
Are the videos and curriculum mostly the same, just implementation is in Pytorch?

When transitioning from Keras and TensorFlow to PyTorch, the fundamental concepts of deep learning and neural networks remain the same, but the implementation details and some aspects of the workflow will differ.
key differences:-

Syntax and API:
Keras/TF: Keras is high-level and designed to be user-friendly, often allowing for quick model building with less code.
PyTorch: PyTorch provides more control and flexibility, with a more explicit approach to building and training models.

Dynamic vs. Static Graphs:
Keras/TF: TensorFlow (especially in its early versions) used static computation graphs, which required defining the entire computation graph before running it.
PyTorch: Uses dynamic computation graphs, allowing you to modify the graph on the fly. This can make debugging easier and more intuitive.


Field 'file_hash' doesn't have a default value

Issue Summary
New file_hash field in wagtailimages Image model having issue with mysql database (v5.7) when uploading images through wagtail admin.
Steps to Reproduce

Install following version described in Technical Details
Try to upload an image.

After looking into wagtail source it seems like, this issue lies in field definition
file_hash = models.CharField(max_length=40, blank=True, editable=False)

Possibly MySQL strict mode is throwing error as no default value has been provided for file_hash
Technical details

Python version: 3.6
Django version: 2.0.8
Wagtail version: 2.1.3
MySQL version: 5.7

Stack trace
Traceback (most recent call last):
  File ".venv/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File ".venv/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 71, in execute
    return self.cursor.execute(query, args)
  File ".venv/lib/python3.6/site-packages/MySQLdb/cursors.py", line 250, in execute
    self.errorhandler(self, exc, value)
  File ".venv/lib/python3.6/site-packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
    raise errorvalue
  File ".venv/lib/python3.6/site-packages/MySQLdb/cursors.py", line 247, in execute
    res = self._query(query)
  File ".venv/lib/python3.6/site-packages/MySQLdb/cursors.py", line 412, in _query
    rowcount = self._do_query(q)
  File ".venv/lib/python3.6/site-packages/MySQLdb/cursors.py", line 375, in _do_query
    db.query(q)
  File ".venv/lib/python3.6/site-packages/MySQLdb/connections.py", line 276, in query
    _mysql.connection.query(self, query)
_mysql_exceptions.IntegrityError: (1364, "Field 'file_hash' doesn't have a default value")

Possible Solution
For now I have manually altered the database with a default value -
Alter table wagtailimages_image modify column file_hash varchar(40) not null default '';

Field declaration might be like following, so that either a default value is there or null is accepted
file_hash = models.CharField(max_length=40, blank=True, null=True, editable=False)

Or
file_hash = models.CharField(max_length=40, blank=True, default='', editable=False)

Hi @shimulch - thanks for the report.
The file_hash field does not exist on Image in Wagtail 2.1.3 - it was added in 2.2. Is it possible that you're running Wagtail 2.1.3 against a database that was created for Wagtail 2.2? This would explain the error you're seeing (since Django would normally supply a default value for the field, but doesn't know about the existence of file_hash here).

@gasman You were right. Somehow our pipenv lock file were changed. Which led to different version of wagtail when migrating between servers.
Sorry for not checking out that. Anyway, we love wagtail.

Happened to us too two times: in August and again yesterday. Wagtail is pinned to 2.1.3 in our PIpefile.

Also of note, If you have upgraded to/past 2.2, and you have any custom image models you will need to run makemigrations to add the file hash for the model.

Also of note, If you have upgraded to/past 2.2, and you have any custom image models you will need to run makemigrations to add the file hash for the model.

This repaired my incompatible database, which was created with a version <2.2, after upgrade to 2.4


feat: Disable search box for marketing page GRO-485

This is a quick PR to just add a particular meta tag to a marketing page. The goal here is to signal to Google that we don't want the Buying with Artsy marketing page to show up as a site link.
Looks like this:

https://artsyproduct.atlassian.net/browse/GRO-485
/cc @artsy/grow-devs

#mergeOnGreen


NEXT-11540 - Added quantity-selection

1. Why is this change necessary?
We should switch to an input-field when quantity-selection would have too many options.
2. What does this change do, exactly?
Storefront

Added new utility template storefront/utilities/quantity-selection.html.twig to take care of input or select output
Changed block component_offcanvas_product_buy_quantity in component/checkout/offcanvas-item.html.twig to use new utility
Changed block page_product_detail_buy_quantity in page/checkout/checkout-item.html.twig to use new utility
Changed block page_product_detail_buy_quantity in page/product-detail/buy-widget-form.html.twig to use new utility

Administration

Added config cart.maxSelectFieldOptions in cart settings to specifiy when input field should be displayed instead of the select field

3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/NEXT-11540
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

did you check if there is some validation on backend site? like if I want to order a quantity of "beer" products?

did you check if there is some validation on backend site? like if I want to order a quantity of "beer" products?

@mitelg Please give me a hint, what you mean :-) Yes, there are some validations, like steps, maxPurchase in Core 🤔

if the selection switches to an input field, is the actual input given by the customer validated by the core? no, I don't mean HTML5 validation.
so it is possible to put "beer" products in the cart? or does Shopware says: sorry but this is not a valid quantity

Will check it ;-)

Just FYI - design-wise this is fine, since default browser components are used in the storefront. Are you still on this @tinect ?

Hey @philipgatzka,
Thanks for the information :-) So I can check when I get some free time to make this ready.

Alright :+1: I'll leave this open for now then.

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://docs.shopware.com/en/shopware-platform-dev-en/contribution/contribution-guideline


Can not set client order id for orders while create batch orders.

Describe the bug
Can not set 'client order id' for orders while create batch orders.
To Reproduce
Create batch orders with custom 'order client id'.
Expected behavior
Orders was created, and have corresponding 'order client id'.
Note
BitMart.NET sends the property name "client_order_id" instead of "clientOrderId" which is expected for function https://developer-pro.bitmart.com/en/spot/#new-batch-order-v4-signed.

Fixed in latest version


Keyword Arguments in Constructor not working

A bug from my latest update... keyword arguments that are passed to the constructor of a chart aren't being applied. Example trinket: https://trinket.io/charts
Code below
import pygal

# Our data is a list of series.
# Each series is a list with a label and a list of data points
data = [["Firefox", [None, None, 0, 16.6,   25,   31, 36.4, 45.5, 46.3, 42.8, 37.1]],
        ["Chrome",  [None, None, None, None, None, None,    0,  3.9, 10.8, 23.8, 35.3]],
        ["IE",      [85.8, 84.6, 84.7, 74.5,   66, 58.6, 54.7, 44.8, 36.2, 26.6, 20.1]],
        ["Others",  [14.2, 15.4, 15.3,  8.9,    9, 10.4,  8.9,  5.8,  6.7,  6.8,  7.5]]]

# Make a Pygal chart
stackedline_chart = pygal.StackedLine(fill=True)
stackedline_chart.title = "Browser usage evolution (in %)"
stackedline_chart.x_labels = map(str, range(2002, 2013))

# For each series in our data, add label and data points
for label, data_points in data:
    stackedline_chart.add(label, data_points)

# Render the chart
stackedline_chart.render()

# Example modified from the pygal.org documentation

Aw dern.  I should've caught that fill=True but i forgot what the original looked like.  Good catch.


SyncerManager launches Syncerd(Coin, Network)

Syncer = SyncerManager = SyncerBroker = etc...

i guess it would look like a super small service, rather than a broker to all syncers

i like the specific syncer(Coin, Net) talking directly to swapds

Today I was thinking about how we could interact with syncers running on another machine based on discussion I had with @zkao.
I think it would be nice if we can start the 'manager'/'broker' and then start some syncers manually and if we could ask the 'manager' the list of running syncers, ask for new ones, attach to one, detach from one, or ask to kill one (and detach at the same time).
With the attach/detach thing we could keep swapd directly talking to syncer maybe.


Add more CEL Validation in BackendTrafficPolicy

Description:

Describe the issue.

Disable targetRef.sectionName for now
Make sure consistentHash is non nil when type of load balancer is set to ConsistentHash

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Also need tests for those things.

/assign


The LightCurve remove_nans method functionality changed --- now breaks a tutorial

The LightCurve remove_nans method functionality changed --- now breaks a tutorial
Short version:
The "Science with lightkurve" tutorial "How to perform aperture photometry with custom apertures"
is now broken after using the LightCurve remove_nans method.
Long version:
In the "Science with lightkurve" tutorial "How to perform aperture photometry with custom apertures" an attempt is made to clean up a combined light curve using the LightCurve remove_nans method:

It appears that the remove_nans method now works with single quarter light curves
(see cell#5 above) and but not with  combined light curves created using the append method.
-Ken Mighell
<EMAIL_ADDRESS>

Looks like the error is  not in the remove_nans method but rather in the append method.

This is the source for the append method:

Note that the cadenceno array is not appended with np.append like all the other arrays.
-Ken Mighell
<EMAIL_ADDRESS>

The new one-line addition of
new_lc.cadenceno = np.append(new_lc.cadenceno, others[i].cadenceno)

in the LightCurve append method given in the lightcurve.py file in my
pull request #130 should probably be replaced with the following:
if hasattr(new_lc, 'cadenceno'):
    new_lc.cadenceno = np.append(new_lc.cadenceno, others[i].cadenceno)

I did not realize that only some (not all) LightCurve objects have a cadenceno array.
-Ken Mighell
mighell at noao dot edu

Pull request https://github.com/KeplerGO/lightkurve/pull/132 implements this suggested addition to the LightCurve append method:
if hasattr(new_lc, 'cadenceno'):
    new_lc.cadenceno = np.append(new_lc.cadenceno, others[i].cadenceno)

This 2-line change is more general than the 1-line change of Pull request https://github.com/KeplerGO/lightkurve/pull/130 and should work for Kepler and generic LightCurve objects.
-Ken Mighell
mighell at noao dot edu

Thanks for the contribution @KenMighell!


WebContent.GetUrl() and LoadURLOptions.ExtraHeaders

WebContent.GetUrl()
is used to get the Url of the loaded page. It's usefull if a web-server redirects you and you need to know where it redirects. For instance, It's useful in case of Implicit Authorization.
LoadURLOptions.ExtraHeaders
is used to setup additional page loading options. For example ExtraHeaders = "pragma: no-cache\n" forces Chrome to load web page without using of the cache.

@GregorBiswanger Merge?

Yes. Thank you.


CSGN-28: Add script to pull staging data down

This PR adds a script to the bin folder that will use pg_dump and pg_restore to grab staging data and clobber your local dev database with it. It's a blunt instrument at this point, but works great!
Note: you have to be connected to the staging VPN or this will fail.

@pepopowitz good call on some docs - I ended up starting a docs folder and wrote up a basic doc for our custom scripts and this new one in particular. My hope is that as people use these things we'll improve the documentation but at least there's something to start with!


Update workflows

See https://github.com/senzing-garage/go-grpcing/issues/58

Pull Requests:

https://github.com/senzing-garage/go-helpers/pull/124


Reland "Make sure all isolates start during flutter driver tests"

Description
Fixes #24703.
Flutter driver has problems when flutter apps use more than a single isolate. The other isolates don't start, so apps malfunction. This PR fixes the problem by listening for new isolates to become runnable, and automatically starting them.
There was significant discussion of a prior version of this fix in https://github.com/flutter/flutter/pull/63167. I wrecked my git change history with a bad merge, so this is a cleaned up version of the PR.
Related Issues
#24703.
Tests
I added the following tests:
I added the following tests:

Added unit tests in flutter_driver_test.dart to verify that all isolates have resume() invoked.
Ran devicelab tests for the flutter gallery app, verifying that the bug that caused this change to be reverted last time (#62239) doesn't reoccur.
Added a new example app that uses isolates, and tested it on several platfoms: macos, android simulator and physical devices, ios simulator and physical devices.
Manually tested against an app that uses isolates started from native plugins.

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

Thanks for your work, looks great! Only thing is I don't think the examples directory is the best place, github.com/flutter/tests may be it.
For the VMNoneEvent issue, have you seen https://github.com/flutter/flutter/blob/54e136e70dbfd0810c5fe24b841e9f015e6795cd/packages/flutter_driver/lib/src/driver/vmservice_driver.dart#L106?

Internal testing is much happier with this change, only 1 failed test. A hot reload change on Android that crashes during tearDownAll with driver.close().
Root cause may be https://github.com/flutter/flutter/issues/26953 (cc @DanTup)
Relevant logs:
00:21 +0: can hot reload the app
00:22 +0: can hot reload the app
00:23 +0: can hot reload the app                                                                                VMServiceFlutterDriver: Connecting to Flutter application at http://[::1]:42893/Ejuscjt8zzM=/
VMServiceFlutterDriver: Isolate found with number:<PHONE_NUMBER>925111
VMServiceFlutterDriver: Isolate is not paused. Assuming application is ready.
VMServiceFlutterDriver: Connected to Flutter application.

00:24 +0: can hot reload the app
00:25 +0: can hot reload the app
00:26 +0: can hot reload the app                                                                                VMServiceFlutterDriver: New runnable isolate<PHONE_NUMBER>788315

00:26 +1: can hot reload the app
00:26 +1: (tearDownAll)
00:26 +0 -1: can hot reload the app [E]
  Bad state: The client closed with pending request "getIsolate".
  package:json_rpc_2/src/client.dart 70:24                                              new Client.withoutJson.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                                            _Completer.completeError
  package:json_rpc_2/src/client.dart 67:27                                              new Client.withoutJson.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                                            Future.whenComplete
  package:json_rpc_2/src/client.dart 65:10                                              new Client.withoutJson
  package:json_rpc_2/src/peer.dart 90:22                                                new Peer.withoutJson
  package:vm_service_client/vm_service_client.dart 133:33                               new VMServiceClient.withoutJson
  package:vm_service_client/vm_service_client.dart 125:11                               new VMServiceClient
  package:flutter_driver/src/driver/vmservice_driver.dart 652:9                         _waitAndConnect
  ===== asynchronous gap ===========================
  dart:async                                                                            _asyncThenWrapperHelper
  package:flutter_driver/src/driver/vmservice_driver.dart 92:39                         VMServiceFlutterDriver.connect
  package:flutter_driver/src/driver/driver.dart 156:35                                  FlutterDriver.connect
  google3:///mobile/flutter/tests/app/test/hot_reload_with_code_change_test.dart 81:34  main.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                                            _asyncThenWrapperHelper
  google3:///mobile/flutter/tests/app/test/hot_reload_with_code_change_test.dart        main.<fn>
  package:mobile.flutter.testing/runner_tests.dart 114:15                               testWithParameters.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                                            _asyncThenWrapperHelper
  package:mobile.flutter.testing/runner_tests.dart                                      testWithParameters.<fn>

I don't have any visibility of internal code so I can't offer much insight, but it seems like the json_rpc_2 package throws if the client closes the connection with outstanding requests. If a small delay fixes it, I'd guess whatever is triggering the getIsolate request isn't being awaited (perhaps because the test doesn't care about it), so awaiting it might be a nicer/more reliable fix than a delay?
(I'm not sure if it's related to #26953 though - the extra isolates in that issue are weird, but I wouldn't expect them to affect getting a response to getIsolate - especially if a small delay fixes it)

Remembering to cancel the subscription fixed the bug.

The presubmit checks look OK, let me know if you think there is more for me to do on those. The windows failure failure looks unrelated to my change, I'm guessing that's a problem at head, not something new with this pull request.

I'm rerunning "hostonly_devicelab_tests-2-windows" to see if the failure is just a flaky test.

Woohoo! Just waiting for the flutter build to be fixed now.
Is someone willing/able to tag this with waiting for tree to go green?

It's really unfortunate that that test still isn't passing. @dnfield I've looked in this and can't determine the root cause. Could you please have a look? (sponge2/d7d06397-8953-429d-a446-fcc58ab25236)

Can someone send me a log for the failing test? (Or is it new_gallery_transition_perf/new_gallery_ios__transition_perf? I can run those directly.)
If the error is still of the variety Bad state: The client closed with pending request "ext.flutter.driver", perhaps we should catch exceptions as the VM service client closes?

There seem to be two different errors.
Type A:
Bad state: The client closed with pending request "getIsolate".
package:json_rpc_2/src/client.dart 70:24                                              new Client.withoutJson.<fn>
===== asynchronous gap ===========================
dart:async                                                                            _Completer.completeError
package:json_rpc_2/src/client.dart 67:27                                              new Client.withoutJson.<fn>
===== asynchronous gap ===========================
dart:async                                                                            Future.whenComplete
package:json_rpc_2/src/client.dart 65:10                                              new Client.withoutJson
package:json_rpc_2/src/peer.dart 90:22                                                new Peer.withoutJson
package:vm_service_client/vm_service_client.dart 133:33                               new VMServiceClient.withoutJson
package:vm_service_client/vm_service_client.dart 125:11                               new VMServiceClient
package:flutter_driver/src/driver/vmservice_driver.dart 654:9                         _waitAndConnect
===== asynchronous gap ===========================
dart:async                                                                            _asyncThenWrapperHelper
package:flutter_driver/src/driver/vmservice_driver.dart 109:35                        VMServiceFlutterDriver.connect
package:flutter_driver/src/driver/driver.dart 156:35                                  FlutterDriver.connect

Type B:
Unexpected <collected> sentinel.
package:vm_service_client/src/isolate.dart 244:7                                  VMIsolateRef.load
===== asynchronous gap ===========================
dart:async                                                                        _asyncErrorWrapperHelper
package:flutter_driver/src/driver/vmservice_driver.dart                           VMServiceFlutterDriver._initIsolateHandler.<fn>
dart:async                                                                        _EventSinkWrapper.add
package:vm_service_client/vm_service_client.dart 147:12                           new VMServiceClient._.<fn>
dart:async                                                                        _BroadcastStreamController.add
package:vm_service_client/src/stream_manager.dart 69:30                           new StreamManager.<fn>
package:json_rpc_2/src/server.dart 212:30                                         Server._handleSingleRequest
package:json_rpc_2/src/server.dart 188:24                                         Server._handleRequest
dart:async                                                                        _StreamController.add
package:json_rpc_2/src/peer.dart 128:36                                           Peer.listen.<fn>
===== asynchronous gap ===========================
dart:async                                                                        _BoundSinkStream.listen
package:flutter_driver/src/driver/vmservice_driver.dart 47:44                     VMServiceFlutterDriver._initIsolateHandler
package:flutter_driver/src/driver/vmservice_driver.dart 39:32                     new VMServiceFlutterDriver.connectedTo
package:flutter_driver/src/driver/vmservice_driver.dart 136:66                    VMServiceFlutterDriver.connect
===== asynchronous gap ===========================
dart:async                                                                        _asyncThenWrapperHelper
package:flutter_driver/src/driver/driver.dart 156:35                              FlutterDriver.connect

These are happening in the host script - the logs on the emulators aren't showing any obvious errors to me.

One red flag here is that driver is still using package:vm_service_client instead of package:vm_service. It's possible there's some bug in vm_service_client, which is discontinued.

Interesting. Two different errors, both happening while establishing the VM connection. I have not seen these at all when testing locally.
Any additional information available about what these test cases are trying to test for? Is this a hot restart/reload during the initial setup? I can probably recreate that condition locally if I add sleep() statements in enough places. =)
I did notice that the vm service client library has some deprecation warnings. Anybody have thoughts on how much work it would be to replace it with the modern version...?

The type B error makes sense to me and is fixable. There's a race condition between the isolate becoming runnable and the VM canceling/removing the isolate for some other reason. The isolateRef.load() call can fail, and that's harmless. Catching the exception would fix it.
The type A error is still confusing. Any ideas about what could cause that would be helpful, I suspect I'm misreading the code flow.

Context for the type A error:
The test is a wrapper/host for a counter app that auto-increments itself. The runner is sent the letters 'r' and 'R' to trigger a hot reload and hot restart, respectively. From the video recording, the test crashes sometime after a successful hot restart, possibly during tearDown

I was able to reproduce this by adding a sleep statement towards the end of a test case, and then repeatedly restarting the app.
Somewhat different root causes for A and B.
The uncollected sentinel error happens if the onIsolateRunnable() callback produces a new isolate, but the isolate is destroyed before the call to isolateRef.load(). Fix is to handle that exception gracefully.
The pending call error is more subtle, but making sure to wait for the results of _resumeLeniently in the onIsolateRunnable callback seems to have fixed it. I think the issue here was that stream cancellation waits for the pending callback to finish. Before: stream cancellation wrapped up early, then the vm service client close would interrupt the pending call. Now: stream cancellation waits for the pending callback to finish.
Finally, there is still a race condition during driver connection: if the VM is restarted while we're still loading the first isolate in connect(), things go badly. That's an existing problem, and it's unclear what correct behavior would be. Maybe a retry? I'm not inclined to fix it in this pull request, but let me know if you want me to go for it.

Nice! We're also updating the internal tests to use package:vm_service instead of package:vm_service_client. I'll let @dnfield answer that last question.

I'm not sure what the infra failure here is about - @godofredoc or @digiter may know.
@guidezpl - do these changes now pass internally? Switching to package:vm_service will likely require changes upstream in flutter/driver.

We have an update on the builders, please rebase to the HEAD of master and retry tests.

testonly_devicelab_tests is still timing out after 3 hours, with no debug output that I've been able to find.
Any tips on debugging this? Or on reproducing the problem locally?

testonly_devicelab_tests is still timing out after 3 hours, with no debug output that I've been able to find.
Any tips on debugging this? Or on reproducing the problem locally?

Please rebase and upload a new commit. Those tests were removed like a week ago.

Weird, I thought I rebased yesterday, but I still had the failing ancient tests. Just rebased again, and this time it seems to have gone well.
Crossing my fingers that the tests pass!


bad coroutine parsing

test "coroutine in a struct field" {
    const Foo = struct {
        bar: async fn() void,
    };
    var foo = Foo {
        .bar = simpleAsyncFn2,
    };
    cancel try async(std.debug.global_allocator) foo.bar();
}

async fn simpleAsyncFn2() void {
    suspend;
}

Also add a compile error for the missing allocator type in the fn proto.


doma: change start dependency to block

In the current  product configuration, doma
should wait for a block device prior to start.
Signed-off-by: Andrii Chepurnyi<EMAIL_ADDRESS>

Closing in favor of https://github.com/xen-troops/meta-xt-common/pull/26


Compiling never stops

I'm using mill to build using
> mill reds.compile

In order to isolate the problem to zinc I modified the run task to call:
val r = zincWorker.worker().compileMixed(
        upstreamCompileOutput(),
        files,
        compileClasspath().map(_.path),
        javacOptions(),
        scalaVersion(),
        scalaOrganization(),
        scalacOptions(),
        scalaCompilerClasspath().map(_.path),
        scalacPluginClasspath().map(_.path),
        T.reporter.apply(hashCode)
      )
println("############################## DONE COMPILING ##############################")

It never reaches the println.
The compiler output that results is something like:
[info] compiling 40 Scala sources and 132 Java sources to /Users/tballard/vs_repo/redspro/out/reds/compile.dest/classes ...
[warn] 1 deprecation
[warn] 6 deprecations (since 2.13.0)
[warn] 3 deprecations (since 2.13.3)
[warn] 2 deprecations (since 2.13.7)
[warn] 12 deprecations in total; re-run with -deprecation for details
[warn] 3 feature warnings; re-run with -feature for details
[warn] 6 warnings found
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/web/modules/taglibs/jobs/Member.java: Some input files use or override a deprecated API.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/web/modules/taglibs/jobs/Member.java: Recompile with -Xlint:deprecation for details.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/CRaGLoader.java: Some input files use unchecked or unsafe operations.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/CRaGLoader.java: Recompile with -Xlint:unchecked for details.
[info] done compiling
[info] compiling 7 Scala sources and 177 Java sources to /Users/tballard/vs_repo/redspro/out/reds/compile.dest/classes ...
[warn] 1 deprecation
[warn] 5 deprecations (since 2.13.0)
[warn] 3 deprecations (since 2.13.3)
[warn] 2 deprecations (since 2.13.7)
[warn] 11 deprecations in total; re-run with -deprecation for details
[warn] 2 feature warnings; re-run with -feature for details
[warn] 6 warnings found
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/PageLoader.java: Some input files use or override a deprecated API.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/PageLoader.java: Recompile with -Xlint:deprecation for details.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/RecycleBin.java: Some input files use unchecked or unsafe operations.
[info] /Users/tballard/vs_repo/redspro/reds/src/main/java/org/redangus/redspro/biz/RecycleBin.java: Recompile with -Xlint:unchecked for details.
[info] done compiling
[info] compiling 7 Scala sources and 105 Java sources to /Users/tballard/vs_repo/redspro/out/reds/compile.dest/classes ...
[warn] 1 deprecation
[warn] 5 deprecations (since 2.13.0)
[warn] 3 deprecations (since 2.13.3)
[warn] 2 deprecations (since 2.13.7)
[warn] 11 deprecations in total; re-run with -deprecation for details
[warn] 2 feature warnings; re-run with -feature for details
[warn] 6 warnings found
...

and it compiles forever.
Note the number of files it thinks it needs to compile keeps changing.
The module had 2 java source directories and 1 scala source directory but changing that to 1 of each had no effect.
I have noticed this behavior with all mill versions since 0.9.4, for what that's worth.
The project I'm building is a ball of mud that is not particularly easy to distribute and run so it would not be trivial to give it to you to debug.
How can I help you solve this issue?

See https://github.com/sbt/sbt/issues/6183#issuecomment-1124485848

See also comment https://github.com/sbt/zinc/issues/1120#issuecomment-1474874822 which describes a way to reproduce.


Move assignment as SYSTEM_CALLSTACK clears sy-subrc

This makes perfect sense to me.

suggest merging the PR?

code changed in https://github.com/hardyp/AbapToTheFuture03/commit/35b31c28853dff3f5e87b156629d6cb58c1990fd


added STRIPE_CURRENCY

added STRIPE_CURRENCY

I am testing this too, but my idea is to set all the STRIPE variables in the same way.
unsing this:
STRIPE_CURRENCY = os.environ.get("STRIPE_CURRENCY")
and set STRIPE_CURRENCY in the environment in some script outsite.

I think is useless...

This var is used for a template tag
Actually the currency of the payments is hardcoded inside stripe/views.py

On Monday, February 16, 2015, Oier<EMAIL_ADDRESS>wrote:

I am testing this too, but my idea is to set all the STRIPE variables in
the same way.
unsing this:
STRIPE_CURRENCY = os.environ.get("STRIPE_CURRENCY")
and set STRIPE_CURRENCY in the environment in some script outsite.
—
Reply to this email directly or view it on GitHub
https://github.com/EuroPython/epcon/pull/13#issuecomment-74474682.

--
Best,
Christian

True story. I will do it in your way :+1:

:+1:


Allow installation of discoverable C API development files

The problem I'm trying to address
The use case I'm trying to address here is that of a downstream C extension that wishes to integrate with the yarp gem's C API.
We don't export the C API from yarp.{so,bundle} and so (for example) downstream C extensions can't resolve the symbol yp_parse from that shared object.
The implementation of this solution
This PR presents one possible solution:

support for a --install-c-api flag at gem install time, which installs header files and librubyparser.a as part of the gem installation footprint
a standalone ruby file yarp/c_api which provides CPPFLAGS and LDFLAGS to allow compilation and linking to happen

So usage might look like this:
$ gem install yarp -- --install-c-api
Building native extensions with: '--install-c-api'
This could take a while...
Successfully installed yarp-0.4.0

and then the downstream consumer's extconf.rb could look something like this:
# frozen_string_literal: true
require "mkmf"

require "yarp/c_api"
append_cppflags(*Yarp::CAPI::CPPFLAGS)
append_ldflags(*Yarp::CAPI::LDFLAGS)

append_cflags("-fvisibility=hidden")

create_makefile("ruby_indexer/ruby_indexer")

If the gem is installed without --install-c-api then requiring yarp/c_api will raise a LoadError exception:
warning: LoadError: Yarp's C API is not installed. Please re-install with the --install-c-api flag.

Alternative solutions
One idea is to ship a separate gem which contains the C API development files, but version it the same as the yarp gem so there's a one-to-one correspondence between them. So users of the C API would do:
gem "yarp-c-api"

Reasons not to do this?
Is the C API going to be stable enough to package and version like this? @eregon brings up some valid points below:

Node structs might be public currently but I'm not sure they should stay so (except for CRuby of course), I would see them as implementation details and it's definitely much harder to evolve in a compatible way than a Ruby API.
(note: exposing struct members in a C API is often considered a mistake in terms of API evolution)

One question about the --install-c-api flag, how would a gem pass that to add it as a dependency?
E.g.:
# I don't think this exists, but you get my idea. How would we be able to do something like
# this from a dependency?
spec.add_dependency("yarp", "~> 0.5.0", "--install-c-api")

how would a gem pass that to add it as a dependency

Yeaaaah, that's the weak part of this approach, there's no easy way to do that today in a Gemfile (though you can do it with a bundler configuration setting).
One alternative is to install the C development dependencies by default (and flip the flag to --no-install-c-api). Maybe that would be better?
Some people get very upset at a gem installation footprint being bigger than it needs to be! Otherwise I'd just install those files and not worry about it.

Is there a way for the gem that wants the dependency to specify the bundler setting? If not, then indeed it'll be difficult to define that a gem depends on the C API.
Would setting an environment variable in the gemspec work? E.g.: ENV["YARP_INCLUDE_C_API"]=true.

I'm debugging an issue with the location of the installed C development files.

Are there gems that plan to use the (public) C API of YARP?
That's pretty small in terms of public functions, I don't think it's very useful/usable.
Node structs might be public currently but I'm not sure they should stay so (except for CRuby of course), I would see them as implementation details and it's definitely much harder to evolve in a compatible way than a Ruby API.
Why not use the Ruby API?

Are there gems that plan to use the (public) C API of YARP?

Yes, a team I work with within Shopify is experimenting with this for performance reasons (running across a large codebase to build an index). @vinistock has more context.

I've update the description with a bit more information. This branch works, for whatever that's worth (I have a private project using the C API that is green).
But the maintainers should discuss:

whether shipping a C API is something they want to do,
and decide whether this is the right solution.

As Mike mentioned, we made an exploration for indexing codebases. If we hook directly into C, we can avoid allocating Ruby objects for each node in the tree and instead only produce objects for the things we're interested in maintaining on the index. We parse in C, go through the nodes in C and then produce objects only when we find what we need.
This has proved to have very significantly better performance than the approaches using only the Ruby API and allows tools such as the Ruby LSP to achieve the desired experience even on super large projects. The performance is so good, it allows us to not have to take on the complexity of using parallelism or caching for maintaining the index.
In terms of whether the node structs are a private API, that's a decision for the maintainers, so I'll defer to them. But in terms of usefulness, we have everything we need to analyze an AST: the ability to parse and the node structures.
Keeping the ability for gems to hook into the C part directly like this is definitely an exception. The only reason we explored it was to achieve our performance goals. But for these specific scenarios, it produces amazing results, so I hope that the team is open to allowing for something like this.

We are continuing to explore this and it turns out we made an unfair comparison between the Ruby API and the C API. We're able to achieve similar performance using the Ruby API after fixing some discrepancies so this may not be needed after all.

That's great news.
I think the Ruby API has also some room to be optimized further (e.g. delaying Location allocations, I did some of that in https://github.com/ruby/yarp/pull/928 but it changed since then).
It's also worth trying with YJIT, as it might optimize the allocations and ivar sets in initialize quite a bit better.

That is good news. I'm going to close this until/unless we have a use case.


ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib/libSystem.tbd' for architecture x86_64

I got this linker error build AI-Feynman on OS X 12.4 with XCode 13.4.
 % clang --version
Apple clang version 13.1.6 (clang-13<IP_ADDRESS>.5)
Target: x86_64-apple-darwin21.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
(AI-Feynman) davidlaxer@x86_64-apple-darwin13 AI-Feynman % ld -v
@(#)PROGRAM:ld  PROJECT:ld64-530
BUILD 05:01:35 Aug  4 2021
configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em (tvOS)
LTO support using: LLVM version 12.0.0 (static support for 26, runtime is 27)
TAPI support using: Apple TAPI version 10.0.0 (tapi-1000.10.8)

% xcode-select -p
/Applications/Xcode.app/Contents/Developer
(AI-Feynman) davidlaxer@x86_64-apple-darwin13 AI-Feynman % xcrun  --show-sdk-platform-path
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform
(AI-Feynman) davidlaxer@x86_64-apple-darwin13 AI-Feynman %  xcrun --show-sdk-path --sdk macosx
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk

x86_64-apple-darwin13.4.0-gfortran:f77: build/src.macosx-10.9-x86_64-3.9/aifeynman/_symbolic_regress1-f2pywrappers.f
/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/x86_64-apple-darwin13.4.0-gfortran -Wall -g -arch x86_64 -Wall -g -undefined dynamic_lookup -bundle build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/_symbolic_regress1module.o build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/fortranobject.o build/temp.macosx-10.9-x86_64-3.9/aifeynman/symbolic_regress1.o build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/_symbolic_regress1-f2pywrappers.o -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5 -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5/../../.. -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5/../../.. -lgfortran -o aifeynman/_symbolic_regress1.cpython-39-darwin.so
ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib/libSystem.tbd' for architecture x86_64
collect2: error: ld returned 1 exit status
error: Command "/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/x86_64-apple-darwin13.4.0-gfortran -Wall -g -arch x86_64 -Wall -g -undefined dynamic_lookup -bundle build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/_symbolic_regress1module.o build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/fortranobject.o build/temp.macosx-10.9-x86_64-3.9/aifeynman/symbolic_regress1.o build/temp.macosx-10.9-x86_64-3.9/build/src.macosx-10.9-x86_64-3.9/aifeynman/_symbolic_regress1-f2pywrappers.o -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5 -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5/../../.. -L/Users/davidlaxer/anaconda3/envs/AI-Feynman/bin/../lib/gcc/x86_64-apple-darwin11.4.2/4.8.5/../../.. -lgfortran -o aifeynman/_symbolic_regress1.cpython-39-darwin.so" failed with exit status 1

Solved.  There was an older version of 'ld' in my Anaconda virtual environment which conflicted with the latest version of XCode.

@dbl001 how did you update the ld version in the conda env?

I renamed the ld executable in the andaconda3 bin to something else so that the build would find the system compiler or Macport compiler.
You can also try setting CC= path to c compiler and CXX= path to c++ compiler, or adjusting you PATH environment variable so the build doesn’t find the Anaconda version of ld first.

On Mar 13, 2023, at 3:45 AM, Giulio Starace @.***> wrote:
@dbl001 https://github.com/dbl001 how did you update the ld version in the conda env?
—
Reply to this email directly, view it on GitHub https://github.com/SJ001/AI-Feynman/issues/67#issuecomment-1465903813, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXWFW6YUYQYHBNORVL3W5DW333DFANCNFSM5XR5XNVA.
You are receiving this because you were mentioned.


Error on creating date field

I tried to create date field and got such a stack trace:
Error: input.size is not a function
dateTimePicker@http://localhost:9080/assets/lib/js/eonasdan-bootstrap-datetimepicker/bootstrap-datetimepicker.js:2305:17
$.fn.datetimepicker/<@http://localhost:9080/assets/lib/js/eonasdan-bootstrap-datetimepicker/bootstrap-datetimepicker.js:2364:46
.each@http://localhost:9080/assets/lib/js/jquery/jquery.js:359:10
jQuery.prototype.each@http://localhost:9080/assets/lib/js/jquery/jquery.js:152:10
$.fn.datetimepicker@http://localhost:9080/assets/lib/js/eonasdan-bootstrap-datetimepicker/bootstrap-datetimepicker.js:2359:16
.date<@http://localhost:9080/assets/js/allcount.js:153:17
this.$get</service.fieldEditor@http://localhost:9080/assets/lib/js/allcountjs-angular-base/allcount-base.js:538:20
renderField/controller.$render/<@http://localhost:9080/assets/lib/js/allcountjs-angular-base/allcount-base.js:616:49
publicLinkFn@http://localhost:9080/assets/lib/js/angular/angular.js:6940:29
createBoundTranscludeFn/boundTranscludeFn@http://localhost:9080/assets/lib/js/angular/angular.js:7080:16
controllersBoundTransclude@http://localhost:9080/assets/lib/js/angular/angular.js:7733:18
renderField/controller.$render@http://localhost:9080/assets/lib/js/allcountjs-angular-base/allcount-base.js:615:29
renderField@http://localhost:9080/assets/lib/js/allcountjs-angular-base/allcount-base.js:625:21
fieldDirective/</<.link/<@http://localhost:9080/assets/lib/js/allcountjs-angular-base/allcount-base.js:632:21
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://localhost:9080/assets/lib/js/angular/angular.js:14195:23
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://localhost:9080/assets/lib/js/angular/angular.js:14457:13
done@http://localhost:9080/assets/lib/js/angular/angular.js:9614:36
completeRequest@http://localhost:9080/assets/lib/js/angular/angular.js:9804:7
requestLoaded@http://localhost:9080/assets/lib/js/angular/angular.js:9745:9

Datepicker does not appear

Me too.
Allcountjs version
1.0.4

Package.json
{
  "name": "test-app",
  "version": "1.0.0",
  "author": {},
  "dependencies": {
    "allcountjs": "^1.14.5"
  },
  "scripts": {
    "start": "./node_modules/.bin/allcountjs --app app-config"
  },
  "allcountjsTemplate": "twenty-two-lines"
}

And me.
node v6.2.2, allcount v1.14.5

Me also on 1.0.4. Took a quick look and I noticed that changing that input.size() call to input.length got me past the error (to another of the same kind). Also noticed that https://api.jquery.com/size/ says size() is deprecated. Any chance the version of Bootstrap packaged with allcountjs is being matched with an incompatible jQuery version?

Looks like this is actually https://github.com/Eonasdan/bootstrap-datetimepicker/issues/1657. The issue is that bootstrap-datepicker is not compatible with jQuery 3, but does not put an upper bound on its jQuery dependency. My bower-fu is not strong, but if there is a way allcountjs could apply an upper bound on a dependency's (bootstrap-datepicker) dependency (jQuery), then I suspect this issue goes away. That'd be a temporary workaround of course.

Me too. I thinks allcountjs is not work...


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: istio-testing
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
06039a68a4e1eb222feb9dacc436ad422a2d3390
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
06039a68a4e1eb222feb9dacc436ad422a2d3390
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
06039a68a4e1eb222feb9dacc436ad422a2d3390
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Server] Database Error 1002

Current Behavior
Meshery deployments with fresh database (empty database) run into the error below.
Screenshots/Logs
WARN[2022-03-09T11:14:43-06:00] Unable to read MeshSync data to the Meshery Database  app=meshery code=1002 probable-cause="Meshery Database is crashed or not reachable" severity=2 short-description="Error while deleting meshsync data.table `key_values` already exists" suggested-remediation="Restart Meshery Server.Please check if Meshery server is accessible to the Database"

Environment

Meshery Server Version: stable-v0.6.0-rc5-b

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

https://github.com/meshery/meshery/blob/313eb4ae4b3734f92aea8e0e1982fa5451097057/internal/graphql/resolver/meshsync.go#L122

@Revolyssup progress to report in tomorrow's Meshery meeting?


NRL-787 Fix warnings in integration tests due to pointer already deleted

Closed and opened https://github.com/NHSDigital/NRLF/pull/732 instead


Handle exceptions in early event handler

Also checks that handlers are called in the order they were registered
Closes #751

Coverage increased (+0.2%) to 71.857% when pulling 012423f789227a842bc2c06a14d59e30bda94e07 on handle-exceptions-in-event-handler into 1efbddf04a1aad4fc3d0aa7ebbfa94e90708b322 on master.

AWESOME : ) LGTM

Thanks mister @tjenkinson lol


Fixing lint errors.

Indeed it's not :(
https://github.com/google/kythe/issues/80
Wishful thinking that one day we'll have a bazel release that doesn't break us.


Seg Fault on 2 sides of 4 boundary sides

I found that when I have the origin and world length specified, if I try to access a coordinate on the boundary of the world, it’d seg fault. E.g., origin = (0,0), world length = (width = 50, height = 20), resolution = 0.05, then I cannot access (any x, -10), or (-25, any y) but (any x, 10) and (25, any y) were fine. It took some digging into your source code for me to understand how the numerical coordinate values actually corresponded to individual grids, so it made sense and I don’t think it was necessarily a bug in your code (which is very well written and organized, by the way), but rather that you just never took that nuance into consideration?

Hi Alice,
Thanks for reporting this behavior. You are right, I have not taken this special case into consideration since we’ve never run into this issue. I you have a suggestion for a change in code, I would be happy to take a look at it in a pull request.
Best, Péter
On 6 Dec 2017, 22:35 +0100, Alice Gong<EMAIL_ADDRESS>wrote:

I found that when I have the origin and world length specified, if I try to access a coordinate on the boundary of the world, it’d seg fault. E.g., origin = (0,0), world length = (width = 50, height = 20), resolution = 0.05, then I cannot access (any x, -10), or (-25, any y) but (any x, 10) and (25, any y) were fine. It took some digging into your source code for me to understand how the numerical coordinate values actually corresponded to individual grids, so it made sense and I don’t think it was necessarily a bug in your code (which is very well written and organized, by the way), but rather that you just never took that nuance into consideration?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sure. I'll fork it and modify, and let you know when I've made a pull request!


Properly onboard the Parks and Sec-Ops teams with a real Project-set

Describe the issue
When SecOps and Parks teams were onboarded, there was an AWS SEA platform bug affecting the provisioning of account spaces such that they were unusable by teams.  We provisioned them with some existing lab Tools and Dev spaces we had set aside for events.  This got them started, but is not suitable for final use.
By Real Project-Set we mean a full set, Tools, Dev, Test and Prod
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context

Dependent on when we get a proper patch for the LZ2 that fixes the state machine timeout bugs.

Definition of done

Run the vending machine to create new environments for SecOps and Parks teams.  We will use the same billing metadata settings and allow the teams to hold on to both sets so that they can transition smoothly.

There is a semi-manual workaround of running the stacksets against the individual accounts.   In the scope of this ticket, we have 2 accounts we've given to each team (4 total) and we need to provide each team [licenseplate]-test and [licenseplate]-prod


Update swagger for v16

Closes: #XXX
What is the purpose of the change
Update swagger and client docs to match most recent state.
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

https://github.com/osmosis-labs/osmosis/pull/5454/commits/c674842eeb854be23b824966d5a99188615ec0bb This change has already been merged in different commit, reverted it


The item text didnt hide when i quickly switch between tabs

see this screenshot pic

@nimdanoob Thanks, i was able to check the issue i will fix and update the library this weekend.

@nimdanoob pushed latest version with bug fix. You can import 1.2.1 library


Working policies implementation required

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Implement, design and validate all middleware policies.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

We will have to consider not only global policies but also scoped policies. During the meeting, we identified the example "Deployment Policy" that will allow the deployment of the specific NetApp only in the private Cloud/Edge machine, not the public one.

The initial policy in the system will be the Network Slice Selection Policy. This is needed as part of the Slice Manager integration into the Middleware.
The policy can be attached to the Instance and specify what actions must be considered when deploying the Instance.
The example Policy URLLC Network would mean that if the Slicing mechanism is available, connect the Robot utilising the instance to the URLLC Network Slice.
Things to be compleated:

[ ] Division of the Policies into the system-scoped and Instance-scoped
[ ] How to attach policies to the Instance / another object like Robot.
[ ] Implementation of the URLLC Policy.


Timezone setup doesn't work like described in alpine wiki

If you follow these steps on your Docker alpine image :
https://wiki.alpinelinux.org/wiki/Setting_the_timezone
it won't setup timezone on your image, because you've setup a "TZ" env var to UTC somewhere.
This wiki setting works on Docker alpine official image (for x86_64 arch) : https://hub.docker.com/_/alpine/
The only way to setup timezone to Europe/Paris for example, on your image is to keep tzdata installed after setup (not like described in the wiki) and to setup a new TZ env var to "Europe/Paris" (again not like described in the wiki).

I don't think the wiki article applies to this image. Adding tzdata to set /etc/localtime to the correct file and the TZ environment variable is correct. Would this be make more sense if it was documented somewhere like gliderlabs.viewdocs.io/docker-alpine/ or https://hub.docker.com/_/alpine/?

Just to be more clear, the point is :
This wiki setting works on Docker alpine official image (for x86_64 arch) : https://hub.docker.com//alpine/, so https://hub.docker.com//alpine/ doesn't need any complementary doc.
gliderlabs.viewdocs.io/docker-alpine/ is not having the same behaviour as https://hub.docker.com//alpine/. For a mysterious reason, TZ is set (it's NOT set in https://hub.docker.com//alpine/ )

Hmm, can you give an example? They are both UTC for me with no TZ:
$ dri gliderlabs/alpine sh -c "env; date"
no_proxy=*.local, 169.254/16
HOSTNAME=3cfcc4117537
SHLVL=1
HOME=/root
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
Wed Jul 19 18:58:49 UTC 2017
$ dri alpine sh -c "env; date"
no_proxy=*.local, 169.254/16
HOSTNAME=570d6a5d659b
SHLVL=1
HOME=/root
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
Wed Jul 19 18:58:57 UTC 2017

Sure, TZ appears in "docker inspect", in the env section. It appears in gilderslabs/alpine (same as arm32v6/alpine right ?) and not in alpine.
$ docker inspect arm32v6/alpine:3.6
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "TZ=UTC"
            ],

$ docker inspect alpine:3.6
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],

That's a quirk particular to the current hacky multiarch Alpine images;
I'll look at adjusting that to use tzdata instead.

Hi Tianon, your name is familiar in Docker forums, you want to adjust that on arm32v6/alpine, not on regular alpine right ?
What do you mean by "adjusting that to use tzdata instead" ? Don't you think you can just not set TZ which would make all alpine images the same and respecting the alpine doc ?

Yes, arm32v6/alpine is currently using ENV TZ UTC because otherwise, Alpine defaults to GMT.  This repository uses a temporary install of tzdata in order to create an appropriate /etc/localtime file which overrides that default instead, which is what I need to do in the temporary ARCH/alpine images as well (until #304 is resolved).

The ARCH/alpine images should now be updated with the fix.

It's all good to me, TZ appears no more in $ docker inspect arm32v6/alpine:3.6
        "Env": [
            "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
            "TZ=UTC"
        ],


Don't send included over the wire when POSTing or PATCHing cards

This is the correct thing to do, and mysteriously it seems to solve issues in staging with returning 403 when creating cards that have included in the payload (unsure why that is--seems like AWS infra is returning 403's)

Could this be backed by an expectEvents assertion?

could you elaborate? i'm not sure what events you mean

hmm maybe I misunderstand what the expectEvents test helper does but I’d usually expect to see an assertion in tests to enforce this, I thought that helper was somewhat like a Mirage handler where you can make assertions on what the “server” receives, so the missing included could be checked for.

ah yeah i see. i don't think we have any assertions for over the wire format. We make assertions around the file that is serialized to the realm, but not how it's transported. I think we'd need to tap into our loader for that since requests may be short circuited and not actually result in a fetch (especially requests in our tests)

one super crazy thought would be to make a loader middleware that is able to perform assertions.

ah well if this turns out to be a source of trouble it seems worth future improvement, thanks for the explanation 😀

I'm actually gonna take a stab at using our loader middleware to make fetch assertions in our tests

Our loader middleware actually worked really well in fashioning a new onFetch test helper to make assertions on fetches


Managerial Components

Goal

Develop managerial components of delegation and communication between AI tasks

Inspiration

See MLflow multistep workflows (documentation or code examples) for how multiple machine learning models can communicate with each other

One idea to consider is to make inputs and outputs explicit for all machine learning models. This will allow AI Platform to chain tasks together, where the output of one task becomes the input of another.