NUT-06: Deprecate amount field on PostSplitRequest

{
  "proofs": Proofs,
  "outputs": BlindedMessages,
  "amount": int //deprecate
}

the amount field is not necessary, since it introduces unwanted constraints.
The client has to manage split amounts (send, return) , but the mint does not need to. The mint only needs to perform split according to the clients request.

    fst: BlindedSignatures
    snd: BlindedSignatures

will become
    blinded: BlindedSignatures

and it is up to the client software to  accumulate the proofs accordingly after the split.

This makes sense to me. I was just running into an issue where cashu.me sends outputs in the reverse order cashu-rs expects. This would solve that.

This makes sense to me. I was just running into an issue where cashu.me sends outputs in the reverse order cashu-rs expects. This would solve that.

Could you explain how this happens? The order shouldn't be expected anywhere specifically iirc (except for the spendable check?)

the order matters inside the split operation: the second amount is the "send" amount, the frist amount is "return amount"

The fields are

the order matters inside the split operation: the second amount is the "send" amount, the frist amount is "return amount"

The fields are labeled though, so there is no "order" between fst and snd. There is an order inside those fields, that's what I thought @thesimplekid is referring to.

ACK.
Implemented in Nutshell mint (and wallet) in this PR: https://github.com/cashubtc/cashu/pull/263

Let's please move the discussion over here and track progress in upgrading: https://github.com/cashubtc/nuts/pull/34


handle format .svg and .ogv

.svg is for example in https://commons.wikimedia.org/wiki/File:Fountains_of_the_place_Louis-Lépine,_OSM_2017.svg or rather in
https://beta.water-fountains.org/fr-paris?l=de&i=Q3076321
and on the 5th image, there is the never ending wheel.

similarly with .ogv in
https://commons.wikimedia.org/wiki/File:Basel,_Barfüsserplatz_—_Leaves_floating_under_water.ogv
or rather
https://beta.water-fountains.org/ch-bs?l=de&i=Q29685311
Best would be:

include the 2 formats in the gallery (at least my win10 firefox and chrome are fine with them)
provide a proper error handling
a) target=_blank to underlying URL
b) timeout at some point?
What do you think ?

this is another format that should be dealt with:
https://commons.wikimedia.org/wiki/File:DJI_0111.webm


Add --include option

In some cases, it would be useful to have an --include option in addition to the existing --exclude option. If both options are specified at the same time, start with all files in --include and remove files as specified in --exclude.

From @PeterCaldwell in #248:

zstash create --exclude is very handy. It would be nice to also have a zstash create --include option.
For example, for the 50 TB per simulated month SCREAM runs I'm doing, I want to be able to zstash all the "T_2m" files together without also having to zstash a bunch of other files (which are individually 200 GB to 2 TB in size).

It looks like this is the function we'd need to change: https://github.com/E3SM-Project/zstash/blob/main/zstash/utils.py#L58
def get_files_to_archive(cache: str, exclude: str) -> List[str]:
    # List of files
    logger.info("Gathering list of files to archive")
    # Tuples of the form (path, filename)
    file_tuples: List[Tuple[str, str]] = []
    # Walk the current directory
    for root, dirnames, filenames in os.walk("."):
        if not dirnames and not filenames:
            # There are no subdirectories nor are there files.
            # This directory is empty.
            file_tuples.append((root, ""))
        for filename in filenames:
            # Loop over files
            # filenames is a list, so if it is empty, no looping will occur.
            file_tuples.append((root, filename))

    # Sort first on directories (x[0])
    # Further sort on filenames (x[1])
    file_tuples = sorted(file_tuples, key=lambda x: (x[0], x[1]))

    # Relative file paths, excluding the cache
    files: List[str] = [
        os.path.normpath(os.path.join(x[0], x[1]))
        for x in file_tuples
        if x[0] != os.path.join(".", cache)
    ]

    # Eliminate files based on exclude pattern
    if exclude is not None:
        files = exclude_files(exclude, files)

    return files

It looks like we always do for root, dirnames, filenames in os.walk("."):, so perhaps that just needs to be changed to for root, dirnames, filenames in os.walk(f"{included_files}"):, where included_files is the value given to --include. I'm not quite sure how parsing will work out for 1) individual files versus directories and 2) wildcards like "*".


Save button  'On' anytime user edits

Currently the user is required to step out of the edit block to save text.
Expected Behaviour:  User should be able to 'Save' while editing without having to step out of the block.

The Save button should be enabled any time there is an unsaved change to any editable text, and disabled is there are no pending changes to save.

Looks good in v1.0.5-rc.5. Save button is enabled when there is unsaved edits and disabled when there is no change to save.


Remote deletions not happening on Amazon drive

When filing an issue, please include the following information if
possible as well as a description of the problem.

What is your rclone version (eg output from rclone -V) 1.29

Which OS you are using and how many bits (eg Windows 7, 64 bit) Ubuntu 16 (64 bit)

Which cloud storage system are you using? (eg Google Drive) Amazon

The command you were trying to run (eg rclone copy /tmp remote:tmp) sync

A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)

Files are not being deleted from the Amazon drive after transfers are completed.
Some files, with newly edited meta tags, are being modified but their older versions are not showing up in the Trash as they used to.  This is not a problem as such.  I am reporting it in case it is an unintended behavior.

Note that if there were IO errors in the sync, then rclone won't delete files.  rclone will log Not deleting files as there were IO errors.
The API doesn't give control over which files end up in the trash or not, so if something has changed about which files end up in the trash then amazon have changed something most likely.
Did updated files used to end up in the trash - I don't remember testing that?

Yes, updated files used to go in the trash.  Or, was it renamed files?  A seed of doubt has entered my mind now, because I can't remember for sure whether file name changes and file size changes both caused older versions to be sent to trash, or only the former.  I sorted the files by 'Date Modified' to confirm the updates had taken place.  Whatever rclone does it does consistently so I don't worry about it now.
It is the same I/O error every time being caused by a directory called 'lost+found' which puts up a 'Permission denied' because it is reserved by the file system.  I have added an external drive and mounted it as a sub directory, hence this issue.  Is there a way to exclude that directory from the sync?
Thanks, NCW!

