Add dependency support.

Closes #7

Without going into the change itself, which is appreciated, there is the question of this depends.txt file. Where does this come from? Is there any other plugin manager using this format and name? Are there any plugins out there that require dependencies and are using this file?
I had read of a json file that VAM uses with some metadata. And since it's been there for ages, there is a change a few plugins are using it. I always imagined we would use whatever plugins were using already. Otherwise http://xkcd.com/927/ :smile:

Dang, forgot about xkcd/927!
Yes, there are a few plugins that use addon-info.json.
I'll rewrite vundle#scripts#getdeps() to use that format instead.

I read issue #384 and added one more commit to fix it. (Can't push ATM.)

If I'm reading the code right, the dependency names have to be Vundle plugin identifiers, which are incompatible with addon-info.json keys (but in some cases can be translated). I'm very +1 for using the addon-info.json format, but unless/until vim-pi support is added to Vundle, you'd need to translate entries and ignore some of them to avoid forking a "Vundle addon-info.json format".
A bare name in Vundle points to vim-scripts.org, but in addon-info.json it's a vim-pi plugin name. So "L9" fetches the same plugin in both, but many names will exist in one and not the other, or point to one plugin on vim-scripts.org and a different plugin in vim-pi.
Plugins can be specified by github URL in both Vundle and addon-info.json, but the syntax is different. Where in Vundle you would install 'tpope/vim-fugitive', in an addon-info.json file that name is meaningless and you would need to have something like this instead:
"dependencies": {
  "fugitive": {
    "type": "git",
    "url": "git://github.com/tpope/vim-fugitive"
  }
}

So I would recommend in v1 you detect the special case of github paths like this and translate them into Vundle plugin handles, and ignore everything else for now. That would only work for explicit repo details (for names that exist in vim-pi like "fugitive", it's common to omit the repo details to have them looked up in vim-pi), but it's a good start.

@dbarnett: Now I know why this hasn't been done in 4 years. I shall make it so! (probably)

There we go!

As before, it should be trivial to add support for other formats.
Supports any git URL.

If you want, I'll squash the commits, but I am not sure how GitHub will react to a git push -f that overwrites a pull request.

I added some comments to the commits, not just the pull request. I'd also like to see some "rich" addon-info.json files, if anybody has some examples.

Yeah... This isn't going to work without rewriting vim-addon-manager inside of Vundle.

 Why not start with that to get things moving on dependency support?

So, what didn't work?

@jdevera: Adding full dependency support for the addon-info.json format would require rewriting vim-addon-manager inside of Vundle. It would be easier to just use VAM instead at the moment.
@dbarnett: I set up a better pull request at https://github.com/gmarik/Vundle.vim/pull/560, it includes the non-standard depends.txt format (users might make one to simplify things), and git-url-only support for the addon-info.json format.

We should not have an option to make vundle secure, all behaviour should be :)
The fix for s:expand_path in config.vim I'd like to apply separately, I've asked @av3r4ge to create a separate PR.
When we have dependency support it will always be disabled by default. I like the idea of having a global option and then being able to override it per plugin.
I'm against asking anything to the user during installation, the user should speak their intentions with configuration.
I don't want to encourage at all any tricks in the json files. For me, this should be as if vimscript had a proper json parser that was not evalling. If something doesn't look like a straight dep, then we don't consider it.


WIP fix powershell

There is a big amount of time without UI/UX feedback during:

Do you want to install Python
After
2024-11-19T18:47:00.383773100+08:00 - WARN - No ELF ROM directories found in C:\esp\v5.3.1\tools\tools\esp-rom-elfs
2024-11-19T18:47:00.384527+08:00 - WARN - No OpenOCD scripts found in C:\esp\v5.3.1\tools\tools\openocd-esp32
until save configuration dialog appears.

I suggest some User loading or print before to let the user know install is on going and not frozen.
Please confirm and verify with log
eim-cli-log.txt


helm: set hubble-ui securityContext

The image hubble-ui no longer needs run as root user
Special notes for your reviewer:
Do not merge it until new hubble-ui image is released, see corresponding pull request: cilium/hubble-ui#31. Tested on k8s (v1.18) with enforced  restricted PSP.
UPDATE:
Set it as optional to not to break hubble-ui <= 0.5.0 deployments.
Signed-off-by: Alex Szakaly<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[X] For first time contributors, read Submitting a pull request
[X] All code is covered by unit and/or runtime tests where feasible.
[X] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[X] All commits are signed off. See the section Developer’s Certificate of Origin
[X] Provide a title or release-note blurb suitable for the release notes.
[X] Thanks for contributing!

Fixes:
N/A

/cc @gandro  - I don't know what is wrong with the label: 1st: filled release not 2nd: removed section => same result.

Coverage increased (+0.02%) to 37.89% when pulling 4e76557012fa5d471d0ff5266e3d4b7264a99cf8 on alex1989hu:helm/hubble-ui-security-context into e24ab5b85abfebb47bdf7b164d5771fc77fadf83 on cilium:master.

test-me-please

test-me-please

retest-net-next


Build Failure - iOS

Experiencing the following error when attempting to build...
** BUILD FAILED **

The following commands produced analyzer issues:

    Analyze /Users/me/nelsonApp/node_modules/react-native/ReactCommon/yoga/yoga/YGNodeList.c normal x86_64
    Analyze /Users/me/nelsonApp/node_modules/react-native/ReactCommon/yoga/yoga/Yoga.c normal x86_64
(2 commands with analyzer issues)

The following build commands failed:
    PhaseScriptExecution Install\ Third\ Party /Users/me/nelsonApp/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/nelsonApp.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/nelsonApp.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Any ideas?

https://github.com/GeekyAnts/NativeBase/blob/master/ISSUE_TEMPLATE.txt


Change to webDavV2 + cleanup

fixes https://github.com/owncloud/owncloud-sdk/issues/958

Please do not merge before tomorrow, i wonder why the tests still pass even if we nearly changed all routes.
cc.: @individual-it, can you give us a short onboarding for pact tomorrow?

i wonder why the tests still pass even if we nearly changed all routes.

Because we also adjusted the tests 😄  Basically all /remote.php/webdav/... -> /remote.php/dav/files/${testUser}/...

nice, thanks for bringing light into the dark :) so lets see what next test run says

ci fails now, alpha release postponed to tomorrow

It fails because you've updated pact to 10.0.0-beta.54. We cannot use that version (yet at least), see https://github.com/owncloud/owncloud-sdk/pull/961#issuecomment-1021064665.

(after rebase on master which now is on the usual semver/calens-changelog flow)

Aaaaand it was merged without the changelog :D


Error Message: Value cannot be null. Parameter name: uriString

Hello Olaf,
We have configured according to the latest documentation, but still receive an error message during login attempt.
I would really appreciate if you could have a look on this.
Kind Regards,
Mustafa
Here is also the paragraph from the content of the trace file.
Feedback Type:
Frown (Error)
Error Message:
Value cannot be null.
Parameter name: uriString
Stack Trace:
System.ArgumentNullException
at System.Uri..ctor(String uriString, UriKind uriKind)
at System.UriBuilder..ctor(String uri)
at Microsoft.Mashup.Client.UI.Extensions.Windows.SystemBrowserOAuthDialog.WrapUrlForPowerBiOAuthRedirect(Uri authorizationUri, UriBuilder redirectUriBuilder)
at Microsoft.Mashup.Client.UI.Extensions.Windows.SystemBrowserOAuthDialog.Authorize(Uri logoutUri, Uri authorizationUri)
at Microsoft.Mashup.Client.UI.Shared.OAuthManager.OpenOAuthDialog(IWindowHandle parentWindowHandle, ITelemetryService telemetryService, String resourceKind, String accessToken, String resourceUrl)
at Microsoft.Mashup.Client.UI.Shared.OAuthManager.<>c__DisplayClass6_0.b__0()
at Microsoft.Mashup.Client.UI.Shared.OAuthManager.<>c__DisplayClass7_0.b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
Stack Trace Message:
Value cannot be null.
Parameter name: uriString

Hi MOe2377,
could you please provide additional details of steps you are performing? At which point of time or after which step the error occurs?
Thanks a lot, Olaf

Hello Olaf,
Thank you for the provided direct-support. It was very much appreciated.
As discussed, we switched off Default Browser, afterwards we were able to connected and authenticate.
Kind Regards,
Mustafa

I have the same problem with the error message "Value cannot be null. Parameter name: uriString".
When I switch off the "Use my default web browser", I no longer have the problem but I still cannot connect. It seems the logon scren opens and closes immediately without letting me enter my credentials. Could you help me solve this?
Thanks,
Alex

Closing due to inactivity


Automatic failsafe land in fixed wing RTL not possible

Expected behavior
Goal: When losing RC the fixed-wing plane should fly back to home, loiter over it for a certain time and then slowly descend while loitering until it reaches the ground. This allows configuring a least possible damage failsafe for the worst case that the pilot loses control but didn't plan any landings.
By default a plane comes back in RTL and loiters indefinitely over the home point because RTL_LAND_DELAY is set to -1 in the fixed-wing defaults.
Describe the bug/To Reproduce
I did some fixed-wing RTL SITL tests before risking my real plane:

setting RTL_LAND_DELAY to 0 presuming I already lost control completely when I don't regain connection until the plane reaches home and it should start descending immediately. It immediately upon reaching home starts descending going straight ahead without turning. After half the way to the ground, it suddenly starts ascending indefinitely continuing straight with the same heading. First thing in the log.
setting RTL_LAND_DELAY to 20 presuming I anyways want to loiter at least one full turn above my head before descending for good practice. It starts loitering and continues indefinitely. The many turns above home in the log.
The only way to get the plane down in auto but triggered manually which is not usable as a failsafe is to do an RTL first having it loiter above home. Then issue commander land on the console since QGC doesn't show the button or the mode in the mode switcher. The plane starts descending, doesn't loiter nicely around home anymore but rather comes down in a random spiral further away from home. At the end of the log.

Log Files and Screenshots
Here's the SITL log of my tests: https://logs.px4.io/plot_app?log=3cbedcc2-3823-409f-84da-65ab0d88df6d
Showing 1. visually.

Drone (please complete the following information):

Master state ffa9fdbd5677eaedf0bec9bea99967cfaee9e562
SITL make px4_sitl gazebo_plane

Additional context
Sounds like it's related to https://github.com/PX4/Firmware/issues/12035

So just to be clear, what we're seeing here sounds like the documented behaviour: http://docs.px4.io/master/en/flight_modes/return.html#fixed-wing-fw
I think you're saying this is not optimal. Currently RTL_LAND_DELAY=-1 means  "do not land/loiter" forever" and you're saying it should mean "loiter while descending slowly"? Sounds good to me.
If you change this, can we keep the docs in sync - e.g. note what has changed, especially any configurable params.

I think you're saying this is not optimal. Currently RTL_LAND_DELAY=-1 means "do not land/loiter" forever" and you're saying it should mean "loiter while descending slowly"? Sounds good to me.

