Global search with file filters does not work for Network Shares

If you open VSCode in an network share the "files to include" with a valid file extension returns nothing (* returns a subset of all results) and the "files to exclude" returns everything even with gibberish.

VSCode Version:
C:\Users\jerobins.REDMOND>code --version
1.19.2
490ef761b76b3f3b3832eff7a588aac891e5fe80
x64

OS Version:
Windows 10

Steps to Reproduce:

Open VSCode in a network share
Do your search with "files to include" or "files to exclude" set to something
In the files to exclude case it returns everything, in the files to include case it returns nothing.  (for me atleast)

As you can see in the image below I have some xml files.

When I filter "files to include" it fails.

I mounted the share as a drive and the problem went away.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

Could you try this with the Insiders version? There were some bugs fixed with UNC paths for search in the past month.

@roblourens Seems to work correctly in the insiders version.


Small feature updates to gh34-35

Allow for string Ee dictionary keys
Only iterate over unique cells when setting entire module to one Ee
Only copy when necessary when setting subset of cells in a module with scalar Ee
Only copy when necessary when setting suns on a list of cells with a list of Ee values

Object sizes for 20 string by 20 module system with PCT492 cells, npts=1001:

Fresh system: 411kB
Application of test shade before changes: 402.2MB
Application of test shade before changes: 63.1MB

For reference, before the changes made in gh34-35 a fresh system of this size would take >10GB.
Finally, nosetests ran in 5.12 seconds on my computer before the changes in this pull request. Now, they run in 3.88 sec.

ha, ha, I never saw this. sorry. but better to open pr on upstream instead of using my fork as proxy.


Links are blocked

I am getting "graph-tutorial" links are blocked message when the sign-in button is clicked and tries to redirect.  Can you please help me with why I am getting this error and how to resolve this?

Sounds like you need to register the redirect URL scheme, which is graph-tutorial.
For iOS: https://github.com/FormidableLabs/react-native-app-auth#register-redirect-url-scheme
For Android: https://github.com/FormidableLabs/react-native-app-auth#android-setup

Added intent tag in Android Manifest


bump cosign to v1.9.0 to resolve reporting of GHSA-66x3-6cw3-v5gj

Signed-off-by: Weston Steimel<EMAIL_ADDRESS>

Looks like this is a large change to their library code! I'll take a look here as soon as I have time to see what we can refactor so we can stay in sync.
Thanks for the nudge that this should be updated


Can't get Gradle shared read-only cache to work

Expected Behavior
I was expecting that after seeding the read only shared cache, the write only cache will be empty, or at least smaller than the read only cache, after the next gradle init run
Current Behavior
The shared cache, and the normal write cache end up as exactly the same size, which leads me to believe the shared cache is not being used
Context
Not applicable I believe
Steps to Reproduce
gradle --version
------------------------------------------------------------
Gradle 6.7
------------------------------------------------------------

Build time:   2020-11-10 23:24:12 UTC
Revision:     <unknown>

Kotlin:       1.3.72
Groovy:       2.5.12
Ant:          Apache Ant(TM) version 1.10.8 compiled on May 10 2020
JVM:          11.0.8 (Oracle Corporation 11.0.8+10)
OS:           Linux 5.9.11-arch2-1 amd64

