Host pool stuck in not initialized mode while all hosts are OPTIMAL

Environment info

NooBaa Version: 5.2
Platform: OpenShift 3.11
CC: @nb-ohad

Actual behavior

After restarting the services, perhaps while pool_server was handling the host pool scale, the _init function of pool_server bails because all hosts are already running and optimal, and it does not fix the initialized flag on the pool.

Expected behavior

Should fix the initialized state when all hosts are OPTIMAL.

Steps to reproduce

Restart the server soon after creating a host pool, while it waits for the hosts to start.

More information - Screenshots / Logs / Other output

I fixed it manually by replacing this line:
https://github.com/noobaa/noobaa-core/blob/15cd9a82871dc2b0813d4cf1112ebc656174977c/src/server/system_services/pool_server.js#L91
with:
if (actual_host_count === configured_host_count && pool.hosts_pool_info.initialized) {

@nb-ohad Can we push this as a quick fix? is it safe?


How to disable encryption

Is there any config to disable encrypted request or disable encryption totally?

You should implement TrustOptionsStoreInterface and tag it with lightsaml.trust_options_store. In it's implementation you will provide TrustOptions with encryptAssertions = false for all or specific entityID


Have to set interface properties to null to implement

This is invalid code because Dart requires MyInterface.foo to be initialized even though its abstract.
abstract class MyInterface {
  final String foo;
}

class MyClass implements MyInterface {
  final String foo;

  MyClass(this.foo);
}

This is invalid code because MyClass doesn't have a setter for MyInterface.foo
abstract class MyInterface {
 String foo;  // remove final
}

class MyClass implements MyInterface {
  final String foo;

  MyClass(this.foo);
}

This is valid code but it is confusing and ugly.
abstract class MyInterface {
 final String foo = null;  // add back final, add set to null
}

class MyClass implements MyInterface {
  final String foo;

  MyClass(this.foo);
}

What about
abstract class MyInterface {
  String get foo;
}

That does work but it's not obvious to me that a getter can be done with a final but a final cannot be done with a getter or a final. I'll defer to others to decide if this warrants a change.
My personal opinion is that the implementation should be able to match the abstract interface exactly to improve clarity.
Glad to know that the getter works, though! :)

Sounds like https://github.com/dart-lang/language/issues/45

It is indeed dart-lang/language#45.
The problem you run into here is that a final field must be initialized, either with an initializer expression or by all generative constructors.
The final field foo in your abstract MyInterface class is not initialized, so your program has an error.
It doesn't matter that you won't ever use the class for anything other than its interface, the rule is strict.
If someone somewhere decided to extend your abstract class, they would not be able to get the field initialized.
That's why changing the field to be non-final, initializing it or changing it to a getter signature all work, the class no longer contains an uninitialized final field. Using a getter signature is the recommended solution.
We could change rules to make this easier. The largest impact change would be to change grammar for property getters/setters and allow you to write something like:
abstract class MyInterface {
  String foo { get; }
}

It's still further from an abstract field.
Another option is to reintroduce the interface keyword, which would make it clear that it is not a class that can be extended, so the field must be abstract:
interface MyInterface {
  final String foo;
}

Another option is to allow abstract on a field declaration to mark it abstract (for all other members you can omit the body, but there is no body for a field to omit).
abstract class MyInterface {
  abstract final String foo;
}

