openai: 1.7.1 -> 1.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/openai/openai-python/releases.
meta.description for openai is: Python client library for the OpenAI API
meta.homepage for openai is: https://github.com/openai/openai-python
meta.changelog for openai is: https://github.com/openai/openai-python/releases/tag/v1.9.0
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.0 with grep in /nix/store/2q1by8r4yriw31pfg4n46z7k3nvrgd82-python3.11-openai-1.9.0
found 1.9.0 in filename of file in /nix/store/2q1by8r4yriw31pfg4n46z7k3nvrgd82-python3.11-openai-1.9.0

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

16 total rebuild path(s)

16 package rebuild(s)

First fifty rebuilds by attrpath
chatblade
chatgpt-retrieval-plugin
checkov
home-assistant-component-tests.openai_conversation
imaginer
khoj
llm
open-interpreter
openai
pentestgpt
python311Packages.guidance
python311Packages.litellm
python311Packages.llm
python311Packages.open-interpreter
python311Packages.openai
shell-genie

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2q1by8r4yriw31pfg4n46z7k3nvrgd82-python3.11-openai-1.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/0897155dfc37dd1bfcfa95285e7e30756a99d2ca#openai

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2q1by8r4yriw31pfg4n46z7k3nvrgd82-python3.11-openai-1.9.0
ls -la /nix/store/2q1by8r4yriw31pfg4n46z7k3nvrgd82-python3.11-openai-1.9.0/bin

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

1 package marked as broken and skipped:

chatgpt-retrieval-plugin

3 packages failed to build:

khoj
llm (python311Packages.llm)
shell-genie

8 packages built:

chatblade
checkov
imaginer
open-interpreter (python311Packages.open-interpreter)
openai (python311Packages.openai)
pentestgpt
python311Packages.guidance
python311Packages.litellm

Maintainer pings
cc @malob for testing.

Closing in favor of: #281620


Recommend Raven.context in getting started docs

I'm a little torn on adding this. For one, it's an additional onboarding step which might pose additional difficulty for users getting started. But for a small % of users (20%?), using Raven.context here will surface other errors that would otherwise get lost to 'Script error". And because we discard "Script error" by default (and no console logging), I feel we need to recommend using it.
For more on this, see "An alternative solution: try/catch" in this script error blog post.
cc @dcramer @mattrobenolt @lewisjellis

I'm good with adding it, but I feel like it's missing a "here's why" or "more on that" link. Do we have any further explanation of this anywhere deeper in the docs we could link to? I'd at least want to include a link to the blog post here, or some sort of explanation for why we recommend that. We make a similar "run your app in a context wrap" recommendation in raven-node (also without a ton of explanation), and I get the feeling (from a few issue tracker discussions) that there's been a bit of user confusion around it.

Agree with @LewisJEllis, it'd be nice to add some more context to this one, so that users know why it's recommended. @benvinegar

@benvinegar updated the recommendation and added reasoning behind it

So, this is the text that is showed to brand new users of Sentry, right as they're signing up and after they've chosen a platform. We shouldn't link to external resources here, because people could exit the onboarding flow and that would be bad.
I'd also rather not inform them about "Script error", or any other concepts that might deviate them from the mission of just getting this running in their application.

Gotcha. Updated.


file missing in ./log

Hi, sorry to bother you, I really appreciate this new method paper on relative topic, but it raised the issue "Traceback (most recent call last):
File "/root/codes/MuseNet/train.py", line 778, in
os.mkdir(log_dir)
FileNotFoundError: [Errno 2] No such file or directory: './log/debug'
run.sh: 4: --name: not found" when runnning training step. It seems that ./log/debug is missing. Could you pls re-upload the repository? Thx a lot:)

cd MuseNet
mkdir log
The above two commands will fix the error you describe.


Unexplainable tooltip offset in XY-Chart when orientation of YAxis is set to left.

It might be a bug, but I've been wrapping my head around this for a couple of hours now. Once I put the Y-Axis on the left side, the tooltip is no longer in sync with the position of the mouse.

It seems to be caused by the orientation-prop of the YAxis.
    <YAxis label="GPTW RPM" orientation='left' numTicks={8}/>

Full
  <XYChart
      margin= {{top: 10, left: 60, right: 10, bottom: 40 }}
      width={props.parentWidth}
      height={props.height}
      showYGrid
      showXGrid
      xScale={{ type: 'time' }}
      yScale={{ type: 'linear' }}
      renderTooltip={({ event, datum, data, color }) => {
       const monthNames = ["January", "February", "March", "April", "May", "June",
        "July", "August", "September", "October", "November", "December"
       ];
       const month = monthNames[datum.x.getMonth()];
       return (

           {datum.label}

Month: {month} {datum.x.getYear() + 1900}

       );
      }}
      snapTooltipToDataX
    >
    <HorizontalReferenceLine
      reference={1}
      stroke='#000000'
      strokeWidth={1}
      strokeDasharray='3 3'
      dashType='dotted'
      strokeLinecap='butt'
      label="House average"
      labelProps={{ width: 100, verticalAnchor: 'middle', dx: 5, dy: -10}}
    />

    <XAxis label="Time" />
    <YAxis label="GPTW RPM" orientation='left' numTicks={8}/>
     <CrossHair showHorizontalLine={false} fullHeight stroke="pink" />
  </XYChart>

Any help is appreciated!

hey @jhofstede thanks for checking out @data-ui. We recently discovered this bug as well when orientation="left". It should be a pretty straightforward fix, I think the computation just doesn't take into account the left margin properly.
I'll try to get to it in the next day or so 👍

@williaster many thanks for your work on @data-ui and your quick reply!


(Help!) How do you use the funtions :

Item.setProperties(par1int, par2Object);
function redstoneUpdateHook(x, y, z, newCurrent, someBooleanIDontKnow, blockId, blockData);
Tanks!
Psdt:(openinghish traslator. )

Item.setProperties is using a json thing in the object, for example:
Item.setProperties(331/redstone dust/, { "foil": /enchantment grid/ true });
and the redstoneUpdateHook is hard to splain

Example for setProperties: https://github.com/zhuowei/ModPEScripts/blob/master/500ise_exttest.js#L38
Example for redstoneUpdateHook: https://github.com/zhuowei/ModPEScripts/blob/master/piston.js#L120
Hope that helps - if you need more explanation, I'll try to do a writeup on Connor's wiki

@Sime69
Block.setRedstoneConsumer(2,true);
function redstoneUpdateHook(x,y,z,newCurrent,worldLoading,blockId,blockDamage) {
	var powered = newCurrent;

if(blockId == 2 && powered >= 1 && powered <= 15){
clientMessage("was this helpful?");
}}


build and publish precompiled sedna sdk to PyPI

What would you like to be added/modified:
It would be great if you set up Github Actions CI to build wheels for all supported python versions and platforms and publish them (either automatically when pushing git tags, or manually if you prefer) to the Python Package Index (PyPI) so that pip install sedna works without needing a complete clone from github.
for more documentation
you can read
GitHub Actions Docs
also you can watch this video to get an understanding / maybe it will help
Video on PyPi GitHub Actions

/close


another fd leak

similar to #655
one line 244 https://github.com/camlistore/camlistore/blob/master/pkg/blobserver/diskpacked/diskpacked.go#L244
if this f.Seek() call returns error, fd should be closed. Otherwise, the error populate up and no Storage object is created then the fd becomes an orphan.

When openAllPacks() fails on nextPack() or openForWrite(), those read fds should also be closed.

When openAllPacks() fails on nextPack() or openForWrite(), those read fds should also be closed.

The first one I see, but openAllPacks calls storage.Close on error which closes all in s.fds. Ain't that enough?

PTAL https://camlistore-review.googlesource.com/6326

Try to remember what I meant back then.
To answer your question, When openAllPacks fails on nextPack() or openForWrite(), it won't call storage.Close() which is only called when openAllPacks fails on openForRead(). In another word, if line 310 return s.nextPack() returns an err, those read fds should be closed but not.
Hope I made myself clear.

I've moved the s.Close() from openAllPacks to its (only) caller. This way all open fds will be closed on any error.


Atom-Beautify on Mac not working

Description
I've been using beautify to great success until today... when i went to use it just now I continually get a notification that, "Atom Beautify could not determine a supported beautifier to handle this file with grammar "Null Grammar" and extension "undefined"."
Input Before Beautification
This is what the code looks like:

14pt Standard Business Cards

Gloss-Coated or Matte Finish width Rounded Corners and Special Shapes available!

I havent been able to get any further.
Checklist
I have:

[ X] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] Reloaded (or restarted) Atom to ensure it is not a caching issue
[X] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

Please run Atom Beautify: Help Debug Editor and add the link.


groom integration_tests cargo.toml file

context https://github.com/rusoto/rusoto/pull/1304#discussion_r263906072
the integration_tests module is an essential smoke testing harness. it's cargo.toml file a large number of items that would benefit from some organization. This could be as easy as setting up a process arround running https://github.com/tbrand/cargo-tomlfmt on it to keep it tidy. I tried this once but found that subkeys of table like those of [dependencies.xxx] are not included in alphabetized sorting.
Let's see if we can't do something about making this file easier to contribute to.
Bonus points if we can automagically synthesize this file from the knowledge the build has about what services exist so that no manual modifications is needed.

This would also be good to have for splitting up our test runs: right now we stuff everything into one big cargo project that's getting bigger and bigger, which makes running tests for all services take a long, long time on my personal laptop.


Mapping non List nested collections fix (lile HashSet etc), Tests.

Automapper raises an exception if collection type was not a List due calling Add method using reflection. This was because we explicitly set baseListType as List<> but if instance is not null it may not be a List<>.

@sharpcoder7 Had this same issue today, your PR did the trick :) Thanks a lot!


