Fixing Issue - 1669 - PeoplePicker returns no results with webAbsoluteUrl and ensureUser

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #1669

What's in this Pull Request?
Fixing issue - 1669 - PeoplePicker returns no results with webAbsoluteUrl and ensureUser
Problem statement
When setting webAbsoluteUrl prop to a different site and property to ensureUser = true, results are expected to be returned.
But, No results are fetched, If both the webAbsoluteUrl prop is pointing to a different site than the current one, and ensureUser is set to true, no results are returned in the picker. Instead, the console shows the error: PeopleSearchService::searchTenant: error occured while fetching the users.

A deeper error says Cannot read properties of undefined (reading 'push'), which I've tracked down to PeopleSearchService.ensureUser:295. The object cachedLocalUsers assumes it already contains the webAbsoluteUrl as a key but it does not.
Solution
When checked, in the method ensureUser, the user object is pushed into this.cachedLocalUsers. But this is empty because the user is given webAbsoluteUrl to fetch the users from other site collection, for which it is erroring out as Cannot read properties of undefined (reading push) as shown in the below figure.

By checking if this.cachedLocalUsers and initializing it as empty array (as below), this is working as expected.

Screenshot with working example

Thanks,
Nishkalank Bezawada

Hello @michaelmaillot @joelfmrodrigues
Kindly review this PR and let me know your comments.
Thanks,
Nishkalank

Thanks @NishkalankBezawada, we'll review this PR shortly!

PR merged, thank you!


Rewrite from proc-macro to build.rs

The current implementation uses a proc-macro. This macro is not expanded in incremental builds. This causes changes in the static asset directory to not show up in the binary.
This proposed change drops the load_assets! macro and introduces a build script for the memory-serve crate. The build script takes an environment variable  to load assets from. Any changes in the path defined by ASSET_DIR or changes to the variable itself will trigger a rerun and will load fresh assets.
Note that this will be a breaking change:
MemoryServe::new(load_assets!("static"))

Becomes:
MemoryServe::new()

And the ASSET_DIR environment variable will be required.
This PR also ships some improvements to logging and improves build performance.

That'd be great! We already use similar metadata for cargo-leptos so that would be very familiar.

Hmm - I am sill not happy about the fact that we need to specify an absolute path with the ASSET_DIR variable (or via metadata). I like to find a solution before merging this work.

Hmm - I am sill not happy about the fact that we need to specify an absolute path with the ASSET_DIR variable (or via metadata). I like to find a solution before merging this work.

Looks like rust-embed uses a proc macro but probably avoids the stale assets in incremental builds problem by serving the files from disk in debug mode by default (configurable with a feature). Not sure if that's a good option here, just throwing around ideas.

Hmm - I am sill not happy about the fact that we need to specify an absolute path with the ASSET_DIR variable (or via metadata). I like to find a solution before merging this work.

Looks like rust-embed uses a proc macro but probably avoids the stale assets in incremental builds problem by serving the files from disk in debug mode by default (configurable with a feature). Not sure if that's a good option here, just throwing around ideas.

This is how memory-serve already worked, unless the new force-embed feature is enabled.

That'd be great! We already use similar metadata for cargo-leptos so that would be very familiar.

So metadata is not available when build.rs is executed. So for now there are two options: use the macro as before or use a environment variable. Both work with relative or absolute paths.

So for now there are two options: use the macro as before or use a environment variable. Both work with relative or absolute paths.

Looks like we now use include_bytes! (which should automatically handle incremental reloads) so it should work with incremental builds in either case. Am I understanding that right?
I'm not sure if it works with the procmacro with compression enabled though since we create the compressed file in the procmacro so I think it wouldn't see the change.  Maybe when compression is enabled we could still use include_bytes! on the original file just to ensure it's tracked but not actually use it? Looks like that's how rust-embed's include_flate! dependency fixed that: https://github.com/SOF3/include-flate/commit/4cf6b8e1ece726e16e1fd5a7f7e9e2237726bf9f Guessing since it's just included when the procmacro runs, so it doesn't get included in the final binary? Not sure though. This issue is what led me to that: https://github.com/pyrossh/rust-embed/issues/182


Allow RenderObjects to be layed out and painted multiple times per frame

Use case
I know this is very niche, but I'd like to layout and paint a RenderOobject multiple times per frame.
The use case is having the same widget (with the same state and all) drawn multiple times given different constraints.
Proposal
The framework has a lot of assertions that prevent such behavior. I don't really have a proposal; I was more wondering if something like this would be even compatible with the current architecture on a deep level.

Hello @Norbert515
Curious to know if this is for gaming, given that same widget need to be drawn multiple times ?
Also, would be better if you could give an example about assertion that prevents drawing same widget multiple times ? It would help to understand the context in better way.
I am also not sure how feasible it would be to implement this because as you said above, it's not a proposal, but more of a question if something like this could be achieved.

