Try Building the Visitor Frontend in the CodePipeline

Changes

Try building the visitor frontend in the codepipeline before deploying the cdk

not sure if this will work as intended, this change is to test on the actual pipeline, and can be reverted if the CI stage fails
eventually move the build artifact of this step into the cdk/visit/console folder for actual deployment

I squashed & merged the 3 commits from #79 and now GitHub doesn't know how to resolve the conflicts. Can you rebase or cherry-pick f023e45251e23b9533f27bab88fa24725c2bf3d2 onto mainline & then force push?
When you split the "Testing pipeline build of frontend" commit into its own PR from #79 you included the 3 commits from #79 here - I think it would have been better to put f023e45251e23b9533f27bab88fa24725c2bf3d2 onto its own branch & set the upstream as the branch #79 was on. This would have made this PR diff only show f023e45251e23b9533f27bab88fa24725c2bf3d2 and I suspect it would have made rebasing easier after I squashed the commits.

I reverted https://github.com/clemsonMakerspace/unified-makerspace/commit/4e9c21224a2a5df242c5830ff0e46241a62e820e with 7df212251feac6b412e41895b6159756b2061229 because during testing of this change after deployment to prod I noticed that it was posting all requests to https://www.google.com/ instead of https://api.cumaker.space/.

I've just tested https://visit.cuMaker.space/ after deployment of https://github.com/clemsonMakerspace/unified-makerspace/commit/7df212251feac6b412e41895b6159756b2061229 and the rollback work. https://github.com/clemsonMakerspace/unified-makerspace/commit/4e9c21224a2a5df242c5830ff0e46241a62e820e is confirmed bad.

I've just tested https://visit.cuMaker.space/ after deployment of 7df2122 and the rollback work. 4e9c212 is confirmed bad.

Oh dang, sorry I left that there. I was testing the change and deployed to my test env, and forgot to rebuild the app for the actual pr.

squashed & merged the 3 commits from #79 and now GitHub doesn't know how to resolve the conflicts. Can you rebase or cherry-pick f023e45 onto mainline & then force push back to this branch?
When you split the "Testing pipeline build of frontend" commit into its own PR from #79 you included the 3 commits from #79 here - I think it would have been better to put f023e45 onto its own branch & set the upstream as the branch #79 was on. This would have made this PR diff only show f023e45 and I suspect it would have made rebasing easier after I squashed the commits.

I just rebased the branch onto the mainline changes.
This pr is from last week however; I think you mentioned not wanting to merge a change like this into prod, so I planned on standing up my own pipeline to test this, and potentially solve the environment dependent build aspect of it aswell. This could remove the need to build the site in the mean time, it just wont have the correct api endpoints.

Ive done some more testing on my end, ill open a new PR with updated changes on a new branch.
*Ill link it on here when I open it.


On Linux use D-Bus GATT APIs

Lets please not alienate the Linux upstream, we do have a very complete set of APIs for BLE including GATT, which is build with a LGPL C library and D-Bus APIs so you don't need to rewrite everything from scratch. It is actually in use in Chrome OS as well so I wonder how much code can be shared.

@Vudentz both noble and bleno have been running on Linux prior to the BlueZ 5 release. This makes the out of the box experience much easier for distros that still ship with BlueZ 4.
I'd still like to continue to support the HCI socket binding, as from what I understand the D-Bus API is still experimental and not enable in bluetoothd by default. (Maybe this is no longer correct?)
Anyways, let's continue to discuss adding support for the D-Bus API in:

https://github.com/sandeepmistry/noble/issues/310
https://github.com/sandeepmistry/bleno/issues/24


chore: make cnpg plugin commands compatible with OLM

Improve the plugins to run the commands fio, publication, subscription and
psql smoothly on OLM environments.
Closes #5824

/test depth=push


HBASE-24057 Add modules to mapreduce job classpaths

Branch-2.1 did not move to thirdparty GSON in HBASE-20587 so Jackson dependencies need to stay.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 42s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1 :green_heart:
mvninstall
5m 29s
branch-2.1 passed

+1 :green_heart:
compile
0m 29s
branch-2.1 passed

+1 :green_heart:
checkstyle
0m 24s
branch-2.1 passed

+1 :green_heart:
shadedjars
4m 13s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 20s
branch-2.1 passed

+0 :ok:
spotbugs
0m 54s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 53s
branch-2.1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 52s
the patch passed

+1 :green_heart:
compile
0m 28s
the patch passed

+1 :green_heart:
javac
0m 28s
the patch passed

+1 :green_heart:
checkstyle
0m 23s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 18s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
20m 10s
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1 :green_heart:
javadoc
0m 18s
the patch passed

+1 :green_heart:
findbugs
0m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
19m 29s
hbase-mapreduce in the patch passed.

+1 :green_heart:
asflicense
0m 19s
The patch does not generate ASF License warnings.

70m 15s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1372/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1372

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 0ec59e1eb998 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1372/out/precommit/personality/provided.sh

git revision
branch-2.1 / 503d332527

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1372/1/testReport/

Max. process+thread count
4730 (vs. ulimit of 10000)

modules
C: hbase-mapreduce U: hbase-mapreduce

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1372/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Issue with nested fzf usage in bash script causing script to halt

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] macOS

Shell

[x] bash (in the script)
[x] zsh (default shell)

Problem / Steps to reproduce
I am encountering an issue when trying to use fzf within fzf in a bash script. The script stops
when I make a second selection from ⌃ Control + H, and continues only when ⌃ Control + C
is pressed.
The idea I am pursuing is using the --history flag read from my past queries and make a selection,
this selection will then replace my current query. For simplicity, the script has been reduced to
the following:
#!/usr/bin/env bash
set -o errexit -o nounset -o pipefail

export FZF_DEFAULT_OPTS=""
export FZF_DEFAULT_COMMAND=""
SHELL=$(which bash)

curl_custom() {
	command curl --request POST "localhost:$FZF_PORT" --silent --data "$@"
}

query() {
	for i in {1..100}; do
		curl_custom "change-header:$i"
	done
}

view_history_commands() {
	command fzf --no-multi <<<$'A\nB' | while read -r item; do
		curl_custom "change-query:$item"
	done
}

export -f curl_custom query view_history_commands

: | command fzf \
	--bind "change:reload:query {q}" \
	--bind 'ctrl-h:execute:view_history_commands' \
	--listen

Here is the GIF of the script in action:

First, I press ⌃ Control + H and select A.
While the query is still running, I press ⌃ Control + H again and select B.
The script is blocked and only continues when I press ⌃ Control + C.

Alternatives
The idea worked when modifying the script using the --expect flag.

Related issue(s):

#3291

Adopting a stop_loop check appears to be effective. Would you recommend that?
#!/usr/bin/env bash
set -o errexit -o nounset -o pipefail

export FZF_DEFAULT_OPTS=""
export FZF_DEFAULT_COMMAND=""
SHELL=$(which bash)

export stop_loop="/tmp/stop_loop"
trap 'rm -rf $stop_loop' EXIT

curl_custom() {
	command curl --request POST "localhost:$FZF_PORT" --silent --data "$@"
}

query() {
	for i in {1..100}; do
		[[ -s $stop_loop ]] && break
		curl_custom "change-header:$i"
	done
}

view_history_commands() {
	echo "stop" >"$stop_loop"
	item=$(command fzf --no-multi <<<$'A\nB')
	curl_custom "change-query:$item"
	: >"$stop_loop"
}

export -f curl_custom query view_history_commands

: | command fzf \
	--bind "change:reload:query {q}" \
	--bind 'ctrl-h:execute:view_history_commands' \
	--listen

The reason that the curl command in view_history_commands doesn't finish is that fzf uses a bounded buffer for server requests.

Thank you, increasing the buffer size does work.

Can you share what you were trying to implement?

The script is designed to search GitHub code and list the results. The header updates to reflect the
progress of file retrieval.
The hotkey ⌃ Control + H allows viewing of past queries and select one.
Refer to the GIF below for further clarity.

The code is present here. For the time being, I have implemented the stop_loop workaround.
interactive history by LangLangBart · Pull Request #2 · LangLangBart/gh-find-code · GitHub

I'm thinking of increasing the buffer size to 1K. Do you think this will be enough? We can't make it absurdly large because that would waste memory.

I'm also going to put a timeout on POST requests. So with the channel size 10,
$ fzf --listen --bind 'start:execute(for i in $(seq 1000); do curl -if localhost:$FZF_PORT -d up || break; done)+abort'
HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 503 Service Unavailable

curl: (22) The requested URL returned error: 503

Do you think this will be enough?

Indeed, tests with 100 as the parameter (serverInputChan in src/terminal.go) were successful on
the script in the issue description. Therefore, 1k should be more than adequate.

I'm also going to put a timeout on POST requests.

A timeout feature would indeed be a valuable addition.

Therefore, 1k should be more than adequate.

Alright, let's settle with 100 with 2-second timeout. 1K does seem a bit too much to be honest. We'll see if anyone hits the limit.


re-open Statix.Conn port on closure

~This PR adds Statix.Supervisor, a GenServer responsible for managing StatsD connections and reopening when a port closure is detected. To accomplish this, it introduces a new managed mode for connections, where port closures will raise.~
The previous approach isn't viable since it relies on transmit raising, which means that any process that calls MyApp.Statix.increment and similar functions that rely on transmit will raise if the port's closed, which isn't acceptable. This new approach simply provides the Statix.Conn with the name that it's registered under, so when it notices a port closure it can re-open a new port and register it under the same name.

This will only resolve Erlang's :gen_udp port driver failures, not actual network port closures (UDP is a connectionless protocol, so there's not really a concept of dropping/restarting a UDP "connection"). I'm going to close this, since it seems that our missing stat issues are caused by Datadog's StatsD server failing to receive/transmit packets.


Minor UI cleanup!