[FEATURE REQUEST] From raw C GdkGlContext*

I have a C++ Flutter code which generates me a GdkGLContext:
  GdkWindow *window = gtk_widget_get_parent_window(GTK_WIDGET(self->fl_view));
  GError *error = NULL;
  GdkGLContext *context = gdk_window_create_gl_context(window, &error);

where the pointers are C pointers.
On https://github.com/gtk-rs/gtk3-rs/blob/master/gdk/src/auto/gl_context.rs I added
    pub fn new_from_ptr(gl_context: *mut ffi::GdkGLContext) -> Self {
        assert_initialized_main_thread!();
        unsafe {
            from_glib_none(gl_context)
        }
    }

so I could initialize it from a raw C GdkGlContext, but I get a panic on assert_initialized_main_thread!, probably because the gtk3-rs has an internal watcher to see if the main thread is initialized, and I'm trying to initialize an object without having a context.
Can I do a PR without the assertion?
    pub fn new_from_ptr(gl_context: *mut ffi::GdkGLContext) -> Self {
        //assert_initialized_main_thread!();
        unsafe {
            from_glib_none(gl_context)
        }
    }

works but I can't be sure yet cause I get a function was not loaded panic probably on epoxy (cause I don't know how to do OpenGL on gtk3-rs)

you can use from_glib_none from your side as well?

Sorry I did not understand the question. i used it, it didn't crash, it crashed on epoxy as far as I understood.
-------- Mensagem Original --------
Em 23 de jul. de 2022 19:01, Bilal Elmoussaoui escreveu:

you can use from_glib_none from your side as well?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I fixed the epoxy crash, now no crashes (but also no image), but I need to know if it's ok to do
    pub fn new_from_ptr(gl_context: *mut ffi::GdkGLContext) -> Self {
        unsafe {
            from_glib_none(gl_context)
        }
    }

on the PR

You don't need a new function, just call from_glib_none() yourself.
For initialization there's the unsafe gtk::set_initialized() that you'd need here if you assume something else called gtk_init() for you already.

    unsafe { gtk::set_initialized() };
    println!("gtk::is_initialized: {}", gtk::is_initialized());
    let context = unsafe { gdk::GLContext::from_glib_none(gdk_gl_context_ptr) };
    println!("version: {:?}", context.version());
    println!("is_legacy: {:?}", context.is_legacy());

gives
(my_app:13317): Gdk-CRITICAL **: 21:46:24.482: gdk_gl_context_get_version: assertion 'priv->realized' failed

(my_app:13317): Gdk-CRITICAL **: 21:46:24.482: gdk_gl_context_is_legacy: assertion 'priv->realized' failed

and prints
gtk::is_initialized: true
version: (0, 33742432)

I even tried putting gtk::init() before but same problem.

As the error suggests, your problem is that the context is not realized yet and because of that can't be used.


Change Problem class definition

The PR mentioned in the other PR.

Tests aren't passing because they're using the old version of algobattle, if you clone both PR branches and install them they pass


ML 4.5 : Deep Q-Networks (D)

Description
📌  Issues for Week 4
Welcome to 'ML' Team, good to see you here
:arrow_forward: This issue will helps readers in acquiring all the knowledge that one needs to know about ----
Deep Q-Networks.
:red_circle: To get assigned to this issue, add your Batch Numbers mentioned in the spreadsheet of "Machine Learning", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
✔ Domain : Machine Learning
:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.

"Issue Title" and "PR Title should be the same. Include issue number along with it.

Changes should be made inside the Machine Learning/Machine_Learning/Reinforcement_Learning Branch.

Follow Contributing Guidelines & Code of Conduct before start Contributing.

This issue is only for 'GWOC' contributors of 'Machine Learning' domain.

:white_check_mark: To be Mentioned while taking the issue :

Full name
Batch Number
GitHub Profile Link
Which type of Contribution you want to make :

[ ] Documentation

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎
Domain
Machine Learning
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Name- Uttara Bahad
Batch Number- 3
GitHub Link- https://github.com/uttarabahad
Type of contribution- Documentation

name tisha jhabak batch 6 github: https://github.com/TishaJhabak1014 Documentation

@uttarabahad Issue assigned to you, complete this within 3 days.


Suggestion - Registering a property with the Omni Foundation

Hey guys,
I've been reflecting on certain issues and have come up with a suggestion that may serve to address several topics to various degrees in one swoop.
The concept is a simple one.  Registration of a property with the foundation offers zero technical benefits and is not in any way required to use the functionality of the Omni Protocol, however it does grant certain social and marketable benefits via products and services the Omni Foundation sponsors.
The proposed benefits can be aligned with needs we are starting to see entrench themselves in day to day ops.    We've looked at multiple options, and I myself have proposed a couple of others (such as floating algo for issuing a SYMBol on property creation) but we haven't really reached a consensus on method.  Registering a property with the foundation would include registration of a SYMBol which would be used in place of the SPT# to display tokens.

We have no concept of icons for the different tokens in any of the foundation sponsored platforms.  Registration of a property would include submission of an icon/coin image/whatever eg 64x64px for displaying tokens.

We are limited to 255 characters for property 'detailed information' without sending the client to a web resource (which is not desirable for privacy reasons).  Registration of a property would include (example) 5000 characters additional text and one additional banner image for a property.

Note it's critical to understand that registering a property with the Omni Foundation is not mandatory, and only grants these benefits to Foundation sponsored platforms (so OmniWallet, OmniChest, Omni Core etc) and does not guarantee any 3rd party usage of these resources.
Note, once registered the resources supplied (icons, text, SYMBol etc, if accepted) would be included in the official github repos as part of the source (we would not store them web-side or blockchain-side).
Note, this has no impact at all on the sponsoring a property transaction methodology or validity, it is an entirely centralized concept about the issuer-foundation relationship and the benefits there-in; it bears no technical impact on the technology.  It is simply an ability to allow issuers to register resources (icon/SYMBol etc) for usage in reference software (and our web wallet/block explorer).  I really want to stress that this not about the software of the protocol, it's simply about presentation (and perhaps a little monetization :P)
There are many other similar types of benefits I could harp on about but I think you get the idea.  A potential revenue stream is always helpful and I think it would allow us to really neaten up the UI for properties that want to register (unregistered props would function just fine, just wouldn't be as 'pretty').
Thoughts?
Thanks
Z

Interesting idea. So, instead of assigning a human-readable name to every
asset, we'd wait for them to pay us?
On Fri, Dec 26, 2014 at 8:31 PM, zathras-crypto<EMAIL_ADDRESS>wrote:

Also, I'm not positioning a cost - that's for the business guys :)
—
Reply to this email directly or view it on GitHub
https://github.com/mastercoin-MSC/spec/issues/297#issuecomment-68168558.

Interesting idea. So, instead of assigning a human-readable name to every
asset, we'd wait for them to pay us?
On Fri, Dec 26, 2014 at 8:31 PM, zathras-crypto<EMAIL_ADDRESS>wrote:

Also, I'm not positioning a cost - that's for the business guys :)
—
Reply to this email directly or view it on GitHub
https://github.com/mastercoin-MSC/spec/issues/297#issuecomment-68168558.

Interesting idea. So, instead of assigning a human-readable name to every asset, we'd wait for them to pay us?

Well, asset creation remains completely unchanged.  For example MaidSafe would still be issued with the human readable name 'MaidSafeCoin (#3)' and function as per current regardless of registration.  There are no protocol changes here at all, only 'display' changes for Omni sponsored systems (Omniwallet, OmniCore, Omnichest etc).
Perhaps I could use 'Chest as an example.  By default, properties will have a generic icon, a generic token SYMBol and no extended property info, which all become available after registration.
NON-FOUNDATION-REGISTERED PROPERTY

FOUNDATION-REGISTERED PROPERTY

TL:DR; registration is a layer above the protocol - nothing is changed on the blockchain for a property registration, we simply add extra data for the property into a new token customization DB which is shipped with each of our sponsored platform.

Interesting idea. So, instead of assigning a human-readable name to every asset, we'd wait for them to pay us?

Well, asset creation remains completely unchanged.  For example MaidSafe would still be issued with the human readable name 'MaidSafeCoin (#3)' and function as per current regardless of registration.  There are no protocol changes here at all, only 'display' changes for Omni sponsored systems (Omniwallet, OmniCore, Omnichest etc).
Perhaps I could use 'Chest as an example.  By default, properties will have a generic icon, a generic token SYMBol and no extended property info, which all become available after registration.
NON-FOUNDATION-REGISTERED PROPERTY

FOUNDATION-REGISTERED PROPERTY

TL:DR; registration is a layer above the protocol - nothing is changed on the blockchain for a property registration, we simply add extra data for the property into a new token customization DB which is shipped with each of our sponsored platform.

I think this is great and is sort of related to #250 - moving meta-data off-chain, while this topic is about providing enhanced meta data as a service. This again, is somewhat close to the initial idea of the "promote property" idea, I think.
I have a rather strong opinion on meta-data in general and I'd prefer to get rid of it in general, so a property is only defined and identified by it's id - which, by the way, should not be derivded from previous state (see the problems the P2SH rollout created where property ids where off  by two numbers for old clients). Different topic though, ...
Now I hope there will be the day when Masterchest.info finally becomes the explorer for MSC properties again and I think you should provide such a service anyway, either with or without consensus or doing a likewise move with other "official products", because it adds value - namely easier property identification and enhanced information.
I have no insight in the whole sponsoring process, but regarding this idea here I have one rather important question:
Who is eligible to register for enhanced property information and such a service?

