[ios] Some of the markers fed to the map is not displayed in google map ios device

Details
This issue can be reproduced if more than 1300 markers are fed to the map. The markers after that count are not displayed  in iOS device but in android all the markers are displayed.
The total number of markers that I need to show in the map is about 1800 in average. But the issue is iOS device only show limited number of markers which is around 1300.
The issue is only with iOS devices.
Devices Tested :

iPhone 11 Pro (v 16.3.1)
iOS Simulator (v 16.2)

Package:
google_maps_flutter 2.2.5
Code snippet:
Future loadMarkers(
List markers, BitmapDescriptor markerIcon) async {
for (int i = 0; i < markers.length; i++) {
_markers.add(
Marker(
markerId: MarkerId(i.toString()),
position: markers[i],
icon: markerIcon,
onTap: () async {
facilityMarkerHighlight(
_context!, _filteredFacilities[i], markers[i]);
},
),
);
}
_markers.toSet;
notifyListeners();
}
GoogleMap(
initialCameraPosition: model.cameraPosition,
markers: Set.of(model.getMarkers).map((e) => e).toSet(),
zoomControlsEnabled: false,
mapType: MapType.normal,
rotateGesturesEnabled: true,
onMapCreated: (GoogleMapController mapController) {
model.initializeContext(context);
model.googleMapController = mapController;
},
),
Target Platform: iOS
Target OS version: 12 and above
Devices: iOS mobile device / simulator
Logs:

`Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.2, on macOS 13.0 22A380 darwin-arm, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.76.1)
[✓] Connected device (4 available)
[✓] HTTP Host Availability
• No issues found!`
Screenshots:
iOS - Markers are lesser than in the android screenshot

Android - Works as expected

Very much appreciated if this issue can be addressed soon as possible as this is a major impact to our clients.

Hi @rsachiendran
Which google_maps_flutter plugin version are you using? Could you please provide a completed and minimal reproducible code sample so that we may verify this? Also, please provide the output of flutter doctor -v as well.
Thank you!

Thank you so much for the complete sample code. I checked this on both Android and iOS and I can see it's more lagging on iOS than on Android when zooming or dragging the map, though I can not verify the number of markers on these platforms:).
However, I see there are some (similar) issues: #60750, #45508 (is closed as a duplicate of #60750). So I will close this issue in favor of #60750.
Please follow up on it for further updates. You can also leave there your comment and react an upvote to the original comment will help to raise the issue. Thank you!


return value of fetch and mutate methods does not correspond to network response

Describe the bug
I have a sequence of pages that create an object then update it with more information. When it updates, the Houdini value is not the same as what I see in the Network panel in Chrome dev tools.
The actual object schema is complex, but to keep it simple, let's say it looks like {id: UUID!, title: string!, places: [Place]}. The places field starts out empty and will be populated by the second upsert.
// FirstComponent.svelte

await new UpsertMyObjectStore().mutate({ title: 'my object' });
// { id: 'abcd-0123', title: 'my object', places: null }

// Load next page
document.location.href = anotherUrl;

Then:
// SecondComponent.svelte

const initialObj = await new GetMyObjectStore().query({ id: 'abcd-0123' }).data;
// { id: 'abcd-0123', title: 'my object', places: null }

const newPlaces = [ ... ];

const response = await new UpsertMyObjectStore().mutate({
  title: 'a better title',
  places: newPlaces
}).data;

const updatedObj = await new GetMyObjectStore().query({ id: 'abcd-0123' }).data;

The Network panel shows that the server returns an object with the new title and array of places. I can see in the database that the operations were successful. Houdini, however, gives a null places field instead of the correct array.
console.log(response);
// { id: 'abcd-0123', title: 'a better title', places: null }  <--- `title` is right, `places` is wrong

console.log(updatedObj);
// { id: 'abcd-0123', title: 'a better title', places: null }  <--- `title` is right, `places` is wrong

I've spent hours trying everything I can think of—making sure to use NetworkOnly, manually clearing caches, setting timeouts between API calls, etc.—but I feel like I'm missing something. Is it normal or even possible that the return value is different from the network response?
Severity
blocking all usage of Houdini
Steps to Reproduce the Bug
I can't share much because of strict IP policies, but here's a screenshot showing the network traffic vs. what Houdini reports:

Reproduction
No response

I should mention that when I refresh the page, the GetMyObjectStore query does return the correct data, which is why it seems to be a caching issue (even though the store says that its source is "Network").

Thank you for the detailed report @TheophileMot! I'm sorry to hear you are running into this. Unforunately, due to the limited inforimation that you are able to share, it will be very hard to debug what exactly is going on.
Could you try to use the e2e tests  in this repo to create a reproduction? That would be incredibly helpful

@AlecAivazis Thank you for directing me to the e2e tests. I realise that it's not really feasible to look into the issue without being able to replicate it; if ever I get the time, I'll see if I can make a test.
For posterity, I managed to circumvent the issue for now by writing a client plugin. The afterNetwork step has the correct data, while the end step is incorrect; therefore, I put the data in afterNetwork into ctx.stuff, and use that in the end step instead of whatever Houdini thinks it should be.

Okay good to hear you fixed this. I'm going to close the issue until we have something more concrete to address


Updated method to get CPU arch to get it from the full uname string

This PR changes how the main runner grabs the CPU arch, as using os.uname()[4] is unreliable when used with Rosetta 2 on Apple Silicon.
Instead, we just search the uname string provided by os.uname()[3], and lowercase it to match existing data.
I have tested this with the arm64 and x86_64 strings, but I don't have a physical machine to test i386 with 😅

Superseded by PR #1498

Already merged in 5.x


Don't transmit to Honeycomb without an API key

Question is what to do... Throw an exception when registering into DI, or throw a warning? or throw a warning and drop the packets on send.

Our other libraries will print the traces to stdout if you don't supply an API key...

We’re going to close this for now as we're moving more towards supporting OpenTelemetry SDKs. Feel free to re-open if it’s still relevant.


Issue#24 - New Feature - Option to add Server URL

Issue#24
User can now add custom Sever URL:
Example:
SERVER_URL = "http://localhost:8080"
generator.generate_swagger(app,
                destination_path="/static/swagger.yaml",
                server_url="http://localhost:8080"
)

Thanks @fizaashraf37. Maybe you can add this to the develop branch and add some tests

Test case has been added. I have also Refactored Tests code to make it more generic and reusable.


Replace Path class with Symfony Path class

Path could be possibly be replaced with the Path class in symfony/filesystem
Acceptance criteria

[ ] Determine if replacing the Silverstripe Path class is worthwhile and viable
[ ] Deprecate and replace Path
[ ] If we can simply swap it out and no unit tests break, then do the work directly in CMS 5 instead. Otherwise if we need to update the code that calls these methods, then target CMS 6

I don't think this is worthwhile as the Silverstripe Path methods having additional logic which symfony path does not
Silverstripe Path::join() includes protection against directly traversal i.e. not allowed .. and will throw an exception, whereas Symfony Path will not stop you from having a path with '..' and will simply return a path with the the .. resolved for you - "all "." and ".." segments are removed as far as possible"
The Silverstripe normalize() method also has an additional param $relative which means that the directory seperators will be rtrim()'ed off

Silverstripe Path::join() includes protection against directly traversal i.e. not allowed .. and will throw an exception, whereas Symfony Path will not stop you from having a path with '..' and will simply return a path with the the .. resolved for you - "all "." and ".." segments are removed as far as possible"

I honestly think the way symfony does that is better. Directory traversal protection doesn't belong in a "join these two paths together" method, it belongs in whatever is using that path - at which point you'd know where you are or aren't allowed to traverse to.
If I go Path::join('_resources/theme/simple/images/', '../css/'); I should be able to get '_resources/theme/simple/css/' as a result without an error thrown in my face for trying to get a perfectly valid path.

The Silverstripe normalize() method also has an additional param $relative which means that the directory seperators will be rtrim()'ed off

I think it's worth losing that little bit of functionality and having a few ltrim(Path::normalize($myPath), '/'); around the place for the sake of

not having any confusion at all about which Path class to use, because there's only one
IMO better join functionality
All of the additional methods symfony has on their Path class

And yes technically we can use the other Path class along side our one, but that just makes point 1 worse imo.

I'd go with Symphony's Path class, too, so that we don't have the same conversation in a year why we didn't replace this component when we replaced others.

https://github.com/silverstripe/silverstripe-framework/pull/11380#pullrequestreview-2311488637
We're not doing it I guess


Fix flaky workflow stack trace logging

Prevent worker routines from queueing next steps to help assure
correct stack traces.
(( forward to .9 as well ))
Please take a look.

Codecov Report

Merging #233 (5d3f5f6) into 2021.3.x (1faae47) will increase coverage by 0.35%.
The diff coverage is 55.55%.

@@             Coverage Diff              @@
##           2021.3.x     #233      +/-   ##
============================================
+ Coverage     41.15%   41.51%   +0.35%
============================================
  Files           602      602
  Lines         60681    60691      +10
============================================
+ Hits          24973    25194     +221
+ Misses        32832    32600     -232
- Partials       2876     2897      +21

Impacted Files
Coverage Δ

automation/types/session.go
57.37% <33.33%> (ø)

pkg/wfexec/session.go
59.52% <57.57%> (+6.35%)
:arrow_up:

pkg/handle/handle.go
78.57% <0.00%> (-7.15%)
:arrow_down:

pkg/envoy/store/user.go
66.00% <0.00%> (-6.00%)
:arrow_down:

compose/automation/expr_types.gen.go
3.58% <0.00%> (+0.47%)
:arrow_up:

pkg/expr/expr_types.gen.go
25.15% <0.00%> (+0.60%)
:arrow_up:

automation/types/expr.go
52.17% <0.00%> (+1.08%)
:arrow_up:

pkg/expr/vars.go
70.00% <0.00%> (+1.53%)
:arrow_up:

compose/automation/expr_types.go
57.59% <0.00%> (+1.76%)
:arrow_up:

automation/types/param.go
40.00% <0.00%> (+3.63%)
:arrow_up:

... and 11 more

Continue to review full report at Codecov.

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


use annotation tracking by default

Annotation tracking method is a must when using Crossplane with ArgoCD. This PR enables it.
https://argo-cd.readthedocs.io/en/stable/user-guide/resource_tracking/#additional-tracking-methods-via-an-annotation

@cmoulliard Good idea. Reflected it in the README.


chore: bump version to v0.27.0

Bumps version to 0.27.0, this is a major bump as #677 is breaking.

LCOV of commit bc95c86 during CI #2065
Summary coverage rate:
  lines......: 81.9% (2297 of 2805 lines)
  functions..: 44.4% (363 of 818 functions)
  branches...: 58.1% (264 of 454 branches)

Files changed coverage rate: n/a


webpack file naming issues

I have just been integrating corber with a custom webpack setup and came across a couple of gotchas.
"corber": "^1.3.3",
"corber-webpack-plugin": "^1.0.0",
"webpack": "^4.29.3",
"webpack-cli": "^3.1.2",
"webpack-dev-server": "^3.1.10"

I had an issue where the cordova javascript files were being served as 'name.js.js', it seems that by default webpack has output.filename = '[name].js'. And the corber-webpack-plugin provides name as 'cordova.js'. Hence you end up with 'cordova.js.js'.
The second issue was the name on the cordova plugin files appear to be wrong, it is providing the full path from the CWD as the 'name' to webpack. Eg: corber/cordova/platforms/ios/www/plugins/cordova-plugin-file/www/ProgressEvent.js. It should be relative to the cdvAssets path Eg: plugins/cordova-plugin-file/www/ProgressEvent.js.
The first issue can be worked around by doing something like:
entry: {
    "bundle.js": path.resolve(ROOT_DIR, "src", "app.js")
},
output: {
    filename: "[name]",
    path: path.resolve(ROOT_DIR, 'build')
},

The second issue is harder to work around. Is there something in a basic setup which I am missing?

Thanks for the report here - I'm still working on a resolution that is stable on generic webpack & Vue CLI.
Just a quick confirmation - you should only be encountering this problem during serve and start, but not during build?

Yeah this is an issue with the 'CorberWebpackPlugin', which is serve / start only I believe.

Thanks for the comment / patch. I'll be giving it a QA on my side for release asap.
It can unfortunately take a little while to test across webpack generic / react / vue-cli. Unfortunately that part of our stack has been very tough to write testing for :-)

Is a bit of a hack, not sure how well it would hold up under different situations. The other option here is to copy the required files into the build folder so they get served like static files. I am sure that also has some edge cases, but would probably be nicer for my setup.

We've had trouble historically with copying the files. Once we are running in a cordova shell - even for start - it is best to leave them in place and link relatively.
I'm working on a deeper solution /w Vue-CLI, hopefully will have time to wrap in a few more days. From there we can potentially merge your solution for more generic webpack cases :-)

Just a heads up, I've released vue-cli-plugin-corber for Vue users now.
That clears me up to merge your changes for pure Webpack. I owe it a QA and expect a merge next week. Thanks!

FYI - feel free to submit these changes directly on the webpack plugin. Thanks.


openocd issue with windows's path backslash.

This line convert parameter to absolute path using native style https://github.com/adafruit/Adafruit_Adalink/blob/master/adalink/cores/nrf51822.py#L72 in case of windows it is ‘backward slash’. However, openocd.exe on windows still take the file parameter as it would on Linux, i.e ‘forward slash’.
DEBUG:adalink.programmers.stlink:OpenOCD response: Open On-Chip Debugger 0.9.0 (2015-05-19-12:09) Licensed under GNU GPL v2 For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD adapter speed: 1000 kHz Info : Unable to match requested speed 1000 kHz, using 950 kHz Info : Unable to match requested speed 1000 kHz, using 950 kHz Info : clock speed 950 kHz Info : STLINK v2 JTAG v23 API v2 SWIM v4 VID 0x0483 PID 0x3748 Info : using stlink api v2 Info : Target voltage: 3.205380 Info : nrf51.cpu: hardware has 4 breakpoints, 2 watchpoints target state: halted target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
Error: couldn't open C:UsershathachDropboxdafruiluetoothworkspaceAdafruit_nRF51822_FlasherAdafruit_BluefruitLE_Firmwaresoftdevices110_nrf51_8.0.0_soft
device.hex
comment out the line  f = os.path.abspath(f), it will work (taking relative path).
Maybe we should force forward slash always ? I am not sure how to do it properly (blindly replace ‘\’ with ‘/’ would cause issue with actual escape e.g space on linux).

Oh ack sorry missed this until now.  Ouch what a pain, it turns out OpenOCD's Tcl interpretor doesn't like backslashes and needs to have them escaped with a second backslash: http://sourceforge.net/p/openocd/mailman/message/28333473/  I just submitted a small fix to add this backslash escaping and gave it a quick test on windows.  It seems to load firmware fine and program it (using a nRF51822 as a test).
Should just be able to do a git pull on the repo and then just for good measure run 'python setup.py develop' again (add sudo on Linux or OSX).  Let me know if you still see issues after this fix, thanks!

It works perfectly, just tested :D, thanks


Getting Started still refers to ./node_modules/mocha/bin/mocha

The Getting Started section in https://mochajs.org/ mentions
$ ./node_modules/mocha/bin/mocha

But this is not the right path anymore. #4880

fyi @juergba Hardik and I is working on this issue.

Fixed by #4927.


Automated cherry pick of #1832: 避免因cloudprovider disable导致账号同步失效

Cherry pick of #1832 on release/2.8.0.
#1832: 避免因cloudprovider disable导致账号同步失效

/lgtm
/approve


bug: autonaming conversation shouldn't take into account the system prompt

Otherwise most of my chats get named useless things like "concise" or "answer quickly" because that's part of my system prompt

System prompt is not included in chat namin request. Starting from version 3.7 name generating prompt type changed to "User"

Hi, I keep having conversation named "ConciseAnswer" or things irrelevant like that so I investigated a bit and I'm fairly conviced the system prompt is included in the chat naming request :

Should work in 3.23


Rails 5 + Rack + Rack Cors + Puma produces "can't add a new key into hash during iteration" Errors

Description
Error: can't add a new key into hash during iteration
/root/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/request.rb:79:in `set_header'
We're fighting with this persistent and long-standing error again on production with New Relic and Rack when deploying using Puma with multiple threads in Rails. It appears that the env hash isn't atomic and Rack (or rack-cors) attempts to add a key while New Relic iterates over it internally leading to a somewhat rare but breaking error. It usually takes 20-30 minutes, and the frequency increases based on number of threads, especially when not using workers. This happens on any route at random intervals.
There are some related topics I’ve found online but no public solutions, and the only solution I’ve found is either to not use New Relic at all or to set the thread count to 1 and compensate for that concurrency slack by increasing the number of workers that Puma uses. I’ve spoken to an engineer on another project using a similar setup but they don’t seem to be affected by this issue, possibly due to the fact they’re using Rails 4 and outdated gems, or that they wrap their rack-cors implementation in Grape middleware.
There seem to be other tickets out there referring to this issue as well, if any relevant communication can be relayed from those, that'd be appreciated.
Troubleshooting or NR Diag results
Provide any other relevant log data.
TIP:  Scrub logs and diagnostic information for sensitive information
Steps to Reproduce
This can be reproduced by deploying a Rails app with Puma, that has New Relic set up, and using Rack and / or rack-cors. Disable workers and increase number of threads to 16+, the higher the number of threads the more frequently this error will occur.
Your Environment
Our gem versions are:
rails <IP_ADDRESS>
rack 2.2.3
rack-cors 1.1.1
newrelic_rpm 6.15.0
puma 5.2.1
Additional context

New Relic Explorers - Ruby runtime error: “can’t add a new key into hash during iteration”
Stack Overflow - RuntimeError: can't add a new key into hash during iteration in Rack
nattfodd/stack.txt

We are experiencing this issue with:
rails 5.1.7
rack 2.0.8
rack-cors 1.0.6
newrelic_rpm 6.15.0
puma 4.3.6

The problem here is that the ENV variable contains a hash-like entity which, like all Ruby Hashes, is not modifiable while it is being iterated.
The only viable fix, short of replacing ENV in Ruby with a more concurrency-friendly structure, is to change how the NR code does the iteration.
In doing a survey of the ruby agent code, there is actually only a single location that I can find where a direct iteration over the ENV hash occurs:
https://github.com/newrelic/newrelic-ruby-agent/blob/dev/lib/new_relic/agent/connect/request_builder.rb#L52
There are options to replace this, depending on how performant it needs to be versus how resistant to race conditions (i.e. the environment being changed underneath it while it is iterating).
My hunch is that since ENV typically changes very little or not at all during the course of regular program execution, performance trumps absolute integrity. I can make a PR for you that will hopefully address this problem.

I have a fix that I did on stream. I'll send the PR tomorrow. I don't have an app/setup that I can actually test it on, though, so I may need to collab with someone else in the team to actually test it.

Quick update.  I just realized that with FutureStack, I forgot to actually create this PR.  You'll have it today.

Thank you for your fix @wyhaines , but we are still encountering this error using newrelic_rpm 7.2.0 and a similar gem configuration which to my understanding should have fixed this issue. I can provide an updated stack trace if needed, but it's ultimately the same concurrency issue (changing the ENV variable during iteration).

I can also confirm that this issue persists with newrelic_rpm 7.2.0. The easiest way I was able to reproduce in my local test environment was to do the following:

setup endpoint with bad code that will raise an error. Note that we did not explicitly raise the error, the code was just not ideal.
setup another endpoint that returns a simple html page
perform simple load test on both endpoints simultaneously

When reviewing logs, we noted that the simple endpoint that returned the html page occasionally  has iteration error.
The fix we did for our project was to prevent/explicitly rescue these errors in our app. I can imagine this issue is much more prevalent with apps that process a high volume of requests per second.

@evanjuneau @raman162 Can you tell me which versions of Rack you are both using? I am trying to figure this out, and it would be helpful to know if you are both on versions that are at or around the originally reported version of 2.2.3, or if you are on different versions?

Hi @wyhaines we are using rack 2.2.3 as well

@raman162 Thank you. I am trying to establish a minimal test case to reliably reproduce the problem. There have been some architecture changes in the Rack Request object between 2.2.3 and the current version, so I wanted to make sure that I was starting with what you all are currently using.

Thanks for your time and attention for looking into this @wyhaines. It is greatly appreciated.

I apologize for the late response. I am the original reporter for this issue through New Relic’s help section, so I want to provide a proper update with a newer stack trace using newrelic_rpm 7.2.0 attached. I’m very grateful you’re looking into this, and thank you so much for your time @wyhaines!
Here’s an updated list of possible relevant gems and their versions:
rails 5.2.6
rack 2.2.3
rack-cors 1.1.1
newrelic_rpm 7.2.0
puma 5.4.0
The easiest way I've found to test it is to bump up the number of minimum / maximum threads and don’t use workers in Puma. Then hit a few endpoints simultaneously as @raman162 mentioned. You should encounter a similar error occasionally. I should also mention that our product is using Rails in an API-only context (Rails::API).
I have also looked into our stack trace a bit, and although I do see iteration over the ENV variable explicitly (actionpack-5.2.6/lib/action_dispatch/middleware/request_id.rb:26) where it's setting the request ID in the headers hash, I'm unsure if this is caused by New Relic somewhere deeper in the stack trace specifically, or if the root of the issue is more on the side of Rails and New Relic is handling this error correctly or erroneously rescuing early. Once again, thank you!
`RuntimeError: can't add a new key into hash during iteration
/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/request.rb:79:in `set_header'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/actionpack-5.2.6/lib/action_dispatch/http/request.rb:299:in `request_id='

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/actionpack-5.2.6/lib/action_dispatch/middleware/request_id.rb:26:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/runtime.rb:22:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/activesupport-5.2.6/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/actionpack-5.2.6/lib/action_dispatch/middleware/executor.rb:14:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/actionpack-5.2.6/lib/action_dispatch/middleware/static.rb:127:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/sendfile.rb:110:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-cors-1.1.1/lib/rack/cors.rb:100:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/railties-5.2.6/lib/rails/engine.rb:524:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/newrelic_rpm-7.2.0/lib/new_relic/agent/instrumentation/middleware_tracing.rb:101:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/tempfile_reaper.rb:15:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/lint.rb:50:in `_call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/lint.rb:38:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/show_exceptions.rb:23:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/common_logger.rb:38:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/content_length.rb:17:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/configuration.rb:249:in `call'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/request.rb:77:in `block in handle_request'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/thread_pool.rb:340:in `with_force_shutdown'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/request.rb:76:in `handle_request'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/server.rb:440:in `process_client'