rm -rf ~/.gradle/caches/modules-2/* # Empty the "normal" write cache
gradle init # Repopulate the write cache
# ... stuff happens
export GRADLE_RO_DEP_CACHE=/tmp/gc/ # Specify location for read only shared cache
cp -r ~/.gradle/caches/modules-2 $GRADLE_RO_DEP_CACHE/ # Seed the shared cache
rm -rf ~/.gradle/caches/modules-2/* # Empty the normal cache again
gradle init # Run gradle again
# ...
du -hs ~/.gradle/caches/modules-2/ /tmp/gc # Check the sizes of the caches
108M	/home/myuser/.gradle/caches/modules-2/
108M	/tmp/gc

### Your Environment
This is a private project, I will have to ask whether it's okay to upload a build scan

@norbertkeri Do you see something like this at the start of the second gradle init?

The read-only dependency cache is disabled because of a configuration problem:
Read-only cache is configured but the directory layout isn't expected. You must have a pre-populated modules-2 directory at /tmp/gc/modules-2 . Please follow the instructions at https://docs.gradle.org/6.7/userguide/dependency_resolution.html#sub:shared-readonly-cache

I think your cp command is copying the contents of modules-2 into GRADLE_RO_DEP_CACHE instead of the directory itself because GRADLE_RO_DEP_CACHE does not exist yet.

@big-guy you are entirely right, this was the problem.
I have also checked the user guide again, and I /swear/ the last time I looked at it (in December) the suggested directory layout was what I described in the ticket (having the contents of modules-2 inside $GRADLE_RO_DEP_CACHE, and not the folder itself), but it's entirely possible it was just me looking forward to my vacation, and misunderstood.
So for anyone else finding this, this is the directory layout you should have:
$ tree -L 2 $GRADLE_RO_DEP_CACHE
/tmp/gc/
└── modules-2
    ├── files-2.1
    ├── metadata-2.96
    └── modules-2.lock

Thanks a lot.

@big-guy you are entirely right, this was the problem.
I have also checked the user guide again, and I /swear/ the last time I looked at it (in December) the suggested directory layout was what I described in the ticket (having the contents of modules-2 inside $GRADLE_RO_DEP_CACHE, and not the folder itself), but it's entirely possible it was just me looking forward to my vacation, and misunderstood.
So for anyone else finding this, this is the directory layout you should have:
$ tree -L 2 $GRADLE_RO_DEP_CACHE
/tmp/gc/
└── modules-2
    ├── files-2.1
    ├── metadata-2.96
    └── modules-2.lock

Thanks a lot.

Actually, it still doesn't work. I'm not sure what happened, but now my read only cache, and the normal cache has the same size, after a gradle init run.
Can you please confirm that the "normal" cache directory is supposed to be smaller, than the read only cache directory?

Actually, it still doesn't work. I'm not sure what happened, but now my read only cache, and the normal cache has the same size, after a gradle init run.
Can you please confirm that the "normal" cache directory is supposed to be smaller, than the read only cache directory?

I'm experiencing the same problem with gradle 6.8.3

Running gradle init --debug shows these log messages:
2021-04-21T15:43:43.326+0200 [DEBUG] [org.gradle.cache.internal.DefaultCacheAccess] Creating new cache for metadata-2.97/module-metadata, path /tmp/gc/modules-2/metadata-2.97/module-metadata.bin, access org.gradle.cache.internal.DefaultCacheAccess@55338619
2021-04-21T15:43:43.327+0200 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Opening cache module-metadata.bin (/tmp/gc/modules-2/metadata-2.97/module-metadata.bin)
2021-04-21T15:43:43.338+0200 [DEBUG] [org.gradle.cache.internal.DefaultCacheAccess] Creating new cache for metadata-2.97/resource-at-url, path /tmp/gc/modules-2/metadata-2.97/resource-at-url.bin, access org.gradle.cache.internal.DefaultCacheAccess@55338619
2021-04-21T15:43:43.338+0200 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Opening cache resource-at-url.bin (/tmp/gc/modules-2/metadata-2.97/resource-at-url.bin)
2021-04-21T15:43:44.862+0200 [DEBUG] [org.gradle.cache.internal.DefaultCacheAccess] Creating new cache for metadata-2.97/module-artifact, path /tmp/gc/modules-2/metadata-2.97/module-artifact.bin, access org.gradle.cache.internal.DefaultCacheAccess@55338619
2021-04-21T15:43:44.862+0200 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Opening cache module-artifact.bin (/tmp/gc/modules-2/metadata-2.97/module-artifact.bin)

Seems strange that it is writing into /tmp/gc, which is supposed to be the read only cache.

Revision:     <unknown> indicates your are using a non standard Gradle distribution and is usually a red flag for any unexpected behavior.
Please try again with a real Gradle version.
Closing for now as we have been unable to reproduce and know the feature works in other cases.


operator: Failed to resolve table or column or scalar expression named 'Event'

The very first example dies with this exception.  Are we missing a step on how to enable this or select some scope first?

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

ID: ba6a8ef4-0b79-9ce3-eff0-66566ec454c2
Version Independent ID: 13444c5c-8428-071d-8c85-57a9384507f2
Content: Get started with Azure Monitor Log Analytics
Content Source: articles/azure-monitor/log-query/get-started-portal.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

For search query:
search: must have at least one tabular expression as a source, no matching entities were found. 'search' operator: Failed to resolve table expression named 'Event'

@CastleArg Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

@CastleArg Can you please validate whether you have the table named 'Event' in schema that can be checked under 'Logs' tile of your Log Analytics workspace. For illustration, please see below screenshot. Similarly, check whether you have configured to collect event logs as explained in this document.

@CastleArg Did you get chance to check my above comment and validate ?

Hi there, off the bat there is nothing to select in the schema browser..
I guess what is missing in the docs is the instruction to select an
appropriate resource and a link to an example of how to do this.
Also not everything will have an Event table (azure functions for example)
Maybe this is all obvious but as it's a getting started page it would be
good to have the above links, as a newbie just following the instructions
will immediately encounter errors.
On Tue, Sep 17, 2019 at 2:31 PM KrishnaG-MSFT<EMAIL_ADDRESS>wrote:

@CastleArg https://github.com/CastleArg Did you get chance to check my
above comment and validate ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/38928?email_source=notifications&email_token=ADTPCMN2GBVG7HWTTJS3XFLQKA6RPA5CNFSM4IW4LCN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD63CTTA#issuecomment-532031948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTPCMNHHWE3JL23VOTCRMLQKA6RPANCNFSM4IW4LCNQ
.

Assigning content owner @bwren for visibility, review and document enhancement considerations.

This does assume that your environment has an agent monitoring a VM, which is where the Event table comes from.  Otherwise, you can use the demo environment.  I'm updating the note at the top of the article to specify that.

#please-close


k8s-spot-rescheduler doesn't trigger cluster autoscale up if no spot instances available

We're using kops 1.10.0 and k8s 1.10.11. We're using two separate instance groups (IG), nodes (on-demand) and spots (spot), both spread across 3 availability zones. I've applied the appropriate nodeLabels and have defined the following in my k8s-spot-rescheduler deployment manifest:
- --on-demand-node-label=on-demand
- --spot-node-label=spot

The nodes IG has the spot=false:PreferNoSchedule taint so the spots IG is preferred. I'm using the cluster autoscaler to autodiscover both IGs via the --node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,kubernetes.io/cluster/kubernetes.metis.wtf and these tags exist on both IGs. I've confirmed that pods on most nodes nodes are able to be drained and moved to spots nodes. With an exception:

The spots IG was set to minSize: 1 and maxSize=3 and we had one spots node up and running in us-east-1c
k8s-spot-rescheduler attempted to drain the pods on a nodes node but failed with

I0117 02:16:49.099271       1 rescheduler.go:288] Considering ip-172-20-127-232.ec2.internal for removal
I0117 02:16:49.099797       1 rescheduler.go:293] Cannot drain node: pod metis-internal/rabbitmq-0 can't be rescheduled on any existing spot node

metis-internal/rabbitmq-0 is a statefulSet with a PVC
the PVC resides in us-east-1a so it makes sense why it couldn't be scheduled on the spots node

Why didn't the failure to schedule metis-internal/rabbitmq-0 trigger the cluster autoscaler to try to provision a new spots node until it created one in the same availability zone? I'm wondering if k8s-spot-rescheduler would have actually evicted the pod, the cluster autoscaler would have noticed that a pod needed to be scheduled and would have spun up a new node in the spots IG.

Any news on this front?
If you guys have a strategy, I'm more than willing to help with the implementation of this feature, as it seems important for us.

Taint can be add to on-demand instance group other than spot-instance IG like below.
labels              = "kubernetes.io/role=common,lifecycle=OnDemand"
taints              = "lifecycle=OnDemand:PreferNoSchedule"
This works for me.

Hi,
I having the same issue so I was thinking creating automation which will see if there is an on-demand node is up in the environment and if yes I will add a few spot node so k8s-spot-rescheduler can move the pod to this spot and we will get rid of the on-demand node.
So was thinking can have a parameter which will take the name of spot IG or ASG and if we don't have spot capacity we will scale that IG or ASG(can use CA's code for scaling).


b-table: Template data item shows {{items}} and I think it should be {{item}}

So in the code below- see where I have {{data}} to look at it? When we look at it it has {value: .... , items:} but I think it should be {value:... and item:...} (ellipses is just to help it read easier).  I also think it should include index so it should be {value:..., item: ... , index: ...}
I did dump {{data}} below the html

Here is a dump of the {{data}} variable from above. Note it has items and I think it should be item and its also missing index.
{ "value": 0, "items": [ { "name": "DwfEnkAdvSteel", "inTime": "2021-11-15 11:58:58.000", "status": "76", "alarmTime": "2021-11-15 12:07:18", "expectedCheckinSeconds": 500, "expired": 0, "emailsToAlertCsv"<EMAIL_ADDRESS>"snoozeRepeatSeconds": 3600, "alarmCount": 0 }, { "name": "EnkApdBBackup", "inTime": "2021-11-14 07:25:09.000", "status": "true", "alarmTime": "2021-11-15 07:25:09", "expectedCheckinSeconds": 86400, "expired": 1, "emailsToAlertCsv"<EMAIL_ADDRESS>"snoozeRepeatSeconds": 3600, "alarmCount": 1 } ] }

Are you using the development version or the stable version?

ummmm... just npm install bootstrap-vue-3 . I think I am answering your question

"item" and "index" were added to template only recently. You can either wait for release or use development branch (installed as "npm install bootstrap-vue-3@develop").
And about "items"... It is indeed contains data for all items in the table. I am not sure myself, why it can be needed in cell template. But it was already there when I changed BTable so I left it.


New package: LKH v0.1.0

Registering package: LKH
Repository: https://github.com/chkwon/LKH.jl
Created by: @chkwon
Version: v0.1.0
Commit: 5d53920171355c5e9900bb9c920abb00ea471f3e
Reviewed by: @chkwon
Reference: https://github.com/chkwon/LKH.jl/commit/5d53920171355c5e9900bb9c920abb00ea471f3e#commitcomment-47577175

[noblock] This package is a wrapper of the famous LKH library.  http://webhotel4.ruc.dk/~keld/research/LKH/. Hence the name of the package is LKH.jl.

This package is a wrapper of the famous LKH library. http://webhotel4.ruc.dk/~keld/research/LKH/. Hence the name of the package is LKH.jl.


Added sticky left table header option

I've added the "stickyLeftTableHeader" option that does what the option says. I've added an example in the docs but did not re-compile so the dist folder does not reflect these changes. This was based off ZURB Foundation responsive tables.

Version 5.1? ;)


[PE-D][Tester E] Error message for add - invalid command

When typing an invalid format for add, the error message does not seem relevant as shown below:

Perhaps can consider giving more relevant examples for the error message such as "add c/ cs2103t". The description of the feature does not fix the context of the application

Labels: severity.Medium type.FunctionalityBug
original: tayruxin/ped#2

Situation: The invalid command format is caused due to the add ab3 address book command not being removed
Fix: Removed the add command in the application


Documentation for solid-start

Umbrella issue to track documentation for solid-start at https://docs.solidjs.com/start

[ ] #155
[x] #154
[ ] #141
[ ] #120

https://github.com/solidjs/solid-docs-next/projects/3


Azure consumption costs in ROI calculation?

In terms of cost calculation you don't seem to mention anything about estimating Azure consumption costs. For example, if the calculation is including the reduction in operational costs of the existing data centre, surely it should also include new costs associated with Azure consumption (and not just in support of the migration activities, but Azure costs associated with the Azure landing zone and workloads to be migrated)?
Thanks

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

ID: 42f8649e-4a66-2667-b4c7-88698cf5183f
Version Independent ID: ce9e86a7-423d-7177-685d-ed9f426940b5
Content: Financial model for cloud migration - Cloud Adoption Framework
Content Source: docs/strategy/financial-models.md
Service: cloud-adoption-framework
Sub-service: strategy
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 411645

Estimating cost deltas using the Azure pricing calculator and the Azure TOC calculator is discussed in the previous article. https://docs.microsoft.com/azure/cloud-adoption-framework/strategy/cloud-migration-business-case
Thanks for your feedback.


'FSMap' object has no attribute 'missing_exceptions'

What happened:
I was trying to get my dataset to merge, but I'm unable to access and work with it. It's stored as a zarr directory in S3 right now.
What you expected to happen:
Ideally, I would be able to stream this data and compute the mean without any problems, and have been successful in the past
Minimal Complete Verifiable Example:
s3_file_system = s3fs.S3FileSystem()

def read_zar_file(s3_path, chunks = 'auto', is_consolidated=True):
    # Initilize the S3 file system
    s3_file_system = s3fs.S3FileSystem()
    store = s3fs.S3Map(root=s3_path, s3=s3_file_system, check=False)
    return xr.open_zarr(store=store, consolidated=is_consolidated, chunks = chunks)

failed = []
for file in tqdm(input_dataset_files):
    dataset = read_zar_file(file)
    var = list(dataset.keys())[0]
    dataset[var].mean(dim='time').plot()

Error Traceback
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-10-a33923c4bda1> in <module>
      3     dataset = read_zar_file(file)
      4     var = list(dataset.keys())[0]
----> 5     dataset[var].mean(dim='time').plot()

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/plot/plot.py in __call__(self, **kwargs)
    444
    445     def __call__(self, **kwargs):
--> 446         return plot(self._da, **kwargs)
    447
    448     @functools.wraps(hist)

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/plot/plot.py in plot(darray, row, col, col_wrap, ax, hue, rtol, subplot_kws, **kwargs)
    162
    163     """
--> 164     darray = darray.squeeze().compute()
    165
    166     plot_dims = set(darray.dims)

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/core/dataarray.py in compute(self, **kwargs)
    825         """
    826         new = self.copy(deep=False)
--> 827         return new.load(**kwargs)
    828
    829     def persist(self, **kwargs) -> "DataArray":

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/core/dataarray.py in load(self, **kwargs)
    799         dask.array.compute
    800         """
--> 801         ds = self._to_temp_dataset().load(**kwargs)
    802         new = self._from_temp_dataset(ds)
    803         self._variable = new._variable

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/core/dataset.py in load(self, **kwargs)
    649
    650             # evaluate all the dask arrays simultaneously
--> 651             evaluated_data = da.compute(*lazy_data.values(), **kwargs)
    652
    653             for k, data in zip(lazy_data, evaluated_data):

~/miniconda3/envs/main/lib/python3.6/site-packages/dask/base.py in compute(*args, **kwargs)
    435     keys = [x.__dask_keys__() for x in collections]
    436     postcomputes = [x.__dask_postcompute__() for x in collections]
--> 437     results = schedule(dsk, keys, **kwargs)
    438     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    439

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/client.py in get(self, dsk, keys, restrictions, loose_restrictions, resources, sync, asynchronous, direct, retries, priority, fifo_timeout, actors, **kwargs)
   2723                     should_rejoin = False
   2724             try:
-> 2725                 results = self.gather(packed, asynchronous=asynchronous, direct=direct)
   2726             finally:
   2727                 for f in futures.values():

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/client.py in gather(self, futures, errors, direct, asynchronous)
   1990                 direct=direct,
   1991                 local_worker=local_worker,
-> 1992                 asynchronous=asynchronous,
   1993             )
   1994

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/client.py in sync(self, func, asynchronous, callback_timeout, *args, **kwargs)
    831         else:
    832             return sync(
--> 833                 self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
    834             )
    835

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/utils.py in sync(loop, func, callback_timeout, *args, **kwargs)
    338     if error[0]:
    339         typ, exc, tb = error[0]
--> 340         raise exc.with_traceback(tb)
    341     else:
    342         return result[0]

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/utils.py in f()
    322             if callback_timeout is not None:
    323                 future = asyncio.wait_for(future, callback_timeout)
--> 324             result[0] = yield future
    325         except Exception as exc:
    326             error[0] = sys.exc_info()

~/miniconda3/envs/main/lib/python3.6/site-packages/tornado/gen.py in run(self)
    733
    734                     try:
--> 735                         value = future.result()
    736                     except Exception:
    737                         exc_info = sys.exc_info()

~/miniconda3/envs/main/lib/python3.6/site-packages/distributed/client.py in _gather(self, futures, errors, direct, local_worker)
   1849                             exc = CancelledError(key)
   1850                         else:
-> 1851                             raise exception.with_traceback(traceback)
   1852                         raise exc
   1853                     if errors == "skip":

~/miniconda3/envs/main/lib/python3.6/site-packages/dask/array/core.py in getter()
    104         c = a[b]
    105         if asarray:
--> 106             c = np.asarray(c)
    107     finally:
    108         if lock:

~/miniconda3/envs/main/lib/python3.6/site-packages/numpy/core/_asarray.py in asarray()
     83
     84     """
---> 85     return array(a, dtype, copy=False, order=order)
     86
     87

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/core/indexing.py in __array__()
    489
    490     def __array__(self, dtype=None):
--> 491         return np.asarray(self.array, dtype=dtype)
    492
    493     def __getitem__(self, key):

~/miniconda3/envs/main/lib/python3.6/site-packages/numpy/core/_asarray.py in asarray()
     83
     84     """
---> 85     return array(a, dtype, copy=False, order=order)
     86
     87

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/core/indexing.py in __array__()
    555     def __array__(self, dtype=None):
    556         array = as_indexable(self.array)
--> 557         return np.asarray(array[self.key], dtype=None)
    558
    559     def transpose(self, order):

~/miniconda3/envs/main/lib/python3.6/site-packages/xarray/backends/zarr.py in __getitem__()
     47         array = self.get_array()
     48         if isinstance(key, indexing.BasicIndexer):
---> 49             return array[key.tuple]
     50         elif isinstance(key, indexing.VectorizedIndexer):
     51             return array.vindex[

~/miniconda3/envs/main/lib/python3.6/site-packages/zarr/core.py in __getitem__()
    569
    570         fields, selection = pop_fields(selection)
--> 571         return self.get_basic_selection(selection, fields=fields)
    572
    573     def get_basic_selection(self, selection=Ellipsis, out=None, fields=None):

~/miniconda3/envs/main/lib/python3.6/site-packages/zarr/core.py in get_basic_selection()
    695         else:
    696             return self._get_basic_selection_nd(selection=selection, out=out,
--> 697                                                 fields=fields)
    698
    699     def _get_basic_selection_zd(self, selection, out=None, fields=None):

~/miniconda3/envs/main/lib/python3.6/site-packages/zarr/core.py in _get_basic_selection_nd()
    737         indexer = BasicIndexer(selection, self)
    738
--> 739         return self._get_selection(indexer=indexer, out=out, fields=fields)
    740
    741     def get_orthogonal_selection(self, selection, out=None, fields=None):

~/miniconda3/envs/main/lib/python3.6/site-packages/zarr/core.py in _get_selection()
   1032             lchunk_coords, lchunk_selection, lout_selection = zip(*indexer)
   1033             self._chunk_getitems(lchunk_coords, lchunk_selection, out, lout_selection,
-> 1034                                  drop_axes=indexer.drop_axes, fields=fields)
   1035
   1036         if out.shape:

~/miniconda3/envs/main/lib/python3.6/site-packages/zarr/core.py in _chunk_getitems()
   1664
   1665         ckeys = [self._chunk_key(ch) for ch in lchunk_coords]
-> 1666         cdatas = self.chunk_store.getitems(ckeys)
   1667         for ckey, chunk_select, out_select in zip(ckeys, lchunk_selection, lout_selection):
   1668             if ckey in cdatas:

~/miniconda3/envs/main/lib/python3.6/site-packages/fsspec/mapping.py in getitems()
     92         out = {
     93             k: (KeyError() if isinstance(v, self.missing_exceptions) else v)
---> 94             for k, v in out.items()
     95         }
     96         return {

~/miniconda3/envs/main/lib/python3.6/site-packages/fsspec/mapping.py in <dictcomp>()
     92         out = {
     93             k: (KeyError() if isinstance(v, self.missing_exceptions) else v)
---> 94             for k, v in out.items()
     95         }
     96         return {

AttributeError: 'FSMap' object has no attribute 'missing_exceptions'

Anything else we need to know?:
This script has worked in some cases as well and was working until today. Without more clarification, I don't know what might be relevant and what might not be.
Environment:
Output of xr.show_versions()

INSTALLED VERSIONS
commit: None
python: 3.6.10 |Anaconda, Inc.| (default, Jan  7 2020, 21:14:29)
[GCC 7.3.0]
python-bits: 64
OS: Linux
OS-release: 5.4.0-1029-aws
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: C.UTF-8
LOCALE: en_US.UTF-8
libhdf5: 1.10.4
libnetcdf: 4.6.1
xarray: 0.15.0
pandas: 0.25.3
numpy: 1.18.1
scipy: 1.4.1
netCDF4: 1.4.2
pydap: None
h5netcdf: 0.8.1
h5py: 2.10.0
Nio: None
zarr: 2.5.0
cftime: 1.2.1
nc_time_axis: None
PseudoNetCDF: None
rasterio: 1.1.0
cfgrib: None
iris: None
bottleneck: 1.3.2
dask: 2.11.0
distributed: 2.30.0
matplotlib: 3.1.3
cartopy: None
seaborn: None
numbagg: None
setuptools: 50.3.0.post20201006
pip: 20.2.4
conda: None
pytest: None
IPython: 7.16.1
sphinx: None

Hi @v2thegreat — this looks like an issue with fsspec or zarr — xarray is calling np.asarray(array[self.key], dtype=None) half way down the stack trace and then zarr & fsspec are responsible for the rest.
One immediate thing to do is to upgrade your deps versions to the latest — some of those are not recent.
We recognize these sorts of errors are difficult to pinpoint, and it's something we're thinking about how to improve.

Alright, I'll try that out and let you know. Do you have any idea what change might've caused this? I recently installed the latest for tpot for python 3.6. Do you suggest that I upgrade everything for python 3.8 to get everything as the latest?

I think most libraries still support 3.6 (just) — so I would focus on upgrading any library on that stack trace to the latest release, and don't worry too much about 3.8 yet.

Nope, I ran conda update --all and it updated everything, and I'm still getting the same error

Your best bet is putting an issue in on zarr — keen to be helpful — but this really doesn't look like an xarray issue, unfortunately

I opened this issue in zarr as you mentioned. I'll let you know if I come up with a solution

Thanks for the bug report. This is the same as dask/gcsfs#299
The solution is to upgrade fsspec to to version >= 0.8.4. Please try that and report back. I'll close this and we can continue discussion in zarr-developers/zarr-python#646.


Remove custom iterator; replace with slice::Iter

Replaced the iterators with slice::Iter and slice::IterMut. My rationale for this change has two main points:

An iterator over the contents of a StaticVec can't benefit from knowledge of N, since it internally just tracks start and end, which are based on the current length. It's not clear to me how a StaticVec iterator can ever benefit from knowledge of N or even need to be aware of it in the first place.
Because the implementations are basically identical, it makes more sense to defer to slice::Iter, which is reliably very tightly designed and optimized, since iterating over slices is one of the most common operations in rust.  This includes implementations of internal optimization trains and of many of the iterator methods

Part of a series of pull requests to split #11 into more easily reviewed parts

I can't account for the build failure; it seems that cargo bench was randomly SIGKILLed

Yeah, I was testing some different stuff with Clone and I had committed a  > that needed to be an >=. As far as removing the iterators though, I know they seem a bit redundant right now, but they won't be forever. I've got a lot of ideas for methods for them (that don't exist on the Slice iterators) and other various const-y stuff I intend to slowly ease in.
Plus, with the deref impl, StaticVec has direct access to those iterators anyways if anyone wants it.

As far as removing the iterators though, I know they seem a bit redundant right now, but they won't be forever. I've got a lot of ideas for methods for them (that don't exist on the Slice iterators) and other various const-y stuff I intend to slowly ease in.

These would be API breaking changes anyway, right? Since adding consty stuff to the iterators (still unclear on what that looks like) would at the very least would require adding  as a template parameter to the iterator.

These would be API breaking changes anyway, right? Since adding consty stuff to the iterators (still unclear on what that looks like) would at the very least would require adding <N> as a template parameter to the iterator.

I'm don't think the actual generic constraints for the iterators are something anyone needs to specify directly very often at all, so I'm not sure it would be breaking. What I have in mind was moreso based on methods with const generic parameters (or methods that are just const fns, or methods that are both if they ever allow it.)
We can leave this PR open for now if you want as it doesn't really matter either way, but at this point I don't think I'm going to merge it any time soon (and I feel bad in saying that as I really appreciate your contributions so far.)
Bear with me for a while and hopefully you'll see what I'm getting at.

I'm gonna close this now, just because even in the event we did end up revisiting the concept at some point it'd make more sense to do it from a new branch regardless.

Thanks for your consideration! I totally understand having other plans in the works. I'll keep an eye on the iterators and see where they land


Installation Error

Following the instructions in the documentation, I getting an error during installation.
I have the setup on MacOS
trading_view node -v
v18.7.0

trading_view npx @alleyway/create-tradingview-alerts-home
@alleyway/create-tradingview-alerts-home.. version: 1.6.0
✔ Choose which action you'd like to do: › Initialize in current folder
Adding file: HOWTO.txt
Adding file: blacklist.csv
Adding file: config.yml
Adding file: package.json
Adding file: atat
Installing dependencies
npm ERR! code ENOSYS
npm ERR! syscall symlink
npm ERR! path<EMAIL_ADDRESS>npm ERR! dest /Users/januj/Amazon WorkDocs Drive/My Documents/workspace/trading_view/node_modules/.bin/atat
npm ERR! errno -78
npm ERR! ENOSYS: function not implemented, symlink<EMAIL_ADDRESS>-> '/Users/januj/Amazon WorkDocs Drive/My Documents/workspace/trading_view/node_modules/.bin/atat'

npm ERR!      /Users/januj/.npm/_logs/2022-08-09T18_43_25_537Z-debug-0.log
Error: Command failed: npm --loglevel=error --no-package-lock update
    at checkExecSyncError (node:child_process:828:11)
    at execSync (node:child_process:899:15)
    at initializeMain (file:///Users/januj/.npm/_npx/5455a11893b177f3/node_modules/@alleyway/create-tradingview-alerts-home/dist/index.js:106:9) {
  status: 178,
  signal: null,
  output: [ null, null, null ],
  pid: 82749,
  stdout: null,
  stderr: null
}
done

Don't know if I am doing something wrong, or something that needs to be looked at from a code's perspective.

noticed the Amazon WorkDocs Drive it's likely because of this which probably uses a different filesystem not capable of making sym links


Curate export list

Currently my strategy is to export anything that doesn't conflict with any other modules I'm exporting. That's not great, as I noted here: https://github.com/tfausak/purescript-batteries/pull/15#discussion_r42891749. I should make a pass through the exports and make sure they all make sense to export.

As part of this, I would like to document the exports. First pass could list them. Next pass could add types. Next pass could add links to the package they came from. And so on...
That sounds like a lot of work, though. And potentially hard to keep in sync. So I'll keep it in mind and open another issue when I want to do that.

This could take a while, Batteries exports over 1,000 things.

If you split up the different passes into tickets, I'd be willing to tackle some of it while you do others. For instance, once you've figured out what to export from Data.List, I could go back through and add links or whatever that you wanted (given there is an example of what you want accomplished first).

I added a raw list of exports in c8bebbca3c7932a1aa7da4020e78312db45cd6b0. I think adding types might be unnecessary, since you can search by name or type on Pursuit. Also if the docs link to where the function came from, that place will have the type. So I think adding links is really all I want to do with regards to documentation. I'll make an issue for that.

Even with the performance considerations I mentioned, or am I just imagining things? That is, in Haskell, I'd be 100% for polymorphic functions, but since that gets compiled down to a manually passed around instance dict, I'd be nervous. If you're convinced that worrying about performance is premature, I'll continue the work I was later this week (buried under school work and real work).

I'd rather have slow, convenient functions that fast, cumbersome ones. If you're using a polymorphic function and recognize that it's slowing you down, you can easily switch it for the monomorphic version.

Perhaps raising that caveat would be good for new comers. Something like "note: While polymorphic functions are more convenient than their monomorphic variants, they are slower. If you find that your application is experiencing considerable slow downs, a quick way to improve performance is to switch to the monomorphic variants where necessary."
Actually, if people are typing their functions, specializing them at the call site should be sufficient enough to avoid the performance penalty, right? Not sure why that didn't occur to me, assuming I'm correct!

raising that caveat would be good for new comers

Agreed. Although probably not really necessary until this package hits 1.0.

specializing them at the call site should be sufficient enough to avoid the performance penalty

That's definitely worth investigating. I have no idea.

I was wrong about the specializing stuff :-(

I am not planning on addressing this anymore. Batteries will continue to export everything it can. If you want a curated export list, you can depend on Batteries and make your own prelude.

make your own prelude

Sounds fair. Simple enough as well.
On Fri, Jan 29, 2016 at 2:54 PM, Taylor Fausak<EMAIL_ADDRESS>wrote:

Closed #16 https://github.com/tfausak/purescript-batteries/issues/16.
—
Reply to this email directly or view it on GitHub
https://github.com/tfausak/purescript-batteries/issues/16#event-531827197
.

--
Regards,
Edwin O Marshall (aspidites)
http://github.com/aspidites https://github.com/aspidites
http://bitbucket.org/aspidites https://bitbucket.org/aspidites
http://www.assembla.com/profile/aspidites?public=true


[Enhancement] fix stream load log format

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：
Add blank to separate error message and brief description

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_be_unittest

run starrocks_admit_test


Unknown type resolution does not work recursively

I try to implement a function that resolves my service registration on demand by using Stashbox' WithUnknownTypeResolution feature. Look at the following classes:
	[UsedImplicitly]
	public class BillingPeriodService : BaseServiceWithUnitOfWork
	{
		public BillingPeriodService(IServiceContextWithUnitOfWork serviceContext, AccountService accountService)
			: base(serviceContext)
		{

	[UsedImplicitly]
	public class AccountService : BaseServiceWithUnitOfWork
	{
		public AccountService(IServiceContextWithUnitOfWork serviceContext)
			: base(serviceContext)
		{

	[UsedImplicitly]
	public class ServiceContextWithUnitOfWork : ServiceContext, IServiceContextWithUnitOfWork
	{
		public ServiceContextWithUnitOfWork(IObjectProvider objectProvider)
			: base(objectProvider)
		{

When I try to resolve BillingPeriodService, my UnknownTypeResolution-function is invoked with a context to BillingPeriodService. I can check my service descriptors and complete the registration context with correct lifetime and implementation type. After that, I get an exception that the type not be resolved. I would expect that my UnknownTypeResolution-function is invoked again and again for all required constructor parameters...?

Is this still an issue with the latest pre-release version? A covered issue could have led to this, could you please check again? Thanks!

Yes, the issue is still there with https://github.com/z4kn4fein/stashbox/commit/34d7caf469566106dd790d72e812883eeaf97874

Okay, I'm moving forward to this then, thanks!

Hey, the issue was that the UnknownTypeResolver was not able to resolve your IServiceContextWithUnitOfWork because it's an interface type, so it was bypassed by the resolver completely. I turned off this behavior when the configuration delegate for the unknown type resolution is set, so it will be called for the interfaces too. Could you please try the new version? Thanks!

There is a new side effect now.
My code gets an InvalidRegistrationException when I try to get an "optional" interface value from the container using Resolve<ISomeInterface>(true). In this case, it's correct that the UnknownTypeResolver is not able to resolve this type, but that's fine as null is allowed here.

Hey, thanks for reporting, that side effect should be covered now, could you check please? Thanks!

This seems to work now, but another issue (not sure if this is caused by the fix): services registered with Lifetime.NamedScope are not found if you try to resolve them form a different scope, regardless if registered at startup or in UnknownTypeResolver.

Sorry for the late response, thanks for reporting these!
That's a by-design thing, services registered with NamedScope are only picked when you resolve them within the scope that has the matching name. That's kind of a resolution condition also. In what case you consider this as an issue? Should it work differently in your opinion?
Could you give me an example of the Singleton issue? I'm not able to reproduce that. Thanks!

I have several services that are registered as "Singleton". In the current implementation, they all share their dependencies and are registered in the same scope. For example, they all use the same DbContext. So my idea was to register the services into a separate "named scope", to isolate them from each other.

Sorry, i think i wasn't clear with this one, i meant that could you please send me a code example or a sample project where the dispose issue with the singletons are reproducable? I did not find any composition to recreate this kind of issue. Singletons are disposed only by the root scope, and I can't see where could be the behavior changed.

I think my Dispose problem was caused by my very strange tries to register Singletons in a Named Scope, sorry for the confusion. I have changed my code to make sure that the Singleton dependencies are registered with Transient scope instead of Scoped/NamedScope. It seems to work now, if I run into new issues, I will create a new issue here.
Thank you for fixing everything :-)


Use 64 bit addresses in bit_address

This is a hot fix for intermittent crashes in bitstream generation for ql_memory_bank caused by selecting an incorrect address size.  I believe using 64 bit addresses in all cases should have no problems outside of increasing the bitstream file size.

Motivate of the pull request

[ ] To address an existing issue. If so, please provide a link to the issue:
[ ] Breaking new feature. If so, please describe details in the description part.

Describe the technical details
What is currently done? (Provide issue link if applicable)

What does this pull request change?

Which part of the code base require a change

[ ] VPR
[ ] Tileable routing architecture generator
[ ] OpenFPGA libraries
[ ] FPGA-Verilog
[x] FPGA-Bitstream
[ ] FPGA-SDC
[ ] FPGA-SPICE
[ ] Flow scripts
[ ] Architecture library
[ ] Cell library
[ ] Documentation
[ ] Regression tests
[ ] Continous Integration (CI) scripts

Impact of the pull request

[ ] Require a change on Quality of Results (QoR)
[ ] Break back-compatibility. If so, please list who may be influenced.

Hi @tangxifan, I replicated the failing checks on this branch locally; it seems like the current version of vpr doesn't like the --openfpga_fast_configuration flag used in some of the tests?

@ganeshgore
could we upstream this change? I don't have a publicly available test case at the moment, but the variable address length is causing crashes on some architectures that this change resolves.  There's a slight memory overhead associated with it, but I think for most users it's not significant.

@ganeshgore could we upstream this change? I don't have a publicly available test case at the moment, but the variable address length is causing crashes on some architectures that this change resolves. There's a slight memory overhead associated with it, but I think for most users it's not significant.

Disagree. I think it is important to support all the configuration protocols we have. Also if there are no test cases to validate. It will hurt QoR.

@ganeshgore could we upstream this change? I don't have a publicly available test case at the moment, but the variable address length is causing crashes on some architectures that this change resolves. There's a slight memory overhead associated with it, but I think for most users it's not significant.

Disagree. I think it is important to support all the configuration protocols we have. Also if there are no test cases to validate. It will hurt QoR.

That's okay.  I'll create a minimum failing example and work on addressing the bug in that code that was causing it.  However, I don't think that this will break other configuration protocols, will it? I tried at least on ccff and ql_memory_bank without issue.

@scott-temple I believe the hotfix causes some existing reg test failures. It is a functional problem now. As you can see, that is why I did not use size_64 directly.

@scott-temple I believe the hotfix causes some existing reg test failures. It is a functional problem now. As you can see, that is why I did not use size_64 directly.

@tangxifan Thanks.  When I replicated the failing regression tests locally a week or two ago they all failed with or without the change with a message from VPR saying --fast_configuration was an unknown flag. Removing the flag from the openfpga script caused them to pass. I assumed that meant the failures were unrelated to this code change, but I haven't looked deeply into what's causing the failures.

@scott-temple I checked the reg test failures. Currently, they are not related to --fast_configuration. The failed test cases are mainly on wrong bitstream was generated or bitstream generation aborts. You may check the details in the CI.

@chungshien, I believe this PR is also not necessary for your new solution.
Please confirm and we can close it.

No. We do not need this.
We should generate exact WL bits size as original implementation of openfpga.
When I look at the code, I always wonder why we want to pad WL bits size to be 64bits-alignment.
I did talk to Muhammad few days ago (or last week) if this is because of our HW requires that, and he confirm this is not required by our HW. He even said that "we are not using the wl-address from the file".
Hence in the code that I implement, I do not do such padding -- the WL size that I generated match with original OpenFPGA implementation.
We can close this

@chungshien @alain-rs Thanks for confirmation. Close the PR now. The branch is kept in case you need in future.


Can not connect to k8s cluster after version 3.1.0

Describe the bug
Can not connect to k8s cluster (aks china) after version 3.1.0
Screenshots

**Environment

Lens Version: 3.3.1
OS: windows 10 pro
Installation method: release exe

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
info: Checking for update
info: Update for version 3.3.1 is not available (latest version: 3.3.1, downgrade is disallowed).
(node:23352) UnhandledPromiseRejectionWarning: Error: spawn UNKNOWN
    at ChildProcess.spawn (internal/child_process.js:394:11)
    at Object.spawn (child_process.js:548:9)
    at env (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\webpack:\src\main\kube-auth-proxy.ts:54:17)
    at C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:641406
    at Object.next (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:641511)
    at a (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:640228)
(node:23352) UnhandledPromiseRejectionWarning: Error: spawn UNKNOWN
    at ChildProcess.spawn (internal/child_process.js:394:11)
    at Object.spawn (child_process.js:548:9)
    at env (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\webpack:\src\main\kube-auth-proxy.ts:54:17)
    at C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:641406
    at Object.next (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:641511)
    at a (C:\Users\XXXX\AppData\Local\Programs\kontena-lens\resources\app.asar\main.js:1:640228)
(node:23352) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:23352) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:23352) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:23352) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
error: Failed to connect to cluster bwntest: {"name":"RequestError","message":"Error: ESOCKETTIMEDOUT","cause":{"code":"ESOCKETTIMEDOUT","connect":false},"error":{"code":"ESOCKETTIMEDOUT","connect":false},"options":{"json":true,"timeout":10000,"headers":{"host":"4a010d12-a8f4-401b-876f-68165e9a952c.localhost:49153"},"uri":"http://<IP_ADDRESS>:49153/api-kube/version","simple":true,"resolveWithFullResponse":false,"transform2xxOnly":false}}

kubectl can connect

I have the same issue. After the 3.1.0 I cannot connect to the cluster!

I'm also on 3.3.1 but on MacOSX. It seems I cannot connect to any configuration (neither GKE, EKS or OIDC). I also get timeouts.

I think this is the same
https://github.com/lensapp/lens/issues/238
Though, apparently, the fix did not work

3.4.0-beta.2 same issue

It'd be nice if there was a way to turn off the auto-update so we could continue to use an actual working version.

3.4.0 same problem

Do you all see the same error message?
(node:23352) UnhandledPromiseRejectionWarning: Error: spawn UNKNOWN
    at ChildProcess.spawn (internal/child_process.js:394:11)
    at Object.spawn (child_process.js:548:9)

I fixed issue by removing bundled kubectl and put a symlink to the kubectl from the PATH

I fixed issue by removing bundled kubectl and put a symlink to the kubectl from the PATH

@davydkov  Thanks your workaround!
On windows you can close lens first and delete all files and  folders in the target folder:
C:\Users[username]\AppData\Roaming\Lens\binaries\kubectl  .
Then open lens and waiting for the kubectl auto download finish, and hit reconnect.

Is this still a problem in 4.1.4?

I haven't encountered it after I cleaned up the binary

Okay thanks for the update. I think I'll close this and if someone encounters this again they can open a new issue.


Update reporter.js

I've added comments to explain what each section of the code is doing, and I've also made the code a bit more readable by using descriptive variable names and formatting.

Sorry but these changes don’t meaningfully improve the code (and in most cases make it worse with overly verbose comments)


feat: support array containment @>, <@

Is your feature request related to a problem? Please describe.
This is a subfunction of #7117
This is appropriate as my good first issue
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Infact pgsql has type range but risingwave does not have , but this operator  usage like this:

Is there necessary to add array contains element ? I try it in pgsql and it;s not ok:

Or Just Keep the behavior consistent with pgsql？
cc @

Hi. We'll keep consistent with pg and we are going to add array @> array soon. This should be able to support array containment. There will be no array contains element operation for this.

Hi. We'll keep consistent with pg and we are going to add array @> array soon. This should be able to support array containment. There will be no array contains element operation for this.

I have done this and I will push a mr soon

Closed by https://github.com/risingwavelabs/risingwave/pull/13253


Generate function assist puts .await and ? in the wrong order

When generating an async fn that returns a Result with "generate function", rust-analyzer replaces the previous code with fun_name(/* arguments... */)?.await. It should be .await?.