I think this is great and is sort of related to #250 - moving meta-data off-chain, while this topic is about providing enhanced meta data as a service. This again, is somewhat close to the initial idea of the "promote property" idea, I think.
I have a rather strong opinion on meta-data in general and I'd prefer to get rid of it in general, so a property is only defined and identified by it's id - which, by the way, should not be derivded from previous state (see the problems the P2SH rollout created where property ids where off  by two numbers for old clients). Different topic though, ...
Now I hope there will be the day when Masterchest.info finally becomes the explorer for MSC properties again and I think you should provide such a service anyway, either with or without consensus or doing a likewise move with other "official products", because it adds value - namely easier property identification and enhanced information.
I have no insight in the whole sponsoring process, but regarding this idea here I have one rather important question:
Who is eligible to register for enhanced property information and such a service?

Thanks for the feedback...

which, by the way, should not be derivded from previous state (see the problems the P2SH rollout created where property ids where off by two numbers for old clients). Different topic though, ...

May be different topic but I would love to see us revisit this in open discussion with everyone - there are some potential roadblocks we can avoid if we shifted away from sequential property ID's.

Now I hope there will be the day when Masterchest.info...

FYI masterchest.info is not long for this world - will be taken over by Chest v5 (parses via Core), been spending Xmas trying to get it ready before 0.0.9 tag (STO support etc).  v5 will be launched at http://omnichest.info (very much WIP) to fit in with the rebranding.  Re services from 'Chest, at the moment the foundation sponsors it by paying the hosting fees thus I wouldn't feel right monetizing it personally (though I reserve the right to monetize 'Chest at some point in future if the foundation decides to stop sponsoring for any reason haha!)

Who is eligible to register for enhanced property information and such a service?

