CI: Run test in Electron as well

Looking at this https://github.com/WiseLibs/better-sqlite3/pull/1036#issuecomment-2227422329 I think it would be great if we could catch these things early and also if Electron specific PRs would actually show that tests are now passing.
Is this feasible? Too slow? It should be possible to run Jest with an Electron process and also run @electron/rebuild before running the tests.
@m4heshd you seem to be knowledgeable regarding GitHub CI stuff

We’d want to run with both supported electron builds and a phase that pulls the latest beta that doesn’t mark the build as “failed.”  That could be as simple as splitting the beta electron build into a different .yml file.

It would most probably slow down the tests significantly however, it's worth the effort.
I'm gonna have to look into how Mocha could handle this. The first thing that comes to my mind is to execute the Mocha process via Electron using ELECTRON_RUN_AS_NODE=1 env. Not sure if it would work as intended though. Need to run some tests.

Since it's not recommended to run DB tasks on the renderer process in the first place, I think it's unnecessary to test that scenario.

Agreed, definitely only run tests in the main process

Given how common using better-sqlite3 with Electron is, this makes total sense and would improve the DX for many.

While it is not recommended to run (concurrent) DB tasks in the renderer, I came across several projects, that use a hidden browser window for decoupling the persistence layer from the main process. But in the end - if everything goes right - the renderer process should behave the same as the main process when it comes down to loading native node modules. At least until today I had no issues testing the better-sqlite3 integration with electron-mocha in the main and renderer process.

While it is not recommended to run (concurrent) DB tasks in the renderer, I came across several projects, that use a hidden browser window for decoupling the persistence layer from the main process. But in the end - if everything goes right - the renderer process should behave the same as the main process when it comes down to loading native node modules. At least until today I had no issues testing the better-sqlite3 integration with electron-mocha in the main and renderer process.

Given how this issue arose because things that were presumed to work ended up not working after a new electron version due to the lack of explicit tests, I believe not covering the greatest area possible with these new tests is an invitation for the same problems to appear further down the line.
While not making sense to have separate tests now for both main and renderer, a future electron version may introduce breaking changes that will require such tests to be written.

renderer process should behave the same as the main process when it comes down to loading native node modules.

It unfortunately doesn't. There's a countless amount of issues open in Electron about the very same issue and the team's response is always the same. They DO NOT recommend it. That's why they even unplugged the remote module and marked it as risky. If somebody utilizes Node's native features on the renderer, it's on them to maintain that unreliable mess. I've experienced this firsthand myself. This is also why Tauri went on a much safer path when it comes to that.

I came across several projects, that use a hidden browser window for decoupling the persistence layer from the main process

I use a Worker Thread spawned from main to host the entire application logic (to not block main). There is no reason to use better-sqlite3 in renderer. Ever. Using a hidden browser window might have been the recommended approach five years ago.

I use a Worker Thread spawned from main to host the entire application logic (to not block main). There is no reason to use better-sqlite3 in renderer. Ever. Using a hidden browser window might have been the recommended approach five years ago.

This and only this. I do not recommend any other practice when it comes to Electron. I learned an expensive lesson many years ago and this is the exact method I adapted to use. I even updated the threads documentation when I finally got it to be stable for production.
Final conclusion, DO NOT perform important logic on the renderer unless you're super lazy.  Let it simply be the UI Renderer (which it's supposed to be) and a messenger.

I came across several projects, that use a hidden browser window for decoupling the persistence layer from the main process

I use a Worker Thread spawned from main to host the entire application logic (to not block main). There is no reason to use better-sqlite3 in renderer. Ever. Using a hidden browser window might have been the recommended approach five years ago.

We should pin this to this project (maybe add it to the README?)


cargo-tree: 0.19.0 -> 0.20.0

Motivation for this change
It was outdated
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[x] 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)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build cargo-tree


Prevent non-defined props from getting set in connect?

Given this basic example:
import React from 'react';
import { connect } from 'react-redux';

class Foo extends React.Component {
  static propTypes = {
    foo: React.PropTypes.string
  };
}

export default connect((state) => {
  return {
    // Legit prop is set:
    foo: state.foo,

    // Non-existent prop is set. I want a lint error here:
    bar: state.bar
  };
})(Foo);

Is there a way to get eslint to report the invalid bar prop as an error?

I think this is a good idea

I'm not sure I understand. How could anyone statically determine that in this IIFE that returns an object, the object is meant to represent props?

because of this line import { connect } from 'react-redux'

and this one connect()

That's some really really specific deduction for one single library. That seems like something that some sort of eslint-config-redux would handle, but not generic React.
I'm particularly concerned that usage of https://www.npmjs.com/package/react-with-styles would trigger this, short of the very specific import detection.

@ljharb I'd argue redux is pretty huge https://www.npmjs.com/package/redux, but you're right a redux specific plugin may make the most sense. Wondering how it would work with the existing propTypes validation if it was separate though 🤔

Agreed, this seems like a useful rule but it would be best for a redux or react-redux specific eslint plugin.
Can you elaborate on your concerns about existing propTypes validation?

Thanks for the discussion, y'all. At the very least, it sounds like this is the wrong repository for this rule, so I'm going to close the issue. Please feel free to keep commenting on the issue – it's all really valuable input from my perspective :)


OverflowToolbar doesn't support MultiComboBox

Is there a particular reason why an OverflowToolbar cannot move a MultiComboBox into the overflow area? This does work for a normal ComboBox and it seems like it'd be quite easy to implement, but of course I might be missing something.

MCVE: https://jsbin.com/jobucam/edit?html,js,output
Even if forced with <OverflowToolbarLayoutData priority="AlwaysOverflow" />, the MultiComboBox cannot be seen in the overflow area.

Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub

Hello @gbrfarkas  there are a limited set of controls that can be used within the OverflowToolbar, you can see them all in the official documentation page here - https://ui5.sap.com/#/api/sap.m.OverflowToolbar%23overview
There are technical limitations not allowing placing any control as content, such as the one mentioned a bit later in the API reference:
Note: The OverflowToolbar is an adaptive container that checks the available width and hides the part of its content that doesn't fit. It is intended that simple controls, such as [sap.m.Button](https://ui5.sap.com/api/sap.m.Button) and [sap.m.Label](https://ui5.sap.com/api/sap.m.Label) are used as content. Embedding other adaptive container controls (with the exception of [sap.m.Breadcrumbs](https://ui5.sap.com/api/sap.m.Breadcrumbs)), results in competition for the available space - both controls calculate the available space based on the other one's size and both change their width at the same time, leading to incorrectly distributed space.

@ndeshev Thanks for replying - I do understand that currently you can only put the controls in that list into an OverflowToolbar, it just seemed weird to me that the MultiComboBox would be excluded. I had a requirement recently where I needed this and ended up subclassing MultiComboBox and implement IOverflowToolbarContent which seemed to work OK.


InlfuxDB Sink Feature check

This is in continuity to https://github.com/Landoop/stream-reactor/issues/329
Thanks @stheppi for your help , this will mean schema for each topic is kind of fixed and I can only have certain property names that can be selected from the fields. In my case Telegraf is sending host level metrics https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system to a single topic for example : SWAP information comes as
"fields": { "free": 473169920, "total":<PHONE_NUMBER>, "used":<PHONE_NUMBER>, "used_percent": 85.31087239583334 }, "name": "swap", "tags": { "dc": "us-east-1", "host": "Viveks-MacBook-Pro.local", "rack": "1a" }, "timestamp":<PHONE_NUMBER> }
and
CPU information comes as
{ "fields": { "usage_guest": 0, "usage_guest_nice": 0, "usage_idle": 75.3, "usage_iowait": 0, "usage_irq": 0, "usage_nice": 0, "usage_softirq": 0, "usage_steal": 0, "usage_system": 10.1, "usage_user": 14.6 }, "name": "cpu", "tags": { "cpu": "cpu0", "dc": "us-east-1", "host": "Viveks-MacBook-Pro.local", "rack": "1a" }, "timestamp":<PHONE_NUMBER> }
I want to both (and) more information to be relayed to influxDB fluidly.
Is this supported by this connector ?

@vivekatme
Let's take the CPUs
{
   "fields": {
   	"usage_guest": 0,
   	"usage_guest_nice": 0,
   	"usage_idle": 75.3,
   	"usage_iowait": 0,
   	"usage_irq": 0,
   	"usage_nice": 0,
   	"usage_softirq": 0,
   	"usage_steal": 0,
   	"usage_system": 10.1,
   	"usage_user": 14.6
   },
   "name": "cpu",
   "tags": {
   	"cpu": "cpu0",
   	"dc": "us-east-1",
   	"host": "Viveks-MacBook-Pro.local",
   	"rack": "1a"
   },
   "timestamp":<PHONE_NUMBER>
}

you should use the following KSQL syntax:
INSERT INTO cpu
SELECT fields.*
FROM $YOUR_TOPIC_WITH_CPU_DATA
WITHTIMESTAMP timestamp
TIMESTAMPUNIT=MILLISECONDS
WITHTAG (tags.cpu, tags.dc, tags.host, tags.rack)

I assume the timestamp from Telegraf is in millis acuracy.
You need to take the latest from master and build it locally.
Let us know how it goes.

@vivekatme Closing, reopen if you still have an issue.


Updadting documentation

The passport.org website has completly changed.
http://passportjs.org/docs
All the documentation and de references in the comment are 404 link, please upade :)

From the README:

OBS: This generator is not currently maintained. Check out https://github.com/tjwebb/sails-auth for an actively maintained project based on this generator.

Please note that Sails.js is no longer actively maintained, and therefore sails-auth is also no longer maintained either. See https://github.com/tjwebb/sails-auth/issues/118

Closing as the project is no longer maintained.


Metadata spec requires that geometry columns has no duplicates

Currently, the columns field in the geo metadata returns a dictionary mapping column names to metadata objects:
In [140]: import geopandas, dask_geopandas, pyarrow.parquet, json