Hey @flodiebold, can I take this up?

It's yours!

Nice, thanks, I am still confused a bit, is it possible I could get a MRE?

I would guess it is something like:
async fn foo() -> Result<(), ()> {
    Ok(())
}

and then extracting Ok(()) as new function using an assist.

Shifted discussion to https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/Issue.20.2310333


Revert "lz4 seems to be unused here."

Reverts vespa-engine/vespa#12467
Please review only. In case this doesn't work, see discussion in  vespa-engine/vespa#12467.

Seems the first one was OK, closing.


Ref

Fix reference in io manual.
Add note to KIT readers.

Other than my minor gripe, LGTM with my limited knowledge of that system

thanks @teonlamont


Create a blank conversation

Is your feature request related to a problem? Please describe.
Similar to ChatGPT, users should be able to store past conversations, and create blank ones.
Describe the solution you'd like
We should provide:

A button to create a new conversation
A "chat history" view allowing users to open previous conversations
Everything is stored in local storage.

Closed by #175


Manual Summary Shows Image alt Text

v0.116.1
Blog summaries set manually with <!--more--> cause image alt text to show in the summary -
If I have the following blog post
![Database Image](database.png)

Manual summary shows the image alt text
<!--more-->

the summary shows as follows -

If I don't manually set the summary and remove <!--more--> , the alt text does not show -

