Relocate Ziggy Constant in front end so it is not shown in view page source.

I am using Ziggy to expose my Laravel routes for vue using inertia js .
but while i view the page source i can clearly see all of laravel routes like.
    const Ziggy = {"url":"http:\/\/<IP_ADDRESS>:8787","port":8787,"defaults":{},"routes":
    ......

"sup_finish_tt_order":{"uri":"front\/finishorder","methods":["POST"]},"assign__tt":{"uri":"front\/assigntt","methods":["POST"]},"technicians":{"uri":"technicians","methods":["GET","HEAD"]},"change-password":{"uri":"change-password","methods":["GET","HEAD"]},"reset.password":{"uri":"c
----------

is there  anyway to movw this to other file e.g app.js

Yes, take a look at the JavaScript frameworks and Filtering Routes sections of the Readme. Feel free to comment here again if you have specific questions or run into issues setting it up!

If  possible it would be great to create a repo  that demonstrates advance configuration with  frontend frameworks .
Laravel vue  and inertia js stack is promoting Ziggy , there will more and more confused users  [like me], please support.


Fix DID key format

See commit.

First time I see that, but looking at the dependencies, it's tied to a different key implementation anyway.

First time I see that, but looking at the dependencies, it's tied to a different key implementation anyway.

Right, good point :)


Async Event dispatching and the EventStore

From @albe on September 16, 2016 20:40
Greg Young and a couple of others state that the EventStore itself can work as an Event dispatcher/bus, because it basically works like a queue if you just keep an index of where you last dispatched from.
A similar discussion was started in #2 which I'd like to contiue here:

you want the events to be published within the same transaction

I think I read that too somewhere, but I must say I'm not convinced. My reasoning mainly is, that the publishing of the events can be retried at any time anyway.
The events become a fact, the instant they are written to permanent storage. Everything happening afterwards is conceptually eventual consistent. Binding the dispatching of the events into the same transaction would mean, that if dispatching fails for whatever reason, the eventstore would need to be rolled back. This is wrong on so many levels I can't even express it.
What I do think is a required contract though, is to guarantee at-least-once delivery of the events. But that just means to keep a secondary index of events that have already been (successfully) dispatched as stated above.
Probably someone will state that there are cases where you need an immediately consistent read model. I'd argue to reconsider your case. Do you really need immediate consistency, or is it just that you want to work with a projected state within the same request? That's quite a difference!
Also if you only need the immediately consistent projected state for some aggregate behaviour, check if you shouldn't put the projected state into your aggregate. For all other cases I guess our current in-process EventBus is good enough, so it only needs to be selectively available (ie. through some InprocessEventListenerInterface).
The (default?) async behaviour would instead query the EventStore from it's last position cronically (cron CLI command maybe), then dispatch the events to all EventListenerInterfaces.
Copied from original issue: neos/Neos.EventStore#8

To clarify what I meant with the phrase you quoted:
I meant that you want the event to be stored atomically and I think we're completely on the same track on that: Before the event is published to the store it has no value to the system. So it should go to the store first and within the same transaction.
Whether those published events are handled sync or async could well be abstracted through different busses etc

It might be a lack of coffee on my side, but I don't really get what you are suggesting?

From @albe on September 20, 2016 19:57
Bear with me, I'm always good in overcomplicating things with my writing :)
What I mean is, "within the same transaction" implicates that if anything inside that transaction fails (store or dispatch), everything needs to be rolled back. But I don't see an already successful store being rolled back because the dispatch failed.

From @albe on September 21, 2016 13:31
OK, so you weren't using the term transaction in the technical definition kind of way (https://en.wikipedia.org/wiki/Transaction_processing), but were rather talking about "within the same request", correct?
So we agree that the process inside a single Request is:
Transaction Begin:
  Aggregate::executeSomeCommand(...)
  EventStore::commit(Aggregate::pullUncommittedEvents())
Transaction End.
try EventBus::dispatchUndispatchedEvents()

The Aggregate::executeSomeCommand being in a transaction with the EventStore commit is only conceptually, because the commit is never triggered if the Aggregate fails, and if the commit fails, the Aggregates uncommitted Events will be lost anyway on the next Request.
But: If the dispatch fails, it can be reattempted at the next Request or by a cronjob or whatever - it just holds a reference to the last commitId of the EventStore that it already dispatched successfully.
The latter only would need to be transactional if you want a strongly/immediate consistent Projection. We could implement this when it's explicitly asked for (not trivial), but the default should always be an eventual consistent projection model IMO.

OK, that was a bit misleading. I never thought of any rollback (especially not of published events).
It can be useful to publish more than one event within a transaction (including rollback on failure) but that's a different topic I guess

OK, so you weren't using the term transaction in the technical definition [...] but were rather talking about "within the same request", correct?

Well, what I meant is: You want to ensure that the event is actually published to the store within an atomic process. In other words: $someAggregateRepository->save($someAggregate) should immediately halt with an exception if events couldn't be stored for some reason.
In (yet) other words: The line after $someCommandHandler->handleSomeCommand($someCommand) you know the events in question have been stored for good.
And, yes, I agree to your process description: If there are multiple events* those should be published transactional. And dispatching via the EventBus must not be part of the transaction.
*) I don't think that there will ever be more than one unpublished event in an aggregate, but sometimes you need to transactionally publish multiple events of multiple aggregates – at least I haven't found a good way around this in some rare scenarios

From @albe on September 22, 2016 13:44
Then we're on the same track with that, nice :)

#113


pip-dump: add --dry-run option to pip-dump / dry-run y default

I have just tried pip-dump, and it did not work very well (report might follow, probably caused mainly by vcs-style/editable installs).
I would like to have a --dry-run option, which would not rewrite / add to the existing files, but display what it would output.
Maybe "dry-run" should even be the default, and a switch like "-f" would be required to write the files?!

Why was this closed?  It still seems like it would be good to have a "dry-run" option!
(Also note, it looks like the master branch is once again current....)
Can you re-open this?  Thanks!


🗡 Review DNS Security Group Rules

Terraform needs to be amended to provide for only the following traffic throughtout environments.
![image.png](https://images.zenhubusercontent.com/622a1024f6731fe223cfa94b/ecb41b87-6504-48dd-9984-90af76a6f9a3)


require lower-switch in preISel passes.

This is a workaround which is likely to be superseded by work in
progress on a better divergence analysis that can handle irreducible
blocks.
The default target of the switch instruction may sometimes be an
"unreachable" block, when it is guaranteed that one of the cases is
always taken. The dominator tree incorrectly computes that that such a
switch instruction does not have an immediate post dominator. This
confuses divergence analysis, which is unable to propagate sync
dependence to the targets of the switch instruction.
As a workaround, the AMDGPU target now includes lower-switch in the
list of preISel passes. The LowerSwitchPass handles the unreachable
default target correctly, allowing the dominator tree to find the
immediate post dominator.

Need to create a Phabricator review to get it into trunk.

Submitted in trunk.


Update history and wrap localstorage in try/catch

So this is just porting changes from 1.0 into 2.0?

What about this pull request?

If I remember correctly that is what it was.

@mitar @alanning Any updates on v2 or this package in general?


Python-Levenstein required

/usr/local/lib/python2.7/dist-packages/fuzzywuzzy/fuzz.py:35: UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning   warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')
I have read issues with Levenstein. This error often appears on Windows, as I understood. But I use Linux Mint 17.1 . And I have this error too. Can you help with it?

This appears to be a warning, not an error. So I don't think it's required, it's just highly recommended.

@kevin-brown is correct.
If you're goal is to remove the warning, your options are

Install the python-Levenshtein package with pip.
Silence UserWarning level warnings when running your code.

Ok. Thank you. Python-Levenshtein can't be installed. Got an error with it, too. I will ignore it until it's not critical. Oh try to fix this later.)


[Task] Extend Agent with DID Comm Functionalities

Description
DID Communications is a standard from the Decentralized Identity Foundation (DIF) that enables different entities that utilize SSI, to talk to each other in a common language. They can use this language to establish trust, share trustworthy information and request things from each other.
The task requires to add DID Comm functionalities to the Identity Agent. This includes all the different interactions researched and specified in the specifications folder. Whether we should implement our own specifications or those from Aries (to maximize interoperability) needs to be investigated.
Motivation
It provides a way to create out-of-the-box interoperability between different applications using IOTA Identity.
Resources

Our Spec
DIF Rendered Draft
DIF Spec Files (More up-to-date then render)

To-do list
Please open a new PR per task for this issue.

[ ] Trust Ping
[ ] Feature Discovery
[ ] DID Discovery
[ ] DID Authentication
[ ] DID Resolution
[ ] Credential Options
[ ] Credential Schema
[ ] Credential Issuance
[ ] Credential Revocation
[ ] Presentation Verification
[ ] DID Introduction

Change checklist per item

The feature or fix is implemented in Rust and across all bindings whereas possible.
The feature or fix has sufficient testing coverage
All tests and examples build and run locally as expected
Every piece of code has been document according to the documentation guidelines.
If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
If the feature is not currently documented, a documentation task Issue has been opened to address this.

Agent and DIDComm are out of the current scope of the library


[3.x] HTTP API healthcheck

The concept of having an API for the bot can ease multiple tasks:

~sending commands to the bot via HTTP (opens up new ways of implementing SDKs for tf2autobot, implementable in any language since it's REST)~
~reading information about the BOT, including current item configurations for trading~
periodic healthchecks performed on the bot via HTTP endpoint (useful for Docker/Kubernetes, but not limited to)

Roadmap

[x] Base implementation, /health endpoint for checking readiness/aliveness
[x] Uptime endpoint for reading the current uptime status
[ ] ~Configured items/bots endpoint for reading the configured items and bots~
[ ] ~Tests, lots of tests~

The GUI v3 rework already has an entrypoint for the API, so sticking just with healthchecks and uptime should be fine. 👍🏼

Love the idea. I will let the others share their thoughts too.

I'm working on something simular - but I'm using mode-IPC for it, is gonna be used for GUI

Discussed with @arik123 earlier on Discord about IPC and the need of having an API server on a bot. The main points were:

Having a bot running is not going to start the second one since the API is already running on the specified port. This isn't an issue on Docker or any other distributed system since the API is isolated from external networking, and will only be accessible at their respective container names.
The GUI is on its way and will act as a master for all bot processes. This is an excellent idea because it doesn't expose the bot on the network and the other functionalities on this PR are redundant, so I put a strike on them on the roadmap.

The only left issue is the healthcheck functionality. The healthcheck can pass/fail if I either:

call an URL present on the process (200 = pass, non-200 = fail)
ping a TCP socket (established = pass, rejected = fail)
execute a command (exit code zero = pass, exit code non-zero = fail)

I was looking for the TCP or the command execs for healthchecks, but I'm not sure which one to pick or how we can acheive this. The HTTP /health check is still good, but it doesn't work for simple processes, outside Docker/Kubernetes, excepting if a different port is set for each one.

Thanks for the update. You may keep this pull request open so every progress/discussion can be seen here.
This may sound weird but a built-in GUI (not enabled by default) might be good, but not sure if that will use a lot of resources.

it could be probably implemented such that, it would take near to nothing if not enabled

it could be probably implemented such that, it would take near to nothing if not enabled, but then the whole part of GUI that I have planned - Managment of multiple bots would not work

Oh right true. in that case, probably best to make the GUI a separate app.

Maybe the API can still exist (and be disabled by default) for non-GUI-based applications, like managing your own bots?

Maybe the API can still exist (and be disabled by default) for non-GUI-based applications, like managing your own bots?

Yes, sure thing.

Also maybe add some note to the source, that tells everyone about GUI as main API provider.

Now let say I want to use this and want to check by bot uptime via an API, and I am running my bot on a VPS, I need to type this on my browser URL:
http;//<IP_ADDRESS:PORT>/uptime
right?

@idinium96 Yes.


Hierarchical Netlist Names Not Found by SPEF Annotation

Describe the bug
For the special case where synthesis netlists preserve hierarchy and OpenROAD flattens them, the resulting naming convention in the netlist and that of the SPEF file do not appear to align.  This results in SPEF parasitic annotation failures.
As an example, we use a particular hierarchical name from an open source design implemented with hierarchy preserved during synthesis.  The netlist name for a particular instance is:
sky130_fd_sc_hd__xor2_2 \soc/gpio/gen_filter[14].filter/_14_  (.A(ea_din[0]),
The corresponding instance name mapping in the SPEF file is:
*27610 soc/gpio/gen_filter\[14\]\.filter/_14_
For the example above, the expected behavior is that the slight differences in name syntax used between the two files are resolved internally to OpenROAD and that annotation succeeds without causing warnings.  Instead, the following warning is generated:
[WARNING STA-0172] ./asic_core.minimum.spef line 263475, instance soc/gpio/gen_filter\[14\].filter/_14_ not found.
Note that thousands of similar examples are present in the open source design used, and that they result in delay modeling errors posted in Issue #3211.
To investigate, the above example was modified in the netlist AND SPEF file with matching names that lack special characters that are treated as corner cases by many EDA software products when managing ASIC netlist names (notably '', '[', ']', and '.').  The diff of the netlists is as follows:
28564c28564
<  sky130_fd_sc_hd__xor2_2 \soc/gpio/gen_filter[14].filter/_14_  (.A(ea_din[0]),
---
>  sky130_fd_sc_hd__xor2_2 soc_gpio_gen_filter_14_filter_14_  (.A(ea_din[0]),
Similarly, the SPEF file is modified to produce a matching name:
< *27610 soc_gpio_gen_filter_14_filter_14_
---
> *27610 soc/gpio/gen_filter\[14\]\.filter/_14_
Expected Behavior
The expected outcome of this experiment is elimination of the warning noted above.  The intended outcome is obtained, along with some additional side effects, yielding the following overall diff in warning messages from readback of the netlist and SPEF:
36a37
> [WARNING STA-0172] ./asic_core.minimum.spef line 263475, instance soc/gpio/gen_filter\[14\].filter/_14_ not found.
39a41
> [WARNING STA-0174] ./asic_core.minimum.spef line 263482, net soc/gpio/gen_filter\[14\].filter/_14_ not found.
59a62
> [WARNING STA-0174] ./asic_core.minimum.spef line 263537, net soc/gpio/gen_filter\[14\].filter/_14_ not found.
1142,1143d1144
< [WARNING STA-0174] ./asic_core.minimum.spef line 266209, net soc/gpio/u_reg/direct_out_we not found.
< [WARNING STA-0174] ./asic_core.minimum.spef line 266210, net soc/gpio/u_reg/_014_ not found.
2037d2037
< [WARNING STA-0172] ./asic_core.minimum.spef line 298393, instance soc/u_rv_core_ibex/u_core/genblk1.genblk1.gen_regfile_latch.register_file_i/wdata_a_q_$_DFFE_PN0P__Q_23 not found.

Right facing diffs (">") indicate warnings present in the unmodified netlist and not in the modified netlist.  Left facing diffs ("<") indicate warnings in the modified netlist that didn't line up with warnings found in the unmodified netlist.  Inspection via tkdiff suggests that these new warnings in the modified netlist arise because the warning count limit is being reached, and eliminating the three warnings via modification allows previously unprinted warnings to appear in the log file.
Environment
[WARNING] Your current OpenROAD version is outdated.
It is recommened to pull the latest changes.
If problem persists, file a github issue with the re-producible test case.
kernel: Linux 5.14.0-1059-oem
os: Ubuntu 20.04.5 LTS (Focal Fossa)
cmake version 3.24.2
-- The CXX compiler identification is GNU 9.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- OpenROAD version: v2.0-7537-g47991be87
-- System name: Linux
-- Compiler: GNU 9.4.0
-- Build type: RELEASE
-- Install prefix: /usr/local
-- C++ Standard: 17
-- C++ Standard Required: ON
-- C++ Extensions: OFF
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- The C compiler identification is GNU 9.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found Python: /usr/bin/python3.9 (found version "3.9.5") found components: Interpreter
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Performing Test C_COMPILER_SUPPORTS__-Wall
-- Performing Test C_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive - Success
-- Performing Test C_COMPILER_SUPPORTS__-x
-- Performing Test C_COMPILER_SUPPORTS__-x - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-x
-- Performing Test CXX_COMPILER_SUPPORTS__-x - Failed
-- Performing Test C_COMPILER_SUPPORTS__c++
-- Performing Test C_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__c++
-- Performing Test CXX_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
-- TCL readline header: /usr/include/x86_64-linux-gnu
-- Found SWIG: /usr/bin/swig4.0 (found suitable version "4.0.1", minimum required is "3.0")
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0")
-- boost: 1.80.0
-- Found Python3: /usr/include/python3.9 (found version "3.9.5") found components: Development Development.Module Development.Embed
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- spdlog: 1.10.0
-- Found BISON: /usr/bin/bison (found version "3.5.1")
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.17") found components: doxygen dot
-- STA version: 2.4.0
-- STA git sha: 882681a674e7089e5f02de4ba2050c6be32b6cd1
-- System name: Linux
-- Compiler: GNU 9.4.0
-- Build type: RELEASE
-- Build CXX_FLAGS: -O3 -DNDEBUG
-- Install prefix: /usr/local
-- Found FLEX: /usr/bin/flex (found version "2.6.4")
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- SSTA: 0
-- STA executable: /tools/OpenROAD/src/sta/app/sta
-- GPU is not enabled
-- Found re2: /opt/or-tools/lib/cmake/re2/re2Config.cmake (found version "9.0.0")
-- Found Clp: /opt/or-tools/lib/cmake/Clp/ClpConfig.cmake (found version "1.17.7")
-- Found Cbc: /opt/or-tools/lib/cmake/Cbc/CbcConfig.cmake (found version "2.10.7")
-- Found Eigen3: /usr/local/share/eigen3/cmake/Eigen3Config.cmake (found version "3.4.0")
-- Found SCIP: /opt/or-tools/lib/cmake/scip/scip-config.cmake (found version "8.0.1")
-- GUI is enabled
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS)
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found suitable version "1.80.0", minimum required is "1.78")
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization system thread
-- TCL readline enabled
-- Tcl Extended disabled
-- Python3 enabled
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/tmp.qQqyGyCxIs

To Reproduce
Download this tarball:
Example netlist modification to eliminate SPEF annotation warnings

untar to directory of your choosing.
cd testcase
./run.sh

Execution of run.sh executes readback of the design database and loading of the verilog netlist and SPEF file to generate above warnings and redirect them to a log file.  A provided perl script eliminates filename differences in the warning messages to simplify the analysis of the logfile diff.  The diff is then executed and printed to STDOUT.  When run successfully the resulting diff should match that posted to this issue thread.
Relevant log output
No response
Screenshots
No response
Additional Context
No response

I think this is more of an spef generation issue.  If you have:
*27610 soc\/gpio\/gen_filter\[14\]\.filter\/_14_

then it annotates fine.  Please package your setup to extract the spef.


Support for https://status.okta.com/

Summary
Support to add https://status.okta.com/ status page in the app.
Desired Behaviour
Have a quick setup item for Okta
Possible Solution
Additional context
Configuring CORS still throws the following error:
xhr.js:35          GET https://status.okta.com//api/v2/incidents.json net::ERR_FAILED 401

+1 for okta support

@ahmedlearns, in our plan for upgrade project for next quarter we will add this requests as well, consider adding support for status.okta.com to status-pages nerdlet. and update the issue - thank you


lang agenda: include concerns and FCP notes

One of the items in the lang-agenda dumps out the proposed FCPs:
https://github.com/rust-lang/triagebot/blob/bc415ec002845aa0c90a28df5457b666381769f2/templates/lang_agenda.tt#L46-L51
It would be awesome to include registered comments and the like.

as one who is less familiar with the lang-agenda goings-on, not 100% certain what you mean by registered comments.
would you be willing to clarify?
Given the following description, assuming it’s accurate, would I be correct to assume you mean the “preceding summary comments” that come before the FCP (described in the second sub-bullet)?

Ah, I somewhat mistyped. I meant registered concerns. But really I think what I would want to do is to reproduce (a) the summary comment and (b) the content of the FCP comment (which includes a set of checkboxes along with a set of registered concerns).

So as an example, reproducing the content of this comment would be a start; ideally we'd include this comment too to give more context.

FWIW, having looked a little into this, it will likely require modifications to the rfcbot API -- it currently only exposes the Markdown of the FCP comment. Maybe it's enough to inline those, but IIRC one of the additional problems is that there's no way to ask the rfcbot API for issues which are under FCP for a particular team (though that information is presumably tracked somehow -- it's displayed on rfcbot.rs). I'm capable of reviewing and deploying changes there, though; see https://github.com/rust-lang/rfcbot-rs/ for the source code.
I'm significantly less familiar with rfcbot than triagebot, so am not really able to point in the right direction though.

The API is https://rfcbot.rs/api/all, by the way -- it technically has the barebones of the right information (e.g., you can pull the comments Niko is looking for from it for sure), but I'm not sure if it's easy to pull everything from it. Maybe starting with what it has is a good first step though -- it's probably easier than doing upstream modifications first :)

@Mark-Simulacrum we know the set of issues already based on github labels, can we ask rfcbot for the markdown test for a particular issue? that'd be a good start.

Not directly, but I think the rfcbot API does contain enough to find it from the full set -- probably a good approach.

Thanks for the clarifications, y'all. Familiarizing myself with this now.
Here's my current understanding.

@nikomatsakis wants wants the lang agenda to output all proposed FCPs (which it currently does) but for each proposed FCP, include the following:

the content of the bot tracking comment (and presumably the link to said comment)

the comment ID  is available via rfcbot.rs/api/all endpoint through the path fcp.fk_bot_tracking_comment
the content of the comment is available via rfcbot.rs/api/all endpoint through the path status_comment.body

the content of the initiating comment (and presumably the link to said comment)

the comment ID is available via rfcbot.rs/api/all endpoint through the path fcp.fk_initiating_comment
the content of the comment is NOT YET available via rfcbot.rs/api/all endpoint — however, we could get it through hitting GitHub API since we have the initiating comment ID

@Mark-Simulacrum you're in favor of doing what we can in triagebot now and making upstream changes (to rfcbot) in the future

eventually, we may want to include (for instance) the initiating comment content within the rfcbot.rs/api/all endpoint through the bath initiating_comment.body or something of the sort

Outstanding questions:

@nikomatsakis, would you be able to point me in the direction of where the lang agenda spits out currently? Is it in a Zulip channel or somewhere else?
regarding the following quote:

IIRC one of the additional problems is that there's no way to ask the rfcbot API for issues which are under FCP for a particular team (though that information is presumably tracked somehow -- it's displayed on rfcbot.rs)

@Mark-Simulacrum would you be able to link to wherever that's displayed in rfcbot? Or are you saying it's in the rfcbot.rs/api/all endpoint already?

@Mark-Simulacrum & @nikomatsakis — what's the significance of knowing the particular team? Does this affect which FCPs get rendered? (Ties in with the first question about where the lang agenda outputs currently)

regarding this quote:

we know the set of issues already based on github labels, can we ask rfcbot for the markdown test for a particular issue? that'd be a good start.

@nikomatsakis what's the relevance of knowing the labels? Is that what determines the relevant team in an FCP?

@nikomatsakis what do you mean by a "markdown test"?

Oh also... another outstanding question:

@Mark-Simulacrum / @nikomatsakis  Since we're only trying to get proposed FCPs — am I correct in saying the way we'd get that from the rfcbot.rs/api/all endpoint is to map through each FCP in that list and only pull the ones with fcp.disposition == "merge"?

@chazkiker2
The template actually lives in this repo! It is generated by cargo run --bin lang-agenda or something like that. The template itself is here but the binary and wrapper is invoked here:
https://github.com/rust-lang/triagebot/blob/2a37c453c01f0d50d5266cab2318a729eb217f64/src/bin/lang.rs#L12-L13
which in turn uses this helper:
https://github.com/rust-lang/triagebot/blob/2a37c453c01f0d50d5266cab2318a729eb217f64/src/agenda.rs#L440

what's the significance of knowing the particular team? Does this affect which FCPs get rendered? (Ties in with the first question about where the lang agenda outputs currently)

I actually don't think you need to worry about that. The agenda is already identifying issues tagged with the appropriate team. We just want to add extra info for particular issues.

what's the relevance of knowing the labels? Is that what determines the relevant team in an FCP?

Yes. The issues tagged with T-lang are those that are waiting on a lang team decision.

what do you mean by a "markdown test"?

Typo, I meant "markdown text"

@chazkiker2

Since we're only trying to get proposed FCPs ...

Right now, the list of issues is generated by querying github. I think that is working fine, so potentially we could just consult the RFC bot for particular issues, and not to generate the list itself, but I'm not sure how the API is setup. I also think it would be fine to consult the list -- the only catch is that some of the things in FCP, I realize, may be using the "rustbot second" system as well, so we'd have to account for that.
(We need to bring those two into more harmony.)

@rustbot claim


update license's year in vim-airline-themes

Hi, Christian.
This Pull Request is related to this url.

https://github.com/vim-airline/vim-airline/pull/2040

Cloud you check this Pull Request?

thanks!

Thanks for checking!


[AIRFLOW-2639] Dagrun of subdags is set to RUNNING immediately

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title.

https://issues.apache.org/jira/browse/AIRFLOW-2639

Description

[X] Here are some details about my PR, including screenshots of any UI changes:

Forward dagrun conf to subdag directly in SubdagOperator
Remove eager creation of subdags when triggering a DAG

Tests

[X] My PR adds the following unit tests

test_forwards_dag_run_conf

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[X] In case of new functionality, my PR adds documentation that describes how to use it.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3540 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3540      +/-   ##
==========================================
+ Coverage   77.32%   77.33%   +<.01%
==========================================
  Files         204      204
  Lines       15274    15267       -7
==========================================
- Hits        11811    11806       -5
+ Misses       3463     3461       -2

Impacted Files
Coverage Δ

airflow/operators/subdag_operator.py
96.87% <100%> (+6.55%)
:arrow_up:

airflow/api/common/experimental/trigger_dag.py
100% <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 702a57e...c5effd3. Read the comment docs.

@milton0825 @kaxil Can you please take a look?

This seems to address two issues at once. Please split and make sure to add tests to both. Changing the trigger of a dag requires end to end test. Ie. will the sundag still run when the dag is triggered but its subdag not set to running

I should have written that this PR tries to fix behaviour that was introduced in #3460 just some days ago. Before that the subdag was not eagerly created at all (and hence not set to running), so this PR reverts the changes in trigger_dag.py.
Are there e2e tests in airlfow repo? Can you point me to them? I tested manually e2e and deployed this change already to our dev env and will deploy to production tomorrow. And yes, the subdag run is created by the SubdagOperator and runs properly.
But I'm ok with splitting it up this PR. Then I'd suggest to revert #3460 for 1.10, and then create a separate PR for passing conf from the main dag to the subdag.


fix: Line::styled not being rendered correctly inside a paragraph

rendering a Paragraph with a Line::styled ignores the style, but using styled spans with a Line::default().spans(vec![Span::styled]) works just fine.
the issue seems to be, that the paragraph tries to render the styled_graphemes of the Spans instead of the Line directly

repro of the problem
fn ui(frame: &mut Frame) {
	let l1 = Line::styled("should be bold", Style::default().bold());
	let l2 = Line::styled("should be colorful", Style::default().cyan());
	let l3 = Line::styled("should be dim", Style::default().dim());

	let lp = Line::default();

	let s1 = vec![Span::styled("but it works with spans", Style::default().cyan())];
	let ls = Line::default().spans(s1);

	let block = Block::default()
		.borders(Borders::ALL)
		.padding(Padding::new(4, 4, 2, 2));
	let paragraph = Paragraph::new(vec![l1, l2, l3, lp, ls]).block(block);

	frame.render_widget(paragraph, frame.size());
}

Thanks for making a PR! Can you add a test to make sure this fixes it?

done, idk what's going on with codecov though


Unable to display Validation Messages with Zod in Next.js

Describe the bug
I am encountering an issue in my Next.js project where I am unable to display validation messages. Although the field.form.state.errors property correctly contains the errors, the field.state.meta.errors property is empty. For validation, I am using Zod.
Your minimal, reproducible example
https://codesandbox.io/p/github/mariusraupach/curly-fiesta/main?import=true&embed=1
Steps to reproduce

Enter a value that is not an email address into the input field.

Expected behavior
As a user, I expected to see a validation message indicating that the value must be an email address.
How often does this bug happen?
None
Screenshots or Videos
No response
Platform

OS: macOS 14.5
Browser: Google Chrome - Version 126.0.6478.127 (Official Build) (arm64)

TanStack Form adapter
None
TanStack Form version
0.26.4
TypeScript version
5.5.3
Additional context
No response

Same issue here

@stijnvanderlaan
I resolved the issue by adding the following code to the form.Field:
validators={{
  onChange: userSchema.shape.email,
}}

The updated field now looks like this:
<form.Field
  name="email"
  children={(field) => {
    console.log(field.state.meta.errors);
    console.log(field.form.state.errors);

    return (
      <>
        {field.name}
        <input
          onChange={(event) => field.handleChange(event.target.value)}
          type="email"
        />
        <>
          {field.state.meta.isTouched && field.state.meta.errors.length ? (
            {field.state.meta.errors.join(",")}
          ) : null}
          {field.state.meta.isValidating ? "Validating..." : null}
        </>
      </>
    );
  }}
  validators={{
    onChange: userSchema.shape.email,
  }}
/>;

However, if I understand the maintainer correctly, this is a bug and the mapping should occur automatically. Nevertheless, it would be very helpful to include a “how-to” in the documentation for using a Zod schema.

Validation can be defined at field or form level as mentioned in the docs so each field needs its validator as of today.
However, we're planning to expand the feature with #656 soon

@mariusraupach tnx! that works! @Balastrong great!

This should be fixed now!


705 | Design HashSet | C++

Title - Adding C++ code for 705. Design HashSet
What will change - Adding solution for leetcode problem 705
Type of Issue -

[x] Adding New Code

Programming Language

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

First time here, can I have this?

@SinisterGaze Hi! This issue is already assigned, however, you can checkout the contributions guideline and create your own issues!


Update install.md

PR types

Others
PR changes

Docs
Describe

Fix typo, Hip->Tip

 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.

Thanks for your cortribution, please sign for CLA thx~!


Add new filters to the extension [WIP]

Description
This PR adds more filters, supported by the Catalog API, to the extension. Very broadly there will be three objectives :

add functioning, multi-select dropdowns for choosing the filters.
modify the current workflow to incorporate the searching by new filters.
Adding the new filters to the "filters" tab of the Options page so that default filters can be set.

Checklist:

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the master branch of the repository.
[ ] My commit messages follow best practices.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

@aldenstpage The main feature of new filters has been completed. Only the checkbox for search setting of "enabling mature content" is left. I will be adding it to the options page.

During the next two days, I will be refactoring the code and making other fixes (which might not be related to the filters feature) because after merging this PR, I am planning to push the update to the extension stores. You can review the PR after I am done with these minor fixes.


Wallet base64 address incorect

Step 1) take raw address string
Step 2) create new instance of Address
Step 3) call ToString with base64 type
Expecting result: correct base64 address string returned
Actual: 1 first and 3 last letters in base64-form of address changed for some reason