@hamishwillee I don't think you are correct here.
@MaEtUgR It sounds like you are describing two things: 1) bugs with how RTL_LAND_DELAY works, and 2) new landing logic for the RTL around home scenario where the vehicle loiters slowly to the ground if RTL_LAND_DELAY is 0 or a positive value?
I'm curious: What happens if throttle is forced to 0 when in a fixed wing loiter?  Will the position controller maintain the loiter ground-track nicely even though the vehicle won't maintain altitude?  I know in Mission mode the vehicle does things like spiral up/down to reach an altitude setpoint ignoring the mission's ground track.

@Antiheavy Thanks. I'm not at all sure, hence the question :-)

I think you're saying this is not optimal. Currently RTL_LAND_DELAY=-1 means "do not land/loiter" forever" and you're saying it should mean "loiter while descending slowly"?

@hamishwillee I think the default is ok or could be discussed separately based on user feedback. I just expect to have the option to spiral down slowly because RTL is the default failsafe for RC loss and if I'm unable to regain control e.g. remote broken or ran out of battery I'd expect it to do what I consider the least damage reaction given no further planning.

bugs with how RTL_LAND_DELAY works

@Antiheavy Yes, big bug that it starts ascending again while landing with RTL_LAND_DELAY 0 this leads not just to a crash but a flyaway. And RTL_LAND_DELAY > 0 doesn't start landing.

new landing logic for the RTL around home scenario where the vehicle loiters slowly to the ground

I wasn't aware it's something new. I thought that's the failsafe when auto-land is enabled in RTL because it's the easiest way to land close to home. Is the originally expected use case landing on a runway planned through a mission? https://docs.px4.io/master/en/flight_modes/return.html#fixed-wing-fw What do you think of the feature then? Do you plan the landing using a mission for every manual flight?


💡[FEATURE] MIDI support

So few MCUs offer USB MIDI HOST support, it would be AMAZING to have RPI2040 support for that. If possible, could you add an example that shows how to implement this?
Thanks!!!

Yes. See pico-usb-midi-filter for an example.

Wow also https://github.com/rppicomidi/midi2usbhost which uses the USB peripheral.

Is this library able to be "pluggable"? ie. can a device be un-plugged, and another plugged-in gracefully?

hey there
I'm on my way to building a USB MIDI host with my RP2040 and Arduino.
I managed to get the device_info sketch working, but I'm not sure what would be the next step to get MIDI controllers recognized and working.
The rest of my code is Arduino, so it would be better if I stayed with it.
Can anyone help?


EKF2 not resetting position state when stopping GPS use and EV is already running

Description
"Failsafe enabled: no local position" when EKF2 switches from GPS to external vision. You can read my diary on discuss.px4.io, which is a lot more detailed.
To Reproduce
Steps to reproduce the behavior:

drone with GPS and SLAM, visual odometry or similar via /mavros/vision_pose, VISION_POSITION_ESTIMATE or similar
EKF2_AID_MASK is GPS + EV_POS + EV_YAW
take off, hover/fly for at least 30 seconds (due to some internal EKF2 checks, see forum post)
fly into a GPS-denied area (tunnel, hall etc.)

Expected behavior
EKF2 recognizes a decrease in GPS quality and switches to EV as primary localization source.
Because GPS was bad and EV can be imperfect as well, it needs to reset its position state, to avoid failing _vel_pos_test_ratio checks.
Log File
https://logs.px4.io/plot_app?log=b7f5fb21-808a-42eb-844d-18901eb24620
Screenshot

pos_test_ratio explodes as soon as stopping GPS use
EKF states[7..8] (position) are only reset after dead reckoning and failsafe

Drone

rotary wing

@priseborough would be great if you could comment.

@artifactz is your vision yaw in the NED frame?

@mhkabir My vision yaw is in ENU, because I use Mavros:

ROS uses ENU frames as convention, therefore position feedback must be provided in ENU.
(https://dev.px4.io/v1.9.0/en/ros/external_position_estimation.html)

Is that incorrect?

@jkflying Could you please assist the review?


add Base theme option

🚀 Description
Added BASE field to Theme
📄 Motivation and Context
Base theme provided by mermaid also looks good and it supports configuring theme colors
🧪 How Has This Been Tested?
No tests.
📦 Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

✅ Checklist

[ ] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Hey! Thanks for the PR!
I'm also planning to support it via #17

Addressed by #18


Move all redis logic to a separate class

Move all the Redis requests to a separated class called RedisManager inside the SidekiqScheduler module.

Coverage increased (+0.4%) to 97.904% when pulling 88b5521c892f0fc27ba61ff78ed6aa69ad53865d on mconiglio:redis-refactor into 8a80dd41119d5aeb394c0c9d2b82bb5de2e775ad on moove-it:master.

Coverage increased (+0.4%) to 97.746% when pulling 998597bcdeb0643547b75ee6cb3de4fbc55e5315 on mconiglio:redis-refactor into 73ea7e0db4d9d5d2e2bddcb9313655e175fc2748 on moove-it:master.


⚠ Bofrost.de has degraded performance

In 0fc7323, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1012 ms

Resolved: Bofrost.de performance has improved in 38895a2 after 6 minutes.


Indeterminate Checkboxes

Indeterminate Checkboxes: http://css-tricks.com/indeterminate-checkboxes/

This issue was imported from Google Moderator
Moderator votes: +16
Issue added by ys on 2014-04-22
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

+1

+1

+1

Now available at http://caniuse.com/#feat=indeterminate-checkbox


/opt/nsm/bro is empty after install

After clicking the "Install Bro-2.5 and Intel Feed Agent" button, it leaves me with a prompt saying
Almost done.  What you will want to do now is to add some feeds.  Since the raspberry pi is limited in its processing power, signing up for too many feeds will overload the unit.
I would suggest signing up for just a few feeds initially, such as 'Phish Tank Intel Feed' and 'Known Tor exit nodes'.
Once you have added your feeds to your sensor, go ahead and pull that info into Bro by issuing the following command:
sudo -u critical-stack critical-stack-intel pull
Now, you will want to perform three final changes.  Go to /opt/nsm/bro/etc
edit Networks.cfg and be sure to add something similar to the following:
<IP_ADDRESS>/8          Private IP space
<IP_ADDRESS>/16      Private IP space
pubicipgoeshere/32      Public WAN IP space
Now, edit nodes.cfg and add in your interface, either eth0 or eth1, etc
finally, start bro.  go to /nsm/opt/bro/bin/ as ROOT and do: ./broctl
type in 'deploy' which should auto start the application.  Log files will be in /nsm/opt/bro/logs/current for active scans and folder archives for completed scans.
That's it. Congrats!

However, /opt/nsm/bro is empty.  There are 3 files in /root/bro-2.5.tar.gz.[123], but I couldn't find hide nor hair of bro elsewhere on the system.

sounds like it could be a dependency issue without having any logs to work off of.  Have you made it beyond the configure command?  Also pay attention to your make command output in the terminal console to see if any errors were presented during install.  I made a quick edit on the bro-installer.sh file to remove the 'clear' command so you can review the command output and see if there were any errors during the 'make' and 'make install' command.  just click 'Check for Updates from Github' on the Briar main menu to get the update.  Below is what you should expect to see after the configure command:
====================|  Bro Build Summary  |=====================
Install prefix:    /opt/nsm/bro
Bro Script Path:   /opt/nsm/bro/share/bro
Debug mode:        false
CC:                /usr/bin/cc
CFLAGS:             -Wall -Wno-unused -O2 -g -DNDEBUG
CXX:               /usr/bin/c++
CXXFLAGS:           -Wall -Wno-unused -std=c++11 -O2 -g -DNDEBUG
CPP:               /usr/bin/c++
Broker:            false
Broker Python:     false
Broccoli:          true
Broctl:            true
Aux. Tools:        true
GeoIP:             true
gperftools found:  false
tcmalloc:  false
debugging:  false
jemalloc:          false
================================================================
-- Configuring done
-- Generating done
-- Build files have been written to: /root/bro-2.5/build
issuing 'make' command.

Thanks - it was compiling, but I'd always missed the output before the clear, so this change should at least reveal what's happening.
I've kicked it off and will check on it tomorrow.

All good.  I did switch from a Raspberry Pi B to a Raspberry Pi 3 B - I'm guessing that made the difference.  I'll switch back to the slower platform and confirm.

Glad it cooperated for you on the Pi 3 B.  I'll be sure to update the wiki on confirmed supported Pi models.  If you find out what went wrong on the older Pi unit I'll see if I can add a legacy install option to the script to support older units depending on what the problem is.  Thanks @glyph02

Did you change anything else other than the pause?   It successfully compiled and installed on the older platform as well.  (shrug)

Nope no changes/commits were made that I can recall other than those simple edits made to the clear command.  Maybe it caught a dependency that was missed the first time around or something.  I wouldn't beat yourself up over it.  These things happen.  I'm just glad it is cooperating for you now

Glad it's solved.  Cheers!


[Important] The current website is about to enter maintenance mode to aid with v3 launch

TL;DR; At the end of Jan 2021, all tracks will enter v3 staging mode. Updates will no longer sync with the current live website, but instead sync with the staging website. The JavaScript section of the v3 repo will be extracted and PR'd into this track (if appropriate). Further issues and information will follow over the coming weeks to prepare JavaScript for the launch of v3.
Over the last 12 months, we've all been hard at work developing Exercism v3. Up until this point, all v3 tracks have been under development in a single repository - the v3 repository. As we get close to launch, it is time for us to explode that monorepo back into the normal track repos. Therefore, at the end of this month (January 2021), we will copy the v3 tracks contents from the v3 repository back to the corresponding track repositories.
As v3 tracks are structured differently than v2 tracks, the current (v2) website cannot work with v3 tracks. To prevent the v2 website from breaking, we'll disable syncing between track repositories and the website. This will effectively put v2 in maintenance mode, where any changes in the track repos won't show up on the website. This will then allow tracks to work on preparing for the Exercism v3 launch.
Where possible, we will script the changes needed to prepare tracks for v3. For any manual changes that need to be happening, we will create issues on the corresponding track repositories. We will be providing lots of extra information about this in the coming weeks.
We're really excited to enter the next phase of building Exercism v3, and to finally get it launched! 🙂

As of today, the website has entered maintenance mode.

As of today, the website has entered maintenance mode.

I think this has been acked and can be closed. Here we go 🚀


RFC: Extensible pre-definition-elaboration

Proposal
Context
Recursive function definitions are currently elaborated to a PreDefinition, which is what’s sent to the compiler/interpreter. On the way to the kernel, the PreDefinitions are grouped by strongly connected component, and then pass through Lean.Elab.addPreDefinition which turns them into non-recursive Definition suitable for the kernel.
Status quo
Currently, Lean has a few built-in modes to do this step:

Non-recursive definitions are translated straight-forwardly
unsafe definitions are turned into axioms
partial definitions are made opaque (but don’t require axioms because the result type must be Inhabited)
structurally non-mutual recursive functions are expressed using bounded recursion brec recursor of the underlying data type
well-founded recursive functions are expressed using WellFounded.fix

The code makes educated guesses: Certain annotations cause it to go for well-founded recursion, otherwise it tries structurally first and then well-founded.
This also means that these strategies have a rather simple interface:

(preDefs : Array PreDefinition) : TermElabM Unit

Motivation for more strategies
There are possibly a large number of alternative ways to process a PreDefinition. Some particularly interesting ones are

Partial functions with an explicit inductive predicate for the domain of the function
Monotone functions in a CPO, where the function exists by construction, even for non-terminating equations. In particular

Monadic functions in the Option monad (and inhabited result type)
Tail-recursive functions with inhabited result type.

Well-founded recursion using extrinsic “termination” proof using congruence lemmas
Coinductive definitions

It’s easy to tell that I am approaching this from an Isabelle background, where all these are possible. Of course it’s not completely trivial to port them to Lean, but at least with enough Inhabited side conditions and expecting only propositional equalities I believe they can be used here, and will be useful.
There many be many more interesting takes here that people would experiment with, or some very domain-specific ones.
It’s unlikely that we want to have to develop and maintain all of these within the main lean repository. So it seems desirable to make this part of the pipeline user-extensible.
Incidentially, this also reduces friction even for those working on the “core strategies” if bigger changes can be iterated upon in a separate project.
Proposed change (high-level)
Lean is generally a very extensible system. So it beholds of Lean to allow users to write their own PreDefinition processor, without having to touch the core repo.
So this requires

A good name for the concept
An API interface
Surface syntax

Proposed change (detail)
(This is right now mostly a straw man proposal, I don’t have much experience with designing good extensible interfaces in Lean yet).

I need help finding the right name.
Is this a “PreDefinition compiler”? “Derecursifier”? Something else?

The API interface could simply be
def Derecursifier :=  Array PreDefinition → TermElabM Unit

Maybe with certain expectations (which could be checked), such as that afterwards, certain names
have been added to the environment with certain types.

For the surface syntax, I’d expect we can use the macro and elaboration system, define a syntax (syntax category?) for these derecursifiers, and an annotation that goes where terminating_by goes, so derecursify $derecursifier.

Community Feedback
(None yet)
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Big +1 to the idea. I would suggest not giving it any frontend syntax though, and just using an environment extension to track declared derecursifiers. These are fairly easy to set up and use inside or outside the core. A representative example is:
https://github.com/leanprover/lean4/blob/e217ad3929ed1c6f3dc71d5d47e18458b2357e39/src/Lean/Linter/MissingDocs.lean#L32-L65
You can add new extensions using the @[builtin_foo] attribute inside lean core and @[foo] outside of the core.

I see, we can use Environment Extensions to declare possible handlers.
How would I annotate a concrete function definitions to use a specific handler? And pass additional parameters (possibly including longer proofs even)?

How would I annotate a concrete function definitions to use a specific handler? And pass additional parameters (possibly including longer proofs even)?

That would be new syntax, we currently don't have anything like that. I imagine you could have something like a termination_using foo clause after the definition, where foo could either be a new syntactic class or an identifier referencing a Derecursifier object (in which case it need not be globally registered like the structural and WF handlers are).

termination_using foo with foo a new syntactic class was my original idea :-)
What are the downsides?