I am unable to reproduce the behavior as described. Please try this:
git clone --single-branch -b hugo-github-issue-11703 https://github.com/jmooring/hugo-testing hugo-github-issue-11703
cd hugo-github-issue-11703
hugo server

Files of interest:

content/_index.md (the markdown)
layouts/_default/home.html (the template that calls .Summary)

@jmooring I am also unable to reproduce this issue. I haven't seen it pop up again since the day after I reported the issue!


Update Checklist

We need to update the checklist to be in sync with some of the new content across the guide:
http://webguide.ucsb.edu/web-standards-checklist/

I find "Design websites for display adapters capable of at least 1024 x 768 pixels screen resolution" to be a odd item.


SPY-1037: sizing the #slices used in parallelize() call of ParquetRelation#mergeSchemasInParallel

@markhamstra
@davidnavas

I think we can further narrow the parallelism calculation to none s3 Path.
    // Use the first file as an indicator to see if we are dealing with s3.
    // if it is on s3, use the defaultParallelism from sparkContext,
    // otherwise we size it properly.
    val parallelism = partialFileStatusInfo.headOption.filter(!_._1.startsWith("s3")).map( _ =>
      math.min(
        math.max(1, partialFileStatusInfo.length),
        sqlContext.sparkContext.defaultParallelism)
    ).getOrElse(sqlContext.sparkContext.defaultParallelism)