Thanks for the quick response!
It's no for gaming but for a dev tool.
Basically, I want to draw the application with different sizes and resolutions to preview how the app looks on different phones (very similar to this https://sizzy.co/).
Regarding the assertions - pretty much the whole system is designed to operate by first laying out and then painting. Laying out a child mutates it, therefore, implementing this layout would require to either call layout during paint (which is prevented by for example assert(owner == null || !owner!.debugDoingPaint); in object.dart[2130]) or do something completely different.
I don't think changing significant parts of the core is justified by such a small feature, but I was wondering if there could be some kind of loophole or non-invasive change to enable this?

@kf6gpe A render object is not an engine component. It should be possible to construct duplicate scenes in the frameworks and render them multiple times on-screen using currently vended dart:ui APIs.


Replace pathephone.github.io with pathephone-web

Pathephone web app should be moved to the root domain. That said, pathephone-web should provide some info about the latest desktop version or something.

Not for now, should set ReactRouter root path though.


add std.int128 a 128 bit integer arithmetic type

A 128 bit signed integer type.
Not done is the unsigned version.

I think a generic arbitrary-fixed-size integer type would be a better addition.
An implementation exists here:
https://github.com/d-gamedev-team/gfm/blob/master/integers/gfm/integers/wideint.d

For fellow under-a-rock-dwellers, this exposes core.int128 via Phobos.

Blocked by https://github.com/dlang/druntime/pull/3794

Is there a link to centralized discussion? My immediate question is that from the Druntime pull requests I got the impression that core.int128 was to be exposed as language-builtin cent/ucent types by the compiler, not via a Phobos module.

discussion: https://digitalmars.com/d/archives/digitalmars/D/When_will_you_implement_cent_and_ucent_358854.html

Will this come with support for 128-bit literals? Or will we have to wait for importC to gain int128_t support for that?

Blocked by https://github.com/dlang/druntime/pull/3795

I don't see why this should be in Phobos versus druntime. Having 128 bit types as a library is already bizarre compared to what you get in basically any other systems programming language (even if we then special case them to use the proper compiler intrinsics i.e. the code generated at the moment is terrible), but if we really do that why would they be split across phobos and druntime?

I don't see why this should be in Phobos versus druntime. Having 128 bit types as a library is already bizarre compared to what you get in basically any other systems programming language (even if we then special case them to use the proper compiler intrinsics i.e. the code generated at the moment is terrible), but if we really do that why would they be split across phobos and druntime?

Thinking about that, I also think we should define a decent public interface on druntime and not duplicate it on phobos. We do a similar duplication for, e.g. std.math and core.math builtins/intrinsics, which is currently horrible. See https://sourcegraph.com/github.com/dlang/dmd/-/blob/src/dmd/toir.d?L523 .
Another thing I'm currently thinking about wrapping Cent into a different aligned struct: Isn't this going to make loads/stores of the struct data potentially slower? Why not provide those interfaces on the aligned struct instead of wrapping it?

Having 128 bit types as a library is already bizarre

Not really. See std.complex. It used to be a builtin type, but D got to the point where it could be done handily as a library type. Int128 is a rarely used type (yes, I know some people use it a lot). I've never had a use for it in 45 years of programming. So why make the compiler more complex than it needs to be?
Having a 128 bit integer will bloat a lot of the internal data structures, that are used a lot, by 64 bits. That's pretty expensive.

why would they be split across phobos and druntime?

Druntime provides the guts that need to be adjusted for each target. Phobos provides the user interface. std.complex is in Phobos. We also split math routines between druntime and phobos.
Other languages do it as a builtin type because their metaprogramming facilities are deficient or nonexistent.
Lastly, doing it in Phobos means it can be done now.

Having 128 bit types as a library is already bizarre

Not really. See std.complex. It used to be a builtin type, but D got to the point where it could be done handily as a library type. Int128 is a rarely used type (yes, I know some people use it a lot). I've never had a use for it in 45 years of programming. So why make the compiler more complex than it needs to be?

Your experience is not universal. 128-bit integers are very useful in applications like cryptography and random number generation. This implementation is useless to me, as it appears to provide neither ucent nor 128-bit literals.

Having a 128 bit integer will bloat a lot of the internal data structures, that are used a lot, by 64 bits. That's pretty expensive.

why would they be split across phobos and druntime?

Druntime provides the guts that need to be adjusted for each target. Phobos provides the user interface. std.complex is in Phobos. We also split math routines between druntime and phobos.
Other languages do it as a builtin type because their metaprogramming facilities are deficient or nonexistent.
Lastly, doing it in Phobos means it can be done now.

Which metaprogramming facilities can we use to support 128-bit literals? Does this pass isIntegral? Can we use unsigned 128-bit integers now? What will happen when size_t becomes 128-bit? Will it be an alias to this somehow, or will D simply refuse to support such a platform? Why would someone use this over their existing implementations? Will there be a 128-bit floating point struct as well?
I have a permuted congruential generator RNG implementation that could have supported 128-bit state and/or values trivially - all I need is to uncomment two lines - if ucent were implemented with ucent literal support. Instead, I will need to do some nontrivial refactoring to support this. If this is the best I can hope for, I won't be waiting for this module to support unsigned 128-bit integers and will instead use some existing 128-bit unsigned integer code or simply delete the code entirely. I'm thinking the latter, since parts of std.random (uniform01, notably) won't work unless the RNG produces types that don't pass isIntegral or isFloatingPoint.
I was proud that this implementation was so much cleaner than the reference C++ implementation. Now I have to choose between weakening it or making it as ugly as the C++ it was based on. I am disappointed.

Your experience is not universal.

I didn't say it was. But I do have a lot of experience with a variety of code.

128-bit integers are very useful in applications like cryptography and random number generation.

Both of which are a very tiny percentage of written code. Yes, I've done both.

This implementation is useless to me, as it appears to provide neither ucent nor 128-bit literals.

it's a replacement for ucent
having a literal is pretty trivial, just make a template int128!"92834572783456287346587324652834756" that uses CTFE to create an Int128 instance. Anyone can write it, it's just atoi(). I didn't bother yet, because there's no point if Int128 is not approved.
I didn't implement Uint128 yet because there's no point in doing the work if Int128 is not approved.

What will happen when size_t becomes 128-bit?

It's highly unlikely. 64 bit pointers can already address all the atoms in the universe, what use is there for 128 bit pointers?

isIntegral()

Could be done with overloads.
I'm sorry you're disappointed in this, but it is progress and the whole point is to make it usable.

having a literal is pretty trivial, just make a template int128!"92834572783456287346587324652834756" that uses CTFE to create an Int128 instance. Anyone can write it, it's just atoi(). I didn't bother yet, because there's no point if Int128 is not approved.

Feels like that is hacky. If we want someday to support that as a built-in type, we need to deprecate all of this stuff and we can do it in a way that whole deprecation is not needed, even though it's library implemented. So why not?

Your experience is not universal.

I didn't say it was. But I do have a lot of experience with a variety of code.

128-bit integers are very useful in applications like cryptography and random number generation.

Both of which are a very tiny percentage of written code. Yes, I've done both.

D code is also a very tiny percentage of written code. I do not see how this is relevant. Why should any code have unnecessary friction?

This implementation is useless to me, as it appears to provide neither ucent nor 128-bit literals.

it's a replacement for ucent
having a literal is pretty trivial, just make a template int128!"92834572783456287346587324652834756" that uses CTFE to create an Int128 instance. Anyone can write it, it's just atoi(). I didn't bother yet, because there's no point if Int128 is not approved.
I didn't implement Uint128 yet because there's no point in doing the work if Int128 is not approved.

What will happen when size_t becomes 128-bit?

It's highly unlikely. 64 bit pointers can already address all the atoms in the universe, what use is there for 128 bit pointers?

You know that pointer size isn't equivalent to physical address size. x86-16 had 32-bit far pointers, but only 20 bits of physical addressing. x86-64 will need extended pointers to address more than 4PB of memory, as several bits are used for other purposes. I can easily imagine living long enough to see systems like this. Yet, even if we don't get to that point, system designers may find it useful to encode other data in pointers. RISC-V, with its planned RV128I ISA, is already preparing for this. 128-bit is an inevitability, not a possibility.
Also, and this is just nitpicking, current estimates place the number of atoms in the universe somewhere in the neighbourhood of 10^80. That requires more than 256-bit addressing.

isIntegral()

Could be done with overloads.

isIntegral is a template. It explicitly rejects all integral types except for those that are built-in.

I'm sorry you're disappointed in this, but it is progress and the whole point is to make it usable.

Then make it usable. In this state, it's another set of items for the todo list.

x86-64 will need extended pointers to address more than 4PB of memory, as several bits are used for other purposes

Source?  W/5-level-paging (57-bit address space), we can already address 128pb, and I see no reason why it wouldn't be possible to use all 64 bits given a further extension.

x86-64 will need extended pointers to address more than 4PB of memory, as several bits are used for other purposes

Source? W/5-level-paging (57 significant bits), we can already address 128pb, and I see no reason why it wouldn't be possible to use all 64 bits given a further extension.

I suppose my knowledge is a bit out of date then, since 52 bits was the maximum possible (and 48 was the maximum available) at the time I looked into it. I don't believe they'll be able to go past 63 bits without dropping the NX bit or expanding beyond 64-bit, though.

The NX bit is set in the page tables (and therefore is a property of a mapping); it is not part of the address itself.

After re-reading the criticism towards this design I unfortunately have to concur what the LDC maintainers are saying in the forum topic: The user interface should be the cent keyword, not a Phobos struct.
The problem here is that you're trying to change a long-agreed spec just to take some shortcuts with the implementation. We have been keeping a high bar for new modules to Phobos for a long time. Adding a module just because it's easier to implement than a cent interface in the compiler (that can even forward to the DRunTime just like this one) is nowhere near enough of a reason. I hereby reject this PR (as far as my rejection counts).
That said, this one would still be a nice DUB library while waiting for cent.

For now I don't actually mind this being in druntime but I just think it being a Phobos module apparently solely for the purpose of some operator overloads is weird and somewhat annoying for betterC

When I add bitfields to the language, I get blocked because people say it should be done with metaprogramming. When I add a much-requested feature with metaprogramming, it gets blocked for not being built in. dlang/dmd#13568

I've added a few compiler intrinsics for core.int128 so that it is pretty much a built-in type.  The only negative thing I have to say is that the layout of Cent is not BigEndian friendly, and the conversion between library<->native results in slightly worse code-gen than when layout matches native cent.
i.e: This results in same code-gen as if the input parameters were already ucent.
// struct Cent { ulong lo; ulong hi }
version (LittleEndian):
const tmp1 = *cast(ucent*)&c1;  // mov (load)
const tmp2 = *cast(ucent*)&c2;  // mov (load)
const tmp3 = tmp1 OP tmp2;      // op
return *cast(Cent*)&tmp3;       // ret (because it's already in the correct registers)

vs. This results in more shifts, masks and movs.
// struct Cent { ulong lo; ulong hi }
version (BigEndian):
const tmp1 = cast(ucent)c1.lo + (cast(ucent)c1.hi << 64); // mov+xor+ad[dc] (load)
const tmp2 = cast(ucent)c2.lo + (cast(ucent)c2.hi << 64); // mov+xor+ad[dc] (load)
const tmp3 = tmp1 OP tmp2;                                // op+mov
return Cent(cast(ulong)tmp3, cast(ulong)(tmp3 >> 64));    // mov+ret

It seems a bit too late now to swap the lo and hi fields, replacing enum One = Cent(1); with enum Cent One = {lo:1}; just looks wrong, and adding a this(U lo, U hi) for consistency will just make things worse for everyone.

When I add bitfields to the language, I get blocked because people say it should be done with metaprogramming. When I add a much-requested feature with metaprogramming, it gets blocked for not being built in. https://github.com/dlang/dmd/pull/13568

The difference is that with bitfields, you're pushing for totally new semantics to the language. cent on the other hand is already on the spec. Moreover, cent is a much simpler language feature from spec perspective than bitfields would be.
In case it is not clear, the issue is not whether the implementation is the DRuntime one or a complier intrinsic. cent can be either. It's just that it needs to be a language feature from the user perspective.
If you can gather a consensus to drop cent from the spec, then I will admit this module to Phobos (with the details corrected of course).

In this case specifically I'm (can't say for others) say add it, but put it with the rest of the functions in druntime. druntime and dmd semantically are one project, so things like atomics and arrayOp are in druntime, I think 128bit integers are so fundamental that they have to go in druntime.

It seems a bit too late now to swap the lo and hi fields

Not really, it's pretty obvious that nobody has been using Cent, because of the alignment issue blocking this PR.

It seems a bit too late now to swap the lo and hi fields

Not really, it's pretty obvious that nobody has been using Cent, because of the alignment issue blocking this PR.

I can't remember whether int128 was before or after the last round of cross-platform testing I kicked off.  Ought to run it again to see how much of int128 passes on sparc64-solaris.

Surprised by the amount of comments. I wrote widest.d and I think there are more people linking about it than using it. I don't think 128-bit integers are that much used anyway, so maybe let something get rolling?

I'm not going to use 128-bit integers most likely (on purpose). But I want to leave some general comments on this discussion (I have not tried nor reviewed the actual code):