Adding a new (extensible) syntactic class is a comparatively large extension to the grammar, requiring documentation and so on. It might also cause some new challenges for the formatting / style guide - it's not immediately obvious how it would be formatted to me, and it might also depend on what derecursifiers need in practice, which makes it tricky to spec in the absence of such (except for the two existing derecursifiers, but these would presumably be globally registered and not use the syntax at all).

I'd be excited for what this enables in combo with Alex Keizer's https://github.com/alexkeizer/QpfTypes, big +1

While it was very useful when experimenting, the urgent needs for this seem to be rather low, and for example the aeneas project seems to be fine by extending the syntax as needed. Closing for now.


Fix time skew exceptions crashing disruptor thread

For now, we fix all known issues with time skew in Metric Views.

In the event of a detected time skew, we just throw away all our data.  We really don't know if it's safe to push anything we have, and we cannot safely do any aggregation / report correct timestamps.
We add (the first?) tests for MutableViewData to ensure it does not throw when time rewinds, but instead drops recorded data points and resets itself.

Fixes #2068 (deemed to not have a workaround)

Codecov Report

Merging #2071 (929962f) into master (6123b84) will decrease coverage by 0.01%.
The diff coverage is 60.00%.

@@             Coverage Diff              @@
##             master    #2071      +/-   ##
============================================
- Coverage     83.08%   83.06%   -0.02%
  Complexity     2264     2264
============================================
  Files           322      322
  Lines         10557    10565       +8
  Branches       1048     1049       +1
============================================
+ Hits           8771     8776       +5
- Misses         1448     1451       +3
  Partials        338      338

Impacted Files
Coverage Δ
Complexity Δ

.../io/opencensus/implcore/stats/MutableViewData.java
92.07% <60.00%> (-1.52%)
4.00 <0.00> (ø)

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 6123b84...929962f. Read the comment docs.

Codecov Report

Merging #2071 (929962f) into master (6123b84) will decrease coverage by 0.01%.
The diff coverage is 60.00%.

@@             Coverage Diff              @@
##             master    #2071      +/-   ##
============================================
- Coverage     83.08%   83.06%   -0.02%
  Complexity     2264     2264
============================================
  Files           322      322
  Lines         10557    10565       +8
  Branches       1048     1049       +1
============================================
+ Hits           8771     8776       +5
- Misses         1448     1451       +3
  Partials        338      338

Impacted Files
Coverage Δ
Complexity Δ

.../io/opencensus/implcore/stats/MutableViewData.java
92.07% <60.00%> (-1.52%)
4.00 <0.00> (ø)

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 6123b84...929962f. Read the comment docs.


tests/kernel/context/testcase.yaml#kernel.common.k_sleep fails on nrf52_pca10040 and nrf52840_pca10056

Execution log:
Running test suite context
===================================================================
starting test - test_kernel_interrupts
PASS - test_kernel_interrupts
===================================================================
starting test - test_kernel_timer_interrupts
SKIP - test_kernel_timer_interrupts
===================================================================
starting test - test_kernel_ctx_thread
Testing k_current_get() from an ISR and thread
Testing k_is_in_isr() from an ISR
Testing k_is_in_isr() from a preemptible thread
PASS - test_kernel_ctx_thread
===================================================================
starting test - test_busy_wait
Thread busy waiting for 20000 usecs
Thread busy waiting completed
PASS - test_busy_wait
===================================================================
starting test - test_k_sleep
 thread sleeping for 50 milliseconds
 thread back from sleep
FAIL - thread_sleep@684. timestamp out of range, got 70

    Assertion failed at /home/kspoorth/work/latest_zephyr/tests/kernel/context/src/main.c:753: test_k_sleep: (rv not equal to 0)
 *** thread timed out waiting for thread on k_sleep().
FAIL - test_k_sleep
===================================================================
starting test - test_kernel_cpu_idle_atomic
SKIP - test_kernel_cpu_idle_atomic
===================================================================
starting test - test_kernel_cpu_idle
PASS - test_kernel_cpu_idle
===================================================================
starting test - test_k_yield
PASS - test_k_yield
===================================================================
starting test - test_kernel_thread
PASS - test_kernel_thread
===================================================================
===================================================================

PROJECT EXECUTION FAILED

Platforms: nrf52_pca10040 and nrf52840_pca10056
Latest commit on which the failure is seen: afa0e0026fb94d37f50dc53f9d0981b1dc5c306b

@pizi-nordic can you take a look?


[LD-1014] Update Api Docs for adding contacts to sequence

Make sure you've checked off all these things before submitting:
https://apollopde.atlassian.net/browse/LD-1014

[x] This pull request isn't for a company's fork, it's intended for the upstream Slate shared by everybody.
[x] This pull request is submitted to the master branch.
[x] If it makes frontend changes, this pull request has been tested in the latest version of Firefox, Chrome, IE, and Safari.
[x] If it is an API related fix, the shell and python code have been tested


Need clarification regarding the relationship between Activation Functions and the Initializers

In the Table 11-1, shown below, the formula for Glorot and He Initializers is dependent on the Activation Functions.
But in the Tensorflow Source Code of neither the He Initializer, nor the Glorot Initializer, along with the Code of the Parent Class, VarianceScaling Initializer, there is no mention of Activation Function's dependency on the Initializers.
This should be either a mistake in the book or should be a bug in the Tensorflow Code. Can you please clarify?

Image from the first version of "Hands on Machine Learning with Scikit-Learn and Tensorflow":

Hi @worldpeaceaspirer ,
That's a great question! Here are some reasons that might explain why the main deep learning libraries do not try to automatically match the initializer with the activation function:

firstly, whether you choose to use Glorot initialization or He initialization makes little difference in many neural nets (especially shallow ones). That said, it does make a difference for deeper nets (or else I wouldn't have mentioned it in the book), so this argument is insufficient.
secondly, it's often best for an API to be as simple and consistent as possible, even if it means not always being optimal. Adding too much magic might do more harm than good. Having one default initializer is simple and easy to understand, even if it is not always optimal. If you're training a deep net, there are things you will need to tweak to get the best results, including the initializers.
thirdly, and perhaps most importantly, it might be quite hard to implement. Indeed, what about neural nets where the layer containing the weights is not directly attached to the activation function (for example, there may be a BatchNormalization layer in between a Convolutional layer and the activation function)? In PyTorch, the layers with weights and the activation function are treated separately, so it would be very tricky to tie them automatically. And what about user-provided activation functions? Should the user be forced to provide both the activation function and the corresponding initializer? If not, then what should the default initializer be?

Note that Keras uses the Glorot uniform initialization by default, while PyTorch uses He (Kaiming) uniform initialization by default. Keras lets you easily choose another initializer when creating a layer, by setting kernel_initializer. In PyTorch, you have to set the weights yourself after creating the layer, typically using one of the provided initialization functions:
dense = torch.nn.Linear(10, 3) # 10 inputs, 3 outputs
torch.nn.init.xavier_uniform_(dense.weight)

Interestingly, PyTorch provides a calculate_gain() function that returns the "gain" as a function of the initialization function. The gain is the number by which the Glorot initialization must be multiplied. For example, it returns sqrt(2) for ReLU. It also supports some more complex activation functions, such as Leaky ReLU, for example:
gain = torch.nn.init.calculate_gain("leaky_relu", 0.2)  # leaky_relu with negative_slope=0.2
torch.nn.init.xavier_uniform_(dense.weight, gain=gain)

I hope this helps!

Note that I recommended a gain of 2 for the hyperbolic activation function (𝑡𝑎𝑛ℎ) in the first edition of my book (I don't remember what source I got that from, but it seemed reasonable given that 𝑡𝑎𝑛ℎ(𝑥)=2⋅𝜎(2𝑥)−1). However, the paper On weight initialization in deep neural networks by Siddharth Krishna Kumar recommended using a gain of 1, which explains the change in the second edition.
However, looking at the calculate_gain() function a few minutes ago, I was surprised to see that it returns 5/3 for 𝑡𝑎𝑛ℎ! I could not find a paper to support this number, but Thomas Viehmann gave an interesting justification in this discussion.
Similarly, the authors of the SELU paper recommend using a gain of 1, but the calculate_gain() function returns 3/4 instead. The discussion above also explains why they use this value.

@ageron,
Sorry for the delayed response. It's my pleasure discussing with you because I have learnt many concepts of Machine Learning and Deep Learning from your books. Thank you for the detailed explanation. Closing the issue.


return 'playlistinfo'

Hi, thanks for sharing your library.
I have been using it in a couple small scripts to send basic commands like clear, play, load [playlist name].
I wanted to get playlistinfo -  mpd doc description:
Displays a list of all songs in the playlist, or if the optional argument is given, displays information only for the song SONGPOS or the range of songs START:END [2]
t = mpc:send('playlistinfo')
for k,v in pairs(t) do print(k,v) end

This returns metadata for only the last item in a playlist. I took a look at mpd.lua, but did not have any luck figuring this one out.
If you have any ideas it would be much appreciated!
musicbrainz_albumartistid	e6de1f3b-6484-491c-88dd-6d619f142abc
pos	49
last-modified	2020-05-13T08:59:09Z
album	Rush: Original Motion Picture Soundtrack
composer	Stephen Lipson, Bryce Jacobs, Hans Zimmer, Jack Dolman
originaldate	2013-09-09
musicbrainz_trackid	f3c00e6a-7f7e-4300-8b3a-3bce0489379e
albumartistsort	Bobby Krlic
id	39986
albumartist	Hans Zimmer
musicbrainz_albumid	ab1dd476-9587-493a-aa26-0b21500a3b8e
disc	1
musicbrainz_artistid	e6de1f3b-6484-491c-88dd-6d619f142abc
title	20%
track	10
time	62
label	WaterTower Music
date	2013
artist	Hans Zimmer, Bryce Jacobs, Stephen Lipson & Jack Dolman
musicbrainz_releasetrackid	17f6db58-c1fa-4c80-9915-be5bd351099a
file	Scores/Hans Zimmer/2013 - Rush_ Original Motion Picture Soundtrack/10 - 20%.flac
duration	61.573
genre	Score, Classical

Hello @vredesbyyrd,
Thanks for your report. I think this part of the code is causing your issue:
https://github.com/kAworu/lua-mpd/blob/master/mpd.lua#L121-L140. Specifically, My guess is that https://github.com/kAworu/lua-mpd/blob/master/mpd.lua#L138 override the song information for each songs.
I think fixing this require to break the API of send. Maybe returning err, table, raw where err is an error (if any), table the response "values" as we do now, and raw the complete MPD response string. That way, functions needing a "simple" response representation can use table while thoses needing more involved parsing (such as playlistinfo) could use raw.

@kAworu
Thanks for the breakdown!

That way, functions needing a "simple" response representation can use table while thoses needing more involved parsing (such as playlistinfo) could use raw.

That sounds like a good approach to me :) I am still very much learning lua, but i'll see if I can implement returning mpd's raw string alongside err, table.


writeln('{{deploy_path}}'); Does not work

The bracket placeholder syntax is currently only available in run function. e.g. writeln('{{deploy_path}}'); does not work. Extending it to all functions can be really useful.

Working in v5.


Uncaught TypeError: this.peekTop(...).setTarget is not a function

[Enter steps to reproduce below:]
Unfortunately, it's rather hard to determine when it happens. But while working, it happens multiple times a day, usually just when navigating.
I know it's vague and may be hard to reproduce - if it's too much so, please feel free to close.
Also I will amend to this ticket in case I learn when exactly it happens.
Atom Version: 1.5.4
System: Mac OS X 10.11.3
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: this.peekTop(...).setTarget is not a function
At /Users/sthiel/dev/cs/atom-vim-mode-plus/lib/operation-stack.coffee:45

TypeError: this.peekTop(...).setTarget is not a function
    at OperationStack.process (/Users/sthiel/dev/cs/atom-vim-mode-plus/lib/operation-stack.coffee:57:20)
    at OperationStack.run (/Users/sthiel/dev/cs/atom-vim-mode-plus/lib/operation-stack.coffee:37:8)
    at run (/Users/sthiel/dev/cs/atom-vim-mode-plus/lib/base.coffee:13:29)
    at atom-text-editor.<anonymous> (/Users/sthiel/dev/cs/atom-vim-mode-plus/lib/base.coffee:200:65)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:570:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:378:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -0:44.1.0 find-and-replace:confirm (atom-text-editor.editor.mini.is-focused)
     -0:42.8.0 find-and-replace:focus-next (atom-text-editor.editor.mini.is-focused)
     -0:42.8.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:42.2.0 find-and-replace:replace-all (atom-text-editor.editor.mini.is-focused)
     -0:40.9.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:40.9.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  3x -0:40.9.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:40.1.0 core:save (atom-text-editor.editor.vim-mode-plus.normal-mode.is-focused)
  2x -0:38.9.0 blur (atom-text-editor.editor.vim-mode-plus.is-focused.visual-mode.characterwise)
     -0:34.4.0 linter:next-error (atom-text-editor.editor.vim-mode-plus.visual-mode.characterwise.is-focused)
  2x -0:34.4.0 blur (atom-text-editor.editor.vim-mode-plus.visual-mode.characterwise.is-focused)
     -0:20.9.0 vim-mode-plus:find (atom-text-editor.editor.vim-mode-plus.visual-mode.characterwise.is-focused)
  3x -0:20.9.0 blur (atom-text-editor.editor.vim-mode-plus.visual-mode.characterwise.is-focused)
     -0:19.1.0 vim-mode-plus:find (atom-text-editor.editor.vim-mode-plus.normal-mode.is-focused)
     -0:18.6.0 vim-mode-plus:move-to-previous-paragraph (atom-text-editor.editor.vim-mode-plus.normal-mode.is-focused)
  4x -0:14.8.0 blur (atom-text-editor.editor.vim-mode-plus.normal-mode.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "linter-jshint"
    ],
    "excludeVcsIgnoredPaths": true,
    "packagesWithKeymapsDisabled": [
      "turbo-javascript",
      "git-blame",
      "vim-mode-plus",
      "es6-javascript",
      "emmet",
      "node-debugger"
    ],
    "themes": [
      "atom-material-ui",
      "one-dark-syntax"
    ]
  },
  "editor": {
    "fontSize": 16,
    "invisibles": {},
    "scrollPastEnd": true,
    "showIndentGuide": true
  }
}

Installed Packages
# User
aligner, v0.19.1
atom-beautify, v0.28.26
atom-material-ui, v1.2.0
atom-ternjs, v0.13.2
atom-typescript, v8.3.0
autocomplete-ctags, v0.4.0
autocomplete-python, v1.7.0
autocomplete-ruby, v0.1.0
build, v0.55.0
build-cargo, v0.12.0
build-make, v0.7.0
coffee-compile, v0.21.1
css-snippets, v0.9.0
cursor-history, v0.5.9
emmet, v2.4.2
expand-region, v0.2.4
javascript-snippets, v1.2.1
language-apache, v1.4.0
language-elm, v1.3.3
language-escript, v0.1.0
language-jade, v0.6.3
language-mako, v0.6.0
language-rust, v0.4.6
linter, v1.11.3
linter-clang, v3.4.4
linter-coffeelint, v1.1.2
linter-csslint, v1.3.2
linter-docker, v0.1.2
linter-elm-make, v0.4.0
linter-eslint, v7.0.0
linter-flake8, v1.13.0
linter-golinter, v1.2.0
linter-htmlhint, v1.0.3
linter-javac, v1.8.0
linter-js-standard, v3.2.1
linter-js-yaml, v1.2.5
linter-jscs, v3.4.8
linter-jsonlint, v1.1.6
linter-jsxhint, v0.1.2
linter-lua, v1.0.1
linter-markdown, v1.5.0
linter-pylint, v1.2.0
linter-python-pep8, v0.2.0
linter-ruby, v1.2.2
linter-rust, v0.4.1
linter-sass-lint, v1.1.1
linter-scss-lint, v2.5.1
linter-shellcheck, v1.1.0
linter-tslint, v0.8.3
linter-xmllint, v1.3.4
minimap, v4.19.0
minimap-git-diff, v4.1.8
minimap-linter, v1.1.1
node_modules, vundefined
pretty-json, v0.4.1
project-manager, v2.7.6
racer, v0.18.0
react, v0.14.1
react-es6-snippets, v0.3.0
react-snippets, v0.3.0
rust-api-docs-helper, v0.5.1
snippets-jade, v0.1.1
source-preview-jade, v0.1.1
source-preview-react, v0.2.0
symbol-gen, v1.0.0
symbols-tree-view, v0.11.0
vim-mode-plus, v0.23.0
you-complete-me, v0.7.1

# Dev
No dev packages

Hmmm, not sure why this was reported as thrown from Atom core, but this looks like a vim-mode-plus issue (and like you might have linked a local version of it into packages with apm link sometime ago), so I'm going to close this out.

Thanks ! How could I miss this :) ! Maybe I trust tooling too much sometimes.
The bug was reposted here in the respective repository.
Maybe the possibility of atom posting exceptions to the incorrect repository is something worth looking at, provided the author of vim-mode-plus (@t9md) didn't do anything special.

@Byron-TW I suspect it has to do with the fact that it wasn't located in ATOM_HOME/packages and was instead symlinked.  Hopefully I'll have time to take a look at it.


User on cloudCode do not match real values

Steps to reproduce:

Lets say that we have column in User called "Enable"
setup Enable=false
call cloudCode function from JS SDK -> change enable to Enable=True
call same cloudCode function (or any other) from JS SDK -> check request.user.Enable
you will get Enable=false instead of Enable=True

My question is: when a user call any CloudFunction from and SDK do the parse lib become the user each time and query for the latest values, meaning, can we say with confident that request.user is always up-to-date or should I become the user with session token on each call?

Without seeing the code, it's hard to know exactly. Perhaps you're not calling the .save() method?

We have lots of passing test cases that cover these features. Can you post some code that reliably reproduces your issue? Ideally as a test case we can add to our test suite.

Closing due to lack of activity, please update to latest parse-server version and reopen if the issue persist.
Don't forget to include your current:

node version
npm version
parse-server version
any relevant logs (VERBOSE=1 will enable verbose logging)


Throw custom error for premium domains and brand block

If a domain is blocked due to a Donuts DPML brand block, or registerable at a premium price by contracting the registrar, the whois query might return unconventional output.
> whois google.chat
...
The registration of this domain is restricted, as it is currently protected by a DPML Block. Additional information can be found at http://www.donuts.domains/what-we-do/brand-protection.

> whois good.download
...
This platinum domain is available for purchase. If you would like to make an offer, please contact<EMAIL_ADDRESS>
This currently causes the whois-parser code to return an ErrDomainInvalidData error, which implies there is an error with the querying. So I added custom errors detecting these two additional domain states so the result is more explicit.
Application code calling the library can catch the errors and decide how to handle them. This allows to use the whois-parser tool to check if a domain is registerable.

Codecov Report

Merging #26 into master will decrease coverage by 0.96%.
The diff coverage is 65.21%.

@@             Coverage Diff             @@
##            master      #26      +/-   ##
===========================================
- Coverage   100.00%   99.03%   -0.97%
===========================================
  Files            3        3
  Lines          909      932      +23