I'm concerned about what happens when defaultParallelism is not set and we are dealing with s3.  Then we will launch as many Tasks as we have cores, which has the potential to tie up many, even all, cores for the duration of a read from s3.  I don't think we want to risk blocking other Jobs in that way.

The current s3 optimization is too extreme.
Should we introduce a new parameter for that? Did we introduce our own configuration to csd-spark?

That's kind of what I am thinking, that a different config variable than sparkContext.defaultParallelism may be needed for this default, one more specific or maybe exclusive to reading parquet schemas.

the parquet specific config property naming from http://spark.apache.org/docs/latest/sql-programming-guide.html is suggesting something like "spark.sql.parquet.*"
I am thinking about spark.sql.parquet.mergeSchema.parallelism!

jttp


darktable: 4.6.1 -> 4.8.0

Description of changes
Update darktable to the latest.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofBorg build darktable

I upgraded yesterday and did some light editing, and it seemed fine to me, with OpenCL and the nvidia proprietary driver.
On June 22, 2024 5:10:48 AM PDT, Freya Arbjerg @.***> wrote:

@freyacodes commented on this pull request.
Ever since I started running this version, my config directory seems to be corrupted in such a way that darktable does not render images (except some thumbnails). This persisted with a downgrade to 4.6.1 (and a restore of library.db). This is both the case with and without OpenCL. This renders darktable unusable.
I am unable to reproduce the issue with a fresh darktable config dir. Darktable seems to work fine under default configuration.
I am wondering if anyone else is experiencing such an issue? I will try to put together a proper bug report for the upstream once I have the time.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/321614#pullrequestreview-2133793029
You are receiving this because you authored the thread.
Message ID: @.***>

@freyacodes there have been a lot of changes in the last two version to openCL and thumbnail generation.
If you suspect something with library.db, you can try and do a few things with sqlite like vacuum.
You can also blow away the cached thumbnails and let the regenerate, same for the openCL kernels.
Finally you can diff you nonworking darktablerc vs a fresh one and see what's changed between the two.


Change vault timestamps

This PR introduces two timestamp fields to vault
table and filled them using the block time
in order to have same values for all participants:
funded_at: time of the block containing the deposit
and moved_at: time of the block containing the last
vault transaction.
This PR introduces also delegated_at
and secured_at which are storing local time
from the user side when a vault is secured and
delegated.

If we still need updated_at for offchain updates then i think it's cleaner to have two different fields.

ACK d5ec51f93b09d8eea643f7a6f8d34807e7e61bda

I could not reproduce the panic on master, so i think it was introduced in this PR.

Can you rebase on master so that the CI isn't flaky anymore?


Fix debug asserts for dwarf transform

Fixes #1408
The refactored debug_assert! was poorly designed / afterthought. The PR fixes that by properly checking the iterator item order invariant. Not sure if it requires a test.

We probably don't need to optimize too too much here, so could the #[cfg] be replaced with if cfg!(...)?


chore: Release v1.9.31

This is a promotion branch for the release v1.9.31

/build-deploy-preview skipTests=true

/ok-to-test

@sbalaji1192 - Date_column_editing_1_spec is known failure & fixing this in an open PR now.

/build-deploy-preview skipTests=true

/ok-to-test

/ok-to-test

/ok-to-test


Add Kea, SLS, SMD and heuristic lookup tables to fill out LLDP data for cabling reports and validation

Summary and Scope
Description:
Originally the canu report switch cabling and canu report network cabling commands used LLDP, ARP and MAC address table data from switches, with LLDP data being canonical.  This posed a problem when a device did not run LLDP or LLDP data didn't return anything particularly useful.
This change allows the addition of system metadata and "heuristics" of typical device use to annotate the LLDP data.  The following lookup data can be used and is listed in priority order:

If Kea lease data is available it is used to match an LLDP MAC with a system hostname, then
If SLS data is available it is used to match ARP IP data with a system hostname, then
If SMD data is available it is used to match LLDP MAC addresses with a system hostname, then
Heuristic lookups of the MAC are used to annotate the LLDP and ARP data with hostnames, slots, ports and lags that are valid for Plan of Record systems and devices.  Heuristics are a Pareto's rule.

None of the new lookup tables or flags are required, but are used in the above order if applied.
The new command line often looks like:
 canu report network cabling --ips <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --kea-lease-file kea.json --sls-file sls.json --smd-file smd.json --heuristic-lookups

To obtain the Kea lease JSON file after obtaining a token:
curl -H "Authorization: Bearer ${TOKEN}" -X POST -H "Content-Type: application/json" -d '{ "command": "lease4-get-all",  "service": [ "dhcp4" ] }' https://api_gw_service.local/apis/dhcp-kea | jq -S . > kea.json

To obtain the SLS JSON file:
cray sls dumpstate list --format json | jq -S . > sls.json

To obtain the SMD JSON file:
cray hsm inventory ethernetInterfaces list --format json | jq -S . > smd.json

Original report:
$ canu report switch cabling --ip <IP_ADDRESS>
Password:
Switch: sw-spine-001 (<IP_ADDRESS>)
Aruba 8325
------------------------------------------------------------------------------------------------------------------------------------------------------
PORT        NEIGHBOR       NEIGHBOR PORT      PORT DESCRIPTION                                      DESCRIPTION
------------------------------------------------------------------------------------------------------------------------------------------------------
1/1/1   ==>                14:02:ec:da:b9:98  No LLDP data, check ARP vlan info.                    Hewlett Packard Enterprise<IP_ADDRESS>:vlan2, <IP_ADDRESS>:vlan4
1/1/3   ==>                14:02:ec:da:b8:18  No LLDP data, check ARP vlan info.                    Hewlett Packard Enterprise<IP_ADDRESS>:vlan2, <IP_ADDRESS>:vlan4
1/1/5   ==>                14:02:ec:d9:79:e8  No LLDP data, check ARP vlan info.                    Hewlett Packard Enterprise<IP_ADDRESS>:vlan2
1/1/7   ==> ncn-w001       14:02:ec:d9:7c:40  bond0                                                 Linux ncn-w001 5.3.18-150300.59.87-default #1 SMP Thu
1/1/8   ==> ncn-w002       14:02:ec:d9:76:b8  bond0                                                 Linux ncn-w002 5.3.18-150300.59.87-default #1 SMP Thu
1/1/10  ==>                14:02:ec:d9:7c:9b                                                        Hewlett Packard Enterprise
1/1/11  ==>                14:02:ec:d9:7c:88  No LLDP data, check ARP vlan info.                    Hewlett Packard Enterprise<IP_ADDRESS>:vlan2, <IP_ADDRESS>:vlan2, <IP_ADDRESS>:vlan4
1/1/12  ==>                14:02:ec:d9:7b:db                                                        Hewlett Packard Enterprise
1/1/13  ==>                14:02:ec:d9:7b:c8  No LLDP data, check ARP vlan info.                    Hewlett Packard Enterprise<IP_ADDRESS>:vlan2, <IP_ADDRESS>:vlan4
1/1/14  ==>                14:02:ec:d9:76:9b                                                        Hewlett Packard Enterprise
1/1/15  ==>                14:02:ec:d9:76:9a                                                        Hewlett Packard Enterprise
1/1/19  ==>                14:02:ec:e1:bd:ba                                                        Hewlett Packard Enterprise
1/1/47  ==> sw-spine-002   1/1/47             VSX keepalive                                         Aruba JL635A  GL.10.09.0010
1/1/48  ==> sw-leaf-bmc-0011/1/49             sw-spine-001:48<==sw-leaf-bmc-001                     Aruba JL663A  FL.10.11.1005
1/1/51  ==> sw-spine-002   1/1/51             vsx isl                                               Aruba JL635A  GL.10.09.0010
1/1/52  ==> sw-spine-002   1/1/52             vsx isl                                               Aruba JL635A  GL.10.09.0010
1/1/55  ==> sw-edge-002    Ethernet1/1                                                              Arista Networks EOS version 4.23.0F running on an Aris
1/1/56  ==> sw-edge-001    Ethernet1/1                                                              Arista Networks EOS version 4.23.0F running on an Aris