Or, maybe we can say that having a non-initialized field is only an error for concrete (non-abstract) classes. Since MyInterface is abstract, it's allowed to have a non-initialized final field, but any concrete class extending it will be an error. It makes it easier to forget initializing a field in a class intended as an abstract superclass, but I guess proper testing would catch that.
That rule would have no other reason to exist than to allow abstract classes to be used only for their interfaces, but it can then be used to prevent extending the class (which isn't new, you could already just omit having a public generative constructor).
Currently, all you can do is use the getter.

I personally like how dart has implicit interfaces. I cannot provide a good reason why, it just seems cleaner. But my understanding is that abstract classes cannot use a constructor and thus there would be no way to actually initialize a final property. For that reason I just assumed that I could write my abstract classes like a blueprint, like a pre-paste copy-paste, with finals etc and consume it as an interface without issues.
Is there a scenario I am missing where an abstract class will initialize a final property?
Cheers

Besides a personal obsession with the idea of an abstract class as an interface working like a copy-paste, using the getter does make sense and does seem reasonable. It feels quite Darty.

Abstract classes can have a constructor. You can't call it if you use it as interface though.
Otherwise you invoke it with super() in the sub class.

Whoops. Yeah, I am a little embarrassed that I missed that.

One advantage of implicit interfaces is that it has low "migration cost". If you start something out as an "interface" (a fully abstract class), and you then decide to provide a default implementation for some functions, you can just do that in the same class. You don't have to invent a new class.
Having two ways to do the same thing, one simple and limited, and one complex and powerful, can indirectly drive API designs to stay within the limited capabilities of the simple approach rather than risk the cost of having to convert everything to the more complex design.
This is one place where our enum classes fail. Dart enums are very simplistic. If you want more than that, then you have to rewrite everything to a normal class where you declare each constant manually, even if it's only to add one method to every value. The Java enum feature allows organically adding more features to an initially simple syntax without forcing a sudden and expensive migration. That is why it is better, not just because it's more powerful (it's no more powerful than full classes anyway), but because it can evolve better.

@zoechi the value of those dev tools cannot be understated. That's basically all TypeScript is, one massive autocomplete engine, and it's incredibly successful. Improving dx is important to me because it improves productivity and thus the value of the language.


Add Dependabot to fix vulnerable dependencies

Dependabot security updates make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a Dependabot alert is raised for a vulnerable dependency in the dependency graph of your repository, Dependabot automatically tries to fix it.
Supported repos and ecosystems

@yolken-segment what do you think about adding Dependabot?

Yup, sounds good. I temporarily lost admin access to this repo, but when I get it back I'll merge your change. Thanks!

@yolken Do you know someone else who can merge this? Is there any ETA when will you get the access back?

@jadametz CC

@yolken I'll add some of the new Kafka / Data Infra team. Will ping them and ask who should handle these kinds of requests. Thanks for letting us know about this.

Looking this one over I don't see any issues with it, so I'm going to just merge.  But we'll need a plan for the future for handling contributions and maintenance.


Redis image is hardcoded

in the operator definition the redis image is hardcoded to k8s.gcr.io/redis:v1
As we are using the operator also in disconnected/restricted environments, this will not work.
Please update this reference so it can be used in an olm disconnected environment (for example make it possible to use ImageContentSourcePolicy - in other words an image digest should be used instead of a tag)

Not sure how the disconnected envs work, but could you just update the spec here?
https://github.com/cloud-bulldozer/benchmark-operator/blob/master/resources/operator.yaml#L64-L76

Well when using the OLM (operator lifecycle manager) in OKD/OpenShift/K8S you are using the images available via the operatorhub catalog (https://operatorhub.io/operator/ripsaw). We cannot override the images baked in the images themselves. the only way of overriding is via the ImageContentSourcePolicy object where you can define the mirror "offline" registry. As the ImageContentSourcePolicy object only overrides images referencing the digest (direct sha:x reference) we cannot use it with the one on the benchmark-operator.
More info on OLM: https://docs.openshift.com/container-platform/4.6/operators/understanding/olm/olm-understanding-olm.html
More info about OLM in restricted networks: https://docs.openshift.com/container-platform/4.6/operators/admin/olm-restricted-networks.html
Important snippet I am referring to:
| While OLM can manage Operators from local sources, the ability for a given Operator to run successfully in a restricted network still depends on the Operator itself. The Operator must:List any related images, or other container images that the Operator might require to perform their functions, in the relatedImages parameter of its ClusterServiceVersion (CSV) object.Reference all specified images by a digest (SHA) and not by a tag.See the following Red Hat Knowledgebase Article for a list of Red Hat Operators that support running in disconnected mode:https://access.redhat.com/articles/4740011
-- | --

Maybe you can help with a patch to further explain what you are looking for?


Deprecate npm package

Marking the package deprecated in the NPM registry will help increase visibility of the deprecation. Can the owner of this repository please run:
npm deprecate ember-cli-qunit "Use ember-qunit directly instead."

This deprecation is already mentioned in the README.

NOTE: This addon has been deprecated! Please use ember-qunit directly instead.

done ✅


onyo new --template <path> does not work with absolute path

onyo new --template expects just the template name, or alternatively the absolute path.
❱ onyo new --keys directory=shelf --template /Users/tkadelka/onyo/.onyo/templates/laptop.example
The following will be created:
+/Users/tkadelka/onyo/shelf
---
[....... rest of git diff ........]

❱ onyo new --keys directory=shelf --template .onyo/templates/laptop.example                                                   1 !
ERROR: Template .onyo/templates/laptop.example does not exist.

The relative path should work for --template too.

This feels weird, but Onyo allows it for addressing assets.
I assume we want to enforce that it must be a template in the same Onyo repository? Or do we want to allow using templates from anywhere on the FS?

Or do we want to allow using templates from anywhere on the FS?

I personally think we want to allow templates (and tsv tables) from anywhere.
Obviously in our use-cases we would prefer to have them added to the inventory repository. But since we verify newly created assets independently from their templates (and they are afterwards fully detached from them), I would not see why we would actively disallow specifying a path outside the inventory for this.
Possible use cases:

Using a template I don't want to share with the group from my home dir
Using a template from another inventory system (i.e. laptops from FZJ vs. HHU)

Possible solution: If relative path is given, first check for existence of TEMPLATE_DIR / path and only failing that resolve based on CWD.
Gives a bit of a strange corner case when both exist, but I currently think it's OK.


Consolidated table of the manually annotated disease-LSF relations in LSD600

Greetings, I'm reviewing the preprint LSD600: the first corpus of biomedical abstracts annotated with lifestyle–disease relations. I am excited to look at the 1900 disease to lifestyle factor relationships as per:

The 600 abstracts that make up the corpus were randomly partitioned on the document-level into a training set (60%), a development set (20%), and a held-out test set (20%). The corpus contains a total of 1900 manually annotated relations, which are distributed over eight relation types that are organized into a hierarchy.

From the Zenodo, I downloaded LSD600.tar.gz and began looking at the .txt files with abstracts and .ann files that appear to be BRAT standoff format containing annotated named entities and relations.
Many of the early .ann files only contained entities and no relationships, but I stumbled upon 34621627.ann containing both. Snippet below:
T1	Disease 13 26	Skin Diseases
T16	Lifestyle_factor 2167 2172	shift
T17	Disease 2198 2211	skin diseases
T18	Lifestyle_factor 1905 1908	PPE
T25	Disease 248 269	occupational diseases
T31	Out-of-scope 438 441	may
T32	Lifestyle_factor 1881 1897	safety trainings
R1	negative_statistical_association Arg1:T18 Arg2:T13
T35	Lifestyle_factor 2135 2150	safety training
R6	negative_statistical_association Arg1:T35 Arg2:T17
T36	Lifestyle_factor 2307 2313	gloves
R7	Prevents Arg1:T19 Arg2:T17
R8	Prevents Arg1:T36 Arg2:T17

This preamble is for orientation and to demonstrate that's its not easy for the reader to manually inspect all 1900 relations.
My suggestion is to create a consolidated dataset with one record per manually curated relation across all 600 abstracts. This would not replace the txt/ann files but be a useful access point for users to immediately inspect the data. Suggested fields are:

disease entity
LSF entity
relationship type
abstract/pubmed ID
abstract's dev/train/test category
disease BRAT id, e.g. T1
LSF BRAT id
entity span boundaries
text span containing both entities, if feasible

JSON, TSV, or excel would all make a reasonable format choice for this. Column names are greatly appreciated!
This would help me get a much better appreciation for the types and quality of relationships annotated by LSD600.

Just wanted to note that Figure 1 is a nice graphical representation of these relationships

The dataset would offer more fields and access to all 1900 relations.

Thank you for your valuable feedback and for reviewing the LSD600 preprint!
I’m pleased to inform you that the metadata file you requested is now available. It includes a comprehensive table of all 600 abstracts in the LSD600 corpus with the following columns:

Publication ID
Article Title
Journal Name
Publication Year
Data Set (Dev/Train/Test Category)
Lifestyle Factor Count
Disease Count
Relations Count
Abstract Text

You can access the file here:
🔗 LSD600 Metadata File

Thank you for your valuable input!
The requested table is now available. You can download it from the following link:
🔗 Consolidated Relations Dataset
The table includes the following columns:

Disease Entity
LSF Entity
Relationship Type
Publication ID
Category (Train/Dev/Test)
Disease BRAT ID
LSF BRAT ID
Disease Entity Span
LSF Entity Span
Abstract Text

Feel free to reach out if you have any further suggestions or questions. Thanks again for your support!

Thanks @EsmaeilNourani. Very helpful.
I see the data was added in https://github.com/EsmaeilNourani/LSF_Disease_RE/commit/9895a5e0ffc6d2eddc349204750fc702a95790da. Would it make sense to also commit the code that generates this data?

The contents of Consolidated_Relations_Dataset.tsv look good to me. Nicely executed.
It would be ideal to archive this table in the Zenodo deposit so it lives with the rest of the data release.
Once code is available to generate this dataset and the data is on Zenodo, I will close this issue to denote that the request has been resolved. Same applies to https://github.com/EsmaeilNourani/lifestylefactors-annotation-docs/issues/2.

FYI the full text of my review is online here. Thanks for posting a preprint such that it is possible for me to immediately share my review. Cheers.

Consolidated_Relations_Dataset.tsv is on the Zenodo and the contents look good. The code to generate is at helpers/create_consolidated_relations.py. Thanks @EsmaeilNourani


filter/flipX.js modification and bug fix in kind.js

-wrote method for flipX which flips the image on the horizontal axis based on the data array instead of the getpixel() methods
-fixed bug in kind.js s.t. CMYK's alpha = 0 and CMYKA's alpha = 1

Coverage decreased (-0.08%) to 85.857% when pulling 4d0846953e29dcee574e7df4d37657957248f074 on flip into 2f6f0da085e8aa2a8b2556d8ab56e5d4d0e4fbca on master.

Thank you!


Close versus terminate

Description
I would like to know the difference between Pool.close() and Pool.terminate. The documentation has the following to say:
close() → None
Close the pool to new visitors.

terminate() → None
No running by the pool!

Which is unclear. I thought close would prevent new tasks from being applied, and terminate would stop all currently running tasks, but that doesn't seem to be the case.

This could definitely stand to have better documentation. pool.close() prevents queueing new tasks, and queues commands to the child processes so that they can gracefully stop once the work queue is exhausted, and you can await pool.join() to wait for them to finish. `pool.terminate() will immediately terminate (kill -9) those workers, leaving the work queue unfinished, and any pending jobs will be stuck waiting for results, so it should only be used when the service managing the pool must exit immediately without waiting for any in-flight tasks/results.


Fix/support padding and spacing

Add support for Padding and Spacing.
this was tested using one of the Kenny tiny battle tile sets, I modified it to add padding.
Along the way, It was beneficial to change to using the LDTK tileIds over the calculated ones.
ldtkgridtile.t, according to https://ldtk.io/json/#ldtk-Tile, is the tile id.

i <3 the get it guy


New mocha reporter

Pretty simple change but the diff seems a little confused by some whitespace/reformatting changes. I made a new mocha reporter here https://github.com/danquirk/mocha-fivemat-progress-reporter that will report test output by test suite with a progress bar instead of one giant set of dots. This turns it on by default for jake runtests
Note that after merging this everyone will be required to run npm install again to get the new reporter.
The final output when tests complete is unchanged, total time and a final list of aggregated failures are still reported.
Ex:

@DanielRosenwasser mentioned he might miss his red dots as some crazy means of figuring out which test failed. We could turn the progress bar red as soon as a failure occurs:

Alternatively/in addition we can just print test names immediately upon failure:

Yes, :+1: for crazy red loading bars.

I'd prefer a red dot showing an error happened.  Then just print the errors at the end.  Having hte errors interspersed with progress info will just make investigation annoying.

The final output is unchanged either way so you will always have the errors at the end in the way you're accustomed to with today's reporters. The interspersed name would allow you to immediately note a failure and start investigating while the rest of the tests continue.

Made both of the changes in my first reply.


Host debian package of framework somewhere

This is needed for testing installation of subpackages, example of failure:

Does cloudsmith solve this use case @jbbjarnason  ?

closed in favor of https://github.com/Skaginn3x/framework/pull/147
might still need to document how to add the repo on any debian based distro


Versioned plugin dir without -0 revision is not selected when -0 is requested.

Given the following plugins in the plugin directory:
A-1.0.0
A-1.0.0-1

the plugin A-1.0.0 is not chosen if roddy is called with --usePluginVersion=A:1.0.0-0. This counter intuitive, because the revision-free plugin is otherwise treated as ordinary -0 version, e.g. when compatibility between versions in concerned.

Update: Not only this special-case is broken, but the whole upgrading mechanism is broken. That is, when there is
A_1.0.0-0
A_1.0.0-1

then when requesting --usePluginVersion=A:1.0.0 none of the plugins is chosen.
This is related to issue #94.


Allow PyTorch 2.0

Description of changes: Updates requirements file, and test workflow to run on PyTorch 2.0
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

The requirement on TODO is holding the torch version back in the test workflow. Through:

https://github.com/awslabs/gluonts/blob/dev/.github/workflows/tests-torch.yml#L30
https://github.com/awslabs/gluonts/blob/dev/requirements/requirements-extras-cpflows.txt
https://github.com/KelvinKan/CP-Flow/blob/package-specific-version/requirements.txt#L16

Also holds other stuff back, like Pandas. We need to solve this somehow.

It seems that one test is failing, i.e. test/ext/statsforecast/test_statsforecast.py::test_model_config. Can we check it?

The test issue seems to be related to other dependencies, likely nothing to do with this PR.

The failure is related to https://github.com/plotly/dash/issues/2460


[Bug report] Hive catalog: table comment or column comment has garbled Chinese character

Version
main branch
Describe what's wrong

Error message and/or stacktrace
N/A
How to reproduce

Create a hive catalog, the properties as following:

db properties:

Update table comment
request body:

{
  "updates": [
    {
      "@type": "updateComment",
      "newComment": "数量"
    }
  ]
}

Add column comment
request body:

{
  "updates": [
    {
      "@type": "addColumn",
      "fieldName": [
        "amount6"
      ],
      "type": "string",
      "comment": "数量",
      "nullable": true
    }
  ]
}

Additional context
No response

I have figured it out, this isn't about Gravitino.
It is caused by the MySQL charSet of HMS you are using. you can try to alter the charSet in MySQL by:
alter table COLUMNS_V2 modify column COMMENT varchar(256) character set utf8;
alter table TABLE_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8;
alter table PARTITION_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8 ;
alter table PARTITION_KEYS modify column PKEY_COMMENT varchar(4000) character set utf8;
alter table INDEX_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8;

I have figured it out, this isn't about Gravitino.
It is caused by the MySQL charSet of HMS you are using. you can try to alter the charSet in MySQL by:
alter table COLUMNS_V2 modify column COMMENT varchar(256) character set utf8;
alter table TABLE_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8;
alter table PARTITION_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8 ;
alter table PARTITION_KEYS modify column PKEY_COMMENT varchar(4000) character set utf8;
alter table INDEX_PARAMS modify column PARAM_VALUE varchar(4000) character set utf8;

But this environment is using Postgres of HMS, do I need to alter the charSet in PG by the same command ?

I think so. It depends on the underlying DB's charset setting

Alter the charSet in MySQL by:
ALTER TABLE COLUMNS_V2 CONVERT TO CHARACTER SET utf8;
ALTER TABLE TABLE_PARAMS MODIFY PARAM_KEY varchar(256) CHARACTER SET utf8;

Then there's no garbled Chinese character.
Close this issue.


Do not allow unknown fields in validate

Fixes https://github.com/istio/istio/issues/24860
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@jasonwzm is there any easy way to do the full openapi schema validation? it may be hard since we don't have access to the CRDs?

@howardjohn Yes. I thought about adding openapi validation to istioctl analyze but I could not think of a perfect way of doing it. In many scenarios, users would like to validate/analyze just against static file and accessing to cluster is not a requirement, so we would not be able to get the true schema.

In response to a cherrypick label: new pull request created: #24868

In response to a cherrypick label: new pull request created: #24869


Video not preloading in iOS with preload="auto", it blinks the poster

Is there an existing issue for this?

[X] I have searched the existing issues

Which Mux Elements/Packages does this apply to? Select all that apply
mux-player-react
Which browsers are you using?
Safari on iOS
Which operating systems are you using?
iOS
Description
I'm using the mux-react-player to stream mux assets, we're using preload=auto to start loading the video asap no matter the case as the docs orientation, so the behavior when we click to play is smoother. We can see the assets being downloaded on all devices including the chunks, and we see the poster, as we click the poster is gone and the video starts playing.
But it seems this is not working for iOS Safari, in there even with preload="auto" the chunks are never downloaded (I was able to see it on the iOS simulator), we can see the poster but not the video in the behind, the poster blinks, we see a loader and then the download of chunks starts after we click play with an abrupt transition from poster to play, this is happening only on iOS devices and it's creating a broken experience as in some cases the chunk takes time to download and start, especially if the poster is not the first frame of the video this is more noticeable.

https://github.com/user-attachments/assets/dd7e991d-3670-4067-ba25-450984b98e6c
Reduced test case
https://codesandbox.io/p/sandbox/stoic-bessie-z7d3lr
Steps to reproduce

Open the video on any device and see how it loads and behaves
Open it in IOS, and you see that loads behave differently, no matter if we forced the preload
You can notice the poster blink and the load time as the chunks of the video are not preloaded
We're using v1 but I was able to see the same behavior on v2

Current Behavior
Preload is not actually preloading assets in IOS when we force preload="auto"
Expected Behavior
To download the assets when we force the preload="auto" for the player.
Errors
No response
What version of the package are you using?
v1.11.4

@lucasgdev thanks for the feedback! alas, this is not something we can change on our end.
iOS Safari controls this behavior to keep users from using too much internet or memory.
The behavior can also change based on if the phone is in energy saving mode or if the internet is via cellular.
there is possibly a workaround for iOS >=17 if you add the prefer-playback="mse" attribute.
This should enable the new Managed Media Source extensions which gives the player more control over the loading logic.


enable (or simplify) jupyter notebook raw view

I use vscode for coding, merging, debugging but not to evaluate jupyter or colab notebooks: that I keep in the browsers. And yet often - due to issues with portability between colab + jupyter + github on forked projects - I need to edit the notebook raw json code. It would be useful to have an easily accessible global switch to not start a server for jupyter.
This is probably possible, but it isn't obvious how to set that up. A simple setting, or documentation thereof, would be useful workflow addition.

Have you tried re-opening a notebook with a different editor? You can right-click on any file and select "Open With..." and select "Text Editor" to open the json:

You can also right-click on the tab and re-open from there:

@xvdp does Miguel's suggestion work for you?


Enable export of decoder of quantized models to be exported with pkv

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


GraphQL improvements

Verify response data in assert_bad_user_input
Format database errors to avoid SQL queries exposed to the client
Verify message formatting for non-existent resources
Format error raised from non-existent foreign key ID
Correctly handle field values that evaluate to False
Verify updateShipment handling of non-existent boxes
Verify updateShipment handling of non-existent location/product

 Implement GraphQL best practices


Syslog handler should support writing to /dev/log

A common use case of the syslog handler is running a program on a system which has a normal, local, syslog instance which may not be listening on any network ports.
The syslog hook should ideally allow defaulting or writing to the local /dev/log socket on unix-likes so program data can be collected locally and (potentialy) exported over the network.

PRs welcome :)

According to https://golang.org/src/log/syslog/syslog.go
While call  func Dial(network, raddr string, priority Priority, tag string)
if network  is empty, it will cal unixSyslog()( Try to connect "/dev/log", "/var/run/syslog", "/var/run/log" )
So while I want to make syslog hook writing to the local , I just use hook as
hook, err := logrus_syslog.NewSyslogHook("", "", syslog.LOG_DEBUG, TAG)

Is it what @wrouesnel want ?

Sounds right and plays nicely with flag args too. I wound up hard coding /dev/log previously so I guess this just need to be mentioned in the docs.
On 9 September 2015 12:24:01 am AEST, Owen<EMAIL_ADDRESS>wrote:

According to https://golang.org/src/log/syslog/syslog.go
While call  func Dial(network, raddr string, priority Priority, tag string)
if network  is empty, it will cal unixSyslog()( Try to connect
"/dev/log", "/var/run/syslog", "/var/run/log" )
So while I want to make syslog hook writing to the local , I just use
hook as
hook, err := logrus_syslog.NewSyslogHook("", "", syslog.LOG_DEBUG, TAG)

Is it what @wrouesnel want ?

Reply to this email directly or view it on GitHub:
https://github.com/Sirupsen/logrus/issues/211#issuecomment-138578947

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Any of you mind sending a PR?

I will be glad to send a PR today.


An unexpected error has occurred.

on live website 'hyper.is' when click the logo (left top) got 'An unexpected error has occurred' in Firefox browser.
<a class="jsx-2327597585 logo" href="/">

Cannot reproduce, feel free to comment or open a new issue if you still see this error.


Syngas does not go in buckets

You cannot pick up syngas with a bucket, making it impossible to move around and use it's explosive property like shown in the video without other mods.
I'm running a lightweight personal modpack and I don't want to add any of the other big, usual mods, so being able to move it in a bucket would be nice.
Meanwhile, is there any small mod that allows you to move that fuel around? The video in the syngas page shows you moving it with some sort of canister, but I don't know what mod adds that.

The mod has been recently updated to MC 1.16, older versions are no longer supported.
I'm mass closing older issues to clear up clutter in the bug tracker.
If you find this issue still exists in the current version feel free to reopen it.


Generating a CSS file from the Midnight Lizard config?

Heyo,
As the title says, is it possible to generate a single (or multiple) CSS files from the config?

at least it is possible to copy main colors from the css variables that are injected to each processed web page


Fix: find mmdc binary universally

I was having an issue with missing output svg - it turned out this was because of yarn workspaces installing mmdc in a different location.
I've tested this with yarn workspaces and pnpm workspaces on macOS.
This could be related to #28

Looks like the builder is wanting this to be made type safe first. It thinks your path lookup could be null.

This path to the needed node_modules dependencies keeps coming up. I’m thinking this might work better to give the generator the ability to control this path as a parameter. Looking at this I’m not sure where others are installing and calling npx prisma generate.

Closing this PR and moving suggestion into #40


fix : Passthrough logic inside hardReset()

A small change to read the Passthrough checkbox state directly inside of hardReset(). This is to avoid issuing a reset on passthrough boards (M4 + ESP coprocessor).
This was tested locally, but I believe by forcing a read of the passthrough checkbox the web hosted code will also work.
Hardware successfully tested with this update:
Feather V2
PyPortal
Low risk level of making things worse. The Webserial_ESPTool has not worked in passthrough mode since August 2024.

oops, minor formatting issue

I did a shift-reload on the deployed page, but I'm still getting:
ESP Web Flasher loaded.
Connecting...
Connected successfully.
Try hard reset.
[Object.debug:196] Finished read loop
Error: Couldn't sync to ESP. Try resetting.


fadeOut() broken

Hi, ben. Great plugin. There should be more people helping.
Ok, is it just me or fadeOut() doesn't work except with argument 0 (which doesn't fade of course).
http://jsfiddle.net/DSjr2/2/

This should now be fixed in the latest release


page: rewards: fix duplicated "not" in message

PR Checklist
Please check all that apply to this PR using "x":

[X] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[X] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number:
What is the current behavior?
Duplicate word: "not" in "Reward validation pending" message (https://odysee.com/$/rewards)
What is the new behavior?
No more duplicated word.
Other information

Thanks for the PR! Can we show you some appreciation?

I would love that! I just started using LBRY/Odysee for real, so I'll follow up once I have it figured out and set up.
Thank you very much!

Thanks for the PR @xdevs23
I merged your commit here https://github.com/lbryio/lbry-desktop/commit/991b45d83122164d4c0bc4899610de9ac67914b0 since your PR is trying to merge this into the odysee branch instead of master


Assume UTC when decoding a DATETIME column in sqlite

Sqlite's DATETIME column can have a default value set by CURRENT_TIMESTAMP which is then a string expressed from UTC in the following format: "YYYY-MM-DD HH:MM:SS". Unfortunately, this can't be properly decoded as a time::OffsetDateTime as the TZ info is missing. This PR proposes to assume UTC in such a case.
Related issue #2288.

@nstinus the SQLite driver was moved into its own subdirectory, can you rebase please?

@nstinus the SQLite driver was moved into its own subdirectory, can you rebase please?

Sure, done. Thank you.

To make sure I understand, this doesn't address the concern in https://github.com/launchbadge/sqlx/issues/598, correct? As far as I can tell with this branch we still get back a chrono::NaiveDateTime for DATETIME columns.

To make sure I understand, this doesn't address the concern in #598, correct? As far as I can tell with this branch we still get back a chrono::NaiveDateTime for DATETIME columns.

Correct. This change does nothing on the chrono types. It only touches the time types.


Use sets.NewString from apimachinery

Changes
This replaces the use of map[string]struct{} with sets.String from K8s apimachinery.
This is a nice higher-level API to replace the Go idiom, which (while clever) isn't terribly approachable to folks unfamiliar with Go.
N/A internal cleanup

/kind cleanup
/assign @vdemeester @afrittoli @ImJasonH

/retest

Honestly this doesn't seem worth it to me. Going this route and being consistent would mean we are now gonna need to be vigilant and/or add automation to see if ppl us the go based approach, and it seems like the only thing we maybe gain is ppl not needing to learn the encountered[r.Name] = struct{}{} syntax which is really kind of a one time expense.
f _, ok := encountered[r.Name]; ok makes more sense to me than if encountered.Has(r.Name)
I don't want to die on this hill tho!

My last 2 cents that I can't stop myself from expressing: there is something to be said for using a lang idiomatically. This feels like we are trying to make Go more similar to some other language that is more familiar to ppl, and I'd prefer we use Go idioms instead.

@bobcatfish I tend to agree with you.  And in hindsight I think this perspective would have similarly resulted in me not creating https://github.com/tektoncd/pipeline/issues/2587.  Is there something we can do to codify this approach in our docs?

@bobcatfish Ack on most of these points, but I'll add a bit of my own color to this as well.  Sorry this turned into a wall of text. 😬
Regarding the "one time cost", while I agree that there is a one-time hit to learn the idiom (vs. say map[string]bool), I disagree that the resulting states require an equivalent level of cognitive load to understand.  This isn't about making this look like another language, even when folks have been doing this for years (🙋 ), you have to effectively decode the idiom as you are reading, and (for me) that is strictly more expensive than simply reading a clearly named type or method (I'm reminded of literate programming).  So I don't agree that "the only thing we gain" is folks not needing to learn the idiom.
This becomes especially true when the sets become elements of a larger type, e.g. func (string, map[string]map[string]struct{}) map[string]struct{} vs. func(string, map[string]sets.String) sets.String (there were a number of rewrites like this in this PR).
Furthermore, there are gains beyond simple readability from this as well, such as having methods for walking the deduplicated ordered members:
https://github.com/tektoncd/pipeline/pull/2909/files#diff-751973423f2da1201a11e2c0e41930ccR48
... or should the need arise performing other "set" operations like difference and intersection.
Many Go idioms like map[string]struct{} vs. map[string]bool and chan struct{} vs. chan bool arise because of their inherently superior efficiency over the other approach.  With zero-values if myset[key] { is strictly more readable than if _, ok: myset[key]; ok {, but the latter with struct{} is more efficient.  Encapsulation enables us to have this efficiency without sacrificing readability.
While this library may be overkill for many of the cases rewritten, I do think that it almost universally improves the readability without any material runtime cost (it is after all a type alias of the Go idiom), and I think there are instances (as above) where it eliminates one-off code.  Good use of Go idioms and good use of libraries shouldn't be at odds with each other, and while I value consistency I think this is as much about educating contributors and reviewers about available libraries as it is Go idioms.  I think that understanding of available libraries better prepares both sets of folks (no pun intended) to exercise good judgement about what's best for their particular situation.
I too don't plan to die on this hill 😅 , so if you don't want this PR, I would be happy to roll it back, but it sounded like @ImJasonH and @afrittoli thought this was a positive change (here and in #pipelines-dev) 🤷

@bobcatfish Ack on most of these points, but I'll add a bit of my own color to this as well. Sorry this turned into a wall of text. 😬

np np! my apologies for not replying faster also

you have to effectively decode the idiom as you are reading, and (for me) that is strictly more expensive than simply reading a clearly named type or method (I'm reminded of literate programming).

I agree.  If a language's idioms are too hard to understand, to me that points toward a problem with the language.
Maybe we decide: we are using Go because of XYZ (I'm guessing concurrency support) however we think its idioms are inscrutable, therefore we are hiding them. I'm probably being unreasonable thinking that it's that simple, but in general what I want to do is embrace the language I'm using. If there are problems with the language, it feels like the place to deal with that is in the language itself. (maybe that's happening already...)

func (string, map[string]map[string]struct{}) map[string]struct{} vs. func(string, map[string]sets.String) sets.String

That's a good point, I hadn't thought that through.
Maybe once Go has generics this will all be a moot point - until then it seems like the decision was made that it was okay for folks to duplicate this kinda code when they need it:
// Empty is public since it is used by some internal API objects for conversions between external
// string arrays and internal sets, and conversion logic requires public types today.
type Empty struct{}

// sets.String is a set of strings, implemented via map[string]struct{} for minimal memory consumption.
type String map[string]Empty

Kinda like how it's okay to have to go if err all over the place. I think they might be walking back some of these decisions tho?
Maybe what really bothers me is that this code is inside of k8s api machinery, i.e. we are depending on a lib inside of k8s - fortunately we already rely on it, so maybe that makes sense. I don't know if I'd be having the same reaction if someone had written a set package in this codebase.
Maybe you're right about the other functionality we get - and maybe once Go has generics this will all be moot and the Go standard libs will include more of this kind of thing.

if you don't want this PR, I would be happy to roll it back,

nah that's okay - thanks for taking the time to discuss this!

Feels like backfill to me.  "Oh shoot, people want sets!"  "What is the most efficient way to do this within the language?"
pissing contest ensues
Profit!


How to access dataField in dataFormat?

I have below code
render() {     const col = [ 'id', 'name', 'price' ];     return (       <BootstrapTable data={ products } keyField={ col[0] }>           { col.map(name => <TableHeaderColumn dataField={ name }>{ name }</TableHeaderColumn>) }       </BootstrapTable>     );   }
Now I want to add dataFormat to TableHeaderColumn. How can I acces dataField in dataFormat to know the key?

With inline dataFormat you have access to the enclosing scope so:
col.map( name =>
    <TableHeaderColumn
        dataFormat={
                (cell, row, formatExtraData, index) => {
                    name <-- you can access it
                }
        }
        ....

Have you found the answer?
Please let me know if you have any solutions to this issue.


Reasons for a container instance with restart policy OnFailure to stop and not restart

I have seen this behaviour on 2 container instances communicating with a Bus Service.
Both stop and do not restart, even though one of them is not being executed at all. What reasons may explain this behaviour?

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

ID: cfacc7cf-4224-9bd8-6211-29244cf60a83
Version Independent ID: a940a6f2-e1a9-d32b-4303-ab7705753942
Content: Azure Service Bus messaging exceptions
Content Source: articles/service-bus-messaging/service-bus-messaging-exceptions.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

@PabloBotas Thanks for the question! I believe this is a question best asked on the Azure Container Instances MSDN Forum or StackOverflo with the azure-container-instances tag.
AFAIK the restart policy simply checks for the exit code of the container when it crashes to decide whether to restart it or not.

Thanks! I will do so


Pass all relevant information from Kontrol to KaaS

Currently, KaaS requires of a user to upload the out folder of the project, that is, the kompiled definition and the associated proofs. For users of KaaS us to be able to reproduce the proofs themselves, and also for us to be able to use KaaS to run proofs more efficiently, I think that it would be good to include at least the following information somewhere in the out folder, possibly in the digest file:

the version of Kontrol used to kompile the definition and run the proofs;
the full command used to kompile the definition - this is relevant because perhaps lemmas have been incorporated, etc.
the commit hash of the project at the time of kompilation and proof-running.

These three would allow both KaaS and any user to re-create the definition, assuming it is able to access the project repository, so perhaps if we had this information we would not need to upload the entire out folder. In discussion with @ehildenb, it came up that definitions may vary slightly from machine to machine (say, Ubuntu vs. Mac) so having the above info might even be essential.
The situation is a bit more complex when it comes to replaying the proofs, because the KCFGs could have been created bit-by-bit, using a number of different kontrol prove commands, and modified using node refutations, unrefutations, deletions, etc. If we wanted to replicate a specific KCFG at hand, we would, I think, have to store all the specific commands used, together with some indicators of how long they were executed for (in the sense of if I ran a command with max-iterations set to 100, but stopped the execution after 25, I would ideally record the 25).
If we don't care about fully replaying KCFGs but rather being able to inspect them and continue execution, then we could potentially provide to KaaS the values of the parameters that we expect the proof to be continued with (e.g., max-depth, max-iterations, etc.).

This could help provide useful information to the user when they run remote compute jobs. Having in the list of jobs executed a compute entry could show the flags passed to kontrol build / prove within the 'tile' for that job.


Remove bumping codecov-action to v4

Dependabot had bumped the codecov action to v4 and it passed CI, but now
it doesn't. I'm guessing there was a mistake where they removed v4. At
the time of this PR there are v4-beta tags.

Current dependencies on/for this PR:

main

PR #179   👈

This comment was auto-generated by Graphite.

The original PR that bumped to v4, https://github.com/mobilecoinfoundation/attestation/pull/175
The CI run where it worked, https://github.com/mobilecoinfoundation/attestation/actions/runs/6191610317/job/16810179732


No warning when login needs to be run

This is autogenerated. Please review and update as needed.
Describe the bug
az ssh vm command failed with a massive error message (took up my entire terminal window). When I ran az login again though,  the command worked fine again. When I'm overdue to login again, the ssh vm command should just say that simply.
Command Name
az ssh vm Extension Name: ssh. Version: 0.1.5.
Errors:
Please run 'az login' to setup account.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ssh vm --ip {}

Expected Behavior
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.24.2

Extensions:
ssh 0.1.5

Additional Context

route to service team

@tomshaffner do you happen to have the stacktrace? I have a few ideas where this could be happening but it would help.


[Beta 1.14.0] APM or github packages and Portable mode

Hi,
1> apm cannot be run from atom folder and need a complete path.
2> apm installs and "builds" the installed package in the not-portable user folder, for windows C:\Users\myself\.atom
My setup is somewhere on my D disk and works fine except that :-)
Windows 7 x64
Atom    : 1.14.0-beta4
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0

Thanks

Thank you for contributing!
We require the issue template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests. Please open a new issue and fill out the template for us.
Thanks for understanding and meeting us half way :grinning:


Fixed deserialize with app_label config. close #171

Excuse, I don' want to commit "Require 'salesforce' in installed apps", only the fix 171. (It is usually useful to check the presence of "salesforce" app in settings, but I don't want to do it in the the root this way.)

The last commit is replaced in the next new PR.


QRCode generation

We should generate a QR code when user first logs in.
The code should contain the following data: hackillinois://qrcode/user?id=&identifier=
Once this first step is done, we also introduce a two level image cache for future proofing.
This cache manager will use an in memory NSCache as well as a disk cache.

done


Pasting multiple emails not working in IE11

If you paste multiple emails at the same time (from a spreadsheet, for example), it only takes the first one. Other browsers use all emails that were pasted. I was able to recreate this behavior on the demo page here: http://sliptree.github.io/bootstrap-tokenfield/
To recreate, copy and paste the following emails in both Chrome and IE11 and notice the difference.
<EMAIL_ADDRESS><EMAIL_ADDRESS>

I HAVE THIS PROBLEM TOO


Fixing/Reorganizing of help file

Summary of changes

Fixing of some spelling/grammatical errors
Removal of "banqueue" command category; unused
Addition of "management" category description
Reordering of commands to match the ordering of their respective categories
Reordering of categories

Apologies with the ++strikerequest notification commits, accidentally added those in here without meaning to

I can accept this but in light of keeping things clear you'd need to slice out the strike request change

Sounds good; I'm just going to make a new PR cause I idiotically committed to my develop branch instead of a different one


Makes strings translatable in pagination for available components

Updates make strings translatable but also available to screen readers.

Codecov Report

Merging #344 into master will increase coverage by 18.55%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master     #344       +/-   ##
===========================================
+ Coverage   14.88%   33.43%   +18.55%
===========================================
  Files          79       80        +1
  Lines        1572     2246      +674
  Branches      217      210        -7
===========================================
+ Hits          234      751      +517
- Misses       1131     1337      +206
+ Partials      207      158       -49

Impacted Files
Coverage Δ

components/Pagination/Pagination.js
52.38% <100%> (+52.38%)
:arrow_up:

routes.json
55.55% <0%> (ø)

components/Tabs/pf-tabs.component.js
1.76% <0%> (+1.76%)
:arrow_up:

components/ListView/ComponentDetailsView.js
2.5% <0%> (+2.5%)
:arrow_up:

components/ListView/ListItemComponents.js
2.77% <0%> (+2.77%)
:arrow_up:

components/ListView/ComponentSummaryList.js
5.88% <0%> (+5.88%)
:arrow_up:

core/sagas/composes.js
5.88% <0%> (+5.88%)
:arrow_up:

components/Tabs/pf-tab.component.js
8.33% <0%> (+8.33%)
:arrow_up:

components/Tabs/Tab.js
10% <0%> (+10%)
:arrow_up:

components/Tabs/Tabs.js
12.5% <0%> (+12.5%)
:arrow_up:

... and 41 more

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 d1cf182...8b8e3d3. Read the comment docs.

So, fine from my POV to land, if you are confident that CI didn't break any further.

Please hold off landing, I'm almost done with fixing tests.

@larskarlitski : Should we still hold off, or land this now?

I've gotten the tests to a better state, but there are still some flakes (in particular in CreateNewBluePrint, which sadly is called from many others).
This PR looks good to me and the tests suite passes locally some of the time, just like for master. It's unlikely that this is introducing new failures.


Fix log pointer path in container + make hostPath configurable

What this PR does / why we need it:
Which issue this PR fixes

Fix the log registry volume's mount path inside the container, set it to the standard /opt/datadog-agent/run

fixes #9700

Make the hostPath configurable with the new datadog.logsPointerHostPath option (feature request)

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/lgtm

/lgtm


Updated readme with api usage example for proxy server

Codecov Report
Base: 60.53% // Head: 60.53% // No change to project coverage :thumbsup:

Coverage data is based on head (979d308) compared to base (97f1786).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #612   +/-   ##
========================================
  Coverage    60.53%   60.53%
========================================
  Files           26       26
  Lines         2818     2818
========================================
  Hits          1706     1706
  Misses        1112     1112

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

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


更换数据集后报错：Assign requires shapes of both tensors to match. lhs shape= [4608,1024] rhs

请问是怎么回事？

已解决


Automatically selects last page instead of first on load.

Hey @pieterjandebruyne I'm assuming this is related to #90.

Fixed with #92


Added Arabic Translation

@manastungare Any chance this gets merged soon?

Hi Johanna, thanks for submitting the translation! Before I can merge it, I need to verify that this extension works correctly in right-to-left languages. Have you already been using it in Arabic with your translation? What has your experience been so far?

Hi Manas, thanks for getting back to me on this. I can't find an option to change the extension language, does it default to the OS language?

Yes, it uses the OS language by default and there's no explicit way to change it.

Turns out I only need to change the Chrome Language Settings to change the extension language. Here's a couple of screenshots of the extension in Arabic for verification. Everything is working fine, except the Troubleshooting part which is still in English.

Is this left-to-right layout acceptable for Arabic users, in your opinion?

Ideally, it should be right-to-left, but personally it doesn't bother me since the Options page doesn't have that many options.
That being said, I've discovered something I missed before, the chrome://extensions page was showing the extension name with the parenthesis in the wrong location, (Google Calendar (by Google:

Fixing that caused the the extension name in the Options page to have the same problem due to the left-to-right layout of the page:

As a temporary workaround, we can use a dash instead of parentheses, i.e. Google Calendar - by Google:

What do you think?

Sure, if you prefer a hyphen instead of parentheses, I don't mind. Let me know when you are happy with this commit, and I would be happy to merge it. Thanks, once again, for your effort in translating and verifying this!

Thanks. I changed the parentheses to a hyphen and squashed the commits into one commit for convenience.

Perfect, thanks!


Update feedstock to use cirun-openstack-cpu-large with Cirun

Note that only builds triggered by maintainers of the feedstock (and core)
who have accepted the terms of service and privacy policy will run
on Github actions via Cirun.

[ ] Maintainers have accepted the terms of service and privacy policy
at https://github.com/Quansight/open-gpu-server

Also, note that rerendering with Github actions as CI provider must be done
locally in the future for this feedstock.

Taking this as a win here, will tackle windows separately.


eth_estimateGas is returning 400K gas causing a sendTransaction to fail.

Description
An `eth_estimateGas call with a large amount of bytecode is return 400K
Steps to reproduce
The attached script reproduces the problem against mainnet.
eth_estimateGas.sh.txt
Additional context
No response
Hedera network
mainnet
Version
v0.45.2
Operating system
macOS

I just ran the curl command and it returned:
{"result":"0x14bb4b","jsonrpc":"2.0","id":1}


[BUG] OpenSearch Docker Container

Describe the bug
Hello, I'm running into an issue where I can't connect to the opensearch docker container following the opensearch documentation outlined here:
https://opensearch.org/docs/latest/opensearch/install/docker/
To Reproduce
Steps to reproduce the behavior:
docker pull opensearchproject/opensearch:latest
docker run -p 9200:9200 -p 9600:9600 -e "discovery.type=single-node" opensearchproject/opensearch:latest

In a separate terminal tab I run:
curl -XGET https://localhost:9200 -u admin:admin --insecure

I get the following response:
~ % curl -XGET https://localhost:9200 -u admin:admin --insecure
curl: (7) Failed to connect to localhost port 9200 after 8 ms: Connection refused

Expected behavior
I expect the curl GET request to connect
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: Mac OS Monterey
Version 12.4

Additional context
I'm running docker via Colima installed via homebrew
~ % colima status
INFO[0000] colima is running
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType:
INFO[0000] socket: unix:///Users/<my username>/.colima/default/docker.sock

Thanks in advance! 🙏

Moved this to opensearch-devops.

Hey @liamcassidy-eb running docker run -it -d -p 9200:9200 -p 9600:9600 -e "discovery.type=single-node" opensearchproject/opensearch:2.2.0  and once you are into (exec) the container, the following command should work, please check the logs until the OpenSearch is full up and running.
curl -XGET https://localhost:9200 -u admin:admin --insecure
{
  "name" : "69c22a212027",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "hpFTibawRnCWbOPIOSwgtg",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.2.0",
    "build_type" : "tar",
    "build_hash" : "b1017fa3b9a1c781d4f34ecee411e0cdf930a515",
    "build_date" : "2022-08-09T02:27:25.256769336Z",
    "build_snapshot" : false,
    "lucene_version" : "9.3.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

Thank you

Hey @liamcassidy-eb I suspect this is something to do with colima setup.


Investigate logging during runner shutdown

In some cases, worker threads panic when we try to send log messages to the main process during runner shutdown.
This doesn't really have a practical impact (as it's contained to the runner process and only happens after communication with the main process stops), but it can make stdout/stderr confusing because it looks like something important broke.

New runners should be available after the next nightly build.
To get them, you can delete your runner directory (see https://carton.run/docs/config). This defaults to ~/.carton/runners/. New runners will automatically be fetched the next time you try to load or pack a model.

The nightly build is done and the new runners are published. I confirmed that they fix the issue. Follow the instructions above to clear your local runners and get the new ones.


Framerate

I have some problems with frame rate. Default in ARKit is 60fps, when i turn on recording the whole scene goes 2 times faster, all physics and animations work 2 times faster in record mode than in non record mode. In debug i see that scenekit fps is turned to 120fps while in recording. Is there any workaround ? I tried setting recorder fps to 60, but still same behaviour happens.

Hey @kristokiis!
I have noticed this issue recently. Can you try setting the RecordAR fps to fps30.
If that doesn't make any difference, you may create a workaround by setting the the SceneKit animation to half what it is right now.
Or try adding the following in viewDidLoad:
sceneView.preferredFramesPerSecond = 30
recorder?.fps = .fps30

Please inform me how those steps will workout for you.
-Ahmed

Seems it does not help, recording still forces everything 2 times faster nomatter what those settings are.

@kristokiis,
Thank you for informing me. I'll be including a fix to this issue in version 1.12.
At this moment, the only workaround would be slowing down the nodes' animations to half what it originally is.
-Ahmed

ok, but do you have any estimations when 1.2 will be released?

@kristokiis,
I can't give estimates at this moment; however, I'll try to have it published by end of December.
Also to fix your issue, you may slow down the animation into half what you're using right now. For example, if your animation is taking 5 seconds you'd change the intervals to 2.5 seconds.

but it would affect them when recording is not active. Problem is switching between recording and normal state, physics and world is too different. Question how did you change fps in recording mode that it also affects scenekit fps? Maybe i can use that code to keep same fps in both cases.

Is there any updates coming up with this project? Need to know if i can use this one or need to create my own.


Enable Gradle setting that makes desugaring in debug work

#2  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


[Feature]: Drupal sites

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Build and deploy Drupal sites using a modern Jamstack approach
Why should this be worked on?
integrate Drupal similar to  nellify https://www.netlify.com/with/drupal/

Something similar to https://cloud.wodby.com/stacks/drupal9/overview would be great

I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs.
Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug.
Thanks for your understanding.


logEvent does not save params

Describe the bug
I'm unsure if this is an issue with the library or with the dashboard.
I cant get events parameters to be logged, been trying for weeks now.
Flurry.logEvent('test_event', {'theparam': '1234'});
This Bug is About
Please choose the closest item by replacing [ ] with [x].

[X] Analytics
[?] Flurry Website/Dashboard

Platform
Please choose the platform(s) that you are having the issue by replacing [ ] with [x].

[X] iOS

Environment
Please tell us the versions of SDKs you are using. If you are not sure about React Native version, you can run react-native --version under your project.

React Native version: 0.63.2
react-native-flurry-sdk version: 6.2.0

I just confirmed that the plugin does pass through all params to the underneath SDK without any issues. And see all of the logging params from the UI.
Please first to navigate the features in the Flurry UI. Some tabs you can check are,

Under Analytics tab

Events

Parameter Trend
Parameter Distribution

Or use the params for measurement

Under Explorer tab

Data Analytics

Measures

I just confirmed that the plugin does pass through all params to the underneath SDK without any issues. And see all of the logging params from the UI.
Please first to navigate the features in the Flurry UI. Some tabs you can check are,

Under Analytics tab

Events

Parameter Trend
Parameter Distribution

Or use the params for measurement

Under Explorer tab

Data Analytics

Measures

I just confirmed that the plugin does pass through all params to the underneath SDK without any issues. And see all of the logging params from the UI.
Please first to navigate the features in the Flurry UI. Some tabs you can check are,

Under Analytics tab

Events

Parameter Trend
Parameter Distribution

Or use the params for measurement

Under Explorer tab

Data Analytics

Measures

You are absolutely right, thank you very much for the info. I wasn't looking at the correct flow.

I just confirmed that the plugin does pass through all params to the underneath SDK without any issues. And see all of the logging params from the UI.
Please first to navigate the features in the Flurry UI. Some tabs you can check are,

Under Analytics tab

Events

Parameter Trend
Parameter Distribution

Or use the params for measurement

Under Explorer tab

Data Analytics

Measures

You are absolutely right, thank you very much for the info. I wasn't looking at the correct flow.


Can Ghidra be configured to exceed the 16k max null-terminated string size?

I recently looked at malware with a 16k+ size base64 encoded null-terminated string. Ghidra did not identify the string due to its large size. Is this configurable in the interface somewhere?  (FYI, the "Data" help page says "A null- terminated string will extend until a null character is found (with a sanity check max of 16k)...".

No, the sanity check is hard-coded right now.  This is a interesting situation though.

As a quick workaround, you can manually create a string instance at that location using a GhidraScript:
currentProgram.getListing().createData( askAddress("String start", "starting addr"), StringDataType.dataType, askInt("String len", "number of bytes"));

Maybe the string identification should identify the string up to the max, and then start another string.
If it is a string up to the max length, then it is still a string.
You may also be able to force a string with a selection and create a string.  The string data type doesn't always rely on there existing a terminating null, since a string buffer in memory could be uninitialized, or all zeros.

Question was answered...closing.


Unable to retrieve Tab info for YouTube Speed Memory

When I open a YouTube video, I get the console errors: Unable to retrieve Tab info for YouTube Speed Memory and Unable to retrieve Tab info for YouTube Speed Memory.
Test environment: Chrome 69.0.3497.81 (Official Build) (64-bit)

@nikolayhg When you refresh the YouTube page, does this behavior persist? This is something that can occur in cases where YT did not load quickly enough and the extension stops trying to register itself with the page. In this situation, reloading YT should solve the issue.
This issue will be something included in the large scale refactor of the whole extension, so keep an eye on the project and issue status updates that will be coming soon.

yes. I tried refreshing, same error.

Hm, I'm not sure what is going on here, I've never experienced this symptom across refreshes. You could try reinstalling the extension, but barring that I don't have a lot of intuition about what's going on at this moment. Improving the predictability of the extension will be a top priority during the rewrite, so for the time being, if reinstalling doesn't work, you'll just have to sit tight while I work on the rewrite :)

reinstalled it and deactivated potential collision extension, but get same error.

Ok shoot - the only thing that comes to mind is that your youtube page is not loading fast enough (from YouTube Speed Memory's perspective) or that you have an adblocker (or something) that is blocking the specific elements the extension expects. All it waits to load are the channel name, the video id, and the channel artwork, so I'm not sure what could be blocked by an adblocker, i.e. that seems unlikely to be the culprit. For now you may just need to sit tight while I find the time to get to the updates (or feel free to make a pull request to do them yourself if you are able 😄). I'll update this issue when I've made the updates for you to test.

Thanks! I can wait. FYI: I deactivated all blocking extensions for the test. The video starts in less than 2 secs.

@nikolayhg I finally found out what's happening with this bug. The version of YouTube that you were being served was different than what I was being served (Google does market-subset testing with UI changes). This is why my extension was working fine and yours was not. Today, I started receiving the "new" YouTube that you had been getting and my extension stopped working too. I've made updates that will ensure that both of these versions of the site will work with the extension. I'll be pushing it to the store in the next few minutes, so you should be able to update your extension within the hour and have it start working again.
I'm going to close this issue, but if your issue persists, I can reopen it.
Cheers!


Remove dependency on Abseil

Once the following bugs are fixed we should remove the submodule and remove the dependencies in the makefiles:

[ ] #254
[ ] #253
[ ] #252
[ ] #251
[ ] #250
[ ] #249
[ ] #248

Note to self: remove cctz also.
And remove the packages from the AppVeyor install script.


Add option for specifying viewpoint to arguments

I think this can be done by

rotating the stars and gas, or
by specifying the view point in FIMap

the viewpoint (together  with image_target and up_vector) parameters of fimap specify the view; so I would directly map input arguments to these..

Yeah, that's probably the best approach.


Issue with Passive Investor Excel tzinfo datetime/time object is not set to None

OS Windows10
Error
The program has crashed with the following error:
Excel does not support timezones in datetimes. The tzinfo in the datetime/time object must be set to None.
If the problem persists, please create an Issue with the error message on the project's GitHub page:https://github.com/JerBouma/ThePassiveInvestor/issues.

I've retired the program due to the fact maintaining is not possible. I've updated the package to reflect the changes in yfinance. Please use the package instead, this should work!

Thanks for the update! Do we hve to reinstall the program to make it work or use it directly as is?

The program itself has been deprecated so the only way to use the package now is directly though Python. See: https://github.com/JerBouma/ThePassiveInvestor#installation

Thanks, after -U option progrma seems to act normal and working!! Yeh. May I ask how you fixed Tz zone issue?


Update build configuration

The build configuration of this project is outdated and may no longer work.
This pull request will be merged automatically if there are no conflicts.

:tada: This PR is included in version 4.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(Topology): lemas about MapClusterPt

Also reuse variables and make some arguments implicit.

maintainer merge

Thanks!
bors merge


rocks generate on giant mushrooms

1.12.3 beta
Rocks can generate on at the very least brown giant mushrooms, didn't see them on red but probably worth checking too.

I'll fix this when I get home
-----Original Message-----
From: "Jackson Cribb"<EMAIL_ADDRESS>Sent: 8/27/2017 6:34 PM
To: "theishiopian/ForageCraft"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Subject: [theishiopian/ForageCraft] rocks generate on giant mushrooms (#24)
1.12.3 beta
Rocks can generate on at the very least brown giant mushrooms, didn't see them on red but probably worth checking too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you provide the seed/coords, for testing purposes? will make this a lot easier :)

7670100323430838974
That will work, not my seed but mushroom biome that has multiple occurrences

Awesome, Ill get on this Asap!

Well this looks frightening
http://i.imgur.com/LtaVhGR.jpg

@Octopork Fixed


Add trident_info metric

This PR adds trident_info metric.
# HELP trident_info Information about the Trident
# TYPE trident_info gauge
trident_info{version="20.04.0-custom+cd3680aaefb7534344bd9bb850971789563fe442"} 1

/closes #364
I've already signed NetApp CLA.

@superbrothers, thank you for submitting the PR. We are adding a number of new Prometheus telemetry data in the Trident 20.07 release. We were unable to use your PR as it is with these changes. This is the commit that contains the Trident version information.


Ambiguous measurement units

Quotas are specified in 300k , 80k etc. I assume tokens, not clearly specified.

Lacking information of which time unit quotas are bound by. Concurrent, hourly, daily, monthly?

Other datapoints without specified units such as:

"Max number of /chat/completions messages" - max number per what? Per resource per hour? per subscription?

As a customer who just wants to dive straight into the API and provide a confident case to my economy dept ASAP, I found the information confusing. The azure architect I've been in contact with hasn't been up to date with the details of the AI value proposals. Considering all the learning curves that are happening, you might want to look over the documentation.
Thanks for keeping up the good work!
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a8ff3d7a-b044-63c0-4c66-1bed9e894287
Version Independent ID: 649fbdae-45d1-dd59-2482-4d6640b6eb67
Content: Azure OpenAI Service quotas and limits - Azure AI services
Content Source: articles/ai-services/openai/quotas-limits.md
Service: azure-ai-openai
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@HedaSecurity-GFalting
Thanks for your feedback! We will investigate and update as appropriate.

Hello @HedaSecurity-GFalting
The quotas and limits for Azure OpenAI services are specified in terms of tokens, which are a unit of measurement for the amount of data processed by the service. However, the time unit for these quotas and limits is not always specified.
Regarding the "Max number of /chat/completions messages" quota, it is not clear from the documentation what time unit this quota is bound by. It is possible that this quota is per resource per hour, per subscription, or some other time unit.
I understand that this lack of clarity can be confusing for customers who are trying to plan their usage of Azure OpenAI services. I will pass along your feedback to the appropriate team to see if we can improve the documentation to provide more clarity on the time units for these quotas and limits.

@mrbullwinkle
Please review it.

Hi @Naveenommi-MSFT
Thank you for your time reviewing the feedback! Have a wonderful weekend!

@HedaSecurity-GFalting
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


remove suggestion to exchange xDAi for ETH

🤦♂

@johannbarbie what to do to get this suggestion?

via #54


Videos don't start anymore

I'm submitting a ...

[ ] bug report
[ ] feature request
[ x] support request

General information
Prerequisites

[x ] Are you running the latest version?

Description
[Description of the bug or feature]
Steps to Reproduce

Try starting any film or episode.

Expected behavior: The film starts
Actual behavior: The video doesn't start, it stops right away. No error.
Context (Environment)
Installation

[x ] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[ ] Linux (ARM)
[ ] Android

Libreelec
Additional informatin on the environment
[Descripe your environment a bit more detailed, are you using LibreElec f.e.]
Debug log
N/A
Other information
As of today I noticed that no videos are starting up. No visible error message. Nothing happens, only for a moment it lookd like when a video starts, and then it stops.
I experience exactly the same thing in the HBO addon, but not in YouTube addon, for example. So I suspect it might have something to do with Widevine CDM?...
As troubleshooting I upgraded my Libreelec (on Raspberry Pi) from 9.2.1 to 9.2.4, also did a Widevine CDM installation (at some point I was prompted). Tried collecting debug logs, but had difficulties with that.
For now I'd just like to ask if anybody else has started experiencing this?

Resosolved by uninstalling and then reinstlling Widevine CDM.


Catalog Of My Things

Description
This app allows you to record different types of things you own: books, music albums, movies, and games.
Task: https://github.com/microverseinc/curriculum-ruby/blob/main/group-capstone/catalog_of_my_things.md
This PR makes the following changes:

Creates different types of methods to add all the items
Creates app interface to call the different methods
Store the data in JSON files
Test all methods with Rspec

Note: Unfortunately, Desor had a personal problem in his country so he couldn't be present at the time that we recorded the video but he supported us during the whole project
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Test (change related to testing)
[X] Refactor (non-breaking change that neither fixes a bug nor adds a feature)

Checklist

[X] My code follows the style guidelines of this project (no linters errors)
[X] I have checked my code and corrected any misspellings
[X] I have commented on my code
[X] I have deleted any unused code as comments in my codebase

@elisha2kyakpo1 Thanks!!


Fix: memory leak in transaction handles

Transaction handles are currently allocated upon starting new transactions without proper deallocations of previous handles, which leads to memory leaks. This PR fixes this issue following an approach seen in other OCI driver implementations: a single transaction handle is reused for every new transaction.
Note: somehow, one test case (TestSelectDualString) seems to have a non-deterministic behavior, as it might occasionally fail even in the master branch. All other tests passed normally. We also tested this fix under realistic loads in one of our apps and everything ran smoothly.

Thank you for working on this and looking into this. Have a couple of questions.

How do you know transactions are leaking memory?  If so, can you reproduce that test?

Where is it noted that transaction handles need to be freed?

Also there is not a lot of testing around transactions. Will most likely need to add more testing with transaction. One test in particular is that three or more transactions at the same time will work correctly. Probably a few other new tests would be good as well.

Thank you for working on this and looking into this. Have a couple of questions.

How do you know transactions are leaking memory?  If so, can you reproduce that test?

Where is it noted that transaction handles need to be freed?

Also there is not a lot of testing around transactions. Will most likely need to add more testing with transaction. One test in particular is that three or more transactions at the same time will work correctly. Probably a few other new tests would be good as well.

Hi Michael!
Thank you for your prompt reply. I've just created a new issue (#411) to contextualize this. Apologies for doing it after creating this PR. Regarding your questions,

As stated in the issue, we found significant memory leaks in one of our apps and we strongly think they are due to this. New requests are permanently creating and starting new transactions, and after inspecting the code we found their handles are not freed. We ran stress tests before and after the fix and the leak is definitely gone.
It is actually not noted anywhere, but not doing it leads to the aforementioned issues. We have inspected some other implementations the make use of OCI drivers and they seem to reuse a single handle as proposed in this PR. Unfortunately, official docs (e.g. here) do not provide greater detail, but at least they seem to be consistent with this fix.

Please let us know if you need further details or information!
Best regards

Hi Michael!
Thank you for your prompt reply. I've just created a new issue (#411) to contextualize this. Apologies for doing it after creating this PR. Regarding your questions,

As stated in the issue, we found significant memory leaks in one of our apps and we strongly think they are due to this. New requests are permanently creating and starting new transactions, and after inspecting the code we found their handles are not freed. We ran stress tests before and after the fix and the leak is definitely gone.
It is actually not noted anywhere, but not doing it leads to the aforementioned issues. We have inspected some other implementations the make use of OCI drivers and they seem to reuse a single handle as proposed in this PR. Unfortunately, official docs (e.g. here) do not provide greater detail, but at least they seem to be consistent with this fix.

Please let us know if you need further details or information!
Best regards

If a single transaction handle can be used, can it be created always so nill check is not needed?
I think the only test in the code for transaction is TestDestructiveTransaction. Maybe more testing is needed?

If a single transaction handle can be used, can it be created always so nill check is not needed?
I think the only test in the code for transaction is TestDestructiveTransaction. Maybe more testing is needed?

It should be possible to allocate new transaction handles instead of reusing a single transaction context, but instead of checking against nil we should instead deallocate the handle somewhere --possibly after committing or rollbacking the transaction. I think this approach adds overhead and complexity for current use cases.
As for the tests, I can surely add a couple more cases so that this fix is properly covered.

It should be possible to allocate new transaction handles instead of reusing a single transaction context, but instead of checking against nil we should instead deallocate the handle somewhere --possibly after committing or rollbacking the transaction. I think this approach adds overhead and complexity for current use cases.
As for the tests, I can surely add a couple more cases so that this fix is properly covered.

Not sure if you are following what I am saying. Was saying move conn.ociHandleAlloc(C.OCI_HTYPE_TRANS, 0) out of BeginTx and into database open.
Wonderful :)

Not sure if you are following what I am saying. Was saying move conn.ociHandleAlloc(C.OCI_HTYPE_TRANS, 0) out of BeginTx and into database open.
Wonderful :)

That's right, I misunderstood your sentence. Thanks for the feedback!

That's right, I misunderstood your sentence. Thanks for the feedback!

Sure, tests are not done yet --this was in fact a first commit, still WIP. Thanks for your input, I'll let you know once everything is done on our side.

Sure, tests are not done yet --this was in fact a first commit, still WIP. Thanks for your input, I'll let you know once everything is done on our side.

Michael, I've been reviewing the test case you mentioned earlier today (TestDestructiveTransaction) and it covers several features, even operating with two transactions. I've just pushed an extension to this test with two extra transactions running after the first ones and one of them being eventually rollbacked. Since we do not introduce new functionality here, I believe this test should be enough to cover this PR.
Have a nice weekend and thanks for your time!

Michael, I've been reviewing the test case you mentioned earlier today (TestDestructiveTransaction) and it covers several features, even operating with two transactions. I've just pushed an extension to this test with two extra transactions running after the first ones and one of them being eventually rollbacked. Since we do not introduce new functionality here, I believe this test should be enough to cover this PR.
Have a nice weekend and thanks for your time!


Tooltip and Legend don't have formatter option

Hi!
I was building a quick demo and found out that the tooltip and legend don't have any options for formatting. For my stacked bar chart, legend is empty, for example. It would be great if tooltip and legend had a formatting option like axes do.

You can customize the tooltip demo.
I would consider adding a format option to legend.

@QingWei-Li I know, but you have to create a full custom tooltip for that. All I need for my demo is to format time series data from timestamps (needed to plot the chart correctly) to something more human-readable. I've created a date formatter which I pass to x-axis, and it would be great if I could just use the same formatter for tooltip or legend. Here's my demo: https://codesandbox.io/s/cubejs-vue-demo-9r5xl


Check part "liveness" for Heart Rate Sensor

[x] photo/schematic
[x] code and/or instructions
[x] expected result of "liveness" test

Checked that its powered on and successfully detected through I2C, added pictures/code/confirmation to report

Reopening issue to comment progress

To connect the heart rate sensor and get it working, you will need the following parts.

Heart Rate Sensor for Max 30102
Raspberry Pi
Jumper cables

This heart rate sensor breakout board can accept a voltage range including 3.3V, therefore the power given directly from the raspberry pi is within range to power the sensor. Because of this, no additional component is needed for power. Since the breakout board has a built-in ADC, the values are all readable. The low level schematic for the connections are seen in the figure below.
Following the image in figure 1 above, to connect the part you must first give it power. Connect the 3.3V pin on the top left of the Pi to the pin on the Max 30102 board that reads “Vin”. Then, connect a ground pin from the pi (using the bottom left in the image) and connect this with the “GND” pin on the board. Finally, since we will be using i2c to communicate, the pins for these must be wired. With another jumper cable, the GPIO 2 pin “SDA” on the pi is connected to the “SDA” pin on the Max board. The GPIO 3 pin “SCL” is then connected to the “SCL” pin on the Max board. After these four connections have been successfully created, the Max 30102 board is all wired up and ready for testing.

Testing I2C Connection
After the board is connected, the connection on I2C must be checked to verify that the Pi is reading the device properly. The steps are as follows which reference the I2C lab instructions.
I2C must first be enabled on the Raspberry Pi OS. After logging onto the Pi, run the following command
sudo raspi-config
The following window will pop up as seen in figure 2. Navigate to interfacing options, select I2C and click OK.

After this is done, the following window will appear confirming that you have configured the interface correctly.

To verify in the program that it is enabled, run the following command.
lsmod | grep i2c
The following in figure 4 will be returned on the screen if the setup was successful.

It is now time to confirm that the Max 30102 board is being read and is addressable. This will be done by scanning the entire I2C address space and looking for responses from each address. Run the following command in the terminal to do this.
i2cdetect -y 1
The result should be the peripheral address of the Max board. This expected value will be found in the datasheet of the part. The peripheral address is seen below in figure 5.

The peripheral address for the Max board is 0b1010111, which in hex is equal to 0x57. Running the code from above, the expected result will be this device address present in the I2C address space. Looking at the I2C response in the terminal after running the command, the following is seen.

As expected, the peripheral address for our board is seen at 0x57 which is what it should be according to the datasheet. This confirms that our part is successfully connected through I2C and ready to read values.

working and done


Error during installation with Docker

Hi
When trying to start this project via Docker, I encounter this error:
------
 > [split-pro-ws 5/6] RUN npm run just-build:
0.540
0.540 ><EMAIL_ADDRESS>just-build
0.540 > next build
0.540
2.787 [nextra] You have Next.js i18n enabled, read here https://nextjs.org/docs/advanced-features/i18n-routing for the docs.
2.823 Attention: Next.js now collects completely anonymous telemetry regarding usage.
2.824 This information is used to shape Next.js' roadmap and prioritize features.
2.824 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2.824 https://nextjs.org/telemetry
2.825
2.983   ▲ Next.js 14.2.5
2.994   - Environments: .env
2.994
2.996    Linting and checking validity of types ...
63.37 Failed to compile.
63.37
63.37 ./src/server/api/routers/group.ts:75:11
63.37 Type error: Object is possibly 'undefined'.
63.37
63.37   73 |           balances[balance.currency] = balance.amount;
63.37   74 |         } else {
63.37 > 75 |           balances[balance.currency] += balance.amount;
63.37      |           ^
63.37   76 |         }
63.37   77 |       }
63.37   78 |
------
failed to solve: process "/bin/sh -c npm run just-build" did not complete successfully: exit code: 1

thanks for trying it out, i changed how docker setup works in splitpro and it should work now. https://github.com/oss-apps/split-pro/tree/main/docker

closing this now, lemme know if you face issue using the new docker setup


Get rid of extract

First of all: It looks good.
Maybe we can get around this? https://github.com/preprocess/pre-deferred/blob/master/src/macros.pre#L14
Also, Closures are (unfortunately) very slow in php, maybe we can dig around this(even when this only affects the end of the application, but this still matters e.g. in web apps)?

Addressed in https://github.com/preprocess/pre-deferred/pull/2


Fixed null row error

Don't forget to remove:
./idea folder's files

Your repo contains this folder. 👀


Prototype support for stereo-instanced AR Occlusion on HoloLens

As developers become increasingly interested in occlusion (https://github.com/BabylonJS/BabylonReactNative/issues/39) with ARKit/ARCore/OpenXR exposing their own possibilities, we should attempt to find a method for occluding virtual content that is both efficient and secure.
The WebXR group has a repo for tracking ideas, and we have an issue posted there that goes over the current state of occlusion support across different vendors and offers a below-the-line approach to occlusion rendering:
https://github.com/immersive-web/occlusion/issues/1
We already have changes in-flight to add mesh detection support (#476), and we currently have the option of adding the detected meshes to the scene with the BJS occlusion material (https://github.com/BabylonJS/Babylon.js/pull/9387), but this doesn't necessarily work from a security perspective with WebXR, as there are still many data privacy concerns around exposing real-world data.
Even if we weren't worried about WebXR compatibility, this is still a good opportunity for us to explore adding stereo instancing support to BabylonNative without needing to do anything on the BJS side. This would be a huge performance win on XR, especially on HoloLens, where framerate will be the first to flag when we begin creating more complex scenes.

Closing for now. Reopen if we want to support this feature.


Rework API requests

Description
Rework API request : GET
Related issue (if applicable): fixes #70
Checklist

[x] The code change is tested and works locally.
[x] tests pass. Your PR won't be merged unless tests pass
[x] There is no commented out code in this PR

Thx @markusressel

Done 👍

Forget something in upload picture

Ok now I have to rework grocy.py.
Maybe today or tomorrow.

Sorry, wrong branch...

Fixing


SPF Macro Support

Any plans on supporting SPF macros?

This library already sypports SPF macros.

Hmm. I will do some more testing and get back to you at a later date. I was having some spf fails previously. Here is an example of the SPF record:
d: z.co.nz
i: <IP_ADDRESS>
h: aus01-sy4-obe.outbound.protection.outlook.com
"v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all"
When I manually resolved everything it checked out, but was failing when using the library. I will do some more testing.
Can you point me to the bit of code where it processes the logic for SPF macros? I want to try and debug to figure out what I may be doing wrong.

When I manually resolved everything it checked out, but was failing when using the library. I will do some more testing.

Could you show me the code that fails?

The basic jist of it. The "if" that will fire 99% of the time is the first one with the helo_name. I am wondering if that may be causing some of the issue. If I run it with just the sender and the IP it passes with no problem.
`
if($cfg['helo_checks'] != 'no'){
$environment = new \SPFLib\Check\Environment($pfx_data['client_address'], $pfx_data['helo_name'], $pfx_data['sender']);
}else{
$environment = new \SPFLib\Check\Environment($pfx_data['client_address'], '', $pfx_data['sender']);
}
			$checker = new Checker();
			$checkResult = $checker->check($environment);
			$spf_result = trim(strtolower($checkResult->getCode()));

switch ($spf_result) {
case 'none':
case 'neutral':

case 'pass':

case 'fail':

case 'softfail':

case 'temperror':

case 'permerror':

}
`

The code insert thing doesn't seem to be working. Apologies. IT is there, just not formatted as desired.

The code insert thing doesn't seem to be working. Apologies. It is there, just not formatted as desired.

Are you referring to the way GitHub formatted your comment above?
If so, I've fixed its formatting.
PS: you can insert code blocks enclosing it with three backticks.
For example, if you write
```
if (true) {
    echo 1;
}
```

it will be rendered as
if (true) {
    echo 1;
}

You can also specify the programming language, to turn on syntax highlighting.
For example:
```php
if (true) {
    echo 1;
}
```

it will be rendered as
if (true) {
    echo 1;
}

Back to your example, could you share the values of $cfg['helo_checks'], $pfx_data['client_address'], $pfx_data['helo_name'], $pfx_data['sender'] that aren't working for you?

The $cfg variable is just a set values used to turn features on and off when I incorporate into a larger codeset. $cfg['helo_checks'] simply turns EHLO checking on or off. If it is on, it will also pass the EHLO value in the new $environment.
$pfx_data is just an array of what is passed by postfix. (remote ip, EHLO, sender email. ) I created a unix policy service check in postfix for SPF checks. Apologies, I assumed the names would have been self explanatory. The values used in this example are in my earlier comments. Again below.
d: z.co.nz
i: <IP_ADDRESS>
h: aus01-sy4-obe.outbound.protection.outlook.com
"v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all"

We've had a little misunderstanging here 😉 I wasn't asking about the meaning of the arrays, but the actual values that fail for you.
So, to summarize, the case that's failing for you is:

$cfg['helo_checks'] is not no
$pfx_data['client_address'] contains <IP_ADDRESS>
$pfx_data['helo_name'] contains aus01-sy4-obe.outbound.protection.outlook.com
$pfx_data['sender'] contains z.co.nz

So, in order to replicate your issue, the code is:
$environment = new \SPFLib\Check\Environment(
    '<IP_ADDRESS>',
    'aus01-sy4-obe.outbound.protection.outlook.com',
    'z.co.nz'
);

$checker = new \SPFLib\Checker();
$checkResult = $checker->check($environment);

And you expect that $checkResult->getCode() should be pass.
That's correct?

Just noticed I never closed the issue. Only took over a year for me to notice. Thanks for the feedback!. You were of course correct.


Refactor API interface to have multiple mappings

Resolves #18

Coverage decreased (-0.0007%) to 99.108% when pulling bba2f687115e2a058bb85570f5b98fa1fa61e1d2 on enhacement/#18 into 9a81e77e27fff7078d2fee06b4f5cbab40f20e16 on master.


segfault on mac arm

My environment:
2.4.8
Commercial: None
Python: 3.12.4 (main, Jun  6 2024, 18:26:44) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
Flavor: Homebrew Python
Executable: ~/virtualenv/bin/python
OS: Darwin
Arch: arm64
macOSRelease: 14.6.1
Version C compiler: /usr/bin/clang (clang 15.0.0).

nuikta installed on venv/pip with this requirements.txt:
PySide6==6.7.2
nuitka==2.4.8

Minimal example code:
from PySide6.QtCore import Qt
from PySide6.QtWidgets import QApplication, QMainWindow

# nuitka-project: --standalone
# nuitka-project: --enable-plugin=pyside6
# nuitka-project: --macos-create-app-bundle
# nuitka-project: --debug

class MainWindow(QMainWindow):
    def __init__(self):
        super().__init__()

app = QApplication()
app.exec()

This is not enough information to reproduce because there is no pip list -v output.

With CPython and not Homebrew, and current 2.5 release, I am getting this:
Assertion failed: (Py_REFCNT((&_Py_NoneStruct)) == _Py_IMMORTAL_REFCNT), function Nuitka_Function_New, file CompiledFunctionType.c, line 1328.

That is because older PySide6 is not fully compatible with Python3.12 immortal objects, and accidentically de-immortalizes them, which is semi-OK, Python survives that, but debug mode of Nuitka wants to identify cases where it expects to deal with immortal objects, but then they are not immortal. Can be disabled with --no-debug-immortal-assumptions for at least since 2.5 release, maybe sooner, and then it runs fine. There is no segfault, but an abort.
As such this is not a Nuitka issue, surely PySide6 is being improved eventually to no longer do that. I think Python had assertions against that, but removed them for release, but maybe 3.13 does them and that will trigger fixes in extension modules more globally.