text:
Number of processes must be at least 1

(desfren) C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2>python inference.py -i  C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2>C:\Users\pompous_pigeon\Videos\bob_final_2.mp4 --ffmpeg_bin ffmpeg/bin/ffmpeg.exe --ffprobe_bin ffmpeg/bin/ffprobe.exe --face_enhance --suffix outx2
C:\Program Files\Python310\lib\site-packages\torchvision\transforms\functional_tensor.py:5: UserWarning: The torchvision.transforms.functional_tensor module is deprecated in 0.15 and will be removed in 0.17. Please don't rely on it. You probably just need to use APIs in torchvision.transforms.functional or in torchvision.transforms.v2.functional.
warnings.warn(
Traceback (most recent call last):
File "C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2\inference.py", line 232, in
main()
File "C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2\inference.py", line 227, in main
run(args)
File "C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2\inference.py", line 155, in run
pool = ctx.Pool(num_process)
File "C:\Program Files\Python310\lib\multiprocessing\context.py", line 119, in Pool
return Pool(processes, initializer, initargs, maxtasksperchild,
File "C:\Program Files\Python310\lib\multiprocessing\pool.py", line 205, in init
raise ValueError("Number of processes must be at least 1")
ValueError: Number of processes must be at least 1

The default num_process is set to one but what you could try is adding the following flag --num_process_per_gpu 1 to force it to use 1 sub-process.
Therefore your command would be:
python inference.py -i C:\Users\pompous_pigeon\Desktop\DE-SRFREN\v0.0.2>C:\Users\pompous_pigeon\Videos\bob_final_2.mp4 --ffmpeg_bin ffmpeg/bin/ffmpeg.exe --ffprobe_bin ffmpeg/bin/ffprobe.exe --face_enhance --num_process_per_gpu 1 --suffix outx2

Additionally consider adding  ffmpeg to your environment variables so it can run automatically without the additional flags:
--ffmpeg_bin ffmpeg/bin/ffmpeg.exe --ffprobe_bin ffmpeg/bin/ffprobe.exe

closed due to inactivity

authors: JuvenileLocksmith cliffordkleinsr

repo: cliffordkleinsr/DE-SRFREN


text:
Spacetime publish error

Hi,
Trying to running this project but got this error inside ./Server file:
spacetime-mud/Server on main via 🦀 v1.70.0
➜ spacetime publish -c spacetime-mud
Error: No such file or directory (os error 2)

My Spacetime instance is running:
➜ spacetime start
2023-08-15T20:45:00.414247Z DEBUG crates/standalone/src/subcommands/start.rs:219: Starting SpacetimeDB listening on 127.0.0.1:3000

(I following this: https://spacetimedb.com/docs/unity-tutorial/unity-tutorial-part-1: "In your terminal or command window, run the following commands. cd Server spacetime publish -c yourname-bitcraftmini")
Version:
spacetimedb tool version 0.6.1; spacetimedb-lib version 0.6.1;

Hardware Overview:
      Model Name: MacBook Pro
      Model Identifier: MacBookPro18,3
      Chip: Apple M1 Pro
      Total Number of Cores: 8 (6 performance and 2 efficiency)
      Memory: 32 GB
      System Firmware Version: 8419.80.7
      OS Loader Version: 8419.80.7

Thanks !
Trob'

Are cargo and rustup available in your path?

rustup wasn't installed...  thanks ;)

source: gharchive/issue

authors: Trobyss gefjon

repo: clockworklabs/spacetime-mud

license_type: permissive

license_source: github-api


text:
Terraform scripts for vsphere

Is there any plan to get terraform scripts for vsphere?
Packer is now available for vsphere but not terraform yet.
Thank you,

You'll have to ask @Phat3  :)

Hi! Unfortunately I don't have the new Terraform config because I use vRealize Automation instead to deploy the lab 😰

Closing as a dupe of #531 - it's listed on the feature requests page: https://www.detectionlab.network/customization/feature_requests/

authors: Phat3 aguduszeit clong

repo: clong/DetectionLab

license: MIT


text:
Question: benchmark-operator-kube clusterrole

What is the clusterrole with name benchmark-operator-kube used for? I cannot find any references in the code.
The clusterrole is defined in file:
https://github.com/cloud-bulldozer/benchmark-operator/blob/master/deploy/40_cluster_role_kubevirt.yaml

hey @fritchie if you are running with cnv/kubevirt that role is needed.

authors: fritchie jtaleric

repo: cloud-bulldozer/benchmark-operator


text:
Updating README.md for both uperf and uperf-scale mode

Description
Updating docs describing the usage of both uperf and uperf-scale mode code changes.

Codecov Report

Merging #785 (be37938) into master (94005cd) will decrease coverage by 0.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #785      +/-   ##
==========================================
- Coverage   53.47%   53.17%   -0.31%
==========================================
  Files           8        8
  Lines         331      331
==========================================
- Hits          177      176       -1
- Misses        154      155       +1

Flag
Coverage Δ

gha
53.17% <ø> (-0.31%)
:arrow_down:

python-3.9
53.17% <ø> (-0.31%)
:arrow_down:

unit
53.17% <ø> (-0.31%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cli/ripsaw/clients/k8s.py
90.00% <0.00%> (-1.12%)
:arrow_down:

Continue to review full report at Codecov.

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

@vishnuchalla just few corrections and also squash commits.

source: gharchive/pull-request

authors: codecov-commenter mukrishn vishnuchalla


text:
Add support to increase RDS instance storage size

In order to enable customers to increase their RDS storage size, we want to expose the ability to pass in the -c '{"storage": $SIZE_IN_GB}' argument with the cf update-service command.
Acceptance Criteria

[ ] GIVEN an existing RDS service instance
WHEN a customer updates their service instance
AND provides the -c flag with a storage increase request (e.g., -c '{"storage": $SIZE_IN_GB}')
THEN their database instance storage capacity is updated

Additional resources/reference

AWS Go SDK documentation for ModifyDBInstance
AWS API User Guide documentation for ModifyDBInstance parameters

Security considerations
None - this would be exposing already existing Cloud Foundry and AWS API functionality.  Furthermore, AWS does not allow you to decrease storage size, which could lead to data loss.
Implementation sketch
With the newly implemented modifyDB command under the hood in the aws-broker, add support to accept JSON parameters via the -c flag and process them just like the createDB method does:

[x] Add support for accepting the database size as a custom parameter; this is already done in the ModifyInstance method in broker.go
[x] Add the database storage size to the modify input (or figure out the right place to do this)
[x] Figure out where to add additional error handling for checking that the storage input is correct (either in the Validate method for the RDSOptions struct or in the ModifyInstance method itself; this will help to make sure that this is an appropriate size increase
[x] Add error handling for the AWS API call in the modifyDB method in rds.go in the case of API errors related to storage size changes
[ ] Add unit tests for adjusting storage size
[ ] Add smoke tests adjusting storage size

@onelittlebecca and I paired a bit on this feature this afternoon to walk through where this change will take place and what it might look like.  Based on our initial walkthrough and discussion, I've updated the information in the issue description with additional reference links and more details regarding the implementation sketch.
We'll schedule more time starting at the beginning of next week to begin tackling the implementation itself!

@onelittlebecca and I are continuing to make progress on this and we feel we have the implementation in place for this support now.  Next up is to get some unit tests in place and then try it out in the dev environment.  Once that's getting closer to done, we'll wrap up with a couple of additional smoke tests for MySQL and PostgreSQL instances.

Pushed to prod this morning!

authors: ccostino onelittlebecca

repo: cloud-gov/product


text:
Refactor/change radio button

c'est juste plus joli

plus reponsive
plus dsfr
plus beau

repo: cloud-pi-native/console


text:
Allow to query view with multiple key

It seems that a view can only be queried with a single key, using the key(Object...) method of com.cloudant.client.api.View. In the meantime, cloudant allows querying using multiple keys (using query parameter keys=...), so it would be helpful to have a method that allow querying using multiple keys (for example a method keys(Object[]) on the com.cloudant.client.api.View class).

See the Fetch all/multiple documents section of the Readme. It has an example of example using a list

Unfortunately, this example works only when querying the "_all_docs" view... I would like to be able to query any view, using simple or complex keys. I managed to do so by adding keys(Object[]) method to the com.cloudant.client.api.View and org.lightcouch.View method, and was wondering if it could be added to the api ?

See byComplexKey() in viewsTest for an example of complex keys. There is a start/end e.g. in byStartAndEndKey() too. Over and above that, we welcome Pull requests

As you can seen the byComplexKey only query with one single complex key. I'd be happy to submit a pull request: do you have a documented procedure on how to create a test account on cloudant to run the project unit tests ? I've tried to run the unit tests using a cloudant database created on Bluemix but didn't succeed...

See #29 for another examples of complex keys with start and end. Maybe if show the http request code, i can comment better. What error did u hit with a bluemix created cloudant for running the tests, there is no difference between one created directly from cloudant.com vs bluemix

I've been able to run the tests on my database, so I've created a pull request for you to review: https://github.com/cloudant/java-cloudant/pull/43

fixed via commit 4773586

Hi,
Please update maven dependency jar(1.0.1) with new code changes.
I am not getting keys(Object... keys) changes with dependency jar.
Thanks,

I want to parse my key into objects. My key is something like this ... Is this possible ?
"key":{
"pId":"xxxx",
"pType":"yyy",
"pName":"xxx",
"spT":"qqqq",
"ind":"Y",
"order":1,
"templ":"aaaaa",
"p":[ "aaaaa"]
}

authors: AparnaPillai46 mariobriggs sbrunot sivakashi

repo: cloudant/java-cloudant

license_source: bigquery


text:
🛑 Cloudback Backend Service is down

In 1bfce1e, Cloudback Backend Service (https://app.cloudback.it/api/health) was down:

HTTP code: 400
Response time: 86 ms

Service restart during deployment to the production

repo: cloudback/status


text:
🛑 cbn.id is down

In 3291282, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 3ca91f0.

repo: cloudbip/upptime


text:
🛑 masterweb.com is down

In 3e2ec40, masterweb.com (https://masterweb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: masterweb.com is back up in edcac10 after 9 minutes.


text:
🛑 sintegrasi is down

In 23779c8, sintegrasi (https://sintegrasi.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sintegrasi is back up in f93ccc4.


text:
🛑 mncplay.id is down

In a187df2, mncplay.id (https://mncplay.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mncplay.id is back up in 9a94025.


text:
🛑 mncplay.id is down

In 1e0eef5, mncplay.id (https://mncplay.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mncplay.id is back up in c732321.


text:
🛑 hostinger.co.id is down

In eeb423d, hostinger.co.id (https://hostinger.co.id) was down:

HTTP code: 403
Response time: 257 ms

Resolved: hostinger.co.id is back up in bdec83f.


text:
🛑 cbn.id is down

In 1431484, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in a1006f0.


text:
🛑 cbn.id is down

In 0cad321, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 4738496.


text:
🛑 puskomedia.id is down

In 52bfcf8, puskomedia.id (https://puskomedia.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: puskomedia.id is back up in 2a03dee.


text:
Update polymorphic relationships have no effect

Hello, and thank you for your awesome work.
I tried to update a polymorphic (one to many or many to many with pivot table) relationship but the relationship do not update in the database. I cannot explain why. I had to add a update method to my Adapter which updates the relationship manually.
Here is the data sent by the client :
data: {   id: "1557",    type: "precaution",   attributes: {     ...attributes   },   relationships: {     precaution_cible: {       data: {         type: "principe-actif", id: "163"       }     }   } }
Thank you

Are you using the $fillable property on the adapter, and if so, is the relation listed in it?

My bad, I did not add the relation in my Adapter class.
Sorry for the inconvenience.

authors: lindyhopchris pharmarin

repo: cloudcreativity/laravel-json-api


text:
Update JdbcOutput.java for JDBC append

Update JdbcOutput.java to resolve JDBC append issue.
DataFrameWriter defaults to Save mode.ErrorIfExists, not allowing for appending to an existing table.
Explicitly set SaveMode to Append.

Hello @jeremybeard,
I am currently using Envelope for a project I am working on, and came across an issue while trying to append when using JDBC as an output, with an planner type of append. I have provided my solution as per this pull request, any feedback and review on the code change would be greatly appreciated.
Best Regards,
Gianfranco Cusmano

repo: cloudera-labs/envelope


text:
added builtin str for compatiblity with python2 and python3

related #1171
added builtin str, especially for https://github.com/cloudera/hue/blob/d3cc8ff366620b90670121eea0bad013cfd74dc1/apps/filebrowser/src/filebrowser/views_test.py#L1286
I tested test cases with OK in the file. apps/filebrowser/src/filebrowser/views_test.py
./build/env/bin/hue test specific filebrowser.views_test:TestFileBrowserWithHadoop

Thanks!

authors: romainr sungpeo

repo: cloudera/hue


text:
Ambiguous column with WHERE ... IN

I'm using ibis 0.8.1. When I use WHERE ... IN with JOIN query, specific column becomes ambiguous.
Error message is as following.
input
#expr = ratings.timestamp.cast('timestamp')
#ratings2 = ratings['userid', 'movieid', 'rating', expr.name('datetime') ]
#joined2 = ratings2.join(movies, ['movieid'])[ratings2, movies['title']]
#joined3 = joined2.filter([joined2.userid == 118205, joined2.datetime.year() > 2001])
#top_user_old_movie_ids = joined3.filter([joined3.userid == 118205, joined3.datetime.year() < 2009])[joined3.movieid]
print(ibis.impala.compile(top_user_old_movie_ids))
cond = joined3.movieid.isin(top_user_old_movie_ids.movieid)
print('--------------')
print(ibis.impala.compile(joined3[cond]))
joined3[cond]

output
SELECT `movieid`
FROM (
  SELECT t1.*
  FROM (
    SELECT t4.*, t2.`title`
    FROM (
      SELECT `userid`, `movieid`, `rating`,
             CAST(`timestamp` AS timestamp) AS `datetime`
      FROM default.`rating_parquet`
    ) t4
      INNER JOIN default.`movie_parquet` t2
        ON t4.`movieid` = t2.`movieid`
  ) t1
  WHERE t1.`userid` = 118205 AND
        extract(t1.`datetime`, 'year') > 2001 AND
        t1.`userid` = 118205 AND
        extract(t1.`datetime`, 'year') > 2001 AND
        extract(t1.`datetime`, 'year') < 2009
) t0
--------------
WITH t0 AS (
  SELECT `userid`, `movieid`, `rating`,
         CAST(`timestamp` AS timestamp) AS `datetime`
  FROM default.`rating_parquet`
),
t1 AS (
  SELECT *, `title`
  FROM t0
    INNER JOIN default.`movie_parquet`
      ON `movieid` = `movieid`
),
t2 AS (
  SELECT t1.*
  FROM t1
  WHERE t1.`userid` = 118205 AND
        extract(t1.`datetime`, 'year') > 2001
)
SELECT t2.*
FROM t2
WHERE t2.`movieid` IN (
  SELECT `movieid`
  FROM (
    SELECT t1.*
    FROM t1
    WHERE t1.`userid` = 118205 AND
          extract(t1.`datetime`, 'year') > 2001 AND
          t1.`userid` = 118205 AND
          extract(t1.`datetime`, 'year') > 2001 AND
          extract(t1.`datetime`, 'year') < 2009
  ) t4
)
---------------------------------------------------------------------------
HiveServer2Error                          Traceback (most recent call last)
/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/IPython/core/formatters.py in __call__(self, obj)
    697                 type_pprinters=self.type_printers,
    698                 deferred_pprinters=self.deferred_printers)
--> 699             printer.pretty(obj)
    700             printer.flush()
    701             return stream.getvalue()

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/IPython/lib/pretty.py in pretty(self, obj)
    381                             if callable(meth):
    382                                 return meth(obj, self, cycle)
--> 383             return _default_pprint(obj, self, cycle)
    384         finally:
    385             self.end_group()

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/IPython/lib/pretty.py in _default_pprint(obj, p, cycle)
    501     if _safe_getattr(klass, '__repr__', None) not in _baseclass_reprs:
    502         # A user-provided repr. Find newlines and replace them with p.break_()
--> 503         _repr_pprint(obj, p, cycle)
    504         return
    505     p.begin_group(1, '<')

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/IPython/lib/pretty.py in _repr_pprint(obj, p, cycle)
    692     """A pprint that just redirects to the normal repr function."""
    693     # Find newlines and replace them with p.break_()
--> 694     output = repr(obj)
    695     for idx,output_line in enumerate(output.splitlines()):
    696         if idx:

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/expr/types.py in __repr__(self)
     48         if config.options.interactive:
     49             try:
---> 50                 result = self.execute()
     51                 return repr(result)
     52             except com.TranslationError as e:

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/expr/types.py in execute(self, limit, async)
    143         """
    144         from ibis.client import execute
--> 145         return execute(self, limit=limit, async=async)
    146
    147     def compile(self, limit=None):

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/client.py in execute(expr, limit, async)
    312 def execute(expr, limit='default', async=False):
    313     backend = find_backend(expr)
--> 314     return backend.execute(expr, limit=limit, async=async)
    315
    316

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/client.py in execute(self, expr, params, limit, async)
    228             raise NotImplementedError
    229         else:
--> 230             return self._execute_query(ast.queries[0], async=async)
    231
    232     def _execute_query(self, ddl, async=False):

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/client.py in _execute_query(self, ddl, async)
    232     def _execute_query(self, ddl, async=False):
    233         klass = self.async_query if async else self.sync_query
--> 234         return klass(self, ddl).execute()
    235
    236     def compile(self, expr, params=None, limit=None):

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/client.py in execute(self)
     47     def execute(self):
     48         # synchronous by default
---> 49         with self.client._execute(self.compiled_ddl, results=True) as cur:
     50             result = self._fetch(cur)
     51

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/client.py in _execute(self, query, results)
    152
    153     def _execute(self, query, results=False):
--> 154         cur = self.con.execute(query)
    155         if results:
    156             return cur

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/impala/client.py in execute(self, query, async)
    117
    118         try:
--> 119             cursor.execute(query, async=async)
    120         except:
    121             cursor.release()

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/ibis/impala/client.py in execute(self, stmt, async)
    225
    226     def execute(self, stmt, async=False):
--> 227         self._cursor.execute_async(stmt)
    228         if async:
    229             return

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in execute_async(self, operation, parameters, configuration)
    287             self._last_operation = op
    288
--> 289         self._execute_async(op)
    290
    291     def _debug_log_state(self):

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in _execute_async(self, operation_fn)
    306         self._reset_state()
    307         self._debug_log_state()
--> 308         operation_fn()
    309         self._last_operation_active = True
    310         self._debug_log_state()

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in op()
    284             op = self.session.execute(self._last_operation_string,
    285                                       configuration,
--> 286                                       async=True)
    287             self._last_operation = op
    288

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in execute(self, statement, configuration, async)
    917                                    confOverlay=configuration,
    918                                    runAsync=async)
--> 919         return self._operation('ExecuteStatement', req)
    920
    921     def get_databases(self, schema='.*'):

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in _operation(self, kind, request)
    847
    848     def _operation(self, kind, request):
--> 849         resp = self._rpc(kind, request)
    850         return self._get_operation(resp.operationHandle)
    851

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in _rpc(self, func_name, request)
    815         response = self._execute(func_name, request)
    816         self._log_response(func_name, response)
--> 817         err_if_rpc_not_ok(response)
    818         return response
    819

/Users/ariga/.virtualenvs/ibis/lib/python3.5/site-packages/impala/hiveserver2.py in err_if_rpc_not_ok(resp)
    602             resp.status.statusCode != TStatusCode.SUCCESS_WITH_INFO_STATUS and
    603             resp.status.statusCode != TStatusCode.STILL_EXECUTING_STATUS):
--> 604         raise HiveServer2Error(resp.status.errorMessage)
    605
    606

HiveServer2Error: AnalysisException: Column/field reference is ambiguous: 'movieid'

+1, I've seen what I think is the same problem.
If I make this expression which joins on a common column, uuid:
detail = imp.client.table('detail', database='taf')
counts = detail.group_by(['uuid','keyword']).size()
max_counts = (detail.group_by(['uuid','keyword']).size()
    .group_by('uuid')
    .aggregate(lambda x: x['count'].max().name('max_count'))
    )
main_kw=(max_counts
  .left_join(counts, ['uuid', max_counts.max_count==counts['count']])
  .projection([counts]))

print(main_kw.compile())

Compiled output:
WITH t0 AS (
  SELECT `uuid`, `keyword`, count(*) AS `count`
  FROM taf.`detail`
  WHERE `date` = 20160901
  GROUP BY 1, 2
)
SELECT t0.*
FROM (
  SELECT `uuid`, max(`count`) AS `max_count`
  FROM t0
  GROUP BY 1
) t1
 LEFT OUTER JOIN t0
    ON t1.`uuid` = t0.`uuid` AND
    t1.`max_count` = t0.`count`

Here the uuid join is properly qualified:
t1.`uuid` = t0.`uuid`.

Now if I keep going and compose a more complex expression:
last_visit=detail.group_by('uuid').aggregate(lambda x: x.ts.max().name('last_visit'))
result = main_kw.left_join(last_visit, 'uuid').projection([main_kw, last_visit.last_visit])
print(result.compile())

compiled output:
WITH t0 AS (
  SELECT `uuid`, `keyword`, count(*) AS `count`
  FROM taf.`detail`
  GROUP BY 1, 2
)
SELECT t1.*, t2.`last_visit`
FROM (
  SELECT *
  FROM (
    SELECT `uuid`, max(`count`) AS `max_count`
    FROM t0
    GROUP BY 1
  ) t3
    LEFT OUTER JOIN t0
      ON `uuid` = `uuid` AND
         `max_count` = `count`
) t1
  LEFT OUTER JOIN (
    SELECT `uuid`, max(`ts`) AS `last_visit`
    FROM taf.`detail`
    GROUP BY 1
  ) t2
    ON t1.`uuid` = t2.`uuid`

Now the columns are not qualified:
    LEFT OUTER JOIN t0 ON `uuid` = `uuid`.

I tried this with a slightly simpler query and the problem did not recur.  It only happened with a few layers of nesting.

thx! @cpcloud

authors: chezou pteehan

repo: cloudera/ibis


text:
[do not merge] Revamp Service Bindings docs for RPC

Consolidates Service binding documentation to be within the Runtime APIs section of the docs.

Currently docs for configuring a Service binding, and docs for how to write code around Service bindings are in separate sections of the docs, which makes getting started hard, requires jumping back and forth between pages. Relevant content from the configuration section has been moved here, and will be removed.
Explains what Service bindings are and what to use them for.

Provides separate code examples RPC and HTTP modes of working with Service bindings.
Todo:

[ ] More thorough docs on the WorkerEntrypoint class
[ ] "Why bindings?" section
[ ] Link to Durable Objects RPC API docs
[ ] Add back in the examples from existing docs, but under their own example/tutorial sections (ex: auth service)

refs https://github.com/cloudflare/workerd/pull/1658, https://github.com/cloudflare/workerd/pull/1692, https://github.com/cloudflare/workerd/pull/1729, https://github.com/cloudflare/workerd/pull/1756, https://github.com/cloudflare/workerd/pull/1757

i need important decision advice. we clear here now.

One final thing: I think it's worth calling out somewhere that the rpc compat flag (or date >= 2024-04-03) is needed specifically on the client.

@elithrar for ✅ stamp so that we have it (not quite merging yet, some redirects, errors)

authors: GregBrimble XoL1507 irvinebroque

repo: cloudflare/cloudflare-docs


text:
[KV] Overhaul KV API docs

this resolves https://github.com/cloudflare/cloudflare-docs/issues/14454 regarding kv
~need to give it a final review tomorrow, but sharing early to get feedback~ Self-reviewed, ready for PR review

Ready for PR review

Converted into https://github.com/cloudflare/cloudflare-docs/pull/16435


text:
[Docs Site] changelog-next

Summary
Adds /changelog-next/ and /changelog-next/.../ routes, with custom styling.
These are authored as distinct MDX files and surface in the /changelog-next/rss.xml feed.
Screenshots (optional)

Preview: https://kian-changelog-next.cloudflare-docs-7ou.pages.dev/changelog-next/


text:
Remove API only mention ?

Unless I'm missing something, the feature can be configured using the Cloudflare Dashboard. API is still available but it's not "required" as the only way to configure Custom Error Response. Right ?

Hi @wolruf
I just checked and the feature is still API only. Are you referring to the error pages you can configure via Custom Pages?
Custom Pages is a different feature, less powerful than custom error responses -- it only depends on the status code returned by the origin server, and you cannot set up an expression to configure an error response for a subset of your traffic.
As stated in the custom error responses documentation, if you configure both, custom error responses will override Custom Pages.

Hi @pedrosousa I'm referring to custom error response (beta), that, I believe, is what is seen in WAF Custom Rule configuration

Hi @pedrosousa where can we document that a custom response for Block actions is a great way to have a maintenance page when such a maintenance is happening on the Origin server (in lieu of using the Origin server) ?

Let's track this internally first — I need to check with PMs what's our best recommendation for this use case.
I created PCX-5140 for this purpose.

authors: pedrosousa wolruf


text:
cloudflare: move HTTP request debugging to httputil

Within the library, we provide a way to output the HTTP interactions that the library makes. We previously used a custom approach and format the output. Even though it works, there are better approaches using httputil.DumpRequestOut and httputil.DumpResponseOut for dumping the HTTP interactions.
Alongside this work, we're adding support for redacting sensitive values in the HTTP interactions. This is useful for both this library and the consumers of this library (like the Terraform Provider) to prevent leaking sensitive information in logs.
Closes #1143

Codecov Report

Merging #1164 (fdc3a7d) into master (6153c1e) will decrease coverage by 0.12%.
The diff coverage is 46.94%.

@@            Coverage Diff             @@
##           master    #1164      +/-   ##
==========================================
- Coverage   49.40%   49.28%   -0.13%
==========================================
  Files         127      128       +1
  Lines       12290    12416     +126
==========================================
+ Hits         6072     6119      +47
- Misses       4840     4896      +56
- Partials     1378     1401      +23

Impacted Files
Coverage Δ

cloudflare_experimental.go
0.00% <0.00%> (ø)

utils.go
72.72% <ø> (ø)

cloudflare.go
68.37% <14.28%> (-0.34%)
:arrow_down:

mtls_certificates.go
26.59% <26.59%> (ø)

origin_ca.go
57.26% <90.90%> (-2.09%)
:arrow_down:

dns.go
68.69% <92.45%> (+4.97%)
:arrow_up:

email_routing_destination.go
66.66% <100.00%> (+0.41%)
:arrow_up:

email_routing_rules.go
65.64% <100.00%> (+0.26%)
:arrow_up:

filter.go
43.38% <100.00%> (+0.41%)
:arrow_up:

firewall_rules.go
54.38% <100.00%> (+0.40%)
:arrow_up:

... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter jacobbednarz

repo: cloudflare/cloudflare-go


text:
rtr.rpki.cloudflare.com public server: "transport error"

Hello,
I have configured my BIRD 2.0.7 router to use rtr.rpki.cloudflare.com public server on port 8282.
Here is the config of bird:
ROA
roa6 table r6;
protocol rpki validator {
roa6 { table r6; };
remote "rtr.rpki.cloudflare.com" port 8282;
retry keep 90;
refresh keep 900;
expire keep 172800;
}

It works for some time but after a while (a few hours or days) the connection is lost, with this error message in bird:
Name Proto Table State Since Info
validator RPKI --- start 10:06:02.441 Transport-Error
have you ever had this problem?

Cloudflare is a public validator on anycast servers. I assume Cloudflare will keep updating server software and when that happens, you will see the TCP connection drop.
BIRD should just reconnect.
However what you should do instead is use two different, geographically diverse validator instances on your own, as opposed to a single, public anycast server.

Cloudflare is a public validator on anycast servers. I assume Cloudflare will keep updating server software and when that happens, you will see the TCP connection drop.
BIRD should just reconnect.
However what you should do instead is use two different, geographically diverse validator instances on your own, as opposed to a single, public anycast server.

yes, for some reason bird doesnt reconnect, but it's more a bird-related problem I guess.
You're right about installing my own validators. I am familiarising myself with this technology before that.

@jranma I can look into the logs for TCP failures but it might be a Bird issue.
rtr.rpki.cloudflare.com is load-balanced, like Lukas said, if we redeploy or do operations on a machine, connection will break.

@jranma I can look into the logs for TCP failures but it might be a Bird issue.
rtr.rpki.cloudflare.com is load-balanced, like Lukas said, if we redeploy or do operations on a machine, connection will break.

It's not a big deal, but if you can look in the logs, that's fine.
My IP: 91.134.140.163 and 2a0c:b641:270::1

it seems to be preferring ipv4
2020-11-27 13:19:19 ipv4 up
2020-12-06 12:19:42 ipv4 down
2020-12-17 11:04:28 ipv6 up
2020-12-17 11:04:30 ipv6 down
2020-12-17 11:08:43 ipv4 up
2020-12-17 12:32:42 ipv4 down
2020-12-18 09:26:35 ipv4 up
2020-12-18 10:56:08 ipv4 down

last event match a crash of a GoRTR instance but system is still available.

thanks @lspgn
my concern is not the disconnection but the fact that bird doesn't reconnect automatically. But this is not the right place to discuss it I think :)

authors: jranma lspgn lukastribus

repo: cloudflare/gortr


text:
Added init_downstream_modules phase allowing modules to be set up before startup

This addresses a roadblock I’ve hit trying to make the new downstream modules mechanism work for me: these cannot be configured from within the HttpProxy instance. The configuration has to happen after http_proxy_service has been called, but at this point the HttpProxy instance has been moved into the service and is no longer accessible. In order to adjust the compression level for example some code outside the actual handler would have to mess with the service configuration which is a significant logic break.
In case of compression this can be addressed by adjusting compression level in early_request_filter. When the handler wants to add its own module however (helps remove some work-arounds I’ve added before), this option is rather suboptimal.
So I’ve added an init_downstream_module phase where HttpProxy can adjust modules to its liking.

When the handler wants to add its own module however (helps remove some work-arounds I’ve added before), this option is rather suboptimal.

Actually, I can see now that the module list is no longer mutable during early_request_filter, so adding modules isn’t even possible there. Hooking into the server initialization is really the only way.

You can access and mutate the modules here. Be this PR also provides a nicer API.
let mut proxy = http_proxy_service(...);
proxy.app_logic_mut().unwrap().downstream_modules

You can access and mutate the modules here.

I know. As I said, doing this via some code outside the handler is possible but a significant logic break.

We've brought this into main as dda7bec58cb176228b8194e97c8c9e52bf36b878. Thanks!

authors: drcaramelsyrup eaufavor palant

repo: cloudflare/pingora


text:
Invalid zone setting "**" (value: ) found - cannot be set as it is read only

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.1.7
on darwin_amd64

provider registry.terraform.io/cloudflare/cloudflare v3.10.0
provider registry.terraform.io/hashicorp/aws v3.74.0

Affected resource(s)

cloudflare_zone_settings_override

Terraform configuration files
data "cloudflare_zone" "zone" {
  name = "example.org"
}

resource "cloudflare_zone_settings_override" "settings" {
  zone_id  = data.cloudflare_zone.zone.id

  settings {
    ssl                         = "full"
    always_use_https            = "on"
  }
}

Debug output
output too long...
Panic output
Error: invalid zone setting "polish" (value: ) found - cannot be set as it is read only
Expected output
All changes applied
Actual output
Error: invalid zone setting "polish" (value: ) found - cannot be set as it is read only
and every time, the setting that causes the error is different (it just throws a random readonly setting every time), but as you can see on the example above, I am never setting it.
Steps to reproduce

Create a zone in Cloudflare
Reference that zone as data on your main.tf
Then add a resource cloudflare_zone_settings_override and use the zone_id from the data from step 2, after this, add the settings block and set one setting such as ssl = "full"
Try to apply the changes

Additional factoids
This happens on both local and latest stable docker image on Gitlab CI
References
Duplicate of #1117

For people who is having this same issue try the following:

Checkout your state file (in case you have it remotely like me), I recommend you switch your backend to a local one (you'll have to do a migration).
Delete the settings_override resource from your state file and also from your tf file
Do a terraform apply
Now re-add the settings_override resource
Do a terraform apply (It should work now!)
Now change your backend back to what it was and do the migration in case needed

I'm not really sure what caused this, but in my case it was because I did a terraform apply, and the script failed while being created (I did the terraform validate, and plan but no errors were thrown).

Thanks for the workaround @davidvpe! But I think you should reopen this issue, it is clearly a bug.

For anyone else running into this, all you need to do is run this before reapplying:
terraform state rm cloudflare_zone_settings_override.example

You neither need to move your remote state, nor edit it directly.

authors: colans davidvpe fionn


text:
CI: add wranglerjs release

fixes #152

I deleted my test tag (v0.1.2); I'm going to go ahead and merge this.

repo: cloudflare/wrangler


text:
Better stemcell alerts

I was talking to @LinuxBozo about the bosh outdated stemcell alerts that I contributed here, and he pointed out it's easy to miss outdated stemcells. If the prometheus deploy that bumps the expected version fails, or gets canceled, or if an operator pauses the concourse job that deploys it, etc, we won't notice if stemcells are out of date.
I'm wondering if we can do better by adding a tiny exporter that emits the current stemcell version for a particular stemcell series. Two quick proposals:
First approach
The stemcell exporter queries http://bosh.io/api/v1/stemcells/ and emits metrics like this:
bosh_stemcell_info{bosh_stemcell_version="3312.29"} 1
bosh_stemcell_info{bosh_stemcell_version="3312.28"} 0
bosh_stemcell_info{bosh_stemcell_version="3312.27"} 0
...

Then we can write a query like this:
bosh_deployment_stemcell_info * on(bosh_stemcell_version) group_left bosh_stemcell_info

This gives a simple prometheus query, but could potentially miss stemcells that are from the wrong series entirely. I don't know if that's realistic, but we can handle that using a different approach:
Second approach
The stemcell exporter emits a single metric, for the expected stemcell:
bosh_stemcell_info{bosh_stemcell_version="3312.29"} 1

Then we can find outdated stemcells by listing all deployments, then subtracting deployments with the expected version:
bosh_deployment_stemcell_info unless (bosh_deployment_stemcell_info * on(bosh_stemcell_version) group_left bosh_stemcell_info)

I'm still new to prometheus, so maybe there's a simpler approach. WDYT?
cc @cnelson

There's a third approach (or complementary to the above). Instead of returning 0 or 1 we can return when the stemcell was released (in unix timestamp format). From here we can match each deployment stemcell with the release date and emit an alert if it's older than x sec/mins/days (time() - (bosh_deployment_stemcell_info * on(bosh_stemcell_version) group_left bosh_stemcell_info) > x).
w/r/t the stemcell series, one thing we can do is to emit also labels for the major and minor versions, both at the bosh_io_exporter and the bosh_exporter. This will allow us to match the exact stemcell series and alert on minor versions.
Oh, and we can do the same for releases :stuck_out_tongue:.

I don't think I care how old a stemcell is in time--I only care whether it's the latest version. If no CVEs get patched over a few weeks it's fine that stemcells are a few weeks old, but if there are a few stemcell updates over a week, allowing stemcells to be a few weeks old would be bad.
I'll think about this more and hopefully write a quick bosh-io-exporter over the weekend.

Let me rephrase it. There're customers that don't live on the edge, and they update stemcells ie once a week. Having an alert that notifies them they don't have the latest stemcell they day after the stemcell has been released doesn't make any sense to them, they know they risk and accept it. Instead, having an alert that notifies them that the stemcells they're using are outdated if the latest one has been released more than 1 week ago make sense, hence that adding the timestamp makes sense. Also I find more intuitive to use a timestamp as value that not 0 or 1.

A few things:

It doesn't look like the bosh-hub api currently includes release timestamps, although that would be a quick patch to https://github.com/cppforlife/bosh-hub/blob/a745e1693e553b5a5a2b07cf76dfb82be8344a93/ui/stemcell/stemcell.go#L224-L234
I think I'm still misunderstanding how you're suggesting the alert would work. As far as I can tell, stemcell releases don't have a regular cadence but happen when cves get patched. Let's say a new stemcell doesn't come out for two weeks, and I configure my alerts to go off after a week. It sounds like I would start getting spurious alerts after a week, which isn't useful--I never want to get alerted if I'm using the current stemcell. Do you mean that we would alert if the stemcell is older than some interval unless it's the latest in the series?

Thanks / sorry if I'm misunderstanding!

No, what I mean is "Alert only if a deployment is not using the latest stemcell in the series and it has been more than x time since it was released". What I want to avoid is to emit alerts if I'm not using the latest one and that one was released yesterday (because I'm upgrading stemcell once a week). I guess this is the same as using the "FOR" clause, but using an alert rule (to not have a pending alert during the FOR time, that can be pretty large).

When you say...

"Alert only if a deployment is not using the latest stemcell in the series and it has been more than x time since it was released"

...do you mean time since the outdated stemcell was released, or time since the current stemcell was released? Based on the situation you're describing, I'm guessing you mean time since current stemcell, since you're trying to avoid annoying alerts right after a stemcell comes out.
It sounds like we would have metrics like this:
bosh_stemcell_info{bosh_stemcell_version="3312.29",current="true"} 1499047468
bosh_stemcell_info{bosh_stemcell_version="3312.28",current="false"} 1499047468
bosh_stemcell_info{bosh_stemcell_version="3312.27",current="false"} 1499047468

...and a query like this:
time() - (bosh_deployment_stemcell_info * on(bosh_stemcell_version) group_left bosh_stemcell_info{current="false"}) > x

Is that what you had in mind?

Yep, something like that will work.

authors: frodenas jmcarp


text:
Upgrade Docker image's Golang to 1.8.1

fixes intermittent STREAM/Protocol errors
probably HTTP/2-related
change default tag v2 -> v6 (gift to future self)
don't install PostgreSQL; it doesn't work

fixes:
E: Package 'postgresql-9.3' has no installation candidate
E: Unable to locate package postgresql-client-9.3
E: Couldn't find any package by regex 'postgresql-client-9.3'

fixes #185

LGTM! can you merge/update the pipeline?

The pipeline should automatically pull in the changes the next run (i.e., we haven't updated the pipeline.yml, only the the tasks' .yml files).

Great point, thanks :)

authors: cunnie johnsonj


text:
Runtimes api endpoint 404

The API docs mention a runtimes api endpoint (for apps) yet we get a HTTP 404 when hitting it. A quick scan of the code suggests it has not been implemented.
Is the goal to use the other endpoints for apps, given that metrics are generic enough that an application/services split may not be necessary? Having looked at what cf-abacus does (and I like it a lot, I think we can get huge benefit from it) , making things just a little more abstract and not having a hard apps/services split in the model (and perhaps also not forcing the model to mirror CF so tightly) would make it more flexible as we try to build a cloud platform featuring not just CF, but other runtimes also (much like Bluemix)

The API docs mention a runtimes api endpoint (for apps) yet we get a HTTP 404 when hitting it.  A quick scan of the code suggests it has not been implemented.

Yes, the code doesn't yet implement all the APIs listed in the doc. The idea here is to evolve the APIs and implementation together with the community over time.

Is the goal to use the other endpoints for apps, given that metrics are generic enough that an application/services split may not be necessary

One goal is to get that kind of feedback and ideas from the community, so this is good feedback :smiley:
We had that applications/services split in our initial implementation for Bluemix, and that's one of the main reasons why we still have it in the doc. Then, as the service usage APIs evolved over time to support more service providers, they became more generic and you're right that they could easily be used for runtimes too now.
For example -- just brainstorming here -- if we renamed 'service_id' to a more abstract 'resource_id' or made it a service_id | runtime_id choice in the schemas, and with a few other minor adjustments (we'd have to work out the details) we could probably make the same API work for runtimes as well.

Check the comments in eede09f which describe how we've now combined service usage and runtime usage into a single (simpler) API. Let us know if this does what you had in mind or if you have any more ideas on this.

authors: johnmcteague jsdelfino

repo: cloudfoundry-incubator/cf-abacus


text:
Create npm release

We need to publish all the modules (with the custom time provider).

We need to publish a new dev version with all changes in Abacus

modules are published as 0.0.6-dev.9

authors: hsiliev nmaslarski


text:
Bump node to 8.9.0

Add eval performance test

Coverage increased (+0.02%) to 91.332% when pulling f5667f3c82e448c38655a439c3d90b5e7d1cde83 on SAP:eval_perf into 7597f96ed97c60bd24d22eeeacdb97bc945bb418 on cloudfoundry-incubator:master.

Coverage remained the same at 91.361% when pulling c4768c7c6e454b38a249ac9910187673d23383b5 on SAP:eval_perf into 2bed1355160623eee2f917d1f45343b1ae14dbe4 on cloudfoundry-incubator:master.

Coverage remained the same at 91.361% when pulling c4768c7c6e454b38a249ac9910187673d23383b5 on SAP:eval_perf into 2bed1355160623eee2f917d1f45343b1ae14dbe4 on cloudfoundry-incubator:master.

Coverage remained the same at 91.361% when pulling c4768c7c6e454b38a249ac9910187673d23383b5 on SAP:eval_perf into 2bed1355160623eee2f917d1f45343b1ae14dbe4 on cloudfoundry-incubator:master.

Coverage remained the same at 91.295% when pulling a360a158b007f055a64cc44ffc100779d07d89da on SAP:eval_perf into bf694da69505ca2b23111a55b048aee96a9a869e on cloudfoundry-incubator:master.

Coverage remained the same at 91.295% when pulling a360a158b007f055a64cc44ffc100779d07d89da on SAP:eval_perf into bf694da69505ca2b23111a55b048aee96a9a869e on cloudfoundry-incubator:master.

authors: coveralls hsiliev


text:
Upstream patch for opi BPM

Ties to https://github.com/cloudfoundry-community/eirini-bosh-release/pull/69.
Part of the effort to upstream patches we currently have on kubecf - https://github.com/SUSE/kubecf/issues/12.

@jimmykarily how hard would it be to get this in the eirini BOSH release?

@f0rmiga if that gets merged, wouldn't we remove the patch altogether?

@viovanov Yes. In any case, I wanted to have this merged here so we don't get confused about differences in what we have in the patch and what we have upstream as a PR.

The eirini bosh relese is becoming obsolete because of #651

repo: cloudfoundry-incubator/kubecf


text:
a

a

This is closed because it's for testing


text:
Update auto-release pattern

Previously, if the patch version of the CLI was bumped due to the check-for-updated-binary-version task returning successfully, then the check-for-patched-cves task afterward would fail because it would try to look up the new version as a git tag. If that didn't cause a failure and it also returned successfully, the version could have been bumped twice.
Now, the golang-release task scripts create a
release-notes/needs-release file when the condition for the script is met. This allows us to chain the scripts together, build up release notes from each script, then bump a single time if any of the scripts were successful.

See also: https://github.com/cloudfoundry/bosh-package-golang-release/commit/be6d9118f0a12a9db822e237237cc9c2e732c611

repo: cloudfoundry/bosh-cli


text:
Update ubuntu stemcell libpcre3

There is a vulnerability in libpcre3_1:8.31-2ubuntu2.1 and it should be updated to libpcre3_1:8.31-2ubuntu2.2.
Whats the best way of doing that?

Story: https://www.pivotaltracker.com/story/show/117646763 as requested.

Updated in stemcell 3215.4 - https://github.com/cloudfoundry/bosh/releases/tag/stable-3215.4

authors: cppforlife dlapiduz dpb587-pivotal

repo: cloudfoundry/bosh


text:
as an operator, i expect to be able to retrieve exact same manifest t…

…hat was submitted
Manifest text, which is sent to director, is stored at database and retrieved from it without modifications.
Manifest.load_from_hash was renamed to Manifest.load_from_text according to input parameter type.
New :manifest_file option was added to deploy method of IntegrationExampleGroup to support ability to pass manifest files from fs directly.
Usage of hash which is based on manifest text in the actual deployment process is out of the scope
(#150869116)[https://www.pivotaltracker.com/story/show/150869116]
Signed-off-by: Konstantin Maksimov kmaksimov@ru.ibm.com

Hi @barthy1 , I revert the pr because it has some un-intended consequence. To be more specific, if we use latest version in manifest and upload a newer version of the release after the initial deployment, when we recreate vm, it will automatically bump all the instances to use the latest release version. One potential way to solve this problem is to still use the old hash in planner_factory.rb, and record the manifest returned to user in a different location, so that we can separate the internal representation of manifest from manifest presented to the user.


text:
Add name parameter to cloud_configs_controller

What is this change about?
This change add a name parameter to the cloud_configs_controller.rb.
This is required to the fix https://github.com/cloudfoundry/bosh-cli/issues/542
In general this solves a inconsistency between the options of command update-runtime-config and update-cloud-config
This PR is prerequisite for: https://github.com/cloudfoundry/bosh/pull/2390
Please provide contextual information.
https://github.com/cloudfoundry/bosh-cli/issues/542
What tests have you run against this PR?
I ran the bosh-director unit tests
How should this change be described in bosh release notes?
cloud_configs_controller offers a --name parameter to upload, diff and retrieve a named cloud config
Does this PR introduce a breaking change?
no
Tag your pair, your PM, and/or team!
PO: @friegger

Looks great. Thanks!

authors: jpalermo mvach


text:
set use_single_app_instance config through env var

Modified the shared-functions to use a given password and not credhub
Changes to be less diego specific

Hey @vitreuz, we've updated the PR based on your feedback. Let us know if this looks good.


text:
cf push returning a 403 for a user

Please fill out the issue checklist below and provide ALL the requested information.

[X] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[X] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[X] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
When pushing a staticfile app with cf push command, got a 403 error even when the user has correct permissions/roles in the org and space.
Error:
You are not authorized to perform the requested action
What happened
Below is the part of the call trace that failed:
Creating app nyan-sample-app-1...
REQUEST: [2018-09-20T12:04:18-07:00]
POST /v2/apps HTTP/1.1
Host: api.system.aws-usw02-dev.ice.predix.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: cf/6.39.1+efdd631d2.2018-09-18 (go1.10.4; amd64 darwin)
{
"memory": 64,
"name": "nyan-sample-app-1",
"space_guid": "e81e6cde-d667-4977-a054-5700c4e0fed6"
}
RESPONSE: [2018-09-20T12:04:18-07:00]
HTTP/1.1 403 Forbidden
Connection: keep-alive
Content-Length: 131
Content-Type: application/json;charset=utf-8
Date: Thu, 20 Sep 2018 19:04:17 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 22980fc5-0f70-4a12-6dbe-179a6bfbd131
X-Vcap-Request-Id: 7eccdad5-810e-4933-62ff-c82e06e3323a::f675ce61-f691-4d38-a9ca-d8d7717b5dd0
{
"code": 10003,
"description": "You are not authorized to perform the requested action",
"error_code": "CF-NotAuthorized"
}
You are not authorized to perform the requested action
FAILED
Expected behavior
The app should push successfully. The user is a spacemanager and orgmanager in the org and space.
To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

Run cf ...
Bind a service cf bind-service
See error

Provide more context

platform and shell details ( e.g. Mac OS X 10.11 iTerm) Mac OS terminal
version of the CLI you are running : cf version 6.39.1+efdd631d2.2018-09-18
version of the CC API Release you are on : 2.92.0

Note: As of January 2018, we no longer support API versions older than 2.69.0/3.4.0 (CF Release: 251 / CAPI Release: 1.15.0)

Hey @nayanchandni thanks for raising this issue. In order to perform this operation, you must either have an admin or space developer role. Please see our roles and permissions page for more information. Do not hesitate to reopen or create a new issue if you have additional questions (or find us on Cloud Foundry slack at #cli).

authors: abbyachau nayanchandni

repo: cloudfoundry/cli


text:
Response time on "cf apps" call on v2 vs. v3 api

Issue
We measured the response time on cf apps calls of the v2 api and the v3 api and observed a significantly increased response time on the v3 api.
Context
On one of our large landscapes we have a space with ~700 apps.
If cf apps gets called it takes about 4-5 minutes which is barely acceptable for customers. However if we use cf7 apps the response time increases to ~2 hours (Yes we triple checked this) which is absolutely not acceptable. We dug deeper into this and found the following:
In the V2 api it is just called:

/v2/spaces/someguid/summary - This call alone takes 300-450 seconds to come back.
In the space with 700 apps it made about 111000 select statements during this time period.
So the time increase per app on that scale seems to be ~0.5 - 1 second.

In the V3 api there are several calls made:
First to get all the apps:

/v3/apps?space_guids=someguid - This call takes about 5 seconds (totally fine)

The Problem seems to be that after the initial call that gets all apps, for every app found there are more calls:

/v3/apps/someguid/routes - This call takes about 4-6 seconds
/v3/apps/someguid/processes - This call takes about 1-2 second
/v3/processes/someguid/sidecars - This call takes about 1-2 second
/v3/processes/someguid/stats - This call takes about 1-2 second
... that are the ones that took the longest.

That adds up to a total time of ~700 apps x ~10 seconds = ~7000 seconds = ~2 hours.
So the time increase per app on that scale seems to be 10 seconds.
Steps to Reproduce
Not sure if reproduce-able due to the size of the landscape this problem was observed on. We were not able to reproduce the exact times mentioned here on a development landscape. Nevertheless we observed, that the time increase and the number of calls that are executed for cf apps and cf7 apps scale with the number of apps per space.
Expected result
300-450 seconds is barely acceptable for customers working with the cli and websites which use the cli to display all apps in a space are not usable at all. But the v2 (cf apps) can still be used with a bit of patience. However the v3 api (cf7 apps) with more than 2 hours of loading time is not useable with the mentioned amount of apps in a space. We would expect the loading time of the v3 api to be at least as fast as the v2 api.
Current result
The v2 api outperforms the v3 api on a big landscape that has a space with ~700 apps in it on the cf apps (cf7 apps) call.

Thanks for filing this! We have also noticed that cf7 apps is quite slow, and we very recently did some work to investigate and fix it. Here are some stories:
https://www.pivotaltracker.com/story/show/172461503
https://www.pivotaltracker.com/story/show/172625875
https://www.pivotaltracker.com/story/show/172625783
These changes are not yet widely available. They require the newest CAPI version (which may not be in a cf-deployment version yet), and the master branch of the CLI. You're welcome to try it out, if you want, or you can wait for these changes to be released.
I do not think we have matched the performance of v2/v6 exactly, but we made some dramatic improvements!
Some rough numbers from our testing on a small BOSH-lite environment with 20 apps in the targeted space:

cf6 took 1.414s
cf7 before our optimizations took 9.609s (this is the version you're using, I believe)
cf7 after our optimizations took 3.265s


text:
No pageable way to gets users by space or org

Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
We would like to be able to get users by space or org and the v3 endpoints do not allow that specification in a pageable format.  We could page through the roles endpoints, then process all of the roles to group by users.  But the problem with going through the roles endpoint is that we get inconsistent page sizes when it comes to displaying users and their roles in a table.
Ideally we would have a consistent way to get a page of unique users for a space or org, and then pull all their associated roles
Context
We are updating an app to use v3 endpoints from v2 and while upgrading GET /v2/spaces/:guid/user_roles and GET /v2/organizations/:guid/user_roles endpoints we could not find a comparable way in v3 to construct a consistently sized table of users and roles via pagination.  We expect to have lots of users, so we would like to be able to paginate these requests in order to retrieve the information in a performant way.
Possible Fix

Replicate the user_roles endpoints
Create a v3/space/:guid/users and v3/organizations/:guid/users
Add a group_by filter to the roles endpoint

We think 2 is the most feasible and reasonable based on the 1. being a composite endpoint and 3. might be computationally hard

Reopening as the org level endpoint has not been completed

This was released as part of CAPI 1.117.0

authors: JenGoldstrich moleske sweinstein22


text:
[Feature]: API Client can update a route via PATCH /v3/routes/

Blockers/Dependencies
No response
Background
As a client of the API shim
I want to be able to update a Route
So that I can modify the route's properties
Acceptance Criteria
TODO
Documentation
Document this endpoint in our API docs
Dev Notes

Update a route

Closing this since we're tackling it as part of the Labels/Annotations epic. See: https://github.com/cloudfoundry/korifi/issues/1446

authors: davewalter tcdowney

repo: cloudfoundry/korifi


text:
Add Laravel Example with updated Image View component for Optimization

After completing a recording for a Cloudinary Dev Hint, I came across a Github Issue for the Laravel Cloudinary SDK that was closed but not merged.
I wanted to create an example folder showing what a component with additional features for format() and quality() options might look like.

hey thanks @joshcirre can you do me a favor and see if anything needs updated in the README for getting started with the example?
it probably doesnt need all that upload stuff, i think that was copied from the other example right?

hey @joshcirre no rush on this at all but just bumping in your inbox for whenever you have the time!

authors: colbyfayock joshcirre


text:
Laravel 9.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.
Before merging, you need to:

Checkout the l9-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: The latest version of Laravel has a dependency for phpunit/phpunit of ^9.3. If you would like to also upgrade your tests, you may run the PHPUnit 9 Shift for free.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/cloudinary-laravel.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "cloudinary-labs/cloudinary-laravel": "dev-l9-compatibility",
    }
}

Finally, run: composer update

@unicodeveloper would be nice to approve this change.

hi! any timeline on merging this pull request? thank you!

ping @unicodeveloper

@unicodeveloper thanks for the 1.0.5 update!

@mpowell-atomic glad to make the update!

authors: SlimGee laravel-shift mpowell-atomic parth391 unicodeveloper

repo: cloudinary-labs/cloudinary-laravel


text:
Support for Azure SQL Service

This is a (Bug Report / Feature Proposal)
Description
For bug reports:

What went wrong?
What did you expect should have happened?
What was the config you used?
What stacktrace or error message from your provider did you see?

For feature proposals:

What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.

This allows nodecloud to extend its first support to SQL service of Azure Cloud Provider. :1st_place_medal:

If there is additional config how would it look

Similar or dependent issues:
Additional Data

Operating System:
Stack Trace:
Provider Error messages:

Closing this issue as it will be taken care in GSoC project

repo: cloudlibz/nodecloud


text:
chore: Cleanup unused code

Description
Run npx knip (static analyzer to detect unused code) and then manually a fix some false matches
Related links, issue #, if available: n/a
How has this been tested?

PR build
npm start locally
dry-run 7136287246

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I explained it in my pre-review comment: https://github.com/cloudscape-design/components/pull/3081#discussion_r1864659773
There were some unused types which were hanging in the code only because they were exported. This is more useful than keeping an export "just in case". You can always restore the export of ComponentNameProps type if you actually have a use for it

repo: cloudscape-design/components


text:
GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.14.258",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8af815ab052eaf74addbbfb556d63ce2137c0e1b"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "8af815ab052eaf74addbbfb556d63ce2137c0e1b",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ALSA: pcm: oss: Fix negative period/buffer sizes\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.258 by commit 8af815ab052eaf74addbbfb556d63ce2137c0e1b. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002406

repo: cloudsecurityalliance/gsd-database


text:
Add RunWithClient in truncate package in order to pass a client as an argument

Hello!
Thanks a lot for the incredible work on spanner-truncate.
While utilizing this code, I realized there are opportunities to enhance its convenience and usability as a package. I've made these small changes and would be really grateful if you could take a moment to look over this PR.
Background
I considered using the truncate package to implement data migration code, which includes truncating specific tables. While the Run method internally generates a client, I thought that reusing the same client for a series of processes would enhance efficiency and reduce overhead in the calling code.
Changes

Added the RunWithClient function. This change allows external callers to pass a Spanner client to the function.
Upgraded spanner library in order to use spanner.Client#DatabaseName.
Updated Readme to add description of RunWithClient.

Benefit
By enabling the caller to utilize the same client that may be used for subsequent database operations, it improves efficiency and reduce overhead in my opinion.
Before changes on this PR
// generates a client for a series of processes
client, err := NewSpannerClient(ctx, projectID, instanceID, databaseID)
if err != nil {
    return err
}

// truncate specific tables
// uses an internally generated client
if err := truncate.Run(ctx, projectID, instanceID, databaseID, false, os.Stdout, targetTables, excludeTables); err != nil {
    return err
}

// some follow-up database operations using the client
if err := followUpOperation(ctx, client); err != nil {
    return err
}

After changes on this PR
// generates a client for a series of processes
client, err := NewSpannerClient(ctx, projectID, instanceID, databaseID)
if err != nil {
    return err
}

// truncate specific tables
// uses an externally passed client
if err := truncate.RunWithClient(ctx, client, false, os.Stdout, targetTables, excludeTables); err != nil {
    return err
}

// some follow-up database operations using the client
if err := followUpOperation(ctx, client); err != nil {
    return err
}

v0.1.2 was tagged. Go package will be updated soon: https://pkg.go.dev/github.com/cloudspannerecosystem/spanner-truncate/truncate

Now it's available: https://pkg.go.dev/github.com/cloudspannerecosystem/spanner-truncate@v0.1.2/truncate

authors: shuto-facengineer yfuruyama

repo: cloudspannerecosystem/spanner-truncate


text:
kitex proto文件生成service，运行报错：undefined: descriptorpb.Default_FileOptions_PhpGenericServices

kitex proto文件生成service，undefined: descriptorpb.Default_FileOptions_PhpGenericServices
kitex version: v0.11.3
go version: go1.23.1 darwin/arm64
api.proto
syntax = "proto3";

package api;

import "google/protobuf/descriptor.proto";

option go_package = "/api";

extend google.protobuf.FieldOptions {
  string raw_body = 50101;
  string query = 50102;
  string header = 50103;
  string cookie = 50104;
  string body = 50105;
  string path = 50106;
  string vd = 50107;
  string form = 50108;
  string go_tag = 51001;
  string js_conv = 50109;
}

extend google.protobuf.MethodOptions {
  string get = 50201;
  string post = 50202;
  string put = 50203;
  string delete = 50204;
  string patch = 50205;
  string options = 50206;
  string head = 50207;
  string any = 50208;
  string gen_path = 50301;
  string api_version = 50302;
  string tag = 50303;
  string name = 50304;
  string api_level = 50305;
  string serializer = 50306;
  string param = 50307;
  string baseurl = 50308;
}

extend google.protobuf.EnumValueOptions {
  int32 http_code = 50401;
}

user.proto
syntax = "proto3";

package user;

option go_package = "user";

import "api.proto";

message UserReq {
  string Name = 1[(api.query)="name"];
}

message UserResp {
  string RespBody = 1;
}

service UserService {
  rpc Method1(UserReq) returns(UserResp) {
    option (api.get) = "/user";
  }
}

执行命令：
kitex -service user -module kitex_demo idl/user.proto

运行提示：
github.com/golang/protobuf/protoc-gen-go/descriptor
/go/pkg/mod/github.com/golang/protobuf@v1.5.2/protoc-gen-go/descriptor/descriptor.pb.go:106:61: undefined: descriptorpb.Default_FileOptions_PhpGenericServices
需要把github.com/golang/protobuf 1.5.2升级到1.5.4才能解决

嗯，protobuf 1.5.2 引入了一个不兼容变更。是这个版本的话需要替换下（但 kitex 默认的依赖并不是1.5.2，可能是你其他地方引入了）。升级到1.5.4就是protobuf官方给出的解决办法之一。

authors: HeyJavaBean ifrans

repo: cloudwego/kitex


text:
feat(tool): add protoc plugin flag

What type of PR is this?

feat
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
为 kitex 工具添加 protoc 插件选项
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:  add protoc plugin option for kitex tool
zh(optional): 为 kitex 工具添加 protoc 插件选项
Which issue(s) this PR fixes:

添加 protoc 插件选项，拓展第三方插件的接入。
需要 protobuf 的 go_package 以 "{$MODULE}/kitex_gen/x/y/" 这种形式定义。
添加插件的选项 protobuf-plugin 的参数形式为 "plugin_name:plugin_options:out_dir"，分别对应 protoc 指定插件的命令。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@FGYFFFF 测试挂了，还需要修下

authors: CLAassistant FGYFFFF joway


text:
在实现discover时候watch方法一直提示不符合签名

但是我经过多次对比，并没有找到区别

你看下你的 async_broadcast 的版本是否一致

你看下你的 async_broadcast 的版本是否一致

大佬您好，我看了一下，版本都是0.7

你好，你可以把 async-broadcast 版本降低到 0.6 再试试看，非 main 分支上的版本依赖的还是 0.6

@PureWhiteWu 我们是不是把 async-broadcast 的依赖版本改成用 *或0 比较好，这样应该就可以保证和用户依赖到的版本一致？

@Millione 不太合适，主要原因有几个：

带有版本为 * 的依赖是无法 publish 到 crates 上的；
写 0 的话，不能保证用户也用的 “0”，而且这样也很容易产生 break change；
更好的方案还是 re-export 一下

或者可以看看这里能不能改成用 tokio 的实现

@Millione 不太合适，主要原因有几个：

带有版本为 * 的依赖是无法 publish 到 crates 上的；
写 0 的话，不能保证用户也用的 “0”，而且这样也很容易产生 break change；
更好的方案还是 re-export 一下

改为 async-broadcast=">=0.6"呢

@iamazy 还是问题 2，比如如果 async-broadcast 发了一个版本 0.8 产生了 break change，那用户就会编译失败。

authors: Millione PureWhiteWu brian-god iamazy

repo: cloudwego/volo


text:
ported_token_1_noun-Causal is overall not good

I've been systematically looking at extractions and the overwhelming majority of extractions by ported_token_1_noun-Causal aren't right. The failures come from actual texts but I could reproduce them on minimal examples in the shell.
The issue seems to be that causal relationships are extracted from non-causal phrases due to inadvertently being triggered by a noun e.g. "IPC Phase Source", "food aid delivery", "several aid agencies", "social support networks", "climate change impacts", "methodological limitations identified", and the list goes on. There are some cases where the phrase does have some sort of a causal influence in it like "fuel options compound food insecurity risk" but even in these cases the cause and effect are assigned in the opposite of what I would expect, (i.e. food insecurity risk causes fuel options, delivery causes food, impacts cause climate, etc.).
While the above examples are not due to this, I also think that this rule is particularly sensitive to messy PDF to text conversions where groups of disconnected nouns can show up next to each other, separated by spaces, even though they don't actually appear in a real sentence.

Having reviewed extractions with the latest version of Eidos, I can confirm that this is still an issue

thanks!
On Fri, Apr 6, 2018 at 4:53 PM, Benjamin M. Gyori notifications@github.com
wrote:

Having reviewed extractions with the latest version of Eidos, I can
confirm that this is still an issue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/issues/264#issuecomment-379413872, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniVlj2YWn85D8jX0sV-IRZI1kSn0tks5tmAAWgaJpZM4TJjf_
.

authors: bgyori bsharpataz

repo: clulab/eidos


text:
add a http server in agent predictor and scheduler call predictor

Signed-off-by: yinsenyan yinsenyan@tencent.com

What type of PR is this?
feature
What this PR does / why we need it:
communication for predictor and scheduler
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #367 (e61c111) into main (122bc21) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #367      +/-   ##
==========================================
- Coverage   12.92%   12.85%   -0.07%
==========================================
  Files          53       53
  Lines        5331     5335       +4
==========================================
- Hits          689      686       -3
- Misses       4594     4600       +6
- Partials       48       49       +1

Impacted Files
Coverage Δ

...ernet/clusternet/pkg/hub/apiserver/shadow/utils.go
89.28% <0.00%> (-10.72%)
:arrow_down:

...ithub.com/clusternet/clusternet/pkg/agent/agent.go
1.79% <0.00%> (-0.02%)
:arrow_down:

...thub.com/clusternet/clusternet/pkg/agent/option.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter yinsenyan

repo: clusternet/clusternet


text:
CI conflict with code

What happened?
1· pipeline workflow always download golangci-lint@1.46.2
2. ci staticcheck error with not changed code  pkg/storage/internalstorage/config.go#L8
What did you expect to happen?
pipeline succeed
How can we reproduce it (as minimally and precisely as possible)?
as what happened
Anything else we need to know?
No response
Clusterpedia Version

# replace the pod name of clusterpedia apiserver
$ kubectl -n clusterpedia-system exec {clusterpedia-apiserver-pod-name} -- apiserver --version=raw
# paste output here

# replace the pod name of clusterpedia clustersynchro-manager
$ kubectl -n clusterpedia-system exec {clustersynchro-manager-pod-name} -- clustersynchro-manager --version=raw
# paste output here

Host Kubernetes version

$ kubectl version
# paste output here

@Iceber

ci staticcheck error with not changed code pkg/storage/internalstorage/config.go#L8

It will check all the code, but the version hasn't been modified, and the problem wasn't reported before, which is a strange behavior
It looks like updating the package dependencies would be fine, would you like to do it?

1· pipeline workflow always download golangci-lint@1.46.2

It doesn't look like caching is being used? I still need to take a look

ci staticcheck error with not changed code pkg/storage/internalstorage/config.go#L8

It will check all the code, but the version hasn't been modified, and the problem wasn't reported before, which is a strange behavior
It looks like updating the package dependencies would be fine, would you like to fix it?

1· pipeline workflow always download golangci-lint@1.46.2

It doesn't look like caching is being used, I still need to take a look

I can fix it tomorrow and I want have a test before commit the code.  Can you wait for it ?

I can fix it tomorrow and I want to have a test before commit the code. Can you wait for it ?

It's okay.

authors: Iceber wuyingjun-lucky

repo: clusterpedia-io/clusterpedia


text:
vite@3 support

First, thanks for setting this up.
I'm trying to use this plugin with vite@3 and apparently, the return type is not compatible with PluginOption.
Type 'Plugin' is not assignable to type 'PluginOption'.
  Type 'Plugin' is not assignable to type 'Plugin_2'.
    Types of property 'apply' are incompatible.
    ...

Do you have plans to upgrade it?

@gnbaron Thank you for sharing this. I've been using this plugin with Vite 3 since it was released and haven't seen this issue. Do you have a repo you can share where this is happening?

Really weird you not see this, package.json says Vite peer dependency version is ^2.7.6, which means the Plugin you are exporting is a v2 plugin, while my Vite 3 project is expecting a v3 plugin.
Here is a quick repro repository, straight out of Vite react+ts template, I just added vite-plugin-sass-glob-import plugin.

Shouldn't Vite peer dependency here be something like "^2.7.6 || ^3.0.0" instead? This would allow consumers to use either Vite 2 or 3, whatever they are using in their project.

@gnbaron Thanks for sharing. You're correct that the peerDependencies should be bumped - I neglected to do so because, like I said, I've been using this with 3.x versions of Vite for a long time and never had an issue. I'm actually still not exactly sure why your reproduction repo is throwing this error and none of my other 3.x projects are.
I'll look into it. This plugin doesn't get a ton of downloads, but it definitely gets enough that I'm surprised this issue wouldn't have popped up for someone before now.

No worries @cmalven! Let me know if you need help with that.

I just started trying this out too, seems to work fine with vite 3 indeed. Thanks for the useful plugin!
But I also noticed the dependency issue.
Note that vite is actually listed as a straight dependency, not just a peerDependency! It's listed twice, which I don't think is probably desirable.
https://github.com/cmalven/vite-plugin-sass-glob-import/blob/2cad5760491f7e341c12b1575f8c96881e4754ac/package.json#L29-L33
In addition to changing the peerDependency (either bump or just expand the range to include both 2 and 3?), can you drop it from dependencies so it's only peerDependencies?
I am in the middle of transitioning a project from webpack to vite, and just ran into this -- what a coincidence only a week after @gnbaron filed this issue?
I'm not sure if it's actually causing me any problems or not, I'm not personally having the probelm @gnbaron reports... but it is really bloating my node_modules (and my yarn.lock) with a whole additional copy of vite 2 and all it's dependencies, since yarn installs em all since it's listed as a dependency!  I would prefer to keep things tidy.
Would a PR help?

Thanks @jrochkind for adding to this conversation.
I just released 1.4.0 (https://github.com/cmalven/vite-plugin-sass-glob-import/releases/tag/1.4.0) that changes things in two ways:

Updates the peer dependency on Vite to ^3.0.0
Moves the internal dependency on Vite into devDependencies. Hopefully this will remove the duplicate Vite installation you're seeing while still allowing me to include it for local testing.

As far as I can tell, no other updates are needed for the plugin to work with Vite v3, and the issue @gnbaron is having seems to be related to using "type": "module" in package.json which I'll need to investigate separately.
Would you mind installing 1.4.0 locally and let me know if everything works out for you?

Thanks for working on this @cmalven! I've just upgraded it and the TypeScript error is gone. 🎉
I'm also migrating from Webpack @jrochkind haha. Not sure if I didn't make it clear, but I was only having that TypeScript error, besides that, everything seems to be working as expected.

Thank you! I will not have time to test this until next week, but i will get back to you next week!

@gnbaron Re-reading your original message it is clear to me that you were only referring to the typescript error. I get a different error - one that actually breaks your build - running your sample repo locally so I just got things mixed up and assumed that was the error.
I'll take another look at your Typescript error.

1.4.0 seems to be working well for me, thanks @cmalven !

authors: cmalven gnbaron jrochkind

repo: cmalven/vite-plugin-sass-glob-import


text:
Repository

My Introduction
Name
Eyob Westerink
Class
TECH3
About me
i like to design and develop websites.
I have worked as a front-end developer for various companies and I have established a online sneakerplatform.
Goals
Expand knowledge
Skill level
Intermediate / advanced
GitHub username
https://github.com/EyobDejene
GitHub repository
https://github.com/EyobDejene/js-bootcamp

Thanks, added the link to your repo to the admin sheet sneakerhead! 🎉👟

authors: EyobDejene dandevri


text:
covidcast_meta optional caching

use a short-lived cache to make covidcast_meta super fast
integration tested
all unit and integration tests pass
i owe unit tests for this

@capnrefsmmat please take a look

repo: cmu-delphi/delphi-epidata


text:
Add envoy-website as a repo for Envoy

Add https://github.com/envoyproxy/envoy-website as a repo for Envoy (https://clomonitor.io/projects/cncf/envoy). I'd have submitted a PR myself (based on, say #509), but it seems that things have changed since then, so I'll just create an issue for now.

Hi @chalin 👋
Adding a project or a repo should be easier now, you just need to add it to the corresponding data file and CLOMonitor will pick it up automatically. So if you still would like to submit the PR, please go ahead. It'll be helpful to see how more people interact with the data files and how do they feel about it (if they encounter any problems, etc). Otherwise we are happy to do it, not a problem 🙂

authors: chalin tegioz

repo: cncf/clomonitor


text:
Merge main into  branch dev-ja

Describe your changes
Merge main into  branch dev-ja
Related issue number or link (ex: resolves #issue-number)
no issue related in this PR
Background
Currently, when creating a PR for Japanese localization, the labeler action fails (e.g., #2798). This is because, in #2738, the main branch was merged into dev-ja, and the labeler action was updated to v5. (The PR for updating the labeler action is #2673)
Unfortunately, the PR #2774 that fixed the labeler action was not merged into dev-ja. It seems we need to merge main again to resolve this issue
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[ ] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

Hi @Okabe-Junya
Thanks! LGTM!
By the way, please try to use https://github.com/cncf/glossary/compare/dev-ja...main if we don't have merge conflict. :)
(will simplify review process)

@seokho-son
Thank you.
I wanted to create a PR for the changes in dev-ja...main, but I do not have the permissions to do so. Therefore, I needed to checkout branch from main. (Please refer to the image below.)

I am interested in this project, so adding me as an approver might resolve this issue (or alternatively, I can request another approver to create a PR to merge upstream/main).

Slack: https://cloud-native.slack.com/archives/C057F81GFUG/p1705327504026509

authors: Okabe-Junya seokho-son

repo: cncf/glossary


text:
Update landscape.yml

move Cyber Armor to the Security category
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] 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.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 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"?

Build failed because of:
bad indentation of a mapping entry at line 6596, column 10:
             - item:
             ^

Deploy preview for landscape failed.
Built with commit de8ddad92389217a426898900b14e984b69c2c3c
https://app.netlify.com/sites/landscape/deploys/5ee63ad2671aaf0007e9d4af

@amirkCA - I've opened #1712 to fulfill your request to add Cyber Armor to the Security & Compliance section. The listing you were trying to move is your membership listing, which we need to keep in the member section.  I'll go ahead and close this PR.  Thanks!

authors: CNCF-Bot amirkCA taylorwaggoner

repo: cncf/landscape


text:
Kubernative logo

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 included a URL for your SVG or added it 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)?
[ ] ~15 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"?

Deploy preview for landscape ready!
Built with commit 8d66f65c0432e807233904cdbe2d11dfabc53226
https://deploy-preview-2021--landscape.netlify.app

authors: CNCF-Bot taylorwaggoner


text:
Member updates 10.19.22

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

[ ] 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.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you added your SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~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


text:
Deploy platform whitepaper from versioned folder

This resolves https://github.com/cncf/tag-app-delivery/issues/389

FYI @cjyabraham

authors: joshgav niklasbeinghaus

repo: cncf/tag-app-delivery


text:
XDR-4667: Compare between most recent tag and next more recent

previous_parent_hash was exactly the same as current_hash
So git diff "$previous_parent_hash..$current_hash" would always return no result.
Solution
We will do git diff $previous_tag..$current_hash
We obtain previous_tag by doing git tag --sort='-authordate' --no-contains HEAD | head -n1
This gets all the tags that do not contain the HEAD, sorts them (most recent first), and we take the first result. This works even if semver has not yet been run. This works on feature branches (non-main branches) too. It also works when HEAD is a merge commit.

👏

authors: GerardSetho arledesma

repo: cncsc/actions


text:
Develop

I restyled the cmake file while fixing the problem I had in issue #277.
I suggest the use of target_include_directories (instead of include_directories) and target_compile_definitions (instead of add_definitions) as they allow more control over the properties being specified. For example client programs linking to nana will now inherit the public include paths and macro definitions, but not the private ones (cmake will still make sure all the needed pieces are there at link-time).
Some of these changes required me to bump cmake version to 3.1, which should be available pretty much everywhere at this point.
I'm also using the variables provided by the cmake scripts to link to the required libraries and they often contain absolute paths, which made NANA_LINKS look very messy. Also note that the new cmake find scripts tend to define an imported target (for example PNG::PNG, Boost::Boost) to link to, which is very handy and reduces the possibility of mistakes. This, however, would require extracting the actual name of the library from the target in order to be added to NANA_LINKS, and I'm not sure it is worth the extra code. For those reasons I decided to just get rid of the NANA_LINKS library.
As a personal preference I don't like to see too much output in my cmake, unless I want to (in which case I can compile with make VERBOSE=1), so I would be for getting rid of all the print statements at the end of the cmake file. This should remove quite a bit of clutter as well.
Important: I'm only able to test this on Linux, so it's possible my changes introduce problems to non-Linux platforms. Somebody with access to other OS should have a second look at my changes.
I'm open to discussions on how to further improve the cmake file.

Thanks for your PR! This PR has been referred by qPCR4vir's(#342 ).

It is my bad and a shame that I didn't saw this PR and your explanation a year ago. More exactly, I probably read it but I was unprepared for it and just ignore it. Sorry. By trying to fix by myself the problems I kome back here to see that you have alrready pointed to most of what I was using and a few more.
I think now left only to use the Boosr::boost thing, but a got some problem and I have read that some time Boost go to fast for cmake and one need to use the other aproach.
I hope you will keep helping.
Thank!

authors: KingDuckZ cnjinhao qPCR4vir

repo: cnjinhao/nana


text:
3.1.8版无法启动

爱快里的docker,只映射了下载目录和数据目录.
错误提示
[syno] 绑定目录 "/dev" -> "/xunlei/dev" 失败: operation not permitted

这个dev是哪来的呀

翻了下之前的issue,解决办法是开启容器特权模式,爱快不支持.


text:
Cannot read property 'slug' of undefined

I'm currently using the develop branch (4cfe89a593cd9e2691bd91bc6268ce77091549c4 is what my composer.lock says) because my App is on Laravel 7 already.
When I try to add a custom Featured Image to my post (either before it is created, or after it has been saved as a draft, or even after it has been published), nothing happens. The image is showing in the upload area, and it says upload complete. This does not happen when I use Unsplash. I've made sure I have the latest assets published.
(By the way, 👍 for Filepond - I'm using it in another project and it is great.)
In the browser's console I have this error:
TypeError: Cannot read property 'slug' of undefined
    at a.<anonymous> (app.js?id=4f95e6a5db98bc9497d2:2)
    at a.INkZ.e._render (app.js?id=4f95e6a5db98bc9497d2:2)
    at a.r (app.js?id=4f95e6a5db98bc9497d2:2)
    at fn.INkZ.fn.get (app.js?id=4f95e6a5db98bc9497d2:2)
    at fn.INkZ.fn.run (app.js?id=4f95e6a5db98bc9497d2:2)
    at un (app.js?id=4f95e6a5db98bc9497d2:2)
    at Array.<anonymous> (app.js?id=4f95e6a5db98bc9497d2:2)
    at Ke (app.js?id=4f95e6a5db98bc9497d2:2)

And expanded:
Fe @ app.js?id=4f95e6a…:2
Xe @ app.js?id=4f95e6a…:2
We @ app.js?id=4f95e6a…:2
INkZ.e._render @ app.js?id=4f95e6a…:2
r @ app.js?id=4f95e6a…:2
INkZ.fn.get @ app.js?id=4f95e6a…:2
INkZ.fn.run @ app.js?id=4f95e6a…:2
un @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
Ke @ app.js?id=4f95e6a…:2
Promise.then (async)
Ue @ app.js?id=4f95e6a…:2
tt @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
INkZ.fn.update @ app.js?id=4f95e6a…:2
INkZ.de.notify @ app.js?id=4f95e6a…:2
set @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
Promise.catch (async)
saveActivePost @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
L2JU.u._withCommit @ app.js?id=4f95e6a…:2
L2JU.u.commit @ app.js?id=4f95e6a…:2
commit @ app.js?id=4f95e6a…:2
saveActivePost @ app.js?id=4f95e6a…:2
(anonymous) @ app.js?id=4f95e6a…:2
L2JU.u.dispatch @ app.js?id=4f95e6a…:2
dispatch @ app.js?id=4f95e6a…:2
save @ app.js?id=4f95e6a…:2
clickDone @ app.js?id=4f95e6a…:2
He @ app.js?id=4f95e6a…:2
n @ app.js?id=4f95e6a…:2
Gr.o._wrapper @ app.js?id=4f95e6a…:2

Fresh install. I installed it a few days ago while I was still on Laravel 6, then upgraded my app to Laravel 7.
I'm using S3 as my storage, here are my environment variables:
CANVAS_STORAGE_DISK=s3
CANVAS_STORAGE_PATH=blog

I know my connection to S3 is working because I also use Spatie's media library package, but maybe it didn't create the path?

I updated to your latest commit (b2e5ded3dce6a05c0bad75af653e3667d53d7cae), and have a better error message now:
[Vue warn]: Error in render: "TypeError: Cannot read property 'slug' of undefined"

found in

---> <SettingsModal> at resources/js/components/modals/SettingsModal.vue
       <PostsEdit> at resources/js/screens/posts/PostEdit.vue
         <Root>

Aha! I found the problem. Telescope Toolbar is adding its assets to the file path that is getting saved to the featured_image column.
Something I've noticed is that Telescope Toolbar (and also DebugBar, I think) add their assets to any response that is not JSON or plain text. So you'll need to set the content type before this return: https://github.com/cnvs/canvas/blob/b2e5ded3dce6a05c0bad75af653e3667d53d7cae/src/Http/Controllers/MediaController.php#L28

Turns out Telescope Toolbar doesn't have this ability. I've opened an issue here: https://github.com/fruitcake/laravel-telescope-toolbar/issues/25
We can close this if you want since it isn't technically relevant to Canvas. A quick fix would be to add header('Content-Type: text/plain') before the return I mentioned above, but I don't know if it is fair to ask you to change Canvas for some obscure issue from another (development-only) package.

Great find! Like you said, we'll leave Canvas as it is and hope that some resolution can from from the toolbar side of things.
But I appreciate you finding the answer to this!

authors: austintoddj mikemand

repo: cnvs/canvas

license: mit


text:
User session time out and warning

Added 20 minutes as the session timeout.
META refresh will auto update the page to session-ended page.

Raised another PR with cleaner version.

repo: co-cddo/domains-register-a-govuk-domain


text:
Align beginning of quickstarts

Link to local cluster option from serverless quickstart
Combine before you begin with step 1 in dedicated quickstart

This change is

authors: cockroach-teamcity jseldess

repo: cockroachdb/docs


text:
feat: Helm commands used to install the LMS

Hey team!
Here's a small change to make the helm commands a more obvious part of the LMS installation.

@codingconcepts Thank you for this! Adding @Jeremyyang920.

authors: codingconcepts taroface


text:
[CC-25231] Generated documentation is comprehensive and accurate

Went over all the resource and database schemas and updated the Description/MarkdownDescription fields where missing or needed improvement. Standardized on adding a period to the end of each description.
Added a helper to format allowed enum value lists, which show up as bullet points in a markdown renderer.
Fixed the formatting of a few ID fields, where angle brackets were getting swallowed by the markdown renderer.
Renamed "cockroach_cluster_data_source" to "cluster_data_source" for consistency and "networking_resource" to "allowlist_resource" to match the name of the actual resource.
Commit checklist

[x] Changelog
[x] Doc gen (make generate)
[x] Integration test(s)
[x] Acceptance test(s)
[x] Example(s)

This change is

@erademacher Hi! Sorry for the delayed review -- found out what the process and expectations are just yesterday. It's on my to-do list for today!

Reviewable status: 0 of 42 files reviewed, 21 unresolved discussions (waiting on @Amruta-Ranade, @gemma-shay, @ianjevans, and @jenngeorge)

a discussion (no related file):
Previously, jenngeorge (Jenn Georgevich) wrote…

The cockroach_user_role_grants resource requires the ID of the user being granted roles. A service account's ID can be found in the url for its detail page like "/service-accounts/{service account user id}", but we didn't have a way for customers to get the user ID of a person in their org. So we added the API endpoint & data source to address that specific problem. Here's a workflow with example use: https://github.com/cockroachdb/terraform-provider-cockroach/blob/main/examples/workflows/cockroach_user_role_grants/main.tf

@Amruta-Ranade thoughts on this? Are we ok publicly calling it a "person user"?

How about "individual user"?

authors: Amruta-Ranade erademacher