[Bug] Ubuntu 18.04 - Crash on application startup

Describe the bug
The application is unresponsive when launched. It's memory usage goes up to ~2gb and CPU usage spikes, then the application crashes.
Samples of terminal outputs :
insomnia
Error org.freedesktop.DBus.Error.Failed: cannot use setting "default-url-scheme-handler": not allowed
[fix] Running database repairs
[db] Initialized DB at /home/user/snap/insomnia/55/.config/Insomnia/insomnia.$TYPE.db
Init responses DB
[localstorage] Initialized at /home/user/snap/insomnia/55/.config/Insomnia/localStorage
[main] Loading file:///snap/insomnia/55/resources/app.asar/renderer.html
[updater] Updater not running platform=linux dev=false

#
# Fatal error in , line 0
# API fatal error handler returned after process out of memory
#
#
#
#FailureMessage Object: 0x7efec8a30120#0 0x0000013f80a3 <unknown>
#1 0x00000354d28b <unknown>
#2 0x7efee19619e8 <unknown>
#3 0x7efee22e0ad0 <unknown>
#4 0x7efee1c19e12 <unknown>
#5 0x7efee1c07f23 <unknown>
#6 0x7efee1c077da <unknown>
#7 0x7efee1c07477 <unknown>
#8 0x7efee1c25d3e <unknown>
#9 0x7efee1bf4e6e <unknown>
#10 0x0000013f9db4 <unknown>
#11 0x00000139a49e <unknown>
#12 0x00000139ab7b <unknown>
#13 0x000001399cfb <unknown>
#14 0x00000137eb7b <unknown>
#15 0x0000013ab031 <unknown>
#16 0x7efee0ee56db <unknown>
#17 0x7efeda92f88f <unknown>

<--- Last few GCs --->

[30216:0x219319d2f000]     4749 ms: Mark-sweep 1386.0 (1464.2) -> 1385.7 (1465.7) MB, 116.5 / 0.0 ms  allocation failure GC in old space requested
[30216:0x219319d2f000]     4911 ms: Mark-sweep 1385.7 (1465.7) -> 1385.7 (1432.7) MB, 161.9 / 5.0 ms  last resort GC in old space requested
[30216:0x219319d2f000]     5070 ms: Mark-sweep 1385.7 (1432.7) -> 1385.7 (1432.2) MB, 158.8 / 4.7 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x3463246040bd]
    1: StubFrame [pc: 0x34632465872a]