In [141]: gdf = geopandas.read_file(geopandas.datasets.get_path("naturalearth_lowres"))

In [142]: gdf.to_parquet("data.parquet")
<ipython-input-142-1be891435621>:1: UserWarning: this is an initial implementation of Parquet/Feather file support and associated metadata.  This is tracking version 0.1.0 of the metadata specification at https://github.com/geopandas/geo-arrow-spec

This metadata specification does not yet make stability promises.  We do not yet recommend using this in a production setting unless you are able to rewrite your Parquet/Feather files.

To further ignore this warning, you can do:
import warnings; warnings.filterwarnings('ignore', message='.*initial implementation of Parquet.*')
  gdf.to_parquet("data.parquet")

In [143]: schema = pyarrow.parquet.ParquetFile("data.parquet").schema.to_arrow_schema()

In [144]: json.loads(schema.metadata[b"geo"])["columns"]
Out[144]:
{'geometry': {'crs': 'GEOGCRS["WGS 84",ENSEMBLE["World Geodetic System 1984 ensemble",MEMBER["World Geodetic System 1984 (Transit)"],MEMBER["World Geodetic System 1984 (G730)"],MEMBER["World Geodetic System 1984 (G873)"],MEMBER["World Geodetic System 1984 (G1150)"],MEMBER["World Geodetic System 1984 (G1674)"],MEMBER["World Geodetic System 1984 (G1762)"],ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1]],ENSEMBLEACCURACY[2.0]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433]],CS[ellipsoidal,2],AXIS["geodetic latitude (Lat)",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433]],AXIS["geodetic longitude (Lon)",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433]],USAGE[SCOPE["Horizontal component of 3D system."],AREA["World."],BBOX[-90,-180,90,180]],ID["EPSG",4326]]',
  'encoding': 'WKB',
  'bbox': [-180.0, -90.0,<PHONE_NUMBER>0000006, 83.64513000000001]}}

Because we're using a dictionary, we can't represent tables with duplicate column names for geometries. (it turns out geopandas can't even write the parquet file when there are duplicate geometries; I'll open an issue if we care about taht).
I wanted to explicitly confirm that we're OK with not allowing duplicate column names for geometries.

How else would we be able to uniquely identify a given column than its name?  DataFrames / GeoDataFrames with duplicate column names seem problematic regardless.
Pandas doesn't allow duplicate column names to be exported to parquet:
>>> df = pd.DataFrame([[1,2]], columns=['foo','foo'])
>>> df
   foo  foo
0    1    2
>>> df.to_parquet('/tmp/test.pq')
...
ValueError: Duplicate column names found: ['foo', 'foo']

Personally, I'm OK with not allowing duplicate column names - geometry or otherwise.

How else would we be able to uniquely identify a given column than its name? DataFrames / GeoDataFrames with duplicate column names seem problematic regardless.

It'd have to be by position I think, which would be annoying for producers and consumers of the data.

Pandas doesn't allow duplicate column names to be exported to parquet:

Good point! It turns out pyarrow.parquet can write a table with duplicates, but seems to fail when reading it.

Personally, I'm OK with not allowing duplicate column names - geometry or otherwise.

Same here.

Yes, I think I am also certainly fine with not allowing duplicate geometry column names.
(one solution for this would be to use field-level metadata instead of top-level metadata for the column metadata; that came up in discussions elsewhere, and that might be worth discussing, but maybe not necessarily for this reason)
Do we want to explicitly add this to the metadata description?


Base-types folder migration cleanup

Moved changes from docs-internal; deleted earlier versions of base-types docs with truncated names, changed .NET Framework to .NET in newly migrated docs.  Another PR by @tompratt-AQ will do the redirects from the short names to the long names.

PR 1869 covers the redirects.

@tdykstra I only see :eyes: two here. I wish I was that good. :+1:

@tdykstra Was the plan to catch-up on titles for TOC later? ... here's one, but there might be more lurking out there ...
### [.NET Framework Regular Expressions](regular-expressions.md)

Line 33 at https://github.com/dotnet/docs/edit/master/docs/standard/base-types/toc.md

@GuardRex No, I missed that.  I'll fix that and review toc.md,

@tdykstra Thanks ... @wadepickett is going to either ❤ me or 🔫 me for this, but I'm determined not to have @mairaw come back to a PR insanity! :grinning:

Thanks, @GuardRex, it'll be ❤ not 🔫
Stale PRs are a breeding ground for merge conflicts.

Stale PRs are a breeding ground for merge conflicts.

Tom, we're so on the same wavelength here ... @mairaw should come back to FEWER unmerged PR's than she left us with. For our kindred spirit, let's end the vacation on a high note 🎵 🎷.


range slider

how can i achieve this thing through asvalue tracking slider...
rightnow iam able to do this. but still could not able to find solution to made like above one...

please help...


Add Ipgeolocation into public apis

Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[x] Your submissions are formatted according to the guidelines in the contributing guide
[x] Your additions are ordered alphabetically
[x] Your submission has a useful description
[x] The description does not end with punctuation
[x] Each table column should be padded with one space on either side
[x] You have searched the repository for any relevant issues or pull requests
[x] Any category you are creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for contribution, but this api no longer exists:


check nrf_802154_sleep_if_idle() return status to set correct pending event

Need to rerun fuzzing after PR #5505 is merged.


Add import raw dataset for spectrum table

This PR is for support Redshift Spectrum. The modification is only redshift_adapter.rb

Modify fetch_rows, to omit check spectrum table

The function did not execute for spectrum table because The price of spectrum depends on the amount of scanning data
According to my research, both query of select * from spectrum_table limit 20 and select count(*) from spectrum_table is not so expensive

(TBW: my research on the amount of scan to query to spectrum table )

Below table is my research on the amount of scan to query to big spectrum table.
https://aws.amazon.com/jp/redshift/pricing/#redshift-spectrum-pricing

With Redshift Spectrum, you are billed at $5 per terabyte of data scanned, rounded up to the next megabyte, with a 10 megabyte minimum per query.

The table has<PHONE_NUMBER>08 rows, but select * limit 20 scanned only 2.477GB (by s3_scanned_bytes).
The price of this scan size is $0.124 (= 2.477 / 100 * 5 ).

column_name
infor of select * limit 20
info of select count(*) before left query

jst_start
2019-07-02 10:41:22
2019-07-02 10:40:40

jst_end
2019-07-02 10:41:26
2019-07-02 10:40:57

segment
0
0

step
1
1

starttime
2019-07-02 1:41:22
2019-07-02 1:40:40

endtime
2019-07-02 1:41:26
2019-07-02 1:40:57

elapsed
4224580
17260796

aborted
0
0

external_table_name
S3 Scan our_big_table_at_spectrum
S3 Subquery our_big_table_at_spectrum

file_format
ORC
ORC

is_partitioned
t
t

is_rrscan
f
f

is_nested
f
f

s3_scanned_rows
808448
269026086908

s3_scanned_bytes
2477937242
525926400

s3query_returned_rows
808448
40846

s3query_returned_bytes
33020824
694382

files
37
5136

files_max
2
67

files_avg
0
40

splits
280
40846

splits_max
10
503

splits_avg
2
319

total_split_size
16559997684
5204958405367

max_split_size
142308637
150858374

avg_split_size
59142848
127428840

total_retries
0
3

max_retries
0
1

max_request_duration
1073884
5798397

avg_request_duration
524553
358565

max_request_parallelism
10
10

avg_request_parallelism
1.7
9.3

total_slowdown_count
0
0

max_slowdown_count
0
0


[ERROR] It occurred an error, when installation

When, I use command "pip install -v -e .", It occurred an error below.
Using pip 22.3.1 from /root/anaconda3/envs/occ/lib/python3.7/site-packages/pip (python 3.7)
Obtaining file:///root/Tri-Layer_Plugin_Occluded_Detection
  Running command python setup.py egg_info
  running egg_info
  creating /tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info
  writing /tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/PKG-INFO
  writing dependency_links to /tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/dependency_links.txt
  writing requirements to /tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/requires.txt
  writing top-level names to /tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/top_level.txt
  writing manifest file '/tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/SOURCES.txt'
  reading manifest file '/tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/SOURCES.txt'
  adding license file 'LICENSE'
  writing manifest file '/tmp/pip-pip-egg-info-ioxndeml/mmdet.egg-info/SOURCES.txt'
  Preparing metadata (setup.py) ... done
Requirement already satisfied: matplotlib in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmdet==2.11.0) (3.5.3)
Collecting mmpycocotools
  Using cached mmpycocotools-12.0.3.tar.gz (23 kB)
  Running command python setup.py egg_info
  running egg_info
  creating /tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info
  writing /tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/PKG-INFO
  writing dependency_links to /tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/dependency_links.txt
  writing requirements to /tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/requires.txt
  writing top-level names to /tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/top_level.txt
  writing manifest file '/tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/SOURCES.txt'
  reading manifest file '/tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  writing manifest file '/tmp/pip-pip-egg-info-3bzg8_hl/mmpycocotools.egg-info/SOURCES.txt'
  Preparing metadata (setup.py) ... done
