programs.ssh.knownHosts..hostNames -> extraHostNames

Motivation for this change
There is no good reason to have knownHosts be a set. The only place the keys are used is in error reporting. Having it be a set without a clear meaning for the keys causes confusion (it did for me at least). "What do I name it?" "Am I missing something about how it's being used?"
Let me know if I am in fact missing something and there's a good reason it's a set.
Things done
Haven't tested it at all yet. Will do later and update.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@pennae Okay, I implemented our new idea. I did make a basic test to see that the deprecation warning gets printed, and that the options work as expected.

added some release notes for the changed option. if you're happy them we'd say this is ready to merge :)

Looks good to me; thanks for reviewing the PR so quickly! :)

sure thing! :) not going to merge quite yet though to give others a chance to comment as well.

I'm not very happy with the deprecation of hostNames.
Previously the attribute names of knownHosts didn't have any meaning associated with them, their only purpose was naming the entries, so you could refer to them from other modules and override specific values. But now with this PR, the attribute name suddenly gained the semantics of "machines with this attribute name are expected to have this public key", and it's not just for naming purposes anymore.
This becomes a bit more of a problem when you consider that the same host can have different host keys, in which case you need multiple knownHosts entries, and the only way to do this is by providing multiple entries. In this case, this PR essentially forces the user to pick some arbitrary hostname that doesn't match what the machine is actually available under.
In addition, there can be hosts which aren't available under any "nice" name, such as just IP addresses. This PR encourages users to use IP addresses as the attribute name.

I think it would be best to revert this PR, but to find a better solution for the original problem: Documenting that the attribute name doesn't have any semantics, it's purely for naming purposes.

not sure reverting is necessary, but perhaps undoing the deprecation and warning would be an option? the old usage of attrs as names without semantics is still possible if you set hostNames. we're not sure how common it is to configure multiple keys for a host. if it's not a very common thing it's probably a nice convenience to have that default.

I'm having a hard time understanding the first use-case (multiple knownHosts).

Before this PR, the name of the attribute was not just an arbitrary label. It had meaning, unless hostNames was set.

If we want NixOS modules to have attrsets with arbitrary names for overriding purposes, this should be standard across NixOS modules. As it stands, there are plenty of places where we have lists that just can't easily be overwritten. (I acknowledge this is a downside, but it seems to be the standard nonetheless) It is quite confusing (IMO) to have one (or maybe a few) places where a value is morally a list but in fact is written as an attrset.

for 1, imagine a system with multiple host keys (as usually happens) and a user who wants to list them all. we forgot about that too during review because ed25519 has become so ubiquitous, but the use case is there. more complicated setups could also be possible, eg a pacemaker system where each node has its own unique host key but failover from one to the other doesn't change the hostname.
programs.ssh.knownHosts = {
  host = {
    publicKey = "<main ed25519 key>";
  };
  "host/secondary" = {
    hostNames = [ "host" ];
    publicKey = "<secondary ed25519 key>";
  };
};

Ohh I understand. Thanks for the example. Yeah, seems like the solution to this is making publicKey into a list publicKeys, no? Writing out a single host in multiple entries like this seems like a pain, and there is naturally a list of public keys associated with a host, not a single public key.
Is it designed the way it is so that each entry corresponds to a line in the known_hosts file?

lists also works, but they can lead to potentially misleading configs. take the setup from earlier, but with a shared key added:
host-primary = { hostNames = [ "host" "a" ]; ... };
host-secondary = { hostNames = [ "host" "b" ]; ... };

in the list scheme with hostNames deprecated you'd have to use b for the second entry, unless you used a for the first one—or create three entries, again duplicating some keys. having the names serve only as documentation here seems preferrable for cases where host is the most used name to access a thing.
maybe the best way to go is doing both, lists for keys and allowing hostNames again?

I'm kind of lost. I don't understand what the problem with the example you gave is. Can you spell it out for me? Where do we run into trouble? Why do you have "have to use b for the second entry? are you talking about in the known_hosts file? what are the constraints we're running up against?

it's about known_hosts, yes. there's no technical limitations if each entry has a list of keys on it, just one of documentation. eg if you have lists of keys but hostNames is deprecated you'd have to write
host = { extraHostNames = [ "a" ]; publicKeys = [ k1 k2 ]; };
b = { extraHostNames = [ "host" ]; publicKeys = [ k1 k3 ]; };

or
a = { extraHostNames = [ "host" ]; publicKeys = [ k1 k2 ]; };
b = { extraHostNames = [ "host" ]; publicKeys = [ k1 k3 ]; };

or
host = { publicKeys = [ k1 k2 k3 ]; };
a = { publicKeys = [ k1 k2 ]; };
b = { publicKeys = [ k1 k3 ]; };

all of those work but they somewhat obscure the fact that host is the primary name and a/b are just there by architectural accident. using labels like host/primary and host/secondary (which aren't valid host names) seems to communicate that intent more clearly.

I see. I dunno, the last of those doesn't seem bad, especially with some comments.

Here's specifically how I'm using knownHosts: https://github.com/Infinisil/nixus/blob/60ea7eb5e18d58ac7742234855b7192112fd4049/modules/ssh.nix#L38-L42. Note how the name of the entry ("${toHost}-${hostKeyName}") is just a combination of the host name and the name of a key (of which there can be many), which together isn't really a sensible host name. It's just the name of an entry for overriding purposes.

Regarding changing publicKey to publicKeys but keeping the "using the attribute name as a host name", the problems with that are that:

Some hosts don't have a reasonable default host name, e.g. machines only accessible by IP (as also mentioned in https://github.com/NixOS/nixpkgs/pull/155517#issuecomment-1069967355)
It adds the relatively arbitrary restriction that all entries for the same host need to share all options for different public key. Just as an example, reading through man sshd to see the known_hosts file format, there's a @revoked prefix that can be used to revoke specific keys, something that could not be supported with publicKeys as a list.

Okay, seems like my original idea of just having programs.ssh.knownHosts be a list might have been the way to go

No, then you can't override entries

No, then you can't override entries

I still don't understand if this is something special about knownHosts. Is the same not true of systemd.mounts, services.smartd.devices, services.openssh.listenAddresses, networking.interfaces.<name>.ipv4.routes, etc? None of those have easily overridable entries. This just seems like a general problem with the interplay between modules and lists, not a reason to do things differently here. (unless I'm missing something that makes this situation different, which is completely possible)

No there's nothing special about knownHosts. I think all values of the module system should be overridable. If we could go back I'd probably make all of those attribute sets instead.
I have planned for a while to make an RFC to deprecate lists from the module system completely, replacing it with better alternatives. E.g. a type where you can still provide a list as a value, but it converts it to an attribute set underneath.


ER Diagram: cannot add view object

I created a new ER diagram, including only the tables.
Then I tried to add the views, dragging them from the views list, both on the diagram or on the list of tables (to the left of the diagram), but the views are not added.
If I create an ER diagram including the views and then I remove one and try to add it again, I can not add it (same issue above).
[database: PostgreSQL 9.6]

You can enable views in diagram by enabling it in preferences:

And I think we should enable it by default (in fact I don't remember why we disabled it in the past).


⚠ Cioos National CKAN has degraded performance

In 120ca27, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 16124 ms

Resolved: Cioos National CKAN performance has improved in e634d40 after 36 minutes.


add support for RTREE index

What problem does this PR solve?
Add support for RTREE index.
What is changed and how it works?
MySQL syntax:
index_type:
          BTREE_SYM { $$= HA_KEY_ALG_BTREE; }
        | RTREE_SYM { $$= HA_KEY_ALG_RTREE; }
        | HASH_SYM  { $$= HA_KEY_ALG_HASH; }
        ;

Check List
Tests

Unit test

LGTM

@kennytm  PTAL

LGTM


Updated for Express 4.

Thank you much for the guide, it helped me understand how to use passport correctly. I had to do some work on my own to get it to work with Express 4 but was an easy update. Forked and updated such that just the template is updated for Express 4, should also make updating the guide easy as well.

The only problem with this is that now I will have to update the blog post.
I could -

update the current blog post
create a new blog post
do not update the blog post, and just add this code as a new branch

What are your thoughts?

Thanks so much for doing this btw! :+1:

Working on a new blog post -> https://gist.github.com/mjhea0/93266da1113249d9fea2

Awesome, that's what I would think of recommending, actually.
Just a note, I was unable to port forward the testing suite, so don't rely on the code for that part to be up-to-date as well.

http://mherman.org/blog/2015/01/31/local-authentication-with-passport-and-express-4/#.VM13YFXF8Yc


remove the use_thin_strokes parameter from Rasterize::new

this only tries to do anything on macOS, but as of more recent macOS
versions, it does nothing there either (issue #36)
instead, enable or disable "font smoothing" on macOS based on the AppleFontSmoothing user default
this lets users get the old thin strokes behavior by setting AppleFontSmoothing to 0 with:
defaults write -g AppleFontSmoothing -int 0
use lazy_static! to read this value once, rather than in every call to get_glyph
also refactor the Darwin module to remove dead code and only export CoreTextRasterizer

@kchibisov here is what I have.
I think the biggest gap here is how to handle AppleFontSmoothing being set to 1 or 3, which macOS does handle differently, but I don't see any public API for, or any documentation of what it is supposed to mean.
On the issue thread you said:

Can you configure this default actually?

If you're asking whether this can be configured, I describe in more detail in the commit message and the code comments what we do with the setting, but let me know if I've misunderstood your question or haven't answered it there.

Fixed to only use cacao and lazy_static in the macOS config.

Another thing I discovered in my experiments is that CGFontRenderingFontSmoothingDisabled is fully deprecated now and doesn't do anything. macOS has a private API that WebKit uses for obtaining this: https://github.com/WebKit/webkit/blob/6e14685cafbd406eb0bf2a9dac5d3518213183a1/Source/WebCore/PAL/pal/spi/cg/CoreGraphicsSPI.h#L336
I tried on my machine running 12.4 to call this function to see what it does, and the disassembly shows it always returns true; it doesn't go and look up the corresponding user default that crossfont was using to control this.
CoreGraphics`CGFontRenderingGetFontSmoothingDisabled:
0x188240784 <+0>: mov    w0, #0x1
0x188240788 <+4>: ret
CoreGraphics`CGFontRenderingGetFontSmoothingDisabled:
0x7ff81952d022 <+0>: pushq  %rbp
0x7ff81952d023 <+1>: movq   %rsp, %rbp
0x7ff81952d026 <+4>: movb   $0x1, %al
0x7ff81952d028 <+6>: popq   %rbp
0x7ff81952d029 <+7>: retq
Based on this WebKit issue https://bugs.webkit.org/show_bug.cgi?id=216588 this has likely been the case since Big Sur.

How does it work? I think it doesn't do anything wrt the actual font-smoothing no? Since the Api to make font smooth or thin(like it was before) doesn't work anymore?
In particular would it allow us to achieve thin strokes, the ones with subpixel AA, which apple killed in all of their applications in macOS 10.12?

As far as I know, subpixel AA is gone for good, but the "thin strokes" behavior, to my understanding, has meant to disable "font smoothing", which means telling macOS not to make your font stroke width artificially larger. The only setting that needs to change to control this is set_should_smooth_fonts.

Thanks for the review! I will address the requested changes later today.

Should also add a CHANGELOG entry wrt user settings and wrt breaking rasterizer Api.

Addressed most recent feedback, added changelog entry.

Was a little overzealous in my refactor of the objc code and managed to break the key lookup. It's working now. Ready for further review. Thanks!

Updated changelog and commit message. Removed extraneous test.

Comments and changelog updated. Ready again.

Thanks for the thorough reviews! I'll work on updating the corresponding alacritty PR this weekend. https://github.com/alacritty/alacritty/pull/6186

Thanks for helping out with macOS, always appreciated.

thanks for the PR, by the way, we can disable font smoothing for Alacritty only by specifying a domain ( ps: the domain was io.alacritty but it is now org.alacritty), since disabling font smooth for the whole system is probably not what most people want.
defaults write org.alacritty AppleFontSmoothing -int 0

@cattyhouse yes, that's mentioned in the commit on Alacritty here: https://github.com/alacritty/alacritty/commit/2a676dfad837d1784ed0911d314bc263804ef4ef
Alacritty's bundle domain changed after the crossfont change was merged, but before the alacritty change was merged. crossfont is used in some other projects too, and so I mentioned in this commit message to use the appropriate domain if you don't want the global behavior. Personally I think it makes everything look better, though. This post is a good description of what the default actually does. tl;dr: This setting is not really "smoothing" anything anymore, just making things slightly thicker. To get accurate font rendering, you must disable it.


Installer requires admin privileges [feature request]

As it stands, the installer requires admin privileges to run. It would be nice to have a version of the program that can be user installed to the user "home directory". Editing the path probably isn't possible in this case, but I think that is a worthwhile tradeoff.

I agree! This would be awesome! But, I don't know how to do that. At least as an "option" so to speak.  Maybe a separate installer?


Add a service with a streaming binary input shape

The best option on the current roadmap is probably EBS: https://github.com/awslabs/aws-sdk-rust/issues/66

such as Amazon Lex's PostContent API. Though, it's probably not in really high demand.

Actually lambda has a streaming binary input shape on invoke. I'm going to update this ticket to say we should have use that in the example

does the new tokio write_all_buf help here or is that just for writing to a file?

That's the opposite direction
On Fri, May 14, 2021, 7:36 PM Richard H Boyd @.***>
wrote:

does the new tokio write_all_buf help here or is that just for writing to
a file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/smithy-rs/issues/347#issuecomment-841551645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADYKZ7B2ACGK7KSMTPVKG3TNWXYVANCNFSM434GTC3Q
.

is the stream writer a functionality in the SDK? I don't think the actual Lambda HTTP API accepts streaming body inputs.

Ah, I looked into it. The stream is actually only on the payload of the deprecated API invoke_async

done from s3


Unnecessary click event

When you select a button to go to the next chapter, it also shows a reader interface for a brief moment. If you enable a touch sound on your phone, you're able to hear that it was two clicks.
It started to happen after the last update

Should be resolved in current develop branch.


[Event Request] Page 233 "Apply Vendor Entries" - trigger OnModifyRecord

Describe the request
trigger OnModifyRecord(): Boolean
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCalcApplnAmountOnModifyRecord(CalcType, AppliedVendLedgEntry, IsHandled); //CustPub
    if not IsHandled then
        CODEUNIT.Run(CODEUNIT::"Vend. Entry-Edit", Rec);
    if Rec."Applies-to ID" <> xRec."Applies-to ID" then
        CalcApplnAmount();
    exit(false);
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeCalcApplnAmountOnModifyRecord(CalcType: Enum "Vendor Apply Calculation Type"; var Rec: Record "Vendor Ledger Entry"; var IsHandled: Boolean) //CustPub
begin
end;

Additional context
Publisher request marked with //CustPub tag.Internal work item: AB#494024

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 14714.


Could someone fix the Project so that it works

Hi have had to change several things to get this to work.
I am talking about the TestApp

One of the references is confused. had to remove Excel.4.5 and add back. (strange behavior)
Was complaining about missing bin/Debug45/Excel.dll

2.The reference flies are missing from TestApp to PCLStorage and PCLStorage.Abstractations
if you don't add this is will complain about method not implemented i the Portable Project.

After all that when i try and Test a file it says that it has no
_workbook..... line " for (int ind = 0; ind < _workbook.Sheets.Count; ind++)"

_workbook is null.... I think this has to do with all the async methods.
Could be wrong about all this but would be nice if it just worked out the box.

just to add to this.... its way more complicated to use Excel.4.5 vs Excel
I think a better tutorial is needed for what is all needed to make Excel.4.5 work... as it seems to require a lot more other refereanses

Hi, Further to this.... I assume that moving to 4.5 the goal was to remove a reference to ICSharpCode.SharpZipLib.
Could someone give me an explanation of why. (it would be most useful for my own learning)
and now 4 references are needed;
ExcelDataReader.Desktop
ExcelDataReader.Portable
PCLStorage
PCLStorage.Abstractions

The stable version is in the master branch. That reflects the version in nuget. You are welcome to use that.
The version in the develop branch is largely untested. I switched the default branch to develop just so I could get some feedback as otherwise it would be only me testing it and I can't release it like that. So, thank you for your comments, I will look into them.
The Excel 4.5 version has exactly the same interface as the 2.0 version so I'm not sure why you think it much harder to use.
The main change in the version in the develop branch is that the 4.5 version uses a Portable Class Library. Meaning, in theory, it is easier to get it to work on different platforms that support PCL, SharpZipLib has gone because there is a framework zip implementation that is used instead.
The new references to PCLStorage are to support the PCL version, however, it was more a convenience at the time to use those than roll my own storage abstraction. It should be possible to inline those abstractions but I'd lose benefit of uses a third-party library (i.e. I don't have to maintain that bit). Does having extra references cause you a problem? If so, I'd like to understand that  better, for my own benefit.
I'll look into the compilation issues you mentioned,.
Thanks

Hi Ian1971
Thanks....
Now that i can been looking/staring at it for some time.
I downloaded the lib from Github. (I will try the nuget later.)
Just to clarify. To me it was/is confusing as to why all of these are needed.;
ExcelDataReader.Desktop
ExcelDataReader.Portable
PCLStorage
PCLStorage.Abstractions
You imply(above) that it can be used without.....PCLStorage.
Its not clear how to remove this abstraction if you are referencing the lib without modifying it.
(lets come back to this one later)
What does not work, The TestApp with an xlsx(2007) file... seems to work with a xls(2003) file.
Saying that if I build a simple console App and Reference these
Excel.dll
ExcelDataReader.Desktop.dll
ExcelDataReader.Portable.dll
PCLStorage.dll
PCLStorage.Abstractions.dll
I am able to read both xls and xlsx.
What I was suggesting is that when some downloads the project that it include these references in the TestApp;
ExcelDataReader.Desktop.dll
ExcelDataReader.Portable.dll
PCLStorage.dll
PCLStorage.Abstractions.dll
As it does not work with out them... or well i can not understands what i would need to do.

It's possible I messed up the references in TestApp, because I was recently
running it against the stable nuget package to compare it to the develop
branch.
On Sun, Jan 11, 2015 at 3:37 PM, Seabizkit<EMAIL_ADDRESS>wrote:

Hi Ian1971
Thanks....
Now that i can been looking/staring at it for some time.
I downloaded the lib from Github. (I will try the nuget later.)
Just to clarify. To me it was/is confusing as to why all of these are
needed.;
ExcelDataReader.Desktop
ExcelDataReader.Portable
PCLStorage
PCLStorage.Abstractions
You imply(above) that it can be used without.....PCLStorage.
Its not clear how to remove this abstraction if you are referencing the
lib without modifying it.
(lets come back to this one later)
What does not work, The TestApp with an xlsx(2007) file... seems to work
with a xls(2003) file.
Saying that if I build a simple console App and Reference these
Excel.dll
ExcelDataReader.Desktop.dll
ExcelDataReader.Portable.dll
PCLStorage.dll
PCLStorage.Abstractions.dll
I am able to read both xls and xlsx.
What I was suggesting is that when some downloads the project that it
include these references in the TestApp;
ExcelDataReader.Desktop.dll
ExcelDataReader.Portable.dll
PCLStorage.dll
PCLStorage.Abstractions.dll
As it does not work with out them... or well i can not understands what i
would need to do.
--
Reply to this email directly or view it on GitHub
https://github.com/ExcelDataReader/ExcelDataReader/issues/49#issuecomment-69498426
.

--
Ian Cox
C.T.O.
Release  Mobile
m:            Matrix Studios, 91 Peterborough Road, London, SW6 3BU
w:            http://www.releasemobile.com
Registered in England.  Number 06323661

Hope its ok to close this now. The develop branch should work out of the box in latest VS2017


ControlNet not showing

Not showing there too

try running the colab without the gdrive cell (first cell), if the issue persist, I'll check it out

Yep, it seems to work without connecting to Gdrive

Then there is a problem with your SD folder


Quickstart updates #2

A couple more improvements to the descriptions of various quickstarts
As well as deleting some duplicate ones

@jpvajda yes, they were duplicate quickstarts


Problem reprojection with ecw ED_1950_UTM_Zone33N e NUTM33 together OpenStreetMap.

This issue was imported from CodePlex
mogikanin wrote 2014-08-05 at 11:28
Hi, i have a problem when i load my rasters (ecw) projected ED_1950_UTM_Zone33N e NUTM33 together with a OpenStreetMap. When i load raster the program asks me if i want to reproject, i say yes but unfortunately the rasters are not reprojected correctly
as you can see from the image that is on the link
https://docs.google.com/drawings/d/12EPKTA9iOba8G9TuLzGr-80BPaEXOqqTYs_pJwhk10I/pub?w=960&h=720
If I try to pan, the program freezes and crashes.
I'm using DotSpatial version 1.7.
Copied from
https://dotspatial.codeplex.com/discussions/558222
Angela77Dir wrote 2014-09-12 at 13:53
Hi! I wanted to know if there is any news about the fix for this issue?

Issue still exists


Add some WASI-specific branches.

Adds some WASI-specific branches to platform-specific code (instead of falling back to the "unknown" case with warnings.)
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

@swift-ci please test Windows

@swift-ci please test macOS


display type

add a display type identifier to tell us which OS's are a terminal or GUI on boot

Can you clarify what you mean by this?

what I mean by display type is, when it's fully booted up, does it boot as a console, such as Archlinux or MS-DOS, or is it a desktop, such as Windows, ReactOS, or Android.

https://github.com/copy/v86/pull/935


engineered_resids in interactive.npy cannot take np.arange()

It will work as a list() though...

Also, that cell in interactive.ipynb cannot be ran multiple times if engineered_resids are specified


What is optimal for resample: blockwise or cohorts?

This will need some benchmarking.

uff with cohorts we end up sorting because the cohorts don't come out sequentially.

Ah for blockwise, we cannot have one group split over many chunks, that's the issue! I should add a test case in xarray to make sure I don't forget and change it later.

But if method=="blockwise" we do actually rechunk to make it a blockwise problem. So perhaps it is always better.

Handled by the method=None heuristics now I think.


Running query in console doesn't show execution time anymore

Runtime information:
Neo4j database version: 3.0.3
neo4j gem version: 8.0.0
neo4j-core gem version: 7.0.0

Can you share an example?  When I try I see the execution time

Sorry, I forgot to specify:
I mean, using BOLT protocol ;)

