text:
Why when I run eval benchamrk, the name of categories is different from blog.

it only shows the follow query_categories:
date_functions, group_by, instruct, order_by, ratio, table_join.
It different from the blog listed in https://defog.ai/blog/open-sourcing-sqlcoder-70b/:
date | group_by | order_by | ratio | join | where |
is "instruct"  mapping to "where"?

Hi @cometyang yes we have modified the benchmark recently to reflect the nature of capabilities that are more useful to users.

@wongjingping thanks for clarification. One more question, my test results varied from the blog report but similar. For the reported results, it is average or the best? For example, are u running for 5 times for averaging?

@wongjingping  I tested on sqlcoder-70b-alpha, it reported correctness 87% using sql-eval, which is 0.5% better than gpt-4-0613.  Though the number is not 93%, but it indeed an achievement. Just wondering the variance is normal or not. I use vLLM as inference framework.

Hi there, thanks for reporting. Apologies for the delay on this. We finally got the chance to try and replicate this again.
The 70b model was trained on a slightly different prompt that the current prompt.md file in this directory. It was trained on the prompt below, and is what the model was originally tested with.
### Task
Generate a SQL query to answer the following question:
`{user_question}`

### Database Schema
The query will run on a database with the following schema:
{table_metadata_string}

### Answer
Given the database schema, here is the SQL query that answers `{user_question}`:
```

With vllm and using this prompt, we get 92.5% accuracy (a little down from 93.5% – likely because of minor changes in sql-eval since then). You can use the command below to replicate this. You can likely get higher accuracy if you use transformers `model.generate directly.
python -W ignore main.py   -db postgres   -o "results/vllm.csv"   -g vllm   -f "/path/to/updated_prompt.md"   -m defog/sqlcoder-70b-alpha

If you don't get these results, please do let us know what runner and device you're using! Would love to get to the bottom of the cause in variance