Tool is awesome. Good job.
Some of the menu items are not working properly. Like New in File menu, About, etc. This is just cosmetic but will make the product look great.

thanks, @muthuka!


fix: payload is not serialized to JSON

The payload is sent as "[object Object]" because the method body.toString() does not return the serialized body
There might also be other files where there also is this problem but I have not found any yet.

Thank! There is no testing env for browser now. I think jest have this functionality already. Maybe I'll enable it later.


ubuntu 18.04 - rocksdb & old python

so it doesn't work with rocksdb...you have to add --leveldb as a parameter
also you have to upgrade python to python3.7
install python3.7 and
sudo update-alternatives --config python3
....maybe you can include this somehow in the install script, if you have the time :)

It works fine in the Travis tests: https://travis-ci.org/github/bauerj/electrumx-installer/jobs/732800035
Please give more information. What doesn't work? How does it fail? What did you do?

so this is what i did:
got a brand new ubuntu 18.04
run your install script. it fails at rockdb something...
tried to run it with --leveldb... now it fails at pip not found. installed pip, fails at python3.7 (default on ubuntu 18.04 is python3.6)
install python3.7 and point python3 to go to python3.7
installed again with --leveldb, everything works ok now.

it fails at rockdb something...

Okay, I will need more information to figure out what causes this.

I just want to also say that it isn't working with stock ubuntu 18 due to an older version of python, but it works just fine with stock ubuntu 20.04


Add diurnal cycles

I think that for larger time periods this is definitely a capability that users will want.
If you agree, feel free to assign me to the task. I think that having this assigned, even if it's not ready before the tutorial, would be nice to be able to say that it is "under development", or that it's coming to MM.
Cheers
Pablo

Currently it is being addressed in xarray_plots


[sensors_plus] issues from Flutter repository

Todo

[ ] https://github.com/flutter/flutter/issues/65620
[ ] https://github.com/flutter/flutter/issues/56997
[ ] https://github.com/flutter/flutter/issues/49608
[ ] https://github.com/flutter/flutter/issues/47703
[ ] https://github.com/flutter/flutter/issues/43653
[ ] https://github.com/flutter/flutter/issues/26078
[ ] https://github.com/flutter/flutter/issues/25971
[ ] https://github.com/flutter/flutter/issues/19386

Link to all issues

I'm sorry if my message was intentionally deleted. I was wondering if these issues (specifically https://github.com/flutter/flutter/issues/25971) was on your immediate todo list? I have a use case that needs to define the sample rate and I'm willing to investigate it if its something that you will not be doing anytime soon. Please let me know. Thank you.

Hello
This is on our list and we may pick that anytime. If you'd like to help and investigate to address these issues, you are more than welcome.

any updates on the sampling rate

Here is a PR for Consider adding timestamps to sensor events flutter/flutter#26078


Add a note about author order

see  https://acl2020.rocket.chat/channel/helpdesk?msg=5KjAkvMbPaoZWZiYL

Close #485


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1364

Questions ?
Please refer to the Backport tool documentation


a question about the code of universal transformer

https://github.com/tensorflow/tensor2tensor/blob/2f8423a7daf39c549fa4f87d369d3ff95e719e6c/tensor2tensor/models/research/universal_transformer_util.py#L1207
Is this supposed to be "(previous_state * (1 - update_weights))" instead of "(previous_state * 1 - update_weights)"?
Thanks.

It makes sense to be  new_state = transformed_state * update_weights +previous_state given that update_weights is just p_t (in some sense) and previous_state is just the sum of previous p_t*s_t


merge wrappers into contained placeholder

Spawned from #3
If all that a wrapper contains is a placeholder (no text content), we should not create a wrapper and should instead merge its component(s) into the placeholder value, e.g. consider:

Hello {user}

Ideally that should yield the following (note the lack of wrapper):
"Hello %{user}"

The value for %{user} would be {user}

upon adding a failing test i realized it actually does this already, except that, the placeholder is poorly named (e.g. {user} => %{b_user}) ... so maybe we just need better inferred placeholders


Wanting some help with correctly reading keys.

I am using the latest version. Great tool btw! However my lack of javascript might be creating an issue.  I recently made an api that returns active directory users, and I am using your tool for predictive user text.
Here is a sample returned by the API
<EMAIL_ADDRESS>And here is my JS (mostly) successfully running:

User names populate/show just fine.  However I cannot get the "mail" items to automatically populate in the list even though they are in the JSON object.  I think I should be seeing the "samaccountname" and "mail" text on the right of the predicted text.
And a second question, we have ~500 users in our org.  Would it make more since to do a single query and just store that data instead of continuously querying?
Thanks!  Love your tool!

Hello @icsy7867,
I'm glad autoComplete.js came in handy for you!

Displaying custom resultItem

resultItem: {
    element: (item, data) => {
        // Modify Results Item Style
        item.style = "display: flex; justify-content: space-between;";
        // Modify Results Item Content
        item.innerHTML = `

        ${data.value.samaccountname}

        ${data.value.mail}
        `;
    },
    highlight: true,
},

Storing data instead of continuously fetching it

In your case, I would recommend you store the data instead of fetching it with every query, as you've mentioned.
You have two different approaches to doing so:

Rely on the data.cache config, which will cache the data until the next page reload.
Store the data.src data return to localStorage or sessionStorage and combine it with the data.cache to prevent fetching data with every query

I hope I've answered your questions; please let me know if you have any more questions or need any clarification.
Cheers! :)


Create GOVERNANCE.md

@tisonkun community can propose topics by just sending PRs to add items and have them removed by maintainers, like https://github.com/todogroup/ospology/pull/21

@anajsana added some info on voting rules, but kept it simple, thank you


Botany team only: policy on descriptions

I had a useful conversation with Arvid Aase from Fossil Butte that we should think about a policy for. Nothing to worry about until after Hack-a-Thon, but want to get this in before I forget it.
Let's say that you have a compound leaf, and the terminal leaflet looks very different from the lateral leaflets. For example, the terminal leaflet could be palmately veined and the lateral leaflets pinnate. And whichever it is will propagate differences throughout the description. There are two ways to handle this. First, we could instruct users to create separate descriptions for the two types of leaflets (e.g., "Platanites raynoldsii terminal leaflet" and "Platanites raynoldsii lateral leaflet"). Not sure how this would display for the OTU description, though. Would they just get lumped into a composite description, or is it possible to hold them separate? Alternatively, we could have users create a single description, based on multiple specimens, that chooses multiple character states. This is somewhat less informative, as particular character states may be tied together. For example, leaves that sometimes are lobed and sometimes are not deeply incised enough and so would be considered toothed, whereas the lobed specimen would be untoothed.

@doricon : we should add discussion of this to the best practices document that we've started.

@ecurrano Yes, this would be great for that best practices doc! Probably won't be a one-size-fits-all solution.
A thought off-hand:
There is no limit to the number of descriptions/schemas that can be associated with specimen(s) and thus OTUs. So, you don't actually have to lump character states under one description regardless of whether the leaves are one or more specimens. You can create a description node "terminal leaflet MLA" and fill that out, then make another description node for "lateral leaflet MLA"  and fill it out. Those descriptions can belong to one specimen (if both types of leaves are preserved on one specimen) or separate specimens that are all assigned to the same OTU. I think it will work great!


test_fft.py fails with 2023.1.1 on a GTX 1080 Ti