New report with metadata from Kea, SMD, SLS and general general heuristic hints:
canu report network cabling --ips <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --kea-lease-file kea.json --sls-file tsls.json --smd-file smd.json --heuristic-lookups

Switch: sw-spine-001 (<IP_ADDRESS>)
Aruba 8325
------------------------------------------------------------------------------------------------------------------------------------------------------
PORT        NEIGHBOR       NEIGHBOR PORT      PORT DESCRIPTION                                      DESCRIPTION
------------------------------------------------------------------------------------------------------------------------------------------------------
1/1/1   ==> ncn-m001       14:02:ec:da:b9:98  Kea data: Hostname from MAC                           Hewlett Packard Enterprise
1/1/3   ==> ncn-m002       14:02:ec:da:b8:18  Kea data: Hostname from MAC                           Hewlett Packard Enterprise
1/1/5   ==> ncn-m003       14:02:ec:d9:79:e8  Kea data: Hostname from MAC                           Hewlett Packard Enterprise
1/1/7   ==> ncn-w001       14:02:ec:d9:7c:40  bond0                                                 Linux ncn-w001 5.3.18-150300.59.87-default #1 SMP Thu
1/1/8   ==> ncn-w002       14:02:ec:d9:76:b8  bond0                                                 Linux ncn-w002 5.3.18-150300.59.87-default #1 SMP Thu
1/1/10  ==>                14:02:ec:d9:7c:9b  Heuristic data: Often a OCP card port                 Hewlett Packard Enterprise
1/1/11  ==> ncn-s001       14:02:ec:d9:7c:88  Kea data: Hostname from MAC                           Hewlett Packard Enterprise
1/1/12  ==>                14:02:ec:d9:7b:db  Heuristic data: Often a OCP card port                 Hewlett Packard Enterprise
1/1/13  ==> ncn-s002       14:02:ec:d9:7b:c8  Kea data: Hostname from MAC                           Hewlett Packard Enterprise
1/1/14  ==>                14:02:ec:d9:76:9b  Heuristic data: Often a OCP card port                 Hewlett Packard Enterprise
1/1/15  ==>                14:02:ec:d9:76:9a  Heuristic data: Often a OCP card port                 Hewlett Packard Enterprise
1/1/19  ==>                14:02:ec:e1:bd:ba  Heuristic data: Often a OCP card port                 Hewlett Packard Enterprise
1/1/47  ==> sw-spine-002   1/1/47             VSX keepalive                                         Aruba JL635A  GL.10.09.0010
1/1/48  ==> sw-leaf-bmc-0011/1/49             sw-spine-001:48<==sw-leaf-bmc-001                     Aruba JL663A  FL.10.11.1005
1/1/51  ==> sw-spine-002   1/1/51             vsx isl                                               Aruba JL635A  GL.10.09.0010
1/1/52  ==> sw-spine-002   1/1/52             vsx isl                                               Aruba JL635A  GL.10.09.0010
1/1/55  ==> sw-edge-002    Ethernet1/1                                                              Arista Networks EOS version 4.23.0F running on an Aris
1/1/56  ==> sw-edge-001    Ethernet1/1                                                              Arista Networks EOS version 4.23.0F running on an Aris

Additional changes:

Added logging to canu report switch cabling

PR checklist (you may replace this section):

[ ] I have run nox locally and all tests, linting, and code coverage pass
[ ] I have added new tests to cover the new code
[ ] My code follows the style guidelines of this project
[ ] If adding a new file, I have updated pyinstaller.py
[ ] I have updated the appropriate Changelog entries in README.md

Issues and Related PRs

Resolves: Issue
Relates to: Issue
Requires: Issue

Testing
Tested on:

Tested on Fanta (Dellanox) without issue.


License check queue

All of the apps that still need license tags. I will also try to add more homepages at the same time.