===========================================
+ Hits           909      923      +14
- Misses           0        4       +4
- Partials         0        5       +5

Impacted Files
Coverage Δ

parser.go
96.68% <0.00%> (-3.32%)
:arrow_down:

utils.go
95.06% <78.94%> (-4.94%)
:arrow_down:

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 5826660...daba02a. Read the comment docs.

Hello @phgn0
Thanks for your PR.

Hey @likexian, thanks for merging this so fast :)
Also thanks for creating the library, it's very useful.


adding more tests for docker build with requirements file

Pull Request Test Coverage Report for Build 109

4 of 4 (100.0%) changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 82.176%

Files with Coverage Reduction
New Missed Lines
%

datmo/core/util/json_store.py
2
93.22%

Totals

Change from base Build 99:
0.02%

Covered Lines:
1775

Relevant Lines:
2160

💛  - Coveralls


Bump go versions in CI from 1.14 and 1.15 to 1.15 and 1.16

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

Looks good to me!


Why is there a B-grid support?

I see some mention to MOM5 and B grid here:
https://github.com/COSIMA/regional-mom6/blob/663b5f3011475addb41abd3f1f619e39f4410a97/regional_mom6/regional_mom6.py#L576-L620
Is it to read an input from a B grid? From the code I understand that the initial condition is converted to a B grid but I don't understand why?

I was just trying to keep things as flexible as possible. The code is read as a B grid but output as C always right?

Not sure if that's the case but I can see why that is the intention. Thanks for explaining. :)

Can you elaborate on this issue Navid? ACCESS-OM2 is a B grid, and this function is what does the interpretation of B grid data before it's converted to C grid for use with MOM6

OK, so the B-grid support is for the input, right?

Yes only input. Output is always C

Okie. I must have gotten the impression that it was for the output and I was confused. I'm closing this!


implemented hotkeys for controlling scheduler

Added components for global hotkeys and changed SKoreScheduleView to use them. Pressing the specified key combination toggles the schedule on and off.

Awesome, thanks for this.


how recover use my backup dat file?

i reinstall windows (cleaned disk c:)
my wallet software installed to disk D:
i have dat file (backup copy)
but i not understand how use dat
please help !
how recover use dat file?

i replace file wallet.dat
balance not confirmed, need waiting?

i replace file wallet.dat
balance not confirmed, need waiting?


GHSA-77vh-xpmg-72qh: Clarify mediaType handling

Anchore and Twistlock both identify Pumba as being vulnerable to Github Security Advisory https://github.com/advisories/GHSA-77vh-xpmg-72qh.
Fix is described as upgrading github.com/opencontainers/image-spec  to at least 1.0.2.
-Kevin

fixed


Make the lack of AtlasTexture support in AnimatedTexture more prominent

See https://github.com/godotengine/godot/issues/33855#issuecomment-674661935.

Thanks!

Cherry-picked for 3.2.3.


fix(vscode): textmate grammar

Slidev's syntax highlighting is broken in the latest VSCode. I think this is due to https://github.com/microsoft/vscode/pull/221204.
This fix works but I don't know if it is the best way.

Closes #1801


wallet balance doesnt match explorer balance

This was asked by a member of the community on bitcointalk.