As you can see, raw strings are equal but base64 forms differs

just use different formatings, https://docs.tonsdk.net/user-manual/core/address

string raw = address.ToString(AddressType.Raw);

// ex, EQC...2N
string base64Bounceable = address.ToString(AddressType.Base64, new AddressStringifyOptions(true, false, false);

// ex, UQC...BI
string base64NonBounceable = address.ToString(AddressType.Base64, new AddressStringifyOptions(false, false, false);

// ex, kQC...YH
string base64BounceableTestOnly = address.ToString(AddressType.Base64, new AddressStringifyOptions(true, true, false);

// ex, 0QC...vC
string base64NonBounceableTestOnly = address.ToString(AddressType.Base64, new AddressStringifyOptions(false, true, false);```

Got it, thanks


Join Github App Visibility

Problem: Keep having to link people to the join Github app.
Option 1: Create a Slack workflow to send introductory message to new joiners containing useful information, such as a link to the join github app
Option 2: Create a bot to automatically respond to messages asking to join an org.

Link in onboarding docs


Allow override fetch package already vendored

If the package foo was vendored in fetching another pachage bar, I cannot fetch foo after bar.
gb vendor fetch <bar>
gb vendor fetch <foo>

> FATAL command "fetch" failed: <foo> is already vendored

Please allow overriding package already vendored.

Have you tried gb vendor update  ?

yes, but gb vendor update needs an existing dependency.
I need a solution to install a new package, and I want not to mind other packages in order to fetch the package.

Closing as described above. Please feel free to reopen if you disagree


Type exit to exit is not exit actually

rajarshi@rajarshi-X200CA:~/kit$ gitsh
gitsh 0.9
Type :exit to exit
kit facebook! exit
git: 'exit' is not a git command. See 'git --help'.

Did you mean this?
	init
kit facebook!

I am new on gitsh but exit is not working.

You need to use the : prefix: :exit instead of exit. You can also exit by sending an EOF character (ctrl+d)
The colon prefix is there to distinguish gitsh commands, that tell the shell to do something, from Git commands, that perform version control tasks. We didn't want to assume that users wouldn't already have Git aliases with names like set and exit that would conflict with the gitsh commands.
The manual page (man gitsh from your regular Unix shell) is a good source of information on how to use gitsh.
Hope that helps.

Thanks you @georgebrock


📊 pandemics: add avian influenza cases from who

To track avian cases/deaths, we import two datasets:

avian_influenza_ah5n1: This dataset comes from the WHO, via CDC, and estimates cases since 1997.
avian_influenza_ah5n1_kucharski: This dataset comes from an author (Kucharski), and provides estimates on cases and deaths since late 2023.

Notes

Both datasets provide data at the month level, hence we make use of zeroDay attribute. However, instead of setting that one in the garden metadata, we automatically add it in Grapher (via code). This is so users using the dataset from Garden can work with actual dates, and the transformations (date → number of days since zeroDay) are done later in Grapher.
There are reports on a few countries. Countries not present in the dataset are assumed to have had zero cases or deaths.

Thanks, Fi! Nice catch.


Fixed some misleading comment

I realized that deleting the repository before the owner agrees to PR will lose the branch, that's why I have to PR again, sorry

Not a real issue.

Oh... Okay


DynamicYAxis

-Allows monitoring of dynamic yAxis additions and subtractions
-Created a helper function this.removeUnlinkedObjects to help separate
out the code
-Renamed variables in ensureIds to better represent the functions
creating Ids for more than series

@Yoshi9143 great work. I'll get around to merging it soon. The tasks I intend to do are:

[ ] update jsfiddle links to point to master
[ ] factor out common logic for axes and series
[ ] add support for xAxis

I'll hopefully get to these at some point. But if you get there first then I'm happy to merge.

@Yoshi9143 could you give me permissions to write to this fork? https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/

closed as part of #595. Thanks @Yoshi9143 !

Thank you! Sorry I am on vacation and now getting to some work time here so
I wasnt able to give you fork permissions
Thank you so much!
Rishi
On Sun, May 14, 2017 at 8:08 PM, Barry Fitzgerald<EMAIL_ADDRESS>wrote:

Closed #584 https://github.com/pablojim/highcharts-ng/pull/584.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pablojim/highcharts-ng/pull/584#event-1081376540, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJxvVXK1Rucc-AOmuuZVLxLxxA8f7_Oks5r51E8gaJpZM4NDJyS
.


check_number_status returns an empty dict

I'm using Windows 8, Python 3.8.3 (default, Jul  2 2020, 17:30:36) [MSC v.1916 64 bit (AMD64)], Mozilla Firefox 88.0.1and geckodriver 0.29.1, and installed webwhatsapi via pip (pip install webwhatsapi) on May 30, 2021.
Then, I use check_number_status function wthout problems, returning "200" or "400" according to the phone_id status.
Today (Jun 11, 2021) I only get "{}".
Assuming a wsp update on my Android phone could modify something, I downgraded my wsp to version <IP_ADDRESS>, but the problem remains.
My code:
from webwhatsapi import WhatsAPIDriver
driver = WhatsAPIDriver(loadstyles=False)
phone_safe = heremynumber  # Phone number with country code
phone_whatsapp = "{}@c.us".format(phone_safe)
aaa=driver.check_number_status(phone_whatsapp)
aaa.status
Returns:
{}
Any hint?

solution ---> https://github.com/open-wa/wa-automate-nodejs/issues/1748

Just change store discovery for WapQuery, getting wrong reference.
{
id: "WapQuery",
conditions: (module) => (module.default && module.default.queryExist) ? module.default : null
},

Just change store discovery for WapQuery, getting wrong reference.
{
id: "WapQuery",
conditions: (module) => (module.default && module.default.queryExist) ? module.default : null
},

Dear @imamsy, thanks for you answer.
I'm not very expert, so I'm not sure if I do what I must do...
The only place where I can perform such change, which results in correcting the error, was in:
C:\ProgramData\Anaconda3\Lib\site-packages\webwhatsapi-2.0.3-py3.8.egg\webwhatsapi\js\wapi.js    at    line 22,
replacing the line:
{ id: "WapQuery", conditions: (module) => (module.queryExist) ? module : ((module.default && module.default.queryExist) ? module.default : null) },
with that you have given.
Is what I did okay? Was that what you suggested to me?
I'll appreciate your response.


How to install the module named 'fcn'?

Now after I ran python setup.py install, I got the following error:
import torchfcn
Traceback (most recent call last):

  File "<ipython-input-1-c08454750c97>", line 1, in <module>
    import torchfcn

  File "/home/zhang/anaconda2/lib/python2.7/site-packages/torchfcn-0.2-py2.7.egg/torchfcn/__init__.py", line 3, in <module>
    from trainer import Trainer  # NOQA

  File "/home/zhang/anaconda2/lib/python2.7/site-packages/torchfcn-0.2-py2.7.egg/torchfcn/trainer.py", line 6, in <module>
    import fcn

ImportError: No module named fcn****

pip install -r requirements.txt


Please tag this repo as kdb

to help GitHub users find it!

Sorry, I didn't realize this, just added tags.


hey i know nothing about anything help if you can

I dont know anything about code. note 1 bit. I also dont know anything in github, so i dont know if this is the best place to say this, but i get a log in failure when trying to create new database couldnt retrieve t field from login response. I think there might be a fix that ive seen? but i cant understand the jargon so it literally means nothing to me. Im able to log onto the website and thats the only thing I could understand to do. thanks for the help

i do have it linked with my microsoft account. I think ive read through the jargon and am now downlaoding sky py 0.10 which if im correct would help?

v0.10 replaces the old method of logging in under the hood with one that still works, as long as your Skype account is linked to a Microsoft account with an email address.


-r fails when requiring the same file from multiple folders

Take this project for example:
/util.js
/main.js --> require('./util'), require("./a/submodule")
/a/submodule.js --> require('../util')
Run: browserify -r ./util.js main.js > bundle.js
The bundle.js will not run because the resolved dependencies for util.js point to undefined. E.g.
{"./a/submodule.js":1,"./util.js":undefined}
{"../util":undefined}
Now run:browserify -r ./util.js:./util main.js > bundle.js
The bundle.js still won't run but only one of the two resolved dependencies is undefined
{"./a/submodule":1,"./util":"./util"}
{"../util":undefined}
This seems like a bug to me, but I could just be misunderstanding this whole thing. A sample project to reproduce can be found here: https://github.com/marcboscher/browserify-test
Using browserify 7.0.0 on Windows 7
Thanks

Confirming it's fixed for me as of 8.0.3

Isn't it reproducing again in 8.1.3? I have the same problem with including modules from the same directory.


No aliasing feature ?

 What exactly from that query are you missing in Prisma, and what would a possible API for that look like?

The result of thinking again a few weeks later ,may aliasing feature is a bad ideal for type safety.
If still want this feature, look like this?
    prisma.platform.findMany({
      select: {
        _counts: [
          {
            select: {
              applications: { where: { published: true } },
            },
            alias:{
              as:"publishedAppCount",
            }
          }, {
            select: {
              applications: {},
            },
            alias:{
              as:"totalAppCount",
            }
          }
        ],
      },
      take: 100
    });

Finally I think what I wanted is not aliasing , it's case/when/then like this existed issue so I close my issue.


Update greasedLineSimpleMaterial.ts

https://forum.babylonjs.com/t/greasedlinesimplematerial-infnite-loop-in-color-getter/53841
Fixing issue with the color getter

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15648/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15648/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15648/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15648/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15648/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15648/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15648/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15648/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15648/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15648/merge/testResults/webgl2playwright/index.html


Add support for code regions to GDScript

I know its not an urgent issue, but if GDScript will support scrollable regions, like in C#, life become more better.. (and sharp symbol ideally fits in GDScript cuz its already used for comments)
#region Test
....
#endregion

#region in C# is a pretty polarizing feature of the language.  I'm of the boat that thinks it is a bandaid for overly complicated code that should instead be refactored/rethought.  However, I do not entirely mind its presence in general purpose languages, as I'd rather look at poorly written code that has a semblance of documentation than poorly written code with no documentation.
However, GDScript is not a general purpose language, and benefits from keeping things concise.

The only place I see these useful is to delimit code that was generated and should not be edited. But I don't think this use case exists in GDScript.

For those like me who had no clue what regions are: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-region
Note that it's an editor-specific feature (based on a language macro) and not really a language feature per se. Since we already have code folding, I don't see much use case for this. And if it should be scrollable instead of just foldable, then it requires a lot of work on TextEdit to be able to have multiple scrollable areas, for what seems to be a quite non-consensual feature.
I'll leave it up to gather some more opinions, but sounds like a "not wanted" so far.

Yeah, not a good idea really

Those who are not fans of it, you do not have to use it. ;-)
Many of us comming from Unity and C# do use it so would be nice if it can be added when there is time.

Those who are not fans of it, you do not have to use it. ;-) Many of us comming from Unity and C# do use it so would be nice if it can be added when there is time.

for those of you who are stumbling upon this thread when searching if Godot has regions, this is my workaround, maybe you will find it useful if you are coming from C#


np.where has not been implemented

The current version 0.21.0 of Tensorflow.NET does not implement np.where()

@Banyc If possible, you need to get familiar with porting Unit Tests from native from google to Tensorflow.NET as discussed here.
Then if will have the "helicopter" view where are the missing parts and where the community can contribute in complementary way.

@Banyc please help us update the table so future questions on what has and has not implemented is clearly summarised.


Add support for GET and POST /deployments/:id/whitelist API commands

Newly supported API methods:
POST /2016-07/deployments/:id/whitelist
GET /2016-07/deployments/:id/whitelist
We're testing from the code being developed for alphagov/paas-compose-broker#22
Whilst implementing this, we noticed that the API documentation claims that whitelist POST will respond with 200 OK, but in reality it seems to respond with 202 Accepted as we'd expect for async processing.

Odd, thought it had taken. Well, it's merged now.

Thank you!


Makefile:93: *** "No go in PATH: Check dependencies".  Stop.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9.1 linux/amd64
Does this issue reproduce with the latest release?
I'm using the latest release.
What operating system and processor architecture are you using (go env)?
Linux amd64
What did you do?
Try to set up Hyperledger Fabric
@:/src/github.com/hyperledger/fabric$ sudo make dist-clean all
Makefile:93: *** "No go in PATH: Check dependencies".  Stop.
What did you expect to see?

What did you see instead?
Makefile:93: *** "No go in PATH: Check dependencies".  Stop.

This has indeed nothing to do with the Go project.


[Wave Collect] [Guided Setup Stage 2] Add the split expense task type

Problem
As part  of the stage 2 onboarding flow, the user will be able to choose an intent saying they want to chat and split expense with friends.
This task is missing in backend right now
Solution
Add the new task to the guided setup flow and ensure its autocompleted when user splits their bill with someone.

Pr is up but I need to add more tests there

@mountiny this can be closed, right?

Going to close this!


Add Select(Ref)StructCollection

No possible because select function can have a state.
Get(i) could be different of Get(i-1) then Get(i)


tooltip conflict with sublime default function.

when i haven't disabled tooltips( by default) . i find there are some errors, which caused my sublime stuck.
when i disabled it, problem fixed.
	"sv.tooltip" : false, // True to display information in a tooltip (sublime 3072+), false to use the status bar instead
	"sv.tooltip_hide_on_move" : false, // True to hide the tooltip when the mouse move away from the tooltip
	"sv.tooltip_show_module_on_port" : false, // True to include module type and instance when showing tooltip for a port
	"sv.tooltip_show_refs" : false, // True to show reference to module/interface/...
	"sv.tooltip_show_signal_links" : false, // True to show links to driver/reference for signals

You need to be more precise about the issue and provide a way to reproduce it, otherwise I cannot help.

This is a fun one. I'm really frequently getting crashes when I mouse over certain signals. I narrowed it down, such that the following SV, on its own, will reliably crash Sublime when I mouse over or run the "verilog type" command on BAR_A/B/C/D. Interestingly, reducing the indent before the commas in foo_t, or moving the commas onto the prior lines, resolves the crash, as does reducing the number of enumerations in foo_t, moving the list of enumerations for foo_t onto a single line, or removing the range of enum declarations in foo_t.
`
typedef enum logic [4:0]
{ FOO_A[1]
, FOO_B[1]
, FOO_C[1]
, FOO_D[1]
, FOO_E[1]
, FOO_F[1]
, FOO_G[1]
, FOO_H[1]
, FOO_I[1]
, FOO_J[1]
, FOO_K[1]
} foo_t;
typedef enum logic [2:0] {BAR_A, BAR_B, BAR_C, BAR_D} bar_t;
`

Thanks for taking the time to create a simple reproducible example: funny thing is it actually does not even crash on my machine, but it looked a bit slower than normal, and I finally pinpoint that this seems to be due to a regexp running out of stack.
I'll need some time to actually find a proper fix, but I'm on it.

I tested the fix this week, seems to work fine: tell me if it is fine on your side as well


Support decimal crf in sample-encode, encode

Supports using decimal crf in sample-encode & encode subcommands.  Note svt-av1 only supports integer crf. crf-search remains an integer search.
See #83

I've been using this feature and it seems to be working perfectly fine.
I'll test #87 when I have a bit more of time.


Added tools for changing project extents and geolocation.

NOTE: There is currently a bug with undo not updating the IModelProps.
Conflict resolution?

NOTE: There is currently a bug with undo not updating the IModelProps.

I guess TxnManager would need to sniff for changes to the be_Props table, @kabentley?
Related: @AlainRobertAtBentley I suppose if somebody changes the GCS property in the db, then undoes that change, the C++ GCS doesn't get notified?

I guess TxnManager would need to sniff for changes to the be_Props table, @kabentley? Or, the TypeScript functions that perform undo/redo would have to query the IModelProps afterward and see if they had changed.

I guess we should add a table handler for be_Props and have a new TypeScript event when they change. Ugh.

Related: @AlainRobertAtBentley I suppose if somebody changes the GCS property in the db, then undoes that change, the C++ GCS doesn't get notified?
I do not know anything about the undo/TxnManager but currently forcefully removing the property from the database would probably not eliminate the DgnGCS cached instance in the database AppData and retreiving the IModelProps would most probably still return the previous GCS. I think removing the GCS should be through the native backend call UpdateIModelProps() instead. Note also that after calling the frontend UpdateIModelProps() the IModelProps should be fetched anew since properties are interdependant one from another (ECEF is computed from GCS definition is present for example, and GCS definition can be incomplete when setting [id only] then completed [full definition] when refetched.). Probably @swwilson-bsi would no more what goes under the hood in the databasse concerning DgnGCS.


add language setting

It bothers me that there needs to be four related sets of changes to add one setting.
I think overall the settings and configuration logic needs to be move out of the daemon.

Larger structural issues notwithstanding, this LGTM.

Yes, @alexliebowitz PLEASE introduce state to the web app. The web app
should not be setting state in the daemon.
On Wed, Aug 3, 2016 at 3:17 PM, Job Evers‐Meltzer<EMAIL_ADDRESS>wrote:

It bothers me that there needs to be four related sets of changes to
add one setting.
I think overall the settings and configuration logic needs to be
move out of the daemon.

Larger structural issues notwithstanding, this LGTM.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry/pull/108#issuecomment-237342215, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgZVi_WBLdhxnsmAhL0ubNYLft5C_fvks5qcOlGgaJpZM4JaTM8
.

--
Jeremy Kauffman, Founder, LBRY http://lbry.io/
(267) 210-4292
Build LBRY: get https://lbry.io/get, follow https://twitter.com/lbryio,
like https://facebook.com/lbryio

Oh, I see how that was confusing. When I said "settings and configuration should be moved out of the daemon" - I meant out of the LBRYDaemon class.  The logic for that should be delegated to another class.
But, yes, I agree that the UI should avoid using the backend to persist its state.

:D
On Wed, Aug 3, 2016 at 3:53 PM, Job Evers‐Meltzer<EMAIL_ADDRESS>wrote:

Oh, I see how that was confusing. When I said "settings and configuration
should be moved out of the daemon" - I meant out of the LBRYDaemon class.
The logic for that should be delegated to another class.
But, yes, I agree that the UI should avoid using the backend to persist
its state.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry/pull/108#issuecomment-237351984, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgZViBpr74M7GwA4ZY0KMZ7AG_OJf1qks5qcPHVgaJpZM4JaTM8
.

--
Jeremy Kauffman, Founder, LBRY http://lbry.io/
(267) 210-4292
Build LBRY: get https://lbry.io/get, follow https://twitter.com/lbryio,
like https://facebook.com/lbryio


Node.length?

What's this?
https://github.com/guardian/scribe/blob/master/src/plugins/core/inline-elements-mode.js#L12
Nodes do not have a .length property, so most likely that part of the expression simply evaluates as false in every case.
What was this part of the expression intended to accomplish?

My guess would be that this is meant to be a check on the childNodes length.
@OliverJAsh I don't suppose you can recall what this condition was aiming to do can you?

I don't remember writing that! Sorry that's not very helpful…

Well, the comment says "If the node is a non-empty element or has content", so that explains the intent. Except this wouldn't work, and one wonders if it should work that way or not?
I'd suggest de-obfuscating that curious use of Array.indexOf and the binary ~ operator as well.
So probably:
        if (treeWalker.currentNode.nodeName === "BR" || treeWalker.currentNode.children > 0) {
          return true; // If the node is a non-empty element or has content
        }

(probably this function should be given a name though, and moved into node.js with the other helpers, and have a test.)


unban rakv3

Description of the issue
rak is banned
Proposed solution
unban rak
Additional comments
as jammy said, #computer-science just isnt the same without the regular doses of APL
also in general rak is cool
unban him pls

BEANO before you close this can you please merge my PR because it actually isn't bad
I'm not jack
https://github.com/CyberDiscovery/cyberdisc-bot/pull/610

BEANO before you close this can you please merge my PR because it actually isn't bad
I'm not jack
https://github.com/CyberDiscovery/cyberdisc-bot/pull/610

I'd like to share my support for this issue. I really miss Rak as a great person to have a chat with in general.

I'd like to share my support for this issue. I really miss Rak as a great person to have a chat with in general.

quack quack unban rak

quack quack unban rak

i don't know rak that well but he also seemed kinda funny in #general so i would support bringing him bacc

i don't know rak that well but he also seemed kinda funny in #general so i would support bringing him bacc

quack quack unban rak

pls can we have Rak back, I miss him

I miss him too, he's clever and some of the APL stuff fascinates me


[CLI] Add support for cancelling training runs

Can it work now?

not yet

@bourdakos1 is there any way to cancel training.
Don't know why but my training was running since last 5 days and not yet completed.
Whenever i check cacli progress model-id it is very slow and only ~1968 / 200000 steps are showing.

Tried with bx ml cancel training-runs {model-id}.
It works.

I’m working on rewriting the CLI in go, It should be a first class feature when released

implemented in new golang CLI


Wrong config file path for hermes config.tmol

Summary of Bug
in previous step the file is copied directly under .hermes  folder "cp config.toml $HOME/.hermes"
but doing view using config directory path nano $HOME/.hermes/config/config.toml
Steps to Reproduce
Steps to reproduce the behavior:

...

Thank you, so what is the correct path?

I just saw your PR, I commited it here because he just refactored the docs:
https://github.com/osmosis-labs/docs/commit/fa3a79169136f9244da839966da0ceae48f80a3d
tysm


skywalking springcloud gateway plugin not suppot springcloud greenwish sr4

Bug

Which version of SkyWalking, OS and JRE?
skywalking version 6.5
springcloud version greenwish SR4   (Spring Cloud Gateway 2.1.4.RELEASE)
springboot version2.1.10.release

I can not got trace form springcloud gateway  in skywalking.
other springmvc app I can got trace In these versions
when I  use spring  springcloud version greenwish SR3(Spring Cloud Gateway 2.1.3.RELEASE
) 。Ｉ can got trace  for Spring Cloud Gateway  in Skywalking .
There are also some bugs in skywalking springcloud gateway plugin  from  springcloud sr3
I write customer filter for gateway.  In filter  do a spring feign method  call in a mono
`
public GatewayFilter apply(Config config) {
return (exchange, chain) -> {
        Mono<Mono<Void>> objectMono = Mono.create(monoSink -> {
            executor.execute(new Runnable() {
                @Override
                public void run() {

                    CgiResult<JSONObject> cgiResult = null;
                    try {
                        cgiResult = iIotimTicketValidateService.validate(token, iotimTicket, din);
                    } catch (Exception e) {
                        logger.error("feign error:", e);
                    }

                    if (cgiResult != null && cgiResult.getErrCode() == 0) {

                        monoSink.success(chain.filter(exchange));
                    } else {
                        monoSink.success(unauthorizedResponse(exchange, cgiResult.getErrCode(), cgiResult == null ? "feign error" : cgiResult.getErrMsg()));
                    }
                }
            });
        });
        return objectMono;

}
This  feign call not seen in one trace chain .
my call chain is
user ->gateway->feigncall_In_mono->feignRet->gatewayRouterToAppCall

Gateway is a very complex scenario, @zhaoyuguang @ascrutae Please take a look.
@seifeHu Please try to debug first.


build(devtools): Fix packageVersion.ts discrepency

Version was not fully updated when package was added in #15490.
Updated via npm run build in the package directory.

Is this file used in this project? If so, for what purpose?

Is this file used in this project? If so, for what purpose?

Not to my knowledge. It isn't totally clear to me which packages need this step and which don't. Do we have guidance on that?

This is an improvement, though we really should consider if we need this and how to prevent this issue in the future.


Consider: Reduce version # duplication in Dockerfiles

Currently our Dockerfiles in ci/... contain blocks such as:
https://github.com/googleapis/google-cloud-cpp/blob/a442ac1c5823a2ac6244102a5d8a7c85f4890c30/ci/kokoro/docker/Dockerfile.fedora-install#L66-L75
This is fine and works, but when we update our version of the cpp-cmakefiles package, we need to update the version number in 3 separate places. And the version has a slightly different format in the various places, so doing the replacement w/ a regex is not trivial.
Proposal
We may be able to rewrite these docker commands to only use the version number in a single location. For example, we can directly untar the output of the wget, bypassing the need to name the tar.gz file a second time. We can also use tar's --transform= flag to remove the version number from the extracted files, so that we can simply cd cpp-cmakefiles/ after extracting. So something like the following should work:
WORKDIR /var/tmp/build
RUN wget -q -O - https://github.com/googleapis/cpp-cmakefiles/archive/v0.8.0.tar.gz | \
      tar -zxf - -transform='s,^[^/]\+/\?,cpp-cmakefiles/,'  # <-- NEW
    cd cpp-cmakefiles                                        # <-- NO VERSION
    cmake \
      -DBUILD_SHARED_LIBS=YES \
      -H. -Bcmake-out && \
    cmake --build cmake-out --target install -- -j ${NCPU} && \
    ldconfig && \
    cd /var/tmp && rm -fr build

We could probably do something similar for more than just the cpp-cmakefiles repo.
I'm sure there are other ways (besides --transform=) to extract the tar into an unversioned directory of a statically known name. Those options would probably work fine too.

An alternative option is to automatically generate these Dockerfiles, like we do for ci/kokoro/install/Dockerfile.*.

I'm sure there are other ways

Perhaps something like ...
mkdir cpp-cmakefiles
cd cpp-cmakefiles
wget ... | tar -zxf - --strip-components=1
cmake ...


Don't print line number every time smoothie#middle() is called

I don't know why every time I pressed zz line number was displayed
Since it was a bit annoying I disabled it

Hey @xeluxee,
Sorry for the very late reply. I didn't know anyone else used this besides myself :laughing:. I'll merge this one in. But I recommend checking out https://github.com/psliwka/vim-smoothie. He's implemented zz zt zb, in there and I think he's done some good stuff over there as well.

I didn't know anyone else used this besides myself

As this repo has three stars I'm not the only one using it :smile:

But I recommend checking out https://github.com/psliwka/vim-smoothie (I originally forked off of that). He's implemented zz zt zb, in there and I think he's done some other good stuff over there as well.

Scrolling for zt, zz, zb has been implemented some months ago. But it doesn't work well with foldings (see https://github.com/psliwka/vim-smoothie/issues/40), so I'll keep using this for a while.


List structure

Add list layout
Add javascript functionality
Install webpacks
Run linters for code errors

@Tafloninno, linters are failing. Will you do the fixing?


doc: clean up README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
537

Relevant Lines:
537

💛  - Coveralls


Why remove the root's trailing slash when wantPustState on IE8?

Example:
Backbone.history.start({ pushState: true, root: '/root/' })

The browser is IE8 (no pushState)
Our server will force a trailing slash, a request of /root will receive a redirection to /root/
Visit /root/aa/bb

Due to this commit d550b8b , an replaced url will be /root#aa/bb, then the server returns a redirection to /root/, which lead to an additional request, and at the same time the hash will be lost. The /root/aa/bb can't be reached.
I've read the #2656 and #3443. I'm thinking that should the tailing slash here also be optional ? Which means:
Backbone.history.start({ pushState: true, root: '/root/' }) // /root/#aa/bb
Backbone.history.start({ pushState: true, root: '/root' }) // /root#aa/bb

+1

ping @akre54  maybe this can be closed due to https://github.com/jashkenas/backbone/pull/4008


How to change the style of the profane words?

Trying to figure out how to make the profane words turn red instead of replacing them with *, but no luck. Ideas?

good question. I'd have to take a look.

@glennax will the latest PR do what you're asking?
Take a look at the demo page

@ChaseFlorell Thank you for getting back to me! However, what i would like to do is only highlight all the individual profane words found in the text. Would it be possible?

I just published a version that adds an array of bad words to the callback (see example #5 of the demo page).
Use that callback to string.replace the words with styled ones.

Try this fiddle.
https://jsfiddle.net/rockinthesixstring/Lqruyncw/


Error on startup

Describe the issue
Error appears on start up (during loading flash screen):
Microsoft Visual C++ Runtime Library
Assertion Failed!
Program: C:\Program Files\RaptoreumCore\raptoreum-qt.exe
File: evo/evodb.cpp
Line: 71
Expression: hashBestBlock == hashBlockIndex
Abort/Retry/Ignore
Selecting 'Ignore' seems to allow the wallet to start.
Can you reliably reproduce the issue? Yes
If so, please list the steps to reproduce below:

Start Raptoreum core
Wait
Error appears

Expected behaviour
Tell us what should happen.
Raptoreum should start without errors.
Actual behaviour
Tell us what happens instead
Raptoreum should started with errors.
Screenshots.

What version of Raptoreum Core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Machine specs:

OS: Windows 10 21H1 19043.1348
CPU: 5900X
RAM: 64GB 3600 C16
Disk size: 2TB
Disk Type (HD/SDD): SSD

Any extra information that might be useful in the debugging process.
Wallet sync has not completed yet.

Fixed on current testnet build if it is the same corruption error. Temp fix is:
Download: https://github.com/Raptor3um/raptoreum/releases/download/<IP_ADDRESS>/bootstrap.zip

Stop wallet or daemon
In your wallets data directory delete folders:
-- blocks
-- chainstate
-- evodb
-- llmq
Unzip bootstrap and copy folder into your data directory
Start wallet

@Bigpiggy01 The temp fixed seemed to clear things up so I imagine it's the same error. Thanks.


Require python 3.6 for host conda-forge host build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

@tboggs I am +1 to merge this. We can then rebase #16 and take it from there.

Are there any blockers here? Would be nice to have a new version of spectral on conda-forge!


Add ExpressRouteServiceProvider and rename operationStatus

Add specs for ListExpressRouteServiceProvider
Rename OperationStatus to NetworkOperationStatus

Hi @DeepakRajendranMsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


Create new UI for the home page

If you are interested to work in this issue then write assign me in the comment

Hey i would like to work on it

Go ahead @Sahad-09

Hey! I would also like to work on it.

I would Like to create a new UI for Product Launching Website.

I would Like to create a new UI for Product Launching Website.

Create new issue I will assign it to you

Hey! I would also like to work on it.

Go ahead @Shubhodaya

I would Like to create a new UI for Product Launching Website.

Create a new issue I will assign that to you

CreatedThe issue.


Calling train in SavedModelEstimator gives ValueError: At least two variables have the same name

System information

TensorFlow version (use command below): 1.12.0-rc2-3-ga6d8ffae09 1.12.0
Python version: Python 3.6.9

Describe the current behavior

Defining a model using tensorflow.keras
Converting the compiled model to estimator
Training estimator using train_and_evaluate
Export all saved models for  "TRAIN", "EVAL" and "PREDICT"

When I create a SavedModelEstimator from the previous exported data, I am able to call evaluate and predict successfully. However, if I call the method train I get an error "ValueError: At least two variables have the same name: dense_1/bias/Adam)".
I can warm-start sucessfully if I change the line in _get_grouped_variables to: https://github.com/tensorflow/tensorflow/blob/9c52e7ce02532c22a79ae7139f37c663add4c90f/tensorflow/python/training/warm_starting_util.py#L349
ops.GraphKeys.TRAINABLE_VARIABLES, scope=v)
Code to reproduce the issue
import tensorflow as tf
from tensorflow.keras.layers import Input, Dense, Dropout
from tensorflow.keras.models import Model
from tensorflow.keras.estimator import model_to_estimator
import keras.backend as K
import numpy as np
import os

def model_fn():
    # 10 features
    input_layer = Input(shape=(10,), name="inputs", dtype=tf.float32)
    dense_1 = Dense(units=10, activation="relu", name="dense_1")(input_layer)
    dense_2 = Dense(units=1, activation="linear", name="outputs",
                    dtype=tf.float32)(dense_1)
    model = Model(inputs=input_layer, outputs=dense_2)
    model.compile(optimizer=tf.train.AdamOptimizer(),
                  loss="mse")
    return model

def synthetic_input_fn(num_examples, num_features):
    # dummy data
    return tf.data.Dataset.from_tensor_slices(({"inputs": np.random.random((num_examples, num_features))}, np.random.randint(10, size=num_examples))) \
        .shuffle(512) \
        .batch(32) \
        .repeat(10)

if __name__ == "__main__":

    MODEL_DIR = "./model"
    SAVED_MODEL_DIR = os.path.join(MODEL_DIR, "saved")

    def cust_train_input_fn():
        return synthetic_input_fn(1000, 10)

    def cust_eval_input_fn():
        return synthetic_input_fn(100, 10)

    tf.logging.set_verbosity(tf.logging.INFO)

    # define model and convert to estimator
    model = model_fn()
    estimator = model_to_estimator(
        keras_model=model,
        model_dir=MODEL_DIR
    )

    train_spec = tf.estimator.TrainSpec(input_fn=cust_train_input_fn)
    eval_spec = tf.estimator.EvalSpec(input_fn=cust_eval_input_fn)

    # train and evaluate dummy model
    tf.estimator.train_and_evaluate(
        estimator=estimator,
        train_spec=train_spec,
        eval_spec=eval_spec
    )

    # export all modes
    feature_spec = {"inputs": tf.placeholder(tf.float64, (None, 10))}

    label_spec = tf.placeholder(dtype=tf.int64)

    serving_fn = tf.estimator.export.build_raw_serving_input_receiver_fn(feature_spec)
    training_fn = tf.contrib.estimator.build_raw_supervised_input_receiver_fn(feature_spec, label_spec)

    rcrv_fn_map = {
        tf.estimator.ModeKeys.TRAIN: training_fn,
        tf.estimator.ModeKeys.EVAL: training_fn,
        tf.estimator.ModeKeys.PREDICT: serving_fn
    }

    tf.contrib.estimator.export_all_saved_models(
        estimator,
        export_dir_base=SAVED_MODEL_DIR,
        input_receiver_fn_map=rcrv_fn_map
    )

    tf.keras.backend.clear_session()

    saved_estimator = tf.contrib.estimator.SavedModelEstimator(os.path.join(SAVED_MODEL_DIR, os.listdir(SAVED_MODEL_DIR)[0]))
    saved_estimator.train(cust_train_input_fn)

Other info / logs
Using TensorFlow backend.
INFO:tensorflow:Using default config.
INFO:tensorflow:Using the Keras model provided.
2019-10-29 14:26:59.280066: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
INFO:tensorflow:Using config: {'_model_dir': './model', '_tf_random_seed': None, '_save_summary_steps': 100, '_save_checkpoints_steps': None, '_save_checkpoints_secs': 600, '_session_config': allow_soft_placement: true
graph_options {
rewrite_options {
meta_optimizer_iterations: ONE
}
}
, '_keep_checkpoint_max': 5, '_keep_checkpoint_every_n_hours': 10000, '_log_step_count_steps': 100, '_train_distribute': None, '_device_fn': None, '_protocol': None, '_eval_distribute': None, '_experimental_distribute': None, '_service': None, '_cluster_spec': <tensorflow.python.training.server_lib.ClusterSpec object at 0x62b766be0>, '_task_type': 'worker', '_task_id': 0, '_global_id_in_cluster': 0, '_master': '', '_evaluation_master': '', '_is_chief': True, '_num_ps_replicas': 0, '_num_worker_replicas': 1}
INFO:tensorflow:Not using Distribute Coordinator.
INFO:tensorflow:Running training and evaluation locally (non-distributed).
INFO:tensorflow:Start train and evaluate loop. The evaluate will happen after every checkpoint. Checkpoint frequency is determined based on RunConfig arguments: save_checkpoints_steps None or save_checkpoints_secs 600.
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Warm-starting with WarmStartSettings: WarmStartSettings(ckpt_to_initialize_from='./model/keras/keras_model.ckpt', vars_to_warm_start='.*', var_name_to_vocab_info={}, var_name_to_prev_var_name={})
INFO:tensorflow:Warm-starting from: ('./model/keras/keras_model.ckpt',)
INFO:tensorflow:Warm-starting variable: dense_1/kernel; prev_var_name: Unchanged
INFO:tensorflow:Warm-starting variable: dense_1/bias; prev_var_name: Unchanged
INFO:tensorflow:Warm-starting variable: outputs/kernel; prev_var_name: Unchanged
INFO:tensorflow:Warm-starting variable: outputs/bias; prev_var_name: Unchanged
INFO:tensorflow:Create CheckpointSaverHook.
INFO:tensorflow:Graph was finalized.
INFO:tensorflow:Running local_init_op.
INFO:tensorflow:Done running local_init_op.
INFO:tensorflow:Saving checkpoints for 0 into ./model/model.ckpt.
INFO:tensorflow:loss = 32.57418, step = 1
INFO:tensorflow:global_step/sec: 1201.8
INFO:tensorflow:loss = 24.11268, step = 101 (0.083 sec)
INFO:tensorflow:global_step/sec: 1799.1
INFO:tensorflow:loss = 12.514932, step = 201 (0.056 sec)
INFO:tensorflow:global_step/sec: 1810.48
INFO:tensorflow:loss = 9.915621, step = 301 (0.055 sec)
INFO:tensorflow:Saving checkpoints for 320 into ./model/model.ckpt.
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Starting evaluation at 2019-10-29-14:27:00
INFO:tensorflow:Graph was finalized.
INFO:tensorflow:Restoring parameters from ./model/model.ckpt-320
INFO:tensorflow:Running local_init_op.
INFO:tensorflow:Done running local_init_op.
INFO:tensorflow:Evaluation [10/100]
INFO:tensorflow:Evaluation [20/100]
INFO:tensorflow:Evaluation [30/100]
INFO:tensorflow:Evaluation [40/100]
INFO:tensorflow:Finished evaluation at 2019-10-29-14:27:00
INFO:tensorflow:Saving dict for global step 320: global_step = 320, loss = 8.093195
INFO:tensorflow:Saving 'checkpoint_path' summary for global step 320: ./model/model.ckpt-320
INFO:tensorflow:Loss for final step: 10.114872.
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Signatures INCLUDED in export for Classify: None
INFO:tensorflow:Signatures INCLUDED in export for Regress: None
INFO:tensorflow:Signatures INCLUDED in export for Predict: None
INFO:tensorflow:Signatures INCLUDED in export for Train: ['train']
INFO:tensorflow:Signatures INCLUDED in export for Eval: None
WARNING:tensorflow:Export includes no default signature!
INFO:tensorflow:Restoring parameters from ./model/model.ckpt-320
WARNING:tensorflow:From /anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py:1044: calling SavedModelBuilder.add_meta_graph_and_variables (from tensorflow.python.saved_model.builder_impl) with legacy_init_op is deprecated and will be removed in a future version.
Instructions for updating:
Pass your op to the equivalent parameter main_op instead.
INFO:tensorflow:Assets added to graph.
INFO:tensorflow:No assets to write.
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Signatures INCLUDED in export for Classify: None
INFO:tensorflow:Signatures INCLUDED in export for Regress: None
INFO:tensorflow:Signatures INCLUDED in export for Predict: None
INFO:tensorflow:Signatures INCLUDED in export for Train: None
INFO:tensorflow:Signatures INCLUDED in export for Eval: ['eval']
WARNING:tensorflow:Export includes no default signature!
INFO:tensorflow:Restoring parameters from ./model/model.ckpt-320
WARNING:tensorflow:From /anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py:1046: calling SavedModelBuilder.add_meta_graph (from tensorflow.python.saved_model.builder_impl) with legacy_init_op is deprecated and will be removed in a future version.
Instructions for updating:
Pass your op to the equivalent parameter main_op instead.
INFO:tensorflow:Assets added to graph.
INFO:tensorflow:No assets to write.
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Signatures INCLUDED in export for Classify: None
INFO:tensorflow:Signatures INCLUDED in export for Regress: None
INFO:tensorflow:Signatures INCLUDED in export for Predict: ['serving_default']
INFO:tensorflow:Signatures INCLUDED in export for Train: None
INFO:tensorflow:Signatures INCLUDED in export for Eval: None
INFO:tensorflow:Restoring parameters from ./model/model.ckpt-320
INFO:tensorflow:Assets added to graph.
INFO:tensorflow:No assets to write.
INFO:tensorflow:SavedModel written to: ./model/saved/temp-b'1572359223'/saved_model.pb
INFO:tensorflow:Using default config.
WARNING:tensorflow:Using temporary folder as model directory: /var/folders/8s/tjdwdq296s5fdljp3p6jd9z40000gn/T/tmp7c0vhh49
INFO:tensorflow:Using config: {'_model_dir': '/var/folders/8s/tjdwdq296s5fdljp3p6jd9z40000gn/T/tmp7c0vhh49', '_tf_random_seed': None, '_save_summary_steps': 100, '_save_checkpoints_steps': None, '_save_checkpoints_secs': 600, '_session_config': allow_soft_placement: true
graph_options {
rewrite_options {
meta_optimizer_iterations: ONE
}
}
, '_keep_checkpoint_max': 5, '_keep_checkpoint_every_n_hours': 10000, '_log_step_count_steps': 100, '_train_distribute': None, '_device_fn': None, '_protocol': None, '_eval_distribute': None, '_experimental_distribute': None, '_service': None, '_cluster_spec': <tensorflow.python.training.server_lib.ClusterSpec object at 0x1c316e6208>, '_task_type': 'worker', '_task_id': 0, '_global_id_in_cluster': 0, '_master': '', '_evaluation_master': '', '_is_chief': True, '_num_ps_replicas': 0, '_num_worker_replicas': 1}
INFO:tensorflow:Checking available modes for SavedModelEstimator.
INFO:tensorflow:Available modes for Estimator: ['train', 'eval', 'infer']
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Done calling model_fn.
INFO:tensorflow:Warm-starting with WarmStartSettings: WarmStartSettings(ckpt_to_initialize_from='./model/saved/1572359223/variables/variables', vars_to_warm_start=['dense_1/bias', 'dense_1/bias/Adam', 'dense_1/bias/Adam_1', 'dense_1/kernel', 'dense_1/kernel/Adam', 'dense_1/kernel/Adam_1', 'global_step', 'outputs/bias', 'outputs/bias/Adam', 'outputs/bias/Adam_1', 'outputs/kernel', 'outputs/kernel/Adam', 'outputs/kernel/Adam_1', 'training/TFOptimizer/beta1_power', 'training/TFOptimizer/beta2_power'], var_name_to_vocab_info={}, var_name_to_prev_var_name={})
INFO:tensorflow:Warm-starting from: ('./model/saved/1572359223/variables/variables',)
INFO:tensorflow:Warm-starting variable: dense_1/bias; prev_var_name: Unchanged
INFO:tensorflow:Warm-starting variable: dense_1/bias/Adam; prev_var_name: Unchanged
Traceback (most recent call last):
File "main.py", line 83, in
saved_estimator.train(cust_train_input_fn)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py", line 354, in train
loss = self._train_model(input_fn, hooks, saving_listeners)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py", line 1207, in _train_model
return self._train_model_default(input_fn, hooks, saving_listeners)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py", line 1241, in _train_model_default
saving_listeners)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/estimator/estimator.py", line 1360, in _train_with_estimator_spec
warm_starting_util.warm_start(*self._warm_start_settings)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/training/warm_starting_util.py", line 463, in warm_start
_warm_start_var(variable, ckpt_to_initialize_from, prev_var_name)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/training/warm_starting_util.py", line 170, in _warm_start_var
current_var_name = _infer_var_name(var)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/training/warm_starting_util.py", line 142, in _infer_var_name
name_to_var_dict = saver.BaseSaverBuilder.OpListToDict(var)
File "/anaconda3/envs/tf-abalone/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 572, in OpListToDict
name)
ValueError: At least two variables have the same name: dense_1/bias/Adam

Issue replicating for TF 1.12,kindly find the gist of colab.Thanks!

Forgot to mention that there is an issue when running the same code in TensorFlow 1.13, 1.14 and 1.15, in the SavedModelEstimator call to train, raising:
ValueError: Dimension 0 in both shapes must be equal, but are 0 and 1. Shapes are [0] and [1]. for 'loss/outputs_loss/weighted_loss/broadcast_weights/assert_broadcastable/is_valid_shape/has_valid_nonscalar_shape/has_invalid_dims/DenseToDenseSetOperation' (op: 'DenseToDenseSetOperation') with input shapes: [0,1], [1,2].
Should this be a new issue?

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.