[ko] Minor Fix in Korean docs fixed : Fix 02

Fix: #34909
The 2nd suggestion has been applied.

Is it intended to touch 6 languages in one PR?
Feel free to /unhold once the git issue is solved.
/hold

How do I push only single committ of mine to dev -1.24 branch then?
On Sat, 16 Jul, 2022, 8:44 am Sean, @.***> wrote:

Is it intended to touch 6 languages in one PR?
Feel free to /unhold once the git issue is solved.
/hold
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/35062#issuecomment-1186076391,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUQQSLR5UBJSJ5D5OLH4JDDVUISKZANCNFSM53WK7G4Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

@NitishKumar06 for help with using Git, you could ask in the #sig-docs channel on Slack, or to https://softwareengineering.stackexchange.com/

Hi @NitishKumar06
Please take a look on my previous comment regarding the base branch.
https://github.com/kubernetes/website/pull/34932#issuecomment-1184814596
And please use (retitle) understandable title for a PR :)
You can change the title by using /retitle [ko]xxxxx command. ([language code] is a convention for a localization PR)

@seokho-son I think that's what I've done:
First of all, I made changes to a new branch I just created. Ater that, I pushed the changes and in the Github UI , I changed the base branch to dev-1.24 instead of main. Anything wrong in it?

/retitle Minor Fix in Korean docs fixed : Fix 02

/retitle [ko] Minor Fix in Korean docs fixed : Fix 02

First of all, I made changes to a new branch I just created. Ater that, I pushed the changes and in the Github UI , I changed the base branch to dev-1.24 instead of main. Anything wrong in it?

In order to work in a different branch other than main branch (like this PR),
When you create your new (local) development branch, the base of the new branch should be dev-1.24-ko.2.
It seems .. current base of your development branch NitishKumar06:Nitish/Korean is main branch which is a wrong base branch for this PR.
(following commands are just example to checkout to a different branch other than main branch)

git fetch upstream
git checkout upstream/dev-1.24-ko.2
git checkout -b yourlocaldev

(If this comment is hard to understand for you, I also recommend you to check Git related contents suggested by above comments.)

@seokho-son Correct me if I'm wrong:
First of all I'll have to checkout the dev-1.24 branch using git checkout dev-1.24 and from that branch I'll have to create a new branch whichever I want. After committing the changes, I'll have to push the changes using the command git push origin  . Once done I'll have to change the base branch in the Github UI to dev-1.24, right?

I'm closing this PR since the following PR resolves this issue:https://github.com/kubernetes/website/pull/35248

/remove-area blog release-eng
/remove-language de en es fr id it ja pt vi zh
/remove-sig release


[Feature Request] Similar to TachiJ2K ability to remove manga from library as well as tracking service

Why/User Benefit/User Problem
Reduces so much steps if done from within the app
What/Requirements
Just a popup like J2K asking to remove from tracking service as well

Any plan for this as this is the only deal breaker for me. Sorry for being irritating.

Im personally not interested in this as I dont use trackers, if someone wants to implement it go ahead


toLocaleString is only working on ios not android.

toLocaleString is only working on ios and not android.
When will this be supported?

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

Dude, there's no missing information. toLocaleString() is a Javascript number formatting string method that just doesn't work at all on android. Please fix this

Hi all, I am also facing the same issue in Android although it is working fine in iOS.

I've noticed, that .toLocaleString does weirdly only work in JS Debug Mode on Android

Any update?

I'm using version 0.47.1 of react-native.  Using number.toLocaleString('fa') works perfectly in iOS but not in android.

Hi all, I am also experiencing this issue on android although it works fine in IOS.

I have the same issue. Works fine on iOS but not Android. On Android Expo will crash when I try to call it

This should be re-opened @hramos , this is a real bug.

Same here, work fine on iOS and only in debug-mode on Android. Any workaround for the meantime?

@tzig You can try using react-native-globalize if yiu don't mind using an extra library in your app.

This issue was so terribly closed, such an easy to see bug and they still want us to create templates to show that a simple JS function wont work on a specific OS.... terrible.
I'm on react native 0.50.3 and I got the same issue

There is an other open issue for this bug with their prefered template: https://github.com/facebook/react-native/issues/16867. Hope they don't close it.

@abhandaru I've been using https://github.com/smirzaei/currency-formatter for currencies, which works well on iOS and Android.

I had the same problem on Android; using toLocaleDateString() instead seems to work. Since I only was interested in the date part and not the time part, that was enough for me. I would assume, though, that for complete date and time results a combination of toLocaleDateString() and toLocaleTimeString() would work

This is an issue still, with numbers:
https://imgur.com/xCLWo16
They are formatting correctly in iOS, not in Android.

@ferdicus this is likely due to the JavaScript engine being used. Normally RN will use JavaScriptCore. However while debugging under chrome debugging, it has to use V8. Though I thought JavaScriptCore supported this feature. So there must be more to this puzzle.
This issue being closed looks silly. Is this resolved in RN 0.55.3?

Work around solution is:
number.toString().replace(/\B(?=(\d{3})+(?!\d))/g, ",")

☝ I opened a new issue for this and sacrificed a small goat to the template gods 😬

In my way that solve this problem was this, I hope to help:
var today = new Date();                  var dd = today.getDate();                  var mm = today.getMonth()+1; //January is 0!                 var yyyy = today.getFullYear();                 if(dd<10)                         {dd='0'+dd}                  if(mm<10)                         {mm='0'+mm}                  var today = dd+'/'+mm+'/'+yyyy;                 console.log(today)                 console.log('aqui')                 return today; // dd/mm/yyyy

It's a real shame, to those who are using toLocaleString() method for Currency you can use this code for now:
`
_getPriceValue() {
if (Platform.OS === 'ios')

  return (+this.props.number).toLocaleString(fa ? 'fa-IR' : 'en-US', {maximumFractionDigits: 0});

else

  return (+this.props.number).toString().replace(/\B(?=(\d{3})+(?!\d))/g, ",");

}
`

Shameful.

Here is the workaround I use. toLocaleTimeString() returns military time, so it is easy enough to convert from there.
    formatStandardTime = date => {
        let time = date.toLocaleTimeString();
        time = time.split(':'); // convert to array

        // fetch
        var hours = Number(time[0]);
        var minutes = Number(time[1]);
        var seconds = Number(time[2]);

        // calculate
        var timeValue;

        if (hours > 0 && hours <= 12) {
        timeValue= "" + hours;
        } else if (hours > 12) {
        timeValue= "" + (hours - 12);
        } else if (hours == 0) {
        timeValue= "12";
        }

        timeValue += (minutes < 10) ? ":0" + minutes : ":" + minutes;  // get minutes
        timeValue += (seconds < 10) ? ":0" + seconds : ":" + seconds;  // get seconds
        timeValue += (hours >= 12) ? " P.M." : " A.M.";  // get AM/PM
        return timeValue
    }

stack overflow code source

Still having this.

Still face with this problem. it's only work in debug mode

Guys it's clear it still exists! cause there is no new release and also no one is taking care of this thread :|

The root cause here is the outdated JSC runtime that React Native Android ships with.
It isn't something that can be easily patched; so there isn't going to be a PR specifically for this -- but there is a wider discussion around migrating to either a newer JSC version or allowing users to bundle any arbitrary JSC here.
If and when the JSC ever gets updated, this should work as expected on both platforms. But until then, you have two options.

polyfill it yourself

(the hardcore route) use the JSC buildscripts repo to compile a newer version and bundle it into your app.

⚠ The JSC is a fairly core piece of the Android architecture though; so proceed at your own risk

Unless you fully understand the implications of replacing it with your own version, I'd recommend sticking to option 1.

still not fixed, hehe, niiiiiiice


Reformat configuration of deployerConfigContext

Re-arranges the deployerConfigContext, fixes formatting issues and gives a number of beans explicit ids, so that sub modules can manipulate them automatically when needed.

I found the comments pretty useful...

I can restore them, but I was thinking that our canonical source for guidance and docs should be the documentation. Otherwise, it just increases maintenance burden. For example, if you want to know what an authentication policy is, you really should be consulting the CAS docs. Comments in the config, I think, should only be reserved for technical implementation issues and. What do you think?

You're right. Maintaining the documentation in two places is a bad idea.
+1


read_loom failed

Hi,
I use scanpy 1.3.1. I have tried the 'read_loom' function, but it produced the following error:

adata = sc.read(filename=path_to_velocyto_files + 'all_controls.loom')

--> This might be very slow. Consider passing `cache=True`, which enables much faster reading from a cache file.
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-52-61a36c9ba297> in <module>()
----> 1 adata = sc.read(filename=path_to_velocyto_files + 'all_controls.loom')

~/anaconda3/lib/python3.6/site-packages/scanpy/readwrite.py in read(filename, backed, sheet, ext, delimiter, first_column_names, backup_url, cache, **kwargs)
     73         return _read(filename, backed=backed, sheet=sheet, ext=ext,
     74                      delimiter=delimiter, first_column_names=first_column_names,
---> 75                      backup_url=backup_url, cache=cache, **kwargs)
     76     # generate filename and read to dict
     77     filekey = filename

~/anaconda3/lib/python3.6/site-packages/scanpy/readwrite.py in _read(filename, backed, sheet, ext, delimiter, first_column_names, backup_url, cache, suppress_cache_warning, **kwargs)
    311             adata = _read_softgz(filename)
    312         elif ext == 'loom':
--> 313             adata = read_loom(filename=filename, **kwargs)
    314         else:
    315             raise ValueError('Unkown extension {}.'.format(ext))

~/anaconda3/lib/python3.6/site-packages/anndata/readwrite/read.py in read_loom(filename, sparse, cleanup, X_name, obs_names, var_names)
    144     filename = fspath(filename)  # allow passing pathlib.Path objects
    145     from loompy import connect
--> 146     with connect(filename, 'r') as lc:
    147
    148         if X_name not in lc.layers.keys(): X_name = ''

AttributeError: __enter__