A wallet can have multiple addresses, and you can have so-called "change addresses" (see https://en.bitcoin.it/wiki/Change) which will be generated automatically whenever you spend less than you have.
Those "change addresses" are part of the ROIcoin anonymity features, are known only to your wallet and can hold more than small change.
They are not displayed in the usual wallet UI, but you can typically view them by going to the debug console and typing "listunspent".
Additionally the POS rewards are currently not reported ( and likely stored in your personal wallet ).


"upstream" and "downstream" terminology in istio

Hello,
I am confused by the use of the terms "upstream" and "downstream" in istio documentation.
The glossary https://istio.io/latest/docs/reference/glossary/ uses the term to define Source as The downstream client of the Envoy proxy. A similar wording is in https://istio.io/latest/docs/reference/config/networking/virtual-service/ A downstream client calling a service.
This sounds like a client is always assigned the role of a downstream when calling a service. And consequently, a service always has the role of an upstream when called by a client.
However, for me upstream and downstream are message flow directions. A message is always flowing from upstream to downstream. For example, for a HTTP request the client is upstream, the server downstream. For the response this reverses. Then the server is upstream, the client is downstream. I understand this from RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing (https://tools.ietf.org/html/rfc7230#section-2.3):

The terms "upstream" and "downstream" are used to describe
directional requirements in relation to the message flow: all
messages flow from upstream to downstream.

I would like to learn the official definitions of the two terms in istio. And maybe the referenced documentation can be updated to add those definitions and a clarification with respect to RFC 7230?
Thanks
Thomas

https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology
and
https://discuss.hashicorp.com/t/why-does-hashicorp-seem-to-refer-to-upstream-downstream-as-the-opposite-of-everything-else-ive-read/8663
May be helpful here


Allow rendering geometries to an arbitrary canvas

Fixes #4514.

Nice work @ahocevar this will greatly simplify things like GeoExt vector legends, not having to use a Map anymore.
I've put a few comments / questions in there.

@bartvde I have addressed your comments. The optional 2nd argument is now an object literal with options, including size as you suggested.

@ahocevar I put a small comment wrt the example code, but this LGTM
Please merge if Travis gives the okay

Thanks for the review @bartvde.

Great idea!


Describe the proposed solution

Server load function — +page.server.js, +layout.server.js
Universal load function — +page.js, +layout.js

Alternatives considered
'Isomorphic' 🤮
Importance
nice to have
Additional Information
No response

Shared always made sense to me. Universal seems a bit weird to me because it's like they can run on anything anywhere, but there's really only two places they're running - the client and the server - so it doesn't seem like it needs such an all encompassing name

Not to be utterly controversial, but what if we just named them like we do environment variables? Public load and private load. They both follow the same semantics -- public x can be used both server-side and client-side, while private x can only be used server-side.

Isomorphic seems like it has a clear definition that matches the intent of usage here, so why 🤮?

It's a pretentious word that means the opposite of what people in the JavaScript world want it to mean. Isomorphism describes different things that have the same form, rather than one thing adapting to multiple surfaces. It's backwards.

what do you think about omni-side load function ?

@Jerboas86 In this case, another one in this style: both-side. :)


[Preset] include sourcekit-inproc in default install on Linux

Resolves SR-3699.
Is there any reason to not do this yet?

@swift-ci please test

There's no particular reason why this can't be done, but I haven't tested it yet with one of the build presets that packages up the instance. I'll try and build this tomorrow on my Ubuntu and Darwin boxes to verify that it doesn't have any unforseen issues.

Ah, we should configure sourcekitdInProc to having RUNPATH.

I added a commit that configure RPATH for loading libdispatch.so in relative path.

@swift-ci please test

As a result of doing some verifications, I came to the conclusion that I can not use it as it is.
The following workarounds seem to be necessary for proper operation.
ln -s /usr/lib/sourcekitdInProc.framework/sourcekitdInProc /usr/lib/libsourcekitdInProc.so

It seems necessary to change the installation destination on Linux.

There's probably an easy fix somewhere to solve the installation path without needing a symlink. I'll have a look and see but if you can find/test as well that would be great.
Alex
Sent from my iPhone 📱

On 29 Mar 2017, at 08:50, Norio Nomura<EMAIL_ADDRESS>wrote:
As a result of doing some verifications, I came to the conclusion that I can not use it as it is.
The following workarounds seem to be necessary for proper operation.
ln -s /usr/lib/sourcekitdInProc.framework/sourcekitdInProc /usr/lib/libsourcekitdInProc.so
It seems necessary to change the installation destination on Linux.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Not in apple/swift, but we have some tests failing on SourceKitten with sourcekitdInProc in Swift 3.1 for Linux that built by me. https://github.com/jpsim/SourceKitten/issues/354
Those tests failed even by applying a workaround using symlink.

https://github.com/norio-nomura/swift/tree/enable-sourcekit-test
It needs renaming sourcekitdInProc to proper name.

I added https://github.com/norio-nomura/swift/commit/d9a7f494c3c50023b41b463944453ff7de2d68ba renaming to libsourcekitdInProc.so.

Opened https://github.com/apple/swift/pull/8485

Adjusted rpath that assuming sourcekit-inproc's path is /usr/lib/libsourcekitdInProc.so by https://github.com/apple/swift/pull/8485

@swift-ci please smoke test

@alblue What else is needed to advance this PR?

#8485 has been reverted by #8988. 😞

I think now this can be merged... right? Since #9025 completed the missing piece in #8485 ^^

Can we rebase the change against master to check it applies, and then we can kick off tests again?
Alex
Sent from my iPhone 📱

On 28 Apr 2017, at 22:02, Félix Fischer<EMAIL_ADDRESS>wrote:
I think now this can be merged... right? Since #9025 completed the missing piece in #8485 ^^
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

rebased.

@swift-CIA please smoke test

@swift-ci please smoke test

Can we retry test?

@swift-ci please clean smoke test Linux platform

Can we retry?

I think that failed test is not related to my changes…
https://ci.swift.org/job/swift-PR-Linux-smoke-test/7184/consoleFull#708282560ee1a197b-acac-4b17-83cf-a53b95139a76

I think you can test it, but merging with the latest tag instead of with
the latest commit.
On Sat, Apr 29, 2017 at 1:26 AM Norio Nomura<EMAIL_ADDRESS>wrote:

I think that failed test is not related to my changes…
https://ci.swift.org/job/swift-PR-Linux-smoke-test/7184/consoleFull#708282560ee1a197b-acac-4b17-83cf-a53b95139a76
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apple/swift/pull/8189#issuecomment-298146240, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALNBJx9N3gvhgDUrxBdvEmFr7AkV8e-6ks5r0rvXgaJpZM4MhsnQ
.

@swift-ci please smoke test Linux platform

Yay! 🙌  Thanks! 🙏

🎉🎉🎉
Awesome!
On Sat, Apr 29, 2017 at 6:02 AM Norio Nomura<EMAIL_ADDRESS>wrote:

Yay! 🙌 Thanks! 🙏
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apple/swift/pull/8189#issuecomment-298157031, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALNBJxfjX5vNVTSjmz57Mk1Lkjdz7kFcks5r0vyfgaJpZM4MhsnQ
.


Snapshot testing of API response with excluding specific fields

Is there a way to exclude a list of fields from the json response of an API while testing with snapshot?
For example if there are keys like updated_at, a randomly generated code or a new id

work around: delete the random or unimportant fields/data before performing the comparison.


FireStore timestampsInSnapshots

Version info

**Angular:5.2.10
**Firebase:4.13.0
**AngularFire:5.0.0-rc.5-next
Debug output
** Errors in the JavaScript console **
** Screenshots **

Steps to set up and reproduce
For now, i solve it like this;
https://firebase.google.com/support/release-notes/js
export class CoreModule {

  constructor( ...,
               private afs: AngularFirestore) {

    const settings = {timestampsInSnapshots: true};
    afs.app.firestore().settings(settings);

   ...
  }
}

I am not able to use your temporary solution when i have AngularFirestoreModule.enablePersistence()
Error i get:
ERROR Error: Firestore has already been started and its settings can no longer be changed. You can only call settings() before calling any other methods on a Firestore object.

I have the same issue and the temporary fix didn't work for me

Sorry it's working, just put it in the config too and had to remove it from there:
var firebaseConfig = {     ...    timestampsInSnapshots: true };

the same problem as @tgangso

@tgangso
I have the same issue here.
Please have more details of how is it working. I've checked FirebaseAppConfig interface
and it seems not having "timestampsInSnapshots"
export interface FirebaseAppConfig {
apiKey?: string;
authDomain?: string;
databaseURL?: string;
storageBucket?: string;
messagingSenderId?: string;
projectId?: string;
}
I use the code below:
AngularFireModule.initializeApp({...firebaseconfig, timestampsInSnapshots: true}),
and it's not working. Please let me know how to add correct config to it. Thank you.

try something like this:
@NgModule( {
  imports: [
    ...,
    AngularFireModule.initializeApp( environment.firebase, 'XXX' ),
  ],
  declarations: [
    ...
  ],
  providers: [
    ...
  ]
} )
export class CoreModule {
  constructor( @Optional() @SkipSelf() parentModule: CoreModule,
               private afs: AngularFirestore ) {

    const settings = { timestampsInSnapshots: true };
    afs.app.firestore().settings( settings );

    ...
  }
}

@egaviriarestrepo
Thank you, but my issue is that our app need to enable offline support.
So if I add "AngularFirestoreModule.enablePersistence(),"
I will get this error:
console.error: Unhandled Promise rejection: Firestore has already been started and its settings can no longer be changed. You can only call settings() before calling any other methods on a Firestore object.
`
@NgModule( {
imports: [
...,
AngularFireModule.initializeApp( environment.firebase, 'XXX' ),
AngularFirestoreModule.enablePersistence(),
],
declarations: [
...
],
providers: [
...
]
} )
export class CoreModule {
constructor( @Optional() @SkipSelf() parentModule: CoreModule,
private afs: AngularFirestore ) {
const settings = { timestampsInSnapshots: true };
afs.app.firestore().settings( settings );

...

}
}
`

you can try, but i dont know if it work :
    afs.app.firestore().settings( settings );
    afs.app.firestore().enablePersistence();

and comment:
AngularFirestoreModule.enablePersistence()

@egaviriarestrepo
Thank you, it works.
Import AngularFirestoreModule instead of AngularFirestoreModule.enablePersistence() then it's working.

@egaviriarestrepo Thank you made it work also like @nathanfan46 sais you have to remove enablePersistence from module load.

This solution isn't working for me.  I've modified my app.module.ts to look like this:
import { AngularFirestoreModule, AngularFirestore } from 'angularfire2/firestore';
...
  imports: [
    ...,
    AngularFireModule.initializeApp(environment.firebase, 'test-app'),
    AngularFirestoreModule
  ]
...
export class AppModule {
  constructor( @Optional() @SkipSelf() parentModule: AppModule,
                 private afs: AngularFirestore ) {

      const settings = { timestampsInSnapshots: true };
      afs.app.firestore().settings( settings );
    }
}

But I get the error error TS2339: Property 'app' does not exist on type 'AngularFirestore'.

@ziftytodd Try afs.firestore.settings({timestampsInSnapshots: true});, that's what worked for me when I got that error.

I tried the solution  of @pshields to @ziftytodd and it solve my issue but now I'm getting Error: InvalidPipeArgument: 'Unable to convert "Timestamp(seconds=1523022000, nanoseconds=0)" into a date' for pipe 'DatePipe' a lot of time. I'm Using firebase 5.0.1

Just
import { AngularFirestoreModule, AngularFirestore } from 'angularfire2/firestore';
in your app.module
then also in your app.module
export class AppModule {
constructor(private afs: AngularFirestore) {
afs.firestore.settings({
timestampsInSnapshots: true,
});
afs.firestore.enablePersistence();
}
}
And we are fine since the dependency injector will always will inject configured instance in this module

Fixed in angularfire2@next

Thank you so much @SaHeinem , worked well for me!!!

and if I have  active AngularFireAuthModule
imports: [
...
AngularFireModule.initializeApp(firebaseConfig),
// AngularFirestoreModule.enablePersistence(),
AngularFireAuthModule,
...
],


Log file not generated on Ubuntu

Based on release notes in RC4, it looks like the log should be at /var/log/rexray.log.  I have ran it from rexray start and also /etc/init.d/rexray start and no luck.  Am I missing something?

Hi @clintonskitson,
I'll update the release notes. They are partially incorrect. The directory is listed as /var/log/rexray but I call out the log file as /var/log/rexray.log erroneously. Please feel free to update them yourself.

@akutz I have no directory or file as /var/log/rexray.

Hi @clintonskitson,
Please echo $REXRAY_HOME to see if it is set to anything.

Hi @clintonskitson,
Also, when you started REX-Ray, was it configured? Did it actually start, or did you receive a warning about missing storage driver configurations? Because nothing is written to the log file until the service actually starts. The CLI refuses to start the service if it's not configured per your request (you wanted early errors).

root@ec2-54-219-167-85:/home/ubuntu# curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -
dpkg: warning: files list file for package 'rexray' missing; assuming package has no files currently installed
(Reading database ... 77281 files and directories currently installed.)
Preparing to unpack rexray-latest-x86_64.deb ...
Unpacking rexray (0.2.0+rc4-1) over (0.2.0+rc4-1) ...
Setting up rexray (0.2.0+rc4-1) ...

REX-Ray has been installed to /usr/bin/rexray

SemVer: 0.2.0-rc4
Binary: Linux-x86_64
Branch: v0.2.0-rc4
Commit: cc3eabe9e4d908def02168e0522db3c5e978d55d
Formed: Mon, 21 Sep 2015 15:17:02 UTC

root@ec2-54-219-167-85:/home/ubuntu# rexray start
Starting REX-Ray...
                          ⌐▄Q▓▄Ç▓▄,▄_
                         Σ▄▓▓▓▓▓▓▓▓▓▓▄π
                       ╒▓▓▌▓▓▓▓▓▓▓▓▓▓▀▓▄▄.
                    ,_▄▀▓▓ ▓▓ ▓▓▓▓▓▓▓▓▓▓▓█
                   │▄▓▓ _▓▓▓▓▓▓▓▓▓┌▓▓▓▓▓█
                  _J┤▓▓▓▓▓▓▓▓▓▓▓▓▓├█▓█▓▀Γ
            ,▄▓▓▓▓▓▓^██▓▓▓▓▓▓▓▓▓▓▓▓▄▀▄▄▓▓Ω▄
            F▌▓▌█ⁿⁿⁿ  ⁿ└▀ⁿ██▓▀▀▀▀▀▀▀▀▀▀▌▓▓▓▌
             'ⁿ_  ,▄▄▄▄▄▄▄▄▄█_▄▄▄▄▄▄▄▄▄ⁿ▀~██
               Γ  ├▓▓▓▓▓█▀ⁿ█▌▓Ω]█▓▓▓▓▓▓ ├▓
               │  ├▓▓▓▓▓▌≡,__▄▓▓▓█▓▓▓▓▓ ╞█~   Y,┐
               ╞  ├▓▓▓▓▓▄▄__^^▓▓▓▌▓▓▓▓▓  ▓   /▓▓▓
                  ├▓▓▓▓▓▓▓▄▄═▄▓▓▓▓▓▓▓▓▓  π ⌐▄▓▓█║n
                _ ├▓▓▓▓▓▓▓▓▓~▓▓▓▓▓▓▓▓▓▓  ▄4▄▓▓▓██
                µ ├▓▓▓▓█▀█▓▓_▓▓███▓▓▓▓▓  ▓▓▓▓▓Ω4
                µ ├▓▀▀L   └ⁿ  ▀   ▀ ▓▓█w ▓▓▓▀ìⁿ
                ⌐ ├_                τ▀▓  Σ⌐└
                ~ ├▓▓  ▄  _     ╒  ┌▄▓▓  Γ
                  ├▓▓▓▌█═┴▓▄╒▀▄_▄▌═¢▓▓▓  ╚
               ⌠  ├▓▓▓▓▓ⁿ▄▓▓▓▓▓▓▓┐▄▓▓▓▓  └
               Ω_.└██▓▀ⁿÇⁿ▀▀▀▀▀▀█≡▀▀▀▀▀   µ
               ⁿ  .▄▄▓▓▓▓▄▄┌ ╖__▓_▄▄▄▄▄*Oⁿ
                 û▌├▓█▓▓▓██ⁿ ¡▓▓▓▓▓▓▓▓█▓╪
                 ╙Ω▀█ ▓██ⁿ    └█▀██▀▓█├█Å
                     ⁿⁿ             ⁿ ⁿ^
:::::::..  .,::::::    .,::      .::::::::..    :::.  .-:.     ::-.
;;;;'';;;; ;;;;''''    ';;;,  .,;; ;;;;'';;;;   ;;';;  ';;.   ;;;;'
 [[[,/[[['  [[cccc       '[[,,[['   [[[,/[[['  ,[[ '[[,  '[[,[[['
 $$$$$$c    $$""""        Y$$$Pcccc $$$$$$c   c$$$cc$$$c   c$$"
 888b "88bo,888oo,__    oP"''"Yo,   888b "88bo,888   888,,8P"'
 MMMM   "W" """"YUMMM,m"       "Mm, MMMM   "W" YMM   ""'mM"

INFO[0000] dialing /tmp/PPkSjDrrdNwImmOUdjtkxReVDMdRhCYW.sock
INFO[0000] created pid file, pid=7326
INFO[0000] initialized module instance                   address=tcp://:7979 id=1 ignoreFailOnInit=false typeId=1 typeName=AdminModule
INFO[0000] initialized module instance                   address=unix:///run/docker/plugins/rexray-remote.sock id=2 ignoreFailOnInit=true typeId=2 typeName=DockerRemoteVolumeDriverModule
INFO[0000] initialized module instance                   address=unix:///run/docker/plugins/rexray.sock id=3 ignoreFailOnInit=true typeId=3 typeName=DockerVolumeDriverModule
INFO[0000] started module                                address=tcp://:7979 id=1 typeId=1 typeName=AdminModule
INFO[0000] started module                                address=unix:///run/docker/plugins/rexray-remote.sock id=2 typeId=2 typeName=DockerRemoteVolumeDriverModule
INFO[0000] started module                                address=unix:///run/docker/plugins/rexray.sock id=3 typeId=3 typeName=DockerVolumeDriverModule
INFO[0000] service sent registered modules start signals
INFO[0000] service successfully initialized, waiting on stop signal
SUCESS!

  The REX-Ray daemon is now running at PID 7326. To
  shutdown the daemon execute the following command:

    sudo /usr/bin/rexray stop

root@ec2-54-219-167-85:/home/ubuntu# ls -laF /var/log/rex*

Btw the REXRAY_HoME is not set
On Monday, September 21, 2015, Schley Andrew Kutz<EMAIL_ADDRESS>wrote:

Hi @clintonskitson https://github.com/clintonskitson,
Also, when you started REX-Ray, was it configured? Did it actually start,
or did you receive a warning about missing storage driver configurations?
Because nothing is written to the log file until the service actually
starts. The CLI refuses to start the service if it's not configured per
your request (you wanted early errors).
—
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/79#issuecomment-142177147.

Hi @clintonskitson,
I hate Ubuntu... It's failing to log to the log file because you're starting it from a terminal instead of via the service scripts. Of course, this isn't your fault as I cannot even give you a way to start it via a non-term session in Upstart-hell. The SystemD infrastructure spawns services in non-term sessions so that this bit of code kicks in:
func startDaemon() {

	var out io.Writer = os.Stdout
	if !log.IsTerminal() {
		logFile, logFileErr := util.LogFile("rexray.log")
		failOnError(logFileErr)
		out = io.MultiWriter(os.Stdout, logFile)
	}
	log.SetOutput(out)

It turns out on Ubuntu no matter how a service is started, the file handle returned for stdout is a file descriptor with a terminal session attached.
SystemD on the other hand....
[0]akutz@poppy:rexray$ curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -

REX-Ray has been installed to /usr/bin/rexray

SemVer: 0.2.0-rc4
Binary: Linux-x86_64
Branch: v0.2.0-rc4
Commit: cc3eabe9e4d908def02168e0522db3c5e978d55d
Formed: Mon, 21 Sep 2015 10:17:02 CDT

[0]akutz@poppy:rexray$ sudo rm -fr /var/log/rexray

[0]akutz@poppy:rexray$ sudo systemctl start rexray

[0]akutz@poppy:rexray$ tail /var/log/rexray/rexray.log
 888b "88bo,888oo,__    oP"''"Yo,   888b "88bo,888   888,,8P"'
 MMMM   "W" """"YUMMM,m"       "Mm, MMMM   "W" YMM   ""'mM"

time="2015-09-21T23:33:17-05:00" level=info msg="created pid file, pid=2315"
time="2015-09-21T23:33:17-05:00" level=info msg="initialized module instance" address="tcp://:7979" id=1 ignoreFailOnInit=false typeId=1 typeName=AdminModule
time="2015-09-21T23:33:17-05:00" level=warning msg="ignoring initialization failure" error.message="no storage drivers initialized"
time="2015-09-21T23:33:17-05:00" level=warning msg="ignoring initialization failure" error.message="no storage drivers initialized"
time="2015-09-21T23:33:17-05:00" level=info msg="started module" address="tcp://:7979" id=1 typeId=1 typeName=AdminModule
time="2015-09-21T23:33:17-05:00" level=info msg="service sent registered modules start signals"
time="2015-09-21T23:33:17-05:00" level=info msg="service successfully initialized, waiting on stop signal"

[0]akutz@poppy:rexray$

I'll have to think on this as the reason I toggled the log file based on the presence of a detected TTY is because if a TTY is detected the logs get written with color codes. Also for permission reasons. A user executing REX-Ray may not have permissions to log to /var/log/rexray/rexray.log if the service created the file and the service created it as the root user.
Clearly I need to think on this a bit more.

Hi @clintonskitson,
However, this may be a bug with logrus. It always writes color codes, even to files, if stdout has a TTY attached. If a service cannot be started on a Linux without a TTY present (that is by a user), then that would imply that the logging subsystem would always write color codes to a file, making it nearly unreadable.
Do me a favor. Restart the box and see if the file gets created on boot. I'm wondering if on boot the session that starts the file won't have a TTY attached and thus actually create the file.

Same thing, no file or directory

Duh. Do this:
sudo rexray start 1> /dev/null
This will redirect the process's stdout descriptor to a non-term descriptor. I just tested it, it works. This makes sense as to why so many services echo status updates to stderr. They must have to to similar things when detecting whether or not stdout is a terminal descriptor or not.

Hi @clintonskitson,
I can whip up a fairly straight-forward fix in the morning that will make this work out of the box. I just need to stop redirecting the stdout descriptor of the secondary service process back to the primary process's own stdout descriptor as well as change any status messages to go to stderr.

PR #80 fixes this issue and has been merged. Please try again with latest build.

Hi @clintonskitson,
I tested it prior to the merge, but here it is end-to-end with the install-unstable script on Ubuntu 14.04:
[0]akutz@ubuntu:rexray$ sudo rm -fr /var/log/rexray

[0]akutz@ubuntu:rexray$ sudo curl -sSL https://dl.bintray.com/emccode/rexray/install-unstable | sh -
Selecting previously unselected package rexray.
(Reading database ... 65609 files and directories currently installed.)
Preparing to unpack rexray-latest-x86_64.deb ...
Unpacking rexray (0.2.0+rc5+19-1) ...
Setting up rexray (0.2.0+rc5+19-1) ...

REX-Ray has been installed to /usr/bin/rexray

SemVer: 0.2.0-rc5+19
Binary: Linux-x86_64
Branch: master
Commit: e795ef8f080dfe3c89462c2766aad05b40519324
Formed: Tue, 22 Sep 2015 00:29:27 CDT

[0]akutz@ubuntu:rexray$ sudo rexray start --force
Starting REX-Ray...SUCESS!

  The REX-Ray daemon is now running at PID 30472. To
  shutdown the daemon execute the following command:

    sudo /usr/bin/rexray stop

[0]akutz@ubuntu:rexray$ tail /var/log/rexray/rexray.log
 MMMM   "W" """"YUMMM,m"       "Mm, MMMM   "W" YMM   ""'mM"

time="2015-09-22T00:32:35-05:00" level=info msg="dialing /tmp/meVxKGoLjQtdHMSKaGRQyWHMXcSqQRLq.sock"
time="2015-09-22T00:32:35-05:00" level=info msg="created pid file, pid=30472"
time="2015-09-22T00:32:35-05:00" level=info msg="initialized module instance" address="tcp://:7979" id=1 ignoreFailOnInit=false typeId=1 typeName=AdminModule
time="2015-09-22T00:32:35-05:00" level=warning msg="ignoring initialization failure" error.message="no storage drivers initialized"
time="2015-09-22T00:32:35-05:00" level=warning msg="ignoring initialization failure" error.message="no storage drivers initialized"
time="2015-09-22T00:32:35-05:00" level=info msg="started module" address="tcp://:7979" id=1 typeId=1 typeName=AdminModule
time="2015-09-22T00:32:35-05:00" level=info msg="service sent registered modules start signals"
time="2015-09-22T00:32:35-05:00" level=info msg="service successfully initialized, waiting on stop signal"

[0]akutz@ubuntu:rexray$


Modify sysmon graphql api

Modify to use Networkfilter in sysmon raw event Graphql Api.
Added search sysmon event Graphql Api for sysmon supported by giganto.

Close: #512

Codecov Report
Patch coverage has no change and project coverage change: -0.37% :warning:

Comparison is base (1ca28c7) 53.73% compared to head (2c64bb4) 53.36%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #513      +/-   ##
==========================================
- Coverage   53.73%   53.36%   -0.37%
==========================================
  Files          23       23
  Lines        5207     5243      +36
==========================================
  Hits         2798     2798
- Misses       2409     2445      +36

Files Changed
Coverage Δ

src/graphql/network.rs
85.91% <ø> (ø)

src/graphql/sysmon.rs
0.00% <0.00%> (ø)

src/ingest/implement.rs
58.52% <ø> (+6.03%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add missing commits from dxWDL

https://github.com/dnanexus/dxWDL/commit/722cef57f9d44b111d0e0ac0e7fdbf93ca8e82b0
https://github.com/dnanexus/dxWDL/commit/4a0b33f7690ac6925867dbe622980af81392ca1a

Hmm, I don't see Yih-Chii's workflow added here: https://github.com/dnanexus/dxWDL/commit/4a0b33f7690ac6925867dbe622980af81392ca1a (and it's not used/compiled in tests).

@jdidion Thank you, I'll merge and cut a release.


[BC] Customcheckout error

I have just cloned the project and set my .env with BC then enabled customCheckout which display an error when clicking on checkout. See the picture bellow
TypeError: Cannot read properties of undefined (reading 'fetcher')

I am getting this error as well but using Swell provider

@Florian-crg I managed to get mine working but, you have to add the useCheckout hook to your provider.ts in the BC folder.
export const swellProvider: Provider & { swell: any } = {
  locale: 'en-us',
  cartCookie: SWELL_CHECKOUT_ID_COOKIE,
  swell,
  fetcher,
  cart: { useCart, useAddItem, useUpdateItem, useRemoveItem },
  customer: { useCustomer },
  products: { useSearch },
  checkout: { // Added this object and hook. You will have to fill in the logic for your provider
    useCheckout,
  },

  auth: { useLogin, useLogout, useSignup },
}

@ReevMich should do the same thing in the Shopify folder ? having the same issue

I don't think is possible to have a custom checkout out with BigCommerce.
In BigCommerce's checkout SDK docs they say that their Storefront Web API does not support CORS.
https://github.com/bigcommerce/checkout-sdk-js#cors
Unfortunately because next commerce is a headless solution I don't think you can use custom checkout with BigCommerce.

If you try the fix here https://github.com/vercel/commerce/issues/533#issuecomment-981149223 you only just get other errors further down the line. E.g. if you click into Payment Method, you get:
../packages/commerce/dist/utils/use-hook.js (24:0) @ useMutationHook

  22 | export function useMutationHook(hook) {
  23 |     const fetcher = useFetcher();
> 24 |     return hook.useHook({

You also get the same error for Shipping Method.
Getting the custom checkout to actually work therefore just feels like endless whack-a-mole.

Hi I have same error :
../packages/commerce/dist/utils/use-hook.js (24:0) @ useMutationHook

  22 | export function useMutationHook(hook) {
  23 |     const fetcher = useFetcher();
> 24 |     return hook.useHook({
  25 |         fetch: useCallback(({ input  } = {})=>{
  26 |             return hook.fetcher({
  27 |                 input,

+1

I wasn't able to resolve this, we abandoned Vercel Commerce and went down a different route.

up! I'm getting the same error trying to proceed checkout with shopify from the cart drawer

Same error

I think custom checkout only works with OrderCloud 😞

Having the same issues with Saleor. Did anyone fix this issue or finally implement their own custom checkout?

Same error using Shopify commerce

same issue with bigcommerce

Looks like all the hooks (useCheckout, useSubmitCheckout) for the checkout functionality are empty. Would anyone know if its something that is coming very soon, or something that we have to roll out ourselves?

i got same error and unable to solve it. If anyone has resolved so can you please tell me.

i got same error and unable to solve it. If anyone has resolved so can you please tell me. And i am using Next js storefront with vendure

Why this issue has not been solved or have idea to solve yet.

Why this issue has not been solved or have no idea to solve yet.

This would be amazing if this can be addressed. This is a really wonderful project and works great otherwise, its a shame this is holding it back

same issue with shopify

Same error getting with me

Hey there! Thank you for opening this issue. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: https://github.com/vercel/commerce/pull/966


live <= main

Docs Build status updates of commit d62da1a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/renee-noble.png
:white_check_mark:Succeeded
View

advocates/renee-noble.yml
:white_check_mark:Succeeded
View

advocates/steven-murawski.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix GFS cloud cover to irradiance processing for odd times, values

closes #144

codecov/patch test fails due to changes to the gfs_quarter_deg_3hour_to_hourly_mean function that has never been used or tested.

hopefully good now


Uncaught TypeError: switchEditors.switchto is not a function

Hey there, just downloaded this and got it working pretty quickly, so thanks for the example! I am having an issue when trying to switch back and forth between Text/Visual tabs on the editor:
Uncaught TypeError: switchEditors.switchto is not a function
It doesn't look like switchto() is a method in the switchEditors object any longer. Do you happen to know what I might be able to change this to in order to fix the toggling between these two tabs?

This is due to changes to the core in Wordpress 4.3+.
You need replace
onclick="switchEditors.switchto(this);"
to
data-wp-editor-id="'+current_id+'"
in the js-wp-editor js file.

Any reason this hasn't been merged in yet? Also possible to add a flag check for which version of WP is loaded and adding the correct output for each?

@danieliser
sorry, I should now have more time to spend on this lib.

@anteprimorac Awesome, I just pitched a new JS based modal, tab & form rendering set of templates, models & functionality to the core team. If that gets any momentum I think this would be a great inclusion.
Question on the enqueuing, couldn't you just do wp_editor('', 'apid');


Suddenly Leaves video [BUG]

Describe the bug
Im playing a live video, with the isLive = true and i allow the user to rotate the screen to resize the video. But even if i don't rotate de video suddenly the player leaves the video and shows youtube account page.
To Reproduce
Steps to reproduce the behavior:

Get any live video id, like SkyNews Live.
Use the videoId and set isLive to true.
Rotate OR just wait it to happen...

Expected behavior
The video should keep running or stop, no problem. But it just leaves...
Screenshots

Technical Details:

Device: iPhone 8
OS: iOS 13.4.1

Can you test with v7.0.0 ?

@sarbagyastha ok i will test it, thenks.


fix: update dependencies

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

v1.0.2
npm package (@latest dist-tag)
GitHub release
v1.0.2
v1.0.2

Your semantic-release bot :package::rocket:


Add developer environment setup script and fix symlink issues.

This diff adds a script after postinstall that sets up the dev environment using lerna. Once we move jest's source itself into a package, we can drop the custom calls to npm link.
Linking jest-util pointed out a symlink unmocking bug in Jest I've been meaning to fix for a long time. After running the setup script, Jest would not be able to mock chalk properly if jest-util was linked into Jest. It turns out we are calling fs.realpathSync. I think this was necessary with for node-haste1 support and is a leftover, however symlink unmocking was never properly supported then so I'm questioning why it was there in the first place.

@facebook-github-bot import

Note that travis will likely fail because I haven't pushed the version 9.0.3 of all packages yet. I'll do that before landing this diff.

@facebook-github-bot import


Solidify this repo

At last, the IPC codebase is in a monorepo -- and the build and CI both work! This issue tracks a bunch of follow-ups to solidify the structure and usage of this repo.
Repos cleanup

[ ] Archive and deprecate old repos, adding a note in the README pointing to the monorepo.

[ ] https://github.com/consensus-shipyard/fvm-utils
[ ] https://github.com/consensus-shipyard/ipc-solidity-actors
[ ] https://github.com/consensus-shipyard/ipc-ipld-resolver
[ ] https://github.com/consensus-shipyard/ipc (rename to ipc-libs first, to free up the ipc name)
[ ] https://github.com/consensus-shipyard/fendermint

[ ] Rename this repo to ipc.
[ ] Update the README of this repo.

Build and CI

[ ] Restore the correct name for the Fendermint Docker image (fendermint).
[ ] Port the Ganache test job from ipc-solidity-actors here: https://github.com/consensus-shipyard/ipc-solidity-actors/commit/bf36dba67ca30de03b5d671374bdb59cf27db6f6 (this got added last minute and was not integrated here).
[ ] Ensure we're using caching all throughout (except when publishing?).

Non-code reorg

[ ] Move infra scripts from inner modules to top-level /infra directory.
[ ] Move docs from inner modules to top-level /docs directory.

Code reorg

Here's a concrete code tree proposal, let's discuss in comments.

/
|__ infra
|__ docs
|__ contracts
|__ cli # binary crate containing the ipc cli
|
|__ ipc
|  |__ wallet # former ipc/identity; this is a wallet library containing keystores, key types, wallet, etc.; using the opportunity to adjust naming to be more descriptive
|  |__ provider
|  |__ api # former ipc/sdk; these contain external IPC API types; SDK tends to imply "developer SDK", which this isn't
|  |__ types # former fvm-utils/primitives; these contain basic types; some may move to ipld/types (e.g. Hamt, Cid, etc.)
|
|__ ipld
| |__ resolver # ipld-resolver
|
|__ fendermint
| |__ abci
| |__ app
| |__ crypto
| |__ ...
|
|__ testing # former ipc/testing, to be refactored later

Update infra scripts
Some infra scripts are outdated, e.g. the current ipc/scripts/install_infra.sh still clones fendermint. Need to figure these out in detail.

Test comment

types # former fvm-utils/primitives; these contain basic types; some may move to ipld/types (e.g. Hamt, Cid, etc.)

I agree that they aren't ipc specific. Where to put this was exactly my question when I first suggested this in https://github.com/filecoin-project/builtin-actors/issues/489
ipld/types sounds better to me, although we should clean up the error types to remove references to fil_actor_runtime, which was one of the reasons I never imported these, even though we could use it in fendermint_vm_actor_interfaces for example.

@raulk What do you mean with "Restore the correct name for the Fendermint Docker image"? Not sure I know exactly what that details

consensus-shipyard/ipc (rename to ipc-libs first, to free up the ipc name)

Note that this will break old issue referencing (i.e. if there's something in the new ipc-monoreporeferencingipc#21`, GH won't be able to redirect and will instead link to a wrong issue). I agree it's the right thing to do, mind you, just something to keep in mind. If we really wanted to preserve this, we should rewrite references first, but it's probably not worth it.
Unrelated: I also went ahead and closed the old GitHub projects, given the move to Linear.


Add htsget-http-aws-lambda HTTP backend

To integrate well with #62 and not require actix-web logic (more lightweight and better integrated for AWS lambdas).
Fixes issue #47

Deprecated by #76


Offers update but then says no update available

Version
Microsoft Windows [Version 10.0.22622.598]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Gives me a message that an update it available
Run  wsl.exe --update
Expected Behavior
Should update to latest version
Actual Behavior
A new WSL update is available. It can be installed by running: wsl.exe --update
➜  ~ wsl.exe --update
Checking for updates.
The most recent version of Windows Subsystem for Linux is already installed.
➜  ~ wsl.exe --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.819
Diagnostic Logs
No response

I have similar problem but a bit worse. I did not see the message A new WSL update is available. It can be installed by running: wsl.exe --update. I've checked for update in Microsoft Store several times but no luck.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.25236.1010

I was having the same problem.
My guess is this might happen if WSL2 was manually installed in the past, which is my case (but this is just a guess).
This was my version prior to the update:
❯  wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.25236.1010

I've fixed it by opening cmd or powershell and running:
wsl.exe --update --web-download

The --web-download option can be found when running wsl --help:
...
    --update
        Update the Windows Subsystem for Linux package.

        Options:
            --web-download
                Download the update from the internet instead of the Microsoft Store.
...

After doing that, here is the wsl --version output:
❯  wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.25236.1010

Having the same issue. Got the message while running ubuntu that wsl update is available. But wsl --update says latest version is already installed.
↪  ~ ➤ wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.819
↪  ~ ➤ wsl --update
Checking for updates.
The most recent version of Windows Subsystem for Linux is already installed.

@sarim, just follow the step above.
I've updated my comment by adding the FIX heading, hopefully making it clearer.


Paper cuts

hide date/time start/end radio button.

This is as far as we'll get with the paper-cuts. Will follow this up in phase 2 probably.


Package request: Safing.io

Project description
Portmaster is a free and open-source application firewall that does the heavy lifting for you. Restore privacy and take back control over all your computer's network activity.
Metadata

homepage URL: https://safing.io/
source URL: https://github.com/safing
license: mit, bsd, gpl2+ , ...
platforms: unix, linux, darwin, ...
other: https://wiki.safing.io/en/Portmaster/Install/Linux#manual-install-and-launching

Add a :+1: reaction to issues you find important.

Duplicate:
https://github.com/NixOS/nixpkgs/issues/242409
https://github.com/NixOS/nixpkgs/issues/227913
https://github.com/NixOS/nixpkgs/issues/174194
There is this PR which is still in draft:
https://github.com/NixOS/nixpkgs/pull/264454


feat: add new command gtctl connect mysql

The password is empty, just press enter and start mysql cli.

@zyy17 mysql has been down. If ok, i will add pg.

@sjcsjc123 You can change the PR status as ready for review.


Bootstrap 3.3.1

New bootstrap version has new html markup. Please update the plugin new bs version. thanks.

I won't be doing this at this time. This plugin was designed for BS2 and currently don't believe it is worth creating and maintaining two versions of this plugin as the BS3 modals address a lot of issues from the BS2 modal.


Terraform apply after changing max_pods_per_node does not take effect

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version

Terraform v1.4.2
Affected Resource(s)

oci_containerengine_node_pool
Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
# Please remove any sensitive information from configuration files before sharing them.

Debug Output

Panic Output

Expected Behavior

Using oke module, we wanted to change the value of max_pods_per_node from 110 to 15, after terraform apply it has to update this value on the  nodepool.
Actual Behavior

In terraform plan it shows that it needs to be updated, but after doing the apply, the node pool configuration does not get updated. When you do terraform plan again, it shows that the parameter has not changed.
Steps to Reproduce

terraform apply

Important Factoids

References

@shb-mll / @hyder / @devoncrouse - This looks like a provider bug. There's a similar issue opened here -https://github.com/oracle/terraform-provider-oci/issues/2011. The terraform apply for autoscaler_pool completes without actually changing the value for max_pods_per node but fails for oke-vm-standard pool.

Error: 409-Conflict, Cannot perform nodepool cycling and nodepool Placement Configuration change simultaneously.
│ Suggestion: The resource is in a conflicted state. Please retry again or contact support for help with service: Containerengine Node Pool
│ Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/containerengine_node_pool
│ API Reference: https://docs.oracle.com/iaas/api/#/en/containerengine/20180222/NodePool/UpdateNodePool
│ Request Target: PUT https://containerengine.us-ashburn-1.oci.oraclecloud.com/20180222/nodePools/ocid1.nodepool.oc1.iad.aaaaaaaaxxxxxx
│ Provider version: 5.25.0, released on . This provider is 15250 Update(s) behind to current.
│ Service: Containerengine Node Pool
│ Operation Name: UpdateNodePool
│ OPC request ID:
│
│
│   with module.oke.module.workers[0].oci_containerengine_node_pool.workers["oke-vm-standard"],
│   on .terraform/modules/oke/modules/workers/nodepools.tf line 5, in resource "oci_containerengine_node_pool" "workers":
│    5: resource "oci_containerengine_node_pool" "workers" {


add page icon

@harshita0802goswami this issue is already open #9.
Before opening any issue always make sure that no other similar issue is open.