Getting = Cannot read property 'unlockWallet' of null when trying to connect to my lnd note

Description
I have setup a btcpay server with lnd and ride the lighting.
i have funded the onchain and without establishing and funding any new channels for outbound, I am trying to connect zap.

Expected Behavior

Without performing the same workflow before, it was supposed to connect zap wallet to lnd without asking for wallet password as the video below.
https://www.youtube.com/watch?v=yBQX0CFnAh4
Actual Behavior

Zap asks for wallet password and when assigning a new password, it returns the following error : Cannot read property 'unlockWallet' of null
I see nothing related on my lnd logs
Possible Fix
No idea, just reporting

Steps to Reproduce

fresh lnd node
try to connect zap

Context

Your Environment

Zap version: can't find the version, it has been updated with auto-update right after I install it.

Device: mac os x

LND Version: Version: 0.13.3-beta commit=basedon-v0.13.3-beta-fresh-btcpay

I'm seeing the same issue on Linux (via the AppImage binary).

I see the error when trying to connect to a lnd server which is already unlocked. When the server is not yet unlocked, then the zap desktop connects after correctly unlocking it. I think that there is a related problem, where the app just shows a blank screen if it is restarted while lnd is unlocked.

Hi, please try with the latest version of the app - 0.7.5 https://github.com/LN-Zap/zap-desktop/releases/tag/v0.7.5-beta

The issue remains for me.

as @joshuanapoli, this happens when the lnd node is already unlocked. Indeed if you restart it and it's in lock state (waiting fon lncli unlock) zap will ask for the password and successfully unlock it, then it allows you to open the wallet.
Please fix it :)

This is probably the same as issue #3774. Zap for Linux/Windows cannot connect to LND v0.14.1-beta unless the wallet is locked in LND (which will not be true if the server is running).  Starting LND, leaving it locked, starting Zap and unlocking the wallet is a cumbersome workaround.  This is true when using Zap v0.7.5-beta for Linux.  The iphone app, which was previously connected still works however.

I concur with @kshartman and arrived at same conclusion.. I am having the same issue as the OP of this bug and also have the same LND server version and have tested this across multiple versions upto latest zap desktop client of v0.7.5-beta.exe (windows)
The strange thing is that Zap wallet is still working fine on my Android handset. Even after update to latest UmbrelOS my Android Zap Wallet works fine. Its The desktop version which throws the error "Cannot real property 'unlockWallet' of null"
This "error/Bug" has changed from the original issue that Zap Desktop had which just left the GUI in a "blank" state partially loaded GUI.
-- The suggested workaround is not really feasible when running a 24/7/365 BTC node.
Good Luck.

I have the same issue as described by other users above. I get the Cannot read property 'unlockWallet' of null after inputting my wallet password.
Environment: Ubuntu 20.04
Version: Zap 0.7.5 Beta (Zap-linux-x86_64-v0.7.5-beta.AppImage)

I have the same issue as described by other users above. I get the Cannot read property 'unlockWallet' of null after inputting my wallet password.
Environment: Ubuntu 20.04
Version: Zap 0.7.5 Beta (Zap-linux-x86_64-v0.7.5-beta.AppImage)

@mrfelton could you please advice about this issue? Currently zap-desktop on linux is not usable with the last version of lnd.

I did some digging and the error comes from here: https://github.com/LN-Zap/node-lnd-grpc/blob/master/src/services/walletUnlocker.js#L24

Ok, it's 5 AM but this job had to be done.
I've found the issue and submitted the PR. Once @mrfelton merge and integrate this new version of node-lnd-grpc it will fix this issue.
It's time to sleep now :P

Was this solved? I have 0.7.6 installed on my mac and still see this problem.

@Javihache I've 0.7.6 installed on my Linux and I have no issues connecting to my lnd node anymore. I will try with my old mac

@Javihache @hirishh I'm running 0.7.6-beta on Mac OS and getting the same issue

Seems the error was a red herring, I switched from 'server.local' to '192.168.x.x' in the connection settings and it unlocks fine with lnd unlocked

Still get the error on linux with btcpay


Send logs from daemon into python extension

For #7242

Log (almost) everything from daemon in python extension
Log execution of code in daemon the same way we log process execution (so  we can see what's going on in output panel).

Codecov Report

Merging #8588 into master will decrease coverage by 0.17%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##           master    #8588      +/-   ##
==========================================
- Coverage   59.43%   59.26%   -0.18%
==========================================
  Files         512      512
  Lines       23757    23769      +12
  Branches     3842     3842
==========================================
- Hits        14120    14086      -34
- Misses       8713     8764      +51
+ Partials      924      919       -5

Impacted Files
Coverage Δ

...rc/client/common/process/pythonExecutionFactory.ts
93.54% <100%> (+0.1%)
:arrow_up:

src/client/common/process/pythonDaemon.ts
23.52% <100%> (+0.97%)
:arrow_up:

src/client/common/process/pythonDaemonPool.ts
38.7% <22.22%> (-34.57%)
:arrow_down:

Continue to review full report at Codecov.

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


[Code reviews] Nits to fix and refactoring

The code reviews section requires some copy-editing and other minor fixes. The items collected here are based on the snapshot of commit b1497e6. This is not exhaustive list.
Blocking PR: #727
Generally:

Improve language in general
Slashes have whitespaces surrounding them and slashes in general can be removed by rephrasing

FAQ

Code reviews vs. PRs: Add a covering note before a table
FAQ titles inconsistent with question marks
“completed on their own” – rephrase
“…complex PR on GitHub” – not GitHub specific, remove
Explain “mob” when mentioned the first time

Join the three last (pair/mob) questions if sensible

Evidence and measures

Folder not required after #782

@tompaana I am not sure that's what you meant in this issue and I might be suggesting something which is too large or doesn't fit. LMK what you think:
I think it is missing an 'intro' instead of the 'code reviews' section, maybe start with the 5 whs:
Why do we need code reviews?
Who will do a code review?
What will be reviewed?
When will it be reviewed?
Where it will be reviewed?? (not sure we need this one 😛 )
and in the different sections we can dive into the topics more.
For example the 'Inclusion in code review' can be the 'who' section. The  'Pull requests' section can be the 'what'.
A new addition suggestion:
I think each person have different things they look at when they do review. I would actually add a section of different people saying what they look at in a code review, where do they start and main points.

@shiranr I did write this issue (and others) in a hurry and it shows, sorry about that. This issue was meant to collect all small things that aren't right: bad grammar, typos, bad links etc. Not a good practice to have issues like this, but I think we needed this anyway.
You raise excellent points! A good "intro" is indeed something we want, and we have another issue for it: #781 (Another piece of my slobby, hastily done work.) I also think it is important to provide good motivation for why we do code reviews - which I also think should be backed up with data (see #783).
I'm not against restructuring the sections at all. Let's just make a good plan before we execute.
As to your new suggestion: Sounds like D&I focused theme that goes well along with the CSE culture. I'm terribly bad at writing content around that topic. You could work together with @madossan01 who has created couple of related issue for code reviews section.

Thanks @tompaana for clarifying. Sounds good.
I will take a look again and see if I can find small issues and add them to this ticket.
If there's anything I can take once we are done with this one, please LMK. :)

In addition to what you said:
long sentences should be shortened for example:
in the PR section, fix alignment of General process -> section 2


Unique identifier for each oplog operation

Hi,
We're sending the oplog to a kafka stream that will be sanitized then sent .
We'd like to identify each oplog operation to be sure to not have duplicates of the operations. (we'd like to reprocess the stream if needed)
Here what give the oplog in the shell
> db.oplog.rs.find()
{
  "ts" : Timestamp(1395663575, 1),
  "h" : NumberLong("-5872498803080442915"),
  "v" : 2,
  "op" : "i",
  "ns" : "wiktory.items",
  "o" : {
    "_id" : ObjectId("533022d70d7e2c31d4490d22"),
    "author" : "JRR Hartley",
    "title" : "Flyfishing"
    }
}

It seems like this the unique identifier is the "h" field. I was wondering if it exists a way to get this value? Maybe I miss something in the options?
Thank you!

Mongo-connector does not replicate the "h" field but the "ts" field is also unique and is sent to the DocManagers. If you're writing your own DocManager implementation the "ts" field is given as the timestamp argument. See https://github.com/mongodb-labs/mongo-connector/wiki/Writing-Your-Own-DocManager.
Does this answer your question?

It does! thank you @sha1sum  :)


Expose createReducer utility?

What Lua does have are great dictionaries, so it's possible we should expose a method like this Redux library called 'redux-create-reducer'.
In short:
local reducer = createReducer(initialState, {
    [Action.SetUsername] = function(state, action) {
        -- do something to create a new state
        return state
    }
})

Lua doesn't have pattern matching, so matching on a bunch of actions gives us a bunch of chained if statements that are kind of painful.

That's true if you're applying the Redux philosophy of using strings for action types, which you kind of have to do in JavaScript because associative arrays in JavaScript only supported string keys for the longest time.
Since Lua's great dictionaries support using objects as keys, I don't use string values for action.type; I use function references that reference action creators.  Each reducer is then a simple dictionary that maps each action creator to its appropriate reducer function:
function createReducerForDriving()
  local actions = getActionCreatorsForDriving()
  local reducerFunctions = getReducerFunctionsForDriving()

  self.handlers = {}
  self.handlers[actions.increasedAcceleration] = reducerFunctions.increasedAcceleration
  self.handlers[actions.decreasedAcceleration] = reducerFunctions.decreasedAcceleration
  self.handlers[actions.appliedBrake] = reducerFunction.appliedBrake

  local consoleActions = getActionCreatorsForDrivingViaConsole()
  self.handlers[consoleActions.playerQuitGame] = reducerFunction.appliedBrake

  return function(state, action)
    local handler = self.handlers[action.type]

    if not handler then
      return state
    end

    return handler(state, action)
  end
end

Each action creator appends its own human-readable string name to the _name property of the returned action, for debugging purposes.


How to use /grieflogger lookup

Minecraft : 1.20.1
Fabric: 0.15.6
Mod Version: 1.1.2
Hello,
I'm trying to understand how to use /grieflogger lookup or /grieflogger page, I always get no result.
In my example, I wanted to see which players have interacted with a lever. That's why I tried this command without success. Is it even possible to display something like this?
/grieflogger lookup action.add_item user.Robotter112
GriefLogger - No results found.

Please specify a Radius. The radius is 0 by default.


 I will keep trying though.

Oops sorry I tried databricks not dataproc

OK I figured it out.  Dataproc actually runs the tests distributed, and there is ambiguity in the the floating point sort.  100.0 - something really close to 0 is still 100.0.  Because of this the output, although still valid, varied a lot. I'll update the test so there is no ambiguity.


Performance: nvm use default slow, slows down shell startup (nvm.sh)