[x] Artsy Shows
[x] EX Player
[ ] Provenance
[x] UitzendingGemist by jeffkreeftmeijer
[ ] WWDCTV
[ ] BaiduFM-Swift
[x] Bither
[x] Brew
[ ] Bus Today
[ ] Calculator by noodlewerk
[ ] Calculator by mukeshthawani
[x] Cherry
[x] Connectivity Demo
[x] CoolSpot
[x] Cortado
[x] Done
[x] FlickrWatch
[x] GrandCentralBoard
[ ] Gulps
[ ] heartrate
[x] HighStreet
[ ] HN Reader
[ ] Impulse
[ ] KTPomodoro
[ ] Lister
[x] Natural Language Clock
[x] OnTime
[x] Parties for WWDC
[ ] PhoneBattery
[x] PhotoWatch
[ ] Soon
[x] WatchKit-Apps
[ ] Watchman
[ ] WatchNotes
[x] watchOS-2-Sampler
[x] WatchPics
[ ] WatchSnake
[ ] WatchStocks
[x] Wunderschnell
[x] Brave
[ ] Endless Browser
[x] Firefox
[ ] Frameless
[x] Actor
[x] BLEMeshChat
[ ] Chats
[x] ChatSecure
[ ] Colloquy
[ ] IRCCloud
[ ] M
[x] Mumble
[x] Rocket.Chat
[ ] Signal
[ ] surespot
[ ] Telegram
[x] TextEthan
[x] EventBlankApp
[ ] NortalTechDay
[ ] ParseDeveloperDay
[ ] RWDevCon
[ ] trySwiftApp
[x] Valio
[ ] Adblock Fast
[ ] Adblock Plus
[x] BlockParty
[x] Focus
[x] AppLove
[ ] Bequest
[ ] Codinator
[ ] Charter
[ ] CI2Go
[x] Review Time
[ ] TLDR Man Page
[x] wat
[x] Github-Swift
[ ] Monkey
[x] MrCode
[ ] OctoPodium
[x] BitStore
[x] breadwallet
[ ] Buck Tracker
[x] Coins
[ ] Concurrency
[x] doughwallet
[x] Savings Assistant
[ ] TodayStocks
[ ] ToThePenny
[ ] 翻翻看
[x] 2048 in Objective-C
[x] 2048 in Swift
[ ] Bridges
[ ] Canabalt
[x] CardsAgainst
[ ] Chess
[x] CodeCombat
[ ] Chuck
[ ] DOOM
[ ] DOOM-IOS2
[ ] Dungeon Crawl
[x] Five In A Row (五子棋)
[ ] FlappySwift
[x] Game Of Life
[ ] GBA4iOS
[ ] Gorillas
[ ] GrubbyWorm
[x] littlego
[x] MUDRammer
[x] Mission999
[ ] Orbit7
[ ] Sakura Fly
[x] SceneKitFrogger
[ ] Spare Parts
[x] Stick-Hero-Swift
[ ] Wolfenstein 3D
[x] Arex
[x] AsthmaHealth
[x] Depressed
[x] GlucoSuccess
[ ] HealthKit~Swift
[ ] Jim
[ ] LogU
[x] mPower
[x] MyHeartCounts
[ ] rTracker
[x] Share The Journey
[ ] Speak
[ ] AA-Keyboard
[ ] ClickWheelKeyboard
[ ] Hodor
[x] NaughtyKeyboard
[ ] Slidden
[x] Alarm
[ ] Doppio
[x] Cafe
[ ] DoctorNearby
[ ] EatNow
[x] GeoTappy
[ ] HopperBus
[ ] iBeaconTasks
[ ] Locative
[x] Moves
[x] OneBusAway
[ ] OwnTracks
[x] ParkenDD
[ ] pathlogger
[ ] PebCiti
[x] Startups - Mapped In Israel
[ ] Swift-Walk-Tracker
[x] Smart Traveller (UberGuide)
[ ] VisitBCN
[x] 360 VR Player
[ ] Analog Synth X
[x] Artsy
[x] Artsy Folio
[ ] CollageMaker
[ ] ColorBlur
[x] ComicFlow
[x] DoubanFM
[x] Dunk
[ ] Eleven
[ ] Filterpedia
[ ] Flickr-Search
[ ] FreeStreamer
[ ] KonaBot
[x] Longboxed
[ ] Megabite
[ ] movies
[ ] OCiney
[x] OpenPics
[x] Open Source Selfie Stick
[ ] PhotoBrowser
[x] Poppins
[ ] PhishOD
[ ] PopcornTime
[ ] prankPro
[ ] Pugs
[x] Revolved
[x] SoundCloudSwift
[x] Swift ASCII Art Generator
[x] Swifteroid
[x] SwiftFlickrApp
[x] Swift Radio Pro
[ ] SwiftSpace
[ ] TechTavta
[ ] That Movie With
[ ] Textbook
[x] Upupu
[ ] VLC
[x] VoiceMemos
[x] xkcd
[ ] xkcd Open Source
[ ] Designer News App
[x] Feeds4U
[x] GrinnellEvents
[x] NirZhihuDaily2.0
[x] Reddit
[ ] RSSRead
[x] TabDump
[x] The Oakland Post
[x] v2ex
[ ] Hacker News Client
[ ] HackerNews (Y)
[x] HackerNews
[ ] Hackers
[ ] HN-App
[x] News/YC
[x] news
[ ] Simple Reader
[ ] Coding
[ ] DuckDuckGo
[ ] WhiteHouse
[ ] Wikipedia
[ ] WordPress
[x] Cannonball
[ ] Apple Developer Library
[ ] Apple WWDC 2015
[x] CloudKit in Objective-C
[x] CloudKit in Swift
[ ] Federal Data SDK
[x] Furni
[ ] HomeKit-Demo
[x] iOS 8 Sampler
[x] iOS 9 Sampler
[ ] KnockToReact
[x] Layer-Parse
[x] LayerPlayer
[x] LVMC
[x] OpenShop.io
[x] Polls
[ ] Reusable Code
[x] RKGist
[ ] SafariAutoLoginTest
[x] Starship
[ ] StateRestorationDemo
[ ] Swift-Demos
[ ] FreeOTP Authenticator
[x] MasterPassword
[ ] MiniKeePass
[ ] SkeletonKey
[x] ZeroStore
[ ] Aozora
[ ] Peggsite
[ ] StreetMusicMap
[x] Yep
[ ] 1Trackr
[x] CloudKit-To-Do-List
[x] MyAwesomeChecklist
[ ] RealmToDo
[ ] Swift Off
[ ] Todo
[ ] Todo.txt
[x] Tinylog
[x] Lucid Weather Clock
[x] Pocket Forecast
[ ] RainMan
[x] Sol
[x] SmileWeather
[x] SwiftWeather
[x] Tropos
[ ] WeatherApp
[ ] WeatherMap
[ ] YoCelsius
[x] PHPHub
[ ] ProMonster
[x] QiitaCollection
[x] A Menjar
[ ] bar
[ ] Be my eyes
[ ] BlogQuest
[ ] Borrowed Books UFGRS
[ ] CardDecks
[x] ChineseZodiac
[x] Colo
[x] DeckRocket
[x] EmotionNote
[ ] GammaThingy
[ ] GoodNight
[x] GreatReader
[ ] Hack Cancer
[ ] Hidrate
[x] iCopyPasta
[x] iContactU
[ ] iGrades
[ ] Jupp
[ ] LidderbuchApp
[x] Mirror++
[ ] my41
[x] OpenCB
[ ] Onions
[ ] Open States
[ ] ownCloud
[x] Phonetic
[ ] Population Clock
[ ] Round & Split
[x] Runner-Stats
[ ] Swiflytics
[x] Tether
[x] Theseus
[ ] TheReservist
[x] TrollDrop
[x] VPN On
[x] Vinylogue
[x] WaniKani
[x] Words
[ ] WWDC Students
[ ] Yorkie
[ ] ForceSketch
[ ] Plum-O-Meter
[ ] Malendar
[x] Workdays
[x] Edhita
[x] SimpleMemo
[x] SwiftNote
[x] Coffee Timer
[ ] Fojusi
[x] TrackMyTime
[x] Tracker 4 Compassion
[x] DVD Collection Tracker
[ ] Nested Lists
[ ] Tasks
[ ] Vegan Lists UK
[ ] 2CITY
[ ] Anypic in Objective-C
[ ] Anypic in Swift
[ ] AnyWall
[x] how-much
[ ] Parse-Challenge-App
[ ] ParseStore
[ ] Paws
[x] allyoop
[ ] 2048
[ ] Movies
[ ] TicTacToe
[ ] UIExplorer
[ ] Around Me
[ ] Assemblies
[x] Calculator
[ ] Currency Converter
[x] Den
[x] Dribbble
[ ] F8 2016
[ ] Facebook Login
[x] Finance
[ ] Foreign Exchange
[x] HackerNews-React-Native
[x] Iceland Earthquakes
[ ] iTunes Catalog Search
[ ] london-react
[ ] newswatch
[ ] PocketNode
[ ] Product Kitty
[ ] Property Finder
[ ] ReactNativeHackerNews
[ ] RSS Reader
[ ] Songkick
[ ] Spacepics
[ ] Sudoku
[ ] To Do List
[ ] Twitch
[x] Weather
[ ] BrewMobile
[x] C-41
[x] GitBucket
[ ] GroceryList
[x] HausClock
[ ] ReactiveHackerNews
[ ] ReactiveSwiftFlickrSearch
[x] SimpleAuth
[ ] SwiftRACGoogleImages
[ ] GitHub API Client
[x] Kiosk
[ ] Contacts
[x] Counter
[ ] Rambler.Conferences
[ ] To do
[ ] Toggl Timer
[ ] RealmVideo
[ ] ReactiveKitten
[ ] RailsCasts
[ ] MetricTime
[ ] AppSales-Mobile
[ ] Bancha
[x] Cheddar
[x] Everest
[ ] iOctocat
[ ] LastFM
[ ] Mume
[ ] Pancake
[ ] PocketFlix
[x] Repo
[x] SudokuResolv
[ ] Vim
[ ] wikiHow
[ ] ActiveGS
[ ] RetroArch
[ ] MAME4iOS
[x] DOSPad
[ ] PPSSPP
[x] Scary Flight
[ ] MiamiSunglasses
[ ] nds4ios
[ ] iUAE
[x] SwiftHub
[ ] Balloon Burst
[x] Closebox
[x] Sentiments
[x] TSWeChat
[ ] Colorblind
[x] UitzendingGemist by 4np
[x] Fibonacc iClock
[x] Chaty
[x] iCook
[x] Tweetometer
[ ] Neverlate
[x] Telemat-tvOS
[ ] NumberPad
[x] MAPS.ME
[ ] Linphone
[ ] Molecules
[ ] Task Coach
[ ] Castle Hassle
[ ] Skeleton Key
[ ] Cryptose
[ ] Aeropack
[ ] teh internets
[ ] hoxChess
[ ] iLabyrinth
[ ] Heredox
[ ] Pterodactyl Attack
[x] Neocom for EVE Online
[ ] Hostile Takeover
[ ] XPilot
[ ] AppSlate
[ ] Authenticator
[ ] CodeHub
[ ] Dragon Shout App 2
[ ] Frotz
[x] Inkpad
[ ] Wizard War
[ ] ZBar Barcode Reader
[x] Prey Anti Theft
[ ] Prey Swift Client
[ ] Radio Paradise
[ ] Kodi
[ ] Official Kodi Remote
[x] Antidote
[ ] Tutanota
[x] Piwik Mobile 2
[ ] Seafile Pro
[x] OsmAnd Maps
[x] Habitica
[ ] MuPDF
[ ] Kiwix
[ ] Hedgewars
[x] FreeRDP
[ ] Minds Mobile App
[x] Encryptr
[ ] Spika
[ ] Onion Browser
[ ] projectM
[x] openHAB
[ ] LibreOffice Remote for Impress
[ ] Free42
[x] Miataru
[ ] Wheelmap
[ ] Ello

You're doing this manually???

I'm currently making a script that should automate this for most github apps.

The script didn't work quite as well as I had hoped. Still, it took care of about half of them.
For the curious:
https://jsfiddle.net/scribblemaniac/nf2sxkaa/2/

Cool

I'll give it a go

Script https://github.com/dkhamsing/open-source-ios-apps/commit/065fa8abbac33c3b335e95a7ff2500ddf1ab3c8c

As of ab3005b1a946d87d277aecfe088a431a8d0ff92c, all apps have licenses. Can we make this mandatory?

For all the data nerds out there, here are some graphs:

License Distribution
Star Count by License

I'd rather not make it mandatory but can be at the discretion of the pull request review

Okay


[WSY-45] Check the port options before defaulting

Connection adapter was checking RABBIT_PORT and
immediately falling back to 5672 before checking the
documented port option.

Thanks, @esatterwhite - I appreciate the catch on that.

Possible to version and republish to npm?


Missing drag scrolling support in davi package

Describe the bug/problem
The davi package currently in use to display request params, headers and form data doesn't support drag scrolling (touch) and the package has been dormant for a while.

Proposed Solution
Switch to data_table_2 a more popular and active package and most importantly supports drag scrolling.

repo link - davi
repo link - data_table_2
Steps to Reproduce the bug/problem

Launch in device with touch input.
Attempt to scroll table when params/headers/form data rows overflow available height.

Expected behavior
Touch Drag scrolling should work.
Device Info (The device where you encountered this issue):

OS: Mobile
Version: Android 12

hey am interested  assigned to me


Project structure and configuration upgrades

According to modern best practices and PEP-517, Python projects should contain pyproject.toml  file at the root of project, which contains build system requirements and configuration for other tools, like linters, tests and etc. Also, defining setup.cfg  is a good way to create declarative config and specify all dependencies and metadata.
The usage of both pyproject.toml and setup.cfg simplifies project building and installation in editable mode for different environments using extras options.
Also, it is a best practice to separate tests code and source code using different directories art the root. In such case, it's easy to store and use different types of tests (e2e, integration, unit, etc.) at one place.
In addition to these project structure upgrades, packages installation to to specific directory and copying this content to /usr/bin/ of final layer of image could lead to misbehaviour of entrypoints of installed packages. In order to build python packages in one layer and install them in final, pip wheel should be used to create binaries of dependencies and pip install --no-index --find-links=<wheels_path> to install that binaries in final layer.
Pull request with all suggested enhancements and fixes is attached: #34

Restored project structure after discussion

#34 assigned PR to issue

#34 merged. So I can close the issue. Thanks for your contributing!


List contributors for each page

Webpack's website lists contributor at the bottom of each page.

The list of usernames is stored in the header of the page. Since we are publishing files from the babel/babel repo, how/where could we include this information?

Is this something we are interested in doing?
The list of contributors could be stored inside the front matter (like webpack.js.org does) of each page. We could run a one-time script that goes through all the readme.md for each package and add the users to the contributors front matter on this repo.
After that we should probably mention in the docs that if you want your name to show up in the contributors list, you need to edit the front matter of the doc page that is found on this repo (alternatively we could re-run the script every once in a while).
As to where to put this information, I think just above the Community Discussion section.
Thoughts?

how could we include this information

I like the idea of a script (I guess Webpack does it manually). We need to fingure out how to run it when a doc PR was merged in babel/babel repo.

where could we include this information

Sorry if it wasn't clear but I meant where to store the list of contributors. I think we could add this informations in the header of each pages (like the description).

Is this something we are interested in doing?

It seems that most doc updates are done by the Babel team. I don't know if this is an interresting information. The idea was to invite people to collaborate at the documentation because they will show up in the website. What do you think?


requrements extendable to Neos/Flow ^6.0?

It would be nice if this package also would be available for Neos/Flow version 6.0 and above...

This will come some time next year. The driving project of this package is still running on neos/flow v5 at the moment.
Anyway, I'm happy to get a PR with the required changes ;-)

Fixed with v2.0


Support Emoji in /profile PADD Text

Not quite sure how this would be accomplished but maybe worth looking into.

There’s a work in progress for this, but it is still in the testing phase.  https://github.com/python-pillow/Pillow/pull/6926  Currently the only way to do it would be to create a merge font and use that instead.


javax.net.ssl.SSLException: Unable to create application data

java.lang.RuntimeException: javax.net.ssl.SSLException: Unable to create application data
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.newSsl(ConscryptFileDescriptorSocket.java:161)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.(ConscryptFileDescriptorSocket.java:152)
at com.android.org.conscrypt.OpenSSLSocketFactoryImpl.createSocket(OpenSSLSocketFactoryImpl.java:149)
at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:369)
at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.java:337)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:209)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.java:226)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.java:106)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.java:74)
okhttp version is 4.2.2