/root/.rbenv/versions/2.6.8/lib/ruby/gems/2.6.0/gems/puma-5.4.0/lib/puma/thread_pool.rb:147:in `block in spawn_thread'

`

I can confirm that it still happens


@remote-ui/webcompat: A DOM implementation on top of remote-ui

Video Demo:
https://user-images.githubusercontent.com/105127/195653912-52bf9df2-e7e0-46fc-837f-63b749dc7d94.mov

@developit Woah, you actually implemented it! Madman!


Need separate API section

Right now our origin.js API documentation is just mixed in with the rest of the docs. We have sections for things like Users and Listings, but these sections are at the same level as other sections such as Introduction. We really need a section called API that makes it clear what part of the docs pertains to the API. Either that, or we may eventually need separate documentation for the API. 🤔

Thanks @tyleryasaka 👍
Related to https://github.com/OriginProtocol/company-website/issues/157 ☑
I believe that the intended audience for the docs is DApp developers, and the developer landing page should be the definitive 'welcome, here are all of the places to go to learn/contribute/etc'. So I would think that these docs would be scaled down to focus on the API while some of the other stuff would move to the website.

I'm going to close this for now, as it's been a while.
That said, I'm not sure Slate is going to be the right solution for us long-term: we don't need it's feature of supporting multiple languages. Futhermore our docs site has become way more than just documenting our API methods, so the right column seems wasted most of the time.

I'm also thinking slate probably won't work long term.


Move the analytics database and related infra to BigQuery

Following a suggestion by @brunocalza, we should have some ETL or decided process to move the analytics database information living in the SQLite validator to BigQuery.
This is much nicer since:

Retool has a native interface against BigQuery, so we don't need to run postlite  in the validator VM to act as a reverse proxy to give a Postgres wire-protocol support for SQLite. Also, it potentially means removing firewall rules to let Retool access the VM.
Analytics read load won't hit the validator, prioritizing syncing chains and serving read queries.
We'd have easier access to analytics information for the team and community by directly accessing the BQ database to do ad-hoc queries.

We can easily make a batch ETL pipeline that takes the backup file we have in GCS and load them into BQ. But that means we'll have data at most 4 hours old.
Having a live copy of the validator's data into BQ (streaming ETL), requires a bit more thinking.
Maybe we can start with 1).

Yes, having a four hours delay would be a bit annoying for a live dashboard.
My take is that we should think about the streaming ETL idea and just leave things as they are until we do that. I'm not sure it is worth doing an intermediate step.
The streaming ETL could simply know which is the last block_number per chain in BQ, and do some select * from system_evm_events where chain_id=x and block_number>y limit z. It could be a simple Go program, or some cron command with a mix of bq+sqlite3, which I think it's pretty doable/easy.


Switch affiliations to datastream

Switch affiliations vocabulary to datastream and make it consistent with funders. This also needs to move the ROR transformer to common and label it more generally.

Main PR is https://github.com/inveniosoftware/invenio-vocabularies/pull/327 and small one to make it work in RDM https://github.com/inveniosoftware/invenio-app-rdm/pull/2680

Additionally there are small documentation https://github.com/inveniosoftware/docs-invenio-rdm/pull/639, cookiecutter https://github.com/inveniosoftware/cookiecutter-invenio-rdm/pull/282, and rdm-records PRs https://github.com/inveniosoftware/invenio-rdm-records/pull/1752 that should be looked at once the main PR is merged.

Will reopen until there is a vocabularies release and we can merge the app-rdm pr.

Didn't mean to close the issue, but merging connected PRs does this automatically 😅.
We're planning to merge everything next week, but need to orchestrate releases as well, to make sure dependencies don't break.

Yup, I'll let you all handle that release dance!


Material UI setup

Description
Research: Material UI Integration
This PR sets up Material UI in napari hub with SSR enabled. This library adds a lot of value to napari hub because:

It improves accessibility in napari hub and is easier to build an accessible site using MUI components.
It provides a library of components that are commonly used in napari hub designs
It'll allow us to eventually migrate over to the Science Design System

Changes

Moves colors to separate module so that it can be used by the client and in the Tailwind config
Uses transform-imports plugin to transpile Material UI imports
Server Side Rendering of Material UI components based on official Material UI example
Adds Barlow font

Unrelated to MUI, but when Napari Hub needs to add HSTS and CSP for security before launch, cellxgene has code for reference! https://github.com/chanzuckerberg/corpora-data-portal/blob/main/frontend/next.config.js

Unrelated to MUI, but when Napari Hub needs to add HSTS and CSP for security before launch, cellxgene has code for reference! https://github.com/chanzuckerberg/corpora-data-portal/blob/main/frontend/next.config.js

Thanks for letting us know Timmy! I haven't set up HSTS or CSP from scratch before, so this will be super helpful 😻


Method call and returning error "Assertion after the final assert.async was resolved"

Hi, I am trying to test javascript method as below,
var	spyPostRender = sinon.spy(proxy, "postRender");
var done = assert.async();
proxy.init();
done();
assert.ok(spyPostRender.calledOnce, "postRender() function was called.");