Started looking at this but I need to go to bed now ;)  So that you're on the same page, though, the new API introduces separate event subscriptions for requests/transactions and queries.  The query notification just shows that a query was made, while the other other is what shows the time.  Check out this line for where it's supposed to be working in the railtie:
https://github.com/neo4jrb/neo4j/blob/v8.0.0.alpha.2/lib/neo4j/railtie.rb#L75
The problem is that now in the new API in neo4j-core you can have more than one query in the same HTTP request, so the elapsed time doesn't belong on either query.  The link above is trying to make subscriptions to something outside of the queries.  For HTTP it's pretty simple that it's the request.  For embedded I went with it being the transaction.  For bolt, however, it's less clear to me.  There isn't really a single "request" because it's a persistent connection consisting of a lot of little back and forth requests.  Maybe queries for bolt actually could contain the elapsed time and/or maybe we give a subscription to the transactions.  Come to think of it, perhaps transactions should be instrumented at a higher level so it just works for all adaptors.


add an important notification

please help check asap. thanks.

@Yueying-Liu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off
@Yueying-Liu - Next time, please submit your changes against azure-docs-pr: https://github.com/MicrosoftDocs/azure-docs-pr.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


VP 78 pistol and magazine

About the PR
Basic implementation of VP 78 pistol and its magazine. It works, but its (assumed) original stats cannot be replicated without system updates we can't have different ROF for different firemodes, or different damage for guns that fire the same cartridges
Additionally, the pistol ROF values shown on the CM-SS13 wiki make no sense so for now I just gave it the same ROF as the 88M4
Part of  #1551
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Okay I guess the wiki was prosaic about it being automatic, but if it's semi-auto, do we set it's rate of fire for burst mode? Meaning it will also be a fast firing semi-auto?