From https://github.com/google/conscrypt/issues/891 looks like an out of memory error.  We can't help with this.  But I would suggest confirming you are not creating lots of OkHttpClient instances.


Switch to GitHub Actions from Travis CI

see https://twitter.com/mxstbr/status/1323225573683060736

Closed by #138.


Delete the CNAME DNS record used for certificate validation in hosted zone

Attempting to delete a newly created SCAR stack in CloudFormation currently fails due to the CNAME DNS record that is created manually as part of the validation step. A custom resource could be added to the template to remove this record from the hosted zone so that the record is deleted after validation is successful.

Same here.

How should I resolve it?

Hi @yanlinaung30 - the manual workaround for this issue is to manually delete the CNAME record first before deleting the CloudFormation stack.
You can do this by using the AWS Route 53 console to open the hosted zone that was created as part of your stack, selecting the CNAME record set, then "Delete Record Set". After that, you should be able to fully delete the CloudFormation stack as it will then be able to delete the hosted zone.
Let me know if that works.

@cloudkj
Thanks for your reply!
I delete CNAME manually as soon as the certificate is issued successfully.
But I encountered another issue.
I upload json template file to my s3 bucket of my region & Create the CloudFormation stack in my region
CloudFrontRootDistribution
The specified SSL certificate doesn't exist, isn't in us-east-1 region, isn't valid, or doesn't include a valid certificate chain. (Service: AmazonCloudFront; Status Code: 400; Error Code: InvalidViewerCertificate; Request ID: 67acde6a-8687-11e9-b0a2-4f83c31ceffd)

CloudFrontWWWDistribution
The specified SSL certificate doesn't exist, isn't in us-east-1 region, isn't valid, or doesn't include a valid certificate chain. (Service: AmazonCloudFront; Status Code: 400; Error Code: InvalidViewerCertificate; Request ID: 67944d42-8687-11e9-aadb-fd94b97f8503)

Hi @yanlinaung30 - it looks like ACM has a restriction that requires certificates to be created in the us-east-1 region in order to be used with CloudFront: https://docs.aws.amazon.com/acm/latest/userguide/acm-regions.html

To use an ACM Certificate with Amazon CloudFront, you must request or import the certificate in the US East (N. Virginia) region. ACM Certificates in this region that are associated with a CloudFront distribution are distributed to all the geographic locations configured for that distribution.

Unfortunately, for now you'll have to create the stack in us-east-1. Note that there should be no degradation in performance for visitors since the CloudFront distribution will be global. However, I can see that there can be a performance/cost issue in dealing with uploading or syncing assets if us-east-1 is not your home region.
I'll open a separate issue to track this problem. At the very least, the docs should be updated to reflect this limitation. It's possible that CloudFormation Stack Sets can offer a path forward by requesting only the ACM certificate in us-east-1 but other resources in the chosen region, but some work is needed to see if that's possible.

@cloudkj
Oh, this must be the reason!
Thanks a lot for your reply and explanation.
I will create the CloudFormation in North Virginia for now.
Thank you!


chore: introduce pre-commit hooks

Please check if the PR fulfills these requirements

[x] It's submitted to right branch according to our branching model
[x] It's right issue type on title
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has description for the breaking change

Description

This PR enables Git pre-commit hooks using husky and lint-staged

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

Can one of the admins verify this patch?


Adding performance notebook

I created a small notebook for replication of UMAP performance when increasing dataset size and dimensionality.
I can not create a pull request though. Is this something on my end, or do I need a permission for this?
How to proceed?

I am honestly note sure what the issue is. You can post the notebook as a gist and I can add it myself if you feel that would be useful, but pull requests should just work.

It is probably a local issue then. Thanks.
For now, here is the notebook: https://github.com/MLWave/notebooks/blob/master/UMAP Performance Tests.ipynb . It is a start.
Currently looking into using UMAP embeddings for meta-learning. t-SNE XGBoost meta-bagging style on the Otto competition. Seeing some good top 10% results.

1: UMAP seems good diverse addition to ensemble (it is doing something new),
2: UMAP, like XGB, is fast enough to hypertune and experiment with).

If I get a good binary supervised machine learning example working I'll also create a notebook for this. Comparison between [raw features, embeddings, raw features + embeddings] is a bit difficult, due to requiring different XGB hyperparams for working best. For now, I try to allocate each model+feature_set an equal random grid-search time, but I don't know if that is fair.


Should respect isort:skip comments

ruff currently respects noqa: I001 comments to prevent sorting certain imports. For improved isort compatibility, it should also respect isort:skip and isort:skip_file comments (documentation).

Good call.

It looks like isort:off and isort:on are recommended in the docs, so maybe I'll do those first.

Some extremely crude metrics from code search:


Clicking CC/BCC intermittently collapses fields before entering text

What operating system are you using?
Windows 10 Pro
What version of N1 are you using?
0.4.49
Bug?
Do you have any third-party plugins installed? If so, which ones?
No
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
No.
Is the issue reproducible with a particular attachment, message, signature, etc?

NA
Feature Request?
Does this feature exist in another mail client or tool you use?
Basic email feature.
When I try to click on the CC or BCC section when composing a new email the To field collapses back down to the recipients list. I am never actually able to enter a CC or BCC. I also use N1 on Linux and this issue is not present there.

@spetz83 Are you using the default Light theme?

@jackiehluo Yes, I am.

Another incidence: https://github.com/nylas/N1/issues/1955
@spetz83 Does CC/BCC never do anything when you click the buttons, or do you see them for a moment and then they collapse before you can enter content?

So, I can see the BCC and CC buttons. As soon as I click on one of them they both disappear, but the text input for adding BCC or CC never actually appears.

@khamidou just experienced this issue!

This should be resolved by 01fc435a4af3d8bec9845875416cccfc3ce521af - there was a small bug in the focus management code in the key-commands-region that was causing things to become unfocused!

Hi.... I cannot use CC or BCC either. I'm using OSX 10.10.5 using NYlas version  0.4.201
Clicking CC/BCC intermittently collapses fields before entering text #2754 @jackiehluo @spetz83  I see this issue was closed but I have not been able to resolve....is there something I need to do? thanks

Same problem there!
More specifically:

For new messages + previous e-mails that don't contains any Cc or Bcc: unable to see/add anything in Cc or BCc.
For previous e-mails: If I answer to a previous e-mail that already contains Cc or Bcc I've no problem to add some contacts in these fields.

Config:

OS = apple sierra 10.12.2
Nylas version: 1.0.15
Accounts: Gmail (2 pure gmail + 1 google app)

Thanks !


Event dispatcher

Alright, this is great. Thank you for bringing this :)
Will publish the package now.

Sorry for my late reply, thank you for the review!


virtualbox: 6.1.6 -> 6.1.8

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Made obsolete by pull request #89798

Closing in favor of #89798.


Added docker container for running fasthttploader

Created a docker container, so that fasthttploader can be run from any environment supporting docker.

This is a nice addition, why it haven't been accepted ?

I just tested the docker image and works fine.


No license file included

package.json says ISC for the license, but does not include a license file. Besides this needed for being clear about what license is used, it's also needed to comply with the ISC license itself.

Good call. I’ll fix this when I’m not on mobile, but in the meantime this comment confirms that it’s under the ISC license.


v0.0.17 (#203)

Notable changes:

Return correct length of string in fd_prestat_get (8fe8eec)

@cjihrig doing a release to get fix into Node.js. Also a good opportunity to test out the new automation and how that works in terms of automatically picking up the new uvwasi release and generating a PR.


multiroot jest-change-files

first step towards optimizing performance of this module.
the problem we hit at fb is that we have too many roots specified for every project, and we had to get changed files for each root.
Now all roots are first resolved to a SCM root and deduped, so we'll be querying SCM only once per context.
includes a shitload of tests and types.
todo (followup PRs):

[ ] Share results between context (www, mobile are in the same repo and will give different results, but with the current implementation it'll do one request for every context)
[ ] Start fetching the result as soon as possible, before any of the hastemap stuff is generated (might be happening already, haven't looked into it yet)

This looks fine overall, but I'm not entirely sure about the plan here. This doesn't really change anything, does it? Are you planning to take the main call out of SearchSource and pass Set<Context> into the SCM code at the end?

Codecov Report

Merging #3969 into master will decrease coverage by 0.12%.
The diff coverage is 67.94%.

@@            Coverage Diff            @@
##           master   #3969      +/-   ##
=========================================
- Coverage   59.92%   59.8%   -0.13%
=========================================
  Files         196     196
  Lines        6785    6769      -16
  Branches        6       6
=========================================
- Hits         4066    4048      -18
- Misses       2716    2718       +2
  Partials        3       3

Impacted Files
Coverage Δ

packages/jest-cli/src/search_source.js
79.31% <0%> (+8.29%)
:arrow_up:

packages/jest-changed-files/src/hg.js
32.25% <32.14%> (-54.41%)
:arrow_down:

packages/jest-changed-files/src/git.js
92.59% <92.59%> (+0.28%)
:arrow_up:

packages/jest-changed-files/src/index.js
95.23% <95%> (+95.23%)
:arrow_up:

packages/jest-haste-map/src/module_map.js
77.77% <0%> (-2.23%)
:arrow_down:

packages/jest-matchers/src/matchers.js
99.37% <0%> (-0.01%)
:arrow_down:

packages/eslint-config-fb-strict/index.js
0% <0%> (ø)
:arrow_up:

packages/jest-haste-map/src/index.js
92.8% <0%> (ø)
:arrow_up:

packages/jest-matchers/src/index.js
97.46% <0%> (+0.13%)
: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 c11a98e...0ef151e. Read the comment docs.


UI issues on different screen:

Proceed button is getting cut from bottom.

Check the alignment of "Send Max" button.

Icon is overlapping.

**- Tested on keeper app v1.2.11(379)

Device: Android One plus 9R**

1 and 2 are device specific, not able to regenerate.
3 i have already fixed.


Not working in Big Sur

This isn't currently working on 11.0.1, will there be an update soon?

Hey,
I just upgraded to 11.0.1 myself and it's working fine for me.
Do you have any more info? Does it crash on startup? Does it not sync?

I have this model: https://www.lg.com/us/monitors/lg-27un850-w-4k-uhd-led-monitor
Maybe my monitor isn't compatible?

Yes, it's not compatible. This app is specifically for LG UltraFine displays. There are other apps that might help you, like https://github.com/alin23/Lunar

That worked for me, thank you sir!


groupby apply and new dataframe.apply_*()

Implements

groupby.apply for basic pandas-like .apply on the groups.
groupby.apply_grouped for transforming each group with user provided GPU function.
dataframe.apply_rows for row-wise transform with a GPU function.
dataframe.apply_chunks for chunk-wise transform with a GPU function.  This is the underlying function for groupby.apply_grouped.

Docs still look to be missing is docs for groupby.apply_grouped and groupby.apply