Security context: 0x16ee90152fe9 <String[7]: file://>
    2: replace(this=0x3630ca7e819 <Very long string[649231954]>,0x3630ca7e841 <JSRegExp <String[6]: ^\s*\n>>,0x18eb7a282441 <String[0]: >)
    3: json [file:///snap/insomnia/55/resources/app.asar/bundle.js:241116] [bytecode=0x2cb898a08f9 offset=806](this=0x37e67bd04159 <Object map = 0x31d543e05d1>,/* anonymous ...

To Reproduce
Launching the application. I am unsure what caused this suddenly since it worked fine before.
Expected behavior
The application is responsive and doesn't crash.
Desktop (please complete the following information):

OS: Ubuntu 18.04 running LXDE
Installation Method: snap
App Version: 7.0.6

Additional context
Add any other context about the problem here.

On macOS Mojave 10.14.6 (18G84) I am seeing Insomnia 7.0.6 crash immediately after startup - split second of the app jumping in the dock before closing immediately.

Having this same issue on newest version: 7.1.1 using snap.
Tried uninstalling / reinstalling, and downgrading to 7.1.0, but still same issue.
Error org.freedesktop.DBus.Error.Failed: cannot use setting "default-url-scheme-handler": not allowed
[fix] Running database repairs
[db] Initialized DB at /home/user/snap/insomnia/62/.config/Insomnia/insomnia.$TYPE.db
Init responses DB
[localstorage] Initialized at /home/user/snap/insomnia/62/.config/Insomnia/localStorage
Trace/breakpoint trap (core dumped)

Trying it again today, the app is now version 7.1.1 and seems to behave normally.

I just installed a bunch of updates to my system yesterday... Maybe something there that broke insomnia.

It seems like Snap is somehow broken... My Spotify stopped working as well, with similar Gtk messages. Installing insomnia via apt works.

Seems like a duplicate of https://github.com/Kong/insomnia/issues/1873 and https://github.com/Kong/insomnia/issues/1700

@tvelich At least not 1873, since that freezes the whole system. For me it just won't start with those Gtk messages. Installing insomnia from the repositories works though, so it seems like the snap package is broken somehow.

Still happening on the latest version for me unfortunately. I'm wondering if this has to do with an existing Electron app running already. It seems to not do this as frequently if I close Slack before launching Insomnia.

Error org.freedesktop.DBus.Error.Failed: cannot use setting "default-url-scheme-handler": not allowed
[fix] Running database repairs
[db] Initialized DB at /home/otavio/snap/insomnia/65/.config/Insomnia/insomnia.$TYPE.db
Init responses DB
[localstorage] Initialized at /home/otavio/snap/insomnia/65/.config/Insomnia/localStorage
[1]    26683 trace trap (core dumped)  insomnia

snap --version

snap    2.44.3-2
snapd   2.44.3-2
series  16
arch    -
kernel  5.6.7-arch1-1


Balck screen after navigating

This modules is leaving a black frame on the lower part of the app after navigating away from it. I only manage to remove the black frame after reopening the app.
Also it needs urgently a start and stop feature.

Nothing?

can confirm

I'm experiencing the same issue.
The scanner is in an initial Scene. Another Scene is loaded when onBarCodeRead is fired.
The first time the second Scene is loaded, everything is fine. If I go through that process again, the black frame is visible and wont leave until the app is reopened.

I did a hack that fixes this. But it has to be done on the JAVA side.

@affibox Maybe fork and make a pull request if you haven't done that yet.

@affibox  Please share fix :+1:

@obykoo @Scimonster i just saw this message. Let me see if i can tackle this in the morning. God bless

Please look at this code
'''
<BarcodeScanner
onBarCodeRead={this.barcodeReceived.bind(this)}
style={{ width:(Dimensions.get('window').width0.95),height:(Dimensions.get('window').height0.95) }}
torchMode={this.state.torchMode}
cameraType={this.state.cameraType}
>
'''
I remember that the problem went away after hardcoding the height and width of the bardcode scanner component.
Let me know if this works.

Did it work? @Scimonster @obykoo

@affibox it works if not set width to SCREEN_WIDTH

I've encountered the same issue, this works for me:
I set <BarcodeScanner>'s width to Dimensions.get('window').width - 1 and the height to Dimensions.get('window').height - 25 where 25 is the height of the status bar. Then I placed it inside a <View> with a background color black to at least hide the white border appearing.
<View style={{flex: 1, alignItems: 'center', justifyContent: 'center', backgroundColor: 'black'}}>
  <BarcodeScanner
    onBarCodeRead={this.barcodeReceived.bind(this)}
    style={{width: Dimensions.get('window').width - 1, height: Dimensions.get('window').height - 25}}
    torchMode={this.state.torchMode}
    cameraType={this.state.cameraType}
    />
</View>


Add metrics e2e tests

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Adds sanity tests for general and local queue metrics
Which issue(s) this PR fixes:

Fixes #3746
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/cc @mbobrovskyi

/ok-to-test

/retest


Starter has optional dependency

Describe the bug
Both starters have an optional dependency to the loadbalancer starter. As described in the reference documentation, an optional dependency serves no purpose for a starter as it is an empty jar.
Sample
n/a

Where has two starter? One is spring-cloud-starter-gateway, other one is ?


Materialbox

Hello,
I have issue when put materialbox in modal.
I have black square rectangle in background and position of image is random.
Codepen: http://codepen.io/vdeville/pen/KzEQxM
Regards

Your codepen is using outdated materialize files


proxy failed due to {'status': 407, 'reason': b'Proxy Authentication Required'}

Hi i getting this error may time i have used my own custom middleware i have passed proxy like this http://username:password@<IP_ADDRESS>:12345"
error message
scrapy.core.downloader.handlers.http11.TunnelError:Could not open CONNECT tunnel with proxy <IP_ADDRESS>:12345 [{'status': 407, 'reason': b'Proxy Authentication Required'}]

Same issue


Syntax highlighting broken by fn_error_context::context attribute macro

Putting #[fn_error_context::context("something")] on an async function causes RA's syntax highlighting to get confused:

The same is not true for other attribute macros, for example tracing::instrument.
No idea whether this can be fixed without complete attribute macro support in RA (it's still incomplete, right?) and / or whether there is something fn_error_contexts author can do about this (I guess there has to be, considering it works for tracing). Just opening this to get some more eyes on the problem.

If the issue is just that async is highlighted as if it was a literal, that's a known bug with attribute macros (and shouldn't be too hard to fix)

Well, goto-def also doesn't work but I imagine that's harder to fix and probably alrady tracked elsewhere.

@jplatte I assume you have rust-analyzer.experimental.procAttrMacros turned on? What exactly do you mean by find references not working -- finding references to the function with the attribute, or finding references inside its body?

@jplatte I assume you have rust-analyzer.experimental.procAttrMacros turned on?

Yes.

What exactly do you mean by find references not working -- finding references to the function with the attribute, or finding references inside its body?

The former is what I meant, though I just checked and found that both don't work, at least for the affected function that also has the syntax highlighting problem. I did just notice that this doesn't affect all functions with the #[context] attribute though, for some both syntax highlighting and finding references works just fine; I can't tell what's the difference between functions where it works and those where it doesn't.


NativeWind error 😱

When using NativeWind className, I get the following error:
This error is located at:     in CssInterop.Text (created by UITextView) ... ERROR  [ERROR: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.]
Current setup:
M1 mac 14.5
node 20.12.2
expo 51.0.8 (default template)
nativewind 4.0.36
react-native-uitextview 1.1.7
ios 17.5
No error when only using StyleSheet. Other react native components are functioning with NativeWind.

huh...I was lazy and put a platform check at the top of a component which does break react rules and could just be move to a parent component, but that's still weird to me. does native wind change the value of Platform.OS for some reason?
can push a fix up for that in a bit, but otherwise there shouldn't be any hook calls.

@aretrace Okay, I removed that in 1.1.8. Coudl you try that and see if it's helpful at all?

🧐
When I add the uiTextView prop or the selectable prop on UITextView by themselves, UITextView renders className styles as expected. BUT, when both uiTextView and selectable props are on UITextView, all NativeWind className styles do not render (they are completely ignored as if no styles exist).
With StyleSheet, when the uiTextView prop or the selectable prop is applied to UITextView by themselves, StyleSheet functions normally. BUT, when both uiTextView and selectable props are on UITextView, fontWeight is not applied. (I suspect other CSS properties could also not be appropriately rendered or applied by UITextView when both props are used)

previous error no longer appears


Cluster and transport code clean up. Part 3

Introduce new Message and migrate all components to it
Clean up IGossipProtocol interface and make it work with new Message
Clean up IClusterMembership interface
Clean up Cluster code and ICluster interface (without JavaDocs yet)

@ronenhamias We need to say from where this message arrived - TransportMessage basically a wrapper that contain Message and sender member from where this message arrived.
This class should be improved, I didn't modify it in this PR, but still conceptually it will be the same - message + origin.

@ronenhamias @antonkharenko  Message now provides headers map, so origin could be put there. In this case we wouldn't need TransportMessage.

@artem-v it is string-string map - what we should put as origin - originEndpointId?

I am just thinking that it can be kind of abuse of Message if we will extend it with additional headers which were not sent by sender.

@antonkharenko originEndpoint as well, as it could also be wrote down as string.

@antonkharenko More to say on this origin. This should be a collection.  Imagine we send message from A to C via some transit nodeB: nodeA  --> nodeB --> nodeC.

@artem-v I think it is very specific and I don't think it should be built into Transport. Actually how it is done if FD make sense - if you need it it can be part of the data. Currently Transport support only point to point connection and actually it should support only point to point connection so origin only one. There may be other component on top of transport which is doing this transit sends, but it will be responsibility of this component to handle paths

+1

+1 but do not forget to squash the commits

Rebased and squash


Release 0.5.0

[0.5.0]
Added

New github action workflow and Jupyter notebook that can be used for testing the concise service via Harmony

Changed

issues/34: harmony-service-lib-py version updated to ^1.0.20 to support reading/writing STAC objects to/from S3

Deprecated
Removed
Fixed
Security

I think Zoltan has more work on this before it should be released.

@jamesfwood we can get this release in ops as is. We want the new service lib version to get deployed.

Yes, merging it now


v7.0.0

This is a sizeable PR, but is mostly updating deps, modifying tooling, updating docs, cleaning up TypeScript, and adding two new features and one fix.
Here's a rundown:

Dependencies were updated
Tooling was updated
TypeScript config, imports, and types were cleaned up
Docs were cleaned up to reflect new features and updated integrations with lint-staged and husky
Features

Transformations:

There is support for a special * property on transformations in the config that allows you to override the default behavior when a property is found that doesn't have a defined transformation.

By default, values without specified transforms are alphabetized

CLI:

A new --check option has been added that will exit code 2 if files did/would change. The exit code choice is purposeful to distinguish it from an exit code of 1 when there is an error. --check and --write options can be used together.
Small formatting changes for how the output is written per each file being formatted

Fixes

exports are no longer ordered by default

Closes #116
Closes #113

Hey there! Nice to see you're working on this! Need a hand on something?

Quick sanity check would be nice if you have a moment to spare. Tests and such are passing with your PR logic and feedback in issues, but it's probably wise for another set of eyes to glance at it.

Hey there ! Don't hesitate to close review conversations if you think they are not relevant. I'll validate my review once all are closed to unblock github workflows


Add foreign key parsing for schemarb parser

Summary
Add foreign key parsing for schemarb parser.
Related Issue
For postgres paser:

https://github.com/liam-hq/liam/pull/131

Changes

Testing

Other Information
Two patterns of notation for foreign key constraints in schema.rb
1⃣: Foreign key constraints at the same time as table creation
create_table :products do |t|
  t.references :category
end

2⃣: Foreign key constraints after table creation
add_foreign_key :articles, :authors

I looked through several Rails projects and they are all written in  2⃣.
https://github.com/mastodon/mastodon/blob/main/db/schema.rb
https://github.com/autolab/Autolab/blob/master/db/schema.rb
https://github.com/lobsters/lobsters/blob/master/db/schema.rb
https://github.com/astuto/astuto/blob/main/db/schema.rb
https://github.com/chatwoot/chatwoot/blob/develop/db/schema.rb
It would be good to support  2⃣ first.
If we find a project that uses  1⃣, we can support that as well.

1⃣: Foreign key constraints at the same time as table creation
create_table :products do |t|
  t.references :category
end

t.references :category, foreign_key: true is needed?

It would be good to support 2⃣ first.
If we find a project that uses 1⃣, we can support that as well.

Yes, I also think Rails' schema dumper always uses 2⃣. Since db/schema.rb isn’t manually written, I believe t.references :category, foreign_key: true won’t appear in the schema file (db/schema.rb ) as a result. 👍

@hoshinotsuyoshi

t.references :category, foreign_key: true is needed?

Yes, thank you for letting me know.
When we need foreign key constraint on database, foreign_key: true is needed.

When using references in a migration, you are creating a new column in the table and you'll have the option to add a foreign key using foreign_key: true to that column.
https://guides.rubyonrails.org/active_record_migrations.html#foreign-keys


Revisions on mechanism for don't save and stay_active?

So the stay active system is only turned on at create time if you want it? The don't save bit being always on in the same way seems potentially problematic if we ever run into an issue of training multiple agents at once. Most of our simulations don't do that but my RumbleBlocks implementation can do it.
Originally posted by @eharpste in https://github.com/cmaclell/apprentice_learner_api/pull/29

So I think the main issue is that currently the "stay active" system assumes there is only 1 agent being used at a time. The one time I implemented a similar system in the past I had a dictionary of active agents that could be looked up by their ids because the way I RumbleBlocks system worked it was possible to have actions for different agents interleaved. One possible solution is to just say architectures like that are dumb and we don't support them. Another possible option could be to require that you send a "keep_active":True signal with all requests as long as you want to keep the current agent active and not save it and then as soon as you don't see that signal save and dump the current agent and otherwise assume you should save.

Related side note, we should probably create something, maybe a wiki page, that documents the RESTful-ish API. Its kind of written up in doc comments but we don't have a page that generates those so its not really helping anyone.

@DannyWeitekamp has this issue been resolved?

This is related to #39

@DannyWeitekamp has this issue been resolved?

nope

Closing this issue for now, as stay active is now default behavior.


Move to Apache Thrift

This replaces FBThrift with Apache Thrift. This is possible now that
THeaderProtocol is available in Apache Thrift. This is a breaking change
that will require modification to services built on Baseplate, but the
wire protocols should be identical so it should be possible to upgrade
piece by piece.
As an example of what a service would need to do to upgrade, this
is the diff for the activity service.
diff --git a/reddit_service_activity/__init__.py b/reddit_service_activity/__init__.py
index dd8c607..e1acf20 100644
--- a/reddit_service_activity/__init__.py
+++ b/reddit_service_activity/__init__.py
@@ -14,7 +14,7 @@ from baseplate import (
     tracing_client_from_config,
 )
 from baseplate.context.redis import RedisContextFactory
-from baseplate.integration.thrift import BaseplateProcessorEventHandler
+from baseplate.integration.thrift import baseplateify_processor

 from .activity_thrift import ActivityService, ttypes
 from .counter import ActivityCounter
@@ -48,7 +48,7 @@ class ActivityInfo(ttypes.ActivityInfo):
         )