I have found that when I try to read the file the interactive console, I have the following result:
> filename =os.fspath(path_to_velocyto_files + 'all_controls.loom')
> lc =connect(filename, 'r')
> lc.layer.keys()
dict_keys(['', 'ambiguous', 'spliced', 'unspliced'])

So for my loom file, it's not 'layers', but 'layer'. Can you consider to include this case in the anndata read function?

connect returns a LoomConnection object. __enter__ was added to LoomConnection in linnarsson-lab/loompy@aaafe0cc1694904adb3a15f11edc97a9dd6cc92a
Looks like you have an ancient loompy version <1.1.0, is that correct?

Yes!

Great!

Ok, updated to loompy 2.0.12:

adata = sc.read_loom(filename=path_to_velocyto_files + 'all_controls.loom')

Variable names are not unique. To make them unique, call `.var_names_make_unique`.
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-8-de63a2957df4> in <module>()
----> 1 adata = sc.read_loom(filename=path_to_velocyto_files + 'all_controls.loom')

~/anaconda3/lib/python3.6/site-packages/anndata/readwrite/read.py in read_loom(filename, sparse, cleanup, X_name, obs_names, var_names)
    172             obs=obs,  # not ideal: make the generator a dict...
    173             var=var,
--> 174             layers=layers)
    175     return adata
    176

~/anaconda3/lib/python3.6/site-packages/anndata/base.py in __init__(self, X, obs, var, uns, obsm, varm, layers, raw, dtype, shape, filename, filemode, asview, oidx, vidx)
    681                 layers=layers,
    682                 dtype=dtype, shape=shape,
--> 683                 filename=filename, filemode=filemode)
    684
    685     def _init_as_view(self, adata_ref: 'AnnData', oidx: Index, vidx: Index):

~/anaconda3/lib/python3.6/site-packages/anndata/base.py in _init_as_actual(self, X, obs, var, uns, obsm, varm, raw, layers, dtype, shape, filename, filemode)
    901         self._clean_up_old_format(uns)
    902
--> 903         self._layers = AnnDataLayers(self, layers, dtype)
    904
    905     def __sizeof__(self):

~/anaconda3/lib/python3.6/site-packages/anndata/layers.py in __init__(self, adata, layers, dtype, adata_ref, oidx, vidx)
     31                     raise ValueError('Shape does not fit.')
     32                 if layers[key].dtype != np.dtype(dtype):
---> 33                     self._layers[key] = layers[key].astype(dtype, copy=False)
     34                 else:
     35                     self._layers[key] = layers[key]

TypeError: astype() got an unexpected keyword argument 'copy'

Can you try the newest anndata from git?
pip install -U git+https://github.com/theislab/anndata.git

It should give you a better error message

OK. I test if layer is a np.ndarray (which has .astype with copy) or a scipy.sparse.spmatrix (which also has .astype with copy)
for the sparse matrices, this was added in scipy/scipy@d09dc32a4d1444ccabda4d353a6008c4b6756f07, which ended up in scipy 1.0, released almost a year ago. do you also have an old scipy version?

OK, my scipy version is 0.19.1.

Hi, I am facing a similar issue too.
When I processed my spliced and unspliced using Velocyto and loaded those loom files, it worked. But when
I converted my seurat to loom and I tried loading it into velocyto but received the following error:
>>> ls003 = scv.read_loom('/home/praghu/yojetsharma/new/loom_files/ls003/ls003.loom')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/anndata/compat/__init__.py", line 305, in inner_f
    return f(*args, **kwargs)
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/anndata/_io/read.py", line 251, in read_loom
    with connect(filename, "r", **kwargs) as lc:
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/loompy/loompy.py", line 1515, in connect
    return LoomConnection(filename, mode, validate=validate)
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/loompy/loompy.py", line 85, in __init__
    if not lv.validate(filename):
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/loompy/loom_validator.py", line 50, in validate
    self.version = get_loom_spec_version(f)
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/loompy/utils.py", line 19, in get_loom_spec_version
    if "attrs" in f and "LOOM_SPEC_VERSION" in f["/attrs"]:
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "/home/praghu/yojetsharma/.conda/envs/yojet_velo/lib/python3.10/site-packages/h5py/_hl/group.py", line 483, in __contains__
    return self._e(name) in self.id
  File "h5py/h5g.pyx", line 466, in h5py.h5g.GroupID.__contains__
  File "h5py/h5g.pyx", line 467, in h5py.h5g.GroupID.__contains__
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5g.pyx", line 540, in h5py.h5g._path_valid
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5l.pyx", line 212, in h5py.h5l.LinkProxy.exists
RuntimeError: Unable to get link info (addr overflow, addr = 12416, size = 176, eoa = 2048)


chore: release 1.0.0

:robot: I have created a release *beep* *boop*
1.0.0 (2019-05-13)
Bug Fixes