Investigate pending intents to send data

Currently, we are sending data every 10 seconds as determined by a ScheduledExecutorService. @BarteldKlasens suggested that we consider PendingIntent for this, so that Android may decide when would be a battery-friendly time to send data.

https://developer.android.com/training/scheduling/alarms.html


CodeCov coverage fix, take 2

Codecov Report

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

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
+ Coverage    82.5%   88.52%   +6.02%
==========================================
  Files          16        9       -7
  Lines        2880     1333    -1547
==========================================
- Hits         2376     1180    -1196
+ Misses        504      153     -351

Impacted Files
Coverage Δ

spec/checker_spec.lua

spec/coder_spec.lua

spec/types_spec.lua

spec/parser_spec.lua

spec/lexer_spec.lua

spec/util_spec.lua

spec/symtab_spec.lua

titan-compiler/types.lua
100% <0%> (+48%)
:arrow_up:

titan-compiler/util.lua
94.87% <0%> (+68.26%)
:arrow_up:

Continue to review full report at Codecov.

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

It works! Please approve this so I can squash-merge this with a nicer commit message.

Approved!


Allow wildcard for allow control allowed origins

Description
The new --access-control-allow-origins flag did not function correctly with wildcards. This means that tech that didn't explicitly specify an Origin header on requests to the JSON RPC API would be blocked. This includes standard tech like MetaMask.
Changes include

[ x ] Bugfix (non-breaking change that solves an issue)

Testing

[ x ] I have tested this code manually

Manual tests
I was able to do various actions via MetaMask and explore the blockchain via typical eth_ functions.

I have read the CLA Document and I hereby sign the CLA

@thegoldenmule Thank you for the comments. That's true. In current implementation, multiple domains that contains wildcard can be given. So my comment at that line was not correct. We need to talk about whether we can give domains with wildcard.
@zivkovicmilos @lazartravica

A simple alternative, btw, would be to skip the array and loop entirely and simply set the string directly to whatever was specified in the configuration.

@zivkovicmilos Not sure setting wildcard as default is good. Wildcard will allow all web browsers to access to JSON-RPC. (Of course, you can block by different layer)

@zivkovicmilos @Kourin1996 IMO * by default makes the most sense. I can't tell you what the goals of your project are-- but as I see it, an opensource blockchain server that by default doesn't work with standard web3 clients (like Metamask) doesn't make a ton of sense.

I was thinking more along the lines of magic SDK for contributing to
charitable organizations. For the protection of both parties involved.
Sincerity is priority number one. People don't bake projects that cant is
protected. Always open to Ideas.
On Tue, Feb 15, 2022 at 6:58 AM Benjamin Jordan @.***>
wrote:

@zivkovicmilos https://github.com/zivkovicmilos @Kourin1996
https://github.com/Kourin1996 IMO * by default makes the most sense. I
can't tell you what the goals of your project are-- but as I see it, an
opensource blockchain server that by default doesn't work with standard
web3 clients (like Metamask) doesn't make a ton of sense.
—
Reply to this email directly, view it on GitHub
https://github.com/0xPolygon/polygon-edge/pull/414#issuecomment-1040371804,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVUYHFUCUG6NJ353Y4DUKFDU3JSY5ANCNFSM5OCGFV4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

@STZeed I'm not sure I'm following but if any offense was taken, it was certainly not intended. My point is only that this project provides an open API that, by default, does not work in the larger open ecosystem. It's not CORS that is providing the security guarantees behind dapps, though I understand you might as well use every tool your disposal.
As far as ideas, I have already mentioned one that may have been passed over. Why not simply set the header explicitly to the value provided by --access-control-allow-origins rather than any sort of dynamic logic? This option would result in the simplest implementation, the easiest documentation to understand, and cover a large number of use cases.

@thegoldenmule @STZeed Thank you for having opinions and apologize for late reply. Basically I'm not clearly disagree with that. Perhaps there will be few cases of that we want to disable CORS. It will work with allowing CORS to any domains for now.