I think the name cent/ucent can be used at some point once we prove this works (it's currently a keyword, so we have as much time as we want to prove this works).
I would expect endianness to be depending on the platform. Is this not doable via version statements?
While this seems maybe like it belongs in phobos, where BigInt and octal literals live, I think this really will eventually go into druntime. Just because if anyone eventually needs to use this in druntime, it can go there, and it has no phobos dependencies (good).
I don't see any discussion of VRP here. That is one major benefit of making it a builtin type.
Any performance deficiencies I think can be handled eventually with special recognition of the type by the compiler when appropriate. This also points at putting in druntime.

I'd be good with having this in the language as a library. I'd prefer it in druntime, but it's also fine in phobos.
My two cents (pun intended)

Still blocked by https://github.com/dlang/druntime/pull/3795

Style sez:
std/int128.d(47:15)[warn]: Public declaration 'Int128' has no documented example.

but it obviously does.

@ibuclaw Same error. I don't know what it wants.

@RazvanN7 do you know what DScanner wants here?

@WalterBright :
std/int128.d(19:15)[warn]: Public declaration 'Int128' has no documented example.

@WalterBright The version(unittest) might confuse D-scanner. You could try putting the documented unittest right after the Int128 declaration.

I tried it:

embedded in the documentation for the struct
as a member of the struct
following the closing brace of the struct

No joy. I filed an issue for dscanner:
https://github.com/dlang-community/D-Scanner/issues/862
In the meantime, how do I disable this check?

There's a .dscanner.ini file that configures which checks are enabled for each file. There is a undocumented_declaration_check variable which currently lists the files for which the check is not enabled. You can  add -std.int128 to that list of checks.

Thank you. Also, dscanner does not come with the distribution.
Oh, I see why I didn't see the .dscanner.ini earlier. It has the . which hides it. What is the purpose of hiding critical files?

What is the purpose of hiding critical files?

I have no idea. When I started contributing to D this modus operandi was already put in place, but I would assume that, ideally, all checks would be enabled for all files, so it might be that the config file is just a stop gap solution until we reach that point.

.dscanner.ini also explains why doing it the way std.complex didn't work, either. That's in the disable list.

It's good that dmd.conf is not .dmd.conf

There is a undocumented_declaration_check variable which currently lists the files for which the check is not enabled. You can add -std.int128 to that list of checks.

Did that. It still fails that check.

So what about the cent/ucent in the spec and ABI? They are useless now?

We may eventually implement cent and ucent. This, in the meantime, will work.


PushState error when attempting to scroll to Hash

When I attempt to scroll to a path with a hash fragment, I get
Uncaught DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'http:/#overview' cannot be created in a document with origin 'http://localhost:3000' and URL 'http://localhost:3000/indepth/treasures'..
While it does scroll to the section of the page with the text, it ends up freezing for a 1-2 seconds.

This seems like something is wrong with how the code it setup. Do you have a failing example on codesandbox?

@Alan19 I suppose you have a mistake in path to
Wrong:
/{routhe.path}/#overview
/{routhe.path}#overview


Clear Board Modal

Description
Warning Modal to ask for confirmation before clearing the board completely.

hey, I would like to work on this issue.

Thanks @DhairyaBahl for assigning this issue to me.
I researched  on google then I found some tutorial on react models. I got the idea but I am not able to add model in code base.
It would be great  if you little explain  how to do that ?


removed majority of r2 compatibility

There is still a reference to r2 in the encounter export test, but that will be refactored when I finish my version of encounter export.

Need to merge with changes from master.


Make compatible with devtools dark theme

Devtools theme may be set to dark in its Settings or via custom CSS theme, which makes this extension panel look weird. Chrome 54 and newer provides a way to read current theme name so your extension can switch its style accordingly:
chrome.devtools.panels.themeName

Is there a way to have a dark theme ?


SSH connection doesn't get closed

I've got a problem and hopefully I don't missed any other information about this. Your plugin is working like expected but I noticed that it does not close the ssh sessions. After 24 hours there are more then 30 opened connections (can't summarize them on one fullHD screen). After some time our destination server will reach the process limit for that specific user and no new ssh connection could established.
I use EL version[1.3.6] and installed your plugin with the command line plugin installation tool that you prefer at the readme.

curl -XPUT localhost:9200/_river/fs_dokuwiki/_meta -d '
{
  "type" : "fs",
  "fs": {
    "url": "/DIRECTORY",
    "server": "HOSTNAME",
    "port": 22,
    "username": "USERNAME",
    "pem_path": "/home/USER/.ssh/id_rsa",
    "protocol": "ssh",
    "update_rate": "3h",
    "includes": "*.txt"
  }
}
'

Does there already exist a fix? If so would it be possible to compile me a working version for elasticsearch 1.3.6? Thanks :)

That's very true. Working on a fix.

I pushed a fix.
Before releasing, could you test this version?
bin/plugin -install fsriver --url https://oss.sonatype.org/content/repositories/snapshots/fr/pilato/elasticsearch/river/fsriver/1.3.2-SNAPSHOT/fsriver-1.3.2-20150120.134740-1.zip

Thanks for your help!

Hey dadoonet,
thanks for the fast work! Great! I just updated your elasticsearch plugin and will wait until tomorrow - update indices will need some time.

Okay seems not to work properly. Got only 2 connections yesterday after restart. Now I have much more currently opened connections. They simply do not close. No more "FIN_WAIT2" or "TIME_WAIT" only "CONNECTED" ("Verbunden").

Hey @dadoonet need to restart our elasticsearch once a day, otherwise our remote server won't work properly (no more ssh connections allowed). Any progress on this?

Hey @dadoonet created a pull request: https://github.com/dadoonet/fsriver/pull/104


Support for model binary changes for live reload

Ultimately, we should support live reload to all parts of truss. The most important remaining part is the data section of the truss.
A key challenge is transferring such large payloads for this. The current patch endpoint can't support this, it would be very clumsy to cram big binary blobs into the patch json. A separate endpoint is likely needed on the Control Proxy to upload large blobs. The patch endpoint can then be enhanced to accept the content hash of the blob.

Duplicate of https://github.com/basetenlabs/truss/issues/228


Dissable features

hei there,
so we have your bot in our community and it has some inapporpriate features such as the hentai search function. I was wondering if its possible to dissable those features somehow as a server admin / owner even if you dont own the bot f.e. through roles f.e. that you create a role f.e. NSFW that signalizes the bot that its allowed to enable those commands or not.
would love to hear a fast solution / reply
MirrorsEgg

Hello,
Glad to hear that you are using the bot!
I appreciate your concerns regarding inappropriate features of the bot. The solution is planned and its basic version should be implemented within 36 hours.
That being said, keep in mind that disabling hentai and other "inappropriate" features will not stop users linking similar material manually or through the regular search (~ir, ~i) functions. The bot should not be held responsible or at fault, but the users who are invoking those commands.
The bot is there only to provide convenience.

Hei Kwoth,
Thank you for the quick reply! Didnt expect such a fast reply. We just implemented bots into our community and so far things sre going well. The Bots wont be taken as responsible for what users do with them, thats obviously the users mistake for bringing up inappropriate features. Im really happy that this feature will be implemented soon, cant wait for it :P
Maybe the bot will make it as our "main chat bot" though that depends on the configurability. Is there something like a permission system planned too? F.e. That you give those who should be able to use the bot certain ranks?
Have a nice day
MirrorsEgg
Sent from my iPhone

On 09 Feb 2016, at 15:17, Master Kwoth<EMAIL_ADDRESS>wrote:
Hello,
Glad to hear that you are using the bot!
I appreciate your concerns regarding inappropriate features of the bot. The solution is planned and its basic version should be implemented within 36 hours.
That being said, keep in mind that disabling hentai and other "inappropriate" features will not stop users linking similar material manually or through the regular search (~ir, ~i) functions. The bot should not be held responsible or at fault, but the users who are invoking those commands.
The bot is there only to provide convenience.
—
Reply to this email directly or view it on GitHub.

MirrorsEgg,
Just submitted the initial pull request to get this feature going, the Permissions system is looking really good already. Worked with Kwoth tonight and things are looking promising!
Cuken

Awesome guys :) im crazy happy that you guys are so energetic on this :D your bot is amazing and im sure it'll find a great place in our big comunity :D
Sent from my iPhone

On 11 Feb 2016, at 04:33, Colin<EMAIL_ADDRESS>wrote:
MirrorsEgg,
Just submitted the initial pull request to get this feature going, the Permissions system is looking really good already. Worked with Kwoth tonight and things are looking promising!
Cuken
—
Reply to this email directly or view it on GitHub.

New release with permission system is coming in ~8 hours

Will you be giving examples of the permissions actions in the readme? I'm assuming that the new permissions will for example give me the ability to limit users ability to change volume and stuff, but I'm confused on how to use it.

It was out last night, you can type -h to see help. It has some problems atm, I will fix them within an hour, but basicaly atm you must have "Nadeko" role in order to change permissions.
After the fix you will be able to change the required role, and server owner won't need a role to change the permissions.


No issue here

Just wanted to say, this is a very good concept which I like a lot. Good work!!!

@artworked Great to hear that. Thank you! :muscle:  🎉


Doc updates for NoReadyVirtController

@sradco @nunnatsa when convenient, please review my proposed changes to this runbook file.
Thanks!
Jirka

@apinnick Can you give this lgtm? or is there any additional fix required?

@apinnick Can you give this lgtm? or is there any additional fix required?

@sradco There are still some changes to be made. I will ping you when this is ready to be merged.

Thank you for the review @apinnick , and apologies for the delay in applying it. Hopefully the content is ship-shape now.
@sradco , when you have a bit of time, please look into the changes and let me know if something looks off, and if not, feel free to merge :-)

@sradco LGTM


Issue with Select component

Description
I'm trying to use the Select component for mobile, using expo in the iOS....
When I start the select with some existing value Item, it is showing the VALUE instead of the LABEL.... is it a bug or am I messing with the component?
CodeSandbox/Snack link
No response
Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

gluestack-ui Version
3.3.1
Platform

[ ] Expo
[ ] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

Hey @Gluant101, Please upgrade to latest version of @gluestack-ui/themed & @gluestack-style/react.

@Viraj-10  i tested with latest version, issue still exist.

Hey @teckbeng-payboy, Please check with latest version. @gluestack-ui/themed version 1.0.30 and @gluestack-ui/config 1.0.10.

I checked as well and still have the same issue too.

Hey @pierrebiver @Gluant101, when you pass the value to selectedValue pass selectedLabel as well.

I did passed both and it still won't work using expo on iOS. On top of that (I can open another ticket maybe) I cannot seems to select a item anymore, when I click on a item, it won't do anything, the list stays open and it was working before I upgraded it to the latest version.

@Viraj-10 I just tried to upgrade our apps from native-base to gluestack-ui.
Why do we have to set selectedLabel everytime we update selectedValue?
I do not know the matching label at various positions where I am trying to update the selectedValue from.
In native-base it wasn't required to set the selectedLabel. It updated automatically when updating selectedValue.
Is this behaviour intended to stay after "beta" or it is a temporary solution?

Can this be reopened? I think the selectedLabel prop is a really strange API for a Select component. We are rendering a list of SelectItem components with labels and values so why must we tell the component which label to render?
My expectation would be when the value of selectedValue changes, the Select component will use the SelectItem collection to figure out which label to display.
Also the documentation for selectedValue is currently incorrect, it's not a boolean.

@Viraj-10 Agreed this is really weird especially since selectedLabel is deprecated, but, leaving it out gives you the value as the display

I'm facing the same problem, and neither initialLabel or selectedLabel seems to work as expected.

@petruspierre, Can you please open new issue with minimal reproduction?


The bench tool

Codecov Report

Merging #52 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage     100%   99.94%   -0.06%
==========================================
  Files          10       10
  Lines        1725     1725
  Branches      146      146
==========================================
- Hits         1725     1724       -1
- Misses          0        1       +1


Oracle RAC connection

Is there a way to connect to an Oracle RAC with two servers in failover mode, as JDBC ?
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=server1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=server2)(PORT=1521))(FAILOVER=on)(LOAD_BALANCE=on))(CONNECT_DATA=(SERVICE_NAME=MYRAC)))

the problem I don't have oracle RAC to test this function
did you try connection with the driver and receive any error message?
if yes can you share the trace.log file?