. ~/.nvm/nvm.sh adds about half a second to shell startup. The main culprits seem to be nvm ls default and nvm use default - commenting them out drops the timing reported by time . ~/.nvm/nvm.sh to near-zero.
I wonder if we can speed those up, or replace them with a cheaper operation for shell startup?

OK, I think I identified most of the places that cause slowdown - got it down to .05 seconds by putting in some hacks. I'm not suggesting you apply these hacks, but just wanted to demonstrate that should be possible in principle to get fast startup.
VERSION="$(nvm_version "$PROVIDED_VERSION")"  is slow, but there seems to be no need for it to be so slow. Adding a quick hack above the else speeds it up:
@@ -1307,6 +1307,8 @@ nvm() {
           PROVIDED_VERSION="$NVM_RC_VERSION"
           VERSION="$(nvm_version "$PROVIDED_VERSION")"
         fi
+      elif [ "$2" == default ]; then # performance
+        VERSION="$(< ~/.nvm/alias/default)"
       else
         local NVM_IOJS_PREFIX
         NVM_IOJS_PREFIX="$(nvm_iojs_prefix)"

There is a nvm_ensure_version_installed "$PROVIDED_VERSION" call that might be overkill to do on each shell startup. I just took it out for now:
@@ -1347,7 +1349,6 @@ nvm() {
         return 8
       fi

-      nvm_ensure_version_installed "$PROVIDED_VERSION"
       EXIT_CODE=$?
       if [ "$EXIT_CODE" != "0" ]; then
         return $EXIT_CODE

And finally checking for the presence of a default installation (nvm ls default) could be as easy as checking for file presence:
@@ -1718,7 +1719,7 @@ if nvm_supports_source_options && [ "_$1" = "_--install" ]; then
   elif nvm_rc_version >/dev/null 2>&1; then
     nvm install >/dev/null
   fi
-elif nvm ls default >/dev/null; then
+elif [ -f ~/.nvm/alias/default ]; then
   nvm use default >/dev/null
 elif nvm_rc_version >/dev/null 2>&1; then
   nvm use >/dev/null

Thanks for researching this!
Of these three optimizations:
I'm not opposed to the first "else" check, but the $(< …) syntax concerns me re portability, and I'd definitely prefer to use nvm_alias default 2> /dev/null rather than hardcoding paths etc. Could you verify that using VERSION="$(nvm_alias default 2> /dev/null)" provides a similar performance bump?
The second can't happen - that's inside nvm use, so even if it's not required on initial sourcing, it's required on every nvm use after that.
As for the third one - I'd be fine switching that line to nvm_alias default 2>&1 >/dev/null if that would provide a similar performance enhancement - could you verify?
In summary, I definitely want performance to improve! However, nvm is sufficiently complex that maintainability trumps performance, so there's only so much optimization I'll be comfortable applying in that regard. Thanks again for doing this, it really helps me to know where specific bottlenecks are.

Could you verify that using VERSION="$(nvm_alias default 2> /dev/null)" provides a similar performance bump?

Yes, it does - perfect.

As for the third one - I'd be fine switching that line to nvm_alias default 2>&1 >/dev/null if that would provide a similar performance enhancement - could you verify?

Yes, it does. (Nitpick: I think it needs to be nvm_alias default >/dev/null 2>&1 for the redirect to work.)

The second can't happen - that's inside nvm use, so even if it's not required on initial sourcing, it's required on every nvm use after that.

Right. Maybe there's some way to have a separate (faster) code path for initial sourcing, but I understand that you want things to stay maintainable. :)

Awesome! Would you like to prepare a PR for those 2 changes? If not, I'll take care of it, but I don't want to steal your thunder.

Sure: #705

Awesome! This speed boost makes a huge different.

Still takes almost a second for me to startup. If I remove the . ~/.nvm/nvm.sh my shell loads near instantly..

There's still work to be done here, clearly.
The odd thing is that it's lightning fast on my Mac(s), but enough people have had this issue that it's probably something in my environment allowing it to be fast, not something in yours making it slow.

My problem is also that I had to add that both to my .zshrc and .zprofile for nvm to work on my terminal and for sublime plugins to be able to use node. this makes the startup time twice the normal it has to be.
.zprofile: http://puu.sh/ibneI/065bcb95e0.png
then..
.zhsrc: http://puu.sh/ibneI/065bcb95e0.png

Those are the same link.
But also, presumably there's a better way to set up the profile files so that's not necessary? ie, a file that zsh sources once in all cases?

Yeah my bad, I fixed the second link. Not sure how I can make it so that zsh sources once in all cases though.

i was able to set a custom path for node on my sublime plugin. Now I am only running the shell script once on shell startup. This still has a ~.5 second startup time though.

Anecdotally: I'm seeing a consistent 0.93 - 1.5 second slowdown on every launch.
nvm 0.28.0
zsh 5.0.8
osx 10.10.5

@dylanpyle Are you using oh-my-zsh? What's your output of nvm debug? If you nvm unalias default, does the slowdown disappear?

@ljharb not using oh-my-zsh.
λ nvm debug
$SHELL: /bin/zsh
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: v0.10.38
which node: $NVM_DIR/v0.10.38/bin/node
which iojs: iojs not found
which npm: $NVM_DIR/v0.10.38/bin/npm
npm config get prefix: $NVM_DIR/v0.10.38
npm root -g: $NVM_DIR/v0.10.38/lib/node_modules

If you nvm unalias default, does the slowdown disappear?

Yep, looks like it! Seems like I can just stick something like:
export PATH=/Users/dylan/.nvm/v0.10.38/bin/:$PATH

in my zshrc, and an nvm used version will take priority over that if specified. Seems to defeat the purpose a little bit, but suits my immediate needs — and no more slowdown.

Certainly you can hardcode it, but it shouldn't be necessary :-( if you do nvm alias foo 0.10.38, and then add nvm use foo instead of the PATH line in your zshrc, is it still slow?

is it still slow?

Yep :(
λ gdate +%s.%N && nvm use foo && gdate +%s.%N
1444159024.473559000
Now using node v0.10.38 (npm v1.4.28)
1444159025.456576000

@dylanpyle thanks - and to confirm as well, nvm use 0.10 is not slow? so nvm alias foo is the slow part?

@ljharb aha, good question. nvm use is indeed the bottleneck:
λ time (nvm use 0.10)                                                                                develop 13:50
Now using node v0.10.38 (npm v1.4.28)
( nvm use 0.10; )  0.50s user 0.20s system 83% cpu 0.846 total

λ time (nvm use 4)                                                                                develop 13:50
Now using node v4.1.2 (npm v2.14.4)
( nvm use 4; )  0.72s user 0.23s system 86% cpu 1.089 total

If this is a separate issue than the parent, want me to open a new one?

@dylanpyle please do open a new one with this timing info - I think it's the same issue but let's start with a fresh context.

done: #860

With / Without [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm:
❯ for i in $(seq 1 5); do /usr/bin/time zsh -i -c exit; done
        1.00 real         0.58 user         0.46 sys
        1.00 real         0.59 user         0.46 sys
        0.99 real         0.59 user         0.46 sys
        1.01 real         0.59 user         0.47 sys
        0.99 real         0.59 user         0.46 sys

❯ for i in $(seq 1 5); do /usr/bin/time zsh -i -c exit; done
        0.14 real         0.09 user         0.04 sys
        0.14 real         0.09 user         0.04 sys
        0.14 real         0.09 user         0.04 sys
        0.13 real         0.09 user         0.04 sys
        0.13 real         0.09 user         0.04 sys

I have the same issue. It is quite slow on Ubuntu 16.04


MINOR: Update docs link to deprecated method TimeWindows.grace

@AyoubOm thanks for this contribution. Could you fix https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/SessionWindowedCogroupedKStream.java#L42 also?

@AyoubOm thanks for this contribution. Could you fix https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/SessionWindowedCogroupedKStream.java#L42 also?

Thanks @chia7712, fixed !

@AyoubOm thanks for this contribution!


fix: entry query should handle non-string entry

Summary
Correctly handle all possible entry types to add entry query. Previously, we can only handle string indeed.
Related Links

Checklist

[x] Tests updated (or not required).
[ ] Documentation updated (or not required).

Can we also support EntryDescription in compose bundleless entry?

Can we also support EntryDescription in compose bundleless entry?

I don't think user need to use EntryDescription in bundless mode, even in bundle mode for foreseeable usage. We could talk about that in the future.


When selecting "Leads To", do not include the systems already selected for auto-filling "Leads To" in that system.

If someone really wants to switch the connection, they should just remove the connection from the other first, then select it in the other Leads To.

Bumping this enhancement request some as it would be a big QoL time-saver for adding these connections.

Already linked systems got moved into a separat group and are no longer available for select until they get un-linked from its signature.
Auto-pre-selection is not implemented for now. This might become complex to implement. Maybe in future...


Map Chunk loading, Chunks and Chunk Generation

Maps some parts of the chunk loading and generation code, and clears up a few param names in some chunk related classes.

method_20458 -> tryUnloadChunk

try

good lord clock makes hella commits

Did you forget to push? You resolved my comments without any changes

I had to go do something so I'll push in a few mins after one fix I have to do by hand

Issues have been resolved


Allow symmetric crypto to be called in 'chained mode', support CFB128

The gist of the rationale is in the second commit. The first one adds support for another CNG property, which allows to switch between CFB8 (default) and CFB128 cipher mode.

Thank you for taking a look 🙇


Update to TS release-1.5 branch

Update typings
Fix tsconfig.json build output paths
Add "concat-and-test" grunt task for running tests after building from an editor like Atom

Before we merge this PR, we should wait for TS to release 1.5 so we can point to the npm release in our package.json.


[stable/wordpress] Allow more flexible TLS configuration.

What this PR does / why we need it:
Allows more flexible TLS configuration. Currently you can't do certain things, e.g. generate certificates that cover multiple hosts. Instead of having a custom structure for TLS this PR reverts to using the standard Ingress structure.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/retest

Could you please rebase from master and bump the version of the chart?

Hi @adtennant
I just merged your other PR to unset the nodePort and, as a consequence, the CI complains again about conflicts in the Chart.yml. could you rebase agin?

/ok-to-test
/lgtm


Add YouTube Music search provider

Not sure if this is desired, but I added a sort of rudimentary YouTube Music based search provider. I took a lot of inspiration from the jAPI implementation, which is similar but not music specific
I still need to:

Implement pagination (we only get first page results as of right now)
Reduce some hard coded values and/or make them configurable (not everyone is in the US)
Call out how utterly experimental this is and how likely it is that YouTube Music breaks this implementation
Implement any feedback given
Remove constraint to search only by "Any", since the YouTube Music API allows us to search by Artist, Album or Song
Add tests and fix failing tests

If this isn't wanted, feel free to tell me and I'll just maintain this little class for my own fork or spin this off into mopidy-youtube-music :)

Thanks for this - it looks very interesting! I'll have a proper look when I get a chance and will have a think about how it might fit in.

Just removed a hardcoded search query, and added in pagination support.  I've used up all my access on accident :joy:

Is there documentation for the YouTube Music API?

Unfortunately not, it's not technically a public API and it's something I reverse engineered off of the YouTube Music app

Oh, I see. Interesting. I couldn't exactly work out what you're doing to get the API key. Can you explain how that works?

It's querying the YouTube music home page. Injected into the html via a script tag is a JSON object that contains an API key. We grab that json with regex, parse it, and grab the key from it. After that, we memoize it

I merged this into a new branch for further development - feature/youtubeMusic


dataspeed_ulc_ros: 0.0.5-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository dataspeed_ulc_ros to 0.0.5-1:

upstream repository: https://bitbucket.org/DataspeedInc/dataspeed_ulc_ros.git
release repository: https://github.com/DataspeedInc-release/dataspeed_ulc_ros-release.git
distro file: noetic/distribution.yaml
bloom version: 0.9.7
previous version for package: null

dataspeed_ulc

No changes

dataspeed_ulc_can
* Updates scale factor on linear accel and decel limit CAN signals
* Adds README to document the ROS node interface
* Contributors: Micho Radovnikovich

dataspeed_ulc_msgs

No changes

Closing this PR and creating a new one to fix it


Bad handle of (dynamic) optional dependencies during dependency pre-bundling

Describe the bug
Hello,
First of all, thank you for developping this awesome tool. I use it on many projects now as the replacement of my old but stable toolchain.
Let's get into this issue: I'm maintainer of the library svelte-query which uses an optional dependency (broadcast-channel) to provide an opt-in feature.
When developers install the library on a vite project, vite is throwing an error: Failed to resolve import "broadcast-channel" (SvelteStack/svelte-query#63).
However, this dependency is imported dynamically only when the developper actually use the associated feature.
I think, there are two options to resolve this issue:

Delay the pre-bundling of dynamic imports when they are actually imported (best IMHO)
If solution 1 is not acceptable, maybe we could only delay pre-bundling of dynamic imports that are referenced in optionalDependencies in the package.json.

The only workaround I found is to install the optional dependency even if it's not used. I tried to include @sveltestack/svelte-query, broadcast-channel or both in optimizeDeps.exclude but it's not enough to workaround this issue.
I'm not familiar with vite code but I'm happy to help if needed.
Reproduction
1/ Start by creating a fresh project using create-vite:
$ npm init vite
✔ Project name: … vite-project
✔ Select a framework: › svelte
✔ Select a variant: › svelte-ts

$ cd vite-project
$ npm install

2/ Install svelte-query dependency:
$ npm install @sveltestack/svelte-query

3/ Use it in your code (eg: App.svelte):
<script lang="ts">
  // append this at the end of imports
  import { QueryClientProvider } from "@sveltestack/svelte-query";
</script>

<QueryClientProvider>
  <!-- The content of the page -->
</QueryClientProvider>

4/ Run the project:
$ npm run dev

System Info
System:
    OS: Linux 5.10 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
    Memory: 1.63 GB / 7.57 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
  npmPackages:
    vite: ^2.7.0 => 2.7.1

Used Package Manager
npm
Logs
[vite] Internal server error: Failed to resolve import "broadcast-channel" from<EMAIL_ADDRESS>Does the file exist?
  Plugin: vite:import-analysis
  File<EMAIL_ADDRESS>  1  |  import '../core';
  2  |  export async function broadcastQueryClient({ queryClient, broadcastChannel = 'svelte-query', }) {
  3  |      const { BroadcastChannel } = await import('broadcast-channel');
     |                                                ^
  4  |      let transaction = false;
  5  |      const tx = (cb) => {
      at formatError (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:42587:46)
      at TransformContext.error (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:42583:19)
      at normalizeUrl (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:80909:26)
      at async TransformContext.transform (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:81049:57)
      at async Object.transform (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:42803:30)
      at async doTransform (/projects/vite-project/node_modules/vite/dist/node/chunks/dep-3daf770c.js:57478:29)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I'm having this exact same issue in a SvelteKit project!
Even in a try catch, we get the same error about vite:import-analysis
let dependency;

try {
    dependency = await import('@org/dependency')).default;
} catch {
    //
}

We recently migrated from rollup to Vite and now our old code doesn't work which is super annoying.

I'm seeing this error when conditionally importing a CSS file that doesn't exist - i.e. the error shows up and prevents compilation even when the condition is falsy:
if (import.meta.env.VITE_SOME_FALSY_VAR) {
  import('./some-css-file-that-doesnt-exist-in-this-environment.css');
}

Seems like dynamic imports are analyzed statically just like static imports.

@SomaticIT Hi, just tried to use your repo with SvelteKit and running into this issue. Did you ever find a resolution?

@ZetiMente: Unfortunately, I think there is no simple solution. The only way is to install optional dependencies to allow vite to analyze it. (It will not be bundled during the build)
I think, vite should only analyze and bundle dynamic dependencies when they are actually used in the code. However, it means modifying the dependency analyzer process which is a sensible part of the process.
I would be happy to take some time to create a PR (when possible) but I need some kind of help from a contributor to avoid mistakes.

Hmmmm, I also need to find a way to support an optional dependency.  Storybook is working on react 18 support, but in a way that also continues to support older versions.  We need to dynamically import react-dom/client if using react 18, but vite throws an error since it can't resolve it in older react versions.  I guess we would need to conditionally add react-dom to optimizeDeps.exclude, perhaps?

I am running into this issue as well. I am trying to add an optional dependency to tradingstrategy.ai/frontend application. We would like to include an optional third-party library that's proprietary. If someone clones / forks our app who doesn't have access to the proprietary module (in a private repo within our org), we would like them to still be able to run the dev server, build, etc. We thought we'd be able to dynamically import the module inside a try / catch and gracefully degrade the UI based on whether it loaded.
The "positive" scenario works (dynamically loading when module available). The "negative" scenario results in the same vite:import-analysis error. Adding the module to optimizeDeps.exclude does not seem to help.
Let me know if there's a solution or work-around for this. Thanks!

@kenkunz this is the workaround I arrived at, in addition to optimizeDeps.exclude: https://github.com/storybookjs/builder-vite/pull/320/files#diff-53261c79d121de43b9341f7d87ba28d33c2cdac416c10b0ccf5022f767937e91R68-R75

Thanks for sharing this, @IanVS … I will try out this approach tomorrow!

@IanVS thanks again for your suggestion. I wound up using a different work-around – inspired by another issue you opened: #5728 [Feature request] Allow import.meta.glob from node_modules (addressed by PR #6056).
I am now loading the optional dep using:
const modules = import.meta.glob('/node_modules/chartiq/{js,css}/*.{js,css}');

…and then checking Object.keys(modules).length / importing the modules I need if available. Works great / no vite:import-analysis errors.
My only slight hesitancy with this approach is that it's a Vite-specific feature. But given that it's a work-around to a Vite-specific issue … and this is in a SvelteKit app (no real likelihood of moving away from Vite) … I'm fine with that.

@IanVS would you be able to provide a minimal setup for this so we can reproduce it? Are you using enforce: 'pre' in your plugin to get before the internal resolve plugin? For reference plugin react is now using a proxy when dealing with the jsx runtime, so something, like you were doing, should continue working now too:

https://github.com/vitejs/vite/blob/5151e7466bdb86066991b77df8db6ada066bb71f/packages/plugin-react/src/index.ts#L363

Yes, I'm using enforce: 'pre'.
I'm sorry, I don't quite see the connection to the jsx runtime.
I'll work on a minimal reproduction.

Reporting back, setting an alias to point to my file seems like a usable workaround.  I wasn't able to use a virtual file using the approach from 'react/jsx-runtime'.  One small downside is that rollup warns about generating an empty chunk, but I can live with that.

I tried to create a minimal reproduction, but wasn't able to reproduce the issue when using my previous workaround without an alias on vite 3.  It failed in storybook, but not when I tried to reproduce it.  I'm happy to use the alias unless there's a downside to it I don't know of.

I think an alias is a better solution here, but it would be good to avoid that warning :)

I can probably add a rollupOptions.onWarn to filter it out.


Unable to connect to Contentful

I am providing the necessary spaceId and accessToken for my Contentful space, however I keep getting error:
Accessing your Contentful space failed.
Try setting GATSBY_CONTENTFUL_OFFLINE=true to see if we can serve from cache.
error Command failed with exit code 1.
Starting to fetch data from Contentful
Fetching default locale

 ERROR

Accessing your Contentful space failed.
Try setting GATSBY_CONTENTFUL_OFFLINE=true to see if we can serve from cache.

Used options:
spaceId: "*********rot"
accessToken: "***************************************BlY0"
environment: "development"
host (default value): "cdn.contentful.com"
downloadLocal (default value): false
localeFilter (default value): [Function]
forceFullSync (default value): false
pageLimit (default value): 100
useNameForId (default value): true

not finished source and transform nodes - 0.364s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Steps to reproduce

Clone repository
yarn install
yarn setup
input a valid spaceId
input a valid Content Delivery API
yarn develop

I'm getting the same error over a year later.

I'm getting the same error over a year later.

You need to change the 'environment' for the 'host'.   See the plugin docs > https://www.gatsbyjs.com/plugins/gatsby-source-contentful/.
Make sure to store the host as a env variable so that when deploying live you use the published content instead of preview
like this....
,
    {
      resolve: `gatsby-source-contentful`,
      options: {
        spaceId: process.env.CONTENTFUL_SPACE_ID,
        accessToken: process.env.CONTENTFUL_ACCESS_TOKEN,
        host: process.env.CONTENTFUL_HOST,
      },
    },


The date is weirdly formatted

When listings articles the date looks weird like this:
M/D/YY

The standardized date formatting is this:
YYYY-MM-DD

What's your locale? This should change depending on that.

What's your locale? This should change depending on that.

I'm from Sweden and I use the network provided time.


Typo for 'noncompliant'

CEF processing fixes for noncomliant RFC 5424 logs
noncompliant is the correct spelling.

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

ID: fc10903f-b45a-34ef-026f-1329012640aa
Version Independent ID: 52f35fd8-72d5-4c0d-3774-9bb6e150f003
Content: Azure Monitor agent extension versions - Azure Monitor
Content Source: articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@JFBDO2022 Thanks for the feedback! I have fixed the referenced change, and the change should reflect on the doc within 24 hours.We will now proceed to close this thread. If there are further questions regarding this matter, please revert and we will gladly continue the discussion.


Case sensitivity issue on Mysql during Introspection

If you have very similar names for tables / columns in your db all MySQL versions except MySQL 8 can produce wrong introspection results. Sample schema:
model ADDRESS {
   ADDRESSID Int @id
}

model Address {
  AddressID Int @id @default(autoincrement())
}

model address {
  addressid Int @id
}

This also causes the order of the models in the generated schema file to be random and changing with each time you run Introspection.


Update how secrets are references in workflows

This should address concerns raised in ITHELP-87329

Hey Jeff, apologies but I needed to kick off a rebase to update your PR to remove redundant code therefore I will appear in the commit log. If you prefer, feel free to close this PR and reopen a fresh one. Apologies for any inconvenience caused.

Update my rebase has not resolved the issue. Unfortunately I am going to delete your branch Jeff. Please feel free to rebase and repush to create the PR. Apologies for any inconvenience caused, if you have any addditional queries please do not hesitate to reach me on the community slack. (again sorry).


Revert changes on environment and docker-compose made by #254

Not sure how this happened, this basically reverted changes I made in #264.

late night merging fun funfun. sorry for not getting back to the other folks if you see this, will write you tmrw


Documentation doesnt mention permissions required for creating/assigning Cosmos RBAC roles

Hi
The documentation doesnt mention what management plane RBAC permissions are required on the Cosmos resource to be able to create/assign custom data plane RBAC roles. Is "contributor" privileged enough ?

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

ID: aba612b3-f404-11b2-45d9-6e10f1fbf11d
Version Independent ID: 86ccb46e-5ebd-50a4-a911-2ac83c8a41f4
Content: Configure role-based access control for your Azure Cosmos DB account with Azure AD
Content Source: articles/cosmos-db/how-to-setup-rbac.md
Service: cosmos-db
GitHub Login: @ThomasWeiss
Microsoft Alias: thweiss

@gregt1234 Specific RBAC permissions cover the management of role definitions and role assignments:

Microsoft.DocumentDB/databaseAccounts/sqlRoleAssignments/read
Microsoft.DocumentDB/databaseAccounts/sqlRoleAssignments/write
Microsoft.DocumentDB/databaseAccounts/sqlRoleAssignments/delete
Microsoft.DocumentDB/databaseAccounts/sqlRoleDefinitions/read
Microsoft.DocumentDB/databaseAccounts/sqlRoleDefinitions/write
Microsoft.DocumentDB/databaseAccounts/sqlRoleDefinitions/delete

The Contributor role includes these actions so can be used indeed.

@gregt1234 Thanks for the question! We are investigating and will update you shortly.

@gregt1234 I hope the response from @ThomasWeiss clarifies your query.
If there are further questions regarding this issue, please comment and we will gladly continue the discussion.

Yes thanks - another comment on that documentation page is that it would be helpful to mention that custom roles can also be created via bicep, in addition to PowerShell and AZCLI.


Complete the Search model

Complete the Site Search Function

Need more details.. What are you planning to implement?

Yes, I am willing to do so. Let's discuss about how we should do with it?

ok, we can discuss.. What are you planning to implement? something related to UI or some functionality?

How about using Google site search, or we make it by ourself?
2015-02-09 11:32 GMT+08:00 Abdel Raoof<EMAIL_ADDRESS>
ok, we can discuss.. What are you planning to implement? something related
to UI or some functionality?
—
Reply to this email directly or view it on GitHub
https://github.com/olakara/JekyllMetro/issues/30#issuecomment-73452961.


client is zoomed (f) in addr, offset

PatternBaseAddress = Scan(00 00 06 00 00 00 ?? ?? ?? ?? ?? ?? ?? 43 ?? ?? ?? ?? ?? ?? ?? ?? 00 00 00 00 01 00 00 00 00 00 00 00 00 00 80 3F)
Zoom : uint64(PatternBaseAddress + 0x30)
Pattern occurs outside the base module
Zoomed In : 0x003f0000003f00
Zooming in (motion) > 0x003f0000003000 && != 0x003f0000003f00
Zoomed Out : 0x00
Zooming out (motion) > 0 && < 0xffff
Example Data
// ----[ dumping address 0x4f7e1ad6 ]--------------------------------------------------------------
//           00 01 02 03 04 05 06 07  08 09 0a 0b 0c 0d 0e 0f  01234567 89abcdef
// 00000000  00 00 06 00 00 00 8f bf  06 44 25 06 dd 43 8f bf  ........ .D%..C.. pointer 0x00060000
// 00000010  06 44 96 43 8b 3c 00 00  00 00 01 00 00 00 00 00  .D.C.<.. ........
// 00000020  00 00 00 00 80 3f 00 00  10 40 00 00 10 40 00 00<EMAIL_ADDRESS>// 00000030  00 3f 00 00 00 3f 00 00  00 3f 00 00 00 00 00 00  .?...?.. .?......
             ^^^^^^^^^^^^^^^^^^^^^^^ this is the data

note - Screen to World and World to Screen are 1/2 or 2

@iceisfun thanks for the detailed issue, I would like to discuss a bit more to get better context on this since it's not fully clear to me about the offset we are talking about and the impact. I understand we are reading information from the wrong place (zoomed) instead of normal one? Could you help me understand how this affects the functionality? I'm interested in any ideas you might have for a solution. Looking forward to your input, thanks!

oh, that's super interesting @iceisfun, never thought about that feature but it's true it can be used to increase the precision when hovering, it's a very good tip! 💯
I'm also surprised to see someone else working on something similar in go! I don't see your project in your github profile so I suppose is not open source, you want to connect? I believe we can share some thoughts and maybe collaborate somehow. I'm finding this very interesting. You can reach me via discord: yastxd or just drop me a mail (you can get it from my github profile)


go test exits with non zero exit code, so test parser never runs when tests fail

I must be missing something - the go test task exits with non-zero when a test fails, this means the next task which is meant to be the test parser never runs, which means my tests don't get parsed and shown in the interface.
Is this by design, or have I done something horribly wrong in my setup somewhere?
Failing test - skips to running post build steps ...
build   12-Oct-2016 14:29:34    FAIL build   12-Oct-2016 14:29:34    exit status 1 build   12-Oct-2016 14:29:34    FAIL    bitbucket.org/fusemail/fm-utility-golang-trackerdb  0.007s simple  12-Oct-2016 14:29:34    Failing task since return code of [/usr/local/go/bin/go test -v .] was 1 while expected 0 simple  12-Oct-2016 14:29:34    Finished task 'Test' with result: Failed simple  12-Oct-2016 14:29:34    Running post build plugin 'NCover Results Collector'
Successful test - runs the test parser ...
build   12-Oct-2016 14:26:36    --- PASS: TestBase62 (0.00s) build   12-Oct-2016 14:26:36    PASS build   12-Oct-2016 14:26:36    ok      bitbucket.org/fusemail/fm-utility-golang-trackerdb  0.004s simple  12-Oct-2016 14:26:36    Finished task 'Test' with result: Success simple  12-Oct-2016 14:26:36    Starting task 'Parse Tests' of type 'com.handcraftedbits.bamboo.plugin.go:task.go.test.parser' simple  12-Oct-2016 14:26:36    Parsing test results under /var/lib/bamboo/xml-data/build-dir/GO-TRAC-JOB1... simple  12-Oct-2016 14:26:36    Finished task 'Parse Tests' with result: Success

I am running into this as well. Any updates?

Same here. Updates @handcraftedbits ?

I was able to workaround this by having the test results parser be a "Final Task." This will cause the parser to run even if the tests fail. I think this is how it was designed to work.

Thanks @peternoyes

@peternoyes I did this but the test task still fails even if my tests pass.


question

Will it work on Mac?

yes would work on mac or any kind of os until u have py 3.9+
over 25+ users has tried it one mac worked fine

ok thanks


BackAndroid is not supported anymore in react-native

I removed BackAndroid import from utils/index.js since it is not supported by react-native and throws some errors now.

Hi again,
Would it be possible to publish a new version plz ?
My CI fails because of inconsistent dependencies 1.30.1 => 1.30.3
And btw, I'm thinking of making a new PR with a "value" option in "Toolbar.props.searchable" (default value + controlled mode for Toolbar search). Interested ?
Cheers !

:tada: This PR is included in version 2.0.0-alpha.1 :tada:
The release is available on:

npm package (@develop dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


.travis.yml: remove verify job

The verify job has been moved to prow, so we can remove the one from
travis.
/assign @s-urbaniak

/lgtm
/approve


Completion fuzzy matching filtering does not work on Live Share client.

VS Version: 28721.148.d16.0stg
Python Tool Version: 16.0.19074.1
Repro step:
1.Open Live Share session
2.Type code
import decimal
decimal. ctxt
Except result:
All matched completion lists for 'ctxt' should appear

actual result:
No "Context" with an uppercase 'C' was retrieved

LiveShare IntelliSense implementation doesn't have the same fuzzy matching logic for filtering as the Python IntelliSense.
The Context result is there:

But is filtered out in LiveShare completions when it's not an exact match:


Property to change GraphiQL's /graphql endpoint

Our app exists behind a zuul router, so even with the default mapping of /graphql and /graphiql, /graphiql is not able to find /graphql. Is there anyway to add a property to the graphiql config to change the location it looks for graphql?

I had the same issue and found a workaround.  A graphiql.html file in our main project /resources folder seems to have taken care of the issue after removing the leading /, making it return fetch('graphql', {.  This successfully pulls the schema when hitting a direct instance (ie local development) or if it is behind zuul.
Making this configurable would be a plus to make keeping in sync with project updates easier.

This is added in the latest version (graphiql.endpoint), but you can provide your own graphiql.html and that should work too


Revert "Use local provider to get dev profiles"

Reverts moonshotcollective/drecruit#90
This breaks the network detection and network switch behaviour. A PR to address this should also incorporate the external logic.

Cc @damianmarti @Cali93

@QEDK can you please explain what do you think that needs to be done here to allow to see the profiles when no wallet is connected?

@damianmarti The complicated way would involve setting a state when injectedProvider is set and when attempting to do a tx with a local provider, we detect the state to ask them to connect their wallet if needed. It's important to understand that localProvider is only a provider and never a signer, hence all attempts to do a tx will error in the frontend.
The easy way is the current behaviour of requiring you to connect your wallet.
Now, since we can effectively detect networks when connecting with the injected provider, we can move the network switch mechanism to that level, but it needs to be a solution that does not introduce regressions.
Cc @Cali93 just to cross-check and correct me or suggest necessary improvements

@QEDK I understand, but just for the read operations like getting the dev profiles I think that we can use the localProvider and if the user wants to interact (like request the private profile from a dev) the app will show a message that the user needs to connect your wallet first.

@damianmarti Exactly, and that's something to incorporate with state I believe (or whatever is optimal). The issue is that the user should not be using the local provider for transactions and having the interactions fail.

@QEDK yes! But I just changed the provider to get the dev profiles. Nothing will break with this change or maybe I'm missing something...

@QEDK I see the error when trying to Request contact information....

@QEDK yes! But I just changed the provider to get the dev profiles. Nothing will break with this change or maybe I'm missing something...

It also breaks the network switching behaviour because we rely on context.injectedProvider erroring. For e.g.

Have any other network other than Mumbai testnet selected in your wallet
Click connect
The network alert dialog to add/switch network will not show up.

@QEDK thanks for all the explanation! I think we should find a easy way to use the localProvider for read operations and the injectedProvider for write operations and that everythink work well (like we did with the readContracts and writeContracts on scaffold-eth, using the localProvider for the first one and the userSigner for the last one). In this way, we can show up the public data with no connect wallet required. I will re-open the issue and look into it.


there was one asterisk more than needed

And that broke formatting of the page.
Signed-off-by: Petr Horacek<EMAIL_ADDRESS>

@EdDev @cathay4t please take a look


Auth0 user account linking (v1.1+)

We don't allow duplicate emails so if someone tries to signup with a social account and the same email already registered under they get an error (see #772).
Eventually we want to enable user account linking in such a case. Not critical - release v1.1 (or later).
https://auth0.com/docs/users/concepts/overview-user-account-linking

Will I need access to auth0 to work on this?

@adisen yes there is a setting for this on Auth0, so first need to enable on the dev environment and later also on the other environments, there is also a lot of documentation on Auth0 how that works, I looked at it before but then we didn't have the premium features yet so it was not supported in the free version. I think it should be possible to use their API to show a custom page on our frontend and to go through our back-end to let the user confirm if they want to merge the login methods.

Yes Robin, similar to what is on eBay. A user get prompted, if when they want to signup with a social media account with the same email, to link the 2 accounts.

Hey @adisen @joshmorel @robinv85 , do we have an update on this issue?

Sorry I've been unable to implement this. Someone can pick it up

No problem @adisen. Thanks for giving us an update.
@tejasm2 :

we are going to just return an error for now when addressing issue #1437 if a user tries to sign up with same email
I think we still want this - but likely put it on the back burner (i.e. low priority)

We should definitely be able to link the accounts Auth0 enables this quite easily. But let's put P3 maybe.

progress update:

able to replicate Auth0 demo for accounting linking locally
able to reproduce #1226 phenomenon
applied user accounts detection code, got 403 error from Auth0
Todo next:

need access to Auth0 account, to update API rules

progress update:

403 error was due to using a wrong token
Auth0 new function getUsersWithSameEmail() is completed and tested

Todo next:

finish integration of functions linkAccount() and unlinkAccount() + mergeMetaData()

Questions:

are we creating new endpoints for querying / linking / (unlinking)?
if that's true, new endpoints purposal: get /same-email-accounts, post /link-accounts, (post /unlink-accounts)

just want to give an update:
slowing down due to another higher priority issue, and I am still working on this : )

draft PR #1727 has the code, it's doing an automatically linking right now, depends on the project design, we can fine-tune it.

the basic version is done, ready for review.
one note: not sure how we're going to QA this feature, will need Auth0 account delete to repeat tests.

the latest update, add dialog (learned from @Zaydme code : ) to remind the user

@ddveloper @joshmorel
Customers are observing this issue and reporting, can we prioritize this issue for this upcoming release on Dec 15?
Thanks

@rabbi08 see JV's comment here - https://github.com/FightPandemics/FightPandemics/pull/1727#issuecomment-736267702 . They want QA to test before merging to staging.

@rabbi08 see JV's comment here - #1727 (comment) . They want QA to test before merging to staging.

great thanx @joshmorel for highlighting, this was missed from my side. will test.


feat(converter): support figure and tabular environments

basic support for figure, table and tabular environments.
#mitext(`
  \begin{table}[ht]
      \centering
      \begin{tabular}{|c|c|}
          \hline
          \textbf{Name} & \textbf{Age} \\
          \hline
          John & 25 \\
          Jane & 22 \\
          \hline
      \end{tabular}
      \caption{This is an example table.}
      \label{tab:example}
  \end{table}
`)

Looks pretty well 🎉


Huge Dupe bug (Stackables)

Minecraft version & Mod Version:
1.12.1, cyclic 1.8.6
Single player or Server:
Server (Minecraft Mod Developement public server)
Describe problem (what you were doing / what happened):
Shift clicking an item into a full cyclic inventory (The inventory upgrade) dupes any item that is stackable if there is space in the vanilla inventory.

Crash log (if any):
None
(If this is a suggestion and not a bug report, delete all this and just write your suggestion!)

(Btw, the 4 first slots seem a little bugged)

Thanks for the screenshots, thats really helpful.
This was fixed in  a previous update though, see https://github.com/PrinceOfAmber/Cyclic/issues/518 for more information and download the latest version.
I notice you are still in 1.12.1, you should upgrade to 1.12.2 when you have a chance.  Fixes vanilla bugs and literally every 1.12.1 mod ive tried works just fine in 1.12.2

I tested again with the newest version of everything, using one of the ATM packs, seems still fixed.
Thanks for reporting anyway! better a duplicate report than no reports at all. I wish all reports had screenshots as good as these ❤


Recovering from unexpected Generator Costs

The tool seems to have recurring challenges around the generator cost function block.  Indeed, this is the most complex data structure in the file format.
I propose that we change the parser so that when the generator data can not be understood a warning is raised and the visualization continues, with "unknown" for the cost values.
It would be good if the tool also worked when there was no generator cost function.  In the worst case a user can delete the cost function and then load their network.
Reported by Barry Rawn

Updated STAC to handle the input file which do not have any generator data.
Also the previous custom error messages have not been updated/modified. They are as follows:
Case 1 - When the length of the cost data and the generator data is not equal.
Alert Message - Warning: this test case has cost values on reactive power generation that are not displayed by this tool.
Case 2 - If the value in the first column of the generator cost data the value is 1.
Alert Message - Warning: the piecewise linear generator cost functions in this test case are not displayed by this tool."
Please advise on the above two alert messages.

Updated the rules to allow the parser to continue if the generator cost data object is missing. For this to work the whole mpc.gencost data object needs to be removed.


set no-case-declaration flag

"no-case-declaration | Disallow let, class and enum in case blocks. These are visible within the whole switch statement body but not defined in other case clauses. The compiler currently doesn't warn about such uses. You should use a block to restrict the scope of the declarations"
https://github.com/microsoft/TypeScript/pull/47160

requires us to implement a linter, as its not a typescript setting


Unable to find component fan.xiaomi_miio

Home Assistant release (hass --version):
0.56.2
Python release (python3 --version):
no idea
Component/platform:
fan.xiaomi_miio
Description of problem:
I am trying to add Xiaomi Air Purifier 2 to Home Assistant but I get this info in the log:
2017-11-04 10:39:04 ERROR (MainThread) [homeassistant.loader] Unable to find component fan.xiaomi_miio.
and the component does not load.
Problem-relevant configuration.yaml entries and steps to reproduce:

fan:
  - platform: xiaomi_miio
    name: Xiaomi
    host: <IP_ADDRESS> (The IP of my Purifier)
    token: c628ch37dh37dh37nmpl38xg63h99jdn (not my real token, but looks like this)

Is there something I am doing wrong? What does Unable to find component actually mean? That Hassio does not recognize this component or that it does recognize it but it is unable to connect the air purifier?
Will be grateful for any help.

Hi,
xiaomi_miio was added in Home Assistant 0.57, you are running 0.56.2, so thats why :)
Please see https://home-assistant.io/docs/installation/updating/ for updating Home Assistant.

Hi rasmsube.
Many thanks for such a quick answer, I wasn't aware this was added in 0.57.
I am using hass.io, so I believe the 0.57 has not been rolled out yet. Will be waiting then.


Consolidating file watchers

Relies on #1489
Fixes issues with multiple watchers and resource utilization, which is particularly impactful when running against Azure Files.

To better review the changes (since this builds on top of #1489) , look at commit https://github.com/Azure/azure-webjobs-sdk-script/pull/1490/commits/926ecba5fde1ad6497fe6e3c8fa31647d6264c52

@mathewc @brettsam wrapped up with the remaining changes and have addressed the feedback you guys had. Let me know if you have any additional concerns.

@fabiocav -- Not a concern, but I'm curious. It looks like we register the same FileWatcherEventSource twice: new FileWatcherEventSource(EventManager, "ScriptFiles", config.RootScriptPath); -- once in ScriptHost and one in ScriptHostManager. Do we get dupe events from those?

@brettsam sorry, I thought I had replied to that comment earlier.
That code path in the ScriptHostManager is not executed when running the web host (so it doesn't run in production). I kept that in place to minimize the change but if the flag is set, this will receive the notifications from the publisher setup in the ScriptHost, so I'll go ahead and remove that.
Eventually, I wan to move that logic from the ScriptHost to the ScriptHostManager, executing it as part of the regular initialization so that we have a single publisher ever setup and don't need to tear it down at the host restarts.

@brettsam replying to your earlier comment:

If I'm reading this right -- you're removing the need for having a FileWatcher-per-Invoker. Instead, there's one that watches all files and invokers subscribe to that Observable. Is that right?
Yes, that is correct.

Assuming so -- is there a measurable perf (or other) benefit to this change? I like it either way; just curious :-)

There will be a performance impact as there will be less change notification handles (particularly important when running against Azure Files), but the key thing here is reliability and better resource utilization. Azure Files has a limit on the number of file change notification subscriptions and in some cases (depending on the number of functions and how scaled out the app was) we are hitting that limit, which causes notification failures as well as significant performance degradation.


find unused subnet

and action for delete, subnets report their used/total so this should be easy.

Despite the console showing the available, the APIs actually only return the available IPs. We can easily calculate those numbers by looking at the CIDR though and doing the conversion, keeping in mind that Amazon reserves 5 IP addresses in each subnet.
Describe call:
{
    "Subnets": [
        {
            "VpcId": "vpc-REMOVED",
            "Tags": [
                {
                    "Value": "MY-Sample-Subnet",
                    "Key": "Name"
                }
            ],
            "CidrBlock": "<IP_ADDRESS>/24",
            "MapPublicIpOnLaunch": false,
            "DefaultForAz": false,
            "State": "available",
            "AvailabilityZone": "us-east-1b",
            "SubnetId": "subnet-REMOVED",
            "AvailableIpAddressCount": 251
        }
    ]
}

We see <IP_ADDRESS>/24, so we know /24 -> 256 IP Addresses. 256-5 reserved = 251. So the above would be an unused subnet.

that looks pretty good, the alternative is an exhaustive search through all resources that could be vpc attached, which may actually be what we need to do, since some of those resources (aka lambda) are transient in usage.

I’ve spent some time looking into this and I’m not sure about the feasibility. If we’re going to delete a subnet, we need to be 100% sure it’s “unused”.
As you pointed out, we probably need to search through resources rather than rely on the available number alone, but which resources? There’s a list of related resources in the docs, but it doesn’t include the one example you cited (Lambda) which makes me wonder what else might be missing.
Querying all of those resources individually would require a decent amount of effort, and I’m not sure it will get us to “100% sure”. Do you think it’s worth it?


Document Upgrade Guide for 0.12.0

We need to a better job for 0.12.0 of documenting an upgrade guide. Specifically how to upgrade from 0.10.X to 0.12.0 and 0.11.X to 0.12.0 and I want to have this up before we release.

@nesquena would someone help me finding the final upgrade guide? The link on this issue is 404, just like a post I found on Twitter: http://padrinorb.com/blog/padrino-0-12-0-activesupport-4-rewritten-reloader-smarter-rendering-and-loads-more
I'm updating an old application and that would be really needed.

@igorsantos07 You can see all available blog posts listed here https://github.com/padrino/padrino-docs/tree/master/blog for easy reference. Looks like maybe that post didn't survive the transition?

I guess so, @nesquena! The first post on 0.12 is 0.12.4.
Judging from other frameworks/languages, I think the website should have a dedicated section for upgrades, that would easily list the upgrade path for each major version (i.e. those with breaking changes)... I got really lost looking for those guides around.


upgrade docs- workflow yaml must change; @v6 doesn’t work, @v6.0.0 does

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Previously this worked (and continues to work), but now there seems to be multiple issues with upgrades from v5 to v6, that aren’t covered in the upgrade docs.
If one merely changes the major version number from this working code there are multiple issues
      # Run Linter against code base
      - name: Lint Code Base with env
        uses: github/super-linter/slim@v5

Case 1: Fails because of the repo owner/path hasn’t been changed (Note github/super-linter)
      # Run Linter against code base
      - name: Lint Code Base with env
        uses: github/super-linter/slim@v6

Case 2: May fail due to settings on the user’s repo, even though path is now correct. Maybe docs can reference need to change settings in user’s repo to trust super-linter or Marketplace??
      # Run Linter against code base
      - name: Lint Code Base with env
        uses: super-linter/super-linter/slim@v6

Case 3: with permissions adjusted, this “upgrade” still fails because super-linter now seems to require a full semver number, to run v6
      # Run Linter against code base
      - name: Lint Code Base with env
        uses: super-linter/super-linter/slim@v6

It currently seems like repo owners must use this:
      # Run Linter against code base
      - name: Lint Code Base with env
        uses<EMAIL_ADDRESS>
Expected Behavior
Upgrade should indicate changes required to workflow yaml, such as:
When upgrading from v5 to v6, you must update the super-linter specification path and include a full semver number in your workflow, and super-linter must be a trusted workflow in the repo’s Settings > Actions > General.
      # Run Linter against code base
      - name: Lint Code Base with env
        uses: github/super-linter/slim@v5

becomes
      # Run Linter against code base
      - name: Lint Code Base with env
        uses<EMAIL_ADDRESS>
Anything else?
No response

Thanks for reporting this. #5208 took care of fixing the workflow to push the required tags. They'll be available after we publish a new release.


Messaging polyglot support

Passing part of the documentation as the description of what we're trying to achieve for adding polyglot messaging support.
How can you help
Please read the extract from the documentation below and answer the following questions

did you get anything from the documentation?

tell us how to fix the docs so they are more understandable

does the flow make any sense?

if not what would you change?

If you know python:

would any python person write such an endpoint to trigger a production message
does it make any sense from the python perspective?

If you know any other language

does this flow make sense for your language?
would you be willing to write such an HTTP endpoint to benefit from contract testing?

if that's the case would you be willing to test the feature out?
if that's the case would you be willing to provide a sample that we could embed in the docs? (simple controller that delegates a call to messaging code)

In addition to this please provide any feedback that you have with regards to this feature.
Additional links

Example: Repository with contracts (picked the groovy contract for messaging):
https://github.com/marcingrzejszczak/cdct_python_contracts/blob/master/META-INF/group/application/0.0.1-SNAPSHOT/contracts/consumer1/messaging/pingPong.groovy

Example: Python producer (highlighted the problematic HTTP endpoint to trigger a message)
https://github.com/marcingrzejszczak/cdct_python_producer/blob/patch-1/main.py#L52-L59

Example: Python script to run spring cloud contract messaging test with running middleware
https://github.com/marcingrzejszczak/cdct_python_producer/blob/patch-1/run_contract_tests.sh

Documentation of the feature
Example of Usage via Messaging
If you want to use Spring Cloud Contract with messaging via the Docker images (e.g.
in case of polyglot applications) then you'll have to have the following prerequisites met:

Middleware (e.g. RabbitMQ or Kafka) must be running before generating tests
Your contract needs to call a method triggerMessage(...) with a String parameter that is equal to the contract's label.
Your application needs to have a HTTP endpoint via which we can trigger a message

That endpoint should not be available on production (could be enabled via an environment variable)

Example of a Messaging Contract
The contract needs to call a triggerMessage(...) method. That method is already provided in the base class for all tests in the docker image and will send out a request to the HTTP endpoint on the producer side. Below you can find examples of such contracts.
import org.springframework.cloud.contract.spec.Contract
Contract.make {
    description 'Send a pong message in response to a ping message'
    label 'ping_pong'
    input {
        // You have to provide the `triggerMessage` method with the `label`
        // as a String parameter of the method
        triggeredBy('triggerMessage("ping_pong")')
    }
    outputMessage {
        sentTo('output')
        body([
            message: 'pong'
        ])
    }
    metadata(
        [amqp:
         [
           outputMessage: [
               connectToBroker: [
                   declareQueueWithName: "queue"
               ],
                messageProperties: [
                    receivedRoutingKey: '#'
                ]
           ]
         ]
        ])
}

description: 'Send a pong message in response to a ping message'
label: 'ping_pong'
input:
    # You have to provide the `triggerMessage` method with the `label`
    # as a String parameter of the method
    triggeredBy: 'triggerMessage("ping_pong")'
outputMessage:
    sentTo: 'output'
    body:
        message: 'pong'
metadata:
    amqp:
        outputMessage:
            connectToBroker:
                declareQueueWithName: "queue"
            messageProperties:
                receivedRoutingKey: '#'

HTTP Endpoint to Trigger a Message
Why is there need to develop such an endpoint? Spring Cloud Contract
would have to generate code in various languages (as it does in Java) to make it possible to trigger production
code that sends a message to a broker. If such code is not generated then we need to be able to trigger the message anyways, and the way to do it is to provide an HTTP endpoint that the user will prepare in the language of their choosing.
The endpoint must have the following configuration:

URL: /springcloudcontract/{label} where label can be any text
Method: POST
Basing on the label will generate a message that will be sent to a given destination according to the contract definition

Below you have an example of such an endpoint. If you're interested in
providing an example in your language don't hesitate to file an issue in
the Spring Cloud Contract repository at Github - https://github.com/spring-cloud/spring-cloud-contract/issues/new?assignees=&labels=&template=feature_request.md&title=New+Polyglot+Sample+of+a+HTTP+controller
#!/usr/bin/env python
from flask import Flask
from flask import jsonify
import pika
import os
app = Flask(__name__)
# Production code that sends a message to RabbitMQ
def message(cmd):
    connection = pika.BlockingConnection(pika.ConnectionParameters(host='localhost'))
    channel = connection.channel()
    channel.basic_publish(
        exchange='output',
        routing_key='#',
        body=cmd,
        properties=pika.BasicProperties(
            delivery_mode=2,  # make message persistent
        ))
    connection.close()
    return " [x] Sent via Rabbit: %s" % cmd
# This should be ran in tests (shouldn't be publicly available)
if 'CONTRACT_TEST' in os.environ:
    @app.route('/springcloudcontract/<label>', methods=['POST'])
    def springcloudcontract(label):
        if label == "ping_pong":
            return message('{"message":"pong"}')
        else:
            raise ValueError('No such label expected.')

Running Message Tests on the Producer Side
Now, let's generate tests from contracts to test the producer side.
We will run bash code to start the Docker image
with attached contracts, however we will also add variables for the messaging
code to work. In this case let's assume that the contracts are being stored in
a Git repository.
#!/bin/bash
set -x
CURRENT_DIR="$( pwd )"
export SC_CONTRACT_DOCKER_VERSION="${SC_CONTRACT_DOCKER_VERSION:-3.0.0-SNAPSHOT}"
export APP_IP="$( ./whats_my_ip.sh )"
export APP_PORT="${APP_PORT:-8000}"
export APPLICATION_BASE_URL="http://${APP_IP}:${APP_PORT}"
export PROJECT_GROUP="${PROJECT_GROUP:-group}"
export PROJECT_NAME="${PROJECT_NAME:-application}"
export PROJECT_VERSION="${PROJECT_VERSION:-0.0.1-SNAPSHOT}"
export PRODUCER_STUBS_CLASSIFIER="${PRODUCER_STUBS_CLASSIFIER:-stubs}"
export FAIL_ON_NO_CONTRACTS="${FAIL_ON_NO_CONTRACTS:-false}"
# In our Python app we want to enable the HTTP endpoint
export CONTRACT_TEST="true"
# In the Verifier docker container we want to add support for RabbitMQ
export MESSAGING_TYPE="rabbit"
# Let's start the infrastructure (e.g. via Docker Compose)
yes | docker-compose kill || echo "Nothing running"
docker-compose up -d
echo "SC Contract Version [${SC_CONTRACT_DOCKER_VERSION}]"
echo "Application URL [${APPLICATION_BASE_URL}]"
echo "Project Version [${PROJECT_VERSION}]"
# Let's run python app
gunicorn -w 4 --bind <IP_ADDRESS> main:app &
APP_PID=$!
# Generate and run tests
docker run  --rm \
                --name verifier \
                # For the image to find the RabbitMQ running in another container
                -e "SPRING_RABBITMQ_ADDRESSES=${APP_IP}:5672" \
                # We need to tell the container what messaging middleware we will use
                -e "MESSAGING_TYPE=${MESSAGING_TYPE}" \
                -e "PUBLISH_STUBS_TO_SCM=false" \
                -e "PUBLISH_ARTIFACTS=false" \
                -e "APPLICATION_BASE_URL=${APPLICATION_BASE_URL}" \
                -e "PROJECT_NAME=${PROJECT_NAME}" \
                -e "PROJECT_GROUP=${PROJECT_GROUP}" \
                -e "PROJECT_VERSION=${PROJECT_VERSION}" \
                -e "EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL=git://https://github.com/marcingrzejszczak/cdct_python_contracts.git" \
                -e "EXTERNAL_CONTRACTS_ARTIFACT_ID=${PROJECT_NAME}" \
                -e "EXTERNAL_CONTRACTS_GROUP_ID=${PROJECT_GROUP}" \
                -e "EXTERNAL_CONTRACTS_VERSION=${PROJECT_VERSION}" \
                -v "${CURRENT_DIR}/build/spring-cloud-contract/output:/spring-cloud-contract-output/" \
                springcloud/spring-cloud-contract:"${SC_CONTRACT_DOCKER_VERSION}"
kill $APP_PID
yes | docker-compose kill

What will happen is:

Tests will be generated from contracts taken from Git
In the contract we've provided an entry in metadata called declareQueueWithName that will lead to creation of a queue in RabbitMQ with the given name before the request to trigger the message is sent
Via the triggerMessage("ping_pong") method call a POST request to the Python application to the /springcloudcontract/ping_pong endpoint will be made
The Python application will generate and send a '{"message":"pong"}' JSON via RabbitMQ to an exchange called output
The generated test will poll for a message sent to the output exchange
Once the message was received will assert its contents

After the tests have passed we know that the message was properly sent from the Python app to RabbitMQ.
Example of Usage of Stub Runner with Messaging
In order to make messaging work it's enough to pass the MESSAGING_TYPE environment variable with kafka or rabbit values. This will lead to setting up
the Stub Runner Boot Docker image with dependencies required to connect to the broker.
In order to set the connection properties you can check out Spring Cloud Stream properties page to set proper environment variables.

Spring Boot Integration properties - https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#integration-properties
** You can search for spring.rabbitmq.xxx or spring.kafka.xxx properties
Stream specific RabbitMQ properties - https://docs.spring.io/spring-cloud-stream-binder-rabbit/docs/3.1.0.M1/reference/html/index.html#_configuration_options
Stream specific Kafka properties - https://docs.spring.io/spring-cloud-stream-binder-kafka/docs/3.1.0.M1/reference/html/index.html#_configuration_options

The most common property you would set is the location of the running middleware.
If a property to set it is called spring.rabbitmq.addresses or spring.kafka.bootstrap-servers then you should name the environment variable SPRING_RABBITMQ_ADDRESSES and SPRING_KAFKA_BOOTSTRAP_SERVERS` respectively.
cc @Buzzardo there are some documentation changes here

I get that I can set up an application that has a messaging endpoint to use with contracts.
I get that there's a triggerMessage() method to let me communicate with such an endpoint.
I don't know Python, so I can't comment on that code.
I did have a couple questions as I went along:
What setup steps do I need to do in Docker?
Are we going to have a Java sample? (Since Spring is mostly Java, that seems like something people would want.)

What setup steps do I need to do in Docker?

Set the env vars really. Also mind you that in the documentation we already have a whole chapter on how to configure the docker stuff. So this is just a flow with messaging basing on previously presented docker example.

Are we going to have a Java sample? (Since Spring is mostly Java, that seems like something people would want.)

With Java you don't really need to use Docker cause you can generate tests directly in your codebase

I would definitely add those bits to the docs. I'll read it again after a meeting, to see if I have any further ideas.


v2.1.3 - Two more bugs shaken out

Another v2 update
In testing v3 candidate, I've stumbled upon a couple of additional bugs in v2 upon which v3 is based (now rebased).
This release is in keeping with our plan is to continue to maintain v2 for those users who are not ready to upgrade to v3.
Details

b133b31 - bug: fixes a long-standing bug
17611ae - regression: fixed double-click logic; don't throw error on unknown cell editor
0576b50 - bonus: jsdoc comments documents CellEvent (finally)

@joneit Can you send us a timeline of your targeted release dates for v2.1.3 and 3.0 so we can prep on our end

@Dwaynekj I haven't found anything else since I posted the last 2.1.3 commit a week ago. Would be nice to see a couple of reviews but I'm planning to merge and release it this week (approvals or not), probably by EOD, Wednesday (Feb. 14).
Regarding version 3, I'm just filling in jsdoc comments and writing release notes. I expect to post it for review either EOD today or tomorrow. I'm going to walk @nmichaud through it today or tomorrow. Probably worth waiting for his review first.

@joneit Hey!
Coolios. And in terms of the the 3.0 tentative release date?

As for the bugs in this specific PR. How do I reproduce?

Re: 3.0, assuming reviewers like it, I'd love to do an alpha release by the end of the week.

@Dwaynekj Re: 3.0, assuming reviewers like it, I'd love to do an alpha release by the end of the week.

@Dwaynekj Regarding testing this PR, only the very first commit (17611ae) was a regression. I've added a bit more texture to the comments in the PR description (see); all the rest are just house-cleaning.


[ja]Updated debug-running-pod

Resolved the changes and updated the content/ja/docs/tasks/debug/debug-application/debug-running-pod.md as per instructed.
Resolved issue #38591

@YashPimple
Thank you for creating this PR.
It seems no problem about your commit, but deploy failed by Netlify.
I don't know what happend because deploy log is nothing.
Please try to force push without changing the contents in order to make the deployment process run automatically again.

@t-inu
I have opened a new PR for the above issue since the deployment failed due to Netlify. Please have a look at it.
PR #38909

@YashPimple I'll review that new PR. Closing this PR.
/close


WIP: Add test utils in testing image, change busybox to testing image in examples

Dockerfile: Add pmem-dax-check and fio bundle in -test image.
Changed image:busybox to pmem-csi-driver-test in deployment examples.
Resolves: #620

Implemented bullet points in #620, removing WIP from title, is this all now for this PR?


Remove slurmd restart cronjob

It wasn't working (grep -c inactive wasn't sufficient)
It has been implemented using SystemD in abb487f1

It generates an annoying syslog entry every minute!


Ktor Tutorial for Artisans (Laravel developer)

Develop a Ktor 1.5 tutorial for artisan, mainly focus on the following topics:

Ktor introduction

What's it?
Quick history for the name, the goal, the team
Main advantage (eg. light-weight)

Development environment

IDE with JDK
Ktor plugin

Project creation & dependency

Ktor project template
Gradle

Routing

Hello world app

Request & Response

The call object & application cycle
Retrieve params

Features

Add ContentNegotiation to return JSON response
Add `View to return HTML page

Exposed

Add exposed and mysql-driver dependency
Create schema for migration
Create DAO for CRUD

Retrospective

What we learned?
Similarities and Differences

I would recommend we all use an SQLite database so that users can have minimal environmental setup.

I would recommend we all use an SQLite database so that users can have minimal environmental setup.

Agree with you that we should make the environment setting as simple as possible. However, I found it's more common to use H2 in JVM ecosystem. Maybe we could introduce H2 in this article?


switched back to #import instead of @import module

Hello,
Can you switch back to the old-school #import? We have a project where 'modules' are disabled by some reasons and maybe we're not only one.
As far as I understand how it works, you don't actually need to use the @import keyword. Here is a good explanation:

If you opt-in to using modules, all #import and #include directives are mapped to use @import automatically. That means that you don't have to change your source code (or the source code of libraries that you download from elsewhere). Supposedly using modules improves the build performance too, especially if you haven't been using PCHs well or if your project has many small source files.

Thank you!
Artem

Sure, thanks for contributing!

:+1:


Create mockup of bill search component

Please do work for this task in a branch called issue-09.

Left Side - Departments
Navbar has a dropdown to sort by (XXX way)
Right of the nav bar is a search bar + dropdown (Search by description/Bill No/etc)
Then the search button to the right


The drop ball excample works not good

Hi, I followed the "Hello World" excample about drop a ball of fluid in the center of the fluid simulation domain, however the 29.ply model is not same as the given one.

(the model generated by my excample )

(the model in the readme example)

(the code in my test)

Thanks a lot, my test enviroment is Windows10, Intel Xeon E5-2650 and NVIIDA Quadro M5000. Actually the excample finally worked after another build through the repository.


Link for sample code is broken

The link for the sample code is returning 404
https://github.com/dahall/AeroWizard/blob/master/wiki

Sorry, Wrong link. Try it again.


Sort commands in pdc --help

JIRA: PDC-2059

Tests seems to fail with Python 3.x because relative imports are no longer allowed. So instead of import compat it should be from pdc_client import compat.

Actually, that's problem when I run tests with Python 3.6. Travis tests give different error.

OK, nevermind. Using from pdc_client import compat seems to fix the error for Python 3.4 too. Though the error is very cryptic. :)

@hluk cool. thank you very much :)

Looks good to me.

@hluk ok. fix it.


Hexadecimal parsing is buggy with number suffixes

Description
Parsing numbers in Lexer with a 0x prefix admits all alphanumeric characters, not just [0-9A-Fa-f]. This doesn't play well with number suffixes:
#box(stroke: 0x10pt, [b #sym.zws])

errors with
error: invalid hexadecimal number: 0x10pt
  ┌─ ..\test.typ:1:13
  │
1 │ #box(stroke: 0x10pt, [b #sym.zws])
  │              ^^^^^^

Fixing this for pt is easy, but we should also think about cm and deg et al. that start with valid hex characters.
Reproduction URL
No response
Operating system
Windows
Typst version

[X] I am using the latest version of Typst

what should the expected behavior be? I don't think it's reasonable to parse it as 16pt -- not that anyone would need such a feature, I think. Although if you really want you can write 0x10 * 1pt.

Number suffixes aren't supported for hexadecimal numbers. It's intentional that it allows everything alphanumeric because it arguably creates a better error message than stopping at the >f letter and leaving whatever comes after as a mess to the lexer that generates more errors.


Support for Obj-C

I would suggest adding @objc tags so that the library can be called from Obj-C. If you agree I could PR on this.

+1 I would find this incredibly helpful...


[bug]: swap doesn't work when xformers is enabled

From keturn in https://github.com/invoke-ai/InvokeAI/pull/1583#issuecomment-1366862535

@damian0815 I saw you pushed a fix for the cross-attention crash. Confirmed that it works here, thanks!
Unfortunately it only works if both xformers_memory_efficient_attention and attention_slicing are disabled. If either is enabled, it doesn't crash, but it silently fails to do its thing and just results in rendering the replacement prompt.
How would you like to handle this? Should setup_cross_attention_control disable those things? Or should we move on to using the 0.12.dev diffusers API first, and figure out something based on that? I'm looking forward to that in any case so we can get rid of the monkeypatch.

From damian in https://github.com/invoke-ai/InvokeAI/pull/1583#issuecomment-1368202719

@keturn so the monkey-patched InvokeAIDiffusersCrossAttention does its own slicing internally, using a technique with better performance than the diffusers attention_slicing functionality. if attention_slicing gets turned on and the user wants to do cross-attention control, maybe they should get a warning?
as for the xformers_memory_efficient_attention, yeah it's unsupported for now. this comment links to an xformers-compatible implementation that the author claims would be easy to wrap into a CrossAttentionProcessor - for reference the diffusers update to allow custom CrossAttentionProcessors (https://github.com/huggingface/diffusers/commit/4125756e88e82370c197fecf28e9f0b4d7eee6c3) was merged to diffusers main after the v0.11 tag, so it won't appear until v0.12. my thinking here is, it would be prudent to get the dev/diffusers branch into main before doing extra work enabling xformers - since xformers is currently unsupported in main, it's an extra concern for this PR that ought to be shuffled into the future.
fwiw patrick actually posted what looks to be a better (albeit pseudocode) implementation of cross-attention control than mine in the PR description.

from keturn in https://github.com/invoke-ai/InvokeAI/pull/1583#issuecomment-1368271212

Hmm, okay, I can respect a "current functionality before optimizations and new stuff" argument against scope creep. But with some concerns:

for several versions of diffusers, it had xformers enabled by default when available. Having swap silently not-work in those cases is bad. I'd say at a minimum we need to:

replace the current "if available: enable" code in our initialization code to always explicitly disable the incompatible features.
some kind of assertion that can detect whether the right thing was called. i.e. if it goes to apply a cross-attention control but no attention was ever wrangled, there's a problem we need to detect at some point. Whether that's an integration test or a runtime assertion.

"monkeypatch third-party classes" and "use a not-yet-released API" are both bad options for something we want to merge to main. Between the two, I think going with the not-yet-released API is better in this case. It won't be unreleased for long, and since it is being added specifically for our needs here, it'd be good to try out and see it needs any revisions.

Are you up for giving that 0.12.dev API a try? Or would you like me to take a crack at trying to translate the pseudo-code you mentioned to something that'll work with what we've got here?

there's a 0.12 implementation of cross attention .swap here #2385 - currently only tested/working on mac CPU, MPS i suspect is broken because of https://github.com/pytorch/pytorch/issues/91617 which is fixed in MPS upstream torch 2.0 but with no clear ETA when it will make it to torch mainline nightly

fixed by #2385


backport: ocsp: rotate certs of test data to fix flaky tests (#23635)

Commit Message: backport: ocsp: rotate certs of test data to fix flaky tests (#23635)
Additional Description:
See #23635
Risk Level: low.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.

cc @phlax

/retest

/retest

Required for: https://github.com/envoyproxy/envoy/pull/23639.


[Ci] write unit tests for php script & e2e tests for website itself

Write some tests for isInArea function

Unit tests for php done, e2e tests remaining


Support for Id_token validataion.

You need to validate all ID tokens on your server unless you know that they came directly from Google. For example, your server must verify as authentic any ID tokens it receives from your client apps.
We do not currently have support for token validation
I found a rather old GitHub project on how to achieve this.  gplus-verifytoken-csharp.

How is this coming along? any progress?

I am not really sure if this has even made the list yet
has it @chrisdunelm

This is on a TODO list ;)
But it won't be done until after the fairly major refactoring/retargetting in #977.

I did a own Implementation using the microsoft nuget for jwt. See the gist: https://gist.github.com/twaldecker/da0594baeef0e15466c68112ae375988

The method ValidateAsync in GoogleJsonWebSignature.cs doesn't seem to check if aud value in the ID token is equal to user's app’s client ID as described in the third step here: https://developers.google.com/identity/protocols/OpenIDConnect#validatinganidtoken.
Maybe the method should receive some sort of audience similar to how Java api's GoogleIdTokenVerifier does.

It appears according to the comments here and at #1026 that id_token validation has been implemented in dotnet. Is there any example or documentation on how to do it? It is not so clear to me how to make use fo the code checked in to fix #1026. Any help would be much appreciated.

Have you had a look at the tests 7n the pull request you linked?

@mikecg Once you have a string containing the id_token (an id_token is a JWT), pass that string into GoogleJsonWebSignature.ValidateAsync. ValidateAsnyc will throw an InvalidJwtException if this is not a valid Google-signed JWT.
See https://github.com/google/google-api-dotnet-client/blob/master/Src/Support/IntegrationTests/GoogleJsonWebSignatureTests.cs#L84 for an example of this in an integration test.

Thank you, I figured it all out. Appreciate the help!

GoogleJsonWebSignature.ValidateAsync  should support validating the aud: field in the token.
The validation thats going on now is signature and clock.   Suggest passing in the aud: to validate.
This is useful if an app receives a googleID token...the audience field needs to match the service name. Apart from manually creating an idtoken with the aud: field set, services like cloud Tasks and Cloud Scheduler automatically can emit an idtoken for a given audience.


Add import to image field snippet

When setting up the image field the first time, I ran into some problem that the get method was not defined.
Also, I removed some C&P text.

Good catch. Thank you!!


Error occurred while compiling with 'node:14.16.1-stretch-slim'

Arguments:
  /usr/local/bin/node /opt/yarn-v1.22.5/bin/yarn.js install

PATH:
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Yarn version:
  1.22.5

Node version:
  14.16.1

Platform:
  linux x64

Trace:
  Error: ENOENT: no such file or directory, open '/usr/local/share/.cache/yarn/v6/npm-<EMAIL_ADDRESS>

This error message looks like from yarn,please try to install again.


[Feature] Self-managed JupyterHub on EKS

Highly scalable deployment pattern for running JupyterHub on Amazon EKS with Terraform

Create a new JupyterHub add-on under EKS Blueprints repo
Create new deployment template for Terraform under https://github.com/awslabs/data-on-eks/tree/main/ai-ml/jupyterhub
Create a new README for deployment (Only deployment steps)
Add a new Website Doc with design diagram, deployment (refer to README here for deployment steps) and how to run sample tests etc.

Community Note

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

What is the outcome that you are trying to reach?

Describe the solution you would like

Describe alternatives you have considered

Additional context

Planning to work on this one.
I have a customer who use JupyterHub extensively and this will be of interest to them as well.

Closing this issue. First PR has been merged. You can find the docs here https://awslabs.github.io/data-on-eks/docs/blueprints/ai-ml/jupyterhub
We are planning to add more features to this blueprint as phase-2
1/ Use Cert Manager
2/ Use External DNS
3/ Use EFS CSI Driver - Enable add-on and create dynamic EFS volumes
4/ Use Karpenter to run JupyterHub workloads
5/ Update JupyterHub images to use PySpark, Python etc.
6/ Apache Ranger Server deployment for FGAC
7/ HiveMetastore server implementation for S3 data access

@vara-bonthu I saw that Karpenter seems to be managed now in the stack but EFS still is accessed through NFS protocol from PV/PVC and not the EFS CSI provider. Am I right ? Is it still planned to be included in future ? Is there any issue with the CSI ? Did I miss something ? 😅🙏


Update token timout return with null check exception.

I am currently replacing firedart auth part with this package (you can see my fork here).
Writing to cloud firestore works and I can even listen to changes (real-time stream).
After couple of hours of listening to changes (real-time stream) it is crashing from this package

Calling with autoRefresh = true

Now that the bug in HTTP has been solved this issue isn't fixed yet.
This issue occurs when trying to do HTTP send request after client has been closed, so we need to maybe stop the call or recreate the user or throw exception whenever that happen.

So, if I understand you correctly, your situation is as follows:

You create a FirebaseAuth instance with a dedicated client
You use that API to create a User, who auto-refreshes their credentials automatically
After some time, you close the originally used client
The next time the credentials are to be refreshed, it crashes.

Is that correct? If yes, why do you dispose the client. What would you expect to happen in this case?

I am not closing any client.
Only listening to real-time stream.

Then why is the client closed? The code where the exception occurs does nothing special, it simply sends a HTTP-Post request via the http packages Client to renew the idToken of the logged in account. So somewhere, that client must be closed...
You could try to set FirebaseAccount.autoRefresh to false and call FirebaseAccount.refresh() manually, this way you can react to the exception and recreate the account. Also, this might help in figuring out where the connection fails. For example, you could try to call refresh 5 minutes after the streaming has started, just to see if it happens then to.

Are you still having the problem?

The pull request is still in process

Whatever the problem is, I cannot reproduce it. I ran a small script, running for hours without problems, over multiple session renews. The code and the logs are added below:

Code:
´´´.dart
Future main(List arguments) async {
final client = Client();
final auth = FirebaseAuth(
client,
arguments[0],
);
final account = await auth.signInWithPassword(
arguments[1],
arguments[2],
);
final idTokenSub = account.idTokenStream.listen(
(event) => print('idToken: $event'),
onDone: () => print('idToken: DONE'),
onError: (Object e, StackTrace? s) => print('idToken: $e\n$s'),
cancelOnError: false,
);
final database = FirebaseDatabase(
account: account,
database: 'dart-firebase-rest',
client: client,
basePath: '/firebase_sync/${account.localId}/',
);
final store = database.rootStore.subStore(
path: 'renew',
onDataFromJson: (dynamic json) => json,
onDataToJson: (dynamic data) => data,
onPatchData: (dynamic data, Map<String, dynamic> changes) =>
throw UnimplementedError(),
);
final stream = AutoRenewStream(store.streamAll);
final sub = stream.listen(
print,
onDone: () => print('data: DONE'),
onError: (Object e, StackTrace? s) => print('data: $e\n$s'),
cancelOnError: false,
);
try {
await store.destroy();
// ignore: literal_only_boolean_expressions
while (true) {
await Future.delayed(const Duration(minutes: 5));
await store.create(DateTime.now().toIso8601String());
}
} catch (e, s) {
print('$e\n$s');
} finally {
await sub.cancel();
await database.dispose();
await idTokenSub.cancel();
account.dispose();
client.close();
}
}
´´´

Logs:
logs.txt

Ok so lets close it for now and I will reopen it in case it comes back.
Thanks


No binary package for Debian 10 'buster'

There is no 'td-agent' package for Debian 10 'buster'.

Since td-agent 4: https://github.com/treasure-data/omnibus-td-agent/issues/209
And this is not td-agent issue. Closed.


Bug: snapped kube-commander cannot find kubectl

Hi
Describe the bug
snap version of kube-commander cannot retrieve logs from a pod
To Reproduce

select a running pod
type 'L'
kube-commander shows an error:  kubectl: command not found

Expected behavior
kube-commander shows the logs of the pod
Note that logging works as expected when running kube-commander from the released tarball downloaded from github.
Screenshots or logs
Here's a sligthty edited logs output showing the error:
Executing command: /bin/bash -c KUBECONFIG=/home/domi/.kube/config:/home/domi/.kube/redacted-ovh.config:/home/domi/.kube/redacted-azure-config.yml kubectl --context redacted-azure-dev --namespace prod logs -c redacted-chatserver --tail 1000 --follow redactedchatserver-6c45ffbc9d-dh6wd
/bin/bash: kubectl: command not found
error executing command: exit status 127
Desktop (please complete the following information):

OS: Debian/unstable
Terminal emulator: konsole

Additional context

installed from snap
kubectl is available in /usr/bin/kubectl and installed with snap

All the best

Thank you for the report
Seems to me that snap's way to launch applications has something to do with that. Looking into it

I had to switch kube-commander to classic snap grade to make it work properly. This means that it will have to be reviewed manually by Snap Store team and it will require --classic flag during installation.
I'm keeping this issue to keep track of the review process

I filed a review request: https://forum.snapcraft.io/t/classic-confinement-for-kube-commander/18456

For what it's worth, some alternatives to using --classic are:

include kubectl in your snap
use kubernetes API to get logs (and perform the other operations where kubectl is required)