I tried your update prompt, now I also need to change the eval code since now the sql query is after "sql\n", and I got. accuracy 86.5%. My test setup is A100 80G. and I use API runner:
'''python main.py
-db postgres
-o results.sql70b_old_template.csv
-g api
-b 1
-f prompts/updated_prompt.md
--api_url "your ip address/generate"
-p 5

Ah, the benchmarks are all done with 4 beams. If using the API runner, you should use b=4 to update the benchmarks. b=1 uses greedy decoding, and the 70b-alpha-model doesn't work nearly as well with that
python main.py
-db postgres
-o results.sql70b_old_template.csv
-g api
-b 4
-f prompts/updated_prompt.md
--api_url "your ip address/generate"
-p 5

change to 4, the results improved to 88.5%.

Huh, that's strange. Unfortunately, not much we can do to help with that. When running the vllm runner on multiple 4xA100 80GB runpod instance with 4 beams (the default config for the vllm runner), we could confirm 92.5% accuracy. Hope you manage to figure it out!
python -W ignore main.py \
  -db postgres \
  -o "results/vllm.csv" \
  -g vllm \
  -f "/path/to/updated_prompt.md" \
  -m defog/sqlcoder-7b-alpha

Would you mind to share your vllm server command line? I also tried to run on 4xA100.

You can just run a python process using vllm using the code I included above. You do not have to create a vllm server.

I run the model and the postgres database on different machines, that's the reason I created vllm server.  The sql-70b's performance (86.5%) is close to sql-7b-v2 (84.5%) in b=1 on my test. I need to test on other types of databases and see the difference. If I understand correctly, the best db type is postgres and but other db should be also okay, right?

authors: cometyang rishsriv wongjingping

repo: defog-ai/sql-eval


text:
Fix falloff curve calculation

Hey,
I noticed in light_quad.fp that the radial light intensity value, which should have been affecting only the alpha channel of the color, was in fact being multiplied with all components of the color.  Because of this, when I tried to implement ambient lighting, this weird circular dark spot around the light would get created, since the ambient light was also being multiplied with the light's intensity.
After the fix, you can see that the radial falloff now works properly, the light becomes gradually less dense until it blends perfectly with the ambient light.
Before:

After:

I also took this opportunity to properly hookup the falloff property, it wasn't used before and it was hard-coded to 1.

Note that in the examples above I am not using this repo as an asset. Instead I have incorporated these ideas into my own rendering pipeline. In this sample there's probably no falloff issue, since you rely on Multiply blend modes to hide elements. But this issue does appear when you take the light as a render target, and multiply it with another render target on a quad.

Thank you for the PR! Can you update it with the latest from master?

source: gharchive/pull-request

authors: britzl haath

repo: defold/sample-lights-and-shadows

license: MIT

license_type: permissive

license_source: github-api


text:
Database service recognition failed (boto timeout)

In deis/database/bin/boot
Database service recognition failed
Because this does not work etcdctl set /deis/database/{host and port} ...
STRUCTURED: time=2015-01-14T02:48:52.524374-00 pid=31225
wal_e.retries WARNING  MSG: retrying after encountering exception
        DETAIL: Exception information dump:
        Traceback (most recent call last):
          File "/usr/local/lib/python2.7/dist-packages/wal_e/retries.py", line 62, in shim
            return f(*args, **kwargs)
          File "/usr/local/lib/python2.7/dist-packages/wal_e/worker/s3/s3_deleter.py", line 27, in _delete_batch
            bucket.delete_keys([key.name for key in page])
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/bucket.py", line 726, in delete_keys
            while delete_keys2(headers):
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/bucket.py", line 714, in delete_keys2
            data=data)
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 664, in make_request
            retry_handler=retry_handler
          File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1070, in make_request
            retry_handler=retry_handler)
          File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1029, in _mexe
            raise ex
        timeout: timed out

        HINT: A better error message should be written to handle this exception.  Please report this output and, if possible, the situation under which it arises.

a boto exception would mean that the database failed connecting to ceph. Could you please post the health of your cluster, particularly deis-store-gateway?

deis version 1.2.0
run deisctl list output for all services "loaded active running"
dockel logs from deis-store-gateway
Starting RADOS gateway...
Starting client.radosgw.gateway...
2015-01-13 11:05:21.765179 7f5ba82b8840  0 ceph version 0.87 (c51c8f9d80fa4e0168aa52685b8de40e42758578), process radosgw, pid 122
/usr/bin/radosgw is running.
Starting Apache...
deis-store-gateway running...

Also i use ceph (deis-store-gateway) in other django project, and then it work normally
I think this is due to the large wal file and because of the fact that the boto has no time to send the file to store in 30 seconds (timeout=30s) see https://github.com/wal-e/wal-e/blob/81a25d56e990c20d446eff472ad70c6efb923db8/wal_e/worker/pg/wal_transfer.py#L142

I think need create other executable file, for example 'database/bin/walbackup' and import there backup logic and run it into boot in background mode './walbackup &' :)

@suquant How much data are we talking here? The WAL would have to be pretty big to not complete in 30s.
But you're right - we need to address that. See #2741.

ls -lah in pg_xlog
total 145M
drwx------ 1 101 106 584 Jan 14 03:37 .
drwx------ 1 101 106 388 Jan 13 14:47 ..
drwx------ 1 101 106  16 Jan 11 01:46 .wal-e
-rw------- 1 101 106  42 Jan 11 03:07 00000002.history
-rw------- 1 101 106 332 Jan 13 14:47 0000000200000005000000DF.00000028.backup
-rw------- 1 101 106 16M Jan 14 03:33 000000020000000600000078
-rw------- 1 101 106 16M Jan 14 03:37 000000020000000600000079
-rw------- 1 101 106 16M Jan 14 02:57 00000002000000060000007A
-rw------- 1 101 106 16M Jan 14 03:02 00000002000000060000007B
-rw------- 1 101 106 16M Jan 14 03:07 00000002000000060000007C
-rw------- 1 101 106 16M Jan 14 03:12 00000002000000060000007D
-rw------- 1 101 106 16M Jan 14 03:17 00000002000000060000007E
-rw------- 1 101 106 16M Jan 14 03:22 00000002000000060000007F
-rw------- 1 101 106 16M Jan 14 03:27 000000020000000600000080
drwx------ 1 101 106 190 Jan 14 03:37 archive_status

Once again
just noticed that the timeout arrives at the delete keys :/
WTF ...
STRUCTURED: time=2015-01-14T03:37:01.048553-00 pid=31225
wal_e.main   INFO     MSG: starting WAL-E
        DETAIL: The subcommand is "wal-push".
        STRUCTURED: time=2015-01-14T03:38:01.189975-00 pid=1373
wal_e.worker.upload INFO     MSG: begin archiving a file
        DETAIL: Uploading "pg_xlog/000000020000000600000079" to "s3://db_wal/wal_005/000000020000000600000079.lzo".
        STRUCTURED: time=2015-01-14T03:38:01.198852-00 pid=1373 action=push-wal key=s3://db_wal/wal_005/000000020000000600000079.lzo prefix= seg=000000020000000600000079 state=begin
wal_e.worker.upload INFO     MSG: completed archiving to a file
        DETAIL: Archiving to "s3://db_wal/wal_005/000000020000000600000079.lzo" complete at 46.5657KiB/s.
        STRUCTURED: time=2015-01-14T03:38:03.857892-00 pid=1373 action=push-wal key=s3://db_wal/wal_005/000000020000000600000079.lzo prefix= rate=46.5657 seg=000000020000000600000079 state=complete
wal_e.retries WARNING  MSG: retrying after encountering exception
        DETAIL: Exception information dump:
        Traceback (most recent call last):
          File "/usr/local/lib/python2.7/dist-packages/wal_e/retries.py", line 62, in shim
            return f(*args, **kwargs)
          File "/usr/local/lib/python2.7/dist-packages/wal_e/worker/s3/s3_deleter.py", line 27, in _delete_batch
            bucket.delete_keys([key.name for key in page])
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/bucket.py", line 726, in delete_keys
            while delete_keys2(headers):
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/bucket.py", line 714, in delete_keys2
            data=data)
          File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 664, in make_request
            retry_handler=retry_handler
          File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1070, in make_request
            retry_handler=retry_handler)
          File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1029, in _mexe
            raise ex
        timeout: timed out

        HINT: A better error message should be written to handle this exception.  Please report this output and, if possible, the situation under which it arises.

I think need create other executable file, for example 'database/bin/walbackup' and import there backup logic and run it into boot in background mode './walbackup &' :)

Yep, something like that is definitely planned for #2741!

@suquant We're tracking this in #2741 and is definitely something we need to fix. Thanks for reporting, and sorry for the trouble!

source: gharchive/issue

authors: bacongobbler carmstrong suquant

repo: deis/deis


text:
e2e tests should have a "test all buildpacks" option

Ideally in the same test suite and in parallel. See also deis/deis#2879.

Another idea is to have the tests pick at random what type to do unless the test specifically calls for one type or another. Could potentially extend the e2e run quite a bit tho

Closed by #188.

authors: helgi mboersma


text:
Proposal: Make the quick start docs have one step per page

Right now, the guide at http://docs-v2.readthedocs.io/en/latest/quickstart/ seems to provide a basic outline of the steps, but the guide for what you need to do to accomplish each step is at the other side of a link. For example, to accomplish step 2 ("Boot Kubernetes and Install Deis Workflow"), you have to click on a different link to do each of the following:

Set up your k8s cluster (plus, you have to choose beforehand where you want your cluster to live)

Also, people should look at the system requirements before they decide, but that's not clear they should click on the link first (it's below the guides for GKE and AWS)
It's not clear which kind of cluster is suitable for what needs. For example, an explanation of pros/cons for single-developer testing / "kicking the tires" would be helpful for each kind of k8s cluster

Install Deis workflow on the cluster

This issue proposes inlining all of the information in the quickstart guide, and presenting it in a format similar to a slide-show

the quickstart docs have been optimized a while ago and follows a more tutorial style for each provider. Closing!

authors: arschles bacongobbler

repo: deis/workflow

license: mit

license_source: bigquery


text:
bug(workflow): error during startup because of missing service

Publishing DB state to k8s...
Traceback (most recent call last):
  File "/app/manage.py", line 12, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/python3.5/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.5/site-packages/django/core/management/__init__.py", line 345, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3.5/site-packages/django/core/management/base.py", line 348, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.5/site-packages/django/core/management/base.py", line 399, in execute
    output = self.handle(*args, **options)
  File "/app/api/management/commands/load_db_state_to_k8s.py", line 15, in handle
    obj.save()
  File "/app/api/models/domain.py", line 23, in save
    config = self._load_service_config(app, 'router')
  File "/app/api/models/__init__.py", line 71, in _load_service_config
    svc = self._fetch_service_config(app)
  File "/app/api/models/__init__.py", line 61, in _fetch_service_config
    svc = self._scheduler._get_service(app, app).json()
  File "/app/scheduler/__init__.py", line 1054, in _get_service
    error(response, 'get Service "{}" in Namespace "{}"', name, namespace)
  File "/app/scheduler/__init__.py", line 281, in error
    raise KubeHTTPException(errmsg, response=response)
scheduler.KubeHTTPException: failed to get Service "app-name" in Namespace "app-name": 404 Not Found
{'status': 'Failure', 'metadata': {}, 'message': 'services "app-name" not found', 'reason': 'NotFound', 'kind': 'Status', 'apiVersion': 'v1', 'code': 404, 'details': {'kind': 'services', 'name': 'app-name'}}

We have the same issue with missing/conflicting Namespace and RC as well.
Did your particular situation happen due to a failed deploy?

@helgi I removed the service just to see if is recreated using scale (I saw the same thing with ns and rc)

Ah, that's a known failure scenario. Right now it is all pretty dumb but I have a few things in the works to ease that up with the eventual plan of being able to fill in the blanks.
I'll create a meta ticket to track all the various connected open tickets revolving around this.

Talking to @aledbf and he ran the command again with the same result but it looks like the Domain model is potentially ran before App is ever invoked

#482 got merged with the fixed and verified by @aledbf

authors: aledbf helgi


text:
duffle upgrade fails against thick bundle

Hey!! We ran into an issue when trying to update the instance of our bundle. The command we ran for context is:
duffle upgrade ${CLUSTER_NAME} -c ./credentials.yaml \
    --set kubernetes_env="${CLUSTER_NAME}" \
    -m $PWD/relocated.json \
    --bundle-file build-service-*.tgz

This failed with the following error message: Error: cannot load bundle: invalid character '\x1f' looking for beginning of value.
We were able to work around this by importing the bundle and then running upgrade against the bundle.json directly. The duffle version we used was duffle 0.2.0-beta.3

Ran into this issue as well!

I also noticed that duffle upgrade wasn't validating the bundle, so I'll fix that at the same time.

authors: ashwin-venkatesh glyn youreddy

repo: deislabs/duffle


text:
User Defined Order#1147

What does this change
This addresses the issue of random execution dependencies at Runtime. This implementation reflects the proposition into the spec. see https://github.com/cnabio/cnab-spec/issues/361
What issue does it fix
Closes #1147, #969
Checklist

[x] Unit Tests
[x] Documentation
[x] Schema (porter.yaml)

@MChorfa Let me know if you need help with the test failure or if you are still working on that yourself.

@MChorfa Let me know if you need help with the test failure or if you are still working on that yourself.

@carolynvs yes, please. I am having an issue with the map Keys. The order is never guaranteed even after reordering with sequence definition. Also, I am worried about the for loop range behavior.  The order is also not guaranteed when going through a map.

Oh, it's the ordering that's causing trouble? The way we fix that is often with a custom data structure that sorts according to our desired strategy. I will take a look later today and may push a commit with a data structure to help out.

@MChorfa Your PR wasn't set up to allow commits from maintainers so I couldn't push a commit with a fix for your test. Here's the fix https://github.com/carolynvs/porter/commit/430738eb373cf7d78f4a98d7a9f7440816a06838
Wherever you need to read the dependencies in sorted order you would use the ListBySequence function, instead of reading by the map directly. In Go reading from a map is guaranteed to result in a different order each time to prevent you from relying upon it, and force you to do something like this instead.

Thank you @carolynvs for the review. Still need to write more units tests and update the documentation

@MChorfa also remembered we'll need to update the manifest schema 😅

@MChorfa sorry that you're battling the schema unit test with subtle differences.  I think it can be resolved by copying the schema that is printed out when the test fails (from make test-unit) and copying that to pkg/porter/testdata/schema.json.

Or, even simpler, copy this updated file: https://raw.githubusercontent.com/vdice/porter/mchorfa-user-defined-order/pkg/porter/testdata/schema.json  That should work 🙏

Or, even simpler, copy this updated file: https://raw.githubusercontent.com/vdice/porter/mchorfa-user-defined-order/pkg/porter/testdata/schema.json That should work 🙏

Ah! thank you :)

authors: MChorfa carolynvs vdice

repo: deislabs/porter


text:
'xrange()' is not defined

When trying to run the code, I get the following error message:
"PS D:\Users\John\Documents\GitHub\octree_color_quantizer> python main.py
Traceback (most recent call last):
File "D:\Users\John\Documents\GitHub\octree_color_quantizer\main.py", line 43, in
main()
File "D:\Users\John\Documents\GitHub\octree_color_quantizer\main.py", line 14, in main
octree = OctreeQuantizer()
^^^^^^^^^^^^^^^^^
File "D:\Users\John\Documents\GitHub\octree_color_quantizer\octree_quantizer.py", line 138, in init
self.levels = {i: [] for i in xrange(OctreeQuantizer.MAX_DEPTH)}
^^^^^^
NameError: name 'xrange' is not defined. Did you mean: 'range'?"
Is there a input argument that defines this object, that I'm missing?

Hi @johnwarh, yes you can use range instead of xrange.
I wrote this code for Python 2.7.

I just figured that out myself after looking at the fork in the repository.  Thank you for your quick response.

authors: delimitry johnwarh


text:
[BUG]: Update the branch from master to main in readme for license

Bug Description

Logs

Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
ReadMe file needs to be update
Expected Behavior
master has to be changed to main
CSM Driver(s)
PFLEX, Pstore, Unity, Pscale
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
NA
Operating System
NA

@bharathsreekanth : Can we close this if it has been addressed?

repo: dell/csm


text:
Provide a nicer pandas read interface

Reading Delta tables into pandas DataFrames could be more intuitive.
Here's the current syntax:
import pyarrow.dataset as ds

dt = DeltaTable(f"{pathlib.Path.home()}/data/delta/G1_1e8_1e2_0_0")
dataset = dt.to_pyarrow_dataset()
condition = ds.field("id1") == "id016"
df = dataset.to_table(filter=condition, columns=["id1", "id2", "v1"]).to_pandas()

Could we provide an interface that's more similar to pandas.read_parquet?  Something like this:
import deltalake

dt = DeltaTable(f"{pathlib.Path.home()}/data/delta/G1_1e8_1e2_0_0")
df = dt.filters([("id1", "==", "id016")]).to_pandas()

The list of tuples of how predicates are passed in pandas.read_parquet.
I'm open to other interfaces too.  I think something that hides pyarrow.dataset, is less code, and is familiar with existing pandas syntax would be good.

Have you tried DeltaTable.to_pandas()? I think that's exactly what you are looking for. https://delta-io.github.io/delta-rs/python/api_reference.html#deltalake.table.DeltaTable.to_pandas

@wjones127 - Here's the signature for that function to_pandas(partitions=None, columns=None, filesystem=None).
I don't see any filters argument for metadata-based file skipping.  Let me know if I am missing something!

I see. We can extend that method to pass down filters in the dataset.

Great!  Can we expose the filters to use this syntax [("id1", "==", "id016")] instead of this ds.field("id1") == "id016"?

We may even want to combine the partitions and filters functionality.  That's what pandas and pyarrow do from what I understand.  See here.

Yes, I think we'll deprecate partitions in favor of filters, but leave both in for now. And we can use DNF filters if you want. Or maybe can can accept either?

Hi, guys. I apologize for interrupting your argument. Although it may take me some time to fully grasp the structure of delta-rs, I would like to work on this issue. Would it be possible to assign me to this issue?

We would gladly accept a PR for this. 😄
Note there is a function called filters_to_expression that can handle converting the DNF filter format into PyArrow expressions. (code).

Thank you @wjones127 @MrPowers!
Once there's a consensus on the implementation, please feel free to assign me to this issue, and I will follow the discussion here as well. Also, I will check the source code that you linked.

@ognis1205 - I think there is a consensus on the next steps and you can get started.
See here for more information on the DNF filter format that Will is referring to.
Here's the existing to_pandas method signature: to_pandas(partitions=None, columns=None, filesystem=None)
You can submit a PR that will update the method signature to this: to_pandas(partitions=None, columns=None, filesystem=None, filters=None)
Let me know if you'd like any additional clarification!

Thanks again @MrPowers @wjones127 !!

@wjones127 @MrPowers
Hi, everyone! I have a question.
While making a PR for this issue, I encountered the following error:
 https://github.com/delta-io/delta-rs/actions/runs/4926020116/jobs/8800992032?pr=1349#step:8:18

So, I am considering implementing a fallback function for pyarrow.parquet.core.filters_to_expression that is compatible with PyArrow 7.0.0. However, I came across this comment on another PR:
 https://github.com/delta-io/delta-rs/pull/1315#issuecomment-1532453405

Should I still implement the fallback function if the Python deltalake package will soon drop support for Python 3.7?
Would it be okay to implement a stub function that does nothing instead?

I checked the PyArrow API doc. Only PyArrow >= 10.0.0 supports pyarrow.parquet.core.filters_to_expression.
So I think I should implement the fallback function in either case.

Yes, we will drop support for Python 3.7, but we are keeping support (for now) for PyArrow 7.

@MrPowers @wjones127
FYI:
I created a PR for this issue.

repo: delta-io/delta-rs


text:
feat: integrate unity catalog with datafusion

Description
This is a follow-up from #1331, where we added support for the unity catalog and does a couple of things:

Adds a port of the client implementation from object_store to communicate with unity catalog.
refactors and extends the current client to accept configuration much in the way we do for the storage backends
adds additional (so far only Azure) credentials to authorize requests
adds an integration with datafusion's SchemaProvider and CatalogProvider
add unit tests for various components.

At first glance porting the whole client implementation may seem excessive, but my hope is that with this we can eventually replace the rusoto dependency from the glue catalog, as well as implement the LogStore locking mechanisms suggested by @nkarpov while keeping everything SDK-free :).
@nohajc - unfortunately I do not have access to a unity catalog instance right now. Would it be possible for you to validate, that the requests are still working?
Related Issue(s)
No issues

@nohajc - unfortunately I do not have access to a unity catalog instance right now. Would it be possible for you to validate, that the requests are still working?

Sure, I will gladly test it.

@roeap  So far I only verified it works with Databricks personal access token but if I figure out which AAD roles are needed, I could check the Oauth flows (+ azure cli) as well.

So far I only verified it works with Databricks personal access token but if I figure out which AAD roles are needed, I could check the OAuth flows (+ azure cli) as well.

That would be awesome. Haven't worked with this yet. but from the docs i gather you don't really need specific roles, but rather "Just" need the AAD object user to be available / assigned in the unity catalog.

That would be awesome. Haven't worked with this yet. but from the docs i gather you don't really need specific roles, but rather "Just" need the AAD object user to be available / assigned in the unity catalog.

This is correct. If you have an AAD bearer token with scope set to the azure databricks application you can do everything a databricks personal access token can do. The scope being -> 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d

That would be awesome. Haven't worked with this yet. but from the docs i gather you don't really need specific roles, but rather "Just" need the AAD object user to be available / assigned in the unity catalog.

Successfully tested service principal (client ID / client secret) and Azure CLI credentials. I don't have an opportunity to try with managed identity or workload identity right now...

Thanks for testing this @nohajc!

I don't have an opportunity to try with managed identity or workload identity right now...

I guess we know now, that we are using the right scopes, the rest is just how we get the AAD token, that we have validated elsewhere, so we should be good 🤞.

(I still need to use #[serde(default)] on the sql_path response field.)

(I still need to use #[serde(default)] on the sql_path response field.)

on it :) - applying some fixes and adding datafusion tests.

@roeap Is this ready to get merged?

authors: ion-elgreco jordandakota nohajc roeap


text:
docs: add usage guide for check constraints

Description
Added a usage guide for adding check constraints to tables
Related Issue(s)
Closes #2063
Documentation
I just wrote it

Looks good


text:
fix: reinstate copy-if-not-exists passthrough

Description
If the AWS_COPY_IF_NOT_EXISTS key exists, then we don't require instantiating a lock client or setting allow-unsafe-rename.

Thanks for fixing this!
One thought, should we just check for the corresponding key in the storage config?
This would not require adding an extra config key, and mirrors the previous behaviour.

Yep, I'll make that change.


text:
Specifying dependencies in pyproject toml for auto dependency installation using pip install

https://github.com/delvtech/elf-simulations/issues/547

Codecov Report
Patch and project coverage have no change.

Comparison is base (61e08bf) 75.07% compared to head (54ec9ba) 75.07%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #569   +/-   ##
=======================================
  Coverage   75.07%   75.07%
=======================================
  Files          55       55
  Lines        3362     3362
=======================================
  Hits         2524     2524
  Misses        838      838

Flag
Coverage Δ

unittests
75.07% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter slundqui

repo: delvtech/elf-simulations


text:
Add commas between constructor args

quick fix

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

Comparison is base (36e61a3) 73.67% compared to head (ece66bc) 73.67%.
Report is 1 commits behind head on main.

:exclamation: Current head ece66bc differs from pull request most recent head 339b898. Consider uploading reports for the commit 339b898 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #83   +/-   ##
=======================================
  Coverage   73.67%   73.67%
=======================================
  Files          32       32
  Lines        1679     1679
=======================================
  Hits         1237     1237
  Misses        442      442

Flag
Coverage Δ

unittests
73.67% <ø> (ø)

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

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

authors: codecov-commenter sentilesdal

repo: delvtech/pypechain


text:
[build] Multiple Definitions for  io_uring_get_sqe()

Description
When using Liburing v2.1, we get multiple definitions for  io_uring_get_sqe()

This bug was fixed in commit 5617cab576d4686b78b2831063095bfa4da57d88.

repo: demikernel/liburing-rs


text:
Reference docs expansion to support Scripts and Playbooks

Status
In Progress
Related
Content pr: https://github.com/demisto/content/pull/6333
Description
Support for Scripts and Playbooks for reference docs (still wip).
Screenshots
Paste here any images that will help the reviewer

@fvigo I intentionally didn't include the table of contents in the index. I wanted to provide more space for the table. But I see your point. I'll add it and we can see who it looks.

@kirbles19 please review the preview site. It contains the docs from demisto/content#6333

repo: demisto/content-docs


text:
cannot unpack non-iterable bool object

api stop working and show this error
`[]
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/requests/models.py", line 910, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python3.7/json/init.py", line 348, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.7/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.7/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/content/TiktokApi/api.py", line 92, in getUserFeed
resp = res.json()
File "/usr/local/lib/python3.7/dist-packages/requests/models.py", line 917, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: [Errno Expecting value]
    # i removed the html code because hes is big!!!!!

TypeError                                 Traceback (most recent call last)
 in ()
41
42 while True:
---> 43     userFeed, cookie = Api.getUserFeed(username=user_name, max_cursor=max_cursor)
44     dl = Download(cookie=cookie, path=folder1)
45     for post in userFeed['itemListData']:
TypeError: cannot unpack non-iterable bool object`
i removed the html code from the error report because he is big!!!!!
this error happen with getMusicFeed and with getUserFeed

tiktok changed the API so currently the APIs are not working, I will update the API

thanks for your concern, waiting for update

updated


text:
Issues (5) With New Dendron Preview

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[X] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Describe the bug
Initial impressions of the new Dendron native preview (Preview V2) released with the 0.49.0 update.
1) Code Formatting
The native preview is struggling to display some formatting. For example, code, such as the below:
Dendron: Show Preview V2: Crtl + K V
Is displayed as follows:
Basic Preview:

Markdown Preview Enhanced:

Preview V2:

2) Table Formatting
Likewise with tables, such as the below:

Shortcut
Keybinding

Dendron: Show Preview V2
Crtl + K V

Is displayed as follows:
Basic Preview:

Markdown Preview Enhanced:

Preview V2:

2.5) Table Formatting
In addition, the Preview V2 tables are still unable to recognize wikilinks without the table breaking:

It is possible to use the \ key to get around this, however the \ will be displayed as part of the link:

3) Preview Width
At the bottom of the preview is displayed a bar for shifting horizontally, regardless of whether the content actually exceeds the width of the screen.
See split panel:

And full:

4) Header Size
As already noted by @SeriousBug in their issue #927, the headers are improperly sized. The note title is the same size as Header 1, and both are displayed as smaller than Header 2.
5) Preview Scroll
The preview does not scroll with the note.
However, I am using VS Codium, for which it has been identified that there is an issue with the preview scroll (Issue #694). There is a fix pending the next release.
A VS Code user can confirm whether this is a Dendron specific issue.
Desktop (please complete the following information)

OS: Windows 10
Browser: NA
Version: Dendron 0.49.0

@micharris42 - thanks for reporting these issues. Number 5 is known already (missing functionality) but we'll take a look at the others and make sure to fix before deprecating the old preview.

Images are not displaying for me. See screenshot below with a source file in the left pane, the v1 preview in the centre pane, and the v2 preview in the right pane:

Log file:
{"level":30,"time":1625576503924,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"Logger:configure","msg":"exit","log_level":"info"}
{"level":30,"time":1625576504267,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"_activate","stage":"prod","isDebug":false,"logPath":"/Users/darren/Library/Application Support/Code/logs/20210706T150140/exthost2/dendron.dendron","logLevel":"info","extensionPath":"/Users/darren/.vscode/extensions/dendron.dendron-0.49.0","extensionUri":{"$mid":1,"fsPath":"/Users/darren/.vscode/extensions/dendron.dendron-0.49.0","path":"/Users/darren/.vscode/extensions/dendron.dendron-0.49.0","scheme":"file"},"storagePath":"/Users/darren/Library/Application Support/Code/User/workspaceStorage/ff5acb60aea11441d6a7341d58e6b4cf/dendron.dendron","workspaceFile":{"$mid":1,"fsPath":"/Users/darren/Documents/Writing/Zettelkasten/dendron.code-workspace","external":"file:///Users/darren/Documents/Writing/Zettelkasten/dendron.code-workspace","path":"/Users/darren/Documents/Writing/Zettelkasten/dendron.code-workspace","scheme":"file"},"workspaceFolders":[{"uri":{"$mid":1,"fsPath":"/Users/darren/Documents/Writing/Zettelkasten/drums","external":"file:///Users/darren/Documents/Writing/Zettelkasten/drums","path":"/Users/darren/Documents/Writing/Zettelkasten/drums","scheme":"file"},"name":"drums","index":0},{"uri":{"$mid":1,"fsPath":"/Users/darren/Documents/Writing/Zettelkasten/vault","external":"file:///Users/darren/Documents/Writing/Zettelkasten/vault","path":"/Users/darren/Documents/Writing/Zettelkasten/vault","scheme":"file"},"name":"politics","index":1}]}
{"level":30,"time":1625576504274,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"DendronWorkspace","msg":"initialized"}
{"level":30,"time":1625576504759,"pid":47692,"hostname":"excession.home","name":"SegmentClient","msg":"user telemetry setting: enabled by migration"}
{"level":30,"time":1625576504760,"pid":47692,"hostname":"excession.home","name":"SegmentClient","msg":"telemetry initializing"}
{"level":30,"time":1625576504760,"pid":47692,"hostname":"excession.home","name":"SegmentClient","msg":"using existing id"}
{"level":30,"time":1625576504760,"pid":47692,"hostname":"excession.home","name":"dendron","msg":"Telemetry is disabled? false"}
{"level":30,"time":1625576504761,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"_activate","config":{"version":1,"vaults":[{"fsPath":"drums","name":"drums"},{"fsPath":"vault","name":"politics"}],"useFMTitle":true,"useNoteTitleForLink":true,"noAutoCreateOnDefinition":true,"noLegacyNoteRef":true,"site":{"copyAssets":true,"siteHierarchies":["root"],"siteRootDir":"docs","usePrettyRefs":true,"title":"Dendron","description":"Personal knowledge space","duplicateNoteBehavior":{"action":"useVault","payload":["vault","drums"]}},"initializeRemoteVaults":true,"journal":{"dailyDomain":"inbox.daily","name":"daily","dateFormat":"y-MM-dd","addBehavior":"childOfDomain","firstDayOfWeek":1},"dendronVersion":"0.47.0"},"configMigrated":false,"msg":"read dendron config"}
{"level":30,"time":1625576504768,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"_activate","installStatus":"NO_CHANGE","currentVersion":"0.49.0","previousWorkspaceVersion":"0.49.0","previousGlobalVersion":"0.49.0","platform":"darwin","extensions":[{"id":"dendron.dendron-paste-image","version":"1.0.4","active":false},{"id":"dendron.dendron-markdown-shortcuts","version":"0.12.1","active":true},{"id":"dendron.dendron-markdown-preview-enhanced","version":"0.10.46","active":false}],"vaults":[{"fsPath":"drums","name":"drums"},{"fsPath":"vault","name":"politics"}]}
{"level":30,"time":1625576504769,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"startServer","logLevel":"info"}
{"level":30,"time":1625576504772,"pid":47692,"hostname":"excession.home","name":"api-server","ctx":"appModule:start","dirPath":"/Users/darren/.vscode/extensions/dendron.dendron-0.49.0/dist"}
{"level":30,"time":1625576504775,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"_activate","msg":"post-start-server","port":53356,"durationStartServer":500}
{"level":30,"time":1625576504778,"pid":47692,"hostname":"excession.home","name":"logger","ctx":"FileStorageV2","wsRoot":"/Users/darren/Documents/Writing/Zettelkasten","vaults":[{"fsPath":"drums","name":"drums"},{"fsPath":"vault","name":"politics"}],"level":"info"}
{"level":30,"time":1625576504778,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.reloadIndex:run","msg":"pre-execute"}
{"level":30,"time":1625576504778,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"ReloadIndex.execute","msg":"enter"}
{"level":30,"time":1625576508682,"pid":47692,"hostname":"excession.home","name":"logger","ctx":"parseSchemaModuleOpts","fname":"root","root":{"fsPath":"drums","name":"drums"},"imports":[]}
{"level":30,"time":1625576508686,"pid":47692,"hostname":"excession.home","name":"logger","ctx":"parseSchemaModuleOpts","fname":"resource","root":{"fsPath":"vault","name":"politics"}}
{"level":30,"time":1625576508791,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"ReloadIndex.execute","durationEngineInit":227}
{"level":30,"time":1625576508791,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"ReloadIndex.execute","msg":"exit"}
{"level":30,"time":1625576508791,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.reloadIndex:run","msg":"post-execute"}
{"level":30,"time":1625576508794,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"reloadWorkspace","msg":"post-ws.reloadWorkspace"}
{"level":30,"time":1625576508794,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"reloadWorkspace","msg":"exit"}
{"level":30,"time":1625576508794,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"postReloadWorkspace","msg":"same wsVersion"}
{"level":30,"time":1625576508795,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"postReloadWorkspace","msg":"exit"}
{"level":30,"time":1625576508795,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1625576508812,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"setupViews","msg":"init:treeViewV2"}
{"level":30,"time":1625576508813,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"setupViews","msg":"init:backlinks"}
{"level":30,"time":1625576508814,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"activateWorkspace","stage":"prod","msg":"enter"}
{"level":30,"time":1625576508815,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"toggleViews","msg":"views enabled: true"}
{"level":30,"time":1625576508815,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"_activate","msg":"fin startClient","durationReloadWorkspace":4539}
{"level":30,"time":1625576508815,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"showWelcomeOrWhatsNew","version":"0.49.0","previousExtensionVersion":"0.49.0"}
{"level":30,"time":1625576509110,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:init","msg":"enter","opts":{}}
{"level":30,"time":1625576509110,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:createServerWatcher","msg":"enter","opts":{}}
{"level":30,"time":1625576512111,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:_connect","portCreated":1625576504779,"wsActivation":1625576504762}
{"level":30,"time":1625576512112,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:_connect","msg":"initFromExistingFile","port":53356}
{"level":30,"time":1625576512112,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:tryToConnect","port":53356,"msg":"enter"}
{"level":30,"time":1625576512121,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:tryToConnect","msg":"connected","info":{"version":"0.49.0"}}
{"level":30,"time":1625576512121,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:connectAndInit","msg":"checking for engine"}
{"level":30,"time":1625576512121,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:connectAndInit","msg":"found engine"}
{"level":30,"time":1625576512121,"pid":47692,"hostname":"excession.home","name":"connector","ctx":"EngineConnector:initEngine","msg":"enter","port":53356}
{"level":30,"time":1625576520385,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"/Users/darren/Documents/Writing/Zettelkasten/drums/syllabus.alan-dawson-rudiments.week-01.md"}
{"level":30,"time":1625576520440,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/darren/Documents/Writing/Zettelkasten/drums/syllabus.alan-dawson-rudiments.week-01.md"]}
{"level":30,"time":1625576525936,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"undefined"}
{"level":30,"time":1625576528570,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/darren/Documents/Writing/Zettelkasten/drums/syllabus.alan-dawson-rudiments.week-01.md","/Users/darren/Documents/Writing/Zettelkasten/drums/assets/engravings/exercise.rudiment.roll.single-stroke-roll.ly"]}
{"level":30,"time":1625576538204,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"/Users/darren/Documents/Writing/Zettelkasten/drums/syllabus.alan-dawson-rudiments.week-01.md"}
{"level":30,"time":1625576548352,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.showPreviewV2:run","msg":"pre-execute"}
{"level":30,"time":1625576548353,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"genHTML","view":"dendron.note-preview","src":"http://localhost:53356/vscode/note-preview.html?ws=%2FUsers%2Fdarren%2FDocuments%2FWriting%2FZettelkasten&port=53356"}
{"level":30,"time":1625576548354,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.showPreviewV2:run","msg":"post-execute"}
{"level":30,"time":1625576554517,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"undefined"}
{"level":30,"time":1625578208258,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.dev.openLogs:run","msg":"pre-execute"}
{"level":30,"time":1625578208260,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"execute","opts":{}}
{"level":30,"time":1625578208279,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"dendron.dev.openLogs:run","msg":"post-execute"}
{"level":30,"time":1625578208357,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/darren/Documents/Writing/Zettelkasten/drums/syllabus.alan-dawson-rudiments.week-01.md","/Users/darren/Documents/Writing/Zettelkasten/drums/assets/engravings/exercise.rudiment.roll.single-stroke-roll.ly","/Users/darren/Library/Application Support/Code/logs/20210706T150140/exthost2/dendron.dendron/dendron.log"]}
{"level":30,"time":1625578208364,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"/Users/darren/Library/Application Support/Code/logs/20210706T150140/exthost2/dendron.dendron/dendron.log"}
{"level":30,"time":1625578208367,"pid":47692,"hostname":"excession.home","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","uri":"/Users/darren/Library/Application Support/Code/logs/20210706T150140/exthost2/dendron.dendron/dendron.log","msg":"not in workspace"}

Been a few months since this was opened, giving an update on the various issues with the native Dendron preview.
1) Code Formatting
Resolved. The text is displayed with both a different font and text color, as in the basic VS Code preview.
2) Table Formatting
Resolved. The table lines are now displayed.
2.5) Table Formatting
Unresolved. The behavior of wikilinks in tables remains unchanged.
3) Preview Width
Resolved. The bar to shift the preview pane horizontally is no longer displayed.
4) Header Size
Resolved. The note title and Header 1 are displayed at the correct size.
5) Preview Scroll
Unresolved. The preview does not scroll with the note.

authors: ddbrierton kpathakota micharris42

repo: dendronhq/dendron


text:
HW 21 10 2016

https://github.com/Garasjuk/EPAMtraning2016/tree/master/JsonApplication

https://github.com/Garasjuk/EPAMtraning2016/commit/fe29288e592436c10615e738382feb8f1df193f4


text:
Add support for "react-jsx" and jsxImportSource

(See #10)
This exposes the jsxImportSource  compiler option and allows the jsx option to be "preserve" | "react-jsx" | "react-jsxdev" | "react-native" | "react"

 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.

Thanks! Landed this in #161 with attribution.

authors: CLAassistant benStre dsherret


text:
feat: support for case-insensitive matches

Implements WICG/urlpattern#168
Seems there are no WPTs yet

generate_matcher is going to significantly suffer here. It will be unable to generate matchers for case insensitive parts

thats a problem, but i dont think there is much we can do (I'd be happily proven wrong)

@crowlKats @lucacasonato - Any chance that this might land in Deno? According to https://developer.mozilla.org/en-US/docs/Web/API/URLPattern#browser_compatibility Deno has everything else implemented according to the spec except for the ignoreCase feature.

authors: crowlKats vazexqi

repo: denoland/rust-urlpattern


text:
proposal: add more testing, particularly around database and auth logic

See https://github.com/denoland/saaskit/blob/7d7614636d0629a87c43f97388f357775d46cde7/utils/db_test.ts for an example.

Closing in favour of #267.

repo: denoland/saaskit


text:
[Bug]: "Disable Notifications" Setting not respected on mobile

Describe the bug
The setting is respected on desktop - I do not see any messages from Obsidian Git. However, on mobile, I get constant pop-ups from Obsidian git, telling me everytime there is a push, pull, index, commit, etc. This is even more frustrating on mobile that on desktop, because the status bubbles fill up a third of my screen and are more distracting.
Relevant errors (if available)
No response
Steps to reproduce

Setup an Obsidian Vault that is also a git repo across a desktop device and an iOS device.
Either manually (or just wait for automatic commit/push/pull if enabled) have Obsidian Git perform git commands on your vault on both desktop and mobile.

Expected Behavior
I should only get error messsages from the Obsidian Git extension across all plaforms.
Addition context
I have a single Obsidian fault stored in a git repo that is synced across desktop and mobile (iOS) using Obsidian Git. I have the "Disable Notifications" setting enabled, meaning I should only see error notifications, not standard notifications like "Index x files" or "Pull".
Operating system
Linux
Plugin version
2.8.0

Duplicate of #292

repo: denolehov/obsidian-git


text:
error after fresh installation

just installed on a new iMac, i encountered error message as below:
/usr/local/lib/node_modules/spaceship-prompt/sections/package.zsh:44: parse error near -q' /usr/local/lib/node_modules/spaceship-prompt/sections/xcode.zsh:31: parse error near ".xcode-version"'
/usr/local/lib/node_modules/spaceship-prompt/sections/swift.zsh:31: parse error near ".swift-version"' /usr/local/lib/node_modules/spaceship-prompt/sections/vi_mode.zsh:24: parse error near "vi-quoted-insert"'
spaceship_battery:6: parse error near `}'
spaceship_battery:6: parse error in command substitution
~ 'package' not found'xcode' not found'swift' not found

OK, i resolve this issue.

repo: denysdovhan/spaceship-prompt


text:
Ability to change the colour of the prompt segment symbol

I couldn't see this documented anywhere, but It would be nice to be able to change the colour of the prompt segment symbol, for example: SPACESHIP_PROMPT_COLOR="red"

@jamiestraw Thanks for the request.
As you may have noticed, color of the prompt char changes between green and red depending on the exit code of previous command. So configuring the prompt char color defeats that purpose.

Aha, I hadn't actually noticed that... Nice 😄

May be we could allow options to configure color of prompt for success and failure. Like SPACESHIP_PROMPT_SUCCESS and SPACESHIP_PROMPT_FAILURE.

Sounds ideal!

*_PROMPT_* options are related to whole prompt. char is rather a separated section, so we should consider exposing its options as option for separate section, *_CHAR_* for example.

I would love to submit PR if this is still considered.

#115 is merged. @jamiestraw you can use the latest version from 3.0 branch (carefully) or wait for the official release.

authors: denysdovhan jamiestraw sfarzy

repo: denysdovhan/spaceship-zsh-theme


text:
Support  update PR body of dependabot

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
Hi team, I want to update the pr body of dependabot to add some message , and then i wrote some golang code to update it, just got the error of nvalid Message:Only the pull request author may change the maintainer_can_modify value, this issue is request for dependabot can be setting for the maintainer_can_modify to true and then i can update the PR from golang code,Thanks! Remind me if i missed something!

i can use the command of gh pr edit -R user/repo 123 --body hello to update the pr, so this is not the dependabot issue, closing...

repo: dependabot/dependabot-core


text:
Error when updating NuGet packages from Public and Private Feed

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
NuGet
Package manager version
No response
Language version
C# (.NET 6)
Manifest location and content before the Dependabot update
Manifest files would be kept respectively in the csproj files that contain them,
dependabot.yml content
version: 2
registries:
  internal-packages-nuget-github:
    type: nuget-feed
    url: https://nuget.pkg.github.com/REDACTED/index.json
    username: REDACTED
    password: REDACTED
  nuget:
    type: nuget-feed
    url: https://api.nuget.org/v3/index.json
updates:
  - package-ecosystem: nuget
    directory: "/"
    registries:
      - internal-packages-nuget-github
      - nuget
    schedule:
      interval: daily
      time: "06:00"
      timezone: America/New_York
    groups:
       private-repo-dependencies:
          patterns:
            - "*"
    open-pull-requests-limit: 10
    labels:
      - "nuget"
      - "dependencies"
    assignees:
      - "REDACTED/REDACTED"

Updated dependency
No response
What you expected to see, versus what you actually saw
What I expect: Dependabot to raise a PR with the correct depdendcies updates for both public and private feeds.
What is happening: Only a few packages are being updated and we are getting errors on the rest. Example for a public package:
updater | 2024/02/16 11:43:42 ERROR <job_787880721> Error processing Microsoft.Extensions.Caching.Abstractions (Dependabot::DependabotError)
updater | 2024/02/16 11:43:42 ERROR <job_787880721> FileUpdater failed
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:69:in `run'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/gems/sorbet-runtime-0.5.11193/lib/types/private/methods/call_validation_2_7.rb:59:in `bind_call'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/gems/sorbet-runtime-0.5.11193/lib/types/private/methods/call_validation_2_7.rb:59:in `block in create_validator_method_fast0'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:42:in `create_from'
  proxy | 2024/02/16 11:43:42 [722] 200 https://sentry.io:443/api/1451818/envelope/
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/gems/sorbet-runtime-0.5.11193/lib/types/private/methods/call_validation.rb:169:in `bind_call'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/gems/sorbet-runtime-0.5.11193/lib/types/private/methods/call_validation.rb:169:in `validate_call_skip_block_type'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/gems/sorbet-runtime-0.5.11193/lib/types/private/methods/call_validation.rb:111:in `block in create_validator_slow_skip_block_type'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/group_update_creation.rb:114:in `create_change_for'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/group_update_creation.rb:72:in `block in compile_all_dependency_changes_for'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/group_update_creation.rb:38:in `each'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/group_update_creation.rb:38:in `compile_all_dependency_changes_for'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/refresh_group_update_pull_request.rb:110:in `dependency_change'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/refresh_group_update_pull_request.rb:93:in `perform'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:45:in `run'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/update_files_command.rb:43:in `perform_job'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> /home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:36:in `run'
updater | 2024/02/16 11:43:42 ERROR <job_787880721> bin/update_files.rb:24:in `<main>'

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Could you post the whole log?  There's likely something interesting before the failure listed.

I'm using a similar configuration and have been experiencing this issue for all my repos for the last 2 months or so
In this case, the PR message correctly describes all the necessary updates, but the PR body itself does not contain this
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates

version: 2
updates:
  - package-ecosystem: "nuget" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"
    groups:
      all:
        patterns:
          - "*"

Examples:

https://github.com/tryAGI/Tiktoken/pull/20
https://github.com/HavenDV/OpenApiGenerator/pull/7

Could you post the whole log? There's likely something interesting before the failure listed.

Of course! I have attached it here (since it's massive)
redacted-log.txt
and redacted any information that is personal.

I'm using a similar configuration and have been experiencing this issue for all my repos for the last 2 months or so In this case, the PR message correctly describes all the necessary updates, but the PR body itself does not contain this
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates

version: 2
updates:
  - package-ecosystem: "nuget" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"
    groups:
      all:
        patterns:
          - "*"

Examples:

build(deps): Bump the all group with 4 updates tryAGI/Tiktoken#20
build(deps): Bump the all group with 6 updates HavenDV/OpenApiGenerator#7

Yes, this is a very accurate description of the problem.

@FrankRua some of the log info was truncated too much.  Could you grab some chunks for me from your log?
Specifically line 5749 and the next 100 lines or so.  I need to see the whole line (file paths can be redacted) that starts with:
/opt/nuget/NuGetUpdater/NuGetUpdater.Cli update ...
Similarly line 5826 and the next chunk.
I'm looking for the --dependency, --new-version, and --previous-version arguments and if the --transitive flag is passed.

@brettfo Yes! I have attached it in one text file here, you can see they are separated in sections with:
***********************************
LINES: 5749 - 5885
***********************************

And

***********************************
LINES :5826 - 5922
***********************************

redacted-log-specific.txt
Let me know if you need anything else 😄.

@FrankRua I wasn't able to figure anything out from the bigger log segments.  Are you able to share the full unredacted log with me privately via email?  Maybe something from that will stick out to me.  Anything I receive will only be seen by me and deleted as soon as I'm done.  If this is something you're able to do, my direct email is brettfo@microsoft.com

I've been working with @FrankRua via email and this appears to now be solved.

authors: FrankRua HavenDV brettfo


text:
Dependabot doesn't update NuGet version in all projects

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
NuGet
Package manager version
No response
Language version
.NET 8
Manifest location and content before the Dependabot update
Project layout follows a pattern similar to the following:

/src/Core/Core.csproj
/src/Infrastructure/Infrastructure.csproj
/src/CLI/CLI.csproj
/tests/Core.Tests/Core.Tests.csproj
/tests/Infrastructure.Tests/Infrastructure.Tests.csproj
/tests/TestHelpers/TestHelpers.csproj

dependabot.yml content
version: 2
updates:
  - package-ecosystem: "nuget" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"
  - package-ecosystem: "github-actions" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"

Updated dependency
Microsoft.Test.SDK 17.6.0 to 17.9.0
What you expected to see, versus what you actually saw
I would expect Microsoft.Test.SDK to be updated in all three test projects, but it's only updated in a single project, causing any related restore/builds to fail with a package downgrade error from MSBuild.
Native package manager behavior
Not applicable.
Images of the diff or a link to the PR, issue, or logs

According to the dependabot logs, dependabot knows this dependency is found in other projects:
updater |   name: Microsoft.NET.Test.Sdk, version: 17.6.0
updater |     file: tests/UserCreation.Core.Tests/UserCreation.Core.Tests.csproj, metadata:
updater |     file: tests/UserCreation.Infrastructure.Tests/UserCreation.Infrastructure.Tests.csproj, metadata:
updater |     file: tests/UserCreation.TestHelpers/UserCreation.TestHelpers.csproj, metadata:
updater |   name: MSTest.TestAdapter, version: 3.0.4
updater |     file: tests/UserCreation.Core.Tests/UserCreation.Core.Tests.csproj, metadata:
updater |     file: tests/UserCreation.Infrastructure.Tests/UserCreation.Infrastructure.Tests.csproj, metadata:
updater |     file: tests/UserCreation.TestHelpers/UserCreation.TestHelpers.csproj, metadata:
updater |   name: MSTest.TestFramework, version: 3.0.4
updater |     file: tests/UserCreation.Core.Tests/UserCreation.Core.Tests.csproj, metadata:
updater |     file: tests/UserCreation.Infrastructure.Tests/UserCreation.Infrastructure.Tests.csproj, metadata:
updater |     file: tests/UserCreation.TestHelpers/UserCreation.TestHelpers.csproj, metadata:
updater |   name: coverlet.collector, version: 6.0.0
updater |     file: tests/UserCreation.Core.Tests/UserCreation.Core.Tests.csproj, metadata:
updater |     file: tests/UserCreation.Infrastructure.Tests/UserCreation.Infrastructure.Tests.csproj, metadata:
updater |     file: tests/UserCreation.TestHelpers/UserCreation.TestHelpers.csproj, metadata:

Smallest manifest that reproduces the issue
No response

This looks like a reemergence of the issue here https://github.com/dependabot/dependabot-core/issues/8576, possibly due to this commit https://github.com/dependabot/dependabot-core/commit/02f47fd95be21ba1bf7c39b0309c195f61059573 as it touched the same file after the fix, which seemed to work. I know 0 Ruby so can't comment but perhaps @JamieMagee can take a look?

@prplecake are you able to share any other logs?
@kmcc049 It's hard to say whether or not it's related to Sorbet without any stack traces.

@JamieMagee I'm not sure what other logs I could provide.

@prplecake Is the repo where you're seeing this public?  If not can you share the job ID so I can pull the full logs from my end?  There will be several instances of a string like <job_123456> that should be all I need.

@brettfo Repo is private. I don't have the job ID for the run when I opened this issue, and I haven't had a bunch of dependency updates in the last several weeks. In any case, there was a job that ran two weeks ago, job_817723144, and one that ran a few days ago, job_820810872.
I hope they help.

authors: JamieMagee brettfo kmcc049 prplecake


text:
Bump desired pyyaml to latest due to cython conflict

This spec is currently passing, however it's a time bomb waiting to happen because any version of pyyaml < 6.0.1 throws an inscrutable error with cython 3.0.0: https://github.com/yaml/pyyaml/pull/702
I already fixed a similar error here: https://github.com/dependabot/dependabot-core/commit/0a8e0b46eb928069ea5847875f6faf0232573200
In a newer version of pip-tools this does start failing. But pulling this fix out separately to make it clear.
I considered creating separate handling for this, but it won't appear for most users as most users will be bumping to latest pyyaml, so they will never see this error that happens on intermediate versions. The only reason we see it is that we are pinning the version we want to upgrade to in order to try to keep our specs deterministic.

Hmm... the problem is that this then raises a different error:
Failure/Error:
       expect { updated_files }.to raise_error(Dependabot::DependencyFileNotResolvable) do |err|
         expect(err.message).to include(
           "There are incompatible versions in the resolved dependencies:\n  pyyaml==6.0.1"
         )
       end

       expected Dependabot::DependencyFileNotResolvable, got #<Dependabot::SharedHelpers::HelperSubprocessFailed: ERROR: Cannot install -r requirements/test.in (line 3) and jinja2-cli[yaml]==0.7.0 because these package versions have conflicting dependencies.

I may need to find an altogether different package to use as the example in this test.

Interesting, this error message flip appears to be related to using the legacy resolver... as the test passes if I include --resolver=legacy:
[dependabot-core-dev] ~/python/spec/fixtures/pip_compile_files $ pyenv exec pip-compile --build-isolation --output-file=../requirements/incompatible_versions.txt --no-emit-index-url -P pyyaml==6.0.1 --resolver=legacy incompatible_versions.in
WARNING: the legacy dependency resolver is deprecated and will be removed in future versions of pip-tools.
Using legacy resolver. Consider using backtracking resolver with `--resolver=backtracking`.
Could not find a version that matches pyyaml<5.4,==6.0.1,>=3.10
Tried: 3.10, 3.10, 3.11, 3.11, 3.12, 3.12, 3.13, 5.1, 5.1.1, 5.1.2, 5.2, 5.3, 5.3.1, 5.4, 5.4.1, 6.0, 6.0, 6.0.1, 6.0.1
Skipped pre-versions: 3.13b1, 3.13rc1, 4.2b1, 4.2b2, 4.2b4, 5.1b1, 5.1b3, 5.1b5, 5.2b1, 5.3b1, 5.4b1, 5.4b2, 6.0b1
There are incompatible versions in the resolved dependencies:
  pyyaml==6.0.1
  PyYAML<5.4,>=3.10 (from awscli==1.18.198->-r incompatible_versions.in (line 3))
  pyyaml (from jinja2-cli[yaml]==0.7.0->-r incompatible_versions.in (line 2))

But as soon as I flip to the new backtracking resolver the error changes:
[dependabot-core-dev] ~/python/spec/fixtures/pip_compile_files $ pyenv exec pip-compile --build-isolation --output-file=../requirements/incompatible_versions.txt --no-emit-index-url -P pyyaml==6.0.1 --resolver=backtracking incompatible_versions.in
  ERROR: Cannot install -r incompatible_versions.in (line 3) and jinja2-cli[yaml]==0.7.0 because these package versions have conflicting dependencies.
Traceback (most recent call last):
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 316, in _backjump
    name, candidate = broken_state.mapping.popitem()
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'dictionary is empty'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 92, in resolve
    result = self._result = resolver.resolve(
                            ^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 434, in resolve
    success = self._backjump(causes)
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 318, in _backjump
    raise ResolutionImpossible(causes)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('pyyaml; extra == "yaml"'), parent=ExtrasCandidate(base=LinkCandidate('https://files.pythonhosted.org/packages/83/52/c1bb249f49b204c14bf603e1b1a6dc2db8c3b631c4fe00a2872360085cd6/jinja2_cli-0.7.0-py2.py3-none-any.whl (from https://pypi.org/simple/jinja2-cli/)'), extras=frozenset({'yaml'}))), RequirementInformation(requirement=SpecifierRequirement('PyYAML<5.4,>=3.10; python_version != "3.4"'), parent=LinkCandidate('https://files.pythonhosted.org/packages/4e/68/35522bf3b5ef9186f3cd7cfdc00fe708c019fada077a21009ff78757b0f9/awscli-1.18.198-py2.py3-none-any.whl (from https://pypi.org/simple/awscli/)'))]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/.pyenv/versions/3.11.4/bin/pip-compile", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/piptools/scripts/compile.py", line 657, in cli
    results = resolver.resolve(max_rounds=max_rounds)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/piptools/resolver.py", line 604, in resolve
    is_resolved = self._do_resolve(
                  ^^^^^^^^^^^^^^^^^
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/piptools/resolver.py", line 636, in _do_resolve
    resolver.resolve(
  File "/usr/local/.pyenv/versions/3.11.4/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 101, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts


text:
perf(fly): add sharded list machines

Previously, the list machines takes about 11 seconds. This drops it down to about 2 seconds.

Ok, this is not worth it.  Either I'm doing the queue thing wrong or it is still really slow

Interesting, yeah the queue looks correct to me, Fly may still just be slow

authors: goller jacobwgillespie

repo: depot/cloud-agent


text:
🛑 Derailed API is down

In d9c3d59, Derailed API (https://derailed.one/api) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed API is back up in 0db6aae after 323 days, 14 hours, 54 minutes.

repo: derailed-org/derailed-oss-status


text:
🛑 Derailed Home is down

In e5a600e, Derailed Home (https://derailed.one) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed Home is back up in e6c0ce3.


text:
Replaced HTML codes for greater and less than symbols

cosmetic changes to README.md

Thank you!

authors: derdanne esanchezvela

repo: derdanne/puppet-nfs


text:
Report caller file:line in assert helper fn when test fails

Hi,
I ran into issue #43 and noticed how the error output referenced the assert helper function instead of the actual caller. Here is a suggested fix to make it a bit easier to trace the origin, with the additional cost of importing fmt.

Looks good, just a minor nitpick and then I'll merge it in.

Ok, so I must admit this my first github pull request. I made the requested changes, and to avoid clutter I amended the one commit and forced pushed to my branch. However, I'm not sure this is the preferred workflow. I don't see the change in my github fork, and I begin to suspect force-pushing an amended commit was not the right thing to do.

Hmmm.. that shouldn't cause a problem. Not sure what's happening there, GitHub should pick up the forced push commit.

Now it seems to have been picked up. So I guess I'll stick with the workflow.

Merged, thanks!

authors: derekparker ivarg

repo: derekparker/delve


text:
Requesting to include the strong naming for the Scintilla5.Net assembly

Is your feature request related to a problem? Please describe.
After referencing the Scintilla.NET NuGet package (v5.6.1/v5.6.0) in our project, we encountered a build issue indicating that a strong name is required.  Below is the mentioned error occurred while building the solution.
error MC1000: Unknown build error, 'Could not load file or assembly 'Scintilla.NET, Version=5.6.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A Strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
Describe the solution you'd like
Request to include the strong naming for the assemblies used while referring to the nuget package.
Describe alternatives you've considered
Additional context

There is an ongoing discussion about this already:
https://github.com/desjarlais/Scintilla.NET/discussions/100
I think the workaround of forking the repo and making that a signed version would be a better idea than trying to incorporate it into this one...but I am open to other ideas.

@desjarlais I don't see why signing this lib is such a big deal?

I haven't researched what it would take to add it to the project so I'll take a look at what that entails.  It would be a nice to have, I just haven't looked into the possible issues it could cause yet.

came to reserach the exact same issue and found its just been resolved😀

authors: KalyaniURS ahmetsait desjarlais thehill383


text:
CSV files in webapp/static appear to be absent from git lfs

cloning this repo now fails with:
Error downloading object: webapp/static/A19124_states.csv (76158f0): Smudge error: Error downloading webapp/static/A19124_states.csv (76158f06ce1f43381c535dcded6ddee110fdf7376889f97fc4f6fffc534efcba): [76158f06ce1f43381c535dcded6ddee110fdf7376889f97fc4f6fffc534efcba] Object does not exist on the server: [404] Object does not exist on the server

This would be really helpful to fix. I cannot push or pull to the repo right now because of this problem.

Do you still have this problem? Because I don't fully understand it and I can clone the repo.

Yeah. Do you have git lfs setup? This is the output of a fresh clone:
> git clone https://github.com/destination-earth/DestinE_ESA_GFTS
Cloning into 'DestinE_ESA_GFTS'...
remote: Enumerating objects: 1850, done.
remote: Counting objects: 100% (363/363), done.
remote: Compressing objects: 100% (121/121), done.
remote: Total 1850 (delta 287), reused 241 (delta 241), pack-reused 1487 (from 1)
Receiving objects: 100% (1850/1850), 29.50 MiB | 14.48 MiB/s, done.
Resolving deltas: 100% (1037/1037), done.
Downloading webapp/static/A19124_states.csv (585 MB)
Error downloading object: webapp/static/A19124_states.csv (76158f0): Smudge error: Error downloading webapp/static/A19124_states.csv (76158f06ce1f43381c535dcded6ddee110fdf7376889f97fc4f6fffc534efcba): [76158f06ce1f43381c535dcded6ddee110fdf7376889f97fc4f6fffc534efcba] Object does not exist on the server: [404] Object does not exist on the server

Errors logged to '/private/tmp/DestinE_ESA_GFTS/.git/lfs/logs/20241122T150827.08759.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: webapp/static/A19124_states.csv: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

And checking from the web UI, this file which should be in LFS does not exist (attempting to download it gives 404).

Right. Should we remove these files with git lfs untrack ?

Removed them. These have been just example content.

authors: annefou minrk pantierra


text:
Website search is broken for rules

Steps to Reproduce

https://detekt.dev
search for UseCheckOrError

Expected Behavior
As last week, finds and opens https://detekt.dev/docs/rules/style/#usecheckorerror.
Observed Behavior

Context
For rule identifiers for sure it's not finding them, not sure about other types of docs as I usually search for names of rules.
Your Environment
Windows 10, latest Chrome 103.0.5060.134.

Now it's fixed. I recreated the Algolia index. Thanks for reporting it 👍

authors: TWiStErRob cortinico

repo: detekt/detekt


text:
minified blobs

third_party/webdriver-atoms contains minified javascript blobs -- unreadable, unmodifiable and non-distributable in Debian (i.e. non-free). Please remember that such blobs are practically the same as pre-compiled binaries committed to repository. Please replace with original uncompressed sources.

To perhaps explain the impact of this further, in case it is not clear: because of this issue, phantomjs is not usable as a selenium backend on ubuntu or other debian-derived distributions --- the minified blobs are not included in the packages.

@onlyjob the minified javascript blobs are selenium atoms.  they are compiled with the closure compiler.  debian and ubuntu are more than welcome to compile them from source.  phantomjs includes these resources in the executable.

Please include a README file specifying the build process and where
these files are obtained, if you insist on shipping blobs in source
releases, to make it more likely Debian maintainers will bother (NB. I
have no association with them, just an user).

"wontfix" is not helpful here... Just modify build system to compile selenium atoms. Shipping pre-build blobs is a bad practice... As very minimum build documentation should be made to describe how to re-build those blobs... Thanks.

/README.md does contain documentation on producing minified atoms, per #175 .

authors: dleonard0 jesg onlyjob pv

repo: detro/ghostdriver


text:
🛑 OKTicket is down

In fadd737, OKTicket (https://www.okticket.es) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OKTicket is back up in 1830939.

repo: dev-okticket/status


text:
SwitchBot Color Bulb control

Hi,
Maybe I'm just an idiot and I missed it, but is it possible to control the SwitchBot Color Bulbs?
Thanks

I started the bulb implementation but haven't got around to finishing it. It is a bit more involved then the other devices. I will update this comment if/when the bulb gets supported. Ur the first to ask for it. My assumption is the LED strip is similar and I would try to add that at the same time

authors: devWaves pprobbins


text:
Bump io.micronaut.application from 3.7.10 to 4.0.1

Current WebSocket implementation was deprecated, that's the reason behind the package and classname change. https://micronaut-projects.github.io/micronaut-graphql/latest/guide/
Validation got extracted: https://micronaut-projects.github.io/micronaut-validation/latest/guide/index.html

Requires #217

@yannicklamprecht please rebase

@yannicklamprecht please rebase

Done and resolve issues with javax.validation not found, qa and such.

Here is something breaking with the logging. If you compare https://github.com/devcordde/devmarkt-backend/actions/runs/5602250748/jobs/10247337136?pr=216 with https://github.com/devcordde/devmarkt-backend/actions/runs/5592617112/jobs/10225364931 then you can see that the Flyway migrations are not using the correct logging formatter.
(The backend logs are in the Stop backend section)

Here is something breaking with the logging. If you compare https://github.com/devcordde/devmarkt-backend/actions/runs/5602250748/jobs/10247337136?pr=216 with https://github.com/devcordde/devmarkt-backend/actions/runs/5592617112/jobs/10225364931 then you can see that the Flyway migrations are not using the correct logging formatter.
(The backend logs are in the Stop backend section)

https://github.com/flyway/flyway/issues/3651

authors: Goldmensch Taucher2003 yannicklamprecht

repo: devcordde/devmarkt-backend


text:
Improve our lighthouse scores

A lot of these are just adding alt text to our images.

I fixed some with this pr: https://github.com/devedmonton/devedmonton.com/pull/142
still could use some improvements though

It's feeling snappy for me @MandyMeindersma 🚀

authors: MandyMeindersma MarkBennett


text:
requests/urllib3 installation broken in Dockerfile.db

I tried running the deployment process because eoAPI sounds AWESOME but I hit a snag on the database deployment. I got it working but it's worth a PR to fix it.
Problem description
A recent upgrade to urllib3 seems to have broken the version of requests that gets installed in Dockerfile.db so the BootstrappedDb deployment fails.
I can't seem to get a full traceback from AWS CloudWatch but here is the error message:
[ERROR] Runtime.ImportModuleError: Unable to import module 'handler': cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_' (/var/task/urllib3/util/ssl_.py)

I was able to fix the problem by explicitly installing urllib3<2 in Dockerfile.db:
diff --git a/infrastructure/aws/dockerfiles/Dockerfile.db b/infrastructure/aws/dockerfiles/Dockerfile.db
index 52df1b4..17c4d23 100644
--- a/infrastructure/aws/dockerfiles/Dockerfile.db
+++ b/infrastructure/aws/dockerfiles/Dockerfile.db
@@ -10,7 +10,7 @@ WORKDIR /tmp
 RUN python -m pip install pip -U

 RUN echo "Using PGSTAC Version ${PGSTAC_VERSION}"
-RUN python -m pip install requests psycopg["binary,pool"] pypgstac==${PGSTAC_VERSION} -t /asset
+RUN python -m pip install urllib<2 requests psycopg["binary,pool"] pypgstac==${PGSTAC_VERSION} -t /asset

 COPY infrastructure/aws/handlers/db_handler.py /asset/handler.py

Here is a relevant issue in requests: https://github.com/psf/requests/issues/6432
requests v2.30.0 should be working with urllib3>2 but maybe we are pinned to something less than v2.30.0 by another package. I haven't run the docker network locally yet but will try to dig in to find out the actual best solution.
Environment Information
Ubuntu 22.04, Python 3.10.6

oh nice catch 🙏
I'm sorry because I know that debugging BootstrapedDb step must have been a pain.
I'm not a big fan of requests so I'm going to fix this by replacing it with httpx 😄

should be fixed with latest commit in main 🙏

I'm sorry because I know that debugging BootstrapedDb step must have been a pain.

I got lucky. I tweaked Dockerfile.db and tried again - it worked!

I'm not a big fan of requests so I'm going to fix this by replacing it with httpx smile

Excellent - thanks for the quick fix!

authors: hrodmn vincentsarago

repo: developmentseed/eoAPI


text:
Registry operator incorrect local build source path

Which area this feature is related to?
/kind bug

Which area this bug is related to?

/area registry
What versions of software are you using?
Go project
Operating System and version: RHEL 8.8
Go Pkg Version: 1.19
Bug Summary
Describe the bug:

The main.go source paths under manager and run makefile rules are incorrect:

Makefile#L121
Makefile#L125

As a result, the local build of the registry operator fails.
To Reproduce:

Run make manager.
Expected behavior

Local build should successfully run and create a executable binary bin/manager.
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

test -s /home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin/controller-gen && /home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin/controller-gen --version | grep -q v0.9.2 || \
GOBIN=/home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin GOFLAGS="" go install sigs.k8s.io/controller-tools/cmd/controller-gen@v0.9.2
/home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./..." output:crd:artifacts:config=config/crd/bases
/home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
go fmt ./...
go vet ./...
go build -o /home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/bin/manager ./cmd/main.go
stat /home/mvaldron/source/repos/michael-valdron/devfile-registry-operator/cmd/main.go: directory not found
make: *** [Makefile:122: manager] Error 1

Additional context

Any workaround?

N/A
Suggestion on how to fix the bug

[x] Correct Makefile#L121 to be go build -o $(LOCALBIN)/manager ./main.go
[x] Correct Makefile#L125 to be $(LOCALBIN)/manager

PR ready for review: https://github.com/devfile/registry-operator/pull/58

repo: devfile/api


text:
DWO should track workspaces that go from Running to Starting

Description
The DevWorkspace operator currently makes no note of workspaces that go from the Running phase to the Starting phase. This could be useful information in diagnosing certain issues (e.g. a pod that is continually being updated). In addition, not detecting this event can skew metrics for successful startups, as each time a pod restarts it is counted as a successful start (though with start duration based of when the workspace was initially started).
One factor that should be considered is that sometimes these restarts are expected (if e.g. the user updates their running workspace to use a new plugin).
Additional context
In load testing DWO, I noticed that some pods were continually being recreated, which suggests some sort of issue but isn't tracked by DWO.

Hi, a question to the assignee of this issue:
Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide?
Yes/No?

authors: amisevsk max-cx

repo: devfile/devworkspace-operator


text:
Use Ubuntu 24.04 for workflow jobs

What does this PR do?:

Updates the workflow jobs to use ubuntu-24.04.
Which issue(s) this PR fixes:

PR acceptance criteria:
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened and linked to this PR, if they are not in the PR scope due to various constraints.

[ ] Unit/Functional tests

[ ] QE Integration test

[ ] Documentation (READMEs, Product Docs, Blogs, Education Modules, etc.)

[ ] Client Impact

[ ] Gosec scans

How to test changes / Special notes to the reviewer:

Closing this PR for now, re-open if changes are needed.

repo: devfile/library


text:
How to exclude containers from kibana dashboard?

when we run the metricbeat in kibana the following containers are also shown:
docker-elk_logstash
docker-elk_kibana
docker-elk_elasticsearch
How can we exclude these from the Kibana Dashboard? (Especially in Prod servers)

@prime3045 you can configure a Processor for that: https://www.elastic.co/guide/en/beats/metricbeat/current/filtering-and-enhancing-data.html

@prime3045 you can configure a Processor for that: https://www.elastic.co/guide/en/beats/metricbeat/current/filtering-and-enhancing-data.html
In your case, you should probably use the drop_event processor.
Example (see data sample):
processors:
- drop_event:
  when:
    contains:
      container.image.name:
      - docker-elk_logstash
      - docker-elk_kibana
      - docker-elk_elasticsearch

Many thanks, this is exactly what I was looking for, since I am new with this could you please let me know where shall I configure this processor?

@prime3045 the Metricbeat configuration reference is available at Metricbeat Reference [7.12] » Configure Metricbeat.

To configure Metricbeat, edit the configuration file. The default configuration file is called metricbeat.yml.

If you're using the docker-elk extension for Metricbeat, this file is here: https://github.com/deviantony/docker-elk/blob/main/extensions/metricbeat/config/metricbeat.yml

@prime3045 the Metricbeat configuration reference is available at Metricbeat Reference [7.12] » Configure Metricbeat.

To configure Metricbeat, edit the configuration file. The default configuration file is called metricbeat.yml.

If you're using the docker-elk extension for Metricbeat, this file is here: https://github.com/deviantony/docker-elk/blob/main/extensions/metricbeat/config/metricbeat.yml

Thanks for the response.
For some reason I am getting this error:
Exiting: error loading config file: yaml: line 128: did not find expected key
the modified metricbeat.yml looks like this:
================================= Processors =================================
Configure processors to enhance or manipulate events generated by the beat.
processors:

add_host_metadata: ~
add_cloud_metadata: ~
add_docker_metadata: ~
add_kubernetes_metadata: ~
drop_event:
when:
contains:
container.image.name:
- docker-elk_logstash
- docker-elk_kibana
- docker-elk_elasticsearch

================================== Logging ===================================
What am I doing wrong?

You have mismatched indentations. E.g. you cannot mix indentation levels like you did:
list_of_values:
  - one value    # 2 spaces
- another value  # no space

You must either use "no space" everywhere, or "2 spaces", but not both in the same list.
Correct indentation is critical in YAML documents.

You have mismatched indentations. E.g. you cannot mix indentation levels like you did:
list_of_values:
  - one value    # 2 spaces
- another value  # no space

You must either use "no space" everywhere, or "2 spaces", but not both in the same list.
Correct indentation is critical in YAML documents.
Here are 2 possible syntaxes which are both valid:
processors:
  - add_cloud_metadata: ~
  - drop_event:
    when:
      contains:
        container.image.name:
          - docker-elk_logstash
          - docker-elk_kibana
          - docker-elk_elasticsearch

processors:
- add_cloud_metadata: ~
- drop_event:
  when:
    contains:
      container.image.name:
      - docker-elk_logstash
      - docker-elk_kibana
      - docker-elk_elasticsearch

thank you, now getting this:
Exiting: error initializing processors: each processor must have exactly one action, but found 2 actions (drop_event,when)

My bad! I used the wrong indentation for when:. I just edited my message.

@prime3045 I just tried in a separate Git branch. The syntax is valid, but I still get the events in Elasticsearch for some reason: https://github.com/antoineco/docker-elk/runs/2465889326?check_suite_focus=true#step:8:170
Something must be wrong in the way I used contains: so I'll have to do a little bit more research, but I think we are very close to the solution.

OK, found it.
contains verified that all values match, but we want just one.
You have to use this instead:
processors:
  - add_cloud_metadata: ~
  - drop_event:
    when:
      or:
        - equals:
            container.image.name: docker-elk_logstash
        - equals:
            container.image.name: docker-elk_kibana
        - equals:
            container.image.name: docker-elk_elasticsearch

I changed all as per your comments still getting the containers
https://ibb.co/FnJ8wKS

tried both:
https://ibb.co/g6jbvwH
https://ibb.co/pLvJdC2

Could those be old entries, created before you applied the filter? The filter does not remove old entries, it simply prevents new events from being created. Things that were already created either need to be deleted from Elasticsearch, or you need to exclude them from your dashboards using a Kibana filter expression.
Example:
NOT container.image.name: docker-elk_*

Could those be old entries, created before you applied the filter? The filter does not remove old entries, it simply prevents new events from being created. Things that were already created either need to be deleted from Elasticsearch, or you need to exclude them from your dashboards using a Kibana filter expression.
Example:
NOT container.image.name: docker-elk_*

yes, they might be old entries. How can I "need to be deleted from Elasticsearch" or where to put "NOT container.image.name: docker-elk_*"

@antoineco thanks a ton, after the restart, the container logs are not showing (Except for the "Number of Containers" section, it's counting the ignored ones as well)
https://ibb.co/r4wS9dw

one last thing my metricbeat keeps stopping after sometime, can I use restart= unless-stopped in metricbeat.yml ?

restart: unless-stopped is a Docker Compose setting, not a Metricbeat setting, so it goes inside extensions/metricbeat/metricbeat-compose.yml.
You can do that, but a better solution would be to figure out why the container is stopping by looking at its logs.

@antoineco you rock!!

repo: deviantony/docker-elk


text:
[Feature Request] [Dashboard] - show environment variables for server

No way to know with which environment variables the server (worker) have been started.

We'll show it in 2024.9.1

authors: allburov devlikepro

repo: devlikeapro/waha


text:
error to Execultar gulp command

Error: watch ENOSPC
at exports._errnoException (util.js:746:11)
at FSWatcher.start (fs.js:1172:11)
at Object.fs.watch (fs.js:1198:11)
at Gaze._watchDir (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/gaze.js:289:30)
at /home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/gaze.js:358:10
at iterate (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/helper.js:52:5)
at Object.forEachSeries (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/helper.js:66:3)
at Gaze._initWatched (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/gaze.js:354:10)
at Gaze.add (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/gaze.js:177:8)
at new Gaze (/home/gerardo/projetos/laravel-angular-cms/backend/node_modules/gaze/lib/gaze.js:74:10)

Hello, what npm version you are using?

npm@3.3.5 ,
I am developing a similar project with this , and practically , his is the one who found, you know each other?

Will test npm 3 version soon.
This project own myself. i don't know others. If you would like to develop together . contact me.

yes , I want to work on this project , I hope can make this project grow
My idea is to create a front end page for demo
and sorry for any errors do not speak English errors are graces of the translator google

authors: Gerardo-junior devmark

repo: devmark/laravel-angular-cms


text:
typeahead search not working

I am trying to get typeahead to work, it is working with $http.get but not with the odata library. Seems like it is a problem with returning the promise, not sure if I am missing something.
Works:
return $http.get("/odata/Plants?$filter=substringof('"+val+"',Name)").then(function (response) {
var data = response.data;
return data.value;
});
Returns data but typeahead doesn't get the return and hangs:
appDb.Plants.odata().filter(new $odata.Func('substringof',
new $odata.Value(val),
new $odata.Property("Name"))).query(function (data) {
return data;
});
returns data but typeahead does nothing, doesn't even trigger loading indicator:
return  appDb.Plants.odata().filter(new $odata.Func('substringof',
new $odata.Value(val),
new $odata.Property("Name"))).query(function (data) {
return data;
});

Hi @FarmSol, this is because your library expects a promise, and you're giving it an array. You should use $q and return a proper promise.

Or maybe something like :
var plants = appDb.Plants.odata().filter(...).query();
return plants.$promise;

Some libraries (like angular grids) work well and expect the resource object and know how to check resourceObj.$promise to know when resourceObj array will be populated and to populate the grid.  Others are just built around promises, so you'll have to implement some kind of adapter logic directing it to the $promise, I'm guessing the library would take the response from the properties on the $promise object rather than the resource object itself.
So just keep in mind, this library is a wrapper around the angular Resource object concept.

@devnixs Thanks!!  returning .$promise worked

authors: FarmSol devnixs kyse

repo: devnixs/ODataAngularResources


text:
🛑 Message Board is down

In 96c7bd7, Message Board (https://msg-board-server.onrender.com/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Message Board is back up in 75b0dfb after 10 minutes.

repo: devnullsans/upptime-monitor


text:
Create 0000-01-02-devoloperx.md

Add devoloperx's file

hlo

repo: devoloperx/github-slideshow


text:
Error when try to execute java tests

Expected behavior
As a developer, I want execute "mvn clean test" in order to generate a report on the test coverage.
Actual behavior
It gives me the following error, and the report is not generated.

Steps to reproduce (bug)

Clone the repository
Execute "mvn clean test"

Could not reproduce this issue.. closing ..

authors: DarwinGonzalez sujith-mn

repo: devonfw/my-thai-star


text:
Azure secrets engine

Adding resources to enable flexible configuration of the azure secrets engine in vault.
Adding License file

Overall, this looks great! I've got some nits that I think are worth cleaning up, but otherwise this is good to go.

authors: devops-rob ksatirli