without a  RAC i can use a fake servername (fakeserver) for testing with JDBC.
The JDBC driver establishes the connection to myserver
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=fakeserver)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=1521))(FAILOVER=on)(LOAD_BALANCE=on))(CONNECT_DATA=(SERVICE_NAME=MYSN)))
The JDBC driver establishes the connection to myserver
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=fakeserver)(PORT=1521))(FAILOVER=on)(LOAD_BALANCE=on))(CONNECT_DATA=(SERVICE_NAME=MYSN)))
in GO
var url string = "oracle://myuser:mypassword@" + "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=fakeserver)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=myserver)(PORT=1521))(FAILOVER=on)(LOAD_BALANCE=on))(CONNECT_DATA=(SERVICE_NAME=MYSN)))" + "?TRACE FILE=trace.log"
conn, err := sql.Open("oracle", url)
if err != nil {
fmt.Printf("error : %v\r\n", err)
i have only the following ouput (no trace file) :
error : empty SID and service name

the above code will not working because driver suspect you supply an url with option like this
oracle://user:pass@server/service?option=value
ok I can make a url option to let you specify other servers to connect to when connection to main server failed.
this will be in connect function.
and when you receive connection error during reading & writing process you need to connect again
is that ok for you?

yes, thanks a lot !

I made changes and push it
please test and commit
for usage read readme file version 2.2.9

tests ok
you can close the issue


Flesh out development tasks

As a new project contributor, I want the development tasks to be self-contained so that I can start working on issues immediately.

The goal of this task is to make each issue self-contained: they should contain enough direction and context that someone totally new to this project could pick them up and start working (as much as possible).
Along with #37, this task is designed to help transition from an on-site team workflow to a more distributed, open contribution workflow.

Awesome!
On Sun, Jun 4, 2017, 14:48 Lee Sharma<EMAIL_ADDRESS>wrote:

As a new project contributor, I want the development tasks to be
self-contained so that I can start working on issues immediately.
The goal of this task is to make each issue self-contained: they should
contain enough direction and context that someone totally new to this
project could pick them up and start working (as much as possible).
Along with #37 https://github.com/rubyforgood/playtime/issues/37, this
task is designed to help transition from an on-site team workflow to a more
distributed, open contribution workflow.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rubyforgood/playtime/issues/38, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMNoDROQlaZNvgCROHYTfoKV0sj9Os9ks5sAvv8gaJpZM4NvdMu
.

When I moved the development tasks over from Trello, I broke a couple of them up slightly, but this could probably use more attention.


Default easyrtcsidRegExp does not support express-session signed cookies

The default regex value of easyrtcsidRegExp is: /^[a-z0-9_.-]{1,64}$/i. However the session ids generated by express-session violate this pattern.
Here is a sample session id: s%3AhYdr-V-d6B-2PSsAdnkD8aTNLJjV3vLu.Qilpnf0QIBMm1OCMoKpuBJjsx9f4yNv92EORI1TRIAA
This violates the pattern in 2 ways:

Contains % character. This is caused by sanitization of s: -> %3A, which is used by express session as a prefix to all session ids (see here)
Generated session id is too long (80 chars) whereas the limit of this pattern is 64 chars

@zacharysang I understand your issue, the problem I have with changing the default easirtcid reg exp because it is used on object properties and I think many EasyRTC user would not want to have something else then alphanumeric in the ID, Yet.
The current solution is to pass the option easyrtcsidRegExp see details here:

https://github.com/priologic/easyrtc/blob/master/lib/easyrtc_default_options.js

@zacharysang can you provide new RegExp and I will consider patch over time.

Thanks for your response @hthetiot. I would like to clarify and ensure we are both talking about the easyrtcsid (not the normal easyrtcid). The value for easyrtcsidRegExp is /^[a-z0-9_.%-]{1,100}$/i (although this may not precisely describe the session ids generated by express-session).
While I understand wanting to avoid breaking changes for other users. I am not as clear on why the default behavior when enabling sessions results in invalid session ids. Does this mean that overriding the easyrtcsidRegExp option is required when enabling sessions? If so, is there a place in the docs that this requirement is stated?

Thank you @zacharysang, I miss understood "easyrtcsid" vs "easyrtcsid".
I'm willing to change the easyrtcsidRegExp I will do PR with /^[a-z0-9_.%-]{1,100}$/i for you to test.

see #435 @zacharysang

@zacharysang if you can test the branch ugs/easyrtcsidRegExp-options then i will merge if all good.

An update on this:
The specified regex seems to be working well. I have had it running on a local project of mine for a couple weeks without issue (I started using this around when I reported the issue).
However, I would like to look a little more into the session id generator being used to see if we can get a regex that more closely matches (we may be able to restrict the sid to less than 100 chars, and there may be some other characters in the supported charset that are still missing from the pattern (although this would be surprising since they have not appeared so far)).
I will have more time to look into this later in April after several school projects are submitted.

Thank you @zacharysang
I will wait you feedback on the generator and the Regexp.
I have not myself being able to find info about express cookie UUID detais.


Multiple Pillow versions in requirements.txt

Hi!
I noticed that requirements.txt has three different versions of the Pillow dependency, which interfered with the pip install -r requirements.txt command.
By chance, is it possible that only the most recent version of Pillow is required to run the code?
Thanks!

fixed here https://github.com/ECC-BFMC/Computer/commit/06201538b608cb81cace34b7c84966c3f10d98ca


Question: How to implement Google login with socialite?

If we are going to have tenant wise users (i.e., users table is moved under tenant), how can we implement socialite based google auth? We need to specify a callback/redirect URL and we will have a different URL for each tenant (because of the subdomain - tenant1.example.com, tenant2.example.com...)
This callback/redirect URL need to be added into Google's portal & hence I dont see any way to handle wildcards (unless Google supports wildcards for subdomain) due to this.
A possible solution will be to use IP address (since all subdomains too are served by the same IP:port) in the callback URL that we specify in Google, but I was wondering if
a) we can have a more elegant solution here for multi tenant setups  & (or)
b) Is it a mistake to move the users table to tenant folder itself?

Hi.

Is it a mistake to move the users table to tenant folder itself?

Definitely not, that's how most apps do this.
As for a more elegant solution, assuming your [redirect configg(https://laravel.com/docs/6.x/socialite#configuration) has the right (tenant-specific) URL and the only issue is adding the URL to Google's portal, I think you have two options:

Hook into the tenant.created event and use some sort of Google API to add this host
Just use the IP address.

Honestly if Google is fine with an IP address, I'd just go with that.


Create sales order app with SAP Cloud Platform Rapid Application Development by Mendix

A couple of issues with step 6:
Point 1 reads like we are adding an activity to a microflow called Get List when we are actually adding an activity of Get List to the microflow ACT_...
The URL we want to execute is not .../$metadata but .../SalesOrder

Hi Mark, I will fix it, thanks

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Looker Import Target Folder

Hi,
Is it possible to implement a feature that allows for importing to a non-Shared folder? Currently, the target folder must start with "Shared," but I would like to import for example user 14's space in staging to user 14's space in prod. Thanks!

@dliu9999 This capability is now possible with the recent release of #91.  Thanks for your suggestion!


warn about registering customer service /5

Fixes #29152
Bruno, can't we get an ASPnnnn code analysis to detect this?
Review URL internal only

Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/error-handling.md
Handle errors in ASP.NET Core

Bruno, can't we get an ASPnnnn code analysis to detect this?

@mitchdenny @captainsafia What do you think about this?

cc @david-acker

It seems like adding an analyzer to detect this would be straightforward. The one for ASP0001 serves a similar purpose.

It seems like adding an analyzer to detect this would be straightforward. The one for ASP0001 serves a similar purpose.

@david-acker  can you review https://github.com/dotnet/aspnetcore/issues/48178 and suggest any improvements?

@Rick-Anderson the team usually create analyzer issues using this template https://github.com/dotnet/aspnetcore/issues/new?assignees=&labels=api-suggestion%2C+analyzer&projects=&template=60_analyzer_proposal.md&title=

dotnet/aspnetcore#48180 LGTM!

@david-acker Thanks David! You rock! 🎸


Fail to build environment_cp both Day 4 and Day 5

On the Linux VM Day 4 cellprofiler env build fails with
    /tmp/pip-build-env-2pbks69z/normal/lib/python3.8/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-pmbnfk13/centrosome_2b604ded1ce8454f91ccb472bbdfc7a2/centrosome/_propagate.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)

      Error compiling Cython file:
      ------------------------------------------------------------
      ...
            heap.ptrs[child][k] = new_elem[k]
        heap.items += 1

        # restore heap invariant, all parents <= children
        while child>0:
            parent = (child + 1) / 2 - 1 # __parent(i)
                                     ^
      ------------------------------------------------------------

      centrosome/heap.pxd:148:31: Cannot assign type 'double' to 'unsigned int'
      Compiling centrosome/_propagate.pyx because it changed.
      Compiling centrosome/_cpmorphology2.pyx because it changed.
      Compiling centrosome/_convex_hull.pyx because it changed.
      Compiling centrosome/_fastemd.pyx because it changed.
      Compiling centrosome/_filter.pyx because it changed.
      Compiling centrosome/_lapjv.pyx because it changed.
      [1/6] Cythonizing centrosome/_convex_hull.pyx
      [2/6] Cythonizing centrosome/_cpmorphology2.pyx
      [3/6] Cythonizing centrosome/_fastemd.pyx
      [4/6] Cythonizing centrosome/_filter.pyx
      [5/6] Cythonizing centrosome/_lapjv.pyx
      [6/6] Cythonizing centrosome/_propagate.pyx
      Traceback (most recent call last):
        File "/home/training/miniconda3/envs/imaging_course_cp_day4_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/training/miniconda3/envs/imaging_course_cp_day4_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/training/miniconda3/envs/imaging_course_cp_day4_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
        File "/tmp/pip-build-env-2pbks69z/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 366, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/tmp/pip-build-env-2pbks69z/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-2pbks69z/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 89, in <module>
        File "/tmp/pip-build-env-2pbks69z/normal/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
          cythonize_one(*args)
        File "/tmp/pip-build-env-2pbks69z/normal/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
          raise CompileError(None, pyx_file)
      Cython.Compiler.Errors.CompileError: centrosome/_propagate.pyx
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

failed

CondaEnvException: Pip failed

On the Linux VM Day 5 Cellprofiler build fails with
stall-bxlzz3lv/centrosome_0d701048d79245f88a0b4e72628ad0a5/centrosome/_cpmorphology2.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)
      /tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-bxlzz3lv/centrosome_0d701048d79245f88a0b4e72628ad0a5/centrosome/_fastemd.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)
      /tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-bxlzz3lv/centrosome_0d701048d79245f88a0b4e72628ad0a5/centrosome/_filter.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)
      /tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-bxlzz3lv/centrosome_0d701048d79245f88a0b4e72628ad0a5/centrosome/_lapjv.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)
      warning: centrosome/_lapjv.pyx:281:12: Non-trivial type declarators in shared declaration (e.g. mix of pointers and values). Each pointer declaration should be on its own line.
      warning: centrosome/_lapjv.pyx:281:18: Non-trivial type declarators in shared declaration (e.g. mix of pointers and values). Each pointer declaration should be on its own line.
      /tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-bxlzz3lv/centrosome_0d701048d79245f88a0b4e72628ad0a5/centrosome/_propagate.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)

      Error compiling Cython file:
      ------------------------------------------------------------
      ...
            heap.ptrs[child][k] = new_elem[k]
        heap.items += 1

        # restore heap invariant, all parents <= children
        while child>0:
            parent = (child + 1) / 2 - 1 # __parent(i)
                                     ^
      ------------------------------------------------------------

      centrosome/heap.pxd:148:31: Cannot assign type 'double' to 'unsigned int'
      Compiling centrosome/_propagate.pyx because it changed.
      Compiling centrosome/_cpmorphology2.pyx because it changed.
      Compiling centrosome/_convex_hull.pyx because it changed.
      Compiling centrosome/_fastemd.pyx because it changed.
      Compiling centrosome/_filter.pyx because it changed.
      Compiling centrosome/_lapjv.pyx because it changed.
      [1/6] Cythonizing centrosome/_convex_hull.pyx
      [2/6] Cythonizing centrosome/_cpmorphology2.pyx
      [3/6] Cythonizing centrosome/_fastemd.pyx
      [4/6] Cythonizing centrosome/_filter.pyx
      [5/6] Cythonizing centrosome/_lapjv.pyx
      [6/6] Cythonizing centrosome/_propagate.pyx
      Traceback (most recent call last):
        File "/home/training/miniconda3/envs/imaging_course_cp_day5_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/training/miniconda3/envs/imaging_course_cp_day5_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/training/miniconda3/envs/imaging_course_cp_day5_2024/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
        File "/tmp/pip-build-env-b66uhii6/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 366, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/tmp/pip-build-env-b66uhii6/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-b66uhii6/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 89, in <module>
        File "/tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
          cythonize_one(*args)
        File "/tmp/pip-build-env-b66uhii6/normal/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
          raise CompileError(None, pyx_file)
      Cython.Compiler.Errors.CompileError: centrosome/_propagate.pyx
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