@Kourin1996 Please let me know how you'd like me to proceed.

@thegoldenmule

Set '*' as the default CORS domain
In case of '', set '' in "Access-Control-Allow-Origin HTTP/S header

A simplest way it to add default value here
https://github.com/0xPolygon/polygon-edge/blob/8a033aa1afb191abdac04636d318f83f32511f3c/command/helper/helper.go#L479

@Kourin1996 That file seems to have gone through a large refactor recently. I changed it in command/server/config.go, as it looked like the right place.

@zivkovicmilos @ZeljkoBenovic Thanks so much. I think I've fixed the linter issues. I have not used golangci-lint before, but make lint seems to complete successfully locally for me.


chore: use @rpath as install path

This fixes the load path for rootless, see theos/theos#687 and theos/lib#16.

Don't merge yet, this seems to work for the libsandy.dylib installed to theos but then it doesn't get included properly in the package.


PH_TIMEOUT error is reported

The test below reprots PH_TIMEOUT error.

Test Name: fabric_data_width_32_vc_1/tnoc_fabric_random_test
Random Seed:<PHONE_NUMBER>
Simulator: VCS P-2019.06

Currently, routing modue (X-Y or Y-X) is selectable and this may cause dead lock.
Therefore, this feature should be removed.


Very slight breakage by Rust 2021 Edition

Rust 2021 has reserved the prefix#identifier syntax. This causes the following to fail to compile
use maud::html;

fn main() {
    let markup = html! {
        div#my-id {}
    };
}

because div#my-id uses the reserved syntax.
The easy fix is just to add a space between the tokens: div #my-id. Not very significant but the examples on the website should perhaps be updated with a note about Rust 2021.

Thanks!
Yeah, I have the changes for this locally. Just need to clean it up.
I'll assign myself in the meantime.

BTW, the docs on main mention some unreleased features (#283). So to avoid confusion, I'll hold off on deploying the docs changes until I cut a new release.


Pin Bazel versions

Description:
Ports over bazel pinning functionality from https://github.com/higherkindness/rules_scala.
With this, rules_scala developers on Linux/OSX will have Bazel pinned to the version rules_scala expects, automatically, regardless of the global bazel install version. Windows developers will still need to match global bazel with the rules_scala bazel version.
The tools/bazel script has been tested extensively (via other projects) for OSX/Linux developers.
Motivation:
One hurdle for development on bazelbuild/rules_scala is a lack of Bazel version pinning that's consistent for local development and CI.

Updated with notes covering how to test with multiple bazel versions.

@ittaiz How do you feel about these changes?

Thanks for the clean up! I'll merge now, if @ittaiz has any concerns we can deal with them.

Thanks @andyscott  for asking and thanks @johnynek  even more so for not letting red tape take us down.
@andyscott I didn't deep dive into the script code but it sounds very similar to https://github.com/bazelbuild/bazelisk. Shouldn't we use that? This is also what Wix is moving to internally.


logs: rules as received from RC use some specific consts.

What does this PR do?

Moves interpreting rules received through RC in a separate function for clarity
Uses specific consts strings when interpreting rules received through RC, as these consts don't fully matches strings used in the library itself (which was a naive assumption).

Describe how to test/QA your changes
Not necessary, it will be tested during the #23915 QA (that's actually going through this that I've detected it).

/merge


Add Scenario of " SolarWinds Breach"

Information extracted from: https://www.picussecurity.com/resource/blog/ttps-used-in-the-solarwinds-breach

Thank you @sanchezmia for your time to write this detailed response. I'll make sure to add these changes.

Hi @alaanasser0, we have some interest in completing the SolarWinds flow -- are you okay if we update this flow on your behalf? We would still list you as a co-author.

Hi @mehaase, sure! I wanted to complete it but unfortunately I don't have enough time to focus on it.
Nevertheless, hit me up if you need any help.
Have a great weekend.

The SolarWinds flow has been upgraded to Attack Flow v2 and included in today's public release. Thank you @alaanasser00 and @sanchezmia!


Support for file_uploader_ui resource type migration

Migrate file_uploader_ui type resources and change "url" field from full URL to file name.

I think that migration is done now and we can probably close this @fulior ?


VirtualScroll listview jumps to beginning if object of items has been changed

Short description of the problem:
VirtualScroll is, as it was in ionic1 badly implemented without being properly tested with different usecases. This issue assumes you have a listview using VirtualScroll. One element is ion-item which has click event leading you to details page of that element.
On details page, you change the single object of your array of elements, being show in VirtualScroll.
Going back from the details page to virtualscrollview will always lead you to being at the top of the virtualscroll and will not remember the positioning, since the object has been changed.
So if you would click on element 51 out of 1000, then come back, you will see that you're starting at the top of the view again and not at element 51, which leads to usage of VirtualScroll being unusable. Similar issue/behavior has also been reported on the forums (https://forum.ionicframework.com/t/virtual-scroll-remove-or-hide-item-without-reset-lost-scroll-position/54024/9), but without any official replies.
What behavior are you expecting?
Clicking element 51, navigating to details page of element 51, clicking back would lead you to exact same position you were before.
Steps to reproduce:

VirtualScroll with 1000 elements (even 50 if you wish)
Click element 51 and use nav.push to go to the other page
Edit 1 element in list
Press back
Where are you taken? Exactly, top of the VirtualScroll page.

Which Ionic Version? 1.x or 2.x
Ionic Version 2 beta9
Run ionic info from terminal/cmd prompt: (paste output below)
$ ionic info

Your system information:

You have been opted out of telemetry. To change this, run: cordova telemetry on.
6.2.0

Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.9
Ionic CLI Version: 2.0.0-beta.31
Ionic App Lib Version: 2.0.0-beta.17
OS:
Node Version: v5.9.1

My use case - deleting an item from the array, even without navigating from the list.

It also makes virtualscroll unusable with infinitescroll, as it jumps to the top when new items are fetched

Perhaps slightly related: #6787

It is related to #6423.


feature: how to stake polkadot

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #6885
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[ ] I've tested it at </ksm/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[ ] Fill up your DOT address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Comment

Waiting for reply about what tag must be used for the post

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

Copilot Summary

🤖 Generated by Copilot at 030d4a7
Added a new blog post content/blog/the-complete-guide-on-where-to-stake-polkadot.md that explains how to stake on Polkadot and its benefits for NFT collectors.

🤖 Generated by Copilot at 030d4a7

New blog post added
Polkadot staking guide
Autumn leaves falling

ready for merge? :)

let's go, maybe tag could be polkadot
pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 4.41 USD/DOT ~ 6.803 $DOT
🧗 123PCJXhjb15i6JwVVRGd7KvN2sSNZrtPjr5doJq9oWctoTt
🔗 0xf621bb43a893ad33fd90829b7f1391c52918536a163d3ea2b9b7f2af08f8a60e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


OrangePi Zero Plus 2 H5 not working

I have an issue with OrangePi Zero Plus 2 H5. I cant install RetrOrange. There is no any H5 images. H3 only. Can you help me to install manually RetrOrange with Kodi only on Zero Plus 2 H5 on latest Armbian 5.38? No needed Libretro and OpenELEC. RetrPie and KODI only. Thank you