where init() internally calls an ajax service, however when I do this, I am getting below error. Can anybody help me in resolving this issue?
Assertion after the final `assert.async` was resolved@ 85 ms
Source:
    at Object.QUnit.assert.Assert.ok (http://code.jquery.com/qunit/qunit-1.17.1.js:1296:8)

FYI - I am using QUnit-1.17.1
Thanks in advance

@jzaefferer  any suggestions from your side? thanks in advance...

Two notes:

That behavior by design (see #668 and #669 for discussion), though it still needs to be added to the documentation (see https://github.com/jquery/api.qunitjs.com/issues/91).
You are not using this correctly. The done callback needs to be invoked only after whatever asynchronous operation it is being used for has actually resolved (not just throwing it on the next line).

Your test would probably end up looking more like this:
var spyPostRender = sinon.spy(proxy, "postRender");
var done = assert.async();
proxy.init(function() {
  // Do your real assertions BEFORE invoking the final (i.e. you may have multiple) `done` callback
  assert.ok(spyPostRender.calledOnce, "postRender() function was called.");

  // The final `done` callback MUST be called AFTER all real assertions have been made
  done();
});

Or else perhaps use a sinon.stub to override proxy.postRender to perform your async assertions:
var done = assert.async();

var _postRender = proxy.postRender;
var stubPostRender = sinon.stub(proxy, "postRender", function() {
  var result = _postRender.apply(this, arguments);

    // Do your real assertions BEFORE invoking the final (i.e. you may have multiple) `done` callback
  assert.ok(stubPostRender.calledOnce, "postRender() function was called.");

  // The final `done` callback MUST be called AFTER all real assertions have been made
  done();

  return result;
});

proxy.init();

@JamesMGreene I am new to QUnit framework so I was not fully aware of Assert.async() api usage. Thanks for your response.


initial content changes for the ITT lead mentor journey

Before
After

These all look good, with the exception of the last page with the 'or' separating the EHCO, I feel as though somewhere in the design history, that was discussed and decided against, but might need to check


No documentation on how to access value of wildcard route?

This documentation page explains how to create a route with a wild-card in it, '/user/foo/*', but it never actually explains how to access the value of the matched wildcard. e.g. if I use /user/foo/a/b/c, how do I get my hands on the a/b/c string inside of my controller? The action2 documentation doesn't seem to explain this either.
I remember once, after tons of googling, finding an answer to this in an obscure corner of the web, it had something to do with exporting a special field from your action2 file that states the name of the wildcard, but I can't seem to find that page again.

Hi @theScottyJam, I believe mikermcneil/ration has an example of this.  You can use urlWildcardSuffix: 'nameOfInput' to map the wildcard suffix (*) in your route to a string input definition.  urlWildcardSuffix is a top-level action property in actions2.

@theScottyJam Here's the documentation on that: https://sailsjs.com/documentation/concepts/routes/url-slugs#?slugs-that-might-contain-slashes

Oh, got it, thanks. Looks like I completely missed that page.
Looking at that page, and the custom routes page, I'm wondering - is there any particular reason that this stuff exists as two separate pages, instead of a single page? They both seem to be covering similar stuff - in fact, the only thing the "URL Slugs" page presents that you can't learn about from the "Custom Routes" page seems to be how you access the wildcard route's values. Everything else gets explained in "Custom Routes", but in more detail.

@theScottyJam Great Idea! We'd be happy to review a PR to combine those pages.

Hey, @eashaw are we still interested in merging those two pages? The idea is quite excellent but I'm also taking broken links if we have to do this.

Hey @eashaw I opened a PR to the slug-urls page to custom-routes. Let me know what you think.

Hey @theScottyJam the PR resolving this issue has been merged. I'm closing this issue now to save you the stress of doing that yourself :)

For reference, the merged page is:
https://sailsjs.com/documentation/concepts/routes/custom-routes
And the direct link to URL Slugs is:
https://sailsjs.com/documentation/concepts/routes/custom-routes#url-slugs


Error: "match: no such function" (regression at 99713cbc)

Since the merge of #2072, the following Z returned results. The run below is with zq commit 11b539ab and the zq-sample-data.
$ zq -version
Version: v0.29.0-24-g11b539ab

$ zq -f ndjson 'match(_path=http and windows)' http.log.gz
{"_path":"http","host":"<IP_ADDRESS>","id":{"orig_h":"<IP_ADDRESS>","orig_p":36729,"resp_h":"<IP_ADDRESS>","resp_p":80},"info_code":null,"info_msg":null,"method":"GET","orig_filenames":null,"orig_fuids":null,"orig_mime_types":null,"origin":null,"password":null,"proxied":null,"referrer":null,"request_body_len":0,"resp_filenames":null,"resp_fuids":["FnHkIl1kylqZ3O9xhg"],"resp_mime_types":["text/html"],"response_body_len":56,"status_code":301,"status_msg":"Moved Permanently","tags":[],"trans_depth":1,"ts":"2018-03-24T17:15:20.609736Z","uid":"CpQfkTi8xytq87HW2","uri":"/chassis/config/GeneralChassisConfig.html","user_agent":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)","username":null,"version":"1.1"}
{"_path":"http","host":"<IP_ADDRESS>","id":{"orig_h":"<IP_ADDRESS>","orig_p":39169,"resp_h":"<IP_ADDRESS>","resp_p":80},"info_code":null,"info_msg":null,"method":"GET","orig_filenames":null,"orig_fuids":null,"orig_mime_types":null,"origin":null,"password":null,"proxied":null,"referrer":null,"request_body_len":0,"resp_filenames":null,"resp_fuids":["Ft0zax1DqsZrA0Xjs"],"resp_mime_types":["text/html"],"response_body_len":56,"status_code":301,"status_msg":"Moved Permanently","tags":[],"trans_depth":1,"ts":"2018-03-24T17:15:20.61158Z","uid":"CpjMvj2Cvj048u6bF1","uri":"/Webcam/webcam.html","user_agent":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)","username":null,"version":"1.1"}
...

However, starting with the changes in #2131, there's an error.
$ zq -version
Version: v0.29.0-25-g99713cbc
16:42:49-phil@PhilMac:~/work/zq-sample-data/zeek-default$ zq -f ndjson 'match(_path=http and windows)' http.log.gz
match: no such function

Verified in zq commit 7ca6e7ec.
Repeating the repro steps, the match: no such function error no longer appears.
$ zq -version
Version: v0.29.0-41-g7ca6e7ec

$ zq -f ndjson 'match(_path=http and windows)' http.log.gz
{"_path":"http","host":"<IP_ADDRESS>","id":{"orig_h":"<IP_ADDRESS>","orig_p":36729,"resp_h":"<IP_ADDRESS>","resp_p":80},"info_code":null,"info_msg":null,"method":"GET","orig_filenames":null,"orig_fuids":null,"orig_mime_types":null,"origin":null,"password":null,"proxied":null,"referrer":null,"request_body_len":0,"resp_filenames":null,"resp_fuids":["FnHkIl1kylqZ3O9xhg"],"resp_mime_types":["text/html"],"response_body_len":56,"status_code":301,"status_msg":"Moved Permanently","tags":[],"trans_depth":1,"ts":"2018-03-24T17:15:20.609736Z","uid":"CpQfkTi8xytq87HW2","uri":"/chassis/config/GeneralChassisConfig.html","user_agent":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)","username":null,"version":"1.1"}
{"_path":"http","host":"<IP_ADDRESS>","id":{"orig_h":"<IP_ADDRESS>","orig_p":39169,"resp_h":"<IP_ADDRESS>","resp_p":80},"info_code":null,"info_msg":null,"method":"GET","orig_filenames":null,"orig_fuids":null,"orig_mime_types":null,"origin":null,"password":null,"proxied":null,"referrer":null,"request_body_len":0,"resp_filenames":null,"resp_fuids":["Ft0zax1DqsZrA0Xjs"],"resp_mime_types":["text/html"],"response_body_len":56,"status_code":301,"status_msg":"Moved Permanently","tags":[],"trans_depth":1,"ts":"2018-03-24T17:15:20.61158Z","uid":"CpjMvj2Cvj048u6bF1","uri":"/Webcam/webcam.html","user_agent":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)","username":null,"version":"1.1"}
...

Thanks @mccanne!


Error infinite loop Prettier: failed to parse buffer

Reproduction steps:

modify file in buffer 1 without saving
switch to buffer 2
modify file and :w
switch back to buffer 1

Error appears forever, until restarting Vim.

Thanks @alanhamlett,
I will investigate this as soon as I have some free time. This is a tricky race condition problem to solve.
Do you mind also providing some minimal code for buffer 1 and buffer 2 so that I can try to replicate locally while attempting to work on a fix for it ?

I was using prettier version 1.7.4, after upgrading to 1.10.2 I haven't noticed it happening. Probably still a bug, just not triggered unless prettier fails to parse the file?

I haven't had time to investigate this yet, lets leave this issue open to see if anyone hits on it in the next week or so, otherwise we close it.
Thanks again for all your help @alanhamlett !

@mitermayer I don't know if this will help I had the same problem like this one in this  issue:-
Prettier: failed to parse buffer
It turned out that in my case I had installed prettier using fishshell and when I switch to zsh  I encountered the problem.
You must use the same command line shell that you installed prettier with, in order for you not to get the error.

I think we fixed this on 1.x branch, will double check in there and if thats the case will port back a fix to master repo

@SamHowie, @docwhat, if any of you have sometime and can reproduce this issue, would be great to have it fixed on 1.x branch as we are getting pretty close to have a beta.

This is currently fixed on release/1.x branch which soon will be merged to mater


Renaming files including hour, minute, etc

Description of the new feature / enhancement
This feature gives you options when using PowerRename to set a format for each file, like "IMG_%H_%M_%S_%DD_%MM_%YYYY" and parameters in the new file name would be filled in based on the file's properties.
Scenario when this would be used?
This feature would come in handy when you need to rename a lot of files, for example a folder of a bunch of images, and you want to rename them all with a file name that includes the date it was taken/created.
Supporting information
No response

Possible today!  https://learn.microsoft.com/en-us/windows/powertoys/powerrename#replace-using-file-creation-date-and-time


feat(packages/rspack): support statsPrinter and statsFactory hook

Related issue (if exists)
https://github.com/web-infra-dev/rspack/issues/3090
Summary

🤖 Generated by Copilot at 82da589
This pull request adds statistics generation and printing features to the rspack module. It introduces new classes, hooks, and utilities to allow customization of the statistics. It also adds an example file to demonstrate how to use the rspack module.

Walkthrough

🤖 Generated by Copilot at 82da589

Add examples/basic/build.js file to demonstrate how to use rspack module (link)
Import and expose StatsFactory and StatsPrinter classes in compilation.ts file (link)
Add statsFactory and statsPrinter hooks to Compilation class to allow plugins to customize statistics creation and printing (link, link)
Add createStatsFactory and createStatsPrinter methods to Compilation class to create and return statistics instances and call hooks (link)
Add StatsFactory class in stats/StatsFactory.js file to create statistics objects from compilation data using hooks (link)
Add StatsPrinter class in stats/StatsPrinter.js file to print statistics objects to a string using hooks (link)
Add smartGrouping function in util/smartGrouping.js file to group items based on configurable keys and options (link)
Use createStatsFactory and createStatsPrinter methods in Stats class and add TODO comment for plugin (link)
Remove hash printing from Stats class as it is handled by StatsPrinter class (link)

@ahabhgk can you help review it?

@hardfist This only add two hooks but did nothing about factory stats (stats.toJson) and print stats (stats.toString), from my understanding, this PR is far from complete

closed in favor of #3722


MINOR: Renames IBCT files

Signed-off-by: Arkadiusz Spiewak<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Codecov Report

Merging #1017 into master will increase coverage by 0.25%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1017      +/-   ##
==========================================
+ Coverage   44.87%   45.13%   +0.25%
==========================================
  Files         240      237       -3
  Lines       22391    22202     -189
  Branches     5087     5049      -38
==========================================
- Hits        10049    10021      -28
+ Misses      12342    12181     -161

Impacted Files
Coverage Δ

...test-utils/lib/rendering/RenderingTestResultCli.ts
0% <ø> (ø)

Continue to review full report at Codecov.

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

@heremaps-bot retest this please

@heremaps-bot retest this please


Hide specific date selector

Hi,
Is it possible to hide one of the selectors in the date time selector? I've seen some code apparently doing that in native android: http://stackoverflow.com/questions/21321789/android-datepicker-change-to-only-month-and-year
There is a cool one-liner
((ViewGroup) datePickerDialog.getDatePicker()).findViewById(Resources.getSystem().getIdentifier("day", "id", "android")).setVisibility(View.GONE);
I wanted to test it but I didn't manage to compile the module on my machine.
Thanks for any help

Been away from this module for a bit but sounds like a good idea. It's on the to do list.

Great!
I managed to do it here, but I did the options specific for our use case.
Anyway, this worked
((ViewGroup) picker.getDatePicker()).findViewById(
	Resources.getSystem().getIdentifier("year", "id", "android")
).setVisibility(View.GONE);

It also works with "month" and "day".
I'll try to organize the code a bit better and will make a pull request


Make the stats test fail after 60 seconds

10min wait for each stats test is a lot. Have them fail after 60seconds.

Done and merged into ndio.


Demo, easy to miss second demo

Having both demos on one page, makes it very easy not to see the second one.

All set. The demo index.html now links to demo1.html and demo2.html so the second demo isn't hidden "below the fold"


Feature: building top bar file menu for desktop

Desktop app should support adding menuing to the Top bar menu (File, Edit, View etc). Adding menu and sub category with callbacks to flet methods. Also branding 'About' screen for an app

I think this has already been implemented: https://flet.dev/docs/controls/menubar


Cleanup SignatureGenerator.java [phab:D717]

Created by schroederc at 2016-02-16 16:43:25:

shahms accepted this revision at 2016-02-16 16:52:14

schroederc closed via commit 1b1b799b1a6a0eca836c9eca49777e600eeca743 at 2016-02-16 17:07:25


How can i use this  library with NodeJS

There really is nothing special about DTWAIN.  The DTWAIN library is a plain Windows DLL, and can be used by any language with the ability to call exported DLL functions.
Unfortunately I do not know NodeJS to answer your question.  If you know how to get NodeJS to interface to any DLL (not just this one) and call exported functions, that will be the way to use this library.
Probably you should ask a NodeJS-centric group of programmers and ask in general, how do I get NodeJS to call exported DLL functions.

Thanks，now i know how to use. i will close this issue

use node-addon-api !


Resetting the root navigator doesn't reset the params of child navigators

When you dispatch a reset action on a root navigator, it doesn't wipe the params of the various screens inside any of the child navigators.

Gonna close for inactivity (cleaning up issues) if this is still an issue in the most recent release please re-open.


python310Packages.markdownsuperscript: remove

markdownsuperscript is unmaintained, use pymdown-extensions
https://github.com/jambonrose/markdown_superscript_extension/issues/58
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 237041 run on x86_64-linux 1


18.05

Please do not send pull requests to this docker/docker-ce repository.
We do, however, take contributions gladly.
See https://github.com/docker/docker-ce/blob/master/CONTRIBUTING.md
Thanks!

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "18.05" git@github.com:docker/docker-ce.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842358448736
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Can't switch to next stored config page on 03 Data tab

Unfortunately I can't switch pages for the stored configurations on the 03 Data tab, by clicking on the page number or '>'. Only way is to type in the config name and search it.

This should be fixed and on staging now.

@bdon i can't test this out on staging, as it won't let me save configs?


ENH: optimize.curve_fit: reduce overhead of lightweight memoization

Reference issue
Closes gh-18864
What does this implement/fix?
In gh-17688, a memoizer was added to wrap the callable passed to curve_fit. It remembers the function value at the initial point (only) because the callable is called repeatedly at this point.
Currently, even after the optimizer has moved on from the initial point, the memoizer determines whether to use the memoized function value or to re-evaluate the function by comparing the argument point against the memoized initial point. This comparison is slow (microseconds) due to the overhead of np.all.
This PR takes advantage of the observation that after moving on from the initial point, the optimizer does not return to it, so the "expensive" comparison can be replaced with a faster one. Now, the memoizer remembers when the optimizer has moved away from the initial point, and thereafter immediately resorts to evaluating the function.
More information
Initially, I wrote this PR to use a new variable _memoized_func.skip_lookup, which starts as False and is set to True after the optimizer moves on from the initial point. I refactored it to re-use the existing variable _memoized_func.last_val. In retrospect, this makes the control flow logic a bit less obvious, and it doesn't really reduce diff. Let me know if you'd like me to change it back.

I read through changeset, and it's a little mind bending. One has to run through it in one's mind three times, remembering what is being supplied to the function, and thinking about flow control. It would be nicer if it was a bit clearer.
I don't know what the other approach looked like. Could you paste the other approach so that I could see it?

Much of a muchness I'd say. Let's add as-is. Thank you @mdhaber


Additional bottom spacing on "ul" and "ol" element in Microsoft Edge

Caused by list-style-image: url(data:0) when using .list and .list-inline classes. This was a workaround to remove bullets showing with list-style: none applied in Internet Explorer in some situations.
Further investigation needed.

Fixed.


Print the name of the task that hit the stack watchpoint

This may be enough to troubleshoot (increase stack size).

Thanks @rojer. I've cherry-picked this into our internal review & merge queue.

Cherry-picked as 3ac3a78, thanks for the PR!


[UX] Update icons for widget library

Please reach out for SVGs
Refer -
Doc - https://quip-amazon.com/5U2EAtnId09B/Centurion-UX-Pre-GA
Design - https://www.figma.com/file/pmsbdMcD7ieVWRFMNxStIi/VoT--AppKit-%26-Centurion?type=design&node-id=348%3A423854&mode=design&t=1zPNBiyI9sH6mezN-1

Icon size - 40px
Padding between icons - 15px
Ignore the symbol icon for now

Make sure, to remove the status component when removing the status icon from above

This is the same icon with padding as mentioned in previous comment by Navita. I need bar Icon with no padding like other icons.

Updated the widget panel and removed the text.
Also, designed the hover state - fill the icon with Grey 600 on hover or let me know if you need SVGs for the hover state.

Also, the cursor should change to drag in the hover state.
Refer this screenshot -


feat: 添加生成枚举值方法

Description of change

Pull-Request Checklist

[x] Code is up-to-date with the main branch
[x] npm run lint passes with this change
[x] npm run test passes with this change
[x] This pull request links relevant issues as Fixes #0000
[x] There are new or updated unit tests validating the change
[x] Documentation has been updated to reflect this change
[x] The new commits follow conventions outlined in the conventional commit spec

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Wiki: Add detail about mappings to wiki

Wiki Page:

https://github.com/callahantiff/BioLater/wiki/Mapping

Suggestions:

[ ] Add detailed documentation and preliminary results for each of the mappings that is being performed

[x] Files have been created in Git, will be post soon.


Python example unable to read from bag file

Required Info

Camera Model
L515

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Win 10

Platform
PC

SDK Version
2.39.0

Language
Python 3.6.8

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
I was playing around with the Jupyter notebook example depth_filters.ipynb with the stairs.bag file and wanted to see if I could use this bag file with the other Python examples as well. After modifying opencv_pointcloud_viewer.py to read from the bag file, I ran the code in the terminal via python opencv_pointcloud_viewer.py but I was met with an error instead:

It seems it was unable to open the bag file. I tried running the same chunk of code but on Jupyter notebook instead, and it ran perfectly fine. My pyrealsense2 version is 2.39.0
Am I missing something here? Is this a bug/limitation?

Hi @leemerlas
Given the error, I can only suggest checking if the file exists at this path, accessible and valid. You can open it using the RealSense Viewer, before integrating into the sample.

@dorodnic Hi, thanks for the response.
I did open it using the RealSense Viewer first, and I can open it successfully. Haven't bothered to check if the file path is valid, should I use the absolute file path instead? I made sure to put the bag file in the same directory as opencv_pointcloud_viewer.py but maybe I need to check further.

Hi @leemerlas
Were you able to check this further?  Are you still having issues?
*If we don’t hear from you in 7 days, this issue will be closed.


Autocrafting making a mess with cutting tool creating too many of them

Issue description: Autocrafting does not respect existing cutting tools and makes a lot of new ones
What happens:
Autocrafting of several processors makes many cutting tools
What you expected to happen:
Only one crafting tool is produced and used until end of its durability
Steps to reproduce:

Make crafting and patterns enough to autocraft any RS processors and try to autocreate several

...
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: 1.12.2-<IP_ADDRESS>05
Refined Storage: 1.6.3

IMHO using a solderer was way better way, this cutting tool is annoying as hell

It's about time to support damaged tools on auto crafting...

The autocrafting does support damaged tools, only not in a good way. If it didn't support it at all, it would make a new tool for every processor it wants, which currently, it doesn't.

This is essentially a duplicate of #1961.


odo describe component: display remote source code location for each container component

/kind user-story
User Story
As an IDE plugin developer or user, I want to know where the source code in the container is located, So that I can specify the mapping between source files on the local machine and the remote container.
Acceptance Criteria

[ ] odo describe component should display the source code location for each container container
[ ] odo describe component -o json should display the source code location for each container container
[ ] If the component is not running, it should get the information from the local Devfile. This depends on the values of the following container components fields :

mountSources (default value if not set is true)
sourceMapping (default value if not set is /projects)

[ ] It should not report that information if mountSources is false
[ ] When executed using the --name flag, it should get the information from the PROJECT_SOURCE (or ~PROJECTS_ROOT ?~) environment variable from the running container spec
[ ] It should also work with components running on Podman

Examples
▶ odo describe component
Name: nodejs-starter
Display Name: Node.js Runtime
Project Type: Node.js
Language: JavaScript
Version: 2.1.1
Description: Stack with Node.js 16
Tags: Node.js, Express, ubi8

Running in: Dev

Forwarded ports:
 •  <IP_ADDRESS>:40001 -> runtime:3000
 •  <IP_ADDRESS>:40002 -> runtime:5858

Supported odo features:
 •  Dev: true
 •  Deploy: true
 •  Debug: false

Container components:
 •  runtime
    Project Source: /projects
 •  build
    Project Source: /project

▶ odo describe component -o json
{
	"devfilePath": "/Users/tkral/Code/odo-examples/nodejs-starter/devfile.yaml",
	"devfileData": {
		"devfile": {
			"schemaVersion": "2.2.0",
			"metadata": {
				"name": "nodejs-starter",
				"version": "2.1.1",
				"displayName": "Node.js Runtime",
				"description": "Stack with Node.js 16",
				"tags": [
					"Node.js",
					"Express",
					"ubi8"
				],
				"icon": "https://nodejs.org/static/images/logos/nodejs-new-pantone-black.svg",
				"projectType": "Node.js",
				"language": "JavaScript"
			},
			"components": [
				{
					"name": "runtime",
					"container": {
						"image": "registry.access.redhat.com/ubi8/nodejs-16:latest",
						"projectSource": "/projects"
...

Links
Related to https://github.com/redhat-developer/odo/issues/6419
/kind user-story

I am not sure how this will work for named components in a simple way. One way it can work out is if I exec inside the component's pod and get the value of $PROJECT_SOURCE, but then we'll need to discuss how it would look in the both the output.


Simplify links - move from relative raw links to absolute raw links to GitHub

Issue #, if available:
Description of changes:
Relative links were more elegant because from the https://wellarchitectedlabs.com/ site we are using assets from that site (and not GitHub).  But they introduce ugliness in the filename when used with wget.   Therefore changing back to absolute raw links to GitHub
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Approved. This looks good.


HTML messages not displaying

Expected behavior
HTML messages should be rendered, with an option to show external images
Actual behavior
Email display is blank, with only a "download complete message" button... which does nothing
Steps to reproduce

Open HTML email from inbox
Email is displayed as blank
Press "download complete message"
Email is still blank

Environment
K-9 Mail version: 5.114
Android version: 6.0.1
Account type (IMAP, POP3, WebDAV/Exchange): Gmail (via IMAP)
Logcat:
10-18 22:53:35.104 D/k9      (28045): MessageView displaying message MessageReference{accountUuid='539ac8f9-8c8d-49be-9ead-7501fa654db4', folderName='INBOX', uid='36065', flag=null}
10-18 22:53:35.109 D/k9      (28045): Creating new local message loader
10-18 22:53:35.139 D/ConnectivityService(  820): notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 119]
10-18 22:53:35.406 D/k9      (28045): Creating new decode message loader
10-18 22:53:35.436 V/k9      (28045): LockableDatabase: Transaction ended, took 89ms / com.fsck.k9.mailstore.LocalStore.doBatchSetSelection(LocalStore.java:904)
10-18 22:53:35.502 E/k9      (28045): Unable to getTextFromPart
10-18 22:53:35.502 E/k9      (28045): com.fsck.k9.mail.MessagingException: Provided invalid part: com.fsck.k9.mailstore.LocalBodyPart@86ec7f7
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mail.internet.MessageExtractor.getTextFromPart(MessageExtractor.java:60)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mail.internet.MessageExtractor.getTextFromPart(MessageExtractor.java:42)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mailstore.MessageViewInfoExtractor.buildHtml(MessageViewInfoExtractor.java:224)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mailstore.MessageViewInfoExtractor.extractTextFromViewables(MessageViewInfoExtractor.java:186)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mailstore.MessageViewInfoExtractor.extractViewableAndAttachments(MessageViewInfoExtractor.java:115)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.mailstore.MessageViewInfoExtractor.extractMessageForView(MessageViewInfoExtractor.java:85)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.ui.message.LocalMessageExtractorLoader.loadInBackground(LocalMessageExtractorLoader.java:55)
10-18 22:53:35.502 E/k9      (28045): 	at com.fsck.k9.ui.message.LocalMessageExtractorLoader.loadInBackground(LocalMessageExtractorLoader.java:18)
10-18 22:53:35.502 E/k9      (28045): 	at android.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:312)
10-18 22:53:35.502 E/k9      (28045): 	at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:69)
10-18 22:53:35.502 E/k9      (28045): 	at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:66)
10-18 22:53:35.502 E/k9      (28045): 	at android.os.AsyncTask$2.call(AsyncTask.java:295)
10-18 22:53:35.502 E/k9      (28045): 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
10-18 22:53:35.502 E/k9      (28045): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
10-18 22:53:35.502 E/k9      (28045): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
10-18 22:53:35.502 E/k9      (28045): 	at java.lang.Thread.run(Thread.java:818)
10-18 22:53:35.567 I/Xposed  (28045): getWebViewPackageName
10-18 22:53:35.568 I/WebViewFactory(28045): Loading com.google.android.webview version 53.0.2785.124 (code 278512400)
10-18 22:53:35.700 I/art     (28045): Rejecting re-init on previously-failed class java.lang.Class<com.android.webview.chromium.ServiceWorkerControllerAdapter>
10-18 22:53:35.701 I/art     (28045): Rejecting re-init on previously-failed class java.lang.Class<com.android.webview.chromium.ServiceWorkerControllerAdapter>
10-18 22:53:35.704 I/art     (28045): Rejecting re-init on previously-failed class java.lang.Class<com.android.webview.chromium.TokenBindingManagerAdapter>
10-18 22:53:35.705 I/art     (28045): Rejecting re-init on previously-failed class java.lang.Class<com.android.webview.chromium.TokenBindingManagerAdapter>
10-18 22:53:35.746 I/cr_LibraryLoader(28045): Time to load native libraries: 10 ms (timestamps 6710-6720)
10-18 22:53:35.748 I/cr_LibraryLoader(28045): Expected native library version number "53.0.2785.124", actual native library version number "53.0.2785.124"
10-18 22:53:35.797 V/WebViewChromiumFactoryProvider(28045): Binding Chromium to main looper Looper (main, tid 1) {7f6f200}
10-18 22:53:35.797 I/cr_LibraryLoader(28045): Expected native library version number "53.0.2785.124", actual native library version number "53.0.2785.124"
10-18 22:53:35.817 I/chromium(28045): [INFO:library_loader_hooks.cc(151)] Chromium logging enabled: level = 0, default verbosity = 0
10-18 22:53:35.867 I/cr_BrowserStartup(28045): Initializing chromium process, singleProcess=true
10-18 22:53:36.124 W/cr_media(28045): Requires BLUETOOTH permission
10-18 22:53:36.204 D/ConnectivityService(  820): listenForNetwork for Listen from uid/pid:10093/28045 for NetworkRequest [ id=157, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
10-18 22:53:36.233 W/cr_AwContents(28045): onDetachedFromWindow called when already detached. Ignoring
10-18 22:53:36.274 E/SELinux (  232): avc:  denied  { find } for service=batterymanager scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:battery_service:s0 tclass=service_manager
10-18 22:53:36.286 I/cr_Ime  (28045): ImeThread is not enabled.
10-18 22:53:36.289 D/k9      (28045): No external images.
10-18 22:53:36.300 I/Choreographer(28045): Skipped 44 frames!  The application may be doing too much work on its main thread.

Original email
Link: https://gist.github.com/anonymous/caa7b4a3ed4d9090882c6e4f30c6e668

Works for me. Try uninstalling and reinstalling.
Closing this issue because you're using the Xposed framework. Chasing bugs on such a device is more often than not a waste of time. If it's a valid bug in K-9 Mail someone else will open a new issue.

Ok, that's fine.  All xposed is doing is letting me use the "system webview" from the play store on my custom rom, but that may be an issue.
I reported this because it worked fine in 5.010, but not 5.113, so I thought maybe it was related to the pgp/mime updates.


Remove Pact rake task and its dependencies

This removes a Pact test branch rake task that was never used.
Trello: https://trello.com/c/rnfUFP5o/2453-experiment-with-common-configuration-for-pact-tests-timebox-2-days

@thomasleese sorry, could I have a re-review? I've removed a bit more code, and bumped the version.


[CT-1940] [Feature] Stand-alone Python module for PostgresColumn

See also: https://github.com/dbt-labs/dbt-redshift/issues/290
Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
There is a stand-alone {adapter}/column.py module almost everywhere:

https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/adapters/base/column.py
https://github.com/dbt-labs/dbt-bigquery/blob/main/dbt/adapters/bigquery/column.py
https://github.com/dbt-labs/dbt-spark/blob/main/dbt/adapters/spark/column.py
https://github.com/dbt-labs/dbt-snowflake/blob/main/dbt/adapters/snowflake/column.py

The two exceptions are:

dbt-core/plugins/postgres/dbt/adapters/postgres/relation.py
dbt-redshift/dbt/adapters/redshift/relation.py

It's easy enough to standardize on the convention by splitting PostgresColumn into its own file.
Describe alternatives you've considered
It won't affect the functionality of the dbt-postgres adapter if it stays as-is. But it also won't affect the functionality if it is moved.
Who will this benefit?
It is easier to find the definition or compare definitions across adapters if things are in the standard locations. This is helpful for anyone inspecting the code, including adapter maintainers outside of dbt-postgres that want to compare/contrast implementation details.
It will also allow for slightly more standardization of this file:
https://github.com/dbt-labs/dbt-core/blob/c653330911ccbfdee331e56f5c2f8ced1aea5681/plugins/postgres/dbt/adapters/postgres/__init__.py#L4
Are you interested in contributing this feature?
Yep :thumbsup:
Anything else?
No response

@dbeatty10, I can pick this up along with a similar change in Redshift.

@nssalian That sounds perfect! Here's the files to create or update:

create: dbt-core/plugins/postgres/dbt/adapters/postgres/column.py
update: dbt-core/plugins/postgres/dbt/adapters/postgres/relation.py
update: dbt-core/plugins/postgres/dbt/adapters/postgres/init.py


Bugfix/config param passing

Changes:

Fixes the issue where SentinelHubRequest didn't pass config parameter to a download client.
Added a test for cases of wrong and missing credentials.
Updated integration tests regarding the recent service update.

Looks good. 👍


declaration shadows another variable

Hello,
some variable declarations shadowing another variables. So you get warnings if you have strict compiler flags (-Wshadow).
jansson/dump.c: In function 'do_dump':
jansson/dump.c:358: warning: declaration of 'key' shadows a previous local
jansson/dump.c:309: warning: shadowed declaration is here
jansson/dump.c:401: warning: declaration of 'key' shadows a previous local
jansson/dump.c:309: warning: shadowed declaration is here

Would be nice if you could change the name to solve that.
Thanks.

Fixed, thanks!


Calling new DefineClass

What should happen when new DefineClass() is called. It should set all props like can-define does.
var defineClass = new DefineClass({ a: 'b' });

Depends on https://github.com/canjs/can-define-class/issues/35

in can-define this makes the instance unsealed.

Because of proxies and unsealed being the default, you can pass undefined values into the constructor, as well as setting values on the instance, for both DefineClass and extended DefineClasses.

This was added as a test in can-define-object.


Set cannot be destroyed: it is in use by a kernel component

What happened?
Getting "ipset v7.2: Set cannot be destroyed: it is in use by a kernel component"
[root@k10dal1terarocketio ~]# kubectl get all --all-namespaces
NAMESPACE     NAME                                              READY   STATUS              RESTARTS   AGE
kube-system   pod/coredns-f9fd979d6-mdnst                       0/1     ContainerCreating   0          117s
kube-system   pod/coredns-f9fd979d6-xxzvl                       0/1     ContainerCreating   0          117s
kube-system   pod/etcd-k10dal1terarocketio                      1/1     Running             0          2m8s
kube-system   pod/kube-apiserver-k10dal1terarocketio            1/1     Running             0          2m8s
kube-system   pod/kube-controller-manager-k10dal1terarocketio   1/1     Running             0          2m8s
kube-system   pod/kube-proxy-m74fl                              1/1     Running             0          117s
kube-system   pod/kube-scheduler-k10dal1terarocketio            1/1     Running             0          2m8s
kube-system   pod/weave-net-sfwg2                               1/2     CrashLoopBackOff    4          117s

NAMESPACE     NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   <IP_ADDRESS>    <none>        443/TCP                  2m15s
kube-system   service/kube-dns     ClusterIP   <IP_ADDRESS>   <none>        53/UDP,53/TCP,9153/TCP   2m14s

NAMESPACE     NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/kube-proxy   1         1         1       1            1           kubernetes.io/os=linux   2m14s
kube-system   daemonset.apps/weave-net    1         1         0       1            0           <none>                   2m8s

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   0/2     2            0           2m14s

NAMESPACE     NAME                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-f9fd979d6   2         2         0       117s

How to reproduce it?

CentOS 8
cri-o
Kubernetes 1.19.3
Deploy weave:
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')&env.IPTABLES_BACKEND=nft"

Anything else we need to know?
Vultr VM. CentOS 8, 4GiB of RAM
Versions:

[root@server ~]# uname -a
Linux server 4.18.0-193.19.1.el8_2.x86_64 #1 SMP Mon Sep 14 14:37:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@server ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

Logs:
[root@server ~]# kubectl -n kube-system logs pod/weave-net-sfwg2 weave
ipset v7.2: Set cannot be destroyed: it is in use by a kernel component
[root@server ~]# kubectl -n kube-system logs pod/weave-net-sfwg2 weave-npc
INFO: 2020/10/20 14:16:48.880872 Starting Weaveworks NPC 2.7.0; node name "k10dal1terarocketio"
INFO: 2020/10/20 14:16:48.881322 Serving /metrics on :6781
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `NFLOG'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `BASE'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `PCAP'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:981 building new pluginstance stack: 'log1:NFLOG,base1:BASE,pcap1:PCAP'
WARNING: scheduler configuration failed: Function not implemented
DEBU: 2020/10/20 14:16:48.904826 Got list of ipsets: [weave-kube-test]
DEBU: 2020/10/20 14:16:48.904849 Flushing ipset 'weave-kube-test'
DEBU: 2020/10/20 14:16:48.905421 Destroying ipset 'weave-kube-test'
INFO: 2020/10/20 14:16:48.965197 EVENT AddNamespace {"metadata":{"creationTimestamp":"2020-10-20T14:16:20Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:phase":{}}},"manager":"kube-apiserver","operation":"Update","time":"2020-10-20T14:16:20Z"}],"name":"default","resourceVersion":"162","selfLink":"/api/v1/namespaces/default","uid":"b22b510a-72de-49fd-b8c0-a2ee10bea40b"},"spec":{"finalizers":["kubernetes"]},"status":{"phase":"Active"}}
INFO: 2020/10/20 14:16:48.976327 creating ipset: &npc.selectorSpec{key:"", podSelector:labels.internalSelector{}, namespaceSelector:labels.Selector(nil), policyTypes:[]npc.policyType(nil), ipsetType:"hash:ip", ipsetName:"weave-k?Z;25^M}|1s7P3|H9i;*;MhG", nsName:"default"}
DEBU: 2020/10/20 14:16:48.977034 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-DEFAULT, [-m set --match-set weave-;rGqyMIl1HN^cfDki~Z$3]6!N dst -j ACCEPT -m comment --comment DefaultAllow ingress isolation for namespace: default]
DEBU: 2020/10/20 14:16:48.978996 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -j WEAVE-NPC-EGRESS-ACCEPT -m comment --comment DefaultAllow egress isolation for namespace: default]
DEBU: 2020/10/20 14:16:48.980585 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -j RETURN -m comment --comment DefaultAllow egress isolation for namespace: default]
INFO: 2020/10/20 14:16:48.982342 EVENT AddNamespace {"metadata":{"creationTimestamp":"2020-10-20T14:16:19Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:phase":{}}},"manager":"kube-apiserver","operation":"Update","time":"2020-10-20T14:16:19Z"}],"name":"kube-system","resourceVersion":"10","selfLink":"/api/v1/namespaces/kube-system","uid":"1d3ff025-501b-4395-a50f-6b25a7650da3"},"spec":{"finalizers":["kubernetes"]},"status":{"phase":"Active"}}
INFO: 2020/10/20 14:16:48.985383 creating ipset: &npc.selectorSpec{key:"", podSelector:labels.internalSelector{}, namespaceSelector:labels.Selector(nil), policyTypes:[]npc.policyType(nil), ipsetType:"hash:ip", ipsetName:"weave-iuZcey(5DeXbzgRFs8Szo]+@p", nsName:"kube-system"}
DEBU: 2020/10/20 14:16:48.985956 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-DEFAULT, [-m set --match-set weave-P.B|!ZhkAr5q=XZ?3}tMBA+0 dst -j ACCEPT -m comment --comment DefaultAllow ingress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.987540 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -j WEAVE-NPC-EGRESS-ACCEPT -m comment --comment DefaultAllow egress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.989199 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -j RETURN -m comment --comment DefaultAllow egress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.992608 EVENT AddPod