Sure - check out the filters page.  --exclude /path/to/lost+found/** is probably what you want.  Check using rclone ls with the filter first.

That should fix it.  Thank you!

Today's log still has 'Not deleting files as there were IO errors'
I may have placed the exclude flag in the wrong place.  This is the exact command I am using
'/usr/sbin/rclone sync --exclude /home/isaiahsellassie/Music/JAZZ/lost+found/** /home/isaiahsellassie/Music Adrive:Music'
Perhaps I should try it without the trailing slash and asterisks.  Or, put the exclude flag after the sync paths.

It doesn't matter where you put the --exclude flag.
Note that you don't repeat the path in the remote in the exclude, so you want something like this.  (I should have said it needed the relative path from the root of the sync.)  I'd put it in quotes too as it contains shell metacharacters *.
/usr/sbin/rclone sync --exclude "/JAZZ/lost+found/**" /home/isaiahsellassie/Music Adrive:Music

You can test whether it is working with the ls commands which obey excludes in the same way, eg
/usr/sbin/rclone ls --exclude "/JAZZ/lost+found/**" /home/isaiahsellassie/Music

Or if you decided you never wanted a directory called lost+found wherever it was found then you could use --exclude "lost+found/**"

I did a --dry-run -v with the corrected command, and it concluded without an IO error.  It did report, 'Attempt 3/3 failed with 1 errors' at the end but I don't know what that refers to.
I'll find out if remote deletes are working again after cron runs the sync as usual tonight.  I have deleted a folder completely as it happens.
Thank you kindly, sir!

It should have left a log for that error that will give you a clue as to what happened. You can use the - - log-file option to save the log somewhere.
You need to track down that last error or it won't do the remote deletions.

So, if I add --log-file will it default to my home directory?  or, should I follow it with an explicit path and file name?

A full path is safest

I have attached the log.  The uploads occurred but remote deletions did not.  It is still trying to open the JAZZ/lost+found directory.
rclone-log.txt

Is there a fix in the offing, Nick?

We need to stop it looking in the lost+found directory - any IO errors will stop remote deletions.
Which command line did you use with that log?  Did it have the --exclude "/JAZZ/lost+found/**" in it?  I'm pretty sure that should work.

Yes, that was it exactly.  I thought it should be without the slash and asterisks at the end but I followed your instructions.

The first slash roots it to the start of filesystem hierarchy.  The /** means this directory and anything under it which is quite important.
I see what the problem is now - you need to upgrade rclone - the feature I'm trying to use was only put in 1.30.
I suggest you upgrade to the latest rclone 1.32 and try again.

I did the upgrade yesterday, and sure enough, when I look at the log email from cron, the problem is solved!  It is no longer trying to open the excluded directory, and deletions are being completed.
THANK YOU!

The only thing it needs now is the ability to delete empty folders.

Excellent! Deleting empty folders is #100 so I'll close this one.


Why does a no-key-found delete increments stats' misses

Hi,
I'm wondering as to why a delete miss would be a cache miss.
Here: https://github.com/tcs-de/nodecache/blob/master/_src/lib/node_cache.coffee#L223
Thank you

Good point ...
On the one hand i would count a delete miss, because it's a valid request to the cache.
But on the other hand it should also count a delete of an existing key as hit ...
Memcached, for example, counts every hit and miss for each command.
...
STAT cmd_get 2
STAT cmd_set 1
STAT cmd_flush 0
STAT cmd_touch 0
STAT get_hits 0
STAT get_misses 2
STAT delete_misses 1
STAT delete_hits 0
STAT incr_misses 0
STAT incr_hits 0
STAT decr_misses 0
STAT decr_hits 0
STAT cas_misses 0
STAT cas_hits 0
STAT cas_badval 0
STAT touch_hits 0
STAT touch_misses 0
...

So there are three solutions:

don't count a delete miss
also count a delete hit
far more detailed stats similar to memcached

Whats your opinion?

I definitely think it should be more detailed or not count it (if it's too much trouble)
The notion of a 'hit/miss' in a cache is when you go search it. I feel that the way it is affects the statistic.


Enable pkg_rpm and pkg_subrpm to create empty RPMs

At present we fail in two ways if we try to create empty RPMs:

we expect srcs to be both non-empty and will fail if it is empty and we have no spec file

we don't emit anything for the %files block in the RPM if there are no actual files and rpmbuild doesn't like this

This change tweaks the former condition so that srcs has to be non-None or we have to have a specfile, but will allow us to have an empty ([]) value for srcs.  Additionally, it injects %defattr(-,root,root) as a reasonable default for the %files blocks so as to allow rpmbuild to be happy with what we're providing.
Fixes #711

I still wonder why anyone would want an empty RPM, but I'll go with the flow on that.

The examples I've encountered thusfar involve having an empty / stub top level RPM with non-empty sub RPMs, although I figured it's harmless to also enable sub RPMs to do this too.


deprecate clear sky default in modelchain

[x] Closes #707
[x] I am familiar with the contributing guidelines.
[x] Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests (usually) must pass on the TravisCI and Appveyor testing services.
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.
[x] Code quality and style is sufficient. Passes LGTM and SticklerCI checks.
[x] New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
[x] Pull request is nearly complete and ready for detailed review.

Brief description of the problem and proposed solution (if not already fully described in the issue linked to above):

Appveyor failures are unrelated.


Fix audio recording issues

Summary
Audio recording permission is now requested by the library and
permission handling was added to the example code.
Hopefully:

Fixes https://github.com/watson-developer-cloud/android-sdk/issues/22
Fixes https://github.com/watson-developer-cloud/android-sdk/issues/17

Codecov Report

Merging #34 into master will not change coverage.
The diff coverage is 0%.

@@         Coverage Diff          @@
##           master   #34   +/-   ##
====================================
  Coverage       0%    0%
====================================
  Files           1     1
  Lines         150   150
  Branches       10    11    +1
====================================
  Misses        150   150

Impacted Files
Coverage Δ

...oper_cloud/android/myapplication/MainActivity.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


clean up some duplicated code related to TickQueue

nextTick and futureTick have different functionality.

Yes, the objects have different purpose. However, the implementation is the same...

Have a look at method tick. Different functionality AND implementation. Maybe you didn't understand the difference.

Indeed, now I see it. Sorry for your time. I'll just close this now...

The documentation might not have been to clear or maybe it was just me.
If we're here, we might as well ask try to figure it out why I was confused in the implementation interface (excepting the fact that I didn't pay attention when I should have).
Is there any contract regarding calling nextTick from a callback that was scheduled with a futureTick ? Because callbacks registered this way will be executed after the timers and this is not expected as declared in the documentation.
Is there any contract regarding calling futureTick from a callback that was scheduled with a nextTick? Because callbacks registered this way will be executed before any timers and this might not be expected.
Thank you!


Forking dnslib

Hi @mosquito, @Alviner,
I've noticed a few pull requests against paulc/dnslib which appear to be originating from this repository.
Before continuing, you might want to take a look at my PR https://github.com/paulc/dnslib/pull/61 where I did a lot of work to update dnslib to python 3.
In addition it looks like the original author (paulc) would prefer to have dnslib forked rather than continue under it's current name: https://github.com/paulc/dnslib/pull/61#issuecomment-2003796960
Depending on your intentions it might be worth starting a discussion with paulc if you did want to continue to maintain an updated dns lib into the future. In this regard I would be happy to contribute the code in that PR to teh cause, and may be able to help maintain it (though do not have the time to do heaps of feature work at the moment).
That said per my comment on that PR, unless you /really/ want to use dnslib, it might be better to focus efforts on the much more active dnspython rather than having 2 communities attempting the same thing.

Yep, I saw it. My aim the change this library and do not afraid the breaking changes. I want to rewrite some things using dataclasses and enum modules.

@nhairs Hi,
Thank you for reaching out and for your work on the dnslib project.
We have indeed decided to fork the package and will continue under the name dnslib3. We appreciate your efforts on the pull request; however, it changes too much at once and loses a lot of the history.
That said, PRs are always welcome! We have already integrated pyproject, pytest and are in the process of refactoring, during which we will also incorporate typing with a linter.
We would be happy to have you contribute to the new repository if you are interested.


Example period histogram plots

Period histograms based on the feature set.

Plots are simple. Can be fancied up as people like down the line.


chore: bdd-ghfjxy-import-1586287254 to 0.0.1

chore: Promote bdd-ghfjxy-import-1586287254 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


JIT .ll code error

While testing the other issue, I noticed after cleaning the JIT cache, another program was failing. After a whole lot of trial and error, this seems to be the minimum function to cause the problem:
atomic void t()
{
    int a, b;

    for (a=1; a--;) {
        sscanf("3", "%d", b);
        catch(b = 3);
    }
}

This results in (after compiling twice and calling f() on it, for some reason?) an error much like the following:
cache/05/05843706b1e0936d55143796c287a630.ll:51:42: error: use of undefined value '%l1m34'
        %l1r24 = call i32 %c9(i8* %f, i8 2, i32 %l1m34)
                                                ^
1 error generated.

This is a variant of the same problem, but now in the context of the JIT compiler.  b = 0; before the loop should solve the problem. Either DGD has to generate an initializer for b, or the JIT compiler has to.

I didn't have time to test this until today; should be fixed by https://github.com/dworkin/lpc-ext/commit/1bbfa35f3ec299f80382dda3136a64a75cd58416.

Looks like it's fixed now, thanks! ^^
Now I just need to convince clang to stop crashing. I think my server has a super old version for some reason...

Looks like it's fixed now, thanks! ^^ Now I just need to convince clang to stop crashing. I think my server has a super old version for some reason...

@nyankers The JIT compiler should work with clang 3.8 and later. The crashing may be due to a malformatted LLVM source code file. Feel free to open an issue for it, if you can identify the actual .ll file.

Ah, I'd deleted them when I cleared the cache, but sure thing. I wish there was an easier way to know which program goes with which .ll code, like if it could be commented in or something.
As far as I'm aware, dgd doesn't even send the program path (since JIT wouldn't be able to meaningfully use it anyway), but it's been a little while since I poked around there.

Ah, I spoke too soon. After the above change, cloud-server seems to throw a JIT error on boot-up and login as admin. Checking out before the above change, the error doesn't show up.
cache/22/228431a7bf3200b00fceb59b3bda826a.ll:6800:23: error: use of undefined value '%t140'
        %c193 = icmp sge i32 %t140, %t141
                             ^

It looks like the program failing might be /kernel/lib/wiztool.c. I didn't catch this at first because only admin uses that lib on my normal server, only saw it while trying to recreate another issue. ^^;

I reproduced it, it is indeed wiztool.c.

Should be fixed by https://github.com/dworkin/lpc-ext/commit/fa8443a256c27fd5d6afc4271101487e30002ef1.

Looks like it is, thanks!


Update README badges

Add version missing link
Fix broken likes link
Update health link

@deandreamatias thanks!

@all-contributors please add @deandreamatias  for doc


How to get one element record to another element in orchard

I have 2 element one is Element1 and 2nd one is Element2, and i have saving some data's in element1 and i need to fetch that data to Element2. How can i do that?

Hi! Please ask questions on the forum - we use GitHub for issue tracking. Thanks!

Ho ok....
I have also created one question in form
https://orchard.codeplex.com/discussions/646355


Layer norm for cudnnlstm?

I am training a very large and deep lstm-RNN. Using cudnnlstm can save memories and speed up the training process. However, I need some extra functions such as layer norm, adding attention wrapper, etc.
Is there a way to achieve this? Should I rewrite the c++ code and recompile? If so, which file of the source code contains the cudnnlstm implementation?

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.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

I think I just need a hint that if implementing the layer norm is possible and some simple guidelines regarding how to do this. If simply I can register a new op written in C++ and implement a new version of cudnn wrapper mimicking the cudnn_rnn_ops.cc functions. As I know, layer norm is just a moving average of weights and biases. If that part can be buried into C++ code, it should be okay. Or there can be a solution to embed the algo into python code.
I think this would be a great contribution to tensorflow community as cudnnlstm is very memory and computation saving. Adding layer norm and some other functions might be useful to make it perform better.

Still no response for this topic?

I'm very sorry for the slow response. @zheng-xq is probably better placed to comment on whether this can be done in Python or would need a new custom op.

Any update on this issue? @zheng-xq @michaelisard

Nagging Assignee @protoget: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 74 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 104 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 119 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @protoget: It has been 134 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


Create SECURITY.md

Submitting Issues
If you are submitting a bug, please create a jsfiddle demonstrating the issue.
Read before submitting Pull Requests

Pull requests to the master branch will be closed. Please submit all pull requests to the develop branch.
You will be required to sign a JS Foundation CLA before your pull request can be merged. Sign it right now.
Locale translations will not be merged without unit tests. See the British English unit tests for an example.
Do not include the minified files in your pull request. These are
moment.js, locale/*.js, min/*.js. Don't worry, we'll build them when
we cut a release.

Code organization
Starting from version 2.10.0 the code is placed under src/.
moment.js, locale/*.js, min/*.js are generated only on release.
DO NOT submit changes to the generated files. Instead only change
src/**/*.js and run the tests.