Requirement already satisfied: numpy in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmdet==2.11.0) (1.21.5)
Requirement already satisfied: six in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmdet==2.11.0) (1.16.0)
Requirement already satisfied: terminaltables in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmdet==2.11.0) (3.1.10)
Requirement already satisfied: timm in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmdet==2.11.0) (0.9.12)
Requirement already satisfied: pyparsing>=2.2.1 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (3.1.1)
Requirement already satisfied: kiwisolver>=1.0.1 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (1.4.5)
Requirement already satisfied: python-dateutil>=2.7 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (2.8.2)
Requirement already satisfied: cycler>=0.10 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (0.11.0)
Requirement already satisfied: fonttools>=4.22.0 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (4.38.0)
Requirement already satisfied: packaging>=20.0 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (23.2)
Requirement already satisfied: pillow>=6.2.0 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from matplotlib->mmdet==2.11.0) (9.4.0)
Requirement already satisfied: setuptools>=18.0 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmpycocotools->mmdet==2.11.0) (65.6.3)
Requirement already satisfied: cython>=0.27.3 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from mmpycocotools->mmdet==2.11.0) (3.0.6)
Requirement already satisfied: torch>=1.7 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from timm->mmdet==2.11.0) (1.10.0)
Requirement already satisfied: safetensors in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from timm->mmdet==2.11.0) (0.4.1)
Requirement already satisfied: pyyaml in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from timm->mmdet==2.11.0) (6.0.1)
Requirement already satisfied: huggingface-hub in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from timm->mmdet==2.11.0) (0.16.4)
Requirement already satisfied: torchvision in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from timm->mmdet==2.11.0) (0.11.1)
Requirement already satisfied: typing-extensions in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from kiwisolver>=1.0.1->matplotlib->mmdet==2.11.0) (4.7.1)
Requirement already satisfied: tqdm>=4.42.1 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from huggingface-hub->timm->mmdet==2.11.0) (4.66.1)
Requirement already satisfied: fsspec in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from huggingface-hub->timm->mmdet==2.11.0) (2023.1.0)
Requirement already satisfied: importlib-metadata in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from huggingface-hub->timm->mmdet==2.11.0) (6.7.0)
Requirement already satisfied: requests in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from huggingface-hub->timm->mmdet==2.11.0) (2.31.0)
Requirement already satisfied: filelock in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from huggingface-hub->timm->mmdet==2.11.0) (3.12.2)
Requirement already satisfied: zipp>=0.5 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from importlib-metadata->huggingface-hub->timm->mmdet==2.11.0) (3.15.0)
Requirement already satisfied: certifi>=2017.4.17 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from requests->huggingface-hub->timm->mmdet==2.11.0) (2022.12.7)
Requirement already satisfied: urllib3<3,>=1.21.1 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from requests->huggingface-hub->timm->mmdet==2.11.0) (2.0.7)
Requirement already satisfied: idna<4,>=2.5 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from requests->huggingface-hub->timm->mmdet==2.11.0) (3.6)
Requirement already satisfied: charset-normalizer<4,>=2 in /root/anaconda3/envs/occ/lib/python3.7/site-packages (from requests->huggingface-hub->timm->mmdet==2.11.0) (3.3.2)
Building wheels for collected packages: mmpycocotools
  Running command python setup.py bdist_wheel
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-cpython-37
  creating build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/__init__.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/cocoeval.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/coco.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/mask.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  running build_ext
  Compiling pycocotools/_mask.pyx because it changed.
  [1/1] Cythonizing pycocotools/_mask.pyx
  /root/anaconda3/envs/occ/lib/python3.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-wl38a1ze/mmpycocotools_5e6d1af3ce9041b988195bf4ab2b3b8c/pycocotools/_mask.pyx
    tree = Parsing.p_module(s, pxd, full_module_name)
  building 'pycocotools._mask' extension
  creating build/common
  creating build/temp.linux-x86_64-cpython-37
  creating build/temp.linux-x86_64-cpython-37/common
  creating build/temp.linux-x86_64-cpython-37/pycocotools
  gcc -pthread -B /root/anaconda3/envs/occ/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/root/anaconda3/envs/occ/lib/python3.7/site-packages/numpy/core/include -Icommon -I/root/anaconda3/envs/occ/include/python3.7m -c ../common/maskApi.c -o build/temp.linux-x86_64-cpython-37/../common/maskApi.o
  gcc: error: ../common/maskApi.c: No such file or directory
  error: command '/usr/bin/gcc' failed with exit code 1
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /root/anaconda3/envs/occ/bin/python -u -c '
  exec(compile('"'"''"'"''"'"'
  # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
  #
  # - It imports setuptools before invoking setup.py, to enable projects that directly
  #   import from `distutils.core` to work with newer packaging standards.
  # - It provides a clear error message when setuptools is not installed.
  # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
  #   setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
  #     manifest_maker: standard file '"'"'-c'"'"' not found".
  # - It generates a shim setup.py, for handling setup.cfg-only projects.
  import os, sys, tokenize

  try:
      import setuptools
  except ImportError as error:
      print(
          "ERROR: Can not execute `setup.py` since setuptools is not available in "
          "the build environment.",
          file=sys.stderr,
      )
      sys.exit(1)

  __file__ = %r
  sys.argv[0] = __file__

  if os.path.exists(__file__):
      filename = __file__
      with tokenize.open(__file__) as f:
          setup_py_code = f.read()
  else:
      filename = "<auto-generated setuptools caller>"
      setup_py_code = "from setuptools import setup; setup()"

  exec(compile(setup_py_code, filename, "exec"))
  '"'"''"'"''"'"' % ('"'"'/tmp/pip-install-wl38a1ze/mmpycocotools_5e6d1af3ce9041b988195bf4ab2b3b8c/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' bdist_wheel -d /tmp/pip-wheel-r7ept2_l
  cwd: /tmp/pip-install-wl38a1ze/mmpycocotools_5e6d1af3ce9041b988195bf4ab2b3b8c/
  Building wheel for mmpycocotools (setup.py) ... error
  ERROR: Failed building wheel for mmpycocotools
  Running setup.py clean for mmpycocotools
  Running command python setup.py clean
  running clean
  removing 'build/temp.linux-x86_64-cpython-37' (and everything under it)
  removing 'build/lib.linux-x86_64-cpython-37' (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-3.7' does not exist -- can't clean it
Failed to build mmpycocotools
Installing collected packages: mmpycocotools, mmdet
  Running command Running setup.py install for mmpycocotools
  running install
  /root/anaconda3/envs/occ/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
    setuptools.SetuptoolsDeprecationWarning,
  running build
  running build_py
  creating build/lib.linux-x86_64-cpython-37
  creating build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/__init__.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/cocoeval.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/coco.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  copying pycocotools/mask.py -> build/lib.linux-x86_64-cpython-37/pycocotools
  running build_ext
  building 'pycocotools._mask' extension
  creating build/temp.linux-x86_64-cpython-37
  creating build/temp.linux-x86_64-cpython-37/common
  creating build/temp.linux-x86_64-cpython-37/pycocotools
  gcc -pthread -B /root/anaconda3/envs/occ/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/root/anaconda3/envs/occ/lib/python3.7/site-packages/numpy/core/include -Icommon -I/root/anaconda3/envs/occ/include/python3.7m -c ../common/maskApi.c -o build/temp.linux-x86_64-cpython-37/../common/maskApi.o
  gcc: error: ../common/maskApi.c: No such file or directory
  error: command '/usr/bin/gcc' failed with exit code 1
  error: subprocess-exited-with-error

  × Running setup.py install for mmpycocotools did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /root/anaconda3/envs/occ/bin/python -u -c '
  exec(compile('"'"''"'"''"'"'
  # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
  #
  # - It imports setuptools before invoking setup.py, to enable projects that directly
  #   import from `distutils.core` to work with newer packaging standards.
  # - It provides a clear error message when setuptools is not installed.
  # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
  #   setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
  #     manifest_maker: standard file '"'"'-c'"'"' not found".
  # - It generates a shim setup.py, for handling setup.cfg-only projects.
  import os, sys, tokenize

  try:
      import setuptools
  except ImportError as error:
      print(
          "ERROR: Can not execute `setup.py` since setuptools is not available in "
          "the build environment.",
          file=sys.stderr,
      )
      sys.exit(1)

  __file__ = %r
  sys.argv[0] = __file__

  if os.path.exists(__file__):
      filename = __file__
      with tokenize.open(__file__) as f:
          setup_py_code = f.read()
  else:
      filename = "<auto-generated setuptools caller>"
      setup_py_code = "from setuptools import setup; setup()"

  exec(compile(setup_py_code, filename, "exec"))
  '"'"''"'"''"'"' % ('"'"'/tmp/pip-install-wl38a1ze/mmpycocotools_5e6d1af3ce9041b988195bf4ab2b3b8c/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' install --record /tmp/pip-record-hd7dwlv3/install-record.txt --single-version-externally-managed --compile --install-headers /root/anaconda3/envs/occ/include/python3.7m/mmpycocotools
  cwd: /tmp/pip-install-wl38a1ze/mmpycocotools_5e6d1af3ce9041b988195bf4ab2b3b8c/
  Running setup.py install for mmpycocotools ... error
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> mmpycocotools

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

It looks the pycocotools is not installed successfully. You could try to pip install it separately yourself.


Policy to Allow Users to Rotate IAM AccessKeys

This police is for attaching to a role to allow 2ndline users to rotate IAM Access Keys.

@issyl0 That's the plan.


fix: fix compose generic type positions

use the same generic type scheme for curry
this happens to be a breaking change when compose is used with 5 or more functions, but actual return type would have been different from inferred type.

Nasty bug.. thanks a lot @bumbleblym

Released a patch.
@bumbleblym out of curiosity, are you using fp-ts for a real world project? fp-ts started as a R&D project but then I succesfully used it in io-ts (leveraging the Either monad) and monocle-ts (functional optics)

wish i could tell you i was, but i'm only hacking on this package out of mathematical curiosity. i haven't used these types in actual projects, whether from this package or other packages/languages.
by the way, have you tried jsverify?


Define feature set of useExperiment

useExperiment() hook.
const useExperiment(name: string, opts: ExperimentOptions = {}): Variant
ExperimentOptions:
interface ExperimentOptions {
  defaultVariant: string | number;
  fetchVariant(): string | number;
  defineVariants?: Array[string] | Array[number];
  enableStickyVariant?: boolean;
  enableForceUrlVariant?: boolean;
}

defaultVariant - default variant value.

fetchVariant(): string | number - is an async function that fetches the variant from the API (useful when experiment functionality is a standalone service).

defineVariants - is an array of variants that is used in your application (e.g. ['a','b'] or [1,2]).

enableStickyVariant - if set to true, the user will always see the variant that was assigned to her/him for the first time. If it's false the user will get the weighted variant every page view where the test is running.

enableForceUrlVariant - if set to true, you can force the variant of your choice via the query parameter. It is useful for the testing purpose.
Forcing the variant of your choice: /?et=exp:variant_a. You can also force variants for multiple experiments: /?et=exp_1:variant_a,exp_2:variant_b

Variant:
interface Variant {
  assignedVariant: string | number;
  isLoading: boolean;
}

Usage

Variants defined on the client-side. An assigned variant is sticky by default (e.g. stored on the local storage).

const Demo = () => {
  const activeVariant = useExperiment(
    'one-billion-dollar-experiment',
    {
      variants: ['a', 'b'],
      defaultVariant: 'a'
    }
  );

  let text;
  if (activeVariant === 'a') {
    text = <div> new text </div>
  } else if (activeVariant === 'b') {
    text = <div> old text </div>
  }

  return (
    <div>
      {text}
    </div>
  );
};

Overall, the api makes sense very much.
I have couple of questions:

Does enableStickyVariant store the response in the localStorage?
Does it makes sense to have a prop as flag to lazily fetch the variant, like on demand?
Should be query parameter name configurable to prevent overlapping in different applications?

@alicanerdogan

Does enableStickyVariant store the response in the localStorage?
Yes.

Does it makes sense to have a prop as flag to lazily fetch the variant, like on demand?
Can you please elaborate more on this? I'm not sure I got it.

Should be query parameter name configurable to prevent overlapping in different applications?
Very good point! We can have as a default query param ?et, and the possibility to override it if needed.

I'm guessing when you use the hook, it call the fetch prop when the component is mounted, right?
For some cases, the call is not needed to be executed immediately.
e.g.:
const { assignedVariant } = useExperiment({
  name: '1-billion-dollar-experiment',
  defineVariants: ['a:50', 'b:50'],
  defaultVariant: 'a',
  lazy: true
});

// assignedVariant will be allways undefined, until lazy prop is false

Initial requirements collected, the issue can be closed.


Make pg_trgm available for supermarket database.

See this for more info:
https://github.com/chef/supermarket/issues/861#issuecomment-112596930

I'm closing this PR out as we've deprecated this cookbook in favor of the omnibus-supermarket cookbook.


Classify items in quick info

Would be nice if a text in the quick info will classify as in the text editor in the first approximate

After a lot of investigation I understand that doesn't exist a way to integrate a custom classifier to the default generated text for quick info. Is only one way to apply custom classifications to quick info – create text of quick info by hand and apply the relevant ClassifiedTextRun of analyzing node.
Besides, in the Microsoft.CodeAnalysis.*.2.9.0 will introduced a public QuickInfoService that allows to get a raw tagged text for applying to them a some custom analysis, but unfortunatly, the WellKnownTags doesn't contain a couple of CoCo classifications. So, for full supporting CoCo classifications in the quick info need to generate a quick info by hand anyway.
Well, I will try to generate full quick info text for nodes and symbols by myself as close as possible to the default quick info text, but it will be not so far.
Would be grateful If I really miss something if someone from community will have a some suggestions for issue.


WIP Port blaze-core to cats-effect-3

https://github.com/http4s/http4s/issues/3837
It's a WIP.
I'd like to receive some early feedback before attacking the websocket part.

Thanks for the feedback @SystemFw !

I'm not blocked by the compilation of the tests: https://github.com/http4s/http4s/pull/3894/commits/e9eeb9511897cca94b575cb1fd69d210547514c9
The 2 specs seems to wait for the same lock. The compilation never completes.

Update: the issue seems to be only on Http4sWSStageSpec. When I comment Http4sWSStageSpec out, the tests can compile. If I comment only Http1WriterSpec out, the tests' compilation never completes.

current status: all tests are now running.
@rossabaker this PR is quite messy as it contains a lot of commits.
Should I open a new PR with one commit?

Should I open a new PR with one commit?

The decision is definitely for Ross, but I actually really dislike that.
In any case, if you do want to do that, there's no need to open a new PR, you can squash on merge (but don't ;))

I agree with @SystemFw.  It also makes it harder to re-review things: we have to look at the whole instead of the recent changes.  I usually never force-push a PR unless I don't think anybody has looked at it yet and I think I can tell a better story with a rebase -i.
The more controversial thing is whether we should squash at merge time or not.  Squash merges make a cleaner history and we can still click through to see the original intermediate commits.  But even then, I think the intermediate commits have value.  In addition to bisection, sometimes we branch off WIP to explore a different direction or, like now, maintain parallel branches through big upgrades.  Squashing is better for history but worse for collaboration, and we've optimize for the latter.
All that said, I'm excited to see the progress, but it's 1:30am here, so I'll have to review it tomorrow.  Hopefully our CE3 experts can keep looking as well.

There is one topic I'm feeling unsure about: I had to create one dispatcher per test in Http4sWSStageSpec to that the tests can run (https://github.com/http4s/http4s/pull/3894/commits/f7d5840e441deb56c22e1bcaf7f8e382107609f4)
But I can still share a dispatcher in Http1WriterSpec.
And this is a change I could eventually rollback: https://github.com/http4s/http4s/pull/3894/commits/c59e3befc5f67d6fc6be949f505d88b4224eae74
Having a timeout when running tests is good not to wait forever. But it also means that slow tests can be flaky in case the timeout is near the execution time.

Is multiple dispatchers a normal usage? I'm a bit worried that having to do that is masking an issue that will prevent the web sockets from working in the real world, but my understanding of CE3 is still a bit hazy.

Thanks to the help from @djspiewak, I could remove blocking calls: https://github.com/http4s/http4s/pull/3894/commits/ce3ea537546a160ab24e56131b867225c6eaedd1
Now all the tests can run with the same Dispatcher. ✌

It was just that unsafeRunSync to create that semaphore in the stage? In CE2, that's a "I promise not to share this" thing. I wouldn't expect it to deadlock things. The Dispatcher is a different world, though.

Yes, the Dispatcher.unsafeRunSync blocks.
https://github.com/typelevel/cats-effect/blob/349fc13c6a6679ebd71168901874ee332e37ff5b/std/jvm/src/main/scala/cats/effect/std/DispatcherPlatform.scala#L29
Every time we use it, we have to keep it in mind. (and we should better not use it)

Anyway, hooray, and great job.

Thanks, that was a long way.
But I've learned a lot, thanks to all the helpful reviews. ❤


[TF v1.1.0] ValueError: Variable dis/BatchNorm/beta already exists, disallowed.

On running
$ python ./src/3dgan_mit_biasfree.py 0 0

Traceback (most recent call last):
  File "./src/3dgan_mit_biasfree.py", line 268, in <module>
    trainGAN(is_dummy=False, checkpoint=None)
  File "./src/3dgan_mit_biasfree.py", line 134, in trainGAN
    d_output_z, d_no_sigmoid_output_z = discriminator(net_g_train, phase_train=True, reuse=True)
  File "./src/3dgan_mit_biasfree.py", line 74, in discriminator
    d_1 = tf.contrib.layers.batch_norm(d_1, is_training=phase_train)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 181, in func_with_args
    return func(*args, **current_args)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/layers/python/layers/layers.py", line 528, in batch_norm
    outputs = layer.apply(inputs, training=is_training)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/layers/base.py", line 320, in apply
    return self.__call__(inputs, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/layers/base.py", line 286, in __call__
    self.build(input_shapes[0])
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/layers/normalization.py", line 125, in build
    trainable=True)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 1049, in get_variable
    use_resource=use_resource, custom_getter=custom_getter)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 948, in get_variable
    use_resource=use_resource, custom_getter=custom_getter)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 349, in get_variable
    validate_shape=validate_shape, use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 1389, in wrapped_custom_getter
    *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/layers/base.py", line 275, in variable_getter
    variable_getter=functools.partial(getter, **kwargs))
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/layers/base.py", line 228, in _add_variable
    trainable=trainable and self.trainable)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/layers/python/layers/layers.py", line 1334, in layer_variable_getter
    return _model_variable_getter(getter, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/layers/python/layers/layers.py", line 1326, in _model_variable_getter
    custom_getter=getter, use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 181, in func_with_args
    return func(*args, **current_args)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 262, in model_variable
    use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 181, in func_with_args
    return func(*args, **current_args)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 217, in variable
    use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 341, in _true_getter
    use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variable_scope.py", line 653, in _get_single_variable
    name, "".join(traceback.format_list(tb))))