-class Handler(ActivityService.ContextIface):
+class Handler(ActivityService.Iface):
     def __init__(self, counter):
         self.counter = counter

@@ -142,8 +142,5 @@ def make_processor(app_config):  # pragma: nocover

     counter = ActivityCounter(cfg.activity.window.total_seconds())
     handler = Handler(counter=counter)
-    processor = ActivityService.ContextProcessor(handler)
-    event_handler = BaseplateProcessorEventHandler(logger, baseplate)
-    processor.setEventHandler(event_handler)
-
-    return processor
+    processor = ActivityService.Processor(handler)
+    return baseplateify_processor(processor, logger, baseplate)

Applications that use Thrift directly would need a little more work (some things got renamed; the Serializer util isn't provided in Apache thrift, so Baseplate now provides it, and Baseplate's thrift pool got moved to be more consistent), but over all it should be a pretty mechanical upgrade process.
For reddit production purposes, we'll need to package Apache Thrift's compiler and Python library off the current upstream HEAD and then use that instead of fbthrift.
There are a few things about this PR I don't love. I'll comment on them to call them out and would love suggestions of alternative approaches.
Tests will be failing in CI right now, unfortunately, since it'll be trying to use FBThrift. I'll try and get some packages ready so we can try it out properly, but until then either trust me that all the checks are passing or pull it down locally and try :)

:eyeglasses: @dellis23 @bsimpson63 @ckwang8128

🐟 lgtm

:haircut_man: packages are up in a new PPA (super easy to build thanks to upstream packaging!) and travis is updated. this pointed out that i had an overbroad gitignore and the new baseplate.thrift.utils module (with serializer stuff) wasn't added to git!


Fixed switching between reports

Addresses issue discovered during the revision process for #168 (should be merged before)

Generated reports

There is same issue here as mentioned in https://github.com/EmbedITCZ/jbehave-support/pull/173#issuecomment-523039145

It seems to still be broken in Firefox. Working on a way to fix it


If a hostname is in additionalSeeds, resolve the address to an IP

Fixes #232
Adds only IPv4 addresses.

If I create dc1 in namespace n1 and dc2 in namespace n2, then with this change should I able to specify the seed service of dc2 for AdditionalSeeds?

If I create dc1 in namespace n1 and dc2 in namespace n2, then with this change should I able to specify the seed service of dc2 for AdditionalSeeds?

Yeah. You should make sure to use something that resolves to PodIPs, though, not a ClusterIP.


mqtt: add tests for MQTT log limiting -- v3

Previous PR: #1836
Changes compared to previous PR:

Rebase against current master.
Rename tests to mqtt-limit-log-* to reflect the fact we're not only restricting messages anymore.
Add test for topic array limiting.
Remove unneeded requirements, add minimum version 8 requirement.

Redmine ticket: https://redmine.openinfosecfoundation.org/issues/6984

Thanks for taking a look!


Adding missing feature descriptions - Batch 6

In the interest of getting https://github.com/web-platform-dx/web-features/pull/761 done ASAP I'm going to merge this and make a list of things that @ddbeck might want to review post facto and send tweaks for.


Dockerfile 3 to 5 NODE=ENV=production

A small typo in these Dockerfiles on line 2 of each you've got NODE=ENV=production and it should be NODE_ENV=production.

Thanks, fixed.


[NPM-3068] Don't use hardcoded ports for some tests

What does this PR do?
Fixes failures like https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/414351549
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Add offline build capability.

Removed flag changing from Spine protobuf plugin dependency.
To update the plugin bump it's version or change it into + sign in the short form.

Current coverage is 80.42% (diff: 100%)

Merging #208 into master will not change coverage

@@             master       #208   diff @@
==========================================
  Files           147        147
  Lines          5406       5406
  Methods           0          0
  Messages          0          0
  Branches        595        595
==========================================
  Hits           4348       4348
  Misses          949        949
  Partials        109        109

Powered by Codecov. Last update a160936...f3077c7

@armiol PTAL

@armiol PTAL again


Http metrics - add scraping for serval api

Everything standard - hopefully Prometheus will be able to parse this without further configuration.

This change is

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/Serval.ApiServer/Startup.cs
65.82% <0.00%> (-2.44%)
:arrow_down:

... and 27 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.

This addresses #83.


WARN[0000] failed to read virtualbox state file