In my view - anyone - you just need to be able to sign a message from the issuing address for the property you want to register to prove ownership, but other than that I see no reason to put in obstacles (though some kind of approval process I guess is needed to avoid accepting logo/text containing something nefarious that'll get us into trouble (eg dodgy pictures of kids or something))

Thanks for the feedback...

which, by the way, should not be derivded from previous state (see the problems the P2SH rollout created where property ids where off by two numbers for old clients). Different topic though, ...

May be different topic but I would love to see us revisit this in open discussion with everyone - there are some potential roadblocks we can avoid if we shifted away from sequential property ID's.

Now I hope there will be the day when Masterchest.info...

FYI masterchest.info is not long for this world - will be taken over by Chest v5 (parses via Core), been spending Xmas trying to get it ready before 0.0.9 tag (STO support etc).  v5 will be launched at http://omnichest.info (very much WIP) to fit in with the rebranding.  Re services from 'Chest, at the moment the foundation sponsors it by paying the hosting fees thus I wouldn't feel right monetizing it personally (though I reserve the right to monetize 'Chest at some point in future if the foundation decides to stop sponsoring for any reason haha!)

Who is eligible to register for enhanced property information and such a service?

In my view - anyone - you just need to be able to sign a message from the issuing address for the property you want to register to prove ownership, but other than that I see no reason to put in obstacles (though some kind of approval process I guess is needed to avoid accepting logo/text containing something nefarious that'll get us into trouble (eg dodgy pictures of kids or something))

May be different topic but I would love to see us revisit this in open discussion with everyone

Great to hear, would really like to make progress in this direction. #280 was an attempt in this direction which quickly stalled.

In my view - anyone

Here is the problem I see: it's for free when using other products (e.g. http://www.blockscan.com/assetInfo/LTBCOIN), but the more relevant issue: "premium" properties imply a certainly higher degree of credibility. If it's free for anyone, there is no exploit vector, because chances are equal and it's "fair", but paid premium properties may open the doors for scam. Let me exaggerate: what if I create a fake MaidSafe token and start to promote it to sell my fake tokens on the DEx? This introduces two consequences:

It would be a bad outcome, if, for some reason, a scam makes it through the approval process. The process itself is undefined at this point, but I would assume such a process is not trivial and the auditor is probably going to be pitchforked, if something dodgy slips through.

It may create pressure on legit issuers, because "no premium" properties imply a lesser degree of credibility.

May be different topic but I would love to see us revisit this in open discussion with everyone

Great to hear, would really like to make progress in this direction. #280 was an attempt in this direction which quickly stalled.

In my view - anyone

Here is the problem I see: it's for free when using other products (e.g. http://www.blockscan.com/assetInfo/LTBCOIN), but the more relevant issue: "premium" properties imply a certainly higher degree of credibility. If it's free for anyone, there is no exploit vector, because chances are equal and it's "fair", but paid premium properties may open the doors for scam. Let me exaggerate: what if I create a fake MaidSafe token and start to promote it to sell my fake tokens on the DEx? This introduces two consequences:

It would be a bad outcome, if, for some reason, a scam makes it through the approval process. The process itself is undefined at this point, but I would assume such a process is not trivial and the auditor is probably going to be pitchforked, if something dodgy slips through.

It may create pressure on legit issuers, because "no premium" properties imply a lesser degree of credibility.

Great to hear, would really like to make progress...

Made a suggestion in that thread, let me know your thoughts

Here is the problem I see...

Whilst I don't necessarily disagree with the points raised, I think those are points relevant to the concept of property promotion as a whole rather than the methodology used to provide it.  Whether an issuer pays the foundation to register a property (indirectly providing development funding) or pays the protocol and has the funds burned, the core concept is still the same - that of a token issuer paying to display their property more prominently than the rest.  From the spec:
Say that having created your "Quantum Miner" smart property (which was assigned property ID #8) you now want it to show up higher in the list of properties.
It's essentially the same thing, only difference is where the money goes - my suggestion adds a layer of human approval (whatever form the vetting process takes) which is more than a protocol-only driven approach.  Additionally I think the entire cycle would result in 'real' issuers registering to secure their SYMBol.  With your example of MaidSafeCoin for example, that could only work if MaidSafeCoin hadn't already registered (since you would not be able to re-register the MAID token).
Interesting points though, food for thought :)

With your example of MaidSafeCoin for example, that could only work if MaidSafeCoin hadn't already registered

It's a non-issue for MaidSafeCoin for several reasons, but might be much more complicated in other cases.

I think those are points relevant to the concept of property promotion

I support the idea, and this topic in general, and I agree, my concerns are somewhat related to "property promotion" in general.

I am also in favor of this idea.  I like that it would be available in Foundation-supported apps first, but would like to see a JSON format queriable blob that others could pull if they wanted to use that information as well.  Making it generic enough such that other “registrars” would be able to publish info would be good too, but I like the direction this is going in its most simple form.

would like to see a JSON format queriable blob

Foundation web resources (OmniChest, OmniWallet) can easily provide registered property metadata over an API.

Making it generic enough such that other “registrars” would be able to publish

Would ship with Core, so anyone using Core can republish this same info :)


Downgrading to go 1.19 to maintain compatibility with applications running go >= 1.19

Could you add a bit more details to the PR description on why we're doing this?

Added!


docker-push: Remove pushing latest tag

latest should be generated by the repo. Pushing latest into ECR/GCR
requires a -f but also isn’t used by us (I think).
k8s-scripts push SHA tags as well which are used in the deploy process
for images uses latest.
@rosskukulinski

So one of the downsides of not pushing :latest is that you then can't really take advantage of pulling :latest to re-use docker layers.  Thoughts @philipcristiano?

@jmound has reactiveops/k8s-scripts#5 which uses branch and previous commit. It will miss on a new branch with 2 commits but future builds should at least have the branch available.


Bluuur not working on iOS 14

Hello,
first of all i want to thank you for the nice framework. But unfortunately it doesn't work properly on iOS 14. After I updated my device, the blur effect does not displayed anymore. The area is only displayed in grayscale.
Here are my functions:
    func blurThemAll(){
        let blurView = MLWBluuurView()
        let navBlur = MLWBluuurView()
        self.navigationController?.navigationBar.addSubviewWithoutAnimation(subview: navBlur)
        blurView.colorTintAlpha = 0
        blurView.colorTint = .BLACK_141B2C
        view.addSubviewWithoutAnimation(subview: blurView)

        UIView.animate(withDuration: 0.4) {
            navBlur.blurRadius = 8
            blurView.colorTintAlpha = 0.6
            blurView.blurRadius = 8
        }
    }

    func allBlurMustDie(){
        var blurView : MLWBluuurView?
        var navBlur : MLWBluuurView?

        self.view.subviews.forEach { view in
            if view.isKind(of: MLWBluuurView.self){
                blurView = view as? MLWBluuurView
            }
        }

        navigationController?.navigationBar.subviews.forEach({ view in
            if view.isKind(of: MLWBluuurView.self){
                navBlur = view as? MLWBluuurView
            }
        })

        UIView.animate(withDuration: 0.4, animations: {
            navBlur?.blurRadius = 0
            blurView?.colorTintAlpha = 0
            blurView?.blurRadius = 0
        }) { _ in
            blurView?.removeFromSuperview()
            navBlur?.removeFromSuperview()
        }
    }

I hope you can help me with this issue quickly.
Many thanks
Mallenow

Bluuur is built on top of the private class _UICustomBlurEffect which seems no longer works in iOS 14.

Will the framework be updated in the near future?

@Mallenow I would give this a try: https://github.com/unboxme/Blurberry so far so good.

@danh-geo @Mallenow

https://github.com/unboxme/Blurberry

While this seems quite comprehensive I wouldn't use it in production because of the extensive use of private APIs. Recently I found out quite an elegant way to set the blur radius using vanilla UIKit:
    private let animator: UIViewPropertyAnimator

    override init(frame: CGRect) {
        let visualEffectView = UIVisualEffectView(effect: nil) // must be nil

        animator = UIViewPropertyAnimator(duration: 1, curve: .linear, animations: {
            visualEffectView.effect = UIBlurEffect(style: .regular)
        })

...

    // set the needed radius with a percentage:
    animator.fractionComplete = 0.5


How do you make a rule that sends an alert when there is, for example, only 80% disk space left? Low disk space rule

Assuming it's a numeric field called disk_used:
name: something
type: any
index: something
filter:
 - range:
      disk_used:
        gt: .8
alert:
 - something

I have two rules defined for disk space (and two for inode usage).  Warning on 75-84% and critical on 85%+ - this is the warning rule:
filter:
-query
  - query_string:
      query: "type:metricsets AND system.filesystem.used.pct:[0.75 TO 0.84]"

query_delay:
  minutes: 1
query_key: host

The critical rule is:
filter:
-query
  - query_string:
      query: "type:metricsets AND system.filesystem.used.pct:[0.85 TO 1.0]"

query_delay:
  minutes: 1
query_key: host

It's important to use query_key so that each host can be alerted on.
I use query_delay since indexing is delayed on ElasticSearch.

I have two rules defined for disk space (and two for inode usage). Warning on 75-84% and critical on 85%+ - this is the warning rule:
filter:
-query
  - query_string:
      query: "type:metricsets AND system.filesystem.used.pct:[0.75 TO 0.84]"

query_delay:
  minutes: 1
query_key: host

The critical rule is:
filter:
-query
  - query_string:
      query: "type:metricsets AND system.filesystem.used.pct:[0.85 TO 1.0]"

query_delay:
  minutes: 1
query_key: host

It's important to use query_key so that each host can be alerted on.
I use query_delay since indexing is delayed on ElasticSearch.

do we need to specify index: something?
or query: "type:metricsets AND system.filesystem.used.pct:[0.85 TO 1.0]" is enough?

You always need to specify an index. Everything in Elasticsearch has an index.

Yes, a more complete example might be the following, which also includes the index, alert information, and a higher threshold for larger disks:
es_host: $es_host

es_port: 80
aws_region: $es_region

name: "$ea_hostname:  CRITICAL : Disk Usage Alert"
index: $es_index

type: any

realert:
  minutes: 15

filter:
- query:
  - query_string:
      query: "type:metricsets"
- query:
  - query_string:
      query: "(system.filesystem.used.pct:[0.85 TO 1.0] AND system.filesystem.total: <2000000000001) OR (system.filesystem.used.pct:[0.95 TO 1.0] AND system.filesystem.total: >2000000000000)"

query_delay:
  minutes: 1
query_key: host

alert_text_type: alert_text_only
include : ["host","system.filesystem.used.pct","system.filesystem.mount_point"]

alert:
- "slack"
alert_text: "
*Used %*        : {0}\n
*Mount Point*   : {2}\n
*Host*          : {1}\n
*ElastAlert Node*  : $ea_hostname"

alert_text_args: ["system.filesystem.used.pct","host","system.filesystem.mount_point"]

slack_webhook_url: $slack_channel_url
slack_emoji_override: ":heavy_exclamation_mark:"

@itsecureadmin  is it working example?

@mayank023 - yes, that is a working example, if you fill in the variables:

$es_host
$es_index
$es_region
$ea_hostname
$slack_channel_url

Assuming it's a numeric field called disk_used:
name: something
type: any
index: something
filter:
 - range:
      disk_used:
        gt: .8
alert:
 - something

Hello @Qmando ,
I am using the above as a rule for alerting, but the problem that I am facing is that I am receiving alarms for one and the same state every minute, although the value of the usage has no change.
For the test I am using:
filter:

range:
system.filesystem.used.pct:
gt: 0.1
And in mine case, I am receiving emails with value 0.172

I guess this should be in "already seen" section as per my understanding.
Can you help me to fix this issue?
Thanks.

I am using the above as a rule for alerting, but the problem that I am facing is that I am receiving alarms for one and the same state every minute, although the value of the usage has no change.
...
I guess this should be in "already seen" section as per my understanding.

What is the value of realert?  The default of 1 minute would cause this rule to alert each minute until the alert condition was resolved.
https://elastalert.readthedocs.io/en/latest/ruletypes.html

Pretty much your only option is realert
For example:
realert:
  hours: 8

If you want that realert to only apply to a single host, you could add
query_key:
 - hostname

Such that you only get a maximum of one alert per host per 8 hours

Thank you @Qmando and @itsecureadmin,
After adding realert the things are perfect.
Cheers!


Build(deps-dev): Bump @storybook/addon-links from 6.4.3 to 6.4.4 (#2069)

Pull request opened by the merge tool on behalf of #2069

Merged in 2534dfeaf16b31893da5d2cb904b08289c4273fc


Question: Does this library add the css in at runtime or compile time?

Other similar libraries like twin.macro, convert the css-in-js to css at compile time. Wanted to know if this library does the same, or does it insert css at runtime like styled-components, since that is not mentioned anywhere in the README.

Nope this is at runtime only. Not sure how to do it a compile time without have a dedicated webpack/babel/vite plugin

@MathiasGilson if it's being used with SSR, wouldn't the performance of it running at runtime not really be an issue?


Change to avoid getting a different icon than the one selected on shortcut
For example, try to add "Computer manager" shortcut under
 "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\"

without this change another icon is added to the app !! :(

Yes, please. I would also appreciate this feature as I am constantly having to write python codes to open said applications; then use Pyinstaller to make exe files- then a shortcut to said exe file; which seems to get rid of the arrow for whatever reason. I also tried going into the registry and changing the info to do so as well, however, it became confusing when I was actually looking for a shortcut in file explorer as editing it from the registry gets rid of the arrows on all shortcut files so I deleted my update to registry and began the python+pyinstaller method previously stated.


Add support for MAXAR_content_geojson 3D Tiles extension

Fixes https://github.com/CesiumGS/cesium/issues/10320.
Merge https://github.com/CesiumGS/cesium/pull/10350 and https://github.com/CesiumGS/cesium/pull/10351 first
This PR adds support for the MAXAR_content_geojson 3D Tiles extension which makes it possible to load vector data in the OWT Well Formed Format. This is not a replacement for Vector Tiles which still needs more planning.
There are several constraints on the GeoJSON files:

The top level GeoJSON type must be FeatureCollection or Feature.
The geometry types must be LineString, MultiLineString, MultiPolygon, or Polygon.
All geometries are converted to geodesic lines.
Only WGS84 geographic coordinates are supported.

2D and 3D coordinates are supported. GeoJSON properties are supported as well. All the features in the GeoJSON are batched into a single primitive to ensure good performance, and feature IDs are generated so that features are still individually pickable and styleable.
Future work:

Process GeoJSON in Web Worker to avoid hitches
Triangulate polygons

Local sandcastle for visualizing the test models

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

I pushed some very small code changes. Otherwise the PR looks great! I tested with a very large dataset and it rendered the lines in the correct places.


[backport] test: Stabilize upsampling_2d by adjusting tolerance

This backports test: Stabilize upsampling_2d by adjusting tolerance #3377

Please rebase.

TODO: Backport #3410 after this PR is merged.

@niboshi Rebased.

LGTM!


fix(material/core): mat-ripple-element is not fired on disable

When button becomes disabled after the ripple initiated and before the
ripple animation is completed, it will somestimes not fire the
mat-ripple-element correctly. Adding the fadeOutAll() method when
set to disable will fix this issue.
Fixes #22520

@devversion why target: rc and not patch?


Finetune tfhub object detection model on Custom data (TensorFlow 2)

I am interested in training object detectors using efficientdet models. I was able to train the model using the official repo, but I could not train the efficientdet-lite models using the official repo. So I'm interested in using tfhub lite model/feature vector to finetune/retrain on custom data. It seems possible, but I could not find any documentation/notes on how to retrain tfhub object detector. All the docs show the inference only. Any help on this would be greatly appreciated!

Hi @ameyparanjape
Please note that only these efficientdet-lite models are fine-tunable.
Unfortunately, we don't have specific instructions for these models but when you have a look at https://github.com/tensorflow/hub/issues/678 you'll find a reference to the TensorFlow Object Detection API  as well as to the
Eager Few Shot Object Detection Colab that shows how to fine-tune a RetinaNet. Hope that helps!

Closing this issue as stale.Please feel free to reopen.Thanks.


Survival Guide at Tutorial Island cannot cut down tree

Hello,
I am testing some things out and I noticed that I cannot get past the survival guide on the tutorial island as I cannot cut down a tree. Is this a known issue?

cc @Major-

From what I have read on #337 it looks like wood cutting is not implemented in the current plugin system and that we should be looking forward to it in the Kotlin plugins.

(Sorry for the delay) yeah that's correct. You'll have to use admin perms to get out of tutorial island.

Fix for this is blocked on wc landing in #355

Woodcutting is now supported, so this depends on the tutorial island plugin being updated to check if the player has cut down a tree (i.e. has logs in their inventory).

Closing as kotlin-experiments doesn't support tutorial island


DOC: Integrate intersphinx, drop external module wrapping

Beef up the intersphinx game, replace old links to internal function and
class definitions by new ones from niworkflows, sdcflows, smriprep & co.
Remove the import stubs (anatomical and fieldmap workflows & interfaces)
as they are not required anymore.

The workflow seems to work locally. I'm going to merge so that we test more thoroughly with the external modules without wrapping.


Change description/title/color programatically

Being able to change the description, title and color programatically would be helpful for certain slides.
I can currently get a slide, but there's no way to access those textviews.

If you use SimpleSlide the text color is automatically set by looking at your background color to ensure legibility. You can't change the text color manually. If you need that then create your own slide type by extending Slide or define your own layout and use FragmentSlide.Builder.layout().


Updating the issue template

I made a few minor changes to the template. Please let me know if you have any other suggestions.

Codecov Report

Merging #779 into dev will decrease coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev     #779      +/-   ##
============================================
- Coverage     48.17%   48.08%   -0.09%
+ Complexity     2776     2772       -4
============================================
  Files           116      116
  Lines         27854    27854
  Branches       4636     4636
============================================
- Hits          13418    13393      -25
- Misses        12215    12251      +36
+ Partials       2221     2210      -11

Flag
Coverage Δ
Complexity Δ

#JDBC42
47.59% <ø> (-0.11%)
2729 <ø> (-6)

#JDBC43
47.99% <ø> (-0.03%)
2767 <ø> (-2)

Impacted Files
Coverage Δ
Complexity Δ

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
41.75% <0%> (-3.3%)
14% <0%> (-2%)

...m/microsoft/sqlserver/jdbc/SQLServerException.java
75.75% <0%> (-1.52%)
30% <0%> (-1%)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
44.63% <0%> (-1.1%)
106% <0%> (-2%)

...ncurrentlinkedhashmap/ConcurrentLinkedHashMap.java
38.14% <0%> (-0.87%)
42% <0%> (-1%)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
53.47% <0%> (-0.33%)
0% <0%> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/dtv.java
62.31% <0%> (-0.24%)
0% <0%> (ø)

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
63.52% <0%> (-0.21%)
64% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
52.72% <0%> (+0.11%)
263% <0%> (+1%)
:arrow_up:

...c/main/java/com/microsoft/sqlserver/jdbc/Util.java
60.26% <0%> (+0.43%)
88% <0%> (+1%)
: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 e301555...da76fbd. Read the comment docs.


Test Fixtures: BL (MARC) > Allmaps georeferenced

LOC will have MARC records we can add as test fixtures.

Closing. We have an example here:
https://github.com/bplmaps/blacklight-allmaps/blob/main/spec/fixtures/solr_documents/blacklight/bl_georeferenced.json


PeerJ R2C2

Section 1
Related to the above, a bit wider discussion on the open science aspects would be appreciated (still within the scope of this particular article). I support the open software movement related to open science, but there are drawbacks and criticisms as well. Which aspects do you explicitly not resolve in this set up? The authors mention the ethics of open source in the beginning and describe at the end the issue of software development, but not the openness part. How does this journal contribute to the wider development of open science practices (open access clearly, but beyond open data to open software)? This is a subject which could be described in the introduction a bit more rather than taking it for granted

Open source software is a core tenant of open science and JOSS encourages this?

I'm also not entirely sure what drawbacks/criticisms of the open software movement the reviewer is referring to...

How does this journal contribute to the wider development of open science practices (open access clearly, but beyond open data to open software)?

Considering we are explicitly a journal publishing open source software (it's in the name!), the contribution to that aspect of open science should be fairly explicit and obvious. Is the reviewer suggesting that they only see us contributing to open access?
I suppose in addition to a response, there can be a stronger/more explicit connection made at the beginning... I'll take a stab at it.

I've added a sentence at the end of the introduction reflecting what @arfon wrote:

JOSS also supports the broader open-science movement by encouraging researchers to share their software openly and follow best practices in its development.

but I'm not sure what else we need to say.

but I'm not sure what else we need to say.

I think what we have in 7c825e8 and in the response to the reviewer is sufficient.

@tracykteal suggested we replace

However, the drawbacks or criticisms of open-source software the reviewers refers to are not clear to us.

with

We appreciate that there are ongoing discussions about challenges and opportunities in open source. That has been discussed, extensively and well, elsewhere, and is beyond the scope of this article. This journal is meant to support those who have decided to make their software open source and encourage good practices in their open-source software work.

which I agree with, and have updated in the response document.


instance default method

there's currently no way to handle handle default behaviour if access to the model instance is required to figure out if access should be allowed or denied.
This introduces an instance default method that, by default, just calls the classes ability method.
It also uses the same logic to pass on or remove options if the ability methods are called with or without options accordingly.
One example where I'm using this is to only allow access to admin users for objects that are not yet "published".

Sorry I haven't looked into this yet - will try to do so very soon

No sweat! I don't even know if it's useful for anyone out there. But since
I had the code here... :) take your time mate
Nathan Long<EMAIL_ADDRESS>schrieb am Di., 6. Jan. 2015 um
22:37:

Sorry I haven't looked into this yet - will try to do so very soon
—
Reply to this email directly or view it on GitHub
https://github.com/nathanl/authority/pull/90#issuecomment-68938335.

@paukul This looks good! Would you add a couple of changes?

Remove the extend Forwardable in authorizer.rb as it's no longer needed
Update the CHANGELOG with a short note about this change under the heading "Unreleased"

I may revisit the README and do another flow diagram after this is merged.

Merged - thanks! :+1: :smile:

Released in version 3.1.0


GitHub Packages tweaks

cleanup comments from #10938
fix download URL
remove incorrect comment

Review period skipped due to critical label.


Step 6/9 : COPY *.go . When using COPY with more than one source file, the destination must be a directory and end with a /

File: language/golang/build-images.md

Thanks for reporting. I suspect you are trying to build with the classic builder, which is a bit more strict on these.
Are you seeing the same problem when enabling buildkit? You can do so by setting the DOCKER_BUILDKIT=1 environment variable; assuming you're using a Linux or macOS shell;
DOCKER_BUILDKIT=1 docker build <etc>.......

Or
export DOCKER_BUILDKIT=1
docker build <etc>.......

Other options are outlined in https://docs.docker.com/go/buildkit/
That said, I think it's good to be explicit, and to update the examples to have a trailing slash if a directory is intended to be the target.

Opened https://github.com/docker/docker.github.io/pull/13208


Exceptions, errors and logs management

The plugin shall produce log traces during execution.
The implemented code shall follow the code review checklist. coding rules.

S2OPC log features have been routed to FLEDGE logger according to log level.

CPPLINT is applied and a Makefile rule has been added.


Deploy failure due to  "/root/.ssh/id_rsa": invalid format

I followed the instructions for setting up the deploy key, and secret environment variable, but am receiving a "/root/.ssh/id_rsa": invalid format error when deploying.  Any ideas on what could be causing this?
 Deploy1s
and the repository exists.
Run peaceiris/actions-gh-pages@v2
/usr/bin/docker run --name e87b52c1e6a5f69eec4e969af6a4bd60e87b0d_ceeab3 --label e87b52 --workdir /github/workspace --rm -e ACTIONS_DEPLOY_KEY -e PUBLISH_BRANCH -e PUBLISH_DIR -e INPUT_EMPTYCOMMITS -e INPUT_KEEPFILES -e INPUT_FORCEORPHAN -e INPUT_USERNAME -e INPUT_USEREMAIL -e INPUT_COMMITMESSAGE -e INPUT_TAGNAME -e INPUT_TAGMESSAGE -e INPUT_TAGOVERWRITE -e HOME -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e GITHUB_ACTIONS=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/finetune/finetune":"/github/workspace" e87b52:c1e6a5f69eec4e969af6a4bd60e87b0d
INFO: Deploy to keherri/finetune
INFO: setup with ACTIONS_DEPLOY_KEY
# github.com:22 SSH-2.0-babeld-849b9b5f
Cloning into '/github/home/ghpages_14933'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
Load key "/root/.ssh/id_rsa": invalid format
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Use pbcopy < ~/.ssh/id_rsa.pub to get the public deploy key.
Use pbcopy < ~/.ssh/id_rsa to get the private deploy key for Secrets.


AttributeError: 'CLIPTextModel' object has no attribute 'conv_in'

In the Inference stage of Single-Subject Generation, I executed the following command and reported the following error. I would like to ask how to solve it:
python inference.py
--pretrained_model_name_or_path="runwayml/stable-diffusion-v1-5"
--spectral_shifts_ckpt="output_models/checkpoint-500/spectral_shifts.safetensors"
--prompt="A picture of a sks dog in a bucket"
--scheduler_type="dpm_solver++"
--num_inference_steps=25
--num_images_per_prompt=2
device: cuda
Resumed from output_models/checkpoint-500/spectral_shifts.safetensors
Traceback (most recent call last):
File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 142, in
main()
File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 73, in main
text_encoder = load_text_encoder(
File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 45, in load_text_encoder
text_encoder = load_text_encoder_for_svdiff(
File "/home/songchaotian/sct/Apps/svdiff-pytorch/svdiff_pytorch/utils.py", line 137, in load_text_encoder_for_svdiff
set_module_tensor_to_device(model, key, param_device, value=f.get_tensor(key), dtype=torch_dtype)
File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 269, in set_module_tensor_to_device
new_module = getattr(module, split)
File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1614, in getattr
raise AttributeError("'{}' object has no attribute '{}'".format(
AttributeError: 'CLIPTextModel' object has no attribute 'conv_in'

In the Inference stage of Single-Subject Generation, I executed the following command and reported the following error. I would like to ask how to solve it:
python inference.py --pretrained_model_name_or_path="runwayml/stable-diffusion-v1-5" --spectral_shifts_ckpt="output_models/checkpoint-500/spectral_shifts.safetensors" --prompt="A picture of a sks dog in a bucket" --scheduler_type="dpm_solver++" --num_inference_steps=25 --num_images_per_prompt=2
device: cuda Resumed from output_models/checkpoint-500/spectral_shifts.safetensors Traceback (most recent call last): File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 142, in main() File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 73, in main text_encoder = load_text_encoder( File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 45, in load_text_encoder text_encoder = load_text_encoder_for_svdiff( File "/home/songchaotian/sct/Apps/svdiff-pytorch/svdiff_pytorch/utils.py", line 137, in load_text_encoder_for_svdiff set_module_tensor_to_device(model, key, param_device, value=f.get_tensor(key), dtype=torch_dtype) File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 269, in set_module_tensor_to_device new_module = getattr(module, split) File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1614, in getattr raise AttributeError("'{}' object has no attribute '{}'".format( AttributeError: 'CLIPTextModel' object has no attribute 'conv_in'

Hi， I have the same error, have you solved it ?

您发给我的信件已经收到，感谢您的配合，辛苦了。

Hi, I get the same error, did you find the solution?

@SongChaotian

In the Inference stage of Single-Subject Generation, I executed the following command and reported the following error. I would like to ask how to solve it:
python inference.py --pretrained_model_name_or_path="runwayml/stable-diffusion-v1-5" --spectral_shifts_ckpt="output_models/checkpoint-500/spectral_shifts.safetensors" --prompt="A picture of a sks dog in a bucket" --scheduler_type="dpm_solver++" --num_inference_steps=25 --num_images_per_prompt=2
device: cuda Resumed from output_models/checkpoint-500/spectral_shifts.safetensors Traceback (most recent call last): File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 142, in main() File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 73, in main text_encoder = load_text_encoder( File "/home/songchaotian/sct/Apps/svdiff-pytorch/inference.py", line 45, in load_text_encoder text_encoder = load_text_encoder_for_svdiff( File "/home/songchaotian/sct/Apps/svdiff-pytorch/svdiff_pytorch/utils.py", line 137, in load_text_encoder_for_svdiff set_module_tensor_to_device(model, key, param_device, value=f.get_tensor(key), dtype=torch_dtype) File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 269, in set_module_tensor_to_device new_module = getattr(module, split) File "/home/songchaotian/.conda/envs/svdiff/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1614, in getattr raise AttributeError("'{}' object has no attribute '{}'".format( AttributeError: 'CLIPTextModel' object has no attribute 'conv_in'

Hi， I have the same error, have you solved it ?

Hi, I get the same error, did you find the solution?


Update upickle to 1.3.11

Updates com.lihaoyi:upickle from 1.3.7 to 1.3.11.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.3.7).
You might want to review and update them manually.
src/main/resources/swagger-ui/swagger-ui-bundle.js.map
src/main/resources/swagger-ui/swagger-ui.js.map

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "upickle" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #29.


now alias returning error, 'No records found for "trackover.watch"'

I'm seeing an error when trying to alias a deploy to a URL, the command I'm running is;
$ now --debug alias set GoKEW10pCKjqB0w0g9rNP6R0 trackover.watch
The error I'm seeing is,
> [debug] Checking for updates.
> [debug] Up to date (0.36.0).
> [debug] /list: 1211.326ms
> [debug] matched deployment GoKEW10pCKjqB0w0g9rNP6R0 by uid GoKEW10pCKjqB0w0g9rNP6R0
> trackover.watch is a custom domain.
> Verifying the DNS settings for trackover.watch (see https://zeit.world for help)
> [debug] #1 GET /domains/trackover.watch: 274.748ms
> [debug] #1 GET /whois-ns: 708.972ms
> [debug] Found domain trackover.watch and nameservers london.zeit.world,singapore.zeit.world,newark.zeit.world,california.zeit.world
> [debug] No records found for "trackover.watch"
> Verification OK!
> [debug] closing agent
> [debug] /now/deployments/GoKEW10pCKjqB0w0g9rNP6R0/aliases #1: 1549.240ms
> Error! Unknown error: Error: Unexpected error occurred while setting up alias: undefined
    at Alias._callee5$ (/Users/macatron/.nvm/versions/node/v6.3.1/lib/node_modules/now/build/lib/alias.js:572:23)

I've also tried adding the domain first, which seems to succeed;
$ now --debug domain add trackover.watch
> [debug] Checking for updates.
> [debug] Up to date (0.36.0).
> Verifying nameservers…
> [debug] #1 GET /whois-ns: 2231.955ms
> Verification OK!
> [debug] #1 POST /domains: 2136.073ms
> Success! Domain trackover.watch (vX6sumVIQm6tvufOGFPL03F8) added [4s]
> [debug] closing agent

But then running the initial alias command again fail with the same error, the only difference being that it no longer lists the Zeit nameservers, it returns undefined;
> [debug] Found domain trackover.watch and nameservers undefined
Any help understanding the issue would be much appreciated.
I'm using Namecheap to set the nameservers, which I've used successfully before so I'm wondering if it's something to do with the .watch TLD and how it's verified.

nameservers = undefined is "expected" behaviour as the domain is already verified. Working on the issue...

That's weird, I tried to add the alias for you and I got a very different looking log
> [debug] Checking for updates.
> [debug] Up to date (0.36.0).
> [debug] /list: 1398.995ms
> [debug] matched deployment GoKEW10pCKjqB0w0g9rNP6R0 by uid GoKEW10pCKjqB0w0g9rNP6R0
> trackover.watch is a custom domain.
> Verifying the DNS settings for trackover.watch (see https://zeit.world for help)
> [debug] #1 GET /domains/trackover.watch: 316.710ms
> [debug] Found domain trackover.watch and nameservers undefined
> [debug] No records found for "trackover.watch"
> Detected zeit.world nameservers! Configuring records.
> [debug] #1 POST /domains: 1430.541ms
> [debug] Domain already exists (noop)
> [debug] Setting up record "*" for "trackover.watch"
> [debug] /domains/trackover.watch/records #1: 1564.135ms
> [debug] #1 POST /domains: 1916.018ms
> [debug] Domain already exists (noop)
> [debug] Setting up record "" for "trackover.watch"
> [debug] /domains/trackover.watch/records #1: 1124.295ms
> DNS Configured! Verifying propagation…
> [debug] No records found for "trackover.watch"
> [debug] Retrying: Error: Please make sure that your nameservers point to zeit.world.
> Examples: (full list at https://zeit.world)
> - california.zeit.world    <IP_ADDRESS>
> - newark.zeit.world        <IP_ADDRESS>
> - london.zeit.world        <IP_ADDRESS>
> - singapore.zeit.world     <IP_ADDRESS>
> Alternatively, ensure it resolves to alias.zeit.co via CNAME / ALIAS.

For some reason it keeps repeating that last error but you can just hit Ctrl-C there, wait for some time, and finally try again. I left the DNS records for you so they will propagate, you can see the records by running now dns ls. So, please wait for some time and try again. I suppose you should be able to add an alias for www.trackover.watch immediately but usually propagating the records for trackover.watch may take some time.

Just re-ran the initial command and all is working. Hopefully this was a one off and I won't come across the issue again!


Ncrypt fixes

Fix missing prototypes
Add some WINPR_ASSERT
Add CMake option to directly link opensc-pkcs11

@hardening ok, done.


Add tint color to Alert api

This PR adds tintColor to the Alert api (only on iOS). The tintColor parameter is used to change the color of the action button's text. This PR addresses the suggestion from issue #7062
Here are a couple examples.
Alert.alert(
    'Invalid credentials',
    '',
    [
      { text: 'OK' }
    ],
    null,
    'green'
);

Alert.alert(
    'Invalid credentials',
    '',
    [
      { text: 'OK' }
    ],
    null,
    'orange'
);

Alert.alert(
      "Are you sure?",
      "Deleting this note will remove it from the server and device.",
      [
        { text: "Delete", onPress: onDeletePress, style: 'destructive' },
        { text: "Cancel" }
      ],
     null,
     'black'
)

As you can see from the image with the Delete and Cancel button, the style property for the button overrides the tintColor.
Would you guys be interested in something like this? OR if there's a better way you would like to see it implemented? Thanks!

I think you should refactor Alert's all parameters to an object because 4 parameters is way too much :O

@henrikra That's exactly what I was thinking! I think we'd have to make a different function and add a deprecation warning before we change the alert function so people's projects don't break.
Something like...
Alert.alertWithProperties({
    title: 'Invalid credentials',
    buttons: [
      { text: 'OK' }
    ],
    tintColor: 'green'
});

Good idea, thanks! However the code here is a breaking change. Where people passed a type in their apps, this will be now treated as the tintColor and fail. We should to avoid breaking changes whenever possible, otherwise we make it very difficult for people to upgrade to new versions of RN.
I agree the Alert.alert( is pretty ugly, and introducing one that accepts an object would be great. No need to introduce a new function with a different name - it is possible to do this in a backwards-compatible way and keep just one function. Check out how it's done in ScrollView.scrollTo. Would you be up for doing that for the Alert API so it's nice once and for all? :)

Sure thing, I'd love to work on it!

Can you restructure the code to have less duplication? You can simply assign title correctly before doing platform-specific behavior.
Also, can you please update the documentation to describe the new object API?
The flow type looks good but I think it should be broken out into a separate, exported type definition. You can search the codebase for export type to see examples of this.

Are you still working on this PR?

Closing due to lack of response. If you're still working on this, just let us know and we can reopen!


fix for assignment to enum variable from expression of different type

Hey!
In this pull request I fixed assignment to enum from different type. Enum should be assignment only by enum type. LRM1800-2017 6.19.4: A cast shall be required for an expression that is assigned to an enum variable where the type of the expression is not equivalent to the enumeration type of the variable.

Accepted. Merged.  Thank you.

Unfortunately this broke other tools.  I will need to revert it.  We will do another fix.

Should I reopen this pull request or create issue about this?


RPC connection error

Hello everyone when i ever i try to execute CUDA_VISIBLE_DEVICES="0" python benchmark_agent.py --suite=town2 --model-path=ckpts/image/model-10.th --show
this error shows up
world = client.get_world()
RuntimeError: rpc::rpc_error during call in function version
any help will be appreciated.

Closing because i've found the solution
1)i did pip3 uninstall carla
2) had to find a workaround to get easy_install to work and installed the provided egg
Thank you, and awesome work!

I think I maybe have the same problem but different error or can say that the client cannot get the world.
But I tried the
uninstall and install provided egg ... still cannot work.

I think I maybe have the same problem but different error or can say that the client cannot get the world.
But I tried the
uninstall and install provided egg ... still cannot work.

OK I finally got the way, you cannot run the benchmark_agent first, when I run other file like data_collection.py it's okay. Just for other people who may meet this question.


cannot add better_enum values to unordered_set

https://godbolt.org/z/ns3Kb3
#include <unordered_set>
#include <unordered_map>
#include <https://raw.githubusercontent.com/aantron/better-enums/master/enum.h>

enum Foo : int {
    foo = 1,
    bar = 2,
};

std::unordered_set<Foo> foos{
    Foo::foo,
    Foo::bar
};

BETTER_ENUM(Bar, int,
    foo = 1,
    bar = 2
)
BETTER_ENUMS_DECLARE_STD_HASH(Bar)

std::unordered_set<Bar, int> bar_set{
    Bar::foo,
    Bar::bar,
};

/opt/compiler-explorer/gcc-10.2.0/include/c++/10.2.0/bits/hashtable_policy.h:1377:16: error: static assertion failed: hash function must be invocable with an argument of key type
 1377 |  static_assert(__is_invocable<const _H1&, const _Key&>{},
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/compiler-explorer/gcc-10.2.0/include/c++/10.2.0/bits/hashtable_policy.h:1379:16: error: expression cannot be used as a function
 1379 |  return _M_h1()(__k);
      |         ~~~~~~~^~~~~

etc...

I'm not able to look in detail for a while. Can you comment on whether this should be working (at a technical level), in light of https://github.com/aantron/better-enums/pull/77?

ah, i have defined BETTER_ENUMS_DECLARE_STD_HASH (and updated the issue above).

ugh. actually i had a typo. looks like it works fine once i RTFM, thanks!


[intern] Initialized WPF app

Used Visual Studio C# WPF app
Used helper MVVM classes from WindowWalker (INotifyPropertyChanged and ICommand wrappers)
Rough implementation is done in /interns/users/t-arsumi/dev-animated-gif/encoder and is feasible to merge by today

Reason for tech stack change:

Able to use ScreenToGif backend (no yellow border using Windows.Graphics.Capture)
Able to support ScreenToGif in the future (multi monitor support)
Transparent overlay in each display

Thank you!


TeamAssigner.py not connecting to MySQL (PromiseConnection error)

Describe the bug
TeamAssigner.py throws errors when connecting to MySQL to write to the Requirements table.
To Reproduce
Steps to reproduce the behavior:

Go to mock_data
run: node --trace-warnings mock_data.js 10 3

Expected behavior
Should create mock data filling all tables with 10 members and 3 projects.
Additional context
Blocking work for setting up the algorithm.

Solved.


fix: add support for solnlib v5.x.x

support for solnlib library which was recently released with version v5.0.0
fix ci:
*removed cache poetry
*removed pipx installer
*change step order - actions/setup-python@v5 before installing poetry

:tada: This PR is included in version 6.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add GOBL::validate operation

[Waiting for #16 to get merged. Will rebase and make it a non-draft when that happens]

This PRs adds the validate operation to the library, bringing the ability to validate GOBL documents and envelops to Ruby developers
It follows the general approach described in "RFC: GOBL Operations from Ruby".
It is based on the work done on #16

Superseded by #17


[Snyk] Security upgrade org.codehaus.jettison:jettison from 1.1 to 1.5.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-reporting-task/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

611/1000  Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS) SNYK-JAVA-ORGCODEHAUSJETTISON-3037311
org.codehaus.jettison:jettison:  1.1 -> 1.5.1
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Approved to merge


Best gear in bags

Similar to raidbots for retail, it would be extremely useful for average users to be able to import all the gear in their bags and preferably their bank and sim all those items at once to see what set is currently their best. This feature is especially useful because of the flood of items we get early on when gearing a character and we are not always in BiS. Takes the guess work out of these situations and a lot of people like myself would be willing to pay a sub for this feature.

#1512 this is half supported through addon and 'experimental' setting


second HACS system won't load (on same token at first, neither on new token)

Version of HACS

0.9
Describe the bug
A clear and concise description of what the bug is.
not sure if a bug or user error, but since I couldn't find clues in the docs for setting up HACS on more than 1 system, files here for the time being
Debug log

Add your logs here.

please see https://community.home-assistant.io/t/custom-component-hacs/121727/178?u=mariusthvdb
bottom line:
I installed HACS  on a second system and it wont load anything, even after a few hours. My first HACS install which had loaded most of the plugins got scrambled after that, and only the install of the custom repositories where left.
Could this be cause by me using the same token....?
Ive created a second token, for the second system. After that, Ive reinstated all plugins on the first system, but the second system still wont do anything.

Enable debug logging, then restart, then paste the log here.

there's no log, other then timeouts, and nothing in the HACS panel at all, so no log either.
After enabling the HACS on my second system again, to do as you asked, and post a log, yet again all my plugins were gone on the first system....as are all integrations ....
sorry to say but this is a bit to dangerous for me to be experimenting with setups... hope you enough info to try in your development setting.
Just try a secondary install on another machine, and see what happens.
Sorry if I can't be of more help.

I have this running on 4 setups without any issue.
Without the (homeassistant) log from your setup, there is nothing I can do.
When your situation changes and you can provide the information needed to debug this feel free to open another issue,

ok but let me ask, do we need a token per setup?

You should have that, but not needed, that is just for authentication.


Images broken on recent Grafeas post

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
Images on http://blog.kubernetes.io/2017/11/securing-software-supply-chain-grafeas.html are broken. It looks like they are referencing private Google docs files.
Proposed Solution:
Make the Google docs files public or copy the images somewhere else.
Page to Update:
http://blog.kubernetes.io/2017/11/securing-software-supply-chain-grafeas.html

cc @kelseyhightower

This is now resolved.

Thanks @kbarnard10!


Improve Dropdown: Make searchable

Imagine a list of countries as values inside of a dropdown selection.
Make it possible that users type with keyboard to search/filter the values so we have nice UX

fixed by https://github.com/web3ui/web3uikit/pull/238


Should rule severity be configurable  ?

I'd like to start the discussion about having an option of adjusting rule severity. I am not sure how PSSA community decides rule severity while onboarding any new rules. But I personally think it would be nice if I am given an option to upgrade some of the rules to Error or vice-versa.
For example, I would really like to upgrade PSAvoidGlobalVars, PSAvoidUsingWriteHost, PSAvoidUsingPlainTextForPassword rules severity to Error within my organization. This would not be the case for everyone. Similarly, I would like to change some of them to Information.
Let me know if this was something discussed and ignored for any reason.

How do you use Severity and what is the impact of them having different values?
I think it's just meant to be an easy way of grouping/filtering rules and severity is usually determined by the impact that a violation might have. With the returned results from Invoke-ScriptAnalyzer you can just filter out the diagnostic records of rule that you are interested in and then do a custom action like e.g. failing CI or only adding a warning message.

Thanks @jegannathanmaniganadan for opening this issue, this is something we want to consider as we re-vamp the configuration options for PSSA 2.0 (our next major version). As @bergmeister mentioned it would still be great to know how you use the severity warnings in your work flow?

@SydneyhSmith I am glad to hear that. My reasons are almost covered by @bergmeister .

The only difference to the user is that VS-Code marks the squiggly as red instead of yellow when it is of type Error as far as I know.

This is not much I am concerned about. Given that the PSSA (with custom rules too) & VSCode performance is not great, I usually turn off PSSA in VScode.

you can just filter out the diagnostic records of rule that you are interested in and then do a custom action like e.g. failing CI or only adding a warning message.

CI is where I am trying to make difference. Grouping based on Severity will be useful and it will also add more meaning to the rule Severity. It is easy to say catch all Violations with Error  than array of values using Include/Exclude rule feature

@jegannathanmaniganadan

CI is where I am trying to make difference. Grouping based on Severity will be useful and it will also add more meaning to the rule Severity. It is easy to say catch all Violations with Error than array of values using Include/Exclude rule feature

PSSA already has the -Severity parameter so that it only runs rules of one or more certain severity levels. Changing the severity of rules to create your custom list of rules you are interested in does not sound right to me as you'd rather want to use the -IncludeRule and/or -ExcludeRule directly, where I do not see advantages/disadvantages. If you want to avoid maintaining a big list of rules to include, then I suggest you to use Get-ScriptAnalyzerRule, which also has a -Severity parameter, this way you could easily create your rule set for -IncludeRule:
((Get-ScriptAnalyzerRule -Severity Error) + (Get-ScriptAnalyzerRule -Name PSAvoidUsingCmdletAliases)).RuleName

Also: you can pipe the results of Invoke-ScriptAnalyzer to Where-Object to include exclude certain violations and PowerShell was explicitly designed for this so that every cmdlet doesn't have to re-invent the wheel around filtering of results.

We have a tool that runs PSScriptAnalyzer as part of our Pull Request process. It will not let anything be checked in that has any Errors or Warnings.
Recently, we started seeing a lot of PSUseSingularNouns. In some cases this is intentional. For example: Send-MessageToTeams (As in Microsoft Teams)
Ideally, we would like to disable the rule for just these cases, but #849 isn't available yet.
In the meantime, we would like to change the rule from Warning to Info so that our devs know about it, but aren't blocked when using it appropriately.

I'd like to be able to change severity from Error to Warning for PSAvoidUsingConvertToSecureStringWithPlainText, because Microsoft tooling sometimes forces me to ConvertTo-SecureString -AsPlainText:

https://github.com/Azure/azure-powershell/issues/24190

I'd be better to have a warning for this than disabling the rule all together.

Did this idea ever get implemented?


settings: Make show more tab look similar to other tabs.

Fixes https://chat.zulip.org/#narrow/stream/101-design/topic/org.20settings.20-.20show.20more.20-.20icon.20alignment/near/1935512

Before
After

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @shubham-padia!


containerd: failed to setup network for sandbox [uuid] error getting ClusterInformation: Get https://[<IP_ADDRESS>]:443/apis/crd.projectcalico.org/v1/clusterinformations/default: Service Unavailable

Can't start any workload on node with containerd
Current Behavior
 k get pods --all-namespaces  -o wide | grep worker06                                                                                (k8s-test/kube-system)
fluentd-operator            es-cluster-1                                               0/1     Init:0/3            0          31m     <none>            abp-kube-test-worker06.pv.mts.ru   <none>           <none>
fluentd-operator            es-cluster-system-1                                        0/1     Init:0/3            0          31m     <none>            abp-kube-test-worker06.pv.mts.ru   <none>           <none>
fluentd-operator            kfo-log-router-zq4kx                                       0/2     ContainerCreating   3          2d6h    <none>            abp-kube-test-worker06.pv.mts.ru   <none>           <none>
kube-system                 calico-node-2vvbd                                          1/1     Running             2          60d     <IP_ADDRESS>      abp-kube-test-worker06.pv.mts.ru   <none>           <none>
kube-system                 kube-proxy-5lqwf                                           1/1     Running             1          8h      <IP_ADDRESS>      abp-kube-test-worker06.pv.mts.ru   <none>           <none>
metallb-system              metallb-speaker-zh98l                                      1/1     Running             2          35d     <IP_ADDRESS>      abp-kube-test-worker06.pv.mts.ru   <none>           <none>
monitoring                  prometheus-node-exporter-xgp5n                             1/1     Running             1          44h     <IP_ADDRESS>      abp-kube-test-worker06.pv.mts.ru   <none>           <none>
monitoring                  prometheus-prometheus-op-prometheus-0                      0/3     ContainerCreating   0          31m     <none>            abp-kube-test-worker06.pv.mts.ru   <none>           <none>
popeye                      popeye-1571245260-kn8bc                                    0/1     ContainerCreating   0          17m     <none>            abp-kube-test-worker06.pv.mts.ru   <none>           <none>

Oct 16 20:15:56 abp-kube-test-worker06 containerd: time="2019-10-16T20:15:56.292386672+03:00" level=info msg="ExecSync for "6e66938190df4596153e197cabb58f798ae77df9878d4a3abc2a68c173465c0b" with command [/bin/calico-node -bird-ready -felix-ready] and timeout 1 (s)"
Oct 16 20:15:56 abp-kube-test-worker06 containerd: time="2019-10-16T20:15:56.362107336+03:00" level=info msg="Finish piping "stdout" of container exec "511495892d1ec36ed6ef560bf598b2729d3d438b1b60bd75cb0a8241fe5b9555""
Oct 16 20:15:56 abp-kube-test-worker06 containerd: time="2019-10-16T20:15:56.362174100+03:00" level=info msg="Finish piping "stderr" of container exec "511495892d1ec36ed6ef560bf598b2729d3d438b1b60bd75cb0a8241fe5b9555""
Oct 16 20:15:56 abp-kube-test-worker06 containerd: time="2019-10-16T20:15:56.363230951+03:00" level=info msg="Exec process "511495892d1ec36ed6ef560bf598b2729d3d438b1b60bd75cb0a8241fe5b9555" exits with exit code 0 and error <nil>"

Oct 16 20:19:41 abp-kube-test-worker06 containerd: 2019-10-16 20:19:41.153 [INFO][30189] plugin.go 75: Extracted identifiers EndpointIDs=&utils.WEPIdentifiers{Namespace:"monitoring", WEPName:"", WorkloadEndpointIdentifiers:names.WorkloadEndpointIdentifiers{Node:"abp-kube-test-worker06.pv.mts.ru", Orchestrator:"k8s", Endpoint:"eth0", Workload:"", Pod:"prometheus-prometheus-op-prometheus-0", ContainerID:"762409e32b6d5af63983ff48ad1c7fe04ec2209ec4101aafbc089c3491580e4d"}}
Oct 16 20:20:56 abp-kube-test-worker06 kubelet: E1016 20:20:56.293212   13366 pod_workers.go:190] Error syncing pod d0f60502-49fc-4fae-9f5c-7eff86310874 ("prometheus-prometheus-op-prometheus-0_monitoring(d0f60502-49fc-4fae-9f5c-7eff86310874)"), skipping: failed to "CreatePodSandbox" for "prometheus-prometheus-op-prometheus-0_monitoring(d0f60502-49fc-4fae-9f5c-7eff86310874)" with CreatePodSandboxError: "CreatePodSandbox for pod \"prometheus-prometheus-op-prometheus-0_monitoring(d0f60502-49fc-4fae-9f5c-7eff86310874)\" failed: rpc error: code = Unknown desc = failed to setup network for sandbox \"762409e32b6d5af63983ff48ad1c7fe04ec2209ec4101aafbc089c3491580e4d\": error getting ClusterInformation: Get https://[<IP_ADDRESS>]:443/apis/crd.projectcalico.org/v1/clusterinformations/default: Service Unavailable"

other five workers works fine.
and when i change containerd to docker - all works fina
Steps to Reproduce (for bugs)

create new cluster
use containerd as cri

Your Environment

Calico version: v3.7.3
kubernetes: v1.15.1
Operating System and version: CentOS 7
cri (containerd):  1.2.4
kube-proxy mode: ipvs

Just run into this issue today.
I set HTTPS_PROXY environment to the containerd daemon and caused this issue.
My use case is to set up kubernetes node with containerd CRI. My machines are behind firewalls so I have to add http proxy for containerd, and it seems that this proxy settings is propagated down to some process calling https://[<IP_ADDRESS>]:443/apis/crd.projectcalico.org/ API.
Finally I add NO_PROXY to all private subnet (e.g. <IP_ADDRESS>/8) and fix this issue.
By specification the NO_PROXY environment variable doesn't support CIDR, but golang does explicitly support it, see https://github.com/golang/go/issues/16704.
Don't know if this is related to your issue, just share my experience here.

@nia1048596 thanks for your input
@lelvisl what is the status of the calico-node pod? From the timeout logs you shared I'm guessing probably not. Is there anything interesting in the logs?
Can you verify that from a node that https://[<IP_ADDRESS>]:443 is reachable?

It might not be relevant to the underlying problem here, but fwiw I don't think https://[<IP_ADDRESS>]:443 is a valid URL.  I think the [...] quotes are only defined for IPv6 literals.

@nia1048596  agree with you!

@nia1048596  agree with you!

The issue happened when you are using contained and kubelet under proxy so please use @nia1048596's solution.

@nia1048596
master or workers nodes?

@itsecforu Well I guess it depends. I encountered this very issue on my bare metal K8s (CRIO+Calico) cluster for some pods which couldn't run on my worker nodes (you can check the node they should run on with kubectl get nodes -o wide). Adding my Calico Subnet (<IP_ADDRESS>/18) to my NO_PROXY environment variable (with systemctl edit crio) on each worker nodes did the trick for me (don't forget to systemctl daemon-reload and systemctl restart crio afterwards though).
However, if I the same problem ever were to happen on one of the pods of my control plane, I'll add it to the masters then.


[Bug] -

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Olá @Teresa5519
Teve algum problema que queria reportar?
Hello @Teresa5519
There is a bug that you want to report?


Add a taint to the node before draining.

This makes it possible to detect that the pods are killed due to spot termination for example. Without tainting the node, you have no way of knowing why a job/pod was killed.
We use this information to enrich our error messages shown to the user.

@nclaeys thanks for contributing. I appreciate this. I just want to know what exactly this change can help you. Taint nodes with TaintEffectNoSchedule will have no effect on pods that already run on this node. How can this taint help you to identify pod termination reasons?

Hi Maksim,
I want to thank you providing the node-termination-handler, it looks very good and from initial testing, does a great job. It was one piece we were still missing in Azure vs our AWS offering.
Well our platform basically monitors batch jobs. We have kubernetes operators to manage them. If a node gets preemted and all the pods get drained, they will receive a sigterm and some of them will fail because of this. We want to show to users, the exact reason why the jobs failed. We do this in our operator by mapping different failure states of our pods/containers to a more human friendly error (translating mounting errors, iam errors, pod pending,...). As part of this we lookup information of the node, and if it has been tainted with preemtion, we know that that is why the job was killed.
It is important to give users this information, since it allows them to decide whether the workloads can run on spot (cheaper) but sometimes they may fail due to preemption. If that is too big an issue, they can run their jobs only on on-demand nodes.
So actually the most important thing is the node being annotated with a specific key, not the effect of the taint. It helps to distinguish node drains due to upgrading a kubernetes version for example from preemption of spot nodes...
I hope this gives you some more insight, if you have any more questions just shoot.

Thanks for the details. Sounds great. In your case this information can be stored as part of node annotation, but node taint also will be a great option.
Niels, what about adding new configuration flags -taint-node=false and -taint-effect=NoSchedule - that will handle adding taints and taint effect before node draining?

It makes sense to add taint-node parameter and indeed. I could add the taint-effect, but to me this looks less useful, any specific reason why you want people to specify that? Right after the taint you will cordon and drain all the pods anyway so the job will be killed anyway.

It will be great to have customizable taint-effect - it will allow for some users terminate also DaemonSets with NoExecute  taint effect. For default it will be NoSchedule

Alright fine, I will update the PR to add both. Thanks for the feedback!

@nclaeys great job! Thanks for contributing. Your changes released https://github.com/maksim-paskal/aks-node-termination-handler/releases/tag/v1.0.0