ValueError: Variable dis/BatchNorm/beta already exists, disallowed. Did you mean to set reuse=True in VarScope? Originally defined at:

  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 217, in variable
    use_resource=use_resource)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 181, in func_with_args
    return func(*args, **current_args)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 262, in model_variable
    use_resource=use_resource)

Tested only on tf-1.0.0, updated readme with it.


Added centre of attraction and masonry layout #72

All the three layouts are added.
This should solve #71 and #72.
However, leave #71 open till all the options are supported by loklak_server
Known bugs:
Editing a created wall is buggy.

I don't get what I'm checking here.

However files change only touch wall related files, so If you need to merge, please check first if this problem occurs when gulp live, gulp prod, because I have this error locally only with your branch.

@fuksi, both gulp prod and gulp live work perfectly fine locally as well on my vm. Try doing an npm install maybe. Things to check for:

3 layouts: linear, masonry and centre of attraction.
Wall creation options
You can directly change the parameters in the URL itself and refresh, to view the result quickly.


fix alias overwriting when 2 or more connectios are created

fix for #144

eval() is dangerous. http://php.net/manual/en/function.eval.php
The eval() language construct is very dangerous because it allows execution of arbitrary PHP code. Its use thus is discouraged. If you have carefully verified that there is no other option than to use this construct, pay special attention not to pass any user provided data into it without properly validating it beforehand.


Client for Snell