From our website http://www.retrorangepi.org
RetrOrangePi is a non profit gaming and media center distribution compatible with boards equipped with CPU H3 and GPU Mali 400 (most Orange Pis, Banana Pi M2+, Beelink X2 and NanoPi M1).
Until we get working GPU drivers, there will be no support for new boards like Orange Pi PC2, Orange Pi Win, Orange Pi Prime or any other with Mali 450 GPU or A64/H5 CPU.

When it will be support?

Unsure. It's been more than a year of release and the board manufacturer still havent sorted it out. There is work in progress, so keep watching the scene.


Update dotnet runtime to 2.0.0

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Refs: https://github.com/caskroom/homebrew-cask/pull/37661#issuecomment-322349574

Thank you for your contribution.


Button is not aligned for small screens

Describe the bug
For smaller screens the button is not aligned.

Screenshots

Expected behavior
A clear and concise description of what you expected to happen.

I would like to work on this issue.


Provide top-level package.json

Many of the other jupyter subprojects provide a top-level package.json file that has subcommands for building different things in the various subdirs. I think this would help a lot in allowing devs to build some/all parts of the widget stuff. Minimally having a command to build each sub-js-package and then one command to build everything would be super helpful.
The reason that is so helpful is that right now the devinstall.sh script does both building and install. Thus, once you start to do development, there is no easy way to just rebuild the part you need.
To go one step further, it would be really nice to have the setup.py script run the top-level npm commands as the notebook/lab does. I realize the extension installation steps still have to be separate for now, but we are all used to that.

I don't think we need this before 6.0, though.

I can probably do a simple version when I do the style changes...
Fine to not block 6.0 on this though...
On Thu, Feb 16, 2017 at 10:56 AM, Jason Grout<EMAIL_ADDRESS>wrote:

I don't think we need this before 6.0, though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ipython/ipywidgets/issues/1119#issuecomment-280424324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0NcUA1EolKnZqswF0KXCWOFsNtj9ks5rdJv6gaJpZM4MDYkt
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

How would this work with the big split?

Not following your question...can you clarify?
Sent from my iPhone

On Feb 17, 2017, at 4:13 AM, Sylvain Corlay<EMAIL_ADDRESS>wrote:
How would this work with the big split?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The different packages currently present in the ipywidgets repo will be
separated into different repositories
jupyter-js-widgets (pure npm)
ipywidgets (pure python, no js at all)
jupyter-widgets-schema (pure npm)
jupyter-sphinx (pure python, no js at all)
widgets-cookiecutter (cookiecutter)
widgetsnbextension (bundles js in python package, classic notebook manager)
jupyterlabwidgets (bundles js in python package, lab manager)
...
Which repo should have the "top-level" package.json?
I am not sur I follow why we need this.
On Feb 17, 2017 2:20 PM, "Brian E. Granger"<EMAIL_ADDRESS>wrote:

Not following your question...can you clarify?
Sent from my iPhone

On Feb 17, 2017, at 4:13 AM, Sylvain Corlay<EMAIL_ADDRESS>wrote:
How would this work with the big split?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ipython/ipywidgets/issues/1119#issuecomment-280647304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSXFj5JjmrDg_bUosFSJUf4UeszgUcfks5rdZ6agaJpZM4MDYkt
.

The different packages currently present in the ipywidgets repo will be
separated into different repositories
jupyter-js-widgets (pure npm)
ipywidgets (pure python, no js at all)
jupyter-widgets-schema (pure npm)
jupyter-sphinx (pure python, no js at all)
widgets-cookiecutter (cookiecutter)
widgetsnbextension (bundles js in python package, classic notebook manager)
jupyterlabwidgets (bundles js in python package, lab manager)
...
Which repo should have the "top-level" package.json?
I am not sure I follow why we need this.

Bumping to 6.1, and with conversations about the repo split

Politely and respectfully as possible...I think you are still
underestimating how difficult it is to install ipywidgets for development.
I had it working fine earlier this week, and just now pulled from master
and tried to run dev-install again...it didn't work (lab is missing its
JS). It is my top priority to work on the widget design stuff today, but
very frustrating I can't even build it reproducibly. I will dig into it and
see where I can get...
The difficultly with the current situation is that the README says "look at
dev-install.sh", but dev-install.sh doesn't tell you what you need to do to
re-build after you change a file in one of the subdirs. Furthermore,
re-running the entire dev-install.sh doesn't work. A top-level package.json
allows you to provide a more fine grained dev process to re-build or
re-install different parts as needed. Minimally, having more documentation
about the dev work flow (how to rebuild if you change files in a particular
subdir) would be super helpful. Keep in mind Cameron has been trying to do
design work on ipywidgets for weeks now. He works extremely fast on both
design prototypes and CSS - the only barrier to him has been installation
and building.
On Fri, Feb 17, 2017 at 1:06 PM, Jason Grout<EMAIL_ADDRESS>wrote:

Bumping to 6.1, and with conversations about the repo split
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipython/ipywidgets/issues/1119#issuecomment-280753032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0Dl67cRawQSxvHjevQzFr-sbmVMMks5rdf3PgaJpZM4MDYkt
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Politely and respectfully as possible...I think you are still underestimating how difficult it is to install ipywidgets for development. I had it working fine earlier this week, and just now pulled from master
and tried to run dev-install again...it didn't work (lab is missing its JS). It is my top priority to work on the widget design stuff today, but very frustrating I can't even build it reproducibly. I will dig into it and see where I can get...

I totally agree that making a development installation is way too complicated.
This is probably not something that we can fix in ipywidgets itself, but by fixing the jupyter extension system.
If we add more layers on the top of the current (broken) mechanism, it is probably going to make things more confusing.

I definitely agree we need better documentation about dev workflow. Here's my typical workflow, once I have it set up (similarly to how the dev-install script sets things up):

Edit jupyter-js-widgets files
To test in notebook, go to the widgetsnbextension directory and run npm run update, then run jupyter notebook
To test in lab, go to the jupyterlab_widgets directory and run npm run update, then run jupyter lab

If I changed dependencies and need to blow away the widgetsnbextension or jupyterlab_widgets node_modules directory, then I run npm install, then npm run update in the respective directory.

Thanks, let me try those things...
On Sat, Feb 18, 2017 at 10:51 AM, Jason Grout<EMAIL_ADDRESS>wrote:

I definitely agree we need better documentation about dev workflow. Here's
my typical workflow, once I have it set up (similarly to how the
dev-install script sets things up):

Edit jupyter-js-widgets files
To test in notebook, go to the widgetsnbextension directory and run npm
run update, then run jupyter notebook
To test in lab, go to the jupyterlab_widgets directory and run npm
run update, then run jupyter lab

If I changed dependencies and need to blow away the widgetsnbextension or
jupyterlab_widgets node_modules directory, then I run npm install, then npm
run update in the respective directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipython/ipywidgets/issues/1119#issuecomment-280862571,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0K1lcJgITITgXQzKVJ2IBh2puSxPks5rdy-ggaJpZM4MDYkt
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Oh, gosh, I started to dig into thing and got WAY more confused. I was expecting this to use the standard pattern we are using in all our other repos:

A single python package at the top level
One or more subdirs with npm package, each with their own package.json
The build steps of the individual package.json files dumps the output into a /static directory in the single, main python package.
The main python package is the one that is used to trigger all of the separate lab/nb installs.

However, I just found out that what ipywidgets has is nested python packages, each with nested npm packages. Personally I think that is extremely confusing and is going to cause huge problems for package maintainers. We have already had problems getting ipywidgets into conda, I think this will make it very difficult. The also violates the fundamental assumptions that python developers have about package/repos, etc. No wonder I can't make heads or tails of this...
Options:

I see why you are moving that direction - getting ready for the big split. I think that is a really good idea. If you want to have actual separate python packages, let's just do that for 6.0. I just created the org for widgets: https://github.com/jupyter-widgets
If you don't want to do the split for 5.0, I would remove the nested python packages and just have the single python package (ipywidgets) and put all of the static assets into a single static dir of ipywidgets.

@SylvainCorlay I apologize that I didn't understand how the lack of the widgets org was causing active problems in development. I thought the need for it was a bit further in the future.

If you don't want to do the split for 5.0, I would remove the nested python packages and just have the single python package (ipywidgets) and put all of the static assets into a single static dir of ipywidgets.

Do you have some time for a quick call? (in 30 min?)

So regarding the big split and where static assets go, actually ipywidgets will not have any static assets in the split.

jupyter-js-widgets is pure npm and holds the base widget manager, the js for the core widgets. There is no python at all in it.
ipywidgets is pure python, and has no static assets. It will be instalable in a bare kernel.
widgetnbextension is python package that has static assets. It is the notebook extension. The npm module specializes the widget manager for the classic notebook.
jupyterlab_widgets  is python package that has static assets. It is the lab  extension. The npm module specializes the widget manager for the jupyterlab.

The other packages are self explanatory. I was asking about the location of the package.json because ipywidgets will have no javascript after the split.

Great, this completely aligns with my understanding of what the big split would look like. I think the main point of confusion is the nested python packages. With the nested python packages the "top-level" package.json files are in effect in the subdirs. Those will become the top-level ones in the split repos.
At this point, I am not worried about a top-level package json. The bigger issue here is the nested python packages.
I am around for a phone call. I got widgets built for the notebook and am doing style work. Call anytime.

Can you make Sylvain and I owners of jupyter-widgets?

Done!
On Sat, Feb 18, 2017 at 12:19 PM, Jason Grout<EMAIL_ADDRESS>wrote:

Can you make Sylvain and I owners of jupyter-widgets?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipython/ipywidgets/issues/1119#issuecomment-280868438,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0E3dhPyOlxO8NdnH7kl2hhRKsVlkks5rd0RDgaJpZM4MDYkt
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@jasongrout I have already moved jupyter-sphinx and widget-cookiecutter.
We could open an issue in the declarative widgets repo.
Also, I would like to move the jupyter-incubator/traittypes there.

At this point, I am not worried about a top-level package json. The bigger issue here is the nested python packages.

Closing this issue, then.


total response of budget allocation is not equl to actual revenue

-Project Robyn
Hi, I have a few questions about the 'initial total repose' value in the budget allocation section.

I understood the meaning of the initial part as the expected value of Y (Revenue) when used at the same cost as the last 4 weeks. Is my understanding correct?

If I'm correct, the total response means the expected revenue for the next 4 months?