Network:
# ipset list
Name: weave-;rGqyMIl1HN^cfDki~Z$3]6!N
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-s_+ChJId4Uy_$}G;WdH|~TK)I
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-k?Z;25^M}|1s7P3|H9i;*;MhG
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-P.B|!ZhkAr5q=XZ?3}tMBA+0
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-E1ney4o[ojNrLk.6rOHi;7MPE
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-iuZcey(5DeXbzgRFs8Szo]+@p
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-Rzff}h:=]JaaJl/G;(XJpGjZ[
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-41s)5vQ^o/xWGz6a20N:~?#|E
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-4vtqMI+kx/2]jD%_c0S%thO%V
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-]B*(W?)t*z5O17G044[gUo#$l
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-sui%__gZ}{kX~oZgI_Ttqp=Dp
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-mF}1zpEo4W6iYroE^=:V3{S6W
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-kube-test
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 120
References: 0
Number of entries: 0
Members:

This happens every time weave is deployed.

If I ipset destroy weave-kube-test, it just gets recreated by the weave pod every time it attempts to start.

Seeing folks hacking in a sleep 1 before the ipset destroy call:
https://github.com/replicatedhq/kURL/pull/717/commits/877767c3abf7f498574f9b2e4199e208683a4dca
It's kind of messy, but maybe something that needs added until the race condition can be figured out.

The solution listed above immediately fixed the issue for me

It seems worked for me, thank you @kallisti5. However, in CentOS 8, the issue can reproduced more easily.

It seems worked for me, thank you @kallisti5. However, in CentOS 8, the issue can reproduced more easily.

This also worked for me when using Kubespray to deploy Kubernetes cluster with Weave. After modifying roles/network_plugin/weave/templates/weave-net.yml.j2 according to the patch provided above everything worked like a charm.
Thanks!


Is it possible to add different chats like the official web

Just throwing idea here, I will be working on this feature in my fork as well.

For each chat, it won't have timeout
Able to manage (delete, rename, create, switch) chat via Telegram commands

Hmm. Do you think it'll be convenient to use such a complex non-linear structure of chats in Telegram?

Oh what does complex non-linear structure mean?

That you have multiple chat dialog in one Telegram dialog


Refit CCIPSucker progress

Description
Adapts the progress on CCIPSucker to fit in the regular JBSucker framework- sucker pairs per chain and should work with previously built infra.

Limitations & risks
We'll need to update repo env variables for the tests to pass CI here but its passing locally with my rpcs.
Are there any trade-off or new vulnarbility surface based on theses changes?
Check-list

[x] Tests are covering the new feature
[ ] Code is natspec'd
[x] Code is linted and formatted
[x] I have run the test locally (and they pass)
[x] I have rebased to the latest main commit (and tests still pass)

Interactions
These changes will impact the following contracts:

Directly:

Indirectly:

Closing, but these changes did make it onto main here https://github.com/Bananapus/nana-suckers/pull/52


Enhancement for the color picker

Description of the new feature / enhancement
It's an enhancement to the color picker, which to add a hash symbol ('#') before the HEX code, so we have it in the clipboard. And of course anyone can toggle between applying this change or not.
Scenario when this would be used?
It's very useful for developers when they want to pick a color to set it as a value on a CSS Property or something like that, so they pick a color and paste it directly with the hash symbol without writing it explicitly which is kind of an annoying thing.
Supporting information
No response

In the past, the copied value did include the #. However, a number of apps only accept 6 characters input.  Compared to that, typing a # by hand is not an effort.

And then there is /dup #8305


Forward port DataflowJavaSDK/pull/512

Also pull/500 and pull/505, both of which are in the commit for 505, but separate files.
R: @dhalperi

LGTM, thanks.


loadOutDirsFromCheck / proc macro ergonomics

We regularly get bug reports from people that are fixed by enabling loadOutDirsFromCheck or proc macros. I'm wondering what the "endgame" is here.
I think there are two reasons why we can't just enable these settings by default:

we don't want to run code without confirmation
we want to be able to function without cargo check.

But the current situation where things just silently don't work or we produce wrong diagnostics isn't really tenable, right? I think we should ideally try to detect the situations where things aren't working because a build script or proc macro wasn't run, and warn the user.
Also maybe there should long-term be a way to have cargo run build scripts and compile proc macros without doing a full check? (Edit: Ah, this is https://github.com/rust-lang/cargo/issues/7178.)
Shorter-term, here are some ideas:

detect usage of env!("OUT_DIR") and produce a diagnostic and/or a popup warning that things may not work?
suppress follow-up name resolution errors from unresolved #[path] modules?
we already resolve proc macros without them being enabled, so we should probably be able to produce diagnostics about their usage? There's probably no way to detect follow-up errors from proc macros not being run though.

Long-term, maybe we want a pop-up that says "your project requires build scripts and/or proc macros to be built correctly, do you want to run them?" and/or a whitelist?

Yeah, it's about time we think about this...
I don't think there really is a nice end-game here, short of banning build.rs and moving all proc macros to wasm.
Short-term, I think we should just bite the bullet and enable this by default: this would be better for new users, because new users typically don't have gigantic projects. And we have checkOnSave enabled by default as well (I think?), so not-enabling loadOutDirsFromCheck is a no-op.
We do need to improve quality of implementation though, before we flip the switch.
Firstly, we need to make loading asynchronous. We first should execute basic cargo metadata, get something working, and only then run/wait for cargo check to fetch proc macros and build scripts. This might lead to some double work though, not sure what's the best way out here. Stupid solution (before we even confirmed that this is a problem): use trimmed-down crate graph at the start, by only adding sysroot deps. That way, we'll pre-process sysroot, but wont prime the world only to be re-checked again with proc macros. Though, this probably is overengineering --
Secondly, we need to add better observability for cargo check: capturing of errors, tracking the time, reporting progress.
Thirdly, we should expose this observability to users: make sure that errors are properly shown, add command to re-query cargo check. Maybe add some pop-ups to enable/disable the features, but I can't see a useful condition here (showing popup on the start would be a no-go, for example :-) ). I guess, we can try to special-guess diagnostics, but my gut feeling that the result would be "Yes" for any non-trivial project -- at least one crate in the crate graph will use build.rs

I agree that we should enable them by default, like we do for all features.
One thing that's missing is detecting a proc macro server that crashes and disabling the feature. This is useful when there's an ABI mismatch, like we had before. I'm not sure we can support multiple ABIs, though.

I wonder... what is the behavior of rustc if you feed rustc A with proc-macro crate compiled with rustc B when:

A and B are different versions, but proc-macro-abi compatible?
A and B are different versions, and macro abi's are incompatible?

See also https://github.com/rust-analyzer/rust-analyzer/issues/6174, though I'm not sure why it's needed.

Ok, so this is 1) but not 2). This means that we need to map rustc version to ABI version ourselves (basically, we need to remember the latest version of rustc we are compatible with, which is either Some(version) if there's a known incompat, or None otherwise)

I wonder... what is the behavior of rustc if you feed rustc A with proc-macro crate compiled with rustc B when:

If the version differs, rustc behaves the same as with any other crate, which is reporting an error. Rustc decodes the full crate metadata for proc macros, which is much more unstable than the ABI of just libproc_macro.

This means that we need to map rustc version to ABI version ourselves (basically, we need to remember the latest version of rustc we are compatible with, which is either Some(version) if there's a known incompat, or None otherwise)

Maybe libproc_macro could export an ABI version just for use by rust-analyzer? This ABI version would then be incremented manually every time there is an ABI incompatible change to libproc_macro.

Maybe libproc_macro could export an ABI version just for use by rust-analyzer? This ABI version would then be incremented manually every time there is an ABI incompatible change to libproc_macro.

Yeah, that would plausible, but that means some manual and hard to remember work in the compiler. This is the right solution theoretically, but, organizationally, I think it would be easier to maintain this ABI version on our side (by mapping from rustc version to ABI version).

I wonder... what is the behavior of rustc if you feed rustc A with proc-macro crate compiled with rustc B when:
* A and B are different versions, but proc-macro-abi compatible?

* A and B are different versions, and macro abi's are incompatible?

error[E0514]: found crate `chalk_derive` compiled by an incompatible version of rustc
  --> /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/chalk-ir-0.36.0/src/lib.rs:13:5
   |
13 | use chalk_derive::{Fold, HasInterner, SuperVisit, Visit, Zip};
   |     ^^^^^^^^^^^^
   |
   = help: please recompile that crate using this compiler (rustc 1.51.0-dev)
   = note: the following crate versions were found:
           crate `chalk_derive` compiled by rustc 1.49.0-beta.1 (21dea46d8 2020-11-18): /home/joshua/rustc3/build/x86_64-unknown-linux-gnu/stage1-rustc/release/deps/libchalk_derive-843b3d0b9b865ca6.so

I wonder... what is the behavior of rustc if you feed rustc A with proc-macro crate compiled with rustc B when:
* A and B are different versions, but proc-macro-abi compatible?

* A and B are different versions, and macro abi's are incompatible?

error[E0514]: found crate `chalk_derive` compiled by an incompatible version of rustc
  --> /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/chalk-ir-0.36.0/src/lib.rs:13:5
   |
13 | use chalk_derive::{Fold, HasInterner, SuperVisit, Visit, Zip};
   |     ^^^^^^^^^^^^
   |
   = help: please recompile that crate using this compiler (rustc 1.51.0-dev)
   = note: the following crate versions were found:
           crate `chalk_derive` compiled by rustc 1.49.0-beta.1 (21dea46d8 2020-11-18): /home/joshua/rustc3/build/x86_64-unknown-linux-gnu/stage1-rustc/release/deps/libchalk_derive-843b3d0b9b865ca6.so

We should also take a look at https://github.com/rust-analyzer/rust-analyzer/issues/3155 before enabling build script support.

We should also take a look at https://github.com/rust-analyzer/rust-analyzer/issues/3155 before enabling build script support.

@lnicola I think that issue is independent of loadOutDirsFromCheck, since it affects the diagnostics we get from check-on-save.

@lnicola I think that issue is independent of loadOutDirsFromCheck, since it affects the diagnostics we get from check-on-save.

Is there any reason not to enable loadOutDirsFromCheck right now already? Also I think we should find a better name for the setting while we're at it.

The big reason is security: running build.rs when you just "read" the
code opens you to attacks. I believe our strategy here would be :shrug:,
but I opened
https://internals.rust-lang.org/t/running-build-rs-in-rust-analyzer/14154
to discuss. I've already started renaming settings yesterday, but
apparently lost the code :( I want local history back ;(
On Wed, 3 Mar 2021 at 14:00, Florian Diebold<EMAIL_ADDRESS>wrote:

Is there any reason not to enable loadOutDirsFromCheck right now already?
Also I think we should find a better name for the setting while we're at it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/issues/6448#issuecomment-789629023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3M5R37JSXPVO6XJQDJ3TBYJGHANCNFSM4TIUZN3A
.

Yeah, but we have checkOnSave enabled by default anyway already.

We could maybe only enable it by default if checkOnSave is enabled? :thinking:

Since proc-macro is enabled by default for now, maybe we close this one  ?

Status: we now set runBuildScripts to true by default.

Since proc-macro is enabled by default for now, maybe we close this one ?

Does that imply that loadOutDirsFromCheck has been removed? According to the VSCode config linter it is an "unknown configuration setting"

but on the other hand there is still some mention of it in the manual.
I'm asking, because the godot-rust FAQ recommends to use "rust-analyzer.cargo.loadOutDirsFromCheck": true to get around the non-working rust-analyzer support. It doesn't seem to be working though. The question whether loadOutDirsFromCheck is still a thing also came up in https://github.com/rust-analyzer/rust-analyzer/issues/5040#issuecomment-875817402.

I think we renamed it to rust-analyzer.cargo.runBuildScripts(Note that these are enabled by default now). Judging from the screenshot in that FAQ I imagine the problem for auto completion here is now the use of attribute/derive macros and them failing expansion on invalid syntax(an unfinished "foo." is not a valid expression) and as such preventing us from offering . completions properly.

I'm puzzled by this. The fix for my proc macro issues was as per #7497 which I implemented 10 minutes ago, but this thread suggests I should be having macros working properly now. Is this an interaction with CoC? I'm regularly updating rust-analyzer whenever prompted.

Both settings should be on by default. Maybe CoC turns them off by default from the client side.


chore: test ci

" ci / build (8) " has been failing in https://github.com/googleapis/gapic-generator-java/pull/1156. Creating an empty pull request to see the build failures.

Bazel version 6.0.0 is suspicious.

Indeed, I'm able to reproduce the issue in Bazel 6.0.0.
https://github.com/bazelbuild/bazel/releases 6.0.0 was released today.


Maya: Set default value for RenderSetupIncludeLights option

Fix
RenderSetupIncludeLights must be either set to 1 or 0 or not at all. This PR is adding default value for edge cases where this is not handled. Without it, DL is crashing.

another question is, for cases with the missing attribute on the instance and in settings, if the "safer" default value should be 0 instead of 1

I think it should follow Maya default and that is 1. Added code to pull default value from the Settings.

I think it should follow Maya default and that is 1. Added code to pull default value from the Settings.

that's exactly what I meant. I thought our default 0 is Maya's default. You are correct it is 1, so we should change our defaults in openpype\settings\defaults\project_settings\maya.json  to 1 to follow Maya's default value.