bpf_ep_mgr.go fails to list existing bpf programs when one has a numeric type

Felix logs a warning if there are existing bpf programs (e.g. not created by Calico) which have a numeric type instead of a string type. This likely is caused by the potentially wrong assumption that the type must always be a string.
Expected Behavior

Regardless if "foreign" bpf programs have been applied, Calico should be able to cope and not stumble upon this.
Current Behavior

Example output:
2023-12-05 11:27:55.854 [WARNING][9529] felix/bpf_ep_mgr.go 1846: Failed to list previously attached programs. We may not clean up some. error=cannot parse json output: json: cannot unmarshal number into Go struct field ProgInfo.type of type string
[{
        "id": 8,
        "type": 26,
        "name": "tcp_connect",
        "tag": "1593e302b3115137",
        "gpl_compatible": true,
        "loaded_at":<PHONE_NUMBER>,
        "uid": 0,
        "bytes_xlated": 2752,
        "jited": true,
        "bytes_jited": 1830,
        "bytes_memlock": 4096,
        "map_ids": [1
        ]
    },{
        "id": 39,
        "type": "sched_cls",
        "name": "calico_tc_skb_a",
        "tag": "a97a0a4e8b4470e5",
        "gpl_compatible": true,
        "loaded_at":<PHONE_NUMBER>,
        "uid": 0,
        "bytes_xlated": 15440,
        "jited": true,
        "bytes_jited": 10242,
        "bytes_memlock": 16384,
        "map_ids": [3,15,14,27,28,4,10,9,13
        ],
...

The message suggests that Calico assumes that the type field always is a string, but for this program it is a numeric.
In this example, it is a program created with bpftrace. 26 likely is BPF_PROG_TYPE_RAW_TRACEPOINT_WRITABLE but I am not 100% sure about that. Maybe the fact that a numeric type is returned is caused by an older Kernel or an outdated libbpf.
Possible Solution

If it is assured that Calico's own programs always have a string type, maybe always sched_cls, it would be fair for Calico to only handle those, but it shouldn't fail for other programs.
Steps to Reproduce (for bugs)

Add a bpf program using bpftrace, I could attach the one we are adding, tracing tcp-connects
restart felix/calico-node to let it process all registered bpf programs

Context

We did not really observe an issue with this, we just noticed the warning in the logs. From the warning, it is not fully clear if this has a negative impact on calico or not.
See Slack discussion: https://calicousers.slack.com/archives/CUKP5S64R/p1701778315209489
Your Environment

Calico version 3.26.1/3.26.4
Orchestrator version (e.g. kubernetes, mesos, rkt): vanilla k8s 1.27.7
Operating System and version: FlatCar 3602.2.2 with Linux 5.15.138

/cc @tomastigera


Document possible HTTP status codes a CDS Service may return (fixes #254)

Fixes #254

+1 to Bryn's comment.

@brynrhodes @brettmarquard - I added this in cd8bcff. Can you guys re-review?


change dependabot to weekly

change to every Sunday
group misc packages to reduce number of PR's

Note, dependabot is currently already broken in dotnet/aspire apparently due to a dependabot upgrade today. I have reported this here: https://github.com/dependabot/dependabot-core/issues/8490 ... we can't merge this until it's fixed.
edit: looks like it was https://github.com/dependabot/dependabot-core/pull/8179

I'm going to close until we have fix mentioned


Fix the error message when executing outside the package

Purpose
Fixes: https://github.com/ballerina-platform/ballerina-standard-library/issues/4018
Examples
Checklist

[x] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[ ] Added tests

 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.Danesh Kuruppu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update AboutUs.md

Codecov Report

Merging #4 (ee4444c) into master (1e08e96) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


knative backend impl.

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@JosepSampe how is this looks to you?

@gilv @sadekjb Looks so good! :)
But I have a couple of questions (from the ignorance of how this backend was built ;))
in knative/config.py, there are some yamls that use tekton.dev API: account_res , task_def and task_run, so..

What is the purpose of these three yamls?
and, does it mean that we also need to install tekton (in addition to knative) in k8s cluster?

@JosepSampe, Thanks for your review and comments!
The create runtime path consists of building an image from a source, pushing to registry and then creating a knative service pointing to that image, ready to accept incoming traffic..
These yamls are used as the basis for building and pushing the image and creating the knative service.
In more details, the account_res uses secret_res (docker secrets) which used to enable k8s TaskRun to build and push an image to the docker registry (given it's credentials) while the git_res resource used to guide the TaskRun about the git repo path and the revision the TaskRun need to build the image from. TaskRun consist of one Task (task_def..) that consists of one step which uses kaniko build that uses the docker credentials and other build params.
In the other hand the service_res used for knative Service creation.
These yaml are used as templates, we read as dictionary and enrich them by inputs coming from the different functions by the user - such as docker user and password, registry, paths, etc...
For service creation, Knative Serving component need to be installed in the k8s cluster.
Yes, in addition to Knative Serving, for the build, tekton pipelines need to be installed in the k8s cluster. Tekton pipelines replaces the Knative Build component which is deprecated..


Fingerprints not generating

Hello,
I am trying to generate fingerprints as you show in your documentation. Here is what I have done so far:
1) git clone https://github.com/coleygroup/molpal.git

2) conda env create -f environment.yml
do this in the directory inside molpal which contains the environment.yml

3) conda activate molpal

4) to test for getting rdkit into jupyter notebook,
conda create --name activelearning rdkit
conda activate activelearning
python -m ipykernel install --user --name=activelearning
jupyter notebook
and then create a notebook with the activelearning conda environment

5) start a ray cluster
redis_password=$( uuidgen 2> /dev/null )
export redis_password
ray start --head --redis-password=$redis_password --num-cpus 4 --num-gpus 1
export redis_password
export ip_head=localhost:6379

6) generate fingerprints
python fingerprints.py --library molpal/libraries/Enamine10k.csv.gz --fingerprint pair --length 2048 --radius 2 --name test_library

When I run this last command, it appears to hang up:
(molpal) cseitz@arizona:/net/gpfs-amarolab/cseitz/from_jam/projects/activelearning$ python fingerprints.py --library molpal/libraries/Enamine10k.csv.gz --fingerprint pair --length 2048 --radius 2 --name test_library
2022-01-04 19:46:31,252	INFO worker.py:826 -- Connecting to existing Ray cluster at address: <IP_ADDRESS>:8899
Namespace(delimiter=',', fingerprint='pair', length=2048, library='molpal/libraries/Enamine10k.csv.gz', name='test_library', no_title_line=False, path='.', radius=2, smiles_col=0, title_line=True, total_size=None)

No results get generated after ~36 hours, and the command prompt does not return to the ready position. Looking at the currently running processes, it is not apparent that any of them are associated with fingerprint generation. Do you have any ideas on what I may be doing wrong? Thanks!
Best,
Christian

I'm not sure what the purpose of step (4) is here. Also in step (5) you only need to use a specific redis password if you want to use multiple ray clusters on one node (e.g., multiple processes with independent ray clusters or multiple users utilitizing ray.) You can just type ray start --head --num-cpus X (because fingerprints.py does not use GPU.)
As for hanging, a few questions. is this persistent? What happens if you run it multiple times? Can you use ray on this computer? Can you see that the ray cluster is responsive? Is the fingerprint file HDF5 file created at all?

I worked with the IT people here today, in the end we realized that my download (from a month or two ago) contained scripts that were different from what you can download today; there must have been some incompatibilities that I couldn't otherwise detect. I deleted and redownloaded everything, and now this works per normal. Thanks for your help though.

Glad you were able to sort it out!


Polish readme.md

fix small typos,
fix broken links,
improve readability,
harmonize formatting.

A lot of good improvements!


Support a depthFailMaterial for 3D Tiles

The 1.70 release introduced improvements for underground visualization. One thing that would help a lot is the ability to see what parts of a 3D Tileset are underground, similar to how you can create a depth fail material for polylines. This has a few advantages over just use globe translucency:

Shows the underground data fully without needing to define a cutout rectangle or figure out a near/far distance for transparency
Makes it easier to see exactly where the cut-off level between above ground/under ground is

Any progress on this feature, was real handy on non-tiled models

This is something we are looking for also.

Hi @katSchmid and @meh9, we don't have immediate plans to work on this item. But we'd be happy to accept a Pull Request for this feature if you have the time! Thanks for your interest!


js tests for spl name service

fixes #4004

@joncinque how to build  name service program before js-test. Make cargo-test-sbf run before js-test ?


Enable discussion page

Hi, Óscar.
Would you like to enable a discussion page?
This way, non-actionable items (questions, discussions) can be housed there.
Thank you for Tabi! 🎖

Good idea :)
Done!


Fix bugs in findScripts

Code was buggy when fileStats had only one entry.
Fix bug in pathToRegExp that was not considering '.' as literal.
Make the code easier to unit test.
More unit tests.

PTAL.


Remove findbugs exclusion since it is needed by quarkus-grpc-common

@zhfeng could you please explain, what problem would this change solve? There is no dependency on GRPC in Quarkus CXF.

Well, it is a transitive dep via io.quarkus:quarkus-opentelemetry. I suppose there might be a potential issue like

https://github.com/apache/camel-quarkus/issues/5167
https://github.com/apache/camel-quarkus/issues/6754

OK, thanks, I see that io.quarkus:quarkus-opentelemetry actually depends on quarkus-grpc-common


Problem with cabon-cache to disk destage