failed

CondaEnvException: Pip failed

https://github.com/ome/EMBL-EBI-imaging-course-04-2024/pull/14


Why does this menu exist?

It seems like the purpose of this menu (to turn on MDM for certain groups) is redundant, considering the menu where you actually assign policies based on groups. It's like having two on-switches on the same control. Am I missing something here?
EDIT: Okay, I think I might have figured it out. The menu exists as a gateway for all MDM vendors, not just Intune. So this has to exist in order to allow other MDM vendors to be managed alongside Intune. This makes sense now.
Second question: What happens when a user does not have any policies applied in Intune, but is enabled for MDM?

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

ID: b95868d3-c141-0038-69b2-7a6a84d817d8
Version Independent ID: b68e29a4-fe87-3c20-4abc-06ab815f33ee
Content: Azure AD and Microsoft Intune - Automatic MDM enrollment in the new Portal
Content Source: windows/client-management/mdm/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md
Product: w10
GitHub Login: @MariciaAlforque
Microsoft Alias: maricia

@officedocsbot assign @mypil

Dear @thedrum808 ,
What happens when a user does not have any policies applied in Intune, but is enabled for MDM? - MDM and Intune are different products, there is no need to deploy Intune if you need to use MDM functionality. You should use CSP (Configuration service provider reference) to configure settings on the device.
Thank you

@thedrum808 - From our understanding, the issue you raised has been MaratMussabekov. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


[Bug]: Binding that belongs to a commented JS statement still gets evaluated

Steps to reproduce

Head to the API tab and edit the response body of an API
Add a JSON key-value pair with a binding eg: { "ABC": {{Input1.text}} }
Comment the key value pair and notice the binding to be evaluated

Loom video
https://www.loom.com/share/4737dfed98574fa0b91fb1b7aedf5fb9

To solve this issue, we will have to remove comments before evaluation. Since removal of comments will require and AST parsing, it will have a performance impact.
We are putting this back in icebox till we can figure out a better solution.


My function code doesn't contain an If statement like the example

In the 'Add code that uses the output binding' instructions there's no indication that I need to move to the index.js file to complete the step.
After adding the context.bindings.msg line my code looks like the attached. It doesn't have an If statement and doesn't match the example given in docs.

Kind Regards
Daniella

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

ID: ca7362b2-b991-a5bb-45e8-1e6d9ebb04d5
Version Independent ID: 6dd2cefe-f557-0ca9-c8cc-6b0e2f762a9f
Content: Connect Azure Functions to Azure Storage using Visual Studio Code
Content Source: articles/azure-functions/functions-add-output-binding-storage-queue-vs-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@LilacBrandy Thanks for the feedback! We will review and update accordingly.

@ggailey777 the code here is part of an include file. So, assigning this issue to you for further review and to update accordingly.


Ability to track non-numerical (Feature Request)

Hi!
I just saw your new component in HACS and was trying to use it in a slightly different case.
What I am wanting to achieve is to track how long a media player is in a specific state.  Would it be possible to set this up so you can track a specific state?
This might be beyond the design on this component, and that's okay - but I thought it would be worth asking 😄 .
For example, how long was a media player in the "playing" state.  Another use would be tracking how long a device was online or offline.  Do you think this is something you would be able to add to this sensor?
Thanks!
DeadEnd

I think this is out of scope of this component. Also, using a template sensor you should be able to go something like: {{ (now().timestamp() - states.sensor.0x00158d00027bf7f5_click.last_updated.timestamp()) | timestamp_custom('%H:%M:%S', False) }}, just copying this from https://community.home-assistant.io/t/display-how-long-ago-a-sensor-state-changed/190277/6

Thanks, I'll take a look at that template sensor instead.
Wasn't sure what it would take and if this custom component would be able to do it.
I'll close this then.
Cheers!
DeadEnd


Telegram bot cannot see messages from group

Hello,
I created a little nodeJS application that listen to messages send to my telegram bot, then answere.
All is right for that, it's working well.
But after that, I wanted to link my bot to the IFTTT telegram bot, to make them "discuss" into a telegram group.
So I created a group with me, my nodeJS bot, and the IFTTT bot. When I send a message in the group, my nodeJS bot see it, and reply correctely.
But when the IFTTT bot send a message into the group, I don't receive anything in the "on message" event.
This is my code:
const TelegramBot = require('node-telegram-bot-api');
const token = 'XXXXXXX:XXXXXXXXXXXXXXXXXXXXXX';  (= my token)

bot.on('message', (msg) => {
	DecryptFunction(msg.text, function (ReturnResponse) { bot.sendMessage(msg.chat.id, ReturnResponse);})
});

I already set my bot privacy to disable then add it to the group as admin.
Thanks in advance for your help

What function is "DecryptFunction"?
By the way before make any complicated operation, try to debug with console.log like this:
bot.on('message', (msg) => {
    console.log(msg);
});

So you can know if is a problem of bot in general or problem of your function.

Bot can't read other bots messages!
See Bots FAQ.

Oh actually I didn't saw this point, thanks for your answere!
I was already thinking about a solution like that, I will change my app :)
Thanks!


frontsite: Patron cancel loan bug

Package version (if known):
Describe the bug
In the frontsite in the your loans section if we cancel a loan and we change pages, for example we go to the home page by clicking the ILS logo we will get an error
Steps to Reproduce

Go to your loans
Click on cancel for a loan
Click on ILS logo
See error

Expected behavior
Even if the action is not finished we should not get an error
Screenshots (if applicable)

Additional context
Related issues: #30

Nice catch!
In fact the use of withCancel was correct but they did not check if the component was unmounted at that point. There may be other occurrences of this issue; in a previous PR I went over all the editors, those should be correct at least.


Unclear how environment works?

I tried opening HW10 and clicking the "Environments" button, and a console with the following tab popped up

But like it didn't have any contents? Not sure how it works

Oh yeah, you need to hit "Run" before trying to debug or look at the environment diagrams. I'll add a separate issue for that.

Oh ok that would fix this.


Update Meridio-Operator submodule

Enable configuration for attractors, vips and gateways

/reverify

Failures with static analysis jobs look like legit lint issues.
The rest of the jobs passed successfully.


Add doc on sigstore policy-controller

Fixes #491
Adds doc on using sigstore policy-controller w/ Kubernetes to verify container provenance.
Signed-off-by: Ian Lewis<EMAIL_ADDRESS>

@laurentsimon @asraa @joshuagl friendly ping
@hectorj2f @vaikas I wrote a short example for how to use sigstore policy-controller to verify images created by our container workflow. We would kindly appreciate feedback.

@ianlewis Thanks for doing this 🤗 ! It looks good to me, I just let some comments in relation to the last paragraph.


Units of QM9 targets

