requestTrackingAuthorization does not generate dialog

Unfortunately, requestTrackingAuthorization does not generate the dialog shown here: https://twitter.com/rdlabo/status/1301392984026394628. I tried in simulator as well as on real device with the latest version @capacitor-community/admob v1.2.5. Tried to submit the app but Apple rejects because no dialog is created, see screenshot: https://i.imgur.com/Vfa1is0.png
Any suggestions on how to generate the dialog? Is it even expected to be created when testing the app on device?

I also the same problem. Apple rejected me because no dialog is created.  Anyone has solution on this?

I have just resolved this problem by update my Xcode. It seems this function required latest version of Xcode

I have just resolved this problem by update my Xcode. It seems this function required latest version of Xcode

@looklookson 's comment is right. requestTrackingAuthorization required iOS14: https://developers.google.com/admob/ios/ios14
I will close this issue. Thanks.

@looklookson 's comment is right. requestTrackingAuthorization required iOS14: https://developers.google.com/admob/ios/ios14
I will close this issue. Thanks.

@looklookson does the request appear every time you reinstall the app?

@looklookson does the request appear every time you reinstall the app?


"Expected preloadedQuery to not be disposed yet." error

First of all, thank you for the library 🙏
For one of my component, I'm using the useQueryLoader + usePreloadedQuery hooks.
Everything was working flawlessly until I updated from React 17.0.2 to 18.1.0. I started getting:
next-dev.js?3515:25 Warning: usePreloadedQuery(): Expected preloadedQuery to not be disposed yet. This is because disposing the query marks it for future garbage collection, and as such query results may no longer be present in the Relay store. In the future, this will become a hard error.
    at eval (webpack-internal:///./components/index/UserBeats.tsx:22:26)
    at LoadableImpl (webpack-internal:///./node_modules/next/dist/shared/lib/loadable.js:101:38)
    at Suspense
    at eval (webpack-internal:///./components/index/IndexLoggedIn.tsx:120:69)
    at LoadableImpl (webpack-internal:///./node_modules/next/dist/shared/lib/loadable.js:101:38)
    at Suspense
    at eval (webpack-internal:///./pages/index.tsx:45:73)
    at div
    at div
    at eval (webpack-internal:///./components/nav/NavWeb.tsx:50:27)
    at RelayEnvironmentProvider (webpack-internal:///./node_modules/react-relay/lib/relay-hooks/RelayEnvironmentProvider.js:21:24)
    at FirebaseContextProvider (webpack-internal:///./lib/firebase.tsx:125:29)
    at MyApp (webpack-internal:///./pages/_app.tsx:112:27)
    at ErrorBoundary (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:20746)
    at ReactDevOverlay (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:23395)
    at Container (webpack-internal:///./node_modules/next/dist/client/index.js:323:9)
    at AppContainer (webpack-internal:///./node_modules/next/dist/client/index.js:825:26)
    at Root (webpack-internal:///./node_modules/next/dist/client/index.js:949:27)

It's not crashing or anything, it's just a warning and it actually disappears when going to prod, but I was wondering if it would ring a bell to you. I really cannot find anything online :/

I haven't seen this error in production mode at all, only sometimes in dev when interrupting the loading process. That said, we're still on React 17 at Revere so it makes sense. I'll try upgrading soon and update here!

If you are using strict mode react renders the component twice. If you use an effect to dispose of your query you might get this error. In that case in your effect fetch the preload the query again.
  useEffect(() => {
    if (_data.isDisposed) revalidate(); // this function preloads the query again

    return () => _data.dispose();
  }, []);

We have this issue too since we started using React 18 with strict mode.
@phikes thanks for your input, a quick search in this codebase highlighted this piece of code:
https://github.com/RevereCRE/relay-nextjs/blob/d9ad8aafba17ec8bc61f4bc054e892b6bfbe9b1f/relay-nextjs/src/wired/component.tsx#L114
Would this be the cause? the <Component child would receive a disposed reference to preloadedQuery when react strict mode renders twice.
however the effect that disposes the query on unmount also calls load on mount, so I am not sure if the issue comes from here.

I am not sure, I actually just stumbled across this issue. I had the same problem with another stack. But this looks very much like the culprit to me, yes.

We have a new version we've been testing internally that replaces this code path I'll work on releasing soon!

@rrdelaney Any update on this issue?

@rrdelaney Any update on this issue?

Hey Jason, we've removed that exact codepath in 2.0. Are you continuing to see the issue after upgrading?


Fixed problem related with dataset privacy

Dataset view:

Share map view:

Also, privacy tags have been changed to have the same size (the big ones), looks ok @josecruz?

cc @josecruz @piensaenpixel
CR: @javierarce
Fixes #9465.

Awesome @xavijam. If we're gonna change privacy tag we'll need to replace it on the Dashboard (basically on every dataset and map list) so we maintain consistency between tags, what do you think @saleiva ?

About the dashboard change, yeah, it will happen eventually.

👍  (except for a comment)


Log "tier" telemetry in all Cody JetBrains events

Purpose:

To track the number of "mDAU", or monetized DAU (pro + enterprise DAU), which is going to be a top-line product metric for 2024.

Requirements:

For all VS Code Cody telemetry, add what tier the user is in to the public_argument metadata field.
tier = free | pro | enterprise

This has already been approved by @kelsey-brown

tier = free | pro | enterprise

FYI it was implemented a bit differently by @philipp-spiess and to remain consistent I followed the same pattern in jetbrains:
enum CodyTier {
    Free = 0,
    Pro = 1,
    Enterprise = 2,
}


Master

Caption For Documents

does it work? because it's not documented

ya sure, i tried it on these channels:
https://telegram.me/TheSeriesChannel
https://telegram.me/TheMovieChannel
check them

https://api.telegram.org/bot13245234523458:wertwertwertwertwert/sendDocument?chat_id=@TheMovieChannel&document=BQADBAADhgQAAnkG_QABba5ab5ID2EEC&caption=testCaption&performer=xxx

make sure code is OK! please :)


Return promise on send message

 [RabbitMQ lib] job.save does not wait for the job to end up in rabbit before resolving

I think it might be a better idea to edit the TS file and generate the js file after to avoid bad diffs with the upstream repository.


use externalTranspiler before doing diffs for status

Create new function getRawOutputRetranspiled with same interface
as getRawOutput except that it returns a Promise.
This function calls getRawOutut, then passes the result through
runExternalTranspiler so that babel, if configured, is applied.
Call/use this new function in getOutputJsStatus.
Net result: people using babel are not constantly being told their
JS is Outdated.
Closes #736

Doh. wrong branch. I changed the function name.


Add github release yml file

This adds auto formatting to the Releases github page

Reference for the curious:  https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

illustrative example in raft: https://github.com/NationalSecurityAgency/raft/releases/tag/0.18.0


Bevy 0.2 compatibility

I'm getting this error:
the trait bevy::prelude::Plugin is not implemented for bevy_prototype_input_map::InputMapPlugin

Could this be because you have bevy 0.1 in your Cargo.toml, i.e. a version mismatch?

Yeah, I believe that's the issue.
I spent a few minutes looking at this. Seems like the serde derives were omitted from the gamepad types in Bevy. I copied them from keyboard.rs and submitted https://github.com/bevyengine/bevy/pull/583 which seems to eliminate the compilation errors in bevy_input_map.
As an aside, it's hard to spot compiler errors amid the warning spam. I'll take a crack at fixing those if no one else gets to it.

@ndarilek Is right bevy Gamepad does not support serde at the moment which is required for JSON/RON Binding support. There is an on going PR for this #524. But I am not getting enough time to finish this PR at the moment.

Actually @ndarilek PR might be enough at the moment since I have create custom serde util methods which works around the need to serialise struct tuples. I have posted a comment on  bevyengine/bevy#583, tagging Carter lets see how he wants to proceed.

Closing issue. As of v0.1.4, bevy 0.2 is supported. I have added release tags to identify stable checkouts. Master is where active development happens, I expect it to break often. Tags will allow visitors to identify stable commits.


Fix allreduce for BF16 and ZeRO0

This PR fixes an issue with allreducing for ZeRO0 + BF16. (This replaces #5154)
DeepSpeed uses BF16_Optimizer when ZeRO0 and BF16 are enabled. The optimizer accumulates gradients on FP32 buffer soon after a backward pass completes. However, DeepSpeed engine performs allreduce on BF16 gradients.
This PR fixes the issue by performing allreduce on the FP32 buffer. It also eliminates an assertion that prohibits BF16+PP+Z1, which is actually runnable.
This shows loss curves of the following conditions:

BF16/Z0,Z1,Z2,Z3/NoPP
BF16/Z0,Z1/PP(2 stages)
(all used 8GPUs, gradient accumulation step: 4)

I meet a NCCL timeout when trainning Qwen-72B with bf16, zero 1 and pipe. https://github.com/microsoft/DeepSpeed/issues/5384


fix: remove hardcoded extractor refs

@alexmarple - This is ready for review now. I manually tested that the links render correctly.

@aaronsteers Merge away!


support Lightgbm

As we know Lightgbm is now becoming more and more popular for its outstanding efficiency. Is it possible to add a new feature so that LightGBM's importance can be supported? That would be tons of help;
thanks a lot!

it's totally possible and on my list. :)

@Far0n Looking forwards to lgb support


Fix function comments based on best practices from Effective Go

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared.
From effective go.
I generated this with CodeLingo and I'm keen to get some feedback, but this is automated so feel free to close it and just say opt out to opt out of future CodeLingo outreach PRs.

One of the fix ups updates the tense and reads well.
But the other basically just add colons to conform to standards and is arguably less readable. Also, it clearly caught a bug in my code - I was expecting the first line of the comment to be an explanation of the function, but actually it's just a TODO. I'm working on a fix to format it more nicely in this case :smil'
Let me know if you think this is valuable! :smile:

Haha, just noticed that this is deprecated! Closing.


Change attribute name to match HTML naming convention

Published as v3.1.0 as messageId still works as the attribute name


added logpdf.(u, v) and logpdf.(u, raw) methods

I feel that PR #411 left out some methods. I feel these methods are needed since we want logpdf to have similar functionality with pdf the difference being just the log.
So this PR Adds logpdf.(u::UniFinArr{S,V,R,P,N}, v::AbstractArray{<:CategoricalValue{V,R},N}) and
logpdf.(u::UniFinArr{S,V,R,P,N}, raw::Union{V,AbstractArray{V,N}}) methods.
Feel free to close this if u feel these method are not needed.

Makes sense to me.
@cscherrer Can you review this?
cc: @ablaom

Codecov Report

Merging #418 into dev will decrease coverage by 0.44%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##              dev     #418      +/-   ##
==========================================
- Coverage   81.62%   81.17%   -0.45%
==========================================
  Files          38       38
  Lines        2699     2678      -21
==========================================
- Hits         2203     2174      -29
- Misses        496      504       +8

Impacted Files
Coverage Δ

src/univariate_finite/arrays.jl
91.93% <28.57%> (ø)

src/sources.jl
78.37% <0.00%> (-5.84%)
:arrow_down:

src/composition/models/inspection.jl
95.23% <0.00%> (-4.77%)
:arrow_down:

src/measures/finite.jl
93.75% <0.00%> (-2.85%)
:arrow_down:

src/data/datasets.jl
86.11% <0.00%> (-2.78%)
:arrow_down:

src/composition/learning_networks/inspection.jl
81.81% <0.00%> (-0.80%)
:arrow_down:

src/composition/learning_networks/nodes.jl
67.66% <0.00%> (-0.48%)
:arrow_down:

src/hyperparam/one_dimensional_range_methods.jl
91.76% <0.00%> (-0.38%)
:arrow_down:

src/resampling.jl
85.66% <0.00%> (-0.36%)
:arrow_down:

src/composition/learning_networks/machines.jl
92.03% <0.00%> (-0.21%)
:arrow_down:

... and 5 more

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 0804910...668fa3d. Read the comment docs.

@cscherrer. I made some changes. The previous logpdf methods mutated the original array used in construction of UnivariateFinite

Sorry, I don't understand. Computing the PDF allocates an array that's never used again, right? Why not reuse that memory?

Oh, or does pdf.(...) not allocate with the broadcasting optimization?

Oh, or does pdf.(...) not allocate with the broadcasting optimization?

Yes. In some cases it doesn't allocate, while in other instances it does allocate. I just made a commit that takes both cases into consideration

@OkonSamuel Thanks for this PR. Looks good to me.

@ablaom. I need to discuss some further changes i wanted to make to this PR with you before this was merged.

No, I would agree this is not desirable. I would welcome a PR.


Fuse mapM_/map seems to drop sort

Recent hlint 3.1.3 and 3.1.4 at least seems to suggest map refactoring which drops sort from my code:
Commands/Spec.hs:332:5-120: Warning: Fuse mapM_/map
Found:
  mapM_ (putHdr "BuildRequires")
    $ (sort . map showRpm)
        (map (RpmHsLib Devel) testDeps ++ map RpmOther testsuiteTools)
Perhaps:
  mapM_
    (putHdr "BuildRequires" . showRpm)
    (map (RpmHsLib Devel) testDeps ++ map RpmOther testsuiteTools)

It looks a bit suspicious to me: could this be a bug?
Also I want to take this opportunity to thank you for hlint (and all your other awesome Haskell work), really amazing.

Thanks for the report! Yep, a bug, and a super serious one! I can reproduce this using the classic map/map fusion hint:
Sample.hs:1:8-32: Suggestion: Use map once
Found:
  map f ((sort . map g) xs)
Perhaps:
  map (f . g) xs

Eek.

So the problem was that HLint knows you can match (sort . map g) xs against map g xs provided you remember to put sort . back at the front. Of course, putting sort . back at the front relies on you being at the outside of a match (otherwise you have nowhere to put it). There were two bugs:

I didn't check if you were at the outside of a patch, which was trivial to add with a conditional.
In some cases, I threw away the extra piece, which is inherently dubious - there should be no extra piece, but if there is, throwing it away is definitely wrong. Therefore I've added a check everywhere I throw away extra.

Quite amazed we didn't have any test that caught this. A little confused by what the code does (there seems to be a fair bit of duplication). No idea when this got introduced - could have always been there!
Will be fixed in the next release, which I'll try to get out tonight.


Make validation optional for non-clipped geometries

Right now, all geometries are cleaned by validate.CleanGeometryGeom. This might not be necessary if all geometries are already valid and the geometry is within a tile (i.e. no clipping).
How about a dont_validate option analog to dont_simplify?

I think this is something we can consider after we have the makevalid optimized and cannot get better performance. (I could be convinced otherwise.)
Yeah, there are plans later to have an IsValid function and to do a faster clipping on it. Right now I'm running everything through it because of the clipping, and to really test out the make valid functions. Also, I think there are some issues with the old clipping code:
https://github.com/go-spatial/tegola/commit/1898434b7bbf247304ab5fe2fc9c3a5598b194d9
Cutouts that fall on the boundary of the clip region. I believe this is because I'm clipping each ring individually instead of considering the cutouts when I clip the main ring. All of this is solved by the current make valid process. Generating better polygons. Ultimately I think it's better to get the performance to be the best we can before we consider this option.
The big problem I'm having right now is trying to get my head wrapped around the Triangulation routines. How a QuadEdge works, and why we are seeing issues with it.

I totally understand!
QuadEdges are all greek to me. Are there any tests we can port to validate the code? Maybe #497 helps to narrow it down.


cant find event name

when trying to start a event, even the default ones when installing the plugib it says it cant find the event, i restart server and it will say plugin started but when round starts it is just a default round. ):

fixed


BOT framework :isTyping not working suddenly  in Web Chat Channel

typing working in emulator and direct line
Web chat initial for some days its worked but now suddenly not working in Web Channel
Code:
public async Task Post([FromBody]Activity activity, CancellationToken token)
{
if (activity.Type == ActivityTypes.Message)
{
using (var scope = DialogModule.BeginLifetimeScope(Conversation.Container, activity))
{
var connector = new ConnectorClient(new Uri(activity.ServiceUrl));
Activity isTypingReply = activity.CreateReply();
isTypingReply.Type = ActivityTypes.Typing;
isTypingReply.Text = null;
await connector.Conversations.ReplyToActivityAsync(isTypingReply);
}
}
}
please let me know the fix

please  help me on this

@Suneethae7 We tested and looks like it's not something on the Web Chat component side. We just added a new test (#807) to ensure we will show the typing indicator when the server instructed us to do so.


Ask for permission without calling 'authenticate'

Hi, I believe there is no way to do this currently, so this is a feature request. We have a settings page in our app where we ask users whether they want to use biometrics or not. If they enable, we call authenticate on app login and FaceId permission is asked here. It would be good to have a way to ask for FaceId permission in settings rather than the login page when they actually attempt to use it for the first time. I believe this would improve the UX. Thanks in advance 🙏

The plugin has no control over the UI of your app. If the user has not enabled biometric login in the settings, you shouldn't be calling authenticate during login.

Let me rephrase: I do not want the plugin to control my app. I just want to be able to use the plugin to ask for system level biometrics permission. For example, on iOS, when I first call authenticate, a native popup shows up and tells: "MyApp would like to use FaceID, do you want to allow?". I want to be able to do this without calling authenticate. Because it becomes weird if a user allows biometrics in my app settings (not in system settings) and then they go to lock screen and rejects it. Or, let's say they allowed it both in system and app settings but user decided to go to system settings and remove the permission. I think it would be good to add hasPermission and requestPermission methods in that case

when I first call authenticate, a native popup shows up and tells: "MyApp would like to use FaceID, do you want to allow?". I want to be able to do this without calling authenticate.

Can't be done. That is a system-level prompt that only appears the first time the user tries to authenticate with FaceID.

Because it becomes weird if a user allows biometrics in my app settings (not in system settings) and then they go to lock screen and rejects it.

That's why you should be calling checkBiometry before even allowing the user the option to enable biometry in your app. If it isn't enabled or the user isn't enrolled at the system level, you shouldn't be offering the option in the app.

let's say they allowed it both in system and app settings but user decided to go to system settings and remove the permission. I think it would be good to add hasPermission

That's why you need to call checkBiometry (which does exactly what your proposed hasPermission would do) on app resume. Please see the demo app for examples, I handled this there.

We are getting inconsistent result withcheckBiometry. For some devices, it returns false even though device has the hardware and is enrolled. We are running on Capacitor 3. We are considering to update to Capacitor 4 if it would help. What do you suggest?

Please open a new issue ("Inconsistent checkBiometry results") with more details about the exact model and OS of the devices, as well as what kinds of biometry the devices support.

@yucehasan I can't help you if you don't give me more info.

@aparajita I am revisiting my code to make sure problem is not on my side. So far, it looks like the plugin is working fine. I will create new issue if I find anything. Thanks for your attention.

The plugin is just reporting what the OS says, so it can't lie. The only possible issue I can think of is Android devices that have more than one biometry option, in which case I only report what the system considers the primary biometry.


Enable pass through mode

It should be possible to start kelon in passthrough mode, which ensures, the user can test his policy changes without affecting his application. The passthrough mode will log every decision and can be examined for errors or similar. The benefit with this is, that the user can test everything on real data.

Depends on #79


Formatted image file data structure that breaks down by subdir

New utility method for the web app, which sorts image files into dicts where the subdir is the key
In the web ui, display each subdir in a table nested in a details tag.
Allow for picking destination subdir when uploading files
Style the expandable details blocks in the images table
Add a check for ~ paths to the is_safe_path() utility method

All looking good!


bug(docs): reserved keywords are not reserved

Bug Report
Cairo version:

Current behavior:
According to the documentation, the following keywords are reserved for future usages:
as
assert
do
dyn
extern
let
macro
mod
move
ref
Self
self
static_assert
static
super
try
typeof
unsafe
where
while
with
yield

as should be moved to "Strict Keywords", and the rest of the keywords are not reserved. It is perfectly possible to create the following program with a variable named, for example, with.

Expected behavior:

Steps to reproduce:

Related code:

fn main() {
    let with = 3;
}

Other information:

Is this still an issue? If not what is the proposed solution? do we include these as keywords in the parser?

do we include these as keywords in the parser?

👍🏻 This should happen IMO

I'll draft out a PR for this.

@cwkang1998 i think this section in the docs has been updated since I opened the PR

@cwkang1998 i think this section in the docs has been updated since I opened the issue

Its updated in cairo book: https://book.cairo-lang.org/appendix-01-keywords.html
but not at the site: https://docs.cairo-lang.org/language_constructs/keywords.html
I have not yet tried to use the future reserved keyword as variables yet, but if they are still not restricted then I think restricting them in the compiler would be nice too.

Interesting, it looks like the changes merged in this PR https://github.com/starkware-libs/cairo/pull/4009 have not been reflected in the docs website?


Embedding set weighs

Hello,
thanks for creating the great Keras!!
I have one issue:
I create weights with np.zeros
    embedding_matrix = np.zeros((max_features , embedding_dims))
Then I use
e = Embedding(
                  max_features,
                  embedding_dims,
                  input_length=maxlen,
                  weights=[embedding_matrix],
                  trainable=False,
                  )

And I get the error:
ValueError: You called set_weights(weights) on layer "embedding_1" with a  weight list of length 1, but the layer was expecting 0 weights. Provided weights: [array([[-0.01543641,  0.00745765,  0.0926055 , .....
If I create the Embedding without setting the weights and query the weights with w = e.get_weights(), w is an empty list. What am I doing wrong?
Thanks a lot,
Ernst

I was having the same issue a few hours ago. A reinstall of Keras fixed the issue. See if that helps.

Nilabhra,
thanks a lot for your maii! I uninstalled Keras and installed a fresh git clone, but the problem still persists.
Kind regards
Ernst

Removed Keras and installed Keras with pip, and now it works. It looks like there might be a bug in the git master branch.

Yes, I did the same. I am sorry, I should have mentioned that I installed from pip the second time. This is a serious problem. @fchollet has it been patched in the master branch?

I had the same issue, and I install and reinstall keras several times ,bug issue still there ! Can anybody who solved the issue give some suggestions or share some tips ? Thanks

Same issue. Seems only exists on 1.2 version, as I resolved it by installing a previous 1.1 version.

It seems that when trainable=False, weights and non_trainable_weights will both be [], hence set_weights() would raise an error. But I am not sure why weights or non_trainable_weights are [] when trainable=False, probably @fchollet can take a quick look?

@chentingpc I did a quick try, seems issue still there, I use version 1.2 and simply do pip install --upgrade keras . By the way, which backend did u use. My setup is : tensorflow under version  0.12.0-rc1

@stone8oy You may need to install the most recent commit. You can do so by git clone the repo, and use command python setup.py install. It works for me on tensorflow backend.

Solved,thanks a lot @chentingpc

@chentingpc I had the same issue. I used Theano as the backend. My keras version is 1.2.0; and the theano version is 0.8.2

@xiaoleihuang
Have you tried to install latest commit ?
As @chentingpc said, you can install latest commit by use command pip install git+https://github.com/fchollet/keras.git or the way provided by @chentingpc.
In my situation, it fixed this issue.

I think I have this same problem. As an example if I do
import numpy as np
from keras.layers import Convolution2D, Input

x = Input(shape=(10,10,3))
x = Convolution2D(16, 5, 5, weights=[np.zeros((3,5,5,16))], border_mode='same', trainable=False, bias=False)(x)

with keras 1.2 I get the error
ValueError: You called set_weights(weights)on layer "convolution2d_1" with a  weight list of length 1, but the layer was expecting 0 weights. Provided weights: [array([[[[ 0.,  0.,  0., ...,  0.,  0.,  0.],
Sounds like I it is fixed in the master branch.

I have the same issue
I upgrade to master branch  using
pip install git+https://github.com/fchollet/keras.git --upgrade
But I still the error:

ValueError: You called set_weights(weights) on layer "predictions" with a  weight list of length 2, but the layer was expecting 0 weights. Provided weights: [array([[-0.06838475, -0.01250052, -0.04821445, .....

 old_config = old_predictions.get_config()
 new_config = dict(old_config)
 new_config['output_dim'] = new_config['output_dim'] + 1
 new_predictions = layer_from_config({'class_name':type(old_predictions),'config':new_config})

Note that for this layer: trainable is True:
The full config itself is:

{'W_constraint': None, 'b_constraint': None, 'name': 'predictions', 'activity_regularizer': None, 'trainable': True, 'init': 'glorot_uniform', 'bias': True, 'activation': 'softmax', 'input_dim': 4096, 'b_regularizer': None, 'W_regularizer': None, 'output_dim': 103}

I solved this problem by updating keras version 1.2.2

I have faced a similar problem and found the solution is to add the layer to an existing model first, and then invoke set_weights. So for your example. I propose to do the following:
model = Sequential()
# create other layers
...
e = Embedding(
                  max_features,
                  embedding_dims,
                  input_length=maxlen,
                  weights=[embedding_matrix],
                  trainable=False,
                  )
model.add(e)
e.set_weights(weights)

Although this thread is too old, I still feel like I should point out how to fix this error.
The problem can be solved by first building the embedding layer and then assigning the weights using set_weight
e.g
embedding_layer =  tensorflow.keras.layers.Embedding(vocabulary_size, embedding_dims)
embedding_layer.build((None, ))
embedding_layer.set_weights(your_embedding_matrix)
embedding_layer.trainable = False


Setting the SHUFFLE parameter on the Blosc filter causes an error

The SHUFFLE parameter is also picked up as the value for COMPRESSOR, and it isn't a valid value for the compressor parameter.
This results in the exception
Exception thrown: 'System.Exception' in PureHDF.Filters.Blosc2.dll
The value of the filter parameter 'shuffle' must be of type String.

While testing locally, https://github.com/Apollo3zehn/Blosc2.PInvoke/issues/1 meant the library failed to load after this point


Consider relicensing under more standard license

Hi, thanks for a great library.
I'd like to use this project for configuration file of http://github.com/3scale/apicast.
The Happy License sounds nice, but would be easier to rely on something more standard like the MIT License.

subject to the licensee inflecting a positive message
unto someone. This includes (but is not limited to): smiling, being nice,
saying "thank you", assisting other persons, or any similar actions percolating
the given concept.

Is quite debatable in my opinion and won't pass a corporate legal team.

Yes, I agree. I chose that license years ago before I knew much about licensing. This is something I've wanted to change but haven't tried to do it until someone asked. I'm just unsure what the standard procedure for changing license terms is.
If you have any advice or tips, let me know. I've wanted to do this but I'm unsure how.

Thank you.
I've seen https://github.com/Safari-FIDO-U2F/Safari-FIDO-U2F/issues/20 recently.
I'd say that you are the only major contributor. Other changes have been trivial.
So it should be just matter of changing the license and maybe updating rockspec to mention the new license.

Fixed in 75d30d2.
I'm considering this a "breaking API change" so I bumped up to version 2.0.0. It's not exactly an API change, but it is potentially breaking in the rare case that MIT doesn't fit someone's needs but the old license does.

Thank you so much for such quick response!


Add support for tab tearoff and tab merge

I'm repurposing this for tab reordering and demoting it to a Task. We'll track the (much larger) workitem to do tab tearoff as a deliverable for vBacklog.
Notes/reasoning:

Tab reordering is easy.
Tab tearoff requires us to answer the following questions:

WT.exe is a multi-instance app. How do we drag tabs between different processes?

Should WT be multi-instance? We may want to single-instance it.

If we want to single-instance it we need to design "new window" (part of #1051)

We still need to design "new window" for tearoff-without-merge because we need a drop target for the old tab.

Originally posted by @DHowett-MSFT in https://github.com/microsoft/terminal/issues/443#issuecomment-501928756

also to have a sort of way to manage many open tabs... If I have 3 WSL tabs 1 cmd and two powershells tabbed it get's out of the UI at the right side of the tab bar (so I can't close the last tabs unless I close the first ones).

This would be so useful. I constantly open new tabs on some focused work, start splitting panes within the tab, and then at some point decide to move the whole tab and panes (right now I just recreate the panes and their directories from scratch) to a new window in a new virtual desktop.

Hi,
Any progress on this?  Just wanted to say I find this to be very useful.
Thanks for all your hard work on this product!

Thanks for asking! Unfortunately, there hasn’t been any progress. When there is, this issue will be the first to be updated about it.

Thanks for the info!  Okay I'll be following this issue :)

@DHowett-MSFT
Whats about to use a similar technique like Chrome does ?
Like wt.exe can create child processes - And when your kill wt.exe, everything will be also killed due the process as child.
So, the Main Profil will be the "father" of the following child process's when a tab gonna be deattached
Was a lightning idea! - while i was looking for something complete different.

I just tried to tear a tab off a window in the Windows Terminal Preview version and was unable to. That led me to searching for this issue.
Here's my use case: I am trying to demonstrate connecting two separate tmux clients to the same session, and running at different window sizes. In order to effectively do this, I need to resize one tmux window to separate dimensions from the other one. Since both my Ubuntu WSL tabs were running in the same Windows Terminal window, I was unable to do this. Hence, I tried to "tear" one of the existing tabs off into its own Windows 10 window.
This is where I got stuck, and had to open a brand new Terminal window instead, and then open up an Ubuntu tab in that window.
The work-around isn't hard, but it's just convenient to be able to tear off existing tabs, just like you can in Google Chrome.

Moving tabs to a different window is important.
I never use Edge, I am a Firefox fan boy (privacy, sharp fonts, amazing dev tools and so on ;-)). But I just tested to move a tab to a different Edge window. It works! Well guys, I am sure you can handle this for Windows Terminal too! =)

Moving tabs to a different window is important.
I never use Edge, I am a Firefox fan boy (privacy, sharp fonts, amazing dev tools and so on ;-)). But I just tested to move a tab to a different Edge window. It works! Well guys, I am sure you can handle this for Windows Terminal too! =)

I need this so much.

Tab tearoff works with Konsole and web browsers which is why I expected this to work.
Interestingly, when I tried it out with other multi-tabbed applications(e.g. Kate) it didn't do it as I expected.
Regardless, it would be useful to drag out tabs to different windows to help organise processes.

Yes, this is an important feature. Please add support. Thanks! 😄

I'd be curious how many people are subscribed to this thread. Browsers have trained us how tabs are supposed to work, and so it's really unexpected when a tool like Windows Terminal has them but doesn't behave like it. Actually, given this is almost 2 years old, there's also a layer of sadness I think people feel that this kind of table stakes feature would be left by the wayside so long.

Listen here pal. This hasn't been deprioritized, this has literally been my main priority for the last basically 12 months now. I've been researching. I've been prototyping. I've been writing specs. There has been a lot of planning that's gone into this, to make sure it works, and works for all the different scenarios we have in mind in the Terminal. Now that we've got a lot of the other foundations out of the way, I'm finally starting to get close to landing this. So I'd appreciate your continued patience while we work on this.
As always, we'll post here when there's an update to share.

"Listen here pal." wow, how condescending. I noticed I had an unknown prejudice against this guy, so looked around for more comments to better inform myself and hopefully change my mind and this is the first one I saw. No need to look further.  Get a grip! I may be toxic myself at times (ok, most of the time), but I'm a user. You are a project member and, apparent, MS employee. Just, wow! Take a course on community management or get out of the public eye.

I appreciate that the original comment was worded more strongly and that it may have been a bad day/week for both/either Mike or Erik. I'm also locking this because I want to keep it on-topic -- not to suppress discussion, but because these discussions are never fruitful.

More specific details, including my todo list are in #5000. I'm hoping to do the control settings rewrite this release (dev/migrie/oop/ragnarok), and hopefully some of the other foundation work before the end of the year (dev/migrie/oop/infinity-war). Hopefully we can get "move-pane -w <id> to move a pane/tab to another Terminal window" early next year, and followed shortly by tearing actual tabs out. This is still my main priority, just one that keeps getting sidelined by other things that can ship in a single release cycle. We've got the end of the year coming up and things always slow way down around then, and there's some time dedicated in the near future to improving our tooling (which should help accelerate overall code velocity)

I just tried to drag a tab from one WT to another, fully expecting it to work. And I ended up here! :-) Another big thumbs up from me for this feature, looking forward to it, it will be really useful.

期待这个功能的进展

I hope that this feature will not be limited to Windows 11 and will be backwards compatible with Windows 10. A lot of businesses and users are still on Windows 10 and likely will be for the time being.

@MattBDev Don't worry, no part of how I plan on implementing tearoff is restricted to Windows 11. Something quite dramatic would have to come up in the next couple months to change that.

Still waiting for this feature in August 2022...

My thoughts exactly...
On Tue Aug 2, 2022, 02:23 AM GMT, paulbrzeski @.***>
wrote:
Still waiting for this feature in August 2022...
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/1256#issuecomment-1201941157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU3BT4VV6BZ4BUZQSEUCTTVXCBDFANCNFSM4HYCMZIQ
.
You are receiving this because you commented.Message ID:
@.***>

This is literally being actively worked on. See https://github.com/microsoft/terminal/issues/5000#issuecomment-1185447944 for the latest status update.

You literally just marked my honest opinion as spam. WTF
On Tue, Aug 2, 2022 at 3:45 AM Mike Griese @.***> wrote:

This is literally being actively worked on. See #5000 (comment)
https://github.com/microsoft/terminal/issues/5000#issuecomment-1185447944
for the latest status update.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/1256#issuecomment-1202320209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU3BT7INVNOP2IPTQESCEDVXD34VANCNFSM4HYCMZIQ
.
You are receiving this because you commented.Message ID:
@.***>

This issue was opened 3 years ago. I think community upset over it is
justified, and marking that organic discourse as spam is at best flat our
wrong, and at worst indicative of a seriously dysfunctional corporate
culture at microsoft.
On Wed, Aug 3, 2022 at 1:37 PM Erik Neff @.***> wrote:

You literally just marked my honest opinion as spam. WTF
On Tue, Aug 2, 2022 at 3:45 AM Mike Griese @.***>
wrote:

This is literally being actively worked on. See #5000 (comment)
https://github.com/microsoft/terminal/issues/5000#issuecomment-1185447944
for the latest status update.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/1256#issuecomment-1202320209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU3BT7INVNOP2IPTQESCEDVXD34VANCNFSM4HYCMZIQ
.
You are receiving this because you commented.Message ID:
@.***>

I collapsed the comments because they did not constructively contribute to the conversation at hand. If you'd like to +1 a comment or issue, the best way to do that is to just press the 👍 button. I'm pretty liberal throughout the repo of collapsing any comments that don't constructively contribute to the discussion, especially on a thread with 300 upvotes. Commentary on how we run this repo is probably best directed at a separate discussion rather than in the midst of another thread.
Progress has been made consistently	on tab tear out over the last few years (as linked in the broader thread). It's involved multiple huge refactors of the codebase, so it's taken quite some effort. There are also other priorities that have come up, and with our limited engineering resources, we choose to provide consistent feature enhancements to the product rather than lock everything down for a few months to finish this one feature.
The work I've got in the last few branches is very promising, but it needs a lot of polish before we can ship it. If anyone's got any advice or wants to help contribute - the comments at the bottom of #5000 have links to the work in progress, and what still needs to be done. Thanks!

I am just adding another comment to the fire instead of an issue request.. Make the windows able to be torn off. This is a BASIC function of any tabbed interface. It is the core of a tabbed interface.
Why you would utilized a common interface feature and then not implement the actual reason why that feature exists is completely bizarre.
Further the entire predicate of a tabbed interface comes from Microdot's prior unwillingness to provide native support for group windows.  Now in this implementation of a Microsoft product, the opposite is true.
Perhaps the most bizarre about this is that you mention in the original feature request from 3 years ago that this is a multi-instance application. It still is, and it still should be. This aids troubleshooting efforts and minimizes the effort to implement an core function and usability in line with standard  UX design recommendations..
The application core functions exactly the same as if you have two open windows or one with two tabs. You nest and run the subordinate shells within the app-x parent thread no matter what.... Every tabbed UX application does this.
Honestly take a step back and look at it from a 1000' view. You are currently working on the function and UX of the most critical application for systems administrators for the bulk of your business. Have you ever tried to identify the root cause of a mail issue with a hybrid deployment of azure and on-prem exchange? It,s not unusual to have 4 screens open at once actively gathering or displaying information.
This issue should be prioritized and there shouldn't be a complaint about it. This team made the decision to revolutionize the method thhat people utilize the Windows shell. For some reason you only read half the book on a UX design. Imagine if Microsoft Launched te chromium version of Edge and didn't implement tear off tabs.  How would the general reception of that product go?

Thanks for your input.
This issue is well-understood and additional community commentary on it has not proven fruitful.
I'm going to lock it for now. If there is additional actionable insight you can provide, I'd love to receive it in a thread that will not notify upwards of twenty people and an unknown number of additional subscribers.

Amazing, thank you for all the effort for such a long time and congrats for finally landing it! 🎉🎉

Is it supposed to add the "Move Tab to New Window" item to the context menu of the tabs

like Mozilla Firefox

in the context of this task?
Screenshots of Windows Terminal Preview 1.17.1023 and Mozilla Firefox 111.0.1 (64-bit), Microsoft Windows 10.0.19045.2788.

@Korb I haven't added that yet but I'll track that in #15127

hurry and build this holy shit

@TylerHelt0 Thanks for your interest in this issue! If you'd read, you'll see that this was merged a couple weeks ago, in #14901

Next time, might I suggest reading?

Is there a release plan for this

Is there a release plan for this

We'll release it when it is ready 😜. I'm tracking the release blockers for tear-out specifically over in #14957. There's assorted other release blockers for 1.18 around the repo as well. There have been quite a few ENORMOUS changes to the codebase in 1.18, so bear with us while we make sure that it's in a stable place for release ☺

Any plans to release this soon?

"released" is a stretch I'd say since 1.18 has been in pre-release since May 23rd...  Is there something specific holding 1.18 back and causing you to miss your quarterly releases?

Preview releases are still solid releases. Honestly, that's what I consider the main Terminal releases. 1.18 is held back from Stable for namely #15496, but also to line up 1.19 with some other internal work/announcements/etc.
Also, we're on a roughly quarterly schedule. "Roughly" doing a lot of work here. I'd much rather land a solid release after a 1mo delay, than cut early for the sake of releasing every 3mos.

No one is trying to downplay the amount of work you're doing on this.  We all agree this is a hefty project.
I think we could probably argue back and forth all day about calling preview releases the main release.  I'm comfortable sitting tight until it reaches general availability and out of a preview or dev release.

I don't think we're pushing you to release faster (I'm not, anyway). But I think that it would be less confusing if you didn't say "this was released 4 months ago" when it was only released to the preview channel.
I am probably not alone in not using the preview channel. I'm sure it's fairly stable, but I've got enough variables in my life so I am using the release channel, so for my purposes it is not yet released.
In other words, it would have been clearer to me if you had said "This was released to the preview channel 4 months ago..." and perhaps an estimate of when it would be released to the, well, release channel.

@randomascii
Thank you for saying what I was trying to in a much better way.

Sorry if this has already been noted, there are many hidden comments and did not see it already mentioned
While tab tear-off works in non-elevated Terminal, it doesn't seem to work with elevated Administrative privileges. I'm assuming this would require a new User Account Control prompt
V 1.18.2822.0

@EduardDurech There's a lot more details about the admin drag/drop problem over in #6661.

Seeing this in stable and it's awesome, thanks @zadjii-msft! It's great to see a conclusion to "the penultimate chapter in the saga of tear-out!" 😄 With all the unnecessary anger and frustration I've seen you guys get, I figured a bit of appreciation is in order. Thanks for getting this across the finish line! 🎉

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

seems like a mishandled corner case? @zadjii-msft

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

seems like a mishandled corner case? @zadjii-msft

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

I only found out about this after a Google search which is non-intuitive UX design. Ideally, moving tabs between windows should replicate the behavior in web browsers. @zadjii-msft

Also when you are tearing a tab, the cursor icon is always "🚫" which seems to imply its invalid operation, but in reality, you can tear it off.

Yep, sure. Those are both known. There are additional notes in:

#14900
#16129
#15438


e_lfanew correction

e_lfanew in object::pe::ImageDosHeader was U32 should be I32. This can resulted in invalid parse

Can you explain how this resulted in an invalid parse? This field is the file offset of the NT headers. A file offset cannot be negative, so it doesn't make sense for this to be I32.

Yes that is true. File offset cannot be true, but according to official documentation (https://www.pinvoke.net/default.aspx/Structures.IMAGE_DOS_HEADER) and unofficial ReactOS (https://doxygen.reactos.org/d2/d81/struct__IMAGE__DOS__HEADER.html) e_lfanew should be long (i32). This can be led to compatibility issues when used together other windows crates.

I still don't see how this can cause a problem. It is trivial to cast between u32 and i32 if that is required, and in my opinion a u32 more correctly encodes the semantics of this field. LLVM also uses a u32: https://github.com/llvm/llvm-project/blob/e9b213131ae9c57f4f151d3206916676135b31b0/llvm/include/llvm/Object/COFF.h#L72

I didn't see LLVM one. I thought this is Int32 for a reason. Sorry for annoyance.


SlackToolkit() does not support proxy configuration

System Info
langchain Version: 0.0.348
Python: 3.9.16
Docs suggests to use proxy entry as follows but it does not work:
from slacktoolkit import SlackToolkit
Proxy settings
proxies = {
'http': 'http://proxy.example.com:8080',
'https': 'https://proxy.example.com:8080'
}
Initialize SlackToolkit with proxy
slack_toolkit = SlackToolkit(proxies=proxies)
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[x] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Proxy settings
proxies = {
'http': 'your_proxy',
'https': 'your_proxy'
}
Initialize SlackToolkit with proxy
toolkit = SlackToolkit(proxies=proxies)
tools = toolkit.get_tools()
llm = OpenAI(temperature=0)
agent = initialize_agent(
tools=toolkit.get_tools(),
llm=llm,
verbose=True,
agent=AgentType.STRUCTURED_CHAT_ZERO_SHOT_REACT_DESCRIPTION,
)
agent.run("Send a greeting to my coworkers in the #slack1 channel. Your name is chatbot. Set the sender name as chatbot.")
Expected behavior
slack message sent in #slack1 channel

This is resolved. It seems setting both HTTTP and HTTPS PROXY env vars was causing the issue. When I set only HTTP_PROXY env var it was able to sent the slack messages. It maybe our corporate https proxy. Closing this issue.


Creator Toolkit Not Working: Errors Appearing when opening

[Enter feedback here]
Creator Toolkit apps are not working. I've installed the solutions twice and the controls are not loading. Was this latest version tested?

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

ID: 9a869972-ce34-c5c9-c591-fd25347181c1
Version Independent ID: 9a869972-ce34-c5c9-c591-fd25347181c1
Content: Set up the Creator Kit - Power Platform
Content Source: power-platform/guidance/creator-kit/setup.md
Service: power-platform
Sub-service: guidance
GitHub Login: @denise-msft
Microsoft Alias: demora

Thanks for your comment, @Re-Invent. This issue has been assigned to the doc author for review.


Fix watch-udp

@njam please review; the problem is with asynchronous request. It behaves differently and do not contains plugin response data. The actual response comes after ack with event.

lgtm

released to rubygems


[Feature-Request]: Option to add custom shortcuts to export/import

Possibility for the user to set custom shortcuts for the "Export to AEM" and "Import from AEM" actions. It should affect the currently selected/ open file in the editor pane.
This would allow the user to quickly sync changes in one specific file which he has recently updated or saved.
Currently the autopush/autosync feature exists but I want to remain in control which files are getting synced by manually triggering it.

Hi,
Thanks for your request.
I have just fixed bug, so now you can set keybindings as you like.


aaaaxy: 1.4.160 -> 1.5.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/aaaaxy/versions.
meta.description for aaaaxy is: A nonlinear 2D puzzle platformer taking place in impossible spaces
meta.homepage for aaaaxy is: https://divverent.github.io/aaaaxy/
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.6 with grep in /nix/store/nnmj83954rwk7vkwcybm2cnfkzxrlpqh-aaaaxy-1.5.6
found 1.5.6 in filename of file in /nix/store/nnmj83954rwk7vkwcybm2cnfkzxrlpqh-aaaaxy-1.5.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
aaaaxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nnmj83954rwk7vkwcybm2cnfkzxrlpqh-aaaaxy-1.5.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aaaaxy https://github.com/r-ryantm/nixpkgs/archive/ebe95b82b1d1a07bea0fd7504e18b215dba303d4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ebe95b82b1d1a07bea0fd7504e18b215dba303d4#aaaaxy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nnmj83954rwk7vkwcybm2cnfkzxrlpqh-aaaaxy-1.5.6
ls -la /nix/store/nnmj83954rwk7vkwcybm2cnfkzxrlpqh-aaaaxy-1.5.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

aaaaxy

Maintainer pings
cc @Luflosi for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


Unify code cormatting style

The default code formatters of eclipse and intellij are different.

Is there a common predefined style?
Use the intellij adapter?

See CONTRIBUTING.md.


all changes lost in WSL after HOST win10 system shutdown

Version
win10
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
ip netns add ns1
ip netns add ns2
ip link add veth2 type veth peer name veth3
ip link add veth0 type veth peer name veth1
...
... ...
after shutdown ,all veth device LOST.
Expected Behavior
persised changes
Actual Behavior
all changes LOST
Diagnostic Logs
No response

This is by design. The WSL2 is created from scratch each time WSL is launched, these types of changes are not persisted.


atom build failed

1、delete atom
2、clone again
3、script/bootstrap
error logs:
bash-3.2$ script/bootstrap
Node: v10.16.2
Npm:  v6.11.3
Installing script dependencies
/Users/01388087/ZKJ/Github/Atom/script/node_modules/electron-mksnapshot/download-mksnapshot.js:19
if (err != null) throw err
^
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node ./download-mksnapshot.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/01388087/.npm/_logs/2019-09-24T01_15_14_984Z-debug.log
child_process.js:650
throw err;
^
Error: Command failed: npm --loglevel=error install
/Users/01388087/ZKJ/Github/Atom/script/node_modules/electron-mksnapshot/download-mksnapshot.js:19
if (err != null) throw err
^
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node ./download-mksnapshot.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/01388087/.npm/_logs/2019-09-24T01_15_14_984Z-debug.log
at checkExecSyncError (child_process.js:629:11)
at Object.execFileSync (child_process.js:647:13)
at module.exports (/Users/01388087/ZKJ/Github/Atom/script/lib/install-script-dependencies.js:9:16)
at Object.<anonymous> (/Users/01388087/ZKJ/Github/Atom/script/bootstrap:37:1)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)

what's the problem?
Originally posted by @ZhangKejun in https://github.com/atom/atom/issues/19944#issuecomment-534347554

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/19944. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

Thanks for taking the time to contribute!
We noticed that this is a duplicate of #19944. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

If it is a network problem, how to prove it?
Your answer did not help me.


Rounded joins don't render at the start of a path

Here's what my design looks like in Rive:

And here's the .riv file in Defold:

I've noticed this with my other .riv files with rounded corners so I assume it's consistent. I've also tried reversing the direction of the path, which doesn't affect the result.
The other types of stroke joins and caps seem to render correctly.
I'm using the latest version of Defold and the latest stable release of this extension.

Hi, thanks for your report! could you share this repro case with us?

Here's the Defold project I was using to reproduce this. It includes the Rive file displayed above, as well as versions of the shape with other join and cap types. Just build and run.

Fixed in 2.0.0
See https://forum.defold.com/t/updated-rive-extension/75169


user12986714: Watch freetechport.com

user12986714 requests the watch of the watch_keyword freetechport\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

freetechport\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by iBug in Charcoal HQ


Transfer ownership of NPM package

@davidagraf Can you transfer the ownership of the NPM package to my account "samypesse", so that we can publish it as part of GitBook v4.
Thank you 🍻

done

thanks 👍


[Feature] MCS: Traffic manager resource identifiers need to be readable (not UUIDs)

When interacting with TrafficManagerBackend or TrafficManagerProfile CRs any references to Traffic Manager instances should use human readable Traffic Manager resource names and not render resource IDs (UUIDs).

The reason of using uuid is to solve the name conflict issue, especially when we introduce BYO resource group/profile. The atm resources are supposed to be managed by our controllers, instead of human. For easier debugging/troubleshooting, it should be addressed in #237 to use the azure resource id returned in the status.


Can't use TLS in client on Fedora 31

Fedora 31, using current Git master of Syncplay (23ca271).
Despite having all of the required dependencies for TLS in the client, I was still seeing "This client does not support TLS" at startup. Running in debug mode, I saw the following:
$ ./syncplayClient.py --debug
UnicodeEncodeError: 'ascii' codec can't encode character '\u0151' in position 126065: ordinal not in range(128)
[...]

After digging through the source code and testing commands related to TLS, I found that the error arises from the following block in syncplay/client.py
try:
    caCertFP = open(os.environ['SSL_CERT_FILE'])
    caCertTwisted = Certificate.loadPEM(caCertFP.read())
    caCertFP.close()
    self.protocolFactory.options = optionsForClientTLS(hostname=host)
    self._clientSupportsTLS = True
except Exception as e:
    self.ui.showDebugMessage(str(e))

What's happening is that my system CA bundle (ca-certificates-2020.2.40-1.1.fc31.noarch) contains Unicode in one of the comments between certs. Specifically on the line
# NetLock Arany (Class Gold) Főtanúsítvány

Then Certificate.loadPEM(caCertFP.read()) raises an exception with the following trace (reproduced in an interactive Python session, running the commands myself):
Traceback (most recent call last):
  File "/usr/lib64/python3.7/site-packages/twisted/internet/_sslverify.py", line 500, in loadPEM
    return Class.load(data, crypto.FILETYPE_PEM)
  File "/usr/lib64/python3.7/site-packages/twisted/internet/_sslverify.py", line 477, in load
    return Class(crypto.load_certificate(format, requestData), *args)
  File "/usr/lib/python3.7/site-packages/OpenSSL/crypto.py", line 1824, in load_certificate
    buffer = buffer.encode("ascii")
UnicodeEncodeError: 'ascii' codec can't encode character '\u0151' in position 126065: ordinal not in range(128)

Here's the thing though: caCertTwisted is never even used for anything. It looks like we attempt to load the system CA bundle just as a test that it...exists, or something? But if I remove the line
    caCertTwisted = Certificate.loadPEM(caCertFP.read())

and then launch the client, TLS works! So, the UnicodeEncodeError raised by PyOpenSSL is actually irrelevant when it comes to actually starting the client with TLS, and I am able to successfully connect to the public server over TLSv1.3 after applying this change.
So, I think that this test done to determine whether the client can launch with TLS needs to be reviewed.
(Alternatively, this could be considered a bug upstream in Twisted or PyOpenSSL, however it kind of looks like these methods are only intended to be loading one certificate, not a bundle containing comments between certificates... So I'm not sure they would accept it as a bug?)

I don't use Fedora so am not in a great position to review the test, but if you can figure out a simple tweak to Syncplay which would fix it then please make a PR.

Are you able to explain what exactly is the need to attempt loading the system CA bundle? Is it enough just to test that the file exists instead?

@Phidica I can't be of much use as I wasn't particularly involved in the development of that feature, but it is possible that @albertosottile or @daniel-123 would be able to comment.

So... I remember writing that code. In the beginning of the TLS client implementation I tried (quite desperately) several approaches to make Twisted load the certifi CA file but, I failed miserably. Then I found out this environmental variable approach which, despite being ugly, has worked perfectly up to now. So, I am quite convinced that the line that is causing your error is a remnant of my experimentations and its not fundamentally needed anymore. Nevertheless, I would still assert if the file exists In the same try block, just to be extra safe.

@Phidica If there is a suitable pull request soon in line with @albertosottile's comments then this can hopefully be included in the release candidate of Syncplay v1.6.5.

Thanks @daniel-123!


Remove header trades

The header trades is not required.
The function ToSlice() is not inserting value for this column: https://github.com/rodrigo-brito/ninjabot/blob/0dcd4382a40d5255be8c73c30633e06b2694f900/model/model.go#L85-L93
You have to remove the header here and fix the tests (if needed)
https://github.com/rodrigo-brito/ninjabot/blob/main/download/download.go#L100

@rodrigo-brito can i work on this one?

I opened a PR for this!


fastlane installer can't update to latest version

New Issue Checklist

[X] Updated fastlane to the latest version (somewhat)
[X] I have read the Contribution Guidelines

Issue Description
I've tried to install fastlane using the fastlane.zip with the following script:
curl -sS -Lo  -fastlane.zip https://download.fastlane.tools/fastlane.zip
unzip fastlane.zip -d fastlane
fastlane/install

It is not possible to update this fastlane installation to the latest version using fastlane update_fastlane because of wired compilation errors. You can find a rundown in this gist: https://gist.github.com/MKuckert/4df58409e932c5650cf85ac0b3ab7ac5

The compiler looks for a sdk at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk but only MacOSX10.12.sdk exists. After fixing that there's an error about missing libraries. The error message of the linker points to -lruby-static, but I think the -L/Users/crashlytics/buildAgent/... paths look suspicious.

🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.11.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.11.6 (15G1212)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.1.3
🚫 Update availaible

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.4

activesupport
<IP_ADDRESS>

addressable
2.5.0

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.13.6

claide
1.0.1

colored
1.2

commander
4.4.2

domain_name
0.5.20161129

dotenv
2.1.1

excon
0.54.0

faraday
0.10.0

faraday-cookie_jar
0.0.6

faraday_middleware
0.10.1

fastimage
2.0.1

gh_inspector
1.0.2

google-api-client
0.9.20

googleauth
0.5.1

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

i18n
0.7.0

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
2.9.0

little-plugger
1.1.4

logging
2.1.0

memoist
0.15.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.4.3

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.3

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.4

rake
10.4.2

rdoc
4.2.0

representable
2.3.0

retriable
2.1.0

rouge
1.11.1

rubygems-update
2.5.2

rubyzip
1.2.0

security
0.1.3

signet
0.7.3

slack-notifier
1.5.1

sqlite3
1.3.12

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

thread_safe
0.3.5

tzinfo
1.2.2

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.2

word_wrap
1.0.0

xcodeproj
1.4.2

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

generated on: 2017-01-02

Hey, we just pushed fastlane 2.4.0 which fixes the bundled fastlane, just run fastlane update_fastlane to get the latest release 🚀
However this release breaks support for Ruby 2.4.0 for now, which we should be able to add again soon. For now, please downgrade to an older version of Ruby, or use the bundled fastlane from download.fastlane.tools
Please let us know if that works for you 👍

I'll close this issue for now, let me know if that works for you


Add quick keys

See #304. Ping @mohkale

How does this work? You start quick select and then each candidate is prefixed with a key or more keys, hh, hk etc depending on the number of candidates?

The quick keys overwrite the candidate keys. I experimented with prefixing but it doesn't work well with horizontal display because the display width changes and I also think this is less bumpy so hopefully nicer as well.

I will not merge this yet, please give it a try, I will look at it tomorrow again, good night!

I tried it. The overwriting does not work correctly. When running this from consult-buffer it adds keys like as, ad, ... I don't understand why it generates the unnecessary "a" prefix key. Regarding the implementation - why use a quick-fun closure instead of just an array of keys indexed by the candidate index - this would be more direct?

To be more precise - when it adds the keys "as", only the letter "s" overwrites the candidate and the "a" is prefixed, which makes the candidates move. And the "a" is unnecessary after all. Besides that - I like it. Maybe there is a more appropriate default face to be used which is more aligned with avy, but probably this should be fixed in the theme in the end.

Thanks, for trying. You get two keys when more than one key when there are too few candidates to highlight with selectrum-quick-keys. I liked the visual consistency when I tried the prefix before but when overwriting it probably makes more sense to allow mixing single and multi chars.
As you noticed there is something wrong with consult-buffer. I will look into that and the closure thing you mentioned.

What about using M-q for quick select and put cycling one some other key? Maybe better because of the mnemonics or is M-m used by ivy for avy?

The reasoning for the bindings is coming from the bindings C-i for normal insertion and C-m for normal selection. M-i and M-m bindings aren't useful in the minibuffer and they can be seen as alternatives for the normal ones.

You get two keys when there are too few candidates to highlight

Yes, that is okay - avy does it in the same way. But I think it should still overwrite for single keys and double keys. There are two bugs - consult-buffer should not require more than a single key, I mean I still have only ten candidates. And the second bug is that the overwriting does not work correctly.

Yes, I did not test with consult, will look into that.

Regarding the keys, your argument makes sense. However C-m is also RET because of the ascii control key encoding, therefore I don't find the symmetry so obvious. In the default bindings you have M-m bound to back-to-indentation and C-m to RET, so there is no symmetry there either.
Generally I find the usage of the ascii control key legacy in Emacs confusing. I am currently using a modified key map where I rebind ijkl to navigation, this messes with the "default" muscle memory where C-i=TAB etc. Because of the ascii control keys I think Emacs keybindings are actually not that configurable as they should really be. It is a big mess with the input-decode-map and all these different keymap layers. Maybe I should just go back to Emacs default bindings :shrug:

The problem is that I use selectrum--actual-num-candidates-displayed but for consult this is including the heading lines. Should we use another variable? One for inserted items and one for actual candidates?

Uh, okay. I guess we have to fix selectrum--actual-num-candidates-displayed then, such that it corresponds to the real number of candidates without the header lines? Do you know what effect that has? The number of lines generated by the display function does not necessarily correspond to the number of candidates!

The insertion functions return how many candidates they inserted because it depends on their behavior. But they don't know which ones were actual candidates.

The function selectrum--vertical-display-style returns the length of displayed-candidates, which is wrong. It is actually the number of lines. We should fix the candidates-display-strings function such that it returns a pair, the number of candidates and the line strings.

Before the grouping selectrum--candidates-display-strings did not add additional lines/candidates.

selectrum--candidates-display-strings  could return the number of candidates + the candidates and return that to the insertion functions, too?

Instead of returning the pair, the proper fix as I see it:
Alternatively, you may want to rewrite the candidates-display-strings function such that it returns actual groups ((group . cands) (group . cands), this would give the display style function more flexibility in the formatting. Furthermore we should not pass horizp to the candidates-display-strings function, such that things are more decoupled.
I think we should refactor that first before merging this PR.

There is the complication though that horizp also controls if annotations/extension is added. I am unsure about the best way to fix this. One could always return annotations and the horizontal style could just ignore them or one keeps the horizp/add-annotations flag.

It is also used to decide about highlight extension.

It is also used to decide about highlight extension.

Yes, I wrote "annotations/extension" above. The extension should actually be done by the display style.

Yes, saw that too late ;)

I think we should actually do this refactoring. It is the logical conclusion of the refactoring commits I made regarding to the display style formatting. I just didn't come to it yet and at some point I stopped, I thought it is sufficiently good as is. But now it turns out, that it is not. So we should refactor more ;)

Okay, do you want to do it? I will wait before merging this PR until this is done.

Okay, I can do it. Maybe not now, but in the evening.

That would be great, we can discuss things further there. I feel a bit uncomfortable for changing more things for the grouping but if it results in a cleaner design overall it is worth it.

Regarding the array instead of a closure I don't know how that would look like, I think a closure is good for handling the state adjustments/display changes but maybe you have something better in mind, we can always change the implementation later, too.

I think you are right with the redesign, it all started from the desire to have general insertion functions which share some code to create the display strings and now we are moving to more specific style functions instead. We just need to make sure that changing the candidate display for all insertion styles (like I do with this PR) is still easy to do.

Because of the ascii control keys I think Emacs keybindings are actually not that configurable as they should really be. It is a big mess with the input-decode-map and all these different keymap layers.

I can relate to that, I often fought with Emacs key quirks in the past and had the following in my config for a while:
;; free up blocked keys (GUI only)
(let ((frame (framep (selected-frame))))
  (unless (or (eq  t  frame)
              (eq 'pc frame))
    (define-key input-decode-map [?\C-m] [C-m])
    (define-key input-decode-map (kbd "C-[") [C-\[])
    (define-key input-decode-map [?\C-i] [C-i])))

I wish one could just do things like (setq save-key (kbd ...)) but we are plagued with all the historical nonsense, which leads to crazy workaround like translating keys to "C-x C-s" instead, which I still do.

Yes, I do the same as you did with [C-m]. I translate some keys to [my-key] in the input-decode-map to work around the nonsense.

What about 'display prefixes? consult-line for example.

Those worked when I tested them, do you have any idea what upstream could change to avoid the invisible disambiguation chars?

You may be interested in this discussion with @dgutov - https://github.com/oantolin/embark/issues/162#issuecomment-787201608. From my current point of view there are multiple upstream proposals which could be made. Some of them must be discussed and worked out a bit more.

x-group-function - it would be good to specify that at least or reserve the key upstream, even if upstream does not implement grouping support. See also https://github.com/minad/consult/wiki/Grouping-support#default-completion. I think this works relatively well and could be proposed as is.
get-original action for the completing-read completion table, to get access to the actual key/value pair. This would be helpful for Embark. This is an idea by @dugtov, and should be fully worked out.
Return text properties from completing-read. If a candidate is selected which is a member of the collection, the string of the collection should be returned, including the text-properties. If require-match=t it is ensured that text properties are always present, except for the nil completion, where an empty string is returned.
Retain object identity for the returned objects and allow duplicate candidate strings - this relates to 3, but is a bit stronger. We do not only require the text properties to be retained, but we require the exact object identity to be preserved. With this proposal, we could get rid of the deduplication prefixes, use duplicate strings with different text properties or decide based on the object identity.
Why is there a nil completion after all? Maybe add a new value for require-match, like 'require-match-no-nil? Or change the current meaning of t, such that nil completion is not allowed.

Thanks, I don't overlook the consequences these changes might have for older Emacs versions but I would be happy if there is a way toward the future ;)

Hi @clemara, thanks for adding this.
I just had a chance to test it out and everything looks OK to me. I'd like a face for the inputted keys as well as selectrum-quick-keys-highlight but otherwise no complaints. Thank you again :smile:.

@mohkale I added selectrum-quick-keys-match face.

I need to do a bit more refactorings on master before this gets merged.


Possible to mock 'fs' and 'process.env' ?

Hi,
Great library, i wasn't liking very much the mock api that jest gives you :-(
Although I was wondering if its possible to mock something from node_modules that is imported inside a class and not passed in via the constructor.
The 2 modules I am talking about is fs (from node), one of my classes uses it. Also another class, my config class, returns methods from process.env
for example, I have a getDatabaseConnectionString() which basically returns the env variables
DATABASE_CONNECTION_STRING so i.e.
process.env.DATABASE_CONNECTION_STRING
I have an internal private validate method on the SUT that ensures that all environment variables exist.
I was wondering if ts-mockito can mock FS and process.env ?
I am using NestJS so technically I could pass in FS on the constructor and then when testing i could override it with a mocked version but I was wonder if ts-mockito can do the same as what jest does i.e.
jest.mock("fs")
As I say, if it doesn't that i can work around this by just passing in fs in the constructor (using dependency injection) and override with a mock at test time but would be nice to know if ts-mockito can mock node_modules ?
The other thing is the process.env, this sounds kind of wrong to pass in the process in the constructor, i was wondering what everyone else is doing ? Actually process you do not import its a method that comes built-in from node.
fs and proces.env are just 2 problems i have right now :-) I know I am going to get another issue as I use log4js - which is also imported directly in a module that depends on it.
Any ideas or help really appreciated
Thanks

Ok I noticed that i can spy on the real object. Real object being any node_module.

Just for whoever is wondering, an environment variable can be overwritten for a test. process.env is a global property and therefore, simply setting the value of the environment variable as follows will set it globally and thus during your test:
process.env.DATABASE_CONNECTION_STRING = "my-connection-string"


[Client] Identity UI component and layout

[x] Improve Identity view layout
[ ] Create es6 class-based yo-yo component like: https://github.com/IBM/ipfs-social-proof/blob/master/client/components/public-key-card.js

view improved in #24


Hot Coners for Windows

Description of the new feature / enhancement
Linux/Unix have the function/feature for hot corners, this should be added in the power toys suite. This would be awesome and increase productivity when working with one screen and even multiple screens if done right. I have wanted this feature forever on Windows and Power Toys seems to be the perfect medium for this.
Here is an example if you do not know what Hot Corners is.
https://www.maketecheasier.com/get-hot-corners-windows-10/#:~:text=However%2C you can still set,each corner of your screen.
https://www.makeuseof.com/use-workspaces-and-hot-corners-in-linux-mint/#:~:text=How to Activate Hot Corners,and click Enter to continue.
https://appleinsider.com/inside/macos/tips/how-to-use-hot-corners-in-macos
Scenario when this would be used?
My main use would be when working on a laptop and wanting to switch to virtual desktops. It is way easier to throw your mouse in a corner than to use hotkeys.
Supporting information
https://www.maketecheasier.com/get-hot-corners-windows-10/#:~:text=However%2C you can still set,each corner of your screen.
https://www.makeuseof.com/use-workspaces-and-hot-corners-in-linux-mint/#:~:text=How to Activate Hot Corners,and click Enter to continue.
https://appleinsider.com/inside/macos/tips/how-to-use-hot-corners-in-macos

/dup https://github.com/microsoft/PowerToys/issues/1305


implemented window and fixed short window, also debug pyomo opt mode

Pull Request Description
What issue does this change request address?
Closes #77
Closes #78
What are the significant changes in functionality due to this change request?

Adds a rolling_window_length option to the pyomo dispatcher.
Adds a debug_mode option to the pyomo dispatcher, allowing verbose printouts of dispatch details to screen.
Fixes a rolling window reset bug for storages and synthetic histories.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass.
[x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[x] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

Since HPC is currently down, I was able to pull the branch and pass all current HERON tests locally. This will satisfy the SQA requirements to merge this code.


fix: flake in test_allow_volume_creation_with_degraded_availability_csi

Which issue(s) this PR fixes:
longhorn/longhorn#9035
What this PR does / why we need it:
https://github.com/longhorn/longhorn/issues/9035#issuecomment-2237341792
Additional documentation or context
I'm not sure about this one yet, as I've had no opportunity to observe a cluster's state right after a failure. However, if my hunch is correct, the slightly modified test will pass 50/50 times.
https://ci.longhorn.io/job/private/job/longhorn-tests-regression/7268/

@mergify backport v1.7.x v1.6.x


Fix inconsistent logging_and_data_dir parameter in AwaDB

Description
Tag maintainer: @rlancemartin, @eyurtsev
log_and_data_dir
AwaDB.__init__() accepts a parameter named log_and_data_dir. But AwaDB.from_texts() and AwaDB.from_documents() accept a parameter named logging_and_data_dir. This inconsistency in this parameter name can lead to confusion on the part of the caller.
This PR renames logging_and_data_dir to log_and_data_dir to make all functions consistent with the constructor.
embedding
AwaDB.__init__() accepts a parameter named embedding_model. But AwaDB.from_texts() and AwaDB.from_documents() accept a parameter named embeddings. This inconsistency in this parameter name can lead to confusion on the part of the caller.
This PR renames embedding_model to embeddings to make AwaDB's constructor consistent with the classmethod "constructors" as specified by VectorStore abstract base class.

thanks - a bit backwards incompatible but i think its fine

It is, but the contributing documentation says, "as pre-1.0 software, even patch releases may contain non-backwards-compatible changes." So I figured it was ok.


Disable Cemu's auto-update option

Since it wouldn't be used with packages anyway
Also seems to not work for Linux?
$ curl 'https://cemu.info/api2/version.php?v=2.0-24%20%28experimental%29&platform=windows'
UPDATE|https%3A%2F%2Fgithub.com%2Fcemu-project%2FCemu%2Freleases%2Fdownload%2Fv2.0-25%2Fcemu-2.0-25-windows-x64.zip|https%3A%2F%2Fcemu.info
$ curl 'https://cemu.info/api2/version.php?v=2.0-24%20%28experimental%29&platform=linux'
# no output

https://github.com/cemu-project/Cemu/blob/9ebbfb3ae2fda578c228bee0a408ac76f73b31fd/src/gui/CemuUpdateWindow.cpp#L101

Closed by c30bcd937c3fd8c3bea388f269c644bfb0ef820d


⚠ Bofrost.at has degraded performance

In b4d0436, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1364 ms

Resolved: Bofrost.at performance has improved in ba95389.


Request: Please support breakpoints config value for Slides component

Resources:
Before submitting an issue, please consult our troubleshooting guide (http://ionicframework.com/docs/troubleshooting/) and developer resources (http://ionicframework.com/docs/developer-resources/)
Please make sure you are posting an issue pertaining to the Ionic Framework. If you are having an issue with the Ionic Pro services (Ionic View, Ionic Deploy, etc.) please consult the Ionic Pro support portal (http://support.ionicjs.com)
Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[x] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
There appears to be no available property for the breakpoints parameter, which is available in Swiper JS
Expected behavior:
This should be available option, please. With the push for PWA, being able to make the Slides component work in these scenarios is vital.
Other information:
http://idangero.us/swiper/api/

Hello! Thank you for the feature request. I'm going to move this issue over to our internal list of feature requests for evaluation.
The slides and swiper are getting a major overhaul as part of Ionic-v4, including more direct usage of the Swiper code, so this should be revisited after v4 has been released to determine if it is still an issue or if it has been fixed.
Thanks!

This issue was moved to ionic-team/ionic-feature-requests#313


Can I pass an Illuminate\Database\Eloquent\Collection element to the EloquentDataProvider?

I have an application which calls an api and get an Illuminate\Database\Eloquent\Collection element to render in the view.
I just want apply the filters over that collection but when I pass that element the app trigger the following error:
Argument 1 passed to Nayjest\Grids\EloquentDataProvider::__construct() must be an instance of Illuminate\Database\Eloquent\Builder, instance of Illuminate\Database\Eloquent\Collection given
I know the error but doesn't have any other way to get the data because the database are remote.
Do you have any idea to solve that issue?

Upd: to use view-component/grids with eloquent, include view-components/eloquent-data-processing package.
Upd2: I think, in your case the simplest solution is to try to work via Eloquent QueryBuilder if its possible.
If your api calls are just a method calls to 3rd-party classes, there is a sense to override api class &
replace
// inside some api method
return $queryBuilder->get();
// or return $queryBuilder->paginate();

to
return $queryBuilder;

The Upd2 doesn't work because cannot transform the builder object to a string from the api.
I will check the view-components/eloquent-data-processing and the view-components/grids. Hope that works.

Hi @pascualm4!
How are thing going? Did you found a solution?

Hi @Nayjest I have a question how to install the view-components/grids. I clone the repo on my project but I don't know what is the name of the class to put in the config/app.php file. In the nayjest/grids package it's very documented.

Hi @Nayjest I found a solution using the package view-components/grids. The DataProvider originally was an Elloquent/Collection. I transform that to an Array and works well. Only I have two issues but I will open another. Thanks for your help.


logging: add mechanism for handling transient strings

Extending logger to support logging transient strings (with %s).
With dedicated call (log_strdup), string is duplicated to a buffer
from internal logger pool. Logger implicitly manages the pool.
See the discussion https://github.com/zephyrproject-rtos/zephyr/pull/9820#discussion_r217403230
In proposed mechanism when message is freed each argument if it is an address within string duplication buffer pool and based on that frees a buffer. Additional mechanism is added to ensure that there is no double free which brakes the system. When buffer is allocated user gets address shifted by one word and first word in the buffer is used as a flag indicating that buffer is allocated. When message is freed and candidate for strdup buffer is found in arguments then strdup buffer is freed only if flag indicates that it is allocated (flag is atomically decremented).
By returning shifted buffer probability of accidental address match is decreased (see https://github.com/zephyrproject-rtos/zephyr/pull/9820#discussion_r217403230).
There is still a chance that buffer is freed before being used by all backends if accidental address is matched but in worst case it will only result in log message corruption. Double freeing is prevented.
The major drawback of that solution is increased time of message freeing. Measurements shown that every message freeing is doubled (e.g. single argument ~1.5us -> ~3us). It means that logger performance degrades if buffer is too small and each log message triggers freeing another message (e.g. single argument log 4us -> ~8us).
The major advantage is that there is very little impact on log API.
API is reduced to log_strdup only. In #9820 it was proposed to have log_malloc and log_free but is risky since module has no control over current severity level so it would be difficult to manage explicitly allocated buffers. If use case requires that string is built (using sprintf) before being logged then additional buffer must be used (stack?) and such buffer must be wrapped with log_strdup() in log message call.
Counterproposal to #9820 Fixes #9090
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

Codecov Report

Merging #10123 into master will decrease coverage by 0.04%.
The diff coverage is 17.14%.

@@            Coverage Diff             @@
##           master   #10123      +/-   ##
==========================================
- Coverage    52.5%   52.46%   -0.05%
==========================================
  Files         213      213
  Lines       26140    26175      +35
  Branches     5634     5643       +9
==========================================
+ Hits        13726    13732       +6
- Misses      10159    10186      +27
- Partials     2255     2257       +2

Impacted Files
Coverage Δ

include/logging/log_msg.h
81.81% <ø> (ø)
:arrow_up:

include/logging/log_core.h
100% <ø> (ø)
:arrow_up:

subsys/logging/log_core.c
61.16% <6.89%> (-8.9%)
:arrow_down:

subsys/logging/log_msg.c
81.56% <66.66%> (-0.67%)
: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 27d99d1...9cd2f67. Read the comment docs.

@pizi-nordic I see you jumped eagerly to code review (great :+1: ) but lets first agree if this solution is accepted by us. Unless your eagerness is the answer. @jhedberg how about you? Is this satisfying?

@dbkinder documentation changes here are the stripped down version of changes in #9820.

@ceolin if you are referring to lines 541-542 then no. First address is decremented then value under this address.

added tests to cover log_strdup feature.

@pizi-nordic @dbkinder  changes are applied. Can you finish the review. It would be good to get that in so it is applied to porting branches (network, bluetooth).

@dbkinder could you rereview? I think your comment has been applied. Seems like we are only missing your approval.


user information not being retreived from local configuration in Linux

Hi, thanks for this plugin for speckle. I am trying to use this under Linux. I read the instructions posted here but I am getting the following error:
Python: Traceback (most recent call last):
  File "/home/tapiac/.config/blender/3.5/scripts/addons/bpy_speckle/operators/users.py", line 82, in execute
    speckle.active_user = str(active_user_index)
TypeError: bpy_struct: item.attr = val: enum "0" not found in ()

Expected vs. Actual Behavior
The users shuold be shown in the GUI, however, an error is raised.
Reproduction Steps & System Config (win, osx, web, etc.)

OS: Linux (Ubuntu 22.04)
Blender: 3.5 (snap package)

The plugin is installed under ~/.confg/blender/3.5/scripts/addons/bpy_speckle
I have manually added the configuration file under ~/.local/share/Speckle/Accounts and symlinked Speckle/ to ~/.config/blender/data/Speckle.
❯ ls -lh .config/blender/data
total 0
lrwxrwxrwx 1 tapiac tapiac 33 Mai 30 11:36 Speckle -> /home/tapiac/.local/share/Speckle

In the folder Accounts I have placed a json file accoriding to the instructions from here.
Running the following commands in the REPL of Blender returns no account:
>>> import bpy_speckle as speckle
>>> speckle.users.get_local_accounts()
[]

Hey @cristobaltapia,
thanks for the test. It does makes sense. Speckle uses a centralized config folder under XDG_CONFIG_HOME which in most cases is ~/.config/Speckle/.
Turns out the blender snap is using classic confinement to allow full access to the host os file system ( if i remember snap terms correctly ). Another variation case in behavior under linux. ( Hence the lack of official support from us for now )
I'm glad it works for you.
Do stop by our forum for a bit of show and tell, we're always curious what ppl are doing with Speckle especially if its pushing the boundaries of our mainstream workflows.


Ability to use StatusLight in a Picker

🙋 Feature Request
The ability to use the StatusLight component as an Item in a Picker component
🤔 Expected Behavior

Selected StatusLight component should be shown in the Picker as styled in the Item when the list is collapsed
The StatusLight component should be rendered correctly as an Item in the list when the list is opened, i.e. the dot and text should be aligned properly.
The Picker width should be resizable without causing the text part of the StatusLight to wrap
If the StatusLight text is too long, should have the option to truncate with an ellipsis.

😯 Current Behavior

The text part of the StatusLight wraps if the size is set to anything less than "size-1400"
Picker width greater than "size-1400" does not seem to have an effect on the size of the Picker.
The selection highlight for non-selected Item is incorrect when the list is open

Workaround for selection highlight:
<Text>
   <View>
        <StatusLight ... />
   <View>
<Text>

💁 Possible Solution

🔦 Context
This Picker component is intended to show progress. Our list has two items, "In Progress" and "Approved". The user chooses "Approved" to move something forward. The StatusLight was also used in a different view to indicate the "progress" for that item.
I ended up spending some time trying to implement workarounds using other components to duplicate StatusLight. All of which did not work out.
The result of the current implementation:
Note that the width of the Picker is too wide compared to the design.

💻 Examples
mockup in dark mode;

🧢 Your Company/Team
Adobe/3D&I

3D&I
🎁 Tracking Ticket (optional)

I think the solution to this should be an option for StatusLight rather than something specific to Picker. I think if StatusLight was inline-flex rather than flex, and removed its builtin padding (which is problematic in many scenarios), the issue would be solved. The question at this point is how to make those changes in a non-breaking way. We'll either need a new prop, a new component, or a new major version for this package.

Is there a downside to just fixing the style issues via slots?

I don't think we should really do component specific overrides that way if we can help it. The problem isn't unique to Picker - the same padding also affects table cells and lots of other things. e.g. #2629