Hello,
I want to use graphite together with grafana to visualize storage system performance metrics.
Since these storage systems are having a lot of volumes with a lot of metrics I have a very high amount of datapoints I want to write to the carbon-cache.
Approx. 25000 volumes x 20 metrics each minute. Currently I have 387148 whipser files in the filesystem...
The script I have written to write data to carbon-cache seams to work but I run into issues running it more frequently.
In the past I had configured MAX_CACHE_SIZE to infinite which brought my server to swapping after the carbon-cache process had 4 GB memory allocated. Now I limited MAX_CACHE_SIZE to 12000000 which will allocate approx. 1.6 GB of memory.
If I run the script that inserts the data into carbon 1 or 2 times approx. 900 MB will be allocated. Running it another 2 - 3 times will trigger the following message in the console.log.
28/02/2017 15:22:23 :: MetricCache is full: self.size=12000001
28/02/2017 15:22:23 :: Exception in cacheFull event handler: args=() kwargs={}
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/carbon/protocols.py", line 78, in lineReceived
    self.metricReceived(metric, datapoint)
  File "/usr/lib/python2.6/site-packages/carbon/protocols.py", line 64, in metricReceived
    events.metricReceived(metric, datapoint)
  File "/usr/lib/python2.6/site-packages/carbon/events.py", line 20, in __call__
    handler(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/carbon/cache.py", line 48, in store
    events.cacheFull()
--- <exception caught here> ---
  File "/usr/lib/python2.6/site-packages/carbon/events.py", line 20, in __call__
    handler(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/carbon/events.py", line 32, in <lambda>
    cacheFull.addHandler(lambda: carbon.instrumentation.increment('cache.overflow'))
exceptions.NameError: global name 'carbon' is not defined

I have found another issue about the "global name 'carbon' is not defined" stuff so perhaps I need a patch here but this is not the issues.
My issue is that the cache is not been given free again! It looks like carbon-cache is not really destaging data to the disk...
On a iostat I can see that the service times of the disk where the whisper files are located are fine and in generall he should be able to perform much more write IOPS.
I allready "played" with diffrent parameters. Currently carbon-cache is configured with the following parameters:
MAX_CACHE_SIZE = 12000000
MAX_UPDATES_PER_SECOND = 5000
MAX_CREATES_PER_MINUTE = 10000
LOG_LISTENER_CONNECTIONS = True
USE_FLOW_CONTROL = True
LOG_UPDATES = False
LOG_CACHE_HITS = False
LOG_CACHE_QUEUE_SORTS = True
CACHE_WRITE_STRATEGY = sorted
WHISPER_AUTOFLUSH = True
WHISPER_FALLOCATE_CREATE = True

I allready tried all diffrent cache strategies in combination with AUTOFLUSH true/false.
I have never seen more than 1000 IOPS been processed to the disk.
Below an output from a IOSTAT where dm-6 is the disk where the whisper files are created.
Currently this is just a single disk but it should be able to perform better in my optinion.
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
vda              23.00    20.00   87.00  111.00     0.45     0.39     8.73     1.92    9.20    3.07   14.00   4.48  88.80
dm-6              0.00     0.00  109.00  103.00     0.45     0.40     8.19     1.95    8.70    3.43   14.28   4.19  88.90

Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
vda               0.00    22.22   95.96  143.43     0.41     0.50     7.73     2.11    8.90    2.64   13.09   4.07  97.37
dm-6              0.00     0.00   95.96  126.26     0.41     0.49     8.29     2.03    9.20    2.64   14.18   4.38  97.27

Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
vda               0.00    17.82  103.96  160.40     0.45     0.53     7.61     1.98    7.69    3.21   10.60   3.64  96.24
dm-6              0.00     0.00  103.96  134.65     0.45     0.53     8.37     1.86    8.00    3.22   11.70   4.03  96.24

Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
vda               0.00    21.21   71.72  111.11     0.30     0.40     7.78     2.14   11.87    3.45   17.30   5.36  98.08
dm-6              0.00     0.00   72.73   98.99     0.30     0.39     8.19     2.05   12.08    3.40   18.46   5.72  98.18

What would be strategies for futher investigation of that issue?
Even if I don't import new data for and hour or two the amount of used memory doesn't decrease - I know that this doesn't neccessary mean that nothing got destage but how can I check how much and how fast data is destaged to disk?
As an update:

The picture show that I really have an issue with the destage from cache to disk.
Amount of received points is far higher than amount of commited. Do I interpret this stats corrent?
It would really be nice if you could give me some hints.
Thanks in advance.
Regards
Timo

"global name 'carbon' is not defined" issue is fixed in https://github.com/graphite-project/carbon/pull/486 - it's a small fix.
How many carbon cache instances do you have?

Hi,
thanks for the feedback.
Currently we are only working with one carbon cache instance.
We have accelerated our disk backend which improved the situation a lot.
We are now able to perform up to  615000 commits per seconds.
See picture:

Since we are importing the data every 30 Minutes we might run into out of memory issue if the cache is not destaged after end of an import before the next import starts...
Is there any possibility to have multiple processes for destage of cache to disk?
Regards
Timo

Hi Timo,
Having faster disk is always better, agreed. But you can try to add multiple carbon-caches too.
You need to add another section of variables to carbon cache and install some relay in front of it, like
[cache]
MAX_CACHE_SIZE = 12000000
MAX_UPDATES_PER_SECOND = 5000
MAX_CREATES_PER_MINUTE = 10000
LOG_LISTENER_CONNECTIONS = True
USE_FLOW_CONTROL = True
LOG_UPDATES = False
LOG_CACHE_HITS = False
LOG_CACHE_QUEUE_SORTS = True
CACHE_WRITE_STRATEGY = sorted
WHISPER_AUTOFLUSH = True
WHISPER_FALLOCATE_CREATE = True
...
[cache:0]
LINE_RECEIVER_PORT = 2013
PICKLE_RECEIVER_PORT = 2014
CACHE_QUERY_PORT = 7012
[cache:1]
LINE_RECEIVER_PORT = 2023
PICKLE_RECEIVER_PORT = 2024
CACHE_QUERY_PORT = 7022

[relay]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2003
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2004
LOG_LISTENER_CONNECTIONS = True
RELAY_METHOD = consistent-hashing
REPLICATION_FACTOR = 1
DESTINATIONS = <IP_ADDRESS>:2014,<IP_ADDRESS>:2024
MAX_DATAPOINTS_PER_MESSAGE = 500
MAX_QUEUE_SIZE = 10000
USE_FLOW_CONTROL = True

I can help you if you will provide your carbon.conf and local_settings.py (with comments stripped).

Hi,
this sound like a good way to scale up our environment.
So there is a hash generated by the relay to decide which cache to use.
What is getting hashed there with setting:
RELAY_METHOD = consistent-hashing
Is it the metric?
Regards
Timo

Yes, metric name.


Gamma handling?

24-bit RGB and YCbCr both use a gamma-adjusted scale for luminosity. Averaging of luminosity values must be done in the linear space in order to avoid corruption (shadows expanding/eating nearby pixels).
Does this library address this? I don't see a reference to gamma adjustment, and the storage format appears to be 8-bit per channel, which can only contain gamma-adjusted data without loss, since you need 14 bits to store linearized values without truncation.
The approach you took to SIMD acceleration here is impressive; I haven't seen an equivalent elsewhere.

No, the library only support 8-bit currently, which means no gamma correction
To do that, like you said, you would need to add 8-bit to N-bit conversion, N-bit resize and N-bit to 8-bit.
That was part of my original plans but lost motivation along the way.
Also, I'm not completely satisfied by the current design. Adding N-bit resizes would explode complexity, and maybe just in time code generation is a better way forward.
Anyway, thanks for your comments !


Configurable root volume size for softlayer

It should be possible to specify the size of root volumes on softlayer clusters by specifying control_volume_size and worker_volume_size in the Terraform template. See #723

Are you interested in adding this @eirslett?

Do we have access to soft layer for testing?

We would need to work with someone currently on softlayer.

this might have been fixed at https://github.com/mantl/mantl/issues/723

More correctly, #724 and we would need someone to verify for us.

We need someone with a softlayer cloud account. @eirslett ?
@thomasvincent @Theaxiom :  Sounds like a lot of the support for different providers would require us to get contributors with access to different cloud providers. How do we get people who have access to those?

For now, I suppose we just leave the issue tagged as 'help wanted' until someone steps up.


Feature request: support for Signe gradient

These lamps support 3 color points

What kind of inputs would you like to have?

Input via API Light/Id/Gradient
Followed by up to 5 points and an optional mode, see https://developers.meethue.com/develop/hue-api-v2/api-reference/#resource_light__id__put


Error: Lambda function (aft-lambda-layer-codebuild-invoker)

Bug Description
Error: Lambda function (aft-lambda-layer-codebuild-invoker) returned error: ({"errorMessage": "An error occurred (AccountLimitExceededException) when calling the StartBuild operation: Cannot have more than 0 builds in queue for the account", "errorType": "AccountLimitExceededException", "stackTrace": ["  File "/var/task/codebuild_invoker.py", line 28, in lambda_handler\n    job_id = client.start_build(projectName=codebuild_project_name)["build"]["id"]\n", "  File "/var/runtime/botocore/client.py", line 391, in _api_call\n    return self._make_api_call(operation_name, kwargs)\n", "  File "/var/runtime/botocore/client.py", line 719, in _make_api_call\n    raise error_class(parsed_response, operation_name)\n"]})
│
│   with module.aft_pipeline.module.aft_lambda_layer.data.aws_lambda_invocation.invoke_codebuild_job,
│   on .terraform/modules/aft_pipeline/modules/aft-lambda-layer/lambda.tf line 21, in data "aws_lambda_invocation" "invoke_codebuild_job":
│   21: data "aws_lambda_invocation" "invoke_codebuild_job" {

What service usage limit does it relates to, what should I ask AWS about ?

a moment later...
I found out this block is causing this issue:
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/blob/f8a3a30627f1dfe228dda7db6d64e72957cecece/modules/aft-lambda-layer/lambda.tf#L21-L29
and
looks like my account has concurrent execution for lambda set to 10, I am increasing it to 200.

and till AWS increase my quota, I am commenting these out and continue with my testing 😅

Found out from support guy on aws,
for new accounts even though concurrent build on codebuild is set to 60,
it is not active at beginning
so had to hop on chat to get it active. All good now.


Moved CollapsingAppBar theme to styles. Moved v21 Theme attrs to v21 …

…res file.
Problem: Refactor of last PR.

you did it ha! thanks @tomaszrykala

@malmstein Gotta do what's right! No problem ;-)


fix(scenario_selector): fix a bug in the presence of multiple parking lots

Description

Related links
https://github.com/autowarefoundation/autoware.universe/issues/861

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kminoda are there any updates on this?

@xmfcx No. I forgot about this PR as I was waiting for some comments on the related issue (https://github.com/autowarefoundation/autoware.universe/issues/861).
I will work on this when I have time, but I would appreciate it if one of you would work on this issue for me instead.


Charlyf/dup hostport

Regression introduced in https://github.com/kubernetes/charts/pull/2474
If deployment.enabled=true is used, the deployment fails.

Hey @unguiculus, it appears that [#2474] embedded a commit I did not want to push and as a result there is a regression. Any chance we can test this PR that fixes the issue ?
Also, not sure why the e2e is not running ?
Thanks a bunch

/ok-to-test

/lgtm


Functions Host V3 and Nodej.s Worker V2

v2.x branch currently (see changes here):

introduces "v1WorkerBehavior" flag which reverts everything "[breaking]"

In the future: we want to have the functions host send over specific breaks to opt out of

[breaking] throws on Node.js v8, keeps 8 binaries for V2 host compat
changes worker version to 2.0.0
[breaking] does not duplicate http payload in context.bindingData
[breaking] fixes #228 (handles http output correctly on context.(null, { body: "hello" });

TODO: https://github.com/Azure/azure-functions-nodejs-worker/issues/268

[breaking] fix camelCase of timer trigger object: #188
[breaking] fix type conversion of code like return { outputBinding: info, outputBinding2: info };: https://github.com/Azure/azure-functions-nodejs-worker/issues/232
[breaking] consume "TypedDataCollection" https://github.com/Azure/azure-functions-nodejs-worker/issues/262
add unspecified for http => https://github.com/Azure/azure-functions-host/issues/4890#event-2852029079

TODO:
~- remove Node.js v10 support?~

[breaking] in host and worker, make sure http payload "as raw" as possible
[breaking] rawBody http property should not be a UTF-8 string for byte data (Azure/azure-functions-host#4475)

In the future:

explore options for bugs with protobuf.js and windows (Issue 1303, Issue 1275)

protoc or just default Linux and accept Windows bugs? Probably document windows bugs

do correct fix for camelCase #188 (potentially add .proto)

Also note we need a change on the platform to auto upgrade customers node versions if they move to V3 and are on an older Node version (8, for instance). They should be notified of this change.

Closed with https://github.com/Azure/azure-functions-host/pull/5335


Allow extractFramesFromTimeline to absorb an existing model

In lighthouse, our most expensive main thread work is recomputing the trace model. (we currently do it 3 times.)
If we can pass a parsed model directly into speedline, we'd speed up things a bit.
In this approach, we duck-type things... I'm happy to adjust things if you'd prefer another way.

Now using a nicer instanceof check. :)

👍 to this

Great! LGTM.


Support better pass through pod/container annotation matching

We are using path.Match today.
However, it is very inconvenient to use.
For example, if we want to match 2 annotations google.com/pod/attribute/device, google.com/pod/name, we need to specify 2 match rules:

google.com/pod/*/*
google.com/pod/*

Ideally google.com/pod/* should cover them all.

Based on the Kubernetes annotation key syntax "Valid annotation keys have two segments: an optional prefix and name, separated by a slash (/)." Only one slash is allowed.
I think path.Match is good enough to handle this case then.


Can not get it to compile

Tested it with different Delphi Enterprise versions.
10.3 gives E2393 invalid operator declaration in TensorFlow.Variable.pas line 63 and some more
10.4 gives serveral E2250 starting with There is no overloaded version of 'Create' that you can call with these arguments in Tensorflow.array_ops.pas line 344
11.0 gives [dcc32 Fatale error] TensorFlow.CondContext.pas(175): F2084 Interneral error: NC338

As the result of the function _RemoveExternalControlEdges in TensorFlow.DApi is never used, I changed it to a procedure. Now the demo application can be compiled with Delphi 11.0 and I got it running.
All tests are ok except "Test Models". Getting exception c0000090 FLOAT_INVALID_OPERATION.

[dcc32 Fatal Error] TensorFlow.DApi.pas(34): F2613 Unit 'Spring.Collections.Enumerable' not found.
This file was not found from "https://bitbucket.org/sglienke/spring4d/src/master/Source/Base/Collections/" either.

[dcc32 Fatal Error] TensorFlow.DApi.pas(34): F2613 Unit 'Spring.Collections.Enumerable' not found.
This file was not found from "https://bitbucket.org/sglienke/spring4d/src/master/Source/Base/Collections/" either.

Tried to compile 'TensorFlowDelphi' with result (same as "wilsonning" at Jan 1?): 'Spring.Collections.Enumerable' not found.
I found a 6 years old version at: "https://github.com/FSharpCSharp/Spring4D/blob/master/Source/Base/Collections/Spring.Collections.Enumerable.pas", but again no success.
Will there be an update of TF.D which is compatible to the actual (April 11, 2024) version of "https://bitbucket.org/sglienke/spring4d/src/master/"?
All in all great job! Thank you, @Pigrecos!


Improve copying of comments

In https://github.com/dropbox/mypy-protobuf/commit/eb1defa98654832732368ee4247009212d337567, comments from the .proto files were copied over into the type stubs.
The comments in the .proto files I'm using are intended to be docstrings, but mypy-protobuf writes them out to the .pyi files using # rather than """, and before message classes rather than on the first line of the class body, so they are not treated as docstrings and so don't show up in the documentation view of the IDE I am using (PyCharm 2021.2).
i.e. I would prefer:
# My leading detached comments
class Foo(google.protobuf.message.Message):
    """My leading comments

    My trailing comments
    """
    DESCRIPTOR: google.protobuf.descriptor.Descriptor = ...
    ...

rather than the current situation of:
# My leading detached comments
# My leading comments
# My trailing comments
class Foo(google.protobuf.message.Message):
    DESCRIPTOR: google.protobuf.descriptor.Descriptor = ...

This convention of documentation as a docstring on the first line of the class seems to me to be common enough to justify the suggested pattern. Since there is less of a prevailing convention for how to document attributes of a Python class, I think the current situation (a # comment before the field attribute) is okay for field comments.

Yep agreed! I admit I thought about this in the initial implementation, but ended up doing it this way as a first pass implementation because it was easier (They all use a single helper that uses # comments).

Didn't end up being as tough as expected! Take a look at #281 if you get the chance @jaredkhan . Thanks for the report.


Imported RKE2 cluster is stuck in Upgrading state because of 'apply-rke2-worker-plan' job

Rancher Server Setup

Rancher version: v2.6.3
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1 v1.21.8

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.22.7+rke2r1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported RKE2 cluster

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

If custom, define the set of permissions:

Describe the bug
Importing an RKE2 cluster which has Windows worker nodes leads to Rancher deploying a "apply-rke2-worker-plan-on-nodename" job with an image for which there are no windows builds.
NAME                                                       READY   STATUS                  RESTARTS        AGE
pod/apply-rke2-worker-plan-on-nodename-with-...--1-5p4pg   0/1     Init:ImagePullBackOff   0               10m
NAME                                                    COMPLETIONS   DURATION   AGE   CONTAINERS   IMAGES                                SELECTOR
job.batch/apply-rke2-worker-plan-on-nodename-with-...   0/1           10m        10m   upgrade      rancher/rke2-upgrade:v1.22.7-rke2r1   controller-uid=...

The cluster is then stuck in Upgrading Status in the Rancher UI.
To Reproduce
Create cluster with RKE2 (without rancher, just running the installation guide from here: https://docs.rke2.io/install/quickstart/ and add a windows node.
Import this cluster into rancher by running the kubectl apply -f command presented by Rancher after creating an imported cluster.
Result
Cluster is stuck in Upgrading forever since the job cannot be completed.
Expected Result
Either the rke2-upgrade image is not run on windows nodes at all or there is a build for windows.
Screenshots

Additional context

This is still a problem as of 2.6.8.


LSP server

If TikiBase concept holds up, it might make sense to build a language server.
what does it

auto-complete for links to notes
move file: update all references to this file
rename file: update all references to this file

related

VSCode plugin

notes
There is no LSP-server for Markdown on the community page yet.

This is overkill, just run some CLI tools.


Advisory section contains recommendations for all available subscriptions

Hi,
Windows 11 Enterprise 22H2
PSVersion 5.1.22621.963
{
"azure-cli": "2.44.1",
"azure-cli-core": "2.44.1",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"account": "0.2.5",
"aks-preview": "0.5.122",
"azure-devops": "0.25.0",
"containerapp": "0.3.20",
"log-analytics": "0.2.2",
"resource-graph": "2.1.0"
}
}
I run the script like this :
.\AzureResourceInventory.ps1 -Diagram -TenantID MyID -Subscription MyID
My account (in Azure) has access to three (3) subscriptions. In the advisory I get advices for all three subscriptions and not just for MyID.
Am I doing something wrong, is this how it's supposed to work or is it a bug?
Could it be that 'advisorresources' could use 'advisorresources | where supscriptionId = 'ID')?

Hello,
I suppose this might be a bug.
Will investigate and let you know soon.

Hi @Claudio-Merola ,
anything new on this?

Hi @KlemenDanfoss
I believe there is a bug in the resource-graph extension for az cli.
I tried to workaround the issue with another path.
Can you try the version 3.0.08 and see if works?
Thanks


SCNN test error

hello, i have some broblems when i try  testing your code
(tensorflow) C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane>python test_lanenet.py --weights_path C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane\model\culane_lanenet_vgg_2018-12-01-14-38-37.ckpt-10000 --image_path C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane\demo_file\1.jpg --save_dir C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane\save
WARNING:tensorflow:
The TensorFlow contrib module will not be included in TensorFlow 2.0.
For more information, please see:

https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md
https://github.com/tensorflow/addons
https://github.com/tensorflow/io (for I/O related ops)
If you depend on functionality not listed there, please file an issue.

W0522 12:58:58.895710 12700 lazy_loader.py:50]
The TensorFlow contrib module will not be included in TensorFlow 2.0.
For more information, please see:

https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md
https://github.com/tensorflow/addons
https://github.com/tensorflow/io (for I/O related ops)
If you depend on functionality not listed there, please file an issue.

Traceback (most recent call last):
File "test_lanenet.py", line 118, in
for line in g.readlines():
File "C:\Users\souhayla\Anaconda3\envs\tensorflow\lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 241: character maps to
do you have any idea about this ???

i fixed the brobleme by adding '''''encoding='cp437'  '''''' when i want to open the file but i have another error
Traceback (most recent call last):
File "test_lanenet.py", line 121, in
test_lanenet(args.image_path, args.weights_path, args.use_gpu, img_name, args.batch_size, save_dir)
File "test_lanenet.py", line 58, in test_lanenet
test_dataset = lanenet_data_processor_test.DataSet(image_path, batch_size)
File "C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane\lanenet_data_processor_test.py", line 30, in init
self._img_list = self._init_dataset()
File "C:\Users\souhayla\Desktop\Codes\Codes\SCNNTensorflow\lane\lanenet_data_processor_test.py", line 48, in _init_dataset
img_list.append(info_tmp[0][1:])
IndexError: list index out of range

You can print the length of the list and current index to debug.

i fixed it thanks but finnly i have another one that the checkpoint are not
valid i didn't understand why !!!
Le lun. 25 mai 2020 à 03:10, HOU Yuenan<EMAIL_ADDRESS>a écrit :

You can print the length of the list and current index to debug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cardwing/Codes-for-Lane-Detection/issues/276#issuecomment-633330672,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5LT5NXEKQUOUKI5DYWGZDRTHAR5ANCNFSM4NHYXETA
.


Check for OpenGL backend before calling GL APIs

Signed-off-by: Ian Chen<EMAIL_ADDRESS>🦟 Bug fix
fixes issue found in this comment: https://github.com/ignitionrobotics/ign-gui/pull/323#issuecomment-989142005
Summary
Now that here is support for more than just OpenGL graphics API, we should check that the OpenGL render system is actually in use before making GL calls.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Checked on macOS / Metal


Fix abstraction loading

good find -- fixed locally but was slow to push my own patch of this -- threw in some additional python visualization tools as well, might have to change filepath in sql to get it going


Typo in STU3 resource name for medication-prescribe

In STU3, the resource name is MedicationRequest, not MedicationOrder.  (It's correct in order-review)

Closing as a duplicate of #308 and being fixed in PR #385


Fully support Agents.OpenStreetMapSpace at all apps

Currently WIP. Todos:

[ ] Remove Main. preface for OSMMakie once the package is released
[ ] Start a changelog
[ ] Port example of pathfinding in examples folder and test it as plotting in 3D

Result:

@fbanning everything works now but I had to remove the recipes because i didn't want to deal with this cryptic message that can only be understood by someone that already knows how recipes work. Because I remove recipes there is apparently no more the nice display on hover you've made. I'll wait for you to tell me the simple answer here on how to either enable the recipe or the hover infobox.

Result:

@fbanning everything works now but I had to remove the recipes because i didn't want to deal with this cryptic message that can only be understood by someone that already knows how recipes work. Because I remove recipes there is apparently no more the nice display on hover you've made. I'll wait for you to tell me the simple answer here on how to either enable the recipe or the hover infobox.

I will read through your work on the PR later but for now let me tell you that adding the recipe system has been a very deliberate decision from my side that I've thoroughly thought through before making the PR for it. From all my understanding of how Makie DataInspector works, it is absolutely necessary for the hovering system to work properly without overwriting the tooltips for other plots (e.g. scatter points on the right hand side of abm_data_exploration).
If you want a few simple answers from my point of view:
Removing recipes will

remove the custom tooltips.
remove the standardised interface for easy plotting of Agents.jl models via abmplot.
removes the ability to extend on the recipe system for more complex plots with multiple layers to them, e.g. for OSMSpace.

I'm currently strongly against this step but want to hold back on a final judgment until after I've read what you've done in this PR.

perfect, we keep the recipes! I just don't know how to fix them!

@fbanning one has to simply replace the new lines I wrote:
    if user_used_polygons(am, markers)
        if am isa Function
            markers[] = [translate(m, p) for (m, p) in zip(markers[], pos[])]
        else
            markers[] = [translate(am, p) for p in pos[]]
        end
        # For polygons we always need vector, even if all agents are same polygon
    end

in line 46 of stepping.jl file, with some lines that call your recipe and do not error.

Alright, I've finally found some time to look at what you did here. There's a bit of "noise" in the PR (like renaming files) but the ideas in there are certainly good and helpful. Your initiative here caught me a bit off guard and I first needed to understand what your approach was before responding in any way.
To me it's also important to remember that we're not in any hurry and can safely take a few more days to sort things out and get them right. I would rather not rush a new release just to get it out there.
Anyways, I have now refactored the recipes to properly dispatch on ABM.space instead of agent positions like it did before. This makes them less restricted to "agent-centric" plots like for GridSpace and allows for other displays of the model like for GraphSpace.
The recipes should also be a bit simpler to understand now, I hope, as well as allowing easier extension should we find that we want to add new spaces in the future.
GridSpace and ContinuousSpace are already back in working order. I'm currently working on adding GraphSpace support but it's not quite there yet because it doesn't have a concept of agent positions and I need to find a sensible way to connect am, ac, as with the graph vertices while keeping things as generally usable as possible. Just takes me a bit more time to finish.
Once that works, I will make a PR so that we can move on with implementing OpenStreetMapSpace. But to be honest, I think it's pretty much impossible (or at least very cumbersome) to rebase your work here on top of those changes because you made some fundamental changes like removing the recipe system.
Would you be OK with me taking some of the more structural changes from your PR here (like renaming files and updating the examples and such) and adding them on top of my working branch? This way we will already have a good starting point for adding OpenStreetMapSpace to the bunch of supported spaces right afterwards. (This approach also gives me a bit more time to properly prepare the registration and publication of OSMMakie which I'm working on in parallel.)

Hi @fbanning ,

Anyways, I have now refactored the recipes to properly dispatch on

I am assuming you have done this locally?

I'm currently working on adding GraphSpace support but it's not quite there yet because it doesn't have a concept of agent positions and I need to find a sensible way to connect am, ac, as with the graph vertices while keeping things as generally usable as possible. Just takes me a bit more time to finish

Please wait. Back in the day when we had Plots.jl plotting for graphspace, our plotting was different there. The way it worked is that the functions ac, as, am were taking as an input a vector of agent ids, the agents that are in the node. Based on all the agents in the node one decide the node size, color, and marker. That makes the most sense I think in GraphSpace.

Once that works, I will make a PR so that we can move on with implementing OpenStreetMapSpace. But to be honest, I think it's pretty much impossible (or at least very cumbersome) to rebase your work here on top of those changes because you made some fundamental changes like removing the recipe system.

That sounds like an inefficient way forwards. This PR works with three spaces. It actually doesn't work with OpenStreetMap because it is not registered, but it would if it was. What we should do is merge this PR that works perfectly and you branch after the merged PR. The main recipe file I haven't really touched anyways.

I am assuming you have done this locally?

No, on a branch of my fork.

The way it worked is that the functions ac, as, am were taking as an input a vector of agent ids, the agents that are in the node. Based on all the agents in the node one decide the node size, color, and marker. That makes the most sense I think in GraphSpace.

That's how I wanted to do it in the abmplot recipe for GraphSpace, yes. Maybe I misphrased something above.

That sounds like an inefficient way forwards. This PR works with three spaces. [...] What we should do is merge this PR that works perfectly and you branch after the merged PR. The main recipe file I haven't really touched anyways.

To be honest, I'm not really happy about this because I feel my concerns are ignored. But since you already merged it, I will look at what can be done with the new state of the master branch. Will take me some time again to understand it and refactor things appropriately. Will open a PR once that's done.

It actually doesn't work with OpenStreetMap because it is not registered, but it would if it was.

I'm aware of this. You already know that I will register the package once it provides a minimal working state with a few more key features implemented (like colouring ways by their type). This is heavily WIP. I cannot work any faster on it than I'm already doing right now.

If you think there is better action moving forwards besides merging this and starting a new PR from master, then certainly let me know!

No, it's one way or the other. I just thought it might be easier to do it the other way around but it's OK now. I'm slowly going over the new code on master branch and will copy over everything from my WIP branch that I deem important. Don't worry. It will just take some time. I've opened a draft PR #87 for you to see how it's going on.

For the GraphSpace, we are completely on the same page as far as I have understood.

Certainly.

This seems to be coming off totally the wrong way. [...] I'm just saying this so that you don't have to be so stressed about putting work into OSMMakie.jl!

Yeah, maybe.


wrong decryption of password/cipher

Following the description at http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html#_encryption_and_decryption I tried to encrypt and decrypt my passwords. This works all fine, unless the password contains a "+" (plus) sign. If I decrypt the cipher of a encrypted password with a "+" then the resulting string does not contain the "+" anymore.
e.g.
$> curl localhost:8080/encrypt -d myp+ass
$> 3bd5c274f5d5bdcb9c93069a370a17ca4b8abc8174e8178a2f36134758d946f9
$> curl localhost:8080/decrypt -d 3bd5c274f5d5bdcb9c93069a370a17ca4b8abc8174e8178a2f36134758d946f9
$> myp ass   # -> missing "+"

I also tried with with escaping "myp+ass", but it does not help either.
This seem not like such a big deal when you have the chance to define your passwords by yourself, but when the passwords are generated then this is a blocker (like on AWS).

See also https://github.com/spring-cloud/spring-cloud-cli/issues/11

It works if you encode the input:
$ CIPHER=`curl localhost:8888/encrypt -d my%2Bpass`
$ curl localhost:8888/decrypt -d $CIPHER
my+pass

yes, I've seen the same thing, the data needs to be urlencoded.

We should include that in the docs I guess. But I don't think there's anything to change in the config server.

I agree.

:+1: yes, encoded works - thanks!


og:image is invalid

https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fubicenter.github.io%2Fcalifornia-ab65-calubi shows

Provided og:image URL, /assets/images/2021-04-03-california-ab65-calubi/cover.png was not a valid URL.

It still works since it seems to grab the first image so low priority but we should fix at some point.

I think this is keeping LinkedIn from previewing the image https://www.linkedin.com/company/53569812/admin/


FileTarget: Performance improvement for CleanupInvalidFileNameChars

Current coverage is 76% (diff: 100%)

Merging #1582 into master will decrease coverage by <1%

@@             master      #1582   diff @@
==========================================
  Files           270        270
  Lines         16413      16410     -3
  Methods        2621       2621
  Messages          0          0
  Branches       1787       1787
==========================================
- Hits          12522      12507    -15
  Misses         3488       3488
- Partials        403        415    +12

Powered by Codecov. Last update 7d8305d...ab311f8


Expand allowed data capacity for barcodes if size constraints allow

https://www.reddit.com/r/rust/comments/1117fpk/comment/j8ea409/?utm_source=share&utm_medium=web2x&context=3

Looking at this, it appears that we should support up to version 40. I tested with default settings and adding a 1kb file and RXing-cli errors with “data too large to encode”. I believe that this is due to either the estimate_size or pick_version helpers in the QRCode encoder module.

Needs a test case, it looks as if the provisional test for size might not account for varying ec levels, when no ec level has been specified.


nixos/xserver:services.xserver.xkbOptions is now commas

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/18646
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/68

This is a breaking change right? If so, maybe a changelog entry would be good.
Also as a minor nitpick: Please use the imperative in your commit message and talk about your intention, not the implementation details (Make xkbOptions mergable or similar).
CC @Ericson2314

This is a breaking change right? If so, maybe a changelog entry would be good.

No, it shouldn't break any existing module or config:
nix-repl> lib.types.str.check "a,b,c"
true

nix-repl> lib.types.commas.check "a,b,c"
true

However if two modules set xkbOptions the values will be appended.

Nice. I don't have much experience with NixOS modules, so thanks for clarifying. Since @Ericson2314 raised the initial issue and has merge rights himself, I think its best if he takes a look at this and ultimately merges it. If he's unresponsive for a couple of days feel free to ping me again.

@pasqui23 Do you know how you can change the commit description the way @worldofpeace suggests? If not, git commit --amend is what you need.

Thank you @pasqui23 !


Fix for app crashing occasionally on iOS

https://github.com/rurico/flutter_video_compress/issues/60#issue-499052434

@Martibis @jonataslaw  This PR is effective and solved my crash.

Thanks for merging @jonataslaw, any chance you could update it at pub dev too?

I will update now

@all-contributors please add @Martibis for maintenance


Add test section in recipe

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Please add test for:
import tensorflow_io_gcs_filesystem


[$1000] [Manual Requests] Ensure correct amount is displayed in the IOUPreview

Coming from this comment, transaction amounts for Expense reports are stored as negative values in the database, so we need to invert the sign from negative to positive and vice-versa.
This is because there are instances where you can get a credit back on your card, or you enter a negative expense to “offset” future expenses. So in theory, the total of your expenseReport could be a negative.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013a4895d6068712f5
Upwork Job ID:<PHONE_NUMBER>162098688
Last Price Increase: 2023-05-10

@mollfpr it might be clear from the body but just noting this applies only for the expense reports, not for the IOU reports

@mountiny Yes, this only happen on the expense reports.

Dope, are you good with a PR for this one @mollfpr?

@trjExpensify Yup! Will clean up my tasks on the proposals review and then raise a PR for this.

Neat, thanks!

https://github.com/Expensify/App/blob/5df596f1be385c9767aef239fd24a6d2fd7771e7/src/libs/actions/IOU.js#L79

transaction amounts for Expense reports are stored as negative values in the database

@luacmartins in building an optimistic expense report based on the above comment, should we subtract the amount rather than increase it?
We have this glitch in the expense report
https://github.com/Expensify/App/assets/25520267/e331f22c-f54c-4e85-aae0-7bdcc3c691eb

Yes, we should do that

PR merged

[@mollfpr / @sobitneupane] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr / @sobitneupane] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@mollfpr / @sobitneupane] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Not a bug. This issue is another work for https://github.com/Expensify/App/pull/18537.

[@mollfpr / @sobitneupane] Determine if we should create a regression test for this bug.
[@mollfpr / @sobitneupane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Propose regression step.

Go to the workspace report
Request money using the action menu item
Put any amount
Submit the requested money
Verify that the IOU preview is shown with a positive amount
Verify that the amount on the Expense report that just added in LHN has a positive amount
Navigate to the Expense report that just added
Verify that the report header shows a positive amount
Back to the workspace report and do request money again
Verify again step 5, 6, and 8
👍 or 👎

Make sense to me!

Alrighty, time to settle up here. Sorry for the delay, as I get back from EC3.
I've sent the following offers on this job:
@mollfpr - $1,500 for the fix & #urgency bonus
@sobitneupane - $1,500 for C+ & #urgency bonus

Settled up with @mollfpr. Awaiting @sobitneupane!

@trjExpensify I didn't review the PR. So, no payment for me.

Ah cool, got it. Thanks! Closing this out then. 👍


remove duplicated alias

CARD64 will always be declared later, also see Issue 15167 – [REG2.069-devel] conflicting error with repeated alias declaration.

Thanks


Add OS to build artefacts

As @rgooding pointed out, the file names may not easily identify the OS they were built for and we should add it to the file names:
AxonOpsCassandra-0.1.0-internal-20240716-arm64.pkg -> AxonOpsCassandra-0.1.0-internal-20240716-mac-arm64.pkg

This is easy to do with a macro: https://www.electron.build/file-patterns#file-macros

@digiserg also - we should populate this stuff also
https://www.electron.build/api/electron-builder#AppInfo


FE: App sessions list does not scroll to top after paging

https://github.com/matrix-org/matrix-authentication-service/issues/1535

This one is a quick win: adding resetScroll to pagination links should be enough
We should also consider enabling scroll restauration so that moving back/forward history restores scroll state


Incompatibility with Tectonic / Terralith

Not sure which one, assumed it would be Tectonic but I’ve heard of a similar problem with Terralith. Issue on 1.20 Fabric, would greatly appreciate it if compatibility could be looked into.

I will look into it, but unfortunately I believe this is likely an issue on Terralith's end. Profundis works by modifying the vanilla biome distribution, while Terralith and other datapacks like it override the vanilla biome distribution. I have heard some say that using Terrablender helps with it, as Terrablender puts two different biome distributions together. I'm sorry I wasn't super helpful :( I will try to look into it

No problem, by the sounds of it there’s not much that can be done anyway. I appreciate the support regardless. Could the issue be bypassed by extracting the data folder of Profundis and using it as a datapack as to avoid it being overridden?

Unfortunately not :/ Profundis works by adding to the VanillaBiomeParameters class (specifically the writeCaveBiomes function) to ensure the most compatibility with other mods. This works because VanillaBiomeParameters is ran during the game to generate the Overworld's biome distribution JSON. However, using a datapack such as Terralith doesn't grant such freedom as they are required to override the Overworld dimension JSON with their own layout, which overrides ALL of the biome layout. The only ways to fix this would be for me to either invasively override how Multinoise works, or to make a new datapack with both Profundis and Terralith biomes, which the latter would be honestly pretty easy to do. Once I push out the new update for Profundis I could try my hand at making a compat layer possibly!

That would be amazing if you get the chance, but don’t stress too much! Will keep an eye on this project as I would love to include it in my modpack’s upcoming 1.20 release.
Sent from my iPad

On 21 Jul 2023, at 9:53 am, firenh @.***> wrote:

Unfortunately not :/ Profundis works by adding to the VanillaBiomeParameters class (specifically the writeCaveBiomes function) to ensure the most compatibility with other mods. This works because VanillaBiomeParameters is ran during the game to generate the Overworld's biome distribution JSON. However, using a datapack such as Terralith doesn't grant such freedom as they are required to override the Overworld dimension JSON with their own layout, which overrides ALL of the biome layout. The only ways to fix this would be for me to either invasively override how Multinoise works, or to make a new datapack with both Profundis and Terralith biomes, which the latter would be honestly pretty easy to do. Once I push out the new update for Profundis I could try my hand at making a compat layer possibly!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

@firenh I think I can add compatibility myself, however I'm not sure what you set these parameters to. If you could provide the parameters, I could probably do it myself and make a compat datapack. Unless I'm missing something, we just need to override this file, but add your biomes to it https://github.com/Stardust-Labs-MC/Terralith/blob/1.20.1/data/minecraft/dimension/overworld.json

Terrablender fixes all of those incompatibilities

@mateus3c that doesn’t count as a solution, as it absolutely ruins worldgen. Still incompatible, and it’s still an issue. Terrablender does not count towards compatibility imo

@mateus3c that doesn’t count as a solution, as it absolutely ruins worldgen. Still incompatible, and it’s still an issue. Terrablender does not count towards compatibility imo

wdym by it ruins worldgen. also wdym by Incompatibility with Tectonic / Terralith. whats the issue?

@stunlocked1 as most people know, terrablender stuffs biome sizing and weighting, and ruins worldgen. Incompatibility’s pretty clear - biomes are unable to generate

@stunlocked1 as most people know, terrablender stuffs biome sizing and weighting, and ruins worldgen. Incompatibility’s pretty clear - biomes are unable to generate

wdym by it ruins worldgen. im running it and doesnt look ruined. whats the issue?

@stunlocked1 as most people know, terrablender stuffs biome sizing and weighting, and ruins worldgen. Incompatibility’s pretty clear - biomes are unable to generate

it says "Terrablender has nothing to do with biome sizing, that's entirely up to the biome mod dev using it. biome placement noise is a vanilla thing, Terrablender just adds a way to allow multiple biomes to use any given noise parameter:"

Please just read what I said previously. It still stands, and I’ve already explained it. It leads to micro-biomes and potential disconnects between worldgen and biomes with some datapacks. Idc what you read, because it doesn’t change the simple reality of what I said

Please just read what I said previously. It still stands, and I’ve already explained it. It leads to micro-biomes and potential disconnects between worldgen and biomes with some datapacks. Idc what you read, because it doesn’t change the simple reality of what I said

thats just increasing worldgen variety imo. micro-biomes do exist irl. but I see what you are saying

Again, due to the nature of Terralith, it breaks worldgen syncing with biomes for some biomes such as the Glacial Chasm or Nullscape’s End biomes. On top of that, there are typically so many micro-biomes together that it ruins it in general, on top of the myriad of issues. Anyway, hopefully some sort of proper compatibility can be sorted at some point, though it’s no big issue if not.


NoteEvent limitation (?)

Is there any way of, in a single track, playing two notes, with different durations, simultaneously?
 Is there any way of producing it with this API?
The same for arpeggios: is it possible to start a note before stopping the previous one?

Hi @PedroAlvesV ,
Currently it is not possible to have overlapping durations within a single track in this API; it would have to be on separate tracks.  This would be a nice feature, though I'm not sure how the API would look for that.  Do you have any ideas?
-Garrett

Yep. I was thinking about giving the user more control over it. I mean, the NoteEvent is an awesome abstraction, but, as I pointed, there's this one limitation. Maybe if the user could, by wish, set the On and Off signals, it would solve the problem. So, it would keep the NoteEvent, but also offer the usage of NoteOn and NoteOff.
Another thing that I noticed is that these classes (NoteOn and NoteOff) do exactly the same, and what they do is not even enough to justify a single whole class, from the way I see it. Also, they're used exclusively in NoteEvent:buildData() and in Track:polyModeOn().

What I would do (and probably will with LuaMidi haha):

Create a Util function to create a table like these current NoteOn/NoteOff objects (possibly "on_off_signal()" or something similar)
Rewrite NoteOn and NoteOff to let the user use them (as stated in the first paragraph)

Hi Pedro,
Good ideas.  I think I used separate classes for NoteOn and NoteOff with the thought that it would be convenient to add more functionality to them later.  You're right though, currently they're just containers for properties.
I'm thinking something like this may work to provide the ability to have two simultaneous notes with different durations, where the duration index would line up with the pitch index:
new MidiWriter.NoteEvent({pitch: ['E4','D4'], duration: ['4', '2']})

The problem, though, is how to know where the next NoteEvent will begin.
As you suggested, we could provide functions which allow you to explicitly turn on/off notes, but the user/developer would need to keep track of timing themselves though so it's just not very user friendly.  Do you have a particular need for this, or is it just something you had in mind?
-Garrett

He would have to be aware of the delta time, that's true, but most people working with MIDI frameworks do. Besides, the NoteEvent would always be available.
I have been wondering about it because I wrote a function that receives a MIDI file and creates LuaMidi objects to represent it. It works pretty fine, actually. The only thing I couldn't manage it to get, yet, is the timing, but that's because I haven't code anything this week haha
However, this overlapping functionality is somehow a basic need. Take as example Stairway to Heaven's intro. It sounds kind of chiptune or something like it, because the arpeggio sounds as if there's a hardware limitation of one note at a time.

I think in the case of Stairway to Heaven, and other similarly played sustained arpeggios, changing the note durations isn't the best approach because it becomes a bit unreadable as musical notation.  I understand that you can dial in the exact note length that way though.  The notes would still be abruptly cut off instead of trailed off.
For this case I think there should be support in this API for Controller Change events.  Then you can apply a sustain pedal as needed for the notes that should be sustained.
Looks like the status code for Control Change is Bn.  Here's a list of messages:
https://www.midi.org/specifications/item/table-3-control-change-messages-data-bytes-2
I'll take a closer look at this when I have some time and try to incorporate into MidiWriterJS.
-Garrett

Hi @PedroAlvesV,
I've added a ControllerChangeEvent class in 1.5.2 which can be used to add controller events.
track.addEvent([
	new MidiWriter.NoteEvent({pitch: ['A4'], duration: '4'}),
	new MidiWriter.ControllerChangeEvent({controllerNumber: 1, controllerValue: 127}),
	new MidiWriter.NoteEvent({pitch: ['B4'], duration: '4'}),
]);

I think whether or not the control changes are respected will depend on the player you use.  But you should now be able to add sustain pedal controls to achieve what we were discussing above.  Let me know if you have any issues.
-Garrett

I knew there was an issue somewhere I meant to comment on!
Starting one note on a channel before another ends (legato?), where the second note "chokes" the first seems often to be how slides/glissando are sequenced on 303-style hardware synths (MB-33 & clones, TT-303, x0xb0x...), probably because they tend not to have MIDI implementations sophisticated enough for controller events. Some more sophisticated synths (e.g. Behringer DeepMind 12) also use this same mechanism, the speed of the slide (or none at all) being dependant on a portamento setting.
IIRC MIDI notes on a single channel cannot overlap, so no gap is a primitive way of specifying slide.
However I have not tested this with MidiWriterJS (I am using it to algo-generate MIDI files and play them with hardware) but will give it a go and find out. Thanks!


Refactor definition and response generator to properly handle slice, map and interface types

I open PR to my old PR to show only additions to support all types including interfaces.
I have been burn out while doing this because there are many cases and it got more complicated 😄 Fixing something brokes another thing etc. And I am tired 😮💨
I think I achieved to support many types that you can see in example/fiber/server.go
But it came with complexity ofc. I think it should be refactored later.
I added hashes after each model which generated from its value. This provides overriding types expecially maps and interfaces.
Btw, I will review my code and refactor necessary parts later in my free time. Can you point the parts which are complex when you review?

@anilsenay I was thinking of merging in your changes but holding off on some like the response.New(), CustomResponseType, and the new supported types that you're parsing until we add some testing so we don't rush in to it or delay our release going down more rabbit holes of complexity. The initial set of functionality we were working on seems to be a good starting point, and the automated tests i have for it seems to be working great. What are your thoughts on that? Do you see any changes that I pointed out that you think are critical to be released in v1.0.0? Let me know when convenient 😁 !

Hmm, I think the last changes that I made is not production ready. I already did them for experimantally to see if we can achieve support more types. You see there is no test etc. Maybe we can just release v1.0.0 without this PR by just merging only your PR. In your PR the whole API changed but the generation did not effect so generation will be same as before without breaking anything.
In summary,

https://github.com/domhoward14/swagno/pull/4 will be merged
https://github.com/domhoward14/swagno/pull/3 will be merged
After this two pr merged, your pr https://github.com/go-swagno/swagno/pull/21 will be ready to merge

@anilsenay I was thinking of merging in your changes but holding off on some like the response.New(), CustomResponseType, and the new supported types that you're parsing until we add some testing so we don't rush in to it or delay our release going down more rabbit holes of complexity. The initial set of functionality we were working on seems to be a good starting point, and the automated tests i have for it seems to be working great. What are your thoughts on that? Do you see any changes that I pointed out that you think are critical to be released in v1.0.0? Let me know when convenient 😁 !

Hmm, I think the last changes that I made is not production ready. I already did them for experimantally to see if we can achieve support more types. You see there is no test etc. Maybe we can just release v1.0.0 without this PR by just merging only your PR. In your PR the whole API changed but the generation logic did not effect so generation will be same as before without breaking anything.
In summary,

Feat/refactoring #4 will be merged
Refactor definition and response #3 will be merged (i think Feat/refactoring #4 already covers this pr)
(make last refactors after merge them)
After this two pr merged, your pr v1.0.0 update go-swagno/swagno#21 will be ready to merge
After release v1.0.0, we can work on supporting new types in time. I tried to make it on time so It made the code a lot complex by adding bad written codes. I think we can do it better if we don't try to push

What do you think? @domhoward14

Yup, totally agree! I think we're on the same page. I have a list of things i'm going to finish in the next 2 days then i'll be ready to merge Feat/refactoring into v1.0.0 😁


[SPIKE] Proof of concept for removing log-and-throw and log-and-rethrow

Overview
Before executing https://github.com/vmware/versatile-data-kit/issues/2570, we need to test the concept on some real scenarios and see the actual user experience. A good way to do this is to execute some failing example jobs in Supercollider with the change in vdk-core and check the logs.
DoD

We have a proof-of-concept branch + short analysis and examples for removing the pattern
Sync conclusions with rest of team

It seems our error format doesn't work well when wrapping our custom errors in other custom errors. Example with added delimiters.
-----------------------------
An error in data job code  occurred. The error should be resolved by ResolvableByActual.USER. Here are the details:
  WHAT HAPPENED : Processing step 30_ingest_into_table.py completed with error.
WHY IT HAPPENED : An exception occurred, exception message was: -----------------------------
An error in data job code  occurred. The error should be resolved by ResolvableByActual.USER. Here are the details:
  WHAT HAPPENED : Provided method, SQLITE, has invalid value.
WHY IT HAPPENED : VDK was run with method=SQLITE, however SQLITE is not part of the available ingestion mechanisms.
   CONSEQUENCES : I'm rethrowing this exception to my caller to process.Most likely this will result in failure of current Data Job.
COUNTERMEASURES : Provide either valid value for method, or install ingestion plugin that supports this type. Currently possible values are ['http', 'file', 'sqlite']
-----------------------------
   CONSEQUENCES : I will not process the remaining steps (if any), and this Data Job execution will be marked as failed.
COUNTERMEASURES : See exception and fix the root cause, so that the exception does not appear anymore.
-----------------------------

It's extremely hard to understand what kind of error happened without the added delimiters.

It seems we conflate logging the an error with the actual exception error messages. We should have a few simple rules:

We should log error messages and throw an exception, but the message we log cannot be the error message of the exception. This should apply to logging and throwing in internals.
We should analyze the traceback and build the final exception message at the app exit point (top-level components like job_input), e.g. when we know we're going to throw the exception. At this point, if it's a User error, we can cherry-pick all the user and non-internal stack frames and log them, then throw the exception with the same message. If it's a platform error, we should log all relevant stack frames again (probably all stack frames) and throw the exception.

I was messing around with the code some more and ended up with this diff https://github.com/vmware/versatile-data-kit/pull/2634/files
These are the issues that popped up

If vdk exits with exit code 1, it prints out the stack trace for the error. The problem with this is that we already logged the stack trace when we handled the exception, so we end up outputting the same thing twice. Hacking the code to always return 0 shortens the stack trace by half. There should be a nicer way to do it, however.

We log too many exceptions along the call stack, so error messages from the exception we log in the run method end up  in the traceback logs.

Our exception format does not support nesting in the cases where one VKD exception concatenates the message from another VDK exception with its own error message.

Note: Look at the resolvable context next. It doesn't seem to be used for anything, so maybe we can remove it.

We can remove resolvable context, I think. It's not used for anything, e.g. some errors are stored in there, but nobody looks at it after.


Continuous CT button can now only select continuous CT's, Discrete CT Button only discrete CT's

Description
Resolves #17799

The continuous CT button in the color table window can now only select continuous color tables.
The discrete CT button in the color table window can now only select discrete color tables.
This works in tandem with the new tagging system. Tags will filter your selection further for these buttons.

Type of change

[ ] Bug fix~~
[x] New feature~~
[ ] Documentation update~~
[ ] Other~~

How Has This Been Tested?

built and ran on rztopaz toss3 and it acted as I expected.
Checklist:

[x] I have followed the style guidelines of this project.~~
[x] I have performed a self-review of my own code.~~
[x] I have commented my code where applicable.~~
[x] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have confirmed new and existing unit tests pass locally with my changes.
[ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[x] I have assigned reviewers (see VisIt's PR procedures for more information).~~

merge w/ deveop in #17877


Podman deployment documentation

Docker is proprietary software and requires a paid license in many cases. Even if institutions are not making commercial tools with their pygeoapi deployment, the license is not free and open source, and I am assuming that because of this, it may not be an option for some governments or institutions

However, containerization seems to be the best option for deploying pygeoapi

https://podman.io/ uses a similar API as Docker, so ideally we can use the same Dockerfiles, but it is free and open source

Thus it is likely to be a preferred option for some institutions.

However, it is bit less feature rich so we would need to test it a bit before documenting it.

Does this seem reasonable? Feel free to close if not or if I do not have the full context on deployment tools within our partner organizations.

Fwiw it seems that podman run -p 5000:80 -it --rm internetofwater/pygeoapi works out of the box just like Docker.


ReferenceError: atob is not defined

Hello,
I got the below error since  a couple of days: js2py.internals.simplex.JsException: ReferenceError: atob is not defined
File "/home/maxx/.local/lib/python3.6/site-packages/js2py/base.py", line 1074, in get
return self.prototype.get(prop, throw)
File "/home/maxx/.local/lib/python3.6/site-packages/js2py/base.py", line 1079, in get
raise MakeError('ReferenceError', '%s is not defined' % prop)
js2py.internals.simplex.JsException: ReferenceError: atob is not defined
Anyone is experiencing the same ?
Thank you!

same me

Hello,
issue has been fixed by @VeNoMouS here: https://github.com/Anorov/cloudflare-scrape/issues/215


Add file extensions

Also ensure that only the zig filetype plugin is loaded
when opening a zig source file.

Isn't this what ftdetect/zig.vim is for? Or is this another thing?

It's different.
http://vimdoc.sourceforge.net/htmldoc/options.html#'suffixesadd'

thanks!


Test eu

@henrycpainter while I appreciate the PR, unfortunately it won't work if merged since the repo itself has no access to secrets needed for interacting with github and datadog API. Closing the PR for now but will follow-up in the future once we have a workaround for the above issue.

Cool cool, note the GitHub token is a freebie secret in any repo - so the solve should just be around datadog.


chore(ci): Aggregate lint-staged in top package.json

Summary
Changes
In this PR the suggested aggregation of the lint-staged configuration into the top package.json is implemented. Closes #2312
Issue number: #2312

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Hey @daschaa, nice to see you again!
Thank you for opening this PR! Going to merge it as soon as the CI completes.
--
Also, ignore the comment about the missing issue that another automation left. It was triggered by mistake due to a formatting issue.

If possible, could I please ask you to leave a comment under the original issue, so that I can assign it to you? It's just for tracking purposes and GitHub doesn't let me assign it to users that have not interacted with it.

Hey Andrea, thanks for the fast review, really appreciate it! :)
I'll comment under the original issue :)


How the view  autoplay

How the view  autoplay？
I have a need to let the view be played automatically

still a handy feature to have.. in the meantime you could use something like panoViewer.lookAt({ yaw: panoViewer.getYaw()+1000}, 2000000);


Fix workflow

Apparently, there was an error on the yml file for the allowed-conclusions input

Apparently, there was an error on the yml file for the allowed-conclusions input

Cool, feel free to merge

Cool, feel free to merge

I should probably amend https://github.com/lewagon/wait-on-check-action/pull/20/files#diff-1243c5424efaaa19bd8e813c5e6f6da46316e63761421b3e5f5c8ced9a36e6b6R32 on my pr to match, right? i.e no quotes.
My editor (VSCode, with Red Hat YAML plugin) is complaining that this line is even an array, saying it should be a string.. I am assuming that is an issue my end, but I don't have intellisense on this.

I should probably amend https://github.com/lewagon/wait-on-check-action/pull/20/files#diff-1243c5424efaaa19bd8e813c5e6f6da46316e63761421b3e5f5c8ced9a36e6b6R32 on my pr to match, right? i.e no quotes.
My editor (VSCode, with Red Hat YAML plugin) is complaining that this line is even an array, saying it should be a string.. I am assuming that is an issue my end, but I don't have intellisense on this.

Don't merge this PR. Is still not solving the issue. Check at my comment on the other PR

Don't merge this PR. Is still not solving the issue. Check at my comment on the other PR


crowdsec: 1.6.1 -> 1.6.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/crowdsecurity/crowdsec/releases.
meta.description for crowdsec is: CrowdSec is a free, open-source and collaborative IPS
meta.homepage for crowdsec is: https://crowdsec.net/
meta.changelog for crowdsec is: https://github.com/crowdsecurity/crowdsec/releases/tag/v1.6.2
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.2 with grep in /nix/store/xk3v73354pc8w92nyz1rs902mcdvzjpj-crowdsec-1.6.2
found 1.6.2 in filename of file in /nix/store/xk3v73354pc8w92nyz1rs902mcdvzjpj-crowdsec-1.6.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

crowdsec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xk3v73354pc8w92nyz1rs902mcdvzjpj-crowdsec-1.6.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A crowdsec https://github.com/r-ryantm/nixpkgs/archive/1f5c2993a55d8b00f8ac000fd23ae955bf33431e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1f5c2993a55d8b00f8ac000fd23ae955bf33431e#crowdsec

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xk3v73354pc8w92nyz1rs902mcdvzjpj-crowdsec-1.6.2
ls -la /nix/store/xk3v73354pc8w92nyz1rs902mcdvzjpj-crowdsec-1.6.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

crowdsec

Maintainer pings
cc @06kellyjac @urandom2 for testing.

hash mismatch on aarch64-darwin
@ofborg build crowdsec


Can't move accessories from two hubs into two different rooms

I have two harmony hubs which i use in two different rooms. However, all the activities appear in one room on my iPhone. When I move one activity from one room, it moves them all leaving no Harmony activities in the original room. Any ideas how to fix?
Thanks in advance!

David

Did you check the name you set ? I lll try to make some changes on the serial number of the accessory / platform properties and will keep you informed .

Hi again, I checked and by declaring a config like the following, I can have on platform (with all activities) in one room and another one in another.
"platforms": [
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Nico HarmonyHub Salon DEV",
        "hubIP": "<IP_ADDRESS>",
        "showTurnOffActivity" : true,
        "TurnOffActivityName" : "HC Off",
        "DEVMODE" : true

    },
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Nico HarmonyHub Salon DEV 2",
        "hubIP": "<IP_ADDRESS>",
        "showTurnOffActivity" : true,
        "TurnOffActivityName" : "HC Off",
        "DEVMODE" : true

    }
]

That seems to have fixed it, which is wild because my original set up
wasn't that different from yours. The new working platform settings are is
as follows:
"platforms": [
{

    "platform": "HarmonyHub",

    "name": "BedRoomHarmonyHub",

    "hubIP": "<IP_ADDRESS>",

    "showTurnOffActivity" : true,

    "TurnOffActivityName" : "HC Off",

    "DEVMODE" : true

},

{

    "platform": "HarmonyHub",

    "name": "LivingRoomHarmonyHub",

    "hubIP": "<IP_ADDRESS>",

    "showTurnOffActivity" : true,

    "TurnOffActivityName" : "HC Off",

    "DEVMODE" : true

}

]
My original configuration that wasn't working as follows:
"platforms": [
{

    "platform": "HarmonyHub",

    "name": "BedRoomHarmonyHub",

    "hubIP": "<IP_ADDRESS>"

},

{

    "platform": "HarmonyHub",

    "name": "LivingRoomHarmonyHub",

    "hubIP": "<IP_ADDRESS>"

}

]
FYI, I am not running the latest Harmony Hub firmware--I'm on 4.15.206 on
my living room hub and I'm too lazy to check my bedroom hub, but its
probably that version or older.
Thanks for your help! I will play around with it and let you know how I
make out!

David

On Fri, Dec 28, 2018 at 11:57 AM Nicolas Dujardin<EMAIL_ADDRESS>wrote:

Hi again, I checked and by declaring a config like the following, I can
have on platform (with all activities) in one room and another one in
another.
"platforms": [
{
"platform": "HarmonyHubWebSocket",
"name": "Nico HarmonyHub Salon DEV",
"hubIP": "<IP_ADDRESS>",
"showTurnOffActivity" : true,
"TurnOffActivityName" : "HC Off",
"DEVMODE" : true
},
{
    "platform": "HarmonyHubWebSocket",
    "name": "Nico HarmonyHub Salon DEV 2",
    "hubIP": "<IP_ADDRESS>",
    "showTurnOffActivity" : true,
    "TurnOffActivityName" : "HC Off",
    "DEVMODE" : true

}

]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nicoduj/homebridge-harmony/issues/6#issuecomment-450409726,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AsCB32kBnD1BD-vPOz0ghBPiUFAvO48tks5u9mmNgaJpZM4ZiIOm
.

Hi, be aware that devmode will rename your activities , prefixing them with « DEV ». I had this hidden switch to run a dev homebridge server for debugging purpose and don’t mix my activities with my « production » server. You should  set it to false if you want to have the real name of your activities (even if you can rename them in home app)

Thanks for the advice! I'll do that!

David

On Sat, Dec 29, 2018 at 5:07 AM Nicolas Dujardin<EMAIL_ADDRESS>wrote:

Hi, be aware that devmode will rename your activities , prefixing them
with « DEV ». I had this hidden switch to run a dev homebridge server for
debugging purpose and don’t mix my activities with my « production »
server. You should set it to false if you want to have the real name of
your activities (even if you can rename them in home app)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nicoduj/homebridge-harmony/issues/6#issuecomment-450488368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AsCB33YOt_keT34JBz5F5_XY_I-hdc9dks5u91sZgaJpZM4ZiIOm
.


Fix crash on release versions after AGP 7.3 bump

Summary
Release versions are currently broken on main. This happened once we bumped the AGP version to 7.3. It seems like that the path we used to use for assets has changed.
The app build successfully but it fails to start as it can't load the bundle.
This is also causing the hermes e2e test to fail: https://github.com/facebook/hermes/pull/821
Changelog
[Android] [Fixed] - Fix crash on release versions after AGP 7.3 bump
Test Plan
Tested this locally and it works fine with RN Tester (can run a release version of it).
Plus, inspecting the zip:
Before
$ unzip -l packages/rn-tester/android/app/build/outputs/apk/hermes/release/app-hermes-arm64-v8a-release.apk | grep android.bundle
  1248608  01-01-1981 01:01   assets/mergeHermesReleaseAssets/RNTesterApp.android.bundle

After
$ unzip -l packages/rn-tester/android/app/build/outputs/apk/hermes/release/app-hermes-arm64-v8a-release.apk | grep android.bundle
  1248608  01-01-1981 01:01   assets/RNTesterApp.android.bundle

Thanks for this. I updated from 7.2.1 to 7.3.1 and ran into this. React Native 0.70.3 still does not have this patch included so for now used patch-package to make it work.

Thanks for this. I updated from 7.2.1 to 7.3.1 and ran into this. React Native 0.70.3 still does not have this patch included so for now used patch-package to make it work.

I would highly encourage you to don't use patch-package. What's the reason why you bumped AGP to 7.3?

I thought it was needed due to a library that I included that relies on the newest kotlin version. Android Studio complained that it requires a more recent version of the gradle plugin.

I thought it was needed due to a library that I included that relies on the newest kotlin version. Android Studio complained that it requires a more recent version of the gradle plugin.

Nope it's not. Android Studio is really eager in asking you to always update AGP, resulting in actually breaking your project sadly :/ I'm investigating if we can turn off those dialogs for React Native projects by hiding the AGP version.

i got this issue this week, I upgraded RN to 0.70.7 and set buildToolsVersion to 33 because I make postnotifications permission requests for Android 13.
When I build, there is a strong warning that suggests I update Gradle to a version higher than 7.2.1, so i set 7.3.1
Then the app will crash when opening either AAB or APK.
My temporary solution is downgrade to 7.2.1

i got this issue this week, I upgraded RN to 0.70.7 and set buildToolsVersion to 33 because I make postnotifications permission requests for Android 13. When I build, there is a strong warning that suggests I update Gradle to a version higher than 7.2.1, so i set 7.3.1 Then the app will crash when opening either AAB or APK.
My temporary solution is to downgrade to 7.2.1

Or you can update React Native to 0.71 which has support for this out of the box

My app is a bare expo and the SDK version is currently 47. maybe I need to hold it until I upgrade to SDK 48.


How to check FLOPs

Hello! Thank you for your hard work.
The paper includes calculations of FLOPs in a table, but upon reviewing the code, it's challenging to locate where FLOPs are measured.
Could you possibly tell me where it is measured?"

Thanks for your attention!
We upload the code for calculations of FLOPs.
You can use `PYTHONPATH="$(dirname $0)/..":$PYTHONPATH python benchmark.py --config local_configs.NYUDepthv2.DFormer_Large' to calculate the Flops and Params.

Thank you!!


Game.ini - Server Password

Pass values if present so if game.ini is auto-downloaded due to server crash/delete it is still working as expected on restart.
Needed values to add for start params:
bServerPassword=
ServerPassword=""

Enabled in Server Start Param on the server in WindowsGSM
To enable add the following to the Server Start Param
bServerPassword=false;ServerPassword="password"
Each item must be separated with a semicolon (;)


CMake: Export include directory in package config file

Fixes: #854

Thanks again!
But does anything needs to be modified here or will it somehow work automatically?

target_include_directories(SOCI::soci_core PUBLIC ...) tells CMake that SOCI::soci_core and anything that uses SOCI::soci_core that it needs to use the correct include directory. Calling target_link_libraries(connect PRIVATE SOCI::soci_core) will automatically bring in the include directory. This is part of modern CMake's usage requirements system. In short, your example will "just work" as it is with no modification.

Give it a try and see :)

Thanks again, this indeed works like magic. Curious that CMake uses -isystem rather than -I for the include directory, but it's a separate matter entirely, of course.


Network pools

This factors the vlan allocation stuff out into extensions that are pluggable; we can use something else for rHaaS (probably create a network upstream and use the name of the network).
Some of the driver related tests have been half-heartedly forced into place; next up is the switch refactoring, which will replace large parts of those anyway, and  mesh better with this.

This builds on top of #441, so it's even bigger.

Thanks for your great work!
One slight modification to the syntax to consider would be specifying the plugin in the section name instead of a special [extensions] section. I don't think it would affect the current code too much, and would have a few advantages:

Determining which config section pertains to which plugin would be really easy. In the current model, the user would need to look up somewhere out of band the section name that pertains to a given plugin.

It avoids namespace collisions. Say two people wrote cisco device drivers (say the python modules were zenhack.cisco and henn.cisco), but both named the the config sections something more generic (like "cisco").

It allows a module to be used twice without having a config name conflict (assuming it's designed for that). Perhaps one of the options for a cisco driver were the IP address of the router. Being able to configure the section twice would allow me to create 2 instances.

An example of this new method would be:
[ext:haas.ext.network.cisco5500]
ip = <IP_ADDRESS>
username = admin
password = admin

[ext:haas.ext.auth.openstack]
keystone_ip = <IP_ADDRESS>

superseded by #455, closing.

@henn, I feel like we talked about this when the design was being proposed.

(I'd forgotten to document this, #455 is updated with the changes now) The strategy here is that we just config section that's the same as the extension module.

same response as (1); this could only happen if the extensions were in violation of that convention.

It is in fact not designed for that. #455 moves switch objects to the database, not the config file.

Let's move any further discussion on this to #455.


ReferenceError: Can't find variable: safari

On Safari 10.0.1/macOS 10.12.1, I get the following error:
ReferenceError: Can't find variable: safari          bridge.js:12

Where bridge.js:12 is:
safari.self.addEventListener("message", function(e) {

I'm going to optimistically close this on the basis that things have changed quite a bit. Please re-open if this is still a problem with 1.1b4.


Search is broken

Currently, the search is broken:
https://disclose.io/programs/
I'm seeing the following error in the console:
An error has occurred.                                                programs-datatable-standalone.html:273

Fixed https://github.com/disclose/diodb/commit/a66a65865a577ce9c9f30a4f8ced659ca2ceb6a7

There was an actual merge conflict merged, all sorted.


add answers to exercise 1-6 chapter 8

Hi, @axel22
Pls see my changes

Nice!
Please address my comments, and I will merge this in.

Thanks for the reply, I'll try to fix

@axel22,
pls see my changes

Thanks! I left a couple of minor comments.

Hi, @axel22
Thanks for you recommendation,
Maybe I should use the Akka persistence (http://doc.akka.io/docs/akka/current/scala/persistence.html) in exercise 2 ?

No, if actors can arbitrarily fail, the only thing you can do is to implement a consensus algorithm and replicate the state of all the bank accounts across multiple actors.
That exercise is meant as a thought experiment to convince yourself of how hard this problem actually is.

LGTM! Thanks a lot!

Thanks !!!


Fixes #739: can not compile empty list of words

reason: unchecked array bound

Thanks for the PR, but it seems to me the case WORDS earlier shouldv've caught this, no?

IIRC not when WORDS is the final token.
These are strange cases anyway... for example:
<[
]>
alert!

I just discovered this -- it fails at AST step.
Sure, in theory you should have that compile to [] but why bother?

Because people are going to expect x = <[]> to work.


Improve support for Swift / SwiftUI

Have a look at this article: https://www.hackingwithswift.com/quick-start/swiftui/how-to-use-dynamic-type-with-a-custom-font
In particular, we might define either decide to keep our hardcoded size matrix, or to use the UIFontMetrics scaling methods to automatically derive font sizes based on style (available with iOS 11).
Moreover, we might need to create extensions for proper resizing support with SwiftUI.

Support for SwiftUI has been improved in iOS 14 (see link mentioned above).
To improve type inference, I also removed support for standard system text styles. This does not make much sense since we want to enforce specific sizes consistently and AFAIK we don't use standard system sizes anywhere. Simpler is better.
This also removes the need for font descriptor caching.
If we really find later that supporting standard system sizes is a good idea, we can restore the code I removed and add new constants to SRGAppearanceFontTextStyle for the system sizes, e.g. SRGAppearanceFontTextStyleSystemBody, with the usual UIFontTextStyle system values.
This change has been made on the feature/swift-improvements branch.

A small improvement will be delivered in 3.0.0, but we should really adopt UIFontMetrics correctly. This has been moved to another issue #4.