Here is the relevant output of test_fft.py
test_c2c (__main__.TestFFT.test_c2c)
Run C2C tests ... nvrtcCompileProgram error: NVRTC_ERROR_BUILTIN_OPERATION_FAILURE
nvrtc: error: failed to load builtins for compute_30.
extern __shared__ float shared[];
extern "C" __global__ void __launch_bounds__(6) VkFFT_main (float2* inputs, float2* outputs) {

For a GTX 1080 Ti, it should use compute_61 afaiu.
nvidia-smi says
Driver Version: 530.30.02    CUDA Version: 12.1

and nvcc --version gives
Cuda compilation tools, release 10.1, V10.1.243

Any help will be appreciated.

Hi Luc, sorry for not seeing this earlier - I'm not sure what the exact issue is, but given the discrepancy between the toolkit (nvcc 10.1.243) and driver (12.1), I would suggest to update the toolkit.
I'm testing using a GTX 1080 before release, so I know there should be no issues with that card (see the test in the current dev branch: http://ftp.esrf.fr/pub/scisoft/PyNX/pyvkfft-test/pyvkfft-test-2023-07-28-gtx1080ti_cu/pyvkfft-test.html), though I'm mostly testing with cuda toolkits >=11.7 now.

Hi Vincent. Thanks a bunch ! Installing cuda-nvcc-12-1 solved the problem indeed.
Just in case someone has the same problem, I shall add that it got installed in /usr/local/cuda-12.1, so the older nvcc in /usr/bin needs to be hidden by changing PATH, and LD_LIBRARY_PATH too for good measure.
Thanks again!

Great ! It should also be possible to rely on the cuda toolkit available trough conda (I think it's automatically installed by the pyvkfft conda-forge package).


Doesn't properly handle CRLF line endings

When reading files with CRLF line endings the file's aren't handled correctly. As an example the CSVImporter sample app unit tests demonstrate this problem. All of the Baseball files use Windows line endings. I just ran the unit tests. At the end of each test they print out the importedRecords. I see the below output for some of the tests. Notice the \r in the last team. The CRs shouldn't be in the results. I think that the underlying File class is set to use \n as the line separator.
Test Case '-[CSVImporter_iOS_Tests.CSVImporterSpec imports_data_from_CSV_file_with_headers]' started.
["yearID", "lgID", "teamID", "franchID", "divID", "Rank", "G", "Ghome", "W", "L", "DivWin", "WCWin", "LgWin", "WSWin", "R", "AB", "H", "2B", "3B", "HR", "BB", "SO", "SB", "CS", "HBP", "SF", "RA", "ER", "ERA", "CG", "SHO", "SV", "IPouts", "HA", "HRA", "BBA", "SOA", "E", "DP", "FP", "name", "park", "attendance", "BPF", "PPF", "teamIDBR", "teamIDlahman45", "teamIDretro\r"]
And another test has \r in several of the values.
Test Case '-[CSVImporter_iOS_Tests.CSVImporterSpec imports_data_from_CSV_file_with_headers]' started.
["yearID", "lgID", "teamID", "franchID", "divID", "Rank", "G", "Ghome", "W", "L", "DivWin", "WCWin", "LgWin", "WSWin", "R", "AB", "H", "2B", "3B", "HR", "BB", "SO", "SB", "CS", "HBP", "SF", "RA", "ER", "ERA", "CG", "SHO", "SV", "IPouts", "HA", "HRA", "BBA", "SOA", "E", "DP", "FP", "name", "park", "attendance", "BPF", "PPF", "teamIDBR", "teamIDlahman45", "teamIDretro\r"]
Progress: 1
Progress: 63
//...

I'm not sure what the proper approach is to fix this. Options would be to expose a line ending setting in CSVImporter that would be passed to the underlying TextFile class. Alternatively CSVImporter could open the input file itself and sniff the line ending.  I think it's best if this is done transparently to the client code.

Fixed by merging #7.


Remove requirements.txt file from delete list.

fixes #1829
Description
Removing the requirements.txt from the list of files to delete if heroku is not enabled.
Rationale
Using TravisCI but not enabling Heroku causes the requirements.txt file in the root dir to be deleted, thus needing an overridden .travis.yml install key.
Use case(s) / visualization(s)
As a user of this template, I want to create an app without Heroku support, but support for TravisCI, using the output of cookiecutter

@webyneter thanks for the suggestion. In my opinion, the requirements.txt file should exist in the root directory at all times, not just if we are using Heroku or TravisCI - it is a very common practice in python projects. Performing an attempted delete, but then not deleting it because we are using TracisCI seems a little backward in my opinion.
LMK what you think.

@cmackenzie1 the thing is, we've already got ./requirements/ with a number of requirements files in it: some of them serve as base templates -- like base.txt -- while the others -- test.txt, local.txt, and production.txt -- are used directly. As a result, there's no need to have yet another requirements file serving merely as a proxy; it's only required in Heroku bare-bones deployment setup anyway... My point is, if not for Heroku we wouldn't have ./requirements.txt in the first place.

@webyneter ahh ok. I made the change, lmk what you think.

Thanks! I'll check it out later this week.


Add new project  'amplify-flutter'

https://github.com/Samaritan1011001/amplify-flutter

@ashitaprasad Can you please assign me this issue


[TODO] Create interface to define tracking point

Create interface to define tracking point

Fixed by #6


Domino Sample REST Service Feature (9.0.1.v00_11_20141217-1000) requires feature "com.ibm.domino.das.feature".

Hi!
I am trying to use the latest (ExtensionLibraryOpenNTF-901v00_11.20141217-1000.zip) version of the library from http://extlib.openntf.org. (http://extlib.openntf.org/Projects\pmt.nsf/downloadcounter?openagent&project=XPages Extension Library&release=901v00_11.20141217-1000&unid=849AB5A1CBA825C986257DB30056EA70&attachment=ExtensionLibraryOpenNTF-901v00_11.20141217-1000.zip)
But when I started installing Domino Sample REST Service Feature (9.0.1.v00_11_20141217-1000) in Domino Designer I got the following error:
Requested operation cannot be performed because it would invalidate the current configuration. See details for more information.
Domino Sample REST Service Feature (9.0.1.v00_11_20141217-1000) requires feature "com.ibm.domino.das.feature".
But com.ibm.domino.das.feature is not included in ExtensionLibraryOpenNTF-901v00_11.20141217-1000.zip at all. Is there a way to get it fixed?
BR Konstantin.

Issue fixed in Extlib release v15


commented line maybe causing issue after a refresh

Is this line commented on purpose?
It may be causing timeline to complain about not having a buffer for ob_end_flush() on the same file, to delete or flush.
un-commentating it stopped the Notice from popping up on my instance, but I'm not sure if that could have other side-effects.

I'm seeing the same behaviour in the sandbox instance:
https://twtxt-sandbox.eapl.me/timeline/

I'll take a look into it

Can it be a problem on your servers? I don't see it anymore, but I remeber having it when I made the refresh page.


MGDCTRS-1419: feat: disable the action items if connector enters to deleted desired state

Closes https://issues.redhat.com/browse/MGDCTRS-1419 https://issues.redhat.com/browse/MGDCTRS-1447

added the test cases and fixed connector type card stories.


couldnt logging

why i cant logging with igdm....wherever i filled my id and password it warning to me this text : no configs given!!!!!
please help me....igdm is only way that i can to connect instagram

Hello I've been using igdm for some time but today on 27/4/2019 there is a problem come to me message no configs given


Remove aliases

Otherwise the following error is generated when building my config
       … while evaluating definitions from `/nix/store/ds9973rzhbwq1mk4lznqwrm9x44qp9qy-source/flake.nix#nixosModules.nixvim':

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: attribute 'system' missing
       at /nix/store/ds9973rzhbwq1mk4lznqwrm9x44qp9qy-source/wrappers/nixos.nix:58:56:
           57|         cfg.printInitPackage
           58|       ] ++ (lib.optional cfg.enableMan self.packages.${pkgs.system}.man-docs);
             |                                                        ^
           59|     }
       Did you mean one of mystem, systemc, systemd, syntex or systemfd?

Could you change the commit message to something like "wrappers: use system from stdenv.hostPlatform", though please? Ideally with a similar explanation to your PR description in the commit body 🙂

@mergifyio queue

I didn't even see that those where all in the wrappers. After seeing the first occurrence I just fixed them trerwide.


Shapeless 2 on Dotty

This is a general meta-issue to aggregate the overall project of getting a version of Shapeless 2 working on Dotty.
Goals

Rough source-compatibility with the Shapeless 2.x versions of any constructs which can be meaningfully expressed on Dotty
Full source-compatibility with the Scala 2.13 variants of the same construct in the same release. In other words, it should be possible to move from 2.13 to 3.0 simply by swapping scalaVersion for any code which exclusively uses the supported constructs

Non-Goals

Perfect binary compatibility with the 2.x line (though, the closer to this we can get, the better)
Ports of less-used constructs, particularly those which are impossible to render on Dotty

Requirements
Each of these should be split out into a separate issue:

[ ] Generic
[ ] HList
[ ] Coproduct
[ ] Polymorphic functions

Comments and opinions very much desired on all of the above!
To be clear, I'm well aware that most of this is covered by out-of-the-box functionality in Dotty (and shapeless 3 is a nice layer on top of that). However, any project which is cross-publishing between Scala 2 and Scala 3 will benefit considerably from this type of functionality. Additionally, cross-publication is a special case of migration, and any project which is using shapeless already will either need something like this, or it will need to recreate this type of functionality on their own for bespoke cross-building (i.e. what Circe had to do).

I think the difficult isn't in the data types, but in the operations. Shapeless uses the aux pattern and inductive derivation to compute types and values together. This approach kind of works in Scala-3, but in my experience the compiler will not tell you what the inferred type is in case of error (you get a type like ?0.Out) so this would need to be fixed in the compiler or we would need to figure out a different way to prod the compiler into doing what we want. The Scala-3 approach seems to be to compute a match type (if you can convince it to reduce, which does not seem easy) and then do an unsafe value-level computation and cast, which is gross but might work.
Miles did a lot of this work already in the Shapeless-3 branch so I would definitely start there. I get the sense that it was not easy.

As far as I understood, it would not be possible to implement Lazy with Scala 3 macros. Maybe we need to assess this statement before going further?
If this is the case, Miles suggested dropping Lazy from Shapeless in favor of using by-name implicit parameters, which are supported in Scala 2.13 and 3.0.0. So, we would release Shapeless 2.4, where Lazy would be deprecated (in favor of by-name implicit parameters). This version would still be binary compatible with 2.x. Then, it would be possible to publish it for Scala 3.0.0 (Lazy would still be part of the API, but there would be no macros that summon it).

Why couldn’t we also implement Lazy in Scala 3.0.0 by using by-name implicits?

It's totally possible. We even have a plugin to enable using by-name implicit syntax on Scala 2.12 which is replaced by Lazy. And on the main branch we already use by-name implicits. See also #1171

This version would still be binary compatible with 2.x

I don't know about that. The biggest problem for binary compatibility is that Shapeless 2.3 is using a weird encoding of Symbol singleton types as labels. I don't know if that can be implemented in Scala 3, but I'm sceptical. And if we can't do that binary compatibility will be broken either way.

The biggest problem for binary compatibility is that Shapeless 2.3 is using a weird encoding of Symbol singleton types as labels. I don't know if that can be implemented in Scala 3, but I'm skeptical. And if we can't do that binary compatibility will be broken either way.

That’s good to know.
I’m summoning @nicolasstucki to ask whether it is possible or not to express type refinements of the type Symbol in Scala 3, and get something like constValue work with it? Essentially, I would like the following code snippet to compile:
inline def getLabel[L <: Symbol]: String = compiletime.constValue[L].name
inline val bar = Symbol("bar")
println(getLabel[bar.type])

https://scastie.scala-lang.org/xKebkhNYSeWFoxfPmMpylg

I like us to get off using Symbol for labels irrespective of the Scala version ... it was always a mistake.
That's already done in shapeless 3, but that's Scala 3 only so far. I think we should do the same for shapeless 2.4 ... it'll be a breaking change, but I think we have to live with that.

I guess it’s OK to switch to String instead of Symbol. Users of shapeless will have to adapt to this change, but hopefully this can be achieved in a binary compatible way.
Typically, I have code like this:
    implicit def consRecord[L <: Symbol, H, T <: HList](implicit
        labelHead: Witness.Aux[L],
        jsonSchemaHead: JsonSchema[H],
        jsonSchemaTail: DerivedGenericRecord[T]
    ): DerivedGenericRecord[FieldType[L, H] :: T] = ...

I will have to change for the following:
    implicit def consRecord[L <: String, H, T <: HList](implicit
        labelHead: Witness.Aux[L],
        jsonSchemaHead: JsonSchema[H],
        jsonSchemaTail: DerivedGenericRecord[T]
    ): DerivedGenericRecord[FieldType[L, H] :: T] = ...

But the erased signature will be the same, so this change will be binary compatible.

But the erased signature will be the same, so this change will be binary compatible.

I'm not sure about that because L would erase to its upper bounds which would change from Symbol to String so in general I don't think we can assume binary compatibility will be preserved.

Oh right, it erases to its bound, so I will have to introduce a separate method.

Ok, so progress is happening on this finally. So far I've gotten a version of Shapeless 2 compiling on both Scala 2 and 3, but where all macros are dummied out. No idea how well it works after it compiles.
One big discussion which needs to be had is what to do with everything that can't be cleanly ported to Scala 3? This is mostly macros that do things Scala 3 macros can't or types not representable in Scala 3. As I can see, there are a bunch of similar macros, which can be grouped and talked about together.

Accesses the outer scope of the macro call (cachedImplicit is one example that does this from a quick glance at it. Also not sure how feasible it would be to implement in Scala 3 with my limited knowledge of what you can do there.)

Type providers of all sorts. Think Union, Witness, Record, HList, Coproduct. Problem here is mainly constructing a type from a string, which is not something I think Scala 3 exposes.

Things that use untyped trees. Think RecordArgs, FromRecordArgs, NatProductArgs, ProductArgs, FromProductArgs, SingletonProductArgs. These macros generally convert calls to a method into calls to a different method, while manipulating the arguments. For example for RecordArgs, lhs.method(x = 23, y = "foo", z = true) becomes lhs.methodRecord("x" ->> 23 :: "y" ->> "foo", "z" ->> true). I don't think Scala 3 macros offers a way to redirect method calls in such a dynamic manner.

Stuff that in some way manipulates source code in ways not exposed by the Scala 3 compiler. Think TypeOf, compileTime. This class of macros in some way serve as a poor mans inline, but manipulates the code as a string. As such I can't see any reasonable way to support it.

There are also the type quantifiers Shapeless exposes, which can be seen here.
https://github.com/milessabin/shapeless/blob/main/core/src/main/scala/shapeless/package.scala#L60
∃ I am fairly certain is not representable in Scala 3. ∀ might still be possible? If it is, it needs a new representation.
It's clear that none of these can be included in the Scala 3 artifact, but should they still be included in the Scala 2 artifact?
My current progress on porting Shapeless 2 to Scala 3 can be found here for anyone interested.
https://github.com/Katrix/shapeless/tree/feature/scala-3-port

@Katrix I think we should drop features that we can't port to Scala 3. My reasoning is that Shapeless 2.4 will almost certainly be the last binary breaking release of Shapeless 2, which means that we can't deprecate those features in 2.4 and drop them later. In any case it would be good to deprecate in 2.3 anything we are going to drop in 2.4. I don't think most of these features are particularly important:

Those features should be replaced by regular implicit resolution:

Lazy is replaced with by-name implicits since Scala 2.13
Strict is not necessary since Scala 2.13 (due to the implicit divergence checker)
Cached is not really necessary given performance improvements in implicit search
LowPriority is a failed experiment and can be replaced by standard implicits prioritization
cachedImplicit is perhaps a bit problematic - worth a try to implement in Scala 3 but if not possible oh well

I think the biggest reason for type providers to exist was the lack of singleton types until Scala 2.13. So I think they won't be missed.
Yeah those are a bit too magic and go into the direction of changing the language, so I'm fine with dropping them. But just out of curiosity, why do you think they can't be implemented in Scala 3? Is it because we don't have access to the parameter names?
Whatever

∃ I am fairly certain is not representable in Scala 3. ∀ might still be possible? If it is, it needs a new representation.

What's the problem with those? Existential types?

@Katrix I agree with @joroKr21 on all points.

∃ I am fairly certain is not representable in Scala 3. ∀ might still be possible? If it is, it needs a new representation.

Does anyone use these? They were date from when shapeless was really just an experiment and they really don't have any practical use. I'm not planning to add anything similar to shapeless 3 and I'd be in favour of dropping them even if they could be ported to Scala 3.

For those that want to follow along, and provide input and help along the way.
Progress to far:

Implemented nat.ToInt and Nat implicit conversion
Changed the encoding of FieldType slightly to work better with Scala 3
Added basic implementation on Generic  using Mirror
Implemented the

Removals:

Lazy and Strict removed. Handled by Scala's implicit divergence checker and by-name implicits.
Removed type providers in: Coproduct, HList, Record, Witness, the, TypeOf, Union
Removed forwarder traits NatProductArgs, ProductArgs, FromProductArgs, SingletonProductArgs, RecordArgs, FromRecordArgs
Removed SelectManyAux and HListOps#selectMany as they used NatProductArgs

Questions:

Record and Union used their type providers to create types of them easily. Should we add a type level ->> to replace this need?
Instead of
Record.`"x" -> Int, "y" -> String, "z" -> Boolean`.T
Union.`"x" -> Int, "y" -> String, "z" -> Boolean`.T

we could provide
"x" ->> Int :: "y" ->> String :: "z" ->> Boolean :: HNil
"x" ->> Int :+: "y" ->> String :+: "z" ->> Boolean :+: CNil

What is NatWith? In particular, this type class has macro implicit conversions. What are their purpose?

What is WitnessWith? In particular, this type class has macro implicit conversions located in Widen. What are their purpose?

Is Widen still needed?

The macros for poly use openImplicits for it's macros to prevent diverging implicits. This is something not available in Scala 3 AFAIK. Is this still needed, and if so, how can be be replaced?

Record and Union use Dynamic to construct instances of them. However, they are very restrictive in the arguments allowed here. Currently macros validate this, but some of these restrictions can be lifted to the method instead. This would however lead to worse error messages as they would just be more generic "wrong type" or "wrong amount of arguments" errors.
As an example for Record, currently this is what we have
def applyDynamic(method: String)(rec: Any*): HList = ???
def applyDynamicNamed(method: String)(rec: Any*): HList = ???

but it could be this instead.
def applyDynamic(method: "apply")(): HNil = HNil
def applyDynamicNamed(method: "apply")(rec: (String, Any)*): HList = ???

Is this something worth doing, at the cost of slightly worse error messages? For the empty case (applyDynamic) we can just straight up get rid of a macro even in Scala 2 by doing this.

As RecordArgs is gone, CopyMethods in alacarte is no longer a thing. Is there anything we can do about this, or should we just remove CopyFacet as well?

How do we want to handle Typeable? Shapeless 3's typeable already exists as a seperate dependency and works just fine for Scala 3. Would it be reasonable to just depend on that on Scala 3, and proxy Shapeless 2's Typeable to Shapeless 3's Typeable?

Here are my 2 cents about some of your questions:

Record and Union used their type providers to create types of them easily. Should we add a type level ->> to replace this need?

It seems that currently there is no convenient syntax for expressing record types, so I would say yes to this proposal.

Record and Union use Dynamic to construct instances of them. However, they are very restrictive in the arguments allowed here. Currently macros validate this, but some of these restrictions can be lifted to the method instead. This would however lead to worse error messages as they would just be more generic "wrong type" or "wrong amount of arguments" errors.

Since the purpose of Shapeless 2 on Scala 3 is mainly to ease cross-compiling, I don’t think it is a big issue to have worse error messages in Scala 3 because I expect people to cross-compile with Scala 2 and get the better error messages there. However, if it is possible to do the same validation in a macro in Scala 3 as well, I would go for that.

How do we want to handle Typeable? Shapeless 3's typeable already exists as a seperate dependency and works just fine for Scala 3. Would it be reasonable to just depend on that on Scala 3, and proxy Shapeless 2's Typeable to Shapeless 3's Typeable?

I would copy Shapeless 3’s implementation in Shapeless 2 instead.

Should we add a type level ->> to replace [Record and Union]

Yes, I think that's a good idea.

What is NatWith?
What is WitnessWith?

Both of these were intended to improve the ergonomics of using singleton types in the pre-SIP23 world ... they should go.

Is Widen still needed?

I don't know. I suggest taking it out and seeing what breaks.

The macros for poly use openImplicits for it's macros to prevent diverging implicits.

All the poly macros should just go with no replacement.

Record and Union use Dynamic to construct instances of them.

Now that we can assuming literal types we should be able come up with some macro-free syntax to replace this, ideally aligned with the ->> type level operator we talked about above.

As RecordArgs is gone, CopyMethods in alacarte is no longer a thing.

I doubt that many people are using alacarte, so I'd drop it altogether, or demote to being an example with CopyFacet removed.

How do we want to handle Typeable?

Copy shapeless 3's.

Just chiming in here to say I think a shapeless 2 for scala 3 would be very valuable.
I understand we might not get 100% source code compatibility, but getting that number as high as possible will really be a help to projects that crossbuild for scala 2, which I expect we will be dealing with for at least several more years.

#1200 does significant progress on this front but the GSoC wasn't enough to complete it.
It needs a new champion unless @Katrix plans to return to that work.

For my masters thesis I need to do comparisons against Shapeless, so I might get back to it then, but I don't know how much I'll get to complete then, so would be good to look for someone else.
I will say that the majority of the remaining work from what I can see is to minimize Scala 3 bugs and irregularities, where it behaves differently from Scala 2. The library has theoretically been ported, only the tests remain, but those tests might show that something is quite broken currently.

https://stackoverflow.com/questions/69483366/scala-3-collection-partitioning-with-subtypes
https://stackoverflow.com/questions/74355212/shapeless3-and-annotations

https://github.com/fthomas/refined/pull/1246


Speed up tests

The tests would take ~45 mins before,
now it takes ~15 mins.
Integration tests in lib module takes a lot of time. We may ignore to some of them to speed up even more.
Closes #88

/land


Add http header configuration option

Unless I've missed it in the documentation, it would be great if the development server could send configurable http-headers.
What I would need this option for specifically is adding a CSP (content security policy) to the pages delivered by the development server.

This, 100%

(y)


EVM-338 fix race condition on account initialization

Description
When a new account sent multiple transactions at the same time, a possible race condition was occurring as follows (using 2 threads example):

thread-1 stores an empty account inside accountsMap
thread-2 checks whether account with address exists, and sees that it does, so it continues without creating an account itself
thread-2 continues it's execution thinking account is valid, and calls a function on one of its fields, which causes a nil dereference exception since thread-1 did not set the account's fields yet

This fix carries the field initialization into the store phase. Since LoadOrStore function is already thread-safe, there won't be a state where an invalid account exists inside the accountMap. And even if multiple threads try to create an account, it is OK since LoadOrStore only allows storing once, and account.init.Do is executed only once and is thread safe as well.
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[x] I have assigned this PR to myself
[ ] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[x] I have tested this code with the official test suite
[x] I have tested this code manually

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Ensure gutter icons show up in the correct locations

Fixes https://github.com/dafny-lang/ide-vscode/issues/237
There's seems to be a bug caused by commands.executeCommand('vscode.executeDocumentSymbolProvider', uri) here not returning the expected results, possibly because it's returning results for a different document version that the one we're expected. This PR no longer uses results from commands.executeCommand('vscode.executeDocumentSymbolProvider', uri) to compute the linesToSkip for gutter icons, this both avoid the bug from #237 and makes the gutter icons show up faster since there's no extra LSP server roundtrip involved.

Fixes #237

Thanks for trying ! However, I just tested this PR, I have the same problem (I pressed three times ENTER, this is what I got the first time)

Thanks for trying ! However, I just tested this PR, I have the same problem (I pressed three times ENTER, this is what I got the first time)

I wasn't able to reproduce that, but I also made some more changes to improve the behavior of the play icon.

I wasn't able to reproduce that, but I also made some more changes to improve the behavior of the play icon.

Just tried your new version, this bug seems indeed harder to obtain, but by writing two methods, and long-pressing and short-pressing enter, I get similar overlaps

I wasn't able to reproduce that, but I also made some more changes to improve the behavior of the play icon.

Just tried your new version, this bug seems indeed harder to obtain, but by writing two methods, and long-pressing and short-pressing enter, I get similar overlaps

What is worse than that, is that an incorrect state in the language server seems to persist when I create a new unrelated document, I get this:


Create Dockerfile

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @realwaynesun, @zbatscha, @havocesp, @jaegerstar, @andrewcz, @LucCADORET, @ugurak, @cat157, @LastAncientOne, @cicaglisa80, @GermanCacha, @mjrose, @giftedlattice, @LeonardioLeon67, @viet91, @arbilse, @austinob7, @braveoverwolf, @Duanmiss, @verystrongjoe, @cheunhong, @MojoCreator, @seangeleno, @opiater, @dcimring, @astrohong, @f13end, @nhphung216, @Spectre988, @dooee, @adeuriarteg, @Poriazy, @martines328, @Olcaey, @MwansaMwango, @johnmathews, @Ledjob, @lui1214, @Dustyik, @sarmel, @MattySpace, @Marcus-Arcadius, @Der-Henning, @nrbcode, @yulong-lu, @mertuska, @facuolivamar, @zhangarejiu, @secp8x32, @FilNN


WIP: Configuration from not hardcoded env variables

Problem: only hardcoded env variables can be used to configure neo4j container. It's only subset of all possible settings
Solution: introduce specific env variable naming convention, which will be used for dynamic configuration
Some things to keep in mind:

Some settings are commented by default and some are not
Not all settings are actually present (commented or not) in the config file. So a sed by itself is not guaranteed to replace something
A user might define a custom config volume AND some environment variables.
Backward compatibility with old hardcoded env variables
Update documentation/examples

WIP: it's only for 3.2 version at the moment; it needs review from somebody with proper neo4j config knowledge (cc: @spacecowboy); I was not able to build docker image on my localhost
This one can be a solution for: #52, #71.

To build and run the tests do this:
echo "NEO4J_VERSION=3.2.0-alpha07" > devenv.local && source devenv && make test-community

If you start a new terminal, remember to source devenv again.
You will see in the console output what the image id is, e.g.
Successfully built 9c2fa1709590

So you can do some manual tests as well. This is needed since the tests don't really tell you why they fail (bash syntax errors for instance)

@jangaraj I made some changes and the tests all ran successfully with them.

Changed the ENV directive to use equal signs to support several variables
Changed declaration of default values to a shorter form
Loop over all variables using set instead of printenv or locally defined NEO4J_ vars are not included
Do not set anything if $value is null.

Here's the diff:
diff --git i/src/3.2/Dockerfile w/src/3.2/Dockerfile
index f158142..619ee8b 100644
--- i/src/3.2/Dockerfile
+++ w/src/3.2/Dockerfile
@@ -4,8 +4,8 @@ RUN apk add --no-cache --quiet \
     bash \
     curl

-ENV NEO4J_SHA256 %%NEO4J_SHA%% \
-    NEO4J_TARBALL %%NEO4J_TARBALL%%
+ENV NEO4J_SHA256=%%NEO4J_SHA%% \
+    NEO4J_TARBALL=%%NEO4J_TARBALL%%
 ARG NEO4J_URI=%%NEO4J_DIST_SITE%%/%%NEO4J_TARBALL%%

 COPY ./local-package/* /tmp/
diff --git i/src/3.2/docker-entrypoint.sh w/src/3.2/docker-entrypoint.sh
index 3f879f3..615a47c 100755
--- i/src/3.2/docker-entrypoint.sh
+++ w/src/3.2/docker-entrypoint.sh
@@ -44,21 +44,21 @@ if [ "$1" == "neo4j" ]; then
         NEO4J_causalClustering_raftAdvertisedAddress

     # Custom settings for dockerized neo4j
-    NEO4J_dbms_tx__log_rotation_retention_policy=${NEO4J_dbms_tx__log_rotation_retention_policy:-100M size}
-    NEO4J_dbms_memory_pagecache_size=${NEO4J_dbms_memory_pagecache_size:-512M}
-    NEO4J_wrapper_java_additional=${NEO4J_wrapper_java_additional:--Dneo4j.ext.udc.source=docker}
-    NEO4J_dbms_memory_heap_initial__size=${NEO4J_dbms_memory_heap_initial__size:-512M}
-    NEO4J_dbms_memory_heap_max__size=${NEO4J_dbms_memory_heap_max__size:-512M}
-    NEO4J_dbms_connectors_default__listen__address=${NEO4J_dbms_connectors_default__listen__address:-<IP_ADDRESS>}
-    NEO4J_dbms_connector_http_listen__address=${NEO4J_dbms_connector_http_listen__address:-<IP_ADDRESS>:7474}
-    NEO4J_dbms_connector_https_listen__address=${NEO4J_dbms_connector_https_listen__address:-<IP_ADDRESS>:7473}
-    NEO4J_dbms_connector_bolt_listen__address=${NEO4J_dbms_connector_bolt_listen__address:-<IP_ADDRESS>:7687}
-    NEO4J_causal__clustering_discovery__listen__address=${NEO4J_causal__clustering_discovery__listen__address:-<IP_ADDRESS>:5000}
-    NEO4J_causal__clustering_discovery__advertised__address=${NEO4J_causal__clustering_discovery__advertised__address:-$(hostname):5000}
-    NEO4J_causal__clustering_transaction__listen__address=${NEO4J_causal__clustering_transaction__listen__address:-<IP_ADDRESS>:6000}
-    NEO4J_causal__clustering_transaction__advertised__address=${NEO4J_causal__clustering_transaction__advertised__address:-$(hostname):6000}
-    NEO4J_causal__clustering_raft__listen__address=${NEO4J_causal__clustering_raft__listen__address:-<IP_ADDRESS>:7000}
-    NEO4J_causal__clustering_raft__advertised__address=${NEO4J_causal__clustering_raft__advertised__address:-$(hostname):7000}
+    : ${NEO4J_dbms_tx__log_rotation_retention_policy:=100M size}
+    : ${NEO4J_dbms_memory_pagecache_size:=512M}
+    : ${NEO4J_wrapper_java_additional:=-Dneo4j.ext.udc.source=docker}
+    : ${NEO4J_dbms_memory_heap_initial__size:=512M}
+    : ${NEO4J_dbms_memory_heap_max__size:=512M}
+    : ${NEO4J_dbms_connectors_default__listen__address:=<IP_ADDRESS>}
+    : ${NEO4J_dbms_connector_http_listen__address:=<IP_ADDRESS>:7474}
+    : ${NEO4J_dbms_connector_https_listen__address:=<IP_ADDRESS>:7473}
+    : ${NEO4J_dbms_connector_bolt_listen__address:=<IP_ADDRESS>:7687}
+    : ${NEO4J_causal__clustering_discovery__listen__address:=<IP_ADDRESS>:5000}
+    : ${NEO4J_causal__clustering_discovery__advertised__address:=$(hostname):5000}
+    : ${NEO4J_causal__clustering_transaction__listen__address:=<IP_ADDRESS>:6000}
+    : ${NEO4J_causal__clustering_transaction__advertised__address:=$(hostname):6000}
+    : ${NEO4J_causal__clustering_raft__listen__address:=<IP_ADDRESS>:7000}
+    : ${NEO4J_causal__clustering_raft__advertised__address:=$(hostname):7000}

     if [ -d /conf ]; then
         find /conf -type f -exec cp {} conf \;
@@ -97,13 +97,15 @@ if [ "$1" == "neo4j" ]; then

     # list env variables with prefix NEO4J_ and create settings from them
     unset NEO4J_AUTH NEO4J_SHA256 NEO4J_TARBALL
-    for i in $( printenv | grep ^NEO4J_ | awk -F'=' '{print $1}' | sort -rn ); do
-        setting=$(echo ${i} | sed 's|^NEO4J_||' | sed 's|_|.|g' | sed 's|\.\.|_|g')
-        value=$(echo ${!i})
-        if grep -q -F "${setting}=" conf/neo4j.conf; then
+    for i in $( set | grep ^NEO4J_ | awk -F'=' '{print $1}' | sort -rn ); do
+      setting=$(echo ${i} | sed 's|^NEO4J_||' | sed 's|_|.|g' | sed 's|\.\.|_|g')
+      value=$(echo ${!i})
+      if [[ -n ${value} ]]; then
+          if grep -q -F "${setting}=" conf/neo4j.conf; then
             sed --in-place "s|.*${setting}=.*|${setting}=${value}|" conf/neo4j.conf
-        else
+          else
             echo "${setting}=${value}" >> conf/neo4j.conf
+          fi
         fi
     done

@spacecowboy nice bash skills 👍

printenv vs set - I'm not sure about set, I have had some problems with special characters in password environment variables in my projects - it needs some testing with NEO4J_AUTH
I've removed also curl - IMHO it's required only for docker image build process
there are some settings dbms.directories.* (for example lib), which are not included in the entrypoint script  volumes part - do we want to implement them as well?

@jangaraj

there are some settings dbms.directories.* (for example lib), which are not included in the entrypoint script volumes part - do we want to implement them as well?

Definitely not the lib dir. It should only point the proper installation folder. It only make sense to override it if you install neo4j according to some odd directory structure. And the user shouldn't concern themselves where those things live inside the container.

I've removed also curl - IMHO it's required only for docker image build process

That's probably perfectly fine

I'm not sure about set, I have had some problems with special characters in password environment variables in my projects - it needs some testing with NEO4J_AUTH

Wasn't aware of any difference. Good catch. Might be worth adding a test for this. I'll do it as soon as you push your latest changes.

@spacecowboy
Yes, volume support for dbms.directories.lib setting doesn't looks like a good idea. I've added /metrics volume support.
I'm not sure about meaning of this line in the Dockerfile:
COPY ./local-package/* /tmp/

Do we really need it?
I'm still not able to build docker image locally:
[root@dockerhost docker-neo4j]# echo "NEO4J_VERSION=3.2.0-alpha07" > devenv.local && source devenv &&  make test-community
bash: - : invalid option
bash: - : invalid option
bash: - : invalid option
make: *** No rule to make target `tmp/.image-id-community', needed by `tmp/.tests-pass-community'.  Stop.

Could you publish test docker image with this change please?

Please keep this for now:
COPY ./local-package/* /tmp/

I think it's used somewhere in the build pipeline.

Done. BTW: spacecowboy/neo4j:pr83 is bigger than neo4j:latest (249MB vs 172MB). That step COPY ./local-package/* /tmp/ has copied 73.5M /tmp/neo4j-community-3.2.0-alpha07-unix.tar.gz into image.
If you need additional modification, please create fork of my fork https://github.com/jangaraj/docker-neo4j/tree/env-variables (unfortunately I'm more less offline this week, so it'll be faster solution).

@jangaraj the size thing is something we can look at in a separate PR. This looks good here.
Pushed an updated build to spacecowboy/neo4j:pr83 and all the tests pass. Will merge this soon (we are in the middle of a release, waiting til after to avoid issues)


Molecule of the Week Name doesn't show up on iPhone and non-default font size

The "Caffeine" label doesn't show up on my iPhone for some reason, so I can't tap it for more information.

It's an issue with the webgl container not properly clearing. I'm working on a solution. It also happens when the font size is greater then the default

I put in a workaround that works in most cases. If you make the font really big it will still be hidden on some devices so I am leaving the issue open.

Fixed with the 3DMol background transparency fix commit 7f22cf7


cob_environments: 0.6.11-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_environments to 0.6.11-1:

upstream repository: https://github.com/ipa320/cob_environments.git
release repository: https://github.com/ipa320/cob_environments-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.9.3
previous version for package: 0.6.10-1

cob_default_env_config
* Merge pull request #140 <https://github.com/ipa320/cob_environments/issues/140> from fmessmer/add_launch_checks
  add launch check for mandatory nav config files
* no longer support automotive-assembly-line
* add mandatory files to empty
* add launch check for mandatory nav config files
* Merge pull request #138 <https://github.com/ipa320/cob_environments/issues/138> from fmessmer/ci_updates
  [travis] ci updates
* catkin_lint fixes
* Contributors: Felix Messmer, fmessmer

cob_environments

No changes

Holding for sync


Delay before scroll

This is a feature request that would be nice. What I would like to see is a possibility to have a small delay before the plugin starts scrolling and snaps the panel in place. This way, the automatic scrolling would be less disruptive to the user.
This webpage has the functionality I'm describing. Scroll the page, wait like 2 seconds, and then watch the page scroll in place.
http://risenchurch.com/

Thanks for your suggestion, I'll implement this sometime soon. Probably somewhere in the coming days.

I would like this feature too.  Has it been implimented?

Fixed in #76


Fix constant optional property

During the recent work in the SDK generator, I have come across a scenario, where there is a constant property which is also an optional property.
For example, look at the following:
........
capacity: {
        defaultValue: "Large"
        isConstant: true,
        serializedName: "details.max_product_capacity",
        type: {
          name: "String"
        }
}

There is a problem with the above definition. Because, capacity is optional, even if the user does not provide any value to it (even though Large is the only accepted value), it is always sent in the request body and it is not correctly deserialized also.
This PR fixes the issue. The SDK generator will also be fixed (by Jonathan) to ensure the defaultValue will be included only if there is a required property and it is set to true. The PR has test cases for serialize and deserialize options also.
@xirzec @jeremymeng Please review and approve the PR.
@ramya-rao-a FYI.....

This change makes sense but I wonder if some of the packages depend on the old behavior to function correctly. Could you please run the live tests pipeline for some?

What is the scenario for isConstant anyway? It doesn't seem to be something from OpenAPI. Is the idea that the value is only supposed to come from defaultValue in this case?
Also, what does it mean to have a property that is isConstant: true but not required?

Let me explain with an example:

In one of our services, we have a definition/model which is defined as an enum (of type string and is not extensible). For example, look at the following definition of capacity:

"max_product_capacity": {
    "type": "string",
    "description": "Capacity of product. For example, 4 people.",
    "enum": ["Large"],
    "x-ms-client-name": "capacity"
},

In the above definition, it is not a required property. It is an optional property. So, the user does not have to provide it at all. But, if the user decides to input the value, then the user could only set it to only one possible value - Large.
Now, if you look at the generated SDK mapper, it will be similar to the following:

capacity: {
        defaultValue: "Large"
        isConstant: true,
        serializedName: "details.max_product_capacity",
        type: {
          name: "String"
        }
}

Now, consider the scenario where the user has not actually set this parameter. But, the core-client package (while serializing) automatically sees the default value and picks it and puts in the request. This is not correct (since the user has not set it). In the same manner, consider the scenario where the service has not sent any value for the capacity. But, the core-client package (while deserializing) automatically sees the default value and picks it and puts in the response. This is also not correct (since the service has not set it)
So, to avoid this issue, my initial thought was let me just remove the defaultValue: "Large" from the mapper and the problem should be solved. So, Jonathan actually opened a PR for the same. But, that caused additional issues. The core-client package is actually expecting the defaultValue for a constant property (i.e. the ones with isConstant set to true)
So, we need to change the logic in the core-client package. The code should use the defaultValue only if the required is set to true. Else, it should not look for the defaultValue (which will not be there) and use the value passed by the user (which will be just the same as the defaultValue - if it existed)

/azp run js - storage-blob - tests

/azp run js - ai-text-analytics - tests

@sarangan12 I ran the storage blob tests pipeline but that packages does not use core-client yet. Does core-http have the same issue?

/azp run js - storage-blob - tests

I think this would be a breaking change for several SDKs (unless they regenerate with this version). So, before releasing/merging this we need to upgrade the major version of the package. This is not urgent. So, I will handle this once I am back

/azp run js - storage-blob - tests


Set access restrictions on new Sections

STORY
As a user, I need to be able to set rights on sections.
ACCEPTANCE

[ ] New sections default to the access rights of the monograph they're attached to.

superseded by #81


Avoid including Kokkos_Core.hpp in Utils and Search packages

Won't Kokkos_View.hpp include Kokkos_Core.hpp?

Won't Kokkos_View.hpp include Kokkos_Core.hpp?

No they include Kokkos_Core_fwd.hpp

Codecov Report

Merging #391 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #391   +/-   ##
=======================================
  Coverage   97.26%   97.26%
=======================================
  Files          96       96
  Lines        6571     6571
=======================================
  Hits         6391     6391
  Misses        180      180

Impacted Files
Coverage Δ

packages/Utils/src/DTK_KokkosHelpers.hpp
100% <ø> (ø)
:arrow_up:

packages/Utils/test/tstKokkosHelpers.cpp
100% <ø> (ø)
:arrow_up:

...h/src/details/DTK_DetailsTreeConstruction_decl.hpp
100% <ø> (ø)
:arrow_up:

packages/Search/test/tstBoostRangeAdapters.cpp
100% <ø> (ø)
: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 53f68b7...41e6c9c. Read the comment docs.

@dalg24 What was the primary reason for this change?

"Include what you use".


Feature/reddit-tipping

Implemented Reddit tipping similarly to how Twitter is done and tested it on multiple reddit profiles

whoot whoot! nice, thanks for tackling this! looking good. I think it is great to bring this to reddit! 🚀
I got a few comments and thoughts:

on twitter all content is loaded asynchronously and also the website navigation only happens in JS. This is the reason why this MutationObserver is used. That observer allows to execute some code and check the DOM changes. I am actually not sure if we need the same approach on Reddit. It seems on reddit the page is fully reloaded and we should be able to just look into the DOM. Did you check this?
it also seems there is a meta tag in the page that contains the user profile description
 maybe this can even be used to extract the lightning information? So we would not need to check for the CSS class?

Hey thanks!

Yeah I assumed at first because of the classnames everything was being generated dynamically so I thought it would be good to use the same MutationObserver but if it's not needed I can take it out an retest
I didn't think to check the meta tags but that seems like a much cleaner way of grabbing the user description. Should I use [https://github.com/BetaHuhn/metadata-scraper] to do this?

Yeah, the MutationObserver is great. but if it works without it it would reduce complexity which I think is good.
to check for the meta tag I would do that dircttly (like here
something like:
const descriptionTag = document.querySelector<HTMLMetaElement>(
    'head > meta[name="description"]'
);
descriptionTag.content...

nice, looks already simpler.
got some more thoughts in the comments.

Great thanks for the suggestions I implemented each one of these and then retested, let me know if anything else looks out of place.

I found one more thing.
but then it looks good:

Ahh good catch! I just updated and retested with a few more accounts now

:shipit: yay!


Suggestion

can you check the roblox cookies that come out of the cookies and write how many robuxes are in the account next to the cookie?

It is possible but in most of the cases, doing this would invalidate the cookie.


Adding data structures

Thank you for contributing to @AllAlgorithms, your pr got merged! ✨ Make sure that you ⭐ the project 🤓, and continue helping us!


Upgrade svelte v5

Upgrading to Svelte v5
Introduction of the Rune
Resolve module dependencies warnings
add vite preprocessor

<EMAIL_ADDRESS>has been released, so we will support it by the end of today.
https://github.com/withastro/astro/blob/refs/heads/main/packages/integrations/svelte/CHANGELOG.md#601

Thank you!


fix: TextInput selectionColor props on iOS

Summary:

This pull request fixes an issue where the selectionColor prop was not applied to the TextInput component on iOS, starting from React Native version 0.74.x.
This issue was introduced in PR 1e68e485 which relocated selectionColor along with selectionHandleColor and cursorColor out of otherProps. This modification inadvertently prevented selectionColor from being passed to the iOS native component.
This change ensures that the selectionColor prop is explicitly included in the RCTTextInputView component's properties, fixing the regression.
Note: selectionHandleColor and cursorColor are Android-specific and do not require explicit passing on iOS.
Changelog:

[IOS] [FIXED] - Fixed an issue where the selectionColor prop was not being applied on the TextInput component.
Test Plan:

Environment: iOS Simulator, React Native 0.74.0.
Steps to reproduce:

Implement a TextInput component with the selectionColor prop set.
Run the application on an iOS device or simulator.
Focus on the TextInput component, write some text and select it.

Expected Result: the selection color should match the color provided to the selectionColor prop.
Actual result before fix: the selection color did not reflect the specified selectionColor prop and fell back to the default iOS selection color (blue).
Screenshots:

Before fix:

After fix:

@NickGerleman looks like the Facebook GitHub Tools / Facebook Internal - Builds & Tests CI step is stuck: it's been running for more than one day now

Posted a cherry-pick request so it can be included in the next 0.74 patch release.


new keyboard layout and separated value / ratio

I've separated the menu into configuration and common usages.
And the stats into the current value and current ratio.
I don't know if it's the best code because I',m not a python developer, but it's working :)

Separating current value and current ratio is a good idea as well as separating all those buttons in two pages.
The only changes to your PR I would suggest are:

Change Current ratio to Current ratios
When one of the buttons in the Configurations sub-menu is pressed, stay in the Configurations sub-menu after button action completition instead of going back to the main sub-menu
Some cleaning up needs to be done in the __btn_current_ratio and __btn_current_value

Thanks for the contributions!

About the cleanup of the code, I don't know too much of the structure of the sqlite :/ and how to do it :(

This snippet:
if update.message.text in ['Begin', 'Go back', 'OK', '⬅ Back']:
            message = 'Please select one of the options.'
            update.message.reply_text(
                message,
                reply_markup=reply_markup
            )

Should also probably separated in two different ones:
if update.message.text in ['Begin', '⬅ Back']:
            message = 'Please select one of the options.'
            update.message.reply_text(
                message,
                reply_markup=reply_markup
            )
elif update.message.text in ['Go back', 'OK']:
            message = 'Please select one of the options.'
            update.message.reply_text(
                message,
                reply_markup=reply_markup_config
            )

In order to properly complete poit 2 of the previous comment

When one of the buttons in the Configurations sub-menu is pressed, stay in the Configurations sub-menu after button action completition instead of going back to the main sub-menu

I'll do the cleaning up in a future commit then, at least as of now it's working 😄


feat: unstoppable domains integration

Thanks for the PR, the changes are integrated in the new design branch that will soon be rolled out to all users. https://github.com/nighthawk-apps/nighthawk-wallet-android/pull/129


Username is repeated when replies are bridged Telegram -> Discord

Describe the bug
Username is repeated when replies are bridged Telegram -> Discord
To Reproduce
Try and bridge a reply from Telegram to Discord with PreverseThreading set to false.
Telegram
Discord
Expected behavior
https://i.imgur.com/XsPYBgI.png
Environment (please complete the following information):
ubuntu, 1.25
Additional context
[telegram]
    [telegram.mytelegram]
        Token="x"
        RemoteNickFormat="<{NICK}> "
        MessageFormat="HTMLNick: "
        QuoteFormat="re @{QUOTENICK}: {QUOTEMESSAGE} \n \n {MESSAGE}"
        QuoteLengthLimit=46
        IgnoreMessages="^/ https://t.me @everyone @here 100x 💎 ⚡ ✅ 🚀 👈 👇 😱 ✍  elon pump 🎉 🎊 😳 🤗 airdrop"

[discord]
    [discord.mydiscord]
        Token="x"
        Server="s" # picked from guilds the bot is connected to
        RemoteNickFormat="{NICK}"
        AutoWebhooks=true
        UseLocalAvatar=["telegram"]
        IgnoreMessages="@everyone @here"
        PreserveThreading=false

    [discord.cometdiscord]
        Token="x"
        Server="s" # picked from guilds the bot is connected to
        RemoteNickFormat="{NICK}"
        AutoWebhooks=true
        UseLocalAvatar=["telegram"]
        IgnoreMessages="@everyone @here"
        PreserveThreading=false

    [discord.sigmavalley]
        Token="x"
        Server="s"
        RemoteNickFormat="{NICK}"
        AutoWebhooks=true
        UseLocalAvatar=["telegram"]
        IgnoreMessages="@everyone @here"
        PreserveThreading=false

Can anyone tell me if Discord replies look like this to them?


Syntax Error

This affected our application when we found out that there is an error with the latest release.
Syntax error in resizeimage/resizeimage.py
def resize_width(image, size, resample=Image.LANCZOS)):

@horaceleung very sorry for this silly mistake. I have published a new release with a fix.


Installing Kerras on R/Windows

Hi All,
I hope somebody can help.
I had a well running Keras version running on R, which took me 30 minutes to install. Then I needed to reinstall after more than 20 hours and several workarounds I got everything running except the install_keras() command. See below:

install_keras()
Using r-tensorflow conda environment for TensorFlow installation
Determining latest release of TensorFlow...done
Installing TensorFlow...
Collecting tensorflow==1.10.1 from https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl
HTTP error 404 while getting https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl
Could not install requirement tensorflow==1.10.1 from https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl because of error 404 Client Error: Not Found for url: https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl
Could not install requirement tensorflow==1.10.1 from https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl because of HTTP error 404 Client Error: Not Found for url: https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl for URL https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Error: Error 1 occurred installing packages into conda environment r-tensorflow
In addition: Warning message:
running command '"C:/MINICO~1/Scripts/activate" r-tensorflow && pip install --upgrade --ignore-installed "https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl"' had status 1

It seems that version 10.10.1 is not available for windows (I use Windows 10), while it is for all other platforms. The file tensorflow-1.10.1-cp36-cp36m-win_amd64.whl seems not to be available anywhere on the Internet (same seems to be true for the 86 version)
I tested  in a browser "https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.1-cp36-cp36m-win_amd64.whl" does not work.
Older version 1.10.0: "https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.10.0-cp36-cp36m-win_amd64.whl" downloads file.
Also:
install_keras(tensorflow="1.10.1)  gives an HTTP error 404 error
install_keras(tensorflow="1.10.0) installs fine, but does not work.
E.g. (below first command works, while second one does not; Flags were set correctly, code used to work in my old installation, I also downgraded numpy and setup tools as requested => no success)
modelNn <- keras_model_sequential()
modelNn %>%
layer_dense(units = FLAGS$dense1Neurons , activation = 'relu', input_shape = c(numInputs)) %>%
layer_dropout(rate = FLAGS$dense1Dropout)%>%
layer_dense(units = 1, activation = 'linear')
I really rely on R tensorflow/keras in my research. Please help!
Thanks
Carsten

@CarstenLange Just want to make sure.
Did you load keras library with library(keras) before modelNn <- keras_model_sequential()?
Also was that successful for tensorflow version 1.10.0?

@ymodak . Thanks for the fast reply.  Yes, Ioaded Keras with library(keras) and the first command executed well. However, only keras_model_sequential() worked other commands did not. E.g.., the second one I mentioned and also "use_session_with_seed(2018)" did not work. I was not surprised, because Keras seems to require tensorflow="1.10.1" and I used  tensorflow="1.10.0" instead, which was kind of a hack.

@CarstenLange You are welcome.Okay. Did you load the libraries such as dplyr or magrittr for the piping operator (%>%) to function? Also can you please paste the error message?

Yes, dplyr was loaded via tidyverse. I also loaded library(magrittr).
Here is the error message (this time from the MNIST example from the Tensorflow R webpage:
model %>%

layer_dense(units = 256, activation = 'relu', input_shape = c(784)) %>%
layer_dropout(rate = 0.4) %>%
layer_dense(units = 128, activation = 'relu') %>%
layer_dropout(rate = 0.3) %>%
layer_dense(units = 10, activation = 'softmax')
Show Traceback

Rerun with Debug
Error in py_call_impl(callable, dots$args, dots$keywords) :
ValueError: Layer dense_1 was called with an input that isn't a symbolic tensor. Received type: <class 'keras.engine.se
However, this was tensorflow 1.10.0 since 1.10.1 does not install (see error at beginning of post).
Thanks.

@CarstenLange Which Keras version did you use? Please also provide the information below so we can better help you.
System information
Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Colab
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version (use command below): 1.10.1
Python version: python 3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

I have installed Keras/R on Windows without any errors.

Hi Wt-Huang,
I had the same experience. I installed first Anaconda (5.0.1) and then MRO some month ago and all worked fine. Then when I tried to update R nothing worked anymore. I deinstalled everything and started from scratch.
The latest version of Anconda does not install correctly on Windows. I found a link and an advice to install Minconda instead. However when installing R I ran into new problems. I gave up and now run the Kerras part of my research on Ubunto.
However, it would be interesting which versions of Anaconda, Python, TensorFlow and Keras work well in your case and when you installed.
Thank you
Carsten
…………………………………………………..
Carsten Lange, Ph.D.
Professor of Economics and Graduate Coordinator
California State University
3801 west Temple Ave.
Pomona, CA 91768
Phone: +1<PHONE_NUMBER>
Email<EMAIL_ADDRESS>From: wt-huang<EMAIL_ADDRESS>Sent: Friday, September 28, 2018 6:37 PM
To: tensorflow/tensorflow<EMAIL_ADDRESS>Cc: Carsten Lange<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [tensorflow/tensorflow] Installing Kerras on R/Windows (#22487)
I have installed Keras/R on Windows without any errors.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftensorflow%2Ftensorflow%2Fissues%2F22487%23issuecomment-425604925&data=02|01|clange%40cpp.edu|9d574ba4e0744669e11d08d625ac062c|164ba61e39ec4f5d89ffaa1f00a521b4|0|0|636737818329140866&sdata=F1y%2F2mv%2BFN5MgpEL%2F%2F8SOesgt0svWqjYRFTZEkwAtfk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAePQqHYJgVaXZr2u0zxw9BggSLHwjhMIks5ufs6vgaJpZM4W3kye&data=02|01|clange%40cpp.edu|9d574ba4e0744669e11d08d625ac062c|164ba61e39ec4f5d89ffaa1f00a521b4|0|0|636737818329140866&sdata=tfcZjL6CYJz0OpPwB%2BfFCcqG26ZyiRdGbyfl0JyAidk%3D&reserved=0.

@CarstenLange
Hi Carten, the previous Anaconda seemingly have less installation issues, however Ubuntu can work just as well if not better. Miniconda is compact but you could miss the benefit of some handy and useful packages. FWIW the versions I have used was Anaconda 3.7.0, Python 3.6, TensorFlow 1.10.0, Keras 2.2.0.

Hi Wt-Huang,
Thanks for the email. I had TensorFlow 1.10.0 installed too when everything still worked. Then when I reinstalled TensorFlow 1.10.0 was not available on the Internet anymore.
I just recently saw that Anaconda 5.3.0 is out. I will wait for a while until it is at least updated ones and then try to install from scratch.
Best
Carsten
From: wt-huang<EMAIL_ADDRESS>Sent: Wednesday, October 3, 2018 1:04 PM
To: tensorflow/tensorflow<EMAIL_ADDRESS>Cc: Carsten Lange<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [tensorflow/tensorflow] Installing Kerras on R/Windows (#22487)
@CarstenLangehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCarstenLange&data=02|01|clange%40cpp.edu|c8208f3e1b2d4377f6f508d6296b5949|164ba61e39ec4f5d89ffaa1f00a521b4|0|0|636741938373054367&sdata=yMCG0wTd1mFkor0ZYf%2BC4E9rbFUq8MNBSsqMHq0VnKs%3D&reserved=0
Hi Carten, the previous Anaconda seemingly have less installation issues, however Ubuntu can work just as well if not better. Miniconda is compact but you could miss the benefit of some handy and useful packages. FWIW the versions I have used was Anaconda 3.7.0, Python 3.6, TensorFlow 1.10.0, Keras 2.2.0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftensorflow%2Ftensorflow%2Fissues%2F22487%23issuecomment-426777772&data=02|01|clange%40cpp.edu|c8208f3e1b2d4377f6f508d6296b5949|164ba61e39ec4f5d89ffaa1f00a521b4|0|0|636741938373064380&sdata=pgXMPBN2l9AJdcF7rMf2ioSo0JlDMq3jdFbESsYSGdc%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAePQqHg0daFyFzpC7uvVdq5oGVTvEL4sks5uhRgqgaJpZM4W3kye&data=02|01|clange%40cpp.edu|c8208f3e1b2d4377f6f508d6296b5949|164ba61e39ec4f5d89ffaa1f00a521b4|0|0|636741938373074388&sdata=xzxh0tNNwSRJMOHstRz%2FRkhnwLT13HSXTRI3In%2F%2BDPY%3D&reserved=0.

@CarstenLange
Hi Carsten, glad that everything works for you now. Any further issues you may have when using TensorFlow, feel free to let us know.


Represent 0 as length of zero vector

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

I signed it!

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ Googlers: Go here for more info.

I signed it!

@DingyuChowMein Are you happy to rebase this?  (Note that a couple more opaque zero/one additions have landed, so you will need to re-number.)

Looks like you didn’t run mvn package locally - seems they the build failed due to checkstyle violations. Can you check?

I'm going to close this due to inaction on the above comments, but do feel free to reopen in due course if you wish.


Update all wallet connection dependencies

Due to the recent exploit in ledgerhq's connect-kit, we should make sure all wallet connection dependencies are updated to their latest version (which should have been released within the last 24 hours from the creation of this issue). The developer on this issue should do the due diligence to make sure that the versions of all updated dependencies have been explicitly acknowledged by their maintainers to be safe from the connect-kit exploit.

Closing this issue, as there are efforts underway to update our wallet stack.


csv generated report

Is your feature request related to a problem? Please describe.
Desiring a faster way to get CSV from the dashboard....
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
From the Reports menu, currently there is a Generate PDF and a Generate PNG option.  We'd like to see a Generate CSV option which would provide all data available to the extend possible.
A clear and concise description of what you want to happen.
When a user, say a data scientist, selects the new Generate CSV menu option, the data matching the visualizations shown in the dashboards is made available for download. Then, they can use that CSV file within tools such as Jupyter Notebook.
Describe alternatives you've considered
I saw this link which illustrates that feature, but would like it in OpenSearch natively.
A clear and concise description of any alternative solutions or features you've considered.
Currently, one can add a data table view and from there using a multistep workaround of saving Dashboard filter, opening the filter query in Discover, resaving in Discover, then reporting -> export as CSV.  Way to complex.
Also, the table option only exports fields that are configured, not ALL, which is desired.
Additional context
Add any other context or screenshots about the feature request here.

i believe this is the same as https://github.com/opensearch-project/dashboards-reporting/issues/113, closing as duplicate


Setting viewportOverrides with Ember.on doesn't work as expected

In the readme, it is recommended to override options like this:
export default Ember.Component.extend(InViewportMixin, {
  viewportOptionsOverride: Ember.on('didInsertElement', function() {
    Ember.setProperties(this, {
      viewportUseRAF            : true,
      viewportSpy               : false,
      viewportScrollSensitivity : 1,
      viewportRefreshRate       : 150,
      viewportTolerance: {
        top    : 50,
        bottom : 50,
        left   : 20,
        right  : 20
      }
    });
  })
});

However, I noticed that setting viewportSpy wasn't working for me. AFAIK, when Ember.on runs is actually non-deterministic. Since we're setting up the observer in the didInsertElement hook in the addon, I actually think it's more appropriate to override like this:
export default Ember.Component.extend(InViewportMixin, {
  didInsertElement() {
    Ember.setProperties(this, {
      viewportUseRAF            : true,
      viewportSpy               : false,
      viewportScrollSensitivity : 1,
      viewportRefreshRate       : 150,
      viewportTolerance: {
        top    : 50,
        bottom : 50,
        left   : 20,
        right  : 20
      }

      this._super(...arguments);
    });
  })
});

to ensure that the properties are set before the InViewportMixin runs.
Does that sound correct? I'll happily submit a PR updating the docs if this sounds reasonable.

Hey @blimmer, thanks for opening this issue. Your override is most definitely correct, although I would move the super call to come before the setProperties. A PR would be welcome!

@poteto I actually think it's important to call _super after setting the properties because _super will call the mixin's didInsertElement before you set the properties. Check it out:
export default Ember.Component.extend(InViewportMixin, {
  didInsertElement() {
    this._super(...arguments);

    console.log('*** IN COMPONENT MIXIN didInsertElement');
  }
});

and the console output:
in-viewport.js:42*** IN IN_VIEWPORT MIXIN didInsertElement
foo-bar.js:6*** IN COMPONENT MIXIN didInsertElement

Actually, why do we overwrite the options in the init method anyway?
In my use case, I just want to set the viewportSpy method and it seems weird that it gets overwritten on init. Seems like I should be able to do:
export default Ember.Component.extend(InViewportMixin, {
  viewportSpy: true,
});

What's the reason for overwriting in init and requiring the user to tap into didInsertElement?

Closing since the mixin approach is less and less common