Hello @SebErstellen ,
I'm searching for a Snell clients for Linux. As you know, Snell is a closed-source protocol by Surge so there isn't much of a choice. I'm aware that Clash works with Snell up to version 3.0.1, but I'm wondering if there are any other clients available that supports the latest version of Snell (v4.0.1).
Do you have any experience with Snell clients for Linux or do you know of any Snell clients for Linux that support v4.0.1?
I'd be grateful if you could provide me information you think would be helpful.
Thank you.

I’m also curious to know, but as of now, since no one has reverse-engineered an open port for Shell v4, it appears that Surge is the only client that supports Shell v4.


Allow running ambassador as a non-privileged user

This commit lets ambassador to be run as a non-root user and
moves all ambassador related configurations to /ambassador
inside the container.

@kflynn ready for review, PTAL!
One way to test this locally to run the resulting container image using with a random user -
docker run --user 10001 --rm <image name>

Closing in favor of #524


Update Build Instructions

The build instructions at https://github.com/fsharp/FSharp.Compiler.Service/blob/aafe8521a5eda0bcb4dd8f72895e2ef0348f6757/docs/content/devnotes.md are insufficient for setting up a working development environment.
It is not obvious that https://github.com/dotnet/cli must be installed.
Repro steps
Provide the steps required to reproduce the problem

Install Win 10
Install Visual Studio Dev15
Follow build instructions linked above
Run .\build.cmd

Expected behavior
It builds successfully after following the instructions.
Actual behavior
Error:
Building C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\FSharp.Compiler.Service.sln failed with exitcode 1.

---------------------------------------------------------------------
Build Time Report
---------------------------------------------------------------------
Target               Duration
------               --------
Clean                00:00:00.0030035
AssemblyInfo         00:00:00.0187638
GenerateFSIStrings   00:00:00.1139912
Total:               00:00:01.0330407
Status:              Failure
---------------------------------------------------------------------
  1) Building C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\FSharp.Compiler.Service.sln failed with exitcode 1.
  2) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\src\fsharp\FSharp.Compiler.Service\FSharp.Compiler.Service.fsproj(0,0): The target "Build" does not exist in the project.
  3) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\UntypedTree\UntypedTree.fsproj(0,0): The target "Build" does not exist in the project.
  4) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\FscExe\FscExe.fsproj(0,0): The target "Build" does not exist in the project.
  5) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\EditorService\EditorService.fsproj(0,0): The target "Build" does not exist in the project.
  6) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\Tokenizer\Tokenizer.fsproj(0,0): The target "Build" does not exist in the project.
  7) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\src\fsharp\FSharp.Compiler.Service.ProjectCrackerTool\FSharp.Compiler.Service.ProjectCrackerTool.fsproj(0,0): The target "Build" does not exist in the project.
  8) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\FsiExe\FsiExe.fsproj(0,0): The target "Build" does not exist in the project.
  9) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\src\fsharp\FSharp.Compiler.Service.ProjectCracker\FSharp.Compiler.Service.ProjectCracker.fsproj(0,0): The target "Build" does not exist in the project.
 10) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\tests\service\data\TestTP\TestTP.fsproj(0,0): The target "Build" does not exist in the project.
 11) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\src\fsharp\FSharp.Compiler.Service.MSBuild.v12\FSharp.Compiler.Service.MSBuild.v12.fsproj(0,0): The target "Build" does not exist in the project.
 12) MSB4057: C:\Users\s\Source\github.com\microsoft\fsharp\FSharp.Compiler.Service\samples\InteractiveService\InteractiveService.fsproj(0,0): The target "Build" does not exist in the project.
---------------------------------------------------------------------

Known workarounds
Install https://github.com/dotnet/cli

I have this problem right now, installing dotnet/cli RC3 does not fix it.

For now just use "build All.NetFx".  We should likely make that the default at least on Windows

The fix for this has been integrated


After disable some audio tracks, the video was frozen for more than 10 seconds

Steps to reproduce the problem:

Prepare an mp4 file with multiple audio tracks. Or you can find a file here:
https://github.com/xiashao1980/chrome_audiotracks/raw/master/output9_dashinit.mp4

Enable chrome flag: Experimental Web Platform features

Write a script to enable or disable some tracks of this mp4 file. You can get a sample script here:
https://raw.githubusercontent.com/xiashao1980/chrome_audiotracks/master/test.html

Open test.html in Edge Beta

Enable A1 and A2 of audioTracks. Then disable A1, and now the video frozen for a while but the audio kept playing.

What is the expected behavior?
The video should not be frozen after any track enabled or disabled.
What went wrong?
The video was frozen for about 10 or more seconds and audio kept playing.
This function works fine in Edge. But doesn't work in Edge beta.
Could you fix this problem?

Thank you for this report! Unfortunately, we're unable to take action on it from this Repo. Please re-submit this feedback through the in-browser "send feedback" option ("..." > "help and feedback" or Alt+Shift+i on Windows), or submit a but via crbug.com if you believe this is rooted in the Chromium engine. Submitting via the feedback tool helps us collect relevant diagnostics context that can be helpful in reproducing and fixing the bug. Thanks!


chore: release 4.2.0

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