Trying to build the example go rumprun unikernel (as described here https://github.com/emc-advanced-dev/unik/blob/master/docs/getting_started.md). I am running this on a mac using docker for mac beta (is this even supported?).
When I run the unik daemon I get the following output:
$> unik daemon
INFO[0000] daemon started                                config={Providers:{Aws:[] Vsphere:[] Virtualbox [{Name:vsphere-1 AdapterName:vboxnet0 VirtualboxAdapterType:host_only}]} Version:}
INFO[0000] Bootstrapping provider virtualbox with config {vsphere-1 vboxnet0 host_only}
WARN[0000] failed to read virtualbox state file at /Users/matt/.unik/virtualbox/state.json, creating blank virtualbox state  error=[state/base_state.go:36] error reading save file /Users/matt/.unik/virtualbox/state.json: {open /Users/matt/.unik/virtualbox/state.json: no such file or directory}
[martini] listening on :3000 (development)

When I run the unik build command I get the following output:
$> unik build --name goImage --path ./ --compiler rump-go-virtualbox --provider virtualbox
INFO[0000] running unik build                            args=[] compiler=rump-go-virtualbox force=false host=localhost:3000 mountPoints=[] name=goImage path=./ provider=virtualbox
INFO[0010] App packaged as tarball: /Users/matt/.unik/159192136

ERRO[0044] build failed: [cmd/build.go:95] building image failed: {[client/images.go:54] failed with status 500: [daemon/daemon.go:254] failed to compile raw image: {Cannot connect to the Docker daemon. Is the docker daemon running on this host?}}

as far as Docker for Mac, I don't have access to the beta, so I haven't been able to test it. However, another user reported that it was working for him. Usually the Cannot connect to the Docker daemon. Is the docker daemon running on this host? error is related to whether docker is accessible from the terminal running the daemon. Ctrl+C on the daemon terminal and run docker ps. If that's working, I may have another idea to deal with this issue and it should be easily fixable with a quick patch.
By the way, that Warning is just a warning that no state file has been written yet (meaning no unikernels have been compiled yet). I should maybe change it from a warning to something less error-ish

$> unik daemon
INFO[0000] daemon started                                config={Providers:{Aws:[] Vsphere:[] Virtualbox:[{Name:vsphere-1 AdapterName:vboxnet0 VirtualboxAdapterType:host_only}]} Version:}
INFO[0000] Bootstrapping provider virtualbox with config {vsphere-1 vboxnet0 host_only}
INFO[0000] checking if instance listener is alive...
INFO[0000] listening for udp heartbeat...
INFO[0000] UDP Server listening on <IP_ADDRESS>:9876
INFO[0010] cannot contact instance listener... cleaning up previous if it exists..
INFO[0010] compiling new instance listener
ERRO[0010] Error creating container                      err=Cannot connect to the Docker daemon. Is the docker daemon running on this host?
ERRO[0010] running daemon failed: [cmd/daemon.go:74] daemon failed to initialize: {[daemon/daemon.go:80] initializing virtualbox provider: {[virtualbox/virtualbox_provider.go:36] deploing virtualbox instance listener: {[virtualbox/deploy_instance_listener.go:37] compiling instance listener source to unikernel: {Cannot connect to the Docker daemon. Is the docker daemon running on this host?}}}}
$> docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

hi @matt2909, I've created and pushed a hotfix that i believe will solve this problem. can you try checking out branch hotfix-26-docker and running make binary to re-compile unik with the hotfix?
cd <unik directory>
git pull
git checkout hotfix-26-docker
make binary
_build/unik daemon --debug

update: i have pushed this hotfix to master

Ok I've got the example http daemon example working. Seems like on Docker for mac, you need to build a virtualbox machine using
$> docker-machine -create -d virtualbox default

and ensuring your environment is set to point at default by adding
eval $(docker-machine env default)

before running make for the unik project.


Covert String formatting from % to .format

Description
This unifies the Python string format methods to the .format method
which is what we want going forward. The "%..." % obj style should no
longer be present in any of our files. Versioneer files remain untouched.
Fixed a few missing formats
Fixed a misused json.dump command
Fixed a few unresolved references which were only reachable in case of failures
Status

[x] Ready to go

This pull request introduces 1 alert when merging 86697897ed423521129170c9951279d21b3aeb4b into 2185a5443f5568b073db3b27c6b90405b1ee1005 - view on LGTM.com
new alerts:

1 for Unused argument in a formatting call

Comment posted by LGTM.com

Codecov Report

Merging #37 into master will decrease coverage by 0.03%.
The diff coverage is 23.07%.


Display the friendly names on claims page (Closes: #2256)

Description
This pr adds friendly names on claims page and migration warning tooltip. Closes https://github.com/balancer-labs/frontend-v2/issues/2256
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

@pkattera I wonder if you approve adding warning tooltip on pools table in claims page


[CIVP-10187] Dynamically decide between polling and notifications

Now that the pubnub.SubscribableResult is available, create a function result.make_platform_future which instantiates either a new SubscribableResult (if pubnub is available and the user has access to the notifications endpoint) or a PollableResult object. We should prefer to use the SubscribableResult, since notifications are much faster (we don't have to wait for polling) and greatly decrease API traffic.

You can ignore those Travis errors. It looks like an issue caused by generate_classes lru cache persisting across tests when some Pubnub tests require a swagger spec with channels. I'll create a separate PR that fixes that.

#35 is a much better approach to this.


Switch between Terminals by keyboard shortcut

I always use 3 terminals and switch between them most of the time, how can I switch by keyboard shortcut?
In macOS terminal we can do it by [shift]+[command]+[left arrow]/[right arrow]

Try adding this to your keybindings.json file:
{ "key": "cmd+shift+right",     "command": "workbench.action.terminal.focusNext" },
{ "key": "cmd+shift+left",     "command": "workbench.action.terminal.focusPrevious" }

Try adding this to your keybindings.json file:
{ "key": "cmd+shift+right",     "command": "workbench.action.terminal.focusNext" },
{ "key": "cmd+shift+left",     "command": "workbench.action.terminal.focusPrevious" }

@Tyriar thanks 🙏

@Tyriar thanks 🙏


Switch to Java's UncheckedIOException.

This is failing because we currently have
<excludes>
<EMAIL_ADDRESS></excludes>

configured in japicmp. This allows the previously deprecated methods (between 1.16.1 and removed in 1.16.2) to not blow up. But I can't see a way to configure japicmp to allow this to be marked deprecated while that exclude is on -- it makes the class invisible and therefore looks like a removal. So I think we need to pick it up after the next release.
Also I think we should change the signature to
public class UncheckedIOException extends java.io.UncheckedIOException

(and throw the extended not base version) for a release. That way if anyone is explicitly catching this exception, the current code will still work and they have an opportunity to migrate.


Mouseover Event Preview

Request type

[ ] New documentation
[x] Correction or update

Details

The mouseover event example only shows a white box.

Fixed. Thanks for reporting!


CMakeLists.txt: Do not require C++ by default

By default, the project() CMake command defaults to C and C++. 1 Therefore, CMake might perform tests for both C and C++ compilers as part of the configuration phase.
However, this has the consequence of the configuration phase to fail if the system does not have a C++ toolchain installed, even if C++ is not really used by the top-level project under the default settings.
Some configurations might still require a C++ toolchain, so enable_language is selectively called under such circumstances.

how have you tested this? on which platform?
our CI coverage here is weak. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2686

Using the same reasoning, I suppose core/iwasm/compilation/iwasm_compl.cmake requires a similar modification.

Using the same reasoning, I suppose core/iwasm/compilation/iwasm_compl.cmake requires a similar modification.

good point.
@midokura-xavi92 please test WAMR_BUILD_JIT=1 as well.

Using the same reasoning, I suppose core/iwasm/compilation/iwasm_compl.cmake requires a similar modification.

Not really: all files that include(${IWASM_DIR}/compilation/iwasm_compl.cmake) always do so from their own CMakeLists.txt (e.g.: wamr-compiler/CMakeLists.txt), and also from their own project, whose languages always default to C CXX, according to the documentation:

it's included via runtime_lib.cmake.
top-level cmake -> runtime_lib.cmake -> iwasm_compl.cmake

@midokura-xavi92 please test WAMR_BUILD_JIT=1 as well.

That would require me to build the wamr-compiler from source:

you don't need to build wamr-compiler. just llvm.
if you are lucky, you might be able to use the existing llvm binary by setting LLVM_DIR.

$ cmake -B build -DCMAKE_EXPORT_COMPILE_COMMANDS=1 -DCMAKE_BUILD_TYPE=Debug
CMake Error at build-scripts/config_common.cmake:106 (message):
  Cannot find LLVM dir: /home/xavier/wasm-micro-runtime/core/deps/llvm/build
Call Stack (most recent call first):
  build-scripts/runtime_lib.cmake:169 (include)
  CMakeLists.txt:122 (include)

I am not against it, but building LLVM and friends from source will take some time. I will let you know once this is done, but in the meantime please take the rationale above into consideration.

as our CI in this area is weak, manual testing is a must.
alternatively you can improve our CI coverage. it's probably a better idea anyway. :-)


Copying Dashboards

It would be nice if it was possible to copy/duplicate dashboards between/to other teams.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d3d9f6cf-89b6-a0e3-0a37-f23446ede457
Version Independent ID: 988af21a-7ee0-66b4-0fac-07360b8be17d
Content: Add, rename, delete, and manage team dashboards - Azure DevOps
Content Source: docs/report/dashboards/dashboards.md
Product: devops
Technology: devops-analytics
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@powerdude  Thank you for the feedback.
Unfortunately changes here are for documentation only.
Please use the Azure Dev Ops community where your request can be voted on and responded to by the product team.

Closing this issue now, please comment below if there are any questions.


WIP: Converting security agent start command to fx, and associated cleanup

What does this PR do?

Remove original way of merging config files for the Security Agent (deleted MergeConfigurationFiles)
Created constructor for Security Agent Config Params
Added simple subcommand tests
Renamed package aliases to prep for using the config and log components (e.g. complog -> log)
Changed ConfPathArray field in GlobalParams struct to ConfigFilePaths
Converted start commands to use log and config components when (easily) possible. Still some todos here, like with the Runtime subcommand.
Moved subcommands around to be consistent with internal fx documentation.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Current dependencies on/for this PR:

main

PR #14833

PR #14814   👈

This comment was auto-generated by Graphite.


Move s3 boto import to avoid un-needed warnings

Rather than warning, we can just fail if we try to actually use an S3
target without boto.  This allows for use cases where s3 module is
imported but an S3 target is not actually used.
Fixes #1485

Failure is on visualiser.visualiser_test.TestVisualiser from TOXENV=visualizer; assuming it is an unrelated failure.

Thanks!! :)


Handling ASC

I was trying to handle abstract simplicial complexes. Reading the data is straightforward since we have the ASC property, so I know to account for subset closure and generate all necessary sub-hyperedges. For dumping to file, though, I’m unsure—do you typically write out every hyperedge or just the maximal ones?

Hi @FraLotito --- in XGI we write maximal faces plus all subfaces with attributes. Here's the module in XGI.

Thanks @nwlandry I will follow the same logic


Fix build scripts for MKL

@vrv, yes, that's a TODO item. But it's part of the build system config, not part of the code.


Dashboards fail to pass Splunk Clouds App Inspect

When trying to upload a custom app to Splunk Cloud, the dashaboards fail to pass App Inspect
The following Error is found and will stop the user from installing
Change the version attribute in the root node of your Simple XML dashboard default/data/ui/views/runtime_manager__rtf__sandbox.xml to <form version=1.1>. Earlier dashboard versions introduce security vulnerabilities into your apps and are not permitted in Splunk Cloud File: default/data/ui/views/runtime_manager__rtf__sandbox.xml

Hi @jrehm-mmm
I have been unable to replicate this. I have just created the dashboards in Splunk Cloud by directly copying the provided xml into the dashboard source and did not receive any such errors. I am going to mark the issue as closed.
If you want to provide additional information on how to replicate please feel free to re-open.
Thanks and regards,
Richard

The way you are testing will not fail. The failure will come if you try to package up the app and try to install it on Splunk Cloud.  It will fail app inspect.
If you expect that users are going to manually create the dashboards then it's not a concern.

Thanks @jrehm-mmm for your quick reply, and for providing that extra detail.
Yes, the dashboards are provided as standalone examples, not as a package-able app so the expectation is that users will install these manually. The dashboards are intended to be examples only, with the expectation that users will refine, extend and customise these to meet their specific requirements.
I will mark this item as closed, and thanks again for your feedback.
Richard


Aws bindings improvements 3

Sorry @iancooper I raised the other PR against the main branch on the original repo rather than against your own feature branch 🤦♀ this one should be correct.

@dpwdec Merged


CLI deployment doesn't provide dynamic map

Type of issue

[X] Bug
[ ] New feature
[ ] Enhancement

Description
I've tried deploying solution from CLI and didn't get a dynamic map. Over the same subscription using staging.azureiotsuite.com it works
...
Steps to reproduce

[First step]
[Second step]
[and so on...]

Expected behavior
...
Current behavior <!-- The actual behavior observed --
...
Known workarounds
...
Possible solution
...
Context and Environment

Operating System: ...
GitHub branch/tag: ...

Screenshot

I see a dynamic map in my subscription:

The only way you will see a dynamic map; if the subscription has less than 2 free Bingmap resources available. Closing this as by design.


When using initialValues inputs don't have any value

when i am initialValues the form i can see that the input field showing the right value
but when i am trying to submit the form its seems that the input filed dont have any value
and the validation is working and i am getting an error
what can be the problem ?
thanks !
Form Component :
import React, {Component} from 'react';
import {Field, reduxForm} from 'redux-form';
import {validate,} from '../../utilites/utilites';
class Profile extends Component {

  constructor() {
        super();
        this.state = {
            edit: true
        }
    }

  render(){
   const {handleSubmit,pristine, reset, submitting } = this.props;
   return(
             <form noValidate onSubmit={handleSubmit(this.submitEditProfile)}>
              <Field
                                name="first_name"
                                component={edit ? InputField : LabelField}
                                type="text"
                                placeholder={this.props.profileDetails.first_name}
                            />

                  <Button disabled={pristine || submitting} type="submit" raised color="primary">
                    update
                  </Button>
                  <Button disabled={pristine || submitting} onClick={reset} raised color="primary">
                  reset
                  </Button>

            </form>
     )
  }
}
const mapStatToProps = ({ProfileReducer}) => {
    return {...ProfileReducer,initialValues:ProfileReducer.profileDetails}
};
Profile = connect(mapStatToProps, actions)(Profile);
Profile = reduxForm({form: 'ProfileForm', validate,enableReinitialize:true})(Profile);

InputField Component :
import React, {Component} from 'react';

   class InputField extends Component {

        render() {
           const {input, disabled, label, placeholder, type, meta: {touched, error, warning}} =
            this.props;
                return (

                   {error ?
Error
 : null}
                   <input {...input}/>

        )
    }

}
export default InputField

Fixed : its seems that when rendering the component on the first time
the initialValues not working
need to do it in the componentWillMount function with this.props.initialize()
Just added to the Form Component
componentWillMount (){
this.props.initialize(this.props.profileDetails)
}


Package dependency on adal-node (being deprecated) needs to be updated.

Package Version: 3.0.3

[x] nodejs

nodejs version: 12.5
os name/version: Linux/Ubuntu

[ ] browser

name/version: ____
Describe the bug
ms-rest-nodeauth has a dependency on adal-node, which is being deprecated (and has dependencies on deprecated packages).  See issue: https://github.com/AzureAD/azure-activedirectory-library-for-nodejs/issues/229#issuecomment-590518066.  Issue response suggests moving to msal (https://github.com/AzureAD/microsoft-authentication-library-for-js).

To Reproduce
Steps to reproduce the behavior:
See dependency in package.json files:

adal-node in ms-rest-nodeauth : https://github.com/Azure/ms-rest-nodeauth/blob/master/package.json
see request package dependency in adal-node: https://github.com/AzureAD/azure-activedirectory-library-for-nodejs/blob/dev/package.json
See request deprecation information: https://github.com/request/request/issues/3142

Expected behavior
The package does not have deprecated dependencies.

Please use node-fetch to fix this deprecation that exists since March 2019.

As mentioned in this comment for adal-node: https://github.com/AzureAD/azure-activedirectory-library-for-nodejs/issues/229#issuecomment-590518066
They won't be updating their library and are recommending to switch over to msal js. Should the fix be to replace adal-node with this new library?

Hi all, ms-rest-nodeauth is currently in "maintenance mode" meaning that we won't be making any major investments like rewriting it to support new/different dependency libraries, etc.
The new @azure/identity library does use msal.js and node-fetch and also provides a much more convenient interface to AAD v2.  That said, not all Azure libraries support it yet (especially many of the @azure/arm-* libraries).  We will be gradually updating all of those libraries to provide support over the coming months.


How can I write unit test in my own form-ui-library？

Question
I create my own formly library based on @ngx-formly/core and ng-zorro-antd, and now I want to write its unit test.
I refer to
https://github.com/ngx-formly/ngx-formly/blob/92d4cfeffac36a0ee33dc6d9f9ee87554606ec17/src/bootstrap/src/lib/types/select.spec.ts
and
https://github.com/ngx-formly/ngx-formly/blob/f5625ea31405c1e432b155a4c72ed8302ef2c79c/src/material/select/src/select.spec.ts
but these two files pass unit test by testing the doms whether has specific dom, and my form components class in my formly library has their method.
so I want to test these method in form components, How can I do to solve this?
or how can I get the instance of form component in unit test?

you can get the component instance using query fn:
fixture.debugElement.query(By.css('formly-field-input')).componentInstance

We've improved our testing in the master branch by introducing createFormlyFieldComponent helper (it'll be part of v6).
for ng-zorro-antd we've made an initial work which you may check:

Source code: https://github.com/ngx-formly/ngx-formly/tree/master/src/ui/ng-zorro-antd
Demo: https://master.formly.dev/ui/ng-zorro-antd

Note: published an early version 0.0.1 for @ngx-formly/ng-zorro-antd which you can use with v5, a stable version is expected in formly@v6.
Happy coding!

I want to use import { createFormlyFieldComponent } from '@ngx-formly/core/testing';
But it is still impossible to import createFormlyFieldComponent . When will it be available?

When will it be available?

yes but in V6 (we'll release an alpha version soon)

you can copy the code from src/core/testing/src/component-factory.ts as helper in your project:

I did that. But I had to adapted to this:
useFactory: (builder: FormlyFormBuilder) => () => {
  builder.buildForm(new FormGroup({}), [field], model, options);
  return of(null);
},

Because function build is not available...

you can also use this library：https://github.com/zzhimin/ngx-ng-zorro-formly


VM check_message is confusing Zero and EmptyInt

Describe the bug

In Lotus, when they do CheckMessage, they check if Value and GasPrice are empty ints, not 0 as we are doing here.
It is most certainly the case that it is possible to send messages with Value = 0 (example here.
So I wonder if we can skip that check? I'm not entirely sure what EmptyInt is in Lotus... Guessing its similar to some nil maybe?

Ah yeah it is just a nil check in the go implementation. I missed fixing that in my pass because I didn't look into what that type was. Will update now, thanks :)


(Issue #58) Do not hard code java path in backup class.

Since the javahome parameter is required. It makes sense to use the
path ${javahome}/bin/java.

Good idea.
Concerning tests, I'd prefer two see this covered more distinctly:

the existing specs should just make sure the default values are applied (from params)
a new test should be added that only concerns itself with the java path that ends up being used, given the parameter value

:+1:

The javahome is actually a required parameter. It used to be set
$javahome,

But I think because that effects the puppet module scoring, I made it
$javahome = undef,

I think I should perhaps make it
$javahome = 'UNSET'

and fail if it is it equals 'UNSET'.
Alternatively add support for the puppetlabs-java module and enable that by default, with an option to turn it off.
I generally find Java pretty hard to manage, Each of my developers have there own opinions what Java version to install and whether it should be from the OS package management tools or directly from oracle. With regards to stash, I kind of feel I want them to explicitly set this and not automatically decide for them.
Atlassians tools generally tend to prefer Oracle JDK/JRE over Open JDK/JRE. To enable this for RHEL, you need to get into managing subscriptions to RHEL channels and so on. I am also not sure how good the supprot is for Oracle java using the https://forge.puppetlabs.com/puppetlabs/java#limitations
To make things even worse as per Atlassian

Support for Java 7 is deprecated, and will be removed in Stash 4.0. Which should released soon.

To me Java is such huge animal it should be managed by the user with a stash role/profile and they should explicitly set what they want to use when calling the module.
Let me know your thoughts.

On 03/25/2015 11:49 AM, Merritt Krakowitzer wrote:

I think I should perhaps make it
$javahome = 'UNSET'
and fail if it is it equals 'UNSET'.

If you feel compelled to perform such antics to please the arcane
mechanisms that power the Forge, it might be those that need fixing or
adjusting. /cc @ryancoleman

Alternatively add support for the puppetlabs-java module and enable
that by default, with an option to turn it off.

That would make the module more self-contained, yes. Good UX.
On the other hand, if we pull this specific Java module in as a
dependency, some users might feel patronized, or will outright have to
forego this module if they cannot have puppetlabs-java in their
environment. I myself am rather sensitive about such things, bordering
on the irrational.

Almost certainly you did not mean to cc @ryancoleman on this. No worries, but you may want to figure out who to cc.

Right. Sorry! I was thinking of @ryanycoleman.

Funny. @ryancoleman is my cousin. /me waves.

@ffrank I feel like I'm missing a piece of context. How's the Forge forcing that behavior?
I agree with you regarding keeping the module discrete and expecting someone to provide their own java. To me, it's a trade-off between simplicity for someone who just wants to puppet module install and puppet agent -t vs flexibility for those who want to choose which content satisfies the dependencies.
For something as big as Atlasssian Stash, I think it's safe to expect someone to do the extra work to satisfy the dependency on java. Bonus points for including in the README docs on how to satisfy the dependency with puppetlabs-java.

Oops, right - the context seems to be gone from this thread.
Here is what @mkrakowitzer had originally written (sorry Merritt if you wanted this gone ;-)

The javahome is actually a required parameter. It used to be set
$javahome,
But I think because that effects the puppet module scoring, I made it
$javahome = undef,
I think I should perhaps make it

I see how a module would score lower for having loads of required parameters. But if this becomes an incentive to build horrors around artificial defaults and calls to the fail function, then overall quality may suffer.

@ffrank no problem, after rereading your initial comment I felt I missed the mark with my response re this PR.
I have tried to address your concerns with an updated PR.
I removed a lot of duplication in the tests and moved them to its own file, all with default params. I left the tests as is that test for the download.
I added a new test that only concerns itself with the java path that ends up being used, given the parameter value.

i think puppetlabs-java's main problem, and the reason we don't use it in complex environments is: https://github.com/puppetlabs/puppetlabs-java/pull/110

@igalic I don’t want to be merging my own commits? Would you be happy to merge this assuming you feel I have addressed everyones comments? and there are no other points that need to be addressed?

absolutely!


Lift Send requirement in wasm builds

What problem does this solve or what need does it fill?
Right now there is a requirement for a lot of things to be Send even in single-threaded targets like wasm: e.g Plugin and Resource. Would be great to lift that in wasm targets.
What solution would you like?
Do not require things to be Send
What alternative(s) have you considered?

Additional context
This blocks being able to use bevy_tokio_tasks for more stuff on wasm: see https://github.com/EkardNT/bevy-tokio-tasks/issues/18#issuecomment-1636076278

Wasm is not single-threaded. You can create multi-threaded wasm applications that run in browsers today.
Afaik bevy does not currently make use of this but keeping it as a future option without a breaking change is the way I personally would go.

Please see #4078 for more information. We eventually want to support full use of Web Workers in all WASM targets, but there are fundamental limitations that we may need to find a workaround for. Knowing this, conditionally lifting Send constraints, where relevant, seems shortsighted.

With the work in #12205, it's pretty apparent that any !Send component or resource on wasm can be wrapped in send_wrapper or bevy_utils::SyncCell to achieve Send + Sync required for Resources or Components. If the actual environment is truly single threaded, both should be a non-issue to deal with. Closing this out for now.


Add the possibility to remember the account password for the cutecoin session

The user should be able to ask cutecoin to remember the password

Added in https://github.com/ucoin-io/cutecoin/commit/cf7d3423ccf02f1c703c11b6daf5bff5086e45ab

Added in https://github.com/ucoin-io/cutecoin/commit/cf7d3423ccf02f1c703c11b6daf5bff5086e45ab


Update link verifier to use Python 3.7 and urllib3 v2

Description
This is done to resolve two dependabot alerts.
https://github.com/aws/aws-iot-device-sdk-embedded-C/security/dependabot/9
https://github.com/aws/aws-iot-device-sdk-embedded-C/security/dependabot/8
UrlLib3 v2 requires python 3.7 or later per their migration guide. I went with the oldest python version to reduce backwards incompatibility.
Testing

Cloned repository
Made modifications to action + requirements.txt
pip install -r requirements.txt

Ran two tests....
verify-links.py -F fileTests/goodFiles/fileWithLowercasemdIntheName.md

No error as expected
verify-links.py -F fileTests/badFiles/fileWithLowercasemdIntheNameAndABrokenLink.md
FILE: fileTests/badFiles/fileWithLowercasemdIntheNameAndABrokenLink.md
  404	https://github.com/FreeRTOS/A-Repo-That-Wins-You-The-Lottery
1 broken link

Errors as expected

From what I can tell the check failures are due to the source repositories and not the changes here.

The action currently pulls python version 3.11 link
Successfully setup CPython (3.11.6)
##[add-matcher]/home/runner/work/_actions/actions/setup-python/v3/.github/python.json

And pulls urlLib3-2.0.7 link
   Collecting urllib3 (from -r /home/runner/work/_actions/FreeRTOS/CI-CD-Github-Actions/main/link-verifier/requirements.txt (line 9))
    Downloading urllib3-2.0.7-py3-none-any.whl.metadata (6.6 kB)
  Collecting charset-normalizer<4,>=2 (from requests==2.31.0->-r /home/runner/work/_actions/FreeRTOS/CI-CD-Github-Actions/main/link-verifier/requirements.txt (line 6))
    Downloading charset_normalizer-3.3.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
    ```

If there's a way to make setup python use a minimal version I'm fine with adding that change.
But this becomes a "six of one, half a dozen of another issue"

We can either ignore the dependabot alerts, that are asking us to use older versions of libraries, and then deal with the Github warnings and deprecation warnings/errors
We can ignore the Github warnings and deprecation warnings - and then deal with actual errors when the versions of the libraries are dropped

Option 1 makes our CI-CD work more closely to what most people will have locally - whatever happens to be sudo apt installed or pip installed
I think this creates a smoother experience compared to tying our CI-CD to a specific version of a tool. Where it then becomes "You need to go and grab this specific version of  and then specific version of ."

We can either ignore the dependabot alerts, that are asking us to use older versions of libraries, and then deal with the Github warnings and deprecation warnings/errors
We can ignore the Github warnings and deprecation warnings - and then deal with actual errors when the versions of the libraries are dropped

Option 1 makes our CI-CD work more closely to what most people will have locally - whatever happens to be sudo apt installed or pip installed

While I mostly agree, I do disagree on some points. We're providing a requirements.txt file with the link verifier script. It's very common to install dependencies using this file + pip. I do not think it's asking much for developers working with our link verifier to use the dependencies we support. Not to mention, we'll just be specifying a range. I think it's reasonable to not support older versions of Python (or at least claim to not support them) if doing so opens us up to vulnerabilities. Many of these vulnerabilities simply won't exist when run locally so a developer can tinker with whatever versions they want.

I think this creates a smoother experience compared to tying our CI-CD to a specific version of a tool. Where it then becomes "You need to go and grab this specific version of and then specific version of ."

Now I do agree with this which is why I'm a fan of setting a range with a reasonably low minimum version.

It's very common to install dependencies using this file + pip. I do not think it's asking much for developers working with our link verifier to use the dependencies we support. Not to mention, we'll just be specifying a range.

Yeah by just specifying a minimum version I'm more than happy to merge this in


Generic for overlapping types

This PR resolves #370.

Many thanks ... much appreciated! Merging :-)

:+1:


Update Swift 4.0 compatibility support for IBAnimatable project.

Pull Request Description
In this PR, we have updated the Swift 4.0 compatibility support for IBAnimatable project. And we have run ./project_precommit_check IBAnimatable --earliest-compatible-swift-version 4.0 with Xcode 9.0.1. And the result looks as below:
PASS: IBAnimatable, 4.0, b565f2, IBAnimatable, generic/platform=iOS
PASS: IBAnimatable, 4.0, b565f2, IBAnimatableApp, generic/platform=iOS
========================================
Action Summary:
     Passed: 2
     Failed: 0
    XFailed: 0
    UPassed: 0
      Total: 2
========================================
Repository Summary:
      Total: 1
========================================
Result: PASS
========================================
--- IBAnimatable checked successfully against Swift 4.0 ---

Please let me know if there are any issues, thanks.
Acceptance Criteria
To be accepted into the Swift source compatibility test suite, a project must:

[x] be an Xcode or swift package manager project
[x] support building on either Linux or macOS
[x] target Linux, macOS, or iOS/tvOS/watchOS device
[x] be contained in a publicly accessible git repository
[x] maintain a project branch that builds against Swift 3.0 and 4.0 compatibility mode
and passes any unit tests
[x] have maintainers who will commit to resolve issues in a timely manner
[x] be compatible with the latest GM/Beta versions of Xcode and swiftpm
[x] add value not already included in the suite
[x] be licensed with one of the following permissive licenses:

BSD
MIT
Apache License, version 2.0
Eclipse Public License
Mozilla Public License (MPL) 1.1
MPL 2.0
CDDL

[x] pass ./project_precommit_check script run

Ensure project meets all listed requirements before submitting a pull request.

@swift-ci test

@JakeLin I'm seeing: xcodebuild: error: '/Users/buildnode/jenkins/workspace-private/swift-PR-source-compat-suite-test-macOS/project_cache/IBAnimatable/IBAnimatable.xcworkspace' does not exist.

It appears that the 3.0 hash doesn't contain the specified workspace.

@lancep I didn't create the configuration for 3.0, it was xcproject instead of xcworkspace. Can I specify it differently for different version?

The current version of the projects.json list doesn't support specifying different actions per version.

@lplarson can we drop version 3 support for IBAnimatable? Otherwise, we don't know how to support both for now.

Let's try this.

@swift-ci test

Thanks @lplarson let's wait for the CI

@swift-ci test

Thanks!

@lplarson thanks for helping me fix it.


[stable/mongodb-replicaset] Use storageClassName for mongodb-replicaset.

Fixed mongodb-replicaset for #1869
/cc @prydonius

/retest

Tests run successfully on my GKE cluster with and without specifying a storage class.


docker login for all image builds in ci

This is a step toward addressing DockerHub rate limiting. Our most frequent pulls are due to the FROM directive in Dockerfiles that we build in our jobs, so logging in before image builds, the way we already do before image pushes is one of the best measures we can take against bumping into the rate limit.
We may still need to do more, but this should be a significant improvement.

@vdice approved this in https://github.com/brigadecore/brigade/pull/1798

This shouldn't be merged yet. There are missing checks for some reason. Investigating...

/brig run

Checks are fixed.


Unicorn rgb332 fix

Enables support for PEN_RGB332 on the Galactic Unicorn; this is necessary to support the sprite functions of PicoGraphics, which only work with that pen.

Looks good to me! I wonder what other pen types are worth supporting.
Mind rebasing to squash those two commits into one and drop the erroneous change to synth.volume?
Thank you!

Oof; I think my attempts to make github make things better have made them much, much worse.
Would you rather I re-opened this PR with a less broken branch? :-)

(closing this, as I've toasted the branch so badly - replacment PR https://github.com/pimoroni/pimoroni-pico/pull/659 opened)


Update deps and inferno layout to match React

I changed Inferno layout to match React layout and updated all dependencies except PReact which didn't work anymore after update. Inferno should perform better now after some optimizations done in v3.5.4 + 3.6.0

Is this going to be merged?


[Technical] Tidied up test build utilities

No product changes
This PR is mainly for info. The helper methods that create MSBuild projects on the fly for testing are numerous, untidy, and reasonably complicated. This commit is a minor cleanup that attempts to organise the methods better and remove some of the clutter.
I've deleted some redundant methods, made a couple of methods private that were public, and grouped methods by purpose.

LGTM


Update run url in readme

@emilymcafee this just wasted most of my afternoon -- I had copied the run URL from the readme file, but was trying to set $AUTOSCALING_GROUP_NAME, which was not a thing until v0.1.0.
>_<

Please accept my most sincerest apologies-est. 🍻


hangs when trying to change RAR preferences

From<EMAIL_ADDRESS>on June 11, 2013 01:57:42
What steps will reproduce the problem? 1. Open ComicTagger
2. Go to Preferences
3. Click '...' button next to either RAR or UnRAR
(4. File Dialog opens, click any folder in it) What is the expected output? What do you see instead? Expected: file dialog to choose a program (usually doesn't get this far, have once had it get to this window but still was unable to navigate to the unrar program)
Actual: Hangs. Crashes when closing the preferences window. What version of the product are you using? On what operating system? Mac OS X 10.8.3
ComicTagger 1.1.9-beta Please provide any additional information below.
Original issue: http://code.google.com/p/comictagger/issues/detail?id=25

From<EMAIL_ADDRESS>on July 08, 2013 18:17:31
OK, I can't seem to re-create this problem.  It may be because I have an older Mac,  running 10.6.8, which, unfortunately, is as high as I can upgrade on this 32-bit machine.
I will ask around about this problem, but in the meantime, you can manually edit the settings file as a workaround.
Just edit the file "/Users/tony/.ComicTagger/settings" and make the proper lines look something like this:
rar_exe_path = /usr/local/bin/rar
Status: Accepted

From<EMAIL_ADDRESS>on March 24, 2014 08:15:06
No repsonse in a while, and no more people with issues for this common procedure, so going to assume it's a one-off issue.  Closing for now, but feel free to re-open
Status: WontFix


Force HDR

When launching on desktop. it forces HDR off on monitor. Not that the game has HDR, but I keep HDR mode of monitor for higher overall brightness (in nits) of screen. Is there any way to disable forced HDR off?

idk, launch game in windowed mode

do you mean FrameInterval option?

do you mean FrameInterval option?

yes. :)

It is recommended to always set 0.
This makes FPS unlimited and allows to bypass game's frame limiter, which causes FPS drops on modern Windows


Should we use anoyher name for MviPresenter?

Since MviPresenter is not a "traditional" presenter, we should consider use another name. Maybe something like MviBinder or MviCoordinator.
On the other hand MviPresenter does make sense since it can be used with traditional view oresenting calls like view.showLoading() instead of just one single view.render(model) method (Mosby doesn't force you to choose one or the other approach) .
Also we may have a PresentationModel which holds some View only properties like if an item in a list is selected or not, which is another good reason to name it MviPresenter.
What are your thoughts?

We will stick with the name MviPresenter

I also agree with this MviPresenter. Coordinator would be a little confused term if someone uses Square's coordinators.


No dissociation method detected

Im trying to process the following file 09apr2014_HESC_SCX8to12_RP4.raw (ftp://massive.ucsd.edu/MSV000086944/raw/raw/09apr2014_HESC_SCX8to12_RP4.raw) and when I convert it to mzML is not exporting the dissociation method.

Hi @ypriverol,
I have processed the file with versions 1.4.0 and 1.4.2 both seem to produce a valid mzML file, i.e. every MS2 scan has an <activation> element and the fragmentation type is set to HCD - <cvParam cvRef="MS" accession="MS:1000422" value="" name="beam-type collision-induced dissociation" />
Did I understand your problem correctly?

Closed for now, please, feel free to reopen if necessary


Bump minimum required pry version to 0.13.0

This is nice for folks using ruby 2.7, as pry 0.13.0 resolves a
deprecation warning introduced in Ruby 2.7.
Ex warning:
<main>: warning: __FILE__ in eval may not return location in binding; use Binding#source_location instead
/Users/mykecameron/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/pry-0.12.2/lib/pry/commands/whereami.rb:40: warning: in `eval'
<main>: warning: __LINE__ in eval may not return location in binding; use Binding#source_location instead
/Users/mykecameron/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/pry-0.12.2/lib/pry/commands/whereami.rb:41: warning: in `eval'

see: https://github.com/pry/pry/issues/2097#issuecomment-602029140

Why hasn't this been merged?

@vassyz good question! It seems like this project may not be maintained.

It's not maintained by me anymore. @banister and @rf- have access to the repo though. If they both also moved on, I can grant access to whoever is willing to maintain it. Maybe there are more active forks though, I don't know. If that's the case, let me know and I put a link in the readme.

@rweng I checked and there aren't any other active forks. All of the recent modified ones have the same commit as this PR.

I merge this now since it's a small change. However, if you are interested in maintaining this project let me know :)

@rweng Thanks for the merge. Any chance you could publish a new release? As for maintaining it, it would be good to ask in the Readme if anyone wants to do it. I don't think I have the time to do it, although this gem probably only needs keeping up with dependencies and new Ruby versions.

@vassyz ay I'm sorry but I didn't maintain this project for a long time. Don't know what happened to the other maintainers. I've not been working with Ruby for a couple of years. So I'd need to setup everything and run the tests and look at the recent changes to feel comfortable to release a new official version. Providing git: still works I assume? But I'll add an info to the readme.


Return User Info from Login Endpoint

Overview
Returns user details from the login endpoint. Both when logging in a new user, and when fetching an already logged in user, we return details about the user, which include their email, Role, and list of Utilities.
Adds a Utility and State serializer along the way. Updates front-end redux arrangement to consume the new user object for login state management. Also uses the user's list of utilities to correctly render the Nav Bar.
Closes #123
Demo

Testing Instructions

Checkout this branch and server
Go to http://localhost:4545/ and log in as a contributor

[ ] Ensure you are logged in correctly

Go to http://localhost:4545/draw and http://localhost:4545/submissions

[ ] Ensure the user's utility is shown correctly in the nav bar

Log out, and log back in

[ ] Ensure logging out works correctly
[ ] Ensure logging in returns you to the previous page instead of taking you to Welcome

Checklist

[ ] fixup! commits have been squashed
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] README.md updated if necessary to reflect the changes
[ ] CI passes after rebase

Taking a look now.

For some reason the linter integration with my VSCode isn't working, leading to all the linting errors. 9552480 should be the last fix that takes care of it.

One thing quickly, since I know you're online. With this PR we now lose this ability to keep the user logged in after refresh, i.e. when we lose redux state. I don't know if our usual approach is to persist the redux state, or to tolerate more API calls, or to just tolerate logging the user out.

Nice catch! Had missed saving the user state in PrivateRoute. Fixed in 33930fe

Thanks for reviewing!


Provide events for installer

It would be nice to receive events like with Squirrel to react to certain - who would have guessed - events.
Events:

Install
First run
Update
Uninstall (probably not possible everywhere)

Also cool to create a small framework to handle migrations to be run when certain versions are passed during an upgrade.

Rather than using events, I chose to use properties on the Configuration object since Configuration was already in place and let me keep all the logic there rather than adding more logic to SparkleUpdater.
In the latest preview of NetSparkle, you can now use Configuration.IsFirstRun to see whether this is the first time the application has run. If you reload the configuration data by calling Configuration.Reload(), this flag will be false, even in the same run of the software, so...be forewarned if you reload data manually.
You can also now use Configuration.PreviousVersionOfSoftwareRan to see what the user ran last. The same warnings about reloading configuration data apply. This property is "" on the first run of the software.
Something like this should be helpful:
if (SparkleUpdater.Configuration.IsFirstRun)
  // handle first run
else if (!string.IsNullOrWhiteSpace(SparkleUpdater.Configuration.PreviousVersionOfSoftwareRan)
          && SparkleUpdater.Configuration.PreviousVersionOfSoftwareRan != SparkleUpdater.Configuration.InstalledVersion)
   // handle update by figuring out what needs to be updated or shown to the user or whatnot

I don't think we can properly handle Install or Uninstall events at this point since we don't control those events of the software at all.

What do you think about storing the previous version as Version? (Nullable), so you don't have to parse it?

I'm sorry for forgetting to reply.
I would rather let the user parse the string themselves if they need to -- they might be storing the version in formats such as 2.0.0-beta2342 or some other incompatible-with-Version format.

Calling this "done" for 2.0, but am open to further suggestions for 2.1+.

Calling this "done" for 2.0, but am open to further suggestions for 2.1+.

Hi, sorry had no time yet. I am trying to build a full stack prototype for the whole software update path using Avalonia for multiple platforms (Linux and Windows for now), Will look into it.

Hi, sorry had no time yet. I am trying to build a full stack prototype for the whole software update path using Avalonia for multiple platforms (Linux and Windows for now), Will look into it.

Oh, that's fine. I'm just wanting to wrap things up for a 2.0 release right now. There's no rush or pressure on you to do anything more (although contributions are always welcome). :)

Oh, that's fine. I'm just wanting to wrap things up for a 2.0 release right now. There's no rush or pressure on you to do anything more (although contributions are always welcome). :)

Closing this as it's been several years and we even now support versions like 1.2.3-beta1 and such. Please re-open or open a new issue if there are more events that are desired.


[FLINK-31398][sql-gateway] OperationExecutor is no longer set context classloader when executing statement.

What is the purpose of the change
Currently, method OperationExecutor#executeStatement in sql client will wrap currently with sessionContext.getSessionState().resourceManager.getUserClassLoader(). Actually, it's not necessary.
It'll will cause the exception Trying to access closed classloader. Please check if you store xxx after quiting sql client.
The reason is in ShutdownHookManager, it will register a hook after jvm shutdown. In ShutdownHookManager, it will
create Configuration. It will then access Thread.currentThread().getContextClassLoader() which is FlinkUserClassLoader, the FlinkUserClassLoader has been closed before. So, it'll then cause Trying to access closed classloader exception.
Brief change log

OperationExecutor is no longer set context classloader when executing statement.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

Thanks @luoyuxia for the review, I have rebased this pr.


Fix dictionary values indexing for Python 3

Current coverage is 85.74% (diff: 0.00%)

Merging #614 into master will decrease coverage by 0.31%

@@             master       #614   diff @@
==========================================
  Files            27         27
  Lines          3198       3198
  Methods           0          0
  Messages          0          0
  Branches        513        513
==========================================
- Hits           2752       2742    -10
- Misses          308        315     +7
- Partials        138        141     +3

Powered by Codecov. Last update bddcc42...b80e958

Thank you.


Package doesn't compile

Hi :)
There is a couple of compile errors with the lib.

Please provide any more details, Xcode version and iOS target.

In last version other code. I think you should upgrade.

Thank you for the quick response!
This is Xcode 14.3.1. Ah ok so you mean it should work with the new Xcode. That makes sense.
Awesome then 👍


C# syntax coloring bug with top-level statements

Version: 1.55.2 (user setup)
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:35:57.887Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042
Steps to Reproduce:

Write a program using C# 9 top-level statements.
Put else clause's statement on same line as the else.

Both the else and the statement will be colored incorrectly. In this example, you can see else, Console, and the string are all wrong. Put them inside the context of a method and everything colors correctly again.
My 10 year old noticed this while he was learning a little C# this weekend. It made him think his code was wrong.

https://microsoft.github.io/monaco-editor/index.html does not seem to have the same bug, if that's helpful. It's also not present here on GitHub.
using System;

// Bug only seems to occur when using C# 9 top-level statements
// https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-9#top-level-statements
if (true) {
    Console.WriteLine("normal syntax coloring");
}
else Console.WriteLine("buggy syntax coloring");

if (true) Console.WriteLine("normal syntax coloring");
else Console.WriteLine ("buggy syntax coloring");

// It looks correct if it's wrapped in a method
static void Foo()
{
    if (true) {
        Console.WriteLine("normal syntax coloring");
    }
    else Console.WriteLine("buggy syntax coloring");

    if (true) Console.WriteLine("normal syntax coloring");
    else Console.WriteLine ("buggy syntax coloring");
}

Does this issue occur when all extensions are disabled?: Yes

Another example:

Every word on the else if line is colored incorrectly.

@JoeRobich should these sorts of bugs be filed in https://github.com/dotnet/csharp-tmLanguage instead?

Have you tried with C# semantic highlighting enabled? That should use the actual language service (and thus Roslyn) to richly color your document. Unfortunately it defaults to false.
…
"editor.semanticHighlighting.enabled": true,
…

@abock with semantic highlighting enabled, the bug goes away, and behavior is more consistent with Visual Studio. This is why I assume the issue is with the tmLanguage file.

@JoeRobich should these sorts of bugs be filed in https://github.com/dotnet/csharp-tmLanguage instead?

That is the right place.

/extC#

@gjsjohnmurray how is this a C# extension bug if I can reproduce with the C# extension disabled?

@sandyarmstrong sorry, I misunderstood the exchange you had with @JoeRobich
@alexr00 please reopen if appropriate and remove incorrect label.

@sandyarmstrong thanks for filing the issue in https://github.com/dotnet/csharp-tmLanguage/issues/203. I usually pull grammar updates from the upstream repos once per month, so if/when the issue gets fixed it will get pulled into VS Code soon.
To track grammar issues like this I usually link to the upstream issue then close the issue in Microsoft/vscode, so I'll just set the labels on this issue.


[WIP] Allow dynamic filters to propagate via inference

This isn't a good approach because it could deadlock query if table scans are waiting for dynamic filters since inferred dynamic filters can land in build side.