Hi,
Thanks for the code.
Different papers seem to report different units and there is large difference in the errors of these papers like MPNN and k-gnn ( https://arxiv.org/pdf/1810.02244.pdf ).  Can you let me know what are the units of targets for QM9 dataset reported in the paper?

The paper reports chemical accuracy, as in the Gilmer et al. 2017 paper. This is derived from the mean absolute error (which is reported in the paper you cite), see https://github.com/microsoft/tf-gnn-samples/blob/master/tasks/qm9_task.py#L279
So for example, you can convert the chemical accuracy 2.36 reported in Tab. 2 of https://arxiv.org/pdf/1906.12192.pdf for GNN-MLP0 on task mu into MAE by multiplying with the corresponding factor in https://github.com/microsoft/tf-gnn-samples/blob/master/tasks/qm9_task.py#L22 (the list is in order of the tasks in the table), so this corresponds to a MAE of 2.36 * 0.066513725 = 0.156972391

Thanks.


The documentation for the latest version of ivory-backend-c is missing on Hackage.

The documentation for the latest version of ivory-backend-c is missing on Hackage. It's been pending on Hackage for some time, this usually indicated that Hackage wasn't able to build the package.
Is it possible for you to manually upload the package using cabal upload --doc, please?
Thanks!

I'll push new docs when we make a Hackage release soon.

Thanks

I've made a new release for all the Ivory related packages at version <IP_ADDRESS> (ivory-quickcheck is <IP_ADDRESS>, for no good reason).
Ccing @cblp, @grwlf, @wiz, @Hodapp87, in case you're interested.
Sorry all for the delays in responding to issues!


Better interop with other JVM languages

Most notably Scala, Kotlin and Clojure. We could write a sample project that makes sure at least:

there's no compilation error due to type parameter inference.
there's no issues with nullness checker.

@tobias- IIRC your Armeria-based project is written in Kotlin. It'd be awesome if you can tell us any issues you've encountered so far that makes your code unnecessarily verbose.

 The syntax for them is slightly different in Kotlin, and the compiler seems less able to figure out what generics are needed. Thus the following generics nightmares:
interface GrpcDecorator<T> : Function<Service<HttpRequest, HttpResponse>, DecoratingService<HttpRequest, HttpResponse, HttpRequest, HttpResponse>>

class GrpcWebCors(kodein: Kodein) :
    GrpcDecorator<CorsService>,
    Function<Service<HttpRequest, HttpResponse>, DecoratingService<HttpRequest, HttpResponse, HttpRequest, HttpResponse>>
    by
    CorsServiceBuilder
...
        .newDecorator() as Function<Service<HttpRequest, HttpResponse>, DecoratingService<HttpRequest, HttpResponse, HttpRequest, HttpResponse>>

private fun ServerBuilder.addHeaders(httpsOnly: Boolean) {
    decorator { oldService: Service<HttpRequest, HttpResponse> ->
        object : SimpleDecoratingService<HttpRequest, HttpResponse>(oldService) {
            override fun serve(ctx: ServiceRequestContext, req: HttpRequest): HttpResponse {
                if (httpsOnly) {
                    ctx.addAdditionalResponseHeader("Strict-Transport-Security", "max-age=31536000; includeSubDomains; preload")
                }
                ctx.addAdditionalResponseHeader("x-server-version", GitProperties.version)
                return delegate<Service<HttpRequest, HttpResponse>>().serve(ctx, req)
            }
        }
    }
}

I think it may be beyond the scope of Armeria to fix this, although a kotlin-project with just helper(extension) methods for kotlin would be nice. Kotlin excels at embellishing existing classes with new methods. I would prefer to write something like:
decorator {
    decorate { ctx, req ->
        if (httpsOnly) {
            ctx.addAdditionalResponseHeader("Strict-Transport-Security", "max-age=31536000; includeSubDomains; preload")
        }
        ctx.addAdditionalResponseHeader("x-server-version", GitProperties.version)
        delegate().serve(ctx, req)
    }
}

I'll let you know if I can think of anything else.

I still wish to know the before and after of your code. Would you mind pasting it?

Sure. The first example is still not working without a lot of generics:
https://gist.github.com/tobias-/cbdc441872d2256b1d7a318b54ae057e

Scala example:
object Test {
  import brave.Tracing
  import com.linecorp.armeria.client.ClientOptionsBuilder
  import com.linecorp.armeria.client.brave.BraveClient
  import com.linecorp.armeria.client.logging.LoggingClient

  // ok
  val a = new ClientOptionsBuilder()
    .decorator(LoggingClient.newDecorator())
    .build()

  // can't compile:
  // [error] /path/to/Test.scala:62:6: overloaded method value decorator with alternatives:
  // [error]   [I <: com.linecorp.armeria.common.HttpRequest, O <: com.linecorp.armeria.common.HttpResponse](decorator: com.linecorp.armeria.client.DecoratingClientFunction[I,O])com.linecorp.armeria.client.ClientOptionsBuilder <and>
  // [error]   [T <: com.linecorp.armeria.client.Client[I,O], R <: com.linecorp.armeria.client.Client[I,O], I <: com.linecorp.armeria.common.HttpRequest, O <: com.linecorp.armeria.common.HttpResponse](decorator: java.util.function.Function[T,R])com.linecorp.armeria.client.ClientOptionsBuilder
  // [error]  cannot be applied to (java.util.function.Function[com.linecorp.armeria.client.Client[com.linecorp.armeria.common.HttpRequest,com.linecorp.armeria.common.HttpResponse],com.linecorp.armeria.client.brave.BraveClient])
  // [error]     .decorator(BraveClient.newDecorator(Tracing.current()))
  // [error]      ^
  // [error] one error found
  val b = new ClientOptionsBuilder()
    .decorator(BraveClient.newDecorator(Tracing.current()))
    .build()

  // ok
  val c = new ClientOptionsBuilder()
    .decorator[Client[HttpRequest, HttpResponse], BraveClient, HttpRequest, HttpResponse](
      BraveClient.newDecorator(Tracing.current())
    )
    .build()
}

@rfkm Looks similar to my problem? Basically you need to force-cast with disabled warnings to get the right generics?

One thing I'd like is not to have to use Optional<> in annotated rest interfaces. If a variable is marked as @Nullable (or one of the other 3-4 annotations with the same purpose) it would allow missing fields annotated with e.g. @Header. In Kotlin, that would mean a String? instead of Optional and it would work better with kotlin-specific operators designed to handle nullability. If IntelliJ is used to program Java, annotating with @Nullable would probably be as good as Optional for clarity in code.

I'd like to assign this issue to @ikhoon because he knows Scala knows well. :wink: It'd be nice to have Scala and Kotlin (and Clojure?) examples that demonstrates smooth integration.

I need to get some hours to check what happens with the changes in 0.96 to decorating and HttpService. It might be that the need for ugly-casting is gone.

I'd like to assign this issue to @ikhoon because he knows Scala knows well. 😉 It'd be nice to have Scala and Kotlin (and Clojure?) examples that demonstrate smooth integration. I hope to have this as a part of our 1.0.0 release.

I missed your mention. 😭 I like to handle issue before 1.0.0 release 🥰

Ok, upgrade complete. Extending the api with HttpService accepting methods did help, but still a lot of weird casts/specification of interfaces. First instinct is to push this for the future and implement a kotlin extension lib with methods for decorating, getting coroutine support etc etc.

Some loose thoughts as a Scala programmer:

It would be great if it was easy to integrate with fs2-based code in cases where we want to be truly async all the way through (i.e. streaming the http response).
Scrooge offers a more idiomatic Scala implementation of thrift. Their server-side support was hardcoded to use Twitter futures at one point, but it's fairly easy to add a template for a different kind of future (I used the one in my fork https://github.com/m50d/scrooge at a previous job).
It would be nice if we could use armeria as a backend for routes defined in rho

It would be great if it was easy to integrate with fs2-based code in cases where we want to be truly async all the way through (i.e. streaming the http response).

Armeria supports Reactive Streams. that means you can easily interop any stream library that supports Reactive Streams.
https://fs2.io/guide.html#reactive-streams

Scrooge offers a more idiomatic Scala implementation of thrift. Their server-side support was hardcoded to use Twitter futures at one point, but it's fairly easy to add a template for a different kind of future (I used the one in my fork m50d/scrooge at a previous job)

Armeria runs on the top of HTTP protocol such as H1, H1C, H2, and H2C. IIUC, scrooge supports TCP :-(
Alternatively, how about using gRPC with ScalaPB?

It would be nice if we could use armeria as a backend for routes defined in rho

That sounds good. Are you interested in making a PR? 😀

Scala example:
object Test {
  import brave.Tracing
  import com.linecorp.armeria.client.ClientOptionsBuilder
  import com.linecorp.armeria.client.brave.BraveClient
  import com.linecorp.armeria.client.logging.LoggingClient

  // ok
  val a = new ClientOptionsBuilder()
    .decorator(LoggingClient.newDecorator())
    .build()

  // can't compile:
  // [error] /path/to/Test.scala:62:6: overloaded method value decorator with alternatives:
  // [error]   [I <: com.linecorp.armeria.common.HttpRequest, O <: com.linecorp.armeria.common.HttpResponse](decorator: com.linecorp.armeria.client.DecoratingClientFunction[I,O])com.linecorp.armeria.client.ClientOptionsBuilder <and>
  // [error]   [T <: com.linecorp.armeria.client.Client[I,O], R <: com.linecorp.armeria.client.Client[I,O], I <: com.linecorp.armeria.common.HttpRequest, O <: com.linecorp.armeria.common.HttpResponse](decorator: java.util.function.Function[T,R])com.linecorp.armeria.client.ClientOptionsBuilder
  // [error]  cannot be applied to (java.util.function.Function[com.linecorp.armeria.client.Client[com.linecorp.armeria.common.HttpRequest,com.linecorp.armeria.common.HttpResponse],com.linecorp.armeria.client.brave.BraveClient])
  // [error]     .decorator(BraveClient.newDecorator(Tracing.current()))
  // [error]      ^
  // [error] one error found
  val b = new ClientOptionsBuilder()
    .decorator(BraveClient.newDecorator(Tracing.current()))
    .build()

  // ok
  val c = new ClientOptionsBuilder()
    .decorator[Client[HttpRequest, HttpResponse], BraveClient, HttpRequest, HttpResponse](
      BraveClient.newDecorator(Tracing.current())
    )
    .build()
}

@rfkm This is fixed @minwoox 's work #2239 😉

What do you think about adding out-of-the-box Option[] type support to annotated services? Could probably load and instantiate the scala.Option class dynamically? I can take a stab if it makes sense and is doable with small amount of modification. Thoughts, @rfkm and @ikhoon ?

@tobias- wrote:

One thing I'd like is not to have to use Optional<> in annotated rest interfaces. If a variable is marked as @Nullable (or one of the other 3-4 annotations with the same purpose) it would allow missing fields annotated with e.g. @Header. In Kotlin, that would mean a String? instead of Optional<String> and it would work better with kotlin-specific operators designed to handle nullability. If IntelliJ is used to program Java, annotating with @Nullable would probably be as good as Optional for clarity in code.

This has been resolved via #2766. Let me know what you think. 🙇

What do you think about adding out-of-the-box Option[] type support to annotated services? Could probably load and instantiate the scala.Option class dynamically? I can take a stab if it makes sense and is doable with small amount of modification. Thoughts, @rfkm and @ikhoon ?

If scala.Option could be supported with small amount of changes, it makes sense.
FYI

Scala 3 will introduce Null type. The Scala 3 compiler has better Java interop for nullable type.
https://dotty.epfl.ch/docs/reference/other-new-features/explicit-nulls.html#java-interop
IMO, Most Scala users prefer routing DSL than annotated service, unlike Java users. In the future, I think, it would be better to add a DSL layer for adopting Scala users.

I know, use and like it! :+1:
Thanks :bow:

@tobias- wrote:

One thing I'd like is not to have to use Optional<> in annotated rest interfaces. If a variable is marked as @Nullable (or one of the other 3-4 annotations with the same purpose) it would allow missing fields annotated with e.g. @Header. In Kotlin, that would mean a String? instead of Optional<String> and it would work better with kotlin-specific operators designed to handle nullability. If IntelliJ is used to program Java, annotating with @Nullable would probably be as good as Optional for clarity in code.

This has been resolved via #2766. Let me know what you think.

IMO, Most Scala users prefer routing DSL than annotated service, unlike Java users. In the future, I think, it would be better to add a DSL layer for adopting Scala users.

Yes, I agree. However, instead of creating a new DSL, it may be better to provide Armeria implementation to existing libraries (e.g. sttp, tapir, http4s, etc).
For example, sttp is a popular HTTP client facade in Scala, but the one of most commonly used backend implementations is AsyncHTTPClient which doesn't support HTTP2.
Contributing to their repositories might help more Scala users know about Armeria 😄

For example, sttp is a popular HTTP client facade in Scala,

I was personally working on sttp for Armeria backend. But I stopped because of multipart issue #253
I’ll resume it once #2894 is merged and released. 😀

@rfkm @m50d You might be interested in http4s/http4s#3614 PR. 😉

Let me unassign a milestone from this issue, because it's actually on-going effort spans across many releases.


@alloy -> fixes for previous web view PR

remove reference to non-existent protocol
remove test that should no longer exist

👌🏾


Ávila data is weird

There is no room to fit all the data for Ávila in a single tweet, so a thread is required. Twitter supports up to 280 characters long, but it does not work if I split the tweet string into 280 (I guess because the emojis...)
Also, in order to split the tweet better, it would be nice if the pairs "kind: status" are not splitted.

Fixed in https://github.com/e-minguez/polen/commit/6a20b8052815e88073638a347039ed3d16e0f501


Add symengine and python-symengine

This PR adds recipes for the C++ symbolic library SymEngine and its Python wrapper library. The package names here follow the convention from conda-forge.
cc @isuruf

thanks for adding the recipe!
A test for the python recipe would be nice (can be enough to just import the build package)


Test custom image but the result is poor

When I used a face as the source image and a video to drive, the results were poor, especially in places where the source image and video were not aligned, such as side faces. What could cause this？Thanks!

Currently we require the input image is square. And the pre-train model is for images with a resolution of 512*512. Check if you use these settings.
2.Although we don't need the driving and source face are exactly aligned like X2Face, we will need the two faces are roughly aligned with each other. We recommend that you follow the preprocessing steps of FOMM to preprocess the inputs. It’s important to note that compared to X2Face, we obtain more natural videos where faces move freely within the bounding box.
Our method support changing the head pose around 30°–45° in either roll, pitch, or yaw. Notice that the most recent works [7,43] that focus on pose editing typically only allow pose changes
up to around 30°, so such range of pose variance can already be considered as large in one-shot face reenactment. If the head pose difference between the source and driving image is too large, the resulting quality may drop.

Thank you for your reply!


TypeError: text.replace is not a function

I'm getting TypeError: text.replace is not a function error when trying to run with Redis. I'm using Node 18 in Docker (I looked at #810 and that doesn't solve the issue for me).
Here's what I'm trying to run:
      const vectorStore = new RedisVectorStore(new OpenAIEmbeddings(), {
        redisClient: client,
        indexName: REDIS_INDEX_NAME,
      });

      const parser = StructuredOutputParser.fromNamesAndDescriptions({
        answer: "Answer: ",
      });
      const formatInstructions = parser.getFormatInstructions();

      const template = `${PROMPT_PERSONA}\n Question: {question}`;
      const query = new PromptTemplate({
        template,
        inputVariables: ["question"],
        partialVariables: { format_instructions: formatInstructions },
      });

      const model = new OpenAI({ temperature: 0 });
      const chain = RetrievalQAChain.fromLLM(
        model,
        vectorStore.asRetriever(1),
        {
          returnSourceDocuments: true,
        }
      );
      const chainRes = await chain.call({ query });

      const result = await chain.call({
        chainRes,
      });

Am I doing something wrong?
Thanks for your help!
Edit: stack trace below.
 TypeError: text.replace is not a function
    at OpenAIEmbeddings.embedQuery (file:///node_modules/langchain/dist/embeddings/openai.js:164:46)
    at RedisVectorStore.similaritySearch (file:///node_modules/langchain/dist/vectorstores/base.js:103:90)
    at VectorStoreRetriever._getRelevantDocuments (file:///node_modules/langchain/dist/vectorstores/base.js:68:33)
    at VectorStoreRetriever.getRelevantDocuments (file:///node_modules/langchain/dist/schema/retriever.js:66:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async RetrievalQAChain._call (file:///node_modules/langchain/dist/chains/retrieval_qa.js:55:22)
    at async RetrievalQAChain.call (file:///node_modules/langchain/dist/chains/base.js:101:28)
    at async file:///app/index.js:43:24

Edit 2: line 43 in app/index.js is const chainRes = await chain.call({ query }); in the block above.

How did you fix this? Running into the same issue here...


Cannot select Done from the Screen Saver Options for Aerial in System Preferences

MacBook Pro (15-inch, Late 2016)
Mojave 10.14.1
Local display
Cannot select Done from the Screen Saver Options for Aerial. This was before the 10.14.1 Mojave update. Must Force Quite System Preferences.
I have the savers cached.

@pws442 was it just after install ? Did you restart the System Preferences panel after install (as suggested) ?
Which version of Aerial are you using ? Pretty sure I fixed this in 1.4 on Mojave.

 I downloaded all that Bask stuff, and tried to upgrade my older version, I guess (don’t know how to show the version), and it still had only the two buttons on the Options in Screen Saver. Finally, I renamed/deleted everything, and clicked the download link for the Mac, and LIFE IS GOOD AGAIN!
Wonderful screen saver. Looking forward to the other options that this has.
Paul W Schluter
<EMAIL_ADDRESS>Sent from my MacbookPro
On Oct 30, 2018, at 16:09, Guillaume Louel<EMAIL_ADDRESS>wrote:
@pws442 https://github.com/pws442 was it just after install ? Did you restart the System Preferences panel after install (as suggested) ?
Which version of Aerial are you using ? Pretty sure I fixed this in 1.4 on Mojave.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/608#issuecomment-434451106, or mute the thread https://github.com/notifications/unsubscribe-auth/AXFabx6juZR9FWPtAK9uMchVhX1sUv64ks5uqLIVgaJpZM4YCvAi.

No problem, enjoy !

I just LOVE this version. I only had 2 buttons in the options, but now a veritable plethora of nice options?
My wife has a MacBook Pro that cannot be upgraded to Mojave, even though it has 16GB RAM and a 2TB SSD. Can she use the same download as I did? I did read the release info on the beta version. Her only issue is that it stops moving after a fashion and then does not change.
Thanks a lot!
Paul W Schluter
<EMAIL_ADDRESS>Sent from my MacbookPro
On Oct 30, 2018, at 18:03, Guillaume Louel<EMAIL_ADDRESS>wrote:
Closed #608 https://github.com/JohnCoates/Aerial/issues/608.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/608#event-1936419242, or mute the thread https://github.com/notifications/unsubscribe-auth/AXFab0Mm7HQv91JpkLUb7-KYFQ3RJLmTks5uqMymgaJpZM4YCvAi.

Hey Paul
Thanks for your kind words. I'll have a much better beta specifically for High Sierra later today. I'll reply to this message when it's posted to let you know, it will be much less cumbersome than the currently posted beta.
You mentioned it stops moving on your wife laptop, I guess that's with 1.4.4 right ? Just wait a bit for next beta, the 1.4.5 betas have a fix for some video driver issues on 10.13.6.

Hi,
It was not 1.4.4, as I just downloaded it yesterday, thank you very much. In fact, I have NO CLUE as to how to check the version! I just know hers has, and mine had, only 2 buttons in the options of the screen saver preferences (and I had to force quit out of System Preferences when I went into the options. Don’t know about hers).
Thanks again!
Paul W Schluter
<EMAIL_ADDRESS>Sent from my MacbookPro
On Nov 1, 2018, at 10:03, Guillaume Louel<EMAIL_ADDRESS>wrote:
Hey Paul
Thanks for your kind words. I'll have a much better beta specifically for High Sierra later today. I'll reply to this message when it's posted to let you know, it will be much less cumbersome than the currently posted beta.
You mentioned it stops moving on your wife laptop, I guess that's with 1.4.4 right ? Just wait a bit for next beta, the 1.4.5 betas have a fix for some video driver issues on 10.13.6.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/608#issuecomment-435034997, or mute the thread https://github.com/notifications/unsubscribe-auth/AXFab_CVz8L9922d5eSgyBXF52TLWFiIks5uqv8VgaJpZM4YCvAi.

Hey Paul
No worries, that was an old version indeed with plenty of known issues. Please uninstall the old version on your wife's Mac, see the instructions here : https://github.com/JohnCoates/Aerial#uninstallation
The first method should do the trick. Then close System Preferences, and install the new beta :
https://github.com/JohnCoates/Aerial/releases/download/v1.4.5beta3/Aerial.saver.zip
Double click the Aerial.saver to install.
This version has proper support for High Sierra and fixes the outstanding bugs we had there !

Thank you Sir,
I will do this Saturday during the wee hours of the morning. My version was installed in June 2016, and I believe the file date was November 2015. Still curious as to how to check the version.
Paul W Schluter
<EMAIL_ADDRESS>Sent from my MacbookPro
On Nov 1, 2018, at 12:50, Guillaume Louel<EMAIL_ADDRESS>wrote:
Hey Paul
No worries, that was an old version indeed with plenty of known issues. Please uninstall the old version on your wife's Mac, see the instructions here : https://github.com/JohnCoates/Aerial#uninstallation https://github.com/JohnCoates/Aerial#uninstallation
The first method should do the trick. Then close System Preferences, and install the new beta :
https://github.com/JohnCoates/Aerial/releases/download/v1.4.5beta3/Aerial.saver.zip https://github.com/JohnCoates/Aerial/releases/download/v1.4.5beta3/Aerial.saver.zip
Double click the Aerial.saver to install.
This version has proper support for High Sierra and fixes the outstanding bugs we had there !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/608#issuecomment-435102110, or mute the thread https://github.com/notifications/unsubscribe-auth/AXFab0aQJ8pZqXlPwZQnMU5IILz4PUzkks5uqyZEgaJpZM4YCvAi.

No worries, regarding versions, only the most recent ones (starting with 1.4) have the version in the corner, so that's why you missed it probably.
Nov 2015 is 1.2, which was indeed the last version released until we got the project back up again this september.

Yep 1.4.5b4 is good, 1.4.5 finale is also out but there are nearly no changes that you should care about ! Enjoy !


Build failure: pkgsMusl.openexr_2

Steps To Reproduce

nix build pkgsMusl.openexr_2

Build log

Log file: openexr_2.txt
Additional context

pkgsMusl.openexr_3 builds fine for Musl.
https://github.com/NixOS/nixpkgs/pull/279949

Notify maintainers
@paperdigits
Maybe @yu-re-ka @risicle ?
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.71, NixOS, 24.05 (Uakari), 24.05.20240108.317484b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `""`
 - channels(intj): `""`
 - nixpkgs: `/etc/nix/channels/nixpkgs`

Note: I have opened this issue so I can open a PR marking it broken so it doesn't get to build for long before erroring builds that depend on it. And yes, I've been finding packages than depend on it. (such as pkgsMusl.i2p)

Duplicate of https://github.com/NixOS/nixpkgs/issues/278713

Thanks. Sorry for the duplicate.


Communication module for interacting with the backend system

We need a communication module for interacting with the RESTful API of the backend application.

See api-client.


CI for Node

Initializes with two players

Starts the game with a random player

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not


Excel not read correctly

https://data.humdata.org/dataset/6d6d947a-27ec-46a4-9fe2-3d072d5df485/resource/622574cd-d173-4b2f-95d2-b0cdf1fdd253/download/16-wrd-tab_v3_external.xls
The above file is not read correctly. Read Tab15 using list format no headers. Iterate through rows. Some rows not read eg Central African Republic.

Closing this as I think problem at my end


[stable-4.9] post-branch cleanup, version bump

No-Issue
branch cleanup for stable-4.9, same as https://github.com/ansible/ansible-hub-ui/pull/4225

I think the only things missing is removing the community/ toplevel dir, and husky from package.json (+update lockfile)


[SPARK-40371][SQL] Migrate type check failures of NthValue and NTile onto error classes

What changes were proposed in this pull request?
This pr aims to replace TypeCheckFailure by DataTypeMismatch in type checks in window expressions, includes NthValue and NTile
Why are the changes needed?
Migration onto error classes unifies Spark SQL error messages.
Does this PR introduce any user-facing change?
Yes. The PR changes user-facing error messages.
How was this patch tested?
Pass GitHub Actions

+1, LGTM. Merging to master.
Thank you, @LuciferYang.

Thanks @MaxGekk


why  can't  i  get any response when i  execute  these  install commands ?

if you can't get any response from "pip install 'git+https://github.com/cocodataset/cocoapi.git#subdirectory=PythonAPI'"
you can change it to "pip install pycocotools"
the other install commands should be ok.  May be you can check your network?


Inconsistent datetime column data importing to Turso

Bug description
Creating a db on TURSO from the local sqlite file built from Prisma results in the following error on columns using DateTime type in schema.prisma
Conversion failed: expected a string in column createdAt, found<PHONE_NUMBER>523.0
How to reproduce
Local Dev

Setup Prisma for local sqlite development
Create a model with DateTimes
Seed entries into that model

Turso Setup

Create a TURSO db using the local file
a. turso db create test-db --from-file prisma/data.db
Connect to turso via these official instructions
#21546

Query

Find a row from your model by id or whatever

Expected behavior
Row gets returned without error
Prisma information

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters"]
}

datasource db {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

model Test {
  id             String               @id @unique @default(cuid())
  createdAt      DateTime             @default(now())
  updatedAt      DateTime             @default(now()) @updatedAt
}

  let test = await prisma.Test.findMany({
    where: {
      id: 'knownID',
    }
  })

Environment & setup

OS: macos
Database: sqlite / turso
Node.js version: v18.16.1

Prisma Version
prisma                  : 5.4.2
@prisma/client          : 5.4.2
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at ../../node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.4.1-2.ac9d7041ed77bcc8a8dbd2ab6616b39013829574
Default Engines Hash    : ac9d7041ed77bcc8a8dbd2ab6616b39013829574
Studio                  : 0.494.0
Preview Features        : driverAdapters

Thanks for the report @bradymwilliams, and trying out our Turso driver adapter. We'll look into this.

Let me know if I can better report on anything or answer any other setup questions

Thanks for the report @bradymwilliams. We could reproduce this and implemented a fix, which should be part of the next release.
If you don't want to wait that long or want to confirm the fix, you can install prisma@dev and @prisma/client@dev from Npm to get our development version that already includes the fix. (Don't use that long term though please.)


Having problem defining flutter as global variable for each terminal session to recognize flutter commands

I have followed the flutter.io steps to install flutter sdk
Here are the steps I took :

Opened a new terminal window and entered the command
git clone -b beta https://github.com/flutter/flutter.git
It gave

fatal: destination path 'flutter' already exists and is not an empty directory.

I can understand that I have previously run the same command for installation process and thus have created this directory . fine
Then I changed the path by : export PATH=pwd/flutter/bin:$PATH
as i press return a new line

Emperor-MacBook-Pro:~ Notorious$
appears as usual whenever we press return in terminal

To create a new .bash_profile file i commanded terminal touch .bash_profile
To Open the created .bash_profile i commanded sudo nano .bash_profile
Terminal asked for password and I gave it the password . It opened the .bash_profile file.
There i exported path as export PATH=/flutter/bin:$PATH and Hit control + X to save and quit -> Y to yes and return key to return back to terminal window
Then I entered source $HOME/.bash_profile to refresh the current window
It gives me

-bash: export: =': not a valid identifier -bash: export: /flutter/bin:/Users/mac/flutter/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin': not a valid identifier

When I command $echo $PATH i get

Users/mac/flutter/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

When I type flutt and Tab terminal automatically recognizes it as flutter
And commanding flutter doctor  gives

Emperor-MacBook-Pro:bin Notorious$ flutter doctor
Warning: the 'flutter' tool you are currently running is not the one from the current directory:
running Flutter  : /Users/mac/flutter
current directory: /Users/mac/Documents/flutter
This can happen when you have multiple copies of flutter installed. Please check your system path to verify
that you're running the expected version (run 'flutter --version' to see which flutter is on your path).

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v0.4.0, on Mac OS X 10.12.6 16G29, locale en-NP)
[!] Android toolchain - develop for Android devices (Android SDK 27.0.3)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] iOS toolchain - develop for iOS devices (Xcode 9.0)
[✓] Android Studio (version 3.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[!] VS Code (version 1.23.0)
[!] Connected devices
! No devices available
! Doctor found issues in 3 categories.
In Opening new Terminal window to create new app say 'ios' i get error
Emperor-MacBook-Pro:~ Notorious$ flutter create ios

-bash: flutter: command not found

Emperor-MacBook-Pro:~ Notorious$

Sorry for the late response.
Is this still an issue?

Please consider asking support questions in one of the other channels listed at http://flutter.io/support .

@RomanEmperor the error is in this line:
There i exported path as export PATH=/flutter/bin:$PATH and Hit control + X to save and quit```

You need to add a `$HOME` before the flutter or whatever your `pwd` (present working directory) is.


Allow manually-specifying which macros should be formatted and how

The libc crate has some macros, called s!, f!, etc. which take a series of items:
f! {
    fn foo();
    fn bar();
    // ...
}

I know that formatting macros is very tricky, and that we probably cannot do that by default.
Instead, would it be possible to specify, e.g., in the rustfmt.toml, a list of macros for which rustfmt should try to format the contents as if the contents were a sequence of items ?
E.g. for the case above, rustfmt could format the f! { ... } the contents of ... as if they were items, adding 4 space indentation inside the block.
I think approaches to macros in which users opt-into formatting them, and somehow conveying what the content of the macro is, might be a more viable way forward with respect to macro formatting than trying to do things automatically.
I don't know how to call this, but I could add the following to libc's rustfmt.toml:
format-macro-content-as-items = ["f", "s"]

I think I could use this in other crates that also make heavy use of macros, like packed-simd.

For many macros, specifying the separator of a list of arguments would be necessary and sufficient. "You're allowed to modify whitespace immediately after this pattern."
Of course this might break in a few special cases, but if it's opt-in that's OK - use it in the other cases.

Also, rather than specifying it in the .toml, how about a #[rustfmt::] block on the macros you want to format? That would give finer-grained control, more closely linked to the source you want to affect (you don't have to export your .toml to let others format your macro invocations).
// For keyword-args like my_macro!(foo: 5, bar: 6, baz: 7)
#[rustfmt::macro_args_separator(",")]
// For the example above with a list of functions
#[rustfmt::macro_args_separator(";")]

Is there any progress on this? Is there anyway to format macros that just receive regular rust code?

Is there any progress on this? Is there anyway to format macros that just receive regular rust code?

This would also be useful in Tokio.

This would also be useful in Tokio.

This would be useful in Maud as well (though its syntax might be too complex for a config-driven solution...)

I have opened a discussion thread in the Rust Internals Forum related to this issue.
If there is something constructive you could add to the discussion (criticism, possible solutions, concerns, use cases), please head through the link below.
https://internals.rust-lang.org/t/discussion-adding-grammar-information-to-procedural-macros-for-proper-custom-syntax-support-in-the-toolchain/21496