deps: update dependency google-gax to v1 (#376) (14a5ca9)
DEADLINE_EXCEEDED is idempotent (#377) (d7ed2d3)
deps: update dependency @google-cloud/promisify to v1 (#367) (f1a5bcc)
deps: update dependency google-gax to ^0.26.0 (#362) (81a3379)
include 'x-goog-request-params' header in requests (4e7a1c6), closes #353
samples: make test assertion less specific (#354) (435ddf0)

Build System

upgrade engines field to >=8.10.0 (#363) (e8a7141)

Features

image annotation batching (#375) (bed2515)

BREAKING CHANGES

upgrade engines field to >=8.10.0 (#363)

Release is at https://github.com/googleapis/nodejs-vision/releases/tag/v1.0.0

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Rails 8 Issue?

Converting from rails 7.2.2 to 8.0.0 and getting this:
/Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/acts_as_paranoid-0.3.1/lib/acts_as_paranoid.rb:42:in alias_method': undefined method validate_find_options' for class `#Class:ActiveRecord::Base' (NameError)
        alias_method :validate_find_options_without_deleted, :validate_find_options
        ^^^^^^^^^^^^
from /Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/acts_as_paranoid-0.3.1/lib/acts_as_paranoid.rb:42:in `singleton class'
from /Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/acts_as_paranoid-0.3.1/lib/acts_as_paranoid.rb:41:in `included'
from /Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/acts_as_paranoid-0.3.1/lib/acts_as_paranoid.rb:166:in `include'
from /Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/acts_as_paranoid-0.3.1/lib/acts_as_paranoid.rb:166:in `<main>'
from /Users/fmorton/.rbenv/versions/3.2.5/lib/ruby/gems/3.2.0/gems/zeitwerk-2.7.1/lib/zeitwerk/core_ext/kernel.rb:34:in `require'

Hi @fmorton this is the same problem is #342. Please add "~> 0.10.2" to your acts_as_paranoid dependency to avoid Bundler picking an ancient version. Rails 8 support is coming soon!

I will be happy to try it out when you are ready. Here is what I get now with a "bundle update":
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...
Could not find compatible versions
Because acts_as_paranoid >= 0.10.2 depends on activesupport >= 6.1, < 8
and rails >= 8.0.0 depends on activesupport = 8.0.0,
acts_as_paranoid >= 0.10.2 is incompatible with rails >= 8.0.0.
So, because Gemfile depends on rails ~> 8.0.0
and Gemfile depends on acts_as_paranoid ~> 0.10.2,
version solving has failed.
Thanks for your work on this. It is a great gem.

I also am getting the same message, I'm considering changing to other gem.

@cancelei as I mentioned to @fmorton, please try pinning acts_as_paranoid's version to "~> 0.10.2", and use Rails 7. Without pinning the version, Bundler will pick a very old version if you try to use acts_as_paranoid with Rails 8.
You're welcome to use another gem if that suits your needs better.

Version 0.10.3 supporting Rails 8.0 has now been released.

Thanks for adding the Rails 8 support and appreciate all your work on this gem.


Application Insights reference

Recommend changing this section: "Both Azure Monitor and Azure Application Insights assist with maximizing the availability and performance of your applications and services"
The reference to Application Insights leads to confusion.  Since OSM does not support integrating to Application Insights, is the intention for a user to implement Application Insights at the code-level and also implement OSM at the cluster? Typically tracing is also a mesh feature, but it's unclear how to provide that capability using only Azure native offerings.

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

ID: 58d8dc53-d684-35bb-9953-4719c790f70e
Version Independent ID: daace182-67a7-31e4-380f-6ac259eced3e
Content: Configure Monitoring and Observability with Open Service Mesh on Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/open-service-mesh-azure-monitor.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: pgibson

@jpocloud  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign:schaffererin

Hi @jpocloud - thank you for your feedback. I apologize for the delay in responding. The doc has since been updated and no longer references Application Insights. I will now close this issue. Thank you again!
#please-close


bootstrap baremetal host management IP addresses

It was pointed out on slack that this ticket is perhaps ambiguous. I was thinking this ticket was more of a OSP/metal3 IP task.
We do need to configure IP addresses for OCP workers too however so perhaps that could be a separate task/issue. Also worth considering if we might align the two as there is value in tooling similarities.


Environment files documentation and changes

I'll log here changes I've made, as I make them.

data-registry.env

Change ENVIRONMENT=production (was development)
Remove DEBUG=on

dqv.env (pelican-frontend)

Remove DEBUG=yes
There is no django schema, so I removed it from DEFAULT_DB_SEARCH_PATH=django,public

Fixed SENTRY_DNS -> SENTRY_DSN typo (and in repos). It stands for Data Source Name.

Okay, my questions:

When should a developer change the STATIC_VERSION environment variable? #
What does ENVIRONMENT control?
https://github.com/open-contracting/pelican-backend/issues/27

STATIC_VERSION has no effect, because the Dockerfile overwrites it in settings.py to a date, instead of reading from the environment.

For a current build, STATIS_VERSION has no effect. However - this can change for other deployment scenarios.

Re-opening and reassigning because I actually have to do something with this info.

@jakubkrafka You said you would look into the ENVIRONMENT variable. As far as I can tell, the code doesn't use it.
Please re-assign to me after answering.

Can be removed from the .env file. It's just a copy&paste mistake.


Accessibility: Role "grid" is used inappropriately in the simple "list" component

Bug Report
If an app uses the list component from react-virtualized, the ARIA markup is incorrect. There is a "grid" container, but no "row" children and "gridcell" grandchildren. Screen readers of all platforms get utterly confused, report a grid with 0 rows, and on Mac, VoiceOver even doesn't render any of the child components, making apps largely inaccessible.
What is the current behavior?
Inaccessible apps due to invalid markup. Grid containers end up with button children or such.
Examples: Signal-Desktop, DeltaChat, Facebook Messenger.
What is the expected behavior?
List should use a generic container role like "region" instead, since you don't know what children there could be. Normally, "listbox" would be appropriate, but that requires that the children be of role "option". Since unlike with grids, you don't populate list children with default roles, this cannot be guaranteed, so for best generic accessibility, "region" is probably the best role to use here.
Which versions of React and react-virtualized, and which browser / OS are affected by this issue? Did this work in previous versions of react-virtualized?

Browser
Several

OS
Mac, Win

React
Several

React DOM
Several

react-virtualized
Several

Facing the same issue. This makes all list items inaccessible to the voiceover when using accessibilities keys like ctrl+option+ right/left arrow.

@bvaughn @TrySound Can we please merge this PR - https://github.com/bvaughn/react-virtualized/pull/1673 to fix current thread.

Two years down the line and this is still an issue? What’s the hold up here?

➕ 1⃣

This is still an issue


fixed an error with filter_level

This belongs to issue #865
Setting filter_level for Streaming API as below gives an error:
AttributeError: 'list' object has no attribute 'encode'
Fixed to:
self.body['filter_level'] = u','.join(filter_level).encode(encoding)
and tested with Python version: 3.5

Sorry, the issue is closed.


Entry selection not working when the React render root is within a Shadow Root

Hello Szhsin. Thanks for making this neat toolbox available to the community, works like a treat!
I'm here to report an issue for when we use react-autocomplete within a Shadow Rooted DOM Tree.
It looks like the selections are not happening, despite the dropdown popover closing.
When disabling the style, we can get the selection back… but we're now stuck with an ever showing dropdown.
It kind of looks like a timing issue (but I think it isn't).
Here is a reproduction:
https://codesandbox.io/p/sandbox/multiselect-forked-p4ph6n?workspaceId=489892b4-3ec8-4706-b740-7a7e40554033

Thank you

Hey @JulianCataldo , thanks for reporting the issue and sending over a PR. Will check it out when I get a chance.

Fixed by 1.0.1.


Decrease load time

Don't fetch information for every community partner or project every time, just add new ones. Otherwise the load time would be too high.

This is done @TarekRamesses


SquishIt replacing javascript variables

Details: http://stackoverflow.com/questions/32552473/squishit-replacing-with-short

This is minifier behavior, not squishit.
I think you might be able to work around it with the MS Minifier using something like this (http://stackoverflow.com/questions/5888580/ajax-minifier-ajaxmin-evaltreatment-for-javascript):
.WithMinifier(new MsMinifier(new CodeSettings { EvalTreatment = EvalTreatment.MakeAllSafe }))

There is an ignoreEval option for YUI minifier that looks like it allows functions calling eval to be compressed (https://github.com/BillyChan501/YUI-Compressor-.NET/blob/master/Projects/Yahoo.Yui.Compressor/Model Tests/JavaScriptCompressorTest.cs#L218-L256).  So the example you have might "just work" using default YUI options for minification?
.WithMinifier<YuiMinifier>()

Did you use the .MakeAllSafe method with the MS minifier?  I'm wondering if that should be the default behavior going forward.
I plan to make YUI the default minification option as of v1.0 so that may make sense if we want to keep behavior consistent.


Handle client updates more gracefully

When we update the client the previous build is no longer available.Therefore, chunk paths are no longer valid and a 404 page is returned were JSON is expected. The effects of which are unpredictable. This failed chunk requests make it all the way through to our monitoring application as an uncaught syntax error.

In the early days of learn.freecodecamp.org we had a serviceworker to handle this type of error, but we found that critical updates were not propagating in the speed required. In the interest of stability/usability, we removed the service worker.
There have been some developments in the plugin gatsby-plugin-offline to help with this issue and I would like to explore this again. See issue comment proposing a fix.
The onServiceWorkerUpdateReady hook will allow us to refresh the page automatically, or provide a confirm box to inform the user that a refresh is required. It should also note that declining to refresh may cause instability in their current session.
I propose we re-enable the offline plugin, with the onServerWorkerUpdateReady hook in use and monitor on .rocks for any issues.
cc/ @QuincyLarson @freeCodeCamp/dev-team for input

Just to make sure, how impacted are we without this. Is the behaviour and perf going to be worse than current prod, if we do this after the sprint?
IMHO, we do not want to be doing too anything that we during our beta sprint that is does not have a clear path ahead.
Coming back to the issue: As long as we implement a "break the glass" to override/unregister the service worker, I am all in favor for exploring it. This failsafe should be really robust to invalidate the worker/cache/etc.

@Bouncey I am in favor of doing this.
We should silently update automatically rather than prompting the user. Otherwise people may say "no" and just think freeCodeCamp is broken.

Hi Stuart,
Revisiting this.
I have been able to make a updates to cache which holds the chunks for 7 days and even considering to do it more aggressively by caching forever.
Don't ask me how its done, 😓 !
See: https://github.com/freeCodeCamp/freeCodeCamp/blob/master/client/static/_headers
I believe we are able to introduce the SW back again, and I guess, we could introduce the notification on an update. We do not need the notification to be confirmed and we do not need to reload automatically because the older chunks are still available.

We should silently update automatically rather than prompting the user. Otherwise people may say "no" and just think freeCodeCamp is broken.

This is not going to matter anymore and rather be counter productive. Automatic updates/reloads will break the state and result in data lose.
Since the chunks are available, it means a polite notification:
Hey, a new version of the platform is available. You can continue working. Just save your progress and reload the page when ready to get awesome new updates.

or something along that lines should be enough.

Closing this, need to create fresh discussion.
The implementation has changed quite a bit and we need to look at this from a fresh perspective. The need is still present.


Navigation actions and MobX based app

First and foremost I want to thank you for this project. As a beginner with RN I've stumbled upon react-navigation and was awfully confused not even mentioning it doesn't work well in some scenarios.
Anyway, I want to ask what would be the best pattern for invoking navigation actions outside of components? Initially, we are rendering simple Loading component with a picture and preloading assets and also verifying authentication. Based on auth state we want to navigate to the different scenes. We are also using MobX for app stores.
export default observer(function Main() {
  if (stores.preloadStore.loading) {
    return <Loading />
  }

  return (
    <Provider {...stores}>
      <Router>
        <Scene tabs navTransparent key="main">
          <Scene hideNavBar key="load" component={LoadingScene} />
          <Scene hideNavBar key="auth" component={AuthScene} />
          <Scene hideNavBar key="menu" component={MenuScene} />
        </Scene>
      </Router>
    </Provider>
  )
})

Then we have this simple autorun. The problem with this solution is that since Actions.auth() is also MobX, this autorun will also observe changes in a navigationStore and if we wouldn't call dispose here, it would end up with endless loop since the navigation action causes change to the navigationStore.
const disposeRedirect = autorun(() => {
  if (!authStore.isInitializing && !preloadStore.loading) {
    if (authStore.isAuthenticated) {
      Actions.menu()
      disposeRedirect()
    } else {
      Actions.auth()
    }
  }
})

Generally, it looks like a bad idea to cause navigation changes within stores. Am I missing something here? Perhaps some more declarative approach from within the component?

Good question, could you please give me a link to that project or even better, could you submit PR with this demo (with simple login/auth/loading screens and some fake auth), so I could include it as mobX example? We could name it as ExampleMobX project.

I will try to prepare some MobX demo (it could be very simple at the beginning) to demonstrate best-practices with MobX

@aksonov I am not sure what are you asking me for. I've already shown relevant code except for store itself, but that's just a couple of observable properties, nothing special about it.
You are saying that only way of using within MobX app is to be careful about disposing of autorun? :) That feels like a rather big source of problems to me.

No, navigation actions should not be done within autorun - it is not intuitive and difficult to debug way. Correct way is to use on(onEnter) and success, failure properties (more correct analog of v3 Switch statement)

Ok, I think I've got some partial solution.  This essentially works for the "load" scene where it can decide which way to go based on auth. However, I am struggling with redirecting to "menu" scene after the moment user gets authenticated. Apparently onEnter of the "auth" scene is not rerun when state changes.
function Main() {
  if (stores.preloadStore.loading) {
    return <LoadingScene />
  }

  const guardAuth = () => {
    const { authStore } = stores
    if (authStore.isInitializing) {
      return false
    }
    return authStore.isAuthenticated
  }

  return (
    <Provider {...stores}>
      <Router>
        <Scene key="main">
          <Scene key="load" component={LoadingScene}  initial on={guardAuth} success={() => Actions.menu()} failure={() => Actions.auth()} />
          <Scene key="auth" component={AuthScene} on={guardAuth} success={() => Actions.menu()} />
          <Scene key="menu" component={MenuScene} />
        </Scene>
      </Router>
    </Provider>
  )
}

There is also a small bummer that I cannot do directly success={Actions.menu} but need to wrap into a function. Not sure why is that, no error is popping there.

Use string, success='menu'

25 июля 2017 г., в 22:52, Daniel K<EMAIL_ADDRESS>написал(а):
Ok, I think I've got some partial solution. This essentially works for the "load" scene where it can decide which way to go based on auth. However, I am struggling with redirecting to "menu" scene after the moment user gets authenticated. Apparently onEnter of the "auth" scene is not rerun when state changes.
function Main() {
if (stores.preloadStore.loading) {
return
}
const guardAuth = () => {
const { authStore } = stores
if (authStore.isInitializing) {
return false
}
return authStore.isAuthenticated
}
return (
<Provider {...stores}>

<Scene key="load" component={LoadingScene}  initial on={guardAuth} success={() => Actions.menu()} failure={() => Actions.auth()} />
<Scene key="auth" component={AuthScene} on={guardAuth} success={() => Actions.menu()} />

)
}
There is also a small bummer that I cannot do directly success={Actions.menu} but need to wrap into a function. Not sure why is that, no error is popping there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, that's nice feature, although undocumented ;)
The main problem still remains though. Where to do navigation when a user gets authenticated? I guess that only viable solution is autorun in componentWillMount of AuthScene. It's not very nice, but I am unable to come up with anything else.

Where is the ExampleMobX demo project? I want to learn how to combo RNRF v4 and Mobx work together, thanks very much.

@aksonov Any other idea how to solve the problem at hand?
I think that things would great if on/onEntry/onExit would actually be automatic observers. Maybe I am missing something out here, but due to the fact, that with MobX it's not about re-rendering whole component tree, it shouldn't be probably build around events on a particular scene/route. Those are not executed when something in MobX store changes.

@FredyC It seems MobX observables/observer/autorun concept is a little bit different from redux-like react-navigation immutable state. onEnter allows to decide where to go but it should not be re-run because app could be already in different state (screen). And yes, you may add simple autoruns to return back to login screen once auth flag is changed easily.
@scriptfans and others
It is difficult and time consuming to create demo from scratch (like create loading/auth screen/main screen/logout/menu/etc, find needed icons, etc). If someone could share simple demo I could help to improve it to work with MobX. Feel free to submit PR or you could create own repo for this if you want to be maintainer.

@aksonov But autorun is what I had initially and it means I need to be careful about disposing it otherwise I might end up with endless loop.  I mean navigation logic in one place.
I can imagine something like this which would use autorun  underneath that would be setup when you enter the scene and disposed when you leave it. Whenever observable yields a change, the result of it would use success/failure as usual. Does that make a sense?
<Scene observe={() => user.isAuthenticated} success="menu" failure="login" />

It is interesting idea. But we can't dispose it when leave that scene - than observing will not happen. And now image several 'observe' Scenes and then could conflict each other or make infinite loop, etc... Need to think about it more. For now let's make some MobX demo but I really need help for this.

Yea, it needs some more thinking through. Maybe if it would work on parent scenes too and then you would have a nice declarative guard that would go to login whenever user loses authentication.
If it would be on a nested scene ten auto dispose would keep logic sane and essentially just used to declaratively say where to go next. For example, you would change currentItem in your store and guard on the scene would catch that and redirect to a detail scene. Something like that...
Anyway, I am afraid I cannot help you with the demo, because I simply don't understand how to do it yet. Using autorun in componentDidMount feels so awfully dirty. And the onEnter/onExit does not really work well with MobX based store. I am clueless how it's intended to work really.

Could you make demo with simple Actions.SCENE calls from componentDidMount() for 'loading' scene ? After that I will replace it with mobx logic.

I change a demo to use RNRF and Mobx, but I am not sure it use the correct way. Can you give me some advice?@aksonov ShiWuPai

@keith527 Great, do you have English interface? I'm not sure I could understand it with Chineese...

@aksonov I am so sorry, This api is from a Chinese company, so....I am not sure what's I can help you.

Just finished some basic conversion of nice starter kit with auth example (without dynamic recipes retrieval from firebase) to RNRF v4: https://github.com/aksonov/react-native-starter-app
Sorry, Redux was replaced for Mobx for great simplicity...
Any PR about new features demonstrated within that starter kit (on/success/failure transitions) is welcome.

@aksonov what if I want to track the previous screen?

@aksonov is there anyway that we can check whether the drawer is open or not?

@radha-bacancy Just check navigation state


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automatically remove the /fakepath/ prefix when editing files in file exercise admin

Should be in the javascript side

Tested on firefox, which uses \ characters as separators even in linux, and seems to work now.

Also tested on chromium, works.


Return to user's theme

Get the user's previous theme before deploying flashbang to avoid gruvbox default.

thanks :>


Build(deps): Bump react-router-dom from 6.4.1 to 6.4.2 (#4162)

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

Merged in 1e0e01c1b3d2f4cccec0a8a57761c81c8aafbee7


Delete folders for nonexistent projects in %appdata%/godot

Godot version:
3.1 RC1
OS/device including version:
Windows 10 x64
Issue description:
While I do a "Scan" in "Project List", the old projects whose folders have been deleted still remain in %appdata%/godot/projects and %appdata%/godot/app_userdata folders.

The app_userdata folder keeps the names of the folders of nonexistent projects, but they are empty.
The projects folder maintains a series of configuration files that should no longer exist.

Steps to reproduce:

Create any project and exit Godot
Delete its folder (via Windows Explorer)
Run Godot and click "Scan" on "Project List" window
Check the %appdata%/godot sub-folders.

Some people run projects from USB, so when the USB is not in, the project is "deleted" (inaccessible) but its cache etc. folders should not be deleted, for obvious reasons... That is a problem with all similar suggestions.

Some people run projects from USB, so when the USB is not in, the project is "deleted" (inaccessible) but its cache etc. folders should not be deleted, for obvious reasons... That is a problem with all similar suggestions.

https://docs.godotengine.org/en/3.0/development/compiling/packaging_godot.html
"The self contained mode can be used to package Godot for distribution systems where it doesn’t live at a fixed location. If the editor finds a ._sc_ file in the directory the executable is located in, Godot will continue in “self contained mode”. On Windows, the file name to use is sc (without the preceding dot)."

Self contained mode is about the editor, not the projects.
An option to clean the cache may be useful in the project manager.
Duplicate of #22467.
Related PR #25882.

Closing as duplicate of #22467.


Add reflector wrapper to WatchStreamExt::reflect

What problem are you trying to solve?
Currently, we rely on some chaining and some function wrapping to create our watcher streams. This leads to awkward readability such as:
let stream = reflector(writer, watcher(api, lp).backoff(bo)).applied_objects();

where some permutations are possible (such as doing the backoff outside the reflector).
It would be nicer if it was a single LTR chain such as:
let stream = watcher(api, lp).backoff(bo).reflect(writer).applied_objects();

Describe the solution you'd like
An impl Stream alternative to the simple reflector signature added added to WatchStreamExt:
    fn reflect<K>(self, mut writer: store::Writer<K>) -> Reflector<Self, K> { todo!() }

The Stream impl is unlikely to be complicated (maybe it can reuse InspectOk).
Name (currently reflect) TBD.
Describe alternatives you've considered
A complication with this approach is that reflector currently has a very easy signature:
pub fn reflector<K, W>(mut writer: store::Writer<K>, stream: W) -> impl Stream<Item = W::Item>
where
    K: Resource + Clone,
    K::DynamicType: Eq + Hash + Clone,
    W: Stream<Item = watcher::Result<watcher::Event<K>>>,
{
    stream.inspect_ok(move |event| writer.apply_watcher_event(event))
}

and we cannot simply lift that into WatchStreamExt as:
    fn reflect<K>(self, mut writer: store::Writer<K>) -> impl Stream<Item = W::Item>

because of:

error[E0562]:impl Trait only allowed in function and inherent method return types, not in trait method return

so it would need a full impl Stream setup instead.
So limited by: impl-trait limitations.
Can be unblocked by something like https://doc.rust-lang.org/beta/unstable-book/language-features/return-position-impl-trait-in-trait.html
Target crate for feature
kube-runtime

This was done in https://github.com/kube-rs/kube/pull/1252 by using a type wrapper that implements Stream


Bikeshedding assemble stage names

Initially, repo2docker buildpacks had two major stages: before adding the repo contents and after. These stages were called "build" and "assemble" respectively. The docs use these names:

Build a base language environment in the docker image
Copy the contents of the repository into the docker image
Assemble a specific environment in the docker image based on repository contents

Now, after #716. we have three stages: before adding repo contents, immediately before, and after, to allow build caching of e.g. environment installs with smaller rebuilds when only non-environment contents change. #716 calls the new stage preassemble since it happens before when assemble normally ran. In working on updating #410 (preassemble for conda and pip), I'm finding that what we've done is allow the stage known as assemble to occur earlier, with a partial repository, rather than only after adding the whole repository. As I look at implementing this for conda, most buildpacks will have either preassemble or assemble, but typically not both, and the two stages do the same thing, but with different file dependencies. It feels a little wonky to have "preassemble" be the stage when the environment is constructed and "assemble" an often empty stage depending on the entire repo contents.
Based on this, in #410 I initially called this assemble_from_subset as a flag for whether assembly happened with a subset of repo contents or all contents, since both stages are really assembly. Anyway, do folks have ideas for clearer naming of these split assembly stages? I think, the two assembly stages are:

begin assembling environment based on a subset of files that specify the environment, and
finish assembling environment based on the complete contents of the repository

but I don't know what to call them. I'm okay with sticking with preassembly/assembly if we don't come up with something more precise, but it's been tickling my brain as I work on implementing it.

I like the idea of changing the names. I can never remember if build or assemble is the one that happens first. I can remember that there is a phase independent of the repo contents and one that depends on the content. Maybe that is a way to get an idea for what to name things and help with remembering which is which. Now with assemble-from-subset and assemble-from-full we have another option for when code could run, potentially making it even harder to remember when stuff runs.
Not sure about buildpacks doing either assemble-from-subset or assemble-from-full. Where does something like postBuild fit? Or is it part of the base buildpack so the rule that a given buildpack only uses one or the other is true but a repo might use both?
Unfortunately I have no good suggestions right now for names (but I want some) :-/

Some possibly overly descriptive names:

assemble_base  - builds base environment, contains no repo files, but not entirely insensitive since it can specify e.g. runtime version
assemble_pre_stage - currently preassemble, this is the part of 'assembly' that runs prior to staging repo contents. May specify partial contents to include prior to staging. This is where most installation is probably going to happen.
stage  - this is where we copy (stage) the full repo, not customized by by the buildpack
assemble_post_stage - currently assemble, occurs after full repo is staged, which mostly occurs only when install includes local references. Usually a no-op.
post_build - the postBuild script runs after everything else, notably not after the stage currently known as 'build'. This is an escape hatch with generic execution, so it can't run any earlier and maintain full functionality.


Testing Suite Automation

Current repo:
https://github.com/francovenica/AutomGnosisSafe

Some info about how this went through:
Puppeteer was selected to do this since there is a library that extends puppeteer functionality called dappeteer, that gives methods to load metamask in a browser, connect to it, import accounts, sign transactions...
Also Jest was integrated so we can have actual results after a test (how long it took, which failed, assertion methods, etc)
At some point we tried Cypress that works better in general and is more user friendly, but loading extensions into it was hard and since you cannot work with more than 1 tab at the time there we had to discard it
It works well, it does what it's supposed to do. So far we were able to load metamask into the browser, connect to the application, and create a safe from scratch by signing the tx in metamaks. If all that was possible then it looks like the rest of the test we do manually can also be automated
The head of master is always a stable version that should be run well enough, but take in account that the code might be rough, unpolished and over all not that pretty. I'm trying to make it work first and then comes the optimization.
Kudos to Fernando and the rest of the guys for giving me a hand with that.
Drawbacks:
There are things that don't work well yet and require better implementation or more research with the tool. Also other things that sadly seem impossible to do:
1 - Is susceptible to failure because of low speed connection or Metamask taking a long time to load: There is simply no way around, if page takes too long to load then it will fail at some point. The only solution to this seems to be giving to every test a time out of several minutes.
2 - Seems to be impossible to do it with a headless browser: Since the browser has to load the metamask extension the browser has to be present, so it cannot be integrated to a CI server for now. I've tried with "Brave" since that browser has the wallet integrated (no need for the load of the extension in the same way chrome does) but it doesn't work, it seems Brave has compatibility issues.
3 - Every test has to be independent: I tried to connect to the wallet in the 1st test and then the rest of the test just keep using the open browser with the connection established, but for some reason it seems that the variables that hold the session open become undefined as you jump to another file, so right now every test has to open the browser and import the full wallet over and over again. Is not a big time loss but it might get annoying

I'm done with a test to send funds. Master was updated already.
@pablofullana what should we do with this ticket? we should keep it open and be renewed in every sprint? or can we close it here and open new ones as they are needed?
Right now my status with automation is: keep automating the test cases I have written and I do manually for every release until there is a specific task that needs to be automated by request of the people from Gnosis.

I'm done with 2 more tests:
-modify policies
-add/remove owners
both were updated in the master repo
Now I'm working with "replacing owners" but there are 2 tickets that are messing up that test:
https://github.com/gnosis/safe-react/issues/635
https://github.com/gnosis/safe-react/issues/649
I can still work on the test, but I'll be not able to complete it until those issues are fixed

This seems like a ticket that would never be closed as this seems to be an ongoing task. Should we just close this and open tickets for individual tests that should be added in the future? Or do I not understand the purpose of this ticket correctly? @francovenica

@lukasschor Yes we should close it.

hey @lukasschor. as far as I can recall, this issue was intended to track the testing suite automation setup. Just the setup, with a few tests to validarte that it is working as expected. So I guess it would be better to close this one and open specific issues for different sets of tests.

NVM, too late with my comment :)

But good that we are aligned :)


Temporarily change setSpec in UW and ESDN maps

For the record: setSpec is set_spec due to a bug in Krikri. This should be reverted this after the changes in dpla/KriKri#176 are merged and deployed.


Edits in bookbinding.

With this commit, now bookbinding is able to provide a more realistic bending effect with the added bending part on top of the page (previously it is bend at the bottom of the page only). For example:
Input image:

Output:


Adding Automated Connection Tracking Test Cases

Signed-off-by: Hiren Thakkar<EMAIL_ADDRESS>

Attached All Scripts Success Logs.
CT_Test_Cases_Logs.txt

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-1/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-2/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-3/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-4/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-5/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-6/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-7/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-8/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-9/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/e3912fbb7759f8158575b02855e5944307347b3b

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-10/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/1aa1cac12c3ef6eb92416072390baa000b36fd8d

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-11/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/94ad571acf9a42b070e7c7265550168b2dda7b5d

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-12/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/191dd962ed2edca8d17c115c014a47204cf0168b

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-13/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/191dd962ed2edca8d17c115c014a47204cf0168b

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-14/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/5a7255dab8729dfbcb845e7e7a8e98a8049698da

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-15/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/5a7255dab8729dfbcb845e7e7a8e98a8049698da

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-16/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/5a7255dab8729dfbcb845e7e7a8e98a8049698da

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-17/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/5a7255dab8729dfbcb845e7e7a8e98a8049698da

Attached ipdk building logs.
PR_59_Build_Logs.txt

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-18/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2c3990d07b362286bd082d477a1ea412e20ec266

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-19/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2c3990d07b362286bd082d477a1ea412e20ec266

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-20/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2c3990d07b362286bd082d477a1ea412e20ec266

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-21/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2c3990d07b362286bd082d477a1ea412e20ec266

Attached ovs building logs and Test cases run logs after made changes as per Siju's comment.
Build_logs_after_make_changes.txt
ptf_ct_tests_after_required_changes.log

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-22/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/c960c30b39ff1da7ab93cb67116dd00d5d48f102

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-23/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/1dedc3d940e00f514124e8cc50dcb3c4e93bd47a

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-24/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/cb2aad4ed62583dd0aeca9aad5b7610ef7938c85

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-25/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/cb2aad4ed62583dd0aeca9aad5b7610ef7938c85

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-26/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/4343a5042f78be13e3b2be7c2f8156fc25ba8936

Hi Siju/ Dwaipayan,
I have completed all netperf related changes and added ct timer test case.
Attached building ovs logs with all changes and ran all scripts logs.
====================
Summary
ct_single_connection_tap_link_ports : PASSED
ct_multiple_connection_tap_link_ports : PASSED
ct_rule_del_add_test : PASSED
nt_ct_unsupported_arguments_values : PASSED
ct_single_connection_vhost_ports_with_netperf : PASSED
ct_multiple_connection_vhost_ports_with_netperf : PASSED
ct_timer_test : PASSED
Ran 7 test(s), 7 Passed, 0 Failed.
ptf_ct_tests.log
Ct_7_test_cases_building_logs.txt

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-28/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ead9c470adcf669e1b7cc9b1b28c402dcb2316eb

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-30/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/12ca04383ef203a6506f140e6d59ac0abdeb891c

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-31/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/12ca04383ef203a6506f140e6d59ac0abdeb891c

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-32/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ca9a072f394684f07076b782637a591a8c252c20

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-33/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ca9a072f394684f07076b782637a591a8c252c20

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-35/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/6e6cb2b125bb49a6491e0e9c5bd91e8cc6dbd96b

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-36/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ed6e8a590271deb2fda3ac6b905ac0928d14e769

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-37/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ed6e8a590271deb2fda3ac6b905ac0928d14e769

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-38/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/ed6e8a590271deb2fda3ac6b905ac0928d14e769

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-39/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/c8097015a5b5ac7254ef3221078c067bdba2b246

below line in Makefile.am is not complete
ideally it should end with an ''
ptf_tests/common/p4c_artifacts/pna_tcp_connection_tracking/pna_tcp_connection_tracking.p
do we have this file?, if not we can remove this from Makefile.am
ptf_tests/common/p4c_artifacts/pna_tcp_connection_tracking/pipe/.gitkeep
Following seen in build log.
[2022-10-03T09:25:19.250Z] make[2]: *** No rule to make target 'ptf_tests/common/p4c_artifacts/pna_tcp_connection_tracking/pipe/.gitkeep', needed by 'all-am'.  Stop.
[2022-10-03T09:25:19.250Z] make[2]: *** Waiting for unfinished jobs....

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-40/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/c8097015a5b5ac7254ef3221078c067bdba2b246

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-41/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/336df5d52a6f3115d70dff7968edbbe657e17425

Result:FAILURE JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-42/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/336df5d52a6f3115d70dff7968edbbe657e17425

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-43/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/01f5e6ab64c936212e4b226de508bbf1b1490421

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-44/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/01f5e6ab64c936212e4b226de508bbf1b1490421

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-45/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/01f5e6ab64c936212e4b226de508bbf1b1490421

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-46/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/12f3c577c2beec74886db707c416085c16aa73a6

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-47/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2a4dadcfa3f5d31df125e96db36dde33b10a6e86

Result:ABORTED JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-48/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2a4dadcfa3f5d31df125e96db36dde33b10a6e86

Result:SUCCESS JenkinsConsole:https://s3.ipdk.io/ovs/PR-59-49/index.html GitCommit:https://github.com/ipdk-io/ovs/commits/2a4dadcfa3f5d31df125e96db36dde33b10a6e86


Add a platform check to homebrew role

This will allow the use of this as a role dependency - Ansible executes role dependencies unconditionally, so it's not possible to add geerlingguy.mac.homebrew to the dependencies section in a role's meta.yml if said role might run on non-macOS hosts (as Ansible will then try to install Homebrew on a non-macOS system, which unsurprisingly fails).
With this change, the role itself will still execute when used as a dependency, but only runs its tasks if the host is indeed running macOS.
The other alternative would be to add the ansible_os_family check to every task in the role; however by having a single include_tasks main step with the check will return much more quickly on non-Mac hosts.

Can you explain more about the use case where you'd use this role as a dependency... but not on Macs?

I've got a Vagrant+Ansible setup for provisioning testing VMs with a range of operating systems/versions, including RedHat, several Windows versions and multiple macOS versions. Among other things, this runs a role for setting up the desktop environment for these test machines including auto-login, with separate yaml files for each platform to do so. At the moment, this includes this bloc in the macOS setup branch of the role to make sure Homebrew is available on the Mac VMs:
include_role: geerlingguy.mac.homebrew
when: ansible_os == "Darwin"

There are multiple other roles in the setup workflow that depend on Homebrew-installed packages on macOS and so have the same inclusion - so it'd be quite nice if rather than manually including the role every time, I could use Ansible's dependency management to de-duplicate this from being run multiple times when provisioning Macs. However, Ansible's dependency management cannot be conditional, so the role would also be included when setting up a Rocky or Windows VM, where it unsurprisingly fails.


A few options for taskbar Icon customizability

Basically, there's a few features that StartIsBack has that I would love to exist in an open source program like this one, as well as a few Taskbar Tweaker options that would well suited here

Change spacing between taskbar icons, SIB+ has various margin sizes to choose between that would be nice to enable here
Large taskbar icons; this is something 7+ Taskbar Tweaker has that's really nice
Remove little line under opened programs icons. I know some custom themes remove it but for the life of me I cannot figure out what they are doing so if anyone figures out how please let me know

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


TFLM: update for supporting new ARC MLI backend

This pull request updates support new ARC MLI backend on Himax WE1 EVB

@googlebot I consent.


integrate mailtrap with autoline

See - https://app.asana.com/0/1202525679663009/1202736364697730/f
backend.env

You mustn't expose the ENV varibles on Github!

@ashonuyak, the password reset PR based on this one?


Invalid non-string/buffer chunk

`><EMAIL_ADDRESS>test /Users/kamwing/Desktop/skipper-qiniu

node -e "require('skipper-adapter-tests')({mocha: { timeout: 360000 }, module: require('./'), bucket:process.env.BUCKET || 'skipper-adapter-tests', accessKey: process.env.ACCESSKEY, secretKey: process.env.SECRETKEY});"

when some big files start coming in, this adapter
1) should work properly with 2 simultaneous requests with decent-sized (1.5MB) files
after uploading a file using this adapter, Skipper
each file metadata object
field
file descriptor (fd)
type
under a bit of load, this adapter
this adapter
this adapter's impact on req.body ::
Ignoring :: req.file("foo"), when a file upload is sent to the "bar" field ::
req.file(...).pipe(...) ::
req.file(...).upload(...) ::
0 passing (375ms)
1 failing

when some big files start coming in, this adapter should work properly with 2 simultaneous requests with decent-sized (1.5MB) files:
Uncaught TypeError: Invalid non-string/buffer chunk
at chunkInvalid (_stream_readable.js:399:10)
at readableAddChunk (_stream_readable.js:144:12)
at Readable.push (_stream_readable.js:130:10)
at Object.put (/Users/kamwing/Desktop/skipper-qiniu/node_modules/qiniu/qiniu/io.js:58:6)
at Writable.onFile (/Users/kamwing/Desktop/skipper-qiniu/index.js:65:16)
at doWrite (_stream_writable.js:307:12)
at writeOrBuffer (_stream_writable.js:293:5)
at Writable.write (_stream_writable.js:220:11)
at Transform.ondata (_stream_readable.js:555:20)
at emitOne (events.js:96:13)`

请问下这个问题可能是什么原因导致的吗？

抱歉，使用这个skipper还需要修改qiniu的内容，因为已经放弃sails了，所以没有打算去更新qiniu。


Beginner's question

Hello author,
Thank you for this great work. I am a beginner in diffusion model. Can I use my own trained model in your project?Currently, I only use diffusion_ffhq_10m and 256x256_diffusion_uncond.

yes you can.
The diffusion model in our method is used to provide image prior, you can use your denoisers in other image domains, e.g, medical image restoration.

Thank you for your answer. If I want to train a model with my own face data set to use in your project, where can I train my data set? Can you point out a path for me?

it is suggested to train a diffusion model using https://github.com/openai/guided-diffusion on your own data set, as our codebase  is based on guided diffusion and utilizes the checkpoints from guided diffusion

Thanks for your quick answer. I'll try.


status_code: 426

{
"status_code": 426,
"error": "HTTP Error",
"message": "An HTTP error occurred: Client error '426 unknown' for url 'https://search5-noneu.truecaller.com/v2/search?q=123456789&countryCode=91&type=4&locAddr=&placement=SEARCHRESULTS%2CHISTORY%2CDETAILS&encoding=json'\nFor more information check: https://httpstatuses.com/426"
}

A 426 status code is caused when a client is attempting to upgrade a connection to a newer version of a protocol, but the server is refusing to do so.
This can happen for several reasons, including:
Incompatibility between the client and server versions of the protocol.
The server may not support the requested version of the protocol.
The server may be configured to only allow certain versions of the protocol to be used.
The server may be experiencing technical issues or undergoing maintenance that prevents it from upgrading the connection.

Now I have encountered this error, I do not know what to do. If you have solved this problem, describe the solution to the problem


⚠ Bofrost.de has degraded performance

In b90631f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1073 ms

Resolved: Bofrost.de performance has improved in 2829c0d after 26 minutes.


Fix Click option error

#5816

Codecov Report

Merging #5817 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5817   +/-   ##
=======================================
  Coverage   63.83%   63.83%
=======================================
  Files         364      364
  Lines       23100    23100
  Branches     2587     2587
=======================================
  Hits        14745    14745
  Misses       8340     8340
  Partials       15       15

Impacted Files
Coverage Δ

superset/cli.py
46.59% <ø> (ø)
: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 a411516...d0c4a88. Read the comment docs.


[many ports] Add mirror

Since the normal ftp.gnu.org site was not accessible for all users to acquire several GNU libraries.
I added mirror https://www.mirrorservice.org/sites to some GNU libraries to fix this issue.
Besides this, I also removed deprecated functions in some ports.
Related issue #4085

Related: #8696


[CLI]: state does not sem to be Exposed on Sweep

Describe the bug

Sweep states are shown in in the dashboard:

and the code for pretty-printing the sweep includes a line to fetch its state.
However, in my sweeps, this always defaults to "Unknown State" - this property never appears to be populated in the same way as the dashboard.

Additional Files
No response
Environment
WandB version: wandb, version 0.16.1
Python version: 3.9
Additional Context
No response

Hello @stellarpower !
There seems to be some missing from my understanding. Are you seeing that there is an Unknown State that is popping up in the UI?
A couple questions if that's the case:

Are you on a Local instance or the Public instance? If its the Public instance, could I have a link to your project?
Could you provide a short, reproducible code snippet of your sweep for my own testing?

Raphael San Andres commented:
Hi Internal, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!


SFTP issues

Ok I had an error in my code that took time to debug the problem. However I found that the problem is the flags. Which is strang as they should be the same.
sftp_handle = libssh2_sftp_open(sftp_session, sftppath.c_str(),
LIBSSH2_FXF_WRITE | LIBSSH2_FXF_CREAT | LIBSSH2_FXF_TRUNC,
LIBSSH2_SFTP_S_IRUSR | LIBSSH2_SFTP_S_IXUSR |
LIBSSH2_SFTP_S_IRGRP | LIBSSH2_SFTP_S_IXGRP |
LIBSSH2_SFTP_S_IROTH | LIBSSH2_SFTP_S_IXOTH );
This returns an sftp handler like expected
var sftp_handle = sftp_open(sftp_session, "/tmp/testsftp",
LIBSSH2_FXF_WRITE or LIBSSH2_FXF_CREAT or LIBSSH2_FXF_TRUNC,
LIBSSH2_SFTP_S_IRUSR or LIBSSH2_SFTP_S_IXUSR or
LIBSSH2_SFTP_S_IRGRP or LIBSSH2_SFTP_S_IXGRP or
LIBSSH2_SFTP_S_IROTH or LIBSSH2_SFTP_S_IXOTH)
this however returns a value of nil. The sftp session is working, the session is set the blocking (session_set_blocking(session, 1)).
However having a file already created and using
    var sftp_handle = sftp_open(sftp_session, "/tmp/testread", LIBSSH2_FXF_READ, 0)

works?
I am confused on this. If you have any advice or could provide a working sftp write example. I would appreciate the help.

I hadnt use SFTP yet, do you think its a library issue?

I have no idea. It's confusing to say the least. If only nim-lang's standered libraries had ssh. However, Nice to know the only one confused. But not nice to know that not even you know. Did you use c2nim? If so then could that have caused an issue?

This is hand crafted wrapper, so I dont think it may causes any issues. I will try to make an example soon!

Thank you!!! I'm trying to create a POC (Proof of Concept). Using ssh

I made an async SFTP client example here, and its working
https://github.com/ba0f3/ssh2.nim/blob/master/tests/test_sftp.nim


Important Code Scanning Alert

Link: https://github.com/Vyxal/Vyxal/security/code-scanning/16
I also recommend storing it as a GitHub secret.

These are supposed to be private issues. Why do you think they have their own page?


[network] memsocket should only appear in debug builds

Motivation
The goal is to make network/memsocket crate test-only.
Have you read the Contributing Guidelines on pull requests?
yes
It fixes issue #3682

@phlip9 @davidiw can you please have a look on this PR ?

Awesome, looks great! Thanks again for the PR : )
@bors-libra r+

:pushpin: Commit e0029ef has been approved by phlip9

:hourglass: Testing commit e0029efe3e3fc50d6f68a773473b9c29c9311824 with merge 0a7e48d6a62f8df10426f46241fc960ad2dc4dd4...

@bors-libra r-

@bors-libra r+

:pushpin: Commit e0029ef has been approved by phlip9

:hourglass: Testing commit e0029efe3e3fc50d6f68a773473b9c29c9311824 with merge 7f2f37e9fd8469784f8969bcf22333a595c3778d...

:hourglass: Testing commit e0029efe3e3fc50d6f68a773473b9c29c9311824 with merge c70ed91cc1af0db7f4f1be0fd5bd0a89137fc1ba...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: phlip9
Pushing c70ed91cc1af0db7f4f1be0fd5bd0a89137fc1ba to master...


Incompatibility with "fork in run" in build.sbt

I have a play 2.3.6 project, with a build.sbt file that ends with the following line:
fork in run := true
After I added the play2war plugin, sbt starting giving me this compile error:
./play-heroku-seed/build.sbt:32: error: reference to fork is ambiguous;
I can workaround the error if I just delete the fork in run line from my build.sbt.  But is this really necessary?  It would be nice if I could keep that line so the fork policy is still set even when I'm not using the play2war plugin.
Thanks.

Which version of Play2war ?

1.3-beta3

Did you try with Play 2.4 and Play2War 1.4-x ?


docs: Replace rimraf with fsPromises.rm in Puppeteer.md

Summary
Replace rimraf with fsPromises.rm in Puppeteer.md
Test plan
This is a document-only change.
See also

#11951

Codecov Report

Merging #11957 (e48aef2) into main (b439692) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #11957   +/-   ##
=======================================
  Coverage   68.76%   68.76%
=======================================
  Files         322      322
  Lines       16620    16620
  Branches     4795     4795
=======================================
  Hits        11429    11429
  Misses       5159     5159
  Partials       32       32

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 b439692...e48aef2. Read the comment docs.


Missing import

It seems that you forgot to import this part:
https://github.com/eric-ai-lab/CPL/blob/16274a860712e7674a8d8fea7f3046fd96a065e4/CPL/trainers/cocoopcf.py#L17
And you also missed the requirements.txt.

Hi, I am sorry, what do you mean by forgot to import?
For requriements, sorry for missing. It should be the same as the CoCoOp one.

from utils import solver, mupdate
I cannot find anything of these two functions.

It seems to be merged when I cleant it up. Let me add it. Thks for pointing it out!

Good work!!! I close this issue!


move segmentation to its own module

thanks! how about let us cs (short for cell segmentation) instead of sg for module name? st.sg. reads more boring compared to st.cs..
We can still just keep the segmentation folder as it is also

thanks again! I faced the same integration error last night. looks like we should comment hdbscan in the Makefile? we don't really use hdbscan in spateo package

thanks again! I faced the same integration error last night. looks like we should comment hdbscan in the Makefile? we don't really use hdbscan in spateo package

Fixed it


Read LB address from infrastructure-managed ressource

I'm opening this issue to find out if our use-case is supported.
We use ingress objects and nginx-ingress-controller to route external traffic coming from ALBs inside the cluster. Currently we have our own approach of updating route53 with the address of the ALB.
However we'd like to move to external-dns and have it update route53 with the address of the ALB, but without leaking the ALB-address into the application manifests.
Not sure how feasible that is. One solution could be to get the ALB-address from a TPR?

Hi @janwillies, with "without leaking the ALB-address into the application manifests" you mean the ALB CNAME shouldn't show up in the status section when you do a kubectl get ing my-ingress -o yaml?

No, I mean the external-dns controller should not read the ALB address from the ingress or service manifests, but from a different source, maybe a TPR. When I update the TPR with a new ALB address, external-ingress should update_all_ corresponding route53 entries with the new destination.
Background: A lot of ingresses are pointing to the same ALB in our environment and we would have a more central point of managing the ALB address, instead of spreading it to all manifests.
I understand this is a bit of a special use-case

@janwillies sorry for the delayed response.
We do plan to support TPRs as a possible source of DNS entries for cases that are more special than just annotating services and ingresses. We didn't discuss them, yet, but it'll probablby boil down to a description of typical DNS record parameters (type, ttl, source, target...) that can be cloud provider agnostic.
What I had in mind until now would be something like this:
apiVersion: external-dns.kubernetes.io/v1alpha1
kind: DNSRecordSet
metadata:
  name: my-stuff
spec:
  source:
  - foo.example.org
  - bar.example.org
  target:
  - <IP_ADDRESS>
  type: A
  ttl: 300

It might make sense to also be able to decouple the target (and source) via a targetRef:
...
spec:
  source:
  - foo.example.org
  target:
    targetRef:
      kind: Pod
      name: foo
  type: A

This would create DNS record pointing to the current IP of the foo pod. This probably doesn't make sense but then one might be able to also reference other resources, including third party resources. For example, creating a Service with type ExternalName pointing to your ALB CNAME:
apiVersion: v1
kind: Service
metadata:
  name: my-alb
spec:
  type: ExternalName
  externalName: alb-1234.awselb.com

And then referencing this resource as a target:
...
spec:
  source:
  - foo.example.org
  target:
    targetRef:
      kind: Service
      name: my-alb
  type: CNAME (or A, ALIAS?)

This would allow you to change the target ALB CNAME in one place that's not in the record set, however you would have to enlist all your source DNS names here. One could think of applying the targetRef stuff to sources as well.

That's a very flexible approach!
Can't we get the source automatically from an annotation? Something like
spec:
  source:
  - annotation:foo
  - annotation:bar

Not sure how to differentiate from a valid DNS identifier, via colon?
And the annotation would be something like:
external-dns.alpha.kubernetes.io/virtualLoadBalancer


Date translation

Hi,
Only the verbose arguments are getting translated. The dates remain in English and so does the "in XX days". Any chance you add those to the translation files?
Many thanks.

Unfortunately not. Tried that, HA does not support setting locale for the dates.
You can translate the "in XX days though" using verbose_format. And you can set the date format using date_format. But it won't translate month names.

What about a translation for "tomorrow" and "today". Any chance here?

Sure, that is no problem. Already translated to French, German, Italian and Czech. Feel free to make a pull request with your language HERE. It is the files sensor.XX.json (the files with just language name translate the configuration web page - feel free to translate that as well ;).

Hm, if its already translated to german, why is it displayed in english on my frontend with "Garbage Collection Card"? I have installed version 2.12 via HACS and I use the verbose option for the sensor.

If you have the language in your user profile set to German, the sensor state should be in German (check the actual sensor state in Developer Tools/States - could it be that the language is coming from the Garbage Collection custom card?)

My Profile is set do "Deutsch", but the sensor state shows "Tomorrow"

I see. It looks like it stopped working. I will look at it. Thanks.

Ok, I guess I forgot how it works. So, here we go. The actual state is in English (it is actually supposed to be in lower case, will fix that in the next release). So that you can use it in your automations and they will run regardless of the user language preference.
On the front end, the state is translated based on your user preference. So if you put a card on Lovelace, or you click on the i in the circle, it the state should be in German. Please check!

Yes, if I just use the "entity" card, it is displayed in German. So it seems to be an issue with "Garbage Collection Card". I'll continue there 😉

I think it could be related to this https://github.com/amaximus/garbage-collection-card/issues/16

Maybe, but there it seems, that this could not be solved. 🤔 And if I use the verbose mode to display the right date format, I have no chance to manually translate 'tomorrow' or 'today', as there is no option in verbose mode for this.

When I put my HA profile to German, the garbage collection card shows the German translation for "tomorrow" and "today". However, I do not want to set my HA profile to German. How can I get the German translation while keeping my HA profile Englisch? Already tried to paste content of the "sensor.de.json" into the "sensor.en.json", but somehow the it does not affect the outcome.

That is weird, that should work. The way it works is, the sensor sets the value to "today/tomorrow". And then the front end translates it based on the user language, using the translation files. So if you fool it and put the German words in the English translation file that should work.
If you use the garbage collection card though, there is another translation under the card, so you might need to change it there as well (suppose the standard translation service does not work in custom cards, so amaximus added his on top).

Yes, if I just use the "entity" card, it is displayed in German. So it seems to be an issue with "Garbage Collection Card". I'll continue there 😉

You can edit the file

"\config\www\community\garbage-collection-card\translations\en.json"

according to your needs. That did it for me.

@bruxy70 Yes, it works perfectly. The garbage-collection-card was the problem in my case. I just changed the translation file there as well and everything is perfect now. Thank you for this cool sensor :)


unable to interact with chadwm

i followed the installation steps, and when dwm started, the background was black except for the task bar, i could move my mouse but no keyboard inputs, no shortcuts worked, i couldnt even exit out, i had to boot into the iso to fix it

by "fix it" i mean not autostart dwm

how can i make it useable?

by "fix it" i mean not autostart dwm

because that autostart file is meant for my system , you have to add your stuff . like add your wallpaper etc. remove everything from it except the line having "dwm"

i did that, same error

i did that, same error

how are you starting dwm?

i added exec dwm to .xinitrc, autostart on reboot

should it be "exec ~/.dwm/autostart" ?

ok i just tried it, still getting the same error, im using arch-linux if that  helps

should it be "exec ~/.dwm/autostart" ?

yes , show your autostart

also you need to uncoment one line from config.def.h , read it properly

ok i removed that thing , https://github.com/siduck76/chadwm/blob/main/chadwm/config.def.h#L136 . update config

I commented that line, still same error

*uncommented

I commented that line, still same error

which terminal are u using? st should work ootb with chadwm or u gotta edit config.h
make changes in config.h. stop editing config.def

I use alacrity should I change my default to st?

Also, mod shift r does not do anything, is the mod key set to something other than alt in chadwm?

Also, mod shift r does not do anything, is the mod key set to something other than alt in chadwm?

its super key

You've got to be kidding me, i used windows key instead of alt, and i got the terminal working, thanks!

Ig this can be closed now :p


Support Rails 5

This PR changes the Rails Rack::Test syntax to match the non-Rails syntax. This will need to be regression-tested against Rails 4.

Resolves #79


Recursion: Reverse a String in Cpp

Before jumping into Pr first comment for assign.
Problem statement:: Write a function that reverses a string. Make your function recursive.
Link: https://edabit.com/challenge/HXGx9oXukEgsFK6PH

Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py

[ ]  In file there should be problem statement and link to probelm

[ ]  Add label for Problem
example -

/* this program will add two numbers
    * Problem : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Can I work on this as part of hacktoberfest?

Could I pick this?

Could I pick this?

@subramanian0 assigned based on priority comment.
@DaniAcu you can make a new issue for new proble. Find problem from Edabit.com

@aayushi-droid  : I was assigned this but the code was already added to the repo.


New posts tweets do not have hastags for posts

It looks like the Blog Post tags are not being added as HashTags for new posts tweets. Probably because we are looking at Categories and not tags.

Looking at this and the reason is that the new posts are being generated from SourceData which does not have categories or tags.


[Bug]: Dupulicate index name in PostgreSQL

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Environment
Self-hosted
Describe the bug
Updating v2.13 to v2.14, migration error happened because index owner_removed_idx are duplicated. Please give a different name to earch index.
The similar errors happened 05.sql in v2.13
To reproduce

Use PostgreSQL instead of CockroachDB.
install zitadel 2.13.
initialize zitadel
install zitadel 2.14
do zitadel start-from-init

Screenshots
No response
Expected behavior
migration finished and started successfully.
Version
v2.14.0
Operating System
OS: Debian 11.5
PostgreSQL: 15.1
Relevant Configuration
Database:
  # Postgres is used as soon as a value is set
  # The values describe the possible fields to set values
  postgres:

Additional Context

log

zitadel@ls:~$ /usr/local/sbin/zitadel start-from-init --masterkeyFile ./master.key --config ./zitadel-config.yaml --tlsMode external
INFO[0000] initialization started                        caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:72"
WARN[0000] postgres is currently in beta                 caller="/home/runner/work/zitadel/zitadel/internal/database/postgres/config.go:61"
INFO[0000] verify user                                   caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:38" username=zitadel
INFO[0000] verify database                               caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:38" database=zitadel
INFO[0000] verify grant                                  caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:33" database=zitadel user=zitadel
INFO[0000] verify zitadel                                caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:69" database=zitadel
WARN[0000] postgres is currently in beta                 caller="/home/runner/work/zitadel/zitadel/internal/database/postgres/config.go:61"
INFO[0000] setup started                                 caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:60"
WARN[0000] postgres is currently in beta                 caller="/home/runner/work/zitadel/zitadel/internal/database/postgres/config.go:61"
INFO[0000] verify migration 01_tables                    caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] verify migration 02_assets                    caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] verify migration 03_default_instance          caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] verify migration 04_eventstore_indexes        caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] verify migration 05_last_failed               caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] verify migration 06_resource_owner_columns    caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39"
INFO[0000] starting migration 06_resource_owner_columns  caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:49"
ERRO[0000] migration failed                              caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:51" error="ERROR: relation \"styling2\" already exists (SQLSTATE 42P07)"
FATA[0000] unable to migrate step 6                      caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:115" error="ERROR: relation \"styling2\" already exists (SQLSTATE 42P07)"

Oh, this has been already fixed. Thanks.


EXC_BAD_ACCESS (code=1, address=0x0) on iOS when running linked Godot Mono project in XCode

Tested versions

Reproducible in v4.3.stable.mono.official [77dcf97d8]

System information
Godot v4.3.stable.mono - macOS 13.7.2 - GLES3 (Compatibility) - AMD Radeon Pro 560 OpenGL Engine - Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 Threads)
Issue description
I'm following Steps to link a Godot project to XCode on a Godot 4.3 mono.
Expected result:

after final step, when running from XCode project should launch

Actual result:

application crashes when launched

Note:
When creating the MRP, i've started without C#/Mono and can confirm that with GDScript project the guide works as expected.
    0x1c6f0813c <+2332>: bl     0x1c6efba70               ; lsl::Lock::unlock()
    0x1c6f08140 <+2336>: ldr    x8, [x19, #0x8]
    0x1c6f08144 <+2340>: ldr    w0, [x8, #0x68]
    0x1c6f08148 <+2344>: ldp    x1, x2, [x8, #0x70]
    0x1c6f0814c <+2348>: ldr    x3, [x8, #0x80]
    0x1c6f08150 <+2352>: blraaz x20
->  0x1c6f08154 <+2356>: mov    x1, x0 Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)
    0x1c6f08158 <+2360>: ldr    x0, [x19, #0x98]
    0x1c6f0815c <+2364>: ldr    x16, [x0]
    0x1c6f08160 <+2368>: mov    x17, x0
    0x1c6f08164 <+2372>: movk   x17, #0x9abf, lsl #48
    0x1c6f08168 <+2376>: autda  x16, x17

Steps to reproduce

Use the MRP project or create an empty
Add a C# script to it
Follow steps in Steps to link a Godot project to XCode

Minimal reproduction project (MRP)
xcodelinkmrp.zip

duplicates: https://github.com/godotengine/godot/issues/86019


Investigate more accurate beam correction methods

see this paper for one example Ive found

This looks like another example, might be more intuitive?  Haven't looked too closely just yet.


Use branchless way to get rv_hi/rv_lo result

We can avoid using conditional branch via bitwise operation.
The value of ((val & (1 << 11)) << 1) is exactly 4096 if (val & (1 << 11)) is true.

Thank @fennecJ for contributing!


plugin different version of package main

What version of Go are you using (go version)?

$ go version
go version go1.12.1 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/lx/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/lx/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.1/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7k/r2p50mb149ngfkbmdw9tdqhc0000gp/T/go-build367373739=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I write a demo to test the go plugin, My work directory structure is

|____gen
| |____src
| | |____main
| | | |____main.go
|____plugin_name.so
|____build.sh
|____main.go

main.go

package main

import "plugin"

func main() {
	p, err := plugin.Open("plugin_name.so")
	if err != nil {
		panic(err)
	}
	v, err := p.Lookup("V")
	if err != nil {
		panic(err)
	}
	f, err := p.Lookup("F")
	if err != nil {
		panic(err)
	}
	*v.(*int) = 7
	f.(func())()
}
gen/src/main/main.go

package main

import "fmt"

var V int
func F() { fmt.Printf("Hello, number %d\n", V) }

build.sh

DIRPATH=$(dirname $0)
GOPATH=$(cd "${DIRPATH}/gen"; pwd)

export GOPATH
cd ${GOPATH}/src/main
go build -v -o plugin_name.so  -buildmode=plugin
mv plugin_name.so ${GOPATH}/..

What did you expect to see?

sh ./build.sh
go run main.go

I expect to see the main.go load the plugin successfully and print line.
What did you see instead?

panic: plugin.Open("plugin_name"): plugin was built with a different version of package main

goroutine 1 [running]:

main.main()
	/Users/lx/go/src/testZoom/tplugin/main.go:8 +0x38b
exit status 2

Why the main package is a different version, howerver if I modify the build.sh to

go build -v -o plugin_name.so  -buildmode=plugin main.go

Then go run main.go load so successfully.
How can the main package be a different version and why the second solution success?

probably cause by
https://github.com/golang/go/blob/release-branch.go1.12/src/cmd/go/internal/work/gc.go#L492

/cc @ianlancetaylor


Bug: windows defender warning is not fixed by recommended script

Environment

Windows 10 version 1903 build 18362.387
Scoop latest commit = 3e55a709
Example commands run in powershell being run as administrator

Steps To Reproduce

scoop checkup
observe warning "WARN  Windows Defender may slow down or disrupt installs with realtime scanning."
Observe recommendation "Consider running:
sudo Add-MpPreference -ExclusionPath 'C:\Users\username\scoop'
(Requires 'sudo' command. Run 'scoop install sudo' if you don't have it.)"
Run sudo Add-MpPreference -ExclusionPath 'C:\Users\username\scoop'
Observe script exit with no error.
Run scoop checkup again.

Expected behavior
Warning about Windows Defender is gone having run recomended script to address issue.
Actual behavior
Warning is still present
Additional notes
I actually get two of these warnings when running scoop checkup the one listed above and an identical one for "C:\ProgramData\scoop". Both behave the same way. I've also tried restarting my PC after running the fix scripts but it seems to have no effect.

Have you tried to open an admin session of PowerShell and ran Add-MpPreference -ExclusionPath 'C:\Users\<yourname>\scoop'?

Have you tried to open an admin session of PowerShell and ran Add-MpPreference -ExclusionPath 'C:\Users\<yourname>\scoop'?

Yes, as I said, all commands were run in an admin session of Powershell. I tried first without sudo, then installed it and ran it with sudo. Same result either way.

update steps to reproduce to make it clear that you ran the command in step 4 twice. once for each folder.

I did Add-MpPreference -ExclusionPath F:\scoop ; it worked when I opened powershell 5.1  session  as admin.
I checked it using the Windows Security app.
steps:- Open the app and then Virus and threat protections, then 'manage settings'  then 'add or remove exclusions'.

did you try double quotes like Add-MpPreference -ExclusionPath "C:\Temp"
and to check if it worked using powershell, try
$Preferences = Get-MpPreference
$Preferences.ScanScheduleDay

before and after doing the Add-MpPreference part.
if you make a mistake, undo it using https://docs.microsoft.com/en-us/powershell/module/defender/remove-mppreference?view=win10-ps#examples

Also, don't worry about this exact warning, you can still use scoop. It maybe slow, but I would not exclude anything if I'm going to be installing scoop or any new app for the first time. Also, there are no guarantees about the slowdown or it being perceivable.

Figured it out. The recommended script has no effect because the computer I encountered the issue on is a company-owned machine, and exclusions are managed by the group policy. Apparently even though I have local admin rights, the group policy can prevent adding exclusions.
Maybe this could be documented in the warning so that others aren't confused over the same thing? That being said, I could see that getting pretty verbose, so I'd be OK just closing the issue with no change.


Support Container Logs Collector Configuration for ADOT add-on

Is your feature request related to a problem? Please describe.
Support Container Logs Collector Configuration for ADOT add-on (update version)
Related blueprints issue : https://github.com/aws-quickstart/cdk-eks-blueprints/issues/881
Also Collector Changes - https://github.com/lewinkedrs/cop-401-instrumentation/blob/main/python-manual-instrumentation-sample-app/prometheus-daemonset.yaml
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Feature implemented. Closing the PR.