pad base64 strings for base64js (#722) (81e0a23)

Features

make both crypto implementations support sign (#727) (e445fb3)

Release is at https://github.com/googleapis/google-auth-library-nodejs/releases/tag/v4.2.0

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

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


ConfigMaps for Spark Configuration of the Driver Container

This specification outlines methods for exposing spark configuration
files through ConfigMaps in the container running the spark driver.

yes, thesteve0 was working on a protoytype of that.   We could have 3 levels, and I think it makes sense to have all of them -- base config in the spark image, override from the git repo for your application during s2i if you like, then potentially override at launch time with a configmap if you like.  The outstanding question is how to treat these -- are they merges, or overwrites?  Do I copy my configs into the well-known config dir, overwriting the files I include but inheriting the other ones?  Or do I treat each config as a complete set and just move the SPARK_CONF_DIR env var around?

good points @tmckayus
we can leave those questions for the next iteration of this


problems console has warnings/errors of HEAD-file

VSCode Version: Code 1.6.1 (9e4e44c19e393803e2b05fe2323cf4ed7e36880e, 2016-10-13T16:21:53.542Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions: donjayamanne.githistory-0.1.0, formulahendry.code-runner-0.4.1, slevesque.vscode-hexdump-1.0.1, waderyan.gitblame-1.3.0

Steps to Reproduce:

open any css file with warnings/errors in code
modify file
open git / diff-view
open Problems console

Expected: Problems console has errors/warnings of modified file
Actual: Problems console has errors/warnings of modified file + HEAD-file

I see this too, it's showing errors for the original file when the diff is open.

This is as designed. Extensions generate errors/warnings for all resources.

But this is useless and duplicate information. Why it was so designed?

@SailorMax Agreed. Reason I closed this because There'd been a long discussion on this on coming up with a good strategy for this issue and decided to keep it like it. See #7773.
But, there is another issue which is similar #16674 where I am kinda re-initiate the discussion. I think, I ld have made it dup of #16674 .


Add MaxHorizontalTransformer

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (5c18f7e) to head (fa927b9).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #373   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           52        53    +1
  Lines         1366      1381   +15
  Branches        55        55
=========================================
+ Hits          1366      1381   +15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


enable 8x10 mode for 40v2

40v2 currently only supports 2x40G native, it needs 8x10G as a port configuration option

hdl updated for 8x10 ports. qsfp1 mirrors any Tx traffic (from packet gen) on qsfp0.
only qsfp0 has active capture ports making it 4x10 currently

4x10G mode is commited


[Core]: Add basic named reading of byte buffer

Allows reading of the following types directly from CANMessage object using dedicated functions:

uint8_t
uint16_t
uint32_t
uint64_t
bool

Also adjusted the process_rx_message in VirtualTerminalClient to use these functions already.
Closes #137

have you tested this yet to make sure it still works as expected?

Sort of... I ran the vt_version_3_object_pool example which worked fine, and checked the diff whether my changes were correct. But I could've probably missed something, so feel free do any additional testing if you feel like!


chore:add event for clicked on price display

The type of this PR is: Feature

This PR resolves PX-5361
Description

This PR adds a new event to Cohesion to utilize in Volt for PX-5307.
PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

:rocket: PR was released in v4.86.0 :rocket:


add Cloudwise Synthetic Monitoring

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

LGTM

LGTM

@biukang can you put this in A-Z order ;)?

Update completed

If it's ok, please merge this PR @caniszczyk


changed the todo.py to add a time estamate for task

Added the ability to add the estimated completion time for a task.

Could potentially make time its own tracked variable instead of it being a part of the task variable, but it does work good.

time was changes to be its own variable


fix: cloudflare workers' serve-static module (onNotFound)

Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno

fixes of #1865

Hi, @yusukebe
Could you please review this one too?
I forgot onNotFound in the serve-static module and refactored around it.

How about this?
Since the options.namespace is not deleted, the actual value could come in, but since it has a type, I think we can go with this.
const module = <E extends Env = Env>(
  options: Omit<ServeStaticOptions<E>, 'namespace'> = { root: '' }
) => {
  options.manifest ??= manifest
  return serveStatic<E>(options)
}

@yusukebe exactly, thank you!

@sor4chi
Okay! Land it.


chore: Update screen shots

See the updated results by loading the following link,
https://github.com/arajkumar/fabric8-analytics-vscode-extension/blob/update-screen-shots/README.md

@invincibleJai , I see that image sizes are too big now. Do you have any concerns around it? Shall I convert it to JPEG? WDYT?

@invincibleJai  Actually the README.md changes comes part of this PR is also usable. So I will push it that too.

Actually the publisher tool vsce does the magic of replacing the relative urls with absolute url based on the package.json#repository.url value.
Please see https://github.com/microsoft/vscode-vsce/blob/master/src/package.ts#L412


fix error code link

r? @jamesmunns
(rust-highfive has picked a reviewer for you, use r? to override)

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against gh-pages. Please double check that you specified the right target!

The HTML code is generated during the build so this will solve itself once #489 is through.
Thank you!
Closing.

@eldruin  Is this automatically generated based on the html code completed by github ci? .md -> .html

Yes, it is indeed.


Embeds admin web app into CLI with a yarn command for development

Added an admin-web command to the CLI, but the web app isn't currently bundled properly for distribution so it's a no-op.
yarn start-admin-web allows local development of this very simple admin web app

There's some hackery in local-dev.ts to make serveBundle() work in this new use case - I tried to make the minimal config that would satisfy the type system and work.

Adds some example HTML, CSS and JS as demonstration for how to use each

I'm curious, what are the intended use cases of this?

I'm curious, what are the intended use cases of this?

Good question: my team wants to address the sharp edges of Backstage adoption by providing a simplified "admin page" developer tool that enables a "guided" setup of Backstage (such as setting up authentication with GitHub, integrating with the catalog plugin, and other commonly-used features).
We'll likely prepare an RFC for this once some more unknowns slide into place, which should make the plans here more clear.

@mitchhentgesspotify very excited to see this even though I'm pretty far into my Backstage journey I help a lot of people on Discord (I'm @Ahhhndre) and I think this will really reduce some of the questions we see there.
I mentioned this to Francesco but this really reminds me of the VueJS CLI GUI and you might want to take some inspiration from there as it's pretty beautiful with a great UX/DX IMO -<EMAIL_ADDRESS>

@mitchhentgesspotify btw don't forget to sign your commits it might become a hassle once we want to merge to main.

I've figured that there may be some rebasing and "cleaning up" (as well as changeset management, etc) once we reach a minimum-viable-mergeable state, but I agree that there's no harm in sign-off-ing commits in advance :+1:


feat: indexed multi-methods

Closes #67

I am re-evaluating the idea, an integer index isn't the best choice because it doesn't play nicely with potentially multiple libraries, what we may want is more of a "priority level" where extensions at the same priority are supposed to be non order dependent so we can for example set a "concat" on List<A> to be priority 0 and the rest (append/prepend) with priority 1 (or 1,2 depending) generally speaking the score should be a decimal and may be not unique


Fixed tests

This fixes tests by correctly enabling the session middleware to work. IHP's renderHtml accesses the session to clear possible flash messages 👍

Thanks.


LED Challenge section instructs edit of wrong file.

Corrected the file to be edited to add the GDB configuration in the LED challenge section.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @therealprof (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Someone else already got to this.


AutoPr-StorageSync-anpint-REST Spec PrNumber 5210

Closing as this cannot be merged due to failing test, the user will have to open a new PR and fix the test first.


Code split browser bundle

JS code for the browser is currently all bundled into one multi-megabyte file. The major pages (gene, region, variant, structural variant, etc) can be split into separate bundles and loaded on demand.
https://reactjs.org/docs/code-splitting.html
https://webpack.js.org/guides/code-splitting/

Also split help content out of entry bundle.


TypeError: unhashable type: 'Config' (regression)

When installing the current git master of jinja, with a trivial Flask application:
import flask

app = flask.Flask(__name__)

@app.route('/')
def test():
    return flask.render_template('test.html')

and then:

Creating an empty template/test.html
Running FLASK_APP=test flask run
Loading the page and reloading it in the browser

This happens:
Traceback (most recent call last):
  File ".../site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File ".../site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File ".../site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File ".../site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File ".../site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File ".../site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File ".../test.py", line 7, in test
    return flask.render_template('test.html')
  File ".../site-packages/flask/templating.py", line 138, in render_template
    ctx.app.jinja_env.get_or_select_template(template_name_or_list),
  File ".../site-packages/jinja2/environment.py", line 898, in get_or_select_template
    return self.get_template(template_name_or_list, parent, globals)
  File ".../site-packages/jinja2/environment.py", line 851, in get_template
    return self._load_template(name, self.make_globals(globals))
  File ".../site-packages/jinja2/environment.py", line 815, in _load_template
    new_globals = globals.items() - template.globals.items()
TypeError: unhashable type: 'Config'

This is caused by #1244 / 40a312e80f4f1b25f201293c3f1a840a1b88191d - the commit before that (f71f5ebab2e76c5ee6f5f705a2703f3891e762bc) works fine. Reproducible with Python 3.6.13, 3.7.10, 3.8.8 and 3.9.2.

Thanks for the quick fix - I can confirm things are working fine again! :+1:


MIC-501: update referral -- CFs

Codecov Report
Attention: Patch coverage is 10.34483% with 52 lines in your changes missing coverage. Please review.

Project coverage is 56.40%. Comparing base (4de99fe) to head (6e1e3e0).

Files with missing lines
Patch %
Lines

...rver/routes/journeys/update-referral/controller.ts
5.26%
31 Missing and 5 partials :warning:

...referral/contributory-factor-comment/controller.ts
9.09%
10 Missing :warning:

server/utils/utils.ts
14.28%
3 Missing and 3 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #195      +/-   ##
==========================================
- Coverage   57.18%   56.40%   -0.79%
==========================================
  Files         202      202
  Lines        2845     2895      +50
  Branches      473      497      +24
==========================================
+ Hits         1627     1633       +6
- Misses       1165     1201      +36
- Partials       53       61       +8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Prevent exception in Buffer.concat, when data starts coming too fast

Fix issue like this:
TypeError: Cannot read property 'length' of undefined
    at Function.Buffer.concat (buffer.js:306:24)
    at SerialPort.<anonymous> (/../node_modules/serialport/lib/serialport.js:348:32)
    at SerialPort.<anonymous> (/../node_modules/serialport/lib/serialport.js:364:7)
    at FSReqWrap.wrapper [as oncomplete] (fs.js:614:17)
uncaughtException: Cannot read property 'length' of undefined

seems that branch was already obsolete, but fix is still valid..


[Bug]: Cannot skip login via browser using SHOPIFY_CLI_DEVICE_AUTH=1

Please confirm that you have:

[x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
I was using SHOPIFY_CLI_DEVICE_AUTH=1 to run npm run dev. Previously, it could work for login in my remote server, which couldn't open a browser GUI. After a while, I upgraded my CLI to the latest version and I couldn't login with SHOPIFY_CLI_DEVICE_AUTH=1 npm run dev. I was logged on before but I was logged out suddenly. I don't know why it was.
Is this option still working? Did I miss anything?
Actual behavior
bennychan:~/abc$ SHOPIFY_CLI_ACCESS_CODE_AUTH=1 npm run dev -- --theme 1234

dev
shopify app dev --theme 1234

To run this command, log in to Shopify.
👉 Press any key to open the login page on your browser
Error: spawn xdg-open ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Verbose output
bennychan@Dev:~/myProject$ SHOPIFY_CLI_DEVICE_AUTH=1 shopify app dev --verbose
2024-09-28T10:07:21.393Z: Running command app dev
2024-09-28T10:07:21.430Z: Getting a random port...
2024-09-28T10:07:21.443Z: Random port obtained: 41035
2024-09-28T10:07:21.478Z: cloudflared already installed, skipping
2024-09-28T10:07:21.494Z:
Running system process:
· Command: /home/bennychan/.nvm/versions/node/v21.6.2/lib/node_modules/@shopify/cli/bin/cloudflared tunnel --url http://localhost:41035 --no-autoupdate
· Working directory: /home/bennychan/myProject
2024-09-28T10:07:21.513Z: Reading cached app information for directory /home/bennychan/myProject...
2024-09-28T10:07:21.515Z: 2024-09-28T10:07:21Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2024-09-28T10:07:21Z INF Requesting new quick Tunnel on trycloudflare.com...
2024-09-28T10:07:21.521Z: Reading the content of file at shopify.app.toml...
2024-09-28T10:07:21.534Z: Reading the content of file at shopify.app.toml...
2024-09-28T10:07:21.546Z: Reading the content of file at shopify.app.myProject.toml...
2024-09-28T10:07:21.624Z: Reading cached app information for directory /home/bennychan/myProject...
2024-09-28T10:07:21.626Z: Reading cached app information for directory /home/bennychan/myProject...
2024-09-28T10:07:21.629Z: Reading cached app information for directory /home/bennychan/myProject...
2024-09-28T10:07:21.632Z: Reading the content of file at shopify.app.toml...
2024-09-28T10:07:21.635Z: Reading the content of file at shopify.app.toml...
2024-09-28T10:07:21.644Z: Reading the content of file at shopify.app.myProject.toml...
2024-09-28T10:07:21.712Z: Ensuring that the user is authenticated with the Partners API with the following scopes:
[]
2024-09-28T10:07:21.713Z: Getting session store...
2024-09-28T10:07:21.715Z: Validating existing session against the scopes:
[
"openid",
"https://api.shopify.com/auth/shop.admin.graphql",
"https://api.shopify.com/auth/shop.admin.themes",
"https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
"https://api.shopify.com/auth/shop.storefront-renderer.devtools",
"https://api.shopify.com/auth/partners.app.cli.access",
"https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
"partnersApi": {
"scopes": []
}
}
2024-09-28T10:07:21.716Z: Initiating the full authentication flow...
2024-09-28T10:07:21.717Z: Requesting device authorization code...
2024-09-28T10:07:21.721Z: Sending POST request to URL https://accounts.shopify.com/oauth/device_authorization
With request headers:

User-Agent: Shopify CLI; v=3.67.2
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: linux
Content-Type: application/json
Content-type: application/x-www-form-urlencoded

2024-09-28T10:07:22.109Z: Request to https://accounts.shopify.com/oauth/device_authorization completed in 386 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"869f07dcab045b5fe5d49eae0737acf1"
server-timing: processing;dur=66, socket_queue;dur=1.746, edge;dur=1.024, util;dur=0.0, cfRequestDuration;dur=326.999903
x-request-id: 5225d8e1-7038-4ee6-92f1-3c321c97e390-1727518041

2024-09-28T10:07:22.116Z: Received device authorization code: {
"verification_uri": "https://shopify.com/activate",
"verification_uri_complete": "https://accounts.shopify.com/activate-with-code?device_code[user_code]=SZWQ-BRVQ",
"expires_in": 599,
"interval": 5,
"device_code": "e75f772e-fc22-47d1-98e9-0ba5e80e23d2",
"user_code": "SZWQ-BRVQ"
}
To run this command, log in to Shopify.
User verification code: SZWQ-BRVQ
👉 Press any key to open the login page on your browser
2024-09-28T10:07:26.255Z: 2024-09-28T10:07:26Z INF +--------------------------------------------------------------------------------------------+
2024-09-28T10:07:26Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2024-09-28T10:07:26Z INF |  https://popular-prerequisite-aud-pod.trycloudflare.com                                    |
2024-09-28T10:07:26Z INF +--------------------------------------------------------------------------------------------+
2024-09-28T10:07:26.256Z: 2024-09-28T10:07:26Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2024-09-28T10:07:26Z INF Version 2024.8.2
2024-09-28T10:07:26Z INF GOOS: linux, GOVersion: go1.22.2, GoArch: amd64
2024-09-28T10:07:26Z INF Settings: map[ha-connections:1 no-autoupdate:true protocol:quic url:http://localhost:41035]
2024-09-28T10:07:26.256Z: 2024-09-28T10:07:26Z INF Generated Connector ID: 2682ce3b-65c9-4081-8f0f-fd5eaa7f17d5
2024-09-28T10:07:26.258Z: 2024-09-28T10:07:26Z INF cloudflared will not automatically update if installed by a package manager.
2024-09-28T10:07:26.275Z: 2024-09-28T10:07:26Z INF Initial protocol quic
2024-09-28T10:07:26Z INF ICMP proxy will use <IP_ADDRESS> as source for IPv4
2024-09-28T10:07:26Z INF ICMP proxy will use fe80::6821:d4ff:feb3:9ad9 in zone eth0 as source for IPv6
2024-09-28T10:07:26.288Z: 2024-09-28T10:07:26Z INF Starting metrics server on <IP_ADDRESS>:41205/metrics
2024-09-28T10:07:26.339Z: 2024-09-28T10:07:26Z WRN Your version 2024.8.2 is outdated. We recommend upgrading it to 2024.9.1
2024-09-28T10:07:26.928Z: 2024-09-28T10:07:26Z INF Registered tunnel connection connIndex=0 connection=597e3c6d-bc19-4e26-89a6-ebcdd294b4ec event=0 ip=<IP_ADDRESS> location=sin12 protocol=quic
Reproduction steps
When I run the command SHOPIFY_CLI_DEVICE_AUTH=1 npm run dev, it shows me "👉 Press any key to open the login page on your browser". When I press any key, it shows the error.
Operating System
Ubuntu 20.04
Shopify CLI version (check your project's package.json if you're not sure)
3.67.1, local Shopify CLI.
But it's still the same when I switch to global Shopify CLI
Shell
No response
Node version (run node -v if you're not sure)
v21.6.2
What language and version are you using in your application?
No response

@ranjan-purbey
Thanks for your suggestion. Can you give me an example on how to add the dummy executable? Or what command to run?

@ranjan-purbey
Thanks for your suggestion. Can you give me an example on how to add the dummy executable? Or what command to run?

For example, you can create an executable like this:
mkdir ~/tmp-bin && export PATH=$PATH:~/tmp-bin && echo "#!/bin/sh" > ~/tmp-bin/xdg-open && chmod +x ~/tmp-bin/xdg-open

This script works well; however, I recommend Bash users replace the " with '. Otherwise, you'll get an error in the console.


chore: Delete automated standup assignment

Reviewers
Functional: @ebezzi
Readability: N/A

Changes
Deletions

Remove automated standup assignment notification as our process has now changed and no longer consists of a single unified standup.

Going ahead and merging this as the unit test is already fixed in a feature branch and is unrelated to this change.


Too many syscalls in wasi?

I'm a big fan of Plan9 and its short list of system calls. Is there any reason why wasi has more system calls than Plan9? It seems redundant to have system calls for things that could be made available through the virtual filesystem, such as environment variables and rng as well as syscalls like sock_send and sock_recv that basically duplicate write and read

I agree about sock_send/sock_recv vs fd_write/fd_read :smile:. As it turns out, I'm currently working on a plan to unify them (brief mention here). There are some subtle issues involved, such as the handling of zero-length datagrams in read, so I'm proceeding carefully, but I believe it's doable.
Concerning "everything is a file" more broadly, there are two sides to it, which in WASI terms translate to: "should every capability be initiated through path_open?" and "should every capability be accessed through fd_read/fd_write?". I myself don't presently have an opinion about this, but I can provide some current thoughts.
Should every capability be initiated through path_open?
One issue is that WASI's capability system means that it has no global namespace. /proc/self/cmdline doesn't easily translate because there are no absolute paths. We could conceivably add a preopened capability representing a /proc-like directory, although depending on what we'll eventually want to put in that directory, it may be better to add preopened capabilities for the individual things inside it instead.
Another is that file descriptors are a limited resource. Operating systems have been moving away from /dev/random and /dev/urandom for obtaining random bytes, and toward dedicated system calls, since opening device files requires obtaining file descriptors, and an attacker can, in some situations, cause applications to exhaust the number of available file descriptors, causing a subsequent open to fail, making random numbers unavailable in situations where they otherwise would be available. We could conceivably add randomness a preopened capability though.
We've also heard feedback from others that want to move all filesystem path handling out of Core, because they otherwise have no use for a filesystem concept.
Should every capability be accessed through fd_read/fd_write?
For things which are naturally byte streams, I agree that this makes sense. As I mentioned above I'd like to merge sock_recv/sock_send with fd_read/fd_write.
Should random_get be fd_read? This may make sense, but there are a few things we'd need to figure out first. First, it would probably want randomness to be a preopened capability, for the reasons discussed above. But if we make it a preopened capability, and random_get gets replaced by fd_read, then there's no distinct random_get import, or anything else which statically indicates that a wasm module actually needs randomness. And that's unfortunate, because it's useful to be able to inspect a wasm module and determine whether it needs randomness or not.
A possible path forward for randomness is to introduce the idea of a "WASI manifest", which is something I have some ideas about, but haven't yet had time to fully design. A WASI manifest would be something that could be embedded within a wasm module, either in a custom section, or via specially-named imports, that would effectively request certain preopened file descriptors. If we had that, then we could say that applications only get a randomness capability if they explicitly request it. And then it might make sense to replace random_get with fd_read.
More broadly, a property of WASI that some people find useful is that static imports (and the manifest, when we have such a thing) of a module can be thought of as representing its static capabilities. This concern tends to favor creating more, fine-grained system calls, rather than fewer more generic ones. That said, this is just one consideration among many, and not always the most important one.
One other consideration is typed interfaces. random_get is relatively simple because it does just return a sequence of bytes. For APIs that consume or return typed data, a dedicated system call can be preferable to serializing data into bytes, whether it's text or binary, because dedicated system calls can have a signature which is statically type-checked, eliminating a class of possible runtime failures.

We've also heard feedback from others that want to move all filesystem path handling out of Core, because they otherwise have no use for a filesystem concept.

I've noticed in a different thread @npmccallum requested more of the socket interface to be exposed as system calls, so the runtime they are working on might not need a path interface not because they only need file descriptors, but because the applications they foresee running on it don't need to open files or directories on the host system. Making access to the network available through path may affect @npmccallum's requirements.
A more elegant approach, I think, is to let each wasi application have a root namespace through which services (that use standardized names) would be made available to it and to embed a manifest that would indicate to the runtime which services the application expects. I don't know how many hoops the runtime would need to jump to do this, however, and if it's worth it in the end, unfortunately.

@eugene2k If you look at #74 , my preference is actually to have a more modular approach.
One alternative could be to encapsulate filesystem (including read()/write()) into one module and sockets (including recv()/send()) into another. This allows a clear conceptual distinction while also maintaining compatibility with existing applications and libraries (that might be shallow-ported to WASM).

I tried experimenting with the "everything is a file" model in my ABI designs and ended up switching to separate wasm modules for each concern. This makes statically analyzing the syscall requirements of a wasm binary very straightforward. With a file-based interface it makes syscall resolution a runtime error. This can be solved with additional tooling and custom sections but it seems to be redoing what the wasm module system already has in place.

After a bit of deliberation, I have to agree: the modular wasi approach seems like the way to go.
My initial concern was that wasi will end up growing more and more because the more people use wasi the more use cases they will have and the more interfaces they will want standardized, until, eventually, wasi ends up with a .NET/CLR of its own. My reasoning was that if wasi offered these interfaces through an IPC mechanism, the runtime wouldn't have to get bloated. However, if the host doesn't follow "everything is a file" philosophy, the runtime will get bloated anyway and, sadly, the world doesn't follow this philosophy. Thanks for your time and answers, everyone!

Sounds good.
One additional thing I want to mention here is that WASI APIs don't need to be implemented in the wasm runtime. They're just wasm imports, and so could just as well be implemented by other regular wasm modules. This is actually another reason why modularization as @npmccallum suggests will be useful.
Closing this issue as the original question is answered, but feel free to open new issues if there are any followup questions or ideas!


readme problem

git clone git@github.com:nicolasgarcia214/damn-vulnerable-defi-foundry.git
doesn't allow to clone in my enviroment (bash, ubuntu).
git clone https://github.com/nicolasgarcia214/damn-vulnerable-defi-foundry.git
work ok to me

I'm used to working with ssh so but it makes sense to have a more general command on the docs. Thanks for playing it and let me know how you liked it. 👍


Java Program to Implement Stack API

Proposed title of article
Java Program to Implement Stack AP
Introduction paragraph (2-3 paragraphs):
A stack is a data structure that keeps track of the order in which insertions and deletions are made. Only one end of the stack, referred to as Top, allows insertion and removal. This happens when the stack is totally full, and this happens when the stack completely empties (overflows).
This Java program will put the Stack API into action. The Stack class depicts a last-in, first-out (LIFO) stack of items. It adds five new operations to the Vector class that allows it to be used as a stack. The standard push and pop operations are available, as well as methods for peeking at the top item on the stack, testing whether the stack is empty, and searching the stack for a specific item to see how far it is from the top.
Key takeaways:

Stack API Implementations
Methods in Stack.
Stack interface.

References:
N/A

Hello @jgesare   and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Thank you for submitting your topic.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentation.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
Please feel free to suggest an alternate topic to explore. 🚀


Fix eslint issues

Enable async/await and other ES2017 features
Add missing parenthesis around arrow param

Updated CONTRIBUTING.md to be consistent with what is currently in node master.


(refactor) some opportunities to use diamond operator

this is a update to a new revision of java, that may bring new programmers for to help with the project

[ ] Review Contribution Guidelines

[ ] Sign Gradle CLA

[ ] Link to Design Spec for changes that affect more than 1 public API (that is, not in an internal package) or updates to > 20 files

[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective

[ ] Provide unit tests (under <subproject>/src/test) to verify logic

[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes

[ ] Ensure that tests pass locally: ./gradlew quickCheck <impacted-subproject>:check

[ ] Verify design and implementation

[ ] Verify test coverage and CI build status

[ ] Verify documentation including proper use of @since and @Incubating annotations for all public APIs

[ ] Recognize contributor in release notes

Hi @desmorto! Thank you for the PR.
Could you please confirm that you've signed a Gradle CLA so we can process your PR?

Signed :)

@desmorto I'm afraid that there are still bits of Gradle that need to be compatible with Java 5/6 (e.g. Tooling API) and we don't have clean separation between the bits of Gradle that are Java 7 compatible and those that are Java 5/6.
This would make developing Gradle today harder unless we do a bunch of work that I don't think will happen soon, so I'm going to close this PR for now.
I do appreciate your initiative though, and will happily accept PRs for issues marked help-wanted if you're eager to contribute :)


Controlling text

https://www.loom.com/share/d6f1ed814d2742d0929ffc818796e7ab
https://neetoformhelp.neetokb.com/admin/articles/google-sheets/edit

@gaagul _a please check this issue.

@neerajdotname @AbhayVAshokan The heading node and the paragraph node in the content somehow got merged into one node, I have made changes to the article and the issue is solved, Please take a look at the article.

@gaagul try to re-create this issue on our side. We need to understand what caused this issue.

@gaagul try to re-create this issue on our side. We need to understand what caused this issue.

I tried recreating the issue from our side and could not do so, That was why i looked into the article itself. I will try different approaches to recreate it.

Closing the issue.


Does this library support posting compressed data

I am able use curl and post gzip compressed data to Spink http end point. Can that be achieved using this Java logging library?

Hi @nramprasad85 sorry for the extremely delayed response. Do you have more specifics about the particular endpoint you are looking to use? A link within https://docs.splunk.com/Documentation/Splunk/8.0.2/RESTREF/RESTprolog might be a good starting point to allow us to better answer your question.

Interested in this feature.
I would expect the HTTPClient that you use to natively support gzip compression. There may be a flag to active it.


Panic when updateCqStatusIfChanged in function of Pending() in cluster_queue

What happened:
Panic when updating cluster queue status, error logs below
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xa0 pc=0x195926c]
goroutine 1014 [running]:
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1()
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:116 +0x1e5
panic({0x2402060?, 0x420b580?})
/usr/local/go/src/runtime/panic.go:770 +0x132
sigs.k8s.io/kueue/pkg/queue.(*ClusterQueue).Pending(0x23d8420?)
/workspace/pkg/queue/cluster_queue.go:283 +0x2c
sigs.k8s.io/kueue/pkg/queue.(*Manager).Pending(0xc064e6b788?, 0xc047b0bdc0?)
/workspace/pkg/queue/manager.go:279 +0xa5
sigs.k8s.io/kueue/pkg/controller/core.(*ClusterQueueReconciler).updateCqStatusIfChanged(0xc064e12fa0, {0x2c2dda8, 0xc0671cb050}, 0xc064e6b600, {0x2804ec5, 0x5}, {0x2809bc0, 0x8}, {0x2824f6c, 0x16})
/workspace/pkg/controller/core/clusterqueue_controller.go:647 +0xa8
sigs.k8s.io/kueue/pkg/controller/core.(*ClusterQueueReconciler).Reconcile(0xc064e12fa0, {0x2c2dda8, 0xc0671cae40}, {{{0x0?, 0xa32964?}, {0xc00100f530?, 0x41ac18?}}})
/workspace/pkg/controller/core/clusterqueue_controller.go:198 +0x5eb
sigs.k8s.io/kueue/pkg/controller/core.(*leaderAwareReconciler).Reconcile(0xc04f718a80, {0x2c2dda8, 0xc0671cae40}, {{{0x0?, 0x5?}, {0xc00100f530?, 0xc065035d10?}}})
/workspace/pkg/controller/core/leader_aware_reconciler.go:77 +0x162
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0x2c363b8?, {0x2c2dda8?, 0xc0671cae40?}, {{{0x0?, 0xb?}, {0xc00100f530?, 0x0?}}})
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:119 +0xb7
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc064e13040, {0x2c2dde0, 0xc00069eb40}, {0x253e3a0, 0xc06520a360})
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:316 +0x3bc
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc064e13040, {0x2c2dde0, 0xc00069eb40})
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:266 +0x1be
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:227 +0x79
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2 in goroutine 820
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:223 +0x50c
How to reproduce it (as minimally and precisely as possible):
Not sure how to easily repro it yet. this is observed when we do the capacity updating for a cohort
Anything else we need to know?:

check further log, it saying the panic happens when updating the status for one cluster-queue, let’s say cq-a, there is only log related to this cq-a listed as below

{"level":"Level(-2)","ts":"2024-06-20T16:57:50.608225383Z","caller":"core/clusterqueue_controller.go:167","msg":"Reconciling ClusterQueue","controller":"clusterqueue","controllerGroup":"kueue.x-k8s.io",
Environment:

Kubernetes version (use kubectl version): v1.28.9-eks-036c24b
Kueue version (use git describe --tags --dirty --always): 0.7
Cloud provider or hardware configuration: aws
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign @mbobrovskyi

cc @mimowo

@GithubWangdf do you know if this was increasing or reducing the quotas?

@GithubWangdf did the "capacity updating for a cohort" involve only changing the quotas, or also creating / deleting the CQs?
I ask because it  appears to me there might be a race condition (bug) if the CQ is deleted (and the event is processed here) before calling Pending from updateCqStatusIfChanged that can result in this error.
I guess if this is the case then we could make the Pending function just throw a dedicated "non exist" error, rather than panic.

Seems I don’t need answer the question any more, thanks @mbobrovskyi , @mimowo for the quick action

It's still useful if you can confirm our suspicions, just in case we missed something.

Image gcr.io/k8s-staging-kueue/kueue:v20240621-v0.7.0-10-g6d2f00dc contains the fix.
Please reopen with some more details about the steps you were performing during the panic, if the issue persists.

sure, here is the update, hope it helps.

we didn’t do any CQ deletion
we add one resource flavor to existing CQ
we add a few new CQs, but none of them are triggering any issues, from log, we see those new CQs are handled correctly, only the one which has new resource flavor added has the panic

I suspect a CQ could temporarily be unavailable in the cache while processing an update and that could have caused the issue. Although we should be removing and adding a CQ to the cache while holding the lock, to avoid this.
@mbobrovskyi can you double check?
/reopen

I don't see any other problems that could have caused this issue. We are locking update of ClusterQueue and also we are not removing previous one.
https://github.com/kubernetes-sigs/kueue/blob/main/pkg/controller/core/clusterqueue_controller.go#L319-L321
https://github.com/kubernetes-sigs/kueue/blob/main/pkg/queue/manager.go#L157-L158

/close
@GithubWangdf please reopen with any details about what the actions you performed, if you see the issue again.


Update nl.json

Updated nl strings. Please note a typo in the english string; -> 'pinnnig' -> pinning
If you store the library when pinnnig then this library will always be used

Thanks! ...and for spotting the typo - fixed now.

Thanks! ...and for spotting the typo - fixed now.


Getting a bunch of 404 when Initializers option is activated

Hi,
I currently have an issue with the apiserver daemon using the default options provided. I have a lot of 404 pointing to /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations which is an alpha feature.
Documentation is available here : https://kubernetes.io/docs/admin/extensible-admission-controllers
Not better when activating --feature-gates=Initializers=true flag.
Dec 19 12:43:30 rmxk8sctl01 kube-apiserver[7012]: I1219 12:43:30.665129    7012 wrap.go:42] GET /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations: (167.967µs) 404 [[kube-apiserver/v1.8.5 (linux/amd64) kubernetes/cce11c6] <IP_ADDRESS>:45026]
Removing Initializers from --admission-control flag fixes the problem but I am not sure to know exactly if this alpha feature is needed or not.
In any cases, kubernetes-the-hard-way's apiserver configuration does not seem to be optimal.
What do you think ?
EDIT : Adding --runtime-config=admissionregistration.k8s.io/v1alpha1 solves the issue... feature-gates does not seem to activate anything for that particular feature though.

@hgfischer
If you want to experiment with Initializers, you need to leave the "admission-control" flag AS IS
So, your kube-api server systemd unit will look as follows
--admission-control=Initializers,NamespaceLifecycle,NodeRestriction,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota
--runtime-config=api/all=true,admissionregistration.k8s.io/v1alpha1=true

Current default action: https://github.com/kubernetes/kubernetes/pull/58428

Using this for 1.10.5 - I had to add the --runtime-config option (replacing what is in the guide curently) for this to work. --admission-control however has been deprecated by --enable-admision-control.. which is in the guide.