src/lib/**/*.js moment core files
src/locale/*.js locale files
src/test/moment/*.js moment core tests
src/test/locale/*.js locale tests

We're using ES6 module system, but nothing else ES6, because of performance
considerations (added code by the transpiler, less than optimal translation to
ES5). So please do not use that fancy new ES6 feature in your patch, it won't
be accepted.
Setting up development environment
To contribute, fork the library and install grunt and dependencies. You need
git and
node; you might use
nvm or
nenv to install node.
git clone https://github.com/moment/moment.git
cd moment
npm install -g grunt-cli
npm install
git checkout develop  # all patches against develop branch, please!
grunt                 # this runs tests, eslint and prettier-check

Changing locale files
If you have any changes to existing locale files, @mention the original
author in the pull request (check the top of the language file), and ask if
he/she approves of your changes. Because I don't know any languages I can't
judge your locale changes, only the original author can :)
In order for your pull request to get merged it must have approval of original
author, or at least one other native speaker has to approve of the change
(happens rarely).
Grunt tasks
We use Grunt for managing the build. Here are some useful Grunt tasks:

grunt The default task lints the code and runs the tests. You should make sure you do this before submitting a PR.
grunt test Run the tests.
grunt lint Perform syntax and code style checks.
grunt release Build everything, including minified files (do not include
those in Pull Requests)
grunt transpile:fr,ru Build custom locale bundles moment-with-locales.custom.js and locales.custom.js inside build/umd/min containing just French and Russian.
grunt size Print size statistics.

Note: If the prompt message is Code style issues found in the above file(s). Forgot to run Prettier?, Please run npm run prettier-fmt.
Becoming a moment team member
Moment's team members have extra powers and responsibilities. If you want to
become one -- be active in our repositories by answering issues, reviewing PRs,
discussing changes, submitting PRs for open bugs. Any help on
moment/moment,
moment/momentjs.com,
moment/moment-timezone will be
noticed.
Once you've proven to be trustworthy, submit your request to the
gitter chat, and it will be reviewed by the
existing team.
Once you become a member:

you can tell your friends
you can close issues submitted by others

But also:

be active in the repositories
pick up work nobody else wants to
attend a monthly meeting
participate in the internal slack group

If we are told about security issues, we release a new version. That's it. Contacting me is not complicated.


make three private methods protected for use in Hibernate Reactive

I can delete a little bit of copy/pasted code if you expose these methods for me.

Hi @gavinking ,
does an associated Jira already exist? if not can you please create one?
Thanks

applied to master and 5.4 branch.
Thanks @gavinking


Accessibility: setting HTML page language

From the audit per rancher/dashboard#4324, an easy quick win to improve accessibility is to add the lang=”en” to the  to allow readers to know the language of the page.

This will need dev attention as language swithces

Need to add code so that when the locale is changed we updated the attribute value

Test Environment:
Rancher version: v2.6-head 68c6c13
Rancher cluster type: HA
Docker version: 20.10
Browser: Chrome Build 102.0.5005.63

Testing:
Tested this issue with the following steps:

Open developer tools after navigating to Rancher UI
Go to Elements tab
Verify <html lang="en-us"... is in the top of the html

Result - Pass
lang tag is now set in the html


Persistence -- key.replace

Hello!
I was still getting permission errors.
Remove URL prefix for localStorage lookup
Keys changed in:
0ba4031d360f51cc977e15b652c0932e6fa5af65

Is this still necessary after the latest release from yesterday?


Prototype running tests from casm

Closes #1140
Introduced changes

Checklist

[ ] Linked relevant issue
[ ] Updated relevant documentation
[ ] Added relevant tests
[ ] Performed self-review of the code
[ ] Added changes to CHANGELOG.md

Ideally, we should be able to create CasmRunner on our own. It is needed because VM has pub(crate) fields which CasmRunner can read.
This is the reason why SierraCasmRunner is copied now (we need its internal CasmRunner to extract used resources from the VM)

Agree with @war-in, injecting the runner would be a nice way to do it
Did we consider moving away from the SierraCasmRunner altogether or breaking it up into parts, so we can reuse the ones that we need?

I think this probably should be followed up with upstreaming it so the code does not change a lot between versions, also i think this should be based off 2.4.0 since it's just around the corner of being merged

Will update this PR for 2.4.0 once relevant PRs are merged. And the changes will be upstreamed once we agree on some version.

Cairo PR: https://github.com/starkware-libs/cairo/pull/4644

Closed in favor of #1626


Error messages have to be more specific

Error messages are vague and missleading. They should be more specific on the actual error. Including errors with the backend.

I agree with this.

Fixed. Error messages are precise now and also give a description of what happend at the backend.


Update README.md

Typo in the go get link
go get -u github.com/Azure/azure-sdk-for=go/storage
Updated to
go get -u github.com/Azure/azure-sdk-for-go/storage
Thanks you for your contribution to the Azure-SDK-for-Go! We will triage and review it as quickly as we can.
As part of your submission, please make sure that you can make the following assertions:

[ ] I'm not making changes to Auto-Generated files which will just get erased next time there's a release.

If that's what you want to do, consider making a contribution here: https://github.com/Azure/autorest.go

[ ] I've tested my changes, adding unit tests where applicable.
[ ] I've added Apache 2.0 Headers to the top of any new source files.
[ ] I'm submitting this PR to the dev branch, or I'm fixing a bug that warrants its own release and I'm targeting the master branch.
[ ] If I'm targeting the master branch, I've also added a note to CHANGELOG.md.
[ ] I've mentioned any relevant open issues in this PR, making clear the context for the contribution.

Howdy @rishi8313, thanks for fixing this! Mind updating your change to be on top of the dev branch?


Column is searchable, still when I am searching it doesn't show result from that column

In the screen-shot above, the column 3 (Brand_name) shows as searchable=true, but when I search from the box, it doesn't shows result from that column.
In brand_name, i have comma separated values eg, brand 1, brand 2, brand 3
Other all columns are filtered from search box, except this?
can anyone help me with this issue? have anyone faced this??

I think you need to use filterColumn function here since global search will make your query looks something like brand like '%brand1,brand2%'. You need to explode the value and then use something like:
->filterColumn('brand', 'whereIn', explode(',', $brands));

I am trying to set filter column but I didn't got success. I also want to setup a drop-down filter column for isMember where I have three conditions (Member type 1, member type 2, member type 3), this will be at the bottom of the datatables. I tried many option, but I failed to get select filter at the bottom/top!
One more thing, when I loaded this DataTables directly with foreach loop, that branding filter is working but when I am using it with AJAX, it filter every column except brands!!
I'll try your solution.

Yes, it will filter all columns by default as it is the default behavior. I also suggest you use the filter() function and just write your custom query. See this for ref: http://datatables.yajrabox.com/eloquent/custom-filter

I am getting error of variable not found!!
Lets first discuss, point 1) In the DataTables listing, I am unable to search for Brand Names, which are comma separated valued. Other fields are searchable but not brands!?
As per your guide, I added the ->filterColumn('brand_name', 'whereIn', explode(',', $brand_name))
where 'brand_name' is my DB column name. I am getting error of $brand_name not found!!!
point 2) In the User DB table, I want to add the drop down select box, to search for i)registered Users ii)anonymous users and iii) silver_member user. Where I select from dropdown and whole table got filtered based on selected value. I have to use filter there??

ok. Point 1) resolved. I donno what error was, in the js I had written serverSide and I noticed that when searching the count in bottom was not updating. So I changed that into serverside, small case and it worked. All columns are searchable now.
Now I am working on Point 2. To keep a select box on search bar.

When I changed the serverSide into serverside, I realized that my datasets are loading at a time and it is taking 46 seconds to load.
This means actual keyword is serverSide. When this is set true, only 10 records are loaded as expected.

But when I use serverSide and use the search feature, the records are filtered but, the filter count shows total count, not the filtered count?!! Due to this, blank paginations are created !!
In pic attached you can see, I had searched for keyword "konn" but
recordsTotal  379
recordsFiltered  379
both are same!!

@tarunhere , serverSide: true is the correct syntax. Just to be clear, what version of the package are you using? Maybe try updating to the latest release (v5.5.5 atm). And test again. As per the demo link I provided, all is working fine.

Datatable "version": "v5.5.1" is the one, I am using. I had checked this, I don't know, why for search its not working!!

Please update to version v5.5.5, there were several fixes done and may have fixed this issue. You can see change log for details.

I think your issue was fixed on v5.5.3
v5.5.3

- Fix total filtered records count when overriding global search.
- Fix implementation of PR #95 on Collection Engine.

sorry to ask you this lame question?? but, how to upgrade package from composer??
I tried to change the version ~5.0 in composer.json to 5.5.5 but its not taking it.

i changed it ~5.5, but it says,nothing to update. Any ideas here!!

on your terminal, change dir to you project folder then run composer update.
cd /path/to/laravel
composer update

with composer update, all my dependencies will be upgraded. I just want to update this datatables.

if you want to update just the package. run composer update yajra/laravel-datatables-oracle

ok.
I was trying this
composer update "yajra/laravel-datatables-oracle":"~5.0"
my bad.
OH YES!! Its working now.
Thanks Yajra for all your help and this awesome plugin too.


Several security vulnerabilities in sphere-stock-import detected

Support reference number
Description
Security vulnerability in sphere-stock-import detected in dependencies.
Expected Behaviour
No security vulnerability in dependencies
Current Behaviour
Security vulnerabilities found are
54 vulnerabilities (18 low, 19 moderate, 16 high, 1 critical)

Context
Sphere-stock-import package.json
Possible Solution
Updating of necessary dependencies to fix vulnerabilities

issue closed with https://github.com/sphereio/sphere-stock-import/pull/80


Resolve past due balance has the wrong information

Step 4 is not correct.

In the Subscription overview page, click the red past due banner to settle the balance.

There is no red banner on this page. The settle balance page can only be found by clicking "Pay now >" in the email you receive from Azure. Please update the information on this page to reflect that or actually add a "Settle balance" link on the Subscription overview page.

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

ID: 8a4a411e-ee69-0830-ea5d-5998b9f42f8d
Version Independent ID: 0594c6a2-940f-0360-eb3d-4cb336a6eaec
Content: Past due balance email from Azure
Content Source: articles/cost-management-billing/manage/resolve-past-due-balance.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @genlin
Microsoft Alias: banders

@JohanWinther Thanks a lot for bringing this to our notice, assigned this issue to our document author @genlin to further review your feedback and update the document.

Hi @JohanWinther, I'm investigating your issue with the Azure Billing enginnering team. In the meantime, is your Azure subscription offer ID MS-AZR-003P or is your billing account type listed as Microsoft Online Services Program?

Hi @JohanWinther, I'm investigating your issue with the Azure Billing enginnering team. In the meantime, is your Azure subscription offer ID MS-AZR-003P or is your billing account type listed as Microsoft Online Services Program?

Yes, the offer ID for the subscription is MS-AZR-003P and the account type is listed as Microsoft Online Services Program.

@JohanWinther Thanks. I'll reply here when I have more info.


upgrade archaius

Pull Request Test Coverage Report for Build 1680

13 of 24 (54.17%)  changed or added relevant lines in 8 files are covered.
15 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.2%) to 62.878%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/router/cse/darklaunch.go
0
2
0.0%

core/router/cse/router_manager.go
0
4
0.0%

core/router/router_config.go
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

core/router/cse/router_manager.go
1
71.11%

core/router/cse/darklaunch.go
2
69.05%

eventlistener/loadbalance_event_listener.go
2
66.67%

core/loadbalancer/session_stickiness_strategy.go
2
78.46%

core/server/options.go
2
50.0%

server/highway/highway_conn.go
6
79.05%

Totals

Change from base Build 1676:
-0.2%

Covered Lines:
5449

Relevant Lines:
8666

💛  - Coveralls


"max words" confusion and zero loss with alpaca dataset

I am trying to finetune LLAMA-2 7B using another instruction tuning dataset. It is pretty similar in format to the alpaca dataset, but the instructions are slightly longer.
I'm often getting zero loss when training the model, and after some debugging i realized the the labels tensor used to evaluate the loss is usually full of zeros. I traced this back to the "max words" parameter in the alpaca dataset. https://github.com/facebookresearch/llama-recipes/blob/905f633dab92688b0a989f8d5cd11d86f882f534/ft_datasets/alpaca_dataset.py#L29
With a sufficiently long instruction, lines 63-65 beginning here https://github.com/facebookresearch/llama-recipes/blob/905f633dab92688b0a989f8d5cd11d86f882f534/ft_datasets/alpaca_dataset.py#L63 end up padding away the entire labels and replacing it with zeros, because the raw prompt is longer than the "example" (after the example is adjusted to fit max_words).
When I change max_words to a larger value, I get a lot of cuda errors like this:
read: [59,0,0] Assertion srcIndex < srcSelectDimSize failed.
/opt/conda/conda-bld/pytorch_1682343967769/work/aten/src/ATen/native/cuda/Indexing.cu:1146: indexSelectLargeIndex: block: [623,0,0], th
This even happens with QLora occupying only 10gb of an 80gb GPU so i don't think it is a memory issue?
Is there a way I can do instruction tuning with somewhat longer instructions? On some investigation, even a significant portion of the Alpaca dataset itself seems to get padded away to zero by this....

@iocuydi Can you please share the full output logs with errors? It will also help if you can share the code changes that you made for the custom dataset

After further debugging I realized I had forgotten to wrap the call to my dataset in "partial" as done here with alpaca:
https://github.com/facebookresearch/llama-recipes/blob/2243b962fa98c9c344f8f1a62be771bb1b71c56f/utils/dataset_utils.py#L17
After making this adjustment, I was able to pass much larger values of "max_words" without issue, and upon doing so I saw training behave as expected, with no more zero loss.

@chauhang why do we name it max_words?  isn't it max_tokens?

another part that is confusing to me, why is the max_words just set to 224?


Only store _edit_use_anchors_ metadata if value is not the default (3.x)

3.x version of https://github.com/godotengine/godot/pull/57863.
The default value is assumed to be false, so this metadata only needs to be stored if the value is true.
Bugsquad edit (keywords for easier searching): edit_use_anchors

Cherry-picked for 3.4.3.


Add the ability to treat Model instances as dictionaries

This change allows Model instances to be treated as dictionaries mapping attribute names to values. There are two motivations for this change:

Make it easier to replace or mix boto3 with PynamoDB.
Make it easy to convert a model to a language-agnostic format (probably JSON).

Regarding the first motivation, boto3 operations that get table entries return the entries as dictionaries mapping attribute names to values. The following is a simplified code snippet from the product that I'm working on. It originally used boto3, but it now uses PynamoDB. Its continued use of "in" to check whether "optionalAttribute" has been set and its continued use of dictionary-style lookups of the "firstName," "lastName," and "email" attributes demonstrate how this change can make switching from boto3 to PynamoDB easier.
def set_optional_attribute_in_user(user_id, new_attribute_value):
    user = User.get(caller_id)  # This used to be the 'Item' from a boto3 'get_item' operation.
    if 'optionalAttribute' in user:
        raise ValueError('The user already has this attribute.')

    x = user['firstName']
    y = user['lastName']
    z = user['email']
    . . . do some other work . . .
    return dict(user)  # This used to be "return user"

Regarding the second motivation, I'm using Lambda and DynamoDB as the backend for an iOS app. The app, written in Swift, asks a Lambda function, written in Python, to get data from DynamoDB, and the Lambda function responds with JSON dictionaries mapping models' attributes to values. I believe that the existing functions to convert PynamoDB models to JSON, such as _serialize and _get_json, do not provide what I need. Those functions produce results that match the way models are stored inside DynamoDB, while what I need is an abstraction away from DynamoDB.
With this change, one can call dict() on a model to get a Python dictionary mapping attribute names to values, and that Python dictionary can easily be converted to JSON. Lambda does it automatically if your function returns a Python dictionary. Any applications that use Python to access a DynamoDB database but need to manipulate the models in other programming languages may find this functionality useful.

Changes Unknown when pulling 79b12de600eea56ee248bb5667633e018328cb1d on csimmons0:model_dict into ** on jlafon:devel**.

+1

Reopening with new default branch

Is anyone prepared to review this?

In principle I totally get the desire to be able to easily convert a model to a dictionary. I spoke with a few people about the best implementation and we settled on exposing an as_dict method on the model (similar to MapAttributes) as a better approach. This would return a copy of the model data as a dictionary, but not expose any kind of additional set functionality. What do you think?

@garrettheel If it's any consolation that's what I do at the moment. I attach to a parent class model of all my models a toolset of common methods, One of them is as_dict(). The code is:
    def as_dict(self):
        '''
        Takes the current model and reviews the attributes to then translate to a dict
        '''
        return {key: getattr(self, key) for key in self._get_attributes().keys()}

Obviously, this is super primitive and doesn't take into account maps of models, et-all.
Copies work fine in my opinion but if people want to be able to edit via dict instead of instance methods then I'd be inclined to run with that.
--Karl.

Would this change also allow dictionaries to be converted to a model instance?

👍
This is a great change, can we get it in?

Is this gonna get in any time soon?

any update on this feature? @jlafon @garrettheel .


Cannot connect to api.ultralist.io right now.

When I try to synchronize my todo list I get this:
~
❯ ultralist sync
Give this list a nametodos
Cannot connect to api.ultralist.io right now.

I tried with both my IP and using shadowsocks proxy (I thought that host is unreachable) but neither non-proxy nor proxy requests work.
OS: Manjaro Linux x64
Installed with: Golang

hey @talentlessguy I'm not able to repro on my end.  could be a network blip or something?  are you still having this problem?

@gammons closing it. After reboot everything works nice, however, would be cool to output the stack trace or any warning to know what's wrong

yeah, the stack runs on heroku right now and I wouldn't say I have excellent logging/monitoring there.  That should change over time.


TypeError: fs.existsSync is not a function

Hi,
I am getting an error:
Uncaught TypeError: fs.existsSync is not a function
This link: provides a workaround to the problem.  To be entirely honest I don't really understand the cause of the problem, but it certainly works for me.
I am using Electron, React, Redux and Webpack.
The full trace that I get is this:
Uncaught TypeError: fs.existsSync is not a function
    at eval (Y:\testdesigner_MVP\node_modules\electron\index.js:6)
    at Object.<anonymous> (bundle.js:2352)
    at __webpack_require__ (bundle.js:679)
    at fn (bundle.js:89)
    at eval (Y:\testdesigner_MVP\node_modules\redux-electron-store\lib\electronRendererEnhancer.js:82)
    at createStore (Y:\testdesigner_MVP\node_modules\redux\es\createStore.js:51)
    at eval (Y:\testdesigner_MVP\app\lib\stores\renderer_store.js:38)
    at Object.<anonymous> (bundle.js:3937)
    at __webpack_require__ (bundle.js:679)
    at fn (bundle.js:89)

The line of code that I wrote (renderer_store.js:38) is:
let renderer_store = createStore(rootReducer, main_store.getState(), enhancer);
which in turn leads (eventually) to electronRendererEnhancer.js:82:
 var _require = require('electron');
which I presume is derived from renderer-enhancer.js:
const { ipcRenderer, remote } = require('electron');
If I change electronRendererEnhancer.js:82 to be:
 var _require = window.require('electron');
the error goes away.
As I said at the top I don't really understand the root cause of this.  If it is appropriate, then perhaps renderer-enhancer.js could be updated to be:
const { ipcRenderer, remote } = window.require('electron');
but that may have other consequences I can't see.
If the change is not possible, then hopefully this issue will help others.

yes when you try to require('electron'); with nodeIntegration: false it dsplay this strange error.

Just want to re-surface this thread. Did anyone end up finding a solution to this issue?
Setting nodeIntegration: true didn't fix it and I also got window.require is not a function. I use electron 10.0.0 if it helps.


Release/release with tweet

Pushing a new stable release since we finished all the goals and looks like everything should work :-)

write tests and get good coverage (we're at 90%+ coverage)
publish a tweet
integrate with ourselves

let's hope we get a tweet on this release :-)

Pull Request Test Coverage Report for Build 213

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.949%

Totals

Change from base Build 197:
0.0%

Covered Lines:
65

Relevant Lines:
69

💛  - Coveralls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore,refactor(egen): reformats get_started_with_custom_training_autologging_local_script.ipynb notebook

The following changes are part of the PR:

Adds colab enterprise
removes boiler plate
lint errors rectified
restructure according to template including changes like "REGION" to "LOCATION"

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[ ] Use the notebook template as a starting point.
[ ] Follow the style and grammar rules outlined in the above notebook template.
[ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

If you are opening a PR for Community Notebooks under the notebooks/community folder:

[ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

If you are opening a PR for Community Content under the community-content folder:

[ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
[ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

/gcbrun

/gcbrun


Run RC workflow on MacOS rather than Ubuntu

Goal

Testing

Release Notes

WHAT:
WHY:

#1025  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Jul 3, 12:14 PM EDT: Graphite rebased this pull request as part of a merge.


Feat: update apiClient in js to skip validate response

Feat: update apiClient in js to skip validate response

LGTM


istioctl replace an existing rule causes a 404 reponse

Hello, I noticed that when I'm updating the istio pilot rules while serving traffic, sometimes I get back a 404 from envoy.
I have a service with 3 different backends (istioctl kube-inject omitted)
apiVersion: v1
kind: Service
metadata:
  name: version
  labels:
    app: version
spec:
  ports:
  - port: 5000
    name: http
  selector:
    app: version
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: version-one
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: version
        version: v1
        env: production
    spec:
      containers:
      - name: app
        image: <PRIVATE_IMAGE>
        ports:
        - containerPort: 5000
        env:
        - name: VERSION
          value: "v1"
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: version-two
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: version
        version: v2
        env: sandbox
    spec:
      containers:
      - name: app
        image: <PRIVATE_IMAGE>
        ports:
        - containerPort: 5000
        env:
        - name: VERSION
          value: "v2"
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: version-three
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: version
        version: v3
        env: sandbox
    spec:
      containers:
      - name: app
        image: <PRIVATE_IMAGE>
        ports:
        - containerPort: 5000
        env:
        - name: VERSION
          value: "v3"

an ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: version-ingress
  annotations:
    kubernetes.io/ingress.class: istio
spec:
  rules:
  - host: <PRIVATE_DNS>
    http:
      paths:
      - backend:
          serviceName: version
          servicePort: 5000

and a default istio traffic rule
# As default rule, route all traffic to the specifig tag (line 10)
type: route-rule
name: version-default
namespace: default
spec:
  destination: version.default.svc.cluster.local
  precedence: 1
  route:
  - tags:
      version: v1
    weight: 100

I have a Python script that opens a request to the endpoint to read the environment variable VERSION
$ python tester.py counter 10000 <PRIVATE_DNS>/envvar/VERSION
2017-07-12 12:04:26,729 - __main__ - INFO - Version: v1
2017-07-12 12:04:26,767 - __main__ - INFO - Version: v1
2017-07-12 12:04:26,816 - __main__ - INFO - Version: v1
2017-07-12 12:04:26,889 - __main__ - INFO - Version: v1
2017-07-12 12:04:26,928 - __main__ - INFO - Version: v1
2017-07-12 12:04:26,967 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,013 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,048 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,084 - __main__ - INFO - Version: v1
[ ....]
2017-07-12 12:04:27,268 - __main__ - INFO - Version: v1

If I change the routing rule to include the other backends
type: route-rule
name: version-default
namespace: default
spec:
  destination: version.default.svc.cluster.local
  precedence: 1
  route:
  - tags:
      version: v1
    weight: 30
  - tags:
      version: v2
    weight: 20
  - tags:
      version: v3
    weight: 50

and then I apply it with istioctl replace -f istio-default-route.yaml, this is what happens
2017-07-12 12:04:27,233 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,268 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,301 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,331 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,363 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,400 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,433 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,466 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,502 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,535 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,567 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,596 - __main__ - INFO - Status code: 404
2017-07-12 12:04:27,634 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,671 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,712 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,760 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,801 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,838 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,878 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,914 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,951 - __main__ - INFO - Version: v1
2017-07-12 12:04:27,987 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,027 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,061 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,104 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,139 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,181 - __main__ - INFO - Version: v1
2017-07-12 12:04:28,222 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,278 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,318 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,377 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,412 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,449 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,498 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,535 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,570 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,605 - __main__ - INFO - Version: v2
2017-07-12 12:04:28,641 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,679 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,715 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,751 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,788 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,822 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,859 - __main__ - INFO - Version: v3
2017-07-12 12:04:28,896 - __main__ - INFO - Version: v3

Is that 404 expected? This is what a header looks like
Headers: {'date': 'Wed, 12 Jul 2017 11:04:27 GMT', 'server': 'envoy', 'content-length': '0'}

This is interesting. Thanks for reporting this and the steps to reproduce this. Can you try the python client from a pod in the cluster, and try to access that service via the local envoy in the pod?
i.e. package this client as another istio app, and do the same route change stuff. And see if the 300ms downtime happens internally as well.  This would help us narrow down the issue to either our ingress implementation or across ingress and internal envoys.
Alternatively, it would be good to take a snapshot of RDS/CDS outputs from istio-pilot, as it would help us understand if this is a problem in Envoy or a problem with the way we are switching to a new config.

cc @mattklein123 @htuch @dnoe - in case you happen to know off the top of your head, whether this downtime is expected. I pretty much think that this should not happen unless RDS update is going ahead of CDS update.

If RDS is received before CDS, yes, this is expected. This is related to the conversation in https://github.com/lyft/envoy-api/issues/102. However, it's difficult to say exactly what is happening here without further debugging.

Yes, a route rule can introduce a new cluster (for special version, for example), and it's hard to coordinate CDS/RDS. I guess with ADS we can do atomic update and solve the issue. Another way could be to use metadata on network endpoints, to avoid creating multiple clusters in the first place (for v1,v2,v3 routes, route rule should point to a cluster + version selector).

@kyessenov Do you need atomicity or jsut single stream semantics with ADS? It's evolving as we speak, let me share my draft with you offline.

Sequencing of updates (CDS prior to RDS) is sufficient. I think that should be a requirement on ADS to process updates bottom-up.

ADS is free to allow the management server to drop traffic if it wants. ADS is really just a mux of the existing xDS.

I wouldn't want to go down the dynamic cluster stuff (using endpoint metadata). Either way, that would still have the same issue, until SDS info with metadata is propagated.
I think ADS with the ability to sequence updates is sufficient (I would potentially extend it to SDS as well if possible).

Hi all, I was able to reproduce the same behavior from a pod inside the cluster running the python script.
Unfortunately, the error seems quite random: sometimes I do an istioctl replace and I don't lose any requests, sometimes I have the 404.

@maruina I think we have narrowed the issue. Its an issue/feature of the way we update the route tables and upstream clusters in the Envoy proxy. Today we have two independent updates which is causing the random 404s during updates. But rest assured that this is fixable :)

Ok, thanks!
Let me know if I can help!

Issue moved to istio/istio #1437 via ZenHub


Mismatch of the input variable of editor.batch_edit()

Dear EasyEdit Team,
I think there is a mismatch for the batch edit function (under the editor class, see here). Should the "locality_ground_truth" be "portability_inputs" and "locality_prompts" be "locality_inputs" just like the edit function? (They are using the same prepare requests function.)
It is possible that I missed something or got something wrong.
Regards,
Syon

Dear Syon,
Thanks for pointing out this issue, we will handle it as soon as possible.
EasyEdit Team

Thank you for your question. I have updated the parameter names, and the function should now work correctly https://github.com/zjunlp/EasyEdit/commit/529b4410e8d2f88a8e40c195bd15652ff86b5856. However, please note that not all editing methods support batch editing. For further details, you can refer to the batch_editor.py file.
Let me know if you have any other questions!

hi, do you have any further questions?

Dear EasyEdit Team,
I'm sorry for not getting back to you sooner, but I currently do not have any questions for this one. However, I do encounter an issue with implementing GRACE. The error message leads me to this function.
I have solved it by changing it to:
def split_epsilons_in_half(self, nearest_key, smallest_distance):
    # print(smallest_distance, self.epsilons[nearest_key])
    # self.epsilons[nearest_key] = self.epsilons[nearest_key].to(torch.float)
    self.epsilons[nearest_key] = (smallest_distance.item() / 2) - 1e-5 # Cut nearest epsilon in half
    self.epsilons[-1] = smallest_distance.item() / 2 # Cut new epsilon in half

I am not sure whether this is caused by my running environment, but I just inform you about this.
Thank you very much for your responses and patience.
Regards,
Syon

This applies to the case where batch size (bs) is 1. If you want to edit multiple instances simultaneously, GRACE is likely not supported (we refer to the official implementation of GRACE for this: https://github.com/thartvigsen/grace).

yeah, I did not use batch edit for grace, I used the editor.edit()

hi, do you have any further issues?


Add support for configuration in F#.

This pull request replaces: https://github.com/workspacer/workspacer/pull/349
Future work: Actually use the IConfig interface and possibly move C# configuration out of main project.

Thanks for cleaning this PR up.
As a high-level comment (without looking into the code itself), this is a lot of code, for a possibly new feature... But there's no documentation for it.
Would it be possible to add a section to the quickstart with a short example of/note about how to use this feature?
That would also make it easier (for a non-regular F#ie) to put the code in the PR into context.

I'll add a section to the documentation as soon as I find the time, until then this pr can be left as is, I'll let you know when the documentation is done.

@josteink I have now updated the quickstart with some information on using the F# configuration feature.

In more testing I discovered a quite bad issue with loading System types such as arrays. Being unsuccessful in fixing it I have put this in draft and on hold.

No problem. Let me know when you have something new to review.

The issue is mainly with compiling the wrong system libraries (as you can't choose apparently), so the solution is to resolve those assemblies to the already loaded version.

Looking pretty good now IMO. That said, I still have a few small nitpicks.
With those sorted out, I think this PR should be ready for merging.

I'd like to move over to this kind of configuration, mainly for syntax highlighting and other QOL features this brings, but my csx config is pretty complex right now, and I'd like to know if there are plans of providing a more indepth configuration example for people moving over that don't exactly know the direct translations from an C# to an F# environment. Here's my current config

@Janthor I don't currently have plans for adding extra documentation on translations to F#. I did take the liberty to convert most (I don't have the aliases) of your configuration to F#. Here is a link to the file.
Here is a link to the F# configuration, please change the paths in the #r @"..." directives to match your system
Note that conversion to F# is relatively straightforward:

convert all var and other variable declarations to let.
convert all mutable assignments to use <- instead of =,  bitwise or to ||| and logical not to not
replace all lambda expressions to F# functions (and surround in brackets if necessary) (x => y becomes fun x -> y)
change definitions of arrays to use  [| |] and remove commas in lists (newline is new item)

Also, that's a lovely bar

it's even more lovely if you install a nerd font 👀. Thanks a ton for the explanation, I'd love to have my config in one of the examples too. I'll update it even more over time.

hate to be commenting on a merged PR for this, but can u give me the missing link that didn't come through here @tlsomers ?

Here is a link to the F# configuration, please change the paths in the #r @"..." directives to match your system

I tried following your brief instructions but I hit a roadblock while declaring the bar, and I feel a practical example would make me understand it better.
This is what I came up with, but I feel i'm doing something extremely wrong lmao
        //* Left Widgets
        LeftWidgets <- fun () -> new IBarWidget[||] =

            new ActiveLayoutWidget()
            new TextWidget("|")
            new WorkspaceWidget() =
                WorkspaceHasFocusColor <- positive
                WorkspaceEmptyColor <- alt_background
                WorkspaceIndicatingBackColor <-  urgent

Hit me up on Discord if you want to keep the github clean Janthor#3673 (a public Workspacer server on Discord would be great also)

Here's the relevant gist:
https://gist.github.com/tlsomers/52fc7da2425bfd2caad4393ce3791e7f
I also sent you a request if you need any more help :)


Update 'Documenting REST API endpoints' docs.

Current Behaviour
On visiting /documentation/api.html#how-it-works
The first paragraph says:
To understand how this documentation system works, start by reading an existing doc file (api_docs/render-message.md is a good example)
Similar thing, in the first paragraph of /documentation/api.html#parameters
But there is no such file -- api_docs/render-message.md
In https://github.com/zulip/zulip/commit/23b991a80106a1d673e387fc7ec11e44b8a8d748 , we removed render-message.md in favour of using a common template.
Expected Behaviour
We should update the paragraphs to -- "start by reading api-doc-template.md and /messages/render endpoint in zulip.yaml" or something better.

could you please assign this issue to me?

@zulipbot claim

@zulipbot add "help wanted"

@zulipbot add "good first issue"

@zulipbot claim

@1010nishant you can claim now this issue.

@zulipbot claim

@zulipbot claim

@iSatVeerSingh
I think, it is not a good practice to add help wanted and good first issue tags yourselves. It is mostly done by maintainers.
@alya please have a look at this issue. This needs some discussion regarding the actual wordings we should have.

@iSatVeerSingh I think, it is not a good practice to add help wanted and good first issue tags yourselves. It is mostly done by maintainers.
@alya please have a look at this issue. This needs some discussion regarding the actual wordings we should have.

Indeed.
I'm not the right person to help with wording here -- @laurynmm could you take a look at this one?

@prakhar1144 - Thanks for the ping! Yeah, it's definitely not great that we reference a non-existing file.
As I was reading through all of this section to write up a summary of the changes that needed to be made, I felt like it was going to be just as much time as me doing a quick revision pass. I've got #24667 as a rough draft of updates to this section and would appreciate folks feedback / thoughts.


Wither erases inherited fields

After calling generated @Wither-method of child class all inherited fields will be erased.
Example:
public abstract class Bar {
    @Getter private long id;
    public Bar(long id) {
        this.id = id;
    }
}

@AllArgsConstructor
public class BarBell extends Bar {

    @Wither private String text;
    @Wither private int a;

    public BarBell(long id) {
        super(id);
    }
}

Now when we use generated methods from outside, variable id will be erased.
    long id = new BarBell(123L).withText("text").withA(2).getId();

    System.out.println(id);

Output: 0.

Your example doesn't compile: Implicit super constructor Bar() is undefined. Must explicitly invoke another constructor.
But if it did, you'd be right. Lombok knows nothing about inherited fields and there's currently no solution for this. The problem happens already with the @AllArgsConstructor.
There's not even a good workaround. I just avoid inheriting from classes containing fields. Sometimes, it's a pain, but usually still much better than doing everything manually.

Sorry for not checking code, I was sure it's OK, but @AllArgsConstructor requires empty constructor in parent class.
This issue is very discouraging to me because I still have to create a ton of withSomething boilerplate, and avoiding the extension of model classes makes impossible to implement desired app design... Much hope it will be resolved...

Sorry for not checking code, I was sure it's OK, but @AllArgsConstructor requires empty constructor in parent class, which I forgot to add.

That's another expression of the impossibility to access the parent class. If Lombok could access it, then it could find the non-empty constructor and call it. Note that for final fields (i.e., those @Wither is meant for) there can be no useful empty constructor.

Much hope it will be resolved...

I don't know the problem exactly (I'm just someone having contributed some small piece), but IIUIC information about other classes is not available at the time Lombok does its job. The problem is called "resolution" and blocks also other useful features.

A positive post here:
I continued to dive into Lombok features and found the solution of my particular problem (impossibility to chain withSomething-methods with saving field values which are already initialized).
There's no need to use @Wither, just @Setterwith @Accessors(chain = true). This will make setSomething-method return this just like withSomething-methods.
Example:
@Accessors(chain = true)
public class StatusAdapter extends EndlessItemAdapter<Item> {
    @Setter private TCallback<Long> onUserTap;
    @Setter private TCallback<String> onImageTap;

    // Adapter implementation
}

Then:
StatusAdapter adapter = new StatusAdapter()
        .setOnUserTap(id -> UserActivity.start(this, id)
        .setOnImageTap(url -> ImageActivity.start(this, url);

Hey thank you @hunter-t . Your tip saved my day.

@jose-jurado Note that @Accessors(chain = true) does not but provide the chaining syntax possibility. The @Setter still modifies an existing object, while the @Wither returns a new object without changing the old one. Sometimes, it doesn't matter, sometimes, you need the former, sometimes, the latter.

Hey thanks for the warning @Maaartinus . I was aware but it fits my scenario anyway.


Compute budget program

In this PR I attempt to create the necessary instructions to interact with the compute_budget_program which also resolves  #293
[CAVEAT]:
SetComputeUnitPrice and SetComputeUnitPrice work just fine, but, SetLoadedAccountsDataSizeLimit and SetLoadedAccountsDataSizeLimit seem to throw abstract errors despite the payload matching and deserializing to the expected payload. Not quite sure if it is because of a lack of a feature activation.
the 2 latter instructions throw the errors:
Error processing Instruction 0: invalid instruction data and  LoadedAccountsDataSizeLimit set for transaction must be greater than 0.
tried digging deep but couldn't find the exact cause of the errors, can someone point me towards some plausible hypothesis for the errors?

Solders covers this https://kevinheavey.github.io/solders/api_reference/compute_budget.html
Though it's missing a set_loaded_accounts_data_size_limit wrapper if you want to add it to solders :)


doc(mempool): skeleton of QoS ADR

This PR reflects the initial discussions, both internal and with users on introducing QoS to the CometBFT mempool.
We will work on top of these changes until we have a problem definition and preliminary design to circulate with our users.
This ADR is not complete -- it's just a skeleton -- so it will not be merged to main but rather to the newly created feature/mempool-qos feature branch.

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[x] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

Thanks folks for all your comments! I updated the text with some of your ideas. I am merging this now, to keep working on it


Updated _build.thor

I was getting an error on deploying and notice that the _build.thor file needed a ,[] after the clean call for production. Thought this would help.

Fixing a bug with deploy to a CDN and removing manifest.appcache for the default site.


Legacy Data Visualization Certificate shows incorrect Issued date

When viewing my Legacy Data Visualization Certificate, the Issued date in the top right corner always displays the current date, not the date the Certificate was completed.
See:
https://www.freecodecamp.org/certification/michaelbecker/legacy-data-visualization
(appears to always have the current date there)

I'll also add, although it may need a new thread or belong somewhere else, that the legacy certificates that were already earned should not be rebranded as "legacy certificates" because it devalues the work that went into getting them when they were not legacy.  The date issued and the certificate should suffice.
Universities don't send out new diplomas when they change their curriculum with new information saying your BS/MS/MA/MD degree is "legacy".

Rebranding the certificates as "legacy" could also cause problems for folks job hunting. Potential employers seeing a "legacy certificate" may conclude that the work accomplished is already out of date.

@michaelbecker I see seemingly correct dates for my legacy front-end and back-end certs, but the legacy data visualization is showing today's date.
@QuincyLarson any thoughts on removing the "legacy" label - they do make a good point, although there would be two certs with the same name (data visualization) - which could be confusing or cause problems.

I've been poking around the code a bit for this one. My guess is that in server/boot/certificate.js, line 427, completeDate is null, which would always give the current date for the ctor of the Date class when this happens. Which implies that somehow completeDate isn't getting set. I'm still working through lines 418-421 trying to guess what's going on there (my background is C / C++, so declaring const {}  on the left hand side is throwing me for a loop).
          const { completedChallenges = [] } = user;
          const { completedDate = new Date() } = _.find(
            completedChallenges, ({ id }) => certId === id
          ) || {};

Thanks @moT01 . I also found this last night https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment
So completedChallenges is an array pulled from the user object using destructuring with a default assignment. completedDate is looking through the completedChallenges array ("_.find(...)") trying to match id with the certId. I'll guess completedChallenges is an array of objects, in which each object includes an id and completedDate field. This code is used for all certs, but only the Legacy Data Visualization has a problem here, so this code in and of itself is probably correct. Which implies that the data being fed into it is a problem, such that it can't find a completedDate for the Legacy Data Visualization cert only.
So my thoughts are:

Possible mismatch between id and certId. Did this id change inadvertently between the old site and the legacy site?
Were completedDates saved for the old Data Visualization Certificate in the first place?

I think the next step to debug this would be to just console.log the values of id, certId, & completedChallenges[] on an instance with access to whatever backend storage FreeCodeCamp actually uses. Should be easy to find from that point on, since this is 100% reproducible.
Unfortunately, I don't have that kind of access, so I don't think I'm going any farther with this bug. Hopefully this offers a jump start to whomever picks this bug up in the future.

@michaelbecker nice digging - I wonder if it's a naming conflict, it's the only legacy cert with the same name as a new one

I cannot reproduce this on my local version - leads me to think that anyone who would claim the legacy data vis certification since the new site went live would not have this problem...
I downloaded all my data from the settings page of the live site - I cannot find the string of the "legacyDataVisId" anywhere in my downloaded data (the string is from https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/server/utils/constantStrings.json). I can find the strings of all the other certs I have claimed - So the id got changed somewhere along the lines I'm guessing - the downloaded data is hard to decipher, but it looks like there may have been two sections for data vis that got created when you claimed the cert on the old site...
{"id":"58d9cc820ce2197370032a13","completedDate":1490789539522,"solution":null,"challengeType":7,"files":[]},{"id":"561add10cb82ac38a17513b3","completedDate":1491530482152,"solution":null,"challengeType":7,"files":[]}

I cut some code out but these are surrounded by projects required for the cert


hydration mismatches error in nuxt 3 static generated ssr mode

Environment

Operating System: Darwin
Node Version:     v14.21.1
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      ssr, modules, i18n
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://euphonious-crepe-e4239a.netlify.app
Try to select a different locale and refresh the page
After page refresh the .selected underline style always applied to EN
Got Hydration completed but contains mismatches. error message in console and the UI rendering issue

Describe the bug
The bug happens whendetectBrowserLanguage.useCookie config is true and nuxt is in ssr: true  SSR mode.
No problem in SPA mode.
Additional context
Full code for reproduction:

Logs
No response

Thank you for you reporting!
I checked your reproduction minimum app on netlify!
However, We would like to get your that codes, because we would like to debug it!
Could you provide your codes please? 🙏

Hi @kazupon here is the code https://github.com/1isten/nuxt3-i18n-bug

I've just fixed this issue, and published edge version
If you would try to use, you can use<EMAIL_ADDRESS>Thanks!

@kazupon Thank you it works


Fix release publish step

Fixes https://github.com/CesiumGS/cesium/issues/11130
This is now fixed on the website itself, but deploying our Cesium releases was broken after the AWS SDK updates.
The error code are no longer what we expected before. Instead I followed parsing the errors as recommended in the docs, though notably the documentation is not correct for the particular error we need to handle– the property is $metadata instead of $$metadata
We didn't catch this the first time around because the file already existed, and therefor didn't throw an error.

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Update client deps

Description
Update lock file with newer dependency versions. Other changes are needed to keep everything working.
This was done by deleting and regenerating the lock file and node-modules, then debugging the various issues that occurred.
This was repeated until no more issues occurred.
After this change, deleting the root lock file and ./node-modules and regenerating them becomes a no-op.
Note that this does not change anything that is shipped to Fluid Framework users: all changes are in the root package json, examples and the lock file, with one exception:
experimental/PropertyDDS/packages/property-inspector-table/package.json had a dep pinned to avoid a build error. This will fix the issue for anyone installing this package as well.
Reviewer Guidance
The review process is outlined on this wiki page.
Open questions

This fails the "syncpack:deps". What should we do about that? The changes are mostly fixes for cases were "^" ranges permitted braking changes, so the guidance of using "^" cannot be used to fix the errors.

After this change, deleting the root lock file and ./node-modules and regenerating them becomes a no-op.

This is only true as long as nothing else gets published that matches our dependency ranges, right? Is there some advantage to finding updates this way vs. pnpm update or something similar? It seems like either way you end up having to modify pnpm.overrides manually.
I get confused about how this affects our customers. Nothing in pnpm.overrides is respected by downstream consumers right?
Finally, why prefer root level overrides to packageExtensions in the packages that need them? I don't see any benefit to putting everything in the root. It makes it more difficult to reason about the scope of the change, or why it's been made.

For the synpack issues, I think this section of the syncpackc onfig is too strict and should probably just be removed:
https://github.com/microsoft/FluidFramework/blob/afe4310b0b60647e5e8dd88e6ac915deefcb4916/syncpack.config.cjs#L72-L78
There may be other adjustments needed. There are sections for packages that should use ~ deps, for example, so you might just need to add some entries. The overall goal of the syncpack config is to keep both version ranges and dep range types in sync across all packages, and also enforce some policy for some packages. If something seems wrong there it's worth discussing. The existing config was a best effort based on how the repo looked when it was created.

After this change, deleting the root lock file and ./node-modules and regenerating them becomes a no-op.

This is only true as long as nothing else gets published that matches our dependency ranges, right? Is there some advantage to finding updates this way vs. pnpm update or something similar? It seems like either way you end up having to modify pnpm.overrides manually.

Yes.
I personally am more confident in my understanding of what this workflow does than how pnpm update works in a workspace (for prod deps its the same as what a use would get when making a new project using our packages). Also pnpm update changes package files as well as the locks, which would impact customers and I don't want to do that:
As noted in the PR description this has no impact on our customers. This workflow is simply an easy way to confirm that if you only follow our dependency ranges everything works.
You only have to modify overrides when someone made a mistake and implied a version should be compatible when it isn't. This needs to be done regardless as you mention.

I get confused about how this affects our customers. Nothing in pnpm.overrides is respected by downstream consumers right?

Nothing in our root package.json file or package lock impacts customers. See PR description for the one case that does impact customers.

Finally, why prefer root level overrides to packageExtensions in the packages that need them? I don't see any benefit to putting everything in the root. It makes it more difficult to reason about the scope of the change, or why it's been made.

Because I wanted the above noted workflow to work, and our use of package extensions didn't accomplish anything while overrides did. I'm not sure if its a pnpm bug, or if extending a package that already has a * dep with a more specific dep doesn't replace the existing dep (maybe extensions only work for missing deps?), but as far as I could tell the extension we had had no effect, and I needed to accomplish that somehow.

Because I wanted the above noted workflow to work, and our use of package extensions didn't accomplish anything while overrides did. I'm not sure if its a pnpm bug, or if extending a package that already has a * dep with a more specific dep doesn't replace the existing dep (maybe extensions only work for missing deps?), but as far as I could tell the extension we had had no effect, and I needed to accomplish that somehow.

Got it; makes sense. Sounds like a bug to me, but maybe packageExtensions have to be in the workspace root to take effect?

Nothing in our root package.json file or package lock impacts customers. See PR description for the one case that does impact customers.

Thanks - I completely missed that.

Got it; makes sense. Sounds like a bug to me, but maybe packageExtensions have to be in the workspace root to take effect?

The docs don't indicate this (unlike for overrides where they explicitly mention that). I have just tested putting it at the root and I still get the error in install:

ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
This error happened while installing the dependencies of<EMAIL_ADDRESS>Your Node version is incompatible with "registry.npmjs.org/marked/5.0.2".
Expected version: >= 18
Got: v16.19.1
This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

This is what happens when the override for simplemde>marked is not applied.


most of these casts are apparently no longer necessary

No changeset since it's only type casting level changes

changeset?

PR body xP


[ListView] Exceptions in getRowData, renderRow, etc are silently swallowed

ListView should either explicitly rethrow or log these errors or let them bubble up to the redbox error handler.

See #1965 for same issue and more details.


Datatable

Hi i want to edit your table to datatable but actually i don't know how can i do this. table doesn't be
responsive when i add datatables.js to project

Hi,
Thank you for the interest in our products. Can you please show me the code?
Best,
Rares


Dummy users no long work using internal shortcut

Current Behavior
Using cmd + shift + 1 on the local instance brings up an option to quickly change between users. However, this no longer works – either the user cannot be found, or an error is presented saying:

Cannot read the properties of undefined (reading 'attributes')

Acceptance Criteria

[ ] Quick user select works

@frozenhelium do you think this is related to MFA?

@frozenhelium has implemented a feature flag to disable MFA locally, will test if this works now.


Same error here " bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)

import urllib3
import urllib3.contrib.pyopenssl
import certifi
urllib3.contrib.pyopenssl.inject_into_urllib3()
http = urllib3.PoolManager(
cert_reqs='CERT_REQUIRED', # Force certificate check.
ca_certs=certifi.where(),  # Path to the Certifi bundle.
)
You're ready to make verified HTTPS requests.
try:
r = http.request('GET', 'https://devapi.trustmile.com/static/index.html')
print r.status
except urllib3.exceptions.SSLError as e:
print e

This is a bug report for urllib3, but you have issued it against Requests. =) Please open this bug report on the urllib3 repository.


tools: add a stack_decode target

This is handy if you want to hermetically run a test with stack decoding.
Signed-off-by: Benjamin Peterson<EMAIL_ADDRESS>
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Thanks would you mind updating the docs here? https://github.com/envoyproxy/envoy/tree/main/bazel#stack-trace-symbol-resolution
/wait


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1401 ms

Resolved: Bofrost.de performance has improved in b415253.


Hyperparameter optimization and TensorFlow

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): N/A
OS Platform and Distribution: Linux-Ubuntu (17.10)
TensorFlow installed from: Binary
TensorFlow version:  1.5.0
Python version: 3.6
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: N/A

Describe the problem
I know that this question has already been addressed here and in Stack Overflow, but until the moment I do not see many evolutions on the subject.
Saw this approach here A Scikit-learn compatible Deep Neural Network built with TensorFlow,, that is, using TensorFlow (model build) and Scikit-learn to make the model's Hyperparameter Tuning.
So far this approach is the most correct?
Really wanted to be able to contribute and work with the optimization of hyperparameters along with the TensorFlow models.
I find this technique very important in Deep Learning...
thanks in advance

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.
Have I written custom code
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Take a look to the Kubeflow related project: https://github.com/kubeflow/hp-tuning

Hello,
I've not had any feedback nor here much less in stackoverflow ...
I've seen several alternatives, one of which I have described here before, and another in this repository here
Consequently I think the second most attractive alternative.
In my final paper (graduation in computer science) I approached the second alternative applying the automatic selection of hyperparameters in DNNClassfier ...
It is still crawling more I think it is possible to create an Estimator following this proposal ... I hope to spread my studies soon ...
I just need to mature better ... For now is can create an example of how to use the optimization of hyperparameters along with Tensorflow ... Reinforcing I think this is very interesting ... And I see that this is still a limitation of Tensorflow

Katib is trying to replicate Google vizier concepts in an opensource impl:
https://github.com/kubeflow/katib

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Closing, as this capability is added in Keras Tuner.


feat: Matrix.fromRows and Matrix.fromColumns multiplied by vectors

Zulip discussion:
https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/.E2.9C.94.20sumType_zeroFun_dotProduct

bors merge
Thanks for this!


Installing pymbar from conda forcing a downgrade of Python 3.7 → 3.6

Installing pymbar from omnia via conda is trying to downgrade python (and a bunch of other packages). I'm not sure this is the intended effect (I can't see anything in the repository pinning python=3.6 or python<3.7).
Briefly, I had an environment with pymbar installed, upgraded ambertools from 18 to 19 and python from 3.6.x to 3.7.3. I then lost the ability to import pymbar. I thought this was probably removed accidentally during whatever magic conda uses for conflict management, but trying to reinstall pymbar using the same command will downgrade ~20 packages, including python.
(paprika-dev) /m/d/d/p/pAPRika-dev ❯❯❯ conda install -c omnia pymbar                                             ✘ 2 openmm-2
Collecting package metadata: done
Solving environment: done

## Package Plan ##

  environment location: /home/davids4/data/anaconda3/envs/paprika-dev

  added / updated specs:
    - pymbar

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    coverage-4.3.4             |           py36_0         226 KB  omnia
    ------------------------------------------------------------
                                           Total:         226 KB

The following NEW packages will be INSTALLED:

  pymbar             omnia/linux-64::pymbar-3.0.1.beta0-np111py36_0

[snip]
The following packages will be DOWNGRADED:
[snip]
  python                                   3.7.3-h0371630_0 --> 3.6.8-h0371630_0

I wonder if @Lnaden would be able to come in quickly and update the installation manager?  I think there are error warnings that are due to bad configurations (as see  with https://github.com/choderalab/pymbar/pull/309) that need to be addressed.

You'll want to get pymbar from the conda-forge channel rather than the omnia channel.
We moved the pymbar deployment from omnia to c-f a while ago, but we left the older packages on omnia available for reproducibility. We also recommend that any time you specify the omnia channel, you also specify conda-forge as an additional, higher-priority channel to ensure the dependencies resolve correctly.
Changing the channel should get you up and going.

Hm, thanks. conda install -c conda-forge -c omnia pymbar does work as expected. In the file that I used to create the environment, there are both omnia and conda-forge packages. I guess the issue comes when upgrading single packages down the line: e.g., manually upgrading AmberTools from 18 to 19 to test in my development environment kicked out pymbar and my one-liner was trying to pull in things only from conda-forge.

Right. If you use another conda install or similar command with different -c ... settings, it resolves only for that command and makes changes to the environment to solve that specific call. Its why we say for all omnia packages to also include conda-forge as a higher priority channel to help reduce those oddities. If you are having issues with resolution, try doing everything in 1 line carefully considering the channel priority.

@slochower can we close this issue?

Yup


Upgrade Dagger to 2.8 and use static provides

According to Android documentation, static methods are 15-20% faster. This PR makes all @Provides methods static when applicable.
More info on Dagger's static provide methods: https://youtu.be/iwjXqRlEevg?t=5m7s

heya, sorry that we've punted on this for so long but if you could fix the spacing so that it matches the Kickstarter style (should be accessible via Preferences > Code Style) and merge latest would be great to get this in!

closing here so we can do the merge in #189


Charge limit not working.

Hello,
I've installed Battery twice. First with the .dmg file, it did not work so I uninstalled it using the button under 'About V.1.1.4.
The second time is by launching the app directly from the .zip file but it's still not working unfortunately.
Can you help?
I'm on a M1 MacBook Air.

Use the issue template please.


Task restrictions work incorrect with task group when deploy script has several hosts

Q
A

Issue Type
Bug

Deployer Version
5.1.3

Local Machine OS
Ubuntu 14.04

Remote Machine OS
Ubuntu 14.04

Description
Task restrictions work incorrect with task group when deploy script has several hosts
Steps to reproduce
Content of deploy.php
namespace Deployer;

require 'recipe/common.php';

// Configuration
set('default_stage', 'test');

host('APP')
    ->hostname('<IP_ADDRESS>')
    ->stage('test')
    ->roles('app')
;
host('DB')
    ->hostname('<IP_ADDRESS>')
    ->stage('test')
    ->roles('db')
;

task('only-db-subtask1', function() {
    run("echo 'SubTask1 should be executed only on db host'");
});

task('only-db-subtask2', function() {
    run("echo 'SubTask2 should be executed only on db host'");
});

task('group-only-db', [
    'only-db-subtask1',
    'only-db-subtask2',
    'deploy:writable'
])->onRoles('db');

task('only-app', function() {
    run("echo 'Should be executed only on app host'");
})->onRoles('app');

task('common', function() {
    run("echo 'Common task executed'");
});

task('deploy', [
    'group-only-db',
    'only-app',
    'common'
]);

Output log
➤ Executing task only-db-subtask1
[APP] > echo 'SubTask1 should be executed only on db host'
[APP] < SubTask1 should be executed only on db host
• done on [APP]
[DB] > echo 'SubTask1 should be executed only on db host'
[DB] < SubTask1 should be executed only on db host
• done on [DB]
✔ Ok [7s 59ms]
➤ Executing task only-db-subtask2
[APP] > echo 'SubTask2 should be executed only on db host'
[APP] < SubTask2 should be executed only on db host
• done on [APP]
[DB] > echo 'SubTask2 should be executed only on db host'
[DB] < SubTask2 should be executed only on db host
• done on [DB]
✔ Ok [1s 588ms]
➤ Executing task deploy:writable
• done on [APP]
• done on [DB]
✔ Ok [1ms]
➤ Executing task only-app
[APP] > echo 'Should be executed only on app host'
[APP] < Should be executed only on app host
• done on [APP]
✔ Ok [658ms]
➤ Executing task common
[APP] > echo 'Common task executed'
[APP] < Common task executed
• done on [APP]
[DB] > echo 'Common task executed'
[DB] < Common task executed
• done on [DB]
✔ Ok [1s 317ms]

Expected result: tasks: "only-db-subtask1", "only-db-subtask2" and "deploy:writable" must be executed only DB host.
Actual result: all tasks are executed on all hosts.
The issue in GroupTask if we have 2 or more hosts.
Workaround
Use manual run of task instead of  group
task('group-only-db', function() {
    invoke('only-db-subtask1');
    invoke('only-db-subtask2');
    invoke('deploy:writable');
})
->onRoles('db');

This issue is still present om Deployer 6.2.0.

Yes, as task flattened before execution and no rutes added. Need to refactor task engine to work on trees instead.

And now it's supported in master!!


Selection rectangle: Don't clear selection if ctrl is pressed

Describe the bug
When starting selection rectangle and holding CTRL, the current selected item gets deselected.
To Reproduce
Steps to reproduce the behavior:

Select an item
Hold CTRL
Trigger selection rectangle
See error

Expected behavior
Don't clear selection
Desktop (please complete the following information):

OS Version: [Windows 10 2009]
App version: [master]

@Thomas1664 This issue should be resolved with #2716.