1.53M seems too small for 4 months of revenue
1.64 ROAS also seems too small
(In the sample code, the last 4 months' ROAS is over 1000%, and the weekly Revenue is greater than 2 million)

I'd be grateful if you could explain what I'm misunderstanding.
Thank you

-Environment & Robyn version
Robyn version: <IP_ADDRESS>00
R version 4.1.3 (2022-03-10)

When I just ran the example code directly, the total response value was smaller.
Why does it appear differently each time I run it?

Look at the subtitle, it's for 4 weeks, not 4 months

Look at the subtitle, it's for 4 weeks, not 4 months, so 932k is 4 weeks' spend and 1.53M the response on it.

Sorry I know it's 4 weeks.  It was just a typo.
Does 1.53 million mean the sum of revenue over the next 4 weeks?
Even if it's 4 weeks, isn't it too small?
In the example data used, more than 2 million revenues were generated in one week.

1.53m is media response only, without "the rest" like trend / season etc. We can't allocate budget for variables that dont have spend.

1.53m is media response only, without "the rest" like trend / season etc. We can't allocate budget for variables that dont have spend.

We can understand it as revenue excluding the baseline.  Thanks for the explanation.


Fix glyphicon display for generic-lookup

Fixes issue #214.

Closing, and going to recreate not based on my master branch.


Position mismatch of freedraw in fixed container size

Give it fixed width and height, and start to draw something. then you can observe there's a gap between your intention and the actual drawing, there's simply a difference as much as you resized the container from the initial render.
Here's a short video of the reproduction
https://github.com/excalidraw/excalidraw/assets/8914311/75226a7f-8814-4a03-8171-da3573423a0e

I also had a similar issue on a project which uses Excalidraw. In our case, we had an absolute container as a direct parent of Excalidraw and a relative container around the absolute container. Whenever we'd set fixed dimensions (height/width) on either of these containers, we'd have the same issue as seen in the video.
I was able to fix it by adding another parent element and setting the fixed dimensions on that element instead of the before mentioned two. This parent element did not have an explicit position css declaration set. It only had the width/height declaration with auto margins.
Might not be an ideal case, but I wanted just to point it out in case it helps someone facing the same issue.


Offline mode doesn't work when saving objects

When saving objects, Offline mode doesn't work since it still tries to use the save_file method in the Offline factory:
  File "/home/wk9874/Documents/temp/venv/lib/python3.10/site-packages/simvue/factory/proxy/offline.py", line 138, in save_file
    fh.write(data["pickled"])
TypeError: a bytes-like object is required, not 'str'

Also means that matplotlib figures cannot be uploaded in Offline mode


cni error when using openstack cloud_provider and extra_binds option

Issue seems to be related to #26880
What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

create a cluster on openstack node with openstack provider, using extra_binds option to provide internal CA to the kubelet containers, but with no cloud_provider configured:

#
# Cluster Config
#
answers: {}
docker_root_dir: /var/lib/docker
enable_cluster_alerting: false
enable_cluster_monitoring: false
enable_network_policy: false
local_cluster_auth_endpoint:
  enabled: true
name: rancher-test
#
# Rancher Config
#
rancher_kubernetes_engine_config:
  addon_job_timeout: 30
  authentication:
    strategy: x509|webhook
  authorization: {}
  bastion_host:
    ssh_agent_auth: false
  dns:
    provider: coredns
    upstreamnameservers:
      - <IP_ADDRESS>
      - <IP_ADDRESS>
    linear_autoscaler_params: {}
    node_selector: null
    nodelocal:
      ip_address: ''
      node_selector: null
      update_strategy: {}
    reversecidrs: null
    stubdomains: null
    update_strategy: {}
  ignore_docker_version: true
#
# # Currently only nginx ingress provider is supported.
# # To disable ingress controller, set `provider: none`
# # To enable ingress on specific nodes, use the node_selector, eg:
#    provider: nginx
#    node_selector:
#      app: ingress
#
  ingress:
    provider: nginx
  kubernetes_version: v1.17.6-rancher2-2
  monitoring:
    provider: metrics-server
    replicas: 1
#
#   If you are using calico on AWS
#
#    network:
#      plugin: calico
#      calico_network_provider:
#        cloud_provider: aws
#
# # To specify flannel interface
#
#    network:
#      plugin: flannel
#      flannel_network_provider:
#      iface: eth1
#
# # To specify flannel interface for canal plugin
#
#    network:
#      plugin: canal
#      canal_network_provider:
#        iface: eth1
#
  network:
    mtu: 0
    options:
      flannel_backend_type: vxlan
    plugin: canal
  restore:
    restore: false
#
#    services:
#      kube-api:
#        service_cluster_ip_range: <IP_ADDRESS>/16
#      kube-controller:
#        cluster_cidr: <IP_ADDRESS>/16
#        service_cluster_ip_range: <IP_ADDRESS>/16
#      kubelet:
#        cluster_domain: cluster.local
#        cluster_dns_server: <IP_ADDRESS>
#
  services:
    etcd:
      backup_config:
        enabled: true
        interval_hours: 12
        retention: 6
        safe_timestamp: false
      creation: 12h
      extra_args:
        election-timeout: '5000'
        heartbeat-interval: '500'
      gid: 0
      retention: 72h
      snapshot: false
      uid: 0
    kube-api:
      always_pull_images: false
      pod_security_policy: false
      service_node_port_range: 30000-32767
      extra_binds:
        - "/usr/local/share/ca-certificates:/usr/local/share/ca-certificates"
    kube-controller: {}
    kubelet:
      fail_swap_on: false
      generate_serving_certificate: false
      extra_binds:
        - "/usr/local/share/ca-certificates:/usr/local/share/ca-certificates"
    kubeproxy: {}
    scheduler: {}
  ssh_agent_auth: false
  upgrade_strategy:
    drain: false
    max_unavailable_controlplane: '1'
    max_unavailable_worker: 10%
    node_drain_input:
      delete_local_data: 'false'
      force: false
      grace_period: -1
      ignore_daemon_sets: true
      timeout: 120
scheduled_cluster_scan:
  enabled: false
  scan_config:
    cis_scan_config:
      override_benchmark_version: rke-cis-1.4
      profile: permissive
  schedule_config:
    cron_schedule: 0 0 * * *
    retention: 24

The cluster is correctly deployed and worker nodes can be added. Add a cloud_provider configuration to the cluster:

rancher_kubernetes_engine_config:
....
  cloud_provider:
    name: openstack
    openstackCloudProvider:
      global:
        username: MMMM5064
        password: PASSWORD
        auth-url: https://api-openstack:5000/v3
        tenant-id: 42f1239d024641388654d5a16038e509
        domain-name: ad-subs
        ca-file: /usr/local/share/ca-certificates/CA-root.crt
      load_balancer:
        use-octavia: true
        subnet-id: 640f9933-6404-4913-b9b8-0421c7322e4c
      block_storage:
        ignore-volume-az: true
...

add a worker node
New node stays a at unavailable status, with this error message : Runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

Kubelet logs:
W0630 14:26:12.844873   13990 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
E0630 14:26:15.994177   13990 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
W0630 14:26:17.845260   13990 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
W0630 14:26:19.133897   13990 setters.go:158] adding overridden hostname of worker3 to cloudprovider-reported addresses
E0630 14:26:21.001771   13990 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
W0630 14:26:22.845710   13990 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
E0630 14:26:26.008869   13990 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
W0630 14:26:27.846005   13990 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
W0630 14:26:29.154433   13990 setters.go:158] adding overridden hostname of worker3 to cloudprovider-reported addresses
E0630 14:26:31.017746   13990 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

On worker node, the /etc/cni directory is emtpy.
Result:
Worker node cannot be deployed.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.5
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Infrastructure Provider
Machine type (cloud/VM/metal) and specifications (CPU/memory): cloud, 2vCPU, 4Go RAM
Kubernetes version (use kubectl version):

kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.6", GitCommit:"d32e40e20d167e103faf894261614c5b45c44198", GitTreeState:"clean", BuildDate:"2020-05-20T13:08:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

docker version
Client: Docker Engine - Community
 Version:           19.03.11
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        42e35e61f3
 Built:             Mon Jun  1 09:12:22 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.11
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       42e35e61f3
  Built:            Mon Jun  1 09:10:54 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

same problem

I'm having this exact same problem, except I'm using the aws provider. Any ideas?

Does it work when you configure the cloud provider from the beginning? And please supply more logs of both the controlplane and worker k8s components (from the start). Also outputs of kubectl get nodes and kubectl get pods --all-namespaces would be a start

I am also having this issue. The whole thing: openstack provider, extra_binds for the kubelet CA, and everything.


sst start: silence logs for specific Functions

Requested by Pavan

I still want live debug, but don't want to print anything in terminal.
I have a lambda which listen to Topic. This SNS Topic is not part of our project. This topic gets lot of events. So we end up getting lots of logs from this particular lambda pollution our terminal.
So we want to silence output from this lambda. May be as follows
sst start -silence Lambda1

Hey @fwang is silence now supported? Is it possible to remove logs from the terminal?
Should this issue still be open?

Hey @riccardogiorato, I must have closed this by mistake. Re-opening this.
Yeah, this is definitely on our mind, and we are making some changes to the terminal to give ppl more control over the lambdas and logs.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Fixed Several Minor Issues  & Page Restructured

Related Issue
Fixing Several Minor Issues Simultaneously
Due to recent pull requests being merged, the BuddyTrail website has developed several bugs from unresolved or incorrectly resolved conflicts. Issues include duplicate footers, misaligned and extra text, and other common problems. Going forward, I’ll group more issues together to handle multiple fixes in a single PR. This approach will allow me to contribute more effectively  and avoid any perception of spam.
Fixes:  #1835
Description
Cookie Policy page was completely disturbed

THEN

NOW

Hotel Page Nav Bar is now have no margin on top. Deleted extra text above nav bar

then

now

footer of  copyright page was disturbed and have useless text below it

then

now

himachal treck page had different picture sizes causing uneven tile ; also it was not linked with himachal.css file

similar issue on rajasthan page

then

now

Type of PR

[x] Bug fix

[x] Feature enhancement

[x] I have made this change from my own.

[x] I have taken help from some online resources.

[x] My code follows the style guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code, particularly in hard-to-understand areas.

[x] I have made corresponding changes to the documentation.

[x] My changes generate no new warnings.

[x] I have tested the changes thoroughly before submitting this pull request.

[x] I have provided relevant issue numbers and screenshots after making the changes.
@PriyaGhosal  please review this pr

@Adarsh-Chaubey03 Great contribution ! 🎉 Your pull request has been successfully merged! Also Take a moment to ⭐ Star the repository if you haven't already.