Auto refresh imports (support %autoreload magic)

Or actually provide some way to make the kernel auto update when I change an external py file.
Suppose I have this:

I'm coding along and I realize I need to add something to matrix.py.
I don't want to go find the cell with the import. Just always reimport that matrix.py whenever I save it.

There was some talk of this previously. (like in #1248)

There was some talk of this previously. (like in #1248)

Well actually rerunning the first cell doesn't even work. Uggh. So this is even more important. I can't update the imports without restarting the kernel or using:
import importlib
importlib.reload(matrix)

Well actually rerunning the first cell doesn't even work. Uggh. So this is even more important. I can't update the imports without restarting the kernel or using:
import importlib
importlib.reload(matrix)

Not sure this works, well.
If i use from matrix import xyz, then such a solution will not work.
Also this is a destruction operation as we lost all informaiton loaded into the module.
Personally I'd just restart the kernel.

I don't want to lose the information already in the kernel. If the state of the kernel is the thing that's important to me, I can't iterate any longer.

But the module's state is not important. Especially if it's a set of functions I'm working on.
Jupyter has this already. It's called autoreload.
https://ipython.org/ipython-doc/3/config/extensions/autoreload.html

Would greatly improve workflows. I think we should add a button in UI to enable it.

Debugpy has implemented this already. We should be able to reuse that code.
https://github.com/microsoft/debugpy/blob/2ae7dc96ecc4ca73b119c2056284d203afa10afd/src/debugpy/_vendored/pydevd/pydevd.py#L677

@rchiodo yes, #5621 is somewhat related

This is a crucial feature for me.
I'm writing my own modules, run them into notebook. And if I want to reimport updated functions I either have to restart kernel, which makes no sense as I just want to update some functions from modules, but not to restart the kernal run from the beggining. Or use the hack @rchiodo suggested.
I think if we want to use VSCode instead default Jupyter Notebook or Jupyter Lab we should have this quite popular functionality. It's really annoying not to have it and break working flow just to restart kernel if you updated a single function in it.

Hmm, I thought I mentioned it here already.
You can put this in your runStartupCommands.
"jupyter.runStartupCommands": [
   "%load_ext autoreload"
   "%autoreload 2"
]

It's actually talked about here: https://github.com/microsoft/vscode-jupyter/issues/1542
That should cause modules to auto reload when they're written to disk. Make sure after you set the 'runStartupCommands' you reload VS code though.

a caveat I have experienced adding
"jupyter.runStartupCommands": [
   "%load_ext autoreload"
   "%autoreload 2"
]

is hanging jupyter cell execution, so much so I had to remove it

this would be very helpful😄

Duplicate of #1542


[tizen/dist] Update tizen packaging

Updated tizen packing spec file
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [x]Passed [ ]Failed [ ]Skipped

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #486. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/486-202008271616080.98117709159851-10113674b73fef4dbc3c69983eb42c612d1a4e61/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/486-202008281103410.68079400062561-641b2803b24d578be108c8ecab0db77ec5a6f43b/.


Shutdown

This PR deals with various issues found in a review of shutdown mechanics on JPype.  Previously we did not force a shutdown until an edge case in which a memory handler crashed during a load test.  Now that we are forcing a clean shutdown there are some robustness issues that need to be addressed.
Since some of the earliest releases of this project the shutdown process has been busted...
        // No idea why I can't find this symbol .... no matter, it does not work anyway.
        //JNI_DestroyJavaVM = (jint (__stdcall *)(struct JavaVM_ *))GetAdapter()->getSymbol("DestroyJavaVM");

The problem is that JPype is not working with the JVM to shutdown but trying to force the process.   The correct process is to ask for the JVM to shutdown and then wait for each of the Java threads to die, then use a shutdown hook to remove our resources.  But due to a number of flaws this process would deadlock leaving us with no choice but to simply halt the JVM.
This became an issue when we started running code coverage tools.   Those tools need the JVM to shutdown gracefully.   Thus it is now time to address this issue.
This PR fixes the following:

Threads that are attached automatically are now attached as daemon so that Python spawned threads will not stop a JVM shutdown unless explicitly attached to the JVM.
ShutdownJVM can only be called from the master thread.
Attaching Python routines to the Java shutdown using Runtime now works.

Those attached using JPype are called as part of the JPype shutdown sequence
Those attached using Java have a race condition so we have to try to force a race loss.
Any that fail the race will be given RuntimeError

The shutdown sequence now is called by the JVM once all but the master thread have been terminated.
As the shutdown is now internal to Java, a special flag has to be used to communicate with Python to inform when is the last time a Java method can be called.
A large number of deadlocks have been removed.
Jacoco now properly reports and no longer requires any special hooks.
Some special flags needed to be added to proxies to communicate state with the shutdown hooks.

This PR may produce some issues.  In the old version, we were yanking the plug on Python while Java was fully running thus there were no issues with Java.  But the consequence was that because Java was fully operational, things like timers and threads were still running and could potential crash the whole process.   Now we wait until Java is on its last leg before removing Python resources.  The process is more robust as the number of things that can happen are severely reduced, but by the same token our routines are have to be hardened to operate even when the whole place is about to blow down.
Fixes #678

@marscher I am not sure if this one addresses the bugs in Kotlin wrappers that was reported on Thrameos/jpype, but it seems like a necessary step for the next release.   Unfortunately we have a lot of PRs that change some fundamental (as well as trivial) things.  Thus we may want to try to gather up a current repo and run with it for a week before.
I am currently tracking two very difficult issues.   On a German version Visual Studio compiler a user is failing to start in the boot up sequence.  We have had a report like this before, but as it is purely a site issue it very hard to resolve.  Secondarily some users are discovering bugs released to the mandatory shutdown on exit.  The issues were always there but they are only now exposed.   I am not sure if either should hold up a release as we have some serious issues with the last release that need to be resolved.

This is a major improvement, as it gracefully shuts down the JVM and (parts?) of the C++ layer. I think we should carefully test this. Eventually we should provide some release candidates for 0.8 and ask big projects to give us feedback. I hope this will not delay the final release too much.
Lets begin and tag everything we want to have in 0.8 and mark the rest for another milestone. By this I mean a feature freeze (I like the proposal for the new cast operators etc., but as you said, it might be wiser to postpone it).

Sounds good.  I anticipated that we would do a release 0.7.3 shortly which would be the last with the deprecated functions rather than just jumping to 0.8 where we actually remove some bad stuff, but it is pretty muddy as we are sort of half way there.  I don't really want to stall 0.7.3 as 0.7.2 has a bad bug with Exceptions.  My customer is having a big issue with the memory exhaustion so I need to get a release to support them.
So one plan would be reapply just bug fixes starting from 0.7.2 and make a release 0.7.3 with minimal changes.  That way we buy a little time to settle issues for 0.8.  I am trying to get the documentation complete, but as I am writing I am turning up a lot of additional edge cases (Lists aren't sequences, null fails here, etc).  I did a very hard press in March but the doc review is turning up another round that needs to be dealt with.
Alternatively we can try to push to 0.8.0 and then we finalize the API at 0.8.1.  I am not much in favor of that.
Just point me which direction you would like and I will try to make it happen this weekend.

I just thought to do a minor since the shutdown thing really changes some behavior users might implicitly depend on (which would be horrible of course). A minor would at least indicate some braoder functionality changes.
But I can also see your need for a micro on 0.7. And the road to 0.8 seems more reasonable and should produce a more stable result. Is the change log file actually up to date?

I believe the changelog is mostly up to date.  I have been putting everything at user level in (though sometimes that is causing conflicts as most stuff is added at the end).  I should a scan of the PR to see if anything was missed.
How about we do a major/minor split using the change log?    If it seems like something should be held off we move it to the "next, next release" section and leave all the rest where they are.    That will give me a plan to issue the micro release.  I can then do one merge step and push a release candidate branch into place.
I think the shutdown behavior and the terminate should likely push to 0.8.

Using the changelog sounds like a good option as it reflects the users perspective.


feat: add recipe screens

👷 Deploy Preview for cooking-project processing.

Name
Link

🔨 Latest commit
6c884956143cd5edf246b5185fc7c9c093187b78

🔍 Latest deploy log
https://app.netlify.com/sites/cooking-project/deploys/632bb5f1728ccb0009850c84


Compilation fails on newer versions of Xcode

Describe the bug
With newer versions of Xcode, a newer version of clang is used, which results in a compilation error in Dependencies/SPIRV-Cross/spirv_common.hpp. Specifically, line 665 contains move(expr) which needs to be std::move(expr). This has already been fixed in SPIRV-Cross, so ideally we should just update to a newer commit that has this fix.
To Reproduce
Steps to reproduce the behavior:

Install the latest version of Xcode
Follow the steps in the README to build for iOS (probably repros for Mac too, but I haven't tried)

Expected behavior
Compilation succeeds.
Other

Platform: iOS

It is fixed, I linked the commit that it was fixed in above 🙂

@SergioRZMasson I think you updated the dependencies. Is this fixed?

This should be fixed!

Can you link to the PR and close this issue?


Pouring large bottles uses lots of memory

Checklist

[X] ran brew update and can still reproduce the problem?
[X] ran brew doctor, fixed all issues and can still reproduce the problem?
[X] ran brew config and brew doctor and included their output with your issue?

Problem
This has been happening for at least a year.
I just ran brew upgrade llvm and it took well over 30 minutes. The Ruby process repeatedly bloated to 3GB and unbloated down to 0.5GB. This made the computer swap very hard and rendered the system completely unusable, except during the unbloats where I could check the Activity Monitor.
By contrast, I can untar the bottle manually in 4 minutes and 1.2 MB RAM:

Command output
$ time -l tar -xf ~/Library/Caches/Homebrew/llvm--9.0.0_1.catalina.bottle.tar.gz
      224.38 real        16.45 user         7.09 sys
   1228800  maximum resident set size
         0  average shared memory size
         0  average unshared data size
         0  average unshared stack size
       358  page reclaims
         4  page faults
         0  swaps
         0  block input operations
         0  block output operations
         0  messages sent
         0  messages received
         0  signals received
      5182  voluntary context switches
     65349  involuntary context switches

This doesn't happen with small bottles, even when brew upgrade pours a bunch of small bottles in a row.
I'm using a case-sensitive APFS volume.
Now, this is a 2012 MacBook without SSD and with 4GB RAM. But the whole bottle is also only 1.2GB packed and 3.8GB unpacked. I expect that, if this also happens on other systems, fixing it would make upgrades noticeably faster.
brew doctor and config

doctor
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: The filesystem on /System/Volumes/Data appears to be case-sensitive.
The default macOS filesystem is case-insensitive. Please report any apparent problems.

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
<EMAIL_ADDRESS>
Warning: Homebrew's sbin was not found in your PATH but you have installed formulae that put executables in /usr/local/sbin.
Consider setting the PATH for example like so:
  echo 'set -g fish_user_paths "/usr/local/sbin" $fish_user_paths' >> ~/.config/fish/config.fish

config
$ brew config
HOMEBREW_VERSION: 2.1.16
ORIGIN: https://github.com/Homebrew/brew
HEAD: 3aa7624284c43180a3f3a71aeaa9263092868e12
Last commit: 2 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0c5930b3e5dd9bc366924a2d7a99acc6b55d77d9
Core tap last commit: 3 hours ago
HOMEBREW_PREFIX: /usr/local
CPU: quad-core 64-bit ivybridge
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1100
Git: 2.24.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 12
macOS: 10.15.1-x86_64
CLT: <IP_ADDRESS>.1.1567737322
Xcode: N/A
CLT headers: <IP_ADDRESS>.1.1567737322

Memory is there to be used. An algorithm using less memory will be slower. This may be related to your case-sensitive filesystem. We can talk more about this if you provide the full output of a slow brew upgrade run (with annotations about where is slow) but we don't consider large memory usage to be a bug.

Okay!
$ brew remove llvm
Uninstalling /usr/local/Cellar/llvm/9.0.0_1... (6,839 files, 3.7GB)
$ rm -r ~/Library/Caches/Homebrew
$ brew install llvm
Updating Homebrew...
==> Downloading https://homebrew.bintray.com/bottles/llvm-9.0.0_1.catalina.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/a8/a8e2475a1fc5a81f0da83a73d17fd54cc2a686f
######################################################################## 100.0%

Everything is fine so far. Then:
==> Pouring llvm-9.0.0_1.catalina.bottle.tar.gz

I turned on a stopwatch when this line appeared. Times are (minutes:seconds).

00:00. Nothing interesting is happening. There's some cp process that's handling about 4GB on disk but I don't know what it's doing.
13:31. Suddenly the Ruby process increases steadily to 1GB of RAM. It climbs slowly until…
14:48. It rises quickly to 3.2GB of RAM. The Activity Monitor stops responding to keypresses. The window manager freezes. The pointer is a spinning ball. The computer is now useless.
18:12. The computer unfreezes. There's about 2.5GB in swap memory. The Ruby process drops back to 0.5GB but quickly climbs back to 1GB. It holds steady.
22:18. The Ruby process rises quickly to 3.2GB. The computer completely freezes again.
26:08. The computer unfreezes. The Ruby process drops to 0.5GB, then grows to 1GB and holds steady.
29:38. The computer freezes again.
32:58. The computer unfreezes.
34:08. The computer freezes.
37:01. The computer unfreezes and…

==> Caveats
To use the bundled libc++ please add the following LDFLAGS:
  LDFLAGS="-L/usr/local/opt/llvm/lib -Wl,-rpath,/usr/local/opt/llvm/lib"

llvm is keg-only, which means it was not symlinked into /usr/local,
because macOS already provides this software and installing another version in
parallel can cause all kinds of trouble.

If you need to have llvm first in your PATH run:
  echo 'set -g fish_user_paths "/usr/local/opt/llvm/bin" $fish_user_paths' >> ~/.config/fish/config.fish

For compilers to find llvm you may need to set:
  set -gx LDFLAGS "-L/usr/local/opt/llvm/lib"
  set -gx CPPFLAGS "-I/usr/local/opt/llvm/include"

==> Summary
🍺  /usr/local/Cellar/llvm/9.0.0_1: 6,839 files, 3.7GB
$

A few minutes later we've unswapped most of the memory and have a normal system again.

I know this isn't much to go on, but it's reproducible. And since it happens between "Pouring…" and "Caveats…" we're not even looking at the whole code base.
I'm hoping this happens on other systems. Specifically, I'm hoping that, when brew install llvm pours llvm-9.0.0_1.catalina.bottle.tar.gz, the Ruby process often uses 3GB of RAM. I would expect the freezing on my machine given that RAM usage fluctuates between 0.5GB and 3.2GB. I would also expect that other machines with more RAM do not freeze, and machines with an SSD and 4GB RAM swap so quickly that you can't notice.

For future reference pasting the full, continuous output would be more helpful. brew install moreutils and piping to ts will provide a timestamp on each line which would be helpful for debugging.

I'm hoping this happens on other systems.

I'm afraid we've not had any other reports of this. It takes 1m15s to extract on my fairly fast SSD so it's unfortunately unsurprising it may take a much longer time on a non-SSD. I'm open to a pull request that makes this better but I'm afraid this probably needs filed under "modern macOS experience on a non-SSD is terrible" for now, sorry.


Explain the six-week release cadence

I've mentioned that I want Capistrano to use a six-week release cadence. Any objections to making this "official policy" by mentioning it in the changelog?
I chose six weeks because I think it strikes a good balance:

Often enough that contributions are regularly published
Not too often that users are overwhelmed trying to keep up with new versions

I also prefer a regular schedule (as opposed to "release whenever it's ready") because:

Contributors know when their code will be published
It encourages stability in master (since a release is always imminent)
A steady project "heartbeat" keeps the community interested and involved

/cc @will-in-wi @leehambley

No objections, I like the idea and think more projects should do it.
Am 19.02.2017 23:22 schrieb "Matt Brictson"<EMAIL_ADDRESS>
I've mentioned that I want Capistrano to use a six-week release cadence.
Any objections to making this "official policy" by mentioning it in the
changelog?
I chose six weeks because I think it strikes a good balance:

Often enough that contributions are regularly published
Not too often that users are overwhelmed trying to keep up with new
versions

I also prefer a regular schedule (as opposed to "release whenever it's
ready") because:

Contributors know when their code will be published
It encourages stability in master (since a release is always
imminent)
A steady project "heartbeat" keeps the community interested and
involved

/cc @will-in-wi https://github.com/will-in-wi @leehambley
https://github.com/leehambley
You can view, comment on, or merge this pull request online at:
https://github.com/capistrano/capistrano/pull/1853
Commit Summary

Explain the six-week release cadence

File Changes

M CHANGELOG.md
https://github.com/capistrano/capistrano/pull/1853/files#diff-0 (8)

Patch Links:

https://github.com/capistrano/capistrano/pull/1853.patch
https://github.com/capistrano/capistrano/pull/1853.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/capistrano/capistrano/pull/1853, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABKCGEbfCUAKUQLLiatHBMOdY88EQHVks5reMCzgaJpZM4MFnfV
.

This makes a ton of sense to me, and seems to be a good balance of not too much work, and getting fixes out in a timely manner.


duplicate task invocations

Sometimes when a workflow is invoked once, some of the tasks are invoked more than once.
(Sorry, I don't have more info right now.)

Hello,
OK so the workflow log from the pod is: http://pastebin.ubuntu.com/25932155/
the router log is :
router-2379729970-gqvs1 router 2017/11/10 14:10:34 Proxying request for /storm-surge to <IP_ADDRESS>:8888
router-2379729970-gqvs1 router <IP_ADDRESS> - - [10/Nov/2017:14:10:34 +0000] "POST /storm-surge HTTP/1.1" 200 259

and the workflow source is :

apiVersion: 1
description: Storm Surge Claim workflow with Weather Risk
output: CreateTicket
# Input: 'Type Form JSON Output Data'
tasks:
  # Capture TYPE FORM Req and transform for Zen Desk
  TransformData:
    run: form-req-transformer
    inputs: "{$.Invocation.Inputs.default}"

  # GET Weather Data
  GetWeatherData:
    run: weather-data
    inputs: "{$.Tasks.TransformData.Output.weatherAPIInput}"
    requires:
    - TransformData

  # Compute Weather Risk
  ComputeWeatherRisk:
    run: compute-weather-risk
    inputs: "{$.Tasks.GetWeatherData.Output}"
    requires:
    - GetWeatherData

  ComposeResult:
    run: compose
    inputs:
      tranformedData: "{$.Tasks.TransformData.Output}"
      weatherData: "{$.Tasks.GetWeatherData.Output}"
      weatherRisk: "{$.Tasks.ComputeWeatherRisk.Output}"
    requires:
    - ComputeWeatherRisk
    - GetWeatherData
    - TransformData

    # Update risk data before creating ticket
  UpdateRiskData:
    run: add-risk-data
    inputs: "{$.Tasks.ComposeResult.Output}"
    requires:
    - ComposeResult

    # Create Fresh Desk Ticket
  CreateTicket:
    run: register-ticket
    inputs: "{$.Tasks.UpdateRiskData.Output}"
    requires:
    - UpdateRiskData

The behavior I expect:
input:  curl -X POST -H 'Content application/json' -d @jsonPayload http://FISSIONROUTER/storm-surge
output: creation of a single output
What happens (everytime): creation of 2 to 5 outputs with similar content
Especially, I believe the ComposeResult is triggered or triggers the next steps several times. But it is a feeling, no data to back it up yet.
Let me know if you need anything else.

Hi @soamvasani @SaMnCo -- thanks for the logs, they really helped. After investigating it, I found that there is a concurrency issue in the invocation controller. If tasks are not finished fast enough, the controller will re-submit the task based on an evaluation of the old state of the workflow invocation. Currently writing a fix for it :)

Great. We are seeing this more and more as we have more use cases and also
we are now implementing Selenium testing for the UX part, so the system
runs a lot more than before. Let us know if you want us to test early
builds, no problem.
Best,
Sam
On Tue, Nov 21, 2017 at 7:14 PM, Erwin van Eyk<EMAIL_ADDRESS>wrote:

Hi @soamvasani https://github.com/soamvasani @SaMnCo
https://github.com/samnco -- thanks for the logs, they really helped.
After investigating it, I found that there is a concurrency issue in the
invocation controller. If tasks are not finished fast enough, the
controller will re-submit the task based on an evaluation of the old state
of the workflow invocation. Currently writing a fix for it :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fission/fission-workflows/issues/77#issuecomment-346114253,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACN4dxonpNlMJoH3FUkYLzcVzmAqRiL7ks5s4xMLgaJpZM4QTmYb
.

--
SaM'n'Co
R'U Ready? I was BORN ready!

Any updates on this issue, @erwinvaneyk ?

So, I thought I found it, but it turned out that I actually already had mechanisms in place for the case I described. It is weird because I can't seem to reproduce it on my own machine. Given the many changes since v0.1.0 (which I am assuming this setup uses), it might already have been resolved.
In any case, I am working on a PR to improve the logging and concurrency to mainly address this kind of issue: https://github.com/fission/fission-workflows/pull/93

@erwinvaneyk Let's first find out whether it's resolved or not. Can you do the following:

Try to repro this case yourself on 0.1.1. If you can't, ask @SaMnCo for more info. Whatever is happening here is a good test case for us to add.
Once you can repro on 0.1.1, see if you can repro on master branch.

Where are we on this @erwinvaneyk ?

Oh this has been fixed in #93


Work around for dart-lang/sdk#28599

Also includes some TODO clean-up.

LGTM

LGTM.

Coverage decreased (-0.7%) to 81.055% when pulling f0ac6137674ad2532f282b999f179aaee58b7399 on goderbauer:winLogger into 236e8137b84a5231480d584c7a4bc1da23b4cffd on flutter:master.


feat: add support for correct an old packet then trace retransmission

I will change how we use the commands, flag middlebox, etc. But it seems good for now.


Same Code  between demo_two_stream.py and main_create_training_set.py

HI @LarryJiang134 , I found the 2 files contains the same code, I guess you upload the wrong main_create_training_set.py as it is supposed to generate some new training images.

fixed


dispose() under-specified for ImageBuffer, ImageDescriptor, ImmutableBuffer

Ref:  https://github.com/flutter/flutter/issues/83764
The spec bug is still unresolved.  That is, it is not specified that:

Users of this API shall ImageBuffer.dispose() after handing the buffer off to the descriptor
Users of this API shall not call ImageBuffer.dispose() until the descriptor is not being used
After instantiating a codec with instantiateCodec(), Users of this API shall not call ImageDescriptor.dispose() until the codec is no longer being used

It really is essential to specify these behaviors.  You can find a good example of the kind of specification text that would be appropriate at https://api.flutter.dev/flutter/dart-ui/Codec/getNextFrame.html

@zathras
As mentioned https://github.com/flutter/flutter/issues/83764#issuecomment-853306419,  please comment on the issue and cc


[Change Request] page 769 "Aged Acc. Payable Chart" procedure UpdateChartForVendor()

Would it be possible to make this procedure available for SaaS versions too?
[Scope('OnPrem')]
procedure UpdateChartForVendor(NewVendorNo: Code[20])
begin
    if not IsVisible then
        exit;

    VendorNo := NewVendorNo;
    UpdateChart();
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11415.


Code Coverage - Branch is reported as not covered

Istanbul reported is reporting this branch is not covered, however, it's clear that it is.
Using typeof (underscore is not the issue).

You can see by the number of calls the branch is covered.
FYI: I ended up using _.isObject( )

Don't know if it's related, but I'm getting missed branches too. Apologies in advance for the CoffeeScript:
getPasswordHash = (password) ->
  new Promise (resolve, reject) ->
    bcrypt.genSalt 10, (err, salt) ->
      return reject(err) if err
      bcrypt.hash password, salt, (err, hash) ->
        return reject(err) if err
        resolve(hash)

I've used rewire to mock crypto and bcrypt and they're still marked as not taking the if path, even though I know they do because I've mocked them deliberately, and the promise is getting correctly rejected, which cannot happen unless an if branch is followed.


keeps redirecting to restsocialexaple.com:8000 with my own facebook keys

Hi,
Is there something I need to change to change this behaviour ? Please help.
I am using my own key and secret within my own app but after accepting facebook permissions or even when cancelling the process it keeps me redirecting to restsocialexample. Please let me know what needs to be changed and where,
Thanks a lot.
Jatinder

Hi jassi,
please tell, what url your server is running at?
By default, django-rest-social-auth will take current server url and use it for redirect.

Hey,
Thanks for replying. I looked everywhere but in the html file that's where it was getting redirected to your example url on the last script. I changed it and it worked.
Cheers
Jatinder
-----Original Message-----
From: "Alexey Evseev"<EMAIL_ADDRESS>Sent: 28-09-2015 01:14 AM
To: "st4lk/django-rest-social-auth"<EMAIL_ADDRESS>Cc: "jassi5887"<EMAIL_ADDRESS>Subject: Re: [django-rest-social-auth] keeps redirecting torestsocialexaple.com:8000 with my own facebook keys (#1)
Hi jassi,
please tell, what url your server is running at?
By default, django-rest-social-auth will take current server url and use it for redirect.
—
Reply to this email directly or view it on GitHub.


Card Price

With the game launching soon, would a card "price" property be something possible, with the cheapest offer of the card in the marketplace? 🤔

This still works for other games, not sure if Artifact's market place will be different.
http://steamcommunity.com/market/priceoverview/?appid=730&currency=3&market_hash_name=StatTrak™ M4A1-S | Hyper Beast (Minimal Wear)
{"success":true,"lowest_price":"42,18\u20ac","volume":"5","median_price":"39,43\u20ac"}

There will be a market api available when the market is available to use.  The README will be updated at that time.


JAVA solution to issue 389

Description
JAVA solution to issue 389
Fixes #389
Replace issue_no with the issue number which is fixed in this PR
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@TasnimAnas remove other files

@Amit366 check now.


Cannot open DB Error: java.lang.NumberFormatException: For input string: ""

OrientDB Version: v3.0.0
Java Version: 1.8.0_151
OS: Docker Image for v3.0.0 (Alpine Linux v3.7)
Expected behavior
Connect to DB
Actual behavior
orientdb {server=remote:localhost/sierralabs_db}> connect remote:localhost/sierralabs_db root
Enter password:

Connecting to database [remote:localhost/sierralabs_db] with user 'root'...
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database 'sierralabs_db'

Error: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database 'sierralabs_db'

Error: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database url=plocal:/orientdb/databases/sierralabs_db

Error: java.lang.NumberFormatException: For input string: ""

Steps to reproduce
I don't have the exact steps but I can attach the DB file. Basically, I just created a new DB and created a few Vertices and Edges with inheritance. I started added some string properties on a couple of vertices, marking them are mandatory and not null, I got an error Error: java.lang.NumberFormatException: For input string: "". Then after that I couldn't add any more properties without getting the same error, though it seemed like the property is created if I do hard refresh of the page. I tried logging out of studio and restarting my docker instance, then tried to sign in again using studio but could not log on to the same database again, I guarantee that I have the right credentials since I can log on to other databases. I tried using the console and same thing happens (shown above)

@csapinoso I suppose you incorrectly set empty max value or maybe Studio set this value for you. Sure those cases should be correctly handled. I have provided a quick and dirty fix so you can build develop branch and work with the database.  Assigned to @tglman .

That makes sense, I think before the issue started I was able to create a property called index of type Integer, I set the minimum value to zero because wanted only positive integers but did not specify a max value. Studio allowed it though, I supposed it should have been validated in the front end and backend if that would have caused an exception. In this case, it made my entire DB unusable. Is there a way to recover from this?

@csapinoso I have already provided the fix if you build a distribution from the develop branch using mvn clean package -DskipTests


Tensorflow Error

After upgrading Rasa to 1.8.1 I can no loner use my forms. I keep on getting this error:
tensorflow/core/kernels/data/generator_dataset_op.cc:103] Error occurred when finalizing GeneratorDataset iterator: Cancelled: Operation was cancelled

Thanks for the issue, @amn41 will get back to you about it soon!
You may find help in the docs and the forum, too 🤗


Sign Release Mac Binary

When launching a user receives the error
“Electrum-Ravencoin” can’t be opened because it is from an unidentified developer.

There is a work around. However, best practice is to sign these binaries.

Will look into this

please let me know if i can be of any help

I think I'll wait until v1.0.0 (when I expect to add everything ravencoin related) before paying apple to verify these binaries. I'll also ask the ravencoin foundation about being able to use the same keys as the upcoming p2sh release (in which case I'll make a signed release sooner)

Someone is graciously letting me use their Developer ID to sign these electrum binaries, so I should have a signed v<IP_ADDRESS> sooner rather than later. Currently the app can be run from anywhere, however -- for whatever reason -- the app inside of the dmg is failing to be run on other machines because of an internal PyInstaller error (it can be run from the DMG on the machine that built it, it's weird). Just wanted to give you an update.

DMGs just don't work on other macs now, so this will have to wait

https://github.com/Electrum-RVN-SIG/electrum-ravencoin/releases/tag/v0.4.6


Added users option to choose a custom channel in their server

Added a command cv!channel args that allows users to choose a custom channel for the bot to send notifications in.

Merged into feature/select-channel


cronjob: fix TypeError in getSchedule()

Fix an white screen at pressing "workloads->cronjobs" button
I found a bug in Headlamp app v0.2.1 & 0.3.0-beta: when you click on "workloads->cronjobs" button in a cluster that do have an cronjobs, you got an empty white screen. I investigated into this problem and found that frontend got TypeError after pressing the button. This patch should fix it.
Testing done
I test it by hands with the same cluster, where the bug occurs, now it should work fine

Good catch! Merged.
Thanks for the patch!


Couldn't fetch parent branch

Hello
I have met, as many others, an issue with deleted or renamed branches (using git-tfs 0.32.0).
v3.1/v3.1.1 is now a folder that contains branches ; there are deleted branches and probably renamed branches too.
I wonder if there is a command to resume the clone without this precise branch (loosing a bit of history).
Do you have an easy way to recover such kind of errors with manual commands?
Ex: ignore parent branch.
Ex: I could lie to the system and say v3.1/v3.1.1 branch is the same as v3.0 or something like that.
However, if I rename a branch via git tfs branch --move v3.0 v3.1/v3.1.1, it is not detected by next git branch --init=OTHER_BRANCH.
I also tried to git tfs init old deleted branches or git branch --init  with --tfs-parent-branch but it seems to be ignored.
- $/Project/v3.1/v3.1.1/b3.1.1
   =>error:error: TFS branches $/Project/v3.1/v3.1.1 not found!
- $/Project/v3.1/v3.1.2/b3.1.2
   =>error:error: Couldn't fetch parent branch
- $/Project/v3.1/v3.1.1/b<IP_ADDRESS>
   =>error:error: TFS branches $/Project/v3.1/v3.1.1 not found!
- $/Project/v3.1/v3.1.1/b<IP_ADDRESS>
   =>error:error: TFS branches $/Project/v3.1/v3.1.1 not found!

2021-03-23 15:02:41.6007 [Debug] Looking for changeset 1012 in git repository...
2021-03-23 15:02:41.6053 [Debug] Looking for changeset 1012 in git repository: CacheIsFull, stopped looking.
2021-03-23 15:02:41.6053 [Debug] Looking for root changeset tree on $/Project/v3.1/v3.1.1/b3.1.1
2021-03-23 15:02:41.6213 [Debug] Looking for root changeset for branch:$/Project/v3.1/v3.1.1/b3.1.1
2021-03-23 15:02:41.6213 [Debug] Looking to find branch '$/Project/v3.1/v3.1.1/b3.1.1' in all TFS branches...
2021-03-23 15:02:41.6213 [Debug] Found parent branch : $/Project/MainBranch
2021-03-23 15:02:42.3289 [Debug] Merge: `Delete, SourceRename` C1010 `$/Project/v3.1/b3.1.1` Source `Rename` C1010 `$/Project/v3.1/v3.1.1/b3.1.1`
2021-03-23 15:02:42.3289 [Debug] Found C1010 on branch $/Project/v3.1/b3.1.1
2021-03-23 15:02:42.3369 [Debug] Found original branch '$/Project/v3.1/b3.1.1' (renamed in branch '$/Project/v3.1/v3.1.1/b3.1.1')
2021-03-23 15:02:42.3369 [Debug] Looking for root changeset for branch:$/Project/v3.1/b3.1.1
2021-03-23 15:02:42.3369 [Debug] Looking to find branch '$/Project/v3.1/b3.1.1' in all TFS branches...
2021-03-23 15:02:42.3369 [Debug] Found parent branch : $/Project/MainBranch
2021-03-23 15:02:42.9512 [Debug] Merge: `Add, Encoding` C1007 `$/Project/v3.1/v3.1.1` Source `Delete, SourceRename` C1007 `$/Project/v3.1/b3.1.1`
2021-03-23 15:02:42.9512 [Debug] Found C1007 on branch $/Project/v3.1/v3.1.1
2021-03-23 15:02:42.9642 [Debug] Found original branch '$/Project/v3.1/v3.1.1' (renamed in branch '$/Project/v3.1/b3.1.1')
2021-03-23 15:02:42.9642 [Debug] Looking for root changeset for branch:$/Project/v3.1/v3.1.1
2021-03-23 15:02:42.9642 [Debug] Looking to find branch '$/Project/v3.1/v3.1.1' in all TFS branches...
2021-03-23 15:02:42.9642 [Debug] Cleaning...
2021-03-23 15:02:42.9781 [Debug] Cleaning...
2021-03-23 15:02:42.9781 [Debug] Getting changeset fetch failed: error: TFS branches $/Project/v3.1/v3.1.1 not found!
2021-03-23 15:02:42.9781 [Debug] Getting changeset fetch failed: error: TFS branches $/Project/v3.1/v3.1.1 not found!
2021-03-23 15:02:42.9781 [Debug] Getting changeset fetch failed: error: TFS branches $/Project/v3.1/v3.1.1 not found!

In the past, I did use the workaround and specified only the branches I am interested explicietly to get past some errors.
As this was a very long time ago, I do not remember the details anymore, but I still had some scripts
which preserved the logic from the past.
MSYS_NO_PATHCONV=1 git tfs init https://your.server.com/tfs $/Some/project/Main clone
cd clone
git config git-tfs.ignore-branches false
git config git-tfs.ignore-not-init-branches true

# Do these two steps for every branch you are interested in
MSYS_NO_PATHCONV=1 git config tfs-remote.Some/project/Dev/BranchA.url             https://your.server.com/tfs
MSYS_NO_PATHCONV=1 git config tfs-remote.Some/project/Dev/BranchA.repository $/Some/project/Dev/BranchA

# Start the fetch and ignore any not yet initialized branch
MSYS_NO_PATHCONV=1 git tfs fetch -i tfs/default --ignore-restricted-changesets --ignore-not-init-branches --all

This is from the top of my head what I would try, but no garantuees that it actually works:
Remove the TFS branch config (or uncomment) from your .git/config and try if fetching with --ignore-not-init-branches --all gets you passed the problematic changesets. Then abort the fetch via CTRL+C and re-start the fetch again, but this time
without the parameter --ignore-not-init-branches so that other branches can still be detected

Hello, thanks a lot for your answer.
It is still in progress, but seems promising.
Here is what I did. Branch v3.1.1 does not exist anymore.
With git tfs list-remote-branches, I saw that all main branches have been pulled from MainBranch ; v3.1.1 is not very important though it has been used in multiple merges.
b3.1.1 is the first branch that has been pulled from v3.1.1 ; I searched for its first commit (1024).
Then:
$DEBUT=(Get-Date); git tfs clone --branches=all --gitignore="D:\.gittfsignore" https://my-tfs-server/Team $/Project/MainBranch . ; $FIN=(Get-Date); 'Temps écoulé : {0}' -f ($Fin-$Debut).totalhours

backup

git config tfs-remote.b3.1.1.url        "https://my-tfs-server"
git config tfs-remote.b3.1.1.repository "$/Project/b3.1.1"
git config tfs-remote.b3.1.1.gitignore-path "D:\.gittfsignore"
=> check in .git/config that everything is correct
git tfs fetch --up-to=1024 --ignore-restricted-changesets --ignore-not-init-branches --all --gitignore="D:\.gittfsignore"
=> Stops automatically on commit C1024 : "Fetching from TFS remote 'Product/b3.1.1'"...

backup

git config git-tfs.ignore-not-init-branches false
$DEBUT=(Get-Date); git tfs fetch --all --gitignore="D:\.gittfsignore"; $FIN=(Get-Date); 'Temps écoulé : {0}' -f ($Fin-$Debut).totalhours

Yesterday process went well.
I see many time this kind of log in git tfs fetch output :
Looking for changeset 3254 in git repository: CacheIsFull, stopped looking.
Is this an error ?
git tfs fetch did not clone branches not yet merged in master
I am running git tfs clone --resumable --branches=all --gitignore... to get them.
I thought about git tfs branch init --all but it doesn't have a --gitignore switch. Maybe it should be added ?
However I'm surprised because in .git/config, git tfs clone --resumable creates missing remote branches without filling gitignore parameter.

Thanks for you support, I managed to migrate the tfs repository thanks to you.
Little improvements can be done to Git-tfs:

Add --gitignore switch to git tfs branch init
git tfs clone --resumable should write gitignore in newly created .git/config branches

Thx for your improvement suggestions.
For others stumbling on this issue, care to elaborate how you finally solved your missing/not imported parent problem?

Yes, I explained it above. Here is a summary:

git tfs clone --branches=all --gitignore "....." SERVER
Add problematic branch manually (via git config or edit .git/config)
Find problematic branch creation changeset in TFS history (first changeset of the branch) => YYY
I had to add 4 more changesets to make it work (why?)
git tfs fetch --up-to=YYY --ignore-restricted-changesets --ignore-not-init-branches --all --gitignore "....."
git config git-tfs.ignore-not-init-branches false
git tfs fetch --all --gitignore="......"
git tfs clone --resumable --branches=all --gitignore...

I was not able to recover 4 branches, but it represents 0.00001% of the codebase.

@nmoreaud: Thanks, the explanation is appreciated!


Generated shellcode does not work with shellcode runners

Hi, I perform pentesting and I need to write my own binaries in C to avoid detection like Metasploit payloads and so on.
But when I generate shellcode with donut from these EXE binaries they don't work with my loaders and droppers.
for example shellcode runner.
Any help guys?

What branch of donut are you using?

master

Some of shellcodes I generated crash the injected process when I perform injection.

Try using dev branch.

Just checking in. Any differences with dev?

Sorry for being late, I didn't check my account
Actually it worked with raw binary shellcode, and in my loader I loaded the shellcode from resource section
and also tested with base64 and worked
but in C format did not work maybe my loader In C format not correct
Thank you guys.

Good to hear. I'll keep this Issue open for now as a reminder to check the C formatted output

Checked on my side and it works for me. I'll close this for now unless somebody else has issues.


Automatic translation of attribute values

Currently show_for looks up the value in the following order as described in the README

use the output of a block argument if given
use the output of the :value argument if given
check if a :"human_#{attribute}" method is defined
retrieve the attribute directly.

According to the docs at http://guides.rubyonrails.org/i18n.html#translations-for-active-record-models in order to translate the attribute values using model.human_attribute_name you can do
en:
  activerecord:
    attributes:
      user:
        gender: "Gender"
        gender/female: "Female"
        gender/male: "Male"

and then you can use User.human_attribute_name("gender.female") to return "Female".
It would be nice if show_for could add another look up in that it will automatically return model.human_attribute_name(attribute.value) if it's translated.
Let me know if this is something that you would merge in and i'll open a PR.
Cheers

Why was this closed?


Unrecognized architecture 'aie'

I have setup all the tools for the first time and can get pretty far.  However, when I try to compile any of the examples it complains about unrecognized architecture 'aie'.
What did I miss in my setup or is this a new bug?
I just cloned this repo earlier today, I have built up to commit 8ea962ad.  Using Ubuntu 20.04LTS & v2021.2 tools.  I have it set to use the sysroot from the remnants of the pynq pre-build.
This is the beefmaker example project make results:
clang ../../../install/runtime_lib/test_library.cpp --target=aarch64-linux-gnu --sysroot=../../../platforms/xilinx_vck190_air/petalinux/sysroot/sysroots/cortexa72-cortexa53-xilinx-linux/ -g  -I../../../platforms/xilinx_vck190_air/petalinux/sysroot/sysroots/cortexa72-cortexa53-xilinx-linux//opt/xaienginev2/include -std=c++17 -I/sandbox-hdd/mlir-air/install/bin//../runtime_lib/airhost/include -I../../../install/runtime_lib -DAIR_LIBXAIE_ENABLE -DLIBXAIENGINEV2 -c -o test_library.o
xchesscc -p me -P /tools/Xilinx/Vitis/2021.2/aietools/data/cervino/lib -c chess/beefmaker_kernel.cc
aircc.py -o beefmaker.air.a --host-target=aarch64-linux-gnu -xbridge --sysroot=../../../platforms/xilinx_vck190_air/petalinux/sysroot/sysroots/cortexa72-cortexa53-xilinx-linux/ air.mlir
Compiling partitions: ['partition_0']
Found Vitis at /enc/tools/Xilinx/Vitis/2021.2
 MLIR compilation: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   0% -:--:-- 0:00:00 0/1 1 Workeropt: unrecognized architecture 'aie' provided.
Error encountered while running: opt --opaque-pointers=0 --passes=default<O2> -inline-threshold=10 -S air_project/partition_0/input.ll -o air_project/partition_0/input.opt.ll
 Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   0% -:--:-- 0:00:00 0/1 1 Worker
Error encountered while running: aiecc.py --sysroot ../../../platforms/xilinx_vck190_air/petalinux/sysroot/sysroots/cortexa72-cortexa53-xilinx-linux/ --host-target aarch64-linux-gnu --tmpdir air_project/partition_0 --aie-generate-xaiev2 --xbridge --no-xchesscc air_project/aiecc.partition_0.mlir
make: *** [Makefile:18: beefmaker.air.a] Error 1

This is a bug. aircc.py makes some (invalid) assumptions about the clang available on your PATH.

I just cloned this repo earlier today, I have built up to commit 8ea962a. Using Ubuntu 20.04LTS & v2021.2 tools. I have it set to use the sysroot from the remnants of the pynq pre-build.

A separate bug is that we don't have any guide on how to build an ubuntu sysroot. We currently use a method based on Docker. You could also mount the pynq image itself as a sysroot.

Try passing the  --xchesscc option (from the linked PR) to aircc.py and see if it gets you any farther. I still had to be careful put the clang and opt from the llvm that I built against in my path ahead of the very old system version.

Thank you @fifield passing -xchesscc (no double --) to aircc.py gets me past the Unrecognized architecture bug!
Next issue for me is runtime_lib/air_host location is also maligned somehow.


Add back link for questions

For https://trello.com/c/LVSlwXmo/246-add-back-link-for-questions
This adds a back link to the question pages in the Brexit Checker so that users can navigate to previous questions.  The exception to this is the first question which directs users to the 'start' page of the checker.  Since we now have 'Back' links on question pages, as per the design system we remove breadcrumbs from these pages.
We also ensure that the answers that a user has already selected are passed as params when they click the back link so that the answers are pre-selected on previous pages.  Answers that are changed on previous pages are carried forward to the results and previous answers are removed.

@benthorner This should be ready to review again.

With this change, can we support changing of answers? @benthorner @emmabeynon

@DilwoarH Yes some work was done previously to support changing answers so as long as we pass the criteria back to previous pages users can change their answers and this will be reflected in the results.

Seems to work as expected.


network: Move to fully hotplugged network

We need to move to fully hotplugged network if we want to support the use case of booting a VM from a template, and also to allow more flexibility.

I wanted to talk about this issue that I had opened a few weeks ago because I am not so sure that's actually something we should do.
I got my PR about moving the OCI hooks out of virtcontainers, and not assuming for any default network being merged recently, and I was wondering if there was a benefit of moving to fully hotplugged model.
Indeed, as long as we make sure we're not making strong/wrong assumptions about adding the underlying network by default, implementation like Frakti can coexist and work with kata-runtime.
Also, I wanted to mention that moving to a fully hotplugged model might not be a good idea as some customer might want to be able to use some device that are not hotpluggable (passthrough of a NIC for instance).
@WeiZhang555 @bergwolf @caoruidong can you think of any strong reason why we should move to a fully hotplugged model for networking?
/cc @egernst @amshinde

@sboeuf I have already done the change (see https://github.com/bergwolf/kata-runtime/tree/network) but there are issues w/ network hotplug[1] so I didn't raise any PR yet. My strong reason for the move is that vm factory requires it otherwise different VMs created from a template will use the same nic config (mostly the mac address). Another (less-strong) reason is to support a use case that a container requires NO external network connections in which case we should not give it a nic at all.
[1]. As I was testing the full network hotplug model, I found that the agent uevent listening code not to be working as expected. If I hotplug a nic, no matter how long I wait in the UpdateInterface call, it never gets the uevents, not until the RPC returns. It feels like agent is single threaded that cannot bring up the uevent listening goroutine while waiting in the UpdateInterface call. @sboeuf @caoruidong how did you guys test network hotplug when implementing it?
And I see that the block device hotplug code actually waits and listens on the uevents on its own. Does it mean the agent uevent listening goroutine does not work for block device hotplug either? @devimc @amshinde

@bergwolf

My strong reason for the move is that vm factory requires it otherwise different VMs created from a template will use the same nic config (mostly the mac address).

The way things are implemented now, as long as you have a factory, no network will be added by default, am I missing something?

Another (less-strong) reason is to support a use case that a container requires NO external network connections in which case we should not give it a nic at all.

This one already works I think. If no network is provided by the upper layer, the network namespace will be empty and nothing will be found, hence nothing will be added to the VM.
Also, we could think about adding a clear boolean flag to the SandboxConfig, instead of relying on the existence of a factory, in order to decide if we want the network scanning to be performed or not.

As I was testing the full network hotplug model, I found that the agent uevent listening code not to be working as expected. If I hotplug a nic, no matter how long I wait in the UpdateInterface call, it never gets the uevents, not until the RPC returns. It feels like agent is single threaded that cannot bring up the uevent listening goroutine while waiting in the UpdateInterface call. @sboeuf @caoruidong how did you guys test network hotplug when implementing it?

That's interesting as some time ago, I had some issues with the uevent listener as it was not working as expected for me. We might need to narrow this one down since we want to make sure using the uevent listener is a reliable way of detecting new interfaces.
About the way I have tested the network hotplug, I have mainly tested with the network monitor process, and also, I had spent some time testing with the full network hotplug PR (but it's not usable right now as not rebased).

@sboeuf

The way things are implemented now, as long as you have a factory, no network will be added by default, am I missing something?

While it is true, it is also the reason vm factory is not fully functional. We need a fully hotplug model to have network setup at least for vm factory case. But again, do we want to diverge that much?

This one already works I think. If no network is provided by the upper layer, the network namespace will be empty and nothing will be found, hence nothing will be added to the VM.

It is working for vm factory, and working for non-factory at the API level. We surely need to change CLI code to make it work in a generic case. But that is just a different approach. If we have fully hotplug network model, we gain the functionality naturally.

I had some issues with the uevent listener as it was not working as expected for me.

Yes, it is exactly the issue I was hitting. I guess for the same reason @amshinde added waiting in block device hotplug code on its own.

I occasionally meet the issue, not very often. Will https://github.com/kata-containers/agent/pull/306 help?

@caoruidong Nop. I am constantly seeing the failure with kata-agent master.

@bergwolf
As long as we can cover all the use cases our user could have, I think we should keep the coldplug as a backup for some specific use cases.
By stong reason, I was asking if there is one use case that cannot be covered by the fact that we're not using fully hotplugged network, but I don't think we have such case.
Also, for the record, I thought that moving to a fully hotplugged network was a good idea because I was interested in reducing the code complexity, but @egernst mentioned that some users might use Kata with Docker and that hotplugging the network, which means supporting network hotplug with the hypervisor, might not be strictly needed. Let's try not to force our user to support some hotplug features (from an hypervisor perspective), when the use case does not require it.
@amshinde could you take a look at this sporadic issue with uevent?

As long as we can cover all the use cases our user could have, I think we should keep the coldplug as a backup for some specific use cases.

I don't have a strong reason, so I think we can choose to support hotplug whenever it can, and leave codeplug as a backup. This is fine for me.

@sboeuf @WeiZhang555 Sure, I understand. I just don't want to diverge too much between vm factory and non-factory code path. I am fine with keeping coldplug.
So the question is, do we determine the hotplug/codeplug switch depending on hypervisor capability (that's what I'd call a backup plan)? Or do we always code plug in non vm factory case?

So the question is, do we determine the hotplug/codeplug switch depending on hypervisor capability (that's what I'd call a backup plan)? Or do we always code plug in non vm factory case?

Vote to "depending on hypervisor capability", and always use hotplug unless the hypervisor can't support.

@bergwolf @WeiZhang555
By depending on hypervisor capability, do you mean actively testing the hypervisor, or simply add a new field in the configuration.toml under the hypervisor section?
I think the configuration option would be the most reliable one.
Now, that being said, I don't know why we should try to hotplug by default. Does it buy us some time? Do we increase our performances? If not, I don't see why we should bother changing this.

@WeiZhang555

it can deduplicate codes then increase the readability and make it easier to maintain.

Unfortunately, moving to full hotplug will not allow to support use case where the hypervisor does not support hotplug.
@bergwolf

It's more about the default behavior you are asking. I am fine if you insist on coldplug it, provided that the network hotplug code path is also extensively tested since that is a feature we must support in all kinds of scenarios (k8s cni, docker connect etc.). I'm worried about network hotplug stability because just recently I found out that it is not working and clearly we do not have any coverage for it in CI.

About CI and making sure network hotplug works, I cannot agree more :)
We obviously need the network hotplug to work since we definitely need this capability!


fix incorrect button text

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

/hold

/unhold

/lgtm


Hot Reload kills the frame

When using pancake views on a physical device and hot reload the frame is removed. This is only an issue on a physical iOS device with hot reload.

I tried with the lastest stable release(1.3.5) and still have the same issue.

I tried with the latest stable release(1.3.5) and still have the same issue.

I am also getting errors on Android.
After pressing "Ctrl + S" a few times, the application is closed for excess memory.

I am running version 1.3.7 and I updated VS mac yesterday to 8.4 and pancake view seems to be working correctly now.

1.3.7 saw #62 get reverted. Might’ve been the cause of your issue as well? Glad it’s fixed now though!

So am I, thanks again for the work you do.


Tests

in this PR we added tests to the profile and missions pages.

Great work on the tests!

Great job on the tests @Arturgouveia1970 !


Typecast refactoring

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues

Thanks


refactor(resolve): replace read-pkg-up with escalade

Summary
Ref https://packagephobia.com/result?p=read-pkg-up https://packagephobia.com/result?p=escalade
Read-pkg-up package is quite big and have a lot of dependencies.
It also handles cases not necessary for jest. Beautiful JSON parsing
errors are not relevant and can be replaced with builtin JSON.parse.
Test plan
Not sure about this. Looks like es modules support was not covered by tests.

Aha, looks like testing on 13.2 is not a good idea. Native ESM support is broken until 13.7. The issue is the same as in many package with es modules support.
Error: No valid exports main found for '/.../jest/node_modules/yargs'

for anyone stumbling across this issue due to this error:
Error: No valid exports main found for '/.../jest/node_modules/yargs'

you need to update the version of node that you're using to >=13.7

Let's revert and re-land for Jest 27

@SimenB Are you gonna revert and escalade and yargs as well? Are you sure any more dependencies won't add it?

yarn why escalade only points to browserlist now, which we have as a dev dep from babel, so should be good


Doesn't work with templates

I'm using Handlebars in my project to add dynamic content on a page. Unfortunately triggering a micromodal in a template doesn't work. Method MicroModal.show("id") does not work either.
Template (passed js-micromodal-trigger="modal-two"  as an attribute):
At the picture

Config:
MicroModal.init({     onShow: modal => console.info(${modal.id} is shown),      onClose: modal => console.info(${modal.id} is hidden),      openTrigger: 'js-micromodal-trigger',     closeTrigger: 'js-micromodal-close', });
P.S. If a button(link) is hardcoded and does not belong to dynamic elements then Micromodal works fine.
Do you have any solution for this particular situation? Thank you.

@IryArkhy Thanks for opening this issue. Micromodal attaches events to all target at the time of initialization, there is no way for it know that new content has been added to the page and therefore it does not bind events to the new elements.
At this moment, I'm afraid this functionality is not available.


fix leftover

Cell 5 of the first tutorial (basic analysis) was not run correctly apparently, and the printed structure of adata still had coords instead of spatial.

sorry for this @falexwolf , quite important that the print structure is correct


feat: add entrypoint contracts support

Closes OPT-551

You need to also upgrade the contract version and run just pre-pr or it will fail on the OP's repo CI.
Here is the guide: https://github.com/ethereum-optimism/design-docs/blob/main/protocol/smart-contract-versioning.md

You need to also upgrade the contract version and run just pre-pr or it will fail on the OP's repo CI. Here is the guide: https://github.com/ethereum-optimism/design-docs/blob/main/protocol/smart-contract-versioning.md

It is werid, we run just pre-pr without changing the version and it worked fine.

We need to add a testFuzz_relayMessage_customEntryPoint_succeeds to cover that branch as well


Scrolling in Firefox on Mac on PageValidator is broken

Describe the bug

Apparently the scrolling is broken there according to one user.
To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

OS:
Browser:
Version:

Smartphone (please complete the following information):

Device:
OS:
Browser
Version

Additional context

confirmed

note: re-write sidebar and header css to get scrolling for free


Update redhat-cop/operator-utils to v1.1.4 (based on operator-sdk v1.9) to fix bug not removing removed resources

We have seen, that with current redhat-cop/operator-utils:v1.1.3 (based on operator-sdk v1.3, the same operatorsdk version used at saas-operator), when removing resources like PDB/HPA, randomly they are not deleted and need to be deleted manually (they are not recreated because the controller no longers reconciles it).
It seems the recocile controller to delete it fails, and on next reconcile thinks it is no longer required to watch it.
I have done some changes on backend and system controllers, deploying initially a basic CR:
apiVersion: saas.3scale.net/v1alpha1
kind: Backend
metadata:
  name: example
spec:
  image:
    tag: v3.2.0
  config:
    rackEnv: dev
    redisStorageDSN: backend-redis-storage
    redisQueuesDSN: backend-redis-queues
    systemEventsHookURL:
      fromVault:
        key: URL
        path: secret/data/some/path
    systemEventsHookPassword:
      fromVault:
        key: PASSWORD
        path: secret/data/some/path
    internalAPIUser:
      fromVault:
        key: USER
        path: secret/data/some/path
    internalAPIPassword:
      fromVault:
        key: PASSWORD
        path: secret/data/some/path
  listener:
    loadBalancer:
      eipAllocations:
        - eip-123
        - eip-456
    endpoint:
      dns:
        - backend.example.com
    config:
      redisAsync: false
    marin3r:
      ports:
        - name: backend-http
          port: 38080
        - name: http-internal
          port: 38081
        - name: backend-htttps
          port: 38443
        - name: envoy-metrics
          port: 9901
  worker:
    config:
      redisAsync: true

By default, if not specified, it creates a  PDB/HPA for worker and listener:
$ oc get hpa
NAME               REFERENCE                     TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
backend-listener   Deployment/backend-listener   <unknown>/90%   2         4         2          2m10s
backend-worker     Deployment/backend-worker     <unknown>/90%   2         4         2          2m9s

$ oc get pdb
NAME               MIN AVAILABLE   MAX UNAVAILABLE   ALLOWED DISRUPTIONS   AGE
backend-listener   N/A             1                 0                     2m15s
backend-worker     N/A             1                 0                     2m15s

Then deploy the same CR, but removing their PDB/HPA:
apiVersion: saas.3scale.net/v1alpha1
kind: Backend
metadata:
  name: example
spec:
  image:
    tag: v3.2.0
  config:
    rackEnv: dev
    redisStorageDSN: backend-redis-storage
    redisQueuesDSN: backend-redis-queues
    systemEventsHookURL:
      fromVault:
        key: URL
        path: secret/data/some/path
    systemEventsHookPassword:
      fromVault:
        key: PASSWORD
        path: secret/data/some/path
    internalAPIUser:
      fromVault:
        key: USER
        path: secret/data/some/path
    internalAPIPassword:
      fromVault:
        key: PASSWORD
        path: secret/data/some/path
  listener:
    hpa: {}
    pdb: {}
    loadBalancer:
      eipAllocations:
        - eip-123
        - eip-456
    endpoint:
      dns:
        - backend.example.com
    config:
      redisAsync: false
    marin3r:
      ports:
        - name: backend-http
          port: 38080
        - name: http-internal
          port: 38081
        - name: backend-htttps
          port: 38443
        - name: envoy-metrics
          port: 9901
  worker:
    hpa: {}
    pdb: {}
    config:
      redisAsync: true

And randomly one PDB and HPA (backend or listener), persists and is not deleted, and need to be manually deleted:
$ oc get hpa
NAME             REFERENCE                   TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
backend-worker   Deployment/backend-worker   <unknown>/90%   2         4         2          15s

$ oc get pdb
NAME             MIN AVAILABLE   MAX UNAVAILABLE   ALLOWED DISRUPTIONS   AGE
backend-worker   N/A             1                 0                     16s
slopez @ ~/work/sidekiq-split/saas-operator

After doing some tests using newer  redhat-cop/operator-utils:v1.1.4 (based on operator-sdk v1.9), the issue seems to be fixed, at least I have not been able to reproduce it, so when removing PDB/HPA from CR spec, they are really deleted.

operator-utils was updated to github.com/redhat-cop/operator-utils v1.2.2 at  https://github.com/3scale-ops/saas-operator/commit/8618a1afbcbff4007abda5fe80d6363b5f068763
Pending to try to reproduce the issue test documented at https://github.com/3scale-ops/saas-operator/issues/126#issue-1012282475  to verify it is already fixed


[Beta] Reorder useState page

This is inspired by https://github.com/reactjs/reactjs.org/pull/4263, but is a more expansive reordering.
The idea is that we got a bunch of feedback about the API page feeling a bit too "guide-y". This is because we start with the higher-level explanation instead of the API syntax explanation.
This flips it around.  So we start with the syntax, then "zoom out" to the usage, then "zoom out" to the recipes. I didn't change much about the special cases at the end.
This also adds clarity about whether an API "gets" or "returns" something. And we link to the function overloads from the main API "pills" so that you can jump to them if that's what you're looking for. (However, they're intentionally small and styled like footnotes.)
Preview page

I agree with Rick - I love the reorder.
However, I worry that folks won't scroll after the recipes -- I myself almost didn't. This might be because elsewhere in the docs the challenges (of which the recipes remind me) are usually located at the very bottom of the page.
I wonder if there could be some way of giving more visibility to the content that comes after the recipes?

I worry that folks won't scroll after the recipes -- I myself almost didn't.

This is partly intentional, since that deals with edge case-y things that don't come up that often. And so it's a good cutoff point for most readers. So that it doesn't feel like you have to read the entire page just to start using it.
However, I do want to try yet another reorder, which I might submit separately.

let's get this in and iterate.


TimeZone#strftime doesn't give correct local offset

TimeZone#strftime replaces %Z with the correct local abbreviation, but it leaves %z at +0000 instead of the correct local wall-time offset.  Same for %:z, %::z and %:::z.

Support for returning the correct offset for %z (and associated formats) in Timezone#strftime has already been implemented. It will be included in the next TZInfo release.

Version 1.2.3 has now been released. This adds support for returning the correct offset for %z.


x/tools/gopls: reduce memory usage

This is a general tracking issue for memory usage in gopls. We need to collect data and set goals for usage for a given project size. We also need to work towards reducing the memory usage when staticcheck is enabled (though that may be a separate issue).
If you have a specific problem with gopls using too much memory on your machine, please create a new issue so that we can investigate it separately.
Please include your VS Code settings and heap profiles with your issue. These can be collected by adding the following settings to your VS Code settings.json:
"go.languageServerFlags": [
    "-rpc.trace",
    "serve",
    "--debug=localhost:6060"
]

and running go tool pprof -http :8080 http://localhost:6060/debug/pprof/heap. For other editors, see details here.

I just upgrade gopls to v0.3.0 today so that I'm able to rename symbols / find reference across package, but the memory usage is very high:

I'm using Ubuntu 16.04
gopls version:

golang.org/x/tools/gopls v0.3.0
<EMAIL_ADDRESS>h1:l9KKK1/n6CIbfgaUvHBWAvCfOxcl1N+KSOK79OlPIao=

go version:

go1.13.4 linux/amd64

As the comment above, I've have had problems with massive memory usage since upgrading to 0.3.0 yesterday, sometimes upward of 12 GB.

macOS Mojave 10.14.6
go version go1.13 darwin/amd64
<EMAIL_ADDRESS>h1:l9KKK1/n6CIbfgaUvHBWAvCfOxcl1N+KSOK79OlPIao=

same here.  Please, keep the feedback constructive.
FWIW this has already been fixed on master via https://go-review.googlesource.com/c/tools/+/217677

I'm sorry that you all encountered this bug - we had a memory leak that was a bit tricky to reproduce, but as @myitcv said, we believe that we've fixed it. You can try it out by downloading the pre-release for the next version of gopls (go get golang.org/x/tools/gopls@v0.3.1-pre1). Please report here if you still see the excessive memory usage with that version.

@stamblerre On the latest master, gopls is using more than 30GB when developing with some kubernetes sub-projects

@vincepri per the bold section in the original issue, please file a new issue with repro instructions, even if they're just "check this repository out and open it."

@stamblerre @heschik
I'm using the latest master and the memory usage is relatively large for a small/medium project. (~1.5GB)
Unfortunately I cannot share the project, but I can send you the pprof heap file for gopls, if it helps :man_shrugging:
Build info
golang.org/x/tools/gopls master
<EMAIL_ADDRESS>h1:yNTWrf4gc4Or0UecjOas5pzOa3BL0WDDyKDV4Wz5VaM=
<EMAIL_ADDRESS>h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
<EMAIL_ADDRESS>h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
<EMAIL_ADDRESS>h1:WG0RUwxtNT4qqaXX3DPA8zHFNm/D9xaBpxzHt1WcA/E=
<EMAIL_ADDRESS>h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
<EMAIL_ADDRESS>h1:BtAc3ytYUhbzaL+TpDGZSBVecmz6ra8/VYiIwtasXXc=
<EMAIL_ADDRESS>h1:/atklqdjdhuosWIl6AIbOeHJjicWYPqR9bpxqxYG2pA=
<EMAIL_ADDRESS>h1:3JgtbtFHMiCmsznwGVTUWbgGov+pVqnlf1dEJTNAXeM=
<EMAIL_ADDRESS>h1:KaMb5GLhlcSX+e+qhbRJODnUUBvlw01jt4yrjFIHAuA=

Here you can find the pprof heap file
Let me know if you need any more info from my side that can be useful for you.

@trajber Unfortunately I don't see any signs of a bug in your profile. That doesn't mean there isn't one, but 1.5GiB is not completely out of line for a project with a lot of dependencies, and without access to the source it's very difficult to judge. Sorry, but I don't think there's going to be much we can do in the short term. Hopefully you will benefit from general optimizations we make in the future.

When not using a huge monorepo and slowly running out of memory, I usually see gopls hanging out at around 800MB to 1GB of memory when browsing smaller repositories.

@Jacalz: Responded to you on https://github.com/golang/go/issues/37670#issuecomment-614732451, so let's continue the conversation on that issue.

I think the commits I pushed today have improved things significantly for large projects. I'll keep looking for a little bit.

The memory uses not as much users commented before. Not even close but yet giving half a GB is big. However it provides better and fast autocomplete.

I just updated to latest and now I have this 🔥

From the first comment:
If you have a specific problem with gopls using too much memory on your machine, please create a new issue so that we can investigate it separately.
There will be zip files in /tmp with additional memory diagnostic information. Please include one of them. If you are uncomfortable sharing the package names of your code you can pick one with a -nonames suffix, otherwise please upload a --withnames` file.

There have been a number of memory improvements in gopls at master. Please try out with the instructions on https://github.com/golang/tools/blob/master/gopls/doc/user.md#unstable-versions, or wait for the next release.

@stamblerre just switched to master and it dropped my ram usage from 10 gigs to 1.5gb! Great work guys!


Stop zenbot from stalling when getTrades is slow

onTrade() in engine.js was returning out of execution immediately when an incoming trade was older than the last known trade. This may occur when an exchange API call response is slower than poll_trades. By returning immediately out of onTrade, further incrementing the trade cursor is prevented, causing the bot to stay stuck in the same time stamp.
Removing the return statement entirely, because further down the function, the incoming trade's timestamp is already being checked before adding it. This way, zenbot resumes operation when an older-than-last trade comes in.
I welcome any feedback on this, as it's hard to know as a contributor what the design thinking behind this was originally.

Seems like it was added here originally:
https://github.com/DeviaVir/zenbot/commit/17e9758eb0c2179ee81a960ffd83bcb54012c025#diff-a41b519e7979a713e894ef8d1b3fe568R347-R349
In the spirit of paper trading. Does paper trading still work without this?

I had to make my changes specifically for paper trading not to halt when the exchange response is slower than poll_trades.

Sounds good to me, thank you for taking the time to contribute!


"Visitors leaving" before they actually leave (Exception while ticking lord with job RimWorld.LordJob_VisitColony)

I tried searching for a few keywords in the Issues list but nothing popped up.
Describe the bug
In my third colony on the world map there are some visitors. After about 9 hours (game save time) they start leaving even before the notification message "Visitors from the Thrombo (insert correct faction name here) are leaving" appears. When the actual message does appear the game throws the following exception, pauses and can not be unpaused again because the same exception happens immediately. At this point they have already left the map hours ago.
Exception while ticking lord with job RimWorld.LordJob_VisitColony
Some remarks
I have just installed RimThreaded mid-game to try it out and have not actually been playing with it from the beginning.
I have tried unloading all the mods except Harmony and RimThreaded and the same thing happens .
Steps to reproduce the behavior (VERY IMPORTANT)
Just unpause the game and after about 10 in-game hours the notification that the visitors are leaving will appear. At that point the game should pause and throw the exception.
Error Log
Player log: https://pastebin.com/v9sRtHV1
HugsLib log: https://pastebin.com/8VtqesX8
Save file
save.zip
Mod list (Preferably a RimPy compatible list.)
I assume you can get the modlist from the logs or the save. I do not use RimPy but for the sake of convenience I shall paste the list here. This is from the game save:
brrainz.harmony
me.samboycoding.betterloading
ludeon.rimworld
unlimitedhugs.hugslib
maarx.modbuttons
kapitanoczywisty.changemapedge
voult.betterpawncontrol
gguake.areaninclusionexclusion
pathavoid.kv.rw
improvedloadtransportpods.rw
mlie.pickupandhaul
avilmask.commonsense
dhultgren.smarterconstruction
uuugggg.gearupandgo
uuugggg.smartmedicine
uuugggg.usebedrolls
smashphil.loadinginprogress
syrchalis.setupcamp
fluffy.blueprints
smuffle.harvestorganspostmortem
jaxe.rimhud
sandy.rpgstyleinventory
mehni.numbers
uuugggg.listeverything
gguake.ui.simplesearchbar
jaxe.morefilters
supes.autoseller.core
supes.autoseller.caravanequip
timmyliang.tradehelper
longwater.quicklinks
fluffy.followme
maarx.firefightingcontrols
avilmask.microdesignations
dubwise.dubsmintmenus
dubwise.dubsmintminimap
jaxe.reorderer
tradingspot.kv.rw
rimfridge.kv.rw
automatic.bionicicons
madeline.pathoverlay
ryder.satisfiedstorage
hatti.qualitybuilder
kikohi.whatsforsale
majorhoff.rimthreaded
Final note
I am really impressed that you are even attempting to make such a complicated mod as this one and if I can help with more data about this error, I shall be happy to help with additional information that I might have not mentioned.
To help further I shall also share the complete Mods directory so you can, hopefully, just unpack the archive, load the save and be on your (debugging) way.
Archived Mods directory: https://tinyurl.com/yb853pgg

Tested in RT 1.3.2 and 2.0.7. Issue happens in both versions.

@cseelhoff this save looks ready to generate hauling errors. Lots of hauling issues with this save and 2.1.5

issue still happens on 2.1.5

should be fixed now


WIP: Removed storageID and UIURL from the app-provider's config

StorageID is auto-resolved in the gateway service, whereas
the UIURL's doc was misleading: we need to decide whether
to drop it entirely (and surely it won't stay in the config).
En passant, this fixes #991 and includes other minor changes
concerning error handling and logging.
Still WIP as it requires https://github.com/cs3org/cs3apis/pull/85 to be merged first.

@glpatcern cs3apis merged, remember changelog

@glpatcern looks already pretty good


Box shadow for tooltip and arrow

How can I add box-shadow for the tooltip and arrow? The tooltip not properly visible if the page background color is similar to the tooltip background color.

Hi @sthadathil, you can try https://react-tooltip.com/docs/examples/styling

As mentioned, this can be achieved by referring to the examples in the docs.
If any problems arise, feel free to reopen this issue.


Medoo::RAW with joined table under Version 2.x.x

Hi all,
I have an issue to join tables and use Medoo::RAW as where.
Database: Postgresql
Example:
$join=array('[>]AdminSegmentTypes'=>['segment_types_id'=>'id']);
$where="WHERE network.networkv4 <<= INET'$net' OR network.networkv6 <<= INET'$net'";
$result=$database->select($table,$join,$fields,Medoo2::raw($where) );
Error:
Uncaught TypeError: Argument 5 passed to medoo2\Medoo2::selectContext() must be of the type array or null, object given, called in classes/medoo2/Medoo2.class.php on line 1593 and defined in classes/medoo2/Medoo2.class.php:1163 Stack trace: #0 classes/medoo2/Medoo2.class.php(1593): medoo2\Medoo2->selectContext('adminnetworksco...', Array, Array, Array, Object(medoo2\Raw)) #1 content/netmgmt/find_networks.php(88): medoo2\Medoo2->select('network...', Array, Array, Object(medoo2\Raw)) #2 {main} thrown in classes/medoo2/Medoo2.class.php on line 1163
If I use version 1.7.10 with the same command then it works.
regards

I came here to report this issue, but found this already here, so I'll just add that I have the same problem. Thanks,


Pagination not working on github pages even site builded locally

Hello!
Tried to build site locally as @sverrirs [said] (https://github.com/sverrirs/jekyll-paginate-v2/issues/9#issuecomment-275615006) and push _site but pagination didn't work.
http://s1lviu.github.io/
https://github.com/s1lviu/s1lviu.github.io

What doesn't work? Are the pagination pages created, does the pagination code get executed? Have you tried turning on the debugging debug:true in the front matter?

I was facing the same issue and then saw this issue and disappointed.
It is really nice to have.
Right now I have to content myself with jekyll-paginate, Commit ID.
https://coolbrg.me/blogs/
When using jekyll-paginate-v2


docs: :memo: added installation instructions

For easier installation, just copy one of the installation commands

For this we have the installation guide: https://valibot.dev/guides/installation/

I understand, but I 99% of the time only visit the GitHub page. I've installed your fantastic library multiple times and every time I missed having an “installation” section, where I can easily copy and paste the installation command. Furthermore, I don't think it pollutes the README and adds more value.

Thank you for your feedback. I will think about it.

Hi,
friendly reminder, it's been two months, have you decided?
Have a nice day

I don't want to add it at this time. However, I am happy to leave this PR open for the time being to give other developers the opportunity to provide feedback. Currently, my focus is on the library code. As soon as we get closer to v1, I will mainly focus on the documentation and rethink this again.

Since there are many ways to install Valibot using different package managers and registries, I don't want to add installation instructions to our readme. However, I would like to thank you for your contribution.


feat(index.html, style.css): add Indication of the active generator/tool

Added a common ".generator-tool-title" class under each generator content in the index.html file. To render the style, updated the style.css file. For rendering the title style, I used fixed position style for them and adjusted the left measurement according to the available media queries. However, when the max-width of the media query is 650 then, it's getting centered.
Fixes Issue
My PR closes #455
👨💻 Changes proposed(What did you do ?)
Added an indication (title) of the active generator or tool on the top left corner initially. Centered on the smaller devices.
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Note to reviewers
I was unsure about how it should look for the smaller devices. So, I've centered it and used the left: auto in the style.css file.

📷 Screenshots

Hi @Dun-sin, forgot to add you as the reviewer. Please have a look!

Hi @Dun-sin, forgot to add you as the reviewer. Please have a look!

Didn't matter, I would see it anyway because I'm the owner of the repo

You got it 😅

:tada: This PR is included in version 2.65.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Final changes for 1.0.1

Pull Request Test Coverage Report for Build 13

73 of 78 (93.59%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+16.7%) to 95.804%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/Game.class.st
43
45
95.56%

repository/IngSoft2-Model/GamePlaying.class.st
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/Game.class.st
1
95.59%

Totals

Change from base Build 8:
16.7%

Covered Lines:
137

Relevant Lines:
143

💛  - Coveralls


[DatePicker] Visual bug: stretched vertically off screen

My DatePicker looks like this out of the box with no style modifications:

The code used was just a simple DatePicker with no modifications:
App.js:
import React from 'react';
import MuiMixin from '../mixins/MuiMixin'
import {Paper, DatePicker} from 'material-ui';

var App = React.createClass({
  mixins: [MuiMixin],

  render() {
    return (
      <DatePicker />
    );
  }
})

export default App;

MuiMixin.js:
import React from 'react';
import mui from 'material-ui';

var ThemeManager = new mui.Styles.ThemeManager();

export default {
  childContextTypes: {
    muiTheme: React.PropTypes.object
  },

  getChildContext: function() {
    return {
      muiTheme: ThemeManager.getCurrentTheme()
    };
  },
};

I'm using WebPack to minify/build my app. Any ideas on what's causing this visual bug?

Fixed my own issue, for anyone having the same problem I added:
<!doctype html>

to the top of my index.html

Thanks you!


fix: do not flatted data in fm stringify

All fm data should be written in standard YAML format

Merge to test on edge


Speed up tests

I did a quick once-over on current CPU usage for tests and fixed some things up. Once we get some better data I'll do another pass, and probably grab @dgquintas and @matt-kwong to pass on some HOWTO details on this.

No significant performance differences


Conv2D is not called if it has only control dependency

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
source
TensorFlow version (use command below):
r1.5
Python version:
2
Bazel version (if compiling from source):
0.5.4
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
9.0/7.0
GPU model and memory:
Titan XP, 12GB

Describe the problem
If conv2d operation has control dependency in the graph, the operation is not executed at all.
I've tested with tf.tfprof and timeline. If I connect the conv2d with its value, it is finally executed.
Is it intended behavior in TensorFlow?
Source code / logs
```
opts = tf.contrib.tfprof.model_analyzer.PRINT_ALL_TIMING_MEMORY
opts['min_accelerator_micros'] = 1
run_metadata = tf.RunMetadata()

config = tf.ConfigProto()
config.gpu_options.allow_growth = True
#config.allow_soft_placement = True
config.inter_op_parallelism_threads=0
config.graph_options.optimizer_options.opt_level = tf.OptimizerOptions.L0
batch = 32
size = 224
in_channels = 3
out_channels = 1
filter_size = 7
inp = tf.ones(shape=[batch, size, size, in_channels], dtype=tf.float32)
v = tf.Variable(inp)
filters = tf.ones(shape=[filter_size, filter_size, in_channels, out_channels], dtype=tf.float32)
conv2d = tf.nn.conv2d(v, filters, [1,1,1,1], padding='VALID')
with tf.control_dependencies([conv2d]):
  train = tf.no_op()
with tf.Session(config=config) as sess:
  sess.run(tf.global_variables_initializer())
  sess.run(train, options=tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE), run_metadata=run_metadata)
  # conv2d is not executed

  sess.run(conv_ops, options=tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE), run_metadata=run_metadata)
  # conv2d is executed
root_node = tf.contrib.tfprof.model_analyzer.print_model_analysis(
              tf.get_default_graph(),
              run_meta=run_metadata,
              tfprof_options=opts)

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Exact command to reproduce

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?


[Question] </shenyu/plugin/selectorAndRules the configuration of this request cannot be synchronized to the console>

Question

After executing this request, the selector and rule in the divide plugin are empty, can't this configuration be synchronized to the console?

which version?

which version?

The latest master branch

from souce code, this request only send to shenyu-bootstrap, update local cache, and wont sync to shenyu-admin
org.apache.shenyu.web.controller.LocalPluginController#selectorAndRule

do you restart shenyu bootstrap?


Accessibility: Extend use of ARIA live regions

Feature Description
Background
When a portion of a page is updated with JavaScript, the update is usually highlighted with animation and bright colors, and is easy to see. But if you don’t have the ability to see the screen, you don’t know this has happened, unless the updated region is marked as an ARIA live region.
If this isn’t marked, there’s no notification for screen readers. But it’s also possible that all the region content will be announced after an update, if the ARIA live region is too large. You want to provide users with just a simple, concise message.
That's what we have the useLiveRegion hook for. Sadly it's been a bit underused in the project, mostly due to lack of documentation and education. Time to change this!
This hook is a simple tool that creates and appends an ARIA live notifications area to the element where developers can dispatch text messages. Assistive technologies will automatically announce any text change in this area. This ARIA live region has an ARIA role of “status” so it has an implicit aria-live value of polite and an implicit aria-atomic value of true.
This means assistive technologies will notify users of updates but generally do not interrupt the current task, and updates take low priority. If you’re creating an application with higher priority updates (such as a notification that their current session is about to expire, for example), then you’ll want to create your own method with an aria-live value of assertive.
This Task
This is a catch-all ticket to improve our usage of aforementioned hook.
Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

ARIA live regions are used appropriately where needed to announce updates to screen readers

Implementation Brief

[ ] Move useLiveRegion to design system so it can be used by both editor and dashboard
[ ] Document useLiveRegion why & how in accessibility docs
(can copy some stuff from above for the intro)
[ ] Snackbars: Add new spokenMessage prop that defaults to the snackbar message
[ ] "Style" panel: if fiddling with colors announce This color combination may be hard for people to read.
NB: It looks like we don't have any text contrast checks in this panel, so maybe we cannot really  do this.
[ ] Search results: announce %d result found / %d results found / No results found
[ ] Auto complete dropdown: announce %d results found, use up and down arrow keys to navigate / ... / No results found
[ ] ...more?

Not getting a "x results found" on Search:

@csossi thanks for checking this. I tried this locally and saw this when using voice over:

Can you give me a little more information about how it's not working for you?

Verified in QA


Tiny Fixes

Overview

Move computeLearningRate util.go > state.go.
Set Word2Vec configs as private variable:

opt, subsampleThreshold, batchSize, and theta.

Rename Lower to ToLower in Config

Coverage increased (+0.2%) to 56.688% when pulling 6f23903c9528606270ad9a1ff5612546c3267568 on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

Coverage remained the same at 56.476% when pulling 27034b1cf0d218090b8bd463fd1f9caa5ec159fc on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

Coverage remained the same at 56.476% when pulling 27034b1cf0d218090b8bd463fd1f9caa5ec159fc on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

Coverage decreased (-0.6%) to 55.839% when pulling 891e89717decc3fdfd8ab6d495c4cbfd4e7936f2 on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

Coverage decreased (-0.6%) to 55.839% when pulling 891e89717decc3fdfd8ab6d495c4cbfd4e7936f2 on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

Coverage decreased (-1.3%) to 55.202% when pulling 9f06afee0de4c6a50b665ebf4494ef3b4b6e0a76 on ref into 3cc0352136b4a75264d3d3160eeeed0858a45f70 on develop.

lgtm


Update README-DevOps.md

Added a summary diagram in Readme-Devops.md of steps taken to build the project

Thanks for the contribution @Anideep-Kalia


resolutionStrategy should be applied lazily before configuration resolution

On our build of 1 500 modules, using Gradle 6.5.1, AGP 4.0.0, kotlin 1.3.72,
we got a 1Gb gain at sync times in AS 4.1 by using applying the following change:

It would be nice if the strategy resolution would always be applied lazily.

Sorry for the late reply.
Since a lot of improvements have been made recently in the area of configuration handling, this is most likely obsolete. Please open a new issue if you still experience issues with that.


[Defect] Typing Indus script & Unicode v39 script fonts does not show up in the Editor

https://ckeditor.com/docs/ckeditor4/latest/api/CKEDITOR_config.html#cfg-contentsCss

Fixed for Unicode v39 script fonts

Indus script also is shown in editor


Add simple install test for PRs

there should be a GitHub action that tests the install of the plugins, this simple test should catch simple errors like on reported on Slack today
Hello Knative, long time no see. I’m really wanting to check out the new quickstart system but it looks like I might have caught it at a bad time or might be doing something wrong. When I try to install it I get:
❯ brew install knative-sandbox/kn-plugins/quickstart
==> Tapping knative-sandbox/kn-plugins
Cloning into '/usr/local/Homebrew/Library/Taps/knative-sandbox/homebrew-kn-plugins'...
remote: Enumerating objects: 203, done.
remote: Counting objects: 100% (203/203), done.
remote: Compressing objects: 100% (152/152), done.
remote: Total 203 (delta 126), reused 66 (delta 43), pack-reused 0
Receiving objects: 100% (203/203), 50.63 KiB | 4.22 MiB/s, done.
Resolving deltas: 100% (126/126), done.
Error: Invalid formula<EMAIL_ADDRESS>No available formula with the name<EMAIL_ADDRESS>Did you mean<EMAIL_ADDRESS>In formula file<EMAIL_ADDRESS>Expected to find class EventAT11, but only found: Event.
Error: Cannot tap knative-sandbox/kn-plugins: invalid syntax in tap!

/assign


lookup for struct

typesafe lookup for struct.
  <K extends string | number | symbol>(path: K) =>
  <A>(obj: { [P in K]: A }): A

I would like to propose the addition of a lookup function to struct.
This lookup function would take a  key as input and return the value directly. It would first receive the struct type, then verify whether the prop exists. If the prop doesn't exist, a compile-time type error would be thrown.
This design is to ensure type safety when accessing elements of a struct, with errors being caught at compile time rather than at runtime.

Thanks! This could be a useful shorthand that's cheaper than lenses.
"Lookup" to me implies a record. Maybe get, or _ (thinking of PureScript), could make more sense?:
const getX1 = S.get('X')
const getX2 = S._('X')

Probably get given the namespacing norm in fp-ts. WDYT?


Fade in route transition

Hi, I've been trying to implement the fade in transition example as in the docs. While in the simple case of example in the docs the demo runs smoothly, when it comes to more complex components the transition becomes very laggy and slow. The React.cloneElement(component, { key: pathname }) operation is the culprit, as it is a very slow operation. As already mentioned in #2638, there really needs to be some configuration available to the <Route> components, like the ability to add a certain key, or the ability to inject dependencies into the containers.

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Could you post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.

dude wtf, did you even read my post above? Why do you keep closing discussion? You did the exact same thing in #1531 without being able to backup you arguments with any real arguments except "go educate yourself in React best practices". This is not the spirit of open source.

I did in fact read your post above.


Add JS source maps in production build for packaged Wagtail

Discussed in #4295. Switches from dev-only inline source maps to external source maps for all builds.
At the moment this adds the following three files:
Time: 11957ms
                                                   Asset     Size  Chunks             Chunk Names
        wagtail/admin/static/wagtailadmin/js/draftail.js   247 kB       0  [emitted]  wagtail/admin/static/wagtailadmin/js/draftail
    wagtail/admin/static/wagtailadmin/js/wagtailadmin.js  56.5 kB       1  [emitted]  wagtail/admin/static/wagtailadmin/js/wagtailadmin
          wagtail/admin/static/wagtailadmin/js/vendor.js   192 kB       2  [emitted]  vendor
    wagtail/admin/static/wagtailadmin/js/draftail.js.map     2 MB       0  [emitted]  wagtail/admin/static/wagtailadmin/js/draftail
wagtail/admin/static/wagtailadmin/js/wagtailadmin.js.map   426 kB       1  [emitted]  wagtail/admin/static/wagtailadmin/js/wagtailadmin
      wagtail/admin/static/wagtailadmin/js/vendor.js.map   1.1 MB       2  [emitted]  vendor
   585 modules

They are quite big, but compressed it's not as bad:
444K	wagtail/admin/static/wagtailadmin/js/draftail.js.map.gz
280K	wagtail/admin/static/wagtailadmin/js/vendor.js.map.gz
104K	wagtail/admin/static/wagtailadmin/js/wagtailadmin.js.map.gz

Tested in Chrome. The source maps load only if the devtools are open AFAIK.
Edit: killed the Travis build